Transparent Interconnection of Lots of Links (TRILL): Appointed Forwarders
draft-ietf-trill-rfc6439bis-05

[Ballot discuss]
Section 2.4 (Overload and Appointed Forwarders) talks about potential Appointed Forwarders which are overloaded.  In IS-IS, a node with the overload bit set "shall not" (ISO 10589) be considered for transit.  However, the use of "SHOULD NOT appoint an RBridge in overload" and "SHOULD re-assign VLANs from the overloaded RBridge" leaves a potential hole in the proper forwarding of TRILL data packers.  Why aren't MUST NOT/MUST used?  Is there something in the specific use of IS-IS by TRILL that I am missing?

I think this should be an easy DISCUSS to clear; either point to the piece I'm missing, or don't use an overloaded node.

[Ballot discuss]
I think this should be an easy DISCUSS to clear; either point to the piece I'm missing, or don't use an overloaded node.

Section 2.4 (Overload and Appointed Forwarders) talks about potential Appointed Forwarders which are overloaded.  In IS-IS, a node with the overload bit set "shall not" (ISO 10589) be considered for transit.  However, the use of "SHOULD NOT appoint an RBridge in overload" and "SHOULD re-assign VLANs from the overloaded RBridge" leaves a potential hole in the proper forwarding of TRILL data packers.  Why aren't MUST NOT/MUST used?  Is there something in the specific use of IS-IS by TRILL that I am missing?

[Ballot discuss]
I would like to see a resolution to Dan Romascanu's OPS DIR concern.
https://datatracker.ietf.org/doc/review-ietf-trill-rfc6439bis-04-opsdir-telechat-romascanu-2017-01-12/
Note that the discussion is under way with Donald Eastlake

[Ballot comment]
I had trouble parsing "output it to or queue it for" (this occurs twice in the sentence).

  However, it does not output it to or queue it for that link,
  although, if appropriate (for example, the frame is multi-
  destination), it may output it to or queue it for other links.

I don't think the text is incorrect, just awkward. Perhaps commas would help?

In these three subsection titles,

  3.2.1 Change Optimization One

  3.2.2 Change Optimization Two

  3.2.3 Settling Detection Optimization

I found the title for 3.2.3 helpful, but not 3.2.1 or 3.2.2. Is it possible to come up with more descriptive titles?

I found

  For robustness, a TRILL switch sends a number of copies of a Port-
  Shutdown messages configurable from one to three, which defaults to
  two copies, at a configurable interval, which defaults to 20
  milliseconds (see Section 6.6).

difficult to parse. Perhaps

  For robustness, a TRILL switch sends a configurable number of copies
  of Port-Shutdown messages separated by a configurable interval. The default
  number of copies is two, although this can be configured as one copy
  or as three copies, and the default interval is 20 milliseconds
  (see Section 6.6).

?

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

The IANA Services Operator has completed its review of draft-ietf-trill-rfc6439bis-03.txt. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there are three actions which we must complete.

First, 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:

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

four new TLV Types are to be registered as follows:

Type: [ TBD-at-registration ]
Name: AppointmentBitmap
Reference: [ RFC-to-be ]

Type: [ TBD-at-registration ]
Name: AppointmentList
Reference: [ RFC-to-be ]

Type: [ TBD-at-registration ]
Name: FGL-VLAN-Bitmap
Reference: [ RFC-to-be ]

Type: [ TBD-at-registration ]
Name: FGL-VLAN-Pairs
Reference: [ RFC-to-be ]

Second, in the RBridge Channel Protocols subregistry also in the Transparent Interconnection of Lots of Links (TRILL) Parameters registry located at:

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

a single, new protocol will be registered from the Standards Action range as follows:

Protocol: [ TBD-at-registration ]
Description: Port Shut-Down
Reference: [ RFC-to-be ]

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

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

the entry for value 0 (Hello reduction support) will have its reference changed from RFC 7780 to [ RFC-to-be ].

We understand that sections 10.2 through 10.5 represent documentation of data structures related to Appointed Forwarders in TRILL and not actions for the IANA Services Operator.

The IANA Services Operator understands that these three 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.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: "Susan Hares" , shares@ndzh.com., akatlas@gmail.com, trill-chairs@ietf.org, trill@ietf.org, draft-ietf-trill-rfc6439bis@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: EXTENSION OF Last Call:  (TRILL: Appointed Forwarders) 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: Appointed Forwarders'
  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 2017-01-10. 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


  TRILL supports multi-access LAN (Local Area Network) links where a
  single link can have multiple end stations and TRILL switches
  attached.  Where multiple TRILL switches are attached to a link,
  native traffic to and from end stations on that link is handled by a
  subset of those TRILL switches called "Appointed Forwarders", with
  the intent that native traffic in each VLAN be handled by at most one
  TRILL switch.  This document clarifies and updates the Appointed
  Forwarder mechanism. It updates RFC 6325, updates RFC 7177, and
  obsoletes RFC 6439.





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

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

The following IPR Declarations may be related to this I-D:

  https://datatracker.ietf.org/ipr/2585/
  https://datatracker.ietf.org/ipr/2685/

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: "Susan Hares" , shares@ndzh.com., akatlas@gmail.com, trill-chairs@ietf.org, trill@ietf.org, draft-ietf-trill-rfc6439bis@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (TRILL: Appointed Forwarders) 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: Appointed Forwarders'
  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 2017-01-03. 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


  TRILL supports multi-access LAN (Local Area Network) links where a
  single link can have multiple end stations and TRILL switches
  attached.  Where multiple TRILL switches are attached to a link,
  native traffic to and from end stations on that link is handled by a
  subset of those TRILL switches called "Appointed Forwarders", with
  the intent that native traffic in each VLAN be handled by at most one
  TRILL switch.  This document clarifies and updates the Appointed
  Forwarder mechanism. It updates RFC 6325, updates RFC 7177, and
  obsoletes RFC 6439.





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

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

The following IPR Declarations may be related to this I-D:

  https://datatracker.ietf.org/ipr/2585/
  https://datatracker.ietf.org/ipr/2685/

).

IANA - section has the definitions of additional PDUs.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

No new registries.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

No XML, BNF, MIB or yang in the document.