TRILL (Transparent Interconnection of Lots of Links) Over IP Transport
draft-ietf-trill-over-ip-17
Approval announcement
Draft of message to be sent after approval:
Announcement
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, martin.vigoureux@nokia.com, shares@ndzh.com, draft-ietf-trill-over-ip@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'TRILL (Transparent Interconnection of Lots of Links) Over IP Transport' to Proposed Standard (draft-ietf-trill-over-ip-16.txt)
The IESG has approved the following document:
- 'TRILL (Transparent Interconnection of Lots of Links) Over IP Transport'
(draft-ietf-trill-over-ip-16.txt) as Proposed Standard
This document has been reviewed in the IETF but is not the product of an IETF
Working Group.
The IESG contact person is Martin Vigoureux.
A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-trill-over-ip/
Ballot Text
Technical Summary
The TRILL (Transparent Interconnection of Lots of Links) protocol
supports both point-to-point and multi-access links and is designed
so that a variety of link protocols can be used between TRILL switch
ports. This document specifies transmission of encapsulated TRILL
data and TRILL IS-IS over IP (v4 or v6) transport. so as to use an IP
network as a TRILL link in a unified TRILL campus. This document
updates RFC 7177 and updates RFC 7178.
Working Group Summary
Consensus is strong with one outlier: Joe Touch
regarding use of IPSEC + TCP/UDP
See mail thread:
https://www.ietf.org/mail-archive/web/trill/current/msg08185.html
Why did we choose this approach:
In our working group investigation of this draft,
the WG was visited by vendors implementing TRILL
(most noteable at IETF 91). The vendors requested
the IPSEC + Transport approach.
While there are other approaches, no
vendor of TRILL equipment has requested the other approach.
Document Quality
Are there existing implementations of the protocol? See comments
above: hardware vendors looking for line rate speed
came to IETF 91 to give feedback to TRILL.
These vendors were in addition to the Huawei and IPInfusion implementations.
Personnel
Document Shepherd: Susan Hares
AD: Alia Atlas
RFC Editor Note