[rfc-dist] RFC 5668 on 4-Octet AS Specific BGP Extended Community

rfc-editor at rfc-editor.org (rfc-editor@rfc-editor.org) Wed, 28 October 2009 16:17 UTC

From: "rfc-editor at rfc-editor.org"
Date: Wed, 28 Oct 2009 09:17:46 -0700
Subject: [rfc-dist] RFC 5668 on 4-Octet AS Specific BGP Extended Community
Message-ID: <20091028161746.46895356983@bosco.isi.edu>

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

        
        RFC 5668

        Title:      4-Octet AS Specific BGP Extended 
                    Community 
        Author:     Y. Rekhter, S. Sangli,
                    D. Tappan
        Status:     Standards Track
        Date:       October 2009
        Mailbox:    yakov at juniper.net, 
                    rsrihari at cisco.com, 
                    Dan.Tappan at Gmail.com
        Pages:      5
        Characters: 9017
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as4octet-ext-community-03.txt

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

This document defines a new type of a BGP extended community, which
carries a 4-octet Autonomous System (AS) number.  [STANDARDS TRACK]

This document is a product of the Layer 3 Virtual Private Networks 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute