< draft-ietf-trill-rbridge-channel-05.txt   draft-ietf-trill-rbridge-channel-06.txt >
TRILL Working Group Donald Eastlake TRILL Working Group Donald Eastlake
INTERNET-DRAFT Huawei INTERNET-DRAFT Huawei
Intended status: Proposed Standard Vishwas Manral Intended status: Proposed Standard Vishwas Manral
HP Networking HP Networking
Li Yizhou Li Yizhou
Sam Aldrin Sam Aldrin
Huawei Huawei
Dave Ward Dave Ward
Cisco Cisco
Expires: August 19, 2012 February 20, 2012 Expires: November 14, 2012 May 15, 2012
TRILL: RBridge Channel Support TRILL: RBridge Channel Support
<draft-ietf-trill-rbridge-channel-05.txt> <draft-ietf-trill-rbridge-channel-06.txt>
Abstract Abstract
This document specifies a general channel mechanism for sending This document specifies a general channel mechanism for sending
messages, such as BFD (Bidirectional Forwarding Detection) messages, messages, such as BFD (Bidirectional Forwarding Detection) messages,
between RBridges (Routing Bridges) and between RBridges and end between RBridges (Routing Bridges) and between RBridges and end
stations in an RBridge campus through extensions to the TRILL stations in an RBridge campus through extensions to the TRILL
(TRansparent Interconnection of Lots of Links) protocol. (TRansparent Interconnection of Lots of Links) protocol.
Status of This Memo Status of This Memo
skipping to change at page 2, line 41 skipping to change at page 2, line 41
6.1 IANA Considerations...................................17 6.1 IANA Considerations...................................17
6.2 IEEE Registration Authority Considerations............18 6.2 IEEE Registration Authority Considerations............18
7. Security Considerations................................19 7. Security Considerations................................19
8. References.............................................20 8. References.............................................20
8.1 Normative References..................................20 8.1 Normative References..................................20
8.2 Informative References................................20 8.2 Informative References................................20
Appendix: Change History..................................22 Appendix: Change History..................................22
Acknowledgmnts............................................24 Acknowledgments...........................................25
Authors' Addresses........................................25
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
1. Introduction 1. Introduction
RBridge campuses provide transparent least-cost path forwarding using RBridge campuses provide transparent least-cost path forwarding using
the TRILL (TRansparent Interconnection of Lots of Links) protocol the TRILL (TRansparent Interconnection of Lots of Links) protocol
that builds on IS-IS (Intermediate System to Intermediate System) that builds on IS-IS (Intermediate System to Intermediate System)
routing [IS-IS] [RFC1195] [RFC6326bis]. Devices that implement TRILL routing [IS-IS] [RFC1195] [RFC6326bis]. Devices that implement TRILL
are called RBridges (Routing Bridges) or TRILL Switches. However, the are called RBridges (Routing Bridges) or TRILL Switches. However, the
TRILL base protocol standard [RFC6325] provides only for TRILL Data TRILL base protocol standard [RFC6325] provides only for TRILL Data
messages and TRILL IS-IS messages. messages and TRILL IS-IS messages.
This document specifies a general channel mechanism for the This document specifies a general channel mechanism for the
transmission of other messages within an RBridge campus, such as BFD transmission of other messages within an RBridge campus, such as BFD
(Bidirectional Forwarding Detection, [RFC5880]) messages, between (Bidirectional Forwarding Detection, [RFC5880]) messages, (1) between
RBridges and end stations that are directly connected on the same RBridges and end stations that are directly connected on the same
link and between RBridges. This mechanism supports a requirement to link and (2) between RBridges. This mechanism supports a requirement
be able to operate with minimal configuration. to be able to operate with minimal configuration.
Familiarity with [RFC6325] and [RFC6327] is assumed in this document. Familiarity with [RFC6325] and [RFC6327] is assumed in this document.
1.1 RBridge Channel Requirements 1.1 RBridge Channel Requirements
It is anticipated that various protocols operating at the TRILL level It is anticipated that various protocols operating at the TRILL level
will be desired in RBridge campuses. For example, there is a need for will be desired in RBridge campuses. For example, there is a need for
rapid response continuity checking with a protocol such as BFD rapid response continuity checking with a protocol such as BFD
[RFC5880] [RFC5882] and for a variety of optional reporting. [RFC5880] [RFC5882] and for a variety of optional reporting.
skipping to change at page 5, line 40 skipping to change at page 5, line 40
| RBridge Channel Header | Section 2.1.1 | RBridge Channel Header | Section 2.1.1
+--------------------------------+ +--------------------------------+
| Protocol Specific Payload | See specific channel protocol | Protocol Specific Payload | See specific channel protocol
+--------------------------------+ +--------------------------------+
| Link Trailer (FCS if Ethernet) | | Link Trailer (FCS if Ethernet) |
+--------------------------------+ +--------------------------------+
Optionally, some channel messages may require examination of the Optionally, some channel messages may require examination of the
frame by transit RBridges that support the RBridge Channel feature, frame by transit RBridges that support the RBridge Channel feature,
to determine if they need to take any action. To indicate this, such to determine if they need to take any action. To indicate this, such
messages use a RBridge Channel Alert extended TRILL header flags as messages use a RBridge Channel Alert extended TRILL header flag as
further described in Section 3 below. further described in Section 3 below.
The Sections 2.1 and 2.2 below describe the Inner frame and the TRILL The Sections 2.1 and 2.2 below describe the Inner frame and the TRILL
Header for frames sent in an RBridge Channel. As always, the Outer Header for frames sent in an RBridge Channel. As always, the Outer
link header and trailer are whatever is needed to get a TRILL Data link header and trailer are whatever is needed to get a TRILL Data
frame to the next hop RBridge, depending on the technology of the frame to the next hop RBridge, depending on the technology of the
link, and can change with each hop for multi-hop messages. Section link, and can change with each hop for multi-hop messages. Section
2.3 describes the outer Link Header for Ethernet. And Section 2.4 2.3 describes the outer Link Header for Ethernet. And Section 2.4
discusses some special considerations for the first hop transmission discusses some special considerations for the first hop transmission
of RBridge Channel messages. of RBridge Channel messages.
skipping to change at page 6, line 45 skipping to change at page 6, line 45
to the specific channel protocol used in the channel message. Details to the specific channel protocol used in the channel message. Details
of that data are outside the scope of this document, except in the of that data are outside the scope of this document, except in the
case of the RBridge Channel Error protocol specified below. case of the RBridge Channel Error protocol specified below.
2.1.1 RBridge Channel Header 2.1.1 RBridge Channel Header
As shown in the diagram above, the RBridge Channel header starts with As shown in the diagram above, the RBridge Channel header starts with
the RBridge-Channel Ethertype (see Section 6.2). Following that is a the RBridge-Channel Ethertype (see Section 6.2). Following that is a
four-byte quantity with four sub-fields as follows: four-byte quantity with four sub-fields as follows:
CHV: A 4-bit field that gives the RBridge Channel Header Version CHV: A 4-bit field that gives the RBridge Channel Header Version.
and MUST be zero. This document species version zero.
Channel Protocol: A 12-bit unsigned integer that specifies the Channel Protocol: A 12-bit unsigned integer that specifies the
particular RBridge Channel protocol to which the message particular RBridge Channel protocol to which the message
applies. applies.
Flags: Provides 12 bits of flags described below. Flags: Provides 12 bits of flags described below.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
ERR: A 4-bit unsigned integer used in connection with error ERR: A 4-bit unsigned integer used in connection with error
skipping to change at page 9, line 16 skipping to change at page 9, line 16
recommendation is made for that case. recommendation is made for that case.
2.2 The TRILL Header for RBridge Channel Messages 2.2 The TRILL Header for RBridge Channel Messages
After the outer Link Header (that, for Ethernet, ends with the TRILL After the outer Link Header (that, for Ethernet, ends with the TRILL
Ethertype) and before the encapsulated frame, the channel message's Ethertype) and before the encapsulated frame, the channel message's
TRILL Header initially appears as follows: TRILL Header initially appears as follows:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=0| R |M| Ext-Len | Hop Count | |V=0| R |M| Op-Len | Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Egress Nickname | Ingress Nickname | | Egress Nickname | Ingress Nickname |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The TRILL Header version V MUST be zero, the R bits are reserved, the The TRILL Header version V MUST be zero, the R bits are reserved, the
M bit is set appropriately as the channel message is to be forwarded M bit is set appropriately as the channel message is to be forwarded
as known unicast (M=0) or multi-destination (M=1) regardless of the as known unicast (M=0) or multi-destination (M=1) regardless of the
fact that the Inner.MacDA is always the All-Egress-RBridges multicast fact that the Inner.MacDA is always the All-Egress-RBridges multicast
address, and Ext-Len is set appropriately for the length of the TRILL address, and Op-Len is set appropriately for the length of the TRILL
Header extensions area, if any, all as specified in [RFC6325] (where Header extensions area, if any, all as specified in [RFC6325].
the extensions area is referred to as the options area and this field
as Op-Len).
When an RBridge Channel message is originated, the Hop Count field When an RBridge Channel message is originated, the Hop Count field
defaults to the maximum value, 0x3F, but particular RBridge Channel defaults to the maximum value, 0x3F, but particular RBridge Channel
protocols MAY specify other values. For messages sent a known number protocols MAY specify other values. For messages sent a known number
of hops, such as one-hop messages or a two-hop self-addressed message of hops, such as one-hop messages or a two-hop self-addressed message
intended to loop back through an immediate neighbor RBridge, setting intended to loop back through an immediate neighbor RBridge, setting
the Hops field to the maximum value and checking the Hop Count field the Hops field to the maximum value and checking the Hop Count field
on receipt provides an additional validity check as discussed in on receipt provides an additional validity check as discussed in
[RFC5082]. [RFC5082].
skipping to change at page 10, line 5 skipping to change at page 9, line 53
unicast message, then the egress nickname is a nickname of the target unicast message, then the egress nickname is a nickname of the target
RBridge; this includes the special case of a message intended to loop RBridge; this includes the special case of a message intended to loop
back from an immediate neighbor where the originator places one of back from an immediate neighbor where the originator places one of
its own nicknames in both the ingress and egress nickname fields. If its own nicknames in both the ingress and egress nickname fields. If
the channel message is a one-hop unicast message, there are two the channel message is a one-hop unicast message, there are two
possibilities for the egress nickname. possibilities for the egress nickname.
o The egress nickname can be set to a nickname of the target o The egress nickname can be set to a nickname of the target
neighbor RBridge. neighbor RBridge.
INTERNET-DRAFT TRILL: RBridge Channel
o The special nickname Any-RBridge may be used. RBridges supporting o The special nickname Any-RBridge may be used. RBridges supporting
the RBridge Channel facility MUST recognize the Any-RBridge the RBridge Channel facility MUST recognize the Any-RBridge
INTERNET-DRAFT TRILL: RBridge Channel
special nickname and accept TRILL Data frames having that value in special nickname and accept TRILL Data frames having that value in
the egress nickname field as being sent to them as the egress. the egress nickname field as being sent to them as the egress.
Thus, for such RBridges, using this egress nickname guarantees Thus, for such RBridges, using this egress nickname guarantees
processing by an immediate neighbor regardless of the state of processing by an immediate neighbor regardless of the state of
nicknames. nicknames.
2.3 Ethernet Link Header and Trailer 2.3 Ethernet Link Header and Trailer
An RBridge Channel frame has the usual link header and trailer An RBridge Channel frame has the usual link header and trailer for a
depending on the type of link on which it is sent. TRILL Data frame depending on the type of link on which it is sent.
For an Ethernet link [RFC6325] the Outer.MacSA is the MAC address of For an Ethernet link [RFC6325] the Outer.MacSA is the MAC address of
the port from which the frame is sent. The Outer.MacDA is the MAC the port from which the frame is sent. The Outer.MacDA is the MAC
address of the next-hop RBridge port for unicast RBridge Channel address of the next-hop RBridge port for unicast RBridge Channel
messages or the All-RBridges multicast address for multi-destination messages or the All-RBridges multicast address for multi-destination
RBridge Channel messages. The Outer.VLAN tag specifies the Designated RBridge Channel messages. The Outer.VLAN tag specifies the Designated
VLAN for that hop and the priority should be the same as in the VLAN for that hop and the priority should be the same as in the
Inner.VLAN tag; however, the output port may have been configured to Inner.VLAN tag; however, the output port may have been configured to
strip VLAN tags, in which case no Outer.VLAN tag appears on the wire. strip VLAN tags, in which case no Outer.VLAN tag appears on the wire.
And the link trailer is the Ethernet FCS. And the link trailer is the Ethernet FCS.
skipping to change at page 12, line 12 skipping to change at page 12, line 12
the frame is being processed at a transit RBridge because the the frame is being processed at a transit RBridge because the
critical RBridge Channel Alert flag is set [RFCext]. However, if critical RBridge Channel Alert flag is set [RFCext]. However, if
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
these conditions are detected at a transit RBridge examining the these conditions are detected at a transit RBridge examining the
message because the non-critical RBridge Channel Alert flag is set message because the non-critical RBridge Channel Alert flag is set
[RFCext] but the critical flag is not set, no error is generated and [RFCext] but the critical flag is not set, no error is generated and
the frame is still forwarded normally. the frame is still forwarded normally.
Error Conditions:
1. The Ethertype is not RBridge-Channel and not any other 1. The Ethertype is not RBridge-Channel and not any other
Ethertype known to the RBridge as usable with the All-Egress- Ethertype known to the RBridge as usable with the All-Egress-
RBridges Inner.MacDA, or the frame is so short that the RBridges Inner.MacDA, or the frame is so short that the
Ethertype is truncated. Ethertype is truncated.
2. The CHV field is non-zero or the frame is so short that the 2. The CHV field is non-zero or the frame is so short that the
version zero Channel Header is truncated. version zero Channel Header is truncated.
3. The Channel Protocol field is a reserved value or a value 3. The Channel Protocol field is a reserved value or a value
unknown to the processing RBridge. unknown to the processing RBridge.
skipping to change at page 12, line 45 skipping to change at page 12, line 47
whether this is (a) transit RBridge processing due to an RBridge whether this is (a) transit RBridge processing due to an RBridge
Channel Alert flag being set or (b) egress processing. Channel Alert flag being set or (b) egress processing.
Errors within a recognized Channel Protocol are handled by that Errors within a recognized Channel Protocol are handled by that
channel protocol itself and do not produce RBridge Channel Error channel protocol itself and do not produce RBridge Channel Error
frames. frames.
3.2 RBridge Channel Errors 3.2 RBridge Channel Errors
A variety of problems at the RBridge Channel level cause the return A variety of problems at the RBridge Channel level cause the return
of an RBridge Channel Error frame unless (a) the "SL" (Silent) flag of an RBridge Channel Error frame unless one of the following apply:
is a one in the channel message for which the problem was detected, (a) the "SL" (Silent) flag is a one in the channel message for which
(b) the processing is due to the non-critical RBridge Channel Alert the problem was detected, (b) the processing is due to the non-
bit being set, (c) the frame in error appears, itself, to be an critical RBridge Channel Alert bit being set, (c) the frame in error
RBridge Channel error frame (has a non-zero ERR field or a Channel appears, itself, to be an RBridge Channel error frame (has a non-zero
Protocol of 0x001), or (d) the error is suppressed due to rate ERR field or a Channel Protocol of 0x001), or (d) the error is
limiting. suppressed due to rate limiting.
An RBridge Channel Error frame is a multi-hop unicast RBridge Channel
message with the ingress nickname set to the nickname of the RBridge
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
An RBridge Channel Error frame is a multi-hop unicast RBridge Channel
message with the ingress nickname set to the nickname of the RBridge
detecting the error, and the egress nickname set to the value of the detecting the error, and the egress nickname set to the value of the
ingress nickname in the channel message for which the error was ingress nickname in the channel message for which the error was
detected. No per-hop transit processing is specified for such error detected. No per-hop transit processing is specified for such error
frames, so the RBridge Channel Alert extended header flags SHOULD, if frames, so the RBridge Channel Alert extended header flags SHOULD, if
an extension is present, be set to zero. The SL and MH flags SHOULD an extension is present, be set to zero. The SL and MH flags SHOULD
be set to one, the NA flag MUST be zero, and the ERR field MUST be be set to one, the NA flag MUST be zero, and the ERR field MUST be
non-zero as described below. For the protocol specific data area, an non-zero as described below. For the protocol specific data area, an
RBridge Channel Message Error frame has at least the first 256 bytes RBridge Channel Message Error frame has at least the first 256 bytes
(or less if less are available) of the erroneous decapsulated channel (or less if less are available) of the erroneous decapsulated channel
message starting with the TRILL Header. (Note: The TRILL Header does message starting with the TRILL Header. (Note: The TRILL Header does
skipping to change at page 15, line 17 skipping to change at page 15, line 17
The RBridge Channel protocol number space for native RBridge Channel The RBridge Channel protocol number space for native RBridge Channel
messages and TRILL Data formatted RBridge Channel messages is the messages and TRILL Data formatted RBridge Channel messages is the
same. If provided for by the channel protocol involved, the receipt same. If provided for by the channel protocol involved, the receipt
of a native RBridge Channel frame MAY lead to the generation and of a native RBridge Channel frame MAY lead to the generation and
transmission of one or more Inter-RBridge Channel frames. The transmission of one or more Inter-RBridge Channel frames. The
decapsulation and processing of a TRILL Data RBridge Channel frame decapsulation and processing of a TRILL Data RBridge Channel frame
MAY, if provided for by the channel protocol involved, result in the MAY, if provided for by the channel protocol involved, result in the
sending of one or more native RBridge channel frames to one or more sending of one or more native RBridge channel frames to one or more
end stations. Thus, there could be an RBridge Channel protocol that end stations. Thus, there could be an RBridge Channel protocol that
involved an RBridge Channel message sent from an origin RBridge where involved an RBridge Channel message sent from an origin RBridge where
the message is created, through one or more other RBridges and from the message is created, through one or more transit RBridges and from
the last as a native RBridge channel message to and end station or the last as a native RBridge channel message to and end station or
the reverse of such a path; however, to do this the RBridge channel the reverse of such a path; however, to do this the RBridge channel
protocol involved must be implemented at the RBridge where the protocol involved must be implemented at the RBridge where the
channel message is changed between a native frame and a TRILL Data channel message is changed between a native frame and a TRILL Data
format frame and must change the channel message itself, at a minimum format frame and must change the channel message itself, at a minimum
complementing the NA flag in the Channel Header and making complementing the NA flag in the Channel Header and making
appropriate MAC address changes. appropriate MAC address changes.
An erroneous native channel message results in a native RBridge An erroneous native channel message results in a native RBridge
channel error message under the same conditions for which an TRILL channel error message under the same conditions for which an TRILL
skipping to change at page 18, line 25 skipping to change at page 18, line 25
Allocation of an RBridge Channel Header Flag is based on Standards Allocation of an RBridge Channel Header Flag is based on Standards
Action as modified by [RFC4020]. Action as modified by [RFC4020].
IANA is requested to create an additional sub-registry in the TRILL IANA is requested to create an additional sub-registry in the TRILL
Parameter Registry for RBridge Channel Error codes with initial Parameter Registry for RBridge Channel Error codes with initial
contents as listed in Section 3.2 above and with available values contents as listed in Section 3.2 above and with available values
allocated by Standards Action as modified by [RFC4020]. allocated by Standards Action as modified by [RFC4020].
6.2 IEEE Registration Authority Considerations 6.2 IEEE Registration Authority Considerations
The IEEE Registration Authority has been assigned the Ethertype <TBD> The IEEE Registration Authority has assigned the Ethertype <TBD> for
for RBridge-Channel. RBridge-Channel.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
7. Security Considerations 7. Security Considerations
See [RFC6325] for general TRILL Security Considerations. See [RFC6325] for general TRILL Security Considerations.
No general integrity, authentication, or encryption mechanisms are No general integrity, authentication, or encryption mechanisms are
provided herein for RBridge Channel messages. If these services are provided herein for RBridge Channel messages. If these services are
required for a particular RBridge Channel protocol, they must be required for a particular RBridge Channel protocol, they must be
skipping to change at page 19, line 31 skipping to change at page 19, line 31
advertised as supported, it would deny the service of that channel advertised as supported, it would deny the service of that channel
protocol to the RBridge in question. protocol to the RBridge in question.
Incorrect presence of indication of RBridge Channel Protocol support Incorrect presence of indication of RBridge Channel Protocol support
or incorrect assertion of support for a channel protocol could or incorrect assertion of support for a channel protocol could
encourage RBridge channel messages to be sent to an RBridge that does encourage RBridge channel messages to be sent to an RBridge that does
not support the channel feature or the particular channel protocol not support the channel feature or the particular channel protocol
used. The inner frame of such messages could be decapsulated and that used. The inner frame of such messages could be decapsulated and that
inner frame could be sent out all ports that are appointed forwarders inner frame could be sent out all ports that are appointed forwarders
for the frame's Inner.VLAN. However, this is unlikely to cause much for the frame's Inner.VLAN. However, this is unlikely to cause much
harm; in particuclar, there are two possibilities as follows: (a) If harm; in particular, there are two possibilities as follows: (a) If
end stations do not recognize the RBridge-Channel Ethertype of the end stations do not recognize the RBridge-Channel Ethertype of the
frame, they will drop it. (b) If end stations do recognize the frame, they will drop it. (b) If end stations do recognize the
RBridge-Channel Ethertype and the channel protocol indicated in the RBridge-Channel Ethertype and the channel protocol indicated in the
frame, they should refuse to process the frame due to an incorrect frame, they should refuse to process the frame due to an incorrect
value of the RBridge Channel Header NA flag. value of the RBridge Channel Header NA flag.
No protection is provided against forging or the ingress nickname in No protection is provided against forging of the ingress nickname in
a TRILL Data formatted channel message or the Outer.MacSA in a native a TRILL Data formatted channel message or the Outer.MacSA in a native
RBridge Channel frame. This may result in misdirected return RBridge Channel frame. This may result in misdirected return
responses or error messages. responses or error messages.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
8. References 8. References
The following sections list normative and informative references for The following sections list normative and informative references for
this document. this document.
skipping to change at page 24, line 7 skipping to change at page 24, line 7
3. Add acknowledgements section. 3. Add acknowledgements section.
4. Replace "OAM" references with "BFD" references in Abstract and 4. Replace "OAM" references with "BFD" references in Abstract and
Introduction. Introduction.
5. Very minor editorial changes. 5. Very minor editorial changes.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Acknowledgmnts Changes from -05 to -06
1. Improve wording in 2.1.1 re CHV values.
2. Revert "Ext-Len" to "Op-Len".
3. Fix typos and make minor editorial changes.
INTERNET-DRAFT TRILL: RBridge Channel
Acknowledgments
The authors gratefully acknowledge the comments and contributions of The authors gratefully acknowledge the comments and contributions of
the follows, listed is alphabetic order: Somnath Chatterjee, Anoop the follows, listed is alphabetic order: Somnath Chatterjee, Anoop
Ghanwani, Raksh Kumar, and Tissa Senevirathne. Ghanwani, Rakesh Kumar, and Tissa Senevirathne.
Authors' Addresses Authors' Addresses
Donald Eastlake 3rd Donald Eastlake 3rd
Huawei R&D USA Huawei R&D USA
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Tel: +1-508-333-2270 Tel: +1-508-333-2270
EMail: d3e3e3@gmail.com EMail: d3e3e3@gmail.com
Vishwas Manral Vishwas Manral
HP Networking HP Networking
19111 Pruneridge Avenue 19111 Pruneridge Avenue
Cupertino, CA 95014 USA Cupertino, CA 95014 USA
Tel: +1-408-477-0000 Tel: +1-408-477-0000
EMail: vishwa.manral@hp.com EMail: vishwas.manral@hp.com
Yizhou Li Yizhou Li
Huawei Technologies Huawei Technologies
101 Software Avenue, 101 Software Avenue,
Nanjing 210012, China Nanjing 210012, China
Phone: +86-25-56622310 Phone: +86-25-56622310
Email: liyizhou@huawei.com Email: liyizhou@huawei.com
Sam Aldrin Sam Aldrin
 End of changes. 22 change blocks. 
36 lines changed or deleted 47 lines changed or added

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