--- 1/draft-ietf-idr-bgp-identifier-08.txt 2008-05-13 20:12:14.000000000 +0200 +++ 2/draft-ietf-idr-bgp-identifier-09.txt 2008-05-13 20:12:14.000000000 +0200 @@ -1,18 +1,18 @@ -Network Working Group Enke Chen -Internet Draft Jenny Yuan -Expiration Date: May 2007 Cisco Systems +IDR Working Group E. Chen +Internet Draft J. Yuan +Expiration Date: November 2008 Cisco Systems AS-wide Unique BGP Identifier for BGP-4 - draft-ietf-idr-bgp-identifier-08.txt + draft-ietf-idr-bgp-identifier-09.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -126,54 +126,81 @@ BGP sessions between two BGP speakers). Therefore it is concluded that the revisions proposed in this document do not introduce any backward compatibility issue with the current usage of the BGP Identifier. 4. Security Considerations This extension to BGP does not change the underlying security issues. -5. Acknowledgments +5. IANA Considerations + + This document has no actions for IANA. + +6. Acknowledgments The authors would like to thank members of the IDR Working Group for discussions on the "IPv6-only Network" related issues that inspired this document. -6. Normative References +7. Normative References [BGP-4] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, January 2006. [BGP-4BYTE-AS] Vohra, Q., and E. Chen, "BGP Support for Four-octet AS - Number Space", Work in Progress, , - November 2005. + Number Space", RFC 4893, May 2007. -7. Author Information +8. Author Information Enke Chen Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134 EMail: enkechen@cisco.com Jenny Yuan Cisco Systems, Inc. 170 W. Tasman Dr. San Jose, CA 95134 EMail: jenny@cisco.com -8. Full Copyright Notice +9. Intellectual Property - Copyright (C) The IETF Trust (2006). + The IETF takes no position regarding the validity or scope of any + Intellectual Property Rights or other rights that might be claimed to + pertain to the implementation or use of the technology described in + this document or the extent to which any license under such rights + might or might not be available; nor does it represent that it has + made any independent effort to identify any such rights. Information + on the procedures with respect to rights in RFC documents can be + found in BCP 78 and BCP 79. + + Copies of IPR disclosures made to the IETF Secretariat and any + assurances of licenses to be made available, or the result of an + attempt made to obtain a general license or permission for the use of + such proprietary rights by implementers or users of this + specification can be obtained from the IETF on-line IPR repository at + http://www.ietf.org/ipr. + + The IETF invites any interested party to bring to its attention any + copyrights, patents or patent applications, or other proprietary + rights that may cover technology that may be required to implement + this standard. Please address the information to the IETF at ietf- + ipr@ietf.org. + +10. Full Copyright Notice + + Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF