Received changes through RFC Editor sync (created alias RFC 8380, changed title to 'Directory-Assisted Transparent Interconnection of Lots of Links (TRILL) Encapsulation', changed abstract to 'This document describes how data center networks can benefit from non-RBridge nodes performing TRILL (Transparent Interconnection of Lots of Links) encapsulation with assistance from a directory service.', changed pages to 10, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-21, changed IESG state to RFC Published)

[Ballot comment]
I support Alvaro's DISCUSS and Kathleen's comment

I also think it would be useful to emphasize the need for some security on the links between the egress and ingress nodes, although presumably that's a standard TRILL consideration.

Finally
      nodes. Such spoofing cannot cause looping traffic because TRILL has a
    hop count in the TRILL header [RFC6325] so that, should there be a
      loop, a TRILL packet caught in that loop (i.e., an encapsulated
      frame) will be discarded.

Is it in fact the case that it cannot cause looping or merely that the loop is contained by the hop count? Perhaps this is just a terminology issue and in routing loop just means infinite loop?

[Ballot discuss]
I have significant concerns about this document; as currently written, I believe the technology is underspecified and can cause significant damage to a DC network where it might be deployed.  I am then balloting a DISCUSS.

The document (including the security considerations) is written assuming that the TRILL-ENs can be trusted (and are not compromised), and that the directory information is accurate.  However, I believe there are several cases that have been overlooked.

(1) There aren't any basic safeguards specified to at least make sure that a TRILL-EN is doing the right thing (or something sensible).  For example, what if the Ingress RBridge Nickname field in the TRILL header doesn't correspond to the first rBridge at the domain boundary?  Should that frame be accepted?

(2) rfc8171 talks about issues with incorrect directory mappings.  Consider the case where a TRILL-EN uses (on purpose!) an incorrect mapping.  That "can result in data being delivered to the wrong end stations, or set of end stations in the case of multi-destination packets, violating security policy." [rfc8171]  How can this risk be mitigated?

I don't think that there are easy mitigations for these issues, but at least mentioning them so that operators are aware of the risk would be enough to clear this DISCUSS.

[Ballot comment]
Thanks for your work on this document.  I'd like to see stronger language used in the security considerations section.  I'll propose edits for you to consider:

OLD:
Therefore, there could be a potential security risk
  when the TRILL-ENs are not trusted.  In addition, if the path between
  the directory and the TRILL-ENs are attacked, false mappings can be
  sent to the TRILL-EN causing packets from the TRILL-EN to be sent to
  wrong destinations, possibly violating security policy. Therefore, a
  combination of authentication and encryption should be used between
  the Directory and TRILL-EN. The entities involved will need to
  properly authenticate with each other to protect sensitive
  information.

NEW:
  Therefore, there could be a potential security risk
  when the TRILL-ENs are not trusted or are compromised.  In addition, if the path between
  the directory and the TRILL-ENs are attacked, false mappings can be
  sent to the TRILL-EN causing packets from the TRILL-EN to be sent to
  wrong destinations, possibly violating security policy. Therefore, a
  combination of authentication and encryption is RECOMMENDED between
  the Directory and TRILL-EN. The entities involved will need to
  properly authenticate with each other, provide session encryption, maintain
  security patch levels, and configure their systems to allow minimal access and
  running processes to protect sensitive information.

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

The IANA Services Operator has reviewed draft-ietf-trill-directory-assisted-encap-09, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Amanda Baber
Lead IANA Services Specialist

The following Last Call announcement was sent out (ends 2018-03-06):

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: draft-ietf-trill-directory-assisted-encap@ietf.org, trill-chairs@ietf.org, trill@ietf.org, shares@ndzh.com, akatlas@gmail.com
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
Subject: Last Call: <draft-ietf-trill-directory-assisted-encap-09.txt> (Directory Assisted TRILL Encapsulation) to Proposed Standard


The IESG has received a request from the Transparent Interconnection of Lots
of Links WG (trill) to consider the following document: - 'Directory Assisted
TRILL Encapsulation'
  <draft-ietf-trill-directory-assisted-encap-09.txt> 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 2018-03-06. 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


  This draft describes how data center networks can benefit from non-
  RBridge nodes performing TRILL encapsulation with assistance from a
  directory service.





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

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

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

  https://datatracker.ietf.org/ipr/3045/

