
From nobody Tue Aug  2 07:48:45 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7FA812D688 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 07:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 7ulZ8fauDQdA for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 07:48:33 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A36D12D178 for <ipv6@ietf.org>; Tue,  2 Aug 2016 07:48:30 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Aug 2016 14:48:29 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id D25D39CC4F; Tue,  2 Aug 2016 07:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; s= selector1; bh=Ds9cw1UFAIkm7GFO6ZYvtADbcP8=; b=oddi/WJt0qvPEG1T+j h18B5wBnXKTRoUMZrfIN0Grz/ntKQP3v2kOMVURH7oWw6aFUXAf3D7HRfeJhJ7iK xCA6fMoeZtHrwuynN9f35GJX3pLJrqy7db3BpLLJRLQfCH7oJ14Z+xdk40xjkwxQ njWXCVRa+m3yEH7xKOsH/6BoI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; q=dns; s=selector1; b=M2nZdVZSH7okBeD6yXqCxBY408LNluU3Ypuf1UY5kR+aeK0p HrCQAh+7aCE3C6H4GotRpl/994UBfm0Dh4PENWOkloMyAlAuWybV+Fr4N/npiQYC O/XQYS3doCQrnvnnzheuQbDHcbC9WrpDqUBvIoRgj/mXRtrPljtGKNdM+ok=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 689669CC4E; Tue,  2 Aug 2016 07:48:28 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 6B0DC2F5A8F7; Tue,  2 Aug 2016 16:48:25 +0200 (CEST)
From: otroan@employees.org
X-Pgp-Agent: GPGMail
Content-Type: multipart/signed; boundary="Apple-Mail=_DDCBC816-9BA3-4F64-BA5C-F6111DC0B522"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Consensus call: Path forward for draft-ietf-6man-default-iids-13
Date: Tue, 2 Aug 2016 16:48:24 +0200
Message-Id: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/q6tSG398VMHoLZGweBVtKm3n3L4>
Cc: 6man-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 14:48:43 -0000

--Apple-Mail=_DDCBC816-9BA3-4F64-BA5C-F6111DC0B522
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

All,

There is one remaining issue we need resolved before we can advance this =
document.
It is the issue of how the document shall update other documents.
Alissa has enumerated the 3 options we see below.

In the room there was support for option 1. Bernie proposed option 3 =
later on the list, as a possible compromise between 1 and 2.

This starts a one week call on confirming consensus for option 1 (Remove =
section 6). The call last until August 9th.

If you disagree with that choice, please state your objections to the =
list.

Best regards,
Ole

=3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D

Under this option, the recommendations in Section 3 would apply to all =
of the IP-over-foo documents listed in the document header. But, for =
nodes that do not follow these recommendations, the IP-over-foo =
documents would still contain their current text explaining how to =
construct an EUI-64 for an IID.


=3D=3D=3D Option 2: Keep Section 6 but add a sentence pointing to =
4291bis =3D=3D=3D

Each of the updates listed in Section 6 could be modified to add =
something along the lines of the last sentence here:

   The entire text of Section 4 of [RFC2464] is replaced with the
   following text:

   ---------------- cut here -------------- cut here ----------------
   The Interface Identifier [AARCH] for an Ethernet interface SHOULD
   be generated as specified in [RFC7217]. Embedding a stable
   link-layer address in the IID is NOT RECOMMENDED [RFCXXXX].
   [I-D.6man-rfc4291bis] Appendix A discusses approaches to IID creation
   for nodes that choose not to follow this guidance.
   ---------------- cut here -------------- cut here ----------------


=3D=3D=3D Option 3: Remove Section 6 but add a list of IP-over-foo =
document section updates =3D=3D=3D

Per Bernie=E2=80=99s suggestion, we could remove Section 6 and update =
Section 3 as follows:

OLD
   By default, nodes SHOULD NOT employ IPv6 address generation schemes
   that embed a stable link-layer address in the IID.  In particular,
   this document RECOMMENDS that nodes do not generate stable IIDs with
   the schemes specified in [RFC2464], [RFC2467], [RFC2470], [RFC2491],
   [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572], [RFC4338],
   [RFC4391], [RFC5121], and [RFC5072].  The specific updates to these
   documents to effectuate this recommendation are included in
   Section 6.

NEW
   By default, nodes SHOULD NOT employ IPv6 address generation schemes
   that embed a stable link-layer address in the IID.

   The recommendations in this Section apply to:

   Section 4 of [RFC2464]
   Section 6 of [RFC2464]
   Section 5 of [RFC2467]
   Section 7 of [RFC2467]
   Section 4 of [RFC2470]
   Section 6 of [RFC2470]
   Section 5.1 of [RFC2491]
   Section 5.1.1 of [RFC2491]
   Section 5.1.2 of [RFC2491]
   Section 5 of [RFC2492]
   Section 4 of [RFC2497]
   Section 8 of [RFC2497]
   Section 4 of [RFC2590]
   Section 4.1 of [RFC2590]
   Section 9 of [RFC2590]
   Section 6 of [RFC3146]
   Section 11 of [RFC3315] // modulo separate discussion about 3315bis
   Section 3 of [RFC3572]
   Section 6.2 of [RFC3572]
   Section 2.5.1 of [RFC4291] // modulo separate discussion about =
4291bis
   Section 5 of [RFC4338]
   Section 8 of [RFC4391]
   Section 4.1 of [RFC5072]
   Section 5 of [RFC5072]
   Section 9.1 of [RFC5121]

--Apple-Mail=_DDCBC816-9BA3-4F64-BA5C-F6111DC0B522
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXoLK5AAoJED4aXnjSQuKWkjYH+gINDnvKYGZmIFczPzm69D3H
91hmjLuldYEu+6A/qreiXihr38zOnWHuQCL54DOKgY9cw4lEHeS0245XyKglExId
Hc7O0nxpXL1OCUpFwJPW3keEHoCLdEn+DlVdEpe6w/1ZePhhuJ+6kGDrDkCiPNwq
7y6MyfKY/OjNwu3+glJT17kN80/mqiNcqD5r5glHdeVsHLdmCIjYTsU6QGnb7FmB
oRMaMisiVs2PU7yPRJcuyQy3VlwCn+OPkC9pnIP/NmTW/WpLH7+ol3ipMR1RH0QP
c4l8S29ovc8Z1YveA+9FAeb5FxGn+S5RjT+zPGTqwogDpyHDL4Ho5BVCWu+o5H0=
=bSxW
-----END PGP SIGNATURE-----

--Apple-Mail=_DDCBC816-9BA3-4F64-BA5C-F6111DC0B522--


From nobody Tue Aug  2 09:24:03 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0098312D7E3 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 09:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Svo6cTCUiu40 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 09:24:00 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (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 4343C12D79A for <ipv6@ietf.org>; Tue,  2 Aug 2016 09:24:00 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id s63so179703978qkb.2 for <ipv6@ietf.org>; Tue, 02 Aug 2016 09:24:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=mVbmTU/n2vT0LYNOnB/o+vVbG5kfXf4rRKNmNy9flWg=; b=Nv+9NOMtQ8dE127PY/Bvggr//UBiKFIsiiZbX8OaCBMP6V4aPgGwg9UMjBHpCztKwH wBnFo9O4ndC8qigypQD91EFfARx6pKDEnqM8DdVy9+PGVFXMSyvf1r68YWaz013w/GvX 97gpvu6YUaY6liGgHAHbVsmHs9wPBDAAj3hsIH8aKSEkoThiIupmHQeJ1Zr+H2cfq5kB 2t859Hj9BceJpaouqjA8BTTSO9bPJ3JQ0n/87Eh7KZin1z8jP4ZK11HO1edel2Qn2GPw St5lu2hQqlq5ApAJ3wQFGDASIzty/rh6ZO4TRLXYM5Q5+sTutuiCEIiQnDEQwQTNNyxa M4KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=mVbmTU/n2vT0LYNOnB/o+vVbG5kfXf4rRKNmNy9flWg=; b=Ue7CBjlcikmOE6GEeve3N99dhMjzm5FAEpndzOn9tE4yp4p9cNxuQc6DmnvNRSx4Vx jyCw1aOn9p8eV7pwRLqeou22RgInRoVTylpLk6pnPhkXNIA7vqL35CyWic5NH11Koq8P 2eWZV19mMqClSCU/fQ0+/ow4homcnR5RdkebSoRkcu9k99n3oOAHnCuJzqwzK0yKegEP 4SSZX210b6G/Rd+oU1Jl09JdJ1mCv1vE4HDu+zPKK7sTJ3VxDQslQAU2hIjlC4zsdZhO 3b0ttOdvvNBtrgHiuyQWRq64h3Q7l1pzLbkls8lfXd3Cjc21XWy7e3NV4CNwB9J/4BOb rUBw==
X-Gm-Message-State: AEkoouv2X2jtPR9Odjbu2tmAbqboGg6Anjw05Z+VI6SrbA0XHlwEW6NZAlW7ygTicKQ77y+7xjkJEZRJ0jxsew==
X-Received: by 10.55.98.205 with SMTP id w196mr76769999qkb.65.1470155039359; Tue, 02 Aug 2016 09:23:59 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Tue, 2 Aug 2016 09:23:58 -0700 (PDT)
In-Reply-To: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Tue, 2 Aug 2016 09:23:58 -0700
X-Google-Sender-Auth: YgurRaibzt8cYeMOimmfLtqgdVc
Message-ID: <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com>
Subject: Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lryjU-PCP-g9RBNpogU7sNB0zTM>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 16:24:02 -0000

At Tue, 2 Aug 2016 16:48:24 +0200,
otroan@employees.org wrote:

> There is one remaining issue we need resolved before we can advance this document.
> It is the issue of how the document shall update other documents.
> Alissa has enumerated the 3 options we see below.
>
> In the room there was support for option 1. Bernie proposed option 3 later on the list, as a possible compromise between 1 and 2.
>
> This starts a one week call on confirming consensus for option 1
> (Remove section 6). The call last until August 9th.

> === Option 1: Remove Section 6 ===
>
> Under this option, the recommendations in Section 3 would apply to
> all of the IP-over-foo documents listed in the document header. But,
> for nodes that do not follow these recommendations, the IP-over-foo
> documents would still contain their current text explaining how to
> construct an EUI-64 for an IID.

This may be not in the scope of this call, but in this case are we
also going to update Section 3 so it will be clearer that it's okay to
not follow the recommendations of this document (assuming that's the
consensus)?  In its current form that's not clear to me, especially
because of wording like "the default scheme".

--
JINMEI, Tatuya


From nobody Tue Aug  2 10:21:16 2016
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD3E12B01B; Tue,  2 Aug 2016 10:21:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: "The IESG" <iesg@ietf.org>
Subject: Stephen Farrell's No Objection on draft-ietf-6man-multi-homed-host-07: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802172111.27938.62324.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 10:21:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jxq9KtWMt0OravN9L5xHWD-QWfc>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, jounikor@gmail.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 17:21:11 -0000

Stephen Farrell has entered the following ballot position for
draft-ietf-6man-multi-homed-host-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-6man-multi-homed-host/



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


general: I think this is very verbose, an editing pass
to remove as many words as possible would be good, some
examples below where I think more words confused me more
than was needed...

- Abstract: is bcp38 really crucial here or advisory? If
the latter, then I'd suggest not making it sound like it
is necessary, no matter how much we'd like it deployed.

- intro: "the only consistent solution" may be an
overstatement (unless you can prove there is no other)

- text on p4 after figure 1: it's probably me but I
found reading this a slog, not sure if it's really
needed, but if (part of) it is, making the necessary
bits clearer would seem like a fine plan. If it's not
needed, maybe delete some or all of it.

- 2.1: When you say SLAAC here, are you encompassing use
of privacy addresses? Sometimes those are presented as
an alternative to SLAAC but I'm not sure which is the
more correct terminology. In any case, I assume this
document is intended to fully work with privacy
addresses.



From nobody Tue Aug  2 10:39:44 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1660712D62A for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 10:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=pOwfnCbe; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=tUcoxlX1
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 DWcLFa5rtpDG for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 10:39:41 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62B7B12D09A for <ipv6@ietf.org>; Tue,  2 Aug 2016 10:39:41 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B0C7920863; Tue,  2 Aug 2016 13:39:40 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 02 Aug 2016 13:39:40 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=vv4NE MapDRcg52pBwQbEVRzUviU=; b=pOwfnCbe7knT+/BYhUZdPvnudUKCmUqD25wxA miMwgb2BT7ZptyVhWALBbwqB/IX81PJC1bUG6aW1X66D65SKxefJ+dA41MyKrm1N +v9EYI/G+zQO/YiiuHuOj9rxN8RGEaLN5TXESMoFC3NV7MXwIOzytggJ44W5T6yr 1oTEwU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=vv4NEMapDRcg52pBwQbEVRzUviU=; b=tUcox lX1kU3GTs5KSpqYFKGwAJ95qHpV/Gl44BlYFKIc3wqXD7iP+8x5mzpC8+GB+sIZK /6lifX+St/NgTo6qIA0xlKTx5+1YfCxXoUkx7GvgUbsyHHImj6++U0pHHJuk9NVb nt2Ztc0mYGCVNo98Q1gkLvesWJp1TY/h6xjH80=
X-Sasl-enc: V6bilrHUa/3bLWwWxg+Z00EqcCRqlc3xisgPgnAMkh/e 1470159580
Received: from dhcp-171-68-20-177.cisco.com (dhcp-171-68-20-177.cisco.com [171.68.20.177]) by mail.messagingengine.com (Postfix) with ESMTPA id F3A88CCDCF; Tue,  2 Aug 2016 13:39:39 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4428C8EC-7133-4D8F-9595-4CD7F296FB4B"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com>
Date: Tue, 2 Aug 2016 10:39:38 -0700
Message-Id: <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/L2veyv28f3qkrzRwwUwGqr14C8o>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 17:39:43 -0000

--Apple-Mail=_4428C8EC-7133-4D8F-9595-4CD7F296FB4B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Jinmei,

> On Aug 2, 2016, at 9:23 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Tue, 2 Aug 2016 16:48:24 +0200,
> otroan@employees.org wrote:
>=20
>> There is one remaining issue we need resolved before we can advance =
this document.
>> It is the issue of how the document shall update other documents.
>> Alissa has enumerated the 3 options we see below.
>>=20
>> In the room there was support for option 1. Bernie proposed option 3 =
later on the list, as a possible compromise between 1 and 2.
>>=20
>> This starts a one week call on confirming consensus for option 1
>> (Remove section 6). The call last until August 9th.
>=20
>> =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D
>>=20
>> Under this option, the recommendations in Section 3 would apply to
>> all of the IP-over-foo documents listed in the document header. But,
>> for nodes that do not follow these recommendations, the IP-over-foo
>> documents would still contain their current text explaining how to
>> construct an EUI-64 for an IID.
>=20
> This may be not in the scope of this call, but in this case are we
> also going to update Section 3 so it will be clearer that it's okay to
> not follow the recommendations of this document (assuming that's the
> consensus)?  In its current form that's not clear to me, especially
> because of wording like "the default scheme=E2=80=9D.

Could you explain precisely what you find unclear? The sentence to which =
you refer says

"Nodes SHOULD implement and employ [RFC7217 =
<https://tools.ietf.org/html/rfc7217>] as the default scheme for =
generating stable IPv6 addresses with SLAAC.=E2=80=9D

The use of SHOULD indicates that there may exist valid reasons in =
particular circumstances to ignore the recommendation (to quote RFC =
2119). Are you saying you=E2=80=99d like to see=20

s/the default scheme/their default scheme/

? Or something else?

Thanks,
Alissa



>=20
> --
> JINMEI, Tatuya
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_4428C8EC-7133-4D8F-9595-4CD7F296FB4B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Hi Jinmei,</div><br class=3D""><div><blockquote=
 type=3D"cite" class=3D""><div class=3D"">On Aug 2, 2016, at 9:23 AM, =
=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 &lt;<a =
href=3D"mailto:jinmei@wide.ad.jp" class=3D"">jinmei@wide.ad.jp</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">At Tue, 2 Aug 2016 16:48:24 +0200,<br class=3D""><a =
href=3D"mailto:otroan@employees.org" class=3D"">otroan@employees.org</a> =
wrote:<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">There is one remaining issue we need resolved before we can =
advance this document.<br class=3D"">It is the issue of how the document =
shall update other documents.<br class=3D"">Alissa has enumerated the 3 =
options we see below.<br class=3D""><br class=3D"">In the room there was =
support for option 1. Bernie proposed option 3 later on the list, as a =
possible compromise between 1 and 2.<br class=3D""><br class=3D"">This =
starts a one week call on confirming consensus for option 1<br =
class=3D"">(Remove section 6). The call last until August 9th.<br =
class=3D""></blockquote><br class=3D""><blockquote type=3D"cite" =
class=3D"">=3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D<br =
class=3D""><br class=3D"">Under this option, the recommendations in =
Section 3 would apply to<br class=3D"">all of the IP-over-foo documents =
listed in the document header. But,<br class=3D"">for nodes that do not =
follow these recommendations, the IP-over-foo<br class=3D"">documents =
would still contain their current text explaining how to<br =
class=3D"">construct an EUI-64 for an IID.<br class=3D""></blockquote><br =
class=3D"">This may be not in the scope of this call, but in this case =
are we<br class=3D"">also going to update Section 3 so it will be =
clearer that it's okay to<br class=3D"">not follow the recommendations =
of this document (assuming that's the<br class=3D"">consensus)? &nbsp;In =
its current form that's not clear to me, especially<br class=3D"">because =
of wording like "the default scheme=E2=80=9D.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Could =
you explain precisely what you find unclear? The sentence to which you =
refer says</div><div><br class=3D""></div><div style=3D"widows: =
1;">"<span style=3D"font-size: 13.3333px; widows: 1;" class=3D"">Nodes =
SHOULD implement and employ [</span><a =
href=3D"https://tools.ietf.org/html/rfc7217" title=3D"&quot;A Method for =
Generating Semantically Opaque Interface Identifiers with IPv6 Stateless =
Address Autoconfiguration (SLAAC)&quot;" style=3D"font-size: 13.3333px; =
widows: 1;" class=3D"">RFC7217</a><span style=3D"font-size: 13.3333px; =
widows: 1;" class=3D"">] as the default scheme for&nbsp;</span><span =
style=3D"font-size: 13.3333px; widows: 1;" class=3D"">generating stable =
IPv6 addresses with SLAAC.</span><font size=3D"2" =
class=3D"">=E2=80=9D</font></div><div><span style=3D"font-size: =
13.3333px; widows: 1;" class=3D""><br class=3D""></span></div><div><span =
style=3D"font-size: 13.3333px; widows: 1;" class=3D"">The use of SHOULD =
indicates&nbsp;</span><span style=3D"white-space: pre-wrap; widows: 1;" =
class=3D"">that there </span><span style=3D"widows: 1;" class=3D""><span =
style=3D"white-space: pre-wrap;" class=3D"">may exist valid reasons in =
particular circumstances to ignore the recommendation (to quote RFC =
2119). Are you saying you=E2=80=99d like to see =
</span></span></div><div><span style=3D"widows: 1;" class=3D""><span =
style=3D"white-space: pre-wrap;" class=3D""><br =
class=3D""></span></span></div><div><span style=3D"widows: 1;" =
class=3D""><span style=3D"white-space: pre-wrap;" class=3D"">s/the =
default scheme/their default scheme/</span></span></div><div><span =
style=3D"widows: 1;" class=3D""><span style=3D"white-space: pre-wrap;" =
class=3D""><br class=3D""></span></span></div><div><span style=3D"widows: =
1;" class=3D""><span style=3D"white-space: pre-wrap;" class=3D"">? Or =
something else?</span></span></div><div><span style=3D"widows: 1;" =
class=3D""><span style=3D"white-space: pre-wrap;" class=3D""><br =
class=3D""></span></span></div><div><span style=3D"widows: 1;" =
class=3D""><span style=3D"white-space: pre-wrap;" =
class=3D"">Thanks,</span></span></div><div><span style=3D"widows: 1;" =
class=3D""><span style=3D"white-space: pre-wrap;" =
class=3D"">Alissa</span></span></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">--<br class=3D"">JINMEI, Tatuya<br =
class=3D""><br =
class=3D"">---------------------------------------------------------------=
-----<br class=3D"">IETF IPv6 working group mailing list<br class=3D""><a =
href=3D"mailto:ipv6@ietf.org" class=3D"">ipv6@ietf.org</a><br =
class=3D"">Administrative Requests: =
https://www.ietf.org/mailman/listinfo/ipv6<br =
class=3D"">---------------------------------------------------------------=
-----<br class=3D""></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_4428C8EC-7133-4D8F-9595-4CD7F296FB4B--


From nobody Tue Aug  2 10:55:31 2016
Return-Path: <akatlas@gmail.com>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9CA12D18B; Tue,  2 Aug 2016 10:55:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alia Atlas" <akatlas@gmail.com>
To: "The IESG" <iesg@ietf.org>
Subject: Alia Atlas' Discuss on draft-ietf-6man-multi-homed-host-07: (with DISCUSS)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802175528.27796.6986.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 10:55:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lYnoZsq5NgikqXKawvljOhIQEDU>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, jounikor@gmail.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 17:55:28 -0000

Alia Atlas has entered the following ballot position for
draft-ietf-6man-multi-homed-host-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-6man-multi-homed-host/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

In section 2.2, the document says:

"The direct implication of Section 2.1 is that, if the network uses a
   routing protocol, the routing protocols used in multihomed networks
   SHOULD implement source-prefix based egress routing, for example as
   described in [I-D.ietf-rtgwg-dst-src-routing]."

I understand the desire behind this statement - but find the SHOULD
extremely
strong given that we don't even have any routing protocol extensions
adopted by
ISIS, OPSF or even Babel WGs to handle source-prefix based egress
routing.  
I know that we are actively discussing the problems motivating this
statement
and, I hope, making progress.   However, I don't think that the dynamics
or scaling
or potential looping (for routers that don't support the same source
prefixes) have
been fully described or resolved.

While this problem has been discussed in rtgwg, I do not yet see
consensus in the
Routing Area that this is the agreed solution.  The email sent by v6ops
about this
problem recommended src-dest-routing as a solution and, indeed, that is
being
investigated.

At a minimum, the language in this section needs to change from SHOULD.





From nobody Tue Aug  2 11:39:14 2016
Return-Path: <aretana@cisco.com>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A639612B018; Tue,  2 Aug 2016 11:39:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "Alvaro Retana" <aretana@cisco.com>
To: "The IESG" <iesg@ietf.org>
Subject: Alvaro Retana's No Objection on draft-ietf-6man-multi-homed-host-07: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160802183910.27796.97116.idtracker@ietfa.amsl.com>
Date: Tue, 02 Aug 2016 11:39:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MVe2sOkcqIpNsa0Jz_Qa5GnVdrg>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 18:39:10 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-6man-multi-homed-host-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-6man-multi-homed-host/



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

Besides my first comment (which matches Alia's DISCUSS, which I support,
but offers a slightly different point of view), I don't think that my
comments raise to the point of a DISCUSS, but I would really like them to
be considered as a STRONG COMMENT (stronger ones are at the top).

1. First of all, there's the topic of the scope.  From Section 1.
(Introduction and Applicability):  "…the mechanics of egress routing once
the packet leaves the host are out of scope."  But then in Section 2.2.
(Expectations of multi homed networks) you write that "The direct
implication of Section 2.1 is that, if the network uses a routing
protocol, the routing protocols used in multihomed networks SHOULD
implement source-prefix based egress routing".  I think that the "SHOULD"
goes against the fact that routing is out of scope.  While the general
statement (of needing src-dst routing) may be true, for the networks
shown in 2.1 all you really need is a default route as the topology and
the host itself take care of selecting the correct exit point — so it is
also not that direct of an implication.  Proposed solution: ideally get
rid of 2.2, but I'm fine with changing the "SHOULD" for something not in
RFC2119, for example may need to/is for future investigation/…

2. In Section 1. (Introduction and Applicability) there are 2 places that
say that implementations "will need to extend/add support".  What does
that mean?  This document is a specification of what has to be done, so
it shouldn't read like a list of future actions.  Given that the next
sentence warns that "Hosts that do not support these features may fail to
communicate in the presence of filters as described above."…I would like
to see the text be a little more prescriptive than just saying "will need
to extend" or "will need to add support".  "SHOULD" seems appropriate.

2.1.  In the same piece of text…  "…this specification is consistent with
[RFC4861].  Nevertheless, implementers of Sections 5.2, 6.2.3, 6.3.4 and
8 of RFC 4861 will need to extend their implementations accordingly."  
It would be very nice if the text included the sections where the
appropriate extensions are mentioned/defined — presumably these
extensions are how RFC4861 is Updated.

2.2. Same text…  "This specification is fully consistent with [RFC6724]
and implementers will need to add support for its Rule 5.5."  It may not
be apparent (at this point in the text) to everyone that 5.5 applies to
the case where information related to which next-hop advertised which
prefix (or that the document is going in that direction) -- please
include a reference to section 3.3.

3. In Section 3.1. (Interpreting Router Advertisements), "…Bob-A and one
had advertised itself as a default router or as having a route to Alice,
that is the router Bob should choose.  If none of Bob-A have advertised
that but Bob-B has, it is irrelevant; Bob is using the address allocated
in PA and courts a BCP 38 discard if he doesn't send the packet to
Bob-A."  I think this case is irrelevant too, but not because Bob
knows/thinks about BCP 38 — it is irrelevant because of Rule 5.5 in
rfc6724 (if I'm reading the order of the rules correctly).  Please
clarify.



From nobody Tue Aug  2 12:58:58 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E658A12D50E; Tue,  2 Aug 2016 12:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 CBhqQb69lEhU; Tue,  2 Aug 2016 12:58:56 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 0939212D52B; Tue,  2 Aug 2016 12:58:56 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id h186so69216057pfg.3; Tue, 02 Aug 2016 12:58:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=NYYR/0r2PqEoe6Gk+qtriJELRnYepGHJ0TAOLTc+gkE=; b=inGxbWqnZyG3zsguChv9EuZCUXxjWEsYFZhsVFY/gIt5RZ3hUNeV7XjZlFhrs3q2c2 9m2kE/3oDJ4q4Ar5ihRQC+1jn5f505eA/n/ir0ARCmFukbOMmUT1mLgtF46tfMtd0+00 VhWnaQ5D0ZKTSQ3YPxwrQ7Xf5mRwLH8fSeYinpnrnTV8dEEfFrNRpKMRAuf72HMPGKon aLc/BN356I6teZ7948hZ0D4s3q1DdDi3IJlOwZvAQoYwlPaCNbkZFyzFXaA4mNoU3OIl 8GDmjcofmYAkuwDDEpisHDXpXDW0qWHqXeGRjWD9eQmx1cdw56mmYiDO8Mgulzh4YSUZ mMHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=NYYR/0r2PqEoe6Gk+qtriJELRnYepGHJ0TAOLTc+gkE=; b=jZl2XjfgiO/XnuqdzjwL9dG8su3XZHEPwzSYQtnxz1GYO3OdT0P7LyrGw1RTdC/aYO 5CFxRDogT64Duf358l3Frs2E+p146JJs40Xx3jzMLnkwwb7+u0wbSrCY3AQzUVFrTDkV 3fl/QeJ+Cbj63xIQuBNqGnVs2fRZFqFWjK/aqrUMtsgogwJMRdhy85SbGAWayug0ca1P 2HatztD5NOHaHiACEH+yUrDmGd27Fxm+fApnXXa7/GDKIB7qKNgWa9gcIPssfWsAb9n2 4oE7wv9IyKhFyTl63v0m6XgbvnMPJWpH+RccytWDcyqIIznRH6G+GLEhwNhJh5ZIj96a 14Ig==
X-Gm-Message-State: AEkoouuM/OPhXnnyvlJiZhcw11PmSRSEGdg8arrV59yrXaXjF+s8xIJaK4UFuaeiAhBI5w==
X-Received: by 10.98.31.219 with SMTP id l88mr109374677pfj.155.1470167935389;  Tue, 02 Aug 2016 12:58:55 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.250]) by smtp.gmail.com with ESMTPSA id m128sm6788102pfm.42.2016.08.02.12.58.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 12:58:54 -0700 (PDT)
Subject: Re: Alia Atlas' Discuss on draft-ietf-6man-multi-homed-host-07: (with DISCUSS)
To: Alia Atlas <akatlas@gmail.com>, The IESG <iesg@ietf.org>
References: <20160802175528.27796.6986.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b79baab3-a029-f57e-4554-bc41ccefe476@gmail.com>
Date: Wed, 3 Aug 2016 07:58:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160802175528.27796.6986.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0EY8NTGPpHVjXJiV9kyGZcYEb8Y>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, jounikor@gmail.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 19:58:57 -0000

On 03/08/2016 05:55, Alia Atlas wrote:
...
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> In section 2.2, the document says:
> 
> "The direct implication of Section 2.1 is that, if the network uses a
>    routing protocol, the routing protocols used in multihomed networks
>    SHOULD implement source-prefix based egress routing, for example as
>    described in [I-D.ietf-rtgwg-dst-src-routing]."
> 
> I understand the desire behind this statement - but find the SHOULD
> extremely
> strong 

Actually, you're right - I don't believe that this draft can make normative
statements about routing practices. I think what we meant here was plain
English "should", not RFC2119 normative SHOULD.

    Brian

> given that we don't even have any routing protocol extensions
> adopted by
> ISIS, OPSF or even Babel WGs to handle source-prefix based egress
> routing.  
> I know that we are actively discussing the problems motivating this
> statement
> and, I hope, making progress.   However, I don't think that the dynamics
> or scaling
> or potential looping (for routers that don't support the same source
> prefixes) have
> been fully described or resolved.
> 
> While this problem has been discussed in rtgwg, I do not yet see
> consensus in the
> Routing Area that this is the agreed solution.  The email sent by v6ops
> about this
> problem recommended src-dest-routing as a solution and, indeed, that is
> being
> investigated.
> 
> At a minimum, the language in this section needs to change from SHOULD.
> 
> 
> 
> 
> 


From nobody Tue Aug  2 13:17:29 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC8C212D94F; Tue,  2 Aug 2016 13:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XA2dqUDPusQ8; Tue,  2 Aug 2016 13:17:19 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 4624B12D948; Tue,  2 Aug 2016 13:17:19 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id h186so69338059pfg.3; Tue, 02 Aug 2016 13:17:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=rAUzAUn1vLAGl1+41rQu9fuLlEncf8BMo8yNzUqBwSw=; b=Rjn0/B8Qh7gFUbZghxCqDwGB8961sISgEyOaGZSnEuQMGNcLM9+vxq47xZjmhkpwKK OVE0cnWdmhxGrmOl6t8kh5larL+d0ooG3G8HQYwhHklg8sdkVjqj6wVO5bG77wcgEQ4S 3gx9c7Pfu+9jt50OLY304/SRlfc0oWbJp4cxdtTjIYa+G5/ii6ByQ9JA2HK4qE4hLj/T QHGx+LwQJuWT+VS1NaZDO/IAYZNstpUTa0tVwdzHK5D8EBJt+dWzUwJd5D1m2O2ez3fx cnZS/ULW9Qxe1MPu5xkVqu71MB/LGXSUlA4XlYYlK0FAlMhzNeQRs1jQ9yNDMbLCdgIv A+9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=rAUzAUn1vLAGl1+41rQu9fuLlEncf8BMo8yNzUqBwSw=; b=bC3x/aZn/oDCwizkeWxqwvIpYxrDw5EbswsR0bbtzTOjSRHYLGsj87PEejaBN2Z61J kucoguBgnHfqatxJpkzgTvicoItJAI7uWwozMlySeYCnvSqlotlqQkEFTsPfuxVPTIbe Q/6rqORCVD5y9dnyuaSdPNVuIeOvfKh2rry+nmgFxNhf1ckLJQBTgI2Td5OFUpTb5r72 CxY1elRRk3qoD5CBffSSRrMgprEa/5m/PY2ebu84zEdqlXnIfVfHC4kKpb2St/90cD20 GUBTwO4XKKspjrVCmG7nfENFwf1ZxjDEyEVsaIV8Rj/e9usEBVEIEgjo1gvWL+AEKrVN Fpcw==
X-Gm-Message-State: AEkooutD3rOecK5ufv6GwYT4AAYZGYq01Ntju5e1K7Z9x4CAwKA5q81xziIzGw+V8LwgwQ==
X-Received: by 10.98.96.193 with SMTP id u184mr80293135pfb.85.1470169038839; Tue, 02 Aug 2016 13:17:18 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.250]) by smtp.gmail.com with ESMTPSA id o2sm6853532pfg.10.2016.08.02.13.17.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 13:17:18 -0700 (PDT)
Subject: Re: Alvaro Retana's No Objection on draft-ietf-6man-multi-homed-host-07: (with COMMENT)
To: Alvaro Retana <aretana@cisco.com>, The IESG <iesg@ietf.org>
References: <20160802183910.27796.97116.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6006274b-71eb-56d1-c4b0-d867af349609@gmail.com>
Date: Wed, 3 Aug 2016 08:17:18 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160802183910.27796.97116.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/3V0YLgrqrUpYuMV6wad4H44bILQ>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 20:17:21 -0000

On 03/08/2016 06:39, Alvaro Retana wrote:
=2E..
> 1. First of all, there's the topic of the scope.  From Section 1.
> (Introduction and Applicability):  "=E2=80=A6the mechanics of egress ro=
uting once
> the packet leaves the host are out of scope."  But then in Section 2.2.=

> (Expectations of multi homed networks) you write that "The direct
> implication of Section 2.1 is that, if the network uses a routing
> protocol, the routing protocols used in multihomed networks SHOULD
> implement source-prefix based egress routing".  I think that the "SHOUL=
D"
> goes against the fact that routing is out of scope.  While the general
> statement (of needing src-dst routing) may be true, for the networks
> shown in 2.1 all you really need is a default route as the topology and=

> the host itself take care of selecting the correct exit point =E2=80=94=
 so it is
> also not that direct of an implication.  Proposed solution: ideally get=

> rid of 2.2, but I'm fine with changing the "SHOULD" for something not i=
n
> RFC2119, for example may need to/is for future investigation/=E2=80=A6

Agreed (see my response to Alia).

> 2. In Section 1. (Introduction and Applicability) there are 2 places th=
at
> say that implementations "will need to extend/add support".  What does
> that mean?  This document is a specification of what has to be done, so=

> it shouldn't read like a list of future actions.  Given that the next
> sentence warns that "Hosts that do not support these features may fail =
to
> communicate in the presence of filters as described above."=E2=80=A6I w=
ould like
> to see the text be a little more prescriptive than just saying "will ne=
ed
> to extend" or "will need to add support".  "SHOULD" seems appropriate.

I wouldn't object to s/will need to/SHOULD/ in both cases. I guess it see=
med
a bit out of place in the Introduction section.

>=20
> 2.1.  In the same piece of text=E2=80=A6  "=E2=80=A6this specification =
is consistent with
> [RFC4861].  Nevertheless, implementers of Sections 5.2, 6.2.3, 6.3.4 an=
d
> 8 of RFC 4861 will need to extend their implementations accordingly."  =

> It would be very nice if the text included the sections where the
> appropriate extensions are mentioned/defined =E2=80=94 presumably these=

> extensions are how RFC4861 is Updated.

IMHO it isn't really helpful to an implementer to specify detailed textua=
l
updates to 4861, since we are adding new behaviour. The way it affects
each implementation will be different, especially depending on whether
or not they already support Rule 5.5 and if so, how they chose to represe=
nt
and store the relevant state.

> 2.2. Same text=E2=80=A6  "This specification is fully consistent with [=
RFC6724]
> and implementers will need to add support for its Rule 5.5."  It may no=
t
> be apparent (at this point in the text) to everyone that 5.5 applies to=

> the case where information related to which next-hop advertised which
> prefix (or that the document is going in that direction) -- please
> include a reference to section 3.3.

OK for me.

>=20
> 3. In Section 3.1. (Interpreting Router Advertisements), "=E2=80=A6Bob-=
A and one
> had advertised itself as a default router or as having a route to Alice=
,
> that is the router Bob should choose.  If none of Bob-A have advertised=

> that but Bob-B has, it is irrelevant; Bob is using the address allocate=
d
> in PA and courts a BCP 38 discard if he doesn't send the packet to
> Bob-A."  I think this case is irrelevant too, but not because Bob
> knows/thinks about BCP 38 =E2=80=94 it is irrelevant because of Rule 5.=
5 in
> rfc6724 (if I'm reading the order of the rules correctly).  Please
> clarify.

But only if Bob already implements Rule 5.5, which many of today's Bob's
don't. Maybe we need to mention that.

Regards
    Brian


From nobody Tue Aug  2 13:29:09 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D20512D0E9; Tue,  2 Aug 2016 13:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 e8Zh47IhhksP; Tue,  2 Aug 2016 13:29:07 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (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 8A0B712B010; Tue,  2 Aug 2016 13:29:07 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id pp5so66410923pac.3; Tue, 02 Aug 2016 13:29:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=9uxX4DfYVpmuEw+uZBwmDeY4q13B2LmzmEI0eo1gKqI=; b=nSbs7MAgylvayo58wbc+r5rtWWu+0D6SSGLNRTImGiYIaeArNJYSFC4QvdfC+DFDmy 4SXsdJXZZlAzTJXHKqnwtSu4DpZeqWgYigMxWsT/svg0QkMqYcNZX3ZhK8VlWqCi1D/Z DR5ixnKWEfmAuLaDN8751YO+fabtST1wboW1pSqu+zA99C9jku4wKsEHz7GH8lu6/bzf gErtCBDLU5UYpLx1QsMvU8gfqn75KaF5RGDmRWXjRIGcTIWCdkiipNU8VL0Co3do3e7l 3aCp4cNXilnPUZGDtBCGS4pG/hrZnfGDY+n76edW1IJKEZdpLcLB+kF2o9dpbBgxqJUV mY5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=9uxX4DfYVpmuEw+uZBwmDeY4q13B2LmzmEI0eo1gKqI=; b=dMpZOfupag8QRdLSt54aDrS8q96PY87MNgrucjbq/WJNmT0SBjT5Vu0Qbmer2Tuiew Cow1fwD9OexKHZetiTrhq4OrUA3TuMrdFuw73xVutEd6ydbhqyp1csc9MbU+jGEaKwbd Cw7N7tUXt9Q88TBFhHDwxPSzVapywh47MHGufztl+ISZPawqW7Nj9AmFIzQDchtc1jnu oSSk1eAz4VlAjhxBGuuCrpav9GDhuqpm/9/69EhYxFvdjE4ril/RrLc22kTTp9i8dOGf 7V4owYjezNzjr4YPvWrLrfYDc061RBTCswS82oSQcMf1AUkgYzgF7iwh96gyS+JcOLbs 5pYg==
X-Gm-Message-State: AEkoouuyrciwvR1krSz4K8TBGndSI4Bm7psAznpeTxjQEXWiE9I5pEyhFZgkqHl8UfWZlA==
X-Received: by 10.66.72.106 with SMTP id c10mr24585058pav.18.1470169746897; Tue, 02 Aug 2016 13:29:06 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.250]) by smtp.gmail.com with ESMTPSA id i62sm6860092pfg.62.2016.08.02.13.29.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 13:29:06 -0700 (PDT)
Subject: Re: Stephen Farrell's No Objection on draft-ietf-6man-multi-homed-host-07: (with COMMENT)
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
References: <20160802172111.27938.62324.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <e780b01d-f52f-55d5-4f3d-7f8149417a06@gmail.com>
Date: Wed, 3 Aug 2016 08:29:06 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160802172111.27938.62324.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vdSJk_6aN18HQdW6iYhhvHIExlM>
Cc: draft-ietf-6man-multi-homed-host@ietf.org, ipv6@ietf.org, jounikor@gmail.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 20:29:08 -0000

On 03/08/2016 05:21, Stephen Farrell wrote:
....
> general: I think this is very verbose, an editing pass
> to remove as many words as possible would be good, some
> examples below where I think more words confused me more
> than was needed...

iirc we added words because the WG feedback was that originally
we were too terse in some areas. One cannot win ;-).

> - Abstract: is bcp38 really crucial here or advisory?

We're covering an issue that mainly arises in cases where
BCP38 filters are present. So it's neither crucial nor advisory;
it's an assumption.

> If
> the latter, then I'd suggest not making it sound like it
> is necessary, no matter how much we'd like it deployed.
> 
> - intro: "the only consistent solution" may be an
> overstatement (unless you can prove there is no other)

I'd buy s/only consistent/only known consistent/. I've been
worriting about IPv6 multihoming for years and I certainly
can't think of any solution except SADR. But it's hard to
prove.

> 
> - text on p4 after figure 1: it's probably me but I
> found reading this a slog, not sure if it's really
> needed, but if (part of) it is, making the necessary
> bits clearer would seem like a fine plan. If it's not
> needed, maybe delete some or all of it.

This is a specific case where the WG asked for more words.

> - 2.1: When you say SLAAC here, are you encompassing use
> of privacy addresses? Sometimes those are presented as
> an alternative to SLAAC but I'm not sure which is the
> more correct terminology. In any case, I assume this
> document is intended to fully work with privacy
> addresses.

SLAAC uses whatever interface identifier the host comes
up with - MAC-based, RFC4941-based (privacy), RFC7217-based
(pseudorandom), or manually configured small integers...

Regards
   Brian


From nobody Tue Aug  2 16:51:00 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1052D12B027 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 16:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UmzbygXUfqCz for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 16:50:58 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 850F812B015 for <ipv6@ietf.org>; Tue,  2 Aug 2016 16:50:58 -0700 (PDT)
Received: by mail-pa0-x231.google.com with SMTP id pp5so67687462pac.3 for <ipv6@ietf.org>; Tue, 02 Aug 2016 16:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=tEil2+cJUh6Ls/RyOF2P/mckPzuC4GslL+pO5BUfn8M=; b=dh9nxyWOEMerTzcQjWLREieTai8D7akF3ZrbcqrUiX2L4o74xh3Xs9V3Hh2s2zVMhE 70tv7UEZJwdJjUU+HgXT+hpVDl3TgooZVT/v5RyIT8sdoBKVfRL+0zXGmmaTZH3Yb2oV 3sV7AgD4m4eiCC9czExwoZ4wJQkKRg/Yy6UTloFbc/GMBHlCpN/scP6mzo2MAbs20rDw RKTivvw2/gbgAoM1LNsQ4349llkgkGecOIi2bN98V1pTcBxp0+mPkUO9jcu9uIp0G9tk GCsjCHGpTfwtyGkYQcD6J0Iz11+z0uJY9RgE9NOQ5KpmVCCzzz4AaH6El+MWCZKY3ZiO Wjqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-transfer-encoding; bh=tEil2+cJUh6Ls/RyOF2P/mckPzuC4GslL+pO5BUfn8M=; b=BNAO7TGHoSfneZQw3niadMM00cxtlprYgTEWb1htuAqcQrJEfm8Lk0nrs+P+GtVK5S lCv5l7njaSdgfgsSTvczESC0Yb+Y+B6MKxiuTxU4WvThfo7goRhaB+mWyG3mCXJKXzFJ dBLZ/S3Hr+fl6lgaYUfCdsTm3eVzBR0wH6pphSe68ec1htyY8I4bu5LjzZqZsti1ORsP XB1zugPhtgwDiTYZXKVpzgT/9Z6raYpHI2+gEMwwb6Mbq/YjvdKYlBfi7TRQ93AqLrz6 YAI21WOvXBtqFlM2TQXc4NZ9CUVlcEJRivz80DxIlAD4HUqMSuK4ojl5xdKU64ICKGT7 5ghg==
X-Gm-Message-State: AEkoouv44dxv/NdtnZnfJ5kGO3hTXNK8AufzMgsp4QHPx6gBIfKgYYhBxq/vAjsiSdG8Qg==
X-Received: by 10.66.157.40 with SMTP id wj8mr109450422pab.53.1470181857865; Tue, 02 Aug 2016 16:50:57 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.250]) by smtp.gmail.com with ESMTPSA id p75sm7336867pfa.71.2016.08.02.16.50.56 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 16:50:57 -0700 (PDT)
To: 6man <ipv6@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Status of RFC 2473?
Organization: University of Auckland
Message-ID: <9b72e639-593f-1993-0fa5-d93d89a2f21f@gmail.com>
Date: Wed, 3 Aug 2016 11:50:59 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Mu8VLLKEDQBZXy5rV3p9PIXrbBw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2016 23:51:00 -0000

Hi,

Some discussion about ECN through tunnels over in TSVWG drew my attention
to RFC 2473, which to be honest I had completely forgotten about. Often
when people want a generic reference to IPv6 tunnels they cite RFC 4213.

So here's my question. Is RFC 2473 still valid and useful? There are
things it definitely doesn't cover in an up to date way: ECN, DSCP,
and flow label for example.

Did anyone ever implement the Tunnel Encapsulation Limit option?

Quite a lot of RFCs cite RFC 2473 (see http://www.fenron.com/~fenner/ietf/deps/index.cgi).

Regards
   Brian

P.S. Another question is whether we should be reviewing the validity of every
other IPv6-related RFC. If we get the main documents to Internet Standard,
obsoleting out-of-date documents should also be on the radar.


From nobody Tue Aug  2 19:01:50 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB92D12D123 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 19:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 10pF8RuLQxkJ for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 19:01:46 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (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 8C71E12B012 for <ipv6@ietf.org>; Tue,  2 Aug 2016 19:01:46 -0700 (PDT)
Received: by mail-pa0-x236.google.com with SMTP id fi15so68741638pac.1 for <ipv6@ietf.org>; Tue, 02 Aug 2016 19:01:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ywpwXpQ/2RUF9xQxpvJ/0B0nEvpcfN7/OGgD/HVA2WM=; b=LSHqKdjVBy3WYBkOeHUyXixrwBKcMjtAry0CnALSRwzPrkNZCc2rrUmCyyoSsW8EFm txx0P+Jz40w1BFXUYlyJwXDzY0bg4TakM0K0v1/6FKDyrz5KKIlj0Kl1XyfaekNoktKK p8knG+RydNKP4UHw/WvyJRcQB2ZQtUrhB6plzutMebgYgUuL6LxqlD0DyCNN/v9Gddh3 aG3vzcS3ATBSmtgB0PU40dftGw60YgDEjQP774GmyKnzrN1GZAOxHSDEbA2nFWrBOOK2 KtyEjZ9Zot5k9VwTumL7W9Nn/wEiF/3gcnA1q/KUbBnwHWIfJgLZo5BmyRjCzov2eYT0 AvuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ywpwXpQ/2RUF9xQxpvJ/0B0nEvpcfN7/OGgD/HVA2WM=; b=a7ScpbM5PZwpL11Urif2ANH1VLWBmORD3wcpTErHrS5YQO0n+CUH29l+pMG6q1YRQ5 lceO/HiuuR+sC19GCUq9ivUwuvJ3SNhOix8Zy989GHRHiWB9/keLG5es/BHGKTaSTbtP yTrDqKv9exNGKJU+4St5Rjw6ScNtKN2oZPiUel2k/lxeKLY8pNjZ4i2MUMT+wwN1aFfT PnIm9EcRMwnL7LZJvmROokTC1xxZsV8o3sibQ+k9F5fHyUnJ49rCbvtouV3zrHzDTXTS ZxkZCZ0P2AkjPIfosn10ukwVWZuXPCU94P5sbeKumFJHDKnuIbNpauWpHbEo/iFBclS7 uvEg==
X-Gm-Message-State: AEkoouuCva1RAVAsXZ7/wP7iOdx2IJSCPEMzsZagJ1l+eYfNrY98UZ6Il60r0bCcgkLIhA==
X-Received: by 10.66.171.197 with SMTP id aw5mr110921131pac.36.1470189706053;  Tue, 02 Aug 2016 19:01:46 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.250]) by smtp.gmail.com with ESMTPSA id y3sm7683648pfd.65.2016.08.02.19.01.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Aug 2016 19:01:45 -0700 (PDT)
Subject: Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d12a524a-d850-7834-bf01-dec9bb95069f@gmail.com>
Date: Wed, 3 Aug 2016 14:01:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ryBKeXU1Njqp8mlmikZycqUHPbg>
Cc: 6man-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 02:01:49 -0000

On 03/08/2016 02:48, otroan@employees.org wrote:
> All,
>=20
> There is one remaining issue we need resolved before we can advance thi=
s document.
> It is the issue of how the document shall update other documents.
> Alissa has enumerated the 3 options we see below.
>=20
> In the room there was support for option 1. Bernie proposed option 3 la=
ter on the list, as a possible compromise between 1 and 2.
>=20
> This starts a one week call on confirming consensus for option 1 (Remov=
e section 6). The call last until August 9th.

On balance, I concur. However, I would like to thank the authors for the =
hard work
involved in creating Section 6, and suggest that it should be kept somewh=
ere for
reference when the relevant documents are updated. (For example, a page a=
t
https://tools.ietf.org/wg/6man/trac/wiki .)

Don't forget to remove the last sentence of section 3.

BTW, while editing, I suggest rewording the IANA considerations to say on=
ly
"This document makes no request to IANA." It's an RFC Editor decision whe=
ther to
remove the IANA Considerations.

   Brian



>=20
> If you disagree with that choice, please state your objections to the l=
ist.
>=20
> Best regards,
> Ole
>=20
> =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D
>=20
> Under this option, the recommendations in Section 3 would apply to all =
of the IP-over-foo documents listed in the document header. But, for node=
s that do not follow these recommendations, the IP-over-foo documents wou=
ld still contain their current text explaining how to construct an EUI-64=
 for an IID.
>=20
>=20
> =3D=3D=3D Option 2: Keep Section 6 but add a sentence pointing to 4291b=
is =3D=3D=3D
>=20
> Each of the updates listed in Section 6 could be modified to add someth=
ing along the lines of the last sentence here:
>=20
>    The entire text of Section 4 of [RFC2464] is replaced with the
>    following text:
>=20
>    ---------------- cut here -------------- cut here ----------------
>    The Interface Identifier [AARCH] for an Ethernet interface SHOULD
>    be generated as specified in [RFC7217]. Embedding a stable
>    link-layer address in the IID is NOT RECOMMENDED [RFCXXXX].
>    [I-D.6man-rfc4291bis] Appendix A discusses approaches to IID creatio=
n
>    for nodes that choose not to follow this guidance.
>    ---------------- cut here -------------- cut here ----------------
>=20
>=20
> =3D=3D=3D Option 3: Remove Section 6 but add a list of IP-over-foo docu=
ment section updates =3D=3D=3D
>=20
> Per Bernie=E2=80=99s suggestion, we could remove Section 6 and update S=
ection 3 as follows:
>=20
> OLD
>    By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed a stable link-layer address in the IID.  In particular,
>    this document RECOMMENDS that nodes do not generate stable IIDs with=

>    the schemes specified in [RFC2464], [RFC2467], [RFC2470], [RFC2491],=

>    [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572], [RFC4338],
>    [RFC4391], [RFC5121], and [RFC5072].  The specific updates to these
>    documents to effectuate this recommendation are included in
>    Section 6.
>=20
> NEW
>    By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed a stable link-layer address in the IID.
>=20
>    The recommendations in this Section apply to:
>=20
>    Section 4 of [RFC2464]
>    Section 6 of [RFC2464]
>    Section 5 of [RFC2467]
>    Section 7 of [RFC2467]
>    Section 4 of [RFC2470]
>    Section 6 of [RFC2470]
>    Section 5.1 of [RFC2491]
>    Section 5.1.1 of [RFC2491]
>    Section 5.1.2 of [RFC2491]
>    Section 5 of [RFC2492]
>    Section 4 of [RFC2497]
>    Section 8 of [RFC2497]
>    Section 4 of [RFC2590]
>    Section 4.1 of [RFC2590]
>    Section 9 of [RFC2590]
>    Section 6 of [RFC3146]
>    Section 11 of [RFC3315] // modulo separate discussion about 3315bis
>    Section 3 of [RFC3572]
>    Section 6.2 of [RFC3572]
>    Section 2.5.1 of [RFC4291] // modulo separate discussion about 4291b=
is
>    Section 5 of [RFC4338]
>    Section 8 of [RFC4391]
>    Section 4.1 of [RFC5072]
>    Section 5 of [RFC5072]
>    Section 9.1 of [RFC5121]
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Tue Aug  2 20:02:20 2016
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2CFC12D626 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 20:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.987
X-Spam-Level: 
X-Spam-Status: No, score=-3.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 yLiy5eMNQjH5 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 20:02:17 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 CFABC12D1B2 for <ipv6@ietf.org>; Tue,  2 Aug 2016 20:02:16 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id j124so222011413ith.1 for <ipv6@ietf.org>; Tue, 02 Aug 2016 20:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7IqZPi4GddRrQ04OKCcudwgeeZFsMWQtc+riI1+yn6I=; b=IufaSwhycRbY3/JUoRxJ/6Z5Z/OQ4vV7AFYmxOaCWHsHlQWTssCaHoTsXn1itH1s8B ZaWp4eLwJc4jt+mG30645z7Wou+h9QSkeMp+rzSqazLY5gJwr8uS24aRq9pqMBojNSJU ET/wjGMQzwyb2R1PspjzQXagW1tR2ifnpX86n6Um3Lsl/aLcZit1tcKzW66l7NKUZL5G PxcoHG8A31fb1vcaEfBJx9+mxXG5Me41HKzeAGfoJ4TXwfnBFUvftWnsuHdkd4j/ACtc 5eFHSMplU3UCUoHVtu+VrcYofHpvAnwTwLc1wiT/fA7QbEl63Dh5i8y8pD0wH4dHBHh+ 03+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7IqZPi4GddRrQ04OKCcudwgeeZFsMWQtc+riI1+yn6I=; b=MFMOm5Rwd8YRG8OtrMnw8nsxmDKH4wPb6QBwWbNo6Mfx5QlJYVX5BZhuqkrAYj1j+/ KN67+jtbHSGV5gi4Ww+D7AVgq8j4ogh2JlFVRW0Ml/u/csHIeSYQeImvDFidj9ykgkMf NRWh5DeiNmLKWOAIXjRKSGfnvfWqrSMgrnJldt5VR4NhG5CXUR/IINHAMKQc3hYdzrRl gAww4XUucrOBjYQuoglz6tULxF6Gb0ayFjyqV+LshdBY499XamRa0P6LzwYYmgsgsqcA NtRku7gPlRuUigQw1emNH1jJXGUC9+VFvOL2Ls3OmSdtWdgdD02sZIkrASZmkmhlipMd RA7Q==
X-Gm-Message-State: AEkoouvylgGL6nz/fzw/yeogAlhFDko0qi5bYUiIP0z4kSDaSImIxqx1vv6tSRAJR2604Hu/Hi7ieuDmP5msc9Ey
X-Received: by 10.36.103.214 with SMTP id u205mr22978534itc.88.1470193335918;  Tue, 02 Aug 2016 20:02:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.26.72 with HTTP; Tue, 2 Aug 2016 20:01:55 -0700 (PDT)
In-Reply-To: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 3 Aug 2016 12:01:55 +0900
Message-ID: <CAKD1Yr00-W8B5m2yuObhqc0fTwuN6BGaMoLTN+gcjrmGbM=H+Q@mail.gmail.com>
Subject: Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114aa8d08a5de90539220fcc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/GvgV24Knh8GAaz2wBMwwamRdgQM>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 03:02:18 -0000

--001a114aa8d08a5de90539220fcc
Content-Type: text/plain; charset=UTF-8

On Tue, Aug 2, 2016 at 11:48 PM, <otroan@employees.org> wrote:

> This starts a one week call on confirming consensus for option 1 (Remove
> section 6). The call last until August 9th.
>

I agree that removing section 6 is the best option. It makes the document
much more focused and easy to understand.

I think the dhcp working group had concerns about section 4 as well.

--001a114aa8d08a5de90539220fcc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Aug 2, 2016 at 11:48 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otroa=
n@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">This starts a one week call on confirm=
ing consensus for option 1 (Remove section 6). The call last until August 9=
th.<br></blockquote><div><br></div><div>I agree that removing section 6 is =
the best option. It makes the document much more focused and easy to unders=
tand.</div><div><br></div><div>I think the dhcp working group had concerns =
about section 4 as well.</div></div></div></div>

--001a114aa8d08a5de90539220fcc--


From nobody Tue Aug  2 23:57:48 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41AC112D095 for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 23:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 1sQU006Mci_F for <ipv6@ietfa.amsl.com>; Tue,  2 Aug 2016 23:57:45 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B420012B020 for <ipv6@ietf.org>; Tue,  2 Aug 2016 23:57:43 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Aug 2016 06:57:41 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id C952D9CC81; Tue,  2 Aug 2016 23:57:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=JnJagbCiEl63/187+6+fd6uRSGI=; b= MiFne3H2JpY8WgpialLwB6N1BuKztXI2rE10+/So7/7Rt9qSA0FS0OTj2SB9/0oA tKb4X7dN4JQNN8DAHXSP8/kJ8r0Md9a4ss2AbrUOrAKQLgz/ut88FAuIFPm4/Ica zanv6WGZVrSEPpW5dt8hPnMB64ou1yxMLPjTkGP2w4w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=tGUDsDXyz3a5pZYdwg+roUTXC4 rRac4i/DFR4wUw7iosv+H0Wf2+ODXdcLVbfym9IifCjfC8lyBihP4zXztjGETXNm OEK+gJdfO+QxBQlWyZJI74lp9frPzk/gxoCDH2i7vtxEXf3dbsvj3Kj0u80DeLtH 1dcDEcjZ6wfWOm4LE=
Received: from h.hanazo.no (unknown [173.38.220.47]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 934A79CC7C; Tue,  2 Aug 2016 23:57:40 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B02652F7068D; Wed,  3 Aug 2016 08:57:41 +0200 (CEST)
Subject: Re: Status of RFC 2473?
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E06A6DB2-34C6-48D9-AA37-03008487BD95"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <9b72e639-593f-1993-0fa5-d93d89a2f21f@gmail.com>
Date: Wed, 3 Aug 2016 08:57:41 +0200
Message-Id: <C330963F-8AEE-4E05-8E8A-3F57B0A36329@employees.org>
References: <9b72e639-593f-1993-0fa5-d93d89a2f21f@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/dV4hKvA4yE-IeFrJJ3l9-C0Q1ZE>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 06:57:47 -0000

--Apple-Mail=_E06A6DB2-34C6-48D9-AA37-03008487BD95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

> Some discussion about ECN through tunnels over in TSVWG drew my =
attention
> to RFC 2473, which to be honest I had completely forgotten about. =
Often
> when people want a generic reference to IPv6 tunnels they cite RFC =
4213.
>=20
> So here's my question. Is RFC 2473 still valid and useful? There are
> things it definitely doesn't cover in an up to date way: ECN, DSCP,
> and flow label for example.

It definitely is. It is the fundament for all these recent IPv4 over =
IPv6 tunnel RFCs out of softwires.

> Did anyone ever implement the Tunnel Encapsulation Limit option?

Nope.

> Quite a lot of RFCs cite RFC 2473 (see =
http://www.fenron.com/~fenner/ietf/deps/index.cgi).

or
http://www.arkko.com/tools/allstats/citations-rfc2473.html

> P.S. Another question is whether we should be reviewing the validity =
of every
> other IPv6-related RFC. If we get the main documents to Internet =
Standard,
> obsoleting out-of-date documents should also be on the radar.

Regards,
Ole


--Apple-Mail=_E06A6DB2-34C6-48D9-AA37-03008487BD95
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXoZXlAAoJED4aXnjSQuKWhG4IAIDQaZigttnwn2XfctH1lo98
t0LUgvJL6q+kMWnVcWo+xgrrA7I/ZeCbRiUk2DmSWWgZ1IhaSEqKxJGNnC2ZBP44
6Txi+Sb9LvHlMqYXHG3uX39lUKjTj32vRmnyiKFwTIm/tc3UfmWnGyLHNTzXhDn+
frD2c/y5OBzZTdmSgXhRXTefCbi/inRRDxgeD6MIDgr57QewK8kmhfvaJ4aWFNyc
oLY+Lf+DDi/PbkY1epV1bvGzyqSMztujgL8ZiumexvVutyUuKADl6wyydEa4INF9
YZJGsHkmeWhnMCKrd+BGhKcOMEB6qQhhtC9oS/koc0j1OPB6BiD+OIMLr3rMcLw=
=ZTJu
-----END PGP SIGNATURE-----

--Apple-Mail=_E06A6DB2-34C6-48D9-AA37-03008487BD95--


From nobody Wed Aug  3 08:52:40 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340B812DD40 for <ipv6@ietfa.amsl.com>; Wed,  3 Aug 2016 08:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 weHI8ZOm9ReH for <ipv6@ietfa.amsl.com>; Wed,  3 Aug 2016 08:52:33 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 63F5812DC9C for <ipv6@ietf.org>; Wed,  3 Aug 2016 08:51:00 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id x25so145882938qtx.2 for <ipv6@ietf.org>; Wed, 03 Aug 2016 08:51:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=I5r9jQNjpt8CV3JS/P7CTcfbsy/waEBi2yuwkyS838A=; b=N9HixREjVcR7SAAsCisoMcq47XQdRvuAxKVX/+PbtTpJQY+toLQX5AAeiXgIa5etG+ 445CjrrlGWQuekk0jHcseX607cmOh2BUjT5NegID5GhAG3VKQpyUjJy1V+8pQbCFktGy Vdyn6sW1V3cjKO1CtcxwZDsDPpr126AQI+Up8OuFqrZgbM2DO8Uc/C25IKCyHFT528eK A4XpZ43DPHVmdgiqqQcim/3sl72CpoKWCzmsfXCtYeYCVhnf9NhojBn7fyvrDzjp/lbz MKH6GeavF4KgU6sLe428nAz6R8nSGqxb6rAMFiK7q8ADNLP8kpO7zTI6YB+nl4Oj/bO5 n2sQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=I5r9jQNjpt8CV3JS/P7CTcfbsy/waEBi2yuwkyS838A=; b=lkdtpKdp3u2yYqr0iEInkNFD97+3J2bGMmsiygWUPKAQFcMBLPiHGinTp93L8lGGg9 0TkKkT06TWDEyXJx8MydMGSZfAFu3F5bKdCqu0NPyyNBF/JQghfR4A1a5XGvdH1z+pKN nC5YBgYUqZyEWbK1eE57ohSG5KoDg2+KnKLwCuDWXndGKRBxmdR2i1dF4B7CK0XvsbEL BI7Hf5MoIwtIrVGYiZFq1chwyK6AlCpEwrIiTESHU0d6u5+qlOFOEG6BxMRMN3gmQRSp zcdRvTKGb1WtU7gIstNLT68Y1U4wRbVcrusMtJEiftnd0T50h6qff+QHEMAvlAOHwNgx p0Uw==
X-Gm-Message-State: AEkoouvIv6z9KshLCIHJ3vV/FObyvnAFxYk64L+v2HxTu0gBDGh5ExjvUxut36TROJydGwEkDo5Aq3XbNzZYkw==
X-Received: by 10.237.49.130 with SMTP id 2mr690360qth.38.1470239459547; Wed, 03 Aug 2016 08:50:59 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Wed, 3 Aug 2016 08:50:58 -0700 (PDT)
In-Reply-To: <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Wed, 3 Aug 2016 08:50:58 -0700
X-Google-Sender-Auth: Yk62XS4BGmXdKdTYXJ-sDrlLhhg
Message-ID: <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com>
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/g9Jo0CyTzy6AtxckD7txIY0S1EQ>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 15:52:39 -0000

At Tue, 2 Aug 2016 10:39:38 -0700,
Alissa Cooper <alissa@cooperw.in> wrote:

> >> There is one remaining issue we need resolved before we can advance th=
is document.
> >> It is the issue of how the document shall update other documents.
> >> Alissa has enumerated the 3 options we see below.
> >>
> >> In the room there was support for option 1. Bernie proposed option 3 l=
ater on the list, as a possible compromise between 1 and 2.
> >>
> >> This starts a one week call on confirming consensus for option 1
> >> (Remove section 6). The call last until August 9th.
> >
> >> =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D
> >>
> >> Under this option, the recommendations in Section 3 would apply to
> >> all of the IP-over-foo documents listed in the document header. But,
> >> for nodes that do not follow these recommendations, the IP-over-foo
> >> documents would still contain their current text explaining how to
> >> construct an EUI-64 for an IID.
> >
> > This may be not in the scope of this call, but in this case are we
> > also going to update Section 3 so it will be clearer that it's okay to
> > not follow the recommendations of this document (assuming that's the
> > consensus)?  In its current form that's not clear to me, especially
> > because of wording like "the default scheme=E2=80=9D.
>
> Could you explain precisely what you find unclear? The sentence to which =
you refer says
>
> "Nodes SHOULD implement and employ [RFC7217 <https://tools.ietf.org/html/=
rfc7217>] as the default scheme for generating stable IPv6 addresses with S=
LAAC.=E2=80=9D

What's unclear to me is that whether this ("SHOULD xxx by default")
applies to any IPv6 nodes or nodes "that follow the recommendation of
this document".  This description of "Option 1" seems to suggest the
latter:

> >> [...] But,
> >> for nodes that do not follow these recommendations, the IP-over-foo
> >> documents would still contain their current text explaining how to
> >> construct an EUI-64 for an IID.

but the current draft text could read as if it means the former.  To
make it crystal clear, I'd describe the "nodes" more precisely, e.g.:

   Nodes that need to generate stable IPv6 addresses with SLAAC but
   want to avoid privacy matters SHOULD implement and employ [RFC7217]
   as the default scheme for generating these IPv6 addresses.

--
JINMEI, Tatuya


From nobody Thu Aug  4 13:23:23 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5761B12D5A9; Thu,  4 Aug 2016 13:23:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=IbCtuJaE; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=rgmu8KmE
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 xdqXFySyac8j; Thu,  4 Aug 2016 13:23:20 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81FB912D6AE; Thu,  4 Aug 2016 13:23:19 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4BD7020335; Thu,  4 Aug 2016 16:23:18 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 04 Aug 2016 16:23:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=/93+avcmbqMjuLGFvIl40ev2GRA=; b=IbCtuJ aEYvaM4jjszVCjsLOAYziY7TRWWEen21rzbjuazOnEDY92XeFn4KDrIJg2yPTGcW guPc6IMaxrmcP4DyZaDnQAcPXREkxz7Xw0nQiOIEr5oy0xfs39EdSl8Ge6nxtvmJ IuTa5DN3/ZcPNvzjEV8Fxzj7lPRhFaPwL8njc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=/93+avcmbqMjuLG FvIl40ev2GRA=; b=rgmu8KmESSKzNKlgyBCEoxle+PYLoGLC2IL/ch0VMNZr+F9 igzlXCScfnYD7X+4gNBjcAsnQthjvUlG1W/Gy0zUNcVRpdtk5/86MeizJ9lqSWyz r6VNsKGLZ3iss+/N9d7NLDfhGUQS5VQ/C1DUAGbYNt8qBDrqEqh8wytLAUmg=
X-Sasl-enc: 4PIQZ2nl4/GyiygvtFrd55Nq019pldO6DNz9WLYvIWQk 1470342197
Received: from dhcp-171-68-21-29.cisco.com (dhcp-171-68-21-29.cisco.com [171.68.21.29]) by mail.messagingengine.com (Postfix) with ESMTPA id 72CEDF29D9; Thu,  4 Aug 2016 16:23:17 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <D3B605F6.31290%volz@cisco.com>
Date: Thu, 4 Aug 2016 13:23:16 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/l4ZRGPrsfN3WGCG7Qe-7JyQTlpA>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2016 20:23:22 -0000

> On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> 
> Ole:
> 
> (I fixed 6man mailing list address.)
> 
> That is probably the best solution and I would support that.
> 
> We can still discuss changing some of the text in 3315bis, but that can
> then be done without 6man involvement. (We do still have the older text in
> what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so should really
> clean that up.)

I am fine with this solution and it seems cleaner.

Alissa

> 
> - Bernie
> 
> 
> On 7/21/16, 4:45 AM, "otroan@employees.org" <otroan@employees.org> wrote:
> 
>> Bernie, et al,
>> 
>> The first line of the abstract says:
>>  "This document changes the recommended default IID generation scheme
>>  for cases where SLAAC is used to generate a stable IPv6 address."
>> 
>> I'm not convinced that we need to have the DHCP paragraph there at all.
>> Would that work for you?
>> 
>> Best regards,
>> Ole
>> 
>> 
>>> On 21 Jul 2016, at 10:30, Bernie Volz (volz) <volz@cisco.com> wrote:
>>> 
>>> Alissa, et al:
>>> 
>>> Based on a conversation between some of the draft-ietf-dhc-rfc3315bis
>>> coauthors and in the DHC WG session Wednesday (7/20) morning, we are not
>>> in favor of the replacement text as it currently stands. We will work
>>> something up and send it to you as soon as we can.
>>> 
>>> We are likely to simplify the replacement text to something like the
>>> following (but this is only my proposal and has not been reviewed by
>>> others):
>>> 
>>>    By default, DHCPv6 server implementations SHOULD NOT generate
>>>    predictable IPv6 addresses ([RFC7721]). DHCPv6 servers SHOULD
>>>    NOT assign addresses that use a reserved IPv6 Interface Identifier
>>>    ([RFC5453], [RFC7136], and [IANARESERVEDIID]).
>>> 
>>> We are tracking this issue at
>>> https://trac.tools.ietf.org/group/dhcpv6bis/ticket/166.
>>> 
>>> - Bernie
>>> _______________________________________________
>>> dhcwg mailing list
>>> dhcwg@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dhcwg
>> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From nobody Thu Aug  4 13:29:24 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88A7912D7A1 for <ipv6@ietfa.amsl.com>; Thu,  4 Aug 2016 13:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=gclhdTaj; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=kzzzDBIy
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 XPvFpfCBw_uu for <ipv6@ietfa.amsl.com>; Thu,  4 Aug 2016 13:29:20 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EF0412D768 for <ipv6@ietf.org>; Thu,  4 Aug 2016 13:29:20 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D9CC52047E; Thu,  4 Aug 2016 16:29:19 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 04 Aug 2016 16:29:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=x8TxBWEDs01j+EpGTFBrbTuxC0c=; b=gclhdT ajgFOdMvcbikrbdh6k46npFEP/p+xfeGlaI8+Uq9IWTuTgLAPM99ElM+3zp5xB8j bSg3NbH92QNRjMW2iYXiCGUnJx9E0AqoUjOKAJZ7bDsCmWkoMI2V9OgJG5zwxZWf AYwzB5Z8C9An8sCOaovtkUfqMLtOZi+W0gOHk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=x8TxBWEDs01j+Ep GTFBrbTuxC0c=; b=kzzzDBIyHD0xxROBM6Ige9WffsyxJF3IX1RRgtOKn7CE/Ro I57bgYYKRB+JSZH4eKeGUv7Qi/qrFy0XXOfi3CRsRykY7Xqhm2AhJjYKwXNKUL0J rbBuMS0AKFc81UOSHEFr9C+tBKkmPL6MVbOppEALn6sX3msUnTOV2ea2cT/0=
X-Sasl-enc: 3BqJk++bggK4QlQm8vMaRgrbNSW2o+LdAP3Ydbg3MhtX 1470342559
Received: from dhcp-171-68-21-29.cisco.com (dhcp-171-68-21-29.cisco.com [171.68.21.29]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F31AF29D9; Thu,  4 Aug 2016 16:29:19 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com>
Date: Thu, 4 Aug 2016 13:29:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/b1LecwT7XWtWdxeukH_wC5ZX5vg>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2016 20:29:23 -0000

Hi Jinmei,

> On Aug 3, 2016, at 8:50 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Tue, 2 Aug 2016 10:39:38 -0700,
> Alissa Cooper <alissa@cooperw.in> wrote:
>=20
>>=20
>> Could you explain precisely what you find unclear? The sentence to =
which you refer says
>>=20
>> "Nodes SHOULD implement and employ [RFC7217 =
<https://tools.ietf.org/html/rfc7217>] as the default scheme for =
generating stable IPv6 addresses with SLAAC.=E2=80=9D
>=20
> What's unclear to me is that whether this ("SHOULD xxx by default")
> applies to any IPv6 nodes or nodes "that follow the recommendation of
> this document=E2=80=9D. =20

The recommendation applies to all nodes. Since it is a SHOULD, some =
nodes may not follow it and they would still be compliant. And since the =
recommendation itself is about generating stable IPv6 addresses with =
SLAAC, it applies only when that is what nodes are aiming to do.

> This description of "Option 1" seems to suggest the
> latter:

The options have nothing to do with the extent to which the =
recommendation applies. The question about the options relates to what =
text will continue to be in place to describe what nodes might do if =
they do not follow the recommendation.

>=20
>>>> [...] But,
>>>> for nodes that do not follow these recommendations, the IP-over-foo
>>>> documents would still contain their current text explaining how to
>>>> construct an EUI-64 for an IID.
>=20
> but the current draft text could read as if it means the former.  To
> make it crystal clear, I'd describe the "nodes" more precisely, e.g.:
>=20
>   Nodes that need to generate stable IPv6 addresses with SLAAC but
>   want to avoid privacy matters SHOULD implement and employ [RFC7217]
>   as the default scheme for generating these IPv6 addresses.

I think this is much less clear than the text in the document currently. =
I do not know what =E2=80=9Cwant to avoid privacy matters=E2=80=9D =
means.

Best,
Alissa

>=20
> --
> JINMEI, Tatuya


From nobody Fri Aug  5 04:51:51 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60BB12D841 for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 04:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.561
X-Spam-Level: 
X-Spam-Status: No, score=-0.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, SPF_PASS=-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 5NSkrOESiSmy for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 04:51:47 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55A8012D828 for <ipv6@ietf.org>; Fri,  5 Aug 2016 04:51:46 -0700 (PDT)
Received: from [192.168.1.18] (unknown [84.47.113.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EE57F82BF9; Fri,  5 Aug 2016 13:51:37 +0200 (CEST)
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Alissa Cooper <alissa@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <ad534d9f-df25-d9e2-978d-5d8c9c9cdb38@si6networks.com>
Date: Thu, 4 Aug 2016 02:18:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Z8zyHaAMG6FOkFjLZznXHhoPYV4>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 11:51:50 -0000

On 08/03/2016 05:50 PM, 神明達哉 wrote:
>>>
>>>> === Option 1: Remove Section 6 ===
>>>>
>>>> Under this option, the recommendations in Section 3 would apply to
>>>> all of the IP-over-foo documents listed in the document header. But,
>>>> for nodes that do not follow these recommendations, the IP-over-foo
>>>> documents would still contain their current text explaining how to
>>>> construct an EUI-64 for an IID.
>>>
>>> This may be not in the scope of this call, but in this case are we
>>> also going to update Section 3 so it will be clearer that it's okay to
>>> not follow the recommendations of this document (assuming that's the
>>> consensus)?  In its current form that's not clear to me, especially
>>> because of wording like "the default scheme”.
>>
>> Could you explain precisely what you find unclear? The sentence to which you refer says
>>
>> "Nodes SHOULD implement and employ [RFC7217 <https://tools.ietf.org/html/rfc7217>] as the default scheme for generating stable IPv6 addresses with SLAAC.”
> 
> What's unclear to me is that whether this ("SHOULD xxx by default")
> applies to any IPv6 nodes or nodes "that follow the recommendation of
> this document". 


The recommendation applies to all nodes, at the "SHOULD" level.



>>>> [...] But,
>>>> for nodes that do not follow these recommendations, the IP-over-foo
>>>> documents would still contain their current text explaining how to
>>>> construct an EUI-64 for an IID.
> 
> but the current draft text could read as if it means the former.  To
> make it crystal clear, I'd describe the "nodes" more precisely, e.g.:
> 
>    Nodes that need to generate stable IPv6 addresses with SLAAC but
>    want to avoid privacy matters SHOULD implement and employ [RFC7217]
>    as the default scheme for generating these IPv6 addresses.

 think this text is totally different from what we've working on for
years. And given "pervasive monitoring" et al, something that improves
mod eui-64 must be done by default.

Put another way: if you're not concerned about security and privacy...
you should. :-)

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Aug  5 05:42:25 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE84C12D62D; Fri,  5 Aug 2016 05:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 P-WeztkHqsFq; Fri,  5 Aug 2016 05:42:18 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 497DB12D5A8; Fri,  5 Aug 2016 05:42:18 -0700 (PDT)
Received: from [192.168.1.18] (unknown [84.47.113.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 7556B82614; Fri,  5 Aug 2016 14:42:14 +0200 (CEST)
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
To: Alissa Cooper <alissa@cooperw.in>, "Bernie Volz (volz)" <volz@cisco.com>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com>
Date: Fri, 5 Aug 2016 14:41:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/7PZx0CYXDzVlb6wOKgrNP3CP9Qw>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 12:42:20 -0000

On 08/04/2016 10:23 PM, Alissa Cooper wrote:
> 
>> On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
>>
>> Ole:
>>
>> (I fixed 6man mailing list address.)
>>
>> That is probably the best solution and I would support that.
>>
>> We can still discuss changing some of the text in 3315bis, but that can
>> then be done without 6man involvement. (We do still have the older text in
>> what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so should really
>> clean that up.)
> 
> I am fine with this solution and it seems cleaner.

Background: At some point folks argued that this document should cover
SLAAC, DHCPv6, and manual configuration. And hence this text was added.

I don't mind removing the DHCPv6 text. However, if we do, we should
probably also remove the text about manual configuration. Otherwise it
is not clear why some forms of configuration are covered, but others are
not.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Aug  5 09:47:43 2016
Return-Path: <fbrockne@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB8612D909 for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 09:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Level: 
X-Spam-Status: No, score=-15.807 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 d_dlYYh7sNRL for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 09:47:40 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D49C12D169 for <ipv6@ietf.org>; Fri,  5 Aug 2016 09:47:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11592; q=dns/txt; s=iport; t=1470415660; x=1471625260; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xZ1O8sZNUQ1aWIOG9HPzDMXYbVNU2MGAET1bnJVRDmk=; b=dineTFY0cBsak19ymf8cnBtzbByfpFc6SyE5nCTbXK1Dmh+TN+OrCgB/ 1DhYThnO48VlM91amu71zjRVpkf09TasFZKR+8YF1ZacSTGysonCQa958 ntdB+jjkRonbbvocz7i5qCYgU7OG3M3c48RqUM1eLMCNXlBkH7sPOr1U9 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CRAgChwqRX/5ldJa1dgndOVnwHrHKHI?= =?us-ascii?q?YUHgX0khXkCHIEgOBQBAQEBAQEBXSeEXgEBBSMKTBACAQgRBAEBKAMCAgIfERQ?= =?us-ascii?q?JCAIEAQ0FCIgPAxcOrwSLQg2ENQEBAQEBAQEBAQEBAQEBAQEBAQEBARyGKoRNg?= =?us-ascii?q?kOCMwiCQ4JaBZkBNAGGHIYygjKBcoRbiHyILIQHg3YBHjaDem6GcX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,474,1464652800";  d="scan'208,217";a="307365531"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Aug 2016 16:47:39 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u75GldkT002316 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Aug 2016 16:47:39 GMT
Received: from xch-rcd-008.cisco.com (173.37.102.18) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 5 Aug 2016 11:47:38 -0500
Received: from xch-rcd-008.cisco.com ([173.37.102.18]) by XCH-RCD-008.cisco.com ([173.37.102.18]) with mapi id 15.00.1210.000; Fri, 5 Aug 2016 11:47:38 -0500
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: Hemant Singh <hemantietf@gmail.com>, "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
Subject: RE: Which use cases are using direct EH insertion?
Thread-Topic: Which use cases are using direct EH insertion?
Thread-Index: AQHR5yjAe1pqXPMgDESdzI8t57jxr6AresyAgAA4gYCAAF9ZgIAAf5yAgA4QpLA=
Date: Fri, 5 Aug 2016 16:47:38 +0000
Message-ID: <328702550f9d4b3bb492d19b37ba72b3@XCH-RCD-008.cisco.com>
References: <201607220911.u6M9Bco9077775@givry.fdupont.fr> <948512bb-c741-0509-8442-2d230c5bca49@gmail.com> <F63100FA-C083-4DFE-91ED-8BAE601135C9@employees.org> <b1214a88-937b-57cf-1558-27e5d7e58f6a@gmail.com> <A66B9E3A-7AF8-41F5-8E07-8EB8A464F16C@cisco.com> <C30B0322-23A3-443D-BDEF-60E35949DF9A@employees.org> <18213e8b-117a-a443-36fd-df96d56e14de@gmail.com> <m1bRySw-0000CuC@stereo.hq.phicoh.net> <D09E0D69-95DD-4046-8C04-6A4DF0BD25FC@jisc.ac.uk> <9dac3b40eb2e6fcf339da6fa1a44f9ad@petri-meat.com> <CABdyVt7wgLmdSh1714KH5Egu2JL7TWuCS577avSKFGTMhKG9gg@mail.gmail.com> <D3BE3FA2.38E919%shwethab@cisco.com> <CABdyVt7=_J4HO6K1NXNqKvVnmRTNG3foGorCKFno9HHxCes3FQ@mail.gmail.com>
In-Reply-To: <CABdyVt7=_J4HO6K1NXNqKvVnmRTNG3foGorCKFno9HHxCes3FQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.190.235]
Content-Type: multipart/alternative; boundary="_000_328702550f9d4b3bb492d19b37ba72b3XCHRCD008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0qx9IapgRXOB8-py3ojiMBqIJac>
Cc: "hannes@rtbrick.com" <hannes@rtbrick.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 16:47:42 -0000

--_000_328702550f9d4b3bb492d19b37ba72b3XCHRCD008ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGVtYW50LA0KDQpzb3JyeSBmb3IgdGhlIGRlbGF5IOKAkyBwbGVhc2Ugc2VlIGlubGluZeKApg0K
DQpGcm9tOiBIZW1hbnQgU2luZ2ggW21haWx0bzpoZW1hbnRpZXRmQGdtYWlsLmNvbV0NClNlbnQ6
IE1pdHR3b2NoLCAyNy4gSnVsaSAyMDE2IDE0OjU3DQpUbzogU2h3ZXRoYSBCaGFuZGFyaSAoc2h3
ZXRoYWIpIDxzaHdldGhhYkBjaXNjby5jb20+DQpDYzogRnJhbmsgQnJvY2tuZXJzIChmYnJvY2tu
ZSkgPGZicm9ja25lQGNpc2NvLmNvbT47IENhcmxvcyBQaWduYXRhcm8gKGNwaWduYXRhKSA8Y3Bp
Z25hdGFAY2lzY28uY29tPjsgaGFubmVzQHJ0YnJpY2suY29tOyA2bWFuIFdHIDxpcHY2QGlldGYu
b3JnPg0KU3ViamVjdDogUmU6IFdoaWNoIHVzZSBjYXNlcyBhcmUgdXNpbmcgZGlyZWN0IEVIIGlu
c2VydGlvbj8NCg0KSWYgc2VjdGlvbiAzLjEuMiByZWxhdGVkIHRvIGluZ3Jlc3MsIHdlIGhhdmUg
dGV4dCB0aGF0IHNheXMgImluc2VydGlvbiBvZiB0aGUgaW4tYmFuZCBPQU0gaGVhZGVyIGlzIGVu
YWJsZWQgYXQgdGhlIHJlcXVpcmVkIGVkZ2Ugbm9kZXMgYnkgbWVhbnMgb2YgY29uZmlndXJhdGlv
bi4iICBIb3dldmVyLCB0aGUgc2FtZSB0ZXh0IGRvZXMgbm90IGV4aXN0IGluIHRoZSBlZ3Jlc3Mg
c2VjdGlvbiBpbiAzLjEuNC4gIFdoeSBub3QgYWRkIGNvbW1vbiB0ZXh0IGZvciBpbmdyZXNzL2Vn
cmVzcyBiZWZvcmUgYW55IG9mIHRoZXNlIHR3byBzZWN0aW9ucyBzdGFydD8NCi4uLkZCOiBHcmVh
dCBzdWdnZXN0aW9uLiBXZeKAmWxsIGluY29ycG9ydGF0ZSBpdCBpbnRvIHRoZSBuZXh0IHJldmlz
aW9uLg0KDQpIb3cgZG9lcyBjbGFzc2lmaWNhdGlvbiBvZiBmbG93cyBzaWduYWwgdG8gdGhlIGVn
cmVzcyByb3V0ZXIgdG8gc3RyaXAgb3B0aW9ucz8NCi4uLkZCOiBSZW1vdmFsIGlzIGEgY29uZmln
dXJhdGlvbiBvcHRpb24uIEFuIGVncmVzcyBub2RlIHdpbGwgYmUgY29uZmlndXJlZCB0byBzdHJp
cCBpbi1iYW5kIE9BTSBpbmZvcm1hdGlvbiBmcm9tIGFsbCB0cmFmZmljLCBpLmUuIHRoZXJlIGlz
buKAmXQgYSBuZWVkIGZvciBzcGVjaWZpYyBmbG93IGNsYXNzaWZpY2F0aW9uIHVubGVzcyB5b3Ug
aGF2ZSBmbG93IHNwZWNpZmljIGZlYXR1cmVzIChlLmcuIHNlcXVlbmNlIG51bWJlcmluZyBmb3Ig
YSBzcGVjaWZpYyBzZXQgb2YgZmxvd3MpLg0KDQpSZWdhcmRzLCBGcmFuaw0KDQp0aGFua3MsDQoN
CkhlbWFudA0KDQpPbiBXZWQsIEp1bCAyNywgMjAxNiBhdCAxOjIwIEFNLCBTaHdldGhhIEJoYW5k
YXJpIChzaHdldGhhYikgPHNod2V0aGFiQGNpc2NvLmNvbTxtYWlsdG86c2h3ZXRoYWJAY2lzY28u
Y29tPj4gd3JvdGU6DQoNClRoZSBkZWNpc2lvbiB0byBhZGQvcmVtb3ZlIHRoZSBIYnlIIG9wdGlv
bnMvaGVhZGVyIGlzIGJhc2VkIG9uIGNsYXNzaWZpY2F0aW9uIG9mIGZsb3dzIGFuZC9vciBpbnRl
cmZhY2VzIGFzIGVudGVyaW5nL2xlYXZpbmcgdGhlIGRvbWFpbi4gSW4gb3VyIGN1cnJlbnQgaW1w
bGVtZW50YXRpb24gb2YgSW4tYmFuZCBPQU0gKGluIGZkLmlvPGh0dHBzOi8vZ2Vycml0LmZkLmlv
L3IvZ2l0d2ViP3A9dnBwLmdpdDthPXRyZWU+ICkgaXQgaXMgZG9uZSBieSBwdXNoaW5nIHRoaXMg
Y29uZmlndXJhdGlvbiBvbiB0aGUgZG9tYWluJ3MgcGVyaW1ldGVyIG5vZGVzLg0KDQoNCg==

--_000_328702550f9d4b3bb492d19b37ba72b3XCHRCD008ciscocom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1z
b25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCglt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3Np
emU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgMi4wY20gNzAuODVw
dDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBz
cGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIg
ZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4N
Cjxib2R5IGxhbmc9IkRFIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9
IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGVtYW50LDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPnNvcnJ5IGZvciB0aGUg
ZGVsYXkg4oCTIHBsZWFzZSBzZWUgaW5saW5l4oCmPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IEhlbWFudCBT
aW5naCBbbWFpbHRvOmhlbWFudGlldGZAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IE1p
dHR3b2NoLCAyNy4gSnVsaSAyMDE2IDE0OjU3PGJyPg0KPGI+VG86PC9iPiBTaHdldGhhIEJoYW5k
YXJpIChzaHdldGhhYikgJmx0O3Nod2V0aGFiQGNpc2NvLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+
IEZyYW5rIEJyb2NrbmVycyAoZmJyb2NrbmUpICZsdDtmYnJvY2tuZUBjaXNjby5jb20mZ3Q7OyBD
YXJsb3MgUGlnbmF0YXJvIChjcGlnbmF0YSkgJmx0O2NwaWduYXRhQGNpc2NvLmNvbSZndDs7IGhh
bm5lc0BydGJyaWNrLmNvbTsgNm1hbiBXRyAmbHQ7aXB2NkBpZXRmLm9yZyZndDs8YnI+DQo8Yj5T
dWJqZWN0OjwvYj4gUmU6IFdoaWNoIHVzZSBjYXNlcyBhcmUgdXNpbmcgZGlyZWN0IEVIIGluc2Vy
dGlvbj88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgc2Vj
dGlvbiAzLjEuMiByZWxhdGVkIHRvIGluZ3Jlc3MsIHdlIGhhdmUgdGV4dCB0aGF0IHNheXMgJnF1
b3Q7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Y29sb3I6YmxhY2siPmluc2VydGlvbiBv
ZiZuYnNwO3RoZSBpbi1iYW5kIE9BTSBoZWFkZXIgaXMgZW5hYmxlZCBhdCB0aGUgcmVxdWlyZWQg
ZWRnZSBub2RlcyBieSBtZWFucyZuYnNwO29mIGNvbmZpZ3VyYXRpb24uPC9zcGFuPiZxdW90OyAm
bmJzcDtIb3dldmVyLCB0aGUgc2FtZSB0ZXh0DQogZG9lcyBub3QgZXhpc3QgaW4gdGhlIGVncmVz
cyBzZWN0aW9uIGluIDMuMS40LiZuYnNwOyBXaHkgbm90IGFkZCBjb21tb24gdGV4dCBmb3IgaW5n
cmVzcy9lZ3Jlc3MgYmVmb3JlIGFueSBvZiB0aGVzZSB0d28gc2VjdGlvbnMgc3RhcnQ/PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0QiPi4uLkZCOiBHcmVhdCBzdWdnZXN0aW9uLiBXZeKAmWxsIGluY29y
cG9ydGF0ZSBpdCBpbnRvIHRoZSBuZXh0IHJldmlzaW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5Ib3cgZG9lcyBjbGFzc2lmaWNhdGlvbiBvZiBmbG93cyBzaWduYWwgdG8gdGhlIGVn
cmVzcyByb3V0ZXIgdG8gc3RyaXAgb3B0aW9ucz8NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj4u
Li5GQjogUmVtb3ZhbCBpcyBhIGNvbmZpZ3VyYXRpb24gb3B0aW9uLiBBbiBlZ3Jlc3Mgbm9kZSB3
aWxsIGJlIGNvbmZpZ3VyZWQgdG8gc3RyaXAgaW4tYmFuZCBPQU0gaW5mb3JtYXRpb24gZnJvbSBh
bGwgdHJhZmZpYywgaS5lLiB0aGVyZSBpc27igJl0IGENCiBuZWVkIGZvciBzcGVjaWZpYyBmbG93
IGNsYXNzaWZpY2F0aW9uIHVubGVzcyB5b3UgaGF2ZSBmbG93IHNwZWNpZmljIGZlYXR1cmVzIChl
LmcuIHNlcXVlbmNlIG51bWJlcmluZyBmb3IgYSBzcGVjaWZpYyBzZXQgb2YgZmxvd3MpLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEIj5SZWdhcmRzLCBGcmFuazxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj50aGFu
a3MsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkhlbWFudDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFdlZCwgSnVs
IDI3LCAyMDE2IGF0IDE6MjAgQU0sIFNod2V0aGEgQmhhbmRhcmkgKHNod2V0aGFiKSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnNod2V0aGFiQGNpc2NvLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnNod2V0aGFi
QGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJs
YWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPlRoZSBkZWNpc2lvbiB0
byBhZGQvcmVtb3ZlIHRoZSBIYnlIIG9wdGlvbnMvaGVhZGVyIGlzIGJhc2VkIG9uIGNsYXNzaWZp
Y2F0aW9uIG9mIGZsb3dzIGFuZC9vciBpbnRlcmZhY2VzIGFzIGVudGVyaW5nL2xlYXZpbmcgdGhl
IGRvbWFpbi4gSW4gb3VyIGN1cnJlbnQgaW1wbGVtZW50YXRpb24NCiBvZiBJbi1iYW5kIE9BTSAo
aW4gPGEgaHJlZj0iaHR0cHM6Ly9nZXJyaXQuZmQuaW8vci9naXR3ZWI/cD12cHAuZ2l0O2E9dHJl
ZSIgdGFyZ2V0PSJfYmxhbmsiPg0KZmQuaW88L2E+Jm5ic3A7KSBpdCBpcyBkb25lIGJ5IHB1c2hp
bmcgdGhpcyBjb25maWd1cmF0aW9uIG9uIHRoZSBkb21haW4ncyBwZXJpbWV0ZXIgbm9kZXMuPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_328702550f9d4b3bb492d19b37ba72b3XCHRCD008ciscocom_--


From nobody Fri Aug  5 18:00:15 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 694BC12D0D3 for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 18:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.026
X-Spam-Level: **
X-Spam-Status: No, score=2.026 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.626, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HBh-FLuTW9Wf for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 18:00:12 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 D963812B061 for <ipv6@ietf.org>; Fri,  5 Aug 2016 18:00:11 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id 35so209280645uap.1 for <ipv6@ietf.org>; Fri, 05 Aug 2016 18:00:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=f0YTbBS753ONbkpw/RIhRapVELx8s2TemTnaZxMf/U4=; b=MT5dknFqQd/fSSAG+I4Xo9FMe5hNws/wqhGdE5lUVbRF2WnkEJA5yom4V3YpPb1O1m rolMPJ/dQzCn/fadRQy/2PaAxWUnjD5RxflZS/EjLGazQP5zVPXRPsEn84g61iYWUkjd RdbBkjNP5Vigtxph1KM+40a5yet47C/oMZoaSbzQXejerx1cEQ9Q0kgP3WXwHgUG+eGH FWny94r0H1bHMsSlypX/QdVuI8CQUgoOrZKiZxv+9wYl52OfjizFnKogakML0IWqrMl+ L0cLQCswRpfwpkB9qncfr50/9S7/lKT45kW1648lBb9VIvSQJQm2XTAml4unNbyM7fXR WmhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=f0YTbBS753ONbkpw/RIhRapVELx8s2TemTnaZxMf/U4=; b=IxKJLB/KjOUiAPmB1Cd+tG43MSVEXmfnq3ELeIKlYqHEfG8mGpDG4pRiRE4mPgzh9q ZPg0ZGSRDlbgVozIrrkfn7pEHUhTM+F8UqWpZ17uwqS3XSW+wTiJzGd3CLO3SehXCELO v+HJpabrbJQaP2W0qQ+5IzNojvH1Tx3BZ+LCDRL2BvhAO7bnV3ElvooqvCrJtzV6UJah gk9sOVcmvn5sArOc/rW0GH0zOI1+c65Jlpobhg/FzJ5SsTixz6raAJeoUbLoL95K93bR iUpjGTEIOVSsPDVCtisDh58Gtwfzq/zzNXbXsvyecdx7bahWHmdezPYqVWQH/EtdsqVo 6TfQ==
X-Gm-Message-State: AEkoousFk8Mxaa9CMesXQBsq7He+Czd/sW5dCFEykKY4kBGWtrnYRvmOGaUh8q8GtfiPzAVMV3EgMAwmfZiLWQ==
X-Received: by 10.176.1.214 with SMTP id 80mr36586824ual.129.1470445210886; Fri, 05 Aug 2016 18:00:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.54.233 with HTTP; Fri, 5 Aug 2016 18:00:10 -0700 (PDT)
Received: by 10.159.54.233 with HTTP; Fri, 5 Aug 2016 18:00:10 -0700 (PDT)
In-Reply-To: <ad534d9f-df25-d9e2-978d-5d8c9c9cdb38@si6networks.com>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com> <ad534d9f-df25-d9e2-978d-5d8c9c9cdb38@si6networks.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 6 Aug 2016 11:00:10 +1000
Message-ID: <CAO42Z2wJCQE9NfZuQKE_HPRvLdPkFe+y0Fd12Givt6aeNMofhA@mail.gmail.com>
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113f029674e94805395cb41f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PISmJPKHYrtte6jDM330uZgySYo>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2016 01:00:13 -0000

--001a113f029674e94805395cb41f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 5 Aug 2016 21:52, "Fernando Gont" <fgont@si6networks.com> wrote:
>
> On 08/03/2016 05:50 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> >>>
> >>>> =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D
> >>>>
> >>>> Under this option, the recommendations in Section 3 would apply to
> >>>> all of the IP-over-foo documents listed in the document header. But,
> >>>> for nodes that do not follow these recommendations, the IP-over-foo
> >>>> documents would still contain their current text explaining how to
> >>>> construct an EUI-64 for an IID.
> >>>
> >>> This may be not in the scope of this call, but in this case are we
> >>> also going to update Section 3 so it will be clearer that it's okay t=
o
> >>> not follow the recommendations of this document (assuming that's the
> >>> consensus)?  In its current form that's not clear to me, especially
> >>> because of wording like "the default scheme=E2=80=9D.
> >>
> >> Could you explain precisely what you find unclear? The sentence to
which you refer says
> >>
> >> "Nodes SHOULD implement and employ [RFC7217 <
https://tools.ietf.org/html/rfc7217>] as the default scheme for generating
stable IPv6 addresses with SLAAC.=E2=80=9D
> >
> > What's unclear to me is that whether this ("SHOULD xxx by default")
> > applies to any IPv6 nodes or nodes "that follow the recommendation of
> > this document".
>
>
> The recommendation applies to all nodes, at the "SHOULD" level.
>
>
>
> >>>> [...] But,
> >>>> for nodes that do not follow these recommendations, the IP-over-foo
> >>>> documents would still contain their current text explaining how to
> >>>> construct an EUI-64 for an IID.
> >
> > but the current draft text could read as if it means the former.  To
> > make it crystal clear, I'd describe the "nodes" more precisely, e.g.:
> >
> >    Nodes that need to generate stable IPv6 addresses with SLAAC but
> >    want to avoid privacy matters SHOULD implement and employ [RFC7217]
> >    as the default scheme for generating these IPv6 addresses.
>
>  think this text is totally different from what we've working on for
> years. And given "pervasive monitoring" et al, something that improves
> mod eui-64 must be done by default.
>
> Put another way: if you're not concerned about security and privacy...
> you should. :-)
>

I think one thing to also remember is that the  privacy property of an
address is most important to the end user of the device rather than the
implementor of the device. Implementors aren't always, and I'd say aren't
in most cases by volume (think of a mass market vendor selling to
end-users), in the best position to judge the level of privacy required or
desired by the end user.

We don't want end user privacy reduced because doing so is more convenient
for an end-user privacy context unaware implementor.

Making RFC7217s the default is increasing the privacy of stable addresses.
If an implementor wants to go against this default, we want to make it
clear that they know they're making a privacy judgement on behalf of their
implementation's end-user and they need to be sure that they're meeting
their end-users' privacy requirements.

Regards,
Mark.

> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--001a113f029674e94805395cb41f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"></p>
<p dir=3D"ltr">On 5 Aug 2016 21:52, &quot;Fernando Gont&quot; &lt;<a href=
=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 08/03/2016 05:50 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:<br=
>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; Under this option, the recommendations in Section 3 w=
ould apply to<br>
&gt; &gt;&gt;&gt;&gt; all of the IP-over-foo documents listed in the docume=
nt header. But,<br>
&gt; &gt;&gt;&gt;&gt; for nodes that do not follow these recommendations, t=
he IP-over-foo<br>
&gt; &gt;&gt;&gt;&gt; documents would still contain their current text expl=
aining how to<br>
&gt; &gt;&gt;&gt;&gt; construct an EUI-64 for an IID.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; This may be not in the scope of this call, but in this ca=
se are we<br>
&gt; &gt;&gt;&gt; also going to update Section 3 so it will be clearer that=
 it&#39;s okay to<br>
&gt; &gt;&gt;&gt; not follow the recommendations of this document (assuming=
 that&#39;s the<br>
&gt; &gt;&gt;&gt; consensus)?=C2=A0 In its current form that&#39;s not clea=
r to me, especially<br>
&gt; &gt;&gt;&gt; because of wording like &quot;the default scheme=E2=80=9D=
.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Could you explain precisely what you find unclear? The senten=
ce to which you refer says<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; &quot;Nodes SHOULD implement and employ [RFC7217 &lt;<a href=
=3D"https://tools.ietf.org/html/rfc7217">https://tools.ietf.org/html/rfc721=
7</a>&gt;] as the default scheme for generating stable IPv6 addresses with =
SLAAC.=E2=80=9D<br>
&gt; &gt;<br>
&gt; &gt; What&#39;s unclear to me is that whether this (&quot;SHOULD xxx b=
y default&quot;)<br>
&gt; &gt; applies to any IPv6 nodes or nodes &quot;that follow the recommen=
dation of<br>
&gt; &gt; this document&quot;.<br>
&gt;<br>
&gt;<br>
&gt; The recommendation applies to all nodes, at the &quot;SHOULD&quot; lev=
el.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;&gt;&gt;&gt; [...] But,<br>
&gt; &gt;&gt;&gt;&gt; for nodes that do not follow these recommendations, t=
he IP-over-foo<br>
&gt; &gt;&gt;&gt;&gt; documents would still contain their current text expl=
aining how to<br>
&gt; &gt;&gt;&gt;&gt; construct an EUI-64 for an IID.<br>
&gt; &gt;<br>
&gt; &gt; but the current draft text could read as if it means the former.=
=C2=A0 To<br>
&gt; &gt; make it crystal clear, I&#39;d describe the &quot;nodes&quot; mor=
e precisely, e.g.:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 Nodes that need to generate stable IPv6 addresses wi=
th SLAAC but<br>
&gt; &gt;=C2=A0 =C2=A0 want to avoid privacy matters SHOULD implement and e=
mploy [RFC7217]<br>
&gt; &gt;=C2=A0 =C2=A0 as the default scheme for generating these IPv6 addr=
esses.<br>
&gt;<br>
&gt; =C2=A0think this text is totally different from what we&#39;ve working=
 on for<br>
&gt; years. And given &quot;pervasive monitoring&quot; et al, something tha=
t improves<br>
&gt; mod eui-64 must be done by default.<br>
&gt;<br>
&gt; Put another way: if you&#39;re not concerned about security and privac=
y...<br>
&gt; you should. :-)<br>
&gt;</p>
<p dir=3D"ltr">I think one thing to also remember is that the=C2=A0 privacy=
 property of an address is most important to the end user of the device rat=
her than the implementor of the device. Implementors aren&#39;t always, and=
 I&#39;d say aren&#39;t in most cases by volume (think of a mass market ven=
dor selling to end-users), in the best position to judge the level of priva=
cy required or desired by the end user.</p>
<p dir=3D"ltr">We don&#39;t want end user privacy reduced because doing so =
is more convenient for an end-user privacy context unaware implementor.</p>
<p dir=3D"ltr">Making RFC7217s the default is increasing the privacy of sta=
ble addresses. If an implementor wants to go against this default, we want =
to make it clear that they know they&#39;re making a privacy judgement on b=
ehalf of their implementation&#39;s end-user and they need to be sure that =
they&#39;re meeting their end-users&#39; privacy requirements.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; Thanks,<br>
&gt; --<br>
&gt; Fernando Gont<br>
&gt; SI6 Networks<br>
&gt; e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com=
</a><br>
&gt; PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r></p>

--001a113f029674e94805395cb41f--


From nobody Fri Aug  5 18:17:22 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB9AA12B061; Fri,  5 Aug 2016 18:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.026
X-Spam-Level: **
X-Spam-Status: No, score=2.026 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.626, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 c8Lis0DoXZsg; Fri,  5 Aug 2016 18:17:05 -0700 (PDT)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::231]) (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 475E112D51A; Fri,  5 Aug 2016 18:17:05 -0700 (PDT)
Received: by mail-ua0-x231.google.com with SMTP id 35so209444673uap.1; Fri, 05 Aug 2016 18:17:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=T3VLmIbfe99V/x0Tsbok8s0ZOp0Edmg6Q+HOSArD+Ww=; b=bb91vNNJYtvCVgVlbd7ltO2TSuIWQXVgOZb+cpqrZqYi+qb8lP8ke4cMj+zTpHc9dN DT15xPJYkeIHLHLCYQK3d5owXVrWaU8ZVCvY2LqHgUOp9dwioevGfej3/eieT8XPRdxn XnkWyMe5un52KlFS/dAvYpBh1cK1lz6Alkdgg9OokjAeNB30siDaL0KRCKfRW8SCWu35 MGBLnUJsTxTQKsUpmE5D92qtW7uZiidketU2PcD9mHFY6Hyhpiw8kpQIhqCJk7ZPuT2b ASg2ZRYy89Ga53h6/5T22zArJWPjhrbBtt47bl5TqpimFPaNVPcZo2AKr9C4ES8aZ/FV 8Ktw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=T3VLmIbfe99V/x0Tsbok8s0ZOp0Edmg6Q+HOSArD+Ww=; b=AxpgyD7aXbnctQdi5IY+fzxRkoVcmhNgGPwXhzujKJgbXrc7GDCPGJTWj+gOoQAk5v wC+jUmlr5S3P+TBPUoXaGdfO949Lg4mnMFA7H6ieUr6m+sOy46reBkgPgtgcPEHroHuT /aFNjP1aOBTKUByQdiZXErycgU3eujV8w3+Bew+Ma51c9nWqAz8Jm3t3aGPtyyx1XODN TkpKfM8KxCmEL1+G6HvO0YR+fGfqtSV0bA8L8x4Ujz6+luA8yh4V2XvIUFv2w0Bfsekm vZiBIOTpHxXul7AEs2oViZ4S16RnSith+ZylfSqihGHvS48WGl14hvmoaRFcTE/BxJcE GS1w==
X-Gm-Message-State: AEkooutt6joAb04hy/rGgMEsHLQPQR3WOn2mUbVKUek8r+MmX3A8APrPw5Fm3G7QovuLrS+fberbhxYohP2v0g==
X-Received: by 10.176.0.211 with SMTP id 77mr2180940uaj.75.1470446224337; Fri, 05 Aug 2016 18:17:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.54.233 with HTTP; Fri, 5 Aug 2016 18:17:03 -0700 (PDT)
Received: by 10.159.54.233 with HTTP; Fri, 5 Aug 2016 18:17:03 -0700 (PDT)
In-Reply-To: <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 6 Aug 2016 11:17:03 +1000
Message-ID: <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113d101cdcf14b05395cf0e7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/2yRE6JMpPZ_YVNWt_27ArUKvEtc>
Cc: 6man WG <ipv6@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2016 01:17:07 -0000

--001a113d101cdcf14b05395cf0e7
Content-Type: text/plain; charset=UTF-8

On 5 Aug 2016 22:42, "Fernando Gont" <fgont@si6networks.com> wrote:
>
> On 08/04/2016 10:23 PM, Alissa Cooper wrote:
> >
> >> On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> >>
> >> Ole:
> >>
> >> (I fixed 6man mailing list address.)
> >>
> >> That is probably the best solution and I would support that.
> >>
> >> We can still discuss changing some of the text in 3315bis, but that can
> >> then be done without 6man involvement. (We do still have the older
text in
> >> what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so should
really
> >> clean that up.)
> >
> > I am fine with this solution and it seems cleaner.
>
> Background: At some point folks argued that this document should cover
> SLAAC, DHCPv6, and manual configuration. And hence this text was added.
>
> I don't mind removing the DHCPv6 text. However, if we do, we should
> probably also remove the text about manual configuration. Otherwise it
> is not clear why some forms of configuration are covered, but others are
> not.
>

I argued for that because I think privacy is a primary property of an
address, not the method used to configure it. However, since the different
methods of configuring the address can effect the resulting address's
privacy properties, I think it is necessary to discuss how to achieve
privacy for the three different configuration methods we have in the one
place.

Regards,
Mark.

> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--001a113d101cdcf14b05395cf0e7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"></p>
<p dir=3D"ltr">On 5 Aug 2016 22:42, &quot;Fernando Gont&quot; &lt;<a href=
=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 08/04/2016 10:23 PM, Alissa Cooper wrote:<br>
&gt; &gt;<br>
&gt; &gt;&gt; On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) &lt;<a href=
=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Ole:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; (I fixed 6man mailing list address.)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; That is probably the best solution and I would support that.<=
br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; We can still discuss changing some of the text in 3315bis, bu=
t that can<br>
&gt; &gt;&gt; then be done without 6man involvement. (We do still have the =
older text in<br>
&gt; &gt;&gt; what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so =
should really<br>
&gt; &gt;&gt; clean that up.)<br>
&gt; &gt;<br>
&gt; &gt; I am fine with this solution and it seems cleaner.<br>
&gt;<br>
&gt; Background: At some point folks argued that this document should cover=
<br>
&gt; SLAAC, DHCPv6, and manual configuration. And hence this text was added=
.<br>
&gt;<br>
&gt; I don&#39;t mind removing the DHCPv6 text. However, if we do, we shoul=
d<br>
&gt; probably also remove the text about manual configuration. Otherwise it=
<br>
&gt; is not clear why some forms of configuration are covered, but others a=
re<br>
&gt; not.<br>
&gt;</p>
<p dir=3D"ltr">I argued for that because I think privacy is a primary prope=
rty of an address, not the method used to configure it. However, since the =
different methods of configuring the address can effect the resulting addre=
ss&#39;s privacy properties, I think it is necessary to discuss how to achi=
eve privacy for the three different configuration methods we have in the on=
e place.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; Thanks,<br>
&gt; --<br>
&gt; Fernando Gont<br>
&gt; SI6 Networks<br>
&gt; e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com=
</a><br>
&gt; PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r></p>

--001a113d101cdcf14b05395cf0e7--


From nobody Fri Aug  5 18:23:55 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7C212D18A for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 18:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 hMw5Ani27af8 for <ipv6@ietfa.amsl.com>; Fri,  5 Aug 2016 18:23:53 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 E393E12D605 for <ipv6@ietf.org>; Fri,  5 Aug 2016 18:23:52 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id x185so85794069qkc.2 for <ipv6@ietf.org>; Fri, 05 Aug 2016 18:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=p9wpvCGWz4Ka2vto4/M12x8Iv2P+bgnEFk180IC73jg=; b=FzdIycNRviIf0g14L/VOtrb2dsczwXrZ7L4JUDQysNv9AQawZQp8Iw1mi0z2bMy26O reAipc1i5O6q+U6MIcCenVi/oeBKp8XNyYiMR0aXWHJ0PzpBZIPIAHiN6z7ua3wSxabF fuIqtUnVx06Z61nHrx6TGUyyYb/hYe18XkoFPZnteZ5DP13CkDDU++/iW4mDGaII+AZO q9gV8f0GL0d7b5jwZ1f3oW5YpdA0R1cxKzM75XfGywUE9GkDbkIeUC3BZhCKpwkZl2iP OUfeIZ6EK4qFGLgIOSGrLF2nRsTEk5vRoOcPfxijvS0Lp1Y+AGMOWbQxblwahC41rtf6 biOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=p9wpvCGWz4Ka2vto4/M12x8Iv2P+bgnEFk180IC73jg=; b=jc4L5aY593dzgVUpSIJQqCCj7MSpm3Adi+eJqrc3AgGEijiqe6KPPLnbvzGvB4X8NV g0FkLNwKFMl22n0zY9+TM/m9JM1GrV32tgvKIsQqHsREsTQYo70g9Im+SPOsOuKsxkiA GYVEuvs0C2gTHivqW4rJzpG2/5IewB0rHycZHP21yypC2yzFFBs5mNvvk7tozTMsyBG3 JNuozaeNG9l+ZQ8V5hWbi/Toh3Pa56XsOULHPtBE/Q+iCo0zV49bfGN6sNs6Mvuqkr7U sOGahXovmSZRORIoL9sJq/YO8vSOkKeyuQeNxrr+3HzO+BTrsk5OwlKDSIhd30QBsnLO yn5A==
X-Gm-Message-State: AEkoouvTTJRptyvNuATKjUmhSQKneTP3Dmzu7v3kFmkQ3g2lUUYnD0CVOqhLyKkVhkcGV6/RTSzv3d/VLgy87g==
X-Received: by 10.55.36.131 with SMTP id k3mr7856958qkk.86.1470446631980; Fri, 05 Aug 2016 18:23:51 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Fri, 5 Aug 2016 18:23:51 -0700 (PDT)
In-Reply-To: <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com> <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Fri, 5 Aug 2016 18:23:51 -0700
X-Google-Sender-Auth: HlkHn4ntF6YjzQ0Y6amE1uifh_8
Message-ID: <CAJE_bqdLQLeApRVedfMt0q0YK1nnVvXkm9jYifpx-Ruh3jadLQ@mail.gmail.com>
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5V3fnd9fiMRAZ0tjCiE6SHjNi3U>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Aug 2016 01:23:54 -0000

At Thu, 4 Aug 2016 13:29:18 -0700,
Alissa Cooper <alissa@cooperw.in> wrote:

> >> Could you explain precisely what you find unclear? The sentence to whi=
ch you refer says
> >>
> >> "Nodes SHOULD implement and employ [RFC7217 <https://tools.ietf.org/ht=
ml/rfc7217>] as the default scheme for generating stable IPv6 addresses wit=
h SLAAC.=E2=80=9D
> >
> > What's unclear to me is that whether this ("SHOULD xxx by default")
> > applies to any IPv6 nodes or nodes "that follow the recommendation of
> > this document=E2=80=9D.
>
> The recommendation applies to all nodes. Since it is a SHOULD, some
> nodes may not follow it and they would still be compliant. And since
> the recommendation itself is about generating stable IPv6 addresses
> with SLAAC, it applies only when that is what nodes are aiming to
> do.
>
> > This description of "Option 1" seems to suggest the
> > latter:
>
> The options have nothing to do with the extent to which the
> recommendation applies. The question about the options relates to
> what text will continue to be in place to describe what nodes might
> do if they do not follow the recommendation.

Option 1 states:

>> [...] But,
>> for nodes that do not follow these recommendations, the IP-over-foo
>> documents would still contain their current text explaining how to
>> construct an EUI-64 for an IID.

To rephrase my point, it's about what are "nodes that do not follow
these recommendations".  If my memory was correct, one of the
pushbacks came from people developing routers who don't even bother to
implement RFC7217 and just want to use EUI-64 based IID as before
since they have no privacy related concern in doing so.  I thought
"nodes that do not follow these recommendations" in Option 1 cover
these cases (among other cases like nodes that don't need stable
addresses), and if so, those people won't even be happy if the SHOULD
in Section 3 applies to their case.  Am I now clear enough?

(Forget the text I showed in my previous response - I didn't intend to
propose it as a replacement text but thought it clarified my intent in
that form.  Apparently it didn't, so I'm now explaining my point in a
different way).

To be clear, I personally don't have an issue if it applies to the
router cases.  I just tried to confirm if all of the previous concerns
(at least as I remember them) are now being addressed.

--
JINMEI, Tatuya


From nobody Mon Aug  8 14:37:09 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEEEB12D158; Mon,  8 Aug 2016 14:37:06 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-deprecate-atomfrag-generation-07.txt> (Generation of IPv6 Atomic Fragments Considered Harmful) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <147069222697.32129.11076524310950932474.idtracker@ietfa.amsl.com>
Date: Mon, 08 Aug 2016 14:37:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/H-Z-XK68cWufle451wXkcbRbjU8>
Cc: ipv6@ietf.org, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, bob.hinden@gmail.com, suresh.krishnan@ericsson.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 21:37:07 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'Generation of IPv6 Atomic Fragments Considered Harmful'
  <draft-ietf-6man-deprecate-atomfrag-generation-07.txt> as Informational
RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-08-22. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document discusses the security implications of the generation
   of IPv6 atomic fragments and a number of interoperability issues
   associated with IPv6 atomic fragments, and concludes that the
   aforementioned functionality is undesirable, thus documenting the
   motivation for removing this functionality in the revision of the
   core IPv6 protocol specification.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-6man-deprecate-atomfrag-generation/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-6man-deprecate-atomfrag-generation/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Tue Aug  9 06:14:29 2016
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D3512D801 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 06:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 SHDX5h6474-0 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 06:14:26 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 DEED612D7FC for <ipv6@ietf.org>; Tue,  9 Aug 2016 06:14:25 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id l2so11637591qkf.3 for <ipv6@ietf.org>; Tue, 09 Aug 2016 06:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:from:date:message-id:subject:to; bh=0Yq3ZgKv3p8T4VdJMFLOWIcaQ7WG8AHWvgnm/4ji3C4=; b=dnhUCmSGdnQ0lf7S3ljNN80EwKy0kUISOTJpnkUtuI5areU/J7lgJujMhsu7mN4+MI J9yvuMh2acJzR+csCiZDslAmQmtef5gJ8+yk0+Y00VLTGkmgTLhu6z0dcwJK4DGgxN2B xyX4KXG0Zs38+kJQnFGKatDxlDjbnnba+Pnxw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0Yq3ZgKv3p8T4VdJMFLOWIcaQ7WG8AHWvgnm/4ji3C4=; b=aChgfzfu8z9d4eaxgnaaZPii3qlvNdPLKo/0d6n6wXUc/ZvnESggHcdNM+NrXCz2Y6 1PU76+XdU7T+mcdqghss0aAItI51TLTRnDs/Tt330VoXvKWER8JiMA3Lhdmxsh1KSIkQ jEMenYU/zRjD03KKZD39TUqo+SAfbf/VXu607bkHOCgLh3yKOsc4+m9OqO5F2bh6spMP 1KWHPtUtXSipjZATF0GgAGy49bG7Jv8iDYrhle7ECaV9G5aZL+gu/Iy5Lf+i0dejjVPc jt7M6qpmok6j72eExWf+5adUr62c26kkYUx9TcwIRy6ofH2n549qOkg5o8MakBHsMYO1 NwNg==
X-Gm-Message-State: AEkoout3CpMQP8qOxkXPdpS/4g4jstgvUaEcB40mVSinURy0PLwFhdFvht/r8c13CIdtaox9ak1gZhT55zGfo43Q
X-Received: by 10.55.18.9 with SMTP id c9mr32804999qkh.245.1470748464701; Tue, 09 Aug 2016 06:14:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.58.202 with HTTP; Tue, 9 Aug 2016 06:14:15 -0700 (PDT)
From: Timothy Winters <twinters@iol.unh.edu>
Date: Tue, 9 Aug 2016 09:14:15 -0400
Message-ID: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com>
Subject: Redirected Header (Forwarded/Originating Packet)
To: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a11476364cb06e20539a34f5d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/7nL_C2WFx0RphVqjLxE54XNLYmU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 13:14:28 -0000

--001a11476364cb06e20539a34f5d
Content-Type: text/plain; charset=UTF-8

Hello,

The UNH-IOL has seen several different implementations with varied
interpretations the following line from RFC 4861 Section 8.2 regarding what
should be included in the Redirect Header of an ICMPv6 Redirect message.

"Redirected Header: as much of the forwarded packet as can
             fit without the redirect packet exceeding the minimum MTU
             required to support IPv6 as specified in [IPv6]."

My interpretation has been that the redirected header should be the
forwarded packet, not the originating packet.   Recently we've seen Linux
based routers use   the originating packet.

My guess is they read this line from RFC 4861 Section 4.6.3
The original packet truncated to ensure that the
                     size of the redirect message does not exceed the
                     minimum MTU required to support IPv6 as specified
                     in [IPv6]."

The reason that I'm asking is we have seen host that don't process the
Redirect message unless it's the forwarding packet.   I want to make sure
that we are telling implementations the correct behavior.

~Tim

-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR

--001a11476364cb06e20539a34f5d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>The UNH-IOL has seen several dif=
ferent implementations with varied interpretations the following line from =
RFC 4861 Section 8.2 regarding what should be included in the Redirect Head=
er of an ICMPv6 Redirect message.</div><div><br></div><div>&quot;Redirected=
 Header: as much of the forwarded packet as can</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fit without the redirect packet exceeding th=
e minimum MTU</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0req=
uired to support IPv6 as specified in [IPv6].&quot;</div><div><br></div><di=
v>My interpretation has been that the redirected header should be the forwa=
rded packet, not the originating packet. =C2=A0 Recently we&#39;ve seen Lin=
ux based routers use =C2=A0 the originating packet.</div><div><br></div><di=
v>My guess is they read this line from RFC 4861 Section 4.6.3=C2=A0</div><d=
iv>The original packet truncated to ensure that the</div><div>=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0size of the =
redirect message does not exceed the</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0minimum MTU required to sup=
port IPv6 as specified</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0in [IPv6].&quot;</div><div><br></div><div=
>The reason that I&#39;m asking is we have seen host that don&#39;t process=
 the Redirect message unless it&#39;s the forwarding packet. =C2=A0 I want =
to make sure that we are telling implementations the correct behavior.</div=
><div><br></div><div>~Tim<br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">







<p><font face=3D"georgia, serif" size=3D"1">Now offering testing for SDN ap=
plications and controllers in our SDN switch test bed.=C2=A0</font><span st=
yle=3D"font-family:georgia,serif;font-size:x-small">Learn more today <a hre=
f=3D"http://bit.ly/SDN_IOLPR" target=3D"_blank">http://bit.ly/SDN_IOLPR</a>=
</span></p></div></div></div></div></div></div></div>
</div></div>

--001a11476364cb06e20539a34f5d--


From nobody Tue Aug  9 07:18:49 2016
Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F13E912D0E9 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 l5NVTKZneiNV for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:18:46 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-he.hq.phicoh.net [IPv6:2001:470:d16a:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id E2B1612D16F for <ipv6@ietf.org>; Tue,  9 Aug 2016 07:18:44 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1bX7rf-0000CtC; Tue, 9 Aug 2016 16:18:43 +0200
Message-Id: <m1bX7rf-0000CtC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Redirected Header (Forwarded/Originating Packet) 
From: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
In-reply-to: Your message of "Tue, 9 Aug 2016 09:14:15 -0400 ." <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> 
Date: Tue, 09 Aug 2016 16:18:42 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Kj-dM5wYRsC76O_QmwwKPsmf7hw>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 14:18:48 -0000

>My interpretation has been that the redirected header should be the
>forwarded packet, not the originating packet.   Recently we've seen Linux
>based routers use   the originating packet.
>
>My guess is they read this line from RFC 4861 Section 4.6.3
>The original packet truncated to ensure that the
>                     size of the redirect message does not exceed the
>                     minimum MTU required to support IPv6 as specified
>                     in [IPv6]."
>
>The reason that I'm asking is we have seen host that don't process the
>Redirect message unless it's the forwarding packet.   I want to make sure
>that we are telling implementations the correct behavior.

Am I correct to assume that only difference is the hlim field?

I'm really curious why those hosts do the check and to some extend how they can
tell. It means going back to the original packet and checking that the one in
the error ICMP has its hlim reduced.

Though I have to check my own implementation. It's too easy to get this wrong.


From nobody Tue Aug  9 07:26:09 2016
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13D2012D7CA for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 F-o1ztbEB_mm for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:26:05 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 BD70F12D0DD for <ipv6@ietf.org>; Tue,  9 Aug 2016 07:26:05 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id l2so14029560qkf.3 for <ipv6@ietf.org>; Tue, 09 Aug 2016 07:26:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=unMNIf5th+RkvZHH9zM6wggz6nt8wWRpZgwQVOmzOkE=; b=I4jw9tvI/xJfQPDtzM9Tj0Q/URqJqR21uomR3UgPIquHITsnjmKyW1c6c1cpx2vy5I tbt31K50TBmzekd/Es5hDEadqNVN3J4OZu5tKE9mZLmfOLZ6NJmyTzkjW/oma3ag9wSx 6OsgIaKc0XYMlAtNQsRZMPK99gg0rjYRtIMaE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=unMNIf5th+RkvZHH9zM6wggz6nt8wWRpZgwQVOmzOkE=; b=Lkwmp8Q9ZNE28AkzVEWvUG8UdBftOAwuWj5oORk1zM/GA3nsPl2Dbg5YlP615K+BWf ESKro3frsYFru+yny4o1uuSoRX5/01r773B8bbisUnU5xW+eCmzvLntYQDR0qi+kPojR fhDgzn+Qo2R2/gTs6GvlzsihNMlIbkBLx0ut7hz7lHpZ4ThWhgL4o0t0uVCzJBzJJyqZ ax80hzI+hzBIihQDIyi0QeWg9RxFve4lnJZZPuvMdTXUqsBon8yoKmSdOxZmyftmS7m1 6ZwEXGpekiNv8ajhIul9C3TEMCNyQ7UXxViXa4Qxe6LtLKal/RNKF/R25J+2y79tjpXK 5EDQ==
X-Gm-Message-State: AEkoousOgjYnTHmQMtRbsj4uA6OpqJFb809nffhz1TXZbtOLDtQnsI4UtpmOgyuafGssNk711Kw5tPZp5HA8Vnt7
X-Received: by 10.55.167.69 with SMTP id q66mr34439023qke.158.1470752764890; Tue, 09 Aug 2016 07:26:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.58.202 with HTTP; Tue, 9 Aug 2016 07:25:57 -0700 (PDT)
In-Reply-To: <m1bX7rf-0000CtC@stereo.hq.phicoh.net>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Tue, 9 Aug 2016 10:25:57 -0400
Message-ID: <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary=001a114fd1241aafd50539a45095
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BT-CMYqknKgBUUonfcpVw-ovGI0>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 14:26:08 -0000

--001a114fd1241aafd50539a45095
Content-Type: text/plain; charset=UTF-8

Hi Philip,

You are correct is the hop limit field is decremented.   I have no idea why
the host are choosing to check that field, but my best guess is that they
want to confirm it's being forwarded by the next-hop router?   As opposed
to anyone sending them Redirect?

~Tim

On Tue, Aug 9, 2016 at 10:18 AM, Philip Homburg <
pch-ipv6-ietf-3@u-1.phicoh.com> wrote:

> >My interpretation has been that the redirected header should be the
> >forwarded packet, not the originating packet.   Recently we've seen Linux
> >based routers use   the originating packet.
> >
> >My guess is they read this line from RFC 4861 Section 4.6.3
> >The original packet truncated to ensure that the
> >                     size of the redirect message does not exceed the
> >                     minimum MTU required to support IPv6 as specified
> >                     in [IPv6]."
> >
> >The reason that I'm asking is we have seen host that don't process the
> >Redirect message unless it's the forwarding packet.   I want to make sure
> >that we are telling implementations the correct behavior.
>
> Am I correct to assume that only difference is the hlim field?
>
> I'm really curious why those hosts do the check and to some extend how
> they can
> tell. It means going back to the original packet and checking that the one
> in
> the error ICMP has its hlim reduced.
>
> Though I have to check my own implementation. It's too easy to get this
> wrong.
>



-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR

--001a114fd1241aafd50539a45095
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Philip,<div><br></div><div>You are correct is the hop l=
imit field is decremented. =C2=A0 I have no idea why the host are choosing =
to check that field, but my best guess is that they want to confirm it&#39;=
s being forwarded by the next-hop router? =C2=A0 As opposed to anyone sendi=
ng them Redirect?</div><div><br></div><div>~Tim</div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Tue, Aug 9, 2016 at 10:18 AM, =
Philip Homburg <span dir=3D"ltr">&lt;<a href=3D"mailto:pch-ipv6-ietf-3@u-1.=
phicoh.com" target=3D"_blank">pch-ipv6-ietf-3@u-1.phicoh.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt;My interpret=
ation has been that the redirected header should be the<br>
&gt;forwarded packet, not the originating packet.=C2=A0 =C2=A0Recently we&#=
39;ve seen Linux<br>
&gt;based routers use=C2=A0 =C2=A0the originating packet.<br>
&gt;<br>
&gt;My guess is they read this line from RFC 4861 Section 4.6.3<br>
&gt;The original packet truncated to ensure that the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0size of the redirect message does not exceed the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0minimum MTU required to support IPv6 as specified<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0in [IPv6].&quot;<br>
&gt;<br>
&gt;The reason that I&#39;m asking is we have seen host that don&#39;t proc=
ess the<br>
&gt;Redirect message unless it&#39;s the forwarding packet.=C2=A0 =C2=A0I w=
ant to make sure<br>
&gt;that we are telling implementations the correct behavior.<br>
<br>
</span>Am I correct to assume that only difference is the hlim field?<br>
<br>
I&#39;m really curious why those hosts do the check and to some extend how =
they can<br>
tell. It means going back to the original packet and checking that the one =
in<br>
the error ICMP has its hlim reduced.<br>
<br>
Though I have to check my own implementation. It&#39;s too easy to get this=
 wrong.<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">







<p><font face=3D"georgia, serif" size=3D"1">Now offering testing for SDN ap=
plications and controllers in our SDN switch test bed.=C2=A0</font><span st=
yle=3D"font-family:georgia,serif;font-size:x-small">Learn more today <a hre=
f=3D"http://bit.ly/SDN_IOLPR" target=3D"_blank">http://bit.ly/SDN_IOLPR</a>=
</span></p></div></div></div></div></div></div></div>
</div>

--001a114fd1241aafd50539a45095--


From nobody Tue Aug  9 07:38:48 2016
Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB2B12B038 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 u35F3PBWr4Gt for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 07:38:46 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-he.hq.phicoh.net [IPv6:2001:470:d16a:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 4045512D81E for <ipv6@ietf.org>; Tue,  9 Aug 2016 07:38:28 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1bX8Al-0000CtC; Tue, 9 Aug 2016 16:38:27 +0200
Message-Id: <m1bX8Al-0000CtC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Redirected Header (Forwarded/Originating Packet) 
From: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> 
In-reply-to: Your message of "Tue, 9 Aug 2016 10:25:57 -0400 ." <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> 
Date: Tue, 09 Aug 2016 16:38:27 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/glFFEc_wW1WikDdZO_4Yb9qoQmo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 14:38:47 -0000

In your letter dated Tue, 9 Aug 2016 10:25:57 -0400 you wrote:
>You are correct is the hop limit field is decremented.   I have no idea why
>the host are choosing to check that field, but my best guess is that they
>want to confirm it's being forwarded by the next-hop router?   As opposed
>to anyone sending them Redirect?

Well, the redirect has to come from an onlink node. So you have to rely on L2
filtering anyhow to prevent rogue RA/NA.

But I can understand going the extra mile and checking the redirected packet.
But in that case, I would check fields that are hard to guess, for example TCP
seqence numbers. Checking hlim, which is more or less constant for most stacks
and only 8 bit if you want to brute force sounds like a waste of time.



From nobody Tue Aug  9 08:02:29 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7031312D8B1 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:02:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Of-SGVM-jrhn for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:02:27 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 7C5A112D846 for <ipv6@ietf.org>; Tue,  9 Aug 2016 08:02:26 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id f189so20962785oig.3 for <ipv6@ietf.org>; Tue, 09 Aug 2016 08:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6Vc/6qInfL6pBWZuNvcHgTTiv8lS1Cj5h3jyuijogbM=; b=HpfS05JCO+epU01+tnGINdiIMO/EDicCbr51hFGb8gc9/90bzcO8hUxSeqgCOl9yv7 S08R08kbBOknuEgQl6ICg5wZsN8/hj/vn5X2LLd/AbwcOFYLsnJEENenshcRfJCb+IZP AL6raNTVuLSRSu6sW19Kb1G34eGZ2EKEa+l8Bvz0brdAIphLeVMK75BxOH9Ui7kiF5c2 +pS1kjCCjwTK8FrhFoIfmnuU7ab8InEEVIsxZvdOYVx2g+rfbLGk/ur7ThJzuNaJCwBA jOx5aNX0a9aNv+eEBJimMI6yQNS26Wo6Ty+bZsbj3gwqVX3FFXzdvyvhn89pP6/M695m ipBg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6Vc/6qInfL6pBWZuNvcHgTTiv8lS1Cj5h3jyuijogbM=; b=AYY7d7GX8qQ6T57TGe+hV0NJ5qkBiBDzBu875/W6wiNfwZmitcXjSS7aK0A7IzADlW j24AqaDTKROWkVfzWC665QjCLtsbrr2LpXUlphkbQChwdT6klOz9hSNkiDGiejwFrQL+ LQ5G9E6YYfUvwajaWN67OXd/i6gA5JNYl/Jx68f2tT5oRKXAtHXKX4EyyVifrpdWgBlB aANzBae29/fweIrYMWbm9GH6DwbvkcyLfl1Wa0J6c8D/kcg/Aa5iIhObdLW+i7ZU4QrZ /iHBiXhpD4h0OnibfX0g06Q9Ih/WcK26PrVvnIEXSUP0bNww2h8wvyc8mAV3d+H+gUZI NJiA==
X-Gm-Message-State: AEkoous0bB0TymhiN8SI8y4sRnJdI+rLnvzKZjvzogdqHIQ+IA6WutZg52ZBgAUXYlKOLoEiY/rD/OMqff4dwQ==
X-Received: by 10.157.33.244 with SMTP id s107mr2465052otb.138.1470754945759;  Tue, 09 Aug 2016 08:02:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Tue, 9 Aug 2016 08:02:25 -0700 (PDT)
In-Reply-To: <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com>
From: Hemant Singh <hemantietf@gmail.com>
Date: Tue, 9 Aug 2016 11:02:25 -0400
Message-ID: <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Timothy Winters <twinters@iol.unh.edu>
Content-Type: multipart/alternative; boundary=001a114933ec1802bc0539a4d239
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Y86nzCckztG1vfnL8DNkuRcGH5E>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 15:02:28 -0000

--001a114933ec1802bc0539a4d239
Content-Type: text/plain; charset=UTF-8

Section 8.1 of RFC 4861 clarifies this confusion.

(a) The IP Source Address is the router link-local address.  A packet with
a link-local source is not a forwarded packet.
(b) The IP Hop Limit is 255, i.e., the packet is not a forwarded packet.

Hemant

--001a114933ec1802bc0539a4d239
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Section 8.1 of RFC 4861 clarifies this confusion.<div><br>=
</div><div>(a) The IP Source Address is the router link-local address.=C2=
=A0 A packet with a link-local source is not a forwarded packet.</div><div>=
(b) The IP Hop Limit is 255, i.e., the packet is not a forwarded packet.</d=
iv><div><br></div><div>Hemant</div></div>

--001a114933ec1802bc0539a4d239--


From nobody Tue Aug  9 08:07:33 2016
Return-Path: <pch-bBB316E3E@u-1.phicoh.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C81BC12D68F for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:07:31 -0700 (PDT)
X-Quarantine-ID: <Q1tMs2Ry1ZSj>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 Q1tMs2Ry1ZSj for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:07:31 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-he.hq.phicoh.net [IPv6:2001:470:d16a:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 9E43912D8BD for <ipv6@ietf.org>; Tue,  9 Aug 2016 08:07:30 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1bX8cr-0000FUC; Tue, 9 Aug 2016 17:07:29 +0200
Message-Id: <m1bX8cr-0000FUC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Redirected Header (Forwarded/Originating Packet) 
From: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com> 
In-reply-to: Your message of "Tue, 9 Aug 2016 11:02:25 -0400 ." <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com> 
Date: Tue, 09 Aug 2016 17:07:27 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cNH8zDbXV65XlTmWtCDPT00QJRk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 15:07:32 -0000

>
>Section 8.1 of RFC 4861 clarifies this confusion.
>
>(a) The IP Source Address is the router link-local address.  A packet with
>a link-local source is not a forwarded packet.
>(b) The IP Hop Limit is 255, i.e., the packet is not a forwarded packet.

We were discussing the hlim field in the redirected header, i.e. the copy of the
packet that triggered the redirect, not the outer IPv6 header of the redirect
ICMP itself.



From nobody Tue Aug  9 08:56:42 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D511412D648 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 FqcMbCw9bJU6 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 08:56:39 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 ECA9612D639 for <ipv6@ietf.org>; Tue,  9 Aug 2016 08:56:30 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id c15so23312315oig.0 for <ipv6@ietf.org>; Tue, 09 Aug 2016 08:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sPZwdarmVp9lB+bfwnvmbDINLoTua3qXvxFUfUcFmg0=; b=I8rnTw0qNq+fOXm1eBM6+aqFVOgk7/zFilbiNfQD/q+JaLUyRQVbYyeqBPBbSCLb+C na+mDuM59WRU8TVLvCNqGfZFJO6BHz1u/aIuh5M2qD3E7G5ZDZJdWB1y51TsWF9csehl lZd6DOflBOz4rDclOxzY9vUGuH3zDor314hekWOAbEsVRnrWZF3AQucPLvrrM4w6MN7A FPygDbcoFDfXMbjkGuCd/PWkLaHeo8t/+rNLwbOs1LxdvO/PiEVw1Zr7LWNlAH5bgO2I FhD48QS+LIyDEGz+rRHzMe2ClFQkI56U6M7zLVp76mqwXXtI9747diHhN5dO73vwvGWL rc/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sPZwdarmVp9lB+bfwnvmbDINLoTua3qXvxFUfUcFmg0=; b=HY2i3YwU5sztZeAg2twl4Q94cdKbkQDyGDuWNcbyYwjxjhJGa3MiYymGCxOL4hpIpg 22W53evon47tsGfznVGK8Rr0Z15UxF8Eipms5ypIy8hGbTROQDoQdInAZstgPYbiqFUd YpdWOlZFH+0mIYrl4n6KbWFv2z/h5Jn2KiLg1t3xpZx35cQU+5gcu6mNcvD6OVMWRqSG H/6apAS0GpsFumzHQLr8+QEzTIlDMI0k3rZYYk9AO+MGtkGLz0jgrpHkd+1Th2ZQkHY2 vXXYITC1ozVxWWCuzUlGl3nsfrZbQQjHT365EckH5sEuWAZ4VEVudX3tpF5fCWoEhB+7 IBog==
X-Gm-Message-State: AEkoousUfe0+QOY2Mqrt0fuMmDypj36BVdAuCWk4GF8P1o1gfHXyDDXI6pa6T2A+aO2t62s4O/hjRg+nDXTXVQ==
X-Received: by 10.202.212.139 with SMTP id l133mr15452765oig.11.1470758190218;  Tue, 09 Aug 2016 08:56:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Tue, 9 Aug 2016 08:56:29 -0700 (PDT)
In-Reply-To: <m1bX8cr-0000FUC@stereo.hq.phicoh.net>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com> <m1bX8cr-0000FUC@stereo.hq.phicoh.net>
From: Hemant Singh <hemantietf@gmail.com>
Date: Tue, 9 Aug 2016 11:56:29 -0400
Message-ID: <CABdyVt4a+H24H-UbMVDec22_nQU9LE_H-AM=CtWBzbm3ORkABg@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary=001a113dd9b47a824f0539a593e6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Cs3UgbmPPN36eeYmMr7757AIIl4>
Cc: IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 15:56:41 -0000

--001a113dd9b47a824f0539a593e6
Content-Type: text/plain; charset=UTF-8

Tim,

Sorry, I missed the inner hlim in the email.

The Redirect is a message generated by the router and thus the Redirect is
not really a forwarded packet.  An implementation has no business to change
the hlim IP header of the copied packet.   For reference, please check what
do ICMPv6 Error messages from RFC 4443 do for the inner hlim field; these
messages also have to include a copy of the packet.   We should have
consistent behavior for all such ICMPv6 messages.

Hemant


On Tue, Aug 9, 2016 at 11:07 AM, Philip Homburg <
pch-ipv6-ietf-3@u-1.phicoh.com> wrote:

>
>
> We were discussing the hlim field in the redirected header, i.e. the copy
> of the
> packet that triggered the redirect, not the outer IPv6 header of the
> redirect
> ICMP itself.
>
>
>

--001a113dd9b47a824f0539a593e6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Tim,<div><br></div><div>Sorry, I missed the inner hlim in =
the email. =C2=A0</div><div><br></div><div>The Redirect is a message genera=
ted by the router and thus the Redirect is not really a forwarded packet.=
=C2=A0 An implementation has no business to change the hlim IP header of th=
e copied packet. =C2=A0 For reference, please check what do ICMPv6 Error me=
ssages from RFC 4443 do for the inner hlim field; these messages also have =
to include a copy of the packet. =C2=A0 We should have consistent behavior =
for all such ICMPv6 messages.</div><div><br></div><div>Hemant</div><div><br=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Aug 9, 2=
016 at 11:07 AM, Philip Homburg <span dir=3D"ltr">&lt;<a href=3D"mailto:pch=
-ipv6-ietf-3@u-1.phicoh.com" target=3D"_blank">pch-ipv6-ietf-3@u-1.phicoh.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
><br>
<br>
</span>We were discussing the hlim field in the redirected header, i.e. the=
 copy of the<br>
packet that triggered the redirect, not the outer IPv6 header of the redire=
ct<br>
ICMP itself.<br>
<br>
<br>
</blockquote></div><br></div></div></div>

--001a113dd9b47a824f0539a593e6--


From nobody Tue Aug  9 09:59:23 2016
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A24BA12D0F6 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 09:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 htsdWQ2UWtv2 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 09:59:20 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 C247D12D1D5 for <ipv6@ietf.org>; Tue,  9 Aug 2016 09:59:19 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id l2so18716254qkf.3 for <ipv6@ietf.org>; Tue, 09 Aug 2016 09:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=srSsIsWHezGdl0vrRDPETmtYGsg2EF6zXW/KgO7GCRg=; b=ZEw//IE+hV+qfKolPPSewMhpVeR4r56cjVZXx/0OymKWP4T25IDdZSdotyzS+GhtBA 2lw7CEH+sfMcNtYbGHFL/8lzayzV7lim9BQyc1vXp7+oWox0jESONzE6LMLxXY9uXJKs eiExr/zTIbK3taJTsiGf5otO//Ta016uhPeoA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=srSsIsWHezGdl0vrRDPETmtYGsg2EF6zXW/KgO7GCRg=; b=bwSULB4HQPbpziE7pqQHhkjb3CzNujbyW6epNO+qtKBHiaquSiRNmV5ne/jSkV/CZe 3C+kIbCVmMGhJ7g0fht3qflteOe6fa6s5zCo+nCHRSZOD4hk0OnJAyuQR/D6r/fFljtH tsTrmaQ9n0Uw+dioXzE+ynr2pqn9uhY+cJBUOf55D0LZ+vgjHSly0xFyZ4PzL4xvFBiG lFh8WXLXLNFy3LhBOmfVwYk7xpkV7LPAqUdwbUEijP+u9BE51hiBc7hzdut0/oHKfrZi l65vX0NyF2kDQGoENdx1K0aF1P3ISYXm2SJxk4ctbDxY9y4evDMXQiRJSDtDuJS3JX/k TGMA==
X-Gm-Message-State: AEkooutzB1/4O6iym2q1KQMYxF7FmBLm2UneF1XryNe161DgFLyNHxIv45I0t/acB2vb9uk49o9yymCu9wLJdVUD
X-Received: by 10.55.158.16 with SMTP id h16mr33095495qke.111.1470761958931; Tue, 09 Aug 2016 09:59:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.58.202 with HTTP; Tue, 9 Aug 2016 09:59:17 -0700 (PDT)
In-Reply-To: <CABdyVt4a+H24H-UbMVDec22_nQU9LE_H-AM=CtWBzbm3ORkABg@mail.gmail.com>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com> <m1bX8cr-0000FUC@stereo.hq.phicoh.net> <CABdyVt4a+H24H-UbMVDec22_nQU9LE_H-AM=CtWBzbm3ORkABg@mail.gmail.com>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Tue, 9 Aug 2016 12:59:17 -0400
Message-ID: <CAOSSMjXzapwWmL5KQ3vN_rr3FTVoFEJNDBvz3Y190po9JTuPqQ@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Hemant Singh <hemantietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a114d318e1c9d480539a6743f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ripjFqagvU-hFajj7eTARhuQjbs>
Cc: IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 16:59:21 -0000

--001a114d318e1c9d480539a6743f
Content-Type: text/plain; charset=UTF-8

Hi Hemant,

So my question is which packet that triggers the Redirect.  A redirect is
only transmitted after you forward the packet.  The issue is which packet
gets copied into the Redirect message.  The originating packet or the
forwarded packet?

~Tim

On Tue, Aug 9, 2016 at 11:56 AM, Hemant Singh <hemantietf@gmail.com> wrote:

> Tim,
>
> Sorry, I missed the inner hlim in the email.
>
> The Redirect is a message generated by the router and thus the Redirect is
> not really a forwarded packet.  An implementation has no business to change
> the hlim IP header of the copied packet.   For reference, please check what
> do ICMPv6 Error messages from RFC 4443 do for the inner hlim field; these
> messages also have to include a copy of the packet.   We should have
> consistent behavior for all such ICMPv6 messages.
>
> Hemant
>
>
> On Tue, Aug 9, 2016 at 11:07 AM, Philip Homburg <
> pch-ipv6-ietf-3@u-1.phicoh.com> wrote:
>
>>
>>
>> We were discussing the hlim field in the redirected header, i.e. the copy
>> of the
>> packet that triggered the redirect, not the outer IPv6 header of the
>> redirect
>> ICMP itself.
>>
>>
>>
>


-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR

--001a114d318e1c9d480539a6743f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Hemant,<div><br></div><div>So my question is which pack=
et that triggers the Redirect.=C2=A0 A redirect is only transmitted after y=
ou forward the packet.=C2=A0 The issue is which packet gets copied into the=
 Redirect message.=C2=A0 The originating packet or the forwarded packet?</d=
iv><div><br></div><div>~Tim</div></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, Aug 9, 2016 at 11:56 AM, Hemant Singh <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:hemantietf@gmail.com" target=3D"_blank">he=
mantietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
<div dir=3D"ltr">Tim,<div><br></div><div>Sorry, I missed the inner hlim in =
the email. =C2=A0</div><div><br></div><div>The Redirect is a message genera=
ted by the router and thus the Redirect is not really a forwarded packet.=
=C2=A0 An implementation has no business to change the hlim IP header of th=
e copied packet. =C2=A0 For reference, please check what do ICMPv6 Error me=
ssages from RFC 4443 do for the inner hlim field; these messages also have =
to include a copy of the packet. =C2=A0 We should have consistent behavior =
for all such ICMPv6 messages.</div><span class=3D"HOEnZb"><font color=3D"#8=
88888"><div><br></div><div>Hemant</div></font></span><span class=3D""><div>=
<br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Aug 9=
, 2016 at 11:07 AM, Philip Homburg <span dir=3D"ltr">&lt;<a href=3D"mailto:=
pch-ipv6-ietf-3@u-1.phicoh.com" target=3D"_blank">pch-ipv6-ietf-3@u-1.phico=
h.<wbr>com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><b=
r>
<br>
</span>We were discussing the hlim field in the redirected header, i.e. the=
 copy of the<br>
packet that triggered the redirect, not the outer IPv6 header of the redire=
ct<br>
ICMP itself.<br>
<br>
<br>
</blockquote></div><br></div></div></span></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">







<p><font face=3D"georgia, serif" size=3D"1">Now offering testing for SDN ap=
plications and controllers in our SDN switch test bed.=C2=A0</font><span st=
yle=3D"font-family:georgia,serif;font-size:x-small">Learn more today <a hre=
f=3D"http://bit.ly/SDN_IOLPR" target=3D"_blank">http://bit.ly/SDN_IOLPR</a>=
</span></p></div></div></div></div></div></div></div>
</div>

--001a114d318e1c9d480539a6743f--


From nobody Tue Aug  9 11:42:44 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1538B12D1A6 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 11:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=yoysSZ+Q; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=punhfevW
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 NiCIupckj0tx for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 11:42:40 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41AE212D1A3 for <ipv6@ietf.org>; Tue,  9 Aug 2016 11:42:40 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8B7CA20719; Tue,  9 Aug 2016 14:42:39 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Tue, 09 Aug 2016 14:42:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=emBJJewu43CQ4L1Lx12djY3gpj4=; b=yoysSZ +QVrF8vuZNqgGdlNfe9JqP9NxFCSHzxoOXuYcomRA1TD7TYNq3iAYS14VZ9V69Cs iULQOP2ISmrcFTo4cqmkOHolLQgTNY/gZeagt3/12nFq/3LFeEhlG+/jT7m9kKF2 ugpFhw7y0IWuGwnaYQ5xZ7pUNSlEMOjxEKj3g=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=emBJJewu43CQ4L1 Lx12djY3gpj4=; b=punhfevW6wcZm2KNkJfWyKdMlwuZnj3n2Kfr2mttFlN6gfA sCitnI76MGW8DAYFS992jx8L+2jBp0y39po6f7b+ZAL92LDEqUt/UW8078fXPM6y UYBMae9e2zIz7o4dYqmD5Tv8U/xt/ITi8VoZOY/lPrR5v/mlh8HZzrOszk+c=
X-Sasl-enc: hBYLSJ3HPIqoO+1mSkw9D4pZ1l1jABsVAEiMI/LICPqh 1470768159
Received: from dhcp-171-68-20-114.cisco.com (dhcp-171-68-20-114.cisco.com [171.68.20.114]) by mail.messagingengine.com (Postfix) with ESMTPA id D249CCCE66; Tue,  9 Aug 2016 14:42:38 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqdLQLeApRVedfMt0q0YK1nnVvXkm9jYifpx-Ruh3jadLQ@mail.gmail.com>
Date: Tue, 9 Aug 2016 11:42:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F95C173-2110-4540-9C1C-8124FB17B04B@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com> <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in> <CAJE_bqdLQLeApRVedfMt0q0YK1nnVvXkm9jYifpx-Ruh3jadLQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Rkh77sdNYrse2C0NvVYryv-6h1U>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:42:42 -0000

> On Aug 5, 2016, at 6:23 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Thu, 4 Aug 2016 13:29:18 -0700,
> Alissa Cooper <alissa@cooperw.in> wrote:
>=20
>>>> Could you explain precisely what you find unclear? The sentence to =
which you refer says
>>>>=20
>>>> "Nodes SHOULD implement and employ [RFC7217 =
<https://tools.ietf.org/html/rfc7217>] as the default scheme for =
generating stable IPv6 addresses with SLAAC.=E2=80=9D
>>>=20
>>> What's unclear to me is that whether this ("SHOULD xxx by default")
>>> applies to any IPv6 nodes or nodes "that follow the recommendation =
of
>>> this document=E2=80=9D.
>>=20
>> The recommendation applies to all nodes. Since it is a SHOULD, some
>> nodes may not follow it and they would still be compliant. And since
>> the recommendation itself is about generating stable IPv6 addresses
>> with SLAAC, it applies only when that is what nodes are aiming to
>> do.
>>=20
>>> This description of "Option 1" seems to suggest the
>>> latter:
>>=20
>> The options have nothing to do with the extent to which the
>> recommendation applies. The question about the options relates to
>> what text will continue to be in place to describe what nodes might
>> do if they do not follow the recommendation.
>=20
> Option 1 states:
>=20
>>> [...] But,
>>> for nodes that do not follow these recommendations, the IP-over-foo
>>> documents would still contain their current text explaining how to
>>> construct an EUI-64 for an IID.
>=20
> To rephrase my point, it's about what are "nodes that do not follow
> these recommendations".  If my memory was correct, one of the
> pushbacks came from people developing routers who don't even bother to
> implement RFC7217 and just want to use EUI-64 based IID as before
> since they have no privacy related concern in doing so.  I thought
> "nodes that do not follow these recommendations" in Option 1 cover
> these cases (among other cases like nodes that don't need stable
> addresses), and if so, those people won't even be happy if the SHOULD
> in Section 3 applies to their case. =20

Then those people don=E2=80=99t know what SHOULD means. In fact, =E2=80=9C=
if the SHOULD =E2=80=A6 applies in their case=E2=80=9D is not really a =
meaningful construction. The whole point of using SHOULD is to =
acknowledge that there are exception cases. There is no thought police =
running around judging the reasons why a specific implementor will =
choose to follow the recommendation or not.

Thanks,
Alissa

> Am I now clear enough?
>=20
> (Forget the text I showed in my previous response - I didn't intend to
> propose it as a replacement text but thought it clarified my intent in
> that form.  Apparently it didn't, so I'm now explaining my point in a
> different way).
>=20
> To be clear, I personally don't have an issue if it applies to the
> router cases.  I just tried to confirm if all of the previous concerns
> (at least as I remember them) are now being addressed.
>=20
> --
> JINMEI, Tatuya


From nobody Tue Aug  9 11:49:24 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF02F12D189; Tue,  9 Aug 2016 11:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=eadqU+2F; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=NmHcVdQ9
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 8Z6tr2wVdXFk; Tue,  9 Aug 2016 11:49:18 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11AFC12D50C; Tue,  9 Aug 2016 11:49:18 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 42A26200E5; Tue,  9 Aug 2016 14:49:17 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 09 Aug 2016 14:49:17 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=axUZA 81MzLJT5/PgxL+HqqB9LCM=; b=eadqU+2FRV/LrmEuLNct8xGBgwC1R4IsKXjX5 h4asBCNesk4kifkrWMgvSiNnY+BolCQW5mhLUND50XZLBcacVpRWgJYRuD/zBffs 13vJDuDsTLvrfGPmv0RCUDoATiceWHcbSGZ4M02eJuk4Zk5i0kVSTFgjmm6Xn7Tq 7V9DsE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=axUZA81MzLJT5/PgxL+HqqB9LCM=; b=NmHcV dQ99HlXAlIPBLN882+3qv3SlDkRJNe/aDLZfxGiZ+FB/1rDYkdBp8OLjZfyAMF+w TO6tbmnFEfluuI4S1NeEfju3qkDvfJ0kcFWR+7vWPgCnYnoLO/+UVFfDO41OcXrm 7EYL5tTSx0M4IOVwrh7+fgUFvx92odLj9/6mCg=
X-Sasl-enc: +zq5Kn1eSSb7tAuujxhH5K8dFSX7uhyGBkNYDoUWvWaP 1470768556
Received: from dhcp-171-68-20-114.cisco.com (dhcp-171-68-20-114.cisco.com [171.68.20.114]) by mail.messagingengine.com (Postfix) with ESMTPA id E9842F2983; Tue,  9 Aug 2016 14:49:15 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_849263CB-A4FA-4ABA-80BD-981C40CB278A"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
Date: Tue, 9 Aug 2016 11:49:14 -0700
Message-Id: <362684CB-570E-42F2-A8AE-C976EE537878@cooperw.in>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/19Fw2xnd-bHhYvLhkSjlXOxdshE>
Cc: 6man WG <ipv6@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Fernando Gont <fgont@si6networks.com>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:49:20 -0000

--Apple-Mail=_849263CB-A4FA-4ABA-80BD-981C40CB278A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Aug 5, 2016, at 6:17 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
>=20
>=20
> On 5 Aug 2016 22:42, "Fernando Gont" <fgont@si6networks.com =
<mailto:fgont@si6networks.com>> wrote:
> >
> > On 08/04/2016 10:23 PM, Alissa Cooper wrote:
> > >
> > >> On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) <volz@cisco.com =
<mailto:volz@cisco.com>> wrote:
> > >>
> > >> Ole:
> > >>
> > >> (I fixed 6man mailing list address.)
> > >>
> > >> That is probably the best solution and I would support that.
> > >>
> > >> We can still discuss changing some of the text in 3315bis, but =
that can
> > >> then be done without 6man involvement. (We do still have the =
older text in
> > >> what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so =
should really
> > >> clean that up.)
> > >
> > > I am fine with this solution and it seems cleaner.
> >
> > Background: At some point folks argued that this document should =
cover
> > SLAAC, DHCPv6, and manual configuration. And hence this text was =
added.
> >
> > I don't mind removing the DHCPv6 text. However, if we do, we should
> > probably also remove the text about manual configuration. Otherwise =
it
> > is not clear why some forms of configuration are covered, but others =
are
> > not.
> >
>=20
> I argued for that because I think privacy is a primary property of an =
address, not the method used to configure it. However, since the =
different methods of configuring the address can effect the resulting =
address's privacy properties, I think it is necessary to discuss how to =
achieve privacy for the three different configuration methods we have in =
the one place.
>=20
>=20

As far as what the resulting privacy properties of an address are, I can =
see one overview document being useful. But I could see value in the =
scope of that being broader (to also cover, say, temporary addresses) =
and writing that after the separate specs about how to do configuration =
have stabilized, assuming the DHCP bit moves into 3315bis.

Alissa
> Regards,
> Mark.
>=20
> > Thanks,
> > --
> > Fernando Gont
> > SI6 Networks
> > e-mail: fgont@si6networks.com <mailto:fgont@si6networks.com>
> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org <mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 =
<https://www.ietf.org/mailman/listinfo/ipv6>
> > --------------------------------------------------------------------
>=20


--Apple-Mail=_849263CB-A4FA-4ABA-80BD-981C40CB278A
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 5, 2016, at 6:17 PM, Mark Smith &lt;<a href="mailto:markzzzsmith@gmail.com" class="">markzzzsmith@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div class=""><br class="webkit-block-placeholder"></div><p dir="ltr" class="">On 5 Aug 2016 22:42, "Fernando Gont" &lt;<a href="mailto:fgont@si6networks.com" class="">fgont@si6networks.com</a>&gt; wrote:<br class="">
&gt;<br class="">
&gt; On 08/04/2016 10:23 PM, Alissa Cooper wrote:<br class="">
&gt; &gt;<br class="">
&gt; &gt;&gt; On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) &lt;<a href="mailto:volz@cisco.com" class="">volz@cisco.com</a>&gt; wrote:<br class="">
&gt; &gt;&gt;<br class="">
&gt; &gt;&gt; Ole:<br class="">
&gt; &gt;&gt;<br class="">
&gt; &gt;&gt; (I fixed 6man mailing list address.)<br class="">
&gt; &gt;&gt;<br class="">
&gt; &gt;&gt; That is probably the best solution and I would support that.<br class="">
&gt; &gt;&gt;<br class="">
&gt; &gt;&gt; We can still discuss changing some of the text in 3315bis, but that can<br class="">
&gt; &gt;&gt; then be done without 6man involvement. (We do still have the older text in<br class="">
&gt; &gt;&gt; what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so should really<br class="">
&gt; &gt;&gt; clean that up.)<br class="">
&gt; &gt;<br class="">
&gt; &gt; I am fine with this solution and it seems cleaner.<br class="">
&gt;<br class="">
&gt; Background: At some point folks argued that this document should cover<br class="">
&gt; SLAAC, DHCPv6, and manual configuration. And hence this text was added.<br class="">
&gt;<br class="">
&gt; I don't mind removing the DHCPv6 text. However, if we do, we should<br class="">
&gt; probably also remove the text about manual configuration. Otherwise it<br class="">
&gt; is not clear why some forms of configuration are covered, but others are<br class="">
&gt; not.<br class="">
&gt;</p><p dir="ltr" class="">I argued for that because I think privacy is a primary property of an address, not the method used to configure it. However, since the different methods of configuring the address can effect the resulting address's privacy properties, I think it is necessary to discuss how to achieve privacy for the three different configuration methods we have in the one place.</p><div class=""><br class=""></div></div></blockquote><div><br class=""></div><div>As far as what the resulting privacy properties of an address are, I can see one overview document being useful. But I could see value in the scope of that being broader (to also cover, say, temporary addresses) and writing that after the separate specs about how to do configuration have stabilized, assuming the DHCP bit moves into 3315bis.</div><div><br class=""></div>Alissa<br class=""><blockquote type="cite" class=""><div class=""><p dir="ltr" class="">Regards,<br class="">
Mark.<br class=""></p><p dir="ltr" class="">&gt; Thanks,<br class="">
&gt; --<br class="">
&gt; Fernando Gont<br class="">
&gt; SI6 Networks<br class="">
&gt; e-mail: <a href="mailto:fgont@si6networks.com" class="">fgont@si6networks.com</a><br class="">
&gt; PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br class="">
&gt;<br class="">
&gt;<br class="">
&gt;<br class="">
&gt;<br class="">
&gt; --------------------------------------------------------------------<br class="">
&gt; IETF IPv6 working group mailing list<br class="">
&gt; <a href="mailto:ipv6@ietf.org" class="">ipv6@ietf.org</a><br class="">
&gt; Administrative Requests: <a href="https://www.ietf.org/mailman/listinfo/ipv6" class="">https://www.ietf.org/mailman/listinfo/ipv6</a><br class="">
&gt; --------------------------------------------------------------------<br class=""></p>
</div></blockquote></div><br class=""></body></html>
--Apple-Mail=_849263CB-A4FA-4ABA-80BD-981C40CB278A--


From nobody Tue Aug  9 12:22:32 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0CE312B060 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 12:22:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4d6r4PjsIVdf for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 12:22:28 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 43E0012D0C6 for <ipv6@ietf.org>; Tue,  9 Aug 2016 12:22:28 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id l203so30983120oib.1 for <ipv6@ietf.org>; Tue, 09 Aug 2016 12:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5vdIUUNkNXvfonzlelTBTqoetITpSJGN3BBDCBEtqgg=; b=esL40EovOPVxFTf6tMpV4HDaIpQ92WSyS1XUOvbpq1x3WpoTZvGrobpurlTuO3uK95 R+KJ1/nWv1uYjMOM33E6pIWYud2VyisXPdHT2rW6zBQjzVfs7J4mErOnoOjjW0Kg8gWP lNm7wEvYut0R1leHGb3hHqsKztyFlMuKUcIh5IccWjP816AMcQzhCJ0TlAUiQmykQGDM HsUUSTPx2XtNCUcbAA2ed7D5yh5gF2364d1sHfstm2I5lufpFGnnc+5K4SD8MavePiYq 6luLDzOr8xA3tfqfLky8XLG/10VY/k8dsC8X/yweF51mvMW3DdnBWBKRijvT54B0feHp FIHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5vdIUUNkNXvfonzlelTBTqoetITpSJGN3BBDCBEtqgg=; b=doQ+UEbjHHD4LFY8H4ui91uVLjb6s7YaNsBSXRrX0yh48jWsNTwA0x+L6IrRFy38+P TM6aIm3RWpRvw0oXvyxXZl5mUXMIuQmg+xwMosamjcJF6Ddu9c+LPpUycVgYIoCErKbb ltFEblgFmbxGTIM3iL5T3gyAcsFjTCO6B/EM+NBEgnyQVj+g87CLGWg50OJhrYr4UGw6 DsgmONe6W7f7nBEqdAxSFNoSl+D5wkIyWV0a8r38jxYyC0Gq9iCtWF7fgVjLktqEZqgG 2S49b4wGTAHBjd7g99IsklfqRQ5ZS5ynn9aD/j6eQ6RqBvaEG8XQ/zwem/VB5ujMykpF gnvg==
X-Gm-Message-State: AEkoouuIEwap7tckMEUxGGUlNxCI+bH1G0Qi/1ja08hspUv7rd8tFOMLNYdciUS/e7eOPL5v83aYDylmEFD3iQ==
X-Received: by 10.202.90.130 with SMTP id o124mr45133025oib.7.1470770547670; Tue, 09 Aug 2016 12:22:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Tue, 9 Aug 2016 12:22:27 -0700 (PDT)
In-Reply-To: <CAOSSMjXzapwWmL5KQ3vN_rr3FTVoFEJNDBvz3Y190po9JTuPqQ@mail.gmail.com>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <m1bX7rf-0000CtC@stereo.hq.phicoh.net> <CAOSSMjWhjY1ZnrSn8H6xMViiCOTJ97cOXGJDX+UFOd0U=pzO9g@mail.gmail.com> <CABdyVt6nGKG6dVqF84vR4gsdUb1m+zzjSL1c+dmtNR2fWUPTYQ@mail.gmail.com> <m1bX8cr-0000FUC@stereo.hq.phicoh.net> <CABdyVt4a+H24H-UbMVDec22_nQU9LE_H-AM=CtWBzbm3ORkABg@mail.gmail.com> <CAOSSMjXzapwWmL5KQ3vN_rr3FTVoFEJNDBvz3Y190po9JTuPqQ@mail.gmail.com>
From: Hemant Singh <hemantietf@gmail.com>
Date: Tue, 9 Aug 2016 15:22:27 -0400
Message-ID: <CABdyVt4iZRZ55SExUMVY+a9uC3g4Y9NT=bpTcY4ATO0SwV86MA@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Timothy Winters <twinters@iol.unh.edu>
Content-Type: multipart/alternative; boundary=001a113d59420a45960539a87480
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/k3TUdLmlbgmL8NTiedeOb8USShw>
Cc: IPv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 19:22:31 -0000

--001a113d59420a45960539a87480
Content-Type: text/plain; charset=UTF-8

Hi Tim,

Got it.   I agree the text in section 4.6.3 is inconsistent with the text
in section 8.2.   Section 8.2 is correct for text because the router has
completed the layer-3 forwarding lookup and it's during the layer-2
forwarding lookup, the IPv6 ND Neighbor Cache and the Destination cache are
available.  These caches tell the router the packet source is on-link and
the packet IP destination is not destined to the router nor is the packet
IP destination a multicast destination.  Thus, the router knows a Redirect
has to be issued.  At this juncture, the router has access only to the
forwarded packet.  The router copies the packet before forwarding and uses
the copy in the Redirect.

Hemant



On Tue, Aug 9, 2016 at 12:59 PM, Timothy Winters <twinters@iol.unh.edu>
wrote:

> Hi Hemant,
>
> So my question is which packet that triggers the Redirect.  A redirect is
> only transmitted after you forward the packet.  The issue is which packet
> gets copied into the Redirect message.  The originating packet or the
> forwarded packet?
>
> ~Tim
>
>
>
> --
>
> Now offering testing for SDN applications and controllers in our SDN
> switch test bed. Learn more today http://bit.ly/SDN_IOLPR
>

--001a113d59420a45960539a87480
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Tim,</div><div><br></div><div>Got it. =C2=A0 I agr=
ee the text in section 4.6.3 is inconsistent with the text in section 8.2. =
=C2=A0 Section 8.2 is correct for text because the router has completed the=
 layer-3 forwarding lookup and it&#39;s during the layer-2 forwarding looku=
p, the IPv6 ND Neighbor Cache and the Destination cache are available.=C2=
=A0 These caches tell the router the packet source is on-link and the packe=
t IP destination is not destined to the router nor is the packet IP destina=
tion a multicast destination.=C2=A0 Thus, the router knows a Redirect has t=
o be issued.=C2=A0 At this juncture, the router has access only to the forw=
arded packet.=C2=A0 The router copies the packet before forwarding and uses=
 the copy in the Redirect.</div><div><br></div><div>Hemant</div><div><br></=
div><div><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Tue, Aug 9, 2016 at 12:59 PM, Timothy Winters <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:twinters@iol.unh.edu" target=3D"_blank">twinters@iol.unh.ed=
u</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-le=
ft-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Hemant,<div=
><br></div><div>So my question is which packet that triggers the Redirect.=
=C2=A0 A redirect is only transmitted after you forward the packet.=C2=A0 T=
he issue is which packet gets copied into the Redirect message.=C2=A0 The o=
riginating packet or the forwarded packet?</div><div><br></div><div>~Tim</d=
iv></div><div class=3D"gmail_extra"><div><div><br><br clear=3D"all"><div><b=
r></div></div></div><span>-- <br><div data-smartmail=3D"gmail_signature"><d=
iv dir=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div=
 dir=3D"ltr">







<p><font face=3D"georgia, serif" size=3D"1">Now offering testing for SDN ap=
plications and controllers in our SDN switch test bed.=C2=A0</font><span st=
yle=3D"font-family:georgia,serif;font-size:x-small">Learn more today <a hre=
f=3D"http://bit.ly/SDN_IOLPR" target=3D"_blank">http://bit.ly/SDN_IOLPR</a>=
</span></p></div></div></div></div></div></div></div>
</span></div>
</blockquote></div><br></div></div>

--001a113d59420a45960539a87480--


From nobody Tue Aug  9 14:37:03 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5907212D185 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 14:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 N-_1ly_Ss0LR for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 14:36:59 -0700 (PDT)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::22e]) (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 53CA512D16D for <ipv6@ietf.org>; Tue,  9 Aug 2016 14:36:58 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id w38so12361059qtb.0 for <ipv6@ietf.org>; Tue, 09 Aug 2016 14:36:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=m9iCDtHy2+m/NfUh84GADI1hTlc3jsF1nAhv8TXLpTU=; b=VRt2W9FpR2Z5OQsNhcpI3cxfCaB0Ey8aDJhm/n+DdU1rVUOLKi2SXt4sUqrtXjMv8J P7Q7+G0P1NbNPgfInQZhUQcQ41VdYt80kQfnh9jnpJRKBb+v2seks2vpqeJftvFJlLzN w/rQjgBME8+SWLjIrCn7Cvyxx/znfqmNNsTa9uMymna/mrbN6XNtTAXbfz41niigs+O4 JimEVE2BD1a86wFq8Zks0KLyx9jWFyg0nB7m6VUbSr1ntTEzdlv0JFul/Dn1SLewNUGn WvmNAnaeFYZt7o3Fj+g3rDqqlDKMnxCP5VUCEB0zgsDYzAAPbMwXTHqZGIngI9ncwAIV 0nDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=m9iCDtHy2+m/NfUh84GADI1hTlc3jsF1nAhv8TXLpTU=; b=col/KtBZHNlW5QPb1dRuI8Mlg8JErwNOmFnlK955BfUySSGvb4zlaRLaM9xs+3jma/ hMT9ZVbl9dW4u/W9AupjSNGPkwCMJySDamybm561Zevh+ZhSOf2VByfMxpRwAUBQYnEb v71/gOx2cnJuTwvNSzVoI5Y7hsSH9YJCOMJYMl6cfgvpDsoAhWZTAJ7lEPwAzDrh9cSv P9Igz9mE9B/Gu9bj6r9DVdCSnid/oWbJ9uby6o7m7bV09dMeYxf1r9o8O/PDpN2r8EHC EFalpESxD7F3u5qacbJKxxDyzZrCdoeBudBkpGI4h/Cv4G/DpbG3iitdjBNgrtpsPe6P i2SQ==
X-Gm-Message-State: AEkooutGWPqaNk6NhtWB9Bx2xt7psMCW0hXLsPpNYd6+G51BIgFxo7AKKIoXg64GIZOsoARvLlkWEVS4tOArnw==
X-Received: by 10.200.35.108 with SMTP id b41mr650893qtb.142.1470778617492; Tue, 09 Aug 2016 14:36:57 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Tue, 9 Aug 2016 14:36:56 -0700 (PDT)
In-Reply-To: <7F95C173-2110-4540-9C1C-8124FB17B04B@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com> <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in> <CAJE_bqdLQLeApRVedfMt0q0YK1nnVvXkm9jYifpx-Ruh3jadLQ@mail.gmail.com> <7F95C173-2110-4540-9C1C-8124FB17B04B@cooperw.in>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Tue, 9 Aug 2016 14:36:56 -0700
X-Google-Sender-Auth: HGx_9-DPEvZRC11_ZzY1zciE1Zs
Message-ID: <CAJE_bqf0X_YBHUGhwrvznwt5Y3KcMAa6KKns7HZ2mKDp0Lukag@mail.gmail.com>
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/smmMf6OMc2dXUDQ9qSWxSq_DpW0>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 21:37:00 -0000

At Tue, 9 Aug 2016 11:42:37 -0700,
Alissa Cooper <alissa@cooperw.in> wrote:

> > To rephrase my point, it's about what are "nodes that do not follow
> > these recommendations".  If my memory was correct, one of the
> > pushbacks came from people developing routers who don't even bother to
> > implement RFC7217 and just want to use EUI-64 based IID as before
> > since they have no privacy related concern in doing so.  I thought
> > "nodes that do not follow these recommendations" in Option 1 cover
> > these cases (among other cases like nodes that don't need stable
> > addresses), and if so, those people won't even be happy if the SHOULD
> > in Section 3 applies to their case.
>
> Then those people don=E2=80=99t know what SHOULD means. In fact, =E2=80=
=9Cif the
> SHOULD =E2=80=A6 applies in their case=E2=80=9D is not really a meaningfu=
l
> construction. The whole point of using SHOULD is to acknowledge that
> there are exception cases. There is no thought police running around
> judging the reasons why a specific implementor will choose to follow
> the recommendation or not.

I disagree - with that logic that can even be a MAY.  There's
certainly a difference in nuance between SHOULD and MAY, and while a
SHOULD violation may give some room for excuse, it's more likely to
lead to events that implementers don't like such as customer
escalation.

That said, since no one else seems to be concerned about this point,
perhaps they are now just okay with applying this document to all
nodes (module the subtle difference between MUST and SHOULD).  In that
case that's fine to me.  As I already said I myself have no steak or
opinion on this point.

--
jinmei


From nobody Tue Aug  9 16:26:28 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B971912D8E9 for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 16:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 R3gwOtXZE-Rf for <ipv6@ietfa.amsl.com>; Tue,  9 Aug 2016 16:26:11 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 C5A1212D8E1 for <ipv6@ietf.org>; Tue,  9 Aug 2016 16:26:10 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id c15so38517245oig.0 for <ipv6@ietf.org>; Tue, 09 Aug 2016 16:26:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tJbql2KBKqkVghSgJniBfPwmSKbCSvM36orWAEUMDUI=; b=JJovdf0AjAqkZFz7JT7NlXSHFdDzmPCIhYYKrCx0o5LlZaEYoRuot5j3RT3jeA3VzK IUDATRnj/f1dcnkp83/ttfbDKRFhZO083Uhygbzcvu/cnwXU9Us6G2xnkMz6OWqzoBf/ vsMtRW8EIslLCzc0g38EhxVvQaaj7ntC63+H/4FOLSm56XJ3YFvSeQsffhwTTJbbZv3y ExoNRBI7ImFwz5V322YixyNtfd/NnbU0iMr5NaZyFErokWu7IesUI0aidjFTYHfMQwIh h4+Zzv8rk0ajf9U+zV52AM+KsyxaF24qrHczg2/3sACtwBAdWBGcim6pK6uz3+YKtPw7 7snQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tJbql2KBKqkVghSgJniBfPwmSKbCSvM36orWAEUMDUI=; b=ADRyjUlFo9cWkNM21P+VSNPeJehdmmW8z2Vk5QzEymIQIUa5Tx7EeAnBOemeH2RGhZ KxqHhTevcsVAx43wMsi9Gm1wwYgSevk7jaFHnToMSZJt55SXpqo4xm5RLRyXOdGjkCfM fYkV3TF9p4PbgDIPVd0s5cMuLsWCsZ4TiJZ0vTAqpjGSavWDxAZGY4ppCKUVlKxS7O2U H0F4O0VJ5PmmBibOoq+UDUahodVN6YCzZcBNrY0drFAsLZBq+xfu65a+dD86EmSQaMxm 95HbGIoRz2qqKkbxbbqQRVGuTUU/qNOB0NnJuTXfWmdNgZajyseP9jmqY/Zwhj+AknZY BhcA==
X-Gm-Message-State: AEkoousLlAWpbg6GakJAK+5br43CgzUsHN+D+3LMxKvz46Gp/4N7AZOqAFI8xxsFfY8HihtnCcabI3NBx0sYRw==
X-Received: by 10.157.20.182 with SMTP id d51mr465264ote.61.1470785170198; Tue, 09 Aug 2016 16:26:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Tue, 9 Aug 2016 16:26:09 -0700 (PDT)
In-Reply-To: <7F95C173-2110-4540-9C1C-8124FB17B04B@cooperw.in>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org> <CAJE_bqc2z5aEx_X=KRJ3iFia6Z8FHOhzZE3DWBXz0csKAovERQ@mail.gmail.com> <7E28E9D3-B2B3-41F2-87D2-5BA368B1852A@cooperw.in> <CAJE_bqfA769Ze+jmQ5NdpTXM4ybeFBuJJHn6VG_06c2fRcyOfQ@mail.gmail.com> <D15D54AC-45C6-45A8-A6B4-7612F63DA64F@cooperw.in> <CAJE_bqdLQLeApRVedfMt0q0YK1nnVvXkm9jYifpx-Ruh3jadLQ@mail.gmail.com> <7F95C173-2110-4540-9C1C-8124FB17B04B@cooperw.in>
From: Hemant Singh <hemantietf@gmail.com>
Date: Tue, 9 Aug 2016 19:26:09 -0400
Message-ID: <CABdyVt7hO+5YMKMi1izvF_BRU_dpjxdkEMd32VPaqoYg1b8sBQ@mail.gmail.com>
Subject: Re: default-iids Section 3 clarity (was Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13)
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary=001a11463c569c55ce0539abdb91
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gy9YGldL9QMp2FKZE7fvVlg0fGs>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 23:26:13 -0000

--001a11463c569c55ce0539abdb91
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I agree with Jinmei.  See an example for each from RFC 4861.  The text is
included between squared brackets below.

[3) Senders MAY send a subset of options in different packets. For instance=
,
if a prefix's Valid and Preferred Lifetime are high enough, it might not be
necessary to include the Prefix  Information option in every Router
Advertisement.]

[A router SHOULD send a redirect message, subject to rate limiting, wheneve=
r
it forwards a packet that is not explicitly addressed to itself]

Hemant

On Tue, Aug 9, 2016 at 2:42 PM, Alissa Cooper <alissa@cooperw.in> wrote:

>
>
> Then those people don=E2=80=99t know what SHOULD means. In fact, =E2=80=
=9Cif the SHOULD =E2=80=A6
> applies in their case=E2=80=9D is not really a meaningful construction. T=
he whole
> point of using SHOULD is to acknowledge that there are exception cases.
> There is no thought police running around judging the reasons why a
> specific implementor will choose to follow the recommendation or not.
>
> Thanks,
> Alissa
>
>

--001a11463c569c55ce0539abdb91
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree with Jinmei.=C2=A0 See an example for each from RF=
C 4861.=C2=A0 The text is included between squared brackets below.=C2=A0<di=
v><br></div><div>[<span style=3D"color:rgb(0,0,0);font-size:13.3333px">3) S=
enders MAY send a subset of options in different packets.  For=C2=A0</span>=
<span style=3D"color:rgb(0,0,0);font-size:13.3333px">instance, if a prefix&=
#39;s Valid and Preferred Lifetime are high=C2=A0</span><span style=3D"colo=
r:rgb(0,0,0);font-size:13.3333px">enough, it might not be necessary to incl=
ude the Prefix =C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13.33=
33px">Information option in every Router Advertisement.</span>]</div><div><=
br></div><div>[<span style=3D"color:rgb(0,0,0);font-size:13.3333px">A route=
r SHOULD send a redirect message, subject to rate limiting,=C2=A0</span><sp=
an style=3D"color:rgb(0,0,0);font-size:13.3333px">whenever it forwards a pa=
cket that is not explicitly addressed to </span><span style=3D"color:rgb(0,=
0,0);font-size:13.3333px">itself</span>]</div><div><br></div><div>Hemant</d=
iv><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, A=
ug 9, 2016 at 2:42 PM, Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:alissa@cooperw.in" target=3D"_blank">alissa@cooperw.in</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204=
,204);padding-left:1ex"><div class=3D""><div class=3D"h5"><br><br>
</div></div>Then those people don=E2=80=99t know what SHOULD means. In fact=
, =E2=80=9Cif the SHOULD =E2=80=A6 applies in their case=E2=80=9D is not re=
ally a meaningful construction. The whole point of using SHOULD is to ackno=
wledge that there are exception cases. There is no thought police running a=
round judging the reasons why a specific implementor will choose to follow =
the recommendation or not.<br>
<br>
Thanks,<br>
Alissa<br>
<div class=3D""><div class=3D"h5"><br></div></div></blockquote></div></div>=
</div></div>

--001a11463c569c55ce0539abdb91--


From nobody Tue Aug  9 20:30:03 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6874C12D104; Tue,  9 Aug 2016 20:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 c105OIIs9mX6; Tue,  9 Aug 2016 20:30:01 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78FE812B010; Tue,  9 Aug 2016 20:29:58 -0700 (PDT)
X-AuditID: c618062d-980fb98000000a08-70-57aaa055addc
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id 19.83.02568.550AAA75; Wed, 10 Aug 2016 05:32:37 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0301.000; Tue, 9 Aug 2016 23:29:31 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "draft-ietf-6man-ipv6-mibs-obsolete.all@ietf.org" <draft-ietf-6man-ipv6-mibs-obsolete.all@ietf.org>
Subject: AD evaluation: draft-ietf-6man-ipv6-mibs-obsolete
Thread-Topic: AD evaluation: draft-ietf-6man-ipv6-mibs-obsolete
Thread-Index: AdHyt2fNo+KurI0/TEG3ywNlGJG1TA==
Date: Wed, 10 Aug 2016 03:29:30 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E088A4@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrILMWRmVeSWpSXmKPExsUyuXRPrG7oglXhBu83SFvs3NfHZvHy7Hsm ByaPJUt+MgUwRnHZpKTmZJalFunbJXBlrHk+laXgC2PFvUlTWBoYDzN2MXJySAiYSEz60cve xcjFISSwgVFixdQpbCAJIYFljBLL31qC2GxARRt2fmYCsUUEMiU2320Hs5kFtCRWv/7PCmIL C1hJzNt4mhmixl6i69BpNghbT+Lf9k6wGhYBVYnN6z4DxTk4eAV8JZY1mYCEGQXEJL6fWgM1 Ulzi1pP5TBC3CUgs2XOeGcIWlXj5+B8rhK0kMef1NWaIeh2JBbs/sUHY2hLLFr4Gi/MKCEqc nPmEZQKj8CwkY2chaZmFpGUWkpYFjCyrGDlKiwtyctONDDYxAgP6mASb7g7G+9M9DzEKcDAq 8fAqSK0KF2JNLCuuzD3EKMHBrCTC6zIHKMSbklhZlVqUH19UmpNafIhRmoNFSZxX7JFiuJBA emJJanZqakFqEUyWiYNTqoHRs/L4vFmRemvuiOx4Vq17OmAOu1G+0bvd3fYXgoql/m3xTDjX /OEV80YJ9fZ3xkVLO0OK0x/9qs4V4b8s/+jw6YjTz5b6vUw43nnsMUvRj3MJr36G/S8Me7ch 99NrXTGTtg9Pdi0uD93Es0x7Q2Lck9zyC49aSpylZ/hM4Oc7o9bLX/p9qvEaJZbijERDLeai 4kQAC/Im1GQCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wOcKl9yofoFB_v-gDml1Y5iL_bU>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 03:30:02 -0000

Hi all,=0A=
   I have gone through draft-ietf-6man-ipv6-mibs-obsolete and have not foun=
d =0A=
any issues that prevent the draft from progressing. I have sent the draft =
=0A=
into IETF Last Call.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Wed Aug 10 00:55:11 2016
Return-Path: <rejithomas.d@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7670512B026 for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 00:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0xuCha9koEtq for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 00:55:09 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 23762128B44 for <ipv6@ietf.org>; Wed, 10 Aug 2016 00:55:09 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id x185so36028199qkc.2 for <ipv6@ietf.org>; Wed, 10 Aug 2016 00:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=ttrgwrZTp+Hr7nD+2SWHQEw6ZksJXUcplx/odRadP/c=; b=1JEOPYo7VOxLQQdpcjSOIvFZaVlPlD5rdiHNSvrOv/tKx1ohD9/fiJPetB3dgdUxZH AuvZKS5jGyfxm1/Elag6NO819+5ZY1olwnnCXxkX+Ka4JoVk1ZJH4Dc/XcFZU6Yf9Byk HjRG/YDDkqYaDAPLESsdAxP7XsGuc/muZtd6qK4pCYZD68yUk4WrclqP2Mfi/W+ztAMv itPwWdVqZKDg7vaze4bvzLLIBXiTV9HY4V+LQ0wFD07o0/XXZG0XMvmb4wTNUiGlYQZg 9Hjl7+WuQO3C0AaLnjxXrZAQMXdbxrpfGqovSTwpThGfI4vZPWwA62PqD/sypmOzWoYo QtuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ttrgwrZTp+Hr7nD+2SWHQEw6ZksJXUcplx/odRadP/c=; b=iugYsVJx8C/Agw8uA5JwdIPupdo7uo5LXc8T4L0FtjdSGnRkf9C2Xb1Jm1k1sNmYlH vMTE+H7CgXZexq/gpEpOTZ1pu149ry1RCzRyERtT7fjIFaASkULyLEbcs34F0EuywRfR R2Mpf6X6OtFcisG7+xG4cJ78xFfl4r7Bm9xDipMVxVeBt4vGXd5z+PDYv+TIgAot9BFo gj9AQdhw6sst/YAznva4u/mMROEoCISqz4judfoMpuZ2w/a6/h0IjOG8piufnog6iDAh z37IT2BmeEb8Ue3lgxa8n3+UB+T3lzPexrjU9+Ht50QeuWGtbGfL14znzK3KOcWJUQY3 Ytgw==
X-Gm-Message-State: AEkoousCMOaEUMfEqyqr0woRUZrDSSLpdWcj907qpm6Kq5xx2AXvaxTBRmnY1jLWO3d5kK69pROefeqQzn7Lxg==
X-Received: by 10.55.170.1 with SMTP id t1mr2866358qke.42.1470815708286; Wed, 10 Aug 2016 00:55:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.17.27 with HTTP; Wed, 10 Aug 2016 00:55:07 -0700 (PDT)
From: Reji Thomas <rejithomas.d@gmail.com>
Date: Wed, 10 Aug 2016 13:25:07 +0530
Message-ID: <CAA8Zg7HO1rLDpy=5OkrHpedsbx0Wm+j4XmfLVm8OAXG4HwqGMQ@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: ipv6@ietf.org, hemantietf@gmail.com, twinters@iol.unh.edu
Content-Type: multipart/alternative; boundary=001a114d431ed292340539b2f7a0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/jP9qPT5QuazFaW3xq77874pqYHs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 07:55:10 -0000

--001a114d431ed292340539b2f7a0
Content-Type: text/plain; charset=UTF-8

Hi,

>>Thus, the router knows a Redirect has to be issued.  At this juncture, >>the router has access only to the forwarded packet.  The router copies >>the packet before forwarding and uses the copy in the Redirect.

This doesn't have to mean that routers would have done the layer3
header processing for forwarding .In fact the same is an
implementation specific behaviour i.e. hlim could be adjusted only
when the packet is forwarded and not when redirect is triggered. The
only significance of the text as I see is when to send the redirect
and not on whether its the originating packet or the redirect packet
that needs to be included in the redirect header.


As Hemant pointed out, the packet payload is included in icmpv6 error
messages also and sec 2.4 of RFC 4443 describes the intent and is
inline with V4 redirect where the intent is spelt rather specifically.
Unless I see a specific reasoning for including the packet after doing
the forward processing, I would think it as immaterial and  conclude
as reading too much into the text for that matter.


Regards

Reji

--001a114d431ed292340539b2f7a0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div><pre class=3D"" style=3D"margin-bot=
tom:0px;padding:0px;border:0px;font-family:Courier,&#39;Courier New&#39;,mo=
nospace;font-size:13px;line-height:inherit;vertical-align:baseline;white-sp=
ace:pre-wrap;word-wrap:break-word;color:rgb(0,0,0)">&gt;&gt;Thus, the route=
r knows a Redirect has to be issued.  At this juncture, &gt;&gt;the router =
has access only to the forwarded packet.  The router copies &gt;&gt;the pac=
ket before forwarding and uses the copy in the Redirect.</pre><pre class=3D=
"" style=3D"margin-bottom:0px;padding:0px;border:0px;font-family:Courier,&#=
39;Courier New&#39;,monospace;font-size:13px;line-height:inherit;vertical-a=
lign:baseline;white-space:pre-wrap;word-wrap:break-word;color:rgb(0,0,0)">T=
his doesn&#39;t have to mean that routers would have done the layer3 header=
 processing for forwarding .In fact the same is an implementation specific =
behaviour i.e. hlim could be adjusted only when the packet is forwarded and=
 not when redirect is triggered. The only significance of the text as I see=
 is when to send the redirect and not on whether its the originating packet=
 or the redirect packet that needs to be included in the redirect header.</=
pre><pre class=3D"" style=3D"margin-bottom:0px;padding:0px;border:0px;font-=
family:Courier,&#39;Courier New&#39;,monospace;font-size:13px;line-height:i=
nherit;vertical-align:baseline;white-space:pre-wrap;word-wrap:break-word;co=
lor:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"margin-bottom:0px;paddin=
g:0px;border:0px;font-family:Courier,&#39;Courier New&#39;,monospace;font-s=
ize:13px;line-height:inherit;vertical-align:baseline;white-space:pre-wrap;w=
ord-wrap:break-word;color:rgb(0,0,0)">As Hemant pointed out, the packet pay=
load is included in icmpv6 error messages also and sec 2.4 of RFC 4443 desc=
ribes the intent and is inline with V4 redirect where the intent is spelt r=
ather specifically. Unless I see a specific reasoning for including the pac=
ket after doing the forward processing, I would think it as immaterial and =
 conclude as reading too much into the text for that matter.</pre><pre clas=
s=3D"" style=3D"margin-bottom:0px;padding:0px;border:0px;font-family:Courie=
r,&#39;Courier New&#39;,monospace;font-size:13px;line-height:inherit;vertic=
al-align:baseline;white-space:pre-wrap;word-wrap:break-word;color:rgb(0,0,0=
)"><br></pre><pre class=3D"" style=3D"margin-bottom:0px;padding:0px;border:=
0px;font-family:Courier,&#39;Courier New&#39;,monospace;font-size:13px;line=
-height:inherit;vertical-align:baseline;white-space:pre-wrap;word-wrap:brea=
k-word;color:rgb(0,0,0)">Regards</pre><pre class=3D"" style=3D"margin-botto=
m:0px;padding:0px;border:0px;font-family:Courier,&#39;Courier New&#39;,mono=
space;font-size:13px;line-height:inherit;vertical-align:baseline;white-spac=
e:pre-wrap;word-wrap:break-word;color:rgb(0,0,0)">Reji</pre></div></div>

--001a114d431ed292340539b2f7a0--


From nobody Wed Aug 10 01:16:50 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A924D12D12F; Wed, 10 Aug 2016 01:16:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 WmwZTcMbO4mS; Wed, 10 Aug 2016 01:16:40 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E4912D123; Wed, 10 Aug 2016 01:16:39 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Aug 2016 08:16:36 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id DA2BE9CC51; Wed, 10 Aug 2016 01:16:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=32g7AfmxmYtgsXmBo7D3yVbjY8M=; b= ifDW+G/Q2mrIWv6Vd4Lv9qVZPqYL5eDGORReWV1dcy9irq6QEtil9d9w0UAKx/wT eMO5Vn30Sg5otUhRKxbI2mAFeRigWldMbjiVZWDMPCrLcQVk/1xwO6Fx5if4BpmK VNmF2yASfYz9emobEqVb2qdcWPeRs4n8uuiYN77Ytqs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=b77E5eW7OVR+YLT4+iqPom4m4P 5Ib5e7JJRgEStwty/CZ4kPe1arSx4UyY7Crk+0HycpokfpKrkjBnBXrLve8xCbpM EgrdasxnFooL2HEGC326YPdUNW8Bk9fXIQ9c2gqlJ047s3Mqcsud+V9QAA6sunXB n1x26AFFI+awTjwEw=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 8F2E89CC4F; Wed, 10 Aug 2016 01:16:35 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 31376311D184; Wed, 10 Aug 2016 10:16:33 +0200 (CEST)
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_52604314-412F-43C1-BC26-C3093EF2C3E5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
Date: Wed, 10 Aug 2016 10:16:32 +0200
Message-Id: <A3200A86-B59B-4AD4-9CF2-D2C7F50AE4C8@employees.org>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8ikAOo-Lqjrt4LbKYaPQSAzsp6s>
Cc: 6man WG <ipv6@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Fernando Gont <fgont@si6networks.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 08:16:42 -0000

--Apple-Mail=_52604314-412F-43C1-BC26-C3093EF2C3E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark,

[...]

> I argued for that because I think privacy is a primary property of an =
address, not the method used to configure it. However, since the =
different methods of configuring the address can effect the resulting =
address's privacy properties, I think it is necessary to discuss how to =
achieve privacy for the three different configuration methods we have in =
the one place.

And you don't think RFC7721 is enough?

Cheers,
Ole

--Apple-Mail=_52604314-412F-43C1-BC26-C3093EF2C3E5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXquLhAAoJED4aXnjSQuKWflYH/00Apy63wxW5M7+xMr/MeqOK
Qyh1VLpcuZgQ6DwY7MoVtFknJt1+RaDeLbR1VEt+dYWpd3NPGtXrOZ/vqTW6AoEJ
mCqiGlVI/7Te6XPFJH8wH1L9KfEX+WX6IrZ/CZhR3Q/2mayBrysPl+13roVYpXZI
NwPNLmBqkU1BhpRWhvOzY4pFUKwlJKmu0fqyW61kBikG5XH7vhf+OkYLMWUY3vw8
FYZ1wJ8wB6JelJ6TPCN8zIt/a6NtTuvv671bv1n15v+x0AywcCPXPPSvYT/SdVyO
qnTUoBFpmPxm6TYuu2CCVDr9o3Lzyzo/NGmofz4IuzOH20ztlASObmy9A8zQUpU=
=sLai
-----END PGP SIGNATURE-----

--Apple-Mail=_52604314-412F-43C1-BC26-C3093EF2C3E5--


From nobody Wed Aug 10 01:29:21 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0170D12D187 for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 01:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 gaftYnvFXGJz for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 01:29:17 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D23B12D0A1 for <ipv6@ietf.org>; Wed, 10 Aug 2016 01:29:14 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Aug 2016 08:29:13 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id A7B119CC4F; Wed, 10 Aug 2016 01:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=ji1lxkeuZn+uR15pCI3AMGnuYnU=; b= XywgYPUICZC6blPBbk+cU0RU8UuPJW0tQeNzAw6hb3BHHtHc3itmRz0RoHJ5DUQP zCWNAxnztBiZU2uwZHcB+7iZYaYIAlLfkVTa2L2OjuDp0pOMb+ulnZICnkGVcBNQ i/LXh71Liu4KpjY6YFn4e+12p9cWyhD2LKAP9L04NsE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=lLNpqzflhEmriZaTJiHlU/mj9M KWow6DVLk0+t9iFAGuAqNoQVNXV7ki3CYNzVrPJ0qH4WHDAoQuB0vg3fNJ+xyboW 0vhSagq2MjEF+nt5kqQEdpDinocf5MkQCkhkgSF2G0SHlNkApgj1czYOzuDwuAG0 IosqdWdXl+e9rbGFc=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 626569CC4E; Wed, 10 Aug 2016 01:29:12 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8BEDF311D58A; Wed, 10 Aug 2016 10:29:10 +0200 (CEST)
Subject: Re: Redirected Header (Forwarded/Originating Packet)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_158084EC-FD3D-4E98-80CE-678311330F36"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com>
Date: Wed, 10 Aug 2016 10:29:09 +0200
Message-Id: <20D21BAF-29DD-47FB-9E32-02DDDC2D9F25@employees.org>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qGwjyWxuORHrtFnBxhRs3cBHxas>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 08:29:19 -0000

--Apple-Mail=_158084EC-FD3D-4E98-80CE-678311330F36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Tim,

I think it is implementation dependent.
It depends on where in the forwarding path the redirect check is done in =
relation to the hop limit decrement.

Best regards,
Ole


> On 09 Aug 2016, at 15:14, Timothy Winters <twinters@iol.unh.edu> =
wrote:
>=20
> Hello,
>=20
> The UNH-IOL has seen several different implementations with varied =
interpretations the following line from RFC 4861 Section 8.2 regarding =
what should be included in the Redirect Header of an ICMPv6 Redirect =
message.
>=20
> "Redirected Header: as much of the forwarded packet as can
>              fit without the redirect packet exceeding the minimum MTU
>              required to support IPv6 as specified in [IPv6]."
>=20
> My interpretation has been that the redirected header should be the =
forwarded packet, not the originating packet.   Recently we've seen =
Linux based routers use   the originating packet.
>=20
> My guess is they read this line from RFC 4861 Section 4.6.3
> The original packet truncated to ensure that the
>                      size of the redirect message does not exceed the
>                      minimum MTU required to support IPv6 as specified
>                      in [IPv6]."
>=20
> The reason that I'm asking is we have seen host that don't process the =
Redirect message unless it's the forwarding packet.   I want to make =
sure that we are telling implementations the correct behavior.
>=20
> ~Tim
>=20
> --
> Now offering testing for SDN applications and controllers in our SDN =
switch test bed. Learn more today http://bit.ly/SDN_IOLPR
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_158084EC-FD3D-4E98-80CE-678311330F36
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXquXWAAoJED4aXnjSQuKWXFEIAIEAx43AyTGkKaMPAKPWfb7i
+0Bv/n9Zw5iv533UPKza0W9mXn7AO0LuurS7N4kDXpA8OukbxEjh2Q3ceRBc6Rop
D2jlGiO/dNIS+ZFKomYVM7jPLynNW7l5rnFAX4gxfwsCZTWz9GfE2cmJ/uYfNJ/5
4HqxiMHBCkqx2r7fEeEYIa2VKTAyslldlMKqrjSLOW7a4X6KbwnNtMwwUgIrIKId
sjg9vKw2ziGrrh7xygvWpPoQ4xOG90Kvtcyu7epUDxW+//M82YJVq1ltZKUnFyMK
YPTxIicGaI18Mx8l66wX4vcErqZ+WY9CvxhP/21P+ZkjtYcBHZ2jKirLcKBdpvk=
=6Sfe
-----END PGP SIGNATURE-----

--Apple-Mail=_158084EC-FD3D-4E98-80CE-678311330F36--


From nobody Wed Aug 10 01:29:37 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B3712B014; Wed, 10 Aug 2016 01:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Sdmw3MDZCP31; Wed, 10 Aug 2016 01:29:27 -0700 (PDT)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (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 70A7612D1B8; Wed, 10 Aug 2016 01:29:27 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id n59so57978262uan.2; Wed, 10 Aug 2016 01:29:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=TeXgGsXWh9hTA4mzttn/0wEG/LY3UnxWpvQVKv9EOtE=; b=cpLWWsJdXdIRVGI2ZdomjggxoamtBSpqybXtsQWx61gHqwcwseVd4mjHk4eS1HiZHc z33mQwucmZS1zEjP/J0UOu6DproGofSoBPaHJ4FtW/dkAfeftmxH5a0tsLtddV5ckxnJ zo5MP9957J4D4xdbnCVmyKOX/zzzAFE873xdvHZnikNGyYDSPhV6/Sc3b30Sqx+/lyal sV8Fa8QJGiuS4mpe1bh3h97XdMbJLTtyd3fcwhRvDE6kFXduou2HkM1g6s55CxxKwZRt +gRg84N11HepomNqYSfCoM4/TB1J0egUm2epF3j49XZceUAoQUemWu4IWQyMa2juv+Sk qOxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=TeXgGsXWh9hTA4mzttn/0wEG/LY3UnxWpvQVKv9EOtE=; b=fODZF8f6WhtZWF3fm/EsNv1Tn7JD2cbB4DzBXPUFmNVucJHEn6uxK8ojAaqXCkFhPt 0TTUFxHSZFFxT9w3LoKpa19pxtQc5b+NGsRyE3XQkWQWi+vY9r0HFShwZ1rPKiVvCnyz UPgY1KnoEIps38hGB1+lH8fHh+s1oh+BTsjzO7YHXzZA/0Giu+G8ISBTt1qJB6U1CmDd Db2q874I0WDtQ88dRC0t4j2ZloUUZRj1zh22VKcokdOU4H2bb5Q0EQ92SXfQGhmiXmp5 9XXBKP3uJM7UtzqL+bJ9rUfV6GKDwgf/kr1JDNVf2lo0M0r2tn6TLkybkYSYKkk1kqu7 srYQ==
X-Gm-Message-State: AEkoousVLaQcM60AGohRNKZIPAKV+PKd/H/HVxlUvPKBpiUSaAP2SwbTMJmoWJ4uy+/OiB8vLTE8y08XU9HWsA==
X-Received: by 10.176.0.211 with SMTP id 77mr1348456uaj.75.1470817766578; Wed, 10 Aug 2016 01:29:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Wed, 10 Aug 2016 01:28:56 -0700 (PDT)
In-Reply-To: <A3200A86-B59B-4AD4-9CF2-D2C7F50AE4C8@employees.org>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com> <A3200A86-B59B-4AD4-9CF2-D2C7F50AE4C8@employees.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 10 Aug 2016 18:28:56 +1000
Message-ID: <CAO42Z2yaLjBesCFRqYVZ10Vm0W+HMtNRXj+bPYqOQYm3zVqEmA@mail.gmail.com>
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Kds_yy4DjRiuhrMC4GI-2vsTqvE>
Cc: 6man WG <ipv6@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Fernando Gont <fgont@si6networks.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 08:29:30 -0000

On 10 August 2016 at 18:16,  <otroan@employees.org> wrote:
> Mark,
>
> [...]
>
>> I argued for that because I think privacy is a primary property of an ad=
dress, not the method used to configure it. However, since the different me=
thods of configuring the address can effect the resulting address's privacy=
 properties, I think it is necessary to discuss how to achieve privacy for =
the three different configuration methods we have in the one place.
>
> And you don't think RFC7721 is enough?
>

Yes, got this draft and that RFC mixed up! I think I missed that RFC
getting published, which is why I thought that sort of text was in a
draft somewhere.

Apologies for the noise!

Regards,
Mark.



> Cheers,
> Ole


From nobody Wed Aug 10 04:12:54 2016
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE7312D75B for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 04:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=iol.unh.edu
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 1ZJlEJtMjbJq for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 04:12:51 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 1A9AA12D6AC for <ipv6@ietf.org>; Wed, 10 Aug 2016 04:12:51 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id t7so39624313qkh.0 for <ipv6@ietf.org>; Wed, 10 Aug 2016 04:12:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AGaXGsQDa1bsDzeU1wO8WbBYSeU+/NmX4PgX/4lOoPM=; b=cP8fG4deYi63AJv/rC2wT06uT1ozYwTyP7/6I+jTP+x3lafxVWvDS5OhPq7pZCe/d/ 2/hDJI38YXQZKjCvwNt8BI3HDNpQlhRD2FafcCRad76NesZY8QO3iaeaBvMpnSj/23zZ +ae7JB53/E73dESo/qvMCImp7lL0pQSecC79o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AGaXGsQDa1bsDzeU1wO8WbBYSeU+/NmX4PgX/4lOoPM=; b=hQFYsCVWbGmqSmSF/M913mQYnt90wBG+sEfTsnVYWdaldkvArOgSwmHPEclujWJCD5 oD+57OCZr4tonvr1MVAsdVPPZJr9Q5kqGdxkRX4jxav1XdAlzVB8XAdDYLzd4c2j012a pKKvSgvICO6glXsF6w9WX9TsCMn8mkM9rcQ0rt0KJpC+DI9r05hzmbYSIdWnmywLjQd/ cyvjgapi48jth790sTMRucaCHXymauSWv25mcfgwsCNcAMgobo+gbeoBBPjIVp23uv8d 5943GLfmlUoq+V5LgtbuenoKWswCx71TM+1rRiguw+b2hcIrHvccuAPoAtJ+fTnniL2r 2rkA==
X-Gm-Message-State: AEkoouuM82wufPioeEkV00ANZJbWJajj/6lTUk6pKSBiqHhTE+gdXmraIWixrArItb28PzZK+mHmQtNlNYAfjtIH
X-Received: by 10.55.197.22 with SMTP id p22mr3527958qki.200.1470827570199; Wed, 10 Aug 2016 04:12:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.58.202 with HTTP; Wed, 10 Aug 2016 04:12:49 -0700 (PDT)
In-Reply-To: <20D21BAF-29DD-47FB-9E32-02DDDC2D9F25@employees.org>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <20D21BAF-29DD-47FB-9E32-02DDDC2D9F25@employees.org>
From: Timothy Winters <twinters@iol.unh.edu>
Date: Wed, 10 Aug 2016 07:12:49 -0400
Message-ID: <CAOSSMjUqhkpyT8SWKWRQqHFxDOMd=YQUc7UwFnVPKLWMHUF2SQ@mail.gmail.com>
Subject: Re: Redirected Header (Forwarded/Originating Packet)
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a1149aec8d91aa10539b5ba74
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qXD7KyrDVoadp3vClH5mL-NlPgY>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 11:12:53 -0000

--001a1149aec8d91aa10539b5ba74
Content-Type: text/plain; charset=UTF-8

Hi Ole,

If this is true, either packet is ok to put in the Redirected Header from
the router point of view.   Based on that Host receiving redirects
shouldn't be dropping them depending on what's in the Redirected Header?

~Tim

On Wed, Aug 10, 2016 at 4:29 AM, <otroan@employees.org> wrote:

> Tim,
>
> I think it is implementation dependent.
> It depends on where in the forwarding path the redirect check is done in
> relation to the hop limit decrement.
>
> Best regards,
> Ole
>
>
> > On 09 Aug 2016, at 15:14, Timothy Winters <twinters@iol.unh.edu> wrote:
> >
> > Hello,
> >
> > The UNH-IOL has seen several different implementations with varied
> interpretations the following line from RFC 4861 Section 8.2 regarding what
> should be included in the Redirect Header of an ICMPv6 Redirect message.
> >
> > "Redirected Header: as much of the forwarded packet as can
> >              fit without the redirect packet exceeding the minimum MTU
> >              required to support IPv6 as specified in [IPv6]."
> >
> > My interpretation has been that the redirected header should be the
> forwarded packet, not the originating packet.   Recently we've seen Linux
> based routers use   the originating packet.
> >
> > My guess is they read this line from RFC 4861 Section 4.6.3
> > The original packet truncated to ensure that the
> >                      size of the redirect message does not exceed the
> >                      minimum MTU required to support IPv6 as specified
> >                      in [IPv6]."
> >
> > The reason that I'm asking is we have seen host that don't process the
> Redirect message unless it's the forwarding packet.   I want to make sure
> that we are telling implementations the correct behavior.
> >
> > ~Tim
> >
> > --
> > Now offering testing for SDN applications and controllers in our SDN
> switch test bed. Learn more today http://bit.ly/SDN_IOLPR
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>


-- 

Now offering testing for SDN applications and controllers in our SDN switch
test bed. Learn more today http://bit.ly/SDN_IOLPR

--001a1149aec8d91aa10539b5ba74
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Ole,<div><br></div><div>If this is true, either packet =
is ok to put in the Redirected Header from the router point of view. =C2=A0=
 Based on that Host receiving redirects shouldn&#39;t be dropping them depe=
nding on what&#39;s in the Redirected Header? =C2=A0=C2=A0</div><div><br></=
div><div>~Tim</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Wed, Aug 10, 2016 at 4:29 AM,  <span dir=3D"ltr">&lt;<a href=3D"=
mailto:otroan@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">Tim,<br>
<br>
I think it is implementation dependent.<br>
It depends on where in the forwarding path the redirect check is done in re=
lation to the hop limit decrement.<br>
<br>
Best regards,<br>
Ole<br>
<div><div class=3D"h5"><br>
<br>
&gt; On 09 Aug 2016, at 15:14, Timothy Winters &lt;<a href=3D"mailto:twinte=
rs@iol.unh.edu">twinters@iol.unh.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello,<br>
&gt;<br>
&gt; The UNH-IOL has seen several different implementations with varied int=
erpretations the following line from RFC 4861 Section 8.2 regarding what sh=
ould be included in the Redirect Header of an ICMPv6 Redirect message.<br>
&gt;<br>
&gt; &quot;Redirected Header: as much of the forwarded packet as can<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 fit without the redire=
ct packet exceeding the minimum MTU<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 required to support IP=
v6 as specified in [IPv6].&quot;<br>
&gt;<br>
&gt; My interpretation has been that the redirected header should be the fo=
rwarded packet, not the originating packet.=C2=A0 =C2=A0Recently we&#39;ve =
seen Linux based routers use=C2=A0 =C2=A0the originating packet.<br>
&gt;<br>
&gt; My guess is they read this line from RFC 4861 Section 4.6.3<br>
&gt; The original packet truncated to ensure that the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 size of the redirect message does not exceed the<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 minimum MTU required to support IPv6 as specified<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 in [IPv6].&quot;<br>
&gt;<br>
&gt; The reason that I&#39;m asking is we have seen host that don&#39;t pro=
cess the Redirect message unless it&#39;s the forwarding packet.=C2=A0 =C2=
=A0I want to make sure that we are telling implementations the correct beha=
vior.<br>
&gt;<br>
&gt; ~Tim<br>
&gt;<br>
&gt; --<br>
&gt; Now offering testing for SDN applications and controllers in our SDN s=
witch test bed. Learn more today <a href=3D"http://bit.ly/SDN_IOLPR" rel=3D=
"noreferrer" target=3D"_blank">http://bit.ly/SDN_IOLPR</a><br>
&gt;<br>
</div></div>&gt; ------------------------------<wbr>-----------------------=
-------<wbr>--------<br>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">







<p><font face=3D"georgia, serif" size=3D"1">Now offering testing for SDN ap=
plications and controllers in our SDN switch test bed.=C2=A0</font><span st=
yle=3D"font-family:georgia,serif;font-size:x-small">Learn more today <a hre=
f=3D"http://bit.ly/SDN_IOLPR" target=3D"_blank">http://bit.ly/SDN_IOLPR</a>=
</span></p></div></div></div></div></div></div></div>
</div>

--001a1149aec8d91aa10539b5ba74--


From nobody Wed Aug 10 04:20:13 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC42912D0C8 for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 04:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 DG8sNaYgUAWT for <ipv6@ietfa.amsl.com>; Wed, 10 Aug 2016 04:20:09 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80F6F12D091 for <ipv6@ietf.org>; Wed, 10 Aug 2016 04:20:09 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Aug 2016 11:20:08 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 3F1D99CC4F; Wed, 10 Aug 2016 04:20:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=2eRNfNJbJmyQ1y78zfZbQ4tXjug=; b= pgPBxz8n5ahXp7zM/au02AP8plkSe4xB4conaj5OKC7Spuknd+kRlomYd4fLAyI9 D19YFoljcaZYFR9mIyjgxznhv7zo9FJrL+hcVXy0h+ufoR4/DJMmpHJRutDgPfUc Uhe+yzZuXIz2O42/XLMF0ErNuPh0PN4uN5i55lw/Ttw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=fqv8u+Q/Bvb6RRVJEuIol3+LtX 6z0EXbaOoCgiC0oLVp40FCiMPIbnhhYoTCLywRzXv5AacLcP4Ofw93UAKhsBrcyw MdPGOGSxSLK1H+FyW+cla293MgP70noIM1E3fV6E/coK8ukFIEquiElDhiVGY+02 Qy/KdmXmTBxsvzIZw=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id ECEB19CC4E; Wed, 10 Aug 2016 04:20:06 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 35E303127F4A; Wed, 10 Aug 2016 13:20:04 +0200 (CEST)
Subject: Re: Redirected Header (Forwarded/Originating Packet)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_367E4621-B2CD-4B9C-AE24-978CDFD044C4"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <CAOSSMjUqhkpyT8SWKWRQqHFxDOMd=YQUc7UwFnVPKLWMHUF2SQ@mail.gmail.com>
Date: Wed, 10 Aug 2016 13:20:03 +0200
Message-Id: <D0056A64-0EC0-4784-88A5-836C8B2DA055@employees.org>
References: <CAOSSMjUYJZfDMiRBStQCdO-hs0TZg53oNYo3Bag=QNCufUfD0g@mail.gmail.com> <20D21BAF-29DD-47FB-9E32-02DDDC2D9F25@employees.org> <CAOSSMjUqhkpyT8SWKWRQqHFxDOMd=YQUc7UwFnVPKLWMHUF2SQ@mail.gmail.com>
To: Timothy Winters <twinters@iol.unh.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bWvItB19oGO4i6RoE19_Ve9tETs>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 11:20:11 -0000

--Apple-Mail=_367E4621-B2CD-4B9C-AE24-978CDFD044C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Tim,

> If this is true, either packet is ok to put in the Redirected Header =
from the router point of view.   Based on that Host receiving redirects =
shouldn't be dropping them depending on what's in the Redirected Header?

indeed.
it is not specified in any RFC that the host receiving the redirect =
should check the hop limit of the inner packet. for good reason.

I don't see what checking that would achieve either, compared to the =
already described checks in the RFC.

Cheers,
Ole

--Apple-Mail=_367E4621-B2CD-4B9C-AE24-978CDFD044C4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXqw3jAAoJED4aXnjSQuKWFvIH/AyRhEPKqWVm286JSRD6vXlY
pawiwIbimxz8wG28OgQZrTTGwTl+alQTbqOunnN9kUHlwnAl3dU997IigvJN0hm1
4TIBsXyOp9+hSsPPszL21S3SvqmUaN+NlTNq3GUtN6CrwXDF3hXO+yWUNSQjIFTm
VV/igHnodhTQVmW/1DEuOaoQjTR+APSvUYD197zoSj2G8q3rg4D9p1gLJkUld9w/
Sn5Dy94w45FUG6z7kUu/2Hj6jFlhVkRwbG9pNuRxmntZLGQdtbgHc5QnQ4RnxRWu
deMvtyFoC8+47GyhB0XNJ1sLObOcFeMejdIiwpy0Wj+gwSuhQY7JB6R+UAOPf3o=
=ijGt
-----END PGP SIGNATURE-----

--Apple-Mail=_367E4621-B2CD-4B9C-AE24-978CDFD044C4--


From nobody Wed Aug 10 04:22:38 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEB4C12D784; Wed, 10 Aug 2016 04:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TouSoN0fLSsu; Wed, 10 Aug 2016 04:22:28 -0700 (PDT)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::235]) (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 A571712D770; Wed, 10 Aug 2016 04:22:28 -0700 (PDT)
Received: by mail-ua0-x235.google.com with SMTP id n59so63547194uan.2; Wed, 10 Aug 2016 04:22:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=GvulopnUDAcjGoE4WKvQ6vRLFOHD2psqTh1DMkC2Gbk=; b=IvMvsSIGL2l//yWuTGxe0PsHRpGtjQNnL2OSs0C7VIhbPhUborMnYBFsQqleRwdAm4 3Vf7oAgNWZLZkYPVb5oeoGS5TXBMLgwx1ya+mO0WsnCkfDJ8bwGy2IGCeb0E2dyHBsaE QKvsmByD5q4M5SGZTqZIh/nVRux6XHp78Xi4uM/nIdGdHVOFNIOzJ4dHaiyDIGoTbocO 1/x3L4VEJjEPQUCYYeDVYb5Oq9mV4cG9VaKyIycjGhhIorb6hDnq106RBvVvahXYFGy8 yh3wFgsHZiBme/INuI6rJQwVD5RR1pcpUTO2kf3CE2hkDA6+vlRUxsfUgWuitOE1KF6d x0Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=GvulopnUDAcjGoE4WKvQ6vRLFOHD2psqTh1DMkC2Gbk=; b=IRNjS6CFTLnAEHWtew6efY8mE+9rsdP6rRIQAt28cR9kG3Tnb2Y3+SyL+C/cDju+cw TrTSPx0s2f6OUAk9VRnm/EvRKUKZxKDXrMiMArkHQyRWOibD+Ff0A19yEgVhXfcSuI7T Lw8hDwb+xLlXoKMYShsUqwtZasAaFbcR7bqMd4mwUbupJmuOk2/Uzr4GSVjya8GMG2Iq tJ6kEqah8zfQ3iueMyOo3pfiQJvEUTROWdIt0dLi1KHFlrBv4R7BunLhCypJkNn0ZScW AbyVHrgZxuLxkU908nUy9vz/GxnjBlG7xmvBwBea7GqS7IFdX3/LHP3+jWgdBUezW+Lt Ojsw==
X-Gm-Message-State: AEkoouvQteIbqtObMQh+1X9cb/EEHp+MY1rS70ymXDl7XvUStx7aQ9pjpul+Ro3IfDMvjNfmpkC9A/+LZMeL3A==
X-Received: by 10.31.50.22 with SMTP id y22mr1642775vky.94.1470828147742; Wed, 10 Aug 2016 04:22:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Wed, 10 Aug 2016 04:21:57 -0700 (PDT)
In-Reply-To: <CAO42Z2yaLjBesCFRqYVZ10Vm0W+HMtNRXj+bPYqOQYm3zVqEmA@mail.gmail.com>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com> <A3200A86-B59B-4AD4-9CF2-D2C7F50AE4C8@employees.org> <CAO42Z2yaLjBesCFRqYVZ10Vm0W+HMtNRXj+bPYqOQYm3zVqEmA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 10 Aug 2016 21:21:57 +1000
Message-ID: <CAO42Z2xc3p47qkqJWWrmswCoKFhiw94DqZq-Gvi2sjTOvhvMKg@mail.gmail.com>
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/coMVQlxDVhr7-b0WxSGA-4EBCE4>
Cc: 6man WG <ipv6@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Fernando Gont <fgont@si6networks.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 11:22:30 -0000

On 10 August 2016 at 18:28, Mark Smith <markzzzsmith@gmail.com> wrote:
> On 10 August 2016 at 18:16,  <otroan@employees.org> wrote:
>> Mark,
>>
>> [...]
>>
>>> I argued for that because I think privacy is a primary property of an a=
ddress, not the method used to configure it. However, since the different m=
ethods of configuring the address can effect the resulting address's privac=
y properties, I think it is necessary to discuss how to achieve privacy for=
 the three different configuration methods we have in the one place.
>>
>> And you don't think RFC7721 is enough?
>>
>
> Yes, got this draft and that RFC mixed up! I think I missed that RFC
> getting published, which is why I thought that sort of text was in a
> draft somewhere.
>

Actually I'll take that back. RFC7721 is analysis of the issues.

draft-ietf-6man-default-iids is really about SLAAC and DHCPv6 as they
computer generate IIDs.

My suggestion to also include static IIDs was more as a related side
note (not sure if there is anyway to indicate that in an RFC), as I
think having a bit of advice on static IIDs somewhere would be useful
(a separate RFC might be a bit excessive). The title is general enough
that I think static IIDs advice can be included, and it then makes
this ID cover all current methods of configuring addresses.

Regards,
Mark.


> Apologies for the noise!
>
> Regards,
> Mark.
>
>
>
>> Cheers,
>> Ole


From nobody Wed Aug 10 04:35:55 2016
Return-Path: <volz@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAA212D869; Wed, 10 Aug 2016 04:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.769
X-Spam-Level: 
X-Spam-Status: No, score=-15.769 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 x3LApQyqvMQs; Wed, 10 Aug 2016 04:35:46 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D682F12D7D9; Wed, 10 Aug 2016 04:35:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1883; q=dns/txt; s=iport; t=1470828945; x=1472038545; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BQCALBx7ugSvmCiymhuLdZFuou+wuOqGJNaTsaP0kIA=; b=DNAhMwS5AhHTHDojEqysMYjMHNJkdtaLzRa4Z6dWJ64CiXD9JfWciAa3 G2QnZOa46HV/Yw5MYiyYH1f5uFZ6fZ5gLAaWuORz6eZ73B8qCcH8mRHbE eGLU/L0brzNep4Je9ldS2DY5cXXwsrMJU1Ky4oSd6DPY0F8yp6ZWnBtCZ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BRAgCBEKtX/4cNJK1dg0VWfKx+jCiBf?= =?us-ascii?q?SSFeQKBXjgUAQEBAQEBAV0nhF4BAQQBOj8QAgEIGB4QIRElAgQOBYgXAw8IDr0?= =?us-ascii?q?DDYQyAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWIIgiCTYJDgW0QgyyCLwWZCDQBh?= =?us-ascii?q?hyGOYI8j0OILYQHg3cBHjaDem4BhysBAQE?=
X-IronPort-AV: E=Sophos;i="5.28,499,1464652800"; d="scan'208";a="139766697"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Aug 2016 11:35:44 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u7ABZjVX017548 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Aug 2016 11:35:45 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 10 Aug 2016 06:35:44 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Wed, 10 Aug 2016 06:35:44 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
Thread-Topic: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
Thread-Index: AQHR4yonS2aKHoWIFECnh5Wt1IH5QqAi5eGA///ArQCAFwL/AIABEWyAgADS/oCABr6HAIAAA3cAgAAwV4D//7AJRA==
Date: Wed, 10 Aug 2016 11:35:44 +0000
Message-ID: <13DE5431-7F6B-4699-A49D-3FC7DD5322BA@cisco.com>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com> <A3200A86-B59B-4AD4-9CF2-D2C7F50AE4C8@employees.org> <CAO42Z2yaLjBesCFRqYVZ10Vm0W+HMtNRXj+bPYqOQYm3zVqEmA@mail.gmail.com>, <CAO42Z2xc3p47qkqJWWrmswCoKFhiw94DqZq-Gvi2sjTOvhvMKg@mail.gmail.com>
In-Reply-To: <CAO42Z2xc3p47qkqJWWrmswCoKFhiw94DqZq-Gvi2sjTOvhvMKg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/2t2lwTgmIE3XfqfqiwD6D7RTBrM>
Cc: 6man WG <ipv6@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 11:35:47 -0000

For DHCPv6 we already have information about this in https://tools.ietf.org=
/html/rfc7824#section-4.3. And we have an open ticket to modify text in the=
 3315bis document -- https://trac.tools.ietf.org/group/dhcpv6bis/ticket/166=
.

- Bernie (from iPad)

>> On Aug 10, 2016, at 7:22 AM, Mark Smith <markzzzsmith@gmail.com> wrote:
>>=20
>>> On 10 August 2016 at 18:28, Mark Smith <markzzzsmith@gmail.com> wrote:
>>> On 10 August 2016 at 18:16,  <otroan@employees.org> wrote:
>>> Mark,
>>>=20
>>> [...]
>>>=20
>>>> I argued for that because I think privacy is a primary property of an =
address, not the method used to configure it. However, since the different =
methods of configuring the address can effect the resulting address's priva=
cy properties, I think it is necessary to discuss how to achieve privacy fo=
r the three different configuration methods we have in the one place.
>>>=20
>>> And you don't think RFC7721 is enough?
>>=20
>> Yes, got this draft and that RFC mixed up! I think I missed that RFC
>> getting published, which is why I thought that sort of text was in a
>> draft somewhere.
>=20
> Actually I'll take that back. RFC7721 is analysis of the issues.
>=20
> draft-ietf-6man-default-iids is really about SLAAC and DHCPv6 as they
> computer generate IIDs.
>=20
> My suggestion to also include static IIDs was more as a related side
> note (not sure if there is anyway to indicate that in an RFC), as I
> think having a bit of advice on static IIDs somewhere would be useful
> (a separate RFC might be a bit excessive). The title is general enough
> that I think static IIDs advice can be included, and it then makes
> this ID cover all current methods of configuring addresses.
>=20
> Regards,
> Mark.
>=20
>=20
>> Apologies for the noise!
>>=20
>> Regards,
>> Mark.
>>=20
>>=20
>>=20
>>> Cheers,
>>> Ole


From nobody Wed Aug 10 06:57:52 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F1FCC12D53D; Wed, 10 Aug 2016 06:57:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-ipv6-mibs-obsolete-01.txt> (Republishing the IPV6-specific MIB modules as obsolete) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <147083746494.20604.8362405361335855639.idtracker@ietfa.amsl.com>
Date: Wed, 10 Aug 2016 06:57:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LbJpaltXNQJxo1Uw9OnkwCXtlik>
Cc: draft-ietf-6man-ipv6-mibs-obsolete@ietf.org, ipv6@ietf.org, suresh.krishnan@ericsson.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 13:57:45 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'Republishing the IPV6-specific MIB modules as obsolete'
  <draft-ietf-6man-ipv6-mibs-obsolete-01.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-08-24. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   In 2005, the IPv6 MIB update group published updated versions of the
   IP-MIB, UDP-MIB, TCP-MIB and IP-FORWARD-MIB modules, which use the
   InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the
   same table.  This document contains versions of the obsoleted
   IPV6-MIB, IPV6-TC, IPV6-ICMP-MIB, IPV6-TCP-MIB and IPV6-UDP-MIB
   modules, for the purpose of updating MIB module repositories.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-mibs-obsolete/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-mibs-obsolete/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Wed Aug 10 10:54:35 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C533612D841; Wed, 10 Aug 2016 10:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 mp6MLV8GPgUe; Wed, 10 Aug 2016 10:54:32 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31D6712D83E; Wed, 10 Aug 2016 10:54:31 -0700 (PDT)
X-AuditID: c618062d-980fb98000000a08-49-57ab6afb4aa1
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id F2.FE.02568.BFA6BA75; Wed, 10 Aug 2016 19:57:15 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0301.000; Wed, 10 Aug 2016 13:52:16 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Subject: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Thread-Topic: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Thread-Index: AdHzL+59iRDragK5Q9KnqgmXoALbXg==
Date: Wed, 10 Aug 2016 17:52:16 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyuXRPrO7vrNXhBi+7LCx2T5nGZvHy7Hsm i6mPgcSRw39YHVg8liz5yeSxdWoTWwBTFJdNSmpOZllqkb5dAlfGpEmdjAVbOCo27t3O2sDY yt7FyMkhIWAi0fXqGnMXIxeHkMAGRomjb1uZIJzljBLbtt0Cq2IDqtqw8zNYQkRgC6PE5zfH WboYOTiEBRIknh21AqkREUiVuD7vIAuErSfx52wfM4jNIqAqsfVNN1g5r4CvxPXZCSBhRgEx ie+n1jCB2MwC4hK3nsxngjhIQGLJnvPMELaoxMvH/1ghbCWJOa+vMUPU60gs2P2JDcLWlli2 8DVYnFdAUOLkzCcsExiFZiEZOwtJyywkLbOQtCxgZFnFyFFaXJCTm25ksIkRGNjHJNh0dzDe n+55iFGAg1GJh1dBalW4EGtiWXFl7iFGCQ5mJRFe4aTV4UK8KYmVValF+fFFpTmpxYcYpTlY lMR5xR4phgsJpCeWpGanphakFsFkmTg4pRoYZa1mflx9vE3EwNxAeuGBTf+v1/Uf3Jcio5P1 vvd5w4zqaWse/931jVNDcfaWszyl82+c+Wb5ceuTTcFXt2l3BZaLFbTenaMleixVt2CXR7EI c+LE9XseOWaWzLYoj7VZ7PHVRu3XJecjHHwWLTsqTSpKdTOEn+n/6z973sVWSGarZ7iu4b87 SizFGYmGWsxFxYkA6/lJ8WgCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/MRDV0ma-oS_HL31vKCa5Z9EfM8k>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 17:54:34 -0000

Hi all,=0A=
   I have been notified about this vulnerability and have been asked whethe=
r =0A=
this is due to an issue with the IPv6 protocol specifications. At first =0A=
glance, I have a hard time seeing how this attack is possible on any =0A=
compliant RFC4861 implementation given that the 255 Hop Limit check would =
=0A=
drop any remote attack packets. If someone on the 6man/v6ops mailing lists =
=0A=
has further info, can you please contact me off-list. My goal is to figure =
=0A=
out if there is any protocol work or operational guidance needed from the =
=0A=
IETF side.=0A=
=0A=
More info:=0A=
=0A=
This is the CVE list entry in question=0A=
=0A=
https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2016-1409=0A=
=0A=
The Cisco security advisory=0A=
=0A=
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco=
-sa-20160525-ipv6=0A=
=0A=
The Juniper knowledge base entry=0A=
=0A=
https://kb.juniper.net/InfoCenter/index?page=3Dcontent&id=3DJSA10749&cat=3D=
SIRT_1&actp=3DLIST=0A=
=0A=
Thanks=0A=
Suresh=0A=


From nobody Wed Aug 10 13:35:39 2016
Return-Path: <erey@ernw.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C43A712D0B3; Wed, 10 Aug 2016 13:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 ub4VhUtsfu6Y; Wed, 10 Aug 2016 13:35:36 -0700 (PDT)
Received: from mx1.ernw.net (mx1.ernw.net [IPv6:2003:60:4010:10a0::11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49103126FDC; Wed, 10 Aug 2016 13:35:35 -0700 (PDT)
Received: from mail1.ernw.net (unknown [172.31.1.30]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail1.ernw.net", Issuer "ernw ca1" (verified OK)) by mx1.ernw.net (Postfix) with ESMTPS id 2A16127313; Wed, 10 Aug 2016 22:35:33 +0200 (CEST)
Received: from ws26.ernw.net (unknown [IPv6:fd00:2001:0:d001::70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ws26.ernw.net", Issuer "ernw ca1" (verified OK)) by mail1.ernw.net (Postfix) with ESMTPS id B3A5F558A17; Wed, 10 Aug 2016 22:35:32 +0200 (CEST)
Received: by ws26.ernw.net (Postfix, from userid 1002) id 761E195BA; Wed, 10 Aug 2016 22:38:13 +0200 (CEST)
Date: Wed, 10 Aug 2016 22:38:13 +0200
From: Enno Rey <erey@ernw.de>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Message-ID: <20160810203813.GB6374@ernw.de>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TStQNveM0skxhvYB4ZB3rH8TEKg>
Cc: IPv6 Operations <v6ops@ops.ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 20:35:39 -0000

Suresh,

On Wed, Aug 10, 2016 at 05:52:16PM +0000, Suresh Krishnan wrote:
> Hi all,
>    I have been notified about this vulnerability and have been asked whether 
> this is due to an issue with the IPv6 protocol specifications. At first 
> glance, I have a hard time seeing how this attack is possible on any 
> compliant RFC4861 implementation given that the 255 Hop Limit check would 
> drop any remote attack packets. If someone on the 6man/v6ops mailing lists 
> has further info

some public discussion (hence no need for off-list) incl. practical testing can be found here:
https://www.insinuator.net/2016/05/cve-2016-1409-ipv6-ndp-dos-vulnerability-in-cisco-software/

best

Enno






, can you please contact me off-list. My goal is to figure 
> out if there is any protocol work or operational guidance needed from the 
> IETF side.
> 
> More info:
> 
> This is the CVE list entry in question
> 
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1409
> 
> The Cisco security advisory
> 
> https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160525-ipv6
> 
> The Juniper knowledge base entry
> 
> https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10749&cat=SIRT_1&actp=LIST
> 
> Thanks
> Suresh
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

-- 
Enno Rey

ERNW GmbH - Carl-Bosch-Str. 4 - 69115 Heidelberg - www.ernw.de
Tel. +49 6221 480390 - Fax 6221 419008 - Cell +49 173 6745902 

Handelsregister Mannheim: HRB 337135
Geschaeftsfuehrer: Enno Rey

=======================================================
Blog: www.insinuator.net || Conference: www.troopers.de
Twitter: @Enno_Insinuator
=======================================================


From nobody Wed Aug 10 16:05:09 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D7C12D603; Wed, 10 Aug 2016 16:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jyUxOW1As4KR; Wed, 10 Aug 2016 16:05:06 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 F34E612D550; Wed, 10 Aug 2016 16:05:05 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id f189so79510649oig.3; Wed, 10 Aug 2016 16:05:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=c5VvRb+DyJVJNRydIya1TxAa5iQ/rS5qn4gb5qdNN54=; b=uRtc/MCYadJGZjLyC2gTGYd2kXR7/eothbzY0/u4L7otJKkpgASHxcNL/CMsfgetmb Q/HFGtgzGPHnBMEppn2fF8bmFvakv8oA8PrY5hFnsANII93YzssamSkLMLqY8KR0jMSs j0T14XRg3PWCgS3uhVhuDdpVhPYNbTZalc+Yqnjh75K/ewqmwBuKPf3UyiMatuM5t6dJ q20yhdgTH7QJiaETpBKP/kqkkMgCnIp3cxkokqRHu7qQmbGGudqg9hfoLv/mH858tQWb Y7bBwZ4BxYYiUmBGnFxUnhjrOXrEnQw1xwRvzPE9EsuxU/COwk0SADfzU6pcx0I87Y2f wFFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=c5VvRb+DyJVJNRydIya1TxAa5iQ/rS5qn4gb5qdNN54=; b=WL45fp6w2ZK0w35Aw009nXRNBCAXsG9AO1lBvYKihJwFhtNEZ/EwW5iksnojaO5jfJ ttOR+7XIwFynS6j44vKnmuqVmQ/gUKQ28tan0y4ZEQx5A0ldWcUen+jB/r7BFg7e5w6Q DCGRcq/HDuCglTwomtG3zflSihy8SDtyZ1XJlBI+aAxNLE5g4PuqZH2Ai6mF5aVQmeYE X7yn/CoUHVETWk8g5Pu0iYQh4nsfy5qxPDdFkHMXlo8r8dhcSlX/DIdifn5X3p/6qLpx Fpe1A5XsVTB14Jc7Es8v8d0A0jwsoAUGnxn1HI6lCiSgjWT9pjp3KEAWN+/qDXXTpjmy +L+Q==
X-Gm-Message-State: AEkooutMgFAtLfKujZUUnmqV5lbFt6a4b6KTCQ+9Pycv8e9hG3vI5OyQdt1Ysj6FOziT8VWVj30mAzAOP1w0lw==
X-Received: by 10.202.212.139 with SMTP id l133mr3280910oig.11.1470870305379;  Wed, 10 Aug 2016 16:05:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Wed, 10 Aug 2016 16:05:04 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
From: Hemant Singh <hemantietf@gmail.com>
Date: Wed, 10 Aug 2016 19:05:04 -0400
Message-ID: <CABdyVt68OQs3=tUUk8nNQFpjkZgBwfeVy4TynBVgHQfE8xKftg@mail.gmail.com>
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113dd9b4101b9d0539bfaed8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aVqIXfoUzIeaVbRNSXzXQ2n9RUI>
Cc: IPv6 Operations <v6ops@ops.ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 23:05:08 -0000

--001a113dd9b4101b9d0539bfaed8
Content-Type: text/plain; charset=UTF-8

Suresh,

Thanks for sending this out.

There is no change needed to any protocol RFC.  Based on the Juniper URL
(in the firewall section) I see the the crafted ND packet had a hop-limit
which was not 255 and the packet was still not dropped by the node.  Not
dropping such a packet causes the DOS attack.

RFC4861 is clear in saying that if an IPv6 ND packet is received with a Hop
limit that is not 255, the ND protocol is immune (section 3.1),   To me,
this means the packet should be dropped.  Also, see section 11.2 of RFC4861
as well where 255 hop limit is discussed.

Hemant

On Wed, Aug 10, 2016 at 1:52 PM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> Hi all,
>    I have been notified about this vulnerability and have been asked
> whether
> this is due to an issue with the IPv6 protocol specifications. At first
> glance, I have a hard time seeing how this attack is possible on any
> compliant RFC4861 implementation given that the 255 Hop Limit check would
> drop any remote attack packets. If someone on the 6man/v6ops mailing lists
> has further info, can you please contact me off-list. My goal is to figure
> out if there is any protocol work or operational guidance needed from the
> IETF side.
>
> More info:
>
> This is the CVE list entry in question
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1409
>
> The Cisco security advisory
>
> https://tools.cisco.com/security/center/content/
> CiscoSecurityAdvisory/cisco-sa-20160525-ipv6
>
> The Juniper knowledge base entry
>
> https://kb.juniper.net/InfoCenter/index?page=content&
> id=JSA10749&cat=SIRT_1&actp=LIST
>
> Thanks
> Suresh
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--001a113dd9b4101b9d0539bfaed8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Suresh,</div><div><br></div><div>Thanks for sending t=
his out. =C2=A0</div><div><br></div>There is no change needed to any protoc=
ol RFC.=C2=A0 Based on the Juniper URL (in the firewall section) I see the =
the crafted ND packet had a hop-limit which was not 255 and the packet was =
still not dropped by the node.=C2=A0 Not dropping such a packet causes the =
DOS attack.<div><br></div><div>RFC4861 is clear in saying that if an IPv6 N=
D packet is received with a Hop limit that is not 255, the ND protocol is i=
mmune (section 3.1), =C2=A0 To me, this means the packet should be dropped.=
=C2=A0 Also, see section 11.2 of RFC4861 as well where 255 hop limit is dis=
cussed.=C2=A0<div><br></div><div>Hemant</div></div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Wed, Aug 10, 2016 at 1:52 PM, Su=
resh Krishnan <span dir=3D"ltr">&lt;<a href=3D"mailto:suresh.krishnan@erics=
son.com" target=3D"_blank">suresh.krishnan@ericsson.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">Hi all,<br>
=C2=A0 =C2=A0I have been notified about this vulnerability and have been as=
ked whether<br>
this is due to an issue with the IPv6 protocol specifications. At first<br>
glance, I have a hard time seeing how this attack is possible on any<br>
compliant RFC4861 implementation given that the 255 Hop Limit check would<b=
r>
drop any remote attack packets. If someone on the 6man/v6ops mailing lists<=
br>
has further info, can you please contact me off-list. My goal is to figure<=
br>
out if there is any protocol work or operational guidance needed from the<b=
r>
IETF side.<br>
<br>
More info:<br>
<br>
This is the CVE list entry in question<br>
<br>
<a href=3D"https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2016-1409" =
rel=3D"noreferrer" target=3D"_blank">https://cve.mitre.org/cgi-bin/<wbr>cve=
name.cgi?name=3DCVE-2016-1409</a><br>
<br>
The Cisco security advisory<br>
<br>
<a href=3D"https://tools.cisco.com/security/center/content/CiscoSecurityAdv=
isory/cisco-sa-20160525-ipv6" rel=3D"noreferrer" target=3D"_blank">https://=
tools.cisco.com/<wbr>security/center/content/<wbr>CiscoSecurityAdvisory/cis=
co-<wbr>sa-20160525-ipv6</a><br>
<br>
The Juniper knowledge base entry<br>
<br>
<a href=3D"https://kb.juniper.net/InfoCenter/index?page=3Dcontent&amp;id=3D=
JSA10749&amp;cat=3DSIRT_1&amp;actp=3DLIST" rel=3D"noreferrer" target=3D"_bl=
ank">https://kb.juniper.net/<wbr>InfoCenter/index?page=3Dcontent&amp;<wbr>i=
d=3DJSA10749&amp;cat=3DSIRT_1&amp;actp=3D<wbr>LIST</a><br>
<br>
Thanks<br>
Suresh<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</blockquote></div><br></div>

--001a113dd9b4101b9d0539bfaed8--


From nobody Thu Aug 11 00:05:32 2016
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF56212D13B; Thu, 11 Aug 2016 00:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.768
X-Spam-Level: 
X-Spam-Status: No, score=-15.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 xxEcUh8aE4i5; Thu, 11 Aug 2016 00:05:29 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260D3126FDC; Thu, 11 Aug 2016 00:05:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2721; q=dns/txt; s=iport; t=1470899129; x=1472108729; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=TX4CLDBHQLoS2JML9xsOVSitkAbFJO1Bai9V2l8O+CQ=; b=Sj4+HjinfhXkp+OlKrje0FG1jEm2Os3uj7z3XN8Bt3wMB7ZDq2UAWxm1 BW1P+VcgVqyPgjzdGEhtHsSL80D8MwEu7CD6lVHbkN43tQ0Xmr9UsnKry x977HXSbpaujhu0I7uOX7vPTn2U1fGbsoSmYO/Pvu471dj8iP5i1Hb97P A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BSAgA/I6xX/4gNJK1dg0RWfLktgX0mh?= =?us-ascii?q?S1KAoFiOBQBAQEBAQEBXSeEXwEEAQEBbAsFCwIBCEYnCyUBAQQOBYgpCA7CQgE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBARcFhiqBeIJVgTmBL4E1I4Msgi8FiCaFczmKa?= =?us-ascii?q?gGGHYh2gWuEW4h9hmSFUYN3AR42gh8mgTVuAYVAgUQBAQE?=
X-IronPort-AV: E=Sophos;i="5.28,503,1464652800"; d="scan'208";a="139283413"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 Aug 2016 07:05:28 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u7B75Sj4026066 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 11 Aug 2016 07:05:28 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 11 Aug 2016 02:05:27 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Thu, 11 Aug 2016 02:05:27 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Thread-Topic: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Thread-Index: AdHzL+59iRDragK5Q9KnqgmXoALbXgAbs6id
Date: Thu, 11 Aug 2016 07:05:27 +0000
Message-ID: <17D0B14A-8FF5-49D0-B97C-2857EC999FDF@cisco.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
In-Reply-To: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Z7DW4AXhudFZ5U9CchpPoJHcYpE>
Cc: IPv6 Operations <v6ops@ops.ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2016 07:05:31 -0000

Hello Suresh:

One the side, since it is a different though related issue.

Whereas attacking a node inside the network should not be possible thanks t=
o the HL of 255,   The ND cache in the ingress router is still a potential =
target for sweeping attacks.

Implementations do all sorts of things to protect valid entries (those gone=
 REACHABLE). But at some point but it is difficult to differentiate a packe=
t for an existing node for which the router has no ND Cache Entry vs. a ran=
dom sweep so there are limits to what can be done. And the random sweep wil=
l still consume some amount of resources in the router till its goes on def=
ense mode.=20

This is due to the reactive behavior of Classical IPv6 ND. There is no way =
to pre-populate the forwarding engine with what is there so as to drop what=
 it not.

 The way I see it there's little we can do to update the existing protocol =
in its reactive form. But we may write best practices to protect the ND cac=
he, and we can standardize the proactive form (derived from RFC 6775) on al=
l media. We can also promote routing to the end device (e.g. /64 per device=
 or RPL inside a NBMA subnet). All the above is already happening in variou=
s wireless environments anyway.

Regards,

Pascal

> Le 10 ao=FBt 2016 =E0 19:54, Suresh Krishnan <suresh.krishnan@ericsson.co=
m> a =E9crit :
>=20
> Hi all,
>   I have been notified about this vulnerability and have been asked wheth=
er=20
> this is due to an issue with the IPv6 protocol specifications. At first=20
> glance, I have a hard time seeing how this attack is possible on any=20
> compliant RFC4861 implementation given that the 255 Hop Limit check would=
=20
> drop any remote attack packets. If someone on the 6man/v6ops mailing list=
s=20
> has further info, can you please contact me off-list. My goal is to figur=
e=20
> out if there is any protocol work or operational guidance needed from the=
=20
> IETF side.
>=20
> More info:
>=20
> This is the CVE list entry in question
>=20
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2016-1409
>=20
> The Cisco security advisory
>=20
> https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cis=
co-sa-20160525-ipv6
>=20
> The Juniper knowledge base entry
>=20
> https://kb.juniper.net/InfoCenter/index?page=3Dcontent&id=3DJSA10749&cat=
=3DSIRT_1&actp=3DLIST
>=20
> Thanks
> Suresh
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Sun Aug 14 11:24:13 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 188A612B02A; Sun, 14 Aug 2016 11:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 Da3ErfZp_StI; Sun, 14 Aug 2016 11:24:08 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9857212B00A; Sun, 14 Aug 2016 11:24:08 -0700 (PDT)
Received: from [192.168.3.105] (214-173-16-190.fibertel.com.ar [190.16.173.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B9C02800F5; Sun, 14 Aug 2016 20:24:02 +0200 (CEST)
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
To: Enno Rey <erey@ernw.de>, Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com>
Date: Sun, 14 Aug 2016 20:22:06 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160810203813.GB6374@ernw.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LuYc34TlaqICmZkd6yh4yDHYuRg>
Cc: IPv6 Operations <v6ops@ops.ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 18:24:11 -0000

On 08/10/2016 10:38 PM, Enno Rey wrote:
> Suresh,
> 
> On Wed, Aug 10, 2016 at 05:52:16PM +0000, Suresh Krishnan wrote:
>> Hi all,
>>    I have been notified about this vulnerability and have been asked whether 
>> this is due to an issue with the IPv6 protocol specifications. At first 
>> glance, I have a hard time seeing how this attack is possible on any 
>> compliant RFC4861 implementation given that the 255 Hop Limit check would 
>> drop any remote attack packets. If someone on the 6man/v6ops mailing lists 
>> has further info
> 
> some public discussion (hence no need for off-list) incl. practical testing can be found here:
> https://www.insinuator.net/2016/05/cve-2016-1409-ipv6-ndp-dos-vulnerability-in-cisco-software/

Some comments:
The outcome from your post is what I expected -- I'm not surprised. The
Hop LImit validation check is to be performed by the receiving node,
rather than by the intermmediate devices. If you wanted to enforce it on
intermmediate devices, you'd need to perform DPI, then the attacker
fires packets with EHs, and then we possibly end up with the usual "drop
all EHs, plus what I really want to drop".

My take is that the vuln is completely unrelated to NCE. since al end
systems I know of *do* check the Hop Limit of received ND packets.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Aug 14 11:36:11 2016
Return-Path: <erey@ernw.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416A012D786; Sun, 14 Aug 2016 11:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 q5Paq_d193kY; Sun, 14 Aug 2016 11:36:08 -0700 (PDT)
Received: from mx1.ernw.net (mx1.ernw.net [62.159.96.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A299012D11B; Sun, 14 Aug 2016 11:36:07 -0700 (PDT)
Received: from mail1.ernw.net (unknown [IPv6:fd00:2001:0:d001::30]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail1.ernw.net", Issuer "ernw ca1" (verified OK)) by mx1.ernw.net (Postfix) with ESMTPS id A76A42730F; Sun, 14 Aug 2016 20:36:05 +0200 (CEST)
Received: from ws26.ernw.net (unknown [172.31.1.70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ws26.ernw.net", Issuer "ernw ca1" (verified OK)) by mail1.ernw.net (Postfix) with ESMTPS id 6DD6855CA8E; Sun, 14 Aug 2016 20:36:05 +0200 (CEST)
Received: by ws26.ernw.net (Postfix, from userid 1002) id E25AF9FE1; Sun, 14 Aug 2016 20:38:51 +0200 (CEST)
Date: Sun, 14 Aug 2016 20:38:51 +0200
From: Enno Rey <erey@ernw.de>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Message-ID: <20160814183851.GA21495@ernw.de>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de> <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/cNcO2-y5p-CgAEQZKVTaPj5qCKE>
Cc: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, IETF IPv6 Mailing List <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 18:36:10 -0000

Hi Fernando,

On Sun, Aug 14, 2016 at 08:22:06PM +0200, Fernando Gont wrote:
> On 08/10/2016 10:38 PM, Enno Rey wrote:
> > Suresh,
> > 
> > On Wed, Aug 10, 2016 at 05:52:16PM +0000, Suresh Krishnan wrote:
> >> Hi all,
> >>    I have been notified about this vulnerability and have been asked whether 
> >> this is due to an issue with the IPv6 protocol specifications. At first 
> >> glance, I have a hard time seeing how this attack is possible on any 
> >> compliant RFC4861 implementation given that the 255 Hop Limit check would 
> >> drop any remote attack packets. If someone on the 6man/v6ops mailing lists 
> >> has further info
> > 
> > some public discussion (hence no need for off-list) incl. practical testing can be found here:
> > https://www.insinuator.net/2016/05/cve-2016-1409-ipv6-ndp-dos-vulnerability-in-cisco-software/
> 
> Some comments:
> The outcome from your post is what I expected -- I'm not surprised. The
> Hop LImit validation check is to be performed by the receiving node,

correct.
actually in the post the Cisco device in question (2003:60:4010::8) *is* the receiving node. and it happily accepts ICMPv6 NA/RA/RS packets sent from far remote entities (and hence having a hop limit < 255). the point/problem is not the networks in between forwarding the packets but the final destination accepting them.





> rather than by the intermmediate devices. If you wanted to enforce it on
> intermmediate devices, you'd need to perform DPI, then the attacker
> fires packets with EHs, and then we possibly end up with the usual "drop
> all EHs, plus what I really want to drop".
> 
> My take is that the vuln is completely unrelated to NCE. since al end
> systems I know of *do* check the Hop Limit of received ND packets.

apparently not true for quite some high end C* and J* gear, as their respective advisories state/show.

best

Enno






> 
> Thanks!
> 
> Cheers,
> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 

-- 
Enno Rey

ERNW GmbH - Carl-Bosch-Str. 4 - 69115 Heidelberg - www.ernw.de
Tel. +49 6221 480390 - Fax 6221 419008 - Cell +49 173 6745902 

Handelsregister Mannheim: HRB 337135
Geschaeftsfuehrer: Enno Rey

=======================================================
Blog: www.insinuator.net || Conference: www.troopers.de
Twitter: @Enno_Insinuator
=======================================================


From nobody Sun Aug 14 12:08:07 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F24D412D594; Sun, 14 Aug 2016 12:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 FQAMHA5lw9yU; Sun, 14 Aug 2016 12:08:05 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B10012D0F9; Sun, 14 Aug 2016 12:08:03 -0700 (PDT)
Received: from [192.168.3.105] (214-173-16-190.fibertel.com.ar [190.16.173.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id DA7B180C5E; Sun, 14 Aug 2016 21:07:58 +0200 (CEST)
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
To: Enno Rey <erey@ernw.de>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de> <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com> <20160814183851.GA21495@ernw.de>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <d38ea66a-5662-51c7-9952-6d361fbc53e2@si6networks.com>
Date: Sun, 14 Aug 2016 21:07:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <20160814183851.GA21495@ernw.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/R0lZ4MfFmulG8LMUewYO-dX4Aq8>
Cc: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, IETF IPv6 Mailing List <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 19:08:06 -0000

On 08/14/2016 08:38 PM, Enno Rey wrote:
>> 
>> Some comments: The outcome from your post is what I expected -- I'm
>> not surprised. The Hop LImit validation check is to be performed by
>> the receiving node,
> 
> correct. actually in the post the Cisco device in question
> (2003:60:4010::8) *is* the receiving node. and it happily accepts
> ICMPv6 NA/RA/RS packets sent from far remote entities (and hence
> having a hop limit < 255). the point/problem is not the networks in
> between forwarding the packets but the final destination accepting
> them.

Oops, I was confused, then. So, if, say, the devices gets an NS, it
creates an entry in the NC?


>> rather than by the intermmediate devices. If you wanted to enforce
>> it on intermmediate devices, you'd need to perform DPI, then the
>> attacker fires packets with EHs, and then we possibly end up with
>> the usual "drop all EHs, plus what I really want to drop".
>> 
>> My take is that the vuln is completely unrelated to NCE. since al
>> end systems I know of *do* check the Hop Limit of received ND
>> packets.
> 
> apparently not true for quite some high end C* and J* gear, as their
> respective advisories state/show.

I'll redo testing. I remember testing this, at the time, with a bunch of
devices, but they were all dropping ND packets when HL != 255.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Aug 14 12:29:33 2016
Return-Path: <gert@space.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9B7412D7AA for <ipv6@ietfa.amsl.com>; Sun, 14 Aug 2016 12:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.847
X-Spam-Level: 
X-Spam-Status: No, score=-3.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247] autolearn=unavailable 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 O-zToPbrpddL for <ipv6@ietfa.amsl.com>; Sun, 14 Aug 2016 12:29:29 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B95612D7A8 for <ipv6@ietf.org>; Sun, 14 Aug 2016 12:29:28 -0700 (PDT)
X-Original-To: ipv6@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2DD5C6286B for <ipv6@ietf.org>; Sun, 14 Aug 2016 21:29:26 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id A7B9460262; Sun, 14 Aug 2016 21:29:25 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 9697212A68; Sun, 14 Aug 2016 21:29:25 +0200 (CEST)
Date: Sun, 14 Aug 2016 21:29:25 +0200
From: Gert Doering <gert@space.net>
To: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>
Subject: Re: [ipv6hackers] CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
Message-ID: <20160814192925.GO79185@Space.Net>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de> <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/u4WHL-xxyIhRYzRcb6bb3cXpe28>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 19:29:32 -0000

Hi,

On Sun, Aug 14, 2016 at 08:22:06PM +0200, Fernando Gont wrote:
> My take is that the vuln is completely unrelated to NCE. since al end
> systems I know of *do* check the Hop Limit of received ND packets.

I tried to filter out (by ACL "deny and log") incoming ND packets at
DECIX with a TTL != 255.

And saw legitimate neighbours send such... (unfortunately, XR doesn't log
what the TTL *is* so I cannot answer the obvious question, and I didn't
yet set up infrastructure to sniff it off the wire).

... and when not filtered, these are *answered*...


(The other half of pandora's box I found there was that at least one major
vendor of backbone gear happily forwards packets sourced from fe80::
addresses off-link - as in: I see packets with fe80:: source addresses
coming from outside our network, destined to our DNS servers, containing 
proper queries...)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Sun Aug 14 15:21:45 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DF912D5A3; Sun, 14 Aug 2016 15:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4fWo3zskojmy; Sun, 14 Aug 2016 15:21:42 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (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 0757312B00F; Sun, 14 Aug 2016 15:21:42 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id 4so42817952oih.2; Sun, 14 Aug 2016 15:21:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AxV4HsSq8WJ08Cd7MP3nX2Cq51pshKD2tGN3zp7GvsE=; b=G3Sxn/JySAjMBC5DVqg8JI3CT9oNvKY2nBOO6JzlHcuHACHQ1jTxIRAwkYd9EKTVax ljxBBsRfIqb7IU0ZtUpcXh2MOcXyX64wWR30k4htaGtxN4q7rslXXPRwUqkHykbfCsEW NP+kAW48LdwYGWpxbacCzsGoKazw40c+L2PC5Nt8o5zTRAGcTOy7TllnWOKNzAVXvgDR 1befUWMshs/0cT15mHeNYq2oaC5tVbv2FSLA+zriO0cdrshr2p4JdvqTKExEvu/WIckc US1vIpcwdAYM80ssLSZKMMoieYxO5G9cdl4+fGGghu8gOCn9AXUykOEK1tgafOTudNDq UX+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AxV4HsSq8WJ08Cd7MP3nX2Cq51pshKD2tGN3zp7GvsE=; b=iGcTJazr5hvM9b7yz6gNl+BqYtKCbCHG561QjxvpNsxRHhJiEbxGM7xIRM3Idl3+hN i9ZFBnEnmF7c728+yvG12piyyaj/m7nwrZtNrR8ATvHz0aE9NaVGV5qJAL4b4jRLPVfG yizKwrde8VSlSAJCKQntqu54umWv2q+SPTThOkYSS6o9lpe9H1Kwsbv7DnjlHFOANr2x 4szstkcYy836LA94w/2FgfEE4sdwEgNQe2q3xnen9xmXd1kbjTvfpw4f7MCUffQk4lbg c8rdKP98QWXl2L8KmwR9eg2kbU64x7NLTlBGmXcgk62J2DIEDe7BObwDCEnr88bfZ9qw +I1g==
X-Gm-Message-State: AEkooutQYnu+ORNskMc87YHd26KJkdPMgJ/rd2uYkcwcUdmSfy3UnKZZ6CLMkWL6gAT+OnMWhhvFCpBcKA2cGg==
X-Received: by 10.157.11.93 with SMTP id p29mr268121otd.16.1471213301479; Sun, 14 Aug 2016 15:21:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Sun, 14 Aug 2016 15:21:40 -0700 (PDT)
In-Reply-To: <20160814192925.GO79185@Space.Net>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de> <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com> <20160814192925.GO79185@Space.Net>
From: Hemant Singh <hemantietf@gmail.com>
Date: Sun, 14 Aug 2016 18:21:40 -0400
Message-ID: <CABdyVt7av_ybp5wJqOJzxE8_L8AvgaT-RpDkkbXW4B7CcC-L3Q@mail.gmail.com>
Subject: Re: [ipv6hackers] CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
To: Gert Doering <gert@space.net>
Content-Type: multipart/alternative; boundary=001a113d1874394000053a0f8a82
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lsLUYalZKsOMZLkMNUGat5PrR7Q>
Cc: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, IETF IPv6 Mailing List <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Aug 2016 22:21:43 -0000

--001a113d1874394000053a0f8a82
Content-Type: text/plain; charset=UTF-8

I suspect the pandora box issue below is what has been discussed in v6ops
in the "Packets with LL src and GUA dst" thread.   The DNS server
destination is a GUA and the packet source is a LL src.

Hemant

On Sun, Aug 14, 2016 at 3:29 PM, Gert Doering <gert@space.net> wrote:

> Hi,
>
>
> (The other half of pandora's box I found there was that at least one major
> vendor of backbone gear happily forwards packets sourced from fe80::
> addresses off-link - as in: I see packets with fe80:: source addresses
> coming from outside our network, destined to our DNS servers, containing
> proper queries...)
>
>
>

--001a113d1874394000053a0f8a82
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I suspect the pandora box issue below is what has been dis=
cussed in v6ops in the &quot;Packets with LL src and GUA dst&quot; thread. =
=C2=A0 The DNS server destination is a GUA and the packet source is a LL sr=
c.<div><br></div><div>Hemant<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Sun, Aug 14, 2016 at 3:29 PM, Gert Doering <span dir=3D=
"ltr">&lt;<a href=3D"mailto:gert@space.net" target=3D"_blank">gert@space.ne=
t</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">Hi,<br>
<span><br></span><br>
(The other half of pandora&#39;s box I found there was that at least one ma=
jor<br>
vendor of backbone gear happily forwards packets sourced from fe80::<br>
addresses off-link - as in: I see packets with fe80:: source addresses<br>
coming from outside our network, destined to our DNS servers, containing<br=
>
proper queries...)<br>
<span><font color=3D"#888888"><br></font></span><div><div><br>
</div></div></blockquote></div><br></div></div></div>

--001a113d1874394000053a0f8a82--


From nobody Mon Aug 15 18:13:12 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F3512D612; Mon, 15 Aug 2016 18:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kxgkYFkRkxbN; Mon, 15 Aug 2016 18:13:10 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 1FEE512D621; Mon, 15 Aug 2016 18:13:10 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id u25so28777888qtb.1; Mon, 15 Aug 2016 18:13:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=qyggZ5DcxI2DyyRqbNk7XF5AvNuqHyxvYN1hk9zHdII=; b=0kMY3fRTYV4NcoOg7gHQGixmot9bPbDwxhg2J50na9xAWQpmOFvA4LYJbzJC3ItyKZ bh+3gWacd8u3DqpINdWNBOYW5HnCCQzgpE34qc4YUfcXLpww+HvVKaR8qJs3ztK3Pvdq yxGcdh7/n6AEP/KlsMZyWnemBNHMLAaVX37HRMBoMxrv6IHPMkS8MIQuO501yw00WJA4 sRZEcE25f8kEvUIW70MRDIpykDmXIwBTKKrTMhljdErEPppArdMSQ43D8jRb2XGd7ALO DFr5Qv10xjsKikdTEQ4q/6fV/jtu50JSh/i+EzVkrgU/HCZzrqKVfF9XJhbh50NbCPKZ wi+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=qyggZ5DcxI2DyyRqbNk7XF5AvNuqHyxvYN1hk9zHdII=; b=lmJPNEOGrkNOoIlIg891pQdx1RRszw8xXGELSTLsqfgJG5bZymMkuW+1SJp1VkxIqm KiYf3ht8qbCkHeufvHqvCy6CRBiGmoDU8d7Ycxvxhsw6jROappHjChDAtC5sNhHy0WyA Jup7qRSrmZEzKIMlH6tOaaGPMRcF35pCMdZZkLt25C65155KI9xZRTH5+wYdV+MDSkAs 8EFmuoCbrDq1HLulUzjGzf1Uk52YG9ZYWtxdkA0ZLluR35r8M9MxXwbrfd2ChLMsRVYF ENIlZaWUZbxxL9O29W65/W8q+QKlePnsp6cKQTeGUHYwW8UDlSSVOkW/MnOvVVGQBbTH Gumw==
X-Gm-Message-State: AEkoouuzTFVtjC+x6aXI6odjSo5Gv5i36oh0ImfXZs5suiv8J7Llpog6wPfFvZJbtW3zkbtGQ4WBsDvxixxMzg==
X-Received: by 10.200.52.85 with SMTP id v21mr36608961qtb.21.1471309989246; Mon, 15 Aug 2016 18:13:09 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Mon, 15 Aug 2016 18:13:08 -0700 (PDT)
In-Reply-To: <d38ea66a-5662-51c7-9952-6d361fbc53e2@si6networks.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <20160810203813.GB6374@ernw.de> <721a329b-9d4d-6b28-2906-2ce449db1861@si6networks.com> <20160814183851.GA21495@ernw.de> <d38ea66a-5662-51c7-9952-6d361fbc53e2@si6networks.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Mon, 15 Aug 2016 18:13:08 -0700
X-Google-Sender-Auth: 1WWz9NqpqexXs_jfQRj6Zn2qSJ8
Message-ID: <CAJE_bqd3fVNP65R23pcewNFNmA+Ye-8NSd7Z9LaN1Rdh5w6G=A@mail.gmail.com>
Subject: Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Jp9sB4lxz2YEGL2UAoe9pRQjqk4>
Cc: IPv6 Hackers Mailing List <ipv6hackers@lists.si6networks.com>, IETF IPv6 Mailing List <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, IPv6 Operations <v6ops@ops.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Aug 2016 01:13:11 -0000

At Sun, 14 Aug 2016 21:07:52 +0200,
Fernando Gont <fgont@si6networks.com> wrote:

> >> Some comments: The outcome from your post is what I expected -- I'm
> >> not surprised. The Hop LImit validation check is to be performed by
> >> the receiving node,
> >
> > correct. actually in the post the Cisco device in question
> > (2003:60:4010::8) *is* the receiving node. and it happily accepts
> > ICMPv6 NA/RA/RS packets sent from far remote entities (and hence
> > having a hop limit < 255). the point/problem is not the networks in
> > between forwarding the packets but the final destination accepting
> > them.
>
> Oops, I was confused, then. So, if, say, the devices gets an NS, it
> creates an entry in the NC?

Isn't it just that any software-based processing of ND messages
(including checking the hop limit and discarding it if it's invalid)
in a "slow path" can cause a DoS on the CPU cycle?  (Or are we talking
about the same thing just in a different phrase?).

--
JINMEI, Tatuya


From nobody Thu Aug 18 00:21:47 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10A4F12D10B for <ipv6@ietfa.amsl.com>; Thu, 18 Aug 2016 00:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 D2J6vvz4CnRX for <ipv6@ietfa.amsl.com>; Thu, 18 Aug 2016 00:21:44 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E031F12D0E1 for <ipv6@ietf.org>; Thu, 18 Aug 2016 00:21:43 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Aug 2016 07:21:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B50889CC4F; Thu, 18 Aug 2016 00:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=N4yHlcj5uVW0DrKhhDnZCWMoRcw=; b= keEOyLx8k2q1puVvUkT8qiPNtYGASQNjS1P18SjmvU2DK6rgXItmUBNkZ1m6QMY0 C2c7SB27bKIsEgZ/b21kpvWDrg0E4QfZOjcKScQas2dUBe4cbWLMv6O1Iv2b/sL6 1DWPoh3pw/F0Q03QqiTqEqfcIH1MLGAbtZnQznsavzU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=I+r9u2hkWURL68YmMDruHyuErS SGMggQ3bMkaHCJFUEn2K6s9bWBLV7CrfbMtjupZIBbZQK1Pd/G+dlOp0UMLgAN5o 4RsRu8acqlWy+oFZE5BgRcTcMTk1NPY1gEEDpN11kFWC0X1aullvYUDodPvvzqc6 7+MagwslYqkYpw9YY=
Received: from h.hanazo.no (cm-84.213.17.83.getinternet.no [84.213.17.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 434819CC51; Thu, 18 Aug 2016 00:21:41 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D868E328C3A8; Thu, 18 Aug 2016 09:21:38 +0200 (CEST)
Subject: Re: Consensus call: Path forward for draft-ietf-6man-default-iids-13
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_317F5B6F-66E4-410B-BE29-1D851341F3ED"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
Date: Thu, 18 Aug 2016 09:21:38 +0200
Message-Id: <C9E48618-42ED-4AFB-AF75-00E93274DB36@employees.org>
References: <521A7744-A00F-4D84-99F6-435A1327DCEC@employees.org>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lhWn31ZDXQUqzUiKgvdPdaldMQ0>
Cc: 6man-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 07:21:46 -0000

--Apple-Mail=_317F5B6F-66E4-410B-BE29-1D851341F3ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

All,

Consensus on option 1 (removing section 6) is now confirmed.
Please review the new revision of the document that will be posted =
shortly. My expectation is that we will then advance that revision to =
the IESG expediently.

Best regards,
Ole


> On 02 Aug 2016, at 16:48, otroan@employees.org wrote:
>=20
> All,
>=20
> There is one remaining issue we need resolved before we can advance =
this document.
> It is the issue of how the document shall update other documents.
> Alissa has enumerated the 3 options we see below.
>=20
> In the room there was support for option 1. Bernie proposed option 3 =
later on the list, as a possible compromise between 1 and 2.
>=20
> This starts a one week call on confirming consensus for option 1 =
(Remove section 6). The call last until August 9th.
>=20
> If you disagree with that choice, please state your objections to the =
list.
>=20
> Best regards,
> Ole
>=20
> =3D=3D=3D Option 1: Remove Section 6 =3D=3D=3D
>=20
> Under this option, the recommendations in Section 3 would apply to all =
of the IP-over-foo documents listed in the document header. But, for =
nodes that do not follow these recommendations, the IP-over-foo =
documents would still contain their current text explaining how to =
construct an EUI-64 for an IID.
>=20
>=20
> =3D=3D=3D Option 2: Keep Section 6 but add a sentence pointing to =
4291bis =3D=3D=3D
>=20
> Each of the updates listed in Section 6 could be modified to add =
something along the lines of the last sentence here:
>=20
>   The entire text of Section 4 of [RFC2464] is replaced with the
>   following text:
>=20
>   ---------------- cut here -------------- cut here ----------------
>   The Interface Identifier [AARCH] for an Ethernet interface SHOULD
>   be generated as specified in [RFC7217]. Embedding a stable
>   link-layer address in the IID is NOT RECOMMENDED [RFCXXXX].
>   [I-D.6man-rfc4291bis] Appendix A discusses approaches to IID =
creation
>   for nodes that choose not to follow this guidance.
>   ---------------- cut here -------------- cut here ----------------
>=20
>=20
> =3D=3D=3D Option 3: Remove Section 6 but add a list of IP-over-foo =
document section updates =3D=3D=3D
>=20
> Per Bernie=E2=80=99s suggestion, we could remove Section 6 and update =
Section 3 as follows:
>=20
> OLD
>   By default, nodes SHOULD NOT employ IPv6 address generation schemes
>   that embed a stable link-layer address in the IID.  In particular,
>   this document RECOMMENDS that nodes do not generate stable IIDs with
>   the schemes specified in [RFC2464], [RFC2467], [RFC2470], [RFC2491],
>   [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572], [RFC4338],
>   [RFC4391], [RFC5121], and [RFC5072].  The specific updates to these
>   documents to effectuate this recommendation are included in
>   Section 6.
>=20
> NEW
>   By default, nodes SHOULD NOT employ IPv6 address generation schemes
>   that embed a stable link-layer address in the IID.
>=20
>   The recommendations in this Section apply to:
>=20
>   Section 4 of [RFC2464]
>   Section 6 of [RFC2464]
>   Section 5 of [RFC2467]
>   Section 7 of [RFC2467]
>   Section 4 of [RFC2470]
>   Section 6 of [RFC2470]
>   Section 5.1 of [RFC2491]
>   Section 5.1.1 of [RFC2491]
>   Section 5.1.2 of [RFC2491]
>   Section 5 of [RFC2492]
>   Section 4 of [RFC2497]
>   Section 8 of [RFC2497]
>   Section 4 of [RFC2590]
>   Section 4.1 of [RFC2590]
>   Section 9 of [RFC2590]
>   Section 6 of [RFC3146]
>   Section 11 of [RFC3315] // modulo separate discussion about 3315bis
>   Section 3 of [RFC3572]
>   Section 6.2 of [RFC3572]
>   Section 2.5.1 of [RFC4291] // modulo separate discussion about =
4291bis
>   Section 5 of [RFC4338]
>   Section 8 of [RFC4391]
>   Section 4.1 of [RFC5072]
>   Section 5 of [RFC5072]
>   Section 9.1 of [RFC5121]


--Apple-Mail=_317F5B6F-66E4-410B-BE29-1D851341F3ED
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXtWICAAoJED4aXnjSQuKWtY0H/31mLbxqSOMg/UQ81tci2WbC
pvz9RUXH2JPZaXfpm2I55OH0UOsn8l+d+UvRIJnuMmIRn9Vt5QWOyyR6bBaVW2mp
PtgoRiyVC2jv/y8lxPquM9zMJamGC0FKrTTzAcxGGJFMwVVhgCh/OqcAcuxNLHPA
knp7MsBNoEmdOGNyFykPZDh8ihElzkCnfC/eULI6QgHDEK2XYBjeh829hh/KzdS5
ie212k6xMolhkO7JTU0mSgRxQOOFj/j9wBNaMfYFJ3Xda4vyKJ56wcVV7aPwdhLf
BFuYErNu/4Yi7mPndU81ZPKDPONpkWgdC2+ONcCPgZNOK05M1X8tZ+g39VAslYU=
=B3E4
-----END PGP SIGNATURE-----

--Apple-Mail=_317F5B6F-66E4-410B-BE29-1D851341F3ED--


From nobody Thu Aug 18 04:12:10 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D611A12D92A; Thu, 18 Aug 2016 04:12:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-default-iids-14.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147151872687.22090.1498661768727753843.idtracker@ietfa.amsl.com>
Date: Thu, 18 Aug 2016 04:12:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xwpSYDlQZQsQxCztxafkd2cgpIU>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 11:12:07 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance of the IETF.

        Title           : Recommendation on Stable IPv6 Interface Identifiers
        Authors         : Fernando Gont
                          Alissa Cooper
                          Dave Thaler
                          Will Liu
	Filename        : draft-ietf-6man-default-iids-14.txt
	Pages           : 9
	Date            : 2016-08-18

Abstract:
   This document changes the recommended default IID generation scheme
   for cases where SLAAC is used to generate a stable IPv6 address.  It
   recommends using the mechanism specified in RFC7217 in such cases,
   and recommends against embedding stable link-layer addresses in IPv6
   Interface Identifiers.  It formally updates RFC2464, RFC2467,
   RFC2470, RFC2491, RFC2492, RFC2497, RFC2590, RFC3146, RFC3572,
   RFC4291, RFC4338, RFC4391, RFC5072, and RFC5121.  This document does
   not change any existing recommendations concerning the use of
   temporary addresses as specified in RFC 4941.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-default-iids-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Aug 19 04:30:27 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC1512D8FB for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 04:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 SxgshMN8PQWZ for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 04:30:24 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF81712D8F0 for <ipv6@ietf.org>; Fri, 19 Aug 2016 04:30:23 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 1B771A2; Fri, 19 Aug 2016 13:30:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1471606221; bh=73jOaiSZ8y7+sj8FX3+uIjKgoS22aH6Sn4yCLmZ95/k=; h=Date:From:To:Subject:From; b=Sk/rTRYJ8PyDFKXiTXQ1DXh9r4sBE8LQfAYdD4liXbAOxWexzM5A0RT6XmZ9qSEry 29HUmBudjbb8WagklBpfde4hmcmyOz4zjE1kT7nxMs7udts9UDpO+y0s5aaEisapVw zKQcA1X264C8jSL2azRVODCtHr9NW0MWPJFBzoFk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0E259A1 for <ipv6@ietf.org>; Fri, 19 Aug 2016 13:30:21 +0200 (CEST)
Date: Fri, 19 Aug 2016 13:30:21 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ipv6@ietf.org
Subject: review of draft-ietf-6man-multi-homed-host-07
Message-ID: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/TlUJYbxXwG86_i-DpsMadQeNln8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 11:30:26 -0000

Reading it as if I never read it before.

1.1

I think the "multi-interface router (MIF)" acronym here warrants a bit 
more introduction. The word "MIF" first occurs in the diagram, before it's 
ever been defined in the document.

"Hence, if the router is a multi-interface (MIF) router"

Routers typically have multiple interfaces....?

Speaking of which, "two interfaces sharing a prefix". What does that 
mean? That they're for instance /64s from the same /56? If it's the same 
/64, then it seems this router isn't a router, it's a switch?



I then read the rest, and nothing else came up. My only thought here was 
that the document is very light on prescriptive language. It says what to 
do, but without saying exactly how. Is this on purpose, that we want to 
leave that up to the implementor? Do we foresee a v6ops document outlining 
more operational recommendations for implementors?

Apart from that, I am 100% behind the ideo of this document and it's my 
firm opinion that the kind of behaviour described in it is crucial that 
clients implement in order to enable interoperation with complex networks 
going forward.

What would be interesting to discuss is what to do with other information, 
what resolver should a client use? If it has two interfaces with two 
different prefixes and two different resolvers, should source address 
selection somehow influence (or be influenced by) what DNS resolver 
currently in use? What about other services? NTP? SMTP? I imagine we don't 
want that in this document, but I would imagine it's something that has to 
be fixed somewhere?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Aug 19 05:47:05 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD6A12D989 for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 05:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 XhDK0QXBojXp for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 05:47:02 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE7D212D98A for <ipv6@ietf.org>; Fri, 19 Aug 2016 05:46:51 -0700 (PDT)
X-AuditID: c618062d-980fb98000000a08-af-57b700b5a9bd
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id 48.0E.02568.2B007B75; Fri, 19 Aug 2016 14:51:01 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0301.000; Fri, 19 Aug 2016 08:41:42 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
Thread-Topic: review of draft-ietf-6man-multi-homed-host-07
Thread-Index: AQHR+g0fFwiejz01gEmUnM7HBMb6Sg==
Date: Fri, 19 Aug 2016 12:41:41 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyuXRPuO5Whu3hBksOyFu8PPueyeLl0q1s DkweS5b8ZPL4O+khUwBTFJdNSmpOZllqkb5dAlfGiVXdLAV/hCveX2pkaWCcLNDFyMEhIWAi 0TKPs4uRi0NIYAOjxPzVi5m6GDmBnOWMEq++JILYbEA1G3Z+BouLCHhJPJx9mhXEFhawkvjY vZIFZI6IgLXEgR4DCFNPovFAPUgFi4CqxPtV5xlBbF4BX4m1T5uYQUqEBBwlZizWAQkzCohJ fD+1Bmw4s4C4xK0n88FsCQEBiSV7zjND2KISLx//Y4WwlSTmvL7GDFGvI7Fg9yc2CFtbYtnC 18wQqwQlTs58wjKBUXgWkrGzkLTMQtIyC0nLAkaWVYwcpcUFObnpRgabGIFBfUyCTXcH4/3p nocYBTgYlXh4F3zfGi7EmlhWXJl7iFGCg1lJhFf497ZwId6UxMqq1KL8+KLSnNTiQ4zSHCxK 4rxijxTDhQTSE0tSs1NTC1KLYLJMHJxSDYxS8R9L/tqk/Tuzcrrw/a3PlV64ZRpFPFS0Yju7 f/NBI9eDOkziz/Y9iV/gpyD1+vveOg6PRRfNFnUeDFCoXvlv5VuV/SozrLfVRVysWn/p1pb2 CQ7ubFkda22O285gd1FwC1xiX1Pp4F2Zmnn769zWP1MWV2aq7rh7PniX4v6S9qOvhWu3bXNU YinOSDTUYi4qTgQAwoQXi2YCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QqXOT-r6BvhQFrq2GwMO7MMzZl8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 12:47:04 -0000

Hi Mikael,=0A=
   Thanks for your review. This document has already been evaluated by the =
=0A=
IESG and is close to being approved after the next version will be posted. =
=0A=
The IESG evaluation is here=0A=
=0A=
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/ballot/=
=0A=
=0A=
Adding new prescriptive language to this draft at this point is not going t=
o =0A=
be appropriate. If you feel strongly that there are blocking concerns with =
=0A=
the current draft, please contact the chairs, authors and me offline to =0A=
discuss the possibilities.=0A=
=0A=
Regards=0A=
Suresh=0A=
=0A=
On 08/19/2016 07:30 AM, Mikael Abrahamsson wrote:=0A=
>=0A=
> Reading it as if I never read it before.=0A=
>=0A=
> 1.1=0A=
>=0A=
> I think the "multi-interface router (MIF)" acronym here warrants a bit=0A=
> more introduction. The word "MIF" first occurs in the diagram, before it'=
s=0A=
> ever been defined in the document.=0A=
>=0A=
> "Hence, if the router is a multi-interface (MIF) router"=0A=
>=0A=
> Routers typically have multiple interfaces....?=0A=
>=0A=
> Speaking of which, "two interfaces sharing a prefix". What does that=0A=
> mean? That they're for instance /64s from the same /56? If it's the same=
=0A=
> /64, then it seems this router isn't a router, it's a switch?=0A=
>=0A=
>=0A=
>=0A=
> I then read the rest, and nothing else came up. My only thought here was=
=0A=
> that the document is very light on prescriptive language. It says what to=
=0A=
> do, but without saying exactly how. Is this on purpose, that we want to=
=0A=
> leave that up to the implementor? Do we foresee a v6ops document outlinin=
g=0A=
> more operational recommendations for implementors?=0A=
>=0A=
> Apart from that, I am 100% behind the ideo of this document and it's my=
=0A=
> firm opinion that the kind of behaviour described in it is crucial that=
=0A=
> clients implement in order to enable interoperation with complex networks=
=0A=
> going forward.=0A=
>=0A=
> What would be interesting to discuss is what to do with other information=
,=0A=
> what resolver should a client use? If it has two interfaces with two=0A=
> different prefixes and two different resolvers, should source address=0A=
> selection somehow influence (or be influenced by) what DNS resolver=0A=
> currently in use? What about other services? NTP? SMTP? I imagine we don'=
t=0A=
> want that in this document, but I would imagine it's something that has t=
o=0A=
> be fixed somewhere?=0A=
>=0A=
=0A=


From nobody Fri Aug 19 06:32:57 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3806412DA30; Fri, 19 Aug 2016 06:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham 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 y8NSTmloowfi; Fri, 19 Aug 2016 06:32:55 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF3DE12D531; Fri, 19 Aug 2016 06:32:16 -0700 (PDT)
X-AuditID: c618062d-980fb98000000a08-38-57b70b5abb28
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id ED.34.02568.A5B07B75; Fri, 19 Aug 2016 15:36:27 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0301.000; Fri, 19 Aug 2016 09:27:59 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Subject: Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Thread-Topic: Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Thread-Index: AQHR+h1+T+6QUJfxZEebJBuRK6JsgA==
Date: Fri, 19 Aug 2016 13:27:56 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyuXRPgm409/Zwg59zGC12T5nGZvHy7Hsm i6mP3zM5MHssWfKTKYAxissmJTUnsyy1SN8ugSujbXNVwRWmitOXFjA2MPYwdTFyckgImEi8 f9TE1sXIxSEksIFR4u/qZawQznJGiSd/lrGDVLEBVW3Y+RmsQ0Sgh1HiwjVVEFtYoFSi89A0 Roh4lcTsw7/YIGw9if6eZjCbRUBVYvuGk8wgNq+Ar8TBZ62sILYQkP2ppwGsl1FATOL7qTVg 85kFxCVuPZkPdZ2AxJI955khbFGJl4//sULYShIff89nh6jXkViw+xMbhK0tsWzha6hdghIn Zz5hmcAoPAvJ2FlIWmYhaZmFpGUBI8sqRo7S4oKc3HQjg02MwOA+JsGmu4Px/nTPQ4wCHIxK PLwLvm8NF2JNLCuuzD3EKMHBrCTCW8uyPVyINyWxsiq1KD++qDQntfgQozQHi5I4r9gjxXAh gfTEktTs1NSC1CKYLBMHp1QDY3rov24rw/pZ5z++/y5aZ2pUzX6Gt613k6JFWOOdU752Fr15 dozHvvVeWrhuDb+dQGv77ZuTD6zQKVqVlDZdOcTk/sXaB9ucpf5u45/pLHs8VzWl6SdvqIDc i4P+3rWVBvlyB2RtnM8Zv76aczJWi/30hdQyUXdDbZYDO1+U/w8Mnclrd/yjEktxRqKhFnNR cSIA4ffLQGoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/D4Zlj9K355dlvWPIe09Rg4TzuOs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 13:32:56 -0000

Hi all,=0A=
   Thanks to all who contributed to this thread (both on the mailing list a=
nd =0A=
offline). My conclusion at this point is that this vulnerability is related=
 =0A=
to how ND is implemented on certain nodes and there is no urgent protocol =
=0A=
work necessary to address it.=0A=
=0A=
Regards=0A=
Suresh=0A=
=0A=


From nobody Fri Aug 19 13:27:21 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B769B12B047 for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 13:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9JQYJ38WEm7y for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 13:27:16 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 74BE512B01C for <ipv6@ietf.org>; Fri, 19 Aug 2016 13:27:16 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id p64so12496958pfb.1 for <ipv6@ietf.org>; Fri, 19 Aug 2016 13:27:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=jtNLp5pSpWYTy1ONRvdjx/lKOztrzRNGvOHilBb4qnI=; b=FIHFVCo6eORthBopTSfW2TPirpDXhUxY892qFCickNCAR+vTtKuOJCdxRj73fe/pN3 wTiXNwz6MBUUUfkKliA5gWqC24QbK00P9Q6q0MPBc3h5y6hV0J7vr5cmy/6RNSbTgaAe Nujq0mfvA/wT/oT93qPWlZ9I5ro+j2LFsJ0cTQ6tP9OskKM6nM+jJh2sOZU10R90Me6V qKPQ+hWJ0aVqHsKDtYKOViyUxoGMNfP9VxzKbb4/XFOyJGpzWi1edFYDgCK65fpPGZoU JRAahr9oulQe1hW6E0Q6gySK0ye0EVnc0lD7SANfRULPqWjiz/w43ib89hLRTSq4vAT7 oT1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=jtNLp5pSpWYTy1ONRvdjx/lKOztrzRNGvOHilBb4qnI=; b=bKV9jXcu79ZdJ1k+AmPlIe+OjWpiqgKedRloRu65QWmSvDHng9/r8YDAp8I9LiDU7E +OFHa+sDBBuTcHwSE8tQvPzcJr51mTXiycP6tMzp0DRm/zx30h0Q46mzZ3rPfj5PXdAq MM9pHNoODUnbifsHlBRZ70khkKf+gw0Od8RPShqx2TYehvfpdpLQXm3byrwyf27sfZzF Ux/5c4XyhOC6e5wmqGwuEOqYB37T70rER1uf4FiGJvgpc9833gmzLoKg1NxNie3W6BNm UIfxFMHW/gyjaX0vHpow39zeM87rZsDnhET8VL+J6w7sV+JGsuliWnkfNDn8xsQSyPXj Nkyg==
X-Gm-Message-State: AEkoousdtDY3ixmGD7FeZYViOQgoxSmXNRCgIEognvNfR68pqm733ljltTGfABsdMDj/Wg==
X-Received: by 10.98.149.22 with SMTP id p22mr17469588pfd.88.1471638435957; Fri, 19 Aug 2016 13:27:15 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.121.237]) by smtp.gmail.com with ESMTPSA id sy7sm13548498pac.42.2016.08.19.13.27.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2016 13:27:15 -0700 (PDT)
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Mikael Abrahamsson <swmike@swm.pp.se>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com>
Date: Sat, 20 Aug 2016 08:27:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xh3xEa-ZCRkzRIA_jfU2r-acpcs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 20:27:19 -0000

On 20/08/2016 00:41, Suresh Krishnan wrote:
> Hi Mikael,
>    Thanks for your review. This document has already been evaluated by the 
> IESG and is close to being approved after the next version will be posted. 
> The IESG evaluation is here
> 
> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/ballot/
> 
> Adding new prescriptive language to this draft at this point is not going to 
> be appropriate. If you feel strongly that there are blocking concerns with 
> the current draft, please contact the chairs, authors and me offline to 
> discuss the possibilities.

There is going to be another spin of the document to address concerns that came
up at the very end of IETF Last Call and during IESG review - just waiting
for the last word from the IESG discussion. But my own opinion is that to
add more normative language is very difficult, because the details are mixed
up with implementation choices. What we have done, as you'll see when the
next version appears, is to be more precise about which bits of RFC 4861 are
extended.

Beyond that, see
https://mailarchive.ietf.org/arch/msg/v6ops/6r_FOp8DGRZ0PjhmhCiXoi_AM2Y

   Brian

> 
> Regards
> Suresh
> 
> On 08/19/2016 07:30 AM, Mikael Abrahamsson wrote:
>>
>> Reading it as if I never read it before.
>>
>> 1.1
>>
>> I think the "multi-interface router (MIF)" acronym here warrants a bit
>> more introduction. The word "MIF" first occurs in the diagram, before it's
>> ever been defined in the document.
>>
>> "Hence, if the router is a multi-interface (MIF) router"
>>
>> Routers typically have multiple interfaces....?
>>
>> Speaking of which, "two interfaces sharing a prefix". What does that
>> mean? That they're for instance /64s from the same /56? If it's the same
>> /64, then it seems this router isn't a router, it's a switch?
>>
>>
>>
>> I then read the rest, and nothing else came up. My only thought here was
>> that the document is very light on prescriptive language. It says what to
>> do, but without saying exactly how. Is this on purpose, that we want to
>> leave that up to the implementor? Do we foresee a v6ops document outlining
>> more operational recommendations for implementors?
>>
>> Apart from that, I am 100% behind the ideo of this document and it's my
>> firm opinion that the kind of behaviour described in it is crucial that
>> clients implement in order to enable interoperation with complex networks
>> going forward.
>>
>> What would be interesting to discuss is what to do with other information,
>> what resolver should a client use? If it has two interfaces with two
>> different prefixes and two different resolvers, should source address
>> selection somehow influence (or be influenced by) what DNS resolver
>> currently in use? What about other services? NTP? SMTP? I imagine we don't
>> want that in this document, but I would imagine it's something that has to
>> be fixed somewhere?
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Fri Aug 19 13:49:39 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 590CC12D0EF; Fri, 19 Aug 2016 13:49:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-multi-homed-host-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147163977535.24261.14806227864209999216.idtracker@ietfa.amsl.com>
Date: Fri, 19 Aug 2016 13:49:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/2l3ksEEav3UZk3PI6_h4Je4Be_8>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 20:49:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance of the IETF.

        Title           : First-hop router selection by hosts in a multi-prefix network
        Authors         : Fred Baker
                          Brian Carpenter
	Filename        : draft-ietf-6man-multi-homed-host-08.txt
	Pages           : 14
	Date            : 2016-08-19

Abstract:
   This document describes expected IPv6 host behavior in a scenario
   that has more than one prefix, each allocated by an upstream network
   that is assumed to implement BCP 38 ingress filtering, when the host
   has multiple routers to choose from.  It also applies to other
   scenarios such as the usage of stateful firewalls that effectively
   act as address-based filters.  Host behavior in choosing a first-hop
   router may interact with source address selection in a given
   implementation.  However, the selection of the source address for a
   packet is done before the first-hop router for that packet is chosen.
   Given that the network or host is, or appears to be, multihomed with
   multiple provider-allocated addresses, that the host has elected to
   use a source address in a given prefix, and that some but not all
   neighboring routers are advertising that prefix in their Router
   Advertisement Prefix Information Options, this document specifies to
   which router a host should present its transmission.  It updates RFC
   4861.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Aug 19 14:04:04 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8297112B03D for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 14:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 UjObBZD1DRIa for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 14:03:57 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 4666612B039 for <ipv6@ietf.org>; Fri, 19 Aug 2016 14:03:57 -0700 (PDT)
Received: by mail-pa0-x231.google.com with SMTP id hb8so761068pac.2 for <ipv6@ietf.org>; Fri, 19 Aug 2016 14:03:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=d6+h/Uw0pClQ7Oz2IIjzry4ikpZNY1wDLjbich0G280=; b=lFGbF6NNdU4eQVGaG7I9p2PEgQT3ZQ4T9IEdDiOn3l8Q+NRkHr4rjfaJWvffQaMok0 cN8H1qIAS8dVr1WjEFIEVQdAniQmbtk3HVIa/k5ZQWDFSg9ZVBgR2g6MjfXOLm40tN55 rHCEqbV2aVR2flm2PZOae4Ef7u16B6DyBDJDi65yQRhlCKaosnXk06cP+r7krdkCnLDr Uqcj+1KtuA53odYabLE+4GXBvzC7P+7gs7xx4mVvjNmYstzhURVY/aY+q4cp9RyP3ZHZ Mnhd3vuzA8bhE+3+tL3PlSBn/D8hrd51WJyzM52gJ5usm+qp0H6j+zv0D4PFttxRZKzq /BoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=d6+h/Uw0pClQ7Oz2IIjzry4ikpZNY1wDLjbich0G280=; b=Ag/+l788yfiTbsDsVgfinPzRf+ir1TrT13ETTWHjdMNDB41QRJI9kZFf8U64xHeqw/ ZaY7FvFVz6aIjrJ2H+H3fPf3PwuNXv08J3LpQJNLuwWJbMxTXaAc1dOn3JBM/ay859jP ClqZTqXY8VwgastR9xfvNbRZ+98iPwLu2FjIH6HkYmvbjlFyRP3o4Fl4CTxNJA4DFg1k PxQHp0sCkfhrmPkNCr0T62vCrJYh2ELI77nQ+mHPS8/J8ebUiYeURw5HycUWUWxzPpX0 sT19oaS+T8b9RAnOi9LoRUKXtgSAVQ2u0//X8M5/5JSB8WG6/9S7es/AKrYbzwPOoBYT j5Ig==
X-Gm-Message-State: AEkoouvrvWIiPS4wY18xQt5jICvP+T6HE0cYQseRisdcmKKLqMtha8a0YLLYf0Z1tuGUuw==
X-Received: by 10.66.185.14 with SMTP id ey14mr17622484pac.71.1471640636577; Fri, 19 Aug 2016 14:03:56 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.121.237]) by smtp.gmail.com with ESMTPSA id g24sm8677708pfk.56.2016.08.19.14.03.54 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2016 14:03:55 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-multi-homed-host-08.txt
References: <147163977535.24261.14806227864209999216.idtracker@ietfa.amsl.com>
To: ipv6@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <51346806-3a7a-7072-5657-79fdc7060925@gmail.com>
Date: Sat, 20 Aug 2016 09:04:04 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <147163977535.24261.14806227864209999216.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/w9usrHUFuLeqa-jHgeWq-QLR5qQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Aug 2016 21:04:03 -0000

This version includes various clarifications and improvements following
Last Call and IESG comments. There are not intended to be any substantive changes.

   Brian

On 20/08/2016 08:49, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance of the IETF.
> 
>         Title           : First-hop router selection by hosts in a multi-prefix network
>         Authors         : Fred Baker
>                           Brian Carpenter
> 	Filename        : draft-ietf-6man-multi-homed-host-08.txt
> 	Pages           : 14
> 	Date            : 2016-08-19
> 
> Abstract:
>    This document describes expected IPv6 host behavior in a scenario
>    that has more than one prefix, each allocated by an upstream network
>    that is assumed to implement BCP 38 ingress filtering, when the host
>    has multiple routers to choose from.  It also applies to other
>    scenarios such as the usage of stateful firewalls that effectively
>    act as address-based filters.  Host behavior in choosing a first-hop
>    router may interact with source address selection in a given
>    implementation.  However, the selection of the source address for a
>    packet is done before the first-hop router for that packet is chosen.
>    Given that the network or host is, or appears to be, multihomed with
>    multiple provider-allocated addresses, that the host has elected to
>    use a source address in a given prefix, and that some but not all
>    neighboring routers are advertising that prefix in their Router
>    Advertisement Prefix Information Options, this document specifies to
>    which router a host should present its transmission.  It updates RFC
>    4861.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-08
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-08
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Fri Aug 19 20:51:44 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87A5D12D599 for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 20:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 iyT1fk-JcRtO for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 20:51:41 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC94112D593 for <ipv6@ietf.org>; Fri, 19 Aug 2016 20:51:40 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 3340DA2; Sat, 20 Aug 2016 05:51:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1471665097; bh=yXlFnCq2I5PAT3yoJPVtayzGsg0eTiXnJufUm3/mmQw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=fbzMcjqAbGnLp9wbbxbqma5rotLGiGMI8wGtPLZ+ro5LstC+h32Z4wDAhvp1ed8q6 nRPn1AaSRJb5hHNVtexk9PvWfmUFikdz9DUu3wq2utRsm2+kxbf6FfOVsyPvm7mbvq 1/Z9J5pQtNaRbspCtkf6YkreRateO5KLSdpPrt04=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 1F83CA1; Sat, 20 Aug 2016 05:51:37 +0200 (CEST)
Date: Sat, 20 Aug 2016 05:51:37 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
In-Reply-To: <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com>
Message-ID: <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/P5pA9at-wdYakuUnNRsEXTHN5og>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 03:51:43 -0000

On Sat, 20 Aug 2016, Brian E Carpenter wrote:

> On 20/08/2016 00:41, Suresh Krishnan wrote:
>> Hi Mikael,
>>    Thanks for your review. This document has already been evaluated by the
>> IESG and is close to being approved after the next version will be posted.
>> The IESG evaluation is here
>>
>> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/ballot/
>>
>> Adding new prescriptive language to this draft at this point is not going to
>> be appropriate. If you feel strongly that there are blocking concerns with
>> the current draft, please contact the chairs, authors and me offline to
>> discuss the possibilities.
>
> There is going to be another spin of the document to address concerns that came
> up at the very end of IETF Last Call and during IESG review - just waiting
> for the last word from the IESG discussion. But my own opinion is that to
> add more normative language is very difficult, because the details are mixed
> up with implementation choices. What we have done, as you'll see when the
> next version appears, is to be more precise about which bits of RFC 4861 are
> extended.
>
> Beyond that, see
> https://mailarchive.ietf.org/arch/msg/v6ops/6r_FOp8DGRZ0PjhmhCiXoi_AM2Y

Ok, I understand. I think the document is fine without prescriptive 
language, the result is just that I think we'll end up with a future v6ops 
document giving guidance on these topics. I think that's fine as well.

But my other comment regarding MIF and the shared prefix still stands, if 
there is a document respin could you please take a look at my comment and 
see if minor edit can be made to clarify that for the reader?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Aug 19 21:10:07 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AF512D54F for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 21:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 e54eI0qfiXm8 for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 21:10:04 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (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 0856812D114 for <ipv6@ietf.org>; Fri, 19 Aug 2016 21:10:04 -0700 (PDT)
Received: by mail-pa0-x22f.google.com with SMTP id pp5so21407992pac.3 for <ipv6@ietf.org>; Fri, 19 Aug 2016 21:10:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=PgP/FoYysh+G96JZo0rRF6PYlHKtM7kuuA5GOOY6zNc=; b=ytJPKPjjGrN2t7SWypvw48hcjzEyH25ouL8ebZtHk8v/1n2LuH+4veHOh2b1BZq5Xp SnCHAPHM0fGX9h5qRBcWmz+LhEzhW11Q/MT4mKtmt6Atpef+ArPPj00q5Tbht0+8i5Tw JgtJi4zPAeWr3Zvs88fl17S/uFIwiWEfepEsM6p68O7BC8cO5tNwOvzIErJ8bJjHSKs2 f9HqAF/0oHBDdpxRGLipuWlU/6d8naKxrKnb6TLYihmKznU1iCYvnmloToMwM80bOf8j FOdvz2xNLo/A2FbkqzMob7UhkfkVQ8Q1cfu5nz8livqwsYImqctj+t7ydSlaBUWjDxKN 41GQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=PgP/FoYysh+G96JZo0rRF6PYlHKtM7kuuA5GOOY6zNc=; b=R7l97z/zlF4XWy3zsu6+aR25KKqcRAacM62TsUM9kXkFWSVWsdXhII9mWOsDfUlWoA AIg472VQiNrVuprUzOAn+Pgca/h9rNvDphbv1MxD6nizjnhiDgm9OIXCJqoSSBj7nTPx e7+93zxWgj7R5qhqYWC8LU9lHzMpigYJK/uSK1Xv7l5O86G22Xby+ZRMa+Nd/enm2Y2s 7l+ueIXyzbU/Vqc8A5G+ahXjJt0NQrmwXIWlnyexIymcbOajAD4varFYVQa0/d0Trb2o LeHwUA5uIkpr/UJJt4Mkj9AYisMFNUpUQr1LtDP94igNWGRPyKIXn328u5VQKNXJiIlE A8GA==
X-Gm-Message-State: AEkoouvefgdnPxtBwq8jHhhqGZCNVu+bIA8xdz/tIQ8Yb8lgg35PnxDsnvzLx5rEEXhbtA==
X-Received: by 10.66.249.201 with SMTP id yw9mr20540011pac.130.1471666203621;  Fri, 19 Aug 2016 21:10:03 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.71.16]) by smtp.gmail.com with ESMTPSA id 18sm9895303pfn.33.2016.08.19.21.10.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Aug 2016 21:10:02 -0700 (PDT)
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com>
Date: Sat, 20 Aug 2016 16:10:11 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UHyW1bFwCSI5x9vYnzWsDatp9CE>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 04:10:06 -0000

On 20/08/2016 15:51, Mikael Abrahamsson wrote:
> On Sat, 20 Aug 2016, Brian E Carpenter wrote:
> 
>> On 20/08/2016 00:41, Suresh Krishnan wrote:
>>> Hi Mikael,
>>>    Thanks for your review. This document has already been evaluated by the
>>> IESG and is close to being approved after the next version will be posted.
>>> The IESG evaluation is here
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/ballot/
>>>
>>> Adding new prescriptive language to this draft at this point is not going to
>>> be appropriate. If you feel strongly that there are blocking concerns with
>>> the current draft, please contact the chairs, authors and me offline to
>>> discuss the possibilities.
>>
>> There is going to be another spin of the document to address concerns that came
>> up at the very end of IETF Last Call and during IESG review - just waiting
>> for the last word from the IESG discussion. But my own opinion is that to
>> add more normative language is very difficult, because the details are mixed
>> up with implementation choices. What we have done, as you'll see when the
>> next version appears, is to be more precise about which bits of RFC 4861 are
>> extended.
>>
>> Beyond that, see
>> https://mailarchive.ietf.org/arch/msg/v6ops/6r_FOp8DGRZ0PjhmhCiXoi_AM2Y
> 
> Ok, I understand. I think the document is fine without prescriptive 
> language, the result is just that I think we'll end up with a future v6ops 
> document giving guidance on these topics. I think that's fine as well.
> 
> But my other comment regarding MIF and the shared prefix still stands, if 
> there is a document respin could you please take a look at my comment and 
> see if minor edit can be made to clarify that for the reader?

Yep. I changed the caption in the figure. I didn't change the text
about "MIF" because I couldn't really see putting "multiple, i.e. more
than two" and I think the figure makes it fairly clear.

(If English had a word for "more than two" that would be great. Actually,
some dictionaries claim that "several" means "more than two" but I think
that is a very academic definition and not helpful for the international
readership of RFCs.)

Rgds
    Brian


From nobody Fri Aug 19 21:38:04 2016
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4FCF12D5BE for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 21:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.548
X-Spam-Level: 
X-Spam-Status: No, score=-5.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 XmHbGHrFVqUv for <ipv6@ietfa.amsl.com>; Fri, 19 Aug 2016 21:38:01 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38E1412B05A for <ipv6@ietf.org>; Fri, 19 Aug 2016 21:38:01 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 477B5A2; Sat, 20 Aug 2016 06:37:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1471667879; bh=Qytz5o8KBQXs/Xl6hixlgU5/KieFZJYkCET/crN2LVQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=VV5pOGPqRIlcs8BotcL705gn0EYXf1O0iwkWVHf/XNTPsc5ZU7nJx92U/vYsnHr74 tUMTxs2nMmcoJpZnZAYV6i7KpY6zPZUSKpbfgRTPTnJ/MdQ/ZLA2awlQNfzjjZZEv4 Ovkq/8nrseBE3RSr5PRptuH3Wk/gsLApj+ICUsH0=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 405F7A1; Sat, 20 Aug 2016 06:37:59 +0200 (CEST)
Date: Sat, 20 Aug 2016 06:37:59 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
In-Reply-To: <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com>
Message-ID: <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se> <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/o78p-i05JUYAbfUhE4V6MRe18Hs>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 04:38:02 -0000

On Sat, 20 Aug 2016, Brian E Carpenter wrote:

> Yep. I changed the caption in the figure. I didn't change the text
> about "MIF" because I couldn't really see putting "multiple, i.e. more
> than two" and I think the figure makes it fairly clear.
>
> (If English had a word for "more than two" that would be great. Actually,
> some dictionaries claim that "several" means "more than two" but I think
> that is a very academic definition and not helpful for the international
> readership of RFCs.)

Ok, that was my lesser concern. The "sharing a prefix" is much bigger.

               +-----------------+
               |                 |
               |     MIF Router  +---/--- other interfaces
               |                 |
               +---+---------+---+
                   |         | Two interfaces sharing a prefix
                 --+-+--   --+-+--
                     |         |
                  +--+---------+--+
                  |   MIF Host    |
                  +---------------+

                 Figure 1: Hypothetical MIF interconnection


"Two interfaces sharing a prefix"

I spent 5-10 minutes pondering 1.1 and I still can't figure it out. I see 
a router, it has two interfaces. I have to take for granted that this 
router has routed ports, and typically routers don't allow for overlapping 
address space, so these two ports would have different /64s? Or are they? 
So what's the prefix shared? Upstream /56? Now I'm just guessing.

So I just can't figure it out. Or is this a router with a built in switch 
and it's the same /64 on both ports? I just think there is clarification 
needed in 1.1, and if there is a re-spin, I think the document would be 
better if that could happen.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Sat Aug 20 10:00:47 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B31DE12D0E7; Sat, 20 Aug 2016 10:00:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-default-iids-15.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147171243773.2624.6433457624362093749.idtracker@ietfa.amsl.com>
Date: Sat, 20 Aug 2016 10:00:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/sOtkRwK-Jdp11kl9ylNTLKIx7sg>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 17:00:38 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance of the IETF.

        Title           : Recommendation on Stable IPv6 Interface Identifiers
        Authors         : Fernando Gont
                          Alissa Cooper
                          Dave Thaler
                          Will Liu
	Filename        : draft-ietf-6man-default-iids-15.txt
	Pages           : 9
	Date            : 2016-08-20

Abstract:
   This document changes the recommended default IID generation scheme
   for cases where SLAAC is used to generate a stable IPv6 address.  It
   recommends using the mechanism specified in RFC7217 in such cases,
   and recommends against embedding stable link-layer addresses in IPv6
   Interface Identifiers.  It formally updates RFC2464, RFC2467,
   RFC2470, RFC2491, RFC2492, RFC2497, RFC2590, RFC3146, RFC3572,
   RFC4291, RFC4338, RFC4391, RFC5072, and RFC5121.  This document does
   not change any existing recommendations concerning the use of
   temporary addresses as specified in RFC 4941.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-default-iids-15

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Aug 21 07:28:02 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7583512B059; Sun, 21 Aug 2016 07:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Get8HpApHPH0; Sun, 21 Aug 2016 07:27:58 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 8222F12B01A; Sun, 21 Aug 2016 07:27:58 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id l203so120867461oib.1; Sun, 21 Aug 2016 07:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IRIg6RiEqEKzB89KAywhxjUeUhfYpY5qebjDWhKQgBg=; b=qyvrcZXZeEdTM+i6V1MlgjQdfkveEePPCq3/vyrbcXrF8f+GuUenAYIvAAJfUw2ZO9 Lyd3toBBZ88tiF4V1rGZt9N7e0Wip0+p51CTfC6lqq62Vz7QSgFwtQ9DN514A3ZXncnE iD6jYXP0iEhrO3lCnFvh6XhATPSnfFcleaSOOfkILn+yngKZieXSNbDmpkF9AabZ8RKr pcO9zcmuqw/o71Q/LLKD0nM6HL7Gxh6ECxM67VKj+/2IVJrk8hparemcUEhn7757ndIh JWCGKfibWAnT72hIFDVnHB5nJ3bCpGsA+TdlpZ9sjsXxH2fwLz4LxoZqdad2dAs3IawT GcvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IRIg6RiEqEKzB89KAywhxjUeUhfYpY5qebjDWhKQgBg=; b=bbmmhzS/O4Y+cy3F1LmBZhzJB1Fn/QNGeHeXR7ObgkHXdR+9b1ahFx4wVNBbx4fPvk uIWK/1cMmEpnjgH2wJmJAyQGxL8n/IdMBSTQihkHQ3N0/hRJEDjWUf+bO07ht6jUUsLV 6x5MzZDnwjtrWltLhA9IXNQ7Mu/efJtTuFXr+FX9nltt8ommCkPpcDI3Ff8jZO5qIlx8 RW/nyxMbl8v0OskaKm0oHp7lBg/ZMZ/MCq9lA/QB0e0OsKHojeNvzj8H+SmVPn45uukG NomcoFI7eOFykq+W6XVZVrOsIMM4li841+NJKmkcvm+p8KkNmmXP0Y9GfCD9eJrrR/OC 4HkQ==
X-Gm-Message-State: AEkoouuDYjKPNDVyINCiU3EE0zQ9Dn0JAK/B/ZGIdr5cpj4wwguDrAOpU2U6b6C7xNAzM73zs2RBEy1hU/LZsA==
X-Received: by 10.157.9.39 with SMTP id 36mr9751639otp.138.1471789677671; Sun, 21 Aug 2016 07:27:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Sun, 21 Aug 2016 07:27:57 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se>
From: Hemant Singh <hemantietf@gmail.com>
Date: Sun, 21 Aug 2016 10:27:57 -0400
Message-ID: <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com>
Subject: Re: Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c04f1e0ebffff053a95bc47
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SNR63iAYTzxjNI9KcGviq4LGZes>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2016 14:28:00 -0000

--94eb2c04f1e0ebffff053a95bc47
Content-Type: text/plain; charset=UTF-8

Agree.

A thought, based on what Fernando said in the following post related to
intermediate nodes.

https://mailarchive.ietf.org/arch/msg/ipv6/LuYc34TlaqICmZkd6yh4yDHYuRg


For intermediate nodes, such as a router, to catch such packet the router
needs DPI.   Wouldn't it have been nice, if ND packets used a different
ethertype so that a router forwarding packets at 200 Gbps would still be
easily able to filter the ND packets such as for this Crafted ND DOS
packets?  The router could invoke actions such as sending the packets to a
recycle queue for more inspection or since the packet is filtered already,
the fast path could inspect a fixed offset in the packet for the Hop Limit
and see if it's not 255, drop the packet.   As I said in the past IP and
ARP uses different ethertypes.

One would have to evaluate how often is hardware thrown away for various
IPv6 nodes and see how to phase in an ethertype change for IPv6 ND.

Hemant


On Fri, Aug 19, 2016 at 9:27 AM, Suresh Krishnan <
suresh.krishnan@ericsson.com> wrote:

> Hi all,
>    Thanks to all who contributed to this thread (both on the mailing list
> and
> offline). My conclusion at this point is that this vulnerability is related
> to how ND is implemented on certain nodes and there is no urgent protocol
> work necessary to address it.
>
> Regards
> Suresh
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--94eb2c04f1e0ebffff053a95bc47
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Agree. =C2=A0<div><br></div><div>A thought, based on what =
Fernando said in the following post related to intermediate nodes.<div><br>=
</div><div><a href=3D"https://mailarchive.ietf.org/arch/msg/ipv6/LuYc34Tlaq=
ICmZkd6yh4yDHYuRg">https://mailarchive.ietf.org/arch/msg/ipv6/LuYc34TlaqICm=
Zkd6yh4yDHYuRg</a><br></div><div><br></div><div><br></div><div>For intermed=
iate nodes, such as a router, to catch such packet the router needs DPI. =
=C2=A0 Wouldn&#39;t it have been nice, if ND packets used a different ether=
type so that a router forwarding packets at 200 Gbps would still be easily =
able to filter the ND packets such as for this Crafted ND DOS packets?=C2=
=A0 The router could invoke actions such as sending the packets to a recycl=
e queue for more inspection or since the packet is filtered already, the fa=
st path could inspect a fixed offset in the packet for the Hop Limit and se=
e if it&#39;s not 255, drop the packet. =C2=A0 As I said in the past IP and=
 ARP uses different ethertypes.</div><div><br></div><div>One would have to =
evaluate how often is hardware thrown away for various IPv6 nodes and see h=
ow to phase in an ethertype change for IPv6 ND.=C2=A0</div><div><br></div><=
div>Hemant</div><div><br></div></div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Fri, Aug 19, 2016 at 9:27 AM, Suresh Krishnan =
<span dir=3D"ltr">&lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" targe=
t=3D"_blank">suresh.krishnan@ericsson.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Hi all,<br>
=C2=A0 =C2=A0Thanks to all who contributed to this thread (both on the mail=
ing list and<br>
offline). My conclusion at this point is that this vulnerability is related=
<br>
to how ND is implemented on certain nodes and there is no urgent protocol<b=
r>
work necessary to address it.<br>
<br>
Regards<br>
Suresh<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</blockquote></div><br></div>

--94eb2c04f1e0ebffff053a95bc47--


From nobody Sun Aug 21 15:54:19 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD4012D1E3; Sun, 21 Aug 2016 15:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 kTWFTz6TWBYh; Sun, 21 Aug 2016 15:54:11 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 6159D12D567; Sun, 21 Aug 2016 15:54:10 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id l203so129237813oib.1; Sun, 21 Aug 2016 15:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qV3Mm3ILIO609CQcL7zYGH3mByL49vZ9SUEET3sfIts=; b=NglRrGlVxKxsp0J6mVu4ZWZ770bwJn6TDyZLs9W1t7wyyoEAsCUTow5iHRqK2mjbw0 p/gi5o1mccOlCF4N6O+3dwV1Zz1G4t92GTvV+z6FDY4yzfZymHQNhBAvd61suALkeA3x 8m9P5lCcguK6Vk8ztlrSsjWnkhL+LLv1ZkMVAImeckyoUzlbVng8Isto6dI3TKEbuTFy Do6gftcd4Nm30iEzMO/Z44otExTJkN+eXA67dT6FT/Ue/fbR8conOb19CZW/Qb7hM5F/ AQ6GwOnbMaTIXjsl7FJo/KwoSkGEzq5J2Ver8MgDj/0GFxvRix0lO1zLulfqf099L21y T4/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qV3Mm3ILIO609CQcL7zYGH3mByL49vZ9SUEET3sfIts=; b=FeBza/9ffs/iOnijFAL7xK/26w096jl76k4dGdVsNAj9U6DkWoA6ujNAIKnx0Ltv1K ugbnRvNBLcngnDCHemWiIsV23HhWElYLW9zZXD1ixmy4hZ5IjpYrXgM2FZoDoZPobkrG mzMt+1fs5No405oz1HfMCv/TBTcAK1EQK0aiByHieg2AkT7QDeBso5Anjzam0Pk/FaIk WNha2e505KQaFXciQEmeo6OGf3VsD1GiH46aOUvcC9CuImkTWdzyM8onAfgzu2SQrxv6 kdSpuYtGnUOy2YdIui/JvKecsOO9z0qWHMpH/mPBiTbwILE9xhwhNaEAiCikvHqjggXl 43Fg==
X-Gm-Message-State: AEkoousKePPK2j0Svuz4bWCyqRl8GQz5GJmkN//w0TAmv1JukIJWQqIuCtFSkkWg9S3Rxbau+GQyqcO1Xl/BQA==
X-Received: by 10.202.45.4 with SMTP id t4mr10917956oit.34.1471820049813; Sun, 21 Aug 2016 15:54:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Sun, 21 Aug 2016 15:54:09 -0700 (PDT)
In-Reply-To: <m1bbY2J-0000I5C@stereo.hq.phicoh.net>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net>
From: Hemant Singh <hemantietf@gmail.com>
Date: Sun, 21 Aug 2016 18:54:09 -0400
Message-ID: <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com>
Subject: Re: Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: Philip Homburg <pch-v6ops-5@u-1.phicoh.com>
Content-Type: multipart/alternative; boundary=001a1137b5043e176e053a9ccf25
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ktuGSkFoWCXnAmQn6BPFvoGhkW0>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, v6ops@ietf.org, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2016 22:54:13 -0000

--001a1137b5043e176e053a9ccf25
Content-Type: text/plain; charset=UTF-8

Not quite.  I am specifically comparing ND to ARP which has its own
ethertype while ND does not.   I am not proposing a new ethertype for
crafted packets in attack vectors.   Obviously there was no firewall in
many deployments where this crafted ND packet went through or there was a
firewall which did not catch the crafted packet.  The new ethertype for ND
and another uses.  It can be used to to filter packets for a DAD or ND
Proxy implementation.

Hemant


On Sun, Aug 21, 2016 at 3:03 PM, Philip Homburg <pch-v6ops-5@u-1.phicoh.com>
wrote:

>
>
> In the past, a device that filters out traffic that hosts should not
> receive was called a 'firewall'.
>
> I guess it would be nice if every different type of a packet that a
> firewall needs to recognize would get a different ether type, but I'm sure
> that that's not going to happen.
>
> I think it is safe to assume that a firewall can scan TCP and UDP traffic
> at wire speed, so it doesn't seem unreasonable to assume that the same can
> be done for ND traffic.
>
>
>

--001a1137b5043e176e053a9ccf25
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Not quite.=C2=A0 I am specifically comparing ND to ARP whi=
ch has its own ethertype while ND does not. =C2=A0 I am not proposing a new=
 ethertype for crafted packets in attack vectors. =C2=A0 Obviously there wa=
s no firewall in many deployments where this crafted ND packet went through=
 or there was a firewall which did not catch the crafted packet.=C2=A0 The =
new ethertype for ND and another uses.=C2=A0 It can be used to to filter pa=
ckets for a DAD or ND Proxy implementation.<div><br></div><div>Hemant<br><d=
iv><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Au=
g 21, 2016 at 3:03 PM, Philip Homburg <span dir=3D"ltr">&lt;<a href=3D"mail=
to:pch-v6ops-5@u-1.phicoh.com" target=3D"_blank">pch-v6ops-5@u-1.phicoh.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><=
br>
<br>
</span>In the past, a device that filters out traffic that hosts should not=
<br>
receive was called a &#39;firewall&#39;.<br>
<br>
I guess it would be nice if every different type of a packet that a<br>
firewall needs to recognize would get a different ether type, but I&#39;m s=
ure<br>
that that&#39;s not going to happen.<br>
<br>
I think it is safe to assume that a firewall can scan TCP and UDP traffic<b=
r>
at wire speed, so it doesn&#39;t seem unreasonable to assume that the same =
can<br>
be done for ND traffic.<br>
<br>
<br>
</blockquote></div><br></div></div></div></div>

--001a1137b5043e176e053a9ccf25--


From nobody Sun Aug 21 16:41:22 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E16B127058; Sun, 21 Aug 2016 16:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qV6iuLW43jdh; Sun, 21 Aug 2016 16:41:20 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::22f]) (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 E4F1C12D0F7; Sun, 21 Aug 2016 16:41:19 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id n59so161917521uan.2; Sun, 21 Aug 2016 16:41:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xK0qC6OS2BURv8wP50XYDQPrcAbS7zke2x7eVkTT57Y=; b=eGcI+Sl1gm41zQ3UEjxvILr1Ub92B0baYyPEWLf7V2Ig88f1D/OS9omki8yLteD8M2 bEV2rEeeiReYfv2emxlV2SzJh0daRl5lCWCXD4D/LyaJsueJljA4iVTlC2b6gyUALOXM wQseoEowK84eZkVj4lImJGKKsoWThe/HGk9HctwzHuO8V6eDerHyo7E/uuhehZexxlh7 otMD4rm0ZaEOVqSjmrRxD94v/WB1WAB/IgFteXvlKT7E3MZLVQUaVnlCyHYdlwkCXRf4 vciOuzLo3i0VauuBvTlgdW4vrghO+Q8coJWeAYgFfG1HwcVa/xcuGZg2AIdlKj29mrDu BxUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xK0qC6OS2BURv8wP50XYDQPrcAbS7zke2x7eVkTT57Y=; b=fv2UYgK3+m8w6qvCYKBS3oERuF/iF80Rq2KS3j9ye4Mfi8t/VlMdUw/yCqv3jCNdZo ciNv+ja3h06XWvrabBvl5EscNnqdrKtMwaWiVXBWLkoZld66CaNTd+XMrxrXpSoTmP7m M2618rnph0vIRWTxorvyNYVSVAL85ozEcHJvP7ERA8dZXYK3kkcMmgEVsnCMij0GKWML fwEFhEbAW75GgQHWJwb3B8USSfVJBeMaYvsaKPjyx92S73bEvgkmlB9nUzFLnfA/lBc2 UXlbvZPTQEQS6inHbSaIyNCY9smmaYJmIF1KHAAW1BDwcxlLsQUw+nsWiz5xhTbyyILV Vhmw==
X-Gm-Message-State: AEkooutiJlfZzmNuGRnthLdIDDaCpYYhMN/2bkYPZy8tpsD7uV0opYiXOQnOd6sKXRVi8JWclGCFSK/kVvPuRg==
X-Received: by 10.31.98.133 with SMTP id w127mr8539212vkb.29.1471822878891; Sun, 21 Aug 2016 16:41:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Sun, 21 Aug 2016 16:40:48 -0700 (PDT)
In-Reply-To: <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 22 Aug 2016 09:40:48 +1000
Message-ID: <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com>
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: Hemant Singh <hemantietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FBRFqb23OSGptXhN9qh6r46Iei4>
Cc: Philip Homburg <pch-v6ops-5@u-1.phicoh.com>, v6ops list <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Aug 2016 23:41:21 -0000

On 22 August 2016 at 08:54, Hemant Singh <hemantietf@gmail.com> wrote:
> Not quite.  I am specifically comparing ND to ARP which has its own
> ethertype while ND does not.   I am not proposing a new ethertype for
> crafted packets in attack vectors.   Obviously there was no firewall in many
> deployments where this crafted ND packet went through or there was a
> firewall which did not catch the crafted packet.  The new ethertype for ND
> and another uses.  It can be used to to filter packets for a DAD or ND Proxy
> implementation.
>

Sort of seems to be a lot of effort to mitigate what is fundamentally
a problem of not following very clear processing requirements in
RFC4861 by the target node:

"A node MUST silently discard any received Neighbor Solicitation
   messages that do not satisfy all of the following validity checks:

      - The IP Hop Limit field has a value of 255, i.e., the packet
        could not possibly have been forwarded by a router."

Writing more specifications to mitigate against people not completely
following existing specifications only creates more new specifications
they may not follow completely either.

Does anyone have any insights into how multiple implementations might
have missed or perhaps intentionally decided not to perform this
validity check? It seems a bit unusual that two different commonly
used implementations didn't do it (I just checked the Linux and
FreeBSD source and they do perform the check.)

In cases such as this, perhaps implementation checklists (perhaps as
an RFC appendix) could assist either the implementer or a code
reviewer in ensuring they've implemented things completely.

Regards,
Mark.

> Hemant
>
>
> On Sun, Aug 21, 2016 at 3:03 PM, Philip Homburg <pch-v6ops-5@u-1.phicoh.com>
> wrote:
>>
>>
>>
>> In the past, a device that filters out traffic that hosts should not
>> receive was called a 'firewall'.
>>
>> I guess it would be nice if every different type of a packet that a
>> firewall needs to recognize would get a different ether type, but I'm sure
>> that that's not going to happen.
>>
>> I think it is safe to assume that a firewall can scan TCP and UDP traffic
>> at wire speed, so it doesn't seem unreasonable to assume that the same can
>> be done for ND traffic.
>>
>>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>


From nobody Sun Aug 21 19:05:01 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B5412B03A; Sun, 21 Aug 2016 19:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 9MNFGmrNSpUQ; Sun, 21 Aug 2016 19:04:59 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 EF15F120727; Sun, 21 Aug 2016 19:04:58 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id l203so132719964oib.1; Sun, 21 Aug 2016 19:04:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fGXGC0dEr9VLAQOCp0gCa/YsEvwfnQ5btYxjH1wuKb4=; b=N1J0t4kWAmQ6OcqrhaFaREOW0dlhFtJXecEpD9/YvBfnXGRnxq02amptSlpLToVW2I TYeNCCQ0SWsrdQ/giOrLeiaGj4rp/1ZPEOOnBRV23lU2/UjoUkxCrCMwwpynarp7Ldpz oOn0mFDI+Oml4YxlLeEP1aAY4VZY+TvtCVrs9jisMFp+XjDrP5+IFknWNM5UXvhhYm5p r1izPRTYWJ+OVCTKAjCcOzcNUuvx3nEJpfpPF6IqT3+CVnPGOKof6ZjcSXTbm5Vt9NHr k+em5mcKOvpwq1tpyR7OVrQ9S5e+iYOccTj6Nlym+YXTj5L6FgUWau787r5Nqch/DgC9 VNZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fGXGC0dEr9VLAQOCp0gCa/YsEvwfnQ5btYxjH1wuKb4=; b=IeMskv2wXLTfB5OHBQ6KfMjmJ0Wk/jKS/moex/iUp3dzanWweLJYx5GwfFrfJkdofa MFHSrAnHfYtyjDxDcWP4l929fqeiz3Zs6JGJ527sbG5Mw8Cm17cqVvOaiLlOrg6HqRST qJ9yIJJmmqZyrdTW3rJ9SLWu8iB2z75rhWr/DU14jzNiJACHHcKybORmp4fLjjWDw0ow GQKysGZQF7TkyGQ10qnkUq2CCodhU98czqfliE4/qNpjLa0xyEGjQsh2fFp50sN4c9up DvqCKplnceBAKVH40+t7sG517YzomVWVXf5cJC2Mp0/lvnflXVAKaIEpGPkKYdChM9HD MqeQ==
X-Gm-Message-State: AEkoouvDH1HBHm70iio11WGewXXCeHbc6w8g+DdvpNjncOHIqoQaNT+SvielSQ1bUMVADDBKOcu86I0HetKipw==
X-Received: by 10.202.91.66 with SMTP id p63mr10437586oib.55.1471831498299; Sun, 21 Aug 2016 19:04:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Sun, 21 Aug 2016 19:04:57 -0700 (PDT)
In-Reply-To: <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com>
From: Hemant Singh <hemantietf@gmail.com>
Date: Sun, 21 Aug 2016 22:04:57 -0400
Message-ID: <CABdyVt651B6VPvQXD_kSdy+yGusGxmEcPe=u-DWB9_VAvFuyOQ@mail.gmail.com>
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a113d54c0a02091053a9f795c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/HtrZQeJ9j332K9gdQkXt_gPFiAU>
Cc: Philip Homburg <pch-v6ops-5@u-1.phicoh.com>, v6ops list <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 02:05:00 -0000

--001a113d54c0a02091053a9f795c
Content-Type: text/plain; charset=UTF-8

Mark,

It's been already discussed why some nodes missed it and I have also
pointed out that RFC4861 spells out the requirement clearly.   Thanks for
the reminder again.

The reason some nodes missed it because the nodes are high-end routers
forwarding traffic at high rate such as 200 Gbps.  Such a router's data
plane has to perform DPI (Deep Packet Inspection) to catch this crafted ND
packet and the router's data plane incurs the DPI cost on every forwarded
packet.  This is why some routers do not perform the check and forwarded
the packet instead of dropping the packet.

Another error happened that an end node receiving the packets did not drop
it but decided to issue an address resolution, and thus the cpu the packets
are punted to, got inundated.  The end host should have checked the Hop
Limit and dropped the packet.

Regards,

Hemant


On Sun, Aug 21, 2016 at 7:40 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

>
> Sort of seems to be a lot of effort to mitigate what is fundamentally
> a problem of not following very clear processing requirements in
> RFC4861 by the target node:
>
> "A node MUST silently discard any received Neighbor Solicitation
>    messages that do not satisfy all of the following validity checks:
>
>       - The IP Hop Limit field has a value of 255, i.e., the packet
>         could not possibly have been forwarded by a router."
>
> Writing more specifications to mitigate against people not completely
> following existing specifications only creates more new specifications
> they may not follow completely either.
>
> Does anyone have any insights into how multiple implementations might
> have missed or perhaps intentionally decided not to perform this
> validity check? It seems a bit unusual that two different commonly
> used implementations didn't do it (I just checked the Linux and
> FreeBSD source and they do perform the check.)
>
> In cases such as this, perhaps implementation checklists (perhaps as
> an RFC appendix) could assist either the implementer or a code
> reviewer in ensuring they've implemented things completely.
>
> Regards,
> Mark.
>
>

--001a113d54c0a02091053a9f795c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Mark,<div><br></div><div>It&#39;s been already discussed w=
hy some nodes missed it and I have also pointed out that RFC4861 spells out=
 the requirement clearly. =C2=A0 Thanks for the reminder again. =C2=A0</div=
><div><br></div><div>The reason some nodes missed it because the nodes are =
high-end routers forwarding traffic at high rate such as 200 Gbps.=C2=A0 Su=
ch a router&#39;s data plane has to perform DPI (Deep Packet Inspection) to=
 catch this crafted ND packet and the router&#39;s data plane incurs the DP=
I cost on every forwarded packet.=C2=A0 This is why some routers do not per=
form the check and forwarded the packet instead of dropping the packet. =C2=
=A0</div><div><br></div><div>Another error happened that an end node receiv=
ing the packets did not drop it but decided to issue an address resolution,=
 and thus the cpu the packets are punted to, got inundated.=C2=A0 The end h=
ost should have checked the Hop Limit and dropped the packet.=C2=A0</div><d=
iv><br></div><div>Regards,</div><div><br></div><div>Hemant</div><div><br><d=
iv class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Aug 21, 201=
6 at 7:40 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmi=
th@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
</span>Sort of seems to be a lot of effort to mitigate what is fundamentall=
y<br>
a problem of not following very clear processing requirements in<br>
RFC4861 by the target node:<br>
<br>
&quot;A node MUST silently discard any received Neighbor Solicitation<br>
=C2=A0 =C2=A0messages that do not satisfy all of the following validity che=
cks:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 - The IP Hop Limit field has a value of 255, i.e., the=
 packet<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 could not possibly have been forwarded by a rou=
ter.&quot;<br>
<br>
Writing more specifications to mitigate against people not completely<br>
following existing specifications only creates more new specifications<br>
they may not follow completely either.<br>
<br>
Does anyone have any insights into how multiple implementations might<br>
have missed or perhaps intentionally decided not to perform this<br>
validity check? It seems a bit unusual that two different commonly<br>
used implementations didn&#39;t do it (I just checked the Linux and<br>
FreeBSD source and they do perform the check.)<br>
<br>
In cases such as this, perhaps implementation checklists (perhaps as<br>
an RFC appendix) could assist either the implementer or a code<br>
reviewer in ensuring they&#39;ve implemented things completely.<br>
<br>
Regards,<br>
Mark.<br>
<span class=3D""><br></span></blockquote></div></div></div></div>

--001a113d54c0a02091053a9f795c--


From nobody Sun Aug 21 22:32:57 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E1312D113; Sun, 21 Aug 2016 22:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 8Hg4Fyjconpu; Sun, 21 Aug 2016 22:32:50 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 AC97E12B006; Sun, 21 Aug 2016 22:32:50 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id k90so170647353uak.1; Sun, 21 Aug 2016 22:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GjlCDU3o42llXOQfQq4+lScw4U6p5FkNci/2FY9ZbHQ=; b=ceHZzD4DVrvMo/uTqoxgnMZL3yIt8ukaH/ySWTJVkbhoEiGceptwRGOHTw2VQHchTn X4VqiwF0O9NoxqYMqeBXTjwMaQzWk1qw4UuqU8rIpDK1GrJ0AuRD5xYMZWxwvRfm6WsQ RlFj52vz9IzAjd/Codkl5JEArQQc5orQ9FuKhsBoju3e3VCIjY4Yp9bagfBBw7Ggitsd pJEs9WL0Hr0irTZEg2rOsXP2hGkSAFZ5QeG73aXz+qHoBi4uolRVkan4HzFGPCJZvNO/ oYIEqwbEDDUQDzyKN8h0CZ1SKr178TcoR6ShM60TRJEQzKwYVsvTcj/vFyM681OXYuq8 5FGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GjlCDU3o42llXOQfQq4+lScw4U6p5FkNci/2FY9ZbHQ=; b=aZC4Q7BBRVxH/cGmD/pdY0iy0KcImE2JlbuR5bIrW9iKyz+uJeATmf4Zz85hTGMEBV DjUhT/ioX65YMRLBmQPMIDHQ5RzEY4VJh/N1ktDc3QaLqSDzhUPtNJBPMeLc3xhOszL7 UZvfLQpMb9leO0XzuKux8fEt6EdqoHegv5O0hg4jTzEYHooHHhhL/bQ/tV7DVVJ2Zhwy bKZIRex4w86lVPRq9l5Q6gJdzoOaV0z+P2UWz4kuR+gPSYq+6Aendb2KWXUlEezXDLS8 8BqtSXXpKKGrS7f4JIk14Kcgglo6hAcTuRhk1FFoZarnp2Lq/s5Gmm5Z9HuD5KxW91YJ KokQ==
X-Gm-Message-State: AEkoouukqBvitlzVoFrD8/LFcNBzVIhequ4qHOkmO+IHtFCg2R9MJ68doVlGOcV2c4XmxMrIFOB8FSP9btDaEg==
X-Received: by 10.176.80.58 with SMTP id b55mr10352081uaa.118.1471843969655; Sun, 21 Aug 2016 22:32:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Sun, 21 Aug 2016 22:32:19 -0700 (PDT)
In-Reply-To: <CABdyVt651B6VPvQXD_kSdy+yGusGxmEcPe=u-DWB9_VAvFuyOQ@mail.gmail.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <CABdyVt651B6VPvQXD_kSdy+yGusGxmEcPe=u-DWB9_VAvFuyOQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 22 Aug 2016 15:32:19 +1000
Message-ID: <CAO42Z2zXbyzE5eFPG1UAcV1z6RWz2v-kzNv=YCSQC8c49EzUEw@mail.gmail.com>
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: Hemant Singh <hemantietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/DrKMHZMisLyHWf6Lin960KfZzEU>
Cc: Philip Homburg <pch-v6ops-5@u-1.phicoh.com>, v6ops list <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 05:32:52 -0000

On 22 August 2016 at 12:04, Hemant Singh <hemantietf@gmail.com> wrote:
> Mark,
>
> It's been already discussed why some nodes missed it and I have also pointed
> out that RFC4861 spells out the requirement clearly.   Thanks for the
> reminder again.
>
> The reason some nodes missed it because the nodes are high-end routers
> forwarding traffic at high rate such as 200 Gbps.  Such a router's data
> plane has to perform DPI (Deep Packet Inspection) to catch this crafted ND
> packet and the router's data plane incurs the DPI cost on every forwarded
> packet.  This is why some routers do not perform the check and forwarded the
> packet instead of dropping the packet.
>

So this sort of issue has also popped up recently with forwarding of
packets with link-local source and GUA destination addresses off-link
- routers are purely forwarding based on destination address for
performance reasons.

It has also popped up with the HBH header - RFC2460bis is loosening
the HBH processing requirement for routers, again for performance
reasons.

Forgetting for the moment about how Source Address Dependent Routing
might change this whole space, perhaps we need to loosen the
requirement that these sorts of checks must be performed at each and
every hop.

Instead, view them as checks to be performed either by the first hop
router or by the last hop router where appropriate (e.g., how we view
BCP38 checks), and allow them to be disabled on trusted router to
router hops for performance, at the possible cost of occasionally
forwarding packets that shouldn't be if they're originated within the
network somehow (e.g., router control plane bug). (I've sort of been
thinking this way a bit already, which is why I was thinking the
HL==255 check is only to be performed by the receiving host, and the
use of the term 'node' should have really been 'host' in RFC4861).

Ideally it would be good if there was a way to automate whether to
enable or them or not e.g., between a pair of routers, the link is
known to be a true point-to-point link, or the set of neighbor cache
entries exactly match the routing protocol neighbors, or all of the
neighbors in the neighbor cache have the Router flag set. (or, as they
seem to be being disabled by default now, it could be as simple as
enabling them if there is at least one neighbor cache entry that
doesn't have the Router flag set).

> Another error happened that an end node receiving the packets did not drop
> it but decided to issue an address resolution, and thus the cpu the packets
> are punted to, got inundated.  The end host should have checked the Hop
> Limit and dropped the packet.
>

So in summary, the HL=255 check actually wasn't being performed in two
different places, and if it had been being performed in one of them,
it attack wouldn't have succeeded:

- intermediate routers weren't performing it

- the ND NS target hosts (control plane of the router implementations)
weren't performing it either


Regards,
Mark.


From nobody Mon Aug 22 01:35:58 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC9C12B00D; Mon, 22 Aug 2016 01:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 L8aIZZqk_RrP; Mon, 22 Aug 2016 01:35:52 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F8DA12B00A; Mon, 22 Aug 2016 01:35:51 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Aug 2016 08:35:50 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 3C1069CC82; Mon, 22 Aug 2016 01:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=8HgVdbCZZXepeYSr+uq0bifZjdI=; b= s9Uji1Ax2lfq7E5OV5PoyE5TciVfczHm35sIIVuX0z8Mt/NIYLLuQ5mvyxYn80nb qoAwfErEKt4l49UVi2i9IxTv7Ebq32TX1H9qwN+M3geqaZ+X4FUG4cnpmGR9jRGS FQUILcnSEG2mRNHz330ill4eKPaRnZqL49Bfz5W4w74=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=FP5gMyEECZ/TGKQD58I68Xgga3 8mqj0u/fIV+ZIiwxnQrIpWMnN/m8ASYAutb7GXuT7bH8UoJ3GUHH2vmVlzIgoZYJ 7ANDe01GFl8t/g+jRe2feQdYIE9tC5qBQh4ryFwZy5GwMQas8EEjs7Ul8eczKux4 JTaNtiesMg1kHwJBQ=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id BF7C79CC81; Mon, 22 Aug 2016 01:35:48 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 32F7434B1969; Mon, 22 Aug 2016 10:35:48 +0200 (CEST)
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_20991388-CB14-427D-B696-95A3946359FB"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com>
Date: Mon, 22 Aug 2016 10:35:47 +0200
Message-Id: <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/v9MzNyf1BZIZulJgN5RrYTKvRa4>
Cc: 6man WG <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 08:35:54 -0000

--Apple-Mail=_20991388-CB14-427D-B696-95A3946359FB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark,

>> Not quite.  I am specifically comparing ND to ARP which has its own
>> ethertype while ND does not.   I am not proposing a new ethertype for
>> crafted packets in attack vectors.   Obviously there was no firewall =
in many
>> deployments where this crafted ND packet went through or there was a
>> firewall which did not catch the crafted packet.  The new ethertype =
for ND
>> and another uses.  It can be used to to filter packets for a DAD or =
ND Proxy
>> implementation.
>>=20
>=20
> Sort of seems to be a lot of effort to mitigate what is fundamentally
> a problem of not following very clear processing requirements in
> RFC4861 by the target node:
>=20
> "A node MUST silently discard any received Neighbor Solicitation
>   messages that do not satisfy all of the following validity checks:
>=20
>      - The IP Hop Limit field has a value of 255, i.e., the packet
>        could not possibly have been forwarded by a router."
>=20
> Writing more specifications to mitigate against people not completely
> following existing specifications only creates more new specifications
> they may not follow completely either.
>=20
> Does anyone have any insights into how multiple implementations might
> have missed or perhaps intentionally decided not to perform this
> validity check? It seems a bit unusual that two different commonly
> used implementations didn't do it (I just checked the Linux and
> FreeBSD source and they do perform the check.)
>=20
> In cases such as this, perhaps implementation checklists (perhaps as
> an RFC appendix) could assist either the implementer or a code
> reviewer in ensuring they've implemented things completely.

The issue isn't about the hop limit validation check not being done (it =
is), it is about _where_ it is done.
A packet is determined to be for the router itself, the hardware =
forwarding plane then needs to decide if it should process the packet =
itself, punt the packet to software or drop it. There might be orders of =
magnitude difference in pps capability between software and hardware.

Is there anything we can learn from this?
We have to consider in protocol design how expensive it is to determine =
if a forus() packet should be dropped or not.
Looking deep into a packet to determine it is an ND packet and then do =
the validity checks in hardware might not be optimal.
Perhaps ND packets should have been limited to using link-local =
addresses only.

In-band signalling is fraught with dangers.

Cheers,
Ole

--Apple-Mail=_20991388-CB14-427D-B696-95A3946359FB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXurljAAoJED4aXnjSQuKWuXQIAJZHBsnwuRbVUSp9njmNvFw7
AsADCdgFSnAaNJQl15dxSJr6Kkxa4CZIJsCzH1Wu6UhgEPvO4NWxyzXJ3/dLPfT9
+iu2aT87dy3aUUMEmqMmHEcIx/PbjoVB10vnp8Jw79SNw8o+glhGk8hk1mv1DdpQ
bNeL3VUo4UkTuFTef1lbXZ1YXTUhd1Q6j2cfBcv7/gwN3rIGn74XpYJ8q3+t8XaN
rWR7bN6UqyvFDrEXfVvk6gZ0ZodSg+zpfw7GCzh01bMUt7OpIufZcBR2NuUFjGhr
RK/3jBmmhhWp5RK7ji1UEc1d3oOICz4gOHpkFXtrNR1/kj2abOM3E5w57MXl/00=
=buaf
-----END PGP SIGNATURE-----

--Apple-Mail=_20991388-CB14-427D-B696-95A3946359FB--


From nobody Mon Aug 22 03:24:13 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B868812D12F for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 03:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 Mpae_APwFnk9 for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 03:24:11 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C3BA12D113 for <ipv6@ietf.org>; Mon, 22 Aug 2016 03:24:11 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Aug 2016 10:24:09 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E90E99CC51; Mon, 22 Aug 2016 03:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=eGg0ZZ8O0pQxpCkpa2ObpZUMcg8=; b= q+lyPZLthldX4GGctVQgnCsGuf04ILmCI1BPSzK1A5qsU4lOXQmZZCmpldeyKvPc hEi3FboiZZPrE7Wdm2pJyDdcXF7iOAPjZJOPX34Xgme6N0OoVHoUohRM2QT+hefP PJIJUXDSiJChxusn3chqEQ/fjq5o51wTVt+Db0pUBDk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=TXRGcOz2v2BByegdrWQbNpsYFw nWSjyUxyGpoUMzYptBnZZaGJstk1x7rp8nSBdkbFpWbL/KJxMhK7hUkbHaitXZ0m RxlkEq+uGsW4XTM2bchcpdLfTfWw7SKkwc/ymkkp0ZvIPIpgLCYBcovj/he/8x/1 pzNoblCjKnR+LFmrU=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 752849CC4E; Mon, 22 Aug 2016 03:24:08 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 08E1034DE9F7; Mon, 22 Aug 2016 12:24:05 +0200 (CEST)
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_151243F9-5F63-4C1E-88D7-FD23CB38BBF9"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se>
Date: Mon, 22 Aug 2016 12:24:04 +0200
Message-Id: <80C83445-2B99-4A7C-B039-E073DED71EC1@employees.org>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se> <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com> <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UzSFkSlV8FBWRLPaQDNvaTS4pc4>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 10:24:12 -0000

--Apple-Mail=_151243F9-5F63-4C1E-88D7-FD23CB38BBF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> Yep. I changed the caption in the figure. I didn't change the text
>> about "MIF" because I couldn't really see putting "multiple, i.e. =
more
>> than two" and I think the figure makes it fairly clear.
>>=20
>> (If English had a word for "more than two" that would be great. =
Actually,
>> some dictionaries claim that "several" means "more than two" but I =
think
>> that is a very academic definition and not helpful for the =
international
>> readership of RFCs.)
>=20
> Ok, that was my lesser concern. The "sharing a prefix" is much bigger.
>=20
>              +-----------------+
>              |                 |
>              |     MIF Router  +---/--- other interfaces
>              |                 |
>              +---+---------+---+
>                  |         | Two interfaces sharing a prefix
>                --+-+--   --+-+--
>                    |         |
>                 +--+---------+--+
>                 |   MIF Host    |
>                 +---------------+
>=20
>                Figure 1: Hypothetical MIF interconnection
>=20
>=20
> "Two interfaces sharing a prefix"
>=20
> I spent 5-10 minutes pondering 1.1 and I still can't figure it out. I =
see a router, it has two interfaces. I have to take for granted that =
this router has routed ports, and typically routers don't allow for =
overlapping address space, so these two ports would have different /64s? =
Or are they? So what's the prefix shared? Upstream /56? Now I'm just =
guessing.
>=20
> So I just can't figure it out. Or is this a router with a built in =
switch and it's the same /64 on both ports? I just think there is =
clarification needed in 1.1, and if there is a re-spin, I think the =
document would be better if that could happen.

Re-reading this I also share your confusion.

While the section explors the weak/strong host models and tries to =
exemplify the problem, I think the example might be a little confusing =
as Mikael points out.

"Two interfaces sharing a prefix"; (assuming we're talking onlink =
prefixes here) can only happen for fe80::/10 right?

"For example, a host with a link-local-only interface and a default =
route pointing to that interface"

What if this text is removed:

   Hence, if the router is a multi-interface (MIF) router and is using =
the same prefix on two or more
   LANs shared by the host (as in Figure 1), the host might use each of
   those LANs and meet the requirement.

And s/Two interfaces sharing a prefix/Link-local only prefix/ in the =
caption.

Cheers,
Ole



--Apple-Mail=_151243F9-5F63-4C1E-88D7-FD23CB38BBF9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXutLEAAoJED4aXnjSQuKWqEYH/30jJnfnIO3R/ubzzWpzHK0w
KY2+xuH0x9YbDBRl94Qio2OG5bcQIFf4HWzmVuKHyEDO1IVQNiBYKY6EZGYTLH7K
p8bbri5SUKnKV6Ni8D9F9o+AjZFhTPuKXl/pKIV7QXPVbZzcsh4rlBFocy4d+ahX
wGVOzIgwqe7Jfh9x28mzccxJvbViXvs/LiWMz3A/Yk49eaw1HsdRGH/H8TuGOMEo
53hbuqplZoP4n2T0fHs0VOyNNB8K9H+1nIq6U4dARdPd0oX93arnd15WO6MEHnLc
bigGReA+D3Gzl50fwWSJj+BzLwN6/RYyAxrlV2cXAHa36iImzs+UVNC5tk/VsFM=
=C2i3
-----END PGP SIGNATURE-----

--Apple-Mail=_151243F9-5F63-4C1E-88D7-FD23CB38BBF9--


From nobody Mon Aug 22 05:33:30 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6FD12D190; Mon, 22 Aug 2016 05:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 UuKjcKoqKu4Y; Mon, 22 Aug 2016 05:33:26 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7893F12D197; Mon, 22 Aug 2016 05:33:07 -0700 (PDT)
Received: from [2a02:c0:2:4:1194:17:0:1006] (port=48328 helo=envy) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1bboPX-0000tX-AU; Mon, 22 Aug 2016 14:33:03 +0200
Date: Mon, 22 Aug 2016 14:33:02 +0200
From: Tore Anderson <tore@fud.no>
To: otroan@employees.org
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Message-ID: <20160822143302.2da13b80@envy>
In-Reply-To: <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vSRvnn4Teq5X-MhV9jWPrdGWiuc>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 12:33:28 -0000

* otroan@employees.org

> The issue isn't about the hop limit validation check not being done
> (it is)

Are you certain that it is? Both Cisco CSCuz66542 and Juniper JSA10749
describe how the crafted ND packets will be *processed* by the control
plane - not dropped.

Furthermore, both advisories go on to describe how successful
exploitation might cause the device to stop handling *IPv6* traffic
specifically - as opposed to impacting *all* traffic.

While the advisories don't go into detail, this suggests to me that
successful exploitation of the issue is dependent on the crafted
packets actually being able to manipulate/overwhelm the IPv6 neighbour
caches. That couldn't happen if the hop limit validation was done and
the packet was dropped - even though this was done in software, by the
control plane itself.

> A packet is determined to be for the router itself, the hardware
> forwarding plane then needs to decide if it should process the packet
> itself, punt the packet to software or drop it. There might be orders
> of magnitude difference in pps capability between software and
> hardware.

Sure. If you're able to bombard the control plane with packets,
bypassing any hardware ACL, you're most likely going to be successful
in taking down the box.

However such an attack will not only impact IPv6 (it will offline
everything), nor is there any reason to single out ICMPv6 ND packets as
particularly problematic.

That is: if you're able to saturate the link bandwith between the
control plane and the forwarding plane and/or generate enough PPS to
overwhelm the control plane's CPU (even though it's only going to drop
the packets), then it doesn't really matter what the packets contain.

So I think there's more to this story than a simple volumetric DoS
attack against the control plane that's not being stopped by the
hardware forwarding plane.

Tore


From nobody Mon Aug 22 05:39:58 2016
Return-Path: <gert@space.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D4DF12D126 for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 05:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=unavailable 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 3sLl9BqNro9p for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 05:39:55 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E84112D1AD for <ipv6@ietf.org>; Mon, 22 Aug 2016 05:39:53 -0700 (PDT)
X-Original-To: ipv6@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0CC0E606F9 for <ipv6@ietf.org>; Mon, 22 Aug 2016 14:39:51 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 948F76010F; Mon, 22 Aug 2016 14:39:50 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 82BED306C3; Mon, 22 Aug 2016 14:39:50 +0200 (CEST)
Date: Mon, 22 Aug 2016 14:39:50 +0200
From: Gert Doering <gert@space.net>
To: otroan@employees.org
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Message-ID: <20160822123950.GW79185@Space.Net>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4ih6EAWNdpxH16r3"
Content-Disposition: inline
In-Reply-To: <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/EILRhEwYZAOux9KontZWeG9MjlU>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 12:39:56 -0000

--4ih6EAWNdpxH16r3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Aug 22, 2016 at 10:35:47AM +0200, otroan@employees.org wrote:
> Perhaps ND packets should have been limited to using link-local addresses=
 only.

Indeed...  (that's the conclusion I reached after building an ACL that
permits only valid combinations of link-local, unspecified and GUA addresses
for each external interface a router is connected to).

ARP is not so bad, in retrospective.  Can't be routed, can't be ACLed by
too-strict IP ACLs, doesn't use multicast, ...

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--4ih6EAWNdpxH16r3
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXuvKTAAoJEN9WwGXkzn/F0XUQAJzLwS8cZPyncehb3tbyNDmB
ri+G07VYxCPa0Ks8X3lokY8n6StgjJLonysEEN9eRYVPESiotir+AtHP5kR9U7wR
iJUbpfxPbTwz8kOc1537FNUaeUQSLtv5YXwXHnXQEXl6mz7yKd0N5gJZ7J2zJIDZ
8iQB19/lo76dtE9ARZ505Akz706xDNCo3/ifUfVZ/I2MYIxXmK0Nw1d/4BMd5+BD
D0RhZzcue3uo9IaVtSD5519FgWO0XP9Bzqrq+SXbAtSGVnO4W2Sf9FIClkQf97vq
vdymu7DvuDl0epHODth2QkL8lLBuabZamSoIp5IhbaiNGIVglXhfrQy4uQGxvDuP
iyHTplf8CkHLTIaOzIpqvQxror0uxtLeTcvuIg/6NGfwYJ7wV1vPuEvhD7mYrVlM
F2fQj+SMoFUHPoNBvrbvs/2iyJtuqb7pfCEC9lwaCCZB/3pG5uwdnUh7MW4WrF8V
Xh3xzZW1YE8f3cvD+4UcTU4VKNyel1tAtPNG4JnhzXqDGA3anJptJF9Yj4VTPGSY
K2r/LfpEVkZF6vviDXfFjEC2VlafaYBVMqEjkux2jl6f3sUA+bibJURm80EwDYnj
RAZgVlvD9zt4yYPsY7mFZ7u1mz1UQ1JWY7XRGuLZ6oOW60UI6BJ/wd1bGABlvbLU
R6Lpy79YluG8qjdzrvsF
=lrls
-----END PGP SIGNATURE-----

--4ih6EAWNdpxH16r3--


From nobody Mon Aug 22 06:36:07 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 442E812D193; Mon, 22 Aug 2016 06:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 k_bc-0JiOBQW; Mon, 22 Aug 2016 06:36:04 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E98012D13B; Mon, 22 Aug 2016 06:36:04 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Aug 2016 13:36:03 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 188FC9CC4F; Mon, 22 Aug 2016 06:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=YEUXEbSaaHtcCdXhX46Jtbc91ow=; b= rJ2I14KI4dd/QWeQQG2bfJWC+92ddbuYOO2rtfq+zGUxQ85/O1KgcMXREh70rDLn lu8ERIPsOnUBQSLMsLdOsJfn5tdOglpm60Yrx7oSePj13E3X8CI9dAVPFd2VqtnA de1/CvH5qR77ZBpnXCV3RhzOgkc0Hz92Sl2ivD5g/oY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=ADeIFuWXfpPJwVrBNm6MnjzVRE nu+ybKr/Yz1ba55x2MdE29J78CAB7eK2ptVrFU4TqFxbybmlHADVbftw4eWi3S/c A3ADT41a2rPPwc1ogtjqxwM85n8Dvk/J3eG7zx/fphTg9T1F4015SgzvKnTuy2hZ fr8K3KdfQb1w1cHpo=
Received: from h.hanazo.no (unknown [173.38.220.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id DAE4B9CC4E; Mon, 22 Aug 2016 06:36:01 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id BE146352E44F; Mon, 22 Aug 2016 15:35:59 +0200 (CEST)
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B5A99C13-5E12-4691-BDFD-78A966113D62"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <20160822143302.2da13b80@envy>
Date: Mon, 22 Aug 2016 15:35:59 +0200
Message-Id: <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/LjbRCIVaA2Tg-HZR8uYuk2ykBAQ>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 13:36:06 -0000

--Apple-Mail=_B5A99C13-5E12-4691-BDFD-78A966113D62
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Tore,

> * otroan@employees.org
>=20
>> The issue isn't about the hop limit validation check not being done
>> (it is)
>=20
> Are you certain that it is? Both Cisco CSCuz66542 and Juniper JSA10749
> describe how the crafted ND packets will be *processed* by the control
> plane - not dropped.
>=20
> Furthermore, both advisories go on to describe how successful
> exploitation might cause the device to stop handling *IPv6* traffic
> specifically - as opposed to impacting *all* traffic.
>=20
> While the advisories don't go into detail, this suggests to me that
> successful exploitation of the issue is dependent on the crafted
> packets actually being able to manipulate/overwhelm the IPv6 neighbour
> caches. That couldn't happen if the hop limit validation was done and
> the packet was dropped - even though this was done in software, by the
> control plane itself.

you could explain that behaviour differently.
the consequence of a massive stream of ND packets are that they will be =
heavily throttled between hardware and software forwarding planes. that =
will also impact legitimate ND packets, meaning that whatever entries =
there are in the ND cache or the replies from address resolution will =
not make it back to the ND process.

cheers,
Ole

--Apple-Mail=_B5A99C13-5E12-4691-BDFD-78A966113D62
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXuv+/AAoJED4aXnjSQuKW0cYH/iZRpq045C2Y5UAMFwx36t1Z
K4vGG/6D1gbdAVhsajZFyuKEi8zROc/PSPd9wRZfYPxSnZhzJ+1hSP4+65k+ckHf
wbleNBvNvrFqrQ4hHHycCyGCIIm9vN90JHIUFqfQYFmPAxe1KAHbPzGRFxwfs/Ly
9OsN6XYlIxgns+wBbV5sXy6ElY+RGnhHdTrrH9u6bLAABHZIeQwY1WjEENIhthgI
EZ9y1Ag4oHAC2Aa6m7YSE2ieadMXxiteZHDo+4/QJnuJ3Pqs4Oh1J3eMfS1Rhd+X
Kf6Vr3PPaKIJRdJy726/DxCgAyfRpgAkHp9kEpdbbHL916Lbf0aI4oHpLTGlXRA=
=I/tW
-----END PGP SIGNATURE-----

--Apple-Mail=_B5A99C13-5E12-4691-BDFD-78A966113D62--


From nobody Mon Aug 22 08:12:04 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C24212D792; Mon, 22 Aug 2016 08:12:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 9uEue5dK-_nV; Mon, 22 Aug 2016 08:12:00 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 822F612D645; Mon, 22 Aug 2016 08:10:50 -0700 (PDT)
Received: from [2a02:fe0:c420:314a::8b1] (port=54354 helo=envy) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1bbqsB-0005MU-6U; Mon, 22 Aug 2016 17:10:47 +0200
Date: Mon, 22 Aug 2016 17:10:46 +0200
From: Tore Anderson <tore@fud.no>
To: otroan@employees.org
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Message-ID: <20160822171046.3c62ffe7@envy>
In-Reply-To: <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy> <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Hf1XrLvwf3-o6KSFNtY1M3gp4Dk>
Cc: 6man WG <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 15:12:02 -0000

* otroan@employees.org

> Tore,
> 
> > * otroan@employees.org
> >   
> >> The issue isn't about the hop limit validation check not being done
> >> (it is)  
> > 
> > Are you certain that it is? Both Cisco CSCuz66542 and Juniper
> > JSA10749 describe how the crafted ND packets will be *processed* by
> > the control plane - not dropped.
> > 
> > Furthermore, both advisories go on to describe how successful
> > exploitation might cause the device to stop handling *IPv6* traffic
> > specifically - as opposed to impacting *all* traffic.
> > 
> > While the advisories don't go into detail, this suggests to me that
> > successful exploitation of the issue is dependent on the crafted
> > packets actually being able to manipulate/overwhelm the IPv6
> > neighbour caches. That couldn't happen if the hop limit validation
> > was done and the packet was dropped - even though this was done in
> > software, by the control plane itself.  
> 
> you could explain that behaviour differently.
> the consequence of a massive stream of ND packets are that they will
> be heavily throttled between hardware and software forwarding planes.
> that will also impact legitimate ND packets, meaning that whatever
> entries there are in the ND cache or the replies from address
> resolution will not make it back to the ND process.

Sure, but that'd just be a variation on the simple volumetric DoS,
nothing that would be unique to ND.

That is: if you rate-limit FOO packets, and someone floods you with FOO
packets, then legitimate FOO packets will be dropped and thus the
operation of the FOO protocol will be impacted. (Replace FOO with ND,
BGP, ARP, OSPF, etc.)

This is common knowledge and does not justify security advisories being
published for each possible value of FOO. Yet now we have one for ND.
So I'm not really convinced that there isn't more to this, i.e., that
the crafted ND packets in question are successfully tricking the
control plane into doing actual work/processing (beyond dropping them).

You didn't answer my question, by the way.

Tore


From nobody Mon Aug 22 10:39:55 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9CA12D7CA; Mon, 22 Aug 2016 10:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 x9km46KsgEvP; Mon, 22 Aug 2016 10:39:52 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BD0F12D169; Mon, 22 Aug 2016 10:39:51 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Aug 2016 17:39:50 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 4B9939CC51; Mon, 22 Aug 2016 10:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=PcJYsXMG2xw7s62dIrPwPeFrGyc=; b= K3OE7q7xWSKUuXOxwCls/rOFq0wD+QW5t/WdVRNxKPhuOaH002V4pcNfatco0UHW xTSXibvmMEVgh0uWHbXSjFSOR6cmTpqkJFJoSwlpl8Ha8cNhCdwvVcPNls9Gu2mB dRbv6eVN5pDcaxmvM52IaVAQKMQXYjU0bq2W4IU0mZs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=JBMaPtn/sIr+TrDFkhulWGamV9 b6rkY57rWk+CuS7F9oDHoFcCYKPWOnu203I9FQyAfFE1fH2I6QjtCe8Ru3jcKYQe aevXAyRGlxOh4+xB68xFf+/QhedGBvjA789mEhrJ45Dje8I6Q8+TGkcjjt3ZVBux 3DWobcVRIpwkbY5UU=
Received: from h.hanazo.no (cm-84.213.17.83.getinternet.no [84.213.17.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B98319CC4F; Mon, 22 Aug 2016 10:39:48 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C2E3A35322D7; Mon, 22 Aug 2016 19:39:42 +0200 (CEST)
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E105B5B0-9C9D-4877-9EFF-78A9632F1E71"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <20160822171046.3c62ffe7@envy>
Date: Mon, 22 Aug 2016 19:39:42 +0200
Message-Id: <5D8D4A35-1D8A-4D6D-A5CA-D0D2BF78CA8E@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy> <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org> <20160822171046.3c62ffe7@envy>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/SIkLQgtef-6zvCV-KmrN6ixFLw4>
Cc: 6man WG <ipv6@ietf.org>, v6ops list <v6ops@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 17:39:54 -0000

--Apple-Mail=_E105B5B0-9C9D-4877-9EFF-78A9632F1E71
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Tore,

>>> * otroan@employees.org
>>>=20
>>>> The issue isn't about the hop limit validation check not being done
>>>> (it is)
>>>=20
>>> Are you certain that it is? Both Cisco CSCuz66542 and Juniper
>>> JSA10749 describe how the crafted ND packets will be *processed* by
>>> the control plane - not dropped.
>>>=20
>>> Furthermore, both advisories go on to describe how successful
>>> exploitation might cause the device to stop handling *IPv6* traffic
>>> specifically - as opposed to impacting *all* traffic.
>>>=20
>>> While the advisories don't go into detail, this suggests to me that
>>> successful exploitation of the issue is dependent on the crafted
>>> packets actually being able to manipulate/overwhelm the IPv6
>>> neighbour caches. That couldn't happen if the hop limit validation
>>> was done and the packet was dropped - even though this was done in
>>> software, by the control plane itself.
>>=20
>> you could explain that behaviour differently.
>> the consequence of a massive stream of ND packets are that they will
>> be heavily throttled between hardware and software forwarding planes.
>> that will also impact legitimate ND packets, meaning that whatever
>> entries there are in the ND cache or the replies from address
>> resolution will not make it back to the ND process.
>=20
> Sure, but that'd just be a variation on the simple volumetric DoS,
> nothing that would be unique to ND.

I believe that's largely correct.

> That is: if you rate-limit FOO packets, and someone floods you with =
FOO
> packets, then legitimate FOO packets will be dropped and thus the
> operation of the FOO protocol will be impacted. (Replace FOO with ND,
> BGP, ARP, OSPF, etc.)
>=20
> This is common knowledge and does not justify security advisories =
being
> published for each possible value of FOO. Yet now we have one for ND.
> So I'm not really convinced that there isn't more to this, i.e., that
> the crafted ND packets in question are successfully tricking the
> control plane into doing actual work/processing (beyond dropping =
them).

Correct. I suppose with ND there is a relatively simple workaround that =
can be hardcoded. One which may not apply to any generic protocol.

> You didn't answer my question, by the way.

if I'm certain? yes, I'm quite certain. with the reservation that I'm =
not particularly familiar with XR code.

Cheers,
Ole

--Apple-Mail=_E105B5B0-9C9D-4877-9EFF-78A9632F1E71
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXuzjeAAoJED4aXnjSQuKWcz8H/R51xf89AgCTrsPodS6sFATj
mcUl+76xTyKmav+W4MLkp2WuRAXJ9kiUVMHxFJ9UE+bnDsmUYXjPm58Q4e2ME3cO
6n5DMolTrgjj8f0w+LiekgJE/14qNRgOcyN21LOGUNO4STiyTR4Lk70lb2hzpxAT
2MOY89Okg09EB1C/FUBaRqdYB+CMKh5trX08EX3AnmCPhPXBUDmrvA0BtzSykQpC
6dKX4NKujxrrWzz9PjaCGLVs5jUZoP5B6p/IMdB1/2c1mcjZL4+gyULD7op/8GDJ
WLEQtgf/ccYb6Uaf9wnXVVyCtv4JPerLh8lSXNoe8K9Pi9ObU6WJMVFnQJ5eamo=
=dzpE
-----END PGP SIGNATURE-----

--Apple-Mail=_E105B5B0-9C9D-4877-9EFF-78A9632F1E71--


From nobody Mon Aug 22 18:05:23 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B70D412D63A for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 18:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TezkafLd6Tkq for <ipv6@ietfa.amsl.com>; Mon, 22 Aug 2016 18:05:20 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (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 CD08812B015 for <ipv6@ietf.org>; Mon, 22 Aug 2016 18:05:20 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id ti13so42514115pac.0 for <ipv6@ietf.org>; Mon, 22 Aug 2016 18:05:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Vrb8N9hz8uRaPUlL/Oru0W4aNUST7+eOTjxZ3asRbNw=; b=qzOKYJqECrz98+AzUyBlJEpPSbFhMwVpZjQa1FEQsI6598Fp4UCtDX6RtP9WSheyEr 9r9dPSH3+8MC+8XCVrWJ54G0xZcP9es+B1GmADU16fSRnPD5/f6pRFLI+uj6fDj88PTa qycZUnL0FMWa5CAWaBJIdQHXq4zCiuTZZhyhHtVAljazKnBqGp8SKrl5yGDEfiBT2TYa zWZN1hPB7hfDbv3YEoASIMtUd7ZwF5EYyZI1m3yl6XGHEk6i+tL5rBHx3qBea4emEoqn ASPJUJf8pe/TeLbWLk9SdWepoV5fk3FokckGieR9r1VlYiKv0ZDX4jnvlQDfxGokwe4S aFNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Vrb8N9hz8uRaPUlL/Oru0W4aNUST7+eOTjxZ3asRbNw=; b=N4nNzDTzVQdUwJeFQvjw0RS0RRvWh2AEzJ8zjPugHaZR8KS8cs1w1AoaeacBMbtfzk urVuM+hOCq8q7HaphafDAqspdxfRCsP0c9+WC9/qfA2Y5QCtVd59l/VRXTdQeHmcDfWC /TTDFe0qPPt+PUVLMohY8VmD0hXwEe7/fr0HcawJQTMaeN618le9cDd/QrwHF5UguQ44 VftBP9AdHhyr5M28Tbl8ED/kXJN7opLfrz8zLuJ1k0PKAi5Zxeg67TyE7iAT9E7ETRwP qZRQTxumAX4pxS6YNRv4WgZzuUZUl5qH5+t5dxIDy7aj0Jp7j8pHl3r/v9RoECiCFO5T 37fA==
X-Gm-Message-State: AEkoouv3RF56Bz7+QneKioyuTx1BTrWkrNahKq2Yymi5FofWePU5KDqjVWm8fcWgORq6Mw==
X-Received: by 10.66.217.170 with SMTP id oz10mr47412543pac.61.1471914320310;  Mon, 22 Aug 2016 18:05:20 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id x126sm505965pfx.61.2016.08.22.18.05.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 Aug 2016 18:05:19 -0700 (PDT)
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
To: otroan@employees.org, Mikael Abrahamsson <swmike@swm.pp.se>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se> <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com> <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se> <80C83445-2B99-4A7C-B039-E073DED71EC1@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5e23f16d-691b-5bd6-6251-f66a1df85f65@gmail.com>
Date: Tue, 23 Aug 2016 13:05:19 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <80C83445-2B99-4A7C-B039-E073DED71EC1@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/b_MFrZY1FKqlIOu3yXiKEqzRIHk>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 01:05:22 -0000

On 22/08/2016 22:24, otroan@employees.org wrote:
>>> Yep. I changed the caption in the figure. I didn't change the text
>>> about "MIF" because I couldn't really see putting "multiple, i.e. more
>>> than two" and I think the figure makes it fairly clear.
>>>
>>> (If English had a word for "more than two" that would be great. Actually,
>>> some dictionaries claim that "several" means "more than two" but I think
>>> that is a very academic definition and not helpful for the international
>>> readership of RFCs.)
>>
>> Ok, that was my lesser concern. The "sharing a prefix" is much bigger.
>>
>>              +-----------------+
>>              |                 |
>>              |     MIF Router  +---/--- other interfaces
>>              |                 |
>>              +---+---------+---+
>>                  |         | Two interfaces sharing a prefix
>>                --+-+--   --+-+--
>>                    |         |
>>                 +--+---------+--+
>>                 |   MIF Host    |
>>                 +---------------+
>>
>>                Figure 1: Hypothetical MIF interconnection
>>
>>
>> "Two interfaces sharing a prefix"
>>
>> I spent 5-10 minutes pondering 1.1 and I still can't figure it out. I see a router, it has two interfaces. I have to take for granted that this router has routed ports, and typically routers don't allow for overlapping address space, so these two ports would have different /64s? Or are they? So what's the prefix shared? Upstream /56? Now I'm just guessing.
>>
>> So I just can't figure it out. Or is this a router with a built in switch and it's the same /64 on both ports? I just think there is clarification needed in 1.1, and if there is a re-spin, I think the document would be better if that could happen.
> 
> Re-reading this I also share your confusion.
> 
> While the section explors the weak/strong host models and tries to exemplify the problem, I think the example might be a little confusing as Mikael points out.
> 
> "Two interfaces sharing a prefix"; (assuming we're talking onlink prefixes here) can only happen for fe80::/10 right?

Yes, and I don't think that's what Fred intended when he wrote
this. I *think* he meant that the two interfaces both have prefixes
(of length L) taken out of the same shorter prefix (e.g. of length L-16).
Or to give a very specific example, the two subnets have prefixes
2001:db8:aaaa:1::/64 and 2001:db8:aaaa:2::/64 and the site
has a WAN prefix 2001:db8:aaaa::/48 .

Does that seem right? If so, I certainly need to fix the text some more.

    Brian

> 
> "For example, a host with a link-local-only interface and a default route pointing to that interface"
> 
> What if this text is removed:
> 
>    Hence, if the router is a multi-interface (MIF) router and is using the same prefix on two or more
>    LANs shared by the host (as in Figure 1), the host might use each of
>    those LANs and meet the requirement.
> 
> And s/Two interfaces sharing a prefix/Link-local only prefix/ in the caption.
> 
> Cheers,
> Ole
> 
> 


From nobody Mon Aug 22 23:40:31 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BC012D758; Mon, 22 Aug 2016 23:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 jvm28mFqn_zS; Mon, 22 Aug 2016 23:40:27 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D5BC12B04D; Mon, 22 Aug 2016 23:40:27 -0700 (PDT)
Received: from [192.168.3.108] (214-173-16-190.fibertel.com.ar [190.16.173.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EB68280322; Tue, 23 Aug 2016 08:40:22 +0200 (CEST)
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
To: otroan@employees.org, Mark Smith <markzzzsmith@gmail.com>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <2e84cd40-dcfd-d55d-1241-681d216e88b4@si6networks.com>
Date: Tue, 23 Aug 2016 08:10:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/DeHulVaGVf6rKoP2jQxl6glmdxc>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 06:40:29 -0000

On 08/22/2016 10:35 AM, otroan@employees.org wrote:
[....]
>> 
>> Sort of seems to be a lot of effort to mitigate what is
>> fundamentally a problem of not following very clear processing
>> requirements in RFC4861 by the target node:
>> 
>> "A node MUST silently discard any received Neighbor Solicitation 
>> messages that do not satisfy all of the following validity checks:
>> 
>> - The IP Hop Limit field has a value of 255, i.e., the packet could
>> not possibly have been forwarded by a router."
>> 
>> Writing more specifications to mitigate against people not
>> completely following existing specifications only creates more new
>> specifications they may not follow completely either.
>> 
>> Does anyone have any insights into how multiple implementations
>> might have missed or perhaps intentionally decided not to perform
>> this validity check? It seems a bit unusual that two different
>> commonly used implementations didn't do it (I just checked the
>> Linux and FreeBSD source and they do perform the check.)
>> 
>> In cases such as this, perhaps implementation checklists (perhaps
>> as an RFC appendix) could assist either the implementer or a code 
>> reviewer in ensuring they've implemented things completely.
> 
> The issue isn't about the hop limit validation check not being done
> (it is),

I would expect this to be the case. However, folks seem to have
mentioned that this wasn't really the case?



> it is about _where_ it is done. A packet is determined to be for the
> router itself, the hardware forwarding plane then needs to decide if
> it should process the packet itself, punt the packet to software or
> drop it. There might be orders of magnitude difference in pps
> capability between software and hardware.
> 
> Is there anything we can learn from this? We have to consider in
> protocol design how expensive it is to determine if a forus() packet
> should be dropped or not. Looking deep into a packet to determine it
> is an ND packet and then do the validity checks in hardware might not
> be optimal. Perhaps ND packets should have been limited to using
> link-local addresses only.

If "deep" == "parsing the ICMPv6 header to figure out type/code and tell
the packet type", then... isn't this essentially the same thing with
EHs? That's kind of what all the debate about EHs is about...

(FWIW, I do agree with all your statements above)

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Tue Aug 23 01:37:26 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D14112D89F; Tue, 23 Aug 2016 01:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 k6JTsJnNgU53; Tue, 23 Aug 2016 01:37:19 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6608612D89C; Tue, 23 Aug 2016 01:37:19 -0700 (PDT)
Received: from [2a02:c0:2:4:1194:17:0:1006] (port=52266 helo=envy) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1bc7Ct-0003xF-Mh; Tue, 23 Aug 2016 10:37:15 +0200
Date: Tue, 23 Aug 2016 10:37:15 +0200
From: Tore Anderson <tore@fud.no>
To: otroan@employees.org
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Message-ID: <20160823103715.0b0a4a07@envy>
In-Reply-To: <5D8D4A35-1D8A-4D6D-A5CA-D0D2BF78CA8E@employees.org>
References: <E87B771635882B4BA20096B589152EF643E09933@eusaamb107.ericsson.se> <E87B771635882B4BA20096B589152EF643E3DFC0@eusaamb107.ericsson.se> <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy> <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org> <20160822171046.3c62ffe7@envy> <5D8D4A35-1D8A-4D6D-A5CA-D0D2BF78CA8E@employees.org>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/bDU3hLoy1gYF_cSvzg0QbxDFT-c>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 08:37:21 -0000

* otroan@employees.org

> Tore,
>=20
> >>> * otroan@employees.org
> >>>  =20
> >>>> The issue isn't about the hop limit validation check not being done
> >>>> (it is) =20
> >>>=20
> >>> Are you certain that it is? Both Cisco CSCuz66542 and Juniper
> >>> JSA10749 describe how the crafted ND packets will be *processed* by
> >>> the control plane - not dropped.
> >>>=20
> >>> Furthermore, both advisories go on to describe how successful
> >>> exploitation might cause the device to stop handling *IPv6* traffic
> >>> specifically - as opposed to impacting *all* traffic.
> >>>=20
> >>> While the advisories don't go into detail, this suggests to me that
> >>> successful exploitation of the issue is dependent on the crafted
> >>> packets actually being able to manipulate/overwhelm the IPv6
> >>> neighbour caches. That couldn't happen if the hop limit validation
> >>> was done and the packet was dropped - even though this was done in
> >>> software, by the control plane itself. =20
> >>=20
> >> you could explain that behaviour differently.
> >> the consequence of a massive stream of ND packets are that they will
> >> be heavily throttled between hardware and software forwarding planes.
> >> that will also impact legitimate ND packets, meaning that whatever
> >> entries there are in the ND cache or the replies from address
> >> resolution will not make it back to the ND process. =20
> >=20
> > Sure, but that'd just be a variation on the simple volumetric DoS,
> > nothing that would be unique to ND. =20
>=20
> I believe that's largely correct.

Ack. It seems the HL check is indeed being performed by JUNOS at least
(12.3 and 13.3, MX and EX platforms). I tested this by artificially
lowering the HL of the ICMPv6 packets generated by a directly attached
Linux host, like so:

$=C2=A0ip6tables -t mangle -I OUTPUT -p icmpv6 -m hl --hl-eq 255 -j HL --hl=
-set 254

As one would expect with a compliant ND implementation, the host lost
IPv6 connectivity as neighbour resolution no longer worked.

So if all there is to this vulnerability is a simple volumetric DoS
attack on the control plane I really wonder what all the fuss is about.
Most operators are fully aware that *any* traffic from untrusted
sources that is being allowed to reach the control plane is a potential
DoS vector. Shockingly enough, IPv6 ND is no exception - news at 11.

Tore


From nobody Tue Aug 23 01:45:47 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E910612D89A for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 01:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.566
X-Spam-Level: 
X-Spam-Status: No, score=-0.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 kGriNT_EDC-I for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 01:45:44 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7ECC212D88F for <ipv6@ietf.org>; Tue, 23 Aug 2016 01:45:43 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Aug 2016 08:45:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 618AD9CC4E; Tue, 23 Aug 2016 01:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=sEpdxQN5h7DPn51bHRtHAV4/Zpo=; b= FjIqJU2xLFEIIo5vCFv+LUdcqBW9d/oNXsaC0W5zPwWiVYtxY/xbNOFT1i3vJRnV WKRTLvQJI9YBdKwjar99xy7k2m7yvccFI+MfBApadw8Tmox9RI+v/8A9Dm6YslN5 t8f1jHKWW51aIAelOT4VVBya2jRd970fWN0JXMAJ8Mw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=XL43kcB5+jI9yqFTzi6FanS4SY 1GCdx2gjecG65r41cZFLIzAKcVWz5PuPKo4T4cjdGDr/9k7+efI4ZX+sJXn2M9uu CIfJzEiQ1EYhUdJQ3hD/CsctNY5KHP1oVd+c13K813oQjFOWFpIUyY0ZbZ/wLLcS ZunurJXDJDIkgqgmA=
Received: from h.hanazo.no (unknown [173.38.220.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id D6A859CC51; Tue, 23 Aug 2016 01:45:40 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 14F7C3564CAC; Tue, 23 Aug 2016 10:45:38 +0200 (CEST)
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C0D7B8CB-3494-4279-BAB2-36C2156FEDE5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <5e23f16d-691b-5bd6-6251-f66a1df85f65@gmail.com>
Date: Tue, 23 Aug 2016 10:45:37 +0200
Message-Id: <03E43781-F1D0-4D9C-8676-78926C7B30AD@employees.org>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se> <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com> <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se> <80C83445-2B99-4A7C-B039-E073DED71EC1@employees.org> <5e23f16d-691b-5bd6-6251-f66a1df85f65@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JPUMC14nYec0D-UfhibKkRmX5wA>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 08:45:46 -0000

--Apple-Mail=_C0D7B8CB-3494-4279-BAB2-36C2156FEDE5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

>>>> Yep. I changed the caption in the figure. I didn't change the text
>>>> about "MIF" because I couldn't really see putting "multiple, i.e. =
more
>>>> than two" and I think the figure makes it fairly clear.
>>>>=20
>>>> (If English had a word for "more than two" that would be great. =
Actually,
>>>> some dictionaries claim that "several" means "more than two" but I =
think
>>>> that is a very academic definition and not helpful for the =
international
>>>> readership of RFCs.)
>>>=20
>>> Ok, that was my lesser concern. The "sharing a prefix" is much =
bigger.
>>>=20
>>>             +-----------------+
>>>             |                 |
>>>             |     MIF Router  +---/--- other interfaces
>>>             |                 |
>>>             +---+---------+---+
>>>                 |         | Two interfaces sharing a prefix
>>>               --+-+--   --+-+--
>>>                   |         |
>>>                +--+---------+--+
>>>                |   MIF Host    |
>>>                +---------------+
>>>=20
>>>               Figure 1: Hypothetical MIF interconnection
>>>=20
>>>=20
>>> "Two interfaces sharing a prefix"
>>>=20
>>> I spent 5-10 minutes pondering 1.1 and I still can't figure it out. =
I see a router, it has two interfaces. I have to take for granted that =
this router has routed ports, and typically routers don't allow for =
overlapping address space, so these two ports would have different /64s? =
Or are they? So what's the prefix shared? Upstream /56? Now I'm just =
guessing.
>>>=20
>>> So I just can't figure it out. Or is this a router with a built in =
switch and it's the same /64 on both ports? I just think there is =
clarification needed in 1.1, and if there is a re-spin, I think the =
document would be better if that could happen.
>>=20
>> Re-reading this I also share your confusion.
>>=20
>> While the section explors the weak/strong host models and tries to =
exemplify the problem, I think the example might be a little confusing =
as Mikael points out.
>>=20
>> "Two interfaces sharing a prefix"; (assuming we're talking onlink =
prefixes here) can only happen for fe80::/10 right?
>=20
> Yes, and I don't think that's what Fred intended when he wrote
> this. I *think* he meant that the two interfaces both have prefixes
> (of length L) taken out of the same shorter prefix (e.g. of length =
L-16).
> Or to give a very specific example, the two subnets have prefixes
> 2001:db8:aaaa:1::/64 and 2001:db8:aaaa:2::/64 and the site
> has a WAN prefix 2001:db8:aaaa::/48 .
>=20
> Does that seem right? If so, I certainly need to fix the text some =
more.

'Two interfaces with subnets from the same prefix' ?

cheers,
Ole



--Apple-Mail=_C0D7B8CB-3494-4279-BAB2-36C2156FEDE5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXvA0xAAoJED4aXnjSQuKW9AcH+wZkSiLlYMpaVr9PrLaUoQ5u
In5i8bW/9GJ3FU91RBFyerYbbJETpTIl/ue+0D3laH9qZ9DU1h+oDsX4sLjxcMdI
vH44Ox/EESbbc8kGbNt0eUchBk8erAUsNU4C7rgCD6cg1q9F2sPU174aFB38N7cd
MktBwvjdsMOwbcb9wKoLv4r9/SqRn7RKbadzBijSkKTT2VU8v28248e4LntgVg31
8HBrZTUWzZmTdEdlWfiTNqPql24nQ/S3xquCs/gGoI/AsCtPZuStQomQex6kDQzb
2vQNQ77h+/mFChLe6ralzga462JnyvfpzpCCcIUjmmoGehnePxkP+kNDBQPV7Ek=
=q9XA
-----END PGP SIGNATURE-----

--Apple-Mail=_C0D7B8CB-3494-4279-BAB2-36C2156FEDE5--


From nobody Tue Aug 23 04:27:32 2016
Return-Path: <hemantietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF05212D13A for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 04:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 mi9arFPMBunb for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 04:27:29 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 10467126579 for <ipv6@ietf.org>; Tue, 23 Aug 2016 04:27:29 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id l203so191612402oib.1 for <ipv6@ietf.org>; Tue, 23 Aug 2016 04:27:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uXEvrYTd4sgfHLlLGe494gMbvsUfbm9nD44Q3oDi+4M=; b=Fq19MlA2tqjOvk86xVkV8Bkptho7eWoBzQdsLIFD2bMUHwK+XnurvYIgO9Mndu0bKf m6YfqpNFno49Nf+YEBNPl/wA93gq/bxQCILNV76tAc0d3L0FnH+r328kJpteSDmW5XCB WTKbxSp0NiW72gaQP5j4hLl0jqw7hrpOKoIpT4EjViUPBofMJuOVbR57tsaZL1BB0dce cUFIiqDmFAVTRfYzsrsMM6Cp4je43WAGqVZXy0JXsaq/026E0x9Hg0fiFYujRYYCBXDF ol2+bj6ulKChNbH8Aj8ZGCMqQZD6htQVFpLL7CQHeTpCwORQIp4umCRvc59IAh07OQyH TQ8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uXEvrYTd4sgfHLlLGe494gMbvsUfbm9nD44Q3oDi+4M=; b=bYJBA9avfAZ7TGRbTWzB7/Zqaef7msm+PoAgZcPS+l7Wj808bOhwR0fHBIHAlynQR6 yKhXjNW5g20swquOh1ohLLOKqs0CL92Kr3OyfjbI4DA3LkTi+ZvOmm/TttUAXNGL+5gN ho1VPffrbkft5SBLSCqOs7UxhYYacr/Pjn4VuysevlNo9fR9S6CIfcVfX6FS2CCJ2RoD 3dehNP+ZWikR62UKOuKSy7i9yBBY/mCh8QcojA9UIbvvzIfgICFDJsLMCjeXB1ZDrEa3 fpWfHET1FWfl/ngy3nyWAiVBBK9jP4WM295Y5ZR8TJqY3bwu+jC2wipYOnDGWaNAPM9l uOcw==
X-Gm-Message-State: AEkoousAS6lan/+m/xzu6vM3Av4HBa5EVes7XgcEy4i6sgZ5S4LdwupTImPDXCsCWFyVEqnGrr5bqSgYgBfHFQ==
X-Received: by 10.202.91.66 with SMTP id p63mr15029819oib.55.1471951648429; Tue, 23 Aug 2016 04:27:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.188.4 with HTTP; Tue, 23 Aug 2016 04:27:27 -0700 (PDT)
In-Reply-To: <03E43781-F1D0-4D9C-8676-78926C7B30AD@employees.org>
References: <alpine.DEB.2.02.1608191256490.3593@uplift.swm.pp.se> <E87B771635882B4BA20096B589152EF643E3DE71@eusaamb107.ericsson.se> <a75b9aca-03b6-51e5-7846-c60b41b0cd9d@gmail.com> <alpine.DEB.2.02.1608200548550.3593@uplift.swm.pp.se> <9122a17b-0e7a-1ee1-9688-4faf5d2d8120@gmail.com> <alpine.DEB.2.02.1608200630480.3593@uplift.swm.pp.se> <80C83445-2B99-4A7C-B039-E073DED71EC1@employees.org> <5e23f16d-691b-5bd6-6251-f66a1df85f65@gmail.com> <03E43781-F1D0-4D9C-8676-78926C7B30AD@employees.org>
From: Hemant Singh <hemantietf@gmail.com>
Date: Tue, 23 Aug 2016 07:27:27 -0400
Message-ID: <CABdyVt7xqyf+z38RVibfPr6pHN8gu6u_ZuCPDuaNh7Xavs6HxA@mail.gmail.com>
Subject: Re: review of draft-ietf-6man-multi-homed-host-07
To: otroan@employees.org
Content-Type: multipart/alternative; boundary=001a113d54c0219e00053abb73ca
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FvbXTKfUA0nGpzLv-Zt0Yj-tJh4>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 11:27:31 -0000

--001a113d54c0219e00053abb73ca
Content-Type: text/plain; charset=UTF-8

Right, which router will let one configure two interfaces with the same
subnet for IP address configuration.  This is why others have already
suggested that the two interfaces are using a link-local address.

Hemant

On Tue, Aug 23, 2016 at 4:45 AM, <otroan@employees.org> wrote:

> Brian,
>
> >>>> Yep. I changed the caption in the figure. I didn't change the text
> >>>> about "MIF" because I couldn't really see putting "multiple, i.e. more
> >>>> than two" and I think the figure makes it fairly clear.
> >>>>
> >>>> (If English had a word for "more than two" that would be great.
> Actually,
> >>>> some dictionaries claim that "several" means "more than two" but I
> think
> >>>> that is a very academic definition and not helpful for the
> international
> >>>> readership of RFCs.)
> >>>
> >>> Ok, that was my lesser concern. The "sharing a prefix" is much bigger.
> >>>
> >>>             +-----------------+
> >>>             |                 |
> >>>             |     MIF Router  +---/--- other interfaces
> >>>             |                 |
> >>>             +---+---------+---+
> >>>                 |         | Two interfaces sharing a prefix
> >>>               --+-+--   --+-+--
> >>>                   |         |
> >>>                +--+---------+--+
> >>>                |   MIF Host    |
> >>>                +---------------+
> >>>
> >>>               Figure 1: Hypothetical MIF interconnection
> >>>
> >>>
> >>> "Two interfaces sharing a prefix"
> >>>
> >>> I spent 5-10 minutes pondering 1.1 and I still can't figure it out. I
> see a router, it has two interfaces. I have to take for granted that this
> router has routed ports, and typically routers don't allow for overlapping
> address space, so these two ports would have different /64s? Or are they?
> So what's the prefix shared? Upstream /56? Now I'm just guessing.
> >>>
> >>> So I just can't figure it out. Or is this a router with a built in
> switch and it's the same /64 on both ports? I just think there is
> clarification needed in 1.1, and if there is a re-spin, I think the
> document would be better if that could happen.
> >>
> >> Re-reading this I also share your confusion.
> >>
> >> While the section explors the weak/strong host models and tries to
> exemplify the problem, I think the example might be a little confusing as
> Mikael points out.
> >>
> >> "Two interfaces sharing a prefix"; (assuming we're talking onlink
> prefixes here) can only happen for fe80::/10 right?
> >
> > Yes, and I don't think that's what Fred intended when he wrote
> > this. I *think* he meant that the two interfaces both have prefixes
> > (of length L) taken out of the same shorter prefix (e.g. of length L-16).
> > Or to give a very specific example, the two subnets have prefixes
> > 2001:db8:aaaa:1::/64 and 2001:db8:aaaa:2::/64 and the site
> > has a WAN prefix 2001:db8:aaaa::/48 .
> >
> > Does that seem right? If so, I certainly need to fix the text some more.
>
> 'Two interfaces with subnets from the same prefix' ?
>
> cheers,
> Ole
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

--001a113d54c0219e00053abb73ca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Right, which router will let one configure two interfaces =
with the same subnet for IP address configuration.=C2=A0 This is why others=
 have already suggested that the two interfaces are using a link-local addr=
ess.<div><br></div><div>Hemant</div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Tue, Aug 23, 2016 at 4:45 AM,  <span dir=3D"ltr=
">&lt;<a href=3D"mailto:otroan@employees.org" target=3D"_blank">otroan@empl=
oyees.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Brian,<b=
r>
<div><div class=3D"h5"><br>
&gt;&gt;&gt;&gt; Yep. I changed the caption in the figure. I didn&#39;t cha=
nge the text<br>
&gt;&gt;&gt;&gt; about &quot;MIF&quot; because I couldn&#39;t really see pu=
tting &quot;multiple, i.e. more<br>
&gt;&gt;&gt;&gt; than two&quot; and I think the figure makes it fairly clea=
r.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; (If English had a word for &quot;more than two&quot; that =
would be great. Actually,<br>
&gt;&gt;&gt;&gt; some dictionaries claim that &quot;several&quot; means &qu=
ot;more than two&quot; but I think<br>
&gt;&gt;&gt;&gt; that is a very academic definition and not helpful for the=
 international<br>
&gt;&gt;&gt;&gt; readership of RFCs.)<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Ok, that was my lesser concern. The &quot;sharing a prefix&quo=
t; is much bigger.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+--------------=
---+<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =
=C2=A0MIF Router=C2=A0 +---/--- other interfaces<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+---+---------+=
---+<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Two interfaces sharing a prefix<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0--+-+--=
=C2=A0 =C2=A0--+-+--<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +--+---=
------+--+<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0=
 =C2=A0MIF Host=C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +------=
---------+<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Figure 1=
: Hypothetical MIF interconnection<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &quot;Two interfaces sharing a prefix&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I spent 5-10 minutes pondering 1.1 and I still can&#39;t figur=
e it out. I see a router, it has two interfaces. I have to take for granted=
 that this router has routed ports, and typically routers don&#39;t allow f=
or overlapping address space, so these two ports would have different /64s?=
 Or are they? So what&#39;s the prefix shared? Upstream /56? Now I&#39;m ju=
st guessing.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; So I just can&#39;t figure it out. Or is this a router with a =
built in switch and it&#39;s the same /64 on both ports? I just think there=
 is clarification needed in 1.1, and if there is a re-spin, I think the doc=
ument would be better if that could happen.<br>
&gt;&gt;<br>
&gt;&gt; Re-reading this I also share your confusion.<br>
&gt;&gt;<br>
&gt;&gt; While the section explors the weak/strong host models and tries to=
 exemplify the problem, I think the example might be a little confusing as =
Mikael points out.<br>
&gt;&gt;<br>
&gt;&gt; &quot;Two interfaces sharing a prefix&quot;; (assuming we&#39;re t=
alking onlink prefixes here) can only happen for fe80::/10 right?<br>
&gt;<br>
&gt; Yes, and I don&#39;t think that&#39;s what Fred intended when he wrote=
<br>
&gt; this. I *think* he meant that the two interfaces both have prefixes<br=
>
&gt; (of length L) taken out of the same shorter prefix (e.g. of length L-1=
6).<br>
&gt; Or to give a very specific example, the two subnets have prefixes<br>
&gt; 2001:db8:aaaa:1::/64 and 2001:db8:aaaa:2::/64 and the site<br>
&gt; has a WAN prefix 2001:db8:aaaa::/48 .<br>
&gt;<br>
&gt; Does that seem right? If so, I certainly need to fix the text some mor=
e.<br>
<br>
</div></div>&#39;Two interfaces with subnets from the same prefix&#39; ?<br=
>
<br>
cheers,<br>
Ole<br>
<br>
<br>
<br>------------------------------<wbr>------------------------------<wbr>-=
-------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
<br></blockquote></div><br></div>

--001a113d54c0219e00053abb73ca--


From nobody Tue Aug 23 14:08:24 2016
Return-Path: <gert@space.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC6B12D9FE for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 14:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=unavailable 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 WzS2NgCE7LmI for <ipv6@ietfa.amsl.com>; Tue, 23 Aug 2016 14:08:19 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3424612DAB1 for <ipv6@ietf.org>; Tue, 23 Aug 2016 14:08:17 -0700 (PDT)
X-Original-To: ipv6@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B159E60715 for <ipv6@ietf.org>; Tue, 23 Aug 2016 23:08:14 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 4EA6260142; Tue, 23 Aug 2016 23:08:14 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id 3C5023614C; Tue, 23 Aug 2016 23:08:14 +0200 (CEST)
Date: Tue, 23 Aug 2016 23:08:14 +0200
From: Gert Doering <gert@space.net>
To: Tore Anderson <tore@fud.no>
Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Message-ID: <20160823210814.GO79185@Space.Net>
References: <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy> <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org> <20160822171046.3c62ffe7@envy> <5D8D4A35-1D8A-4D6D-A5CA-D0D2BF78CA8E@employees.org> <20160823103715.0b0a4a07@envy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160823103715.0b0a4a07@envy>
X-NCC-RegID: de.space
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/v26M8ScqXe-Un2VVfXEW74LOQ60>
Cc: 6man WG <ipv6@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2016 21:08:20 -0000

Hi,

On Tue, Aug 23, 2016 at 10:37:15AM +0200, Tore Anderson wrote:
> So if all there is to this vulnerability is a simple volumetric DoS
> attack on the control plane I really wonder what all the fuss is about.
> Most operators are fully aware that *any* traffic from untrusted
                 ^^^^^^^^^^^^^^^
Your optimism on the state of the Internet is amazing :-) - you should
be reading IXP mailing lists for a reality check on the amazingly low
level of understanding out there.

> sources that is being allowed to reach the control plane is a potential
> DoS vector. Shockingly enough, IPv6 ND is no exception - news at 11.

Seriously - I blatantly assumed that IOS XR LPTS would "do the right thing
here", namely, protect me from Joe Random's ND packets sent all over the
Internet to my boxes.  Now, if a peer at the local IXP turns out to be
malicous or gets hacket, yes, this is an obvious attack angle - but
"random packets from the Internet drowning out legitimate on-link
IPv6 ND packets"?

Well, for me, this came as a surprise.

(Arguably, the hardware might not be able to look at TTL - but if it's
smart enough to have a queue for IPv6 ND packets in the first place, why
is it not smart enough to program proper source address filters there?)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Tue Aug 23 19:13:52 2016
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCAEC12D09E; Tue, 23 Aug 2016 19:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham 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 rSEv5aB49SZV; Tue, 23 Aug 2016 19:13:45 -0700 (PDT)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id 06E8612B02A; Tue, 23 Aug 2016 19:13:42 -0700 (PDT)
Authentication-Results: smtp2.au.logicalis.com; spf=None smtp.mailfrom=gdaley@au.logicalis.com; spf=None smtp.helo=postmaster@sdcexchht.au.logicalis.com
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=10.18.196.63; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=10.18.196.63; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([10.18.196.63]) by smtp2.au.logicalis.com with ESMTP; 24 Aug 2016 12:13:18 +1000
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([100.64.20.45]) with mapi id 14.03.0279.002; Wed, 24 Aug 2016 12:13:18 +1000
From: Greg Daley <gdaley@au.logicalis.com>
To: 'Gert Doering' <gert@space.net>, Tore Anderson <tore@fud.no>
Subject: RE: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Thread-Topic: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor Discovery Crafted Packet Denial of Service Vulnerability)
Thread-Index: AQHR+h5NxdCcf1UpP0Oj3kWb+inp7aBS1IyAgAE1gon//2T1AIAAlXmAgABCSQCAABGXgIAAGnsAgAApnQCAAPrFgIAA0dMAgAD1Q+A=
Date: Wed, 24 Aug 2016 02:13:17 +0000
Message-ID: <72381AF1F18BAE4F890A0813768D99282DC9E068@sdcexchms.au.logicalis.com>
References: <CABdyVt77eSwccPNqrFfJSp0iHFABJqxq=GH+kKEAXnv1Jj8=jw@mail.gmail.com> <m1bbY2J-0000I5C@stereo.hq.phicoh.net> <CABdyVt4RBOb-PQ+YtgpcuPBDfU-MvYqAyjQYo9KK2H-idHed3g@mail.gmail.com> <CAO42Z2zs341+97JNmB6gJ-b916CfkF=+E2x=XAM2X0o-dYf2aQ@mail.gmail.com> <8751AC02-956E-4CF3-AA69-139F205209C1@employees.org> <20160822143302.2da13b80@envy> <B0447661-CC53-4667-A9BA-966DF1CD2014@employees.org> <20160822171046.3c62ffe7@envy> <5D8D4A35-1D8A-4D6D-A5CA-D0D2BF78CA8E@employees.org> <20160823103715.0b0a4a07@envy> <20160823210814.GO79185@Space.Net>
In-Reply-To: <20160823210814.GO79185@Space.Net>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.196.183]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zorIX3PFQfQsjVdP5z1xxC95JU8>
Cc: "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 02:13:48 -0000

Hi Gert et al,

While there's not an explicit vulnerability in the protocol which wasn't co=
nsidered previously, some of the points raised indicate it is not obvious t=
o operators how to provide protection from ND messages (amongst other ICMP)=
 ingressing or egressing your network.

Is it worth providing some guidance steps?

There's been some specific work done with ND-Shield (draft-gont-opsec-ipv6-=
nd-shield-00) and ND Problems (RFC6583), as well as filtering rules for ICM=
Pv6 (RFC4890)

There is an explicit assumption in RFC 4890 S4.3.3 that the end device will=
 make the right decision and drop packets based on protocol behaviour (i.e.=
 pass ND traffic only with correct hop limits).  I would recommend a change=
 to this behaviour to explicitly control traffic passing a network border.

This would allow systems with bugs and are hard to patch (e.g. IoT) to oper=
ate within a safer environment, even if they don't implement full ND checks=
.

If so, my guess is that sounds more like an operational WG approach rather =
than 6man.

Sincerely,=20

Greg Daley
Solutions Architect
Logicalis Australia Pty Ltd
e gdaley@au.logicalis.com
t +61 3 8532 4042
m +61 401 772 770

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Gert Doering
> Sent: Wednesday, 24 August 2016 7:08 AM
> To: Tore Anderson
> Cc: 6man WG; v6ops-chairs@ietf.org; v6ops list; 6man-chairs@ietf.org
> Subject: Re: [v6ops] Conclusion (was Re: CVE-2016-1409: IPv6 Neighbor
> Discovery Crafted Packet Denial of Service Vulnerability)
>=20
> Hi,
>=20
> On Tue, Aug 23, 2016 at 10:37:15AM +0200, Tore Anderson wrote:
> > So if all there is to this vulnerability is a simple volumetric DoS
> > attack on the control plane I really wonder what all the fuss is about.
> > Most operators are fully aware that *any* traffic from untrusted
>                  ^^^^^^^^^^^^^^^
> Your optimism on the state of the Internet is amazing :-) - you should be
> reading IXP mailing lists for a reality check on the amazingly low level =
of
> understanding out there.
>=20
> > sources that is being allowed to reach the control plane is a
> > potential DoS vector. Shockingly enough, IPv6 ND is no exception - news=
 at
> 11.
>=20
> Seriously - I blatantly assumed that IOS XR LPTS would "do the right thin=
g
> here", namely, protect me from Joe Random's ND packets sent all over the
> Internet to my boxes.  Now, if a peer at the local IXP turns out to be
> malicous or gets hacket, yes, this is an obvious attack angle - but "rand=
om
> packets from the Internet drowning out legitimate on-link
> IPv6 ND packets"?
>=20
> Well, for me, this came as a surprise.
>=20
> (Arguably, the hardware might not be able to look at TTL - but if it's sm=
art
> enough to have a queue for IPv6 ND packets in the first place, why is it =
not
> smart enough to program proper source address filters there?)
>=20
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
>=20
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culema=
nn
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Aug 24 02:29:10 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADDC12B00C; Wed, 24 Aug 2016 02:29:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 oqeuCUs_df_p; Wed, 24 Aug 2016 02:29:07 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 444AA12B006; Wed, 24 Aug 2016 02:29:07 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id f6so23636718ith.0; Wed, 24 Aug 2016 02:29:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=LLU3AsMcpyw2DRUfsP0uDNLOwjXbgq3iY0G0Q1Zr6D4=; b=NxW36kEsmcIc1uKj+kKoHsMjeC3iJdbW4FuPrg/AU/MT5oSik/vjxVeWDDOtAZddvg 5GhfqNGuFXlPJnSs02fTpINt22jiq+B3tHKqwrddAabeBt29GmKIxFu70rGU40vBWQgF DBckeQSrCx2m/v8eT8Vnk9+2whmHO9Ihn4m0VCjZo0UAIEB51NB8e1TevhbIOiIxup1O Li0FWspAUIH1y5KDMDz0Hna9pip0VRplhL5QyP0a9Ov6WW5wremYu7FSqeGUTir54uu9 MhNi6oBh+TTeS02iujI2T3ZunfFCOPmNIHU4SxeEx/blLzBlogVZHKPFBNZiZgZKSD0j UuGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LLU3AsMcpyw2DRUfsP0uDNLOwjXbgq3iY0G0Q1Zr6D4=; b=K9gpErR0KIhXo63jsGQjylAp4gBULgIIAqZrEab0esuFjuunnma0hrqVWasimbDdba +vGaOHKB9Ll5/bXBM2FeKiELEhM5KWku/lp0Rn3cNUKk2IwKT3JBE+5b1Sko5UNq2U9X iGXSEbW1WGryZO8G4NyWzcIELEPFGxsPCXEQX8kdSgAc+oKYSAnn43osNcSNuc3ptxzN OEK7UfxC9i38A31FYs7q7mAdLhK0IJC/SEZ8mL3HaGGpa11X5nJvuEqzG5Ps4AshVMmQ 2H2FRqmgwZZ2lgH3IRWXsMtTiiUMoOI0+W01Bs3T95gYORYVJNFOGQxFFs7YMdwAYaZX oKcQ==
X-Gm-Message-State: AEkoout0/pCqfbi13zc1ECbn0m1fsuamCXIsptWM0+tEGwxelsjYo2x0LyQDkJ2KkwAfuFR0Vhke9I/P65iGpw==
X-Received: by 10.36.227.78 with SMTP id d75mr31618714ith.75.1472030946240; Wed, 24 Aug 2016 02:29:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Wed, 24 Aug 2016 02:28:45 -0700 (PDT)
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Wed, 24 Aug 2016 14:58:45 +0530
Message-ID: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com>
Subject: Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: ipv6@ietf.org, v6ops@ietf.org
Content-Type: multipart/alternative; boundary=94eb2c111de8a63141053acde9d7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/7tPilbm8XTe8Oh55oqs429_qNPQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 09:29:08 -0000

--94eb2c111de8a63141053acde9d7
Content-Type: text/plain; charset=UTF-8

Hello,

Can anyone tell if there is any SLAAC equivalent for *DHCPv6 Remote-Id /
DHCP Option-82* option that can be used by a gateway to know the SSID,
etc.,?

Yours,
Naveen.

--94eb2c111de8a63141053acde9d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>Can anyone tell if there=C2=A0is=
 any SLAAC equivalent for <b>DHCPv6 Remote-Id / DHCP Option-82</b> option t=
hat can be used by a gateway to know the SSID, etc.,?</div><div><br></div><=
div>Yours,</div><div><div><div class=3D"gmail_signature" data-smartmail=3D"=
gmail_signature">Naveen.</div></div>
</div></div>

--94eb2c111de8a63141053acde9d7--


From nobody Wed Aug 24 02:52:25 2016
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD2612D7D4 for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 02:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 th646NyxjU4J for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 02:52:19 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 A790E12D5A1 for <ipv6@ietf.org>; Wed, 24 Aug 2016 02:52:18 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id o80so18878008wme.1 for <ipv6@ietf.org>; Wed, 24 Aug 2016 02:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lUYCp3WNBZ3WBqdn///svIr/4PLc37WjP/ltyapMk2c=; b=Z/fUNdUOU0kzUxgmTS10OYZGym6gKPsT0sF9k5np22IKw/uUECrGkzBR03J8IH9Cl+ HxpaH6ABKfd+9jpJGDFYDYmirEzsSzPujEYB8iHeqMiqADLlFowg/QmVYAz4oe4tzfm+ Z6FsNOVARfd/5Y70xwJ3yaezEoByvTBgiRiO7hGmxHCs3nY10S6OGiYmTbwrlvndrDJY 21cOf1j0C9UgLtItEkxJ0b4emtO8dXAo4B1yxxgmAskECl6ZniRNjKRtxdLfFoaUkCxx HWkGH7OUGmjvSOAVnjWtjgqy5XvY2tnuAX0XJv8Z/YvcyXmgyihqlGCA+zI6rI3FX1bJ +IMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lUYCp3WNBZ3WBqdn///svIr/4PLc37WjP/ltyapMk2c=; b=iHeP4uXpZo1W63OeBVi+w5PMfb/dY5c+DUgUFkIJktpuwgzQ+Kjw4j6RzkN6h9oPuo v9A8opKQpTXxIIEo4Pj49v/6mK2m50WYwwB1JPIutEaIIQXGan5Ln02ReWHUJZ/Gx5iE +3ZyasshSwXuFl8pCNPnBGJEZBhNhqdGrnCrX7Ak+zLQlZDHDYKkWAFaOfvV8Lujd/Q1 WUYihAH/3Tnswj7BxaYkzcH7wYCbd9kRq75S7/KlxRDwb8TcecrS53wC8DQzuqY4W57W ISy6XeTelLK+l9n76UwwhovoZ+Wr9hDHlitdJFAaS+USUyqJ7AXvfpewK9KaOi0eJU+F ls2A==
X-Gm-Message-State: AEkoouvzRrKR7hawMVmebDtlUN6d2DcUOEIC+uBp/2NjVgqesNn/dhAfwCBg8Q9ay6P3r0YFbuEy1eUtgpvQ0dGq
X-Received: by 10.194.96.205 with SMTP id du13mr1756938wjb.89.1472032336904; Wed, 24 Aug 2016 02:52:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.157.2 with HTTP; Wed, 24 Aug 2016 02:51:56 -0700 (PDT)
In-Reply-To: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Wed, 24 Aug 2016 18:51:56 +0900
Message-ID: <CAAedzxpwP9L31RD29Sgu3CKS+iOc6wozKXDA2QEp6NmmcZ08fA@mail.gmail.com>
Subject: Re: Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Nelw8fWD9ZJ-1kHnuuF0DVblN5E>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 09:52:23 -0000

On 24 August 2016 at 18:28, Naveen Kottapalli <naveen.sarma@gmail.com> wrote:
> Hello,
>
> Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id / DHCP
> Option-82 option that can be used by a gateway to know the SSID, etc.,?

I'm guessing it's not what you want, but there is this:

    https://tools.ietf.org/html/rfc6788#section-4


From nobody Wed Aug 24 03:00:21 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFEA12D878; Wed, 24 Aug 2016 03:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 M-oT_1mt7KFG; Wed, 24 Aug 2016 03:00:16 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 6D9E612D876; Wed, 24 Aug 2016 03:00:15 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id k90so19348748uak.1; Wed, 24 Aug 2016 03:00:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IVoaniLby5ViGhCrB0Cz58HkF2mpI2mxWoyXw/LxHG8=; b=Rw+Rw/fYSkYJcCJHCdWY/ewkVvG9cLiAVPvidB4CId9sLd0pMMO61jbYn+oaBxfUVW fPcPFFgCQ3G/FBu1+75pjCvEAtZSiNJMmm5G+1JlhjJ5DnghAGUGDJNZ2wXsmjehWDIU RWMtbwgwDh8/K9B16M/BCQY5P+raqnQDJdL6LWlW5BVnqehxgLmCQOq4OA7on6bUQFZz 6rX4DZlIuaQaSsmo3Xzafklssd7uJmkaQadNYeCVMDv+cIdVgfGYdXfg8/wuqQMx9KWU q038r4KQ/pQO7Fv5LGKOZbypoG54zoDR5HdEUxKdZ0ZC+2vc780zQ3FMRndnaM1JzLqq KeMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IVoaniLby5ViGhCrB0Cz58HkF2mpI2mxWoyXw/LxHG8=; b=g1kRAGpAf/6NnyPmokobmy+oCF8trEA5DzxtLUhHIITMITq7HY4urxHvsGjf/haPRh b7HphHZby1e6FEsBfu78nbaWaK/RS6nhIVM6iUfZm39XGhAZrxlbazCJVXKHiW1Lcuue TFN1+o/eio8EXH/tfX6FlIeFZjM078SiiuPyIvRIteTF465AB8YDsHyDuVcsmZYUqa6M qJ1bDXtFkdGgF4QrSiTmsg4jh4Lk/E0aRIRcK3rxV2CFVA1sY3XiRgS1sXomkRgHtMGG 9RLOyqs/7mFQLCJM1PbQpb28xy6qXt3FIA5/tXkPLL9T4wdOZNkAkOr/pMvOtesLcghU xi8A==
X-Gm-Message-State: AEkoouuhqr24vZlzxzUtfFFKGsaBe/HuAoMuS9BNWQXZrvWDZd7FrHeQulUzdFXCM/wCEjgKRkSvCGyRqvTrLw==
X-Received: by 10.31.64.196 with SMTP id n187mr1176030vka.150.1472032814469; Wed, 24 Aug 2016 03:00:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Wed, 24 Aug 2016 02:59:44 -0700 (PDT)
In-Reply-To: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 24 Aug 2016 19:59:44 +1000
Message-ID: <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com>
Subject: Re: Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ESIGdaGDZUfu6jWKuJlNordKw_4>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 10:00:21 -0000

Hi,

On 24 August 2016 at 19:28, Naveen Kottapalli <naveen.sarma@gmail.com> wrote:
> Hello,
>
> Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id / DHCP
> Option-82 option that can be used by a gateway to know the SSID, etc.,?
>

No there isn't.

SLAAC is not relayed through a router/gateway is like DHCPv4 is, so
there is no point trying to add information on the way.

SLAAC doesn't actually assign addresses to hosts either - all it does
is provides the hosts on the link with information about what
prefixes/subnets are present on the link, and hosts then generate
their own addresses from within the prefix.

In other words, if you're thinking IPv6 SLAAC is equivalent to IPv4
DHCP, they aren't, they're very different.

The use of DHCPv4 to assign addresses could be described as a
centralised database dependent host address assignment
protocol/method, where hosts don't participate in the generation and
selection of the addresses they end up using. They either take what
they're given from the DHCPv4 server or don't have an address to use.

The use of SLAAC for address assignment in IPv6 could be described as
a distributed address assignment system that doesn't have a central
database. Hosts are entirely responsible for the generation and
validation of addresses that they use based on the prefix information
supplied in RAs.

Regards,
Mark.


> Yours,
> Naveen.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Wed Aug 24 03:29:55 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1098E12DB7E; Wed, 24 Aug 2016 03:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BaGEqcgBgZKz; Wed, 24 Aug 2016 03:29:47 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 D050C12DB83; Wed, 24 Aug 2016 03:29:46 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id n128so25737537ith.1; Wed, 24 Aug 2016 03:29:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h5RTlJvLcPcJOJhwZFaB3OiJzmzDToS3G0k45wN5MQo=; b=dxzH790tuD+0rXWhJx37Sg+RB/aHkdHiUlKcKLKJsasP5Fgw6EBrhKUXiopHfLO5ll VdeZorUhiGV8pXmdid792alI0uKdTCjYizb7MY/4/TeLSIXuqG0lfuePwidg3Mo3HU17 9ROG2gntrZDRyOTgJ4AnyWSyLJRzNyXysRA9kOVhdC86CoUaWz4Phi9F+kEFQ7pCHnXN Wx825i4d+LI1gz3Egud/m32P94g22BP/Ju9zMCFeak1qmgn0CeOC0gBnCV/jcNVZVSb1 3wbJ9MLjNru1ujAdF0QVEFpp9XAT0WBkxLWdkDcuLXHNJNnbJ2kzCz7TMMH54cyULwWL b64Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h5RTlJvLcPcJOJhwZFaB3OiJzmzDToS3G0k45wN5MQo=; b=Hy9fDMGQxo2G36BUCFBxrGKhg3q06rATBuc0HBKapLU0ZgXGslT/hRJ42noY+nz4EB AZMKPcNUtmPqVdk0+8FDgxhP9f2c8FKBB8ZBkx+ShYc7utGsrz1+TG6TpvJ93BfCp+Wl Ip3M5qMcq9Ggxxa6V212dwTJoUKYJkiTnpxjXzCYv0g+hgEit9sjo4zym1swV9ouIKLr jqwhyzLtoktc6nAPoFUX2EK2PrCuehOcBHUfXTKYNgsJGAuv7cd8xJj84LDLUTIjSE/+ N1SocFpqb33WKhZ+j+J5VL4GIs7MA8BuQUITcwM/nq4qAEFqOEMm1y+BAERcGtZPKog0 iC7g==
X-Gm-Message-State: AEkoousBkP4vH5WqVoBu6H1NTwUGGH3FHZmf22rPGhS33wwB5WmNNT1dhs6nJJBWnIJ2HgVDJJwJOOCldOy64Q==
X-Received: by 10.107.16.77 with SMTP id y74mr3122515ioi.161.1472034585189; Wed, 24 Aug 2016 03:29:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Wed, 24 Aug 2016 03:29:24 -0700 (PDT)
In-Reply-To: <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Wed, 24 Aug 2016 15:59:24 +0530
Message-ID: <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com>
Subject: Re: Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a113e811c8c2422053acec26a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kyfELTBfKUpQaj3S_SiyzX7HqCU>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 10:29:49 -0000

--001a113e811c8c2422053acec26a
Content-Type: text/plain; charset=UTF-8

Hello,

If the AP is relaying the RS on a GRE tunnel to the gateway, can whatever
Erik suggested be used to inject the information whatever am looking for?

Yours,
Naveen.

On 24 August 2016 at 15:29, Mark Smith <markzzzsmith@gmail.com> wrote:

> Hi,
>
> On 24 August 2016 at 19:28, Naveen Kottapalli <naveen.sarma@gmail.com>
> wrote:
> > Hello,
> >
> > Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id /
> DHCP
> > Option-82 option that can be used by a gateway to know the SSID, etc.,?
> >
>
> No there isn't.
>
> SLAAC is not relayed through a router/gateway is like DHCPv4 is, so
> there is no point trying to add information on the way.
>
> SLAAC doesn't actually assign addresses to hosts either - all it does
> is provides the hosts on the link with information about what
> prefixes/subnets are present on the link, and hosts then generate
> their own addresses from within the prefix.
>
> In other words, if you're thinking IPv6 SLAAC is equivalent to IPv4
> DHCP, they aren't, they're very different.
>
> The use of DHCPv4 to assign addresses could be described as a
> centralised database dependent host address assignment
> protocol/method, where hosts don't participate in the generation and
> selection of the addresses they end up using. They either take what
> they're given from the DHCPv4 server or don't have an address to use.
>
> The use of SLAAC for address assignment in IPv6 could be described as
> a distributed address assignment system that doesn't have a central
> database. Hosts are entirely responsible for the generation and
> validation of addresses that they use based on the prefix information
> supplied in RAs.
>
> Regards,
> Mark.
>
>
> > Yours,
> > Naveen.
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
>

--001a113e811c8c2422053acec26a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>If the AP is relaying the RS on =
a GRE tunnel to the gateway, can whatever Erik suggested be used to inject =
the information whatever am looking for?<div class=3D"gmail_extra"><br clea=
r=3D"all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signa=
ture">Yours,<br>Naveen.</div></div>
<br><div class=3D"gmail_quote">On 24 August 2016 at 15:29, Mark Smith <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmith@gmail.com" target=3D"_blank=
">markzzzsmith@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">Hi,<br>
<span class=3D""><br>
On 24 August 2016 at 19:28, Naveen Kottapalli &lt;<a href=3D"mailto:naveen.=
sarma@gmail.com">naveen.sarma@gmail.com</a>&gt; wrote:<br>
&gt; Hello,<br>
&gt;<br>
&gt; Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id =
/ DHCP<br>
&gt; Option-82 option that can be used by a gateway to know the SSID, etc.,=
?<br>
&gt;<br>
<br>
</span>No there isn&#39;t.<br>
<br>
SLAAC is not relayed through a router/gateway is like DHCPv4 is, so<br>
there is no point trying to add information on the way.<br>
<br>
SLAAC doesn&#39;t actually assign addresses to hosts either - all it does<b=
r>
is provides the hosts on the link with information about what<br>
prefixes/subnets are present on the link, and hosts then generate<br>
their own addresses from within the prefix.<br>
<br>
In other words, if you&#39;re thinking IPv6 SLAAC is equivalent to IPv4<br>
DHCP, they aren&#39;t, they&#39;re very different.<br>
<br>
The use of DHCPv4 to assign addresses could be described as a<br>
centralised database dependent host address assignment<br>
protocol/method, where hosts don&#39;t participate in the generation and<br=
>
selection of the addresses they end up using. They either take what<br>
they&#39;re given from the DHCPv4 server or don&#39;t have an address to us=
e.<br>
<br>
The use of SLAAC for address assignment in IPv6 could be described as<br>
a distributed address assignment system that doesn&#39;t have a central<br>
database. Hosts are entirely responsible for the generation and<br>
validation of addresses that they use based on the prefix information<br>
supplied in RAs.<br>
<br>
Regards,<br>
Mark.<br>
<br>
<br>
&gt; Yours,<br>
&gt; Naveen.<br>
&gt;<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt;<br>
</blockquote></div><br></div></div></div>

--001a113e811c8c2422053acec26a--


From nobody Wed Aug 24 03:59:17 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 993F512DC26; Wed, 24 Aug 2016 03:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 It4PoDMkEk5m; Wed, 24 Aug 2016 03:59:10 -0700 (PDT)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (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 1BBC312DBE4; Wed, 24 Aug 2016 03:59:10 -0700 (PDT)
Received: by mail-ua0-x232.google.com with SMTP id k90so21402572uak.1; Wed, 24 Aug 2016 03:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IBw/cYkDOTs4+ZwtrYul8QWb4NAiMYw1q4oEWtmoOWg=; b=uGtEey4gKxDFxys1ZO/U9sbQBrMhPeyd25C0X7em9snNVBYjhpCiYq6F9s5cIMRdZn Lz700n6w3YnUUDdCe04WnIslBHBIksn8dzzmt8R2wgY/1jSWsYz+OoC+cHf2fCsljKkx z9kpAM/nDKEemKcmEN28grEpQ9XAmtWJB+I5qekKRj+EYG5gg6OtJEV2PAfhbyeajfex OhCsDckOdW5G2aOyP5YMwwodfgHWbPQ98sVshkqAaeSnlrr4TLFlAO1UMxMoFEOCYXCQ PMIodGx4g1RHakY+M+WH2q2te2WtIkdAs2IqLaOkuvTIfEFNWvAQhbH8V0VwVkTqgiL5 I4sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IBw/cYkDOTs4+ZwtrYul8QWb4NAiMYw1q4oEWtmoOWg=; b=U3S1WTfdBpYRQCPX4ObQD4ORFm21sbW2PMsxdU5+i1Xxun8SniO1fc5m9zcUJh9OHh NoE+Xj48VDIvEEl208cy9qUpvURfU6XIexyKD82PXtHGlEsjwP9PYr9Xxx4jdnC0z9C9 ZrjL3g1Un0xVI2dhUa/cYhK8fP1ctuomAMtS3FzXYDDwwIWB9AHkSkbEmYY/eKVM+6qR uRqfLA6wZsT/IDfxxeynLSk7p2CzvLdv0qlaNyUE83VNQjMVxSYz2B7Mlqon2VNpnNsr HSpjtvZ8rxZ6nf90EsurIDlD2GqplVhVeSCoeJrn3bpOKezivQiE4bLInt14cA6G8Eos voaA==
X-Gm-Message-State: AE9vXwPBf7c2R66j+TyBpmyYnauNCpOhGgzVQDYnSrvTsLytMMnzELCG+RcVOmsewX86I/k3wxPhC+42uLUz2w==
X-Received: by 10.159.41.230 with SMTP id s93mr1105987uas.67.1472036349159; Wed, 24 Aug 2016 03:59:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.1.165 with HTTP; Wed, 24 Aug 2016 03:58:38 -0700 (PDT)
In-Reply-To: <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com> <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 24 Aug 2016 20:58:38 +1000
Message-ID: <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com>
Subject: Re: Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_rvBK_vcTZ2sOneA8YZCs27fQis>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 10:59:11 -0000

On 24 August 2016 at 20:29, Naveen Kottapalli <naveen.sarma@gmail.com> wrote:
> Hello,
>
> If the AP is relaying the RS on a GRE tunnel to the gateway, can whatever
> Erik suggested be used to inject the information whatever am looking for?
>

Possibly (I'd forgotten about that method) if the AP supported it.


Regards,
Mark.


> Yours,
> Naveen.
>
> On 24 August 2016 at 15:29, Mark Smith <markzzzsmith@gmail.com> wrote:
>>
>> Hi,
>>
>> On 24 August 2016 at 19:28, Naveen Kottapalli <naveen.sarma@gmail.com>
>> wrote:
>> > Hello,
>> >
>> > Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id /
>> > DHCP
>> > Option-82 option that can be used by a gateway to know the SSID, etc.,?
>> >
>>
>> No there isn't.
>>
>> SLAAC is not relayed through a router/gateway is like DHCPv4 is, so
>> there is no point trying to add information on the way.
>>
>> SLAAC doesn't actually assign addresses to hosts either - all it does
>> is provides the hosts on the link with information about what
>> prefixes/subnets are present on the link, and hosts then generate
>> their own addresses from within the prefix.
>>
>> In other words, if you're thinking IPv6 SLAAC is equivalent to IPv4
>> DHCP, they aren't, they're very different.
>>
>> The use of DHCPv4 to assign addresses could be described as a
>> centralised database dependent host address assignment
>> protocol/method, where hosts don't participate in the generation and
>> selection of the addresses they end up using. They either take what
>> they're given from the DHCPv4 server or don't have an address to use.
>>
>> The use of SLAAC for address assignment in IPv6 could be described as
>> a distributed address assignment system that doesn't have a central
>> database. Hosts are entirely responsible for the generation and
>> validation of addresses that they use based on the prefix information
>> supplied in RAs.
>>
>> Regards,
>> Mark.
>>
>>
>> > Yours,
>> > Naveen.
>> >
>> > --------------------------------------------------------------------
>> > IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> > --------------------------------------------------------------------
>> >
>
>


From nobody Wed Aug 24 04:38:47 2016
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D671A12DCA2 for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 04:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 iCHIehb-IJgZ for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 04:38:44 -0700 (PDT)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 E5D2A12D931 for <ipv6@ietf.org>; Wed, 24 Aug 2016 04:38:43 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id i5so23215161wmg.0 for <ipv6@ietf.org>; Wed, 24 Aug 2016 04:38:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pBt7Mn6drpq0AuxBcO8ILnv3xT5hcbpcmho2sMhXi38=; b=ogQdSPJA/tcRu2y9ugOwicke4t7rU4Gtu/zYjjmAHQD098qmQvgQ5j4h+NlurnRyla jUXIjhTgQX21fXpKAjwhVoOa19iTYLLyhmdLvqqMuRtkV2wuDox+9CE06fZ/3ml/iGgS sd1AKR7WZ6v1lpwfoql9dsmOYMg2F78ueHDPdzLsD5IsXNawQj3VV8RKbS/MMIu27Jrq wL9GnpEwIvmsMwj29LPM1VNYmHkJEpbQG7L3X/I0uHl9iA1spGwlK+u2dSkPKORRzrie vXQFY1gszM9JPs4nhcMb0024yzy36Nvn35OiJBoaZuFtLZDT8kXxDeFpQFYOPCMgFAh3 d8vQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pBt7Mn6drpq0AuxBcO8ILnv3xT5hcbpcmho2sMhXi38=; b=Z3B+t2eg+QHCFp0dOSBomYy+BG7/R68pSb7Vhbal/TkvXblcpyoMaDUAXkDWKulRNj Viq+zpawRRc3KW/I9GOjNyUYbJf1+D9vYsgeStgZDtC834heFqJiPwlMA8osLhemOgCh 00805ZF892iLeA3aVUVUmbYQsnD0w72MVhWObBJU73BIkdADjuxkyQX/5ouJIVjhjSRY UG5MoOCXVtoAI32mjBXXS0LAwHKceEsxuXObeCQaNZs256hPS+53JBROfoTIhO5Qsi5s EG6Vl3B3PsLJme77gIsglw5sHzFz13zxyvR/eyczghNEpq3zE+UT4MEIc8bJk6EOoqqT 9Tdg==
X-Gm-Message-State: AEkooutKbobAz8VDcHi3Pqma1kjXnVYmmuJ/Ax+aqimL/toBIABRKQlfN0zeAsWGZqkEZUeba4YbisJo8LgirL61
X-Received: by 10.194.96.205 with SMTP id du13mr2177871wjb.89.1472038722226; Wed, 24 Aug 2016 04:38:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.157.2 with HTTP; Wed, 24 Aug 2016 04:38:21 -0700 (PDT)
In-Reply-To: <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com> <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com> <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Wed, 24 Aug 2016 20:38:21 +0900
Message-ID: <CAAedzxpdj4ST94D-1DjWij7L-AARhuzvkgn74b5ORgRV+ZiWgg@mail.gmail.com>
Subject: Re: [v6ops] Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/4-PZogXTk2wJTZKh5hMfQXjYWAY>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 11:38:46 -0000

On 24 August 2016 at 19:58, Mark Smith <markzzzsmith@gmail.com> wrote:
> On 24 August 2016 at 20:29, Naveen Kottapalli <naveen.sarma@gmail.com> wrote:
>> Hello,
>>
>> If the AP is relaying the RS on a GRE tunnel to the gateway, can whatever
>> Erik suggested be used to inject the information whatever am looking for?
>>
>
> Possibly (I'd forgotten about that method) if the AP supported it.

Yeah, definitely a question for your vendor.

>
>
> Regards,
> Mark.
>
>
>> Yours,
>> Naveen.
>>
>> On 24 August 2016 at 15:29, Mark Smith <markzzzsmith@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> On 24 August 2016 at 19:28, Naveen Kottapalli <naveen.sarma@gmail.com>
>>> wrote:
>>> > Hello,
>>> >
>>> > Can anyone tell if there is any SLAAC equivalent for DHCPv6 Remote-Id /
>>> > DHCP
>>> > Option-82 option that can be used by a gateway to know the SSID, etc.,?
>>> >
>>>
>>> No there isn't.
>>>
>>> SLAAC is not relayed through a router/gateway is like DHCPv4 is, so
>>> there is no point trying to add information on the way.
>>>
>>> SLAAC doesn't actually assign addresses to hosts either - all it does
>>> is provides the hosts on the link with information about what
>>> prefixes/subnets are present on the link, and hosts then generate
>>> their own addresses from within the prefix.
>>>
>>> In other words, if you're thinking IPv6 SLAAC is equivalent to IPv4
>>> DHCP, they aren't, they're very different.
>>>
>>> The use of DHCPv4 to assign addresses could be described as a
>>> centralised database dependent host address assignment
>>> protocol/method, where hosts don't participate in the generation and
>>> selection of the addresses they end up using. They either take what
>>> they're given from the DHCPv4 server or don't have an address to use.
>>>
>>> The use of SLAAC for address assignment in IPv6 could be described as
>>> a distributed address assignment system that doesn't have a central
>>> database. Hosts are entirely responsible for the generation and
>>> validation of addresses that they use based on the prefix information
>>> supplied in RAs.
>>>
>>> Regards,
>>> Mark.
>>>
>>>
>>> > Yours,
>>> > Naveen.
>>> >
>>> > --------------------------------------------------------------------
>>> > IETF IPv6 working group mailing list
>>> > ipv6@ietf.org
>>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> > --------------------------------------------------------------------
>>> >
>>
>>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Wed Aug 24 17:56:14 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD2712D189; Wed, 24 Aug 2016 17:56:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-multi-homed-host-09.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147208657311.26545.5848857837645557880.idtracker@ietfa.amsl.com>
Date: Wed, 24 Aug 2016 17:56:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0YS4ksKjF_LaB35r-FcfzWSUxiA>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 00:56:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance of the IETF.

        Title           : First-hop router selection by hosts in a multi-prefix network
        Authors         : Fred Baker
                          Brian Carpenter
	Filename        : draft-ietf-6man-multi-homed-host-09.txt
	Pages           : 14
	Date            : 2016-08-24

Abstract:
   This document describes expected IPv6 host behavior in a scenario
   that has more than one prefix, each allocated by an upstream network
   that is assumed to implement BCP 38 ingress filtering, when the host
   has multiple routers to choose from.  It also applies to other
   scenarios such as the usage of stateful firewalls that effectively
   act as address-based filters.  Host behavior in choosing a first-hop
   router may interact with source address selection in a given
   implementation.  However, the selection of the source address for a
   packet is done before the first-hop router for that packet is chosen.
   Given that the network or host is, or appears to be, multihomed with
   multiple provider-allocated addresses, that the host has elected to
   use a source address in a given prefix, and that some but not all
   neighboring routers are advertising that prefix in their Router
   Advertisement Prefix Information Options, this document specifies to
   which router a host should present its transmission.  It updates RFC
   4861.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-09


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Aug 24 18:02:11 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C454B12D5F7 for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 18:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VD7ODLkL9mUP for <ipv6@ietfa.amsl.com>; Wed, 24 Aug 2016 18:02:08 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 790E512D5F2 for <ipv6@ietf.org>; Wed, 24 Aug 2016 18:02:04 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id h186so11956350pfg.3 for <ipv6@ietf.org>; Wed, 24 Aug 2016 18:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Sf4pouEFFCr1eXvP2x0vbyy9NE/Trp9nswrneJ4Mdhw=; b=ZbrJT3B6/BKrJJeJX+JNFtC9M0N/MVa+m9lxCJgmSwNGdbs4MAFDKvmC/q7uMAsNpb FBXyxfIIq264ij7+e4Mhtg/WKNdOIamkx+5q0WoHOqgOidJn1z5Q//Qf8cJxdw5fzXmC JeWGq9D4rrlCKQSpVOoyGUYur1NQZHIFy2RK/YAUiv9VmnhDT7M/ZJAfNwf7IVYIU34F sf7QWDzjpeXqkqvqQ6pKMsMnqyiIQR1Rr3bcwyU5yMtQwJKSTUvKfI2etS6hv1p0uQfd 2U46MaQ2bQhhOCwPSmAJXDtIoD7sx18p/HoXvbpNjDArkVYa7p1lrqPKN1zNsB66XMqO DHuw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Sf4pouEFFCr1eXvP2x0vbyy9NE/Trp9nswrneJ4Mdhw=; b=fZBODdk8ONkCxbn1W771CwkUQLT5UhyI6N7qPaeMWEF+lgzsLU56kZZmDO/gRVvI9Q 9RgsFfNVSo5OSTbSj9BrBwSiPrs6+FgFft1nWtfKc8ZMtG+MOPLxp6UXSI6PBNguvtZG qXWrylhyu9yaqLHnf6/oHCgz1ny6+ISTUcNFEzPSRQwKI5jX8AraM8HGKYO9i7hIRd9W yDX2tiv9RqM8c3MEKIa7m8+oHJtkEEM0gu5TbZ8mT9Ek6k5GrmtDGQ49/J3fjcbbfCb7 pe1HvpAepaCDlO6w6biwS3fV516XUgWEakX1YweYVkQ3NDptjw9/0GZIt7UPJA50//hP 3Pqw==
X-Gm-Message-State: AE9vXwMnZmwlSWQVTxCpEEEzmAKQqV2X2MHM+dl7ct8jRkLmQzHTo+vnS1RLaRhrbrzFfw==
X-Received: by 10.98.60.217 with SMTP id b86mr11132558pfk.129.1472086923721; Wed, 24 Aug 2016 18:02:03 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.114.131]) by smtp.gmail.com with ESMTPSA id o80sm16403339pfa.67.2016.08.24.18.02.01 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Aug 2016 18:02:02 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-multi-homed-host-09.txt
References: <147208657311.26545.5848857837645557880.idtracker@ietfa.amsl.com>
To: ipv6@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5c8dce33-0047-88cb-4963-9f579e98a198@gmail.com>
Date: Thu, 25 Aug 2016 13:02:08 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <147208657311.26545.5848857837645557880.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fKn55tB5GplzLGIb55p2YNSRtzg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 01:02:09 -0000

FYI, this version clarifies some text "fixed" in the previous version ;-).
Again, no substantive change, but the Fig. 1 scenario should now make sense.

Regards
   Brian

On 25/08/2016 12:56, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance of the IETF.
> 
>         Title           : First-hop router selection by hosts in a multi-prefix network
>         Authors         : Fred Baker
>                           Brian Carpenter
> 	Filename        : draft-ietf-6man-multi-homed-host-09.txt
> 	Pages           : 14
> 	Date            : 2016-08-24
> 
> Abstract:
>    This document describes expected IPv6 host behavior in a scenario
>    that has more than one prefix, each allocated by an upstream network
>    that is assumed to implement BCP 38 ingress filtering, when the host
>    has multiple routers to choose from.  It also applies to other
>    scenarios such as the usage of stateful firewalls that effectively
>    act as address-based filters.  Host behavior in choosing a first-hop
>    router may interact with source address selection in a given
>    implementation.  However, the selection of the source address for a
>    packet is done before the first-hop router for that packet is chosen.
>    Given that the network or host is, or appears to be, multihomed with
>    multiple provider-allocated addresses, that the host has elected to
>    use a source address in a given prefix, and that some but not all
>    neighboring routers are advertising that prefix in their Router
>    Advertisement Prefix Information Options, this document specifies to
>    which router a host should present its transmission.  It updates RFC
>    4861.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-09
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-09
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Thu Aug 25 06:57:45 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1805312D82D; Thu, 25 Aug 2016 06:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 H8FZPTDsPKP7; Thu, 25 Aug 2016 06:57:39 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 74F6D12D13A; Thu, 25 Aug 2016 06:57:38 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id f6so90975737ith.0; Thu, 25 Aug 2016 06:57:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to; bh=9iUnhmz7AVLMre1ZZhc3C9w8jzBB4eOWx9HfsbSoHjw=; b=gh3nl8U4Usv3FLvMcL77TgYM2stM9sxh2agFYjZ5vKxEPDJb4C5NHbrAgTiN7pxZ0Q TiHDeijmdnXHWmYNUrIy2bNrxaPyokPXa8z4Z5Zx5KaLbYYWCGhKgiKpVtO7VrQy2yW5 psEbLipIQwBSPX585cp+c4tqE9Nn2d5sE5BPfeLYQaEScDSvU0VSYBrY9kHjFRajlh6D 8MTinGflKaDPVbRfCFYdZaZsCIrpdoGsI0dH8FyOLk+n95bMn8/ImRNMaAaKWhrcjIE2 2TtJjmrfL9gnGIp4JRiBzNxdWrxXbfVhQCSYr5HgHQXoCJtuVAGliRW+LhPDSVpRwyLR 3A5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9iUnhmz7AVLMre1ZZhc3C9w8jzBB4eOWx9HfsbSoHjw=; b=Z1Sc3wLxRYIBVMhPylgi3A/j7So+oleOZMQS0PHnbOytifhjlyCH2QocyhGRlN3t7u rlYt3+ra17kpSdKCxDjQAy6bAiazFGHGQ+sISb5POXBxe5xksXbCpNaxXW2dl3x3jf5S tn/PevcKHEhInkzL9CPImJ2gyfe2DsiOVrEMoIpxdy+dQxL7K30YVBsbtLRhxwPRwddC O6eWvHrz9EzLcwCmEOKJL6YztER8boWbcWyo+dFSlg6g/9f41nYA8nQ9exiBY/JE05cF f7/cEZErfQtemCFYJyjM9YOSgbmsj36SqrZVj916OudB5tRYfSFfsO4q7hoNHz+jCPHi LASg==
X-Gm-Message-State: AEkooutDwrXCVoWH6ym+qCIDxTybTUd4IFwVuNySC5wom3CiVT7dusrMDTse3HmE0NKR8F2kkjROQT8pJLDReQ==
X-Received: by 10.107.150.83 with SMTP id y80mr10662583iod.113.1472133457812;  Thu, 25 Aug 2016 06:57:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.130.2 with HTTP; Thu, 25 Aug 2016 06:57:17 -0700 (PDT)
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Thu, 25 Aug 2016 19:27:17 +0530
Message-ID: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com>
Subject: v6 gateway data forwarding behaviour
To: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a11405feed0a148053ae5c76a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nu5CzkqueVtYdzbJTKvhsm8NrSY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 13:57:40 -0000

--001a11405feed0a148053ae5c76a
Content-Type: text/plain; charset=UTF-8

Hello,

Assuming that the node is given a prefix in RA by the gateway, does the
gateway need to know the complete address being used by node for data
forwarding?

Yours,
Naveen.

--001a11405feed0a148053ae5c76a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div><div>Assuming that the node is g=
iven a prefix in RA by the gateway, does the gateway need to know the compl=
ete address being used by node for data forwarding?<br></div></div><div cla=
ss=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature" da=
ta-smartmail=3D"gmail_signature">Yours,<br></div></div></div><div><div clas=
s=3D"gmail_signature" data-smartmail=3D"gmail_signature">Naveen.</div></div=
>
</div>

--001a11405feed0a148053ae5c76a--


From nobody Thu Aug 25 13:32:47 2016
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C3A12D0FC for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 13:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham 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 9VJASSRKHjsD for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 13:32:45 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6959B126D74 for <ipv6@ietf.org>; Thu, 25 Aug 2016 13:32:45 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 3A0D6880E6 for <ipv6@ietf.org>; Thu, 25 Aug 2016 13:32:45 -0700 (PDT)
Received: from clemson.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id EF2C53280AE0 for <ipv6@ietf.org>; Thu, 25 Aug 2016 13:32:44 -0700 (PDT)
To: "ipv6@ietf.org" <ipv6@ietf.org>
From: Brian Haberman <brian@innovationslab.net>
Subject: 2460bis and the Traffic Class field
Message-ID: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
Date: Thu, 25 Aug 2016 16:32:36 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Hirjlc0DkUXcOXdt3TsG25csjhOUQfGdu"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ac7yd2rqu9AOEYOtwgrpsfH7jUc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 20:32:46 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Hirjlc0DkUXcOXdt3TsG25csjhOUQfGdu
Content-Type: multipart/mixed; boundary="k2FXVgkuskPadSbXX5D0oItCdaC5nXm00"
From: Brian Haberman <brian@innovationslab.net>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
Subject: 2460bis and the Traffic Class field

--k2FXVgkuskPadSbXX5D0oItCdaC5nXm00
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

All,
     I came across a discrepancy that I think is worth discussing. After
the publication of RFC 2460, RFC 2474 was published and that document
renames the IPv4 TOS and IPv6 Traffic Class fields
(https://tools.ietf.org/html/rfc2474#section-3). RFC 2474 is then
updated by RFC 3260 to provide a clarification on the name of the DS Fiel=
d.

     I know that 2474 did not formally update 2460, but it seems that
there was an attempt to rename the Traffic Class field to be consistent
with its use. Do people think that 2460bis should incorporate those
changes to be consistent with 2474/3260?

Regards,
Brian


--k2FXVgkuskPadSbXX5D0oItCdaC5nXm00--

--Hirjlc0DkUXcOXdt3TsG25csjhOUQfGdu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJXv1XpAAoJEBOZRqCi7goqChUIAJIqNncoghv3b5Sk3Tn/gbA3
xIf3kSeZ2yTvH0zp+Jt9leMcS9iJBjsZ8OKSpDrQh6A3Pcl56lCNFEichx0s99z9
vs6wQ5s76bqem/m4uwZqAexemEJS6HdId3ZJGCIdL+0fOmq6wfaJFBf0TyIqEnlS
42VDIqrc0NxhsrYXnL+UXK8qJDvowoQNOubNOSjW6ZrEA+jhoEPjdNLznYGlFJZ9
/pKvCJt3jjxGrOgpj+4FA9lenO0MasSeNFVWmHpA4jSoXFbPaXepAr7Cc3tR+PAd
qp1LrVBUeH7e4kkDL+hM5/w/tLK7m0e8oaR6KSc05TycB2VdlGSBPE8tmddqhxs=
=KJmE
-----END PGP SIGNATURE-----

--Hirjlc0DkUXcOXdt3TsG25csjhOUQfGdu--


From nobody Thu Aug 25 14:11:20 2016
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B3A12D63E for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 14:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 01eFLuaaD6am for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 14:11:16 -0700 (PDT)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DC4A12D625 for <ipv6@ietf.org>; Thu, 25 Aug 2016 14:11:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u7PLBGgv049752; Thu, 25 Aug 2016 14:11:16 -0700
Received: from XCH15-06-07.nw.nos.boeing.com (xch15-06-07.nw.nos.boeing.com [137.136.238.213]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u7PLBBxw049699 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 25 Aug 2016 14:11:11 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-07.nw.nos.boeing.com (2002:8988:eed5::8988:eed5) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 25 Aug 2016 14:11:10 -0700
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1178.000; Thu, 25 Aug 2016 14:11:10 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: 2460bis and the Traffic Class field
Thread-Topic: 2460bis and the Traffic Class field
Thread-Index: AQHR/w/jrGvQcc18YEusKCmWjdnLDqBaKnTA
Date: Thu, 25 Aug 2016 21:11:10 +0000
Message-ID: <d151229d0033476dae590db74547edb5@XCH15-06-11.nw.nos.boeing.com>
References: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
In-Reply-To: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6m4FrJjSKPe9a0CAcCQkcIKPefA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 21:11:18 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQnJpYW4gSGFiZXJtYW4NCg0KPiBBbGwsDQo+
ICAgICAgSSBjYW1lIGFjcm9zcyBhIGRpc2NyZXBhbmN5IHRoYXQgSSB0aGluayBpcyB3b3J0aCBk
aXNjdXNzaW5nLiBBZnRlcg0KPiB0aGUgcHVibGljYXRpb24gb2YgUkZDIDI0NjAsIFJGQyAyNDc0
IHdhcyBwdWJsaXNoZWQgYW5kIHRoYXQgZG9jdW1lbnQNCj4gcmVuYW1lcyB0aGUgSVB2NCBUT1Mg
YW5kIElQdjYgVHJhZmZpYyBDbGFzcyBmaWVsZHMNCj4gKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9yZmMyNDc0I3NlY3Rpb24tMykuIFJGQyAyNDc0IGlzIHRoZW4NCj4gdXBkYXRlZCBieSBS
RkMgMzI2MCB0byBwcm92aWRlIGEgY2xhcmlmaWNhdGlvbiBvbiB0aGUgbmFtZSBvZiB0aGUgRFMg
RmllbGQuDQo+IA0KPiAgICAgIEkga25vdyB0aGF0IDI0NzQgZGlkIG5vdCBmb3JtYWxseSB1cGRh
dGUgMjQ2MCwgYnV0IGl0IHNlZW1zIHRoYXQNCj4gdGhlcmUgd2FzIGFuIGF0dGVtcHQgdG8gcmVu
YW1lIHRoZSBUcmFmZmljIENsYXNzIGZpZWxkIHRvIGJlIGNvbnNpc3RlbnQNCj4gd2l0aCBpdHMg
dXNlLiBEbyBwZW9wbGUgdGhpbmsgdGhhdCAyNDYwYmlzIHNob3VsZCBpbmNvcnBvcmF0ZSB0aG9z
ZQ0KPiBjaGFuZ2VzIHRvIGJlIGNvbnNpc3RlbnQgd2l0aCAyNDc0LzMyNjA/DQoNCk9uZSBvZiB0
aG9zZSBsb25nLXN0YW5kaW5nIGFtYmlndWl0aWVzLCBJTU8uIFllcywgZGVmaW5pdGVseSwgdGhl
IHF1ZXN0aW9uIG9mIHdoZXRoZXIgRFNDUCBpcyByZWFsLCBvciB3aGV0aGVyIGl0J3MganVzdCBt
ZWFudCB0byBhcHBseSBpbiBjZXJ0YWluIGNhc2VzIGFuZCBjYW4gb3RoZXJ3aXNlIGJlIGlnbm9y
ZWQsIHNob3VsZCBiZSBwdXQgdG8gcmVzdC4gT3IgYW0gSSB0aGUgb25seSBvbmUgd2hvIHdvbmRl
cnMgd2hldGhlciB0aGUgb2xkZXIgYW5kIHRoZSBuZXdlciB3ZXJlIG1lYW50IHRvIGNvZXhpc3Q/
DQoNCk9uIHRoZSBvdGhlciBoYW5kLCB3b3VsZCB0aGlzIGJyZWFrIGFueXRoaW5nIHRoYXQgZXhp
c3RzIG91dCB0aGVyZT8NCg0KQmVydA0KDQo=


From nobody Thu Aug 25 16:03:54 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C683712D642 for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 16:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nTfrxSOAZsO1 for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 16:03:51 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (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 BFFB812D0F5 for <ipv6@ietf.org>; Thu, 25 Aug 2016 16:03:51 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id fi15so20860105pac.1 for <ipv6@ietf.org>; Thu, 25 Aug 2016 16:03:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=O9L9Rdw6Bo3Fz+z2828pNQc6wNGW+Zn4899lxbeLEqs=; b=NftmmaMyl1KgbOUo5D6s7JCgjadznMgZb2yEhVWm23cMpKa3ZelgVpOm+9LpMx+2Sr 7HHM6oe3Y9zDFt+LvBh4F7lR5UvOOaru0SfBh539L1kJa3iGVyDhFDnUym1YoPBhFWrR DwvhNdnxtUFvCjFX3CuvEcAVvh9pRI4CUsX3sgIataNbvIrTISZ4zjDJlQn2cB3ihPw+ ObAhPHyBVHwHzhjbXnMZIwlXhCRL/87UQ7JMnJwqcT/SG90jsiBU2b9Ihcm29F//iD3W StwjkNscoze1HP2Vmyb9TZNwd2dnh7nsAVwqdVYsGRVfYioDSl1OQxQm62x9t0rPZo7v r/RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=O9L9Rdw6Bo3Fz+z2828pNQc6wNGW+Zn4899lxbeLEqs=; b=RTyjUnJn65FbgZMw8AHG+81ozr7Fj06/jESdn51Oubpp4sAGRVia1ffT5CNLfuyyA1 V7P7zOwbIht0LvlJ3O4YJiGRNv4T92dufTvy272MV9h5OkAM+YMuIOy5S5S9LXd989cY ShqcqnUkYS7qZVT2cr5Neq9it5e7OynUm3/euUJTJWNhI9vVxC37YDVOugHpOQhBkz/e g+lps4KKsxxZ8t1vCuhr48JC5hiBsiaOPHvz51FPUAzQOJUwQbR+b6o/SJjssE0IrJ0/ ujb93oRfPi+cHErAjppbYWbmPXCoXdgoVCioR8A7OBxm++th4zCewX+v+R7UYTrou8rk cOiw==
X-Gm-Message-State: AE9vXwPELI2Cc0t1QaswEy79UJegl1NcuVLDsfFNhKnVW6JSvoUMZkDd3MLPKoe0RV+2OQ==
X-Received: by 10.66.246.134 with SMTP id xw6mr90921pac.35.1472166231063; Thu, 25 Aug 2016 16:03:51 -0700 (PDT)
Received: from ?IPv6:2406:e007:5f20:1:28cc:dc4c:9703:6781? ([2406:e007:5f20:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r21sm23270550pfi.52.2016.08.25.16.03.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Aug 2016 16:03:50 -0700 (PDT)
Subject: Re: 2460bis and the Traffic Class field
To: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b6c4073e-d08f-1eda-6453-d1bcf15093b6@gmail.com>
Date: Fri, 26 Aug 2016 11:03:57 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/a1hMUMcH7LhWV4oJ7AQABLvFt3Q>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 23:03:54 -0000

On 26/08/2016 08:32, Brian Haberman wrote:
> All,
>      I came across a discrepancy that I think is worth discussing. After
> the publication of RFC 2460, RFC 2474 was published and that document
> renames the IPv4 TOS and IPv6 Traffic Class fields
> (https://tools.ietf.org/html/rfc2474#section-3). RFC 2474 is then
> updated by RFC 3260 to provide a clarification on the name of the DS Field.
> 
>      I know that 2474 did not formally update 2460, but it seems that
> there was an attempt to rename the Traffic Class field to be consistent
> with its use. Do people think that 2460bis should incorporate those
> changes to be consistent with 2474/3260?

I was about to type "Good catch" but then I thought "Annoying catch" :-).

Two additional points:
1) RFC 3260 is a bit strange - it's Informational but purports to update
a Proposed Standard. I'm not sure that would be approved today. However,
that's a side issue.
2) RFC 3260 cites BCP 37 (RFC 2780 + several updating RFCs). Quoting 2780:

"5.2 IPv6 Traffic Class field

   The IPv6 Traffic Class field is described in [DIFF] as a 6- bit
   Differentiated Services (DS) field and a 2-bit field which is
   currently reserved.  See Section 4.2 for assignment guidelines for
   these fields."

and of course then ECN came along later, but 2780 was not updated in that
respect (I checked all the updating RFCs).

My suggestion:

DO NOT change the name of the Traffic Class field. That would confuse
everybody and invalidate several text books and many other documents.
I consider that this field is used to carry two other fields (DSCP and ECN).
The draft already says:
"  The current use of the Traffic Class field for Differentiated
   Services and Explicit Congestion Notification is specified in
   [RFC2474] and [RFC3168]."

I really don't see what's wrong with that. If we were updating RFC 791,
we'd write

   The current use of the Type of Service field for Differentiated
   Services and Explicit Congestion Notification is specified in
   [RFC2474] and [RFC3168].

I think that referring to RFC 3260 and BCP 37 would muddy the waters.
I'm not sure that many people ever look at 3260 anyway.

DO consider issuing Errata for BCP 37, which really should mention
ECN as well as Diffserv. If we were ever to do RFC2474bis, it would
be useful to adjust its language to take account of ECN too.

Regards
    Brian


From nobody Thu Aug 25 19:06:48 2016
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5555D12D189 for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 19:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 hd8YLBQK2Vx5 for <ipv6@ietfa.amsl.com>; Thu, 25 Aug 2016 19:06:45 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 EA29512D0AF for <ipv6@ietf.org>; Thu, 25 Aug 2016 19:06:44 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id q128so261083985wma.1 for <ipv6@ietf.org>; Thu, 25 Aug 2016 19:06:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Bf7NiAqFFBmbAYzkfntTRtSlDwAgvCUJkCSqvNy+X8o=; b=bWrtOvfVvsnJ4iDrmeoTHxwkirMExDhYS7XMFd/+pxsfHo8uugj5uA3ue8e9CQw9/n PKgKY5wXZ/L16vB5QkouoCxwkuGjt4Jt/yDo3+qZY6Oe5xImzJgG0RJQigfH6MWc/wjz mFMKQ9Xb/XVoGSPyAwyWyPXX/XGgnmwZ845wOjEh8cG3xz9CMWLH6lnx2arY+b8hShQG P0TlDTFwqTP9opw4UoQTCayRpn4r3bcioEWPcrGrYOMsChHuEX2q9EC7/pDSYJHDTBZj zgEaIfIDGWhAKffQUz+tGxJzZkPu+zGqspS+MWrTno3Bt3RjioDUlnQ5OH5umQCHu/QP m7KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Bf7NiAqFFBmbAYzkfntTRtSlDwAgvCUJkCSqvNy+X8o=; b=X0OIf9wdhCo01M85a/GiV/qQUC3wAyAOFFgowxNNmbxAnWZdtniTWHL+fxwg71yUUS gWKDKd8Msfi/tQINEh8DNOcy394LXUIPAyH7nD0IKInmJPbbrvoMYxU+HmSKKsx3VjTu GYkUWYXvjCT6u1haIzpyySNvUyM34gt3R6hnhVk5xa8d8p99euEcpg4SPxfrBv+oDiUh JF3zjW+3LwMzGIokSqZcz3yOUOSGKL0i03GEpJxE20BQjHaXcYUej+tXR33X7rWX6uJ2 1Yju5x6gkWQE0NQ/Y4vzenrPmZ8m7raBG6v/Pyf9cL3wG0He1ef1MwHelKeHYj3/HcCA 6u0Q==
X-Gm-Message-State: AE9vXwNfo0mQDBbbmKGJs+mxL7Ad2tCj/Fj8kVTNClEiz2DGYLktSamMiFTedYWZ6hnYOp/+JFRtBAcd2dQ7MWYy
X-Received: by 10.28.113.135 with SMTP id d7mr658179wmi.43.1472177203341; Thu, 25 Aug 2016 19:06:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.157.2 with HTTP; Thu, 25 Aug 2016 19:06:22 -0700 (PDT)
In-Reply-To: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com>
References: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Fri, 26 Aug 2016 11:06:22 +0900
Message-ID: <CAAedzxqciHA0H+MzJNZVoeA=xGTEo_grO=jaQVMrbmVUytBsRg@mail.gmail.com>
Subject: Re: [v6ops] v6 gateway data forwarding behaviour
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hF3FrThABCLxGGhdWadvRJqAY2c>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 02:06:46 -0000

On 25 August 2016 at 22:57, Naveen Kottapalli <naveen.sarma@gmail.com> wrote:
> Hello,
>
> Assuming that the node is given a prefix in RA by the gateway, does the
> gateway need to know the complete address being used by node for data
> forwarding?

If the RA PIO is 2001:db8:1:2::/64 and the gateway receives a packet
destined to 2001:db8:1:2::f00 which is not in its neighbor cache it
should attempt Neighbor Discovery to find out where to send the
packet.

Did you have some more exotic network configuration in mind?


From nobody Thu Aug 25 20:46:11 2016
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 596CE12D09A; Thu, 25 Aug 2016 20:46:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham 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 qo39tgMeuEkp; Thu, 25 Aug 2016 20:46:02 -0700 (PDT)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id C4E80127071; Thu, 25 Aug 2016 20:45:59 -0700 (PDT)
Authentication-Results: smtp2.au.logicalis.com; spf=None smtp.mailfrom=gdaley@au.logicalis.com; spf=None smtp.helo=postmaster@sdcexchht.au.logicalis.com
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=10.18.196.63; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=10.18.196.63; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([10.18.196.63]) by smtp2.au.logicalis.com with ESMTP; 26 Aug 2016 13:45:42 +1000
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([100.64.20.45]) with mapi id 14.03.0279.002; Fri, 26 Aug 2016 13:45:41 +1000
From: Greg Daley <gdaley@au.logicalis.com>
To: Naveen Kottapalli <naveen.sarma@gmail.com>
Subject: Re: v6 gateway data forwarding behaviour
Thread-Topic: v6 gateway data forwarding behaviour
Thread-Index: AQHR/tjxjRRBpo+F80OHYqRfAvn6zaBamvCe
Date: Fri, 26 Aug 2016 03:45:40 +0000
Message-ID: <CC398CF2-773D-4475-9863-71E869B9E972@au.logicalis.com>
References: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com>
In-Reply-To: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/CcZxyYMwCE2E3rZIRrc36Hj_Xhc>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 03:46:06 -0000

Hi Naveen,

Not for reception from the local link. The router only needs ip address to =
MAC mapping to deliver packets to devices on link (associated with the pref=
ix)

This is why it is called a neighbour cache, not a neighbour table

Sincerely,

Greg Daley
Logicalis Australia Pty Ltd
E gdaley@au.logicalis.com
M +61 401 772 770

On Aug 25, 2016, at 11:59 PM, Naveen Kottapalli <naveen.sarma@gmail.com> wr=
ote:

Hello,

Assuming that the node is given a prefix in RA by the gateway, does the gat=
eway need to know the complete address being used by node for data forwardi=
ng?

Yours,
Naveen.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From nobody Fri Aug 26 00:06:01 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400D812D0A9 for <ipv6@ietfa.amsl.com>; Fri, 26 Aug 2016 00:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=jisc365.onmicrosoft.com
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 zegIbSqLDQ22 for <ipv6@ietfa.amsl.com>; Fri, 26 Aug 2016 00:05:57 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC77128E19 for <ipv6@ietf.org>; Fri, 26 Aug 2016 00:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=fr2tcD1SRcFd7ZhPkdeort2FCovPwx+3SV9RDVaa06Y=; b=ba4jVus9tOTKIM4EN73Y8YozcrZb0NIiVDjxZIr3AvtB0cAsuUOFhyKMDH7HZPKYocVlXhhGdw4RjZgeiK98kBBBoAVzBy3Kb64goIHuimsjdO/aToF16hYpvf5thHcKvXAWYBilWoqAeTj0xLGd+De5Li3SuS1z84tRbeHK+2I=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0177.outbound.protection.outlook.com [213.199.154.177]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-58-IWy1VRy2O_6T9CB7S3PW-g-1; Fri, 26 Aug 2016 08:05:50 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB456.eurprd07.prod.outlook.com (10.242.106.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.549.15; Fri, 26 Aug 2016 07:05:46 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0549.023; Fri, 26 Aug 2016 07:05:46 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 2460bis and the Traffic Class field
Thread-Topic: 2460bis and the Traffic Class field
Thread-Index: AQHR/w/iZqozRCOrcUin2CaESO7h5aBaS8qAgACHdoA=
Date: Fri, 26 Aug 2016 07:05:46 +0000
Message-ID: <4BD82B01-4190-4D47-B063-1D136562A914@jisc.ac.uk>
References: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net> <b6c4073e-d08f-1eda-6453-d1bcf15093b6@gmail.com>
In-Reply-To: <b6c4073e-d08f-1eda-6453-d1bcf15093b6@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:a88:d510:1101:cea:402b:54b4:c217]
x-ms-office365-filtering-correlation-id: bc468943-f2a5-4cb2-b41b-08d3cd7f676c
x-microsoft-exchange-diagnostics: 1; AMSPR07MB456; 20:8Nm0E93zk53GCWPHQ+bYdDvylAYorbudc4o4zStf/j4+E8v6H3ST0Br9cTpT76i+N9qeEbN41l/6+2aDFOPJm+iAYt3bmLPVpOnJkESm5jpp+1yytXZNsE1xvOKtwCiwa6R4vINU5X5dQAx5fJVKKaHe2RafSBPT/OjgjDp4bjs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB456;
x-microsoft-antispam-prvs: <AMSPR07MB456B933004E2C0A66BE218CD6EC0@AMSPR07MB456.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001);  SRVR:AMSPR07MB456; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB456; 
x-forefront-prvs: 00462943DE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(189002)(51444003)(24454002)(199003)(8676002)(5660300001)(2906002)(5002640100001)(7736002)(92566002)(305945005)(11100500001)(50226002)(50986999)(87936001)(8936002)(83716003)(105586002)(19580395003)(4326007)(76176999)(7846002)(101416001)(586003)(15975445007)(110136002)(2900100001)(10400500002)(106116001)(3660700001)(6116002)(2950100001)(81166006)(82746002)(19580405001)(57306001)(77096005)(36756003)(106356001)(33656002)(122556002)(74482002)(68736007)(102836003)(189998001)(3280700002)(86362001)(81156014)(97736004)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB456; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <50710745E52F234395E19D1F3E4629A3@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Aug 2016 07:05:46.6888 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB456
X-MC-Unique: IWy1VRy2O_6T9CB7S3PW-g-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/hiLCA_xtMmec-Zx0-wwh6fmzpe8>
Cc: Brian Haberman <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 07:06:00 -0000

Hi,

> On 26 Aug 2016, at 00:03, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
>=20
> On 26/08/2016 08:32, Brian Haberman wrote:
>> All,
>>     I came across a discrepancy that I think is worth discussing. After
>> the publication of RFC 2460, RFC 2474 was published and that document
>> renames the IPv4 TOS and IPv6 Traffic Class fields
>> (https://tools.ietf.org/html/rfc2474#section-3). RFC 2474 is then
>> updated by RFC 3260 to provide a clarification on the name of the DS Fie=
ld.
>>=20
>>     I know that 2474 did not formally update 2460, but it seems that
>> there was an attempt to rename the Traffic Class field to be consistent
>> with its use. Do people think that 2460bis should incorporate those
>> changes to be consistent with 2474/3260?
>=20
> I was about to type "Good catch" but then I thought "Annoying catch" :-).
>=20
> Two additional points:
> 1) RFC 3260 is a bit strange - it's Informational but purports to update
> a Proposed Standard. I'm not sure that would be approved today. However,
> that's a side issue.
> 2) RFC 3260 cites BCP 37 (RFC 2780 + several updating RFCs). Quoting 2780=
:
>=20
> "5.2 IPv6 Traffic Class field
>=20
>   The IPv6 Traffic Class field is described in [DIFF] as a 6- bit
>   Differentiated Services (DS) field and a 2-bit field which is
>   currently reserved.  See Section 4.2 for assignment guidelines for
>   these fields."
>=20
> and of course then ECN came along later, but 2780 was not updated in that
> respect (I checked all the updating RFCs).
>=20
> My suggestion:
>=20
> DO NOT change the name of the Traffic Class field. That would confuse
> everybody and invalidate several text books and many other documents.
> I consider that this field is used to carry two other fields (DSCP and EC=
N).
> The draft already says:
> "  The current use of the Traffic Class field for Differentiated
>   Services and Explicit Congestion Notification is specified in
>   [RFC2474] and [RFC3168].=94

I agree; a) keeping the name the same avoids confusion, and b) the text now=
 appropriately cites the ECN usage.

Tim

> I really don't see what's wrong with that. If we were updating RFC 791,
> we'd write
>=20
>   The current use of the Type of Service field for Differentiated
>   Services and Explicit Congestion Notification is specified in
>   [RFC2474] and [RFC3168].
>=20
> I think that referring to RFC 3260 and BCP 37 would muddy the waters.
> I'm not sure that many people ever look at 3260 anyway.
>=20
> DO consider issuing Errata for BCP 37, which really should mention
> ECN as well as Diffserv. If we were ever to do RFC2474bis, it would
> be useful to adjust its language to take account of ECN too.
>=20
> Regards
>    Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Fri Aug 26 01:00:50 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30ED712D10C; Fri, 26 Aug 2016 01:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xZhlRPiDqKeg; Fri, 26 Aug 2016 01:00:47 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 D737A127077; Fri, 26 Aug 2016 01:00:46 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id e63so318283902ith.1; Fri, 26 Aug 2016 01:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k+HVP/f0C4w5lKGJxvEgyzvFufpsZMRoVciwGgyUBnk=; b=MZ2ctDYfRxYdeuJkqJyWKozzlNcCFggRC9httnjWKs4RLHWBboKlAzrhUf7IVJChkc j3KNu/DGToeQ6tUP+iqi8KtS/XtyQNdMQ+Jj5clMiYHP63TxAVI8I1G3ZdX69owgCiiX rwHrXKbtHp5Huv9k0BD+W4hjFkKz77UIbzIuW8TTSsryE9Xlz2+tsPVv7nHpBlWdhPgG lUpc11xooseiRyN0OYbLz7Cd8lQEuivm+kWf89qZGW5UH2u435qJgAWDst4W8iPGwFVB f0P9seynLz7+ppzX8hyZQm8eaIL4bgkgCqLE75g4PFLfLBFdnEJllrZlKhhhp1p4tP40 yqSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k+HVP/f0C4w5lKGJxvEgyzvFufpsZMRoVciwGgyUBnk=; b=YqfXhP9DhCpESOLOPpRt7YM1/mDXTPC4YRWQI4vqy1YzVbmtxWIgoGpvLBbwyGa/a9 2ddowcLVt6E0g8Acjy6p/q82wm27Z5GUVU/V+ijoG4NK7u0uuqyqsPvHJeDXwMaLbeZ0 mavg/Aqi4UT/HRp5ukOkd8OhXjcnxYKHcg22BQA8em3H4b1Gin1g4tvEMq6ygSHjXXc5 ddZsN+kEopERRhY1GaUKiFQhQ0d25YaDSdwY3YfIe60GzCiYtvjkBlqhVtsLsQmP+jQl LsM7edTTHTScAfEBAOBy0UdSDinPZ/qICJiXZbFNzKlHnwkG3BC1Fe9LVPbTtDjUbO1W I2Og==
X-Gm-Message-State: AE9vXwNSd51m0Vh8ZC6QW8oEEe7GAXuPYSCMlsCtQGyfm+khr2vjhHfE9n70Sc5B0KJggZWFyjSlvdh2WKaOrQ==
X-Received: by 10.107.16.77 with SMTP id y74mr2221357ioi.161.1472198446203; Fri, 26 Aug 2016 01:00:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Fri, 26 Aug 2016 01:00:25 -0700 (PDT)
In-Reply-To: <CAAedzxqciHA0H+MzJNZVoeA=xGTEo_grO=jaQVMrbmVUytBsRg@mail.gmail.com>
References: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com> <CAAedzxqciHA0H+MzJNZVoeA=xGTEo_grO=jaQVMrbmVUytBsRg@mail.gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Fri, 26 Aug 2016 13:30:25 +0530
Message-ID: <CANFmOtkwiu-sObjH_YtzKKJfM-m_XzdMc=FAGqX6sXC71RWNqQ@mail.gmail.com>
Subject: Re: [v6ops] v6 gateway data forwarding behaviour
To: Erik Kline <ek@google.com>
Content-Type: multipart/alternative; boundary=001a113e811c6cc73f053af4e989
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RfVtic2WM1VH0fIputwYyMEvQpo>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 08:00:48 -0000

--001a113e811c6cc73f053af4e989
Content-Type: text/plain; charset=UTF-8

No, no special configuration is planned.  I was wondering that for data
forwarding does the router need to know the complete 128-bit address of the
client after prefix assignment or not.

Yours,
Naveen.

On 26 August 2016 at 07:36, Erik Kline <ek@google.com> wrote:

> On 25 August 2016 at 22:57, Naveen Kottapalli <naveen.sarma@gmail.com>
> wrote:
> > Hello,
> >
> > Assuming that the node is given a prefix in RA by the gateway, does the
> > gateway need to know the complete address being used by node for data
> > forwarding?
>
> If the RA PIO is 2001:db8:1:2::/64 and the gateway receives a packet
> destined to 2001:db8:1:2::f00 which is not in its neighbor cache it
> should attempt Neighbor Discovery to find out where to send the
> packet.
>
> Did you have some more exotic network configuration in mind?
>

--001a113e811c6cc73f053af4e989
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">No, no special configuration is planned.=C2=A0 I was wonde=
ring that for data forwarding does the router need to know the complete 128=
-bit address of the client after prefix assignment or not.</div><div class=
=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature" data=
-smartmail=3D"gmail_signature">Yours,<br>Naveen.</div></div>
<br><div class=3D"gmail_quote">On 26 August 2016 at 07:36, Erik Kline <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ek@google.com" target=3D"_blank">ek@goog=
le.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On 25 August 2016 at 22:57, Naveen Kottapalli &lt;<a href=3D"mailto:n=
aveen.sarma@gmail.com">naveen.sarma@gmail.com</a>&gt; wrote:<br>
&gt; Hello,<br>
&gt;<br>
&gt; Assuming that the node is given a prefix in RA by the gateway, does th=
e<br>
&gt; gateway need to know the complete address being used by node for data<=
br>
&gt; forwarding?<br>
<br>
</span>If the RA PIO is 2001:db8:1:2::/64 and the gateway receives a packet=
<br>
destined to 2001:db8:1:2::f00 which is not in its neighbor cache it<br>
should attempt Neighbor Discovery to find out where to send the<br>
packet.<br>
<br>
Did you have some more exotic network configuration in mind?<br>
</blockquote></div><br></div>

--001a113e811c6cc73f053af4e989--


From nobody Fri Aug 26 01:07:36 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2D212D0E4; Fri, 26 Aug 2016 01:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ePzyfYaAzCns; Fri, 26 Aug 2016 01:07:33 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (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 787DD12D0DA; Fri, 26 Aug 2016 01:07:33 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id d65so13170420ith.0; Fri, 26 Aug 2016 01:07:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=esJHDANWqet66ToAPIcyMa8JiyCmLP4b3zTGxB1M3Ms=; b=D4SkE+6d3la3352BxyfRXnnhPoOEeXdeNi8HpC/uTv5kwRH6fY0Yt6L881lu6FDYNO /xwX5k0nKNmVReLekZ+YMpGObqCAiCkz19Z/aB+4DTU5WVb+couqpjesTuyNAnYzEBPO N22crFTq2SXp9YEAO+Ont1QZKjBS5A4PhA8T9VLQkeEHE+YKvfT6MZGn4AytOI+oZ2z2 LR1YU5RCdQJSVGMidqR/aT+JnBDbQczhfs7LilK3YP6G/YnlORtc3R49xE8jW+vBmt3V p37q6EuSk+tgaA+La1uUu1sAqr0zf5JmecEB8IZnLrWhGi/Tpcyohm5ixEkPWrta1YUy Mk4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=esJHDANWqet66ToAPIcyMa8JiyCmLP4b3zTGxB1M3Ms=; b=Kvix6FzfdqHjLsDl4GlWPJ5Iyq0mst7zjgEcG9OZKHbdfeT2zpEZJD4cCDhcV7PvXG MMEDqrzIX4m/4PbxU6q6tHoi2tFWdRlvb37vNk/hH0FHeA+tzLO9r2/zQvW41Hgfe8SC zVoXzvSKKwFMm1MmyZil5cGTm4p3QJeIu3fkd/t2bFk5S95JUSi1DeB5cJq9bF8YgmHa Sy0fxdyG6ctZysb6mYMJksVT8mjo/RQXUQFDL7wwMSwqNLWm5lMGxmGn/HtYtqul3fAq Buyw5gH/blWTZ10h0y2nxrt8XnkkdPZUSo6jaHGutW38mawphv0YffcP5CNwMXsbtSJN ZlLw==
X-Gm-Message-State: AEkooutizyXDFd8mxeJ8+8W14AFmv3TWraitw9WRYXVP+hVzCrFPnp90gNhh9hldEZl9Y2vd5reVItwspjw52A==
X-Received: by 10.36.95.202 with SMTP id r193mr10753393itb.48.1472198852862; Fri, 26 Aug 2016 01:07:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Fri, 26 Aug 2016 01:07:12 -0700 (PDT)
In-Reply-To: <CC398CF2-773D-4475-9863-71E869B9E972@au.logicalis.com>
References: <CANFmOtkt9m=e+fLHOj2SY0FSjB_Hicd51TL_-QwYUC7FVJEt3Q@mail.gmail.com> <CC398CF2-773D-4475-9863-71E869B9E972@au.logicalis.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Fri, 26 Aug 2016 13:37:12 +0530
Message-ID: <CANFmOt=qextGX1aWwiw+WmZt8rncDJjLB2ySTLYKfpYVnEFAPg@mail.gmail.com>
Subject: Re: v6 gateway data forwarding behaviour
To: Greg Daley <gdaley@au.logicalis.com>
Content-Type: multipart/alternative; boundary=001a1144c0d6a9ea74053af501b8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_qTiPenOQOQZStW6XxV2UwJawIQ>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 08:07:35 -0000

--001a1144c0d6a9ea74053af501b8
Content-Type: text/plain; charset=UTF-8

Thanks Greg!

Yours,
Naveen.

On 26 August 2016 at 09:15, Greg Daley <gdaley@au.logicalis.com> wrote:

> Hi Naveen,
>
> Not for reception from the local link. The router only needs ip address to
> MAC mapping to deliver packets to devices on link (associated with the
> prefix)
>
> This is why it is called a neighbour cache, not a neighbour table
>
> Sincerely,
>
> Greg Daley
> Logicalis Australia Pty Ltd
> E gdaley@au.logicalis.com
> M +61 401 772 770
>
> On Aug 25, 2016, at 11:59 PM, Naveen Kottapalli <naveen.sarma@gmail.com>
> wrote:
>
> Hello,
>
> Assuming that the node is given a prefix in RA by the gateway, does the
> gateway need to know the complete address being used by node for data
> forwarding?
>
> Yours,
> Naveen.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--001a1144c0d6a9ea74053af501b8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Greg!</div><div class=3D"gmail_extra"><br clear=3D"=
all"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"=
>Yours,<br>Naveen.</div></div>
<br><div class=3D"gmail_quote">On 26 August 2016 at 09:15, Greg Daley <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:gdaley@au.logicalis.com" target=3D"_blan=
k">gdaley@au.logicalis.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">Hi Naveen,<br>
<br>
Not for reception from the local link. The router only needs ip address to =
MAC mapping to deliver packets to devices on link (associated with the pref=
ix)<br>
<br>
This is why it is called a neighbour cache, not a neighbour table<br>
<br>
Sincerely,<br>
<br>
Greg Daley<br>
Logicalis Australia Pty Ltd<br>
E <a href=3D"mailto:gdaley@au.logicalis.com">gdaley@au.logicalis.com</a><br=
>
M +61 401 772 770<br>
<div><div class=3D"h5"><br>
On Aug 25, 2016, at 11:59 PM, Naveen Kottapalli &lt;<a href=3D"mailto:navee=
n.sarma@gmail.com">naveen.sarma@gmail.com</a>&gt; wrote:<br>
<br>
Hello,<br>
<br>
Assuming that the node is given a prefix in RA by the gateway, does the gat=
eway need to know the complete address being used by node for data forwardi=
ng?<br>
<br>
Yours,<br>
Naveen.<br>
</div></div>------------------------------<wbr>----------------------------=
--<wbr>--------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</blockquote></div><br></div>

--001a1144c0d6a9ea74053af501b8--


From nobody Fri Aug 26 03:21:34 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0167712D1AF; Fri, 26 Aug 2016 03:21:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
Subject: 6man - New Meeting Session Request for IETF 97
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147220689196.28435.18012669647135580785.idtracker@ietfa.amsl.com>
Date: Fri, 26 Aug 2016 03:21:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5oulJkUnpXh5aQYLLnSMOg5kQxw>
Cc: ot@cisco.com, ipv6@ietf.org, suresh.krishnan@ericsson.com, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 10:21:32 -0000

A new meeting session request has just been submitted by Ole Troan, a Chair of the 6man working group.


---------------------------------------------------------
Working Group Name: IPv6 Maintenance
Area Name: Internet Area
Session Requester: Ole Troan

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 150
Conflicts to Avoid: 
 First Priority: 6lo 6tisch dhc homenet intarea v6ops softwire spring




Special Requests:
  
---------------------------------------------------------


From nobody Fri Aug 26 12:02:52 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B738612D0DD for <ipv6@ietfa.amsl.com>; Fri, 26 Aug 2016 12:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 10U9DokoHkKW for <ipv6@ietfa.amsl.com>; Fri, 26 Aug 2016 12:02:49 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (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 0994012D798 for <ipv6@ietf.org>; Fri, 26 Aug 2016 12:02:47 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id d65so6996664ith.0 for <ipv6@ietf.org>; Fri, 26 Aug 2016 12:02:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=E1cU9stLkLXK4RngA/SHPhtzMB675SpT6i0FOknEW+0=; b=ZOJ9Qklxy1MJuMumcVmRdQV0Qzz43tpROCVsjUVNFScVtg1UCqT+IeWxMvUFhCMc9F kPcTYsSt71o4Z7LaYqBMRxVFK63jl+fjay8XJEjIxZDjCMSRi+RDMsAbX5c8Cg7sN2fP sl37V1zrZrOAiJZKEEPf9U08q2IfPluXpGrHnln95FzZcPei+zXXm4yIeW2VgM6zKlrs aLrTZafiphhP+Borsz9vWCQkuBoeIdkEjOgpck4U5wr9gice+hQel3UMRVeLVJ1E5g4X kRCFuT4LVwPXPDMnmiDCBLP397H03Sbd0LCyqU9nSEvKLejAqjmYhclodiGyRyF8/l97 ocUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=E1cU9stLkLXK4RngA/SHPhtzMB675SpT6i0FOknEW+0=; b=J2LCBfjdyx5DfU1x5dw2oFxI+XmSbAnYjrJHpp6zOqeLopFVv8OZjISCCRZjPnl1OU m85dlOjww2SdX8CuhU9WSc54cOVAcuXS0WnI77YtVORR7Ag8qW0Df9C300oNiaQPYsLP fxriQPCONWUCDf7T3D0FTODxXOSDxAJXuRGZXhFf/VvAZ47PWZ1hlIzkCg5myeW2FzDF DOHiygIJHeNeqAVxPNidtOZxxng3I/EDyLutUBlc+ufKmYiaIgOyMIcTeAX0mDpkVULv VwNUdwdOWOsizEWXcvYiQF6f8IwCuGP6kgOD3MxlYUyMkj31teJTpxHFWIoxqzOWiaJJ icrQ==
X-Gm-Message-State: AE9vXwNZZs1pWdXZW7CS4vGFafDQOOkXmcCPESPSvszjul3OFZfkrroan38wgmGbVdoOCQ==
X-Received: by 10.107.173.88 with SMTP id w85mr5913218ioe.63.1472238166250; Fri, 26 Aug 2016 12:02:46 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id k69sm8176047ioi.20.2016.08.26.12.02.45 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 26 Aug 2016 12:02:45 -0700 (PDT)
Subject: Re: 2460bis and the Traffic Class field
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_61B772F0-87D1-4030-AD2C-473A45EFAE9C"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4BD82B01-4190-4D47-B063-1D136562A914@jisc.ac.uk>
Date: Fri, 26 Aug 2016 12:02:42 -0700
Message-Id: <BA8A22BB-2056-41B8-8E1E-0A0F738068FF@gmail.com>
References: <b26e392d-98a0-6d0d-2942-38c5dc349981@innovationslab.net> <b6c4073e-d08f-1eda-6453-d1bcf15093b6@gmail.com> <4BD82B01-4190-4D47-B063-1D136562A914@jisc.ac.uk>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qh06qoLDyZgxI7_coDKZXqfQHt0>
Cc: IPv6 List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 19:02:51 -0000

--Apple-Mail=_61B772F0-87D1-4030-AD2C-473A45EFAE9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On Aug 26, 2016, at 12:05 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>=20
> Hi,
>=20
>> On 26 Aug 2016, at 00:03, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>> On 26/08/2016 08:32, Brian Haberman wrote:
>>> All,
>>>    I came across a discrepancy that I think is worth discussing. =
After
>>> the publication of RFC 2460, RFC 2474 was published and that =
document
>>> renames the IPv4 TOS and IPv6 Traffic Class fields
>>> (https://tools.ietf.org/html/rfc2474#section-3). RFC 2474 is then
>>> updated by RFC 3260 to provide a clarification on the name of the DS =
Field.
>>>=20
>>>    I know that 2474 did not formally update 2460, but it seems that
>>> there was an attempt to rename the Traffic Class field to be =
consistent
>>> with its use. Do people think that 2460bis should incorporate those
>>> changes to be consistent with 2474/3260?
>>=20
>> I was about to type "Good catch" but then I thought "Annoying catch" =
:-).
>>=20
>> Two additional points:
>> 1) RFC 3260 is a bit strange - it's Informational but purports to =
update
>> a Proposed Standard. I'm not sure that would be approved today. =
However,
>> that's a side issue.
>> 2) RFC 3260 cites BCP 37 (RFC 2780 + several updating RFCs). Quoting =
2780:
>>=20
>> "5.2 IPv6 Traffic Class field
>>=20
>>  The IPv6 Traffic Class field is described in [DIFF] as a 6- bit
>>  Differentiated Services (DS) field and a 2-bit field which is
>>  currently reserved.  See Section 4.2 for assignment guidelines for
>>  these fields."
>>=20
>> and of course then ECN came along later, but 2780 was not updated in =
that
>> respect (I checked all the updating RFCs).
>>=20
>> My suggestion:
>>=20
>> DO NOT change the name of the Traffic Class field. That would confuse
>> everybody and invalidate several text books and many other documents.
>> I consider that this field is used to carry two other fields (DSCP =
and ECN).
>> The draft already says:
>> "  The current use of the Traffic Class field for Differentiated
>>  Services and Explicit Congestion Notification is specified in
>>  [RFC2474] and [RFC3168].=94
>=20
> I agree; a) keeping the name the same avoids confusion, and b) the =
text now appropriately cites the ECN usage.

I agree as well.

Bob

>=20
> Tim
>=20
>> I really don't see what's wrong with that. If we were updating RFC =
791,
>> we'd write
>>=20
>>  The current use of the Type of Service field for Differentiated
>>  Services and Explicit Congestion Notification is specified in
>>  [RFC2474] and [RFC3168].
>>=20
>> I think that referring to RFC 3260 and BCP 37 would muddy the waters.
>> I'm not sure that many people ever look at 3260 anyway.
>>=20
>> DO consider issuing Errata for BCP 37, which really should mention
>> ECN as well as Diffserv. If we were ever to do RFC2474bis, it would
>> be useful to adjust its language to take account of ECN too.
>>=20
>> Regards
>>   Brian
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_61B772F0-87D1-4030-AD2C-473A45EFAE9C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEbBAEBCgAGBQJXwJJTAAoJEK7rdBF357uoAukH9iZzbCZePwjMj/EEFNhMlFbT
tWy8g2KtmYvdcJfk6Nko4VOwnfY1+YKy3suME+NMbPjWMERNOxp+ODocJrGpP3WA
SI8UPOQ6G0xR9zPVB5xY3AwFGGDAZals7f4+t7Z7ri+8mzi0MvTEU+LARUdIHB8Z
onndg6I32wNNAund0tQzoMp6iXi6PdEpun7oSKVi/WPuOIMLOAtaOUMDxGjbn7IU
+OM437HSw+Gs95lVw8vHiTgC4nWhHHdDBk0rHfCqDxJSS7BhT0AqXTwJPtrZxaSD
gBLLZR76f/ompZU4oV8Uf+n80L7bMsRqMWi03jQFNk8ZTtznezQlLDruAGrRpA==
=Tqg9
-----END PGP SIGNATURE-----

--Apple-Mail=_61B772F0-87D1-4030-AD2C-473A45EFAE9C--


From nobody Fri Aug 26 12:30:39 2016
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119CE12D0DD; Fri, 26 Aug 2016 12:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.447
X-Spam-Level: 
X-Spam-Status: No, score=-7.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 Z-joraw_lMqp; Fri, 26 Aug 2016 12:30:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 63FD512D7F3; Fri, 26 Aug 2016 12:30:33 -0700 (PDT)
Received: from [128.9.184.193] ([128.9.184.193]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u7QJTdIo027716 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 26 Aug 2016 12:29:39 -0700 (PDT)
From: Joe Touch <touch@isi.edu>
To: 6man <ipv6@ietf.org>
Subject: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
Message-ID: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu>
Date: Fri, 26 Aug 2016 12:29:39 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------EC737707B399A92D0C88158E"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/_HuqTbrauwdGcNtRtesQZwrN8go>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 19:30:38 -0000

This is a multi-part message in MIME format.
--------------EC737707B399A92D0C88158E
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Hi, all,

I've reviewed this document as part of the Transport Area Review Team's
(TSVART) ongoing effort to review key IETF documents. These comments
were written primarily for the transport area directors, but are copied
to the document's authors for their information and to allow them to
address any issues raised. When done at the time of IETF Last Call, the
authors should consider this review together with any other last-call
comments they receive. Please always CC ​tsv-art@ietf.org
<mailto:tsv-art@ietf.org> if you reply to or forward this review.

Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-6man-deprecate-atomfrag-generation 
Title: Generation of IPv6 Atomic Fragments Considered Harmful
Reviewer: J. Touch
Review Date: August 26, 2016
IETF Last Call Date: August 8, 2016

Summary: This draft is on the right track but has open issues, described
in the review.

The document has no issues directly applicable to transport protocols.
The impact on transports is indirect, in the ability of RFC 6145-style
IPv6/IPv4 translators to support IPv6-to-IPv4 translation and deal with
IPv4-side fragmentation.

However, there are some important non-transport issues that are noted below.

Major issues:

The impact of this change does not appear to have been explored. Section
3 ends with a claim that links where this translation issue would be a
problem are rare, but there is no evidence presented as to whether
current RFC 6145 translators would be capable of complying with the
changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
ID generation MUST be supported (and used), rather than MAY.

The document concludes that the translator should create IPv4 IDs rather
than relying on atomic fragments as a source of that information (as per
RFC2460) because there is no benefit, but are two reasons why this
method is directly hazardous as well: 1) RFC 2460 does not require that
the IPv6 ID field is generated to ensure that the low 16-bits are unique
as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
translation could result in collisions where two distinct IPv6
destinations are translated into the same IPv4 address, such that IDs
that might have been generated to be unique in the IPv6 context could
end up colliding when used in the translated IPv4 context. I.e., this
does not require ECMP as implied in Section 3.

Minor issues:

IMO, it remains unwise to continue to imply that networks should treat
packets with fragment headers as an attack. Fragmentation support is
critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
find ways to support their use safely. The text should be edited to
explain that the primary motivation here is to avoid generating
erroneous IPv4 ID fields, rather than to react to the incorrect
classification of fragment headers as incompatible with the Internet.

The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
be supported with evidence. I appreciate that such evidence may be
difficult to observe. In the absence of evidence, the statement should
be more clear that there is no evidence to the contrary -- which is not
the same as being able to claim that they *are* in fact rare.

--




--------------EC737707B399A92D0C88158E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, all,</p>
    <p>I've reviewed this document as part of the Transport Area Review
      Team's (TSVART)
      ongoing effort to review key IETF documents. These comments were
      written primarily for the transport area directors, but are copied
      to the document's authors for their information and to allow them
      to address any issues raised. When done at the time of IETF Last
      Call, the authors should consider this review together with any
      other last-call comments they receive. Please always CC <a
        class="mail-link" href="mailto:tsv-art@ietf.org"><span
          class="icon">​</span>tsv-art@ietf.org</a> if you reply to or
      forward this review. <br>
    </p>
    <p>Please resolve these comments along with any other Last Call
      comments you may receive. Please wait for direction from your
      document shepherd or AD before posting a new version of the draft.
      <br>
      <br>
      Document: draft-ietf-6man-deprecate-atomfrag-generation 
      <br>
      Title: Generation of IPv6 Atomic Fragments Considered Harmful<br>
      Reviewer: J. Touch<br>
      Review Date: August 26, 2016
      <br>
      IETF Last Call Date: August 8, 2016
      <br>
      <br>
      Summary: This draft is on the right track but has open issues,
      described in the review. </p>
    <p>The document has no issues directly applicable to transport
      protocols. The impact on transports is indirect, in the ability of
      RFC 6145-style IPv6/IPv4 translators to support IPv6-to-IPv4
      translation and deal with IPv4-side fragmentation. <br>
    </p>
    <p>However, there are some important non-transport issues that are
      noted below.<br>
      <br>
      Major issues: <br>
    </p>
    <p>The impact of this change does not appear to have been explored.
      Section 3 ends with a claim that links where this translation
      issue would be a problem are rare, but there is no evidence
      presented as to whether current RFC 6145 translators would be
      capable of complying with the changes in this doc, e.g., to be
      able to generate IPv4 IDs as needed. I.e., this document needs to
      update RFC6145 Sec 5.1 to require that IPv4 ID generation MUST be
      supported (and used), rather than MAY.<br>
      <br>
      The document concludes that the translator should create IPv4 IDs
      rather than relying on atomic fragments as a source of that
      information (as per RFC2460) because there is no benefit, but are
      two reasons why this method is directly hazardous as well: 1) RFC
      2460 does not require that the IPv6 ID field is generated to
      ensure that the low 16-bits are unique as required for use as IPv4
      IDs as defined in RFC 6145, and 2) RFC 6145 translation could
      result in collisions where two distinct IPv6 destinations are
      translated into the same IPv4 address, such that IDs that might
      have been generated to be unique in the IPv6 context could end up
      colliding when used in the translated IPv4 context. I.e., this
      does not require ECMP as implied in Section 3.</p>
    <p>Minor issues: <br>
    </p>
    <p>IMO, it remains unwise to continue to imply that networks should
      treat packets with fragment headers as an attack. Fragmentation
      support is critical to tunneling (see draft-ietf-intarea-tunnels)
      and we need to find ways to support their use safely. The text
      should be edited to explain that the primary motivation here is to
      avoid generating erroneous IPv4 ID fields, rather than to react to
      the incorrect classification of fragment headers as incompatible
      with the Internet.</p>
    <p>The claim that links with IPv6 MTUs smaller than 1260 are rare
      needs to be supported with evidence. I appreciate that such
      evidence may be difficult to observe. In the absence of evidence,
      the statement should be more clear that there is no evidence to
      the contrary -- which is not the same as being able to claim that
      they *are* in fact rare.<br>
    </p>
    <p>--<br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------EC737707B399A92D0C88158E--


From nobody Sun Aug 28 01:07:55 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8F2A12D1D5; Sun, 28 Aug 2016 01:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.358
X-Spam-Level: 
X-Spam-Status: No, score=-0.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, SPF_PASS=-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 bjRgyJd-HXpC; Sun, 28 Aug 2016 01:07:41 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBA3B12D19E; Sun, 28 Aug 2016 01:07:40 -0700 (PDT)
Received: from [10.10.15.71] (mail.interplazahotel.com.ar [201.216.217.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id A4D0880292; Sun, 28 Aug 2016 10:07:32 +0200 (CEST)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Joe Touch <touch@isi.edu>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com>
Date: Sat, 27 Aug 2016 19:37:40 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/WfSh2OBqpru-WkRzRLDL1gS-VTc>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2016 08:07:43 -0000

Hello, Joe,

Thanks so much for your review! -- Please find my responses in-line...

On 08/26/2016 04:29 PM, Joe Touch wrote:
> 
> Document: draft-ietf-6man-deprecate-atomfrag-generation 
> Title: Generation of IPv6 Atomic Fragments Considered Harmful
> Reviewer: J. Touch
> Review Date: August 26, 2016
> IETF Last Call Date: August 8, 2016
> 
> Summary: This draft is on the right track but has open issues, described
> in the review.
> 
> The document has no issues directly applicable to transport protocols.
> The impact on transports is indirect, in the ability of RFC 6145-style
> IPv6/IPv4 translators to support IPv6-to-IPv4 translation and deal with
> IPv4-side fragmentation.
> 
> However, there are some important non-transport issues that are noted below.
> 
> Major issues:
> 
> The impact of this change does not appear to have been explored. Section
> 3 ends with a claim that links where this translation issue would be a
> problem are rare, but there is no evidence presented as to whether
> current RFC 6145 translators would be capable of complying with the
> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
> ID generation MUST be supported (and used), rather than MAY.

RFC 6145 has been revised as RFC7915.



> The document concludes that the translator should create IPv4 IDs rather
> than relying on atomic fragments as a source of that information (as per
> RFC2460) because there is no benefit, but are two reasons why this
> method is directly hazardous as well: 1) RFC 2460 does not require that
> the IPv6 ID field is generated to ensure that the low 16-bits are unique
> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
> translation could result in collisions where two distinct IPv6
> destinations are translated into the same IPv4 address, such that IDs
> that might have been generated to be unique in the IPv6 context could
> end up colliding when used in the translated IPv4 context. I.e., this
> does not require ECMP as implied in Section 3.

mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
actually describing the only possible scenario in which relying on the
ID in the Frag Header could be of use (i.e., possibly result in lower
collision rates).




> Minor issues:
> 
> IMO, it remains unwise to continue to imply that networks should treat
> packets with fragment headers as an attack. Fragmentation support is
> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
> find ways to support their use safely. The text should be edited to
> explain that the primary motivation here is to avoid generating
> erroneous IPv4 ID fields, rather than to react to the incorrect
> classification of fragment headers as incompatible with the Internet.

Not sure what you mean.

We're not implying that packets employing FH are an attack. FWIW, I
don't personally think so. We do think that, when employing
fragmentation, you open the door to a number of attack vectors. See
e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.



> The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
> be supported with evidence. I appreciate that such evidence may be
> difficult to observe. In the absence of evidence, the statement should
> be more clear that there is no evidence to the contrary -- which is not
> the same as being able to claim that they *are* in fact rare.

I see your point. Any suggestion on how to tweak the text?

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Aug 28 09:34:59 2016
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7E9F12B03B; Sun, 28 Aug 2016 09:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 B5Fz0rGB0WFT; Sun, 28 Aug 2016 09:34:36 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 77AFE12B018; Sun, 28 Aug 2016 09:34:36 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u7SGXsT9008088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 28 Aug 2016 09:33:56 -0700 (PDT)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu>
Date: Sun, 28 Aug 2016 09:33:54 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/3OcebunBfMcpCIu3q_rajiF7LXc>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Aug 2016 16:34:38 -0000

Hi, Fernando,

First, I'd like to note something more important about this doc - the
abstract itself argues that this change should update the core IPv6
spec. Given that is already well underway, why is this document even
needed?

That said, see below in-line...


On 8/27/2016 3:37 PM, Fernando Gont wrote:
> Hello, Joe,
>
> Thanks so much for your review! -- Please find my responses in-line...
>
> On 08/26/2016 04:29 PM, Joe Touch wrote:
>> Document: draft-ietf-6man-deprecate-atomfrag-generation 
>> Title: Generation of IPv6 Atomic Fragments Considered Harmful
>> Reviewer: J. Touch
>> Review Date: August 26, 2016
>> IETF Last Call Date: August 8, 2016
>>
>> Summary: This draft is on the right track but has open issues, described
>> in the review.
>>
>> The document has no issues directly applicable to transport protocols.
>> The impact on transports is indirect, in the ability of RFC 6145-style
>> IPv6/IPv4 translators to support IPv6-to-IPv4 translation and deal with
>> IPv4-side fragmentation.
>>
>> However, there are some important non-transport issues that are noted below.
>>
>> Major issues:
>>
>> The impact of this change does not appear to have been explored. Section
>> 3 ends with a claim that links where this translation issue would be a
>> problem are rare, but there is no evidence presented as to whether
>> current RFC 6145 translators would be capable of complying with the
>> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
>> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
>> ID generation MUST be supported (and used), rather than MAY.
> RFC 6145 has been revised as RFC7915.
The second sentence of this draft cites 6145. You raise a good point,
but given 7915 obsoletes 6145 (rather than updating it), all references
throughout should then refer to 7915 instead.

> The document concludes that the translator should create IPv4 IDs rather
>> than relying on atomic fragments as a source of that information (as per
>> RFC2460) because there is no benefit, but are two reasons why this
>> method is directly hazardous as well: 1) RFC 2460 does not require that
>> the IPv6 ID field is generated to ensure that the low 16-bits are unique
>> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
>> translation could result in collisions where two distinct IPv6
>> destinations are translated into the same IPv4 address, such that IDs
>> that might have been generated to be unique in the IPv6 context could
>> end up colliding when used in the translated IPv4 context. I.e., this
>> does not require ECMP as implied in Section 3.
> mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
> actually describing the only possible scenario in which relying on the
> ID in the Frag Header could be of use (i.e., possibly result in lower
> collision rates).

I'm not speaking of when the ID in the Frag Header can be useful. I'm
speaking of other more likely cases where using the low 16 bits of the
IPv6 ID field can generate IPv4 collisions.

>
>> Minor issues:
>>
>> IMO, it remains unwise to continue to imply that networks should treat
>> packets with fragment headers as an attack. Fragmentation support is
>> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
>> find ways to support their use safely. The text should be edited to
>> explain that the primary motivation here is to avoid generating
>> erroneous IPv4 ID fields, rather than to react to the incorrect
>> classification of fragment headers as incompatible with the Internet.
> Not sure what you mean.
>
> We're not implying that packets employing FH are an attack. FWIW, I
> don't personally think so. We do think that, when employing
> fragmentation, you open the door to a number of attack vectors. See
> e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.
Some of the attacks described are based on the widespread dropping of a
valid IPv6 packet with valid IPv6 extension headers.

IMO, it is important to be clear that this makes users of a legitimate
IPv6 capability vulnerable because of incorrect behavior of routers. It
seems important to remind readers that the real issue here is the
non-compliant routers. If that information isn't present, it implies
that it is the use of the EHs that is incorrect and should be avoided in
general. That's impossible for fragmentation - it is a critical
capability without which tunneling cannot exist.

>
>> The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
>> be supported with evidence. I appreciate that such evidence may be
>> difficult to observe. In the absence of evidence, the statement should
>> be more clear that there is no evidence to the contrary -- which is not
>> the same as being able to claim that they *are* in fact rare.
> I see your point. Any suggestion on how to tweak the text?

It depends on what you know. AFAICT, we have no information on this
issue. If that's the case, then the text should just state the impact on
such links and say that "there is no evidence yet as to the prevalence
of their use".

Joe


From nobody Mon Aug 29 15:06:05 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F5EA12B047; Mon, 29 Aug 2016 15:06:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 7WHubG7dVizW; Mon, 29 Aug 2016 15:06:00 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA4B712B037; Mon, 29 Aug 2016 15:05:58 -0700 (PDT)
Received: from [192.168.1.154] (mail.interplazahotel.com.ar [201.216.217.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 4933B80145; Tue, 30 Aug 2016 00:05:48 +0200 (CEST)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Joe Touch <touch@isi.edu>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com> <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com>
Date: Mon, 29 Aug 2016 19:05:41 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/fxhYth3pbreM6utMrjjaTIKV4to>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 22:06:02 -0000

On 08/28/2016 01:33 PM, Joe Touch wrote:
> Hi, Fernando,
> 
> First, I'd like to note something more important about this doc - the
> abstract itself argues that this change should update the core IPv6
> spec. Given that is already well underway, why is this document even
> needed?

The document says it clearly: "documenting the
   motivation for removing this functionality in the revision of the
   core IPv6 protocol specification."

You just don't remove a feature from a spec silently, without a
rationale. And the place to include the rationale wasn't rfc2460bis --
hence this dcument.





>>> The impact of this change does not appear to have been explored. Section
>>> 3 ends with a claim that links where this translation issue would be a
>>> problem are rare, but there is no evidence presented as to whether
>>> current RFC 6145 translators would be capable of complying with the
>>> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
>>> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
>>> ID generation MUST be supported (and used), rather than MAY.
>> RFC 6145 has been revised as RFC7915.
> The second sentence of this draft cites 6145. You raise a good point,
> but given 7915 obsoletes 6145 (rather than updating it), all references
> throughout should then refer to 7915 instead.

Not really. We're documenting why this feature is being removed -- hence
there's a place for referencing RFC6145 ("state of affairs before any
updates") and RFC7915.

All references to RFC6145 are of the form "legacy translators", or
"RFC6145 was...".



>> The document concludes that the translator should create IPv4 IDs rather
>>> than relying on atomic fragments as a source of that information (as per
>>> RFC2460) because there is no benefit, but are two reasons why this
>>> method is directly hazardous as well: 1) RFC 2460 does not require that
>>> the IPv6 ID field is generated to ensure that the low 16-bits are unique
>>> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
>>> translation could result in collisions where two distinct IPv6
>>> destinations are translated into the same IPv4 address, such that IDs
>>> that might have been generated to be unique in the IPv6 context could
>>> end up colliding when used in the translated IPv4 context. I.e., this
>>> does not require ECMP as implied in Section 3.
>> mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
>> actually describing the only possible scenario in which relying on the
>> ID in the Frag Header could be of use (i.e., possibly result in lower
>> collision rates).
> 
> I'm not speaking of when the ID in the Frag Header can be useful. I'm
> speaking of other more likely cases where using the low 16 bits of the
> IPv6 ID field can generate IPv4 collisions.

So you argue in favor of adding an extra bullet noting that RFC2460 does
not require the lower 16 bits to be unique? (just double-checking). If
so, fine with me.




>>> Minor issues:
>>>
>>> IMO, it remains unwise to continue to imply that networks should treat
>>> packets with fragment headers as an attack. Fragmentation support is
>>> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
>>> find ways to support their use safely. The text should be edited to
>>> explain that the primary motivation here is to avoid generating
>>> erroneous IPv4 ID fields, rather than to react to the incorrect
>>> classification of fragment headers as incompatible with the Internet.
>> Not sure what you mean.
>>
>> We're not implying that packets employing FH are an attack. FWIW, I
>> don't personally think so. We do think that, when employing
>> fragmentation, you open the door to a number of attack vectors. See
>> e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.
> Some of the attacks described are based on the widespread dropping of a
> valid IPv6 packet with valid IPv6 extension headers.
> 
> IMO, it is important to be clear that this makes users of a legitimate
> IPv6 capability vulnerable because of incorrect behavior of routers. 

1) The attack I referenced is just one possible attack. If you employ
fragmentation, an atacker could just send forged packets meant to cause
collisions of frag IDs such that your packets are dropped -- clearly
employing an extra feature (as in this case), creates an attack vector.

2) The bahavior in routers is a policy. We may not like it. BUt it's a
policy, not incorrect behavior.



> It
> seems important to remind readers that the real issue here is the
> non-compliant routers. If that information isn't present, it implies
> that it is the use of the EHs that is incorrect and should be avoided in
> general. That's impossible for fragmentation - it is a critical
> capability without which tunneling cannot exist.

Fragmentation has been considered harmful for ages. And yes, we're
saying that if you *do not need it*, you shouldn't use it.



>>> The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
>>> be supported with evidence. I appreciate that such evidence may be
>>> difficult to observe. In the absence of evidence, the statement should
>>> be more clear that there is no evidence to the contrary -- which is not
>>> the same as being able to claim that they *are* in fact rare.
>> I see your point. Any suggestion on how to tweak the text?
> 
> It depends on what you know. AFAICT, we have no information on this
> issue. If that's the case, then the text should just state the impact on
> such links and say that "there is no evidence yet as to the prevalence
> of their use".

I'll talk to my co-authors about this one.

Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Aug 29 15:15:24 2016
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B6AC12D8A6; Mon, 29 Aug 2016 15:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 dISJuX9lMAY7; Mon, 29 Aug 2016 15:15:16 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 8D44F12B03A; Mon, 29 Aug 2016 15:15:16 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u7TMEumk029966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 29 Aug 2016 15:14:58 -0700 (PDT)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com> <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu> <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu>
Date: Mon, 29 Aug 2016 15:14:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OeZNoIzbOMqZkFafhkexOqWK11U>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 22:15:18 -0000

Hi, Fernando,


On 8/29/2016 3:05 PM, Fernando Gont wrote:
> On 08/28/2016 01:33 PM, Joe Touch wrote:
>> Hi, Fernando,
>>
>> First, I'd like to note something more important about this doc - the
>> abstract itself argues that this change should update the core IPv6
>> spec. Given that is already well underway, why is this document even
>> needed?
> The document says it clearly: "documenting the
>    motivation for removing this functionality in the revision of the
>    core IPv6 protocol specification."
>
> You just don't remove a feature from a spec silently, without a
> rationale. And the place to include the rationale wasn't rfc2460bis --
> hence this dcument.

I don't agree. RFC2460bis should not need a roadmap to explain all of
the associated changes and their rationales. That should be in 2460bis.

Otherwise, changes need to be made incrementally - that's a lot of extra
load on the IETF and a lot of complexity to figure out why things are
the way the end up.


>
>
>
>
>
>>>> The impact of this change does not appear to have been explored. Section
>>>> 3 ends with a claim that links where this translation issue would be a
>>>> problem are rare, but there is no evidence presented as to whether
>>>> current RFC 6145 translators would be capable of complying with the
>>>> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
>>>> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
>>>> ID generation MUST be supported (and used), rather than MAY.
>>> RFC 6145 has been revised as RFC7915.
>> The second sentence of this draft cites 6145. You raise a good point,
>> but given 7915 obsoletes 6145 (rather than updating it), all references
>> throughout should then refer to 7915 instead.
> Not really. We're documenting why this feature is being removed -- hence
> there's a place for referencing RFC6145 ("state of affairs before any
> updates") and RFC7915.
>
> All references to RFC6145 are of the form "legacy translators", or
> "RFC6145 was...".

I don't think it's useful to refer in this doc to a spec that is already
obsoleted.

This is further reason why it's not useful to issue separate change
docs. It gets confusing as to what you're arguing and why.

>
>>> The document concludes that the translator should create IPv4 IDs rather
>>>> than relying on atomic fragments as a source of that information (as per
>>>> RFC2460) because there is no benefit, but are two reasons why this
>>>> method is directly hazardous as well: 1) RFC 2460 does not require that
>>>> the IPv6 ID field is generated to ensure that the low 16-bits are unique
>>>> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
>>>> translation could result in collisions where two distinct IPv6
>>>> destinations are translated into the same IPv4 address, such that IDs
>>>> that might have been generated to be unique in the IPv6 context could
>>>> end up colliding when used in the translated IPv4 context. I.e., this
>>>> does not require ECMP as implied in Section 3.
>>> mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
>>> actually describing the only possible scenario in which relying on the
>>> ID in the Frag Header could be of use (i.e., possibly result in lower
>>> collision rates).
>> I'm not speaking of when the ID in the Frag Header can be useful. I'm
>> speaking of other more likely cases where using the low 16 bits of the
>> IPv6 ID field can generate IPv4 collisions.
> So you argue in favor of adding an extra bullet noting that RFC2460 does
> not require the lower 16 bits to be unique? (just double-checking). If
> so, fine with me.

Yes - specifically, 2460 does not require that the lower 16 bits of the
ID are generated in a way that would comply with the expectations of
using just those bits for IPv4.

>
>>>> Minor issues:
>>>>
>>>> IMO, it remains unwise to continue to imply that networks should treat
>>>> packets with fragment headers as an attack. Fragmentation support is
>>>> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
>>>> find ways to support their use safely. The text should be edited to
>>>> explain that the primary motivation here is to avoid generating
>>>> erroneous IPv4 ID fields, rather than to react to the incorrect
>>>> classification of fragment headers as incompatible with the Internet.
>>> Not sure what you mean.
>>>
>>> We're not implying that packets employing FH are an attack. FWIW, I
>>> don't personally think so. We do think that, when employing
>>> fragmentation, you open the door to a number of attack vectors. See
>>> e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.
>> Some of the attacks described are based on the widespread dropping of a
>> valid IPv6 packet with valid IPv6 extension headers.
>>
>> IMO, it is important to be clear that this makes users of a legitimate
>> IPv6 capability vulnerable because of incorrect behavior of routers. 
> 1) The attack I referenced is just one possible attack. If you employ
> fragmentation, an atacker could just send forged packets meant to cause
> collisions of frag IDs such that your packets are dropped -- clearly
> employing an extra feature (as in this case), creates an attack vector.
There are many possible attacks but you focus on the one where routers
drop packets because they have frag EHs.

> 2) The bahavior in routers is a policy. We may not like it. BUt it's a
> policy, not incorrect behavior.
EHs are not optional in RFC2460. Dropping because you see them is not
policy - it forces the router to fail to support a required feature of IPv6.


>
>> It
>> seems important to remind readers that the real issue here is the
>> non-compliant routers. If that information isn't present, it implies
>> that it is the use of the EHs that is incorrect and should be avoided in
>> general. That's impossible for fragmentation - it is a critical
>> capability without which tunneling cannot exist.
> Fragmentation has been considered harmful for ages.

And is finally being understood as fundamentally necessary for tunneling.

>  And yes, we're
> saying that if you *do not need it*, you shouldn't use it.
Yes, if you don't need tunnels, you shouldn't use them either, but that
doesn't mean tunnels shouldn't be used in general.


>
>>>> The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
>>>> be supported with evidence. I appreciate that such evidence may be
>>>> difficult to observe. In the absence of evidence, the statement should
>>>> be more clear that there is no evidence to the contrary -- which is not
>>>> the same as being able to claim that they *are* in fact rare.
>>> I see your point. Any suggestion on how to tweak the text?
>> It depends on what you know. AFAICT, we have no information on this
>> issue. If that's the case, then the text should just state the impact on
>> such links and say that "there is no evidence yet as to the prevalence
>> of their use".
> I'll talk to my co-authors about this one.

AOK.

Thanks,
Joe


From nobody Mon Aug 29 15:50:31 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8425612D8A9; Mon, 29 Aug 2016 15:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qvOAlG_4IjEG; Mon, 29 Aug 2016 15:50:27 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (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 BA0A712D8B8; Mon, 29 Aug 2016 15:50:03 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id ci2so631047pad.3; Mon, 29 Aug 2016 15:50:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4XL/4jlpxG2X/R/Md+DcVakCDkXRbeCip9Rze/t3mZQ=; b=o8WfhuKeiv44AnIlpiqf+0KQJHbr/f7nU8L90RZSXUMg3h9WoqDy9NDRAtBQr9rm5d CibklMLsANTGvCWOdM054M8WnyAf3jQbjOgqWTXixQTfxCN7buu8gzbammpfVOhsyHPc Yr9wZFgJdPH8RbxCUtf+teoxRQMzus4Zeg/njl6qwTYGR1kd9/miIEurD4wCLWrtdPgT GfopviiqB+I0SexnjNwXJF3d/vhvAOzgkaAdNKcf0v+1SAj6Air2HX7RI9Yu4boI2Goq XCKq+Cs32plInXqllFcDWf+LtRLg3q/FPNiyUyACR0pHVwlnw5aXVIqacvvx42gdb6p6 jYVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=4XL/4jlpxG2X/R/Md+DcVakCDkXRbeCip9Rze/t3mZQ=; b=ZVpq4ag38/Hwu5TZn8tyeZY9UBgLzPTFVDMTWMgzgAZWrfgjz8fIeR1csHzMjUli7U +7+I4Py/NaoXZcBTSGd9knfOiH2vTXaqo4Z9xOn2GYEq2kVkSrwIWf+2sXb8H2cvilfL odXqi/Dprp98T/S/xEHzN4KfzJ5dDfw5tdZuVBAvABGA7NT5ISXw56Jo9VantsXd8aEl QoRIQbrzIFsqHOSYN/iEGSDoBNsoXn+Qf4LrwAa1HgNpcZFWpAbt2+yCi7R614iEml6J kgF9egt1CtmWiBIeGYGSSILW6A+2GYIieYls209iUyExVsbpgFF8SGA33DRJ5Jj5xpuj x1YA==
X-Gm-Message-State: AE9vXwN+TGOsykNewTbrQwR3laRuIIIaOPVLsR4HFo783pEZCT0c7EwiuGypUNXuCmADig==
X-Received: by 10.67.7.170 with SMTP id dd10mr718783pad.152.1472511003053; Mon, 29 Aug 2016 15:50:03 -0700 (PDT)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id n10sm51712132pap.16.2016.08.29.15.49.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Aug 2016 15:50:02 -0700 (PDT)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Joe Touch <touch@isi.edu>, Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com> <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu> <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com> <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ac5d10f5-9667-e446-46f3-4bbfaf5e7d18@gmail.com>
Date: Tue, 30 Aug 2016 10:50:01 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/1zLZ6_KR6bFPUPmmpKjg1m1_Yjo>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, Transport Area <tsv-area@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 22:50:30 -0000

On 30/08/2016 10:14, Joe Touch wrote:
> Hi, Fernando,
> 
> 
> On 8/29/2016 3:05 PM, Fernando Gont wrote:
>> On 08/28/2016 01:33 PM, Joe Touch wrote:
>>> Hi, Fernando,
>>>
>>> First, I'd like to note something more important about this doc - the
>>> abstract itself argues that this change should update the core IPv6
>>> spec. Given that is already well underway, why is this document even
>>> needed?
>> The document says it clearly: "documenting the
>>    motivation for removing this functionality in the revision of the
>>    core IPv6 protocol specification."
>>
>> You just don't remove a feature from a spec silently, without a
>> rationale. And the place to include the rationale wasn't rfc2460bis --
>> hence this dcument.
> 
> I don't agree. RFC2460bis should not need a roadmap to explain all of
> the associated changes and their rationales. That should be in 2460bis.

2460bis has pointers in such cases (and should include a pointer
to deprecate-atomfrag when it becomes an RFC). I don't think it is
helpful to readers of 2460bis to burden it with all the rationales.

> Otherwise, changes need to be made incrementally - that's a lot of extra
> load on the IETF and a lot of complexity to figure out why things are
> the way the end up.

I don't think 2460bis will be the end of history, any more than 791 was
the end of IPv4 history. Incremental change will continue.

Regards
     Brian

> 
> 
>>
>>
>>
>>
>>
>>>>> The impact of this change does not appear to have been explored. Section
>>>>> 3 ends with a claim that links where this translation issue would be a
>>>>> problem are rare, but there is no evidence presented as to whether
>>>>> current RFC 6145 translators would be capable of complying with the
>>>>> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
>>>>> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
>>>>> ID generation MUST be supported (and used), rather than MAY.
>>>> RFC 6145 has been revised as RFC7915.
>>> The second sentence of this draft cites 6145. You raise a good point,
>>> but given 7915 obsoletes 6145 (rather than updating it), all references
>>> throughout should then refer to 7915 instead.
>> Not really. We're documenting why this feature is being removed -- hence
>> there's a place for referencing RFC6145 ("state of affairs before any
>> updates") and RFC7915.
>>
>> All references to RFC6145 are of the form "legacy translators", or
>> "RFC6145 was...".
> 
> I don't think it's useful to refer in this doc to a spec that is already
> obsoleted.
> 
> This is further reason why it's not useful to issue separate change
> docs. It gets confusing as to what you're arguing and why.
> 
>>
>>>> The document concludes that the translator should create IPv4 IDs rather
>>>>> than relying on atomic fragments as a source of that information (as per
>>>>> RFC2460) because there is no benefit, but are two reasons why this
>>>>> method is directly hazardous as well: 1) RFC 2460 does not require that
>>>>> the IPv6 ID field is generated to ensure that the low 16-bits are unique
>>>>> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
>>>>> translation could result in collisions where two distinct IPv6
>>>>> destinations are translated into the same IPv4 address, such that IDs
>>>>> that might have been generated to be unique in the IPv6 context could
>>>>> end up colliding when used in the translated IPv4 context. I.e., this
>>>>> does not require ECMP as implied in Section 3.
>>>> mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
>>>> actually describing the only possible scenario in which relying on the
>>>> ID in the Frag Header could be of use (i.e., possibly result in lower
>>>> collision rates).
>>> I'm not speaking of when the ID in the Frag Header can be useful. I'm
>>> speaking of other more likely cases where using the low 16 bits of the
>>> IPv6 ID field can generate IPv4 collisions.
>> So you argue in favor of adding an extra bullet noting that RFC2460 does
>> not require the lower 16 bits to be unique? (just double-checking). If
>> so, fine with me.
> 
> Yes - specifically, 2460 does not require that the lower 16 bits of the
> ID are generated in a way that would comply with the expectations of
> using just those bits for IPv4.
> 
>>
>>>>> Minor issues:
>>>>>
>>>>> IMO, it remains unwise to continue to imply that networks should treat
>>>>> packets with fragment headers as an attack. Fragmentation support is
>>>>> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
>>>>> find ways to support their use safely. The text should be edited to
>>>>> explain that the primary motivation here is to avoid generating
>>>>> erroneous IPv4 ID fields, rather than to react to the incorrect
>>>>> classification of fragment headers as incompatible with the Internet.
>>>> Not sure what you mean.
>>>>
>>>> We're not implying that packets employing FH are an attack. FWIW, I
>>>> don't personally think so. We do think that, when employing
>>>> fragmentation, you open the door to a number of attack vectors. See
>>>> e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.
>>> Some of the attacks described are based on the widespread dropping of a
>>> valid IPv6 packet with valid IPv6 extension headers.
>>>
>>> IMO, it is important to be clear that this makes users of a legitimate
>>> IPv6 capability vulnerable because of incorrect behavior of routers. 
>> 1) The attack I referenced is just one possible attack. If you employ
>> fragmentation, an atacker could just send forged packets meant to cause
>> collisions of frag IDs such that your packets are dropped -- clearly
>> employing an extra feature (as in this case), creates an attack vector.
> There are many possible attacks but you focus on the one where routers
> drop packets because they have frag EHs.
> 
>> 2) The bahavior in routers is a policy. We may not like it. BUt it's a
>> policy, not incorrect behavior.
> EHs are not optional in RFC2460. Dropping because you see them is not
> policy - it forces the router to fail to support a required feature of IPv6.
> 
> 
>>
>>> It
>>> seems important to remind readers that the real issue here is the
>>> non-compliant routers. If that information isn't present, it implies
>>> that it is the use of the EHs that is incorrect and should be avoided in
>>> general. That's impossible for fragmentation - it is a critical
>>> capability without which tunneling cannot exist.
>> Fragmentation has been considered harmful for ages.
> 
> And is finally being understood as fundamentally necessary for tunneling.
> 
>>  And yes, we're
>> saying that if you *do not need it*, you shouldn't use it.
> Yes, if you don't need tunnels, you shouldn't use them either, but that
> doesn't mean tunnels shouldn't be used in general.
> 
> 
>>
>>>>> The claim that links with IPv6 MTUs smaller than 1260 are rare needs to
>>>>> be supported with evidence. I appreciate that such evidence may be
>>>>> difficult to observe. In the absence of evidence, the statement should
>>>>> be more clear that there is no evidence to the contrary -- which is not
>>>>> the same as being able to claim that they *are* in fact rare.
>>>> I see your point. Any suggestion on how to tweak the text?
>>> It depends on what you know. AFAICT, we have no information on this
>>> issue. If that's the case, then the text should just state the impact on
>>> such links and say that "there is no evidence yet as to the prevalence
>>> of their use".
>> I'll talk to my co-authors about this one.
> 
> AOK.
> 
> Thanks,
> Joe
> 
> 


From nobody Mon Aug 29 15:52:44 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7A112D8A3; Mon, 29 Aug 2016 15:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 0_Xv4lwxSDJR; Mon, 29 Aug 2016 15:52:13 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C29312D7A4; Mon, 29 Aug 2016 15:52:13 -0700 (PDT)
Received: from [192.168.1.154] (mail.interplazahotel.com.ar [201.216.217.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 6878980ECC; Tue, 30 Aug 2016 00:52:09 +0200 (CEST)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Joe Touch <touch@isi.edu>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com> <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu> <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com> <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <d4615e72-0d19-256c-1830-b2c80dc53d2d@si6networks.com>
Date: Mon, 29 Aug 2016 19:51:24 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FQ8FM2CgeLZm_EXLjWdrm2e5neE>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 22:52:16 -0000

Hi, Joe,

On 08/29/2016 07:14 PM, Joe Touch wrote:
> 
> On 8/29/2016 3:05 PM, Fernando Gont wrote:
>> On 08/28/2016 01:33 PM, Joe Touch wrote:
>>> Hi, Fernando,
>>>
>>> First, I'd like to note something more important about this doc - the
>>> abstract itself argues that this change should update the core IPv6
>>> spec. Given that is already well underway, why is this document even
>>> needed?
>> The document says it clearly: "documenting the
>>    motivation for removing this functionality in the revision of the
>>    core IPv6 protocol specification."
>>
>> You just don't remove a feature from a spec silently, without a
>> rationale. And the place to include the rationale wasn't rfc2460bis --
>> hence this dcument.
> 
> I don't agree. RFC2460bis should not need a roadmap to explain all of
> the associated changes and their rationales. That should be in 2460bis.

I don't think RFC2460bis is the place to add six pages about this. All
other changes are similarly discussed in the respective updating
documents. RFC7915 also references this doc for the rationale for
deviating from the behavior in RFC6145.



>>>>> The impact of this change does not appear to have been explored. Section
>>>>> 3 ends with a claim that links where this translation issue would be a
>>>>> problem are rare, but there is no evidence presented as to whether
>>>>> current RFC 6145 translators would be capable of complying with the
>>>>> changes in this doc, e.g., to be able to generate IPv4 IDs as needed.
>>>>> I.e., this document needs to update RFC6145 Sec 5.1 to require that IPv4
>>>>> ID generation MUST be supported (and used), rather than MAY.
>>>> RFC 6145 has been revised as RFC7915.
>>> The second sentence of this draft cites 6145. You raise a good point,
>>> but given 7915 obsoletes 6145 (rather than updating it), all references
>>> throughout should then refer to 7915 instead.
>> Not really. We're documenting why this feature is being removed -- hence
>> there's a place for referencing RFC6145 ("state of affairs before any
>> updates") and RFC7915.
>>
>> All references to RFC6145 are of the form "legacy translators", or
>> "RFC6145 was...".
> 
> I don't think it's useful to refer in this doc to a spec that is already
> obsoleted.
> 
> This is further reason why it's not useful to issue separate change
> docs. It gets confusing as to what you're arguing and why.

We just disagree here. This document explains why RFC7915 does not rely
on atomic fragments anymore, and why the corresponding functionality is
being removed from the spec. I don't see any complexity here.



>>>> The document concludes that the translator should create IPv4 IDs rather
>>>>> than relying on atomic fragments as a source of that information (as per
>>>>> RFC2460) because there is no benefit, but are two reasons why this
>>>>> method is directly hazardous as well: 1) RFC 2460 does not require that
>>>>> the IPv6 ID field is generated to ensure that the low 16-bits are unique
>>>>> as required for use as IPv4 IDs as defined in RFC 6145, and 2) RFC 6145
>>>>> translation could result in collisions where two distinct IPv6
>>>>> destinations are translated into the same IPv4 address, such that IDs
>>>>> that might have been generated to be unique in the IPv6 context could
>>>>> end up colliding when used in the translated IPv4 context. I.e., this
>>>>> does not require ECMP as implied in Section 3.
>>>> mmm.. not sure I follow. When we refer to ECMP in Section 3 we're
>>>> actually describing the only possible scenario in which relying on the
>>>> ID in the Frag Header could be of use (i.e., possibly result in lower
>>>> collision rates).
>>> I'm not speaking of when the ID in the Frag Header can be useful. I'm
>>> speaking of other more likely cases where using the low 16 bits of the
>>> IPv6 ID field can generate IPv4 collisions.
>> So you argue in favor of adding an extra bullet noting that RFC2460 does
>> not require the lower 16 bits to be unique? (just double-checking). If
>> so, fine with me.
> 
> Yes - specifically, 2460 does not require that the lower 16 bits of the
> ID are generated in a way that would comply with the expectations of
> using just those bits for IPv4.

Agreed. Will do.



>>>>> Minor issues:
>>>>>
>>>>> IMO, it remains unwise to continue to imply that networks should treat
>>>>> packets with fragment headers as an attack. Fragmentation support is
>>>>> critical to tunneling (see draft-ietf-intarea-tunnels) and we need to
>>>>> find ways to support their use safely. The text should be edited to
>>>>> explain that the primary motivation here is to avoid generating
>>>>> erroneous IPv4 ID fields, rather than to react to the incorrect
>>>>> classification of fragment headers as incompatible with the Internet.
>>>> Not sure what you mean.
>>>>
>>>> We're not implying that packets employing FH are an attack. FWIW, I
>>>> don't personally think so. We do think that, when employing
>>>> fragmentation, you open the door to a number of attack vectors. See
>>>> e.g., Section 5 of draft-gont-v6ops-ipv6-ehs-packet-drops-03.txt.
>>> Some of the attacks described are based on the widespread dropping of a
>>> valid IPv6 packet with valid IPv6 extension headers.
>>>
>>> IMO, it is important to be clear that this makes users of a legitimate
>>> IPv6 capability vulnerable because of incorrect behavior of routers. 
>> 1) The attack I referenced is just one possible attack. If you employ
>> fragmentation, an atacker could just send forged packets meant to cause
>> collisions of frag IDs such that your packets are dropped -- clearly
>> employing an extra feature (as in this case), creates an attack vector.
> There are many possible attacks but you focus on the one where routers
> drop packets because they have frag EHs.
> 
>> 2) The bahavior in routers is a policy. We may not like it. BUt it's a
>> policy, not incorrect behavior.
> EHs are not optional in RFC2460. Dropping because you see them is not
> policy - it forces the router to fail to support a required feature of IPv6.

The same you could say about a device dropping packets because they are
destined (or are not destined to) a specific port.

The router does support EHs. The network just has a policy that don't
want them.

In any case, there' no need to argue a lot on this specific attack
vector since, as noted, there are others.



>>> It
>>> seems important to remind readers that the real issue here is the
>>> non-compliant routers. If that information isn't present, it implies
>>> that it is the use of the EHs that is incorrect and should be avoided in
>>> general. That's impossible for fragmentation - it is a critical
>>> capability without which tunneling cannot exist.
>> Fragmentation has been considered harmful for ages.
> 
> And is finally being understood as fundamentally necessary for tunneling.

And is necessary for UDP, too. Nobody is arguing against that. But the
case in which we were producing atomic fragments wasn't a case in which
you were really needed fragmentation: you were just using the FH as a
signaling mechanism.   -- for instance, an atomic fragment, hasn't
really fragmented anything.



>>  And yes, we're
>> saying that if you *do not need it*, you shouldn't use it.
> Yes, if you don't need tunnels, you shouldn't use them either, but that
> doesn't mean tunnels shouldn't be used in general.

Where in the texxt do we say "you shouldn't use fragmentation in general"?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Aug 29 15:57:13 2016
Return-Path: <touch@isi.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06699126FDC; Mon, 29 Aug 2016 15:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548] autolearn=ham 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 Q2PpL-pLWFsL; Mon, 29 Aug 2016 15:57:03 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 4192B12B030; Mon, 29 Aug 2016 15:57:02 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u7TMuMRd007908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 29 Aug 2016 15:56:24 -0700 (PDT)
Subject: Re: TSVART review of draft-ietf-6man-deprecate-atomfrag-generation
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
References: <786d5c2c-a88d-7539-9604-6df0b8ed68dd@isi.edu> <0f339ba8-cf63-e961-b19f-895c39585fb7@si6networks.com> <585f4689-d19e-dd54-e75b-4eb3644274ed@isi.edu> <a40199a0-b625-3887-aec6-7e3adfbe504a@si6networks.com> <6755d8bb-3b95-c107-cd72-b799cb2b32f1@isi.edu> <d4615e72-0d19-256c-1830-b2c80dc53d2d@si6networks.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <e5949dc8-870a-36fd-8224-0c8cfabd1c8e@isi.edu>
Date: Mon, 29 Aug 2016 15:56:22 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <d4615e72-0d19-256c-1830-b2c80dc53d2d@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/PeZi6i5E95ng-JF6XS9o9KsniG4>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Transport Area <tsv-area@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 22:57:04 -0000

On 8/29/2016 3:51 PM, Fernando Gont wrote:
> Where in the texxt do we say "you shouldn't use fragmentation in general"?

It's the implication that follows from justifying this change based on
whether frag EHs are dropped.

IMO, that's simply irrelevant. The broader problem is using
IPv6-generated IDs, which are not generated to be compliant in their
bottom 16 bits with IPv4.

That alone is more than sufficient rationale for not using this mechanism.

Joe


From nobody Tue Aug 30 13:20:03 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F6D12D813 for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 13:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4a-8gOQDisP6 for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 13:19:59 -0700 (PDT)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (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 2EAF812D7F6 for <6man@ietf.org>; Tue, 30 Aug 2016 13:19:59 -0700 (PDT)
Received: by mail-oi0-x234.google.com with SMTP id f189so42359364oig.3 for <6man@ietf.org>; Tue, 30 Aug 2016 13:19:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=Q6M9kZqdHFRfWoAVTRp6WejVT8Tatn39XSum4RmmkGI=; b=VTg1qYUEgLEoXnv818ZLBa3EMtcV4SjYT5UjAERtlq+i9pfe/4Z6T20UK5ADyQ2kxi Y0GJc6WdfKP6i0YMMIpzD/LjweS8Hl2wwzmZ7gV35opnstV3HofgHDi/I6gucH1IleNg uiHmqogDjms057SrX/2lnyJh7DpMaFsqqJySwNDWDGH4M8J662bExp2cO9FH1zIqRQSQ FZOAckBMLm7kzHj/fAt9KlOodU4Bws1B2hFYYSIVE5PMObfOOQVKAiLCyLyrOuc0uY7y pPfHchnxpPmMHMMOxNNtOKgFSpNmlOgdh23nw5LIk94VeINgNYJH+eauT42GEDsjOcn1 S8Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=Q6M9kZqdHFRfWoAVTRp6WejVT8Tatn39XSum4RmmkGI=; b=BDMysVcLEmiwxWNn01N0usCJWScJiqurjUYDyWTVTlB28gKvnmlqqk3rg+z2A0Oao+ owwbNy1M6W1DB3gnbuFyDHjK/8P3FjNZXv8xm/EWkgU9swxs4FDSvZrVJwkEbnua+/QC zzwqH1CgXe37No/vZedIwC511P2DXl+5oRxTPPhtH/GrXsEda/KlAnS/6eqBz5nnBvTq boUWa0MVD6XRf3rrum6BEnirYKuBf5F6mo0M1sFzJXJdW/k1p3SbYf7lkTwwNpGiuNTI 2nTRup2xJL3cfHV6J+dEIFItNmsr21cE/f2m1ZttqviAkMbrXgSPjcKFUijuLbYff5va mPAA==
X-Gm-Message-State: AE9vXwPnRLY2oi+yTNMFDD+cwtgb2HZj3Rpszqf+OVerOKSmxa+Yi1deAH300d6gJkbROQ==
X-Received: by 10.157.1.105 with SMTP id 96mr6053347otu.143.1472588398285; Tue, 30 Aug 2016 13:19:58 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id h31sm2126782ote.26.2016.08.30.13.19.56 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 30 Aug 2016 13:19:56 -0700 (PDT)
Subject: Re: Review of draft-ietf-6man-rfc2460bis-05
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_581E1034-7A14-4F4F-9256-75D29089EA06"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk>
Date: Tue, 30 Aug 2016 13:19:53 -0700
Message-Id: <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com>
References: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk>
To: Tim Chown <Tim.Chown@jisc.ac.uk>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Drhg84vyXOC0gi8fdkEPPSAFjhs>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 20:20:02 -0000

--Apple-Mail=_581E1034-7A14-4F4F-9256-75D29089EA06
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Tim,

Thanks for the detailed review.  Comments below.

Bob

> On Jul 18, 2016, at 12:08 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>=20
> Hi,
>=20
> Ole asked me to review draft-ietf-6man-rfc2460bis-05.
>=20
> Generally, the document looks to be in good shape. Personally, I agree =
with the changes made. It looks close to being ready for the four week =
IETF Last Call, as per RFC6410.  The four key criteria for promotion to =
IS as listed in RFC6410 seem to have been met (widespread deployment =
with successful operational experience, errata addressed, no unused =
features that would greatly increase implementation complexity, and not =
IPR encumbered).
>=20
> Where changes to RFC2460 have been made with respect to RFCs published =
since the original publication of RFC2460, there is some inconsistency =
as to whether those RFCs are explicitly cited, or their =E2=80=98message=E2=
=80=99 just incorporated as an update.  Some consistency would be =
desirable; specific occurrences are listed below.
>=20
> The comments below are largely clarification in nature.
>=20
> Comments:
>=20
> Section 1:
>=20
> p.3 on the scope field for multicast addresses there could now be a =
reference to RFC7346.

This is introductory text describing the differences from IPv4, I =
don=E2=80=99t think a reference is needed here.  Multicast addresses are =
defined in RFC2491 (and bis).

>=20
> p.3 the EH text should probably no longer mention =E2=80=9Cgreater =
flexibility for introducing new options in the future=E2=80=9D. In 1998 =
yes, but not now, with the benefit of hindsight. Later sections discuss =
this in more detail.

This text is describing the differences from IPv4, and I think it =
continues to be true.

>=20
> p.3 in the flow label text, delete =E2=80=98for=E2=80=99.

I agree, but I think s/for which/that/ is better.

>=20
> Section 3:
>=20
> p.6 the Destination Address destination talks of the Routing Header, =
but this has now been removed from the list of EHs required for a =
=E2=80=98full implementation=E2=80=99 EHs on p.8. (see more on this =
below).

I agree the the Routing Header should not have been removed from the =
list of required EHs.  I will add it back in, but not be specific about =
which type of RH, that is defined in the IANA table as noted in Section =
4.4

>=20
> Section 4:
>=20
> p.6 there is now more than a =E2=80=9Csmall number=E2=80=9D of EHs =
defined.

Small is a relative term.

> This document only defines / discusses a small number explicitly, but =
a fuller list is included in RFC7045. I think it=E2=80=99s fine that we =
should keep 2460 just referring to the =E2=80=98core=E2=80=99 headers =
(the ones required for a 'full implementation=E2=80=99 on p.8), but =
there may be an argument to refer to RFC7045 as a pointer to the new =
=E2=80=9CIPv6 Extension Header Types=E2=80=9D list maintained by IANA. =
Or maybe that pointer should be in Section 9?

There is a pointer at the end of Section 4.  I think this is adequate.

>=20
> p.7 do we need to be clearer in the meaning of =E2=80=9Cprocessed=E2=80=9D=
 here? Is =E2=80=9Cexamining=E2=80=9D a form of =E2=80=9Cprocessing=E2=80=9D=
.  It might read better if the RFC7045 Note was placed after the =
paragraph on p.8 that states the Hoby-by-Hop exception.

Let=E2=80=99s defer this to a separate thread on the general topic of =
header insertion.  It will be in a separate email.

>=20
> p.7 note that firewalls would be an example of nodes that might =
process EHs beyond the HbH header. Do we need to be clear that 2460 =
talks of normal processing, not processing for security reasons =
(firewall, IDS, =E2=80=A6)?

I don=E2=80=99t think so, this text is based on RFC7045.

>=20
> p.8 in the =E2=80=9CIf, as a result=E2=80=A6=E2=80=9D paragraph, is =
the text now contradictory to RFC7045, which says "If a forwarding node =
discards a packet containing a standard IPv6 extension header, it MUST =
be the result of a configurable policy and not just the result of a =
failure to recognise such a header.=E2=80=9D? The 2460-bis text implies =
a discard, while 7045 implies that shouldn=E2=80=99t happen unless as a =
result of configured policy?

A node that is required by RFC2460bis to process a header must discard =
it if it encounters an unrecognized next header value. RFC7045 defines =
additional reasons why packet might be discarded.

> p.8 should we be removing the Routing header from the list here? Yes, =
RH0 is deprecated, but I understand that SPRING is using the RH, and =
there are also the Type 2 and Type 3 RHs defined in RFC6275 (Mobility =
use) and RFC 6554 (RPL use).

No, as described above.

>=20
> p.9 the text saying =E2=80=9Cin any order=E2=80=9D might be less =
ambiguous if stated as =E2=80=9Cappearing in any order=E2=80=9D (i.e. =
emphasise the EHs are processed sequentially, no matter what order they =
are in, rather than the node processing the EHs in any order).
>=20

I don=E2=80=99t see any problem with the current text.


> p.14 in the =E2=80=9CIf, after processing=E2=80=A6=E2=80=9D paragraph, =
isn=E2=80=99t this true regardless of alterations to the RH?  Is this =
superfluous?

It is saying that if the packet is too big for the next link, it must be =
discarded and a PTB be sent.  I think this should continue to be said =
here, since it is forwarding a packet that was destined for yourself, =
and it might be misunderstood that the node could fragment at this =
point.

>=20
> p.15 the (*) note for =E2=80=9Crecently=E2=80=9D looks a bit ugly. =
Just make it normal text?

I have been trying to avoid making unnecessary changes to the original =
text.

>=20
> p.16 A note about RFC7112 would be best placed after the =E2=80=9CThe =
Fragmentable Part=E2=80=9D paragraph. As it stands, the RFC7112 =
principle (all EHs in the first frag) isn=E2=80=99t mentioned until =
further into the document, on p.17 item (3), and even then 7112 isn=E2=80=99=
t cited.  A note about not creating overlapping fragments could also be =
inserted here, as per RFC5722.

This was a case where I incorporated the ideas of the update and kept =
the terminology as close as possible as the original.  There were =
several updates that had to be incorporated.

I continue to think it reads OK.  The text you mention is on the next =
page.  A subtle change here is that this text doesn=E2=80=99t allow =
overlapping fragments to be created, unlike the origional, as the text =
separates the rules for the first and subsequent fragments.  The =
non-overlaping text is later because it should only happen if sent by a =
non-conforming or malicious sender.

>=20
> p.16 should we mention here that ND messages should not be fragmented, =
as per RFC6980, section 6?

No, RFC6980 doesn=E2=80=99t update RFC2460.  There is no other mention =
of ND in this document.

>=20
> p.17 this diagram emphasises the model that RFC7112 requires, with the =
EHs in the first frag.  Maybe note that in the text.

It is discussed in the text that follows the diagram.

>=20
> p.18 the =E2=80=9CFragments must not be created=E2=80=A6=E2=80=9D line =
is a duplication of the last paragraph on p.19.  Move that larger para =
forward?   Also perhaps note the requirement to slinky discard, as per =
RFC5722?

One is about performing fragmentation, the second is about reassembly.  =
It needs to say it in both places.

=E2=80=9Cslinky=E2=80=9D ?  Did you mean silently?  If so, the text at =
the bottom of page 19 says to discard (and doesn=E2=80=99t say to send =
an ICMP).

>=20
> p.20 paragraph 2 should refer to RFC6946 on handling of atomic =
fragments?

No, his was part of incorporating several updates.  I think this is =
clear.

>=20
> p.20 I suggest numbering the four listed error conditions, for =
clarity.

Perhaps, but not sure it would clarify anything.

>=20
> p.20 is the 60 second rule commonly implemented? This seems a very =
high value, and could contribute to DoS effectiveness?

It sets an upper bound, that is =E2=80=9Cwithin 60 seconds=E2=80=9D.  It =
does not say all fragments must be held for 60 seconds.

>=20
> p.20 the fourth condition could cite RFC7112

See above.

>=20
> p.20 add a fifth error condition of overlapping fragments, as per =
RFC5722?

I think that makes sense, I will add.  I need to think if the text on =
page 19 should then be removed.

>=20
> p.21 para 2, is it common that such headers may differ?  The =
implication of p.17 point (1) is that they=E2=80=99d be the same?
>=20

The text at the end of page 20 says:

  The following conditions are not expected to occur

So it is not expected to be common and they are usually the same.


> p.22 is Next Header value 59 used in practice? (Just curious=E2=80=A6 =
it was omitted from RFC7045).

I am not 100% sure, but think it is used.  But it is not something that =
has been updated.

>=20
> p.22 in section 4.8, cite RFC6564, which appears to be the format used =
in the latter part of that section.

It is the same format, and is noted in Appendix B.

>=20
> p.23 =E2=80=9CDefining new=E2=80=A6=E2=80=9D sentence duplicates the =
start of the paragraph?

I will look at rewriting this paragraph to make it clearer.

>=20
> Section 5:
>=20
> p.24 Do we add a note here about PLPMTUD, or just leave that to =
RFC1981-bis? I would probably say the latter.
>=20

Me too.


> p.24 how strong is =E2=80=9Cdiscouraged=E2=80=9D?  I remember well =
draft-bonica-6man-frag-deprecate-02 ;)

I also remember the discussion about deprecating IPv6 fragments, but =
think =E2=80=9Cdiscouraged=E2=80=9D is fine.

>=20
> Section 8:
>=20
> p.26 add a reference to RFC6935 with respect to tunnels and UDP =
checksums?

The RFC2460bis documents brings in the replacement text from RFC6935 =
(this updating document was very clear as to the change), so I think =
only RFC6936 needs to be referenced and this was part of the replacement =
text (from RFC6935).

>=20
> p.26 is the text in 8.2 consistent with the text on page 6 about the =
Hop Limit?

I don=E2=80=99t see any inconsistency.  This text discusses the =
differences between IPv6 and IPv4.

>=20
> p.27 is the text in 8.4 consistent with Type 2 and Type 3 RH use? (I =
don=E2=80=99t follow RPL in enough detail=E2=80=A6)

As far as I know, it is consistent.



>=20
> Best wishes,
> Tim
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_581E1034-7A14-4F4F-9256-75D29089EA06
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJXxepqAAoJEK7rdBF357uoGdcH/Avn0Z34uM1AUE9q2MPiiRKp
fs5l1nMVVw5g04Eo9HgnegaSmTf/Z67w7CsX+3PpcfIoBz9HETm2P1gSwOkFtzl8
HiD+wQGvdnkKAeDedtQFhmetAorovOQQ+Dwt9u9JybUdMs+lVdrutX9/AF0JoHub
cVSapat9W1I4vWCRJ/zlrn2axVp5WBLdst6aYVZzmVpxTL6zwvuLMdbinYBeRAwV
ucl6axqcDaG+xYk2fEPEI1vq37qx+vpxmg9GOnqfIidZJfqVaQHzIzLDZN8uTYQi
580bUWh2G0MejacuOu7O2w36wiT1B66PYZGU6SNo6q3eIlO8QiviyjXTyHUC7rE=
=LWpY
-----END PGP SIGNATURE-----

--Apple-Mail=_581E1034-7A14-4F4F-9256-75D29089EA06--


From nobody Tue Aug 30 13:39:55 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5D312D827 for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 13:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 d63WgctdbDe6 for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 13:39:52 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 4F14D12D824 for <6man@ietf.org>; Tue, 30 Aug 2016 13:39:52 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id y134so11332971pfg.0 for <6man@ietf.org>; Tue, 30 Aug 2016 13:39:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=LbjaDTcCUyKNm6FCgLYkHP3l7rAfVOYP4pn9L2EloHc=; b=Bglv3pWUhKYli0Bzb82ShdyKcyjfHldENAuI0jP+lw4C0D9rDU5mGPX8PJzlZJZqcC JdqXTCSYDegnY0MCG6jq48EOIxMM9PYqWaTnXj0M6XVT80dTZgIZywhqD3Z6Eo1VAqYp DeY4QItA5QeZz6t0AAzjbnlGdW1RbfPPdsfhVtciwJhba8q2k7wDxAWteNBm15Vv/uGp T7EtBIuoXEhXYwcwZf450+H2sqBqQX0H2Sm9RMLGf3wc59xUQQ8dwEm+fsIknQQs2lXy m3OJw7QIzaBVPR3XW6vZxJRO3he2Mi5PAxY1ul2wDfmtGCJ0EuI07RgoM8jjjaBSOjrJ f2rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=LbjaDTcCUyKNm6FCgLYkHP3l7rAfVOYP4pn9L2EloHc=; b=WjsGSrRQpBNzxy370oH4+XWowXiQqqya14An1S/qHD7o2MFhEOEa1u6yUz37sPe5em I+jWvnjdD36D1mo5hJBU+G2wIMYetj4ErcWxXMiy+7nx3rt/Vg5RAZbtUAqRWs1l5mXJ XgLlHHW1uSclKcqTvpLsrDxiGYU5IM0CRYKzT8gCS/rKOgcb8gg+PIlRc6POuk/2HHeH mIIIjKbNzKlcpMtDPAWIBXDZvRYuFRhMBWAYyexbJT9yI78yKxfMjCWo1yiJe28gvS1j r0ff3/kBxWeFcyfNSDVaHahRsN53CiDNVh2T0l/wsT4cx7fbnZRiDvryM5U+wUBFRpeb gxjQ==
X-Gm-Message-State: AE9vXwM/grU3wNSPKBFWQWnmqnlavZyBSLMODKcAdL+ZDPlTLNVF/7cHL2iYA00D5gUU9g==
X-Received: by 10.98.72.28 with SMTP id v28mr9772608pfa.139.1472589591985; Tue, 30 Aug 2016 13:39:51 -0700 (PDT)
Received: from ?IPv6:2406:e007:7980:1:28cc:dc4c:9703:6781? ([2406:e007:7980:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id xn11sm59437105pac.38.2016.08.30.13.39.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Aug 2016 13:39:51 -0700 (PDT)
Subject: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc2460bis-05]
To: Bob Hinden <bob.hinden@gmail.com>, Tim Chown <Tim.Chown@jisc.ac.uk>
References: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk> <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a653fe9d-3290-3874-b2e5-298aa93e844e@gmail.com>
Date: Wed, 31 Aug 2016 08:39:53 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QlPjKgp90jk-p_aNYvlgWS3qF4Y>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 20:39:54 -0000

On 31/08/2016 08:19, Bob Hinden wrote:

=2E..
>> p.22 is Next Header value 59 used in practice? (Just curious=E2=80=A6 =
it was omitted from RFC7045).
>=20
> I am not 100% sure, but think it is used.  But it is not something that=
 has been updated.

It's a curious case, but we didn't mention it in 7045 or ask IANA to incl=
ude it in
http://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ext=
ension-header
because, well, it isn't a header and doesn't require any processing. I th=
ink
that's OK.

Regards
     Brian


From nobody Tue Aug 30 14:42:27 2016
Return-Path: <huitema@huitema.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F94C12D80F for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 14:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 Q6DS9fMucqNI for <ipv6@ietfa.amsl.com>; Tue, 30 Aug 2016 14:42:23 -0700 (PDT)
Received: from xsmtp12.mail2web.com (xsmtp12.mail2web.com [168.144.250.177]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 826AB12D800 for <6man@ietf.org>; Tue, 30 Aug 2016 14:42:23 -0700 (PDT)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp12.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1beqnS-0003r3-EK for 6man@ietf.org; Tue, 30 Aug 2016 17:42:22 -0400
Received: (qmail 23081 invoked from network); 30 Aug 2016 21:42:17 -0000
Received: from unknown (HELO [IPv6:::ffff:192.168.0.109]) (Authenticated-user:_huitema@huitema.net@[24.16.156.113]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <brian.e.carpenter@gmail.com>; 30 Aug 2016 21:42:16 -0000
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Bob Hinden <bob.hinden@gmail.com>, Tim Chown <Tim.Chown@jisc.ac.uk>
From: <huitema@huitema.net>
Date: Tue, 30 Aug 2016 14:41:42 -0700
Importance: normal
X-Priority: 3
In-Reply-To: <a653fe9d-3290-3874-b2e5-298aa93e844e@gmail.com>
References: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk> <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com> <a653fe9d-3290-3874-b2e5-298aa93e844e@gmail.com>
Content-Type: multipart/alternative; boundary="_E1F13997-80AF-4B80-B048-0C8537A8B11F_"
Subject: RE: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc2460bis-05]
Message-Id: <20160830214223.826AB12D800@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QSDu9L4Sr9p7ywshqdnIBuwJNTs>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 21:42:25 -0000

--_E1F13997-80AF-4B80-B048-0C8537A8B11F_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

It is used in Teredo. The Teredo bubbles have no payload, hence set payload=
 type to 59.

Sent from my Windows 10 phone

From: Brian E Carpenter=

--_E1F13997-80AF-4B80-B048-0C8537A8B11F_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3Dblue vlink=3D"#954F72"><div cla=
ss=3DWordSection1><p class=3DMsoNormal>It is used in Teredo. The Teredo bub=
bles have no payload, hence set payload type to 59.<o:p></o:p></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Sent from my Windows=
 10 phone</p><p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-fami=
ly:"Times New Roman",serif'><o:p>&nbsp;</o:p></span></p><div style=3D'mso-e=
lement:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3=
.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'border:none;padding:0in'><b=
>From: </b><a href=3D"mailto:brian.e.carpenter@gmail.com">Brian E Carpenter=
</a><br><b>Sent: </b>Tuesday, August 30, 2016 1:40 PM<br><b>To: </b><a href=
=3D"mailto:bob.hinden@gmail.com">Bob Hinden</a>; <a href=3D"mailto:Tim.Chow=
n@jisc.ac.uk">Tim Chown</a><br><b>Cc: </b><a href=3D"mailto:6man@ietf.org">=
6man@ietf.org</a><br><b>Subject: </b>Next Header value 59 [was Re: Review o=
f draft-ietf-6man-rfc2460bis-05]</p></div><p class=3DMsoNormal><span style=
=3D'font-size:12.0pt;font-family:"Times New Roman",serif'><o:p>&nbsp;</o:p>=
</span></p><p class=3DMsoNormal>On 31/08/2016 08:19, Bob Hinden wrote:</p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>...</p><p cla=
ss=3DMsoNormal>&gt;&gt; p.22 is Next Header value 59 used in practice? (Jus=
t curious=E2=80=A6 it was omitted from RFC7045).</p><p class=3DMsoNormal>&g=
t; </p><p class=3DMsoNormal>&gt; I am not 100% sure, but think it is used.=
=C2=A0 But it is not something that has been updated.</p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>It's a curious case, but we di=
dn't mention it in 7045 or ask IANA to include it in</p><p class=3DMsoNorma=
l>http://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#ext=
ension-header</p><p class=3DMsoNormal>because, well, it isn't a header and =
doesn't require any processing. I think</p><p class=3DMsoNormal>that's OK.<=
/p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Regards</=
p><p class=3DMsoNormal>=C2=A0=C2=A0=C2=A0=C2=A0 Brian</p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>------------------------------=
--------------------------------------</p><p class=3DMsoNormal>IETF IPv6 wo=
rking group mailing list</p><p class=3DMsoNormal>ipv6@ietf.org</p><p class=
=3DMsoNormal>Administrative Requests: https://www.ietf.org/mailman/listinfo=
/ipv6</p><p class=3DMsoNormal>---------------------------------------------=
-----------------------</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div>=
</body></html>=

--_E1F13997-80AF-4B80-B048-0C8537A8B11F_--


From nobody Wed Aug 31 01:30:28 2016
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C365412DA0C for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 01:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=jisc365.onmicrosoft.com
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 b9sFcNvuUCtO for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 01:30:25 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 039FC12DA0D for <6man@ietf.org>; Wed, 31 Aug 2016 01:30:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Y0NGE8pVw/emQvJBU/1brTK1wVpSH1gQnMJVk+vlSyU=; b=h41MYRw/wmx0LsXK5lzd27xSIArGkIKmpGiVyxM0cuu3J6YMjumLHGvcNnS1aR9iCrqJPjyuMla01gdd8a7OZOToQ61Iq7yfWdpCqOC2ZyOLhG8xjIQ+306KxFx3z4UTL8VclyQ0Ydc0huKL0sn3bCrgXyO79wiYugz4Ex7+7AA=
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0213.outbound.protection.outlook.com [213.199.154.213]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-55-Gf_dhKR9Nm-R5jPjieRBGA-1; Wed, 31 Aug 2016 09:30:17 +0100
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB454.eurprd07.prod.outlook.com (10.242.106.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.10; Wed, 31 Aug 2016 08:30:10 +0000
Received: from AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) by AMSPR07MB455.eurprd07.prod.outlook.com ([10.242.106.148]) with mapi id 15.01.0549.023; Wed, 31 Aug 2016 08:30:10 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "huitema@huitema.net" <huitema@huitema.net>
Subject: Re: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc2460bis-05]
Thread-Topic: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc2460bis-05]
Thread-Index: AQHSAv6ruaQ7Jjxl6UOploV+jwIdUKBiCJoAgAC2FQA=
Date: Wed, 31 Aug 2016 08:30:10 +0000
Message-ID: <F5C4DCD9-002D-4767-9BCB-E7E4366E793D@jisc.ac.uk>
References: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk> <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com> <a653fe9d-3290-3874-b2e5-298aa93e844e@gmail.com> <E1beqnb-0005Wh-7t@mx43.antispamcloud.com>
In-Reply-To: <E1beqnb-0005Wh-7t@mx43.antispamcloud.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [194.82.140.195]
x-ms-office365-filtering-correlation-id: bb139400-b001-4a57-9bcd-08d3d17905a9
x-microsoft-exchange-diagnostics: 1; AMSPR07MB454; 20:qqiid5YjAHAToPkiS/BB4ZnVtmjUi7pCLKl2/9BSxSsxDtVb+ltNd6f8PtyVuGVo3V/f9xrjwDg+oNURvvfZOf2zc35kqFaN7mkCkRu14Ti/a5v9/aPhLAAzuvLFUSRx5rx+lMc9KvC9K6kDlkY6QFwdphNLe8v/kuLV7nai0bU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB454;
x-microsoft-antispam-prvs: <AMSPR07MB45410F9E93AF59D493BBEEBD6E30@AMSPR07MB454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(274715658323672)(1591387915157);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046);  SRVR:AMSPR07MB454; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB454; 
x-forefront-prvs: 00514A2FE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(199003)(24454002)(377454003)(189002)(51444003)(19617315012)(102836003)(86362001)(3280700002)(3900700001)(19580395003)(230783001)(101416001)(87936001)(122556002)(2906002)(2501003)(16236675004)(4326007)(83716003)(3846002)(76176999)(82746002)(19580405001)(33656002)(66066001)(5002640100001)(15975445007)(74482002)(50986999)(2351001)(189998001)(5660300001)(92566002)(106356001)(50226002)(7906003)(81156014)(3660700001)(97736004)(106116001)(10400500002)(81166006)(8676002)(93886004)(8936002)(1730700003)(2950100001)(57306001)(6116002)(110136002)(11100500001)(36756003)(586003)(5640700001)(2900100001)(105586002)(68736007)(7846002)(7736002)(77096005)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB454; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Aug 2016 08:30:10.4140 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB454
X-MC-Unique: Gf_dhKR9Nm-R5jPjieRBGA-1
Content-Type: multipart/alternative; boundary="_000_F5C4DCD9002D47679BCBE7E4366E793Djiscacuk_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kQ8LRqclSDWCj8vOceNSfsAd7Tk>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 08:30:27 -0000

--_000_F5C4DCD9002D47679BCBE7E4366E793Djiscacuk_
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

T24gMzAgQXVnIDIwMTYsIGF0IDIyOjQxLCBodWl0ZW1hQGh1aXRlbWEubmV0PG1haWx0bzpodWl0
ZW1hQGh1aXRlbWEubmV0PiB3cm90ZToNCg0KSXQgaXMgdXNlZCBpbiBUZXJlZG8uIFRoZSBUZXJl
ZG8gYnViYmxlcyBoYXZlIG5vIHBheWxvYWQsIGhlbmNlIHNldCBwYXlsb2FkIHR5cGUgdG8gNTku
DQoNCk9LLCB0aGFua3MsIHRoYXQgc2VlbXMgYSByZWFzb25hYmxlIGdlbmVyaWMgdXNlIGNhc2Us
IGV2ZW4gaWYgdGhlcmXigJlzIG9ubHkgb25lIGV4YW1wbGUgOikNCg0KQnV0IGdpdmVuIGl04oCZ
cyBub3QgaW4gUkZDIDcwNDUsIGFueW9uZSBraW5kIGVub3VnaCB0byBpbXBsZW1lbnQgdGhlIGFk
dmljZSB0aGVyZSB3b27igJl0IG5lY2Vzc2FyaWx5IGluY2x1ZGUgaGVhZGVyIDU5Lg0KDQpUaW0N
Cg0KU2VudCBmcm9tIG15IFdpbmRvd3MgMTAgcGhvbmUNCg0KRnJvbTogQnJpYW4gRSBDYXJwZW50
ZXI8bWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbT4NClNlbnQ6IFR1ZXNkYXksIEF1
Z3VzdCAzMCwgMjAxNiAxOjQwIFBNDQpUbzogQm9iIEhpbmRlbjxtYWlsdG86Ym9iLmhpbmRlbkBn
bWFpbC5jb20+OyBUaW0gQ2hvd248bWFpbHRvOlRpbS5DaG93bkBqaXNjLmFjLnVrPg0KQ2M6IDZt
YW5AaWV0Zi5vcmc8bWFpbHRvOjZtYW5AaWV0Zi5vcmc+DQpTdWJqZWN0OiBOZXh0IEhlYWRlciB2
YWx1ZSA1OSBbd2FzIFJlOiBSZXZpZXcgb2YgZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXMtMDVd
DQoNCk9uIDMxLzA4LzIwMTYgMDg6MTksIEJvYiBIaW5kZW4gd3JvdGU6DQoNCi4uLg0KPj4gcC4y
MiBpcyBOZXh0IEhlYWRlciB2YWx1ZSA1OSB1c2VkIGluIHByYWN0aWNlPyAoSnVzdCBjdXJpb3Vz
4oCmIGl0IHdhcyBvbWl0dGVkIGZyb20gUkZDNzA0NSkuDQo+DQo+IEkgYW0gbm90IDEwMCUgc3Vy
ZSwgYnV0IHRoaW5rIGl0IGlzIHVzZWQuICBCdXQgaXQgaXMgbm90IHNvbWV0aGluZyB0aGF0IGhh
cyBiZWVuIHVwZGF0ZWQuDQoNCkl0J3MgYSBjdXJpb3VzIGNhc2UsIGJ1dCB3ZSBkaWRuJ3QgbWVu
dGlvbiBpdCBpbiA3MDQ1IG9yIGFzayBJQU5BIHRvIGluY2x1ZGUgaXQgaW4NCmh0dHA6Ly93d3cu
aWFuYS5vcmcvYXNzaWdubWVudHMvaXB2Ni1wYXJhbWV0ZXJzL2lwdjYtcGFyYW1ldGVycy54aHRt
bCNleHRlbnNpb24taGVhZGVyDQpiZWNhdXNlLCB3ZWxsLCBpdCBpc24ndCBhIGhlYWRlciBhbmQg
ZG9lc24ndCByZXF1aXJlIGFueSBwcm9jZXNzaW5nLiBJIHRoaW5rDQp0aGF0J3MgT0suDQoNClJl
Z2FyZHMNCiAgICAgQnJpYW4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCklFVEYgSVB2NiB3b3JraW5nIGdyb3Vw
IG1haWxpbmcgbGlzdA0KaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4NCkFkbWlu
aXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2lwdjYNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQoNCg==
--_000_F5C4DCD9002D47679BCBE7E4366E793Djiscacuk_
Content-Type: text/html; charset=UTF-8
Content-ID: <07F07767E9E1FB4599289F3BD9A5C3F5@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdj4NCjxibG9ja3F1b3RlIHR5
cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiAzMCBBdWcgMjAxNiwgYXQgMjI6
NDEsIDxhIGhyZWY9Im1haWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0IiBjbGFzcz0iIj4NCmh1aXRl
bWFAaHVpdGVtYS5uZXQ8L2E+IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1pbnRlcmNo
YW5nZS1uZXdsaW5lIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
IHN0eWxlPSJwYWdlOiBXb3JkU2VjdGlvbjE7IGZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IGZvbnQt
c2l6ZTogMTJweDsgZm9udC1zdHlsZTogbm9ybWFsOyBmb250LXZhcmlhbnQtY2Fwczogbm9ybWFs
OyBmb250LXdlaWdodDogbm9ybWFsOyBsZXR0ZXItc3BhY2luZzogbm9ybWFsOyBvcnBoYW5zOiBh
dXRvOyB0ZXh0LWFsaWduOiBzdGFydDsgdGV4dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFuc2Zvcm06
IG5vbmU7IHdoaXRlLXNwYWNlOiBub3JtYWw7IHdpZG93czogYXV0bzsgd29yZC1zcGFjaW5nOiAw
cHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsiPg0KPGRpdiBzdHlsZT0ibWFyZ2lu
OiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJp
LCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQpJdCBpcyB1c2VkIGluIFRlcmVkby4gVGhlIFRlcmVk
byBidWJibGVzIGhhdmUgbm8gcGF5bG9hZCwgaGVuY2Ugc2V0IHBheWxvYWQgdHlwZSB0byA1OS48
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2PjxiciBjbGFzcz0iIj4N
CjwvZGl2Pg0KT0ssIHRoYW5rcywgdGhhdCBzZWVtcyBhIHJlYXNvbmFibGUgZ2VuZXJpYyB1c2Ug
Y2FzZSwgZXZlbiBpZiB0aGVyZeKAmXMgb25seSBvbmUgZXhhbXBsZSA6KTwvZGl2Pg0KPGRpdj48
YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+QnV0IGdpdmVuIGl04oCZcyBub3QgaW4gUkZDIDcw
NDUsIGFueW9uZSBraW5kIGVub3VnaCB0byBpbXBsZW1lbnQgdGhlIGFkdmljZSB0aGVyZSB3b27i
gJl0IG5lY2Vzc2FyaWx5IGluY2x1ZGUgaGVhZGVyIDU5LjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjxkaXY+VGltPC9kaXY+DQo8ZGl2PjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxMXB0OyIgY2xhc3M9IiI+Jm5ic3A7
PC9zcGFuPjxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0K
PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIiBzdHlsZT0icGFnZTogV29yZFNlY3Rpb24xOyBmb250
LWZhbWlseTogSGVsdmV0aWNhOyBmb250LXNpemU6IDEycHg7IGZvbnQtc3R5bGU6IG5vcm1hbDsg
Zm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDsgZm9udC13ZWlnaHQ6IG5vcm1hbDsgbGV0dGVyLXNw
YWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjogc3RhcnQ7IHRleHQtaW5k
ZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFjZTogbm9ybWFsOyB3aWRv
d3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAw
cHg7Ij4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9udC1zaXplOiAx
MXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPg0KU2VudCBm
cm9tIG15IFdpbmRvd3MgMTAgcGhvbmU8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBp
biAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1z
ZXJpZjsiIGNsYXNzPSIiPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTJwdDsgZm9udC1mYW1p
bHk6ICdUaW1lcyBOZXcgUm9tYW4nLCBzZXJpZjsiIGNsYXNzPSIiPjxvOnAgY2xhc3M9IiI+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyLXN0eWxlOiBzb2xpZCBu
b25lIG5vbmU7IGJvcmRlci10b3AtY29sb3I6IHJnYigyMjUsIDIyNSwgMjI1KTsgYm9yZGVyLXRv
cC13aWR0aDogMXB0OyBwYWRkaW5nOiAzcHQgMGluIDBpbjsiIGNsYXNzPSIiPg0KPGRpdiBzdHls
ZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5
OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBib3JkZXI6IG5vbmU7IHBhZGRpbmc6IDBpbjsiIGNsYXNz
PSIiPg0KPGIgY2xhc3M9IiI+RnJvbTo8c3BhbiBjbGFzcz0iQXBwbGUtY29udmVydGVkLXNwYWNl
Ij4mbmJzcDs8L3NwYW4+PC9iPjxhIGhyZWY9Im1haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFp
bC5jb20iIHN0eWxlPSJjb2xvcjogcmdiKDE0OSwgNzksIDExNCk7IHRleHQtZGVjb3JhdGlvbjog
dW5kZXJsaW5lOyIgY2xhc3M9IiI+QnJpYW4gRSBDYXJwZW50ZXI8L2E+PGJyIGNsYXNzPSIiPg0K
PGIgY2xhc3M9IiI+U2VudDo8c3BhbiBjbGFzcz0iQXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJz
cDs8L3NwYW4+PC9iPlR1ZXNkYXksIEF1Z3VzdCAzMCwgMjAxNiAxOjQwIFBNPGJyIGNsYXNzPSIi
Pg0KPGIgY2xhc3M9IiI+VG86PHNwYW4gY2xhc3M9IkFwcGxlLWNvbnZlcnRlZC1zcGFjZSI+Jm5i
c3A7PC9zcGFuPjwvYj48YSBocmVmPSJtYWlsdG86Ym9iLmhpbmRlbkBnbWFpbC5jb20iIHN0eWxl
PSJjb2xvcjogcmdiKDE0OSwgNzksIDExNCk7IHRleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lOyIg
Y2xhc3M9IiI+Qm9iIEhpbmRlbjwvYT47PHNwYW4gY2xhc3M9IkFwcGxlLWNvbnZlcnRlZC1zcGFj
ZSI+Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpUaW0uQ2hvd25AamlzYy5hYy51ayIgc3R5
bGU9ImNvbG9yOiByZ2IoMTQ5LCA3OSwgMTE0KTsgdGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmU7
IiBjbGFzcz0iIj5UaW0NCiBDaG93bjwvYT48YnIgY2xhc3M9IiI+DQo8YiBjbGFzcz0iIj5DYzo8
c3BhbiBjbGFzcz0iQXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PC9iPjxhIGhy
ZWY9Im1haWx0bzo2bWFuQGlldGYub3JnIiBzdHlsZT0iY29sb3I6IHJnYigxNDksIDc5LCAxMTQp
OyB0ZXh0LWRlY29yYXRpb246IHVuZGVybGluZTsiIGNsYXNzPSIiPjZtYW5AaWV0Zi5vcmc8L2E+
PGJyIGNsYXNzPSIiPg0KPGIgY2xhc3M9IiI+U3ViamVjdDo8c3BhbiBjbGFzcz0iQXBwbGUtY29u
dmVydGVkLXNwYWNlIj4mbmJzcDs8L3NwYW4+PC9iPk5leHQgSGVhZGVyIHZhbHVlIDU5IFt3YXMg
UmU6IFJldmlldyBvZiBkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wNV08L2Rpdj4NCjwvZGl2
Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7
IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQo8c3BhbiBzdHls
ZT0iZm9udC1zaXplOiAxMnB0OyBmb250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbicsIHNlcmlm
OyIgY2xhc3M9IiI+PG86cCBjbGFzcz0iIj4mbmJzcDs8L286cD48L3NwYW4+PC9kaXY+DQo8ZGl2
IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1m
YW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj4NCk9uIDMxLzA4LzIwMTYgMDg6
MTksIEJvYiBIaW5kZW4gd3JvdGU6PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4g
MC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2Vy
aWY7IiBjbGFzcz0iIj4NCjxvOnAgY2xhc3M9IiI+Jm5ic3A7PC9vOnA+PC9kaXY+DQo8ZGl2IHN0
eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1p
bHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj4NCi4uLjwvZGl2Pg0KPGRpdiBzdHls
ZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5
OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQomZ3Q7Jmd0OyBwLjIyIGlzIE5leHQg
SGVhZGVyIHZhbHVlIDU5IHVzZWQgaW4gcHJhY3RpY2U/IChKdXN0IGN1cmlvdXPigKYgaXQgd2Fz
IG9taXR0ZWQgZnJvbSBSRkM3MDQ1KS48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBp
biAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1z
ZXJpZjsiIGNsYXNzPSIiPg0KJmd0OzxzcGFuIGNsYXNzPSJBcHBsZS1jb252ZXJ0ZWQtc3BhY2Ui
PiZuYnNwOzwvc3Bhbj48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAwMDFw
dDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiIGNs
YXNzPSIiPg0KJmd0OyBJIGFtIG5vdCAxMDAlIHN1cmUsIGJ1dCB0aGluayBpdCBpcyB1c2VkLiZu
YnNwOyBCdXQgaXQgaXMgbm90IHNvbWV0aGluZyB0aGF0IGhhcyBiZWVuIHVwZGF0ZWQuPC9kaXY+
DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsg
Zm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj4NCjxvOnAgY2xhc3M9
IiI+Jm5ic3A7PC9vOnA+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAx
cHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBj
bGFzcz0iIj4NCkl0J3MgYSBjdXJpb3VzIGNhc2UsIGJ1dCB3ZSBkaWRuJ3QgbWVudGlvbiBpdCBp
biA3MDQ1IG9yIGFzayBJQU5BIHRvIGluY2x1ZGUgaXQgaW48L2Rpdj4NCjxkaXYgc3R5bGU9Im1h
cmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPg0KPGEgaHJlZj0iaHR0cDovL3d3dy5pYW5hLm9y
Zy9hc3NpZ25tZW50cy9pcHY2LXBhcmFtZXRlcnMvaXB2Ni1wYXJhbWV0ZXJzLnhodG1sI2V4dGVu
c2lvbi1oZWFkZXIiIGNsYXNzPSIiPmh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvaXB2
Ni1wYXJhbWV0ZXJzL2lwdjYtcGFyYW1ldGVycy54aHRtbCNleHRlbnNpb24taGVhZGVyPC9hPjwv
ZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDEx
cHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQpiZWNhdXNl
LCB3ZWxsLCBpdCBpc24ndCBhIGhlYWRlciBhbmQgZG9lc24ndCByZXF1aXJlIGFueSBwcm9jZXNz
aW5nLiBJIHRoaW5rPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7
IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFz
cz0iIj4NCnRoYXQncyBPSy48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAw
MDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsi
IGNsYXNzPSIiPg0KPG86cCBjbGFzcz0iIj4mbmJzcDs8L286cD48L2Rpdj4NCjxkaXYgc3R5bGU9
Im1hcmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTog
Q2FsaWJyaSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPg0KUmVnYXJkczwvZGl2Pg0KPGRpdiBzdHls
ZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5
OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgQnJpYW48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9u
dC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIi
Pg0KPG86cCBjbGFzcz0iIj4mbmJzcDs8L286cD48L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjog
MGluIDBpbiAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwg
c2Fucy1zZXJpZjsiIGNsYXNzPSIiPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj4NCjxkaXYgc3R5bGU9Im1h
cmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgc2Fucy1zZXJpZjsiIGNsYXNzPSIiPg0KSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFp
bGluZyBsaXN0PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZv
bnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0i
Ij4NCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIiBzdHlsZT0iY29sb3I6IHJnYigxNDks
IDc5LCAxMTQpOyB0ZXh0LWRlY29yYXRpb246IHVuZGVybGluZTsiIGNsYXNzPSIiPmlwdjZAaWV0
Zi5vcmc8L2E+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZv
bnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0i
Ij4NCkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOjxzcGFuIGNsYXNzPSJBcHBsZS1jb252ZXJ0ZWQt
c3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2lwdjYiIHN0eWxlPSJjb2xvcjogcmdiKDE0OSwgNzksIDExNCk7IHRleHQtZGVj
b3JhdGlvbjogdW5kZXJsaW5lOyIgY2xhc3M9IiI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pcHY2PC9hPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwaW4gMGluIDAu
MDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlm
OyIgY2xhc3M9IiI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjwvYm9keT4NCjwvaHRtbD4NCg==
--_000_F5C4DCD9002D47679BCBE7E4366E793Djiscacuk_--


From nobody Wed Aug 31 03:24:07 2016
Return-Path: <ietf@kuehlewind.net>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 498C412DAC8; Wed, 31 Aug 2016 03:23:59 -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>
Subject: =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-ietf-6man?= =?utf-8?q?-deprecate-atomfrag-generation-07=3A_=28with_COMMENT=29?=
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147263903929.5250.5342651774611258202.idtracker@ietfa.amsl.com>
Date: Wed, 31 Aug 2016 03:23:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/OA3fLgTaIFSI37eRxiTHN3l2724>
Cc: bob.hinden@gmail.com, ipv6@ietf.org, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 10:24:03 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-6man-deprecate-atomfrag-generation-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-6man-deprecate-atomfrag-generation/



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

I have to say I agree with the tsv-art review that it is not fully clear
to me that this explanation needs an own document. For me a much short
rational for this change (1 or max. 2 paragraphs) that could be
integrated in 2460bis would be sufficient (also given that this document
has soe redundancy).



From nobody Wed Aug 31 03:59:28 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF9812DAC5; Wed, 31 Aug 2016 03:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 n5_-GwLksCyj; Wed, 31 Aug 2016 03:59:24 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 57D4612D16F; Wed, 31 Aug 2016 03:59:24 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id i184so4588345itf.1; Wed, 31 Aug 2016 03:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=E6o8TVz0KASZ+UFr4jWzCyug4qCGMdelNCwbESB6cP0=; b=rGNiW4+wUFR4NVvg3L+W4jks2I0R1UeU9JqKh+X9L0x0jvFJ03UdXMjfxLdvmF+cUC JPIRBGtB/ghn8m1hSHmpW9PpHGTYOnUOQyOIcX+IAfM6Ym9vwTlganM+t/yIRpOQywql qcWMCNnTylLMvYt4rF27w3B+72BYp0oNLt9OLakNnALQ2Erzup3wqPsb1Uxr/56r7TQn a+X78jzStuImTZWTqNCnM5YFnk4r9UZ8kBTGr7E4B1LkHonuR1mgiBN/W+LYf2GQ7nI1 iAe3KeHQiYwCRBlTUlvzbqILUoSq3LUK/KpEuzJdx1UjRuIt5rICRX9L8yrhIPv88pmi 5L6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=E6o8TVz0KASZ+UFr4jWzCyug4qCGMdelNCwbESB6cP0=; b=N7mneUe8Iw13bPlxYRYG84Dquu9ykUPEZIL1Ywuhhbjc6PYDgrKwTDs0tFKedwGQir i75ApgyERY0C0FkQA+ZvEE6nEcDTflyDva9lW591cwcVR5U5kZRWzQm6tmPzIJp7vGIR hVvUeDZJ/yw4ZKvGL2L/YcM5WLP3mFCMWu875klf2gDMxPBdXLoQEip0ZCSndtNGU9T+ RllhzJ5OhihODCdDHd2rpbUdiC7mJNmwHfdkn2Jx9xCzw5G5n/VSm9otA+Txq8pgSO7+ 0hkpGkt/LfoUj+djHZ7arpClZduYaB0LcM2NRFTRmEr6afhqbTxM1uY3Kqy7+m2EJJqM KuHQ==
X-Gm-Message-State: AE9vXwPXVVnf0koxdxQVPngl3+AXsX4VpfnvzvTNhx27Ip2WWRodSLXr2RrKDqgHWAy6NWLEyloBdftoJ3NZLQ==
X-Received: by 10.107.15.38 with SMTP id x38mr4723894ioi.74.1472641163637; Wed, 31 Aug 2016 03:59:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Wed, 31 Aug 2016 03:59:03 -0700 (PDT)
In-Reply-To: <CAAedzxpdj4ST94D-1DjWij7L-AARhuzvkgn74b5ORgRV+ZiWgg@mail.gmail.com>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com> <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com> <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com> <CAAedzxpdj4ST94D-1DjWij7L-AARhuzvkgn74b5ORgRV+ZiWgg@mail.gmail.com>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Wed, 31 Aug 2016 16:29:03 +0530
Message-ID: <CANFmOtk-JXr6DufaC5G54-+L-OJXP-O1jZSW+3iNkfwQ83kDyw@mail.gmail.com>
Subject: Re: [v6ops] Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Erik Kline <ek@google.com>
Content-Type: multipart/alternative; boundary=001a113e9f5270bdf3053b5bfd41
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gyoBn3QTwVaXhFLCSQA-hEqE7qk>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 10:59:26 -0000

--001a113e9f5270bdf3053b5bfd41
Content-Type: text/plain; charset=UTF-8

Hello,

As per section 7 of RFC 6788, Line-Identification option is encoded in
below format.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   |  Option Type  | Option Length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | LineIDLen     |     Line ID...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 4: Line-Identification Option Layout


Does the above layout mean that option type 0x8C will start at 2nd byte?

Yours,
Naveen.

On 24 August 2016 at 17:08, Erik Kline <ek@google.com> wrote:

> On 24 August 2016 at 19:58, Mark Smith <markzzzsmith@gmail.com> wrote:
> > On 24 August 2016 at 20:29, Naveen Kottapalli <naveen.sarma@gmail.com>
> wrote:
> >> Hello,
> >>
> >> If the AP is relaying the RS on a GRE tunnel to the gateway, can
> whatever
> >> Erik suggested be used to inject the information whatever am looking
> for?
> >>
> >
> > Possibly (I'd forgotten about that method) if the AP supported it.
>
> Yeah, definitely a question for your vendor.
>
> >
> >
> > Regards,
> > Mark.
> >
> >
> >> Yours,
> >> Naveen.
> >>
> >> On 24 August 2016 at 15:29, Mark Smith <markzzzsmith@gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> On 24 August 2016 at 19:28, Naveen Kottapalli <naveen.sarma@gmail.com>
> >>> wrote:
> >>> > Hello,
> >>> >
> >>> > Can anyone tell if there is any SLAAC equivalent for DHCPv6
> Remote-Id /
> >>> > DHCP
> >>> > Option-82 option that can be used by a gateway to know the SSID,
> etc.,?
> >>> >
> >>>
> >>> No there isn't.
> >>>
> >>> SLAAC is not relayed through a router/gateway is like DHCPv4 is, so
> >>> there is no point trying to add information on the way.
> >>>
> >>> SLAAC doesn't actually assign addresses to hosts either - all it does
> >>> is provides the hosts on the link with information about what
> >>> prefixes/subnets are present on the link, and hosts then generate
> >>> their own addresses from within the prefix.
> >>>
> >>> In other words, if you're thinking IPv6 SLAAC is equivalent to IPv4
> >>> DHCP, they aren't, they're very different.
> >>>
> >>> The use of DHCPv4 to assign addresses could be described as a
> >>> centralised database dependent host address assignment
> >>> protocol/method, where hosts don't participate in the generation and
> >>> selection of the addresses they end up using. They either take what
> >>> they're given from the DHCPv4 server or don't have an address to use.
> >>>
> >>> The use of SLAAC for address assignment in IPv6 could be described as
> >>> a distributed address assignment system that doesn't have a central
> >>> database. Hosts are entirely responsible for the generation and
> >>> validation of addresses that they use based on the prefix information
> >>> supplied in RAs.
> >>>
> >>> Regards,
> >>> Mark.
> >>>
> >>>
> >>> > Yours,
> >>> > Naveen.
> >>> >
> >>> > --------------------------------------------------------------------
> >>> > IETF IPv6 working group mailing list
> >>> > ipv6@ietf.org
> >>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>> > --------------------------------------------------------------------
> >>> >
> >>
> >>
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>

--001a113e9f5270bdf3053b5bfd41
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>As per section 7 of RFC 6788, Li=
ne-Identification option is encoded in below format.</div><div><br></div><d=
iv><pre class=3D"" style=3D"font-size:13.3333px;margin-top:0px;margin-botto=
m:0px;color:rgb(0,0,0)">    0                   1                   2      =
             3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                   |  Option Type  | Option Length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | LineIDLen     |     Line ID...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 4: Line-Identification Option Layout
</pre></div><div><br></div><div>Does the above layout mean that option type=
 0x8C will start at 2nd byte?</div><div><br></div><div class=3D"gmail_extra=
"><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">Yo=
urs,<br>Naveen.</div></div>
<br><div class=3D"gmail_quote">On 24 August 2016 at 17:08, Erik Kline <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:ek@google.com" target=3D"_blank">ek@goog=
le.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On 24 August 2016 at 19:58, Mark Smith &lt;<a href=3D"mailto:markzzzs=
mith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt; On 24 August 2016 at 20:29, Naveen Kottapalli &lt;<a href=3D"mailto:na=
veen.sarma@gmail.com">naveen.sarma@gmail.com</a>&gt; wrote:<br>
&gt;&gt; Hello,<br>
&gt;&gt;<br>
&gt;&gt; If the AP is relaying the RS on a GRE tunnel to the gateway, can w=
hatever<br>
&gt;&gt; Erik suggested be used to inject the information whatever am looki=
ng for?<br>
&gt;&gt;<br>
&gt;<br>
&gt; Possibly (I&#39;d forgotten about that method) if the AP supported it.=
<br>
<br>
</span>Yeah, definitely a question for your vendor.<br>
<div><div class=3D"h5"><br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt; Mark.<br>
&gt;<br>
&gt;<br>
&gt;&gt; Yours,<br>
&gt;&gt; Naveen.<br>
&gt;&gt;<br>
&gt;&gt; On 24 August 2016 at 15:29, Mark Smith &lt;<a href=3D"mailto:markz=
zzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 24 August 2016 at 19:28, Naveen Kottapalli &lt;<a href=3D"m=
ailto:naveen.sarma@gmail.com">naveen.sarma@gmail.com</a>&gt;<br>
&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt; &gt; Hello,<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; Can anyone tell if there is any SLAAC equivalent for DHCP=
v6 Remote-Id /<br>
&gt;&gt;&gt; &gt; DHCP<br>
&gt;&gt;&gt; &gt; Option-82 option that can be used by a gateway to know th=
e SSID, etc.,?<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; No there isn&#39;t.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; SLAAC is not relayed through a router/gateway is like DHCPv4 i=
s, so<br>
&gt;&gt;&gt; there is no point trying to add information on the way.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; SLAAC doesn&#39;t actually assign addresses to hosts either - =
all it does<br>
&gt;&gt;&gt; is provides the hosts on the link with information about what<=
br>
&gt;&gt;&gt; prefixes/subnets are present on the link, and hosts then gener=
ate<br>
&gt;&gt;&gt; their own addresses from within the prefix.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; In other words, if you&#39;re thinking IPv6 SLAAC is equivalen=
t to IPv4<br>
&gt;&gt;&gt; DHCP, they aren&#39;t, they&#39;re very different.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The use of DHCPv4 to assign addresses could be described as a<=
br>
&gt;&gt;&gt; centralised database dependent host address assignment<br>
&gt;&gt;&gt; protocol/method, where hosts don&#39;t participate in the gene=
ration and<br>
&gt;&gt;&gt; selection of the addresses they end up using. They either take=
 what<br>
&gt;&gt;&gt; they&#39;re given from the DHCPv4 server or don&#39;t have an =
address to use.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The use of SLAAC for address assignment in IPv6 could be descr=
ibed as<br>
&gt;&gt;&gt; a distributed address assignment system that doesn&#39;t have =
a central<br>
&gt;&gt;&gt; database. Hosts are entirely responsible for the generation an=
d<br>
&gt;&gt;&gt; validation of addresses that they use based on the prefix info=
rmation<br>
&gt;&gt;&gt; supplied in RAs.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Regards,<br>
&gt;&gt;&gt; Mark.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &gt; Yours,<br>
&gt;&gt;&gt; &gt; Naveen.<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;&gt; &gt; ------------------------------<wbr>----------------------=
--------<wbr>--------<br>
&gt;&gt;&gt; &gt; IETF IPv6 working group mailing list<br>
&gt;&gt;&gt; &gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt;&gt; &gt; Administrative Requests: <a href=3D"https://www.ietf.org/=
mailman/listinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.iet=
f.org/mailman/<wbr>listinfo/ipv6</a><br>
&gt;&gt;&gt; &gt; ------------------------------<wbr>----------------------=
--------<wbr>--------<br>
&gt;&gt;&gt; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
</div></div>&gt; ______________________________<wbr>_________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/v6ops</a>=
<br>
</blockquote></div><br></div></div>

--001a113e9f5270bdf3053b5bfd41--


From nobody Wed Aug 31 04:05:07 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A8E128874; Wed, 31 Aug 2016 04:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.336
X-Spam-Level: 
X-Spam-Status: No, score=-1.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 0pnH7wUku5SH; Wed, 31 Aug 2016 04:04:58 -0700 (PDT)
Received: from incoming.kjsl.com (inbound02.kjsl.com [IPv6:2001:1868:2002::144]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AE34120727; Wed, 31 Aug 2016 04:04:58 -0700 (PDT)
Received: from cowbell.employees.org ([IPv6:2001:1868:a000:17::142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Aug 2016 11:02:56 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 9A73B9CC4F; Wed, 31 Aug 2016 04:02:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=snwofiSYybRIFHpPecmCihT7Ofg=; b= K8TZZVvjfNjboywrOO8yuFSgS7ffBF1nKW0P3LCx25eWi8pi6XGhXTXA0n+wxBel 4mjcq3UPYwUMrHWU4uQFlyK5KwmB+RiYO9s83l17RC12icilNLLx3v0PiUdgFy/y JEt6BYXPDtAVLIaZjwCSLicxMqx+bLLMY3joN5vgRY0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=DOSWk6vPdw1B98Qb0wDUeKudEa Z/Yn9Ydu2R2YB7E+616Qx/Zk0A4RwFs6SiyBDVgAxMGTAapGmW0832oYB0dZOhOX PlbvV1ecjf0GqLn4B/S0kp+2eCHQkTz3iSeJoPPZcpXOYqXm7eOgA5vrI90Xd4fV RDJPtW8I/Ku5fAH9Q=
Received: from h.hanazo.no (unknown [173.38.220.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 58F9E9CC51; Wed, 31 Aug 2016 04:02:55 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B5BB138AE1F1; Wed, 31 Aug 2016 13:02:52 +0200 (CEST)
Subject: =?utf-8?Q?Re=3A_Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?Q?etf-6man-deprecate-atomfrag-generation-07=3A_=28with_C?= =?utf-8?Q?OMMENT=29?=
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A49276FF-54E1-43EB-BA45-4ECD43742192"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: otroan@employees.org
In-Reply-To: <147263903929.5250.5342651774611258202.idtracker@ietfa.amsl.com>
Date: Wed, 31 Aug 2016 13:02:51 +0200
Message-Id: <E948DE56-F357-4867-B112-A9842CD01E5A@employees.org>
References: <147263903929.5250.5342651774611258202.idtracker@ietfa.amsl.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/7VrlLPS5QvOaptcOio1oZ1AqI_s>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Bob Hinden <bob.hinden@gmail.com>, The IESG <iesg@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 11:05:00 -0000

--Apple-Mail=_A49276FF-54E1-43EB-BA45-4ECD43742192
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>=20
> I have to say I agree with the tsv-art review that it is not fully =
clear
> to me that this explanation needs an own document. For me a much short
> rational for this change (1 or max. 2 paragraphs) that could be
> integrated in 2460bis would be sufficient (also given that this =
document
> has soe redundancy).

The document has served it's purpose by getting the change into 2460bis =
and an updated 6145.
The question is if it worth publishing as a 'historical record' or not =
was also discussed in 6MAN.
The working group was judged to be in favour of publishing, but my take =
is that the WG will not object too much if the larger IETF community =
decided this wasn't worth doing at this point.

Best regards,
Ole

--Apple-Mail=_A49276FF-54E1-43EB-BA45-4ECD43742192
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJXxrlcAAoJEL7aWKiYQt92++oP/i76Tfb6/zo2O/hpgqcpCMJ3
vR6UUWD1YsDFwvaWZey6zNQavxBSstq9QBZN2/9W+EUqd27m6HIqNZS9wmQ7dpjC
dB42j8oOJ7lzsdIMENIpAh1ywz+czMDrC9qseCFiGmYEaPwoIF0Bkyx/wiBhLmxK
zGVVRlc2P+J+E35n8VV/JQRyp60IdziYoRL9WtlVlxr0uZ/8rflSwGtAfMUB/4BX
fyJbZEE0PzYV61T0/fjlb6DhjDqp94ne2L7c4DCgm4FIjF+g56kdqWXsCMNWPKF+
R78IoQ50HQQKWxC3ryVEDyp5VvvRS5V5IbqEJMiMWy0ckcLa6gtW/dOIuCU8f28K
itIcZbSXTVthrBQf4rY6kPYBhC/fShZ0Pl6qZtCKY06ASMVMEum2TUFfftehEHmE
3zxRfsngCLTvU61OobINJGITf03PE9pA7fK7SqHXUEf9O8f4f/00/Tzt5fBmVSKH
BbxaWJE4l2OxuWpkI/UnKXPO8RztNyO1Gezx8paMjKHNqDvyVbaOxSUy9E6+tD0f
MayB7JOVSOT8JTXGGkPvtOhnC14Y/ag16Mak7uRvsF6Q+xMgTL0Mw51Dd0Yavw8B
/LQgsuEh9Okwa+7CiiPgdSYXwZs86oxmzny+oepduCsR1ABCjoWq6jwwjSEC34Vu
IFMFMiCeYByH6eA2btjz
=sQxg
-----END PGP SIGNATURE-----

--Apple-Mail=_A49276FF-54E1-43EB-BA45-4ECD43742192--


From nobody Wed Aug 31 04:31:04 2016
Return-Path: <ietf@kuehlewind.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D23B12DAEC for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 04:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 KD755j1TuUhJ for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 04:31:01 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B721212DAE8 for <ipv6@ietf.org>; Wed, 31 Aug 2016 04:31:00 -0700 (PDT)
Received: (qmail 20348 invoked from network); 31 Aug 2016 13:23:36 +0200
Received: from p5dec2def.dip0.t-ipconnect.de (HELO ?192.168.178.33?) (93.236.45.239) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated);  31 Aug 2016 13:23:36 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: =?utf-8?Q?Re=3A_Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-i?= =?utf-8?Q?etf-6man-deprecate-atomfrag-generation-07=3A_=28with_C?= =?utf-8?Q?OMMENT=29?=
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <E948DE56-F357-4867-B112-A9842CD01E5A@employees.org>
Date: Wed, 31 Aug 2016 13:23:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F519D2FD-7DBD-4AF2-8B19-2ADE950A3D12@kuehlewind.net>
References: <147263903929.5250.5342651774611258202.idtracker@ietfa.amsl.com> <E948DE56-F357-4867-B112-A9842CD01E5A@employees.org>
To: otroan@employees.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/qjfPnkvfImDTJ9Ts_9FNYvxQ7dM>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, Bob Hinden <bob.hinden@gmail.com>, The IESG <iesg@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 11:31:02 -0000

Okay, good to know. I also don=E2=80=99t have a strong opinion about =
this. Just want to bring up this point in case others have an opinion =
too.

Mirja


> Am 31.08.2016 um 13:02 schrieb otroan@employees.org:
>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> I have to say I agree with the tsv-art review that it is not fully =
clear
>> to me that this explanation needs an own document. For me a much =
short
>> rational for this change (1 or max. 2 paragraphs) that could be
>> integrated in 2460bis would be sufficient (also given that this =
document
>> has soe redundancy).
>=20
> The document has served it's purpose by getting the change into =
2460bis and an updated 6145.
> The question is if it worth publishing as a 'historical record' or not =
was also discussed in 6MAN.
> The working group was judged to be in favour of publishing, but my =
take is that the WG will not object too much if the larger IETF =
community decided this wasn't worth doing at this point.
>=20
> Best regards,
> Ole


From nobody Wed Aug 31 05:46:34 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07A1412DB4F; Wed, 31 Aug 2016 05:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 eAJqxJMHD_n6; Wed, 31 Aug 2016 05:46:27 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E471812DB47; Wed, 31 Aug 2016 05:46:26 -0700 (PDT)
X-AuditID: c6180641-e87ff70000000a0b-cd-57c67d3d8abb
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by  (Symantec Mail Security) with SMTP id 3A.01.02571.D3D76C75; Wed, 31 Aug 2016 08:46:23 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0301.000; Wed, 31 Aug 2016 08:46:23 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Naveen Kottapalli <naveen.sarma@gmail.com>, Erik Kline <ek@google.com>
Subject: Re: [v6ops] Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
Thread-Topic: [v6ops] Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
Thread-Index: AQHR/fwZayWIRqHvnkuo2orpk9hUEA==
Date: Wed, 31 Aug 2016 12:46:21 +0000
Message-ID: <E87B771635882B4BA20096B589152EF643E869AE@eusaamb107.ericsson.se>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com> <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com> <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com> <CAAedzxpdj4ST94D-1DjWij7L-AARhuzvkgn74b5ORgRV+ZiWgg@mail.gmail.com> <CANFmOtk-JXr6DufaC5G54-+L-OJXP-O1jZSW+3iNkfwQ83kDyw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXSPt6597bFwg752E4vPt+exW7w8+57J 4t25LywWp4/tZXZg8dg56y67x4JNpR5LlvxkCmCO4rJJSc3JLEst0rdL4Mo48uQTY8EHnoon C5axNzAu4+xi5OSQEDCRWHa2iRHEFhLYwChx6QRbFyMXkL2cUeLtoTNMIAk2oKINOz+D2SIC XhLvdu1nA7GZBSwknk+ewQJiCwsESixe9o8VoiZIYs2RTewQtp7Ep8eXwWpYBFQlfv5vAYvz CvhKXJvQzgqxbDOzxM/2n2DNjAJiEt9PrWGCWCAucevJfCaISwUkluw5zwxhi0q8fAyxTEJA SeLj7/nsEPU6Egt2f4I6Tlti2cLXzBDLBCVOznzCMoFRZBaSsbOQtMxC0jILScsCRpZVjByl xQU5uelGhpsYgTFxTILNcQfj3l7PQ4wCHIxKPLxnbx0NF2JNLCuuzD3EKMHBrCTCu+nCsXAh 3pTEyqrUovz4otKc1OJDjNIcLErivPovFcOFBNITS1KzU1MLUotgskwcnFINjMs35zMohUxn 3uV3hCvO2HlekJZUhNHsm5buU4x9WLQCmOe9vfm3KoFhw0aOxZxVc7oKmWdwxzYbxN9ekBP4 kz/5Q6mSEFfbbVff93UnHC9pa36/022pmd6rN++Qz4k3ztvbH96qTl9xL3Of2eLQc19ennj0 8YLhlC9aUjl/5X24VlopSYZyK7EUZyQaajEXFScCAFIu0NiFAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Savb4VKxa34JjjE7HvSaSucyuwc>
Cc: v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 12:46:29 -0000

Hi Naveen,=0A=
=0A=
On 08/31/2016 06:59 AM, Naveen Kottapalli wrote:=0A=
> Hello,=0A=
>=0A=
> As per section 7 of RFC 6788, Line-Identification option is encoded in be=
low=0A=
> format.=0A=
>=0A=
>     0                   1                   2                   3=0A=
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=0A=
>                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A=
>                                    |  Option Type  | Option Length |=0A=
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A=
>    | LineIDLen     |     Line ID...=0A=
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=0A=
>=0A=
>                 Figure 4: Line-Identification Option Layout=0A=
>=0A=
>=0A=
> Does the above layout mean that option type 0x8C will start at 2nd byte?=
=0A=
=0A=
The Option type 0x8c will be in the first byte (Byte 0) of the option. The =
=0A=
IPv6 ND option formats are shown like this along with a alignment requireme=
nt =0A=
to allow for proper encoding of multi-byte fields. In this particular case =
=0A=
there is no alignment required.=0A=
=0A=
As for your other question upthread, I do not know of any implementations i=
n =0A=
WiFi APs. This option was primarily for Broadband Forum networks and AFAIK =
=0A=
only BNGs and Access Nodes (e.g. DSLAMs) implemented it. If you are =0A=
interested in using this for other purposes, please read Section 2 of the =
=0A=
document to check if the issues mentioned there apply to your specific =0A=
deployment scenario.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=
=0A=


From nobody Wed Aug 31 06:16:41 2016
Return-Path: <naveen.sarma@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBF0212D1BB; Wed, 31 Aug 2016 06:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 SFWXFt0jE2EV; Wed, 31 Aug 2016 06:16:34 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 71F8012D4FB; Wed, 31 Aug 2016 06:16:31 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id e124so6830040ith.0; Wed, 31 Aug 2016 06:16:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/cEEWgCetWgX2t9ZaDasMEVTAPOsmK8vQkU+p7Go+sE=; b=lyNthF/WCay5vgcOCxt7eHaqrPGhqljKSQyjQ/73BOKx40k8PlkLXP+pVLIWDnOagt Zohp5v8O1J1Bk4TCaWr1HiHJrwJkoZMcip09s3cFwSx6jfLwf/9ftAsv5KTB/d+mt25M DBaieocM8IWvAfhsVUj4Nhpkjvi6A38TdYngjA/0yMJ5wpQcJw+Oxx5IuJFV19wR3fEn MKn65GvVp8795bz9QVY9nR4P+9R4mtcp8rmFOgpr6c9SLwdZcYDC3x2xvPT4PH1ASdG1 VEO3OXwnga04blUCFMFsTXHLYL5yhAVhQvwnqwAPcw7UlA2xXWHmupSqlzh4ILOBJV7N k+0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/cEEWgCetWgX2t9ZaDasMEVTAPOsmK8vQkU+p7Go+sE=; b=Nj0VbFXX1r/UiA86fh4JKMkfIa2qgjp+j0gqAOC8F4qlolLrUx/8Ofno8kqXjPcUPc I4PaZCJYGol6S4XZDHgoKn/S43LRM+eYJIPKvMP0iW8rd0GQ+JIjFFvocprSPZ7GPk2n fHfik/odkUyYfvbBu81LErz+9RDZo2LqCH9KeK/DK9+PWHV1H+O3GKGIYNUAdwUK8TKr s1kEYSEE4/0E+glYS7H6x1J2DC0nFsgzLq3+6/IRqDoC6/u3tCCzTby7wywkqY4P3miD CSsHzJwFEXREIGhOWclmTvjT2Qo/n63fHN+q3ubisAq9Et5h/Xx2HQbbqUYIMg/O0x8j ipdg==
X-Gm-Message-State: AE9vXwOKT9faFNhv+ofUh8ofH1elo321HxDmyE9Eh5IZKN0TaFN3Ma7f5ZrLjzMfCtN3ThEzsvoDNZdpOE1OKg==
X-Received: by 10.36.227.78 with SMTP id d75mr29598568ith.75.1472649390804; Wed, 31 Aug 2016 06:16:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.54.209 with HTTP; Wed, 31 Aug 2016 06:16:10 -0700 (PDT)
In-Reply-To: <E87B771635882B4BA20096B589152EF643E869AE@eusaamb107.ericsson.se>
References: <CANFmOtmZwNh7z6wWFg5cJsXMZbix1EKq4VZ5xZvuPOfZfWFD=g@mail.gmail.com> <CAO42Z2z2x+mexvDPrA8F=h+Aq2XGxW-7-JmHUoiccUisTMwmxQ@mail.gmail.com> <CANFmOtmM0-5ypqKEWyLgu63bUvAuNF9UT7SBp11sQT3C=1iR3w@mail.gmail.com> <CAO42Z2yHF6cySgpsr-fE5MceKk+p_reC-P9LTVe7cOp3uSQ0qw@mail.gmail.com> <CAAedzxpdj4ST94D-1DjWij7L-AARhuzvkgn74b5ORgRV+ZiWgg@mail.gmail.com> <CANFmOtk-JXr6DufaC5G54-+L-OJXP-O1jZSW+3iNkfwQ83kDyw@mail.gmail.com> <E87B771635882B4BA20096B589152EF643E869AE@eusaamb107.ericsson.se>
From: Naveen Kottapalli <naveen.sarma@gmail.com>
Date: Wed, 31 Aug 2016 18:46:10 +0530
Message-ID: <CANFmOt=aOtxKeYd4Kf98NYW5WR89dj-3WchAdoZ0uh-wK4KKmw@mail.gmail.com>
Subject: Re: [v6ops] Is there any SLAAC equivalent for DHCPv6 Remote-Id option?
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c111de8d1bf30053b5de793
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xVvwLV8Zv4mEnc8-6uUrRczEGWM>
Cc: Erik Kline <ek@google.com>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 13:16:36 -0000

--94eb2c111de8d1bf30053b5de793
Content-Type: text/plain; charset=UTF-8

Thanks Suresh.  Will get back after exploring more.

Yours,
Naveen.

On 31 August 2016 at 18:16, Suresh Krishnan <suresh.krishnan@ericsson.com>
wrote:

> Hi Naveen,
>
> On 08/31/2016 06:59 AM, Naveen Kottapalli wrote:
> > Hello,
> >
> > As per section 7 of RFC 6788, Line-Identification option is encoded in
> below
> > format.
> >
> >     0                   1                   2                   3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >                                    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >                                    |  Option Type  | Option Length |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    | LineIDLen     |     Line ID...
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >                 Figure 4: Line-Identification Option Layout
> >
> >
> > Does the above layout mean that option type 0x8C will start at 2nd byte?
>
> The Option type 0x8c will be in the first byte (Byte 0) of the option. The
> IPv6 ND option formats are shown like this along with a alignment
> requirement
> to allow for proper encoding of multi-byte fields. In this particular case
> there is no alignment required.
>
> As for your other question upthread, I do not know of any implementations
> in
> WiFi APs. This option was primarily for Broadband Forum networks and AFAIK
> only BNGs and Access Nodes (e.g. DSLAMs) implemented it. If you are
> interested in using this for other purposes, please read Section 2 of the
> document to check if the issues mentioned there apply to your specific
> deployment scenario.
>
> Thanks
> Suresh
>
>
>

--94eb2c111de8d1bf30053b5de793
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Suresh.=C2=A0 Will get back after exploring more.</=
div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_s=
ignature" data-smartmail=3D"gmail_signature">Yours,<br>Naveen.</div></div>
<br><div class=3D"gmail_quote">On 31 August 2016 at 18:16, Suresh Krishnan =
<span dir=3D"ltr">&lt;<a href=3D"mailto:suresh.krishnan@ericsson.com" targe=
t=3D"_blank">suresh.krishnan@ericsson.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Hi Naveen,<br>
<span class=3D""><br>
On 08/31/2016 06:59 AM, Naveen Kottapalli wrote:<br>
&gt; Hello,<br>
&gt;<br>
&gt; As per section 7 of RFC 6788, Line-Identification option is encoded in=
 below<br>
&gt; format.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A03<br>
&gt;=C2=A0 =C2=A0 =C2=A00 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5=
 6 7 8 9 0 1<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-<wbr>+-+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 Option Type=
=C2=A0 | Option Length |<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-<wbr>+-+-+<br>
&gt;=C2=A0 =C2=A0 | LineIDLen=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0Line =
ID...<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-<wbr>+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-<wbr>+-+-+<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Figure 4:=
 Line-Identification Option Layout<br>
&gt;<br>
&gt;<br>
&gt; Does the above layout mean that option type 0x8C will start at 2nd byt=
e?<br>
<br>
</span>The Option type 0x8c will be in the first byte (Byte 0) of the optio=
n. The<br>
IPv6 ND option formats are shown like this along with a alignment requireme=
nt<br>
to allow for proper encoding of multi-byte fields. In this particular case<=
br>
there is no alignment required.<br>
<br>
As for your other question upthread, I do not know of any implementations i=
n<br>
WiFi APs. This option was primarily for Broadband Forum networks and AFAIK<=
br>
only BNGs and Access Nodes (e.g. DSLAMs) implemented it. If you are<br>
interested in using this for other purposes, please read Section 2 of the<b=
r>
document to check if the issues mentioned there apply to your specific<br>
deployment scenario.<br>
<br>
Thanks<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Suresh<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--94eb2c111de8d1bf30053b5de793--


From nobody Wed Aug 31 10:21:23 2016
Return-Path: <aretana@cisco.com>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0056D12D56C; Wed, 31 Aug 2016 10:21:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alvaro Retana" <aretana@cisco.com>
To: "The IESG" <iesg@ietf.org>
Subject: Alvaro Retana's No Objection on draft-ietf-6man-deprecate-atomfrag-generation-07: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147266408199.31928.12507097138433674273.idtracker@ietfa.amsl.com>
Date: Wed, 31 Aug 2016 10:21:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BIUVi9lO5XakrUK1bZkIAQyvydE>
Cc: "Robert M. Hinden" <bob.hinden@gmail.com>, ipv6@ietf.org, draft-ietf-6man-deprecate-atomfrag-generation@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 17:21:22 -0000

Alvaro Retana has entered the following ballot position for
draft-ietf-6man-deprecate-atomfrag-generation-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-6man-deprecate-atomfrag-generation/



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

I'm not going to stand in the way of publication, but I don't think we
need to publish this document: it already served it's purpose.  Evidence
of that is in RFC7915, rfc2460bis...



From nobody Wed Aug 31 13:32:07 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4815812D5BC for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 13:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LRiQyb4YhG_P for <ipv6@ietfa.amsl.com>; Wed, 31 Aug 2016 13:32:03 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (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 48C7912B03D for <6man@ietf.org>; Wed, 31 Aug 2016 13:32:03 -0700 (PDT)
Received: by mail-pa0-x22e.google.com with SMTP id fu3so14071494pad.3 for <6man@ietf.org>; Wed, 31 Aug 2016 13:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=QND4UOUqH4FJTVb2uKMvf/JfPQpVmHRDunBTr7DNs3U=; b=G5FDkFk/STUznhIfPL8fWuv05Betj5gHt5f6uraO+InnvBE72udrsExHseRkEqm9Xn ozqA0QgbANgFMOee2c/Cmcf5K1aBxXXlr1zcCFJcrieg87oS8UQW2ZAqAper0Bjh4c2F USDHtkNp1GbCjaRRhK01T8Tc/wm314TKxT8VZIDoOhNyFhkiAXMDS7LZ2z3JsTznjgFq aC2g/xe0SnRTIJ8rAoQPUWdx1Bnmj27Kkv+3Tg6OlWTrV0A+usPITJaTIXcNtW3cVznm sjXFihAfS6Xh1DSmDP8V5YP8R2uVk+nmGQ/Nc5LyuIGZBVbbhAvPz6a7MzrcG4KkAWeZ 4c/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=QND4UOUqH4FJTVb2uKMvf/JfPQpVmHRDunBTr7DNs3U=; b=Kfrhb5/2gJ4eNoXjKMjC6zJSFKGTt6/VFOTymCoCadTJ7XDECk306jWnksSaJmvbfI qgB1EiuEjCRCEbe7UKxFzCl4R/0bfsCRXONOcfkLmr8SQ/WtJ2WwPVPdlC0uFG9Q+pl7 bmPOY+Pt/eXYNQQHTQ6tW44VcfPRY88GAW6x2jaOpZMZUykFqGuvcIPZkfbWN0foOsYP a0fymILr2Q4tcSjA8Ij73XJhDvFc000fpda7BFee3cnfMYQotdpHWkz54qnOfsOaue2m bzBuuJML4IvxpodCYCyZXQSlg3ain9gG/VsDCHeChblpPV2jPcHXzLxGP5cz2wEYWaHH u0OQ==
X-Gm-Message-State: AE9vXwPHOoQGo96WkQdttXe92HdR0WlYwRp0SNicPR21M2NnePFoUV202fC/CAT+nA4tyA==
X-Received: by 10.66.134.36 with SMTP id ph4mr15279717pab.113.1472675522655; Wed, 31 Aug 2016 13:32:02 -0700 (PDT)
Received: from [192.168.178.23] ([118.148.76.42]) by smtp.gmail.com with ESMTPSA id q4sm1771529pfb.18.2016.08.31.13.31.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Aug 2016 13:32:01 -0700 (PDT)
Subject: Re: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc2460bis-05]
To: Tim Chown <Tim.Chown@jisc.ac.uk>, "huitema@huitema.net" <huitema@huitema.net>
References: <C75A2D0E-7808-4460-ABC0-AD612484663A@jisc.ac.uk> <C453AB9B-3FF4-4706-B5C2-8D747906C088@gmail.com> <a653fe9d-3290-3874-b2e5-298aa93e844e@gmail.com> <E1beqnb-0005Wh-7t@mx43.antispamcloud.com> <F5C4DCD9-002D-4767-9BCB-E7E4366E793D@jisc.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <e80cda24-7fed-42f0-92a0-a6507e8455f4@gmail.com>
Date: Thu, 1 Sep 2016 08:32:06 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <F5C4DCD9-002D-4767-9BCB-E7E4366E793D@jisc.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/0JFygslEyVix94M4UOPUCghy2uA>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Aug 2016 20:32:05 -0000

On 31/08/2016 20:30, Tim Chown wrote:
> On 30 Aug 2016, at 22:41, huitema@huitema.net<mailto:huitema@huitema.ne=
t> wrote:
>=20
> It is used in Teredo. The Teredo bubbles have no payload, hence set pay=
load type to 59.
>=20
> OK, thanks, that seems a reasonable generic use case, even if there=E2=80=
=99s only one example :)
>=20
> But given it=E2=80=99s not in RFC 7045, anyone kind enough to implement=
 the advice there won=E2=80=99t necessarily include header 59.

Actually it is mentioned in 7045 but intentionally not listed in the IANA=
 registry:
   "This list excludes type 59, No Next Header, [RFC2460], which is not
   an extension header as such."

Packets with "No Next Header" followed by additional bytes are allowed by=
 RFC2460,
but would be very suspect to any firewall, I would think.

    Brian

>=20
> Tim
>=20
> Sent from my Windows 10 phone
>=20
> From: Brian E Carpenter<mailto:brian.e.carpenter@gmail.com>
> Sent: Tuesday, August 30, 2016 1:40 PM
> To: Bob Hinden<mailto:bob.hinden@gmail.com>; Tim Chown<mailto:Tim.Chown=
@jisc.ac.uk>
> Cc: 6man@ietf.org<mailto:6man@ietf.org>
> Subject: Next Header value 59 [was Re: Review of draft-ietf-6man-rfc246=
0bis-05]
>=20
> On 31/08/2016 08:19, Bob Hinden wrote:
>=20
> ...
>>> p.22 is Next Header value 59 used in practice? (Just curious=E2=80=A6=
 it was omitted from RFC7045).
>>
>> I am not 100% sure, but think it is used.  But it is not something tha=
t has been updated.
>=20
> It's a curious case, but we didn't mention it in 7045 or ask IANA to in=
clude it in
> http://www.iana.org/assignments/ipv6-parameters/ipv6-parameters.xhtml#e=
xtension-header
> because, well, it isn't a header and doesn't require any processing. I =
think
> that's OK.
>=20
> Regards
>      Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org<mailto:ipv6@ietf.org>
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20

