[L2tpext] Mirja Kühlewind's No Objection on draft-ietf-l2tpext-keyed-ipv6-tunnel-07: (with COMMENT)

"Mirja Kuehlewind" <ietf@kuehlewind.net> Sun, 30 October 2016 11:04 UTC

Return-Path: <ietf@kuehlewind.net>
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 7F1B912944C; Sun, 30 Oct 2016 04:04:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Mirja Kuehlewind" <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.36.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147782548147.20732.6496851240146212616.idtracker@ietfa.amsl.com>
Date: Sun, 30 Oct 2016 04:04:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/l2tpext/sTNDxFY-3GpOIwCtgrTduJAe19k>
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] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draf?= =?utf-8?q?t-ietf-l2tpext-keyed-ipv6-tunnel-07=3A_=28with_COMMENT=29?=
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: Sun, 30 Oct 2016 11:04:41 -0000

Mirja Kühlewind 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:


Two questions:

1) I assume this was in depth discussed in the wg but the given reasoning
for the following MUST does still not justify a MUST for me:
"All packets MUST carry the 64-bit L2TPv3 cookie field."
I would assume that there are possible deployment scenarios e.g. within a
single domain where other existing protection mechanisms might be
sufficient already that you don't really need the cookie...?

2) Further this is not normative language and i wonder if it should be:
"However, for compatibility with existing RFC3931 implementations, the
packets need to be sent with Session ID."
Again I assume that this could be a SHOULD because if you know that you
don't have devices that (only) implement RFC3931, you could probably even
neglect the session id...?