draft-ietf-idr-as4bytes-03.txt   draft-ietf-idr-as4bytes-04.txt 
Network Working Group Quaizar Vohra Network Working Group Quaizar Vohra
Internet Draft Juniper Networks Internet Draft Juniper Networks
Expiration Date: November 2001 Enke Chen Expiration Date: March 2002 Enke Chen
Network Working Group Redback Networks, Inc. Network Working Group Redback Networks, Inc.
BGP support for four-octet AS number space BGP support for four-octet AS number space
draft-ietf-idr-as4bytes-03.txt draft-ietf-idr-as4bytes-04.txt
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 6, line 31 skipping to change at page 6, line 31
is encoded in 4 octets). When such aggregation results in creating a is encoded in 4 octets). When such aggregation results in creating a
route that is less specific than any of the component routes, (route route that is less specific than any of the component routes, (route
whose NLRI covers NLRI of all the component routes), loss of the AS whose NLRI covers NLRI of all the component routes), loss of the AS
path information does not create a risk of a routing loop. In all path information does not create a risk of a routing loop. In all
other cases loss of the AS path information does create a risk of a other cases loss of the AS path information does create a risk of a
routing loop. routing loop.
7. IANA Consideration 7. IANA Consideration
This document uses a BGP Capability code to indicate that a BGP This document uses a BGP Capability code to indicate that a BGP
speaker supports the 4-octets AS numbers. The Capability code needs speaker supports the 4-octets AS numbers. The Capability code has
to be assigned by IANA per RFC 2842. Capability Code values 1 through been assigned by IANA per RFC 2842.
63 are to be assigned by IANA using the "IETF Consensus" policy
defined in RFC2434.
In addition, this document introduces two new BGP optional transitive In addition, this document introduces two new BGP optional transitive
attributes. The first is the NEW_AS_PATH attribute, which preserves attributes. The first is the NEW_AS_PATH attribute, which preserves
the AS path information with 4-octet AS numbers across old BGP the AS path information with 4-octet AS numbers across old BGP
speakers. The second is the NEW_AGGREGATOR attribute, which is speakers. The second is the NEW_AGGREGATOR attribute, which is
similar in use to the current AGGREGATOR attribute but it carries similar in use to the current AGGREGATOR attribute but it carries
4-octet AS numbers. The Type Codes for these attributes are to be 4-octet AS numbers. The Type Codes for these attributes has been
assigned by IANA. assigned by IANA.
Finally, this document introduces a reserved 2-octets AS number - Finally, this document introduces a reserved 2-octets AS number -
AS_TRANS. The AS number for AS_TRANS is to be assigned by the IANA. AS_TRANS. The AS number for AS_TRANS has been assigned by the IANA.
8. Security Considerations 8. Security Considerations
Security issues are not discussed in this document. Security issues are not discussed in this document.
9. Acknowledgments 9. Acknowledgments
The authors would like to thank Yakov Rekhter, Chaitanya Kodeboyina, The authors would like to thank Yakov Rekhter, Chaitanya Kodeboyina,
and Jeffrey Haas for the numerous discussions which went into the and Jeffrey Haas for the numerous discussions which went into the
making of this draft. making of this draft.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/