1 / 4

Updates to 6LoWPAN Interface Identifier (IID) Derivation and Mesh Delivery Header

This document discusses the changes made to the 6LoWPAN Interface Identifier (IID) derivation using 16-bit short addresses and the updated mesh delivery header format. It includes information on the use of PAN ID in IID derivation, transmission reassembly, multicast address mapping, and various editorial changes.

patsyd
Download Presentation

Updates to 6LoWPAN Interface Identifier (IID) Derivation and Mesh Delivery Header

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 6LoWPAN Meeting65 IETF DallasFormat Document changes March 24, 2006

  2. Latest changes 1 • Interface Identifier derivation (IID) using 16-bit short addresses now using the PAN ID as well: • 16_zero_bits:PAN_ID:16-bit_short_address • 48 bits above converted to IID as usual • Word of caution on the transient nature of 16 bit short addresses. • Reassembly now also keying on • destination and datagram_size. • In addition to source and tag previously used

  3. Latest changes 2 • Mesh delivery header now allowing a mix of 16/64 bit addresses. This leaves 6 bits for hops_left (64 hops is plenty). • This supports mesh layer “broadcast” (which uses 16-bit short addresses) • Added Multicast Address mapping patterned after that of ethernet • Error in the draft! Must reduce to 16 from 32 bits as follows: • 0 0 1 1 0 0 1 1 | last_16_bits_of_IPv6_mcast_addr • presumably this *mesh* layer mcast could map to things such as: • dumb flooding • controlled flooding • unicasting to the PAN COORDINATOR • etc • Clarified that “all zero” addresses must not be used • for either 16 or 64 bit formats • Sundry editorial changes.

  4. To Discuss • unicast address mapping to optionally allow both 64 and 16bit addresses? • How to handle two L2 addresses with different stability characteristics? • No discussion, so left it out for now • Should the combined 16/64 bit format be there in addition to the other two? • In order to distinguish between 16/64 combined and 64 only, a 16-bit address cannot be all zeros (so as to distinguish with the padding in the 64 bit case). So added some verbage to the effect that for either 64 or 16 bit addresses, the all zero addresses must not be used.

More Related