[trill] WG LC on draft-ietf-trill-over-ip-14.txt - Consensus reached

"Susan Hares" <shares@ndzh.com> Mon, 19 February 2018 21:06 UTC

Return-Path: <shares@ndzh.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00E1124E15; Mon, 19 Feb 2018 13:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heRYXfGfMx7A; Mon, 19 Feb 2018 13:06:51 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F54C1200B9; Mon, 19 Feb 2018 13:06:51 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.176.251.46;
From: "Susan Hares" <shares@ndzh.com>
To: <trill@ietf.org>
Cc: <trill-chairs@ietf.org>, "'Alia Atlas'" <akatlas@gmail.com>
Date: Mon, 19 Feb 2018 16:06:48 -0500
Message-ID: <03b401d3a9c5$8ebe3d40$ac3ab7c0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03B5_01D3A99B.A5E83540"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdOpwtKnIKiPY61STEiVhy4nOYLFjQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/G4ayRnwMMzrijK3p-tOZPq67IA8>
Subject: [trill] WG LC on draft-ietf-trill-over-ip-14.txt - Consensus reached
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Feb 2018 21:06:53 -0000

Greetings: 

 

Thank you for your comments on the draft-ietfd-trill-over-ip-xx.txt   The WG
has reached consensus on the draft, and it will be sent forward to the IESG.


 

I want to thank Magnus Westlund, Ines Robles, and Joe Touch for their
targeted reviews.  

 

Joe asked two important questions that I want to chat about in announcing
the result.  

1)      Why IPSEC + TCP/UDP tunnels 

2)      Why the name TRILL over IP? - it is really TRILL over IP enabled
Transport port protocols 

 

 

During this WG LC, I spent time looking back into my notes to check our
evaluation of the alternatives GRE, TLS, or DLTS.  I also asked the  WG
leadership team (Jon, Sue, and Donald with Alia Atlas help) to discuss these
points that Joe raised.     Here's what I found. 

 

1)      Why IPSEC and TCP/UDP tunnels

 

After I walked through the WG archives, I found that over several IETFs we
debated TLS, DTLS, and GRE.   Our most substantive debate was at IETF 91.
The WG had settle on utilizing GRE, TLS, or DLTS - until hardware vendors
implementing TRILL came to chat with the WG at IETF 91.   The hardware
vendors asked that we would utilize IPSEC and higher layer tunnels (TCP/UDP)
so that TRILL switches could operate at line speed using these IPSEC
processing chips off board.  The WG decided to listen to vendor creating and
deploying TRILL capable devices. 

 

The hardware vendors reasoning still seems valid to the WG chairs and the
WGs.   If in the future hardware comes up with TLS, DTLS or GRE at Ethernet
switch line rates and vendors want a TRILL product with these tunnels, I'm
sure that a Routing AD or  the RTGWG draft will sponsor such a draft.  

 

2)      Is the name TRILL over IP valid? 

 

Now as to the name, Joe was correct the name should be changed since it is
really TRILL over IPSEC + Transport.   Donald's make the change to the title
of the document, and in the document.   

 

(PS - We did not change the file name.  It will go away when this draft
turns into a RFC)

 

 

Thanks for all your help! 

Susan Hares 

TRILL co-chair