Transparent Interconnection of Lots of Links (TRILL): Header Extension
RFC 7179
| Document | Type |
RFC - Proposed Standard
(May 2014; No errata)
Updated by RFC 7780
Updates RFC 6325
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 7179 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Ralph Droms | ||
| IESG note | Erik Nordmark (nordmark@acm.org) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) D. Eastlake 3rd
Request for Comments: 7179 Huawei
Updates: 6325 A. Ghanwani
Category: Standards Track Dell
ISSN: 2070-1721 V. Manral
Ionos Corp.
Y. Li
Huawei
C. Bestler
Nexenta Systems
May 2014
Transparent Interconnection of Lots of Links (TRILL): Header Extension
Abstract
The IETF Transparent Interconnection of Lots of Links (TRILL) base
protocol (RFC 6325) specifies minimal hooks to safely support TRILL
Header extensions. This document specifies an initial extension
providing additional flag bits and specifies some of those bits. It
updates RFC 6325.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7179.
Eastlake, et al. Standards Track [Page 1]
RFC 7179 TRILL: Header Extension May 2014
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................3
1.1. Conventions Used in This Document ..........................3
2. TRILL Header Extensions .........................................3
2.1. RBridge Extended Flag Handling Requirements ................5
2.2. No Critical Surprises ......................................5
2.3. Extended Header Flags ......................................6
2.3.1. Critical Summary Bits ...............................7
2.4. Conflict of Extensions .....................................8
3. Specific Extended Header Flags ..................................9
3.1. RBridge Channel Alert Extended Flags .......................9
4. Additions to IS-IS ..............................................9
5. IANA Considerations ............................................10
6. Security Considerations ........................................10
7. Acknowledgements ...............................................11
8. References .....................................................11
8.1. Normative References ......................................11
8.2. Informative References ....................................11
Eastlake, et al. Standards Track [Page 2]
RFC 7179 TRILL: Header Extension May 2014
1. Introduction
The base IETF Transparent Interconnection of Lots of Links (TRILL)
protocol [RFC6325] provides a TRILL Header extension feature and
describes minimal hooks to safely support header extensions. (This
feature is called "options" in Section 3.8 of [RFC6325].) But,
except for the first two bits, the TRILL base protocol document does
not specify the structure of extensions to the TRILL Header nor the
details of any particular extension.
This document is consistent with [RFC6325] and provides further
details. It specifies an initial extension word providing additional
flag bits and specifies some of those bits. Additional extensions,
including TLV-encoded options, may be specified in later documents,
Show full document text