
From nobody Fri Mar 17 15:13:14 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: l2tpext@ietf.org
Delivered-To: l2tpext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA2E129527; Fri, 17 Mar 2017 15:13:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-l2tpext-keyed-ipv6-tunnel@ietf.org, draft-ietf-l2tpext-keyed-ipv6-tunnel.all@ietf.org, l2tpext-chairs@ietf.org, cpignata@cisco.com, l2tpext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148978878655.21380.5007514694023898495.idtracker@ietfa.amsl.com>
Date: Fri, 17 Mar 2017 15:13:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/gjIbVgz__cXKAXVFCzWfH50XNr8>
Subject: [L2tpext] Suresh Krishnan's No Objection on draft-ietf-l2tpext-keyed-ipv6-tunnel-07: (with COMMENT)
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 22:13:07 -0000

Suresh Krishnan has entered the following ballot position for
draft-ietf-l2tpext-keyed-ipv6-tunnel-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-l2tpext-keyed-ipv6-tunnel/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my DISCUSS with the RFC Editor note.



From nobody Mon Mar 20 14:59:20 2017
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: l2tpext@ietf.org
Delivered-To: l2tpext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CF1126DFB; Mon, 20 Mar 2017 14:59:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.2
Auto-Submitted: auto-generated
Precedence: bulk
Cc: cpignata@cisco.com, draft-ietf-l2tpext-keyed-ipv6-tunnel@ietf.org, l2tpext@ietf.org, db3546@att.com, draft-ietf-l2tpext-keyed-ipv6-tunnel.all@ietf.org, l2tpext-chairs@ietf.org, "The IESG" <iesg@ietf.org>, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <149004714385.25005.9581870297787917133.idtracker@ietfa.amsl.com>
Date: Mon, 20 Mar 2017 14:59:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/6qQExhLjfMUMmM-hUp6ek6vYYZo>
Subject: [L2tpext] Protocol Action: 'Keyed IPv6 Tunnel' to Proposed Standard (draft-ietf-l2tpext-keyed-ipv6-tunnel-07.txt)
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/l2tpext/>
List-Post: <mailto:l2tpext@ietf.org>
List-Help: <mailto:l2tpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2tpext>, <mailto:l2tpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2017 21:59:04 -0000

The IESG has approved the following document:
- 'Keyed IPv6 Tunnel'
  (draft-ietf-l2tpext-keyed-ipv6-tunnel-07.txt) as Proposed Standard

This document is the product of the Layer Two Tunneling Protocol
Extensions Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-l2tpext-keyed-ipv6-tunnel/





Technical Summary

This document describes a simple L2 Ethernet over IPv6 tunnel
encapsulation with mandatory 64-bit cookie for connecting L2 Ethernet
attachment circuits identified by IPv6 addresses.  The encapsulation
is based on L2TPv3 over IP.

Implementing L2TPv3 over IPv6 [RFC2460] provides the opportunity to
utilize unique IPv6 addresses to identify Ethernet attachment
circuits directly, leveraging the key property that IPv6 offers, a
vast number of unique IP addresses.  In this case, processing of the
L2TPv3 Session ID may be bypassed upon receipt as each tunnel has one
and only one associated session.  This local optimization does not
hinder the ability to continue supporting the multiplexing of
circuits via the Session ID on the same router for other L2TPv3
tunnels.
 
Working Group Summary

The WG process as it relates to this document has been smooth
and without major controversies. One of the key goals of the WG
has been to ensure compliance, compatibility and continued
support of demultiplexing based on Session ID.
 

Document Quality

There are multiple interoperable implementations of the
solution described in this document, among four major router
vendors. These implementations are deployed and running in
production. Further, there is additional interop done with other
vendors, and implementations in Linux.

Personnel

   Who is the Document Shepherd for this document? Carlos Pignataro
   Who is the Responsible Area Director?  Deborah Brungard


RFC Editor's Note:
The last sentence of Section 5 needs to be deleted:
"IP fragmentation issues for L2TPv3 are discussed
  in section 4.1.4 of RFC3931."


