rfc-5396

Textual Representation of Autonomous System (AS) Numbers

G. Huston, G. Michaelson
date2008-12 streamIETF areartg wgidr statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc5396 doi10.17487/RFC5396
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. [STANDARDS-TRACK]

Extracted elements (7)

design-rationale §3

A single textual notation (asplain) is proposed to avoid confusion across documentation, configuration systems, reports, and external tools. The decimal value representation requires no field delimiter, reflecting the lack of internal structure required by AS numbers in inter-domain routing.

routing, bgp

normative-requirement §3 MUST

All documents, systems, and user interfaces referring to AS numbers MUST use the decimal value (asplain) textual representation.

routing, bgp

normative-requirement §4 SHOULD

IANA Registries should use decimal representation (asplain) for AS numbers.

routing, bgp, registry

protocol-element §2

asdot+ notation represents all AS numbers as two decimal integers joined by a period, where the left value is the high-order 16 bits and the right is the low-order 16 bits. For example, AS 65526 is '0.65526' and AS 65546 is '1.10'.

routing, bgp

protocol-element §2

asdot notation uses asplain for AS numbers below 65536 and asdot+ for values 65536 and above. For example, AS 65526 is '65526' and AS 65546 is '1.10'.

routing, bgp

protocol-element §2

asplain notation represents all AS numbers as plain decimal integers without any delimiter. For example, AS 65526 is written '65526' and AS 65546 is written '65546'.

routing, bgp

security-consideration §5

This document does not address matters associated with the security of routing systems.

routing, security