draft-ietf-idr-as4octet-extcomm-generic-subtype-06.txt   draft-ietf-idr-as4octet-extcomm-generic-subtype-07.txt 
Network Working Group D. Rao Network Working Group D. Rao
Internet-Draft P. Mohapatra Internet-Draft Cisco Systems
Intended status: Standards Track Cisco Systems Intended status: Standards Track P. Mohapatra
Expires: April 24, 2013 J. Haas Expires: January 5, 2015 Cumulus Networks
J. Haas
Juniper Networks Juniper Networks
October 21, 2012 July 4, 2014
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-06 draft-ietf-idr-as4octet-extcomm-generic-subtype-07
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 BGP extended community. This document defines a 4-octet AS specific BGP extended community. This document defines
a new sub-type within the four-octet AS specific extended community a new sub-type within the four-octet AS specific extended community
to facilitate this practice. to facilitate this practice.
skipping to change at page 1, line 37 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on April 24, 2013. This Internet-Draft will expire on Jannuary 5, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2014 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 22 skipping to change at page 3, line 22
facilitate this practice. facilitate this practice.
For example, [RFC1998] describes an application of BGP community For example, [RFC1998] describes an application of BGP community
attribute ([RFC1997]) to implement flexible routing policies for attribute ([RFC1997]) to implement flexible routing policies for
sites multi-homed to one or multiple providers. In a two-octet AS sites multi-homed to one or multiple providers. In a two-octet AS
environment, the advertised routes are usually associated with a environment, the advertised routes are usually associated with a
community attribute that encodes the provider's AS number in the community attribute that encodes the provider's AS number in the
first two octets of the community and a LOCAL_PREF value in the first two octets of the community and a LOCAL_PREF value in the
second two octets of the community. The community attribute signals second two octets of the community. The community attribute signals
the provider edge routers connected to the site to set the the provider edge routers connected to the site to set the
corresponding LOCAL_PREF on their advertisements to the IBGP mesh. corresponding LOCAL_PREF on their advertisements to the IBGP mesh. In
In this way, customers can put into practice topologies like active- this way, customers can put into practice topologies like active-
backup. backup.
When such a provider is assigned a four-octet AS number, the existing When such a provider is assigned a four-octet AS number, the existing
mechanism of using communities is not sufficient since the AS portion mechanism of using communities is not sufficient since the AS portion
of the RFC 1997 community cannot exceed two bytes. The natural of the RFC 1997 community cannot exceed two bytes. The natural
alternative is to extend the same mechanism using extended alternative is to extend the same mechanism using extended
communities since it allows for encoding eight bytes of information. communities since it allows for encoding eight bytes of information.
[RFC5668] defines a format for a four-octet AS specific extended [RFC5668] defines a format for a four-octet AS specific extended
community with a designated type field. That document defines two community with a designated type field. That document defines two
skipping to change at page 4, line 16 skipping to change at page 4, line 16
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 or 0x42 | 0x04 | Global | | 0x02 or 0x42 | 0x04 | Global |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Administrator | Local Administrator | | Administrator | Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This is an extended type with Type Field comprising of 2 octets and This is an extended type with Type Field comprising of 2 octets and
Value Field comprising of 6 octets. Value Field comprising of 6 octets.
The high-order octet of this extended type is set to either 0x02 (for The high-order octet of this extended type is set to either 0x02 (for
transitive communities) or 0x42 (for non-transitive communities). transitive communities) or 0x42 (for non-transitive communities). The
The low-order octet or the sub-type is set to 0x04. low-order octet or the sub-type is set to 0x04.
The Value Field consists of two sub-fields: The Value Field consists of two sub-fields:
Global Administrator sub-field: 4 octets Global Administrator sub-field: 4 octets
This sub-field contains a four-octet Autonomous System number. This sub-field contains a four-octet Autonomous System number.
Local Administrator sub-field: 2 octets Local Administrator sub-field: 2 octets
This sub-field contains a value that can influence routing This sub-field contains a value that can influence routing
skipping to change at page 6, line 28 skipping to change at page 6, line 28
Dhananjaya Rao Dhananjaya Rao
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: dhrao@cisco.com Email: dhrao@cisco.com
Pradosh Mohapatra Pradosh Mohapatra
Cisco Systems Cumulus Networks
170 W. Tasman Drive 185 E. Dana Street
San Jose, CA 95134 Mountain View, CA 94041
USA USA
Email: pmohapat@cisco.com Email: mpradosh@yahoo.com
Jeffrey Haas Jeffrey Haas
Juniper Networks Juniper Networks
1194 North Mathilda Ave. 1194 North Mathilda Ave.
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
Email: jhaas@pfrc.org Email: jhaas@pfrc.org
 End of changes. 9 change blocks. 
15 lines changed or deleted 16 lines changed or added

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