draft-ietf-idr-bgp-ext-communities-03.txt   draft-ietf-idr-bgp-ext-communities-04.txt 
Network Working Group Srihari R. Sangli Network Working Group Srihari R. Sangli (Procket Networks)
Internet Draft Procket Networks Internet Draft Daniel Tappan (Cisco Systems)
Expiration Date: September 2002 Expiration Date: October 2002 Yakov Rekhter (Juniper Networks)
Daniel Tappan
Cisco Systems
Yakov Rekhter
Juniper Networks
BGP Extended Communities Attribute BGP Extended Communities Attribute
draft-ietf-idr-bgp-ext-communities-03.txt draft-ietf-idr-bgp-ext-communities-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 1, line 39 skipping to change at page 1, line 34
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.
2. Abstract 2. Abstract
This document describes an extension to BGP [BGP-4] which may be used This document describes an extension to BGP-4 which may be used to
to provide flexible control over the distribution of routing provide flexible control over the distribution of routing
information. information.
3. Introduction 3. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
4. Introduction
The Extended Community Attribute provides two important enhancements The Extended Community Attribute provides two important enhancements
over the existing BGP Community Attribute: over the existing BGP Community Attribute:
- It provides an extended range, ensuring that communities can be - It provides an extended range, ensuring that communities can be
assigned for a plethora of uses, without fear of overlap. assigned for a plethora of uses, without fear of overlap.
- The addition of a Type field provides structure for the - The addition of a Type field provides structure for the
community space. community space.
The addition of structure allows the usage of policy based on the The addition of structure allows the usage of policy based on the
application for which the community value will be used. For example, application for which the community value will be used. For example,
one can filter out all communities of a particular type, or allow one can filter out all communities of a particular type, or allow
only certain values for a particular type of community. It also only certain values for a particular type of community. It also
allows one to specify whether a particular community is transitive or allows one to specify whether a particular community is transitive or
non-transitive across Autonomous system boundary. Without structure, non-transitive across Autonomous system boundary. Without structure,
this can only be accomplished by explicitly enumerating all community this can only be accomplished by explicitly enumerating all community
values which will be denied or allowed and passed to BGP speakers in values which will be denied or allowed and passed to BGP speakers in
neighboring ASes based on the transitive property. neighboring ASes based on the transitive property.
4. BGP Extended Communities Attribute 5. BGP Extended Communities Attribute
The Extended Communities Attribute is a transitive optional BGP The Extended Communities Attribute is a transitive optional BGP
attribute. The attribute consists of a set of "extended attribute, with the Type Code 16. The attribute consists of a set of
communities". Each extended community is coded as an eight octet "extended communities". All routes with the Extended Communities
value. All routes with the Extended Communities attribute belong to attribute belong to the communities listed in the attribute.
the communities listed in the attribute.
The Extended Communities Attribute has Type Code 16.
Each Extended Community is encoded as an eight octet quantity, as Each Extended Community is encoded as an eight octet quantity, as
follows: follows:
- Type Field : 1 or 2 octets - Type Field : 1 or 2 octets
- Value Field : Remaining octets - Value Field : Remaining octets
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type high | Type low(*) | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value |
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
*) Present for Extended types only, used for the Value field
otherwise
Type Field: Type Field:
Two classes of Type Field are introduced: Regular type and Two classes of Type Field are introduced: Regular type and
Extended type. Extended type.
The size of Type Field for Regular types is 1 octet and the The size of Type Field for Regular types is 1 octet and the
size of the Type Field for Extended types is 2 octets. size of the Type Field for Extended types is 2 octets.
The value of the high-order octet will determine if its a The value of the high-order octet of the Type Field determines
regular type or an extended type. The value of the high-order if an extended community is a Regular type or an Extended type.
octet of the Type Field defined as regular type (or extended
type) for a extended community MUST NOT be reused as the value
of the high-order octet of the Type Field defined as extended
type (or regular type). In other words, a new extended
community of regular type (extended type) should have unique
(and new) value for the high-order octet (high-order and low-
order octet).
The high-order octet of the Type Field is as shown below: The high-order octet of the Type Field is as shown below:
First bit (MSB) : IANA authority bit 0 1 2 3 4 5 6 7
Value 0 : IANA assignable type +-+-+-+-+-+-+-+-+
Value 1 : Vendor-specific types |I|T| |
+-+-+-+-+-+-+-+-+
Second bit : Transitive bit I - IANA authority bit
Value 0 : The community is
Transitive across ASes
Value 1 : The community is
Non-Transitive across ASes
Remaining 6 bits : Indicates the structure of the Value 0: IANA assignable type using the "First Come First
community Serve" policy
Value 1: IANA assignable type using the IETF Consensus
policy and experimental
T - Transitive bit
Value 0: The community is transitive across ASes
Value 1: The community is non-transitive across ASes
Remaining 6 bits: Indicates the structure of the community
Value Field: Value Field:
The encoding of the Value Field is dependent on the "type" of The encoding of the Value Field is dependent on the "type" of
the community as specified by the Type Field. The encoding of the community as specified by the Type Field.
the community for the transitive communities should be such
that it is unique globally (i.e. across the Autonomous
Systems).
Two extended communities are declared equal only when entire 8 Two extended communities are declared equal only when all 8 octets
octets are equal. of their encoding are equal.
The two members in the tuple <Type, Value> should be enumerated to The two members in the tuple <Type, Value> should be enumerated to
specify any community value. Based on the value of the Type field, specify any community value. Based on the value of the Type field,
the remaining octets of the community should be interpreted. the remaining octets of the community should be interpreted.
5. New BGP Extended Community Types. 6. Defined BGP Extended Community Types
This document introduces a few extended types and defines the Value This section introduces a few extended types and defines the format
Field for those types. of the Value Field for those types. The types introduced here provide
"templates", where each template is identified by the high order
octet of the extended community Type field, and the lower order octet
(sub-type) is used to indicate a particular type of extended
community.
Type 0x00: 6.1. Two-octet AS specific extended community
This is an extended type with Type Field comprising of 2 octets This is an extended type with Type Field comprising of 2 octets and
and Value Field comprising of 6 octets. Value Field comprising of 6 octets.
The value of the high-order octet of this extended type is 0 1 2 3
0x00. The low-order octet of this extended type is used to 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 or 0x40 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of this extended type is either
0x00 or 0x40. The low-order octet of this extended type is used to
indicate sub-types. indicate sub-types.
The Value Field consists of two sub-fields: The Value Field consists of two sub-fields:
Global Administrator sub-field: 2 octets Global Administrator sub-field: 2 octets
This sub-field contains an Autonomous System number This sub-field contains an Autonomous System number assigned by
assigned by IANA. IANA.
Local Administrator sub-field: 4 octets Local Administrator sub-field: 4 octets
The organization identified by Autonomous System number The organization identified by Autonomous System number in the
in the Global Administrator sub-field, can encode any Global Administrator sub-field, can encode any information in
information in this sub-field. The value and meaning of this sub-field. The format and meaning of the value encoded in
the value encoded in this sub-field should be defined by this sub-field should be defined by the sub-type of the
the sub-type of the community. community.
Type 0x01: 6.2. IPv4 address specific extended community
This is an extended type with Type Field comprising of 2 octets This is an extended type with Type Field comprising of 2 octets and
and Value Field comprising of 6 octets. Value Field comprising of 6 octets.
The value of the high-order octet of this extended type is 0 1 2 3
0x01. The low-order octet of this extended type is used to 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01 or 0x41 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of this extended type is either
0x01 or 0x41. The low-order octet of this extended type is used to
indicate sub-types. indicate sub-types.
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 an IPv4 address assigned by IANA. This sub-field contains an IPv4 address assigned by IANA.
Local Administrator sub-field: 2 octets Local Administrator sub-field: 2 octets
The organization which has been assigned the IPv4 address The organization which has been assigned the IPv4 address in
in the Global Administrator sub-field, can encode any the Global Administrator sub-field, can encode any information
information in this sub-field. The value and meaning of in this sub-field. The format and meaning of this value
this value encoded in this sub-field should be defined by encoded in this sub-field should be defined by the sub-type of
the sub-type of the community. the community.
Type 0x02: 6.3. Four-octet AS specific extended community
This is an extended type with Type Field comprising of 2 octets This is an extended type with Type Field comprising of 2 octets and
and Value Field comprising of 6 octets. Value Field comprising of 6 octets.
The value of the high-order octet of this extended type is 0 1 2 3
0x02. The low-order octet of this extended type is used to 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 or 0x42 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of this extended type is either
0x02 or 0x42. The low-order octet of this extended type is used to
indicate sub-types. indicate sub-types.
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 4-octets Autonomous System This sub-field contains a 4-octets Autonomous System number
number assigned by IANA. assigned by IANA.
Local Administrator sub-field: 2 octets Local Administrator sub-field: 2 octets
The organization identified by Autonomous System number The organization identified by Autonomous System number in the
in the Global Administrator sub-field, can encode any Global Administrator sub-field, can encode any information in
information in this sub-field. The value and meaning of this sub-field. The format and meaning of the value encoded in
the value encoded in this sub-field should be defined by this sub-field should be defined by the sub-type of the
the sub-type of the community. community.
Type 0x03: 6.4. Opaque extended community
This is an extended type with Type Field comprising of 2 octets This is an extended type with Type Field comprising of 2 octets and
and Value Field comprising of 6 octets. Value Field comprising of 6 octets.
The value of the high-order octet of this extended type is 0 1 2 3
0x03. The low-order octet of this extended type is used to 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x03 or 0x43 | Sub-Type | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of this extended type is either
0x03 or 0x43. The low-order octet of this extended type is used to
indicate sub-types. indicate sub-types.
The Value Field contains a 6 byte value of structure with sub- The Value Field contains a 6 byte value of structure with sub-fields.
fields.
This is a generic community of extended type. The value of the This is a generic community of extended type. The value of the sub-
sub-type which should define the Value Field is to be assigned type which should define the Value Field is to be assigned by IANA.
by IANA.
6. Route Target Community 7. Route Target Community
The Route Target Community identifies one or more routers that may The Route Target Community identifies one or more routers that may
receive a set of routes (that carry this Community) carried by BGP. receive a set of routes (that carry this Community) carried by BGP.
This is transitive across the Autonomous system boundary. This is transitive across the Autonomous system boundary.
The value of the Type field for the Route Target Community can be The Route Target Community is of an extended type.
0x00, 0x01 or 0x02. The value of the low-order octet of the extended
type field for this community is 0x02.
When the value of the Type field is 0x00 or 0x02, the value of the The value of the high-order octet of the Type field for the Route
Local Administrator sub-field in the Value Field MUST be unique Target Community can be 0x00, 0x01 or 0x02. The value of the low-
within the Autonomous system carried in the Global Administrator sub- order octet of the Type field for this community is 0x02.
field.
7. Route Origin Community When the value of the high-order octet of the Type field is 0x00 or
0x02, the Local Administrator sub-field contains a number from a
numbering space which is administered by the organization to which
the Autonomous System number carried in the Global Administrator
subfield has been assigned by an appropriate authority.
When the value of the high-order octet of the Type field is 0x01, the
Local Administrator sub-field contains a number from a numbering
space which is administered by the organization to which the IP
address carried in the Global Administrator subfield has been
assigned by an appropriate authority.
8. Route Origin Community
The Route Origin Community identifies one or more routers that inject The Route Origin Community identifies one or more routers that inject
a set of routes (that carry this Community) into BGP. This is a set of routes (that carry this Community) into BGP. This is
transitive across the Autonomous system boundary. transitive across the Autonomous system boundary.
The value of the Type field for the Route Origin Community can be The Route Origin Community is of an extended type.
0x00, 0x01 or 0x02. The value of the low-order octet of the extended
type field for this community is 0x03.
When the value of the Type field is 0x00 or 0x02, the value of the The value of the high-order octet of the Type field for the Route
Local Administrator sub-field in the Value Field MUST be unique Origin Community can be 0x00, 0x01 or 0x02. The value of the low-
within the Autonomous system carried in the Global Administrator sub- order octet of the Type field for this community is 0x03.
field.
8. Link Bandwidth Community When the value of the high-order octet of the Type field is 0x00 or
0x02, the Local Administrator sub-field contains a number from a
numbering space which is administered by the organization to which
the Autonomous System number carried in the Global Administrator
subfield has been assigned by an appropriate authority.
When the value of the high-order octet of the Type field is 0x01, the
Local Administrator sub-field contains a number from a numbering
space which is administered by the organization to which the IP
address carried in the Global Administrator subfield has been
assigned by an appropriate authority.
9. Link Bandwidth Community
When a router receives a route from a directly connected external When a router receives a route from a directly connected external
neighbor (the external neighbor that is one IP hop away), and neighbor (the external neighbor that is one IP hop away), and
advertises this route (via IBGP) to internal neighbors, as part of advertises this route (via IBGP) to internal neighbors, as part of
this advertisement the router may carry the bandwidth of the link this advertisement the router may carry the bandwidth of the link
that connects the router with the external neighbor. The bandwidth of that connects the router with the external neighbor. The bandwidth of
such a link is carried in the Link Bandwidth Community. The community such a link is carried in the Link Bandwidth Community.
MAY be marked as non-transitive across the Autonomous system
boundary.
If the community is marked as non-transitive, then the value of the The Link Bandwidth Community is of an extended type.
high-order octet of the extended Type Field is 0x40, otherwise it is
0x00. The value of the low-order octet of the extended type field The value of the high-order octet of the Type Field is 0x00. The
for this community is 0x04. value of the low-order octet of the Type field for this community is
0x04.
The value of the Global Administrator sub-field in the Value Field The value of the Global Administrator sub-field in the Value Field
MUST represent the Autonomous System of the router that attaches the MUST represent the Autonomous System of the router that attaches the
Link Bandwidth Community. When a router receives a route with the Link Bandwidth Community.
community, the router may check the AS number in the Global
Administrator sub-field to see if its not the local AS and hence
ignore the information carried in the Link Bandwidth Community.
The bandwidth of the link is expressed as 4 octets in IEEE floating The bandwidth of the link is expressed as 4 octets in IEEE floating
point format, units being bytes per second. It is carried in the point format, units being bytes per second. It is carried in the
Local Administrator sub-field of the Value Field. Local Administrator sub-field of the Value Field.
9. Operations 10. Operations
A BGP speaker may use the Extended Communities attribute to control A BGP speaker may use the Extended Communities attribute to control
which routing information it accepts, prefers or distributes to its which routing information it accepts, prefers or distributes to its
peers. peers.
A BGP speaker receiving a route that doesn't have the Extended A BGP speaker receiving a route that doesn't have the Extended
Communities attribute may append this attribute to the route when Communities attribute MAY append this attribute to the route when
propagating it to its peers. propagating it to its peers.
A BGP speaker receiving a route with the Extended Communities A BGP speaker receiving a route with the Extended Communities
attribute may modify this attribute according to the local policy. attribute MAY modify this attribute according to the local policy.
A BGP speaker should not propagate a non-transitive extended By default if a range of routes is to be aggregated and the resultant
community across the Autonomous system boundary. aggregates path attributes do not carry the ATOMIC_AGGREGATE
attribute, then the resulting aggregate should have an Extended
Communities path attribute which contains the set union of all the
Extended Communities from all of the aggregated routes. The default
behavior could be overriden via local configuration, in which case
handling the Extended Communities attribute in the presence of route
aggregation becomes a matter of the local policy of the BGP speaker
that performs the aggregation.
A BGP speaker SHOULD NOT propagate a non-transitive extended
community across the Autonomous system boundary. However, a BGP
speaker SHOULD propagate a non-transitive extended community across
the BGP Conferederation boundary.
A route may carry both the BGP Communities attribute as defined in A route may carry both the BGP Communities attribute as defined in
[RFC1997]), and the Extended BGP Communities attribute. In this case [RFC1997]), and the Extended BGP Communities attribute. In this case
the BGP Communities attribute is handled as specified in [RFC1997], the BGP Communities attribute is handled as specified in [RFC1997],
and the Extended BGP Communities attribute is handled as specified in and the Extended BGP Communities attribute is handled as specified in
this document. this document.
10. IANA Considerations 11. IANA Considerations
The value of the high-order octet of the Type Field determines if an
extended community is a regular type or an extended type. The value
of the high-order octet of the Type Field defined as regular type (or
extended type) for a extended community MUST NOT be reused as the
value of the high-order octet of the Type Field defined as extended
type (or regular type).
For the high-order octet of the Type Field, values 0x00 through 0x03 For the high-order octet of the Type Field, values 0x00 through 0x03
are assigned in this document and are defined as extended types. For and 0x40 through 0x43 are assigned in this document and are defined
the combination of the high-order and low-order octets of the Type as extended types.
Field values 0x0002-0x0004, 0x0102-0x0103, and 0x0202-0x0203 are
For the combination of the high-order and low-order octets of the
Type Field values 0x0002-0x0004, 0x0102-0x0103, and 0x0202-0x0203 are
assigned in this document. assigned in this document.
The Type Field values 0x04-0x3f for regular types (0x0400-0x3fff when The Type Field values 0x04-0x3f and 0x44-0x7f for regular types
expressed as extended types) are to be assigned by IANA, using the (0x0400-0x3fff and 0x4400-0x7fff when expressed as extended types)
"First Come First Served" policy defined in RFC 2434. The extended are to be assigned by IANA, using the "First Come First Served"
type field values 0x0000-0x0001, 0x0005-0x00ff, 0x0100-0x0101, policy defined in RFC 2434.
0x0104-0x01ff, 0x0200-0x0201, 0x0204-0x02ff and 0x0300-0x03ff are to
be assigned by IANA, using the "First Come First Served" policy
defined in RFC 2434. Type values 0x80-0xbf for regular types
(0x8000-0xbfff when expressed as extended types) are vendor-specific
types, and values in this range are not to be assigned by IANA.
11. Security Considerations The extended Type Field values 0x0000-0x0001, 0x0005-0x00ff,
0x0100-0x0101, 0x0104-0x01ff, 0x0200-0x0201, 0x0204-0x02ff,
0x0300-0x03ff, and 0x4000-0x43ff are to be assigned by IANA, using
the "First Come First Served" policy defined in RFC 2434.
The Type Field values 0x90-0xbf and 0xd0-0xff for regular types
(0x9000-0xbfff and 0xd000-0xffff when expressed as extended types)
are to be assigned by IANA, using the "IETF Consensus" policy defined
in RFC2434.
The Type Field values 0x80-0x8f and 0xc0-0xcf for regular types
(0x8000-0x8fff and 0xc000-0xcfff when expressed as extended types)
are experimental, and are not to be assigned by IANA.
12. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
12. Acknowledgements 13. Acknowledgements
The authors would like to thank John Hawkinson, Jeffrey Haas, Bruno The authors would like to thank John Hawkinson, Jeffrey Haas, Bruno
Rijsman for their suggestions and feedback. Rijsman, and Alex Zinin for their suggestions and feedback.
13. References 14. References
[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 [BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 1771, March 1995. (BGP-4)", RFC 1771, March 1995.
[RFC1997] Chandra, R., Traina, P., Li, T., "BGP Communities [RFC1997] Chandra, R., Traina, P., Li, T., "BGP Communities
Attribute", RFC1997, August 1996. Attribute", RFC1997, August 1996.
14. Author Information [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
15. Author Information
Srihari R. Sangli Srihari R. Sangli
Procket Networks, Inc. Procket Networks, Inc.
1100 Cadillac Court 1100 Cadillac Court
Milpitas, CA - 95035 Milpitas, CA - 95035
e-mail: srihari@procket.com e-mail: srihari@procket.com
Dan Tappan Dan Tappan
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
 End of changes. 

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