Shepherd-template date: 2/24/2012

(1) What type of RFC: Proposed staandard

Why: This is an extension to TRILL specifications to allow a node which
does not participate in TRILL'S RBridge IS-IS to encapsulate TRILL packets.

This extension does not require an update to other drafts.
Why? This extension is allowed by RFC6325, section 4.6.2 so it does not update RFC6325 specification.
The directory assistance context is described by RFC7067 and RFC8171, but
the details of encapsulation were not included in those drafts so
this specification does not require an update to this drafts.

[The careful splitting of the technology into clearly defined
orthogonal pieces was by design.]

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

This draft describes how data network can benefit
from non-Rbridge nodes peforming TRILL encapsulation with
assistance from a directory servicve.

RFC7067 and RFC8171 describe the framework nand methods for
for TRILL edge Rbridges to get MAC&VLAN <---> Edge RBridge mappings
from a directory service instead of flooding unknown destination MAC addresses
across a TRILL domain.  If it has the needed directory information,
any node even an non-RBRidge node, can perform TRILL data packet encapsulation.
This specification describes the benefits of and a scheme for
non-RBridge nodes performing TRILL encapsulation.

Working Group Summary

A complete directory service solution for TRILL was one of the
key additions to the base specification needed by the industry.
The TRILL working group designed the whole solution and its component
in discussions over 3-4  years.  This last group of specifications
depended on the approval of earlier specifications.

Document Quality:

Huawei plans an implementation of the protocol.

Personnel

Document Shepherd: Susan Hares
AD: Alia Atlas
RTG-DIR reviewer: Ben Niven

WG LC:
https://mailarchive.ietf.org/arch/msg/trill/vXYHJFIcapf3e2gjQ2iJ53_0CYw

IPR disclosed related to draft:
https://mailarchive.ietf.org/arch/msg/trill/nRtv_8-549eRKHR6PwBTuWBUy7w

Resolution of Donald Estlake Comments on WG LC:
https://mailarchive.ietf.org/arch/msg/trill/iwwppNnSCeGC-nzoM8j20NWdWTg

Resolution of Ben Niven's
https://mailarchive.ietf.org/arch/msg/trill/uO_uwTztWNwo0bIiRup5NOTiJHU

Closing of WG LC
https://mailarchive.ietf.org/arch/msg/trill/PcDQDPNt2JjD9o8xmvhPASZRtfk

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

No.  We've walked through this technology for 4+ years.
We've argued this draft into the ground, and taken reviews.


(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

No.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

No additional information

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

IPR disclosures:
Radia Perlman
https://mailarchive.ietf.org/arch/msg/trill/qynVYc48pAuJ8LXGN2qTrLS0jbQ

Donald Eastlake
https://mailarchive.ietf.org/arch/msg/trill/3H2Zkq5Aybe8Kice9nieoEWlrWQ

Linda Dunbar
https://mailarchive.ietf.org/arch/msg/trill/g4m2reIFY0nzs6ABAHQ-fjPmkIU



(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

IPR Disclosure mentioned on list:
https://www.ietf.org/mail-archive/web/trill/current/msg07897.html
https://datatracker.ietf.org/ipr/3045/


(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it? 

Solid.  We took a careful design approach for creating a whole directory solution.
Then, we broke the piece of the directory solution into component parts.
Due to this careful structure (which I inherited as an incoming chair),
the WG has then just focused on the minor details.

The only place this careful design philosphy is a problem is
when the IESG looks the debates on the specific drafts during WG LC.
You are not going to find these debates.  These occurred as
people brought forth individual drafts and work together toward a solution. 

Harmonious, thoughtful, and good designs - but frustrating to the AD review.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

no - see reasoning above.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

The only ID nit is that the draft is January 18th.  It is this shepherd fault for
being overloaded.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

no special reviews.

(13) Have all references within this document been identified as
either normative or informative?

yes

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

No.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

No.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary.

No drafts changed.


(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).



(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 IANA actions required.

(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.

Nits performed.  Only thing that applies.