[rfc-dist] RFC 4893 on BGP Support for Four-octet AS Number Space

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri May 18 17:32:36 PDT 2007


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4893

        Title:      BGP Support for Four-octet AS 
                    Number Space 
        Author:     Q. Vohra, E. Chen
        Status:     Standards Track
        Date:       May 2007
        Mailbox:    quaizar.vohra at gmail.com, 
                    enkechen at cisco.com
        Pages:      10
        Characters: 21520
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-as4bytes-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4893.txt

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]

This document is a product of the Inter-Domain Routing
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list