Individual submission H. Uijterwaal Internet-Draft RIPE NCC Intended status: Standards Track August 23, 2006 Expires: February 24, 2007 RPSL extensions for 32 bit AS Numbers draft-uijterwaal-rpsl-4byteas-ext-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. This Internet-Draft will expire on February 24, 2007. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document specifies extensions to the RPSL language for dealing with 32 bit (4 byte) AS numbers. 1. Introduction Four byte (32 bit) AS numbers (ASN32) are defined in [as4bytes]. This document does not specify a format to represent these numbers. Uijterwaal Expires February 24, 2007 [Page 1] Internet-Draft RPSL extensions for 32 bit AS Numbers August 2006 A separate document [asn32rep] proposes to represent them as: . This format allows users to easily distinguish 16 and 32 bit ASN. RPSL (Routing Policy Specification Language) ([RFC2622] and [RFC4012]) uses the format "ASx" for an AS, with x a 1 to 5 digit number in the range 0 to 65535. RPSL was defined before the introduction of 32 bit AS Number (ASN32). Deployment of ASN32 will start early 2007 [asn32d]. To use these numbers in RPSL, the RPSL standard will have to be updated to allow for ASN32. 2. Proposal The terms "2-byte only AS Numbers" and "4-byte AS numbers" are defined in [asn32rep]. Following [asn32rep], the field in [RFC2622] (section 2) will be replaced by: An is a string that can be either: o ASx, for 2-byte only AS numbers, or o ASy.z for 4-byte AS Numbers, with x and y using the same format as [asn32rep]. x, y and z are integer numbers in the range 0 to 65535. If y equals 0, it can be dropped. For example, AS3333 and AS0.3333 both refer to the AS with identifier 3333. An identifier of AS65536 is not valid, even though the identifier can be expressed in a 32 bit integer. This AS should be referred to as AS1.0. No other changes to the RPSL standard will be made. 3. Security Considerations Many systems will treat strings "xxx.yyy" as real number values and convert this internally to floating point numbers. One must take care that this will not happen. Systems may use unsigned 16-bit integers for the internal Uijterwaal Expires February 24, 2007 [Page 2] Internet-Draft RPSL extensions for 32 bit AS Numbers August 2006 representation of AS numbers. It should be checked that tools internally use (at least) an unsigned 32-bit number for ASN. 4. IANA Considerations None. (This section may be removed on publication as an RFC.) 5. Acknowledgements The author would like to thank Katie Petrusha and Rene Wilhelm for their feedback on this draft. 6. References 6.1. Normative references [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra, "Routing Policy Specification Language (RPSL)", RFC 2622, June 1999. [RFC4012] Blunk, L., Damas, J., Parent, F., and A. Robachevsky, "Routing Policy Specification Language next generation (RPSLng)", RFC 4012, March 2005. [as4bytes] Chen, E. and Q. Vohra, "BGP Support for Four-octet AS Number Space (draft-ietf-idr-as4bytes, work in progress).". [asn32rep] Michaelson, G., "Canonical representation of 4-byte AS- numbers (draft-michaelson-4byte-as-representation, work in progress).". 6.2. Informative references [asn32d] Huston, G., "4-byte AS Number Policy (RIPE PDP 2005-12).". Uijterwaal Expires February 24, 2007 [Page 3] Internet-Draft RPSL extensions for 32 bit AS Numbers August 2006 Author's Address Henk Uijterwaal RIPE NCC Singel 258 1016 AB Amsterdam NL Phone: +31 20 535 4444 Email: henk@ripe.net Uijterwaal Expires February 24, 2007 [Page 4] Internet-Draft RPSL extensions for 32 bit AS Numbers August 2006 Full Copyright Statement Copyright (C) The Internet Society (2006). 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. 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. Intellectual Property 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 procedures with respect to rights in RFC 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 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Uijterwaal Expires February 24, 2007 [Page 5]