< draft-ietf-trill-vendor-channel-00.txt   vend34fftoc.txt 
TRILL Working Group Donald Eastlake TRILL Working Group Donald Eastlake
INTERNET-DRAFT Yizhou Li INTERNET-DRAFT Yizhou Li
Intended status: Proposed Standard Weiguo Hao Intended status: Proposed Standard Weiguo Hao
Huawei Huawei
Ayan Banerjee Ayan Banerjee
Cisco Cisco
Expires: July 14, 2018 January 15, 2018 Expires: September 7, 2018 March 8, 2018
TRILL: Vendor Specific TRILL Channel Protocol TRILL: Vendor Specific TRILL Channel Protocol
<draft-ietf-trill-vendor-channel-00.txt> <draft-ietf-trill-vendor-channel-01.txt>
Abstract Abstract
The IETF TRILL (TRansparent Interconnection of Lots of Links) The IETF TRILL (TRansparent Interconnection of Lots of Links)
protocol is implemented by devices called TRILL switches or RBridges protocol is implemented by devices called TRILL switches or RBridges
(Routing Bridges). TRILL includes a general mechanism, called RBridge (Routing Bridges). TRILL includes a general mechanism, called RBridge
Channel, for the transmission of typed messages between RBridges in Channel, for the transmission of typed messages between RBridges in
the same campus and between RBridges and end stations on the same the same campus and between RBridges and end stations on the same
link. This document specifies a method to send vendor specific link. This document specifies a method to send vendor specific
messages over the RBridge Channel facility. messages over the RBridge Channel facility.
skipping to change at page 2, line 18 skipping to change at page 2, line 18
1. Introduction............................................3 1. Introduction............................................3
1.1 Terminology and Acronyms...............................3 1.1 Terminology and Acronyms...............................3
2. Vendor Channel Packet Format............................4 2. Vendor Channel Packet Format............................4
3. Vendor Channel Errors...................................7 3. Vendor Channel Errors...................................7
3.1 Sending an Error Response..............................8 3.1 Sending an Error Response..............................8
4. IANA Considerations....................................10 4. IANA Considerations....................................10
5. Security Considerations................................11 5. Security Considerations................................11
Normative References......................................12 Normative References......................................12
Informative References....................................12 Informative References....................................12
Acknowledgements..........................................12
Authors' Addresses........................................13 Authors' Addresses........................................13
INTERNET-DRAFT TRILL: Vendor Channel INTERNET-DRAFT TRILL: Vendor Channel
1. Introduction 1. Introduction
The IETF TRILL (TRansparent Interconnection of Lots of Links) The IETF TRILL (TRansparent Interconnection of Lots of Links)
protocol [RFC6325] [RFC7780] is implemented by devices called TRILL protocol [RFC6325] [RFC7780] is implemented by devices called TRILL
switches or RBridges (Routing Bridges). It provides efficient least switches or RBridges (Routing Bridges). It provides efficient least
cost transparent routing in multi-hop networks with arbitrary cost transparent routing in multi-hop networks with arbitrary
skipping to change at page 10, line 23 skipping to change at page 10, line 23
IANA is requested to establish a registry as follows on the TRILL IANA is requested to establish a registry as follows on the TRILL
Parameters web page indented under RBridge Channel Error Codes after Parameters web page indented under RBridge Channel Error Codes after
RBridge Channel SubError Codes: RBridge Channel SubError Codes:
Registry: Vendor RBridge Channel Error Codes Registry: Vendor RBridge Channel Error Codes
Registration Procedures: Standards Action Registration Procedures: Standards Action
Reference: (This document) Reference: (This document)
Code Description Reference Code Description Reference
---- ----------- --------- ---- ----------- ---------
0 No error This document 0x00 No error This document
1 Message too short This document 0x01 Message too short This document
2 Unknown OUI/CID This document 0x02 Unknown OUI/CID This document
3 Unknown Sub-Protocol This document 0x03 Unknown Sub-Protocol This document
4 Unknown Sub-Version This document 0x04 Unknown Sub-Version This document
0x05-0x0F Unassigned - 0x05-0x0F Unassigned -
0x10-0xFE Reserved for vendor use This document 0x10-0xFE Reserved for vendor use This document
0xFF Reserved This document 0xFF Reserved This document
INTERNET-DRAFT TRILL: Vendor Channel INTERNET-DRAFT TRILL: Vendor Channel
5. Security Considerations 5. Security Considerations
See [RFC6325] for general TRILL Security Considerations. See [RFC6325] for general TRILL Security Considerations.
See [RFC7178] for general RBridge Channel Security Considerations. See [RFC7178] for general RBridge Channel Security Considerations.
The Vendor Specific RBridge Channel Protocol provides no security The Vendor Specific RBridge Channel Protocol provides no security
assurances or features. Any needed security could be provided by assurances or features. (Its first use was as an envelope for BFD
fields or processing within the Vendor Protocol Specific Data, which messages [RFC7175] which provide their own security.) Any needed
is outside the scope of this document. Alternatively or in addition, security can be provided by fields or processing within the Vendor
use of Vendor Channel MAY be nested inside the RBridge Channel Header Protocol Specific Data, which is outside the scope of this document.
Extension Protocol [RFC7978] which can provide some security Alternatively or in addition, use of Vendor Channel MAY be nested
services. inside the RBridge Channel Header Extension Protocol [RFC7978] which
can provide some security services.
INTERNET-DRAFT TRILL: Vendor Channel INTERNET-DRAFT TRILL: Vendor Channel
Normative References Normative References
[802] - IEEE Std 802-2014, "IEEE Standard for Local and Metropolitan [802] - IEEE Std 802-2014, "IEEE Standard for Local and Metropolitan
Area Networks: Overview and Architecture", June 2014. Area Networks: Overview and Architecture", June 2014.
[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, DOI 10.17487/RFC2119, Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119,
skipping to change at page 12, line 39 skipping to change at page 12, line 39
2014, <http://www.rfc-editor.org/info/rfc7178>. 2014, <http://www.rfc-editor.org/info/rfc7178>.
[RFC7780] - Eastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A., [RFC7780] - Eastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A.,
Ghanwani, A., and S. Gupta, "Transparent Interconnection of Ghanwani, A., and S. Gupta, "Transparent Interconnection of
Lots of Links (TRILL): Clarifications, Corrections, and Lots of Links (TRILL): Clarifications, Corrections, and
Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016, Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016,
<http://www.rfc-editor.org/info/rfc7780>. <http://www.rfc-editor.org/info/rfc7780>.
Informative References Informative References
[RFC7175] - Manral, V., Eastlake 3rd, D., Ward, D., and A. Banerjee,
"Transparent Interconnection of Lots of Links (TRILL):
Bidirectional Forwarding Detection (BFD) Support", RFC 7175,
DOI 10.17487/RFC7175, May 2014, <https://www.rfc-
editor.org/info/rfc7175>.
[RFC7978] - Eastlake 3rd, D., Umair, M., and Y. Li, "Transparent [RFC7978] - Eastlake 3rd, D., Umair, M., and Y. Li, "Transparent
Interconnection of Lots of Links (TRILL): RBridge Channel Interconnection of Lots of Links (TRILL): RBridge Channel
Header Extension", RFC 7978, DOI 10.17487/RFC7978, September Header Extension", RFC 7978, DOI 10.17487/RFC7978, September
2016, <http://www.rfc-editor.org/info/rfc7978>. 2016, <http://www.rfc-editor.org/info/rfc7978>.
Acknowledgements
The document was prepared in raw nroff. All macros used were defined
within the source file.
INTERNET-DRAFT TRILL: Vendor Channel INTERNET-DRAFT TRILL: Vendor Channel
Authors' Addresses Authors' Addresses
Donald E. Eastlake, 3rd Donald E. Eastlake, 3rd
Huawei Technologies Huawei Technologies
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Phone: +1-508-333-2270 Phone: +1-508-333-2270
 End of changes. 8 change blocks. 
19 lines changed or deleted 21 lines changed or added

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