draft-ietf-idr-as4octet-extcomm-generic-subtype-00.txt   draft-ietf-idr-as4octet-extcomm-generic-subtype-01.txt 
Network Working Group D. Rao Network Working Group D. Rao
Internet-Draft P. Mohapatra Internet-Draft P. Mohapatra
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: July 30, 2009 J. Haas Expires: April 29, 2010 J. Haas
Arbor Networks Arbor Networks
January 26, 2009 October 26, 2009
Generic Subtype for BGP Four-octet AS specific extended community Generic Subtype for BGP Four-octet AS specific extended community
draft-ietf-idr-as4octet-extcomm-generic-subtype-00.txt draft-ietf-idr-as4octet-extcomm-generic-subtype-01.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on July 30, 2009. This Internet-Draft will expire on April 29, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents in effect on the date of
(http://trustee.ietf.org/license-info) in effect on the date of publication of this document (http://trustee.ietf.org/license-info).
publication of this document. Please review these documents Please review these documents carefully, as they describe your rights
carefully, as they describe your rights and restrictions with respect and restrictions with respect to this document.
to this document.
Abstract Abstract
Maintaining the current best practices with communities, ISPs and Maintaining the current best practices with communities, ISPs and
enterprises that are assigned a 4-octet AS number may want the BGP enterprises that are assigned a 4-octet AS number may want the BGP
UPDATE messages they receive from their customers or peers to include UPDATE messages they receive from their customers or peers to include
a 4-octet AS specific extended community. This document defines a a 4-octet AS specific extended community. This document defines a
new sub-type within the four-octet AS specific extended community to new sub-type within the four-octet AS specific extended community to
facilitate this practice. facilitate this practice.
skipping to change at page 5, line 34 skipping to change at page 5, line 34
6. Security Considerations 6. Security Considerations
There are no additional security risks introduced by this design. There are no additional security risks introduced by this design.
7. Normative References 7. Normative References
[I-D.ietf-l3vpn-as4octet-ext-community] [I-D.ietf-l3vpn-as4octet-ext-community]
Rekhter, Y., Sangli, S., and D. Tappan, "Four-octet AS Rekhter, Y., Sangli, S., and D. Tappan, "Four-octet AS
Specific BGP Extended Community", Specific BGP Extended Community",
draft-ietf-l3vpn-as4octet-ext-community-02 (work in draft-ietf-l3vpn-as4octet-ext-community-03 (work in
progress), November 2008. progress), March 2009.
[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP
Communities Attribute", RFC 1997, August 1996. Communities Attribute", RFC 1997, August 1996.
[RFC1998] Chen, E. and T. Bates, "An Application of the BGP [RFC1998] Chen, E. and T. Bates, "An Application of the BGP
Community Attribute in Multi-home Routing", RFC 1998, Community Attribute in Multi-home Routing", RFC 1998,
August 1996. August 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
 End of changes. 6 change blocks. 
11 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/