Internet-Draft J. G. Jin Expire: December 2005 Y. J. Kim MODACOM June 2005 Transmission of IPv6 Packets over IEEE802.16 Networks draft-jin-ipv6-over-ieee802.16-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright Notice Copyright (C) The Internet Society (2005). All Rights Reserved. Abstract This document specifies the transmission of IPv6 packet over 802.16 networks. The specification includes the MTU size of IPv6 packets, the frame format for transmission of IPv6 packets, the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE802.16 networks. It also specifies the content of the Source/Target Link-layer Address option used in Neighbor Jin & Kim Expires: December 2005 [Page 1] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 Discovery Protocol specified in RFC2461 [DISC] when those messages are transmitted on an IEEE802.16 network. Table of Contents 1. Introduction.................................................2 2. Terminology..................................................3 3. Maximum Transmission Unit....................................3 4. Frame Format.................................................4 5. Stateless Autoconfiguration..................................5 6. Link-Local Addresses.........................................5 7. Address Mapping -- Unicast...................................6 8. Address Mapping -- Multicast.................................6 9. Security Considerations......................................7 10. References...................................................7 10.1 Normative References........................................7 10.2 Informative References......................................7 11. Authors' Addresses...........................................8 1. Introduction This document specifies the transmission of IPv6 packet over 802.16 networks. The specification includes the MTU size of IPv6 packets, the frame format for transmission of IPv6 packets, the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE802.16 networks. It also specifies the content of the Source/Target Link-layer Address option used in Router Solicitation, Router Advertisement, Neighbor Solicitation, Neighbor Advertisement and Redirect messages when those messages are transmitted on an IEEE802.16 network. IEEE802.16 standard is to provide reliable, broadband, fast wireless connectivity in anywhere. IEEE802.16d specifies fixed broadband wireless access and IEEE802.16e specifies an amendment of PHY/MAC access control layer to support mobile connection. Specially, 802.16e support Mobile Subscriber Station (MSS) moving at vehicular speeds and thereby specifies a fixed and mobile broadband wireless access, anytime and anywhere. This document is applicable to both IEEE802.16d and IEEE802.16e networks. The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in [KEYWORDS] Jin & Kim Expires: December 2005 [Page 2] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 2. Terminology This document borrows all of the terminology from RFC2464 [IPv6oE], with the following additional terms from the IEEE802.16 specification [WirelessMAN]. SS Subscriber Station. A generalized equipment set providing connectivity between subscriber equipment and a base station (BS) MSS Mobile Subscriber Station. A subscriber station that supports communications while in motion. BS Base Station. A Generalized equipment set providing connectivity, management, and control of the subscriber station (SS) PDU Protocol Data Unit. The data unit exchanged between peer entities of the same protocol layer. On the downward direction, it is the data unit generated for the next lower layer. On the upward direction, it is the data unit received from the previous lower layer. SDU Service Data unit. The data unit exchanged between two adjacent protocol layers. On the downward direction, it is the data unit received from the previous higher layer. On the upward direction, it is the data unit sent to the next higher layer. PHSI Payload Header Suppression Index. An 8 bits mask that indicates which bytes in the Payload Header Suppression Field (PHSF) to suppress and which bytes to not suppress. 3. Maximum Transmission Unit The default MTU size for IPv6 [IPV6] packets on an IEEE802.16 is 2041 octets because the size of IEEE802.6 MAC PDU is represented by 11 bits in bytes and the MAC PDU includes 6 bytes Generic MAC Header, optional Payload and optional CRC. This size may be reduced by a Router Advertisement [DISC] containing an MTU option which specifies a smaller MTU, or by manual configuration of each node. If a Router Advertisement received on an Ethernet interface has an MTU option specifying an MTU larger than 2041, or larger than a manually configured value, that MTU option may be logged to system management but must be otherwise ignored. For purposes of this document, information received from DHCP is considered "manually configured". Jin & Kim Expires: December 2005 [Page 3] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 4. Frame Format IPv6 packets are transmitted in standard IEEE802.16 MAC PDUs. The MAC PDU includes Generic MAC Header, optional Payload and optional CRC. The Payload contains the IPv6 header followed immediately by the IPv6 payload, and possibly padding octets to meet the minimum frame size for the IEEE802.16 MAC PDU. MSB LSB +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+//+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Generic MAC Header | Payload (Optional) | CRC (Optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+//+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Generic MAC Header Formats in the MAC PDUs have the form illustrated in below. 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |H|E| Type |R|C|EKS|R|LEN | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | LEN LSB | CID MSB | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | CID LSB | HCS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ HT Header Type. Shall be set to zero EC Encryption Control. Payload is encrypted (1) Type The subheaders and special payload types present in the message payload. R Reserved. Mode Selection Feedback type (Defined at IEEE802.16e) C CRC Indicator. 1= CRC is included in the PDU by appending it to the PDU payload after encryption EKS Encryption Key Sequence R Reserved Jin & Kim Expires: December 2005 [Page 4] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 LEN The Length in bytes of the MAC PDU including the MAC header and the CRC if present CID Connection Identifier HCS Header Check Sequence 5. Stateless Autoconfiguration The Interface Identifier [AARCH] for a IEEE802.16 interface is based on the EUI-64 identifier [EUI64] derived from the interface's built- in 48-bit IEEE802 universal MAC address. This address uniquely defines the SS from within the set of all possible vendors and equipment types. It is used during the initial ranging process to establish the appropriate connections for an SS. It is also used as part of the authentication process by which the BS and SS each verify the identity of the other. The Interface Identifier is then formed from the EUI-64 by complementing the "Universal/Local" (U/L) bit, which is the next-to- lowest order bit of the first octet of the EUI-64. Complementing this bit will generally change a 0 value to a 1, since an interface's built-in address is expected to be from a universally administered address space and hence have a globally unique value. A universally administered IEEE 802 address or an EUI-64 is signified by a 0 in the U/L bit position, while a globally unique IPv6 Interface Identifier is signified by a 1 in the corresponding position. For further discussion on this point, see [AARCH]. A different MAC address set manually or by software should not be used to derive the Interface Identifier. If such a MAC address must be used, its global uniqueness property should be reflected in the value of the U/L bit. An IPv6 address prefix used for stateless autoconfiguration [ACONF] of an Ethernet interface must have a length of 64 bits. 6. Link-Local Addresses The IPv6 link-local address [AARCH] for a IEEE802.16 interface is formed by appending the Interface Identifier, as defined above, to the prefix FE80::/64. Jin & Kim Expires: December 2005 [Page 5] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 10 bits 54 bits 64 bits +----------+-----------------------+----------------------------+ |1111111010| (zeros) | Interface Identifier | +----------+-----------------------+----------------------------+ 7. Address Mapping -- Unicast The procedure for mapping IPv6 unicast addresses into 802.16 link- layer addresses is described in [DISC]. The Source/Target Link-layer Address option has the following form when the link layer is IEEE802.16. 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | +- 802.16 MAC -+ | | +- Address -+ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Option fields: Type 1 for Source Link-layer address. 2 for Target Link-layer address. Length 1 (in units of 8 octets). 802.16 MAC Address The 48-bit IEEE802 address, in canonical bit order. This is the address the interface currently responds to, and may be different from the built-in address used to derive the Interface Identifier. 8. Address Mapping -- Multicast An IPv6 packet with a multicast destination address DST, consisting of the sixteen octets DST[1] through DST[16], is transmitted to the Ethernet multicast address whose first two octets are the value 3333 hexadecimal and whose last four octets are the last four octets of DST. Jin & Kim Expires: December 2005 [Page 6] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0 1 1 0 0 1 1|0 0 1 1 0 0 1 1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | DST[13] | DST[14] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | DST[15] | DST[16] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 9. Security Considerations The method of derivation of Interface Identifiers from MAC addresses is intended to preserve global uniqueness when possible. However, there is no protection from duplication through accident or forgery. 10. References 10.1 Normative References [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [WirelessMAN] "Part 16: Air Interface for Fixed Broadband Wireless Access Systems, IEEE WirelessMAN 802.16, IEEE Computer Society, IEEE Std 802.16-2004, October 2004. "Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems, IEEE WirelessMAN 802.16, IEEE Computer Society, IEEE P802.16e/D5, September 2004. [ACONF] Thomson, S. and T. Narten, "IPv6 Stateless Address Autoconfiguration", RFC 2462, December 1998. [IPv6oE] Crawford M., "Transmission of IPv6 Packets over Ethernet Networks", RFC 2464, December 1998. 10.2 Informative References Jin & Kim Expires: December 2005 [Page 7] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 [AARCH] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 2373, July 1998. [EUI64] "Guidelines For 64-bit Global Identifier (EUI-64), http://standards.ieee.org/db/oui/tutorials/EUI64.ht ml [IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998. [DISC] Narten, T., Nordmark, E. and W. Simpson, "Neighbor Discovery for IP Version 6 (IPv6)", RFC 2461, December 1998. 11. Authors' Addresses Jae Gyeong Jin (Editor) MODACOM CO., LTD Korea Phone: +82 2 523 7677 (Ext. 715) Email: jkjin@modacom.co.kr Yong Jin Kim (Editor) MODACOM CO., LTD Korea Phone: +82 2 523 7677 (Ext. 700) Email: cap@modacom.co.kr Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the IETF's procedures with respect to rights in IETF Documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use Jin & Kim Expires: December 2005 [Page 8] Internet-Draft IPv6 Packets over IEEE802.16 Networks June 2005 of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Jin & Kim Expires: December 2005 [Page 9]