[L2tpext] Suresh Krishnan's Discuss on draft-ietf-l2tpext-keyed-ipv6-tunnel-07: (with DISCUSS)
"Suresh Krishnan" <suresh.krishnan@ericsson.com> Thu, 03 November 2016 04:04 UTC
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 4C7BC12940F; Wed, 2 Nov 2016 21:04:30 -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>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.37.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147814587027.24024.3232023685298654420.idtracker@ietfa.amsl.com>
Date: Wed, 02 Nov 2016 21:04:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/XaollJiKDlHuYTieUefEd06__GE>
Cc: cpignata@cisco.com, draft-ietf-l2tpext-keyed-ipv6-tunnel@ietf.org, l2tpext-chairs@ietf.org, draft-ietf-l2tpext-keyed-ipv6-tunnel.all@ietf.org, l2tpext@ietf.org
Subject: [L2tpext] Suresh Krishnan's Discuss on draft-ietf-l2tpext-keyed-ipv6-tunnel-07: (with DISCUSS)
X-BeenThere: l2tpext@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 03 Nov 2016 04:04:30 -0000
Suresh Krishnan has entered the following ballot position for draft-ietf-l2tpext-keyed-ipv6-tunnel-07: Discuss 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/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- * Section 5 I am having a hard time seeing how fragmentation is expected to work It is NOT RECOMMENDED for routers implementing this specification to enable IPv6 fragmentation (as defined in section 4.5 of RFC2460) for keyed IP tunnels. IP fragmentation issues for L2TPv3 are discussed in section 4.1.4 of RFC3931. And that specific section of RFC3931 recommends using RFC2473 to tunnel the packets which again ends up using the RFC2460 fragment header that this draft is trying to forbid. So, can you please clarify exactly what happens when the size of the packet to be tunneled exceeds the MTU?
- [L2tpext] Suresh Krishnan's Discuss on draft-ietf… Suresh Krishnan
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Carlos Pignataro (cpignata)
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Giles Heron
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Mark Townsley
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Carlos Pignataro (cpignata)
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Suresh Krishnan
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Giles Heron
- Re: [L2tpext] Suresh Krishnan's Discuss on draft-… Suresh Krishnan