> You're correct about the lack of RFC2464 compliance (no ff:fe); I had
> it for a while and took it out because it was annoying to type.

Yes, I can imagine.

> I
> guess this isn't a very good attitude towards standards, so if people
> feel strongly about this we can put it back in.

Is it possible to add that as an #ifdef?

> The reason I haven't added support for long EUI-64 based addressing is
> because the messaging layer used by tinyos doesn't support using
> 64-bit addressing mode.  While it would still be possible to use
> 64-bit based IP addresses, it's a little silly since (a) you'd still
> have to manually guarantee that 16-bit short ids are unique in your
> network,

Shouldn't the edge router assign the 16 bit short addresses based on EUI-64 
during bootstrapping?

> and (b) you wouldn't be able to use the L2 address as part of
> the 6lowpan compression scheme.

The assigned 16 bit short address would be your new L2 address and the 
compression would work. Right?

[More below...]

> Steve
> 
> On Mon, Sep 21, 2009 at 7:41 AM, Markus Becker
> 
> <[email protected]> wrote:
> > Hello,
> >
> > I am currently trying out BLIP from tinyos-2.x CVS head. When working
> > with it, a few questions came up:
> >
> > IPAddressP allows for setting the 16 bit short address (which also
> > changes TOS_NODE_ID). From that the Link Local Address is derived by:
> >
> > EUI-48 = PAN_ID(16*'0') + 16*'0' + 16 bit TOS_NODE_ID
> > 6LOWPAN_IP_ADDR = FE80::/64 + 16*'0' + EUI-48
> >
> > According to RFC 4944 Section 6 and 7 shouldn't this be:
> >
> > EUI-48 = PAN_ID(16*'0') + 16*'0' + 16 bit TOS_NODE_ID
> > 6LOWPAN_IP_ADDR = FE80::/64 + EUI48_TO_EUI64_RFC2464(EUI-48)
> > where EUI48_TO_EUI64_RFC2464(EUI-48) inserts FF:FE in the middle?
> >
> > Could additionally the setting of the long address, which is also
> > described in RFC4944, be added to the IPAddress interface?
> >
> > E.g. like this:
> >
> >  command void IPAddress.setLongAddr(ieee_eui64_t newAddr) {};
> >
> > I am trying to put the SerialID of the DS2411 chip to some use, instead
> > of using TOS_NODE_ID for the IPv6 address.

In the meantime I created a mote DB component, which I can wire in, that maps 
the DS2411 serialID to a pre-determined 16 bit short address and thus IPv6 
address. On bootup the mote reads its serialID, checks the serialID against 
the DB to get a fixed TOS_NODE_ID that replaces the programmed one. This way I 
do not need to take care of the addresses while installing the motes.

Markus

> > BR,
> > Markus
> >
> > ------------------------------------------------
> >
> > | ATTENTION: NEW TELEPHONE EXTENSION!
> >
> > ------------------------------------------------
> >
> > | Dipl.-Ing. Markus Becker
> > | Communication Networks
> > | Mobile Research Center
> > | TZI - Center for Computing Technologies
> > | University Bremen
> > | Germany
> >
> > ------------------------------------------------
> >
> > | web: http://www.comnets.uni-bremen.de/~mab/
> > | mailto: [email protected]
> > | telephone: +49 421 218 62379
> > | building: NW1 room: N2260
> >
> > ------------------------------------------------
> 
------------------------------------------------
| ATTENTION: NEW TELEPHONE EXTENSION!
------------------------------------------------
| Dipl.-Ing. Markus Becker
| Communication Networks
| Mobile Research Center
| TZI - Center for Computing Technologies
| University Bremen
| Germany
------------------------------------------------
| web: http://www.comnets.uni-bremen.de/~mab/
| mailto: [email protected]
| telephone: +49 421 218 62379
| building: NW1 room: N2260
------------------------------------------------
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to