transmission of ipv6 packets over ieee 802.15.4 wednesday, november 10, 2004 61 st ietf, washington...

4
Transmission of IPv6 Packets over IEEE 802.15.4 Wednesday, November 10, 2004 61 st IETF, Washington D.C. Monroe East, 1530-1730 Gabriel Montenegro - Sun

Upload: colin-gregory

Post on 06-Jan-2018

214 views

Category:

Documents


1 download

DESCRIPTION

Topics (1 of 2) IEEE mode for IP Contention-based channel access (csma/ca) not Guaranteed Time Service (GTS) Frame format How to carry IPv6 packets within 15.4 packets Address generation EUI-64 addresses for IEEE Interface ID obtained via Addressing Architecture (RFC 3513) But also: mapping to 16-bit addresses possible Autoconfiguration and link-local addresses Adaptation Small Data Payload for IEEE max is 102 (aMaxMACFrameSize) Need a shim or adaptation layer as min IPv6 MTU is 1280 Other functions in this shim (Mesh, Header compression, etc)?

TRANSCRIPT

Page 1: Transmission of IPv6 Packets over IEEE 802.15.4 Wednesday, November 10, 2004 61 st IETF, Washington D.C. Monroe East, 1530-1730 Gabriel Montenegro - Sun

Transmission of IPv6 Packets over IEEE 802.15.4

Wednesday, November 10, 2004

61st IETF, Washington D.C.

Monroe East, 1530-1730

Gabriel Montenegro - Sun

Page 2: Transmission of IPv6 Packets over IEEE 802.15.4 Wednesday, November 10, 2004 61 st IETF, Washington D.C. Monroe East, 1530-1730 Gabriel Montenegro - Sun

Why this document?• Basic requirement to run IPv6

• “IPv6 over Foo”• “Sub-IP” section in node-requirements document• Other Examples of “IPv6 over Foo” documents

• Ethernet – RFC 2464• PPP – RFC 2472• ATM - RFC 2492• IEEE 1394 – RFC 3146

• MAR 2005: Send to IESG as Proposed Standard

Page 3: Transmission of IPv6 Packets over IEEE 802.15.4 Wednesday, November 10, 2004 61 st IETF, Washington D.C. Monroe East, 1530-1730 Gabriel Montenegro - Sun

Topics (1 of 2)• IEEE 802.15.4 mode for IP

• Contention-based channel access (csma/ca) not Guaranteed Time Service (GTS)

• Frame format• How to carry IPv6 packets within 15.4 packets

• Address generation• EUI-64 addresses for IEEE 802.15.4• Interface ID obtained via Addressing Architecture (RFC 3513)• But also: mapping to 16-bit addresses possible• Autoconfiguration and link-local addresses

• Adaptation• Small Data Payload for IEEE 802.15.4

• max is 102 (aMaxMACFrameSize)• Need a shim or adaptation layer as min IPv6 MTU is 1280 • Other functions in this shim (Mesh, Header compression, etc)?

Page 4: Transmission of IPv6 Packets over IEEE 802.15.4 Wednesday, November 10, 2004 61 st IETF, Washington D.C. Monroe East, 1530-1730 Gabriel Montenegro - Sun

Topics (2 of 2)• Mesh

• Layer 2 (Sub-IP) mesh using, say, AODV “lite” (intra-PAN)• Layer 3 (Supra-IP) mesh also possible (e.g., 15.4 + UWB) (inter-

PAN)• Header compression

• Not a luxury• Integration of L2/L3 headers into one single compressed header• Context build-up via configuration phase (not just typical

negotiation)• Header compression in a mesh scenario