CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 19:03:32 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=JMj89Hzq56rpcBCV3XjAq_chegi9o0GCUYib2jEKX_k-1760209412-1.0.1.1-3GXAWllppAW6uq2yqmZr40tGWOb.yTrdsCxUQSeMEHxme87QglOavV_4tR_d978RGXD.4Cj7d4tcoTz.OmVdgC2eM9CZUnYkcxZIU3u.654; path=/; expires=Sat, 11-Oct-25 19:33:32 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d09e3868b9755c-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 4893 » RFC Editor
Search RFCs
RFC 4893
BGP Support for Four-octet AS Number Space, May 2007
- File formats:
- Status:
- PROPOSED STANDARD
- Obsoleted by:
- RFC 6793
- Authors:
- Q. Vohra
E. Chen - Stream:
- IETF
- Source:
- idr (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC4893
Discuss this RFC: Send questions or comments to the mailing list idr@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 4893
Abstract
Currently the Autonomous System (AS) number is encoded as a two-octet entity in BGP. This document describes extensions to BGP to carry the Autonomous System number as a four-octet entity. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us