TRILL: Clarifications, Corrections, and Updates
draft-ietf-trill-rfc7180bis-04
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (trill WG)
|
|
Last updated |
|
2015-03-25
|
|
Replaces |
|
draft-eastlake-trill-rfc7180bis
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
In WG Last Call
|
|
Document shepherd |
|
Susan Hares
|
|
Shepherd write-up |
|
Show
(last changed 2015-03-25)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Susan Hares" <shares@ndzh.com>
|
TRILL Working Group Donald Eastlake
INTERNET-DRAFT Mingui Zhang
Intended status: Proposed Standard Huawei
Obsoletes: 7180 Radia Perlman
Updates: 6325, 7177, 7179 EMC
Ayan Banerjee
Cisco
Anoop Ghanwani
Dell
Sujay Gupta
IP Infusion
Expires: September 24, 2015 March 25, 2015
TRILL: Clarifications, Corrections, and Updates
<draft-ietf-trill-rfc7180bis-04.txt>
Abstract
Since publication of the TRILL (Transparent Interconnection of Lots
of Links) base protocol in 2011, active development and deployment of
TRILL has revealed errata in RFC 6325 and areas that could use
clarifications or updates. RFCs 7177, 7357, and draft-eastlake-trill-
rfc6439bis provide clarifications and updates with respect to
Adjacency, the TRILL ESADI (End Station Address Distribution
Information) protocol, and Appointed Forwarders respectively. This
document provides other known clarifications, corrections, and
updates. It obsoletes RFC 7180 (the previous TRILL clarifications,
corrections, and updates RFC), updates RFC 7177, updates RFC 7179,
and updates RFC 6325.
Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Distribution of this document is unlimited. Comments should be sent
to the TRILL working group mailing list: <trill@ietf.org>.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
D. Eastlake, et al [Page 1]
INTERNET-DRAFT TRILL: Clarifications, Corrections, and Updates
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
D. Eastlake, et al [Page 2]
INTERNET-DRAFT TRILL: Clarifications, Corrections, and Updates
Table of Contents
1. Introduction (Changed)..................................5
1.1 Precedence (Changed)...................................5
1.2 Changes That Are Not Backward Compatible (Unchanged)...5
1.3 Terminology and Acronyms (Changed).....................6
2. Overloaded and/or Unreachable RBridges (Unchanged)......7
2.1 Reachability...........................................7
2.2 Distribution Trees.....................................8
2.3 Overloaded Receipt of TRILL Data Packets...............8
2.3.1 Known Unicast Receipt................................9
2.3.2 Multi-Destination Receipt............................9
2.4 Overloaded Origination of TRILL Data Packets...........9
2.4.1 Known Unicast Origination............................9
2.4.2 Multi-Destination Origination.......................10
2.4.2.1 An Example Network................................10
2.4.2.2 Indicating OOMF Support...........................11
2.4.2.3 Using OOMF Service................................11
3. Distribution Trees and RPF Check (Changed).............13
3.1 Number of Distribution Trees (Unchanged)..............13
3.2 Distribution Tree Update Clarification (Unchanged)....13
3.3 Multicast Pruning Based on IP Address (Unchanged).....13
3.4 Numbering of Distribution Trees (Unchanged)...........14
3.5 Link Cost Directionality (Unchanged)..................14
3.6 Alternative RPF Check (New)...........................14
3.6.1 Example of the Potential Problem....................15
3.6.2 Solution and Discussion.............................16
4. Nicknames Selection (Unchanged)........................18
5. MTU (Maximum Transmission Unit) (Unchanged)............20
5.1 MTU-Related Errata in RFC 6325........................20
5.1.1 MTU PDU Addressing..................................20
5.1.2 MTU PDU Processing..................................21
Show full document text