draft-ietf-idr-as-representation-00.txt | draft-ietf-idr-as-representation-01.txt | |||
---|---|---|---|---|
IDR G. Huston | IDR G. Huston | |||
Internet-Draft G. Michaelson | Internet-Draft G. Michaelson | |||
Intended status: Best Current APNIC | Intended status: Standards Track APNIC | |||
Practice September 9, 2008 | Expires: March 27, 2009 September 23, 2008 | |||
Expires: March 13, 2009 | ||||
Textual Representation of AS Numbers | Textual Representation of AS Numbers | |||
draft-ietf-idr-as-representation-00.txt | draft-ietf-idr-as-representation-01.txt | |||
Status of this Memo | Status of this Memo | |||
By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
applicable patent or other IPR claims of which he or she is aware | 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 | 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. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
skipping to change at page 1, line 35 | skipping to change at page 1, line 34 | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on March 13, 2009. | This Internet-Draft will expire on March 27, 2009. | |||
Copyright Notice | ||||
Copyright (C) The IETF Trust (2008). | ||||
Abstract | Abstract | |||
A textual representation for Autonomous System (AS) numbers is | A textual representation for Autonomous System (AS) numbers is | |||
defined as the decimal value of the AS Number. This textual | defined as the decimal value of the AS Number. This textual | |||
representation is to be used by all documents, systems and user | representation is to be used by all documents, systems and user | |||
interfaces referring to AS numbers. | interfaces referring to AS numbers. | |||
1. Introduction | 1. Introduction | |||
skipping to change at page 2, line 23 | skipping to change at page 2, line 16 | |||
proposes the adoption of a decimal value notation for AS numbers, or | proposes the adoption of a decimal value notation for AS numbers, or | |||
"asplain" according to the representation taxonomy described here. | "asplain" according to the representation taxonomy described here. | |||
2. Taxonomy of Representation Formats | 2. Taxonomy of Representation Formats | |||
A taxonomy of representation for AS numbers is as follows: | A taxonomy of representation for AS numbers is as follows: | |||
asplain | asplain | |||
refers to a syntax scheme of representing all AS numbers using | refers to a syntax scheme of representing all AS numbers using | |||
decimal integer notation. Using asplain notation an AS number of | 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". | number of value 65546 would be represented as the string "65546". | |||
asdot+ | asdot+ | |||
refers to a syntax scheme of representing all AS numbers using a | refers to a syntax scheme of representing all AS numbers using a | |||
notation of two integer values joined by a period character: <high | notation of two integer values joined by a period character: <high | |||
order 16-bit value in decimal>.<low order 16-bit value in | order 16-bit value in decimal>.<low order 16-bit value in | |||
decimal>. Using asdot+ notation, an AS number of value 65526 | decimal>. Using asdot+ notation, an AS number of value 65526 | |||
would be represented as the string "0.65526" and an AS number of | would be represented as the string "0.65526" and an AS number of | |||
value 65546 would be represented as the string "1.10". | value 65546 would be represented as the string "1.10". | |||
asdot | asdot | |||
refers to a syntax scheme of representing AS number values less | refers to a syntax scheme of representing AS number values less | |||
than 65536 using asplain notation and representing AS number | than 65536 using asplain notation and representing AS number | |||
values equal to or greater than 65536 using asdot+ notation. | values equal to or greater than 65536 using asdot+ notation. | |||
Using asdot notation, an AS number of value 65526 would be | 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". | would be represented as the string "1.10". | |||
3. Representation of AS Number Values | 3. Representation of AS Number Values | |||
To avoid confusion, a single textual notation is useful for | To avoid confusion, a single textual notation is useful for | |||
documentation, configuration systems, reports, and external tools and | documentation, configuration systems, reports, and external tools and | |||
information repositories. The decimal value representation, or | 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 | The "asplain" representation represents the number as its decimal | |||
value, without any field delimiter, corresponding to to lack of any | value, without any field delimiter, corresponding to the lack of any | |||
internal fields defined by the semantics AS numbers. | internal structure required by the use of AS numbers in the inter- | |||
domain routing context. | ||||
4. IANA Considerations | 4. IANA Considerations | |||
IANA Registries should use decimal representation ("asplain") for AS | IANA Registries should use decimal representation ("asplain") for AS | |||
numbers. | numbers. | |||
5. Security Considerations | 5. Security Considerations | |||
This document does not refer to matters associated with security of | This document does not refer to matters associated with security of | |||
routing systems. | routing systems. | |||
skipping to change at page 4, line 44 | skipping to change at line 163 | |||
attempt made to obtain a general license or permission for the use of | attempt made to obtain a general license or permission for the use of | |||
such proprietary rights by implementers or users of this | such proprietary rights by implementers or users of this | |||
specification can be obtained from the IETF on-line IPR repository at | specification can be obtained from the IETF on-line IPR repository at | |||
http://www.ietf.org/ipr. | http://www.ietf.org/ipr. | |||
The IETF invites any interested party to bring to its attention any | The IETF invites any interested party to bring to its attention any | |||
copyrights, patents or patent applications, or other proprietary | copyrights, patents or patent applications, or other proprietary | |||
rights that may cover technology that may be required to implement | rights that may cover technology that may be required to implement | |||
this standard. Please address the information to the IETF at | this standard. Please address the information to the IETF at | |||
ietf-ipr@ietf.org. | ietf-ipr@ietf.org. | |||
Acknowledgment | ||||
Funding for the RFC Editor function is provided by the IETF | ||||
Administrative Support Activity (IASA). | ||||
End of changes. 8 change blocks. | ||||
14 lines changed or deleted | 10 lines changed or added | |||
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |