Thread Links			Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

Re: [STDS-802-16] mesh net routing

To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] mesh net routing
From: Markus Kiennen <fastjack@GMX.DE>
Date: Mon, 16 Oct 2006 07:53:50 +0200
In-Reply-To: <003401c6f0be$421fa360$928a10ac@cosmobic.local>
List-Help: <http://listserv.ieee.org/cgi-bin/wa?LIST=STDS-802-16>, <mailto:LISTSERV@LISTSERV.IEEE.ORG?body=INFO STDS-802-16>
List-Owner: <mailto:STDS-802-16-request@LISTSERV.IEEE.ORG>
List-Subscribe: <mailto:STDS-802-16-subscribe-request@LISTSERV.IEEE.ORG>
List-Unsubscribe: <mailto:STDS-802-16-unsubscribe-request@LISTSERV.IEEE.ORG>
References: <FA27FC86ED7F864988659D2E385C3E0E9827A9@cool.research.att.com> <452BFE6A.40909@gmx.de> <452CBCC1.7040504@gmx.de> <452F9E93.3070508@gmx.de> <003401c6f0be$421fa360$928a10ac@cosmobic.local>
Reply-To: Markus Kiennen <fastjack@GMX.DE>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)

Will Lee wrote:
> If the NodeID is not contained, a reception node will not where the message in the mesh network comes after many routing hops.

Higher layers would know? (IP)

Follow-Ups:
- Re: [STDS-802-16] mesh net routing
  - From: Will Lee <will.lee@COSMOBIC.COM>

References:
- Re: [STDS-802-16] mesh net routing
  - From: macsbug@RESEARCH.ATT.COM
- Re: [STDS-802-16] mesh net routing
  - From: Markus Kiennen <fastjack@GMX.DE>
- Re: [STDS-802-16] mesh net routing
  - From: Markus Kiennen <fastjack@GMX.DE>
- Re: [STDS-802-16] mesh net routing
  - From: Markus Kiennen <fastjack@GMX.DE>
- Re: [STDS-802-16] mesh net routing
  - From: Will Lee <will.lee@COSMOBIC.COM>

Prev by Date: Re: [STDS-802-16] mesh net routing
Next by Date: Re: [STDS-802-16] mesh net routing
Prev by thread: Re: [STDS-802-16] mesh net routing
Next by thread: Re: [STDS-802-16] mesh net routing
Index(es):
- Date
- Thread