--- 1/draft-ietf-idr-as-representation-00.txt 2008-09-23 00:12:56.000000000 +0200 +++ 2/draft-ietf-idr-as-representation-01.txt 2008-09-23 00:12:56.000000000 +0200 @@ -1,19 +1,18 @@ IDR G. Huston Internet-Draft G. Michaelson -Intended status: Best Current APNIC -Practice September 9, 2008 -Expires: March 13, 2009 +Intended status: Standards Track APNIC +Expires: March 27, 2009 September 23, 2008 Textual Representation of AS Numbers - draft-ietf-idr-as-representation-00.txt + draft-ietf-idr-as-representation-01.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 @@ -24,25 +23,21 @@ 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 March 13, 2009. - -Copyright Notice - - Copyright (C) The IETF Trust (2008). + This Internet-Draft will expire on March 27, 2009. Abstract A textual representation for Autonomous System (AS) numbers is defined as the decimal value of the AS Number. This textual representation is to be used by all documents, systems and user interfaces referring to AS numbers. 1. Introduction @@ -55,49 +50,50 @@ proposes the adoption of a decimal value notation for AS numbers, or "asplain" according to the representation taxonomy described here. 2. Taxonomy of Representation Formats A taxonomy of representation for AS numbers is as follows: asplain refers to a syntax scheme of representing all AS numbers using decimal integer notation. Using asplain notation an AS number of - value 65526 would be represented as the string "65526" and as AS + value 65526 would be represented as the string "65526" and an AS number of value 65546 would be represented as the string "65546". asdot+ refers to a syntax scheme of representing all AS numbers using a notation of two integer values joined by a period character: .. Using asdot+ notation, an AS number of value 65526 would be represented as the string "0.65526" and an AS number of value 65546 would be represented as the string "1.10". asdot refers to a syntax scheme of representing AS number values less than 65536 using asplain notation and representing AS number values equal to or greater than 65536 using asdot+ notation. Using asdot notation, an AS number of value 65526 would be - represented as the string "65526" and as AS number of value 65546 + represented as the string "65526" and an AS number of value 65546 would be represented as the string "1.10". 3. Representation of AS Number Values To avoid confusion, a single textual notation is useful for documentation, configuration systems, reports, and external tools and information repositories. The decimal value representation, or - "asplain" is proposed as the textual notiation to use for AS Numbers. + "asplain" is proposed as the textual notation to use for AS Numbers. The "asplain" representation represents the number as its decimal - value, without any field delimiter, corresponding to to lack of any - internal fields defined by the semantics AS numbers. + value, without any field delimiter, corresponding to the lack of any + internal structure required by the use of AS numbers in the inter- + domain routing context. 4. IANA Considerations IANA Registries should use decimal representation ("asplain") for AS numbers. 5. Security Considerations This document does not refer to matters associated with security of routing systems. @@ -157,15 +153,10 @@ 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).