Transparent Interconnection of Lots of Links (TRILL): Clarifications, Corrections, and Updates
draft-ietf-trill-rfc7180bis-07

[Ballot comment]
The security considerations text left me wondering what "some" of the changes were as there is only one consideration listed.
Are there considerations for this change:

Appendix C.2
3. Change for the requirement to use the RPF check in [RFC6325] for
      multi-destination TRILL Data packets by providing an alternative
      stronger RPF check.

Or for any other changes?

Thanks.

[Ballot comment]
Based on a scan of the changes compared to the obsoleted and updated RFCs in appendix C, I don't see any changes that would impact OPS.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-trill-rfc7180bis-05. If any part of this review is inaccurate, please let us know.

As this document requests registrations in Expert Review (see RFC 5226) registries, we will initiate those reviews via separate tickets. These actions cannot be completed until the registration proposals are approved by the IESG-designated experts.

IANA understands that, upon approval of this document, there are eight actions which IANA must complete.

First, all but one reference to [RFC7180] in the Transparent Interconnection of Lots of Links (TRILL) Parameters located at:

http://www.iana.org/assignments/trill-parameters/

are replaced with references to [ RFC-to-be ]. The exception is the reference for bit 0 in the PORT-TRILL-VER Sub-TLV Capability Flags, which will be changed to draft-eastlake-trill-rfc6439bis.

Second, in the Sub-TLVs for TLV 144 subregistry of the IS-IS TLV Codepoints in the IS-IS TLV Codepoints registry located at:

http://www.iana.org/assignments/isis-tlv-codepoints/

a new registration will be added as follows:

Value: [ TBD-at-Registration ]
Group Address Type Code: E-L1FS FS-LSP support
Reference: [RFC7356] and [ RFC-to-be ]

This new registration requires expert review.

Third, in the Sub-TLVs for TLV 242 subregistry of the IS-IS TLV Codepoints in the IS-IS TLV Codepoints registry located at:

http://www.iana.org/assignments/isis-tlv-codepoints/

a new registration will be added as follows:

Value: [ TBD-at-Registration ]
Description: E-L1FS FS-LSP support
Reference: [RFC7356] and [ RFC-to-be ]

This new registration requires expert review.

Fourth, in the TRILL APPsub-TLV Types under IS-IS TLV 251 Application Identifier 1 subregistry of the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

http://www.iana.org/assignments/trill-parameters/

a new type is to be added as follows:

Type: [ TBD-at-Registration ]
Name: NICKFLAGS
Reference: [ RFC-to-be ]

IANA notes that the author request that this value come from the range less than 255.

This registration requires expert review.

Fifth, IANA will create a new registry called "NickFlags Bits." The new registry is to be located as a subregistry of the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

http://www.iana.org/assignments/trill-parameters/

The registry is to be managed via IETF Review as defined in RFC 5226. There are initial registrations in the new registry as follows:

Bit Mnemonic Description Reference
----- -------- ----------- ---------
0 IN Used as ingress [ RFC-to-be ]
1-15 - Unassigned

Sixth, in the TRILL Extended Header Flags subregistry of the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

http://www.iana.org/assignments/trill-parameters/

the following entries will be modified and added:

Bits Purpose Reference
---- ------------------------------------------------ ---------------
14-16 Extended Hop Count [ RFC-to-be ]
27-28 Extended Color [ RFC-to-be ]
29-31 Available non-critical ingress-to-egress flags [ RFC7179 ] and [ RFC-to-be ]

Seventh, in the TRILL-VER Sub-TLV Capability Flags subregistry of the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

http://www.iana.org/assignments/trill-parameters/

the following entries will be changed:

Bit Description Reference
----- -------------------------- ----------------
14 Extended Hop Count support [ RFC-to-be ]
15-16 Unassigned [ RFC-to-be ]
27-28 Extended Color support [ RFC-to-be ]
29-31 Extended header flag support [RFC7179][ RFC-to-be ]

Eighth, in the TRILL Nicknames subregistry of the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

http://www.iana.org/assignments/trill-parameters/

the existing "0xFFC2-0xFFFE Unassigned" line is to be changed to the following:

Name Description Reference
------------- -------------- -----------
0xFFC2-0xFFD7 Unassigned
0xFFD8-0xFFDF For use in documentation examples [ RFC-to-be ]
0xFFE0-0xFFFE Unassigned

IANA understands that these eight actions are the only ones required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (TRILL: Clarifications, Corrections, and Updates) to Proposed Standard


The IESG has received a request from the Transparent Interconnection of
Lots of Links WG (trill) to consider the following document:
- 'TRILL: Clarifications, Corrections, and Updates'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-10-19. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-trill-rfc7180bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-trill-rfc7180bis/ballot/


No IPR declarations have been submitted directly on this I-D.