
From nobody Mon May  2 13:38:45 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 ABF7D12D637 for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 13:38:43 -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 4FpZCVCM6A_t for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 13:38:41 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 BD2CE12B074 for <ipv6@ietf.org>; Mon,  2 May 2016 13:38:41 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id o66so305554156ywc.3 for <ipv6@ietf.org>; Mon, 02 May 2016 13:38:41 -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=2XHcDfM4sSoMscEKG1L9NY/B7qM56TXDX+pVmMRroL4=; b=vT8ubb86E6xY9ACC/2z9LKNxv9ARHSxUby82L5O7FzZVpq/n9/qr5Tp2AQOJEZbr/P EUL7fOxjHzW9rYcqjjIwrDQiEe8NUZSr+dSN5K1xZhaivSadT/gF8TWAb7GFNHn1yvli trxKeaIowrgkwY1mTOESSmFFiROx4JCx6m9/Ne5QZJ9S0OKVpGQY8AmWcx4St731qQTh TJqoqPQ3Uv5x2EPsvTLFI0Z3/YRcDVWjhsqYLqApT8oTPQL0PEipdP+vbAV9aiPcps4z Gj4FXLm5Z1ls1XDZmw/9NwtDHpOuSFFGiXFnCNRFHJyfkIYCyVwZ/0lEhNUoWyhziTgM kkeg==
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=2XHcDfM4sSoMscEKG1L9NY/B7qM56TXDX+pVmMRroL4=; b=HXhfTYsC/RH1fBkp4n+0eqhSWDYXyxewontnSezh/CUQiUsBvymot7H3hoRLN/TR8A k5YUazlDNEc4KqY9F805k4kkzKkpHxlLfPUwY0WonPv6C5pzG+qaIghiEWqenBu95ztP AWZH5qJmUzZD5QzYnu7tiiA36lEcoJXxylUgxRC4bUoLXYcURsch5iIWxVcLfb3nY1vH zS6usQyR0mu+7tLMF5zDFOSLIH+banxRMcgpGJWeGXTbI5LLrdEqGIkkk5f6bwhY5riv PZ2gM6UwCP3QBKfQYR9o+RyxfrFybSMRjmnY1Op6g392e+ItbEoylyj3W0MFrJP3ObXF Yx0A==
X-Gm-Message-State: AOPr4FW+k5WxG7GZHScbZCZ5BS4dE4Sd4VZddhcCa0hWps7Uya6MVxopqT/AaEADwajnKw==
X-Received: by 10.13.238.197 with SMTP id x188mr22837748ywe.265.1462221520720;  Mon, 02 May 2016 13:38:40 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id a199sm16236984ywe.30.2016.05.02.13.38.38 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 02 May 2016 13:38:38 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CFCF05F1-1142-4200-92C9-B0CDBA65853B"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <5722B3FA.1090707@si6networks.com>
Date: Mon, 2 May 2016 13:38:35 -0700
Message-Id: <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-AT8W9KfCoD3ZAmznKXJhNlDSDU>
Cc: 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: Mon, 02 May 2016 20:38:43 -0000

--Apple-Mail=_CFCF05F1-1142-4200-92C9-B0CDBA65853B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Based on the discussion, I think there is agreement to keep the text in =
the rfc2460bis -04 draft about not inserting extension headers.  I made =
a change to the second sentence regarding encapsulation based on the =
email discussion:

   Extension headers must never be inserted by any node other than the
   source of the packet.  One approach to meet a requirement to add
   extension headers is to use IP Encapsulation, for example, as defined
   in [RFC2473].

Please let me know if this is OK.

The other related proposed text regarding not deleting or changing the =
size of extension headers is:

   Extension headers must never be deleted or changed in size by any
   node on the path the packet takes.

   The contents of an Extension header or Option in an Extension header
   may be modified if this is permitted by the definition of the
   Extension header or option.

This was proposed earlier on the list.  I think it is consistent the =
prohibition against inserting extension headers.

Please comment.

Thanks,
Bob


> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>> On 29/04/2016 04:34, Fernando Gont wrote:
>>=20
>>> mmm... I guess you don't need ietf permission to violate the specs =
in
>>> your own walled garden?
>>=20
>> Since the protocol police have been very quiet recently, that is a =
fact of
>> life. However, if we want to be explicit about it (after 2460bis) we =
could
>> write it up.
>=20
> I fully agree. What I meant is: the fact that you could potentially =
make
> something work in a walled garden doesn't seem an argument to =
legitimize
> that behavior -- particularly when I guess we're supposed to be
> standarizing more for the general case than for the walled garden =
case.
>=20
>=20
>> Diffserv already allows domain-specific packet mutations; the
>> flow label tolerates mutations in certain circumstances. I don't see =
why
>> we couldn't also describe the circumstances in which other header =
mutations
>> are allowed. But first, define the precise meaning of "the open =
Internet."
>=20
> Have this mutations the same potential implications as the
> insertion/removal of EHs?
>=20
> Thanks,
>=20
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20


--Apple-Mail=_CFCF05F1-1142-4200-92C9-B0CDBA65853B
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

iQEcBAEBCgAGBQJXJ7rMAAoJEK7rdBF357uoe3MH/RqdzgGpnL7/bfVZslCQRM4q
13HlinIWSZuuzP8eYvmIyJKQFVFD7rLH35o8UKVLN30aVNlJDIPDyOEYe3lrR5L0
cQLvPO0BqAlmR4oF0GxexcDBFydjbM1OxKWQJGR7+lr/aSjMofc4bvYdsikI6Ni+
u8v4ONnZ13/f1mQdsOJbMEeFLT9kFKyr0L7ri733NMeHx0qUWm+cbd4IVoajQYGU
7M62+UtvL0iH6Pxj1gZQrmmh/zqVvkE7o4vf+Sr+HLmnh7Jcox0fthtkL9nH8V2d
PjbzMzguxfOmKXIKxq76cFSlm9Vtq/AMOic6EpV1XRkKGRr9MHJWQYPeCenC6gQ=
=19PS
-----END PGP SIGNATURE-----

--Apple-Mail=_CFCF05F1-1142-4200-92C9-B0CDBA65853B--


From nobody Mon May  2 15:37:33 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 78B3212D64A for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 15:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 okevylOeqfSZ for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 15:37:29 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::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 D3C2C12B01C for <ipv6@ietf.org>; Mon,  2 May 2016 15:37:28 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id c189so2981330vkb.3 for <ipv6@ietf.org>; Mon, 02 May 2016 15:37: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:date:message-id:subject:from:to :cc; bh=knjA3nYRkBJsfEbLN3MKKrLggvayUlXAhRupwKOpVew=; b=XAehZjb6Uleytko9vQbmjuEfpdIFRQZYpt2FLtXRv2hjs+i4PcHg220yTYWYIxQ8Y2 Ca4VS8/c8ESuUDcPC86WJs8mjO18k00bTPSvDcW2vfTD9j4Lgo6RjEr2S+JLomnHpu/b hbOa386L2jhCujBRI04ES7Ig4WOxgR9Vw+UBN9K2zHo1KM5PAByEkXD8rMH/f8S8OLNl zNdaOCVQZtAyO9V9z+DEx3/hQFeWPoekq895Wt31sAjOizcnX+0sv59W5oKcGi8asqBJ yHPK9+JGAAasbARRwX+VF48lXrgPt2qZwQpesSdaFe2A/OFbR+M7T5R9sQ+BHinb0iI0 WHjw==
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:date :message-id:subject:from:to:cc; bh=knjA3nYRkBJsfEbLN3MKKrLggvayUlXAhRupwKOpVew=; b=EfR1Uk+cQmCIyTvPNQ32QtazyTS6+ya+q8kJDr6hfT5RgrruIt5O2JuJOv1fwBxd97 cyJZfo0dKw2YYiZHWGzdiY/l9GaKs7u7eEfSREjG7MI/xj0xYoLrlqEn1J3l0LAuiC2q QKQekDiWsxtiIg9SXbkAB4Ct6FKfCJg/pleNOWqCcxkX0uLRBVz12cDe39t2hYj9I4nm cwcBG4KegmZqM7+ivvb9PtNLVo/KXwK+6+ip8UAFZAbS3GWMznmrxMWpRsQwYsoVgtHC MTAZfhyxnr/3dIoT7wb3MNoqI0bkYJicJ94LTLnl8plI+OX1rBH3Og91+MouUKzW6pWp 72Rw==
X-Gm-Message-State: AOPr4FUrQwRlKlh48T1rkerSqAil8PSCigvm4JMLFFnVX2MvguB5cfGCq9/0N5E94yaY4ApMHkk0wveihQD+Kw==
MIME-Version: 1.0
X-Received: by 10.31.163.3 with SMTP id m3mr933172vke.44.1462228647895; Mon, 02 May 2016 15:37:27 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Mon, 2 May 2016 15:37:27 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Mon, 2 May 2016 15:37:27 -0700 (PDT)
In-Reply-To: <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
Date: Tue, 3 May 2016 08:37:27 +1000
Message-ID: <CAO42Z2zovzjBpPzs+sp-38kDWJZk5widU2DNDKirfYFc2uBkPQ@mail.gmail.com>
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
From: Mark Smith <markzzzsmith@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=001a1142d8ca2369d70531e3a3ac
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oMdwbK2xYWOLqOwVUWpNqtgeOwc>
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, 02 May 2016 22:37:31 -0000

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

Hi Bob,

On 3 May 2016 6:38 AM, "Bob Hinden" <bob.hinden@gmail.com> wrote:
>
> Based on the discussion, I think there is agreement to keep the text in
the rfc2460bis -04 draft about not inserting extension headers.  I made a
change to the second sentence regarding encapsulation based on the email
discussion:
>
>    Extension headers must never be inserted by any node other than the
>    source of the packet.  One approach to meet a requirement to add
>    extension headers is to use IP Encapsulation, for example, as defined
>    in [RFC2473].
>

+1

> Please let me know if this is OK.
>
> The other related proposed text regarding not deleting or changing the
size of extension headers is:
>
>    Extension headers must never be deleted or changed in size by any
>    node on the path the packet takes.
>

+1

>    The contents of an Extension header or Option in an Extension header
>    may be modified if this is permitted by the definition of the
>    Extension header or option.
>

The thing I would criticise about this text is that it would not discourage
silent and unattributable changes.

I think change can create opportunities for failure, so having change
attributed to the router that makes them is preferable because it can help
identify the failing router. If silent changes can be allowed, I think the
principle should be to try to minimise when they're allowed. Ideally they
should be now limited and left to hop count, traffic class and flow label.

Routing Header type 0 was a good example of how an EH could be changed in
flight as it is possible to work out which router made the last change to
the RH EH. Is it possible to use that as an example of how to do
attributable EH modifications, while pointing out that it was deprecated
because its function could be abused, rather than anything being wrong with
the EH processing being performed?

Regards,
Mark.

> This was proposed earlier on the list.  I think it is consistent the
prohibition against inserting extension headers.
>
> Please comment.
>
> Thanks,
> Bob
>
>
> > On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com>
wrote:
> >
> > On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
> >> On 29/04/2016 04:34, Fernando Gont wrote:
> >>
> >>> mmm... I guess you don't need ietf permission to violate the specs in
> >>> your own walled garden?
> >>
> >> Since the protocol police have been very quiet recently, that is a
fact of
> >> life. However, if we want to be explicit about it (after 2460bis) we
could
> >> write it up.
> >
> > I fully agree. What I meant is: the fact that you could potentially make
> > something work in a walled garden doesn't seem an argument to legitimize
> > that behavior -- particularly when I guess we're supposed to be
> > standarizing more for the general case than for the walled garden case.
> >
> >
> >> Diffserv already allows domain-specific packet mutations; the
> >> flow label tolerates mutations in certain circumstances. I don't see
why
> >> we couldn't also describe the circumstances in which other header
mutations
> >> are allowed. But first, define the precise meaning of "the open
Internet."
> >
> > Have this mutations the same potential implications as the
> > insertion/removal of EHs?
> >
> > 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
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr">Hi Bob,</p>
<p dir=3D"ltr">On 3 May 2016 6:38 AM, &quot;Bob Hinden&quot; &lt;<a href=3D=
"mailto:bob.hinden@gmail.com">bob.hinden@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Based on the discussion, I think there is agreement to keep the text i=
n the rfc2460bis -04 draft about not inserting extension headers.=C2=A0 I m=
ade a change to the second sentence regarding encapsulation based on the em=
ail discussion:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0Extension headers must never be inserted by any node othe=
r than the<br>
&gt; =C2=A0 =C2=A0source of the packet.=C2=A0 One approach to meet a requir=
ement to add<br>
&gt; =C2=A0 =C2=A0extension headers is to use IP Encapsulation, for example=
, as defined<br>
&gt; =C2=A0 =C2=A0in [RFC2473].<br>
&gt;</p>
<p dir=3D"ltr">+1</p>
<p dir=3D"ltr">&gt; Please let me know if this is OK.<br>
&gt;<br>
&gt; The other related proposed text regarding not deleting or changing the=
 size of extension headers is:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0Extension headers must never be deleted or changed in siz=
e by any<br>
&gt; =C2=A0 =C2=A0node on the path the packet takes.<br>
&gt;</p>
<p dir=3D"ltr">+1</p>
<p dir=3D"ltr">&gt; =C2=A0 =C2=A0The contents of an Extension header or Opt=
ion in an Extension header<br>
&gt; =C2=A0 =C2=A0may be modified if this is permitted by the definition of=
 the<br>
&gt; =C2=A0 =C2=A0Extension header or option.<br>
&gt;</p>
<p dir=3D"ltr">The thing I would criticise about this text is that it would=
 not discourage silent and unattributable changes. </p>
<p dir=3D"ltr">I think change can create opportunities for failure, so havi=
ng change attributed to the router that makes them is preferable because it=
 can help identify the failing router. If silent changes can be allowed, I =
think the principle should be to try to minimise when they&#39;re allowed. =
Ideally they should be now limited and left to hop count, traffic class and=
 flow label.</p>
<p dir=3D"ltr">Routing Header type 0 was a good example of how an EH could =
be changed in flight as it is possible to work out which router made the la=
st change to the RH EH. Is it possible to use that as an example of how to =
do attributable EH modifications, while pointing out that it was deprecated=
 because its function could be abused, rather than anything being wrong wit=
h the EH processing being performed?</p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; This was proposed earlier on the list.=C2=A0 I think it=
 is consistent the prohibition against inserting extension headers.<br>
&gt;<br>
&gt; Please comment.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Bob<br>
&gt;<br>
&gt;<br>
&gt; &gt; On Apr 28, 2016, at 6:08 PM, Fernando Gont &lt;<a href=3D"mailto:=
fgont@si6networks.com">fgont@si6networks.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; On 04/28/2016 09:37 PM, Brian E Carpenter wrote:<br>
&gt; &gt;&gt; On 29/04/2016 04:34, Fernando Gont wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; mmm... I guess you don&#39;t need ietf permission to viol=
ate the specs in<br>
&gt; &gt;&gt;&gt; your own walled garden?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Since the protocol police have been very quiet recently, that=
 is a fact of<br>
&gt; &gt;&gt; life. However, if we want to be explicit about it (after 2460=
bis) we could<br>
&gt; &gt;&gt; write it up.<br>
&gt; &gt;<br>
&gt; &gt; I fully agree. What I meant is: the fact that you could potential=
ly make<br>
&gt; &gt; something work in a walled garden doesn&#39;t seem an argument to=
 legitimize<br>
&gt; &gt; that behavior -- particularly when I guess we&#39;re supposed to =
be<br>
&gt; &gt; standarizing more for the general case than for the walled garden=
 case.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; Diffserv already allows domain-specific packet mutations; the=
<br>
&gt; &gt;&gt; flow label tolerates mutations in certain circumstances. I do=
n&#39;t see why<br>
&gt; &gt;&gt; we couldn&#39;t also describe the circumstances in which othe=
r header mutations<br>
&gt; &gt;&gt; are allowed. But first, define the precise meaning of &quot;t=
he open Internet.&quot;<br>
&gt; &gt;<br>
&gt; &gt; Have this mutations the same potential implications as the<br>
&gt; &gt; insertion/removal of EHs?<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Fernando Gont<br>
&gt; &gt; SI6 Networks<br>
&gt; &gt; e-mail: <a href=3D"mailto:fgont@si6networks.com">fgont@si6network=
s.com</a><br>
&gt; &gt; PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 749=
2<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &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>
&gt;<br>
</p>

--001a1142d8ca2369d70531e3a3ac--


From nobody Mon May  2 16:58:59 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 073C012D533 for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 16:58:58 -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 dmUSQJ7xHxyB for <ipv6@ietfa.amsl.com>; Mon,  2 May 2016 16:58:56 -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 6067612D538 for <ipv6@ietf.org>; Mon,  2 May 2016 16:58:56 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id r5so1897309pag.1 for <ipv6@ietf.org>; Mon, 02 May 2016 16: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=55vV0KcggR9/AqL0+qiR3wFv29t2adDxX8u3SLXosbQ=; b=zGEhlYU67JrTVaO3pgKen8NR63VNpRUVpCz8XqL6ZXVR26tRISW2u7ox1NDtBEcxIi 8ps1PtC67q9aEJc8hrD5ouZKHpTDZRlTqvQsE/U9pRO4ji8tbq561xCpva17QttCgv7A edfTVb20glwwB5moYYfAqV7LfuPh3CgLegNUPUbsYi2uvSWksShkcYbt5XMxZbM8wA1k oo/yW8GGVCpbgW9451liGa8yRKcGOhHqdF+/XyDsf97Sebe5PHX7ZFArJJtHteq3sxnh FnS4PoOOrB4+HJd7e9ull8hP7gyVjeY4VvFhl+7bzruOBwewq49hVXwPhoDCkw8dHVQw FR5Q==
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=55vV0KcggR9/AqL0+qiR3wFv29t2adDxX8u3SLXosbQ=; b=jJT+zA+v8TVbOtE/mmyqdzGgTvEOoIa9Suuqf6aHqvjsfYfJlefJpmE5sMcZdQdOiq 1Wc73/vS49ZPG++Wuf/OoPZw13mITpKfIXvnu+5eFY1T49hHUejTZQwnJ5B8SJpO5np/ 3hylw9zHPxdQVcU/8eklRwEAWp+qvpyETXYyPz/Lfc0B94zcKXiRQ8ZcyzyN0gnGHfBm MjTQYUDe9oLf2ot2kGmAUu3axW8HhdG1Gc1dQewP3vNeRm81ADTBueJB7p9ii29yJ7aV yOpyqJ3aCDtJ7Hd3g6tMKLSRNsYp8aRBTRoAvG+0U8bp4KfNvefLhWUapXonXXaVz5tE rKhA==
X-Gm-Message-State: AOPr4FXjwR6uvnRBEJVc2nVWIbyWib8N8DSUzSfbvvNhBNfamucUHFSZCfE4EOu1TjSqKw==
X-Received: by 10.66.166.207 with SMTP id zi15mr25289731pab.21.1462233536029;  Mon, 02 May 2016 16:58:56 -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 b140sm575872pfb.19.2016.05.02.16.58.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 02 May 2016 16:58:54 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Mark Smith <markzzzsmith@gmail.com>, Bob Hinden <bob.hinden@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <CAO42Z2zovzjBpPzs+sp-38kDWJZk5widU2DNDKirfYFc2uBkPQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <71e44c36-031e-3304-4b5d-2cd707351ce2@gmail.com>
Date: Tue, 3 May 2016 11:58:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2zovzjBpPzs+sp-38kDWJZk5widU2DNDKirfYFc2uBkPQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vW_kNKsrjYyj56cjLV2MhsoXEwI>
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, 02 May 2016 23:58:58 -0000

On 03/05/2016 10:37, Mark Smith wrote:
...
>>    The contents of an Extension header or Option in an Extension header
>>    may be modified if this is permitted by the definition of the
>>    Extension header or option.
>>
> 
> The thing I would criticise about this text is that it would not discourage
> silent and unattributable changes.

The sentence is actually a no-op anyway; it really states the obvious.
A slightly stronger version would be:

 The contents of an Extension header or Option in an Extension header
 must not be modified unless this is permitted by the definition of the
 Extension header or option.

but I am not sure that is a clarification of RFC 2460; it seems a
bit like a new rule.

     Brian


From nobody Wed May  4 08:12:42 2016
Return-Path: <cbowers@juniper.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 97EDF12D713; Wed,  4 May 2016 08:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-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=junipernetworks.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 biZcV6LSuhjr; Wed,  4 May 2016 08:12:29 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0102.outbound.protection.outlook.com [65.55.169.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C39C12D714; Wed,  4 May 2016 08:11:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=w7ie00ptq+2hUMZ9UCV/oDV2oKA1ovdUmKLWn7n5raU=; b=gNSw6/xthvUsZRIzXoecB31GyhJEd5X+wq2CV8K7lP2Nw9huNwC1GRZA8VmwoVz6dHrvPPXs8TOX/MHauW4ZaySIh/AStjBr/Kz/5cAwhGAzKChXYzNf8WKXW8jHZs3yT/HE7IaSK7xFy7wVcPYDirHJZH9pOoDkqJRd8oNk6/4=
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com (10.160.35.143) by BLUPR0501MB1043.namprd05.prod.outlook.com (10.160.35.142) with Microsoft SMTP Server (TLS) id 15.1.477.8; Wed, 4 May 2016 15:10:58 +0000
Received: from BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) by BLUPR0501MB1044.namprd05.prod.outlook.com ([10.160.35.143]) with mapi id 15.01.0477.016; Wed, 4 May 2016 15:10:58 +0000
From: Chris Bowers <cbowers@juniper.net>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RTGWG Virtual Interim Meeting: May 31, 2016
Thread-Topic: RTGWG Virtual Interim Meeting: May 31, 2016
Thread-Index: AdGlkFH1140hKmcyTVCsepgcooS0Tw==
Date: Wed, 4 May 2016 15:10:58 +0000
Message-ID: <BLUPR0501MB104486BB670240E97CD18976A97B0@BLUPR0501MB1044.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.239.11]
x-ms-office365-filtering-correlation-id: 8cc861f5-964e-4640-37d9-08d3742e4c3b
x-microsoft-exchange-diagnostics: 1; BLUPR0501MB1043; 5:CitYsA2hzdNmJAdwkSrAbXXA/NLZEaM/KCdoPH5iG4QEhtSjRXcd818zmReb6J7wOEl5NGwF2oM2RBl037DF8Ll0gESF9K3JvObglTTmWMvMwtWr2/Lg0ZX4EsA1IaBhNgxSBiwByNB9uyD1puyvTg==; 24:oBzdpuZlsaHSujzxPwkIdjcE27S+u1/rlAH3puQM4Ccf9SuF7VrS9AhJ68e9wxYZOwNqjjCKX2CFrOTRRjb43KbMAZcu0d/V5JF/iJXZQqM=; 7:LNZuBFVWAA2PMJiTzKeMQAYc1WALI2pfmyb7dQ954qZEDBxSlAeFGbTPODZAJKr82VD1GO0mFpoUO5Y9wN385n8er12yXu8vVBs7/jCqOr0MLoj9zpV6yT+gp/snX3ibhl31v4SogLBsuCTDARTtpNx06255LHrcmXD2TbzFMXB3N67HWXsii7OnPuX3Na+3
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB1043;
x-microsoft-antispam-prvs: <BLUPR0501MB104335A96BE36AFF63D4EDD9A97B0@BLUPR0501MB1043.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521098)(9101528026)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026); SRVR:BLUPR0501MB1043; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0501MB1043; 
x-forefront-prvs: 093290AD39
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(243025005)(377454003)(9686002)(77096005)(551544002)(3846002)(102836003)(50986999)(6116002)(74316001)(81166005)(4326007)(11100500001)(229853001)(5002640100001)(87936001)(1220700001)(10400500002)(5003600100002)(8936002)(5008740100001)(15975445007)(3480700004)(122556002)(92566002)(76576001)(16799955002)(86362001)(2201001)(2900100001)(2906002)(450100001)(19580395003)(2501003)(586003)(99286002)(3660700001)(19580405001)(5004730100002)(5001770100001)(3280700002)(33656002)(189998001)(66066001)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0501MB1043; H:BLUPR0501MB1044.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 May 2016 15:10:58.4232 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB1043
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4VAvq4prZIyn6tm-_ffTjMkQoB8>
Cc: "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtgwg-ads@ietf.org" <rtgwg-ads@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, 04 May 2016 15:12:35 -0000

RTGWG,=20

RTGWG will hold a virtual interim meeting on Tuesday May 31, 2016 from=20
10:00-12:00 Eastern Daylight Time (14:00-16:00 UTC).=20

The virtual interim will focus on the problem of ipv6 multi-homing with=20
provider-assigned addressing without NAT, and a proposed solution for=20
this problem, destination/source routing.=20

We have contacted several potential presenters based on the discussion=20
of this topic in Buenos Aires and on the RTGWG list and in v6ops. If you=20
are interested in presenting at this virtual interim and we have not=20
already contacted you, please contact us at rtgwg-chairs@ietf.org. We=20
are particularly interested in hearing from enterprises and service=20
providers, who are the ones affected by this problem and would need to=20
deploy and operate any solution we come up with.=20

A detailed agenda will be posted to the rtgwg mailing list at least a=20
week before the meeting.

This initial announcement is being posted to rtgwg, v6ops, homenet,=20
6man, and routing-discussion mailing lists. We only plan to post=20
follow-up email related to this virtual interim to the rtgwg list, so=20
please subscribe to the rtgwg mailing list if you are interested in=20
following this.

The WebEx details are as follows:

RTGWG Virtual Interim Meeting=20
Tuesday, May 31, 2016=20
10:00 am  |  Eastern Daylight Time (New York, GMT-04:00)  |  2 hrs=20

Meeting link:
https://ietf.webex.com/ietf/j.php?MTID=3Dma9394d256b2331260bd5416dc08fb5bd

Meeting number: 648 728 108=20
Meeting password:interim1

Join by phone (US/Canada): 1-650-479-3208

International dial-in (PDF):=20
<http://www.webex.com/pdf/tollfree_restrictions.pdf>

Thanks,
Chris and Jeff


From nobody Wed May  4 14:46:46 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 E45C312D8C8 for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:46:44 -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 1g7XIsxGPrAG for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:46: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 C9D5612D5FD for <ipv6@ietf.org>; Wed,  4 May 2016 14:46:40 -0700 (PDT)
Received: from [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f] (unknown [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f]) (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 A8289801CD; Wed,  4 May 2016 23:46:35 +0200 (CEST)
Subject: Re: when Inserting Extension Headers
To: Michael Richardson <mcr+ietf@sandelman.ca>, 6man WG <ipv6@ietf.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <12014.1461868866@obiwan.sandelman.ca> <CAO42Z2xShXYX=4Yso1unxUSbvaVKSczo0NyoiPnbcJ3qvsGHpg@mail.gmail.com> <11019.1461949709@obiwan.sandelman.ca>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <572A5D35.4030507@si6networks.com>
Date: Wed, 4 May 2016 17:36:05 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <11019.1461949709@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sfq7wlpMLafPtRLkjluLQDIrZf0>
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, 04 May 2016 21:46:45 -0000

On 04/29/2016 02:08 PM, Michael Richardson wrote:
> 
> (I'd love to also change the behaviour of AH so that one would ignore AH
> headers if one hasn't got a matching SPI#. That's what kept us from using AH
> to secure ND back in the SEND days)

Then, what's the point of doing AH, anyway?



> And, it seems that "10", which creates ICMP Parameter Problem messages
> for multicast destinations, allows for amplication attacks, and we should
> deprecate that behaviour, period.

Agreed:
<https://www.ietf.org/archive/id/draft-gont-6man-ipv6-smurf-amplifier-03.txt>

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





From nobody Wed May  4 14:46:50 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 D506A12D8C8 for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:46:46 -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 NHc3KL98cLmP for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:46:45 -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 29BB112D5FD for <ipv6@ietf.org>; Wed,  4 May 2016 14:46:45 -0700 (PDT)
Received: from [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f] (unknown [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f]) (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 7114A801E3; Wed,  4 May 2016 23:46:41 +0200 (CEST)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Mark Smith <markzzzsmith@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <12014.1461868866@obiwan.sandelman.ca> <CAO42Z2xShXYX=4Yso1unxUSbvaVKSczo0NyoiPnbcJ3qvsGHpg@mail.gmail.com> <4af9c8a2c9c843f9a68f4d10e4c7fa5d@XCH-RCD-001.cisco.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <572A6D70.2080601@si6networks.com>
Date: Wed, 4 May 2016 18:45:20 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <4af9c8a2c9c843f9a68f4d10e4c7fa5d@XCH-RCD-001.cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/udT0D1LGVCQlBX54GuGw81zOx7A>
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, 04 May 2016 21:46:47 -0000

On 04/29/2016 04:05 PM, Pascal Thubert (pthubert) wrote:
> Hello Mark:
> 
> Ø  4) troubleshooting modifications that cannot or cannot easily be
> attributed to a specific node can be very time-consuming, require out of
> hours work and are likely to require potentially disruptive packet
> capturing within or downstream of each network element that could have
> modified the packet (assuming it is possible to access that NE or link).
> 
> DetNet has the concept of Replication and Elimination, which created
> intermediate sources and sinks, and certainly observed that need.

I think the original question was different.

The original question was whether inserting headers is part of RFC2460,
and whether it makes sense to clarify this.

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





From nobody Wed May  4 14:58: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 7D17312D905 for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:58:50 -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 dQuOMhgKsQ8P for <ipv6@ietfa.amsl.com>; Wed,  4 May 2016 14:58:49 -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 2D7BB12D901 for <ipv6@ietf.org>; Wed,  4 May 2016 14:58:48 -0700 (PDT)
Received: from [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f] (unknown [IPv6:2001:13c7:7003:100:4082:5d48:1083:98f]) (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 9DB0C801C5; Wed,  4 May 2016 23:58:39 +0200 (CEST)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <572A6E0A.6030609@si6networks.com>
Date: Wed, 4 May 2016 18:47:54 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NpSVWOyXrKcy_hk7C67WqaW6h3g>
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, 04 May 2016 21:58:50 -0000

On 05/02/2016 05:38 PM, Bob Hinden wrote:
> Based on the discussion, I think there is agreement to keep the text in the rfc2460bis -04 draft about not inserting extension headers.  I made a change to the second sentence regarding encapsulation based on the email discussion:
> 
>    Extension headers must never be inserted by any node other than the
>    source of the packet.  One approach to meet a requirement to add
>    extension headers is to use IP Encapsulation, for example, as defined
>    in [RFC2473].
> 
> Please let me know if this is OK.

I think the original text was even clearer. Put another way:
encapsulation is the only rfc2460-compliant way to add EHs.



> The other related proposed text regarding not deleting or changing the size of extension headers is:
> 
>    Extension headers must never be deleted or changed in size by any
>    node on the path the packet takes.
> 
>    The contents of an Extension header or Option in an Extension header
>    may be modified if this is permitted by the definition of the
>    Extension header or option.

Looks good.

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





From nobody Thu May  5 09:31:24 2016
Return-Path: <rbonica@juniper.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 5CFFA12D0E6 for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 09:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.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 DWSIhXR6rPMb for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 09:31:20 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0794.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:794]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5588D12B03E for <6man@ietf.org>; Thu,  5 May 2016 09:31:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=QAzjOuYoo+l0FnOEU8LLGz3im9BrSRH/waV48ScEZWw=; b=Nch2OpugqtL2+9OhEUk3to06P9EH8iwu0TnMQESkQABTOZJ+Uw42ALxydtF8Ltf0j1ee8KuROwixr38ZbVUjy4PTgF62wbItRnbziC1EvkvsDJVB9QPZlzJX/K/eRbxQ5fLpWQ1ROsEtbAGk7L+fDCCAZdBeiKjglp2gls/s8hQ=
Received: from BLUPR05MB1985.namprd05.prod.outlook.com (10.162.224.27) by BLUPR05MB1987.namprd05.prod.outlook.com (10.162.224.29) with Microsoft SMTP Server (TLS) id 15.1.485.9; Thu, 5 May 2016 16:31:02 +0000
Received: from BLUPR05MB1985.namprd05.prod.outlook.com ([10.162.224.27]) by BLUPR05MB1985.namprd05.prod.outlook.com ([10.162.224.27]) with mapi id 15.01.0485.011; Thu, 5 May 2016 16:31:02 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "6man@ietf.org" <6man@ietf.org>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: draft-ietf-6man-segment-routing-header-01
Thread-Topic: draft-ietf-6man-segment-routing-header-01
Thread-Index: AdGm5nLT9DFCNkt9SweF+/9sQdP8yA==
Date: Thu, 5 May 2016 16:31:02 +0000
Message-ID: <BLUPR05MB19856AEFD77BD9C4A9F618F2AE7C0@BLUPR05MB1985.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.241.14]
x-ms-office365-filtering-correlation-id: 6f166777-754e-4d92-3a79-08d37502a5cd
x-microsoft-exchange-diagnostics: 1; BLUPR05MB1987; 5:Q4ezEv3tJj/qLpb1zJpl3spL4WgoVjjQ6IBBuCmlnRFOSCa4hPD/HCoIpUywbaLMWix/Y/3CdYYCheHa8WQ3niXlmVDH3jVdXDMqCyyiPYgF5y/lILqmjLjWS8ia0igv83JZSB4pLsekjCt59ns8RA==; 24:IwuyOZvlC5iXclT8WspmHLwmtK+glWmvOuk0WBM9xwhdsuB0yXVVKqq8hSqYttU7lcIxyiFi7zaI8J2tZglzVu61IjU7DIZOVqcoNGGJHwY=; 7:C7gG8BdFr4z7yVn+ZPpRTo/2K9MlBziY0iIbLjTjsWzEQ+l5Fm+Zhpb7F17CEGTxiAqrLkT3K8u8P13FNQZxKcqFlSICMHz1eGKVqy+6ziNBoJzFYGxtQqIxEJUMivnKKvvy9xW3nKqUfk0bOoBHhOTyKvuUWlme8kgRoeLGTnP/JXpPomjgGTczC5VlyX7q
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB1987;
x-microsoft-antispam-prvs: <BLUPR05MB1987A2F139EEF65DFCB4862FAE7C0@BLUPR05MB1987.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(9101521098)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026); SRVR:BLUPR05MB1987; BCL:0; PCL:0; RULEID:; SRVR:BLUPR05MB1987; 
x-forefront-prvs: 0933E9FD8D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(2900100001)(229853001)(33656002)(230783001)(10400500002)(92566002)(5004730100002)(77096005)(5003600100002)(122556002)(11100500001)(5001770100001)(2501003)(107886002)(5002640100001)(189998001)(54356999)(1220700001)(3846002)(102836003)(6116002)(76576001)(86362001)(99286002)(586003)(87936001)(50986999)(66066001)(2906002)(74316001)(3280700002)(5008740100001)(81166005)(9686002)(8936002)(31430400001)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB1987; H:BLUPR05MB1985.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 May 2016 16:31:02.0665 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB1987
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/VwC6ZUnTINizg-ZfQvI5tgQeWm8>
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, 05 May 2016 16:31:22 -0000

Stephano,

Sections 1 and 2 of draft-ietf-6man-segment-routing-header-01 are, for the =
most part, redundant with text that can be found in draft-ietf-spring-segme=
nt-routing-07.  Please consider replacing those four pages of text with the=
 short paragraphs provided below

                                                                    Ron Bon=
ica


PROPOSED TEXT
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Segment Routing (SR) [I-D.ietf-spring-segment-routing] specifies procedures=
 through which an upstream node can determine that path that a packet trave=
rses on route to its destination. In segment routing, a path is defined as =
a list of segments. In order to determine the path that a packet traverse o=
n route to its destination, the upstream node adds a list of segments to th=
e packet. Downstream nodes steer the packet along the segments that are spe=
cified in the list.

SR relies on control and forwarding plane components. See [draft-ietf-isis-=
segment-routing-extensions] and [draft-ietf-ospf-ospfv3-segment-routing-ext=
ensions] for a description of control plane components.

On the forwarding plane, SR can be instantiated by MPLS or IPv6. When SR is=
 instantiated by MPLS, the segment list is represented as an MPLS label sta=
ck. See [draft-ietf-spring-segment-routing-mpls] for details. When SR is in=
stantiated by IPv6, the segment list is contained by a new IPv6 Routing Hea=
der, called the Segment Routing Header (SRH). This document defines the SRH=
.

The scope of this document is limitted to the SR forwarding plane as it is =
instantiated by IPv6. Control plane topics are beyond the scope of this doc=
ument.


From nobody Thu May  5 17:12:51 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 A79A012D14E for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 17:12:49 -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 0xxAuE8ybyc8 for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 17:12:47 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 3B8CA12D118 for <ipv6@ietf.org>; Thu,  5 May 2016 17:12:47 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id t10so172890429ywa.0 for <ipv6@ietf.org>; Thu, 05 May 2016 17:12: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=NgkJ/ZTB1eZl78yS60iefdmLDTbwA6j+o5MsVlc+91c=; b=0V3q0y5HKfioSB1lmT4UZ/ENCB6uI8+C5mzeCt5zxT+96Kubq48/BoBzsSihqzXu+1 OB7EoXzhuLz93XBvPQct4aAtsspSGRY9e7+iiujGRi2khrrYJ/jRGd3mL5VCxB+zU4Jc UFAu3qjnlkDt4w/GtAv8P+NJFDmyGIQ/tPJlNRCfJK5UuEJ1se403BEsgoWe6kI48XDl gJogbEvcKB3ZmvmM3ywiwtij5LoIdq2dOtblykipDFTNlHDk1gabeJSLxss21dYL80gx K94M4tobozbBezEmpN0iSLPKm6IJgr91ak1zcns+3KpV++bqqJTwNK/e6ZolZAgMUdsI Hu0Q==
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=NgkJ/ZTB1eZl78yS60iefdmLDTbwA6j+o5MsVlc+91c=; b=bX40EtStF/OjesY/F0IB4/PqX3eoIWT0sOAn+JkX5/WLIyTBOqv7VoyZDSQPfSzth+ 7rVm7WDkF3G3I9Yxy+BOj2GWt5V5xQqgdapO4fqbe/0wXyNaZj8OZDKF7OISdhQxkP/l c1OqB/HQKUYDFZ+bHaG1p13bpYoPGk37AAZxzjqmR+WBpMxEr1WA3A9KoY6hI9WMCfMc zhFrvKcF1OtfJ+oLZZMbPsxMfKOQYAGt2mPxLemge5jzLW2WN2lBNzwrChTOAwHAOkC/ k3z2auChSDKukFD/DlMKi0Z+OU003u+rvqf/agLpSJk9EYrZT37l4QykJBq73NO2yt68 XuWA==
X-Gm-Message-State: AOPr4FW9WhLVMp6e3RijBkj3F1ZLOfrJFgrP3L9N9AxXY88i7tIhuYwwAExF/z9erFHC+Q==
X-Received: by 10.129.128.199 with SMTP id q190mr4388888ywf.319.1462493566565;  Thu, 05 May 2016 17:12:46 -0700 (PDT)
Received: from [10.0.0.24] (c-71-202-18-198.hsd1.ca.comcast.net. [71.202.18.198]) by smtp.gmail.com with ESMTPSA id z20sm7203850ywd.44.2016.05.05.17.12.44 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 05 May 2016 17:12:45 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_603FA054-F36C-41C7-9598-64A2B33D45F7"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <71e44c36-031e-3304-4b5d-2cd707351ce2@gmail.com>
Date: Thu, 5 May 2016 17:12:42 -0700
Message-Id: <D3355E7D-F3C5-43C4-B601-0E2379C30F65@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <CAO42Z2zovzjBpPzs+sp-38kDWJZk5widU2DNDKirfYFc2uBkPQ@mail.gmail.com> <71e44c36-031e-3304-4b5d-2cd707351ce2@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GozNbDbomE7UwhFwM8C9wt5_e4s>
Cc: IPv6 List <ipv6@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: Fri, 06 May 2016 00:12:50 -0000

--Apple-Mail=_603FA054-F36C-41C7-9598-64A2B33D45F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Brian,

> On May 2, 2016, at 4:58 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 03/05/2016 10:37, Mark Smith wrote:
> ...
>>>   The contents of an Extension header or Option in an Extension =
header
>>>   may be modified if this is permitted by the definition of the
>>>   Extension header or option.
>>>=20
>>=20
>> The thing I would criticise about this text is that it would not =
discourage
>> silent and unattributable changes.
>=20
> The sentence is actually a no-op anyway; it really states the obvious.
> A slightly stronger version would be:
>=20
> The contents of an Extension header or Option in an Extension header
> must not be modified unless this is permitted by the definition of the
> Extension header or option.

Since we do allow Extension headers and Options to be modified, I have a =
slight preference for the previous text.  It is, as you say=E2=80=9D =
stating the obvious.  Seems like saying this here, right after the text =
about inserting and deleting, makes sense.

Thanks,
Bob

>=20
> but I am not sure that is a clarification of RFC 2460; it seems a
> bit like a new rule.
>=20
>     Brian


--Apple-Mail=_603FA054-F36C-41C7-9598-64A2B33D45F7
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

iQEcBAEBCgAGBQJXK+F6AAoJEK7rdBF357uoEJwIALMvZCwo9iHEOvr6kmpX+VUs
erKz6aTGFJIfcikLfnm5hexfY9TelgVveksKWkO3aDQG3sCTvIQjZ1K9yjsOKaT1
OVw6NxMHB5B80jmcABmpovETc+PRFnugNOxVI7TpyIJgA/+hnaTwEinbbsQHlItY
h25i3cQMLB3/schi3hzpFy3WCqlHBPYKs9H/nZZ1EpfNqPm2JqcJi5FhuBqKckgA
fOzYyT/Y5FRy1gm82DLUdP/UIzN5DuAwzMaC8A1cCetS75vJpMRT/nIonDRjCPQu
jR+hiIdLSzRCR/clwldB/KJIUh3HPiINMdHtmaqmmpifIcz1Xw9GqbVq7KP2Qcs=
=UYr9
-----END PGP SIGNATURE-----

--Apple-Mail=_603FA054-F36C-41C7-9598-64A2B33D45F7--


From nobody Thu May  5 17:18: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 2C97C12D17B for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 17:18:10 -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 wg7inx_bzGBB for <ipv6@ietfa.amsl.com>; Thu,  5 May 2016 17:18:07 -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 0E78312B033 for <ipv6@ietf.org>; Thu,  5 May 2016 17:18:07 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id xk12so41410361pac.0 for <ipv6@ietf.org>; Thu, 05 May 2016 17:18: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=/WihR3BE8eHPYZC8Q3v1OK11jhaH20JgFWYcTQc7r78=; b=pofIRC9x1DNiH31r2UGAD7F7hfn8dQvU2+GaKjBRL91a9yDMj7l20AmbAHlopEtXl/ JCcVhRSUHEwdU87dJKSg279St1whszTvqDX21pmHYRcq5aPPOQogaysP9+miXplQTKO4 ZGPGUGEGPgzjB8z8YVNNi/FgTg3KEg5by7360Kd11xoBL1tIk5oUwm6FxLdpVR1bZvA8 OJuEqfPGSjA/nIMzJejCPD3agMcdpXIVfhA/Tje9zXNHeDYxe9wS/rI86oqIgOTaeHw9 vGtM2HhdDJlk1cQfpnyRTTJLT79ROPmLO/W4feJ3B0BRohr4/Iyofz21DS5dBBdwCCux iWdg==
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=/WihR3BE8eHPYZC8Q3v1OK11jhaH20JgFWYcTQc7r78=; b=UT/0No5HyvocCgHDj/DPAxe1v6BfWjAxKpELsJxK1nphwv6ar8VcgCYp67xbNZns/9 5OJq08yoYVM2kpu/lgdnWQBR3Qa+Phm5fO8NIOYSn5z1HLSWPyHLDoF42tr4P5VZbL5B VLb2DYBsLnIJHJooKyVyjdO/8w38/ihRhy+uzPxaERUnqffN6Itl6H8Ppp2J2xC5jzp0 DjxElwk0OjvS6KWMa1b/HzEF4OSVRESMCs4lmskyEOPrlB2mxz55qjkTPdPEM9wwfjZK QzFUKBCTRdiaWvB3tqCaSNWkjROzv9e9pSS/opEoO7bYuaAIboHp0YUayywDuRvSYtfQ bFjA==
X-Gm-Message-State: AOPr4FU366h0KiCm3RQG/viIbBHgMGyckdretmeMBvE0qsTV0KsIn2ZS3EKB0OtBlLCpCQ==
X-Received: by 10.66.52.112 with SMTP id s16mr25027199pao.35.1462493886685; Thu, 05 May 2016 17:18:06 -0700 (PDT)
Received: from ?IPv6:2406:e007:4a1c:1:28cc:dc4c:9703:6781? ([2406:e007:4a1c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 5sm16206208pfi.91.2016.05.05.17.18.03 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 May 2016 17:18:05 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Bob Hinden <bob.hinden@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <CAO42Z2zovzjBpPzs+sp-38kDWJZk5widU2DNDKirfYFc2uBkPQ@mail.gmail.com> <71e44c36-031e-3304-4b5d-2cd707351ce2@gmail.com> <D3355E7D-F3C5-43C4-B601-0E2379C30F65@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d73dad70-f3f5-8860-7840-93f9b5f097f3@gmail.com>
Date: Fri, 6 May 2016 12:18:13 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <D3355E7D-F3C5-43C4-B601-0E2379C30F65@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DX12jKNz6o9Zf-eUuY7W7yhdQmY>
Cc: IPv6 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: Fri, 06 May 2016 00:18:10 -0000

Bob,

+1

   Brian

On 06/05/2016 12:12, Bob Hinden wrote:
> Brian,
>=20
>> On May 2, 2016, at 4:58 PM, Brian E Carpenter <brian.e.carpenter@gmail=
=2Ecom> wrote:
>>
>> On 03/05/2016 10:37, Mark Smith wrote:
>> ...
>>>>   The contents of an Extension header or Option in an Extension head=
er
>>>>   may be modified if this is permitted by the definition of the
>>>>   Extension header or option.
>>>>
>>>
>>> The thing I would criticise about this text is that it would not disc=
ourage
>>> silent and unattributable changes.
>>
>> The sentence is actually a no-op anyway; it really states the obvious.=

>> A slightly stronger version would be:
>>
>> The contents of an Extension header or Option in an Extension header
>> must not be modified unless this is permitted by the definition of the=

>> Extension header or option.
>=20
> Since we do allow Extension headers and Options to be modified, I have =
a slight preference for the previous text.  It is, as you say=E2=80=9D st=
ating the obvious.  Seems like saying this here, right after the text abo=
ut inserting and deleting, makes sense.
>=20
> Thanks,
> Bob
>=20
>>
>> but I am not sure that is a clarification of RFC 2460; it seems a
>> bit like a new rule.
>>
>>     Brian
>=20


From nobody Fri May  6 01:27:24 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 D475A12D0D3 for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 01:27:22 -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 Acbj7Kh7jDn2 for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 01:27:20 -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 83CFC12B03B for <ipv6@ietf.org>; Fri,  6 May 2016 01:27:19 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 May 2016 08:27:18 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id EA57D9CCFB; Fri,  6 May 2016 01:27:16 -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=zl9CGKhOM/Li3YfQfaXgV/E/mOg=; b= ekvy9E/uuGqd9xuSNxuoMNdnxbuN2n0cMmHZZE1PrsIn/9sBa7FrcK4iejNhhH4W LUdvtQ7CKR7/inVKTQ4ZnWi4OHDMF2m2FpIlm1DCiBm6nrs3dvkgduHhcFHY1n+r lOabZ9nc0aTq5yW4yS+2zKdV2D0FC4FsHu0cf1eG5oU=
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=fAr5TW9Jl4OOAt1jzpWQq83MMs Ge3V4IBfSQqDhE5H/JCiwC+S4dGedTzFT/wqq3brlNwQOmkmYxE93mqJDhdpIljz 7bQF/OuLadCoOmQXg0BPl9EZDXEOH1X+VA2TpWjLITV20YG8yApDwAryLwGYWZXW 4gFbP4PIcubnBuRAM=
Received: from h.hanazo.no (unknown [173.38.220.34]) (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 730B59CC8E; Fri,  6 May 2016 01:27:16 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by h.hanazo.no (Postfix) with ESMTP id C495E15A2DA1; Fri,  6 May 2016 10:27:10 +0200 (CEST)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E08EDD3B-9F5A-4CDD-AC04-A8FD336C67E5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
Date: Fri, 6 May 2016 10:27:10 +0200
Message-Id: <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CsI9Madc-U9NQ-TrARXxX-ODr28>
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: Fri, 06 May 2016 08:27:23 -0000

--Apple-Mail=_E08EDD3B-9F5A-4CDD-AC04-A8FD336C67E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

> Based on the discussion, I think there is agreement to keep the text =
in the rfc2460bis -04 draft about not inserting extension headers.  I =
made a change to the second sentence regarding encapsulation based on =
the email discussion:
>=20
>   Extension headers must never be inserted by any node other than the
>   source of the packet.  One approach to meet a requirement to add
>   extension headers is to use IP Encapsulation, for example, as =
defined
>   in [RFC2473].
>=20
> Please let me know if this is OK.
>=20
> The other related proposed text regarding not deleting or changing the =
size of extension headers is:
>=20
>   Extension headers must never be deleted or changed in size by any
>   node on the path the packet takes.
>=20
>   The contents of an Extension header or Option in an Extension header
>   may be modified if this is permitted by the definition of the
>   Extension header or option.
>=20
> This was proposed earlier on the list.  I think it is consistent the =
prohibition against inserting extension headers.
>=20
> Please comment.

I am not convinced we can add this paragraph.

Have you evaluated the consequence for a BITW implementation of e.g. =
IPsec (RFC4301)?
(or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)

Best regards,
Ole


>=20
>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>>=20
>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>=20
>>>> mmm... I guess you don't need ietf permission to violate the specs =
in
>>>> your own walled garden?
>>>=20
>>> Since the protocol police have been very quiet recently, that is a =
fact of
>>> life. However, if we want to be explicit about it (after 2460bis) we =
could
>>> write it up.
>>=20
>> I fully agree. What I meant is: the fact that you could potentially =
make
>> something work in a walled garden doesn't seem an argument to =
legitimize
>> that behavior -- particularly when I guess we're supposed to be
>> standarizing more for the general case than for the walled garden =
case.
>>=20
>>=20
>>> Diffserv already allows domain-specific packet mutations; the
>>> flow label tolerates mutations in certain circumstances. I don't see =
why
>>> we couldn't also describe the circumstances in which other header =
mutations
>>> are allowed. But first, define the precise meaning of "the open =
Internet."
>>=20
>> Have this mutations the same potential implications as the
>> insertion/removal of EHs?
>>=20
>> Thanks,
>>=20
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>=20
>>=20
>>=20
>>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_E08EDD3B-9F5A-4CDD-AC04-A8FD336C67E5
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

iQIcBAEBCgAGBQJXLFVeAAoJEL7aWKiYQt92eKYP/RxmFsFANYUpZyyMXtN6ZIrF
exWpCK8JIA68QTS/W/26VKpXy8enYgHSum3r3XzwcGEweVbzuPJwJ9PuVWbVJyn7
noyGCe8usInuDwDJuvmrUMC5lMCoyQcExkcCK5DLBYLVFvR0MvOgCzh7LFzbHi28
vtG0UaDuTPKtB3pUo7jP0hCyOPNM7P/MuuOd0DEHVYbbFk4cAoTyOZjxCXCfbmEF
1d3DnvzrtH9uBjH6iN2D07YIJFp8UlIU4NZjG7JfqTyjPu0S1EEhU7bTEAJew7zr
W4rHSDI0d/0l5Ynvverby+4ObdPd+J7gqhyAEG456XoNpX91yZPYaWRvrCSFMFUo
wuGuWCjW0/PK1sqaVdRmIUxovzz0C+HjjnjE9wabANHY88NSwGg9thsYcCgZQQkv
bgNFp6tYIfp2NcMfAwcEuMSUCArVBp3XseuQ1HDAkseu8XeuodZt01I9V2xmybrN
t17E93G6Gpz7m3XTbF3Z6g5vQsHaCWSpm7vhAB+mogwF9FldLuh3Is9CPDojaoM4
DCbdTZkhGl81HbDbu+8xpVu0L+1GMDBodjknqMmVKEkHOLLGpN7uO4WbpJ6k2/k+
OL/2krTpBJMQqyqSDKBDz/prUUQvFYlZY1s02K5LOtCfVSQNi01qQPzvFToJuuXR
jg6qeYUGJYIeRRjZjZFb
=bjoR
-----END PGP SIGNATURE-----

--Apple-Mail=_E08EDD3B-9F5A-4CDD-AC04-A8FD336C67E5--


From nobody Fri May  6 12:48:44 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 8F78D12D6BE for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 12:48:39 -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 pjVyU0vpm3wo for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 12:48:37 -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 82C1812D6B7 for <ipv6@ietf.org>; Fri,  6 May 2016 12:48:37 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id xk12so50886025pac.0 for <ipv6@ietf.org>; Fri, 06 May 2016 12:48:37 -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=G+qxqo37U7D3VXzK3TaH0RiF8R1tV91mW1i3bQMeTkA=; b=ZMJmAXwdGXuvD9NBA3Ns9aw92baogUXbSOpS3h/02ZCyxXhbrGUpC06eNkTgoar/4G 5x/1EnvPnaVO0dNJTjNGl+wdeg+vAFgxhqt8d6qnduFyNn0a1NlaGC03AoUzf+D9jrkq p9HkP4R6ghSXX5/Q3tWRaymGVzZNapwHNO3WjuV5KZWfYfNRHlw9cd5YMp1lLWE5kAwc qlaA1vk+RYDgznYtII71kvVnXVeTFgJ2dYbZ6Q9Zz3ao+JEauYjMMv1LM+gVdG2vwYOF YQFeFheChMdqlvDhgCGidHi8+xyq4+rqD+W3f8bE4uGP/KvLLppFnZ6tzogsJib+sAp7 kh6A==
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=G+qxqo37U7D3VXzK3TaH0RiF8R1tV91mW1i3bQMeTkA=; b=RkAU6Rz6Bue78UjAIHOgMYs22yLAzN0W52Wc5qHYPLQMpKWBTYjGFrMS3vfmGTHPiW SYZ3+EcMKI37Nwa34b0jN55xInc/DIX79NlscYIts7J0LnvtxMG+PsxjqX8GrAUwEO+s 7YYLOSXdXEXo7u+Tu8cHEGOE03yod1LBOfVQP9nu6AzUdBAoNOBEcVUyhCGXig959J2D /AzqDd6Oidd7D9N1GQkMo2PkpFtA4ktiK1fC94Y8dDodckEVJZMm9AQQjsxaiFpEMNns Vrp0XLS6G2aeISHKrB6epxDxKa99xLhJzm4aGcPx4NjdIcQ0swYisIt1HizXYPJVlo14 ZUEQ==
X-Gm-Message-State: AOPr4FXVuvfUNAECEqg0yYY6NmggxRRqAVPxBxwRgx4jboRLF2ryYMjJhLcCfG10T6IW9w==
X-Received: by 10.66.41.107 with SMTP id e11mr31337875pal.15.1462564117097; Fri, 06 May 2016 12:48:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:6c98:1:28cc:dc4c:9703:6781? ([2406:e007:6c98:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id y66sm22866952pfy.66.2016.05.06.12.48.33 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2016 12:48:35 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: otroan@employees.org, Bob Hinden <bob.hinden@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com>
Date: Sat, 7 May 2016 07:48:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oB6pImhsrQUHNQUeVkVHPAqV-ZY>
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: Fri, 06 May 2016 19:48:39 -0000

On 06/05/2016 20:27, otroan@employees.org wrote:
>> Based on the discussion, I think there is agreement to keep the text in the rfc2460bis -04 draft about not inserting extension headers.  I made a change to the second sentence regarding encapsulation based on the email discussion:
>>
>>   Extension headers must never be inserted by any node other than the
>>   source of the packet.  One approach to meet a requirement to add
>>   extension headers is to use IP Encapsulation, for example, as defined
>>   in [RFC2473].
>>
>> Please let me know if this is OK.
>>
>> The other related proposed text regarding not deleting or changing the size of extension headers is:
>>
>>   Extension headers must never be deleted or changed in size by any
>>   node on the path the packet takes.
>>
>>   The contents of an Extension header or Option in an Extension header
>>   may be modified if this is permitted by the definition of the
>>   Extension header or option.
>>
>> This was proposed earlier on the list.  I think it is consistent the prohibition against inserting extension headers.
>>
>> Please comment.
> 
> I am not convinced we can add this paragraph.
> 
> Have you evaluated the consequence for a BITW implementation of e.g. IPsec (RFC4301)?
> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)

There would be consequences if it said "must not be modified unless this is permitted".
But it doesn't. It says "may be modified if this is permitted", which as I said a couple
of days ago is really a no-op.

(BTW there is no RFC describing a shim6 proxy and I sincerely hope there is no
running code either.)

   Brian

> Best regards,
> Ole
> 
> 
>>
>>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>>
>>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>>
>>>>> mmm... I guess you don't need ietf permission to violate the specs in
>>>>> your own walled garden?
>>>>
>>>> Since the protocol police have been very quiet recently, that is a fact of
>>>> life. However, if we want to be explicit about it (after 2460bis) we could
>>>> write it up.
>>>
>>> I fully agree. What I meant is: the fact that you could potentially make
>>> something work in a walled garden doesn't seem an argument to legitimize
>>> that behavior -- particularly when I guess we're supposed to be
>>> standarizing more for the general case than for the walled garden case.
>>>
>>>
>>>> Diffserv already allows domain-specific packet mutations; the
>>>> flow label tolerates mutations in certain circumstances. I don't see why
>>>> we couldn't also describe the circumstances in which other header mutations
>>>> are allowed. But first, define the precise meaning of "the open Internet."
>>>
>>> Have this mutations the same potential implications as the
>>> insertion/removal of EHs?
>>>
>>> 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
>> --------------------------------------------------------------------
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Fri May  6 13:09:11 2016
Return-Path: <tom@herbertland.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 46E5012D1A5 for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 13:09:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 O0OkWEGQ1XTe for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 13:09:08 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 3AB9612D10D for <ipv6@ietf.org>; Fri,  6 May 2016 13:09:08 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id d62so124507843iof.2 for <ipv6@ietf.org>; Fri, 06 May 2016 13:09:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=8gTOh7zuTxIPxC/retdwbtTMzqpj1E/Dk6IGBhmzKw8=; b=vKXHzUqb5ysTyaCBLy8rSqi3s3bThASB9cikhhMCuTMTGeZAjel5KDnDkujGatCEf0 GdHj2AhBaUV1oEURPEJDiTnGpBH4hJ06T7MWC86pPrkUygsyDshBnWSPH6eHBafaKvbq PypbsHqVXhnQi5PkuCz/GbjrPrwtfAN5peLfC0UJO5HHxo0bJMEZOhdE7biuZ0Jpz888 zKfLgLd5cjHZTLOuKkyAO/HFrgIOeRZgv3/L58y1jT0FEXlUClImYC9np+PpHRARJaV9 KFIDhXnII/i5CzfCrhds/b2AVfHaRh/EZCrNXPeUwZSVIIUFf6iE3CKtcUrX55xdhIBI +HVQ==
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:date :message-id:subject:from:to:cc; bh=8gTOh7zuTxIPxC/retdwbtTMzqpj1E/Dk6IGBhmzKw8=; b=HalHR52Us6qmRPLUwgPnwVuMetgXU/4aDN95zmsbek7ZreEKuHjZbgUpXLSSNfnMwy xRbpY5/8mEzyNYI4khmR0ZCoZvJib6hCS3Tu/5Q7l/LaYYstXr7rBvxTlR1MmK+LZkbJ D9IfjkfWcxIruPud175DlWHm81KdQR9XSkV8j8WaOreMajQBfTYvjPtWGJ4HB4nEwJtM BBb9VFeF2Z57eHoh4uQB2G+rBk6Swljnbl24jH2dAlu/dNmSZ8WXA28KU5y+4Sx1uYId MhZy+SdekdfuIrHYmKHjYnl68cBP1+zSYQq9I5OVr6v6X+Fv6q6elHBuR9fbjOis9UBC py6Q==
X-Gm-Message-State: AOPr4FVvdQP/kmrLHBtpINWjg+789W7+ASwSPGrcTobQhu/1qxglYJUh+fomEipn/u3LDb196aifGTOzhtER+g==
MIME-Version: 1.0
X-Received: by 10.107.51.206 with SMTP id z197mr27709343ioz.107.1462565347496;  Fri, 06 May 2016 13:09:07 -0700 (PDT)
Received: by 10.107.56.67 with HTTP; Fri, 6 May 2016 13:09:07 -0700 (PDT)
In-Reply-To: <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com>
Date: Fri, 6 May 2016 13:09:07 -0700
Message-ID: <CALx6S34Zp+dqYkWmnZEfEwkkkTx6=6MCsqZqq9McwB3oY0Ka0A@mail.gmail.com>
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
From: Tom Herbert <tom@herbertland.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5Jul6VIwZyoQZluNixBMTfl16Ro>
Cc: 6man WG <ipv6@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: Fri, 06 May 2016 20:09:10 -0000

On Fri, May 6, 2016 at 12:48 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 06/05/2016 20:27, otroan@employees.org wrote:
>>> Based on the discussion, I think there is agreement to keep the text in the rfc2460bis -04 draft about not inserting extension headers.  I made a change to the second sentence regarding encapsulation based on the email discussion:
>>>
>>>   Extension headers must never be inserted by any node other than the
>>>   source of the packet.  One approach to meet a requirement to add
>>>   extension headers is to use IP Encapsulation, for example, as defined
>>>   in [RFC2473].
>>>
>>> Please let me know if this is OK.
>>>
>>> The other related proposed text regarding not deleting or changing the size of extension headers is:
>>>
>>>   Extension headers must never be deleted or changed in size by any
>>>   node on the path the packet takes.
>>>
>>>   The contents of an Extension header or Option in an Extension header
>>>   may be modified if this is permitted by the definition of the
>>>   Extension header or option.
>>>
>>> This was proposed earlier on the list.  I think it is consistent the prohibition against inserting extension headers.
>>>
>>> Please comment.
>>
>> I am not convinced we can add this paragraph.
>>
>> Have you evaluated the consequence for a BITW implementation of e.g. IPsec (RFC4301)?
>> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>
> There would be consequences if it said "must not be modified unless this is permitted".
> But it doesn't. It says "may be modified if this is permitted", which as I said a couple
> of days ago is really a no-op.
>
> (BTW there is no RFC describing a shim6 proxy and I sincerely hope there is no
> running code either.)
>
For that matter, is there an actual implementation of an ILNP proxy? I
can't find code that just implements ILNP....

Thanks,
Tom

>    Brian
>
>> Best regards,
>> Ole
>>
>>
>>>
>>>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>>>
>>>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>>>
>>>>>> mmm... I guess you don't need ietf permission to violate the specs in
>>>>>> your own walled garden?
>>>>>
>>>>> Since the protocol police have been very quiet recently, that is a fact of
>>>>> life. However, if we want to be explicit about it (after 2460bis) we could
>>>>> write it up.
>>>>
>>>> I fully agree. What I meant is: the fact that you could potentially make
>>>> something work in a walled garden doesn't seem an argument to legitimize
>>>> that behavior -- particularly when I guess we're supposed to be
>>>> standarizing more for the general case than for the walled garden case.
>>>>
>>>>
>>>>> Diffserv already allows domain-specific packet mutations; the
>>>>> flow label tolerates mutations in certain circumstances. I don't see why
>>>>> we couldn't also describe the circumstances in which other header mutations
>>>>> are allowed. But first, define the precise meaning of "the open Internet."
>>>>
>>>> Have this mutations the same potential implications as the
>>>> insertion/removal of EHs?
>>>>
>>>> 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
>>> --------------------------------------------------------------------
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri May  6 20:41:46 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 461E212D0C7 for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 20:41:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 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, 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 mraGKLc-cu-U for <ipv6@ietfa.amsl.com>; Fri,  6 May 2016 20:41:41 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::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 A27A812B026 for <ipv6@ietf.org>; Fri,  6 May 2016 20:41:41 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id m188so11887574vka.1 for <ipv6@ietf.org>; Fri, 06 May 2016 20:41:41 -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=9u24uo67UZhZmFg48VDZ9aeC/wUmpNJkSuB2X7qm3G4=; b=ZW6c1F9PXIYuFGqsiLL8auTG7HPugKrtQixFBcuVkpShkLhYtI9xPORbGr9h4nl+e2 qXlvLszBSceSuVTKCZL1QG30OdbzGbAQv2cwEiHk3GhNBrpPOdJH2AWfO4Yo0Eh61nCD fvBbouMaHH0cEOXAivI2jyHCF21khcqfAXJevizEaEEr842RajYNC5RXGV/IRyJRio2d 86A0nBwEpjoTfvzSWvynnrekq8n0k3DTmPl/WRR6y9Z2zat4r4nmz4rEObDFdD2V4Cxk Kg6zXWfHLaKwVU3hxHn8F9M2/98jSfcDwmqoMhAGHSfmkUtkTJ4RfS7gR3IzakKLy64H gXEg==
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=9u24uo67UZhZmFg48VDZ9aeC/wUmpNJkSuB2X7qm3G4=; b=NtW3EoRYgBHRral7D5LIcNFU8stYlNWF3SvTKaypCpU/zF2kyq55+bmqSy2ZiRO7ym pTQfj+Sym7FASjuD/61nBAIJwYF23VA07bI707HnsqnnqJOvhcz+nzRna0b6o3n8LHiP 1QG4ia5EMcifAVRm4O2WChEdS6Dk9Dwf+JLn6pLOsVDT1ee27zaeN8/OXAAEYsXlG8cb zNYkY4P13E03L6MudlKeImFvaWyMBRvOGl/LMRWr5SspZJgGngBtLdUcFSRrU46fpIqu D1jTrzhGp+0wJVy1Q3eTqEPfhQ9fBhu8kfBLWFCbtVbDfQA40HEWidANQxxZ4NFu+/wO ygPg==
X-Gm-Message-State: AOPr4FU3gYI4N4BJ6Qlwm05hCuWLWkkhg2f0Fsp4IZ3EJhggRqJBZ06j0dT3ZF4YVh1d3oKFj1hjEoIUemltwg==
X-Received: by 10.31.146.144 with SMTP id u138mr855018vkd.2.1462592500703; Fri, 06 May 2016 20:41:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.64.65 with HTTP; Fri, 6 May 2016 20:41:10 -0700 (PDT)
In-Reply-To: <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 7 May 2016 13:41:10 +1000
Message-ID: <CAO42Z2yVxBVnE7hAqTEiOpj_wSUAS38=RaOA991yNPJypZLcOA@mail.gmail.com>
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xKV7E15KvNxGCWbzM42JIVAEkBA>
Cc: 6man WG <ipv6@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: Sat, 07 May 2016 03:41:44 -0000

Hi,

On 6 May 2016 at 18:27,  <otroan@employees.org> wrote:
>> Based on the discussion, I think there is agreement to keep the text in the rfc2460bis -04 draft about not inserting extension headers.  I made a change to the second sentence regarding encapsulation based on the email discussion:
>>
>>   Extension headers must never be inserted by any node other than the
>>   source of the packet.  One approach to meet a requirement to add
>>   extension headers is to use IP Encapsulation, for example, as defined
>>   in [RFC2473].
>>
>> Please let me know if this is OK.
>>
>> The other related proposed text regarding not deleting or changing the size of extension headers is:
>>
>>   Extension headers must never be deleted or changed in size by any
>>   node on the path the packet takes.
>>
>>   The contents of an Extension header or Option in an Extension header
>>   may be modified if this is permitted by the definition of the
>>   Extension header or option.
>>
>> This was proposed earlier on the list.  I think it is consistent the prohibition against inserting extension headers.
>>
>> Please comment.
>
> I am not convinced we can add this paragraph.
>
> Have you evaluated the consequence for a BITW implementation of e.g. IPsec (RFC4301)?

In my thoughts about EH insertion/deletion, to me IPsec has been a
reference model. The reason why was that when I learnt about IPsec and
its transport and tunnel modes, I would have thought that
host-to-IPsec-gateway would use transport mode. This would have meant
that the IPsec gateway would have been inserting and removing the ESP
and/or AH headers to/from the original hosts' packets, rather than
tunnelling them to the host. I think it was a surprise because at the
time I thought of tunnelling as only something that was done between
routers.

In other words,

Host-to-Host: transport mode
Host-to-GW: tunnel mode
GW-to-GW: tunnel mode

None of those would require an IPsec gateway to insert an ESP and/or
AH header into a packet it has received from somewhere else.

This text from Section 4.1 is making it clear that a security gateway
is only allowed to use transport mode if the source or destination
address of the packet is the security gateway itself i.e., the SG is
actually an end-system for this communication.

"To clarify, the use of
   transport mode by an intermediate system (e.g., a security gateway)
   is permitted only when applied to packets whose source address (for
   outbound packets) or destination address (for inbound packets) is an
   address belonging to the intermediate system itself."

RFC4301 seems to be using BITW as more of an implementation method,
rather than having a defined IPsec role.

"c. The use of a dedicated, inline security protocol processor is a
      common design feature of systems used by the military, and of some
      commercial systems as well.  It is sometimes referred to as a
      "bump-in-the-wire" (BITW) implementation.  Such implementations
      may be designed to serve either a host or a gateway.  Usually, the
      BITW device is itself IP addressable.  When supporting a single
      host, it may be quite analogous to a BITS implementation, but in
      supporting a router or firewall, it must operate like a security
      gateway."


This would seem to be saying that when serving a single host, a BITW
implementation is conceptually part of the single host's stack (e.g.,
the text about having an IP address being optional would apply).
However, when it is serving more than one host, it must act as a
security gateway, meaning it must use IPsec tunnel mode for everything
except its own 'end-system' traffic, where it could chose either
transport or tunnel mode.

So I don't think a BITW implementation method for IPsec really
contradicts what is in RFC2460 or what the proposed RFC2460bis text
is.

Regards,
Mark.


> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>
> Best regards,
> Ole
>
>
>>
>>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>>
>>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>>
>>>>> mmm... I guess you don't need ietf permission to violate the specs in
>>>>> your own walled garden?
>>>>
>>>> Since the protocol police have been very quiet recently, that is a fact of
>>>> life. However, if we want to be explicit about it (after 2460bis) we could
>>>> write it up.
>>>
>>> I fully agree. What I meant is: the fact that you could potentially make
>>> something work in a walled garden doesn't seem an argument to legitimize
>>> that behavior -- particularly when I guess we're supposed to be
>>> standarizing more for the general case than for the walled garden case.
>>>
>>>
>>>> Diffserv already allows domain-specific packet mutations; the
>>>> flow label tolerates mutations in certain circumstances. I don't see why
>>>> we couldn't also describe the circumstances in which other header mutations
>>>> are allowed. But first, define the precise meaning of "the open Internet."
>>>
>>> Have this mutations the same potential implications as the
>>> insertion/removal of EHs?
>>>
>>> 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
>> --------------------------------------------------------------------
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Sun May  8 11:40:25 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 06EF912D095 for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 11:40:22 -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 ng3_AuO7Cu9a for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 11:40:19 -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 90268128B44 for <ipv6@ietf.org>; Sun,  8 May 2016 11:40:18 -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; 08 May 2016 18:40:17 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0EF319CCFB; Sun,  8 May 2016 11:40:16 -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=CiKVGwd2wo61aobWqLY/jQtoziQ=; b= mVCKX3rzGKregHhZjO1vfJlawAHCBIH9xb2E/ZZAyzLyMzj3gXdvnoxVmAeKWIyE EeE2EFC6dsZ1Jf1yhvRx+GoGlYMGbRaDnx0HeLM0rWAqTBOfgV3GUgK6OdxJCCpA 63v2w3jrlvy38d1eEAhLlHmQX/M5ro6cwGWCzMqUJE8=
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=Kmi4bmX4fBaKATab+SZn4RXwcZ HD5b6Id7yKBIlwncdixCrgosf6l/xnt9jI27RH43LNcAYq0+W8LZLMU5ppKmuXqU TYC8gzAh0UXwNiAtd4gic+bi5XoYVt4ibcvlenGwI7UeKFzuUGsC4mOVR4eqWR9L QvnjwwP2hmFpI0yg8=
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 8782F9CC8E; Sun,  8 May 2016 11:40:15 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 22627160A3E5; Sun,  8 May 2016 20:40:13 +0200 (CEST)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_87B8BE20-BE7B-4493-BCA1-43946BB1274C"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com>
Date: Sun, 8 May 2016 20:40:02 +0200
Message-Id: <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZR7MpBOCY2OVZEK9SHUOJQzzhuY>
Cc: 6man WG <ipv6@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: Sun, 08 May 2016 18:40:22 -0000

--Apple-Mail=_87B8BE20-BE7B-4493-BCA1-43946BB1274C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>>> Based on the discussion, I think there is agreement to keep the text =
in the rfc2460bis -04 draft about not inserting extension headers.  I =
made a change to the second sentence regarding encapsulation based on =
the email discussion:
>>>=20
>>>  Extension headers must never be inserted by any node other than the
>>>  source of the packet.  One approach to meet a requirement to add
>>>  extension headers is to use IP Encapsulation, for example, as =
defined
>>>  in [RFC2473].
>>>=20
>>> Please let me know if this is OK.
>>>=20
>>> The other related proposed text regarding not deleting or changing =
the size of extension headers is:
>>>=20
>>>  Extension headers must never be deleted or changed in size by any
>>>  node on the path the packet takes.
>>>=20
>>>  The contents of an Extension header or Option in an Extension =
header
>>>  may be modified if this is permitted by the definition of the
>>>  Extension header or option.
>>>=20
>>> This was proposed earlier on the list.  I think it is consistent the =
prohibition against inserting extension headers.
>>>=20
>>> Please comment.
>>=20
>> I am not convinced we can add this paragraph.
>>=20
>> Have you evaluated the consequence for a BITW implementation of e.g. =
IPsec (RFC4301)?
>> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>=20
> There would be consequences if it said "must not be modified unless =
this is permitted".
> But it doesn't. It says "may be modified if this is permitted", which =
as I said a couple
> of days ago is really a no-op.

If it is a no-op what purpose does the text serve?
I presume you are only referring to the second paragraph?

----
  Extension headers must never be deleted or changed in size by any
  node on the path the packet takes.

  The contents of an Extension header or Option in an Extension header
  may be modified if this is permitted by the definition of the
  Extension header or option.
----

apart from increasing the risk of making something like a BITW style =
implementation of something not compliant, can you help me understand =
the motivation behind this change? what are you trying to achieve? have =
text that can be used to prohibit something happening in the future?

RFC2460 has a very clear "world view". a network consists of hosts, =
routers and links. RFC2460 specifies very clearly that a router does not =
examine or process extension headers (with the one well-known =
exception). adding the above paragraph diffuses and weakens that.

cheers,
Ole


>=20
> (BTW there is no RFC describing a shim6 proxy and I sincerely hope =
there is no
> running code either.)
>=20
>   Brian
>=20
>> Best regards,
>> Ole
>>=20
>>=20
>>>=20
>>>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>>>>=20
>>>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>>>=20
>>>>>> mmm... I guess you don't need ietf permission to violate the =
specs in
>>>>>> your own walled garden?
>>>>>=20
>>>>> Since the protocol police have been very quiet recently, that is a =
fact of
>>>>> life. However, if we want to be explicit about it (after 2460bis) =
we could
>>>>> write it up.
>>>>=20
>>>> I fully agree. What I meant is: the fact that you could potentially =
make
>>>> something work in a walled garden doesn't seem an argument to =
legitimize
>>>> that behavior -- particularly when I guess we're supposed to be
>>>> standarizing more for the general case than for the walled garden =
case.
>>>>=20
>>>>=20
>>>>> Diffserv already allows domain-specific packet mutations; the
>>>>> flow label tolerates mutations in certain circumstances. I don't =
see why
>>>>> we couldn't also describe the circumstances in which other header =
mutations
>>>>> are allowed. But first, define the precise meaning of "the open =
Internet."
>>>>=20
>>>> Have this mutations the same potential implications as the
>>>> insertion/removal of EHs?
>>>>=20
>>>> Thanks,
>>>>=20
>>>> --
>>>> Fernando Gont
>>>> SI6 Networks
>>>> e-mail: fgont@si6networks.com
>>>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------


--Apple-Mail=_87B8BE20-BE7B-4493-BCA1-43946BB1274C
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

iQEcBAEBCgAGBQJXL4gMAAoJED4aXnjSQuKWP+0H/37pX+cOGGF2qFxSVp5W2aMh
v8KD+EYofNcL6pwEVgHblo184Q8osz/Ri/92lH7lNqhdToFBbgjJ/Tuwh540krM0
PcbLCE8n33Hj+59Uj/PFR2B7jBZ2oA/ydrBtCm5x919WFlYc+xkmdunOeQmfZTkE
SwMbxFK/BrAdAiJx35p0vhNKCtgRZzEZPeENvopWlNpr6aE9j0Ki7XcfjNfbYsi2
atvH0OcC/e2pyXJdk6Vr4hjqcaSVPlhozJvJhPARmwyXCPICuRIhYSU3ujqAqWII
8YiVnt7UYqHZZsT+Fm26ht5k8vL1YicUc3lBhRUCtw/Vdz/acgTg1wp47jghWB8=
=ITVE
-----END PGP SIGNATURE-----

--Apple-Mail=_87B8BE20-BE7B-4493-BCA1-43946BB1274C--


From nobody Sun May  8 14:41: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 BF0B412D0B6 for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 14:41:10 -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 zB6ma9S4a6gF for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 14:41:06 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::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 6AB7912D095 for <ipv6@ietf.org>; Sun,  8 May 2016 14:41:06 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id 77so68074212pfv.2 for <ipv6@ietf.org>; Sun, 08 May 2016 14:41:06 -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=Jjp/uV1zo7vH3ihFRcMowMx6ltR9m16JLJsPA9pba1E=; b=xgOXP6QHPb9IUbBi7DoE52enI5CHCHSv+c9PsrKj6fq2Dd9Phb3YgdCieQ9ogRuFGJ qWl/wXhAcXWLfGd2yL7dtzYlwx/GEEVsu7vBLn5B7nbsimGxonUdaSi63WiDIRW5t2b5 DyQJHBdM2I216faTwlEEI7VOKCuLNpGoxbixU0eDe0+lzC8ywCw2vPxCBDkBxnwe2zyO Lm+FlUvXCSn0AH+0vHXkRaa4dIt+k83u59aRmbmhNd8eEGCg8B3Gy62HWq4Z16J46Sox queSbxTcL/Gykuqus4DgiyYkBAJPKfNkZjjVOealQ2Kp4zl6ASYLP01hDL5dkHrz+CNP +e2A==
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=Jjp/uV1zo7vH3ihFRcMowMx6ltR9m16JLJsPA9pba1E=; b=ip4fajlec1VZE7+Y0+oLrFSvP54Iwa9WH0ONWoqEzxxPd2vNJiR80tuESphlaVAvT6 V4EQORv2ytNqWWQ3D4DvF/U82gotNSvoVfDG0MyY3LgvR21SVJ55tIMMLTGMYFbfwQ8e rsHVXfp2iY8Fiq4wz5kbwpvWBelFwKIn7CiK4DAYxXSqvIkv8FL61LbVW7jK2oSwvAqU loPtDOAz1EcdQOdBk8Y5u/jmQ6vFnJyWAKcU6ZFXtsE3wsASNw1/SrCq0ppN1dqtgItf xQ3IQi2/27ppDg7vU46x6MV46NQB0v9QuMcw6vwTCxg3xkbhCjedoSaxUjhb2JfpOp5G AZrg==
X-Gm-Message-State: AOPr4FVzZK7il6MAqcNAgJD/QX95Z6vjOMHGxMgfZnbO5scc9nq9HgMQAQIZgxrTYz8lBQ==
X-Received: by 10.98.102.207 with SMTP id s76mr44989666pfj.54.1462743666005; Sun, 08 May 2016 14:41:06 -0700 (PDT)
Received: from [10.10.16.137] ([125.7.18.30]) by smtp.gmail.com with ESMTPSA id eh9sm35480357pad.47.2016.05.08.14.41.02 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 08 May 2016 14:41:04 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: otroan@employees.org
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com> <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com>
Date: Mon, 9 May 2016 09:41:19 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZWYHIKgGnVgGy69aA5Tu7NZJrYA>
Cc: 6man WG <ipv6@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: Sun, 08 May 2016 21:41:11 -0000

On 09/05/2016 06:40, otroan@employees.org wrote:
>>>> Based on the discussion, I think there is agreement to keep the text in the rfc2460bis -04 draft about not inserting extension headers.  I made a change to the second sentence regarding encapsulation based on the email discussion:
>>>>
>>>>  Extension headers must never be inserted by any node other than the
>>>>  source of the packet.  One approach to meet a requirement to add
>>>>  extension headers is to use IP Encapsulation, for example, as defined
>>>>  in [RFC2473].
>>>>
>>>> Please let me know if this is OK.
>>>>
>>>> The other related proposed text regarding not deleting or changing the size of extension headers is:
>>>>
>>>>  Extension headers must never be deleted or changed in size by any
>>>>  node on the path the packet takes.
>>>>
>>>>  The contents of an Extension header or Option in an Extension header
>>>>  may be modified if this is permitted by the definition of the
>>>>  Extension header or option.
>>>>
>>>> This was proposed earlier on the list.  I think it is consistent the prohibition against inserting extension headers.
>>>>
>>>> Please comment.
>>>
>>> I am not convinced we can add this paragraph.
>>>
>>> Have you evaluated the consequence for a BITW implementation of e.g. IPsec (RFC4301)?
>>> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>>
>> There would be consequences if it said "must not be modified unless this is permitted".
>> But it doesn't. It says "may be modified if this is permitted", which as I said a couple
>> of days ago is really a no-op.
> 
> If it is a no-op what purpose does the text serve?

Not much - it states the obvious, doesn't it?

> I presume you are only referring to the second paragraph?

Yes.

   Brian

> 
> ----
>   Extension headers must never be deleted or changed in size by any
>   node on the path the packet takes.
> 
>   The contents of an Extension header or Option in an Extension header
>   may be modified if this is permitted by the definition of the
>   Extension header or option.
> ----
> 
> apart from increasing the risk of making something like a BITW style implementation of something not compliant, can you help me understand the motivation behind this change? what are you trying to achieve? have text that can be used to prohibit something happening in the future?
> 
> RFC2460 has a very clear "world view". a network consists of hosts, routers and links. RFC2460 specifies very clearly that a router does not examine or process extension headers (with the one well-known exception). adding the above paragraph diffuses and weakens that.
> 
> cheers,
> Ole
> 
> 
>>
>> (BTW there is no RFC describing a shim6 proxy and I sincerely hope there is no
>> running code either.)
>>
>>   Brian
>>
>>> Best regards,
>>> Ole
>>>
>>>
>>>>
>>>>> On Apr 28, 2016, at 6:08 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>>>>
>>>>> On 04/28/2016 09:37 PM, Brian E Carpenter wrote:
>>>>>> On 29/04/2016 04:34, Fernando Gont wrote:
>>>>>>
>>>>>>> mmm... I guess you don't need ietf permission to violate the specs in
>>>>>>> your own walled garden?
>>>>>>
>>>>>> Since the protocol police have been very quiet recently, that is a fact of
>>>>>> life. However, if we want to be explicit about it (after 2460bis) we could
>>>>>> write it up.
>>>>>
>>>>> I fully agree. What I meant is: the fact that you could potentially make
>>>>> something work in a walled garden doesn't seem an argument to legitimize
>>>>> that behavior -- particularly when I guess we're supposed to be
>>>>> standarizing more for the general case than for the walled garden case.
>>>>>
>>>>>
>>>>>> Diffserv already allows domain-specific packet mutations; the
>>>>>> flow label tolerates mutations in certain circumstances. I don't see why
>>>>>> we couldn't also describe the circumstances in which other header mutations
>>>>>> are allowed. But first, define the precise meaning of "the open Internet."
>>>>>
>>>>> Have this mutations the same potential implications as the
>>>>> insertion/removal of EHs?
>>>>>
>>>>> 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
>>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
> 


From nobody Sun May  8 19:07:33 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 ACB0B12D145 for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 19:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, 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 cUWNwaHASlZF for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 19:07:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3305412D17E for <ipv6@ietf.org>; Sun,  8 May 2016 19:07:28 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 10749200A3 for <ipv6@ietf.org>; Sun,  8 May 2016 22:12:52 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id E8549638BD for <ipv6@ietf.org>; Sun,  8 May 2016 22:07:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6man WG <ipv6@ietf.org>
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
In-Reply-To: <CAO42Z2yVxBVnE7hAqTEiOpj_wSUAS38=RaOA991yNPJypZLcOA@mail.gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <CAO42Z2yVxBVnE7hAqTEiOpj_wSUAS38=RaOA991yNPJypZLcOA@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 08 May 2016 22:07:26 -0400
Message-ID: <28244.1462759646@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fzVtsXWulucpqZxpsxn071WdNu0>
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, 09 May 2016 02:07:32 -0000

--=-=-=
Content-Type: text/plain


Mark Smith <markzzzsmith@gmail.com> wrote:
    > So I don't think a BITW implementation method for IPsec really
    > contradicts what is in RFC2460 or what the proposed RFC2460bis text
    > is.

I agree.  A BITW is just a host implementation that happens to be split
multiple CPUs.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVy/w24CLcPvd0N1lAQKuygf/cG/1Yc/TS8a3GSSLPtSpSBob9EYpjghp
t/2Kv3bckcezjWrdZxILhfb0EqPRkCEZkINGsfjRus3HOmMVAzV+Z2H3rKi8Nq6f
ZD1EVYF6bHp8gb4SJ27V4CwU0sYJ1rVGspg2qlpmz+vu7IczQ1D2okZ/fUwkydrt
/bWte29dcnmzWTc0vxC8/anYRAp2p7JK4OmoYmzsrOTUe9zRXk1qJHBs+Xq3MeuK
cosEhX2r5BqOoPG6Zwn2LRsg84PTWCCDKwsCDGct9NHG+jUnMUEM8GRTU37YhgG7
IAEW4uYYYh1BmsnQpk3sD/52tjDu/Rwv+/VwZKaz+7koJsF0xq8Vmg==
=N3Q6
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun May  8 23:35:40 2016
Return-Path: <weigengyu@bupt.edu.cn>
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 2353C12B04E for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 23:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] 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 tT_rbenylPvE for <ipv6@ietfa.amsl.com>; Sun,  8 May 2016 23:35:37 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id C249812B024 for <ipv6@ietf.org>; Sun,  8 May 2016 23:35:36 -0700 (PDT)
Received: from mx1.bupt.edu.cn (unknown [127.0.0.1]) by mx1.bupt.edu.cn (AnyMacro(G7)) with SMTP id AA87819F420 for <ipv6@ietf.org>; Mon,  9 May 2016 14:35:35 +0800 (HKT)
Received: from WeiGengyuPC (unknown [114.255.40.27]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 2CE5419F404; Mon,  9 May 2016 14:35:35 +0800 (HKT)
Message-ID: <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Alissa Cooper" <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in>
In-Reply-To: <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
Date: Mon, 9 May 2016 14:35:35 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7WxaV5_jVb_8B9yrt4z1D60Rop0>
Cc: 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, 09 May 2016 06:35:39 -0000

Hiï¼Œ

> This document changes the default scheme for generating stable
   Interface Identifiers with SLAAC to that specified in RFC7217,

There is a question about RFC7217 as this draft is to promote it.
In RFC7217,  in Page 6 and page 7,  "5.  Algorithm Specification"
"1.  Compute a random (but stable) identifier with the expression:
       RID = F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key)
       Where:
       RID:
          Random (but stable) Identifier
       F():
          A pseudorandom function (PRF) that MUST NOT be computable from
          the outside (without knowledge of the secret key).  F() MUST
          also be difficult to reverse, such that it resists attempts to
          obtain the secret_key, even when given samples of the output
          of F() and knowledge or control of the other input parameters.
          F() SHOULD produce an output of at least 64 bits.  F() could
          be implemented as a cryptographic hash of the concatenation of
          each of the function parameters.  SHA-1 [FIPS-SHS] and SHA-256
          are two possible options for F().  Note: MD5 [RFC1321] is
          considered unacceptable for F() [RFC6151]. "

It seems it is a concept error for RID.
RID is not random or random identifier according to the context above.

F() is an inreverse function, not a pseudorandom function.
Within parameters of F(Prefix, Net_Iface, Network_ID, DAD_Counter, 
secret_key),
only the secret_key is generated by a pseudorandom function.
But the secret_key is also a constant because it keeps unchanged after being 
generated.

There are not random features.

The question is why it is called RID, Random ID?


Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----åŽŸå§‹é‚®ä»¶----- 
From: Alissa Cooper
Sent: Thursday, April 28, 2016 10:41 PM
To: IETF IPv6 Mailing List
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt

This version incorporates comments based on discussion before and during 
IETF 95 (thanks to Fernando for spinning the rev). I think this version 
addresses the comments received and should be ready to move forward.

Alissa


> On Apr 27, 2016, at 5:49 PM, 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           : Recommendation on Stable IPv6 Interface 
> Identifiers
>        Authors         : Fernando Gont
>                          Alissa Cooper
>                          Dave Thaler
>                          Will Liu
> Filename        : draft-ietf-6man-default-iids-11.txt
> Pages           : 23
> Date            : 2016-04-27
>
> Abstract:
>   This document changes the default scheme for generating stable
>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>   recommends against embedding 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, by removing the text in these RFCs
>   that required the IPv6 Interface Identifiers to be derived from the
>   underlying link-layer address, and replacing the aforementioned text
>   with a pointer to this document.  Additionally, this document updates
>   RFC3315 by specifying additional requirements on the generation of
>   Interface Identifiers used in Dynamic Host Configuration Protocol
>   version 6 (DHCPv6).  It also provides advice to system administrators
>   who employ manual configuration.  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-11
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-11
>
>
> 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
> --------------------------------------------------------------------

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



From nobody Mon May  9 06:01:17 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 91D3F12B038 for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 06:01:16 -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 1qn45cQbAgwO for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 06:01:13 -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 6444612B030 for <ipv6@ietf.org>; Mon,  9 May 2016 06:01:12 -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; 09 May 2016 13:01:11 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 295019CCFC; Mon,  9 May 2016 06:01:10 -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=anajjOspa8WWzdiiIFsTewDtx9s=; b= WYcf2cAo8kSyMEzehGKlbfv3ksyp5B3dtOXt0U5k7iirDEE76oMHiGVHEJA7avnL aHOYzwXSoG2zXp5QygiIGOHBl+PLNN9etxxqXiOj0e7i7vFd+oa7P1+9+JfD0syh j5beeK7KEaJVnr214TqA6rxANmLyZuKdbc2rr+ArDYs=
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=isFoDQTSCK2ei1moeMC377qc5Y YilUa3WzjvS9k0m893fZDUxPr5CNNkrueyX7/hnuH3YyThdlkHxTsVqiuk5R/CiE WV/0soCxRNOrcNGSz+nSpv0GUnmtsKOU6R8uEBxErqfN3RMSwrhKaE2a4i8ZKN8X KVZaIUwadvBJmg4iM=
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 990609CCFB; Mon,  9 May 2016 06:01:09 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2026B1614A6A; Mon,  9 May 2016 15:01:01 +0200 (CEST)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_26C6DDB3-38E2-44D4-83D2-A176E8752ED3"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com>
Date: Mon, 9 May 2016 15:00:57 +0200
Message-Id: <31B916CF-A12F-4A17-8C0E-887AF9A34C96@employees.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com> <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org> <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CBHZniiGRoLe6VGyiTwy8ZMInUc>
Cc: 6man WG <ipv6@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: Mon, 09 May 2016 13:01:16 -0000

--Apple-Mail=_26C6DDB3-38E2-44D4-83D2-A176E8752ED3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

>>>>> Based on the discussion, I think there is agreement to keep the =
text in the rfc2460bis -04 draft about not inserting extension headers.  =
I made a change to the second sentence regarding encapsulation based on =
the email discussion:
>>>>>=20
>>>>> Extension headers must never be inserted by any node other than =
the
>>>>> source of the packet.  One approach to meet a requirement to add
>>>>> extension headers is to use IP Encapsulation, for example, as =
defined
>>>>> in [RFC2473].
>>>>>=20
>>>>> Please let me know if this is OK.
>>>>>=20
>>>>> The other related proposed text regarding not deleting or changing =
the size of extension headers is:
>>>>>=20
>>>>> Extension headers must never be deleted or changed in size by any
>>>>> node on the path the packet takes.
>>>>>=20
>>>>> The contents of an Extension header or Option in an Extension =
header
>>>>> may be modified if this is permitted by the definition of the
>>>>> Extension header or option.
>>>>>=20
>>>>> This was proposed earlier on the list.  I think it is consistent =
the prohibition against inserting extension headers.
>>>>>=20
>>>>> Please comment.
>>>>=20
>>>> I am not convinced we can add this paragraph.
>>>>=20
>>>> Have you evaluated the consequence for a BITW implementation of =
e.g. IPsec (RFC4301)?
>>>> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>>>=20
>>> There would be consequences if it said "must not be modified unless =
this is permitted".
>>> But it doesn't. It says "may be modified if this is permitted", =
which as I said a couple
>>> of days ago is really a no-op.
>>=20
>> If it is a no-op what purpose does the text serve?
>=20
> Not much - it states the obvious, doesn't it?
>=20
>> I presume you are only referring to the second paragraph?
>=20
> Yes.

=46rom that can I interpret you such that you would be happy with not =
making any changes to 2460?

Ole


--Apple-Mail=_26C6DDB3-38E2-44D4-83D2-A176E8752ED3
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

iQEcBAEBCgAGBQJXMIoMAAoJED4aXnjSQuKWIGIH/jB5NitRwdeZSrycLHOufRhx
DlQ//551XUqwFjLCZr5z8iykJpmdPh2+EWJorJWEnwyGEcM7qTtsXnhTRvU+8J0D
RL1hpksKNWdTXTc0Wyc1F7CavYzQvs4wVzuGm3ByoT1GCeZUbXu4EjmCv+NhB3t6
DjqvVf8L41/OOcy5QTdjichbv+Sr7lkZa8Yz84BZALe6EeBM237/1faJxdMJ3XUx
M1iFMC8TGliQGvcntU55BeKdCXibCB/oOf3AQ8qJ3ow70TPBq5hd1etVTHlY/gW5
ynKt02mgzTR+8jt12y9l/ZTuU0VMi/kIz6/wb1o5zAdjYS9T+RKDU8ij055AdAI=
=8xYW
-----END PGP SIGNATURE-----

--Apple-Mail=_26C6DDB3-38E2-44D4-83D2-A176E8752ED3--


From nobody Mon May  9 09:52:32 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 153F312D11E for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 09:52:31 -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 aLCOfMXdKLG6 for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 09:52:29 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 3C0A112D116 for <ipv6@ietf.org>; Mon,  9 May 2016 09:52:29 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id g133so255318251ywb.2 for <ipv6@ietf.org>; Mon, 09 May 2016 09:52:29 -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=yuuKIwSU7S6VeBSOgx+Wm6bw1xLCk5BupEzicAkcNV4=; b=jEp5N+AKMBiRiTm4EAlu+XjZJMydWI4t8X/teCuwO9L1cYEO5jX95+2xWw4nwfbnkG Y7LSDxIjwwEPB8g8iLg1APul0J5uWUerrdq141IApkQpAY0RukBPHhnFeb1qrpRm8Mhr +n3bfwtCm0UuauiKgLaUzP6kUZeW61KsV9/z0FGRRsfMZvWEUoP4EFxAoOuIClV/pk7P 44RdSSTE2P4IoGvL5DeP4jinwVoXGznDg6Huk2FNJ7U9r+7gPoevK8iqG1mXG+L8mdBw u86W6BJpyNO8yIT7iJ6Ydw5dDi2kMoLuQGMmaXmCdmojEbQ1ScttKx/g+9hUGgC1NDEf I4Hw==
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=yuuKIwSU7S6VeBSOgx+Wm6bw1xLCk5BupEzicAkcNV4=; b=SsnidTCVosGyS2GQN6HJ4FJZb0PJ/++Sj4wg+lyPN64I5Pp4yLdzUhNmliRPmaGTc0 B3BLH7HxgSrE3ylQOLaIegv8WuVqTWsN8WWoiOxKoOn4XCYiijsfHw5Yq3g9iSsUKv3s pEb1GGk6QeM9eb4cWZaSoGCNGQUBEozjRo/eJErP+oxsOoT4vh0tMLbspr551ATpeNaf yM9pjtQS9mPj0+Z5fCOZ2k3tsdELAZB4VByMdess2ypovvkwEbwPKiOb6ATGH052QHvl lA2+tsoKQ0p4NU6WRzwmboKTyAm8OL2Fg8cIqKyKImz1DzGExncRljgkdOLzPcYuaHkm H0XQ==
X-Gm-Message-State: AOPr4FWlFbfqft4TOCWhCPrhlY8ukDsNTpSk/ZWtqM8zwlnjs/IXXkhhDahqQhYkbSpJ8A==
X-Received: by 10.129.97.130 with SMTP id v124mr20507030ywb.269.1462812748490;  Mon, 09 May 2016 09:52:28 -0700 (PDT)
Received: from ?IPv6:2601:647:4d00:abf0:345d:ca50:a9ac:2fc0? ([2601:647:4d00:abf0:345d:ca50:a9ac:2fc0]) by smtp.gmail.com with ESMTPSA id i188sm18039698ywc.19.2016.05.09.09.52.27 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 09 May 2016 09:52:27 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_44710294-283B-4F2D-9CB9-8BEAA20B5FEA"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com>
Date: Mon, 9 May 2016 09:52:25 -0700
Message-Id: <17BE623C-F983-4DF2-9EB2-37C748A6657E@gmail.com>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com> <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org> <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lA25i9LejGm5HIOCi_e8_O2hFYk>
Cc: 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: Mon, 09 May 2016 16:52:31 -0000

--Apple-Mail=_44710294-283B-4F2D-9CB9-8BEAA20B5FEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On May 8, 2016, at 2:41 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 09/05/2016 06:40, otroan@employees.org wrote:
>>>>> Based on the discussion, I think there is agreement to keep the =
text in the rfc2460bis -04 draft about not inserting extension headers.  =
I made a change to the second sentence regarding encapsulation based on =
the email discussion:
>>>>>=20
>>>>> Extension headers must never be inserted by any node other than =
the
>>>>> source of the packet.  One approach to meet a requirement to add
>>>>> extension headers is to use IP Encapsulation, for example, as =
defined
>>>>> in [RFC2473].
>>>>>=20
>>>>> Please let me know if this is OK.
>>>>>=20
>>>>> The other related proposed text regarding not deleting or changing =
the size of extension headers is:
>>>>>=20
>>>>> Extension headers must never be deleted or changed in size by any
>>>>> node on the path the packet takes.
>>>>>=20
>>>>> The contents of an Extension header or Option in an Extension =
header
>>>>> may be modified if this is permitted by the definition of the
>>>>> Extension header or option.
>>>>>=20
>>>>> This was proposed earlier on the list.  I think it is consistent =
the prohibition against inserting extension headers.
>>>>>=20
>>>>> Please comment.
>>>>=20
>>>> I am not convinced we can add this paragraph.
>>>>=20
>>>> Have you evaluated the consequence for a BITW implementation of =
e.g. IPsec (RFC4301)?
>>>> (or perhaps other BITWs like an ILNP proxy or SHIM6 proxy)
>>>=20
>>> There would be consequences if it said "must not be modified unless =
this is permitted".
>>> But it doesn't. It says "may be modified if this is permitted", =
which as I said a couple
>>> of days ago is really a no-op.
>>=20
>> If it is a no-op what purpose does the text serve?
>=20
> Not much - it states the obvious, doesn't it?

Regarding (assuming this is what is being discussed here):

  The contents of an Extension header or Option in an Extension header
  may be modified if this is permitted by the definition of the
  Extension header or option.

It is just summarizing that some exceptions headers and options allow =
their content to be changed.  Since we are making statements about =
inserting and deleting, I think it makes sense to also say that they may =
change to avoid any future argument that they are or are changeable.  =
It=E2=80=99s a clarification.

Bob



--Apple-Mail=_44710294-283B-4F2D-9CB9-8BEAA20B5FEA
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

iQEcBAEBCgAGBQJXMMBJAAoJEK7rdBF357uowAQH/30zlYc50INpIaEtEdQ1H2mv
KAQZNCMhX5uXucgQEbOaA6s9Uq5YggC7TubRe1fAR1IdHC8K9jh/VdQikFKSXWSp
mPmVcOvYUTRnYOo+T5/7rkdhzvTeprORdQxzvD+qpPm6BPPApqUajNQZVFobDH6b
eoNpqFVn64OzbaJ69/YakPR+V/h+gmhTEAXMfZwEPlWBsfp2LEmbShK+BRaUz+hr
gou8ZeP/QNU1AzpsvccXFlE4sIFu0zQAGGA0sXtbhUpGprAI34Xt+XkEh7SEx4dD
U5K45eWheyj9tDvhIuLGb9QBk1ydLUf9QREtWxOLfRyD4wqk+llo/2skfxJGJPM=
=/Z0o
-----END PGP SIGNATURE-----

--Apple-Mail=_44710294-283B-4F2D-9CB9-8BEAA20B5FEA--


From nobody Mon May  9 09:55:39 2016
Return-Path: <joelja@bogus.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 81F4B12D149 for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 09:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 Ot8mc8XaGYCZ for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 09:55:37 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 0C48912D130 for <ipv6@ietf.org>; Mon,  9 May 2016 09:55:37 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4204:51:fd31:95a6:767e:53cd]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u49GtU34000944 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 9 May 2016 16:55:30 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4204:51:fd31:95a6:767e:53cd] claimed to be mb-2.local
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Fernando Gont <fgont@si6networks.com>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Mark Smith <markzzzsmith@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <12014.1461868866@obiwan.sandelman.ca> <CAO42Z2xShXYX=4Yso1unxUSbvaVKSczo0NyoiPnbcJ3qvsGHpg@mail.gmail.com> <4af9c8a2c9c843f9a68f4d10e4c7fa5d@XCH-RCD-001.cisco.com> <572A6D70.2080601@si6networks.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <9e97ac01-52cb-cbc1-f6c8-f0006235262c@bogus.com>
Date: Mon, 9 May 2016 09:55:29 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1
MIME-Version: 1.0
In-Reply-To: <572A6D70.2080601@si6networks.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7qAEJ5meQ6jBFIwWUlJUlWGsbTIJrRvwV"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rVz8jPOY4QixW1-p00TXxjjF9HI>
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, 09 May 2016 16:55:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7qAEJ5meQ6jBFIwWUlJUlWGsbTIJrRvwV
Content-Type: multipart/mixed; boundary="lOPKebc3qq01RlteBMDafFkEBjq9cqSCo"
From: joel jaeggli <joelja@bogus.com>
To: Fernando Gont <fgont@si6networks.com>,
 "Pascal Thubert (pthubert)" <pthubert@cisco.com>,
 Mark Smith <markzzzsmith@gmail.com>,
 Michael Richardson <mcr+ietf@sandelman.ca>
Cc: 6man WG <ipv6@ietf.org>
Message-ID: <9e97ac01-52cb-cbc1-f6c8-f0006235262c@bogus.com>
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com>
 <12014.1461868866@obiwan.sandelman.ca>
 <CAO42Z2xShXYX=4Yso1unxUSbvaVKSczo0NyoiPnbcJ3qvsGHpg@mail.gmail.com>
 <4af9c8a2c9c843f9a68f4d10e4c7fa5d@XCH-RCD-001.cisco.com>
 <572A6D70.2080601@si6networks.com>
In-Reply-To: <572A6D70.2080601@si6networks.com>

--lOPKebc3qq01RlteBMDafFkEBjq9cqSCo
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/4/16 2:45 PM, Fernando Gont wrote:
> On 04/29/2016 04:05 PM, Pascal Thubert (pthubert) wrote:
>> Hello Mark:
>>
>> =D8  4) troubleshooting modifications that cannot or cannot easily be
>> attributed to a specific node can be very time-consuming, require out =
of
>> hours work and are likely to require potentially disruptive packet
>> capturing within or downstream of each network element that could have=

>> modified the packet (assuming it is possible to access that NE or link=
).
>>
>> DetNet has the concept of Replication and Elimination, which created
>> intermediate sources and sinks, and certainly observed that need.
>=20
> I think the original question was different.
>=20
> The original question was whether inserting headers is part of RFC2460,=

> and whether it makes sense to clarify this.

It's not obvious how you do this reliably without running into MSS issues=
=2E

> Thanks,
>=20



--lOPKebc3qq01RlteBMDafFkEBjq9cqSCo--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlcwwQIACgkQ8AA1q7Z/VrIddQCbBKRiy9K3YDDMVpiqVF7TZ0R2
5RsAnRd3D8BcafFmZZSQdszbddbYgH/K
=WkpQ
-----END PGP SIGNATURE-----

--7qAEJ5meQ6jBFIwWUlJUlWGsbTIJrRvwV--


From nobody Mon May  9 14:47: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 7EA7E12D0C5 for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 14:47:07 -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 CTmiwm-HKUtq for <ipv6@ietfa.amsl.com>; Mon,  9 May 2016 14:47:05 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 ADE4112B00A for <ipv6@ietf.org>; Mon,  9 May 2016 14:47:05 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id y69so79731506pfb.1 for <ipv6@ietf.org>; Mon, 09 May 2016 14:47:05 -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=VOd7zIRVAPSGOSh1aUlu+UoawuhWvoCvFlXDfae1GMk=; b=00+O86O/AWksFi94sMpuDbSEGek3iICuIL8Ohp0UIzYpWx9+LsTG98sSzwJYbmzBc4 Zvm8hrg8FkN2JLEbszCk4We8lkub89IEImgDtepJRzJ6Id+PXFAs4aLHn6NkG7sdgT1Y dCNqmzzdQoPxrpPQvr+wmTHxQ6wuBLXQH32Kzx5saWw7imqB6/rEEHhyCAnUKtis9Xdo OCYIJgsHGIH9C0ggke51IMI/Eh3lfsNZf2d2G6gpVKJlcGqzXo8pBKNcXkRHmM/pbJ83 NrdF4Txyvyf9kMhBB+45Fy2pS9ndzXfDOe3jz8Ug5qXr8yEiBhU4lDZO5EoQ9eRb67Fw QDmA==
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=VOd7zIRVAPSGOSh1aUlu+UoawuhWvoCvFlXDfae1GMk=; b=PyFO37hcahqtgn1fCfYzJtIa/X3nEPya22d5Tsxj4BfT0UCx8gImxb3euGX4Dep6I9 SsEuAH0Y2O9sZ0V4nziZiBxIKb0mqZa1vfh1A8wAYnyTyaluIsjpCh7kpmW7sBEKVEpU zHrpvxraRKRJ7xWR9V+3pemzm1nRQmDDeQgqieEJJ8UzFy68ycsHkdqPJ3tWezkcSuvo PtFR/OZMQWpnIR/+Cevta/rtqdJXIhlR9YyH/nVqvNYkU3x4Nyt07a9IntTbEUSptl+4 5CCb0LCHVWkhpyv+1i2DOFtprYPCHegD+CMoYsT3VklUx68WeYnU/6PSpb+HwAJwrLMi ofZg==
X-Gm-Message-State: AOPr4FVajwjel1/3IPdBFoXk87OxbZJcLISDa/fxCGjl2yVuWgpu8299ZEZJkF3r4eVfjA==
X-Received: by 10.98.20.131 with SMTP id 125mr54230766pfu.166.1462830425319; Mon, 09 May 2016 14:47:05 -0700 (PDT)
Received: from [10.10.16.137] ([125.7.18.33]) by smtp.gmail.com with ESMTPSA id dh4sm42879437pad.37.2016.05.09.14.47.01 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 14:47:03 -0700 (PDT)
Subject: Re: Inserting Extension Headers or not [was rfc2460bis question ]
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
References: <E330D833-9CE9-4CEB-9989-26B6E69AA362@gmail.com> <BLUPR05MB1985CE36404529EA59429C92AE650@BLUPR05MB1985.namprd05.prod.outlook.com> <17698869-50BC-42EB-AE49-62246080A374@gmail.com> <d3de0ead-6cd3-d0ba-9b54-de224dab2b1b@gmail.com> <5722B3FA.1090707@si6networks.com> <AC76D0C3-CE50-4CB8-8AFD-7DB754A1563D@gmail.com> <A9BD7079-202B-4F62-84DA-705F1C18A873@employees.org> <0bd978c7-4014-6293-5c61-a02885beae8b@gmail.com> <EC27C89F-955B-405F-9040-6E6676B484B9@employees.org> <4a54017b-3b87-9dee-0f54-6d725a2d6c5d@gmail.com> <17BE623C-F983-4DF2-9EB2-37C748A6657E@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b3e62467-3e71-1632-a8b5-2c39a325e32e@gmail.com>
Date: Tue, 10 May 2016 09:47:20 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <17BE623C-F983-4DF2-9EB2-37C748A6657E@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/i4M6i_wyGwGPkfToTdKvMbOrx6M>
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, 09 May 2016 21:47:07 -0000

On 10/05/2016 04:52, Bob Hinden wrote:

<snip>

> Regarding (assuming this is what is being discussed here):
>=20
>   The contents of an Extension header or Option in an Extension header
>   may be modified if this is permitted by the definition of the
>   Extension header or option.
>=20
> It is just summarizing that some exceptions headers and options allow t=
heir content to be changed.  Since we are making statements about inserti=
ng and deleting, I think it makes sense to also say that they may change =
to avoid any future argument that they are or are changeable.  It=E2=80=99=
s a clarification.

Exactly. It's a judgment call whether to include it.

Ole: I support the changes that Bob proposed, but if there is an objectio=
n to this
particular clarification sentence I have no strong objection to removing =
it.

   Brian


From nobody Tue May 10 05:53:21 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 7025F12B03D for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 05:53:19 -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 4heuLZEnxR_v for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 05:53:16 -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 ED68412D6A2 for <6man@ietf.org>; Tue, 10 May 2016 05:53:15 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lrp0077.outbound.protection.outlook.com [213.199.154.77]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-16-J7BjgxE9QmCgz_GiBnjXXA-1; Tue, 10 May 2016 13:53:09 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZDwyAwXq9m8uf0wSCViABbnxmt8MkWfZiJasXTfgQAI=; b=LYH3+8Cz23u9Nn9JZ3GQopXYOZpCTRlNGu4ytrvDOhK9jnHzF0WrwqO0IZ0G6/Bzh7faZPMfkiBj5n4lBJC+ljFMmICmi4qD7/OmRiIO1U0dt7mbkIUWubKwTAkfY2B3imG+WY0l3SLTRTV/mDJaXT46hgvtxH6xTW4sNuQNoZk=
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB453.eurprd07.prod.outlook.com (10.242.106.143) with Microsoft SMTP Server (TLS) id 15.1.492.11; Tue, 10 May 2016 12:53:08 +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.0492.016; Tue, 10 May 2016 12:53:08 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Ronald Bonica <rbonica@juniper.net>
Subject: Re: draft-ietf-6man-segment-routing-header-01
Thread-Topic: draft-ietf-6man-segment-routing-header-01
Thread-Index: AdGm5nLT9DFCNkt9SweF+/9sQdP8yAD1HMuA
Date: Tue, 10 May 2016 12:53:08 +0000
Message-ID: <96D1CEF7-A2E9-43C1-8368-0D7DC78E58BB@jisc.ac.uk>
References: <BLUPR05MB19856AEFD77BD9C4A9F618F2AE7C0@BLUPR05MB1985.namprd05.prod.outlook.com>
In-Reply-To: <BLUPR05MB19856AEFD77BD9C4A9F618F2AE7C0@BLUPR05MB1985.namprd05.prod.outlook.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: [212.188.254.49]
x-ms-office365-filtering-correlation-id: 974a2f5d-a727-4216-1152-08d378d20965
x-microsoft-exchange-diagnostics: 1; AMSPR07MB453; 5:CvTlIx82aElzrdAL3qprxoNWDjyarSHLoFogMIxiVd3evLNJzAOPl6uxzlVlI2UQ2ngPBTTfbuhZU2vY7aZBN1c3x3GIbjkT3uFbEC7BUiI0p3zOOLFQsKBQsCuL2CFHev2RwcV2bCT70PXFyVpf5g==; 24:ZfpNG1afD1Flw1QsNn7PqAncpY7UJ4bmrNCTeBUy05BbZ93ZkGrkbVVs7pcRpAB3P5P1gVVS+IrAMhxBy0J4IAdZ/lhPOqMbvYQSgN3r0wE=; 7:lIPg5kDYy0hiFsBP2pxrZNDAhxJJguBvX0bEYf0tKMjEhoDIYjIoU6q5Fe9JYNGVmGerkh1FNsIBKgr14ulTMfoUNw5VQAtwGwfzxhgrMVnKgxYW28pLNT1ypDDsduf4XyAd7WkGhEKJuvbIsL6EI4foiH94OXYUTgSCgCza3uNC01gTW4j3C0Xu2s1yAIAc; 20:6rAN8U1kVa/jycTMMGyjaa5waDGEG8sZmRw/Jn4wLauy45I5btz8de492yiGJJuiEWb63FE52sBQkUoUdsH1urvTYBKHNTGaLCWT+kjJiakMXaABwGdWDjgWCtW+uxgMAO+C5zG93ZaQ5DUQ6GIiqZFTReC8uTbWivsxWTx5P/c=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB453;
x-microsoft-antispam-prvs: <AMSPR07MB45343561908DA308FE50909D6710@AMSPR07MB453.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:AMSPR07MB453; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB453; 
x-forefront-prvs: 0938781D02
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(81166005)(5002640100001)(33656002)(83716003)(76176999)(586003)(50986999)(92566002)(6116002)(3846002)(102836003)(77096005)(66066001)(74482002)(3660700001)(1220700001)(57306001)(31430400001)(122556002)(3280700002)(2900100001)(11100500001)(86362001)(2950100001)(110136002)(8936002)(36756003)(5004730100002)(230783001)(19580395003)(19580405001)(10400500002)(82746002)(2906002)(189998001)(5008740100001)(50226002)(87936001)(7059030)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB453; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-ID: <FB787FAABA45FF40B7B4E50E323E6999@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2016 12:53:08.4049 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB453
X-MC-Unique: J7BjgxE9QmCgz_GiBnjXXA-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4OLeIlxbLeoX4MjwF2j_sG_tlwE>
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, 10 May 2016 12:53:19 -0000

Hi Ron,

> On 5 May 2016, at 17:31, Ronald Bonica <rbonica@juniper.net> wrote:
>=20
> Stephano,
>=20
> Sections 1 and 2 of draft-ietf-6man-segment-routing-header-01 are, for th=
e most part, redundant with text that can be found in draft-ietf-spring-seg=
ment-routing-07.  Please consider replacing those four pages of text with t=
he short paragraphs provided below
>=20
>                                                                    Ron Bo=
nica
>=20
>=20
> PROPOSED TEXT
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Segment Routing (SR) [I-D.ietf-spring-segment-routing] specifies procedur=
es through which an upstream node can determine that path that a packet tra=
verses on route to its destination. In segment routing, a path is defined a=
s a list of segments. In order to determine the path that a packet traverse=
 on route to its destination, the upstream node adds a list of segments to =
the packet. Downstream nodes steer the packet along the segments that are s=
pecified in the list.
>=20
> SR relies on control and forwarding plane components. See [draft-ietf-isi=
s-segment-routing-extensions] and [draft-ietf-ospf-ospfv3-segment-routing-e=
xtensions] for a description of control plane components.
>=20
> On the forwarding plane, SR can be instantiated by MPLS or IPv6. When SR =
is instantiated by MPLS, the segment list is represented as an MPLS label s=
tack. See [draft-ietf-spring-segment-routing-mpls] for details. When SR is =
instantiated by IPv6, the segment list is contained by a new IPv6 Routing H=
eader, called the Segment Routing Header (SRH). This document defines the S=
RH.
>=20
> The scope of this document is limitted to the SR forwarding plane as it i=
s instantiated by IPv6. Control plane topics are beyond the scope of this d=
ocument.

This text is not wholly clear on whether =91contained by=92 means insertion=
 of a new header, or an encapsulation approach.  Should it be, or is this i=
ntentionally left open?

Tim


From nobody Tue May 10 06:56:28 2016
Return-Path: <fred@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 504D012D133 for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 06:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.517
X-Spam-Level: 
X-Spam-Status: No, score=-115.517 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=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 qkxsoWErKyRq for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 06:56:25 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A85912D09C for <ipv6@ietf.org>; Tue, 10 May 2016 06:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2519; q=dns/txt; s=iport; t=1462888585; x=1464098185; h=from:to:cc:subject:date:message-id:mime-version; bh=X9A3xuH9l+uZ1ZMOKG8E3rfKiunCbXNi5efIoptBQpQ=; b=HdqrHvvjXjz7x3FMZzplFrH0SkMRlQ9awCCk9fLAak62lXBTfeK6P/qS 4z//IWF4csQgYLqYumEsfel0561P0VAWybBKu+H2ICbvtL4H8Sp98/jVV VTnpcZtKwaNGbWsdea8yhAhcSMDGUCpTRDwntnua2AsriZIx+6koZTG8t U=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BEBQAF6DFX/5tdJa1cgziBWLkugXaGE?= =?us-ascii?q?IEyOhIBAQEBAQEBZSeESHkSAYEAJwQOE4gdtzsBAQEBAQEBAQEBAQEBAQEBAQE?= =?us-ascii?q?BAQENCIgWikCCLgWYJwGBLoF6gWiJDY8Zjz8BJwE6ggUbgUuIeX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,604,1454976000";  d="asc'?scan'208";a="100625745"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2016 13:56:24 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u4ADuOhg009662 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 May 2016 13:56:24 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 10 May 2016 08:56:23 -0500
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Tue, 10 May 2016 08:56:23 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqsO9U1uc49vecEG1wrkiG/Alpg==
Date: Tue, 10 May 2016 13:56:23 +0000
Message-ID: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.75.21]
Content-Type: multipart/signed; boundary="Apple-Mail=_B55330A3-52C4-48C5-8313-41E88F01AEA3"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/kq5QHDRzPpHVHx-bN0o1J2K9Kec>
Cc: "ot@cisco.com" <ot@cisco.com>, "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: Tue, 10 May 2016 13:56:27 -0000

--Apple-Mail=_B55330A3-52C4-48C5-8313-41E88F01AEA3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ole and I were talking about the text in 2460bis that says

   Extension headers must never be inserted by any node other than the
   source of the packet.  IP Encapsulation must be used to meet any
   requirement for inserting headers, for example, as defined in
   [RFC2473].

      01)  Added text that Extension headers must never be inserted by
           any node other than the source of the packet.

He tells me that the justification for adding this to the =
recommendations in 2460 was that "nobody objected". I'd like to explore =
that a moment.

The current hbh draft does not discuss header insertion, but the version =
we discussed at IETF 94 most definitely did, and the segment routing =
people have certainly discussed header insertion. At IETF 94, I was not =
argued out of it; I was told that the folks concerned about it had =
agreed to another approach and was pretty much shot down by the chair. =
Mark Townsley also spoke at the mike supporting the option.

Not that I propose to add it back in.

But in view of that conversation and that version of that draft, I think =
it's not fair to say that nobody objected. Objections were not accepted.

--Apple-Mail=_B55330A3-52C4-48C5-8313-41E88F01AEA3
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 - http://gpgtools.org

iQIVAwUBVzHohkayAOS/EQ8MAQLV/w/9GQ6DTcPeIHHOrEt3rhfcugML8P+t+GD6
J2Yruan/EKd+VpLGV88qK03ZUj0jR23ZPKlvASBhVVyH9LuC9dBwSt19iHeJtL+a
b9x34smHqHixqmyanqttn0joiqbeGIWmIHbsxfBpgiLjpJHbG0haq8AKyG++XEKA
dEVTKeWsxTrrlma9QmX6nLZgkEA3MtZxLhPyp+KbbnQ9tNsJ/tMedNq431ili3HH
f3JXNezIrPSMRTbqXmgbQin+C0QSSYwg6pPhcfi3ZsqzdoJZ2VLsa9zgXhUYGeIx
VAG8DcUEbdsq5Oqo5WP8YqxgyqkdV6Oc/muKZYLBggjwLBp3L7+mShKFoCpuv4Z6
IDWb+DIcuT2M0M05NxhmmAxWd154eIoTAWZ9ps1Up+22lriMyLjLLpToAeV2UCm6
369SsoGHldozT9Hil7KnbRHnJwtSm1/pFzWW/HMMpVOAxR+OzYQ58r0oTwPBAb4y
NvGDE2hQPMN3rkacB6XnwQh60KYf6mz0IwQu3B/Ok34nz52z3IKsHKTpGwZ7cbG4
IMmJ34BjCsDCmElx1gPvyacGKiPV452+mu05bb0ZaGCtmc4ikjF4BSTAko2tc5hs
yangL4IEbGTvj3SXVuQiSmXGfDqL4oGx2VjEsJAJvxlyXUpYBBaoHdnMS+v1si0f
xCSqVr949/g=
=8G+H
-----END PGP SIGNATURE-----

--Apple-Mail=_B55330A3-52C4-48C5-8313-41E88F01AEA3--


From nobody Tue May 10 07:27:49 2016
Return-Path: <sprevidi@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 D29A412D10C for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 07:27:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 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=-0.996, 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 LF3WAHUJUI0V for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 07:27:47 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF7B112D0B8 for <ipv6@ietf.org>; Tue, 10 May 2016 07:27:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2374; q=dns/txt; s=iport; t=1462890466; x=1464100066; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=un0lqQ3sZVQbz5sXizR+DEgyyEKm0lxhz97TspUmt4w=; b=ZJdCkv0gnDOd/GXuC48yKyxVLp+VP4llp+P4etbl1KPQrmXkLDfjI+AV 9U6jPAEnNogym09pJ4pUcCU8K/IjKrKRgBEdx7eR5bv7KGdhEBfBSVqM4 IE5UxC5uYUpTfYjCuHRIPslmJpHT00IRmR/qhzR9tMLaC9FoNDV3L+kPr 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AOAgAP7zFX/4cNJK1dgzhVbg8GuSABD?= =?us-ascii?q?YF2FwuFbgIcgRQ4FAEBAQEBAQFlJ4RBAQEBAwEBAQEgEToLBQsCAQgYAgImAgI?= =?us-ascii?q?CJQsVEAIEDgWIIwgOpnWQeQEBAQEBAQEBAQEBAQEBAQEBAQEBAREEfIUkgXaCV?= =?us-ascii?q?oQ/gwArgi4Fh36LMoR3AY4djxmPPwEeAQFCggUbgUtuiAt/AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,604,1454976000"; d="scan'208";a="102920421"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 May 2016 14:27:46 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u4AERje3010887 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 May 2016 14:27:45 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 10 May 2016 10:27:45 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Tue, 10 May 2016 10:27:44 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqsgeZm+it24ICUytYB5qlO66OQ==
Date: Tue, 10 May 2016 14:27:44 +0000
Message-ID: <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com>
In-Reply-To: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.195.195]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2994042247AD524DAFD81A99BD5D5C8F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8JXhShhPcVWVkM5eZ-xuJ7HUFJU>
Cc: "ot@cisco.com" <ot@cisco.com>, Bob Hinden <bob.hinden@gmail.com>, "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: Tue, 10 May 2016 14:27:49 -0000

DQo+IE9uIE1heSAxMCwgMjAxNiwgYXQgMzo1NiBQTSwgRnJlZCBCYWtlciAoZnJlZCkgPGZyZWRA
Y2lzY28uY29tPiB3cm90ZToNCj4gDQo+IE9sZSBhbmQgSSB3ZXJlIHRhbGtpbmcgYWJvdXQgdGhl
IHRleHQgaW4gMjQ2MGJpcyB0aGF0IHNheXMNCj4gDQo+ICAgRXh0ZW5zaW9uIGhlYWRlcnMgbXVz
dCBuZXZlciBiZSBpbnNlcnRlZCBieSBhbnkgbm9kZSBvdGhlciB0aGFuIHRoZQ0KPiAgIHNvdXJj
ZSBvZiB0aGUgcGFja2V0LiAgSVAgRW5jYXBzdWxhdGlvbiBtdXN0IGJlIHVzZWQgdG8gbWVldCBh
bnkNCj4gICByZXF1aXJlbWVudCBmb3IgaW5zZXJ0aW5nIGhlYWRlcnMsIGZvciBleGFtcGxlLCBh
cyBkZWZpbmVkIGluDQo+ICAgW1JGQzI0NzNdLg0KPiANCj4gICAgICAwMSkgIEFkZGVkIHRleHQg
dGhhdCBFeHRlbnNpb24gaGVhZGVycyBtdXN0IG5ldmVyIGJlIGluc2VydGVkIGJ5DQo+ICAgICAg
ICAgICBhbnkgbm9kZSBvdGhlciB0aGFuIHRoZSBzb3VyY2Ugb2YgdGhlIHBhY2tldC4NCj4gDQo+
IEhlIHRlbGxzIG1lIHRoYXQgdGhlIGp1c3RpZmljYXRpb24gZm9yIGFkZGluZyB0aGlzIHRvIHRo
ZSByZWNvbW1lbmRhdGlvbnMgaW4gMjQ2MCB3YXMgdGhhdCAibm9ib2R5IG9iamVjdGVkIi4gSSdk
IGxpa2UgdG8gZXhwbG9yZSB0aGF0IGEgbW9tZW50Lg0KPiANCj4gVGhlIGN1cnJlbnQgaGJoIGRy
YWZ0IGRvZXMgbm90IGRpc2N1c3MgaGVhZGVyIGluc2VydGlvbiwgYnV0IHRoZSB2ZXJzaW9uIHdl
IGRpc2N1c3NlZCBhdCBJRVRGIDk0IG1vc3QgZGVmaW5pdGVseSBkaWQsIGFuZCB0aGUgc2VnbWVu
dCByb3V0aW5nIHBlb3BsZSBoYXZlIGNlcnRhaW5seSBkaXNjdXNzZWQgaGVhZGVyIGluc2VydGlv
bi4NCg0KDQpjb3JyZWN0LiBJIHJhaXNlZCB0aGUgcG9pbnQgZHVyaW5nIElFVEY5NCBtZWV0aW5n
IGFuZCByZXBlYXRlZCBpdCBpbiB0aGUgbWFpbGluZyBsaXN0LiBJ4oCZbSBhIGJpdCBzdXJwcmlz
ZWQgYWJvdXQgdGhpcyDigJxub2JvZHkgb2JqZWN0ZWTigJ0gc3RhdGVtZW50Lg0KDQpUaGFua3Mu
DQoNCnMuDQoNCg0KPiBBdCBJRVRGIDk0LCBJIHdhcyBub3QgYXJndWVkIG91dCBvZiBpdDsgSSB3
YXMgdG9sZCB0aGF0IHRoZSBmb2xrcyBjb25jZXJuZWQgYWJvdXQgaXQgaGFkIGFncmVlZCB0byBh
bm90aGVyIGFwcHJvYWNoIGFuZCB3YXMgcHJldHR5IG11Y2ggc2hvdCBkb3duIGJ5IHRoZSBjaGFp
ci4gTWFyayBUb3duc2xleSBhbHNvIHNwb2tlIGF0IHRoZSBtaWtlIHN1cHBvcnRpbmcgdGhlIG9w
dGlvbi4NCj4gDQo+IE5vdCB0aGF0IEkgcHJvcG9zZSB0byBhZGQgaXQgYmFjayBpbi4NCj4gDQo+
IEJ1dCBpbiB2aWV3IG9mIHRoYXQgY29udmVyc2F0aW9uIGFuZCB0aGF0IHZlcnNpb24gb2YgdGhh
dCBkcmFmdCwgSSB0aGluayBpdCdzIG5vdCBmYWlyIHRvIHNheSB0aGF0IG5vYm9keSBvYmplY3Rl
ZC4gT2JqZWN0aW9ucyB3ZXJlIG5vdCBhY2NlcHRlZC4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gSUVURiBJ
UHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQo+IGlwdjZAaWV0Zi5vcmcNCj4gQWRtaW5p
c3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
aXB2Ng0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQo=


From nobody Tue May 10 14:04: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 2BC8112D5FF for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 14:04:10 -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 WQAL52uvjJy8 for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 14:04:07 -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 AF93812D154 for <ipv6@ietf.org>; Tue, 10 May 2016 14:04:07 -0700 (PDT)
Received: by mail-pa0-x232.google.com with SMTP id iv1so9389426pac.2 for <ipv6@ietf.org>; Tue, 10 May 2016 14:04: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=E0N304KfOEcN2QPOf/4dp9tQyTmSPpOh76kCAzPewiA=; b=kN7G3ZdyYR/VFlBQcSc1iiriv73+m3R2HsFbk9KcmnJUiPDMLvIZJnJ/CKyi7I4OmV U/kFbsbwnjIMjH5SzasaNlSxGH0HY/tcV63v1MsB2r1OVzQZ/xl/xrcvciW2DgSXuXec Dc83rYCy6P3DzzGwIiS3leeXjIKgA44s0r53hV9ypH7P+G3LRniz+0ruSAKscAMuEgjY ig+PxYxMgQsXWvnGnRho7nE42HyOrU6PfmWnVHHGVV8TZlue3HsADqkqJAt1J+Tv0o5h 7R6MP+1hwANexCuCpiIplNBmBw8UYPNUCCfZms8+gxIXKxljlJ1tntaE4GNgjLJJm/iR zDZg==
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=E0N304KfOEcN2QPOf/4dp9tQyTmSPpOh76kCAzPewiA=; b=MUGBouFZYlahQHcmzhGy2GNY3jbBdap1KGcaVTX+hGahO4XgoopwNbMb0fGGB52rXn M34OAZE6vsftL2w0Frb4CMxUqNjpCOgJ1EPfApa/lbylgv4oQFWjlRinfMVsm6UPlizv OdMbbRafqx0TDWo/eupAKKb+krrNjQhQBKTt9bj2Xl7ONvTJVNZOusDtI+A7LSRaYD7I LBY8jQUUyimjucJhD16xbkN7GJfgTNTYjBq+lRUwnxgcc6AiIIPYfw5j2b6o1B5Hh7eM f9OX7yBXA5uqUJ18695PU/jTJbkwA3SxqEmR9f+YH1DbDFKr6razHGTr1P/WR5Qm9S6A aQ3Q==
X-Gm-Message-State: AOPr4FWeqDs5T8TEKGbtKnPd3ahNcqEIFizkXeMGq3NdshEB8EQhEiY2N8LvkT8crAzmig==
X-Received: by 10.66.132.103 with SMTP id ot7mr61637908pab.27.1462914247312; Tue, 10 May 2016 14:04:07 -0700 (PDT)
Received: from [10.10.16.137] ([125.7.18.32]) by smtp.gmail.com with ESMTPSA id 133sm6642717pfw.35.2016.05.10.14.04.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 May 2016 14:04:05 -0700 (PDT)
Subject: Re: Adding headers and adding options to headers
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com>
Date: Wed, 11 May 2016 09:04:24 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DmE3NruOVZmMirjRe2NvIYUiPzQ>
Cc: "ot@cisco.com" <ot@cisco.com>, Bob Hinden <bob.hinden@gmail.com>, "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: Tue, 10 May 2016 21:04:10 -0000

On 11/05/2016 02:27, Stefano Previdi (sprevidi) wrote:
>=20
>> On May 10, 2016, at 3:56 PM, Fred Baker (fred) <fred@cisco.com> wrote:=

>>
>> Ole and I were talking about the text in 2460bis that says
>>
>>   Extension headers must never be inserted by any node other than the
>>   source of the packet.  IP Encapsulation must be used to meet any
>>   requirement for inserting headers, for example, as defined in
>>   [RFC2473].
>>
>>      01)  Added text that Extension headers must never be inserted by
>>           any node other than the source of the packet.
>>
>> He tells me that the justification for adding this to the recommendati=
ons in 2460 was that "nobody objected". I'd like to explore that a moment=
=2E
>>
>> The current hbh draft does not discuss header insertion, but the versi=
on we discussed at IETF 94 most definitely did, and the segment routing p=
eople have certainly discussed header insertion.
>=20
>=20
> correct. I raised the point during IETF94 meeting and repeated it in th=
e mailing list. I=E2=80=99m a bit surprised about this =E2=80=9Cnobody ob=
jected=E2=80=9D statement.

I agree (even though I support the proposed text). What we are supposed t=
o be doing
is making sure that 2460bis is an unambiguous statement of rough consensu=
s (and in
this case, we are arguing about the intention of 2460 where it left some =
doubt).

    Brian

> Thanks.
>=20
> s.
>=20
>=20
>> At IETF 94, I was not argued out of it; I was told that the folks conc=
erned about it had agreed to another approach and was pretty much shot do=
wn by the chair. Mark Townsley also spoke at the mike supporting the opti=
on.
>>
>> Not that I propose to add it back in.
>>
>> But in view of that conversation and that version of that draft, I thi=
nk it's not fair to say that nobody objected. Objections were not accepte=
d.
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Tue May 10 23:13:10 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 0698A12D198 for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 23:13:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 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=-0.996, SPF_PASS=-0.001] autolearn=ham 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 05JvMqYBWBS1 for <ipv6@ietfa.amsl.com>; Tue, 10 May 2016 23:13:05 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D3F212D13C for <ipv6@ietf.org>; Tue, 10 May 2016 23:13:05 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id D540B9CC4F; Tue, 10 May 2016 23:13:03 -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=9e7FN10+yofjr1aiadcJShYHJOY=; b= sU131ra+eDgBPI8cUAuvDeQM1Qibq1RX79Q4Q5FYB78dcMOnXiwFxdz8bFAyVdaF jB7xTumQPO8LbYnCCU1x0HCGawwrH98v90qzK3lYA2UFEmBty+4Y8RxlzgD72UL6 d2hXS1hH5js7pXnp2f7k2fU/D+QoeUhaRAvSuMqTvZI=
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=k5X45ttEiLR0yNjzxenDGmeVP4 sSCbSi09oXdeXXwnWKs/oBj2O8EWzuNPvh/opBn9ikBB7QplpNmAy5bha7yrdSq7 oaIBkk+rJU7PhmzeZkPchUrRTlr9jlqc0ezAYc68BjMRp7sKLUli8qR4zpUFpmcZ VSbfdrEv0BbD987nA=
Received: from h.hanazo.no (2.150.0.40.tmi.telenormobil.no [2.150.0.40]) (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 8C3309CC0F; Tue, 10 May 2016 23:13:03 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 64F3916261DF; Wed, 11 May 2016 08:13:00 +0200 (CEST)
Subject: Re: Adding headers and adding options to headers
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_DE862246-FBBE-4E69-9D0A-446205EEA744"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com>
Date: Wed, 11 May 2016 08:12:56 +0200
Message-Id: <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/o2ZCkQ2XktQMME7Yq1KS43ypyb0>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 06:13:08 -0000

--Apple-Mail=_DE862246-FBBE-4E69-9D0A-446205EEA744
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

>> correct. I raised the point during IETF94 meeting and repeated it in =
the mailing list. I=E2=80=99m a bit surprised about this =E2=80=9Cnobody =
objected=E2=80=9D statement.
>=20
> I agree (even though I support the proposed text). What we are =
supposed to be doing
> is making sure that 2460bis is an unambiguous statement of rough =
consensus (and in
> this case, we are arguing about the intention of 2460 where it left =
some doubt).

I don't see how finding the intention is particularly important nor =
useful.

Best regards,
Ole

--Apple-Mail=_DE862246-FBBE-4E69-9D0A-446205EEA744
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

iQEcBAEBCgAGBQJXMs1sAAoJED4aXnjSQuKWS3EH/RTDvrnvLJqnhGnrG/+Xv0JW
rmWVvx1I8uz4GwyKfl5bvLgm+iKHr3METW4TUJsgiDOsjJpWsnVTLj2s1lxycSHO
gyn7bpl1tnyrjiXcyUheFYq62Ki7oFrf/LUMgDqNyaYM+4wO907AGOQe34IeI4Qe
WN9x7CHXo8JhTcaXkLaPd4B8QDKsTz5sBFyh13YXot86Q3QD5/QWkd0vJf0wvQ/e
Sg3di4VR+9Z/DfSqsVFwjj58nQIenms+gOkykvx9/L0ZDC7liWMih2nbARvXDr1H
04f/JjTFJc2tfOOpZJgtzuacXyqAXiYRYo0VlVTKLAwTvqKynNUYbouPl1Y3/vg=
=qeMz
-----END PGP SIGNATURE-----

--Apple-Mail=_DE862246-FBBE-4E69-9D0A-446205EEA744--


From nobody Wed May 11 01:22:41 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 4DFF012D1CE for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:22:40 -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 JQdWYkypFeCl for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:22:38 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 574A312D1C8 for <ipv6@ietf.org>; Wed, 11 May 2016 01:22:38 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id y69so15916603pfb.1 for <ipv6@ietf.org>; Wed, 11 May 2016 01:22:38 -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=z1pw3V3AkW16haof677H7CPDjq8KgU5HO2g1xInEQA0=; b=VP5KmR59kYo4ZV9eNBcLvGAMAhK9VTrQ4bqDtro+0R1wdWSzvYfI5FnDuQ6P3hCOzI uLrVV7qqVrmZKMQ/QskKyyte+6IT8tmZnOZ5dqc6sdxxu4pWD2sv3ODnhgxV7K5Lg7Nc TILt0gWa5IOHBLPRRj2qYum0gE1kuEW0JWO6WFnvgHGyEFuPIH5nvGXFt6xAvWqL8qdD 16fpOfanP7kxYEk9P4Ts5Mm7JNB+bro4kPbqerKKriV/BLFryG3iP0woZdHrdzBXNk+o ObwY6Kk3448dkyJVYBmv+OybZSd+9fKlp0tmZnMptudr19qeX32bsGsfd/dLWioa3q9+ ke6w==
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=z1pw3V3AkW16haof677H7CPDjq8KgU5HO2g1xInEQA0=; b=SJKO8fpohC0Sa9pPL37FXHirPjHaEFLkxvQRyh7ITo0wh2NQGs0qZqvVQnExCyQ7rA VRaCYUDb09qPD3DRHu/gn7DTv4ENvM39BFWTQBFeUIzTlUFG+F4I2WVRB4w0dqBLVjnu Zzl9NcXJKP+xZZqNa4webN14Hrh0gMmvpRPKjuV6XiWrMUUnG3C0t2t7Fh9xVoCsy+go fHe4O6ekq8c8MnNlqSnTpia5sjeI1BbiGNXkklXOqJyKdBO5PihEj60vEOxbFMDhEqt1 U2x6lShGm9ouGbuCTA+ee2gEtnAyzCMPF02kXtYYYYwpwS6dr5VptjYTgVT7stUFw1cP 2dvg==
X-Gm-Message-State: AOPr4FVRhjTTAP7Fdt64ZQX6Q5y8XvL43Z9ZxdUVW52FmTa2YFnBIyCglOq+YfDGX+7Ovw==
X-Received: by 10.98.87.220 with SMTP id i89mr2738210pfj.107.1462954957765; Wed, 11 May 2016 01:22:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:7670:1:28cc:dc4c:9703:6781? ([2406:e007:7670:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m184sm10011090pfb.22.2016.05.11.01.22.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 01:22:36 -0700 (PDT)
Subject: Re: Adding headers and adding options to headers
To: otroan@employees.org
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
Date: Wed, 11 May 2016 20:22:57 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Dgwqgmjf3ToN8DYaACYjdvbN2DU>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 08:22:40 -0000

Ole,
On 11/05/2016 18:12, otroan@employees.org wrote:
>>> correct. I raised the point during IETF94 meeting and repeated it in =
the mailing list. I=E2=80=99m a bit surprised about this =E2=80=9Cnobody =
objected=E2=80=9D statement.
>>
>> I agree (even though I support the proposed text). What we are suppose=
d to be doing
>> is making sure that 2460bis is an unambiguous statement of rough conse=
nsus (and in
>> this case, we are arguing about the intention of 2460 where it left so=
me doubt).
>=20
> I don't see how finding the intention is particularly important nor use=
ful.

Look way back in this thread to where I traced the WG rough consensus on =
this
point in 1995; it's why I've read RFC1883/RFC2460 one way, but others (e.=
g. the segment
routing people) read it differently. I really think we need to fix that a=
mbiguity
for the Internet Standard step.

Regards

    Brian


From nobody Wed May 11 01:39:34 2016
Return-Path: <sprevidi@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 4F89612D7DF for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 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=-0.996, 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 0CiIXZ07iRFW for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:39:30 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEF3912D856 for <ipv6@ietf.org>; Wed, 11 May 2016 01:39:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2004; q=dns/txt; s=iport; t=1462955964; x=1464165564; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GaL8ws7k90xqGwkzYs7+x0OmUtwk1lAr4g+umAZ1HuM=; b=Ormz0qKQMKmWtE8TmvJKiQGfq2q5Px4jD+aLuNAA9C0BlUp7Hi/xBzmy 8LzDUyKd+Fao7Z7oZlYgZN4SV5SgwecDsmzYKdll6LGC73ehhSCacWJ2y 7LOEiEKMMH9lcZsayVHPGCTSs8CQJNTljn9QLoU2JplFXRJQh7uu3Yo3I Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlBQAD7zJX/5tdJa1dgziBUgatRItzg?= =?us-ascii?q?XaGEAIcgRk6EgEBAQEBAQFlJ4RCAQEBAwEjEToLBQsCAQgYAgImAgICHxEVEAI?= =?us-ascii?q?EDgWIFQMLCKc3jD8NhCkBAQEBAQEBAQEBAQEBAQEBAQEBAQEVfIUkgXYIgk6CQ?= =?us-ascii?q?4F8F4JpK4IuAQSXdjEBjCSBeYFph3mFN4YtgS+HYwEnCTKDa24BiAp/AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="271417354"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2016 08:39:24 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u4B8dNbg008864 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 08:39:23 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 04:39:22 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Wed, 11 May 2016 04:39:22 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqv9/FKs3EEbEr0GQOr9P9iNQNJ+zhWAAgAAkVICAAASTAA==
Date: Wed, 11 May 2016 08:39:22 +0000
Message-ID: <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
In-Reply-To: <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.161.123]
Content-Type: text/plain; charset="utf-8"
Content-ID: <21A084DC75BF8A4AAFB82FA60EF2A999@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7hFIaTk8Ze0_t38YKRpwwwnnt20>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 08:39:32 -0000

DQo+IE9uIE1heSAxMSwgMjAxNiwgYXQgMTA6MjIgQU0sIEJyaWFuIEUgQ2FycGVudGVyIDxicmlh
bi5lLmNhcnBlbnRlckBnbWFpbC5jb20+IHdyb3RlOg0KPiANCj4gT2xlLA0KPiBPbiAxMS8wNS8y
MDE2IDE4OjEyLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+Pj4gY29ycmVjdC4gSSBy
YWlzZWQgdGhlIHBvaW50IGR1cmluZyBJRVRGOTQgbWVldGluZyBhbmQgcmVwZWF0ZWQgaXQgaW4g
dGhlIG1haWxpbmcgbGlzdC4gSeKAmW0gYSBiaXQgc3VycHJpc2VkIGFib3V0IHRoaXMg4oCcbm9i
b2R5IG9iamVjdGVk4oCdIHN0YXRlbWVudC4NCj4+PiANCj4+PiBJIGFncmVlIChldmVuIHRob3Vn
aCBJIHN1cHBvcnQgdGhlIHByb3Bvc2VkIHRleHQpLiBXaGF0IHdlIGFyZSBzdXBwb3NlZCB0byBi
ZSBkb2luZw0KPj4+IGlzIG1ha2luZyBzdXJlIHRoYXQgMjQ2MGJpcyBpcyBhbiB1bmFtYmlndW91
cyBzdGF0ZW1lbnQgb2Ygcm91Z2ggY29uc2Vuc3VzIChhbmQgaW4NCj4+PiB0aGlzIGNhc2UsIHdl
IGFyZSBhcmd1aW5nIGFib3V0IHRoZSBpbnRlbnRpb24gb2YgMjQ2MCB3aGVyZSBpdCBsZWZ0IHNv
bWUgZG91YnQpLg0KPj4gDQo+PiBJIGRvbid0IHNlZSBob3cgZmluZGluZyB0aGUgaW50ZW50aW9u
IGlzIHBhcnRpY3VsYXJseSBpbXBvcnRhbnQgbm9yIHVzZWZ1bC4NCj4gDQo+IExvb2sgd2F5IGJh
Y2sgaW4gdGhpcyB0aHJlYWQgdG8gd2hlcmUgSSB0cmFjZWQgdGhlIFdHIHJvdWdoIGNvbnNlbnN1
cyBvbiB0aGlzDQo+IHBvaW50IGluIDE5OTU7IGl0J3Mgd2h5IEkndmUgcmVhZCBSRkMxODgzL1JG
QzI0NjAgb25lIHdheSwgYnV0IG90aGVycyAoZS5nLiB0aGUgc2VnbWVudA0KPiByb3V0aW5nIHBl
b3BsZSkgcmVhZCBpdCBkaWZmZXJlbnRseS4gSSByZWFsbHkgdGhpbmsgd2UgbmVlZCB0byBmaXgg
dGhhdCBhbWJpZ3VpdHkNCj4gZm9yIHRoZSBJbnRlcm5ldCBTdGFuZGFyZCBzdGVwLg0KDQoNCkkg
ZG9u4oCZdCBkaXNhZ3JlZSB3aXRoIHRoZSBpZGVhIG9mIHJlbW92aW5nIGFtYmlndWl0eSBmcm9t
IHRoZSBzcGVjLg0KDQpIb3dldmVyLCBJIHN0cm9uZ2x5IGFkdm9jYXRlIHRoZSBmYWN0IHRoYXQg
d2UgYXJlIG5vdCBpbiBhIHBvc2l0aW9uIHRvIGRvIGl0IGJlY2F1c2Ugd2XigJlyZSBqdXN0IGF0
IHRoZSBiZWdpbm5pbmcgb2YgRUggdXNhZ2UgYW5kIHdlIGxhY2sgb2YgZXhwZXJpZW5jZS4NCg0K
V2UgbGl2ZWQgZm9yIG1vcmUgdGhhbiAxOCB5ZWFycyB3aXRoIHRoZSBjdXJyZW50IHNwZWMsIEkg
dGhpbmsgd2XigJlsbCBzdXJ2aXZlIGFub3RoZXIgZmV3IHllYXJzIGR1cmluZyB3aGljaCB0aGUg
aW5kdXN0cnkgY2FuIGFjcXVpcmUgZXhwZXJpZW5jZSwgcmVwb3J0IGl0IHRvIGlldGYgYW5kIHRo
ZW4sIGlmIG5lY2Vzc2FyeSwgdXBkYXRlIHRoZSBzcGVjLiANCg0KVGhhbmtzLg0Kcy4NCg0KDQoN
Cj4gDQo+IFJlZ2FyZHMNCj4gDQo+ICAgIEJyaWFuDQo+IA0KDQo=


From nobody Wed May 11 01:55:52 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 66F9A12D1E4 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 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=-0.996, 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 MwHP4b31FMI1 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 01:55:48 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6547412D1CE for <ipv6@ietf.org>; Wed, 11 May 2016 01:55:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2953; q=dns/txt; s=iport; t=1462956948; x=1464166548; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=PKzkmLxI5/fzqZzu6A1wi6peS1VNPaGXUwGcJb7TJZw=; b=SCIEZjX1vPxAqOLgt+7AmYZOLw4XnImofH8BFV+pkIDeH5JJu81LFMps EWNtL2QW2/H/sL015oVZq1J6kU40XBKc4yNv7OKqv3e0re1WM/s3exipp FNjmhWD1suRh+Pe6DouTMxmJWfFyMV/NoSySoA2bvzy2lgO4hYIZ5RqoS Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQCp8jJX/4ENJK1dgzhVbg+tSotlA?= =?us-ascii?q?Q2BdhcLhW4CgTc4FAEBAQEBAQFlJ4RCAQEBAwEBAQFrCwULAgEIGC4hBgslAgQ?= =?us-ascii?q?OBYgVAwsIDrNsDYQpAQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSGIIF2CIJOgkOBf?= =?us-ascii?q?IMrgi4Fh36PeDEBjCSBeYFph3mFN4YtgS+HYwEeAQFCggUbgUtuiQoBAQE?=
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="272228615"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2016 08:55:47 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u4B8tlXH029228 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 08:55:47 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 03:55:46 -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.1104.009; Wed, 11 May 2016 03:55:46 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: Re: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqsO9U1uc49vecEG1wrkiG/Alpp+yjoUAgABu1ACAAJlCAIAAJFSAgAAElgD//7DEmQ==
Date: Wed, 11 May 2016 08:55:46 +0000
Message-ID: <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>, <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com>
In-Reply-To: <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com>
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="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AsJhCFkv0H7qX1vhC4ARXvev9Ag>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 08:55:50 -0000

Agreed,

the last thing we need is stronger rules without a deep proof that the stro=
nger rule is really needed to get the systems work and interoperate.

 Ambiguity has a good history of creating interop issues (not the case here=
 is it?). It has also provided the necessary elasticity for innovation and =
evolution. Sometimes the authors leave that ambiguity voluntary and removin=
g it for the sake of it is actually destroying their work (eg flow label).

I may have missed one but my summary of why we'd be removing this ambiguity=
 comes from 2 issues, PMTUD (which is so broken anyway) and traceability (w=
ho did what). My take is that those issues should be solved for their own s=
ake as opposed to killing the messenger.

Did this ambiguity prove useful? Yes! Because the source does not know it a=
ll. SR is a clear proof there's value in adding applicable semantics to the=
 packet. There were others before (eg RPL) and there will be more.

Regards,

Pascal

> Le 11 mai 2016 =E0 10:39, Stefano Previdi (sprevidi) <sprevidi@cisco.com>=
 a =E9crit :
>=20
>=20
>> On May 11, 2016, at 10:22 AM, Brian E Carpenter <brian.e.carpenter@gmail=
.com> wrote:
>>=20
>> Ole,
>> On 11/05/2016 18:12, otroan@employees.org wrote:
>>>>> correct. I raised the point during IETF94 meeting and repeated it in =
the mailing list. I=92m a bit surprised about this =93nobody objected=94 st=
atement.
>>>>=20
>>>> I agree (even though I support the proposed text). What we are suppose=
d to be doing
>>>> is making sure that 2460bis is an unambiguous statement of rough conse=
nsus (and in
>>>> this case, we are arguing about the intention of 2460 where it left so=
me doubt).
>>>=20
>>> I don't see how finding the intention is particularly important nor use=
ful.
>>=20
>> Look way back in this thread to where I traced the WG rough consensus on=
 this
>> point in 1995; it's why I've read RFC1883/RFC2460 one way, but others (e=
.g. the segment
>> routing people) read it differently. I really think we need to fix that =
ambiguity
>> for the Internet Standard step.
>=20
>=20
> I don=92t disagree with the idea of removing ambiguity from the spec.
>=20
> However, I strongly advocate the fact that we are not in a position to do=
 it because we=92re just at the beginning of EH usage and we lack of experi=
ence.
>=20
> We lived for more than 18 years with the current spec, I think we=92ll su=
rvive another few years during which the industry can acquire experience, r=
eport it to ietf and then, if necessary, update the spec.=20
>=20
> Thanks.
> s.
>=20
>=20
>=20
>>=20
>> Regards
>>=20
>>   Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed May 11 02:38:11 2016
Return-Path: <alexandre.petrescu@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 D334C12D57D for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 02:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 MhGJym-3IiSv for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 02:38:07 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A1B12D59A for <ipv6@ietf.org>; Wed, 11 May 2016 02:38:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4B9c3Ep013045 for <ipv6@ietf.org>; Wed, 11 May 2016 11:38:03 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6FD7220534E for <ipv6@ietf.org>; Wed, 11 May 2016 11:40:02 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 662C8205346 for <ipv6@ietf.org>; Wed, 11 May 2016 11:40:02 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4B9c3Nl020364 for <ipv6@ietf.org>; Wed, 11 May 2016 11:38:03 +0200
Subject: Re: Adding headers and adding options to headers
To: ipv6@ietf.org
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <10ab2d92-a379-8e76-d8e5-e93be50590bf@gmail.com>
Date: Wed, 11 May 2016 11:38:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/D7i_kL1fi0ZPY1CNtQDkbrFHQ-g>
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, 11 May 2016 09:38:10 -0000

Hi,

The main point is that intermediary routers dont touch forwarded 
packets.  This should be kept that way, otherwise one induces risks of 
fragmenting the Internet.

To support that statement, I am afraid one would need to dive into details:
- yes, the intermediary router MUST decrement the Hop Limit.
- yes, the intermediary router can encap/decap with new headers (list
   them all, AH, ESP, base header).
- yes the intermediary router owning an address in the dst field of a
   packet can swap it with the value in a field in an existing RH.
- no, the intermediary router can not add a DO, MH, HbH, RH,
   frag, unless it creates a new packet (encap).
- no, the intermediary router can not remove a DO, MH, HbH, RH, frag,
   unless it is decapsulating.

Alex


Le 11/05/2016 à 10:55, Pascal Thubert (pthubert) a écrit :
> Agreed,
>
> the last thing we need is stronger rules without a deep proof that
> the stronger rule is really needed to get the systems work and
> interoperate.
>
> Ambiguity has a good history of creating interop issues (not the case
> here is it?). It has also provided the necessary elasticity for
> innovation and evolution. Sometimes the authors leave that ambiguity
> voluntary and removing it for the sake of it is actually destroying
> their work (eg flow label).
>
> I may have missed one but my summary of why we'd be removing this
> ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
> traceability (who did what). My take is that those issues should be
> solved for their own sake as opposed to killing the messenger.
>
> Did this ambiguity prove useful? Yes! Because the source does not
> know it all. SR is a clear proof there's value in adding applicable
> semantics to the packet. There were others before (eg RPL) and there
> will be more.
>
> Regards,
>
> Pascal
>
>> Le 11 mai 2016 à 10:39, Stefano Previdi (sprevidi)
>> <sprevidi@cisco.com> a écrit :
>>
>>
>>> On May 11, 2016, at 10:22 AM, Brian E Carpenter
>>> <brian.e.carpenter@gmail.com> wrote:
>>>
>>> Ole, On 11/05/2016 18:12, otroan@employees.org wrote:
>>>>>> correct. I raised the point during IETF94 meeting and
>>>>>> repeated it in the mailing list. I’m a bit surprised about
>>>>>> this “nobody objected” statement.
>>>>>
>>>>> I agree (even though I support the proposed text). What we
>>>>> are supposed to be doing is making sure that 2460bis is an
>>>>> unambiguous statement of rough consensus (and in this case,
>>>>> we are arguing about the intention of 2460 where it left some
>>>>> doubt).
>>>>
>>>> I don't see how finding the intention is particularly important
>>>> nor useful.
>>>
>>> Look way back in this thread to where I traced the WG rough
>>> consensus on this point in 1995; it's why I've read
>>> RFC1883/RFC2460 one way, but others (e.g. the segment routing
>>> people) read it differently. I really think we need to fix that
>>> ambiguity for the Internet Standard step.
>>
>>
>> I don’t disagree with the idea of removing ambiguity from the
>> spec.
>>
>> However, I strongly advocate the fact that we are not in a position
>> to do it because we’re just at the beginning of EH usage and we
>> lack of experience.
>>
>> We lived for more than 18 years with the current spec, I think
>> we’ll survive another few years during which the industry can
>> acquire experience, report it to ietf and then, if necessary,
>> update the spec.
>>
>> Thanks. s.
>>
>>
>>
>>>
>>> Regards
>>>
>>> Brian
>>
>> --------------------------------------------------------------------
>>
>>
IETF IPv6 working group mailing list
>> ipv6@ietf.org Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Wed May 11 03:04:44 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 D140312D760 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 KaU8O5cWTBD9 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:04:40 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 D210912D5E5 for <ipv6@ietf.org>; Wed, 11 May 2016 03:04:39 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id s184so50335168vkb.3 for <ipv6@ietf.org>; Wed, 11 May 2016 03:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=AqBtBhqya2foW9DPSoDzS99FM18jYEDAwL/Ci1Apt4A=; b=ZPcMPmavZPVtB5Rwm0pQgbQd7mnz+TfwIyc8dBvCxjNvEO3BnoowTrLVhkrMkleg7e hYQyR9iqY7t+d93IfvifyIEzSPuwRBVCMiG2ok2oLVD+iTVzGpra3/nOtBcAmI525ocT FMTrquC8I4AhZ+qQNFwPTB2m7kJ3QFr7CYfwwq23pMi2MYW0sqM9DUEmbKOlPBrqLoDz XmRJKFuJMPMwvHwaV55KazroWaUsXtIG/8r1BLJvUGvsxg7EeRQmugiiTu+pY+g3NVyK YewHfvMtuq8vMTvdtaqeDBKK9Nncl0L1jGDX9ZaE2qSE7p3ZxWA6Soqunr+obbthhPpF Epig==
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:date :message-id:subject:from:to:cc; bh=AqBtBhqya2foW9DPSoDzS99FM18jYEDAwL/Ci1Apt4A=; b=gA8dN219ji/xaW0Ap/dvJEsSBjFp1md3xGolBteNHeE+9OZoOPvG39PTM3Ogl2BLTt id6h3yTdJORE+JYygqNufYVPv6yEJpYQ0woIfGQAY6yFf9U6u5RuQl6BojXFIht/rWVV Nw5YJczZKTFgkqoKqFzQYnjgMKnCMYHydhJu/4XbDWvJyq2WHVWXK9O8v4EljnsM/R/i O8mI+nnQjFGchtdyQmj+Xmp1LobIjrrRBpbENzuRmSsj83+ytUB9WTwWAzHrssBqkQwI Ge+UHSFMEvC7PqNJcXkax7RO1kTIGJfT3GWfpmFH91XbPjDdKo0xWdLDny1wh8qINC// TfrQ==
X-Gm-Message-State: AOPr4FVoMB9+21sHPk2vHyaPSjecOuNjZC3jCoCvVdMg67TM0QB0hbmOlty8EhN52BoTufPuz262z/lZUz+r5g==
MIME-Version: 1.0
X-Received: by 10.176.0.116 with SMTP id 107mr1081440uai.67.1462961078909; Wed, 11 May 2016 03:04:38 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 03:04:38 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 03:04:38 -0700 (PDT)
In-Reply-To: <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com>
Date: Wed, 11 May 2016 20:04:38 +1000
Message-ID: <CAO42Z2xW1ppOwuXNeGoj3qiCvqQpV_6ndwveVVDHL+XDBNy1ag@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: Mark Smith <markzzzsmith@gmail.com>
To: "Pascal Thubert, (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=001a113efac86dc52705328e2b79
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/YXXwuMWOLkAIw7ASxJiUQ269_Rw>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 10:04:43 -0000

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

On 11 May 2016 18:56, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
wrote:
>
> Agreed,
>
> the last thing we need is stronger rules without a deep proof that the
stronger rule is really needed to get the systems work and interoperate.
>

The thing I don't understand is the need for proof. Do we really need to
*prove* that adding unexpected EHs mid-flight is going to break things even
though it is foreseeable that they will, because it is easy to see how it
will interact badly with the existing mechanisms?

>  Ambiguity has a good history of creating interop issues (not the case
here is it?). It has also provided the necessary elasticity for innovation
and evolution. Sometimes the authors leave that ambiguity voluntary and
removing it for the sake of it is actually destroying their work (eg flow
label).
>
> I may have missed one but my summary of why we'd be removing this
ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
traceability (who did what). My take is that those issues should be solved
for their own sake as opposed to killing the messenger.
>

How? How are you going to trace who did what if the device silently did it?
If you don't have an answer, you're creating the problem and then making it
somebody else's problem to fix. I think people who create problems are
obligated to fix them.

Tunneling already solves these problems and facilitates adding EHs. Why are
people choosing to ignore this option? What is the unstated bias against
tunneling?

> Did this ambiguity prove useful? Yes! Because the source does not know it
all. SR is a clear proof there's value in adding applicable semantics to
the packet. There were others before (eg RPL) and there will be more.
>

The question isn't whether or not the added semantics have value.

The question is what is the best way to add those semantics that doesn't
interact badly with or cause to fail existing, widely deployed mechanisms
(like PMTUD), doesn't violate established semantics of existing fields
(like a "multi-source packet" (meaning multiple devices are the source of
parts of the packet) with a single source address field would), and doesn't
make troubleshooting an operational network harder than it already is.

In theory, these edited packets would never leak from the editing domain,
and devices that add or remove them would never need troubleshooting.
Practice and theory are rarely the same.

Regards,
Mark.

> Regards,
>
> Pascal
>
> > Le 11 mai 2016 =C3=A0 10:39, Stefano Previdi (sprevidi) <sprevidi@cisco=
.com>
a =C3=A9crit :
> >
> >
> >> On May 11, 2016, at 10:22 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
> >>
> >> Ole,
> >> On 11/05/2016 18:12, otroan@employees.org wrote:
> >>>>> correct. I raised the point during IETF94 meeting and repeated it
in the mailing list. I=E2=80=99m a bit surprised about this =E2=80=9Cnobody=
 objected=E2=80=9D
statement.
> >>>>
> >>>> I agree (even though I support the proposed text). What we are
supposed to be doing
> >>>> is making sure that 2460bis is an unambiguous statement of rough
consensus (and in
> >>>> this case, we are arguing about the intention of 2460 where it left
some doubt).
> >>>
> >>> I don't see how finding the intention is particularly important nor
useful.
> >>
> >> Look way back in this thread to where I traced the WG rough consensus
on this
> >> point in 1995; it's why I've read RFC1883/RFC2460 one way, but others
(e.g. the segment
> >> routing people) read it differently. I really think we need to fix
that ambiguity
> >> for the Internet Standard step.
> >
> >
> > I don=E2=80=99t disagree with the idea of removing ambiguity from the s=
pec.
> >
> > However, I strongly advocate the fact that we are not in a position to
do it because we=E2=80=99re just at the beginning of EH usage and we lack o=
f
experience.
> >
> > We lived for more than 18 years with the current spec, I think we=E2=80=
=99ll
survive another few years during which the industry can acquire experience,
report it to ietf and then, if necessary, update the spec.
> >
> > Thanks.
> > s.
> >
> >
> >
> >>
> >> Regards
> >>
> >>   Brian
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 11 May 2016 18:56, &quot;Pascal Thubert (pthubert)&quot; &lt;<a href=3D"=
mailto:pthubert@cisco.com">pthubert@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Agreed,<br>
&gt;<br>
&gt; the last thing we need is stronger rules without a deep proof that the=
 stronger rule is really needed to get the systems work and interoperate.<b=
r>
&gt;</p>
<p dir=3D"ltr">The thing I don&#39;t understand is the need for proof. Do w=
e really need to *prove* that adding unexpected EHs mid-flight is going to =
break things even though it is foreseeable that they will, because it is ea=
sy to see how it will interact badly with the existing mechanisms?</p>
<p dir=3D"ltr">&gt; =C2=A0Ambiguity has a good history of creating interop =
issues (not the case here is it?). It has also provided the necessary elast=
icity for innovation and evolution. Sometimes the authors leave that ambigu=
ity voluntary and removing it for the sake of it is actually destroying the=
ir work (eg flow label).<br>
&gt;<br>
&gt; I may have missed one but my summary of why we&#39;d be removing this =
ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and tracea=
bility (who did what). My take is that those issues should be solved for th=
eir own sake as opposed to killing the messenger.<br>
&gt;</p>
<p dir=3D"ltr">How? How are you going to trace who did what if the device s=
ilently did it? If you don&#39;t have an answer, you&#39;re creating the pr=
oblem and then making it somebody else&#39;s problem to fix. I think people=
 who create problems are obligated to fix them.</p>
<p dir=3D"ltr">Tunneling already solves these problems and facilitates addi=
ng EHs. Why are people choosing to ignore this option? What is the unstated=
 bias against tunneling?<br></p>
<p dir=3D"ltr">&gt; Did this ambiguity prove useful? Yes! Because the sourc=
e does not know it all. SR is a clear proof there&#39;s value in adding app=
licable semantics to the packet. There were others before (eg RPL) and ther=
e will be more.<br>
&gt;</p>
<p dir=3D"ltr">The question isn&#39;t whether or not the added semantics ha=
ve value.</p>
<p dir=3D"ltr">The question is what is the best way to add those semantics =
that doesn&#39;t interact badly with or cause to fail existing, widely depl=
oyed mechanisms (like PMTUD), doesn&#39;t violate established semantics of =
existing fields (like a &quot;multi-source packet&quot; (meaning multiple d=
evices are the source of parts of the packet) with a single source address =
field would), and doesn&#39;t make troubleshooting an operational network h=
arder than it already is.</p>
<p dir=3D"ltr">In theory, these edited packets would never leak from the ed=
iting domain, and devices that add or remove them would never need troubles=
hooting. Practice and theory are rarely the same.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; Regards,<br>
&gt;<br>
&gt; Pascal<br>
&gt;<br>
&gt; &gt; Le 11 mai 2016 =C3=A0 10:39, Stefano Previdi (sprevidi) &lt;<a hr=
ef=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>&gt; a =C3=A9crit :<=
br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; On May 11, 2016, at 10:22 AM, Brian E Carpenter &lt;<a href=
=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;=
 wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Ole,<br>
&gt; &gt;&gt; On 11/05/2016 18:12, <a href=3D"mailto:otroan@employees.org">=
otroan@employees.org</a> wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt; correct. I raised the point during IETF94 meeting=
 and repeated it in the mailing list. I=E2=80=99m a bit surprised about thi=
s =E2=80=9Cnobody objected=E2=80=9D statement.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I agree (even though I support the proposed text). Wh=
at we are supposed to be doing<br>
&gt; &gt;&gt;&gt;&gt; is making sure that 2460bis is an unambiguous stateme=
nt of rough consensus (and in<br>
&gt; &gt;&gt;&gt;&gt; this case, we are arguing about the intention of 2460=
 where it left some doubt).<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; I don&#39;t see how finding the intention is particularly=
 important nor useful.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Look way back in this thread to where I traced the WG rough c=
onsensus on this<br>
&gt; &gt;&gt; point in 1995; it&#39;s why I&#39;ve read RFC1883/RFC2460 one=
 way, but others (e.g. the segment<br>
&gt; &gt;&gt; routing people) read it differently. I really think we need t=
o fix that ambiguity<br>
&gt; &gt;&gt; for the Internet Standard step.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I don=E2=80=99t disagree with the idea of removing ambiguity from=
 the spec.<br>
&gt; &gt;<br>
&gt; &gt; However, I strongly advocate the fact that we are not in a positi=
on to do it because we=E2=80=99re just at the beginning of EH usage and we =
lack of experience.<br>
&gt; &gt;<br>
&gt; &gt; We lived for more than 18 years with the current spec, I think we=
=E2=80=99ll survive another few years during which the industry can acquire=
 experience, report it to ietf and then, if necessary, update the spec.<br>
&gt; &gt;<br>
&gt; &gt; Thanks.<br>
&gt; &gt; s.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Regards<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;=C2=A0 =C2=A0Brian<br>
&gt; &gt;<br>
&gt; &gt; -----------------------------------------------------------------=
---<br>
&gt; &gt; IETF IPv6 working group mailing list<br>
&gt; &gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; &gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/=
listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; &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>

--001a113efac86dc52705328e2b79--


From nobody Wed May 11 03:14:48 2016
Return-Path: <sprevidi@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 3FC7312D8EE for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 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=-0.996, 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 Y0ZXqIXD27AX for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:14:39 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D48012D8F9 for <ipv6@ietf.org>; Wed, 11 May 2016 03:14:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4975; q=dns/txt; s=iport; t=1462961670; x=1464171270; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=w8xwZrVURhhgveAculezEh7ZaTQdFrg3ySPSfEl1jmk=; b=MDd10eIkVxEp/HR0RzXTAkNJv6lfuntNQhsEPF10rEpSdLJBc6FCkf0L eMff1aj/k5F/ZriytAhiE1wM48IQn0i3uNGnJ+Eiv95PeLhFaMRRaQLn8 D0uUyajyKtDPkSQ5bZPM2h581VxDUglKtJhBE3ls8VLMKWmEFyleXP+Fe A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQDMBDNX/4gNJK1dgzhVfQatRItlA?= =?us-ascii?q?Q2BdhcLhW4CgTk4FAEBAQEBAQFlJ4RCAQEBAwEBAQFrCwULAgEIGC4hBgslAgQ?= =?us-ascii?q?OBYgVAwsIDrQkDYQpAQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSGIIF2glaCQ4FZI?= =?us-ascii?q?4Mrgi4Fh36PeDEBjCSBeYFph3mFN4YtgS+HYwEeAQFCggUbgUtuAYdMPn8BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="270310169"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2016 10:14:29 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u4BAESuw023763 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 10:14:28 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 06:14:28 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Wed, 11 May 2016 06:14:27 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqv9/FKs3EEbEr0GQOr9P9iNQNA==
Date: Wed, 11 May 2016 10:14:27 +0000
Message-ID: <26FE85C3-D8C0-4DA5-8BAC-50D68B1F68D9@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com> <10ab2d92-a379-8e76-d8e5-e93be50590bf@gmail.com>
In-Reply-To: <10ab2d92-a379-8e76-d8e5-e93be50590bf@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.228.89.71]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <23D9035A759F5544ACE55141722CD2F8@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iqbY8lCR2osG-Xl0iLv3frPmmRA>
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: Wed, 11 May 2016 10:14:46 -0000

> On May 11, 2016, at 11:38 AM, Alexandre Petrescu <alexandre.petrescu@gmai=
l.com> wrote:
>=20
> Hi,
>=20
> The main point is that intermediary routers dont touch forwarded packets.


I=92m afraid the reality is slightly different.

Of course, you=92ll have to define what =93touching the packet=94 means.

Inserting, pushing, removing, pop=92ing info into/from packets by transit n=
odes is being done for ages.

s.


>  This should be kept that way, otherwise one induces risks of fragmenting=
 the Internet.
>=20
> To support that statement, I am afraid one would need to dive into detail=
s:
> - yes, the intermediary router MUST decrement the Hop Limit.
> - yes, the intermediary router can encap/decap with new headers (list
>  them all, AH, ESP, base header).
> - yes the intermediary router owning an address in the dst field of a
>  packet can swap it with the value in a field in an existing RH.
> - no, the intermediary router can not add a DO, MH, HbH, RH,
>  frag, unless it creates a new packet (encap).
> - no, the intermediary router can not remove a DO, MH, HbH, RH, frag,
>  unless it is decapsulating.
>=20
> Alex
>=20
>=20
> Le 11/05/2016 =E0 10:55, Pascal Thubert (pthubert) a =E9crit :
>> Agreed,
>>=20
>> the last thing we need is stronger rules without a deep proof that
>> the stronger rule is really needed to get the systems work and
>> interoperate.
>>=20
>> Ambiguity has a good history of creating interop issues (not the case
>> here is it?). It has also provided the necessary elasticity for
>> innovation and evolution. Sometimes the authors leave that ambiguity
>> voluntary and removing it for the sake of it is actually destroying
>> their work (eg flow label).
>>=20
>> I may have missed one but my summary of why we'd be removing this
>> ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
>> traceability (who did what). My take is that those issues should be
>> solved for their own sake as opposed to killing the messenger.
>>=20
>> Did this ambiguity prove useful? Yes! Because the source does not
>> know it all. SR is a clear proof there's value in adding applicable
>> semantics to the packet. There were others before (eg RPL) and there
>> will be more.
>>=20
>> Regards,
>>=20
>> Pascal
>>=20
>>> Le 11 mai 2016 =E0 10:39, Stefano Previdi (sprevidi)
>>> <sprevidi@cisco.com> a =E9crit :
>>>=20
>>>=20
>>>> On May 11, 2016, at 10:22 AM, Brian E Carpenter
>>>> <brian.e.carpenter@gmail.com> wrote:
>>>>=20
>>>> Ole, On 11/05/2016 18:12, otroan@employees.org wrote:
>>>>>>> correct. I raised the point during IETF94 meeting and
>>>>>>> repeated it in the mailing list. I=92m a bit surprised about
>>>>>>> this =93nobody objected=94 statement.
>>>>>>=20
>>>>>> I agree (even though I support the proposed text). What we
>>>>>> are supposed to be doing is making sure that 2460bis is an
>>>>>> unambiguous statement of rough consensus (and in this case,
>>>>>> we are arguing about the intention of 2460 where it left some
>>>>>> doubt).
>>>>>=20
>>>>> I don't see how finding the intention is particularly important
>>>>> nor useful.
>>>>=20
>>>> Look way back in this thread to where I traced the WG rough
>>>> consensus on this point in 1995; it's why I've read
>>>> RFC1883/RFC2460 one way, but others (e.g. the segment routing
>>>> people) read it differently. I really think we need to fix that
>>>> ambiguity for the Internet Standard step.
>>>=20
>>>=20
>>> I don=92t disagree with the idea of removing ambiguity from the
>>> spec.
>>>=20
>>> However, I strongly advocate the fact that we are not in a position
>>> to do it because we=92re just at the beginning of EH usage and we
>>> lack of experience.
>>>=20
>>> We lived for more than 18 years with the current spec, I think
>>> we=92ll survive another few years during which the industry can
>>> acquire experience, report it to ietf and then, if necessary,
>>> update the spec.
>>>=20
>>> Thanks. s.
>>>=20
>>>=20
>>>=20
>>>>=20
>>>> Regards
>>>>=20
>>>> Brian
>>>=20
>>> --------------------------------------------------------------------
>>>=20
>>>=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
>> --------------------------------------------------------------------
>>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed May 11 03:44:34 2016
Return-Path: <alexandre.petrescu@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 2BCC112D95F for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 IU35O1cPDfZt for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 03:44:29 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66D7412D961 for <ipv6@ietf.org>; Wed, 11 May 2016 03:44:29 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4BAiP34023363; Wed, 11 May 2016 12:44:25 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 23F882053B5; Wed, 11 May 2016 12:46:24 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 162C5205317; Wed, 11 May 2016 12:46:24 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4BAiO7D008990; Wed, 11 May 2016 12:44:25 +0200
Subject: Re: Adding headers and adding options to headers
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com> <10ab2d92-a379-8e76-d8e5-e93be50590bf@gmail.com> <26FE85C3-D8C0-4DA5-8BAC-50D68B1F68D9@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <9a8545e7-9105-91b6-91e1-92650379eb18@gmail.com>
Date: Wed, 11 May 2016 12:44:24 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <26FE85C3-D8C0-4DA5-8BAC-50D68B1F68D9@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/83_fRdNUH-zgou3JfJNTcG-p5ME>
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: Wed, 11 May 2016 10:44:33 -0000

Le 11/05/2016 à 12:14, Stefano Previdi (sprevidi) a écrit :
>
>> On May 11, 2016, at 11:38 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
>>
>> Hi,
>>
>> The main point is that intermediary routers dont touch forwarded packets.
>
>
> I’m afraid the reality is slightly different.

Well, reality - just like beauty - is in the eye of the beholder

> Of course, you’ll have to define what “touching the packet” means.
>
> Inserting, pushing, removing, pop’ing info into/from packets by transit nodes is being done for ages.

If you mean IPv4 ages then it is possible I agree with you.

Alex

>
> s.
>
>
>>  This should be kept that way, otherwise one induces risks of fragmenting the Internet.
>>
>> To support that statement, I am afraid one would need to dive into details:
>> - yes, the intermediary router MUST decrement the Hop Limit.
>> - yes, the intermediary router can encap/decap with new headers (list
>>  them all, AH, ESP, base header).
>> - yes the intermediary router owning an address in the dst field of a
>>  packet can swap it with the value in a field in an existing RH.
>> - no, the intermediary router can not add a DO, MH, HbH, RH,
>>  frag, unless it creates a new packet (encap).
>> - no, the intermediary router can not remove a DO, MH, HbH, RH, frag,
>>  unless it is decapsulating.
>>
>> Alex
>>
>>
>> Le 11/05/2016 à 10:55, Pascal Thubert (pthubert) a écrit :
>>> Agreed,
>>>
>>> the last thing we need is stronger rules without a deep proof that
>>> the stronger rule is really needed to get the systems work and
>>> interoperate.
>>>
>>> Ambiguity has a good history of creating interop issues (not the case
>>> here is it?). It has also provided the necessary elasticity for
>>> innovation and evolution. Sometimes the authors leave that ambiguity
>>> voluntary and removing it for the sake of it is actually destroying
>>> their work (eg flow label).
>>>
>>> I may have missed one but my summary of why we'd be removing this
>>> ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
>>> traceability (who did what). My take is that those issues should be
>>> solved for their own sake as opposed to killing the messenger.
>>>
>>> Did this ambiguity prove useful? Yes! Because the source does not
>>> know it all. SR is a clear proof there's value in adding applicable
>>> semantics to the packet. There were others before (eg RPL) and there
>>> will be more.
>>>
>>> Regards,
>>>
>>> Pascal
>>>
>>>> Le 11 mai 2016 à 10:39, Stefano Previdi (sprevidi)
>>>> <sprevidi@cisco.com> a écrit :
>>>>
>>>>
>>>>> On May 11, 2016, at 10:22 AM, Brian E Carpenter
>>>>> <brian.e.carpenter@gmail.com> wrote:
>>>>>
>>>>> Ole, On 11/05/2016 18:12, otroan@employees.org wrote:
>>>>>>>> correct. I raised the point during IETF94 meeting and
>>>>>>>> repeated it in the mailing list. I’m a bit surprised about
>>>>>>>> this “nobody objected” statement.
>>>>>>>
>>>>>>> I agree (even though I support the proposed text). What we
>>>>>>> are supposed to be doing is making sure that 2460bis is an
>>>>>>> unambiguous statement of rough consensus (and in this case,
>>>>>>> we are arguing about the intention of 2460 where it left some
>>>>>>> doubt).
>>>>>>
>>>>>> I don't see how finding the intention is particularly important
>>>>>> nor useful.
>>>>>
>>>>> Look way back in this thread to where I traced the WG rough
>>>>> consensus on this point in 1995; it's why I've read
>>>>> RFC1883/RFC2460 one way, but others (e.g. the segment routing
>>>>> people) read it differently. I really think we need to fix that
>>>>> ambiguity for the Internet Standard step.
>>>>
>>>>
>>>> I don’t disagree with the idea of removing ambiguity from the
>>>> spec.
>>>>
>>>> However, I strongly advocate the fact that we are not in a position
>>>> to do it because we’re just at the beginning of EH usage and we
>>>> lack of experience.
>>>>
>>>> We lived for more than 18 years with the current spec, I think
>>>> we’ll survive another few years during which the industry can
>>>> acquire experience, report it to ietf and then, if necessary,
>>>> update the spec.
>>>>
>>>> Thanks. s.
>>>>
>>>>
>>>>
>>>>>
>>>>> Regards
>>>>>
>>>>> Brian
>>>>
>>>> --------------------------------------------------------------------
>>>>
>>>>
>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org Administrative Requests:
>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>
>>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>


From nobody Wed May 11 04:21:54 2016
Return-Path: <sprevidi@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 B7CC212D9DB for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 04:21:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.517
X-Spam-Level: 
X-Spam-Status: No, score=-15.517 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, 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 GpLkpK5cftmt for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 04:21:50 -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 5BBA912D9DA for <ipv6@ietf.org>; Wed, 11 May 2016 04:21:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5651; q=dns/txt; s=iport; t=1462965710; x=1464175310; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=HppQtpqv/uLU+7NWjc5ZBJGKK+YUiq0V6k0fQrelXxc=; b=ERx8ReYmvB2ju3HkJFvyY9Cm1a8dFgkNJx3VVeJL/DNtCRzVFWroGnYQ hWbz6BMa/LFGPntkwQyZdz1zLzCG9CluWSfc9gWF0NPVa50pm/4rtCuN6 yOlY+Ms74rENhw2V6adyxMn5s/wC5pQz84nUyAtrQA3SqsuJMxqYIAoX4 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5AQCHFDNX/49dJa1dgzhVfQatRItlA?= =?us-ascii?q?Q2BdhcLhW4CgTo4FAEBAQEBAQFlJ4RCAQEBAwEBAQFrCwULAgEIGC4hBgslAgQ?= =?us-ascii?q?OBYgVAw8IDrQoDYQpAQEBAQEBAQEBAQEBAQEBAQEBAQEBEQSGIIF2glaCQ4FZI?= =?us-ascii?q?4Mrgi4Fh36PeDEBjCSBeYFph3mFN4YtgS+HZAEeAQFCggUbgUtuAYdMPn8BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000"; d="scan'208";a="106838230"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2016 11:21:49 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u4BBLmsp022665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 11:21:49 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 07:21:48 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Wed, 11 May 2016 07:21:48 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqv9/FKs3EEbEr0GQOr9P9iNQNJ+yjoUAgABu1ACAAJlCAIAAJFSAgAAElgD//7DEmYAAHezwgABNdoA=
Date: Wed, 11 May 2016 11:21:48 +0000
Message-ID: <5097CD11-A590-4FA0-AEB4-2B7B981DF0E8@cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com> <10ab2d92-a379-8e76-d8e5-e93be50590bf@gmail.com> <26FE85C3-D8C0-4DA5-8BAC-50D68B1F68D9@cisco.com> <9a8545e7-9105-91b6-91e1-92650379eb18@gmail.com>
In-Reply-To: <9a8545e7-9105-91b6-91e1-92650379eb18@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.228.89.71]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F7800D2EDBB3854D95195632F1A3BBE7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Yfjo5_5fX9MsoIAwpl0YGMclEbw>
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: Wed, 11 May 2016 11:21:53 -0000

> On May 11, 2016, at 12:44 PM, Alexandre Petrescu <alexandre.petrescu@gmai=
l.com> wrote:
>=20
>=20
>=20
> Le 11/05/2016 =E0 12:14, Stefano Previdi (sprevidi) a =E9crit :
>>=20
>>> On May 11, 2016, at 11:38 AM, Alexandre Petrescu <alexandre.petrescu@gm=
ail.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>> The main point is that intermediary routers dont touch forwarded packet=
s.
>>=20
>>=20
>> I=92m afraid the reality is slightly different.
>=20
> Well, reality - just like beauty - is in the eye of the beholder


yeah sure, whatever.

s.


>=20
>> Of course, you=92ll have to define what =93touching the packet=94 means.
>>=20
>> Inserting, pushing, removing, pop=92ing info into/from packets by transi=
t nodes is being done for ages.
>=20
> If you mean IPv4 ages then it is possible I agree with you.
>=20
> Alex
>=20
>>=20
>> s.
>>=20
>>=20
>>> This should be kept that way, otherwise one induces risks of fragmentin=
g the Internet.
>>>=20
>>> To support that statement, I am afraid one would need to dive into deta=
ils:
>>> - yes, the intermediary router MUST decrement the Hop Limit.
>>> - yes, the intermediary router can encap/decap with new headers (list
>>> them all, AH, ESP, base header).
>>> - yes the intermediary router owning an address in the dst field of a
>>> packet can swap it with the value in a field in an existing RH.
>>> - no, the intermediary router can not add a DO, MH, HbH, RH,
>>> frag, unless it creates a new packet (encap).
>>> - no, the intermediary router can not remove a DO, MH, HbH, RH, frag,
>>> unless it is decapsulating.
>>>=20
>>> Alex
>>>=20
>>>=20
>>> Le 11/05/2016 =E0 10:55, Pascal Thubert (pthubert) a =E9crit :
>>>> Agreed,
>>>>=20
>>>> the last thing we need is stronger rules without a deep proof that
>>>> the stronger rule is really needed to get the systems work and
>>>> interoperate.
>>>>=20
>>>> Ambiguity has a good history of creating interop issues (not the case
>>>> here is it?). It has also provided the necessary elasticity for
>>>> innovation and evolution. Sometimes the authors leave that ambiguity
>>>> voluntary and removing it for the sake of it is actually destroying
>>>> their work (eg flow label).
>>>>=20
>>>> I may have missed one but my summary of why we'd be removing this
>>>> ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
>>>> traceability (who did what). My take is that those issues should be
>>>> solved for their own sake as opposed to killing the messenger.
>>>>=20
>>>> Did this ambiguity prove useful? Yes! Because the source does not
>>>> know it all. SR is a clear proof there's value in adding applicable
>>>> semantics to the packet. There were others before (eg RPL) and there
>>>> will be more.
>>>>=20
>>>> Regards,
>>>>=20
>>>> Pascal
>>>>=20
>>>>> Le 11 mai 2016 =E0 10:39, Stefano Previdi (sprevidi)
>>>>> <sprevidi@cisco.com> a =E9crit :
>>>>>=20
>>>>>=20
>>>>>> On May 11, 2016, at 10:22 AM, Brian E Carpenter
>>>>>> <brian.e.carpenter@gmail.com> wrote:
>>>>>>=20
>>>>>> Ole, On 11/05/2016 18:12, otroan@employees.org wrote:
>>>>>>>>> correct. I raised the point during IETF94 meeting and
>>>>>>>>> repeated it in the mailing list. I=92m a bit surprised about
>>>>>>>>> this =93nobody objected=94 statement.
>>>>>>>>=20
>>>>>>>> I agree (even though I support the proposed text). What we
>>>>>>>> are supposed to be doing is making sure that 2460bis is an
>>>>>>>> unambiguous statement of rough consensus (and in this case,
>>>>>>>> we are arguing about the intention of 2460 where it left some
>>>>>>>> doubt).
>>>>>>>=20
>>>>>>> I don't see how finding the intention is particularly important
>>>>>>> nor useful.
>>>>>>=20
>>>>>> Look way back in this thread to where I traced the WG rough
>>>>>> consensus on this point in 1995; it's why I've read
>>>>>> RFC1883/RFC2460 one way, but others (e.g. the segment routing
>>>>>> people) read it differently. I really think we need to fix that
>>>>>> ambiguity for the Internet Standard step.
>>>>>=20
>>>>>=20
>>>>> I don=92t disagree with the idea of removing ambiguity from the
>>>>> spec.
>>>>>=20
>>>>> However, I strongly advocate the fact that we are not in a position
>>>>> to do it because we=92re just at the beginning of EH usage and we
>>>>> lack of experience.
>>>>>=20
>>>>> We lived for more than 18 years with the current spec, I think
>>>>> we=92ll survive another few years during which the industry can
>>>>> acquire experience, report it to ietf and then, if necessary,
>>>>> update the spec.
>>>>>=20
>>>>> Thanks. s.
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> Regards
>>>>>>=20
>>>>>> Brian
>>>>>=20
>>>>> --------------------------------------------------------------------
>>>>>=20
>>>>>=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
>>>> --------------------------------------------------------------------
>>>>=20
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>>=20


From nobody Wed May 11 04:37:29 2016
Return-Path: <mohamed.boucadair@orange.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 DABFC12D9F9 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 04:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.915
X-Spam-Level: 
X-Spam-Status: No, score=-2.915 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 X2odiQ_rHIKH for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 04:37:25 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor36.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE9C312DA39 for <ipv6@ietf.org>; Wed, 11 May 2016 04:36:06 -0700 (PDT)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 5A6E4A010F; Wed, 11 May 2016 13:36:05 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.2]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 2169212005B; Wed, 11 May 2016 13:36:05 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0294.000; Wed, 11 May 2016 13:36:04 +0200
From: <mohamed.boucadair@orange.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqv9/FKs3EEbEr0GQOr9P9iNQNJ+zhWAAgAAkVICAAASTAP//7YOg
Date: Wed, 11 May 2016 11:36:04 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933008D72F82@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com>
In-Reply-To: <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5kKwX0YPBi7YRHUONHHKGHMLFk0>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 11:37:28 -0000

RGVhciBhbGwsDQoNCkkgZnVsbHkgYWdyZWUgd2l0aCBTdGVmYW5vIGhlcmUuIA0KDQpGdXJ0aGVy
LCBJIGRvIHNlZSBzb21lIHZhbHVlIGluIGluc2VydGluZyBFSHMgZm9yIHNvbWUgYWR2YW5jZWQg
c2VydmljZXMgaW4gdGhlIG5ldHdvcmsgc2lkZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1N
ZXNzYWdlIGQnb3JpZ2luZS0tLS0tDQo+IERlwqA6IGlwdjYgW21haWx0bzppcHY2LWJvdW5jZXNA
aWV0Zi5vcmddIERlIGxhIHBhcnQgZGUgU3RlZmFubyBQcmV2aWRpDQo+IChzcHJldmlkaSkNCj4g
RW52b3nDqcKgOiBtZXJjcmVkaSAxMSBtYWkgMjAxNiAxMDozOQ0KPiDDgMKgOiBCcmlhbiBFIENh
cnBlbnRlcg0KPiBDY8KgOiA2bWFuIFdHOyBCb2IgSGluZGVuOyBGcmVkIEJha2VyIChmcmVkKQ0K
PiBPYmpldMKgOiBSZTogQWRkaW5nIGhlYWRlcnMgYW5kIGFkZGluZyBvcHRpb25zIHRvIGhlYWRl
cnMNCj4gDQo+IA0KPiA+IE9uIE1heSAxMSwgMjAxNiwgYXQgMTA6MjIgQU0sIEJyaWFuIEUgQ2Fy
cGVudGVyDQo+IDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+IHdyb3RlOg0KPiA+DQo+ID4g
T2xlLA0KPiA+IE9uIDExLzA1LzIwMTYgMTg6MTIsIG90cm9hbkBlbXBsb3llZXMub3JnIHdyb3Rl
Og0KPiA+Pj4+IGNvcnJlY3QuIEkgcmFpc2VkIHRoZSBwb2ludCBkdXJpbmcgSUVURjk0IG1lZXRp
bmcgYW5kIHJlcGVhdGVkIGl0IGluDQo+IHRoZSBtYWlsaW5nIGxpc3QuIEnigJltIGEgYml0IHN1
cnByaXNlZCBhYm91dCB0aGlzIOKAnG5vYm9keSBvYmplY3RlZOKAnQ0KPiBzdGF0ZW1lbnQuDQo+
ID4+Pg0KPiA+Pj4gSSBhZ3JlZSAoZXZlbiB0aG91Z2ggSSBzdXBwb3J0IHRoZSBwcm9wb3NlZCB0
ZXh0KS4gV2hhdCB3ZSBhcmUNCj4gc3VwcG9zZWQgdG8gYmUgZG9pbmcNCj4gPj4+IGlzIG1ha2lu
ZyBzdXJlIHRoYXQgMjQ2MGJpcyBpcyBhbiB1bmFtYmlndW91cyBzdGF0ZW1lbnQgb2Ygcm91Z2gN
Cj4gY29uc2Vuc3VzIChhbmQgaW4NCj4gPj4+IHRoaXMgY2FzZSwgd2UgYXJlIGFyZ3VpbmcgYWJv
dXQgdGhlIGludGVudGlvbiBvZiAyNDYwIHdoZXJlIGl0IGxlZnQNCj4gc29tZSBkb3VidCkuDQo+
ID4+DQo+ID4+IEkgZG9uJ3Qgc2VlIGhvdyBmaW5kaW5nIHRoZSBpbnRlbnRpb24gaXMgcGFydGlj
dWxhcmx5IGltcG9ydGFudCBub3INCj4gdXNlZnVsLg0KPiA+DQo+ID4gTG9vayB3YXkgYmFjayBp
biB0aGlzIHRocmVhZCB0byB3aGVyZSBJIHRyYWNlZCB0aGUgV0cgcm91Z2ggY29uc2Vuc3VzIG9u
DQo+IHRoaXMNCj4gPiBwb2ludCBpbiAxOTk1OyBpdCdzIHdoeSBJJ3ZlIHJlYWQgUkZDMTg4My9S
RkMyNDYwIG9uZSB3YXksIGJ1dCBvdGhlcnMNCj4gKGUuZy4gdGhlIHNlZ21lbnQNCj4gPiByb3V0
aW5nIHBlb3BsZSkgcmVhZCBpdCBkaWZmZXJlbnRseS4gSSByZWFsbHkgdGhpbmsgd2UgbmVlZCB0
byBmaXggdGhhdA0KPiBhbWJpZ3VpdHkNCj4gPiBmb3IgdGhlIEludGVybmV0IFN0YW5kYXJkIHN0
ZXAuDQo+IA0KPiANCj4gSSBkb27igJl0IGRpc2FncmVlIHdpdGggdGhlIGlkZWEgb2YgcmVtb3Zp
bmcgYW1iaWd1aXR5IGZyb20gdGhlIHNwZWMuDQo+IA0KPiBIb3dldmVyLCBJIHN0cm9uZ2x5IGFk
dm9jYXRlIHRoZSBmYWN0IHRoYXQgd2UgYXJlIG5vdCBpbiBhIHBvc2l0aW9uIHRvIGRvDQo+IGl0
IGJlY2F1c2Ugd2XigJlyZSBqdXN0IGF0IHRoZSBiZWdpbm5pbmcgb2YgRUggdXNhZ2UgYW5kIHdl
IGxhY2sgb2YNCj4gZXhwZXJpZW5jZS4NCj4gDQo+IFdlIGxpdmVkIGZvciBtb3JlIHRoYW4gMTgg
eWVhcnMgd2l0aCB0aGUgY3VycmVudCBzcGVjLCBJIHRoaW5rIHdl4oCZbGwNCj4gc3Vydml2ZSBh
bm90aGVyIGZldyB5ZWFycyBkdXJpbmcgd2hpY2ggdGhlIGluZHVzdHJ5IGNhbiBhY3F1aXJlDQo+
IGV4cGVyaWVuY2UsIHJlcG9ydCBpdCB0byBpZXRmIGFuZCB0aGVuLCBpZiBuZWNlc3NhcnksIHVw
ZGF0ZSB0aGUgc3BlYy4NCj4gDQo+IFRoYW5rcy4NCj4gcy4NCj4gDQo+IA0KPiANCj4gPg0KPiA+
IFJlZ2FyZHMNCj4gPg0KPiA+ICAgIEJyaWFuDQo+ID4NCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IElF
VEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdA0KPiBpcHY2QGlldGYub3JnDQo+IEFk
bWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2lwdjYNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg==


From nobody Wed May 11 09:15:01 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 D952A12B068 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:14:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.516
X-Spam-Level: 
X-Spam-Status: No, score=-15.516 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=-0.996, 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 emp76HksLi2Z for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:14:57 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F15812B04D for <ipv6@ietf.org>; Wed, 11 May 2016 09:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27148; q=dns/txt; s=iport; t=1462983297; x=1464192897; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=d08Hs3XidZgY2PW0AFJt6KNEy5MbAdghoOgsWPR4s2k=; b=ZoBYOO5RlTpLzI0mqiPtkeNuIiRoMAgRvlcwA8Lf5oan/ZOoJkRWzkW5 SuLqrzcEDkwQmy/E7hbG/3WCkPrge0FHOHKUWlSPhCLQJoxeoLBg89CQE i8OVLghYMhjpBBXb3mianMpBBjwYxFhjoqHHHReAQUFzLeyktPsIp6H+9 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AaAgBrWTNX/4QNJK1egmxMVX0GrUWLZ?= =?us-ascii?q?QENgXYXAQqFcgIcgRw4FAEBAQEBAQFlJ4RCAQEBAwEBAQEgCkELBQsCAQgRBAE?= =?us-ascii?q?BAScDAgICHwYLFAkIAgQOBQiIDQMPCA6obIw3DYQpAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBEQSGIIRMgkOCEx+CSoJZBYd+j3gxAYwkgXKBcId5hTeGLYEvh2QBHgE?= =?us-ascii?q?BQoIFG4FLbgGHTSUYfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.24,608,1454976000";  d="scan'208,217";a="272176809"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 11 May 2016 16:14:56 +0000
Received: from XCH-RCD-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u4BGEuIK026555 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 May 2016 16:14:56 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 11 May 2016 11:14:55 -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.1104.009; Wed, 11 May 2016 11:14:55 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: RE: Adding headers and adding options to headers
Thread-Topic: Adding headers and adding options to headers
Thread-Index: AQHRqsO9U1uc49vecEG1wrkiG/Alpp+yjoUAgABu1ACAAJlCAIAAJFSAgAAElgD//7DEmYAAZw8AgAALXkA=
Date: Wed, 11 May 2016 16:14:34 +0000
Deferred-Delivery: Wed, 11 May 2016 16:13:30 +0000
Message-ID: <8e407e65a38b439b808abbbf4f50bf57@XCH-RCD-001.cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com> <CAO42Z2xW1ppOwuXNeGoj3qiCvqQpV_6ndwveVVDHL+XDBNy1ag@mail.gmail.com>
In-Reply-To: <CAO42Z2xW1ppOwuXNeGoj3qiCvqQpV_6ndwveVVDHL+XDBNy1ag@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.60.17.137]
Content-Type: multipart/alternative; boundary="_000_8e407e65a38b439b808abbbf4f50bf57XCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/c2wu7kHK9opg57bM55IFLMCMQUg>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 16:15:00 -0000

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

SGVsbG8gTWFyazoNCg0KQ2hlZXJzLA0KDQpQYXNjYWwNCg0KRnJvbTogTWFyayBTbWl0aCBbbWFp
bHRvOm1hcmt6enpzbWl0aEBnbWFpbC5jb21dDQpTZW50OiBtZXJjcmVkaSAxMSBtYWkgMjAxNiAx
MjowNQ0KVG86IFBhc2NhbCBUaHViZXJ0IChwdGh1YmVydCkgPHB0aHViZXJ0QGNpc2NvLmNvbT4N
CkNjOiBGcmVkIEJha2VyIChmcmVkKSA8ZnJlZEBjaXNjby5jb20+OyBCb2IgSGluZGVuIDxib2Iu
aGluZGVuQGdtYWlsLmNvbT47IDZtYW4gV0cgPGlwdjZAaWV0Zi5vcmc+OyBTdGVmYW5vIFByZXZp
ZGkgKHNwcmV2aWRpKSA8c3ByZXZpZGlAY2lzY28uY29tPg0KU3ViamVjdDogUmU6IEFkZGluZyBo
ZWFkZXJzIGFuZCBhZGRpbmcgb3B0aW9ucyB0byBoZWFkZXJzDQoNCg0KT24gMTEgTWF5IDIwMTYg
MTg6NTYsICJQYXNjYWwgVGh1YmVydCAocHRodWJlcnQpIiA8cHRodWJlcnRAY2lzY28uY29tPG1h
aWx0bzpwdGh1YmVydEBjaXNjby5jb20+PiB3cm90ZToNCj4NCj4gQWdyZWVkLA0KPg0KPiB0aGUg
bGFzdCB0aGluZyB3ZSBuZWVkIGlzIHN0cm9uZ2VyIHJ1bGVzIHdpdGhvdXQgYSBkZWVwIHByb29m
IHRoYXQgdGhlIHN0cm9uZ2VyIHJ1bGUgaXMgcmVhbGx5IG5lZWRlZCB0byBnZXQgdGhlIHN5c3Rl
bXMgd29yayBhbmQgaW50ZXJvcGVyYXRlLg0KPg0KDQpUaGUgdGhpbmcgSSBkb24ndCB1bmRlcnN0
YW5kIGlzIHRoZSBuZWVkIGZvciBwcm9vZi4gRG8gd2UgcmVhbGx5IG5lZWQgdG8gKnByb3ZlKiB0
aGF0IGFkZGluZyB1bmV4cGVjdGVkIEVIcyBtaWQtZmxpZ2h0IGlzIGdvaW5nIHRvIGJyZWFrIHRo
aW5ncyBldmVuIHRob3VnaCBpdCBpcyBmb3Jlc2VlYWJsZSB0aGF0IHRoZXkgd2lsbCwgYmVjYXVz
ZSBpdCBpcyBlYXN5IHRvIHNlZSBob3cgaXQgd2lsbCBpbnRlcmFjdCBiYWRseSB3aXRoIHRoZSBl
eGlzdGluZyBtZWNoYW5pc21zPw0KDQoNCg0KPj4gTG9va3MgbGlrZSBGVUQgdG8gbWUuIEFueSBh
ZGRpdGlvbiBtdXN0IGJlIGRvbmUgY2FyZWZ1bGx5IGFuZCBpZGVhbGx5IHBhc3MgdGhyb3VnaCB0
aGlzIGdyb3VwIGZvciB2YWxpZGF0aW9uLg0KDQo+ICBBbWJpZ3VpdHkgaGFzIGEgZ29vZCBoaXN0
b3J5IG9mIGNyZWF0aW5nIGludGVyb3AgaXNzdWVzIChub3QgdGhlIGNhc2UgaGVyZSBpcyBpdD8p
LiBJdCBoYXMgYWxzbyBwcm92aWRlZCB0aGUgbmVjZXNzYXJ5IGVsYXN0aWNpdHkgZm9yIGlubm92
YXRpb24gYW5kIGV2b2x1dGlvbi4gU29tZXRpbWVzIHRoZSBhdXRob3JzIGxlYXZlIHRoYXQgYW1i
aWd1aXR5IHZvbHVudGFyeSBhbmQgcmVtb3ZpbmcgaXQgZm9yIHRoZSBzYWtlIG9mIGl0IGlzIGFj
dHVhbGx5IGRlc3Ryb3lpbmcgdGhlaXIgd29yayAoZWcgZmxvdyBsYWJlbCkuDQo+DQo+IEkgbWF5
IGhhdmUgbWlzc2VkIG9uZSBidXQgbXkgc3VtbWFyeSBvZiB3aHkgd2UnZCBiZSByZW1vdmluZyB0
aGlzIGFtYmlndWl0eSBjb21lcyBmcm9tIDIgaXNzdWVzLCBQTVRVRCAod2hpY2ggaXMgc28gYnJv
a2VuIGFueXdheSkgYW5kIHRyYWNlYWJpbGl0eSAod2hvIGRpZCB3aGF0KS4gTXkgdGFrZSBpcyB0
aGF0IHRob3NlIGlzc3VlcyBzaG91bGQgYmUgc29sdmVkIGZvciB0aGVpciBvd24gc2FrZSBhcyBv
cHBvc2VkIHRvIGtpbGxpbmcgdGhlIG1lc3Nlbmdlci4NCj4NCg0KSG93PyBIb3cgYXJlIHlvdSBn
b2luZyB0byB0cmFjZSB3aG8gZGlkIHdoYXQgaWYgdGhlIGRldmljZSBzaWxlbnRseSBkaWQgaXQ/
IElmIHlvdSBkb24ndCBoYXZlIGFuIGFuc3dlciwgeW91J3JlIGNyZWF0aW5nIHRoZSBwcm9ibGVt
IGFuZCB0aGVuIG1ha2luZyBpdCBzb21lYm9keSBlbHNlJ3MgcHJvYmxlbSB0byBmaXguIEkgdGhp
bmsgcGVvcGxlIHdobyBjcmVhdGUgcHJvYmxlbXMgYXJlIG9ibGlnYXRlZCB0byBmaXggdGhlbS4N
Cg0KPj4gd2UgY291bGQgd29yayBvbiBpbXByb3ZpbmcgdHJhY2VhYmlsaXR5LiBJ4oCZZCBzdXBw
b3J0IHN1Y2ggd29yay4gVGhpcyBtYXkgbWVhbiBtb3JlIGhlYWRlcnMgYmVpbmcgbW9kaWZpZWQg
b24gdGhlIGZseSA7ICkNCg0KVHVubmVsaW5nIGFscmVhZHkgc29sdmVzIHRoZXNlIHByb2JsZW1z
IGFuZCBmYWNpbGl0YXRlcyBhZGRpbmcgRUhzLiBXaHkgYXJlIHBlb3BsZSBjaG9vc2luZyB0byBp
Z25vcmUgdGhpcyBvcHRpb24/IFdoYXQgaXMgdGhlIHVuc3RhdGVkIGJpYXMgYWdhaW5zdCB0dW5u
ZWxpbmc/DQoNCj4+IHR1bm5lbHMgYXJlIG5vdCBleGVtcHQgb2YgcHJvYmxlbXMuIFRoZXkgY2Fu
IGNhdXNlIGFkZGl0aW9uYWwgZnJhZ21lbnRhdGlvbiwgYWRkIHRvIGxvc3MgYW5kIGxhdGVuY3ku
Li4gQW5kIHR1bm5lbHMgY2Fubm90IHNvbHZlIGV2ZXJ5dGhpbmcuIElmIG1vcmUgdGhhbiBvbmUg
cm91dGVyIG5lZWRzIHRvIGFkZC9tb2Qgc3R1ZmYsIHRoZXJlIHdvdWxkIGJlIElQIGluIElQIGlu
IElQIGFuZCBvbmx5IHRoZSBvdXRlciBlbmNhcHN1bGF0aW9uIHdvdWxkIGJlIG9ic2VydmVkIGFu
ZCB0aGF0IHdvdWxkIG5vdCBiZSB0aGUgZGVzaXJlZCByZXN1bHQuIEJhc2ljYWxseSB0dW5uZWxp
bmcgYnJlYWtzIHRoZSB3aG9sZSBpZGVhLg0KDQo+IERpZCB0aGlzIGFtYmlndWl0eSBwcm92ZSB1
c2VmdWw/IFllcyEgQmVjYXVzZSB0aGUgc291cmNlIGRvZXMgbm90IGtub3cgaXQgYWxsLiBTUiBp
cyBhIGNsZWFyIHByb29mIHRoZXJlJ3MgdmFsdWUgaW4gYWRkaW5nIGFwcGxpY2FibGUgc2VtYW50
aWNzIHRvIHRoZSBwYWNrZXQuIFRoZXJlIHdlcmUgb3RoZXJzIGJlZm9yZSAoZWcgUlBMKSBhbmQg
dGhlcmUgd2lsbCBiZSBtb3JlLg0KPg0KDQpUaGUgcXVlc3Rpb24gaXNuJ3Qgd2hldGhlciBvciBu
b3QgdGhlIGFkZGVkIHNlbWFudGljcyBoYXZlIHZhbHVlLg0KDQpUaGUgcXVlc3Rpb24gaXMgd2hh
dCBpcyB0aGUgYmVzdCB3YXkgdG8gYWRkIHRob3NlIHNlbWFudGljcyB0aGF0IGRvZXNuJ3QgaW50
ZXJhY3QgYmFkbHkgd2l0aCBvciBjYXVzZSB0byBmYWlsIGV4aXN0aW5nLCB3aWRlbHkgZGVwbG95
ZWQgbWVjaGFuaXNtcyAobGlrZSBQTVRVRCksIGRvZXNuJ3QgdmlvbGF0ZSBlc3RhYmxpc2hlZCBz
ZW1hbnRpY3Mgb2YgZXhpc3RpbmcgZmllbGRzIChsaWtlIGEgIm11bHRpLXNvdXJjZSBwYWNrZXQi
IChtZWFuaW5nIG11bHRpcGxlIGRldmljZXMgYXJlIHRoZSBzb3VyY2Ugb2YgcGFydHMgb2YgdGhl
IHBhY2tldCkgd2l0aCBhIHNpbmdsZSBzb3VyY2UgYWRkcmVzcyBmaWVsZCB3b3VsZCksIGFuZCBk
b2Vzbid0IG1ha2UgdHJvdWJsZXNob290aW5nIGFuIG9wZXJhdGlvbmFsIG5ldHdvcmsgaGFyZGVy
IHRoYW4gaXQgYWxyZWFkeSBpcy4NCg0KPj4gU28geW914oCZcmUgb3Bwb3NpbmcgYSBnZW5lcmFs
IGNhcGFiaWxpdHkgdGhhdCBjb3VsZCBpbiBmYWN0IGJlIHVzZWQgdG8gaW5zdHJ1bWVudCBwYWNr
ZXRzIGFuZCBoZWxwIHVuZGVyc3RhbmQgaG93IHRoZSBuZXR3b3JrIGlzIGdvaW5nPyBUaGF0IGNv
dWxkIGJlIHVzZWQgdG8gYXZvaWQgYSBjb25nZXN0aW9uIHRoYXTigJlzIGluZGVlZCBoYXJkIHRv
IHRyb3VibGVzaG9vdD8gV2UgZG8gbm90IG5lZWQgYSBnZW5lcmFsIHJ1bGluZywgd2UgbmVlZCBh
IGNhc2UgYnkgY2FzZSBhbmQgY2FyZWZ1bCBleGFtaW5hdGlvbi4NCg0KSW4gdGhlb3J5LCB0aGVz
ZSBlZGl0ZWQgcGFja2V0cyB3b3VsZCBuZXZlciBsZWFrIGZyb20gdGhlIGVkaXRpbmcgZG9tYWlu
LCBhbmQgZGV2aWNlcyB0aGF0IGFkZCBvciByZW1vdmUgdGhlbSB3b3VsZCBuZXZlciBuZWVkIHRy
b3VibGVzaG9vdGluZy4gUHJhY3RpY2UgYW5kIHRoZW9yeSBhcmUgcmFyZWx5IHRoZSBzYW1lLg0K
DQo+PiBGVUQuIElmIHRoaXMgZ3JvdXAgZGVmaW5lcyBhIG5ldyBvcGVyYXRpb24sIEnigJltIHN1
cmUgaXQgd2lsbCBtYWtlIGl0IHByb3Blcmx5Lg0KDQpSZWdhcmRzLA0KTWFyay4NCg0KPiBSZWdh
cmRzLA0KPg0KPiBQYXNjYWwNCj4NCj4gPiBMZSAxMSBtYWkgMjAxNiDDoCAxMDozOSwgU3RlZmFu
byBQcmV2aWRpIChzcHJldmlkaSkgPHNwcmV2aWRpQGNpc2NvLmNvbTxtYWlsdG86c3ByZXZpZGlA
Y2lzY28uY29tPj4gYSDDqWNyaXQgOg0KPiA+DQo+ID4NCj4gPj4gT24gTWF5IDExLCAyMDE2LCBh
dCAxMDoyMiBBTSwgQnJpYW4gRSBDYXJwZW50ZXIgPGJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNv
bTxtYWlsdG86YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPj4gd3JvdGU6DQo+ID4+DQo+ID4+
IE9sZSwNCj4gPj4gT24gMTEvMDUvMjAxNiAxODoxMiwgb3Ryb2FuQGVtcGxveWVlcy5vcmc8bWFp
bHRvOm90cm9hbkBlbXBsb3llZXMub3JnPiB3cm90ZToNCj4gPj4+Pj4gY29ycmVjdC4gSSByYWlz
ZWQgdGhlIHBvaW50IGR1cmluZyBJRVRGOTQgbWVldGluZyBhbmQgcmVwZWF0ZWQgaXQgaW4gdGhl
IG1haWxpbmcgbGlzdC4gSeKAmW0gYSBiaXQgc3VycHJpc2VkIGFib3V0IHRoaXMg4oCcbm9ib2R5
IG9iamVjdGVk4oCdIHN0YXRlbWVudC4NCj4gPj4+Pg0KPiA+Pj4+IEkgYWdyZWUgKGV2ZW4gdGhv
dWdoIEkgc3VwcG9ydCB0aGUgcHJvcG9zZWQgdGV4dCkuIFdoYXQgd2UgYXJlIHN1cHBvc2VkIHRv
IGJlIGRvaW5nDQo+ID4+Pj4gaXMgbWFraW5nIHN1cmUgdGhhdCAyNDYwYmlzIGlzIGFuIHVuYW1i
aWd1b3VzIHN0YXRlbWVudCBvZiByb3VnaCBjb25zZW5zdXMgKGFuZCBpbg0KPiA+Pj4+IHRoaXMg
Y2FzZSwgd2UgYXJlIGFyZ3VpbmcgYWJvdXQgdGhlIGludGVudGlvbiBvZiAyNDYwIHdoZXJlIGl0
IGxlZnQgc29tZSBkb3VidCkuDQo+ID4+Pg0KPiA+Pj4gSSBkb24ndCBzZWUgaG93IGZpbmRpbmcg
dGhlIGludGVudGlvbiBpcyBwYXJ0aWN1bGFybHkgaW1wb3J0YW50IG5vciB1c2VmdWwuDQo+ID4+
DQo+ID4+IExvb2sgd2F5IGJhY2sgaW4gdGhpcyB0aHJlYWQgdG8gd2hlcmUgSSB0cmFjZWQgdGhl
IFdHIHJvdWdoIGNvbnNlbnN1cyBvbiB0aGlzDQo+ID4+IHBvaW50IGluIDE5OTU7IGl0J3Mgd2h5
IEkndmUgcmVhZCBSRkMxODgzL1JGQzI0NjAgb25lIHdheSwgYnV0IG90aGVycyAoZS5nLiB0aGUg
c2VnbWVudA0KPiA+PiByb3V0aW5nIHBlb3BsZSkgcmVhZCBpdCBkaWZmZXJlbnRseS4gSSByZWFs
bHkgdGhpbmsgd2UgbmVlZCB0byBmaXggdGhhdCBhbWJpZ3VpdHkNCj4gPj4gZm9yIHRoZSBJbnRl
cm5ldCBTdGFuZGFyZCBzdGVwLg0KPiA+DQo+ID4NCj4gPiBJIGRvbuKAmXQgZGlzYWdyZWUgd2l0
aCB0aGUgaWRlYSBvZiByZW1vdmluZyBhbWJpZ3VpdHkgZnJvbSB0aGUgc3BlYy4NCj4gPg0KPiA+
IEhvd2V2ZXIsIEkgc3Ryb25nbHkgYWR2b2NhdGUgdGhlIGZhY3QgdGhhdCB3ZSBhcmUgbm90IGlu
IGEgcG9zaXRpb24gdG8gZG8gaXQgYmVjYXVzZSB3ZeKAmXJlIGp1c3QgYXQgdGhlIGJlZ2lubmlu
ZyBvZiBFSCB1c2FnZSBhbmQgd2UgbGFjayBvZiBleHBlcmllbmNlLg0KPiA+DQo+ID4gV2UgbGl2
ZWQgZm9yIG1vcmUgdGhhbiAxOCB5ZWFycyB3aXRoIHRoZSBjdXJyZW50IHNwZWMsIEkgdGhpbmsg
d2XigJlsbCBzdXJ2aXZlIGFub3RoZXIgZmV3IHllYXJzIGR1cmluZyB3aGljaCB0aGUgaW5kdXN0
cnkgY2FuIGFjcXVpcmUgZXhwZXJpZW5jZSwgcmVwb3J0IGl0IHRvIGlldGYgYW5kIHRoZW4sIGlm
IG5lY2Vzc2FyeSwgdXBkYXRlIHRoZSBzcGVjLg0KPiA+DQo+ID4gVGhhbmtzLg0KPiA+IHMuDQo+
ID4NCj4gPg0KPiA+DQo+ID4+DQo+ID4+IFJlZ2FyZHMNCj4gPj4NCj4gPj4gICBCcmlhbg0KPiA+
DQo+ID4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCj4gPiBJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5nIGxp
c3QNCj4gPiBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KPiA+IEFkbWluaXN0
cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lw
djYNCj4gPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBJRVRGIElQdjYgd29ya2lu
ZyBncm91cCBtYWlsaW5nIGxpc3QNCj4gaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9y
Zz4NCj4gQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vaXB2Ng0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdp
bi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6
MGNtOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
c2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6IzFGNDk3RDt9DQpzcGFu
LkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAq
Lw0KQGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6ODU0MTQ3MTUwOw0KCW1zby1saXN0LXR5cGU6aHli
cmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczo2MTI1MDYwMDggLTMyNDQ5ODM1NCA2NzY5ODY5
MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2
NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLXN0YXJ0LWF0OjExOw0KCW1z
by1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvg5g7DQoJbXNv
LWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCW1zby1mYXJl
YXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5l
dyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250
LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0x
OC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsOA0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxl
dmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9
DQpvbA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQot
LT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4
dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpl
eHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+
DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPkhlbGxvIE1hcms6PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkZSIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkZSIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRlIiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5QYXNjYWw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20g
MGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNv
bGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWYiPiBNYXJrIFNtaXRoIFttYWlsdG86bWFya3p6enNtaXRoQGdtYWlsLmNvbV0NCjxicj4N
CjxiPlNlbnQ6PC9iPiBtZXJjcmVkaSAxMSBtYWkgMjAxNiAxMjowNTxicj4NCjxiPlRvOjwvYj4g
UGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KSAmbHQ7cHRodWJlcnRAY2lzY28uY29tJmd0Ozxicj4N
CjxiPkNjOjwvYj4gRnJlZCBCYWtlciAoZnJlZCkgJmx0O2ZyZWRAY2lzY28uY29tJmd0OzsgQm9i
IEhpbmRlbiAmbHQ7Ym9iLmhpbmRlbkBnbWFpbC5jb20mZ3Q7OyA2bWFuIFdHICZsdDtpcHY2QGll
dGYub3JnJmd0OzsgU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgJmx0O3NwcmV2aWRpQGNpc2Nv
LmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IEFkZGluZyBoZWFkZXJzIGFuZCBhZGRp
bmcgb3B0aW9ucyB0byBoZWFkZXJzPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHA+PGJyPg0K
T24gMTEgTWF5IDIwMTYgMTg6NTYsICZxdW90O1Bhc2NhbCBUaHViZXJ0IChwdGh1YmVydCkmcXVv
dDsgJmx0OzxhIGhyZWY9Im1haWx0bzpwdGh1YmVydEBjaXNjby5jb20iPnB0aHViZXJ0QGNpc2Nv
LmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDs8YnI+DQomZ3Q7IEFncmVlZCw8YnI+DQomZ3Q7
PGJyPg0KJmd0OyB0aGUgbGFzdCB0aGluZyB3ZSBuZWVkIGlzIHN0cm9uZ2VyIHJ1bGVzIHdpdGhv
dXQgYSBkZWVwIHByb29mIHRoYXQgdGhlIHN0cm9uZ2VyIHJ1bGUgaXMgcmVhbGx5IG5lZWRlZCB0
byBnZXQgdGhlIHN5c3RlbXMgd29yayBhbmQgaW50ZXJvcGVyYXRlLjxicj4NCiZndDs8bzpwPjwv
bzpwPjwvcD4NCjxwPlRoZSB0aGluZyBJIGRvbid0IHVuZGVyc3RhbmQgaXMgdGhlIG5lZWQgZm9y
IHByb29mLiBEbyB3ZSByZWFsbHkgbmVlZCB0byAqcHJvdmUqIHRoYXQgYWRkaW5nIHVuZXhwZWN0
ZWQgRUhzIG1pZC1mbGlnaHQgaXMgZ29pbmcgdG8gYnJlYWsgdGhpbmdzIGV2ZW4gdGhvdWdoIGl0
IGlzIGZvcmVzZWVhYmxlIHRoYXQgdGhleSB3aWxsLCBiZWNhdXNlIGl0IGlzIGVhc3kgdG8gc2Vl
IGhvdyBpdCB3aWxsIGludGVyYWN0IGJhZGx5IHdpdGggdGhlIGV4aXN0aW5nDQogbWVjaGFuaXNt
cz88bzpwPjwvbzpwPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgc3R5bGU9Im1hcmdpbi1sZWZ0OjQuOHB0Ij48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PiZndDsmZ3Q7IExvb2tzIGxpa2UgRlVEIHRvIG1lLiBBbnkgYWRkaXRpb24gbXVzdCBiZSBkb25l
IGNhcmVmdWxseSBhbmQgaWRlYWxseSBwYXNzIHRocm91Z2ggdGhpcyBncm91cCBmb3IgdmFsaWRh
dGlvbi4gJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+Jmd0OyAmbmJzcDtBbWJpZ3Vp
dHkgaGFzIGEgZ29vZCBoaXN0b3J5IG9mIGNyZWF0aW5nIGludGVyb3AgaXNzdWVzIChub3QgdGhl
IGNhc2UgaGVyZSBpcyBpdD8pLiBJdCBoYXMgYWxzbyBwcm92aWRlZCB0aGUgbmVjZXNzYXJ5IGVs
YXN0aWNpdHkgZm9yIGlubm92YXRpb24gYW5kIGV2b2x1dGlvbi4gU29tZXRpbWVzIHRoZSBhdXRo
b3JzIGxlYXZlIHRoYXQgYW1iaWd1aXR5IHZvbHVudGFyeSBhbmQgcmVtb3ZpbmcgaXQgZm9yIHRo
ZSBzYWtlIG9mIGl0IGlzDQogYWN0dWFsbHkgZGVzdHJveWluZyB0aGVpciB3b3JrIChlZyBmbG93
IGxhYmVsKS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJIG1heSBoYXZlIG1pc3NlZCBvbmUgYnV0IG15
IHN1bW1hcnkgb2Ygd2h5IHdlJ2QgYmUgcmVtb3ZpbmcgdGhpcyBhbWJpZ3VpdHkgY29tZXMgZnJv
bSAyIGlzc3VlcywgUE1UVUQgKHdoaWNoIGlzIHNvIGJyb2tlbiBhbnl3YXkpIGFuZCB0cmFjZWFi
aWxpdHkgKHdobyBkaWQgd2hhdCkuIE15IHRha2UgaXMgdGhhdCB0aG9zZSBpc3N1ZXMgc2hvdWxk
IGJlIHNvbHZlZCBmb3IgdGhlaXIgb3duIHNha2UgYXMgb3Bwb3NlZCB0byBraWxsaW5nIHRoZQ0K
IG1lc3Nlbmdlci48YnI+DQomZ3Q7PG86cD48L286cD48L3A+DQo8cD5Ib3c/IEhvdyBhcmUgeW91
IGdvaW5nIHRvIHRyYWNlIHdobyBkaWQgd2hhdCBpZiB0aGUgZGV2aWNlIHNpbGVudGx5IGRpZCBp
dD8gSWYgeW91IGRvbid0IGhhdmUgYW4gYW5zd2VyLCB5b3UncmUgY3JlYXRpbmcgdGhlIHByb2Js
ZW0gYW5kIHRoZW4gbWFraW5nIGl0IHNvbWVib2R5IGVsc2UncyBwcm9ibGVtIHRvIGZpeC4gSSB0
aGluayBwZW9wbGUgd2hvIGNyZWF0ZSBwcm9ibGVtcyBhcmUgb2JsaWdhdGVkIHRvIGZpeCB0aGVt
LjxvOnA+PC9vOnA+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7Jmd0OyB3ZSBjb3VsZCB3
b3JrIG9uIGltcHJvdmluZyB0cmFjZWFiaWxpdHkuIEnigJlkIHN1cHBvcnQgc3VjaCB3b3JrLiBU
aGlzIG1heSBtZWFuIG1vcmUgaGVhZGVycyBiZWluZyBtb2RpZmllZCBvbiB0aGUgZmx5IDsgKTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPlR1bm5lbGluZyBhbHJlYWR5IHNvbHZlcyB0aGVzZSBw
cm9ibGVtcyBhbmQgZmFjaWxpdGF0ZXMgYWRkaW5nIEVIcy4gV2h5IGFyZSBwZW9wbGUgY2hvb3Np
bmcgdG8gaWdub3JlIHRoaXMgb3B0aW9uPyBXaGF0IGlzIHRoZSB1bnN0YXRlZCBiaWFzIGFnYWlu
c3QgdHVubmVsaW5nPzxvOnA+PC9vOnA+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7Jmd0
OyB0dW5uZWxzIGFyZSBub3QgZXhlbXB0IG9mIHByb2JsZW1zLiBUaGV5IGNhbiBjYXVzZSBhZGRp
dGlvbmFsIGZyYWdtZW50YXRpb24sIGFkZCB0byBsb3NzIGFuZCBsYXRlbmN5Li4uIEFuZCB0dW5u
ZWxzIGNhbm5vdCBzb2x2ZSBldmVyeXRoaW5nLiBJZiBtb3JlIHRoYW4gb25lIHJvdXRlciBuZWVk
cyB0byBhZGQvbW9kIHN0dWZmLA0KIHRoZXJlIHdvdWxkIGJlIElQIGluIElQIGluIElQIGFuZCBv
bmx5IHRoZSBvdXRlciBlbmNhcHN1bGF0aW9uIHdvdWxkIGJlIG9ic2VydmVkIGFuZCB0aGF0IHdv
dWxkIG5vdCBiZSB0aGUgZGVzaXJlZCByZXN1bHQuIEJhc2ljYWxseSB0dW5uZWxpbmcgYnJlYWtz
IHRoZSB3aG9sZSBpZGVhLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPiZndDsgRGlkIHRoaXMg
YW1iaWd1aXR5IHByb3ZlIHVzZWZ1bD8gWWVzISBCZWNhdXNlIHRoZSBzb3VyY2UgZG9lcyBub3Qg
a25vdyBpdCBhbGwuIFNSIGlzIGEgY2xlYXIgcHJvb2YgdGhlcmUncyB2YWx1ZSBpbiBhZGRpbmcg
YXBwbGljYWJsZSBzZW1hbnRpY3MgdG8gdGhlIHBhY2tldC4gVGhlcmUgd2VyZSBvdGhlcnMgYmVm
b3JlIChlZyBSUEwpIGFuZCB0aGVyZSB3aWxsIGJlIG1vcmUuPGJyPg0KJmd0OzxvOnA+PC9vOnA+
PC9wPg0KPHA+VGhlIHF1ZXN0aW9uIGlzbid0IHdoZXRoZXIgb3Igbm90IHRoZSBhZGRlZCBzZW1h
bnRpY3MgaGF2ZSB2YWx1ZS48bzpwPjwvbzpwPjwvcD4NCjxwPlRoZSBxdWVzdGlvbiBpcyB3aGF0
IGlzIHRoZSBiZXN0IHdheSB0byBhZGQgdGhvc2Ugc2VtYW50aWNzIHRoYXQgZG9lc24ndCBpbnRl
cmFjdCBiYWRseSB3aXRoIG9yIGNhdXNlIHRvIGZhaWwgZXhpc3RpbmcsIHdpZGVseSBkZXBsb3ll
ZCBtZWNoYW5pc21zIChsaWtlIFBNVFVEKSwgZG9lc24ndCB2aW9sYXRlIGVzdGFibGlzaGVkIHNl
bWFudGljcyBvZiBleGlzdGluZyBmaWVsZHMgKGxpa2UgYSAmcXVvdDttdWx0aS1zb3VyY2UgcGFj
a2V0JnF1b3Q7IChtZWFuaW5nDQogbXVsdGlwbGUgZGV2aWNlcyBhcmUgdGhlIHNvdXJjZSBvZiBw
YXJ0cyBvZiB0aGUgcGFja2V0KSB3aXRoIGEgc2luZ2xlIHNvdXJjZSBhZGRyZXNzIGZpZWxkIHdv
dWxkKSwgYW5kIGRvZXNuJ3QgbWFrZSB0cm91Ymxlc2hvb3RpbmcgYW4gb3BlcmF0aW9uYWwgbmV0
d29yayBoYXJkZXIgdGhhbiBpdCBhbHJlYWR5IGlzLjxvOnA+PC9vOnA+PC9wPg0KPHA+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj4mZ3Q7Jmd0OyBTbyB5b3XigJlyZSBvcHBvc2luZyBhIGdlbmVyYWwgY2FwYWJp
bGl0eSB0aGF0IGNvdWxkIGluIGZhY3QgYmUgdXNlZCB0byBpbnN0cnVtZW50IHBhY2tldHMgYW5k
IGhlbHAgdW5kZXJzdGFuZCBob3cgdGhlIG5ldHdvcmsgaXMgZ29pbmc/IFRoYXQgY291bGQgYmUg
dXNlZCB0byBhdm9pZCBhIGNvbmdlc3Rpb24gdGhhdOKAmXMgaW5kZWVkDQogaGFyZCB0byB0cm91
Ymxlc2hvb3Q/IFdlIGRvIG5vdCBuZWVkIGEgZ2VuZXJhbCBydWxpbmcsIHdlIG5lZWQgYSBjYXNl
IGJ5IGNhc2UgYW5kIGNhcmVmdWwgZXhhbWluYXRpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+SW4gdGhlb3J5LCB0aGVzZSBlZGl0ZWQgcGFja2V0cyB3b3VsZCBuZXZlciBsZWFrIGZyb20g
dGhlIGVkaXRpbmcgZG9tYWluLCBhbmQgZGV2aWNlcyB0aGF0IGFkZCBvciByZW1vdmUgdGhlbSB3
b3VsZCBuZXZlciBuZWVkIHRyb3VibGVzaG9vdGluZy4gUHJhY3RpY2UgYW5kIHRoZW9yeSBhcmUg
cmFyZWx5IHRoZSBzYW1lLjxvOnA+PC9vOnA+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7
Jmd0OyBGVUQuIElmIHRoaXMgZ3JvdXAgZGVmaW5lcyBhIG5ldyBvcGVyYXRpb24sIEnigJltIHN1
cmUgaXQgd2lsbCBtYWtlIGl0IHByb3Blcmx5Lg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+
UmVnYXJkcyw8YnI+DQpNYXJrLjxvOnA+PC9vOnA+PC9wPg0KPHA+Jmd0OyBSZWdhcmRzLDxicj4N
CiZndDs8YnI+DQomZ3Q7IFBhc2NhbDxicj4NCiZndDs8YnI+DQomZ3Q7ICZndDsgTGUgMTEgbWFp
IDIwMTYgw6AgMTA6MzksIFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpICZsdDs8YSBocmVmPSJt
YWlsdG86c3ByZXZpZGlAY2lzY28uY29tIj5zcHJldmlkaUBjaXNjby5jb208L2E+Jmd0OyBhIMOp
Y3JpdCA6PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7Jmd0OyBP
biBNYXkgMTEsIDIwMTYsIGF0IDEwOjIyIEFNLCBCcmlhbiBFIENhcnBlbnRlciAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbSI+YnJpYW4uZS5jYXJwZW50ZXJA
Z21haWwuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0OyAmZ3Q7Jmd0Ozxicj4NCiZndDsgJmd0
OyZndDsgT2xlLDxicj4NCiZndDsgJmd0OyZndDsgT24gMTEvMDUvMjAxNiAxODoxMiwgPGEgaHJl
Zj0ibWFpbHRvOm90cm9hbkBlbXBsb3llZXMub3JnIj5vdHJvYW5AZW1wbG95ZWVzLm9yZzwvYT4g
d3JvdGU6PGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBjb3JyZWN0LiBJIHJhaXNlZCB0
aGUgcG9pbnQgZHVyaW5nIElFVEY5NCBtZWV0aW5nIGFuZCByZXBlYXRlZCBpdCBpbiB0aGUgbWFp
bGluZyBsaXN0LiBJ4oCZbSBhIGJpdCBzdXJwcmlzZWQgYWJvdXQgdGhpcyDigJxub2JvZHkgb2Jq
ZWN0ZWTigJ0gc3RhdGVtZW50Ljxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsg
Jmd0OyZndDsmZ3Q7Jmd0OyBJIGFncmVlIChldmVuIHRob3VnaCBJIHN1cHBvcnQgdGhlIHByb3Bv
c2VkIHRleHQpLiBXaGF0IHdlIGFyZSBzdXBwb3NlZCB0byBiZSBkb2luZzxicj4NCiZndDsgJmd0
OyZndDsmZ3Q7Jmd0OyBpcyBtYWtpbmcgc3VyZSB0aGF0IDI0NjBiaXMgaXMgYW4gdW5hbWJpZ3Vv
dXMgc3RhdGVtZW50IG9mIHJvdWdoIGNvbnNlbnN1cyAoYW5kIGluPGJyPg0KJmd0OyAmZ3Q7Jmd0
OyZndDsmZ3Q7IHRoaXMgY2FzZSwgd2UgYXJlIGFyZ3VpbmcgYWJvdXQgdGhlIGludGVudGlvbiBv
ZiAyNDYwIHdoZXJlIGl0IGxlZnQgc29tZSBkb3VidCkuPGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyBJIGRvbid0IHNlZSBob3cgZmluZGluZyB0aGUgaW50ZW50
aW9uIGlzIHBhcnRpY3VsYXJseSBpbXBvcnRhbnQgbm9yIHVzZWZ1bC48YnI+DQomZ3Q7ICZndDsm
Z3Q7PGJyPg0KJmd0OyAmZ3Q7Jmd0OyBMb29rIHdheSBiYWNrIGluIHRoaXMgdGhyZWFkIHRvIHdo
ZXJlIEkgdHJhY2VkIHRoZSBXRyByb3VnaCBjb25zZW5zdXMgb24gdGhpczxicj4NCiZndDsgJmd0
OyZndDsgcG9pbnQgaW4gMTk5NTsgaXQncyB3aHkgSSd2ZSByZWFkIFJGQzE4ODMvUkZDMjQ2MCBv
bmUgd2F5LCBidXQgb3RoZXJzIChlLmcuIHRoZSBzZWdtZW50PGJyPg0KJmd0OyAmZ3Q7Jmd0OyBy
b3V0aW5nIHBlb3BsZSkgcmVhZCBpdCBkaWZmZXJlbnRseS4gSSByZWFsbHkgdGhpbmsgd2UgbmVl
ZCB0byBmaXggdGhhdCBhbWJpZ3VpdHk8YnI+DQomZ3Q7ICZndDsmZ3Q7IGZvciB0aGUgSW50ZXJu
ZXQgU3RhbmRhcmQgc3RlcC48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7
ICZndDsgSSBkb27igJl0IGRpc2FncmVlIHdpdGggdGhlIGlkZWEgb2YgcmVtb3ZpbmcgYW1iaWd1
aXR5IGZyb20gdGhlIHNwZWMuPGJyPg0KJmd0OyAmZ3Q7PGJyPg0KJmd0OyAmZ3Q7IEhvd2V2ZXIs
IEkgc3Ryb25nbHkgYWR2b2NhdGUgdGhlIGZhY3QgdGhhdCB3ZSBhcmUgbm90IGluIGEgcG9zaXRp
b24gdG8gZG8gaXQgYmVjYXVzZSB3ZeKAmXJlIGp1c3QgYXQgdGhlIGJlZ2lubmluZyBvZiBFSCB1
c2FnZSBhbmQgd2UgbGFjayBvZiBleHBlcmllbmNlLjxicj4NCiZndDsgJmd0Ozxicj4NCiZndDsg
Jmd0OyBXZSBsaXZlZCBmb3IgbW9yZSB0aGFuIDE4IHllYXJzIHdpdGggdGhlIGN1cnJlbnQgc3Bl
YywgSSB0aGluayB3ZeKAmWxsIHN1cnZpdmUgYW5vdGhlciBmZXcgeWVhcnMgZHVyaW5nIHdoaWNo
IHRoZSBpbmR1c3RyeSBjYW4gYWNxdWlyZSBleHBlcmllbmNlLCByZXBvcnQgaXQgdG8gaWV0ZiBh
bmQgdGhlbiwgaWYgbmVjZXNzYXJ5LCB1cGRhdGUgdGhlIHNwZWMuPGJyPg0KJmd0OyAmZ3Q7PGJy
Pg0KJmd0OyAmZ3Q7IFRoYW5rcy48YnI+DQomZ3Q7ICZndDsgcy48YnI+DQomZ3Q7ICZndDs8YnI+
DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsmZ3Q7PGJyPg0KJmd0OyAm
Z3Q7Jmd0OyBSZWdhcmRzPGJyPg0KJmd0OyAmZ3Q7Jmd0Ozxicj4NCiZndDsgJmd0OyZndDsmbmJz
cDsgJm5ic3A7QnJpYW48YnI+DQomZ3Q7ICZndDs8YnI+DQomZ3Q7ICZndDsgLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08
YnI+DQomZ3Q7ICZndDsgSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0PGJyPg0K
Jmd0OyAmZ3Q7IDxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3JnPC9h
Pjxicj4NCiZndDsgJmd0OyBBZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2Ij4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaXB2NjwvYT48YnI+DQomZ3Q7ICZndDsgLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08
YnI+DQomZ3Q7PGJyPg0KJmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDsgSUVURiBJUHY2IHdvcmtp
bmcgZ3JvdXAgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyA8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRm
Lm9yZyI+aXB2NkBpZXRmLm9yZzwvYT48YnI+DQomZ3Q7IEFkbWluaXN0cmF0aXZlIFJlcXVlc3Rz
OiA8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYiPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2NjwvYT48YnI+DQomZ3Q7IC0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1s
Pg0K

--_000_8e407e65a38b439b808abbbf4f50bf57XCHRCD001ciscocom_--


From nobody Wed May 11 09:37:49 2016
Return-Path: <osmankh@yahoo.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 9A97112D1DC for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level: 
X-Spam-Status: No, score=-3.716 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 YS9SW_4-aFWH for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:37:45 -0700 (PDT)
Received: from nm17-vm2.bullet.mail.ne1.yahoo.com (nm17-vm2.bullet.mail.ne1.yahoo.com [98.138.91.93]) (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 AC30C12D1D9 for <ipv6@ietf.org>; Wed, 11 May 2016 09:37:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1462984664; bh=Vf55UQ3V6RBIB6yOG74SFwYT9JsegjRdrZeRAIc7zIM=; h=From:Subject:Date:To:From:Subject; b=phMl9Y9O9Xq3FCxcZP/2nPEopF7pgfL90j0IVxrtY78XRhhmdSgmTctPiUm+hnouc8d0eB/bAiHO5z2EkG80/olK9OPrQSoFfWTpTykohcRMmCUghNcO4coEmnrvEFeeBsdCn2jqIRouMsaQqjWXwjBvb74SyKh97qRpi79DjEBoIElzv8961Svm0aGWNJ502doXqY3y4iYRsO5IR4jottuHaR/mcjEnrSKMGWL9LZCh2oBvKhoujaeAcOiMEm/OBGe+T/aCJsakN52k784bVrugW+LXN63begUi/PH69obuQfk91CtShAAGFKVo8WvmCYMDZySku5UYoYIS1NAHsw==
Received: from [98.138.101.130] by nm17.bullet.mail.ne1.yahoo.com with NNFMP;  11 May 2016 16:37:44 -0000
Received: from [98.138.226.58] by tm18.bullet.mail.ne1.yahoo.com with NNFMP; 11 May 2016 16:37:44 -0000
Received: from [127.0.0.1] by smtp209.mail.ne1.yahoo.com with NNFMP; 11 May 2016 16:37:44 -0000
X-Yahoo-Newman-Id: 861128.9304.bm@smtp209.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: yrN1iJYVM1mfUAhOtb6YYYAGo2BC8PW.J6QkpW4yEOD9wQP eJf.IJu3g2nL.2A1MKE4b_ERptB0v9mUhjP0WKArBqzyMcG902kkTH35vgpa OgZd6JFJ7HNpNJj_EMqJNtYLxycwFhOUxrwXHTrmQzBoB8vn9mQ7NOa6xmnc a5xCcy.FAoPvD7Z8yww_MweMnVCzgwvKkvAD1_wQ2WMcjRp_mbPnXo3txnWl vYIElM0DGQiZ5z5bOwKRIEe0Sferk94wGMY2MI8s7lWcicIG_.gOPgjz_SAA N57SWcPZevPg0S0DQDm02JLzk7OXqgkzIB9ZIFbN_H9m3HBVsXa4EMiFtT_S aeBR7mjR340w8t3du4uwhfVTb.i2YNjYodmFuIL5Q75QtXMV6rAzQ6.avjab U6oaombaQkfwjrVm.5yVcQHpZm2YxKFp4DqopO4hR8pIEALJFhNL4fcWhJ99 yrIRL8n9chnu4hQJDQvtoUf8ql0FibDWchPC84IONlNHqpw1HfqxdYi.BJTW S3RrJA18NSNKvfa7OcN1IHZnOBy8X.orBaltIKCIKRlnv29e7nWR94Q--
X-Yahoo-SMTP: RUL5CFuswBD02LFE5KfPCwZifSs-
From: Osman Khan <osmankh@yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Adding headers and adding options to headers
Message-Id: <A877D11A-8E5B-403B-95E6-5CB2E852FA0E@yahoo.com>
Date: Thu, 12 May 2016 02:37:41 +1000
To: ipv6@ietf.org
X-Mailer: iPhone Mail (13E238)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AROwIXGMz0Q5w_fSxG4zheESJJI>
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, 11 May 2016 16:37:47 -0000

I would like to raise some points here since multiple threads have come up r=
ecently regarding inserting extension headers by intermediate nodes (routers=
)
I have recently gone through an IPv6 rollout for a major mobile carrier and o=
ne of the challenges was deciding how much MSS to allocate to handsets durin=
g handset connectivity phase towards S/PGW (in IPv4 this used to be somewher=
e in the ~1400 byte territory)
However, despite knowing that extension headers are only to be inserted by e=
nd-hosts and not by intermediate nodes, there was/is still an uncertainty am=
ong carries on this point and is a cause of major concern - And it doesn't l=
ook like IETF has done much in this space in order to enforce what would be s=
tandardised approach for this?
In my opinion, leaving this point open would further weaken operators confid=
ence in IPv6 so IETF should take a definitive and clear stance on whether th=
is MUST or MUST NOT be allowed
Given the amount of legacy operating systems and the fact that we need a qui=
ck and easy path towards IPv6 for carriers, I personally think PMTUD and esp=
ecially PLPMTUD type features would not be easy to add to host OSes making i=
t more difficult to facilitate IPv6 transition.
In my opinion, insertion of extension header MUST NOT be allowed on intermed=
iate nodes to clear all this ambiguity and have a clear way forward for impl=
ementations to proceed without doubts=20

Regards,
Usman


> On 12 May 2016, at 2:15 AM, ipv6-request@ietf.org wrote:
>=20
> Re: Adding headers and adding options to headers


From nobody Wed May 11 09:40:50 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 1CE0612D0C3 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, 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 7ewV3UHPawUo for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 09:40:44 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001: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 454BD12D509 for <ipv6@ietf.org>; Wed, 11 May 2016 09:40:41 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id 190so61637404iow.1 for <ipv6@ietf.org>; Wed, 11 May 2016 09:40:41 -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:date:message-id:subject :from:to:cc; bh=p7VALn6s2aynHbT6Y+FtSesVL/t0mkoBOp3DZuCEDB4=; b=0RbMnhtcAQS3ApetcpnnLwLolGKq7zCe3pMlBDk5YoHYQc0KuXxrrTij9WgC/aJa4h 67CKMdEiY9yhWCn0Vlak479UZuOi3uFDnmJQ8mAQlASl17Z0AYoGYAp/s1uRzf75EPyy AOpANPGD6bk5C8qOVYbEClZf0vwuj5JxYkdvWXsCaT7g8XIxA47AvKPChtETyWUgh8lu myUqhveYVeHDL9G/ShhxUO6JZBcBpa3D9P10KIk/66Nv1XUFcM1LwGC52DqjUVEgA/8/ rzPsi1fq+LKd+0g5isYV4sEvUXhNeXvBYAxlS0lLAt2NEi//s0I4AvxBXGvcWJJbBH5V YXVA==
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:date :message-id:subject:from:to:cc; bh=p7VALn6s2aynHbT6Y+FtSesVL/t0mkoBOp3DZuCEDB4=; b=mUNSgbh6QlEbMGAL8uNiWM2xOvkk80XhNaju/YgiqZ29Xfo4ne0YmE3Yx0Q71gHiL1 uYJnvMOIHWamQCi9boNdy/CPend2s1jRgToyGQMxsRrBzL2HbBXb48M+MPZovO3DgmdZ 8uQTOWQE5f5IZHKo5NVmX7gWSgG3XMy8IGXKjosmPro/8kyiw/13rg3vHK5tuEwsYxNo NfaOY4ZSV35ONtDRmBwU3y1DTFeUPmnZpR0VZUUjF4YudLMyvCNRjRHB+JIFGAfUpmc7 kC3s0BsqAGsWfbjrSKEnuNPHeplnzg6LtqlsHga+EmmF86J8jU5MRDiFtPPPUXOdn4l1 yuNg==
X-Gm-Message-State: AOPr4FVRVqBINByY7X4OHNdpoLIGiiUQS3SCv/i4qo0dLaEfRjqlY/w8Dh1kzlIyg/gbRzduUWMUJ1oGInUCZg==
MIME-Version: 1.0
X-Received: by 10.36.84.76 with SMTP id t73mr3124738ita.7.1462984840703; Wed, 11 May 2016 09:40:40 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Wed, 11 May 2016 09:40:40 -0700 (PDT)
In-Reply-To: <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
Date: Wed, 11 May 2016 09:40:40 -0700
X-Google-Sender-Auth: uXOv-lwaE2zlIAW5X9tnxeVT81M
Message-ID: <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/v70XRRWZeBaT2n8EiZjiIjtaeTY>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 16:40:49 -0000

At Wed, 11 May 2016 20:22:57 +1200,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> > I don't see how finding the intention is particularly important nor useful.
>
> Look way back in this thread to where I traced the WG rough consensus on this
> point in 1995; it's why I've read RFC1883/RFC2460 one way, but others (e.g. the segment
> routing people) read it differently. I really think we need to fix that ambiguity
> for the Internet Standard step.

+1 (about the need for the fix).

It could be understandable, though I'm not convinced about it yet,
that someone who doesn't like the original intent (because it would
break some existing product of them?) wants to overturn it.  But in
any case it doesn't make sense to me at all to just leave the
ambiguity.  It will just result in more confusion and more possibility
of interoperability problems in the mean time.

--
JINMEI, Tatuya


From nobody Wed May 11 11:39:08 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 6BF3812D586 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 11:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 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=-0.996, SPF_PASS=-0.001] autolearn=ham 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 lUIt5v7-ey43 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 11:39:04 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B80A12D746 for <ipv6@ietf.org>; Wed, 11 May 2016 11:39:01 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 789D69CC7C; Wed, 11 May 2016 11:39:00 -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=sii/msYmectwPw9i13eAC/Af+DQ=; b= UQf5zQn98NYJ+0bGBIOS5wrs37Je0yJGp4e3R52EC4zXeakbxiUnwduQKi1c4euZ o/sZLQ0KmsqvRNSxjy2EPQXGsKbzmleq/7AyLhq1Vhjgt1dX0tdUDHCXLotXw2kl 11F2sJMcq1hhzOfXGGxp/alLvqdRjx1WQWaOfaiCCOM=
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=ChMzfYnRaaBw/tUJYfz9hMvEgH UFMVxZVNTlHcxSHEEEZd1p2WtoInYIm504VZhfcMevSCvBpFAgnzhT/tRTlop4ch Z6fR98+h6VChM2yE3YbQlYpTJ1o6iFWS7zAGBh3v6MT8PPkvguteicI1CVi4fL7k fGgRlhY8avY/A7fII=
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 452229CC0F; Wed, 11 May 2016 11:39:00 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 00F30164C0F8; Wed, 11 May 2016 20:38:54 +0200 (CEST)
Subject: Re: Adding headers and adding options to headers
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_604AAA9B-458F-4A7A-B907-D3875E23F806"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com>
Date: Wed, 11 May 2016 20:38:54 +0200
Message-Id: <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/itgiblWraeeIvd9A27IX4kZBU20>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 18:39:06 -0000

--Apple-Mail=_604AAA9B-458F-4A7A-B907-D3875E23F806
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>>> I don't see how finding the intention is particularly important nor =
useful.
>>=20
>> Look way back in this thread to where I traced the WG rough consensus =
on this
>> point in 1995; it's why I've read RFC1883/RFC2460 one way, but others =
(e.g. the segment
>> routing people) read it differently. I really think we need to fix =
that ambiguity
>> for the Internet Standard step.
>=20
> +1 (about the need for the fix).
>=20
> It could be understandable, though I'm not convinced about it yet,
> that someone who doesn't like the original intent (because it would
> break some existing product of them?) wants to overturn it.  But in
> any case it doesn't make sense to me at all to just leave the
> ambiguity.  It will just result in more confusion and more possibility
> of interoperability problems in the mean time.

do you know of any interoperability problems with the current RFC2460?
that has to be the driving issue in deciding this.

with regards to making prohibitions on future work in current protocol =
specifications, can you cite any example of the IETF being successful =
with that? :-)

RFC2460 already has this prohibition by the way:

   With one exception, extension headers are not examined or processed
   by any node along a packet's delivery path, until the packet reaches
   the node (or each of the set of nodes, in the case of multicast)
   identified in the Destination Address field of the IPv6 header.

I'm afraid I don't see the point in changing RFC2460 here.

cheers,
Ole


--Apple-Mail=_604AAA9B-458F-4A7A-B907-D3875E23F806
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

iQEcBAEBCgAGBQJXM3w+AAoJED4aXnjSQuKW32gH+wXj6tGgnZim4k55Etp9WV9a
cWJLUThEjxyAttTHmPQ/sKeRYAaNKJHcoZhdstCHp6Nf/OtcJuXlhktL8F82YBjm
IknEbnLTxpw3oeRqWdrOqooSHHGgvIzhBRO2pnLZNS8Do4RruIgUkFnQodAj2SgO
wHumkYVbENfdiYwthxXc/J5G4ghrOOEBUNGB4ffq5zhsbKBEioXekVfn7Wbk3mQI
FN5q5cSNdz+ciR2aFvGL7MvEjiBdcLxYhY8SVTEAojGR2ZGQFqwI89xxaLOwjA0i
nrZ16NF74qt0vJf35JEkZCPEHJBRqe90CYDbGEOyMWZGcxWZNEh2RTanaL+zNsM=
=Ek52
-----END PGP SIGNATURE-----

--Apple-Mail=_604AAA9B-458F-4A7A-B907-D3875E23F806--


From nobody Wed May 11 13:36:47 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 6EF4612D1DE for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 13:36:45 -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 JG0rbuurCc2k for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 13:36:43 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 78EA312D5F3 for <ipv6@ietf.org>; Wed, 11 May 2016 13:36:43 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id 77so22133549pfv.2 for <ipv6@ietf.org>; Wed, 11 May 2016 13:36:43 -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=bkWqc32RHVLYDRJIZJNP43zXk1ZgRO9JKG8Mt5kTc6c=; b=to0dFAtlNBTChKBTLctcaINDxcl9HLE0XxHrxJHEjAUCq81xf9zxuu7YWbu5TXqk4n oV8sARLxsIEqSm/PRwD3rx4CdRG02XaCo1eGiz0l6yKOijYt8ufreIktRpi1Td9Cr4G0 SWDtaSRI1plaZapIWMTYms7YhCR6RX2ei2J3dJ1D5X/urmGjvSF559T+79yv5gwLIq/g /q2mfXg6WDNFrAzEags9s4IwgXjIKlWr6Tto6ZltKvb0xFMFXfKHEhTIqa6nIIBjmtnO mk9AOOVvOMMRHKdzalnQATmnoWY5ZAQTFoddJDTIyoNjUPpLYn3LCn/UYMLarLWaEruG c2DA==
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=bkWqc32RHVLYDRJIZJNP43zXk1ZgRO9JKG8Mt5kTc6c=; b=Cq4lKqPFT7ps27qwOkz+QVtKif13sS+DbcGYhLGiRotp4GNOYTCLEP5BZL9x42Yxez lEtR8auGWAAmNNi1NrY7vEMTtB67sX/Wk1CBQPXCuBOt4J6x27ctVDa+AXlNU1D3QGtt 9EGrTW0J2viT7ApvRrNGotTkaXYCb9xwaaTa0FAP9b2mmRkKzvSxf3KUNIaSubLiXmc4 505pbNf3gO00RI8yBQaIMvdcIgH38dILjn/oUp6Kn3KQw3FkpSV4n2qxZ3D5JkeaaA2Z l0qOWMOgsorFHdB9PwRWkUPSi8bIWFEzi5I00Zb/crgOumZG8kWFUwz/yHD+KHKn9O0e M0OQ==
X-Gm-Message-State: AOPr4FUGPmTxBvBDZmHQzT319k7jk3ajmXQy/blqbn9ezN6KrfOt5k2gKqcVDd6tU4ksAQ==
X-Received: by 10.98.54.194 with SMTP id d185mr8014132pfa.34.1462999003122; Wed, 11 May 2016 13:36:43 -0700 (PDT)
Received: from ?IPv6:2406:e007:5004:1:28cc:dc4c:9703:6781? ([2406:e007:5004:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 5sm14249007pfi.91.2016.05.11.13.36.39 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 13:36:41 -0700 (PDT)
Subject: Re: Adding headers and adding options to headers
To: otroan@employees.org, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
Date: Thu, 12 May 2016 08:37:03 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1cKcl80PMW00hD0RkaS9ELhk_Z0>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 20:36:45 -0000

Ole,

Trying to answer your specific comments concisely:

On 12/05/2016 06:38, otroan@employees.org wrote:
>>>> I don't see how finding the intention is particularly important nor useful.
>>>
>>> Look way back in this thread to where I traced the WG rough consensus on this
>>> point in 1995; it's why I've read RFC1883/RFC2460 one way, but others (e.g. the segment
>>> routing people) read it differently. I really think we need to fix that ambiguity
>>> for the Internet Standard step.
>>
>> +1 (about the need for the fix).
>>
>> It could be understandable, though I'm not convinced about it yet,
>> that someone who doesn't like the original intent (because it would
>> break some existing product of them?) wants to overturn it.  But in
>> any case it doesn't make sense to me at all to just leave the
>> ambiguity.  It will just result in more confusion and more possibility
>> of interoperability problems in the mean time.
> 
> do you know of any interoperability problems with the current RFC2460?
> that has to be the driving issue in deciding this.

Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
as "strongly recommended" so that is normative.

> 
> with regards to making prohibitions on future work in current protocol specifications, can you cite any example of the IETF being successful with that? :-)
> 
> RFC2460 already has this prohibition by the way:
> 
>    With one exception, extension headers are not examined or processed
>    by any node along a packet's delivery path, until the packet reaches
>    the node (or each of the set of nodes, in the case of multicast)
>    identified in the Destination Address field of the IPv6 header.
> 
> I'm afraid I don't see the point in changing RFC2460 here.

The word "processed" is the problem here - it is ambiguous. That is the
spcific reason for adding "modified or inserted".

Regards
    Brian


From nobody Wed May 11 13:47:34 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 81AFC12D57E for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 13:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 5dTISWAwcVpX for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 13:47:30 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 6C3CC12D0C9 for <ipv6@ietf.org>; Wed, 11 May 2016 13:47:30 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id m188so72993376vka.1 for <ipv6@ietf.org>; Wed, 11 May 2016 13:47: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:date:message-id:subject:from:to :cc; bh=ugJpVV52c1edIsEOw/QJf8YuLKFqe7kWz5xEH/RsrLg=; b=Xhetc3sFb6Vd6Y0Up3Ab2bnE5pOgVtENFoO3qYqGQpcT5OspsSd8NCI2ZcyNgnhpJC CUNTTwxTvrmUjYQXQVI6nGIuRq7m2dPs39bO2iZze4BMp4JmnqFRXJadNAuTza03SKkY 5cSWdb370pW7d34KhYWg3lK7+IIo1GGLVIaq/ScLk0QOjWuu7KKcav93HE4TQjEPJjty ZYCDcQ16c6RPY8nwCrNdc0xQBxhcZes2zVlk2oo+jQB45s3pmfjELsYGLdsNLMJERIZ7 siTLCuMoPVHSqkB0+6cegts3EXnvVH7OCHynrcNVUReEwmheTYOeUNtwQswRphqi860y KPKg==
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:date :message-id:subject:from:to:cc; bh=ugJpVV52c1edIsEOw/QJf8YuLKFqe7kWz5xEH/RsrLg=; b=UpEEr4xfAGZxekYSUauMcWkTGwaNJBgJ01iO0q2yp/MkV8gyc2bXvXFwPlwUsrlH73 hKXljWuoMh6ZLEB/cvk/gW4rcsJBLt0D8QbwUKGW349InnuU+gL8eoSIf7VawICqkb14 VEjfMPGGeAM2F63MGwlo/gXEZ1pWrg6xh5IjmA1pvcWNX/4CwSjqe8XHRrDhL50+J/YM oHo9f2X9nZA1f9v9QF/JXnMA3l4ZlN2hJDv0ZfXSABKK7AtDMzSca+gY9MUuS9EhJ90o 7r5EfQd/j6r9kW9QBOYPaMz1vbDgAIDGiy1oQsvcZ7nsbvOfqn44zc+V77Hc9TcSpJdr 9kPA==
X-Gm-Message-State: AOPr4FWk0LXpOMUh27CBYrCWJSNDe9Y8fuDOCuZjzDw2mJWdqa5DwfzVPL8isiaratMzdIJ/pbgVBSl9W4YT8w==
MIME-Version: 1.0
X-Received: by 10.31.73.132 with SMTP id w126mr2803378vka.94.1462999649481; Wed, 11 May 2016 13:47:29 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 13:47:29 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 13:47:29 -0700 (PDT)
In-Reply-To: <8e407e65a38b439b808abbbf4f50bf57@XCH-RCD-001.cisco.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <86DB67F3-8918-4547-A840-F7A86F862415@cisco.com> <F70E5C70-73EE-43A5-8032-A256AF60BAC5@cisco.com> <CAO42Z2xW1ppOwuXNeGoj3qiCvqQpV_6ndwveVVDHL+XDBNy1ag@mail.gmail.com> <8e407e65a38b439b808abbbf4f50bf57@XCH-RCD-001.cisco.com>
Date: Thu, 12 May 2016 06:47:29 +1000
Message-ID: <CAO42Z2zhcns=4V6F6sr4x9UYjdZnaQaYvPOhGU3AkQnj_uQ3tA@mail.gmail.com>
Subject: RE: Adding headers and adding options to headers
From: Mark Smith <markzzzsmith@gmail.com>
To: "Pascal Thubert, (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=001a114dd5a069fe050532972654
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Bzg32JvRLWXbiQUEubKu_fB8Cug>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 20:47:33 -0000

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

On 12 May 2016 02:14, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
wrote:
>
> Hello Mark:
>
>

If you think I'm using FUD, then I wonder if you have had any experience
troubleshooting the sorts of problems this could cause. That is why I argue
strongly against it - I don't see the benefits are worth the cost when I
think there is a much better alternative.

Regards,
Mark.

>
> Cheers,
>
>
>
> Pascal
>
>
>
> From: Mark Smith [mailto:markzzzsmith@gmail.com]
> Sent: mercredi 11 mai 2016 12:05
> To: Pascal Thubert (pthubert) <pthubert@cisco.com>
> Cc: Fred Baker (fred) <fred@cisco.com>; Bob Hinden <bob.hinden@gmail.com>=
;
6man WG <ipv6@ietf.org>; Stefano Previdi (sprevidi) <sprevidi@cisco.com>
> Subject: Re: Adding headers and adding options to headers
>
>
>
>
> On 11 May 2016 18:56, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
wrote:
> >
> > Agreed,
> >
> > the last thing we need is stronger rules without a deep proof that the
stronger rule is really needed to get the systems work and interoperate.
> >
>
> The thing I don't understand is the need for proof. Do we really need to
*prove* that adding unexpected EHs mid-flight is going to break things even
though it is foreseeable that they will, because it is easy to see how it
will interact badly with the existing mechanisms?
>
>
>
> >> Looks like FUD to me. Any addition must be done carefully and ideally
pass through this group for validation.
>
> >  Ambiguity has a good history of creating interop issues (not the case
here is it?). It has also provided the necessary elasticity for innovation
and evolution. Sometimes the authors leave that ambiguity voluntary and
removing it for the sake of it is actually destroying their work (eg flow
label).
> >
> > I may have missed one but my summary of why we'd be removing this
ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and
traceability (who did what). My take is that those issues should be solved
for their own sake as opposed to killing the messenger.
> >
>
> How? How are you going to trace who did what if the device silently did
it? If you don't have an answer, you're creating the problem and then
making it somebody else's problem to fix. I think people who create
problems are obligated to fix them.
>
> >> we could work on improving traceability. I=E2=80=99d support such work=
. This
may mean more headers being modified on the fly ; )
>
> Tunneling already solves these problems and facilitates adding EHs. Why
are people choosing to ignore this option? What is the unstated bias
against tunneling?
>
> >> tunnels are not exempt of problems. They can cause additional
fragmentation, add to loss and latency... And tunnels cannot solve
everything. If more than one router needs to add/mod stuff, there would be
IP in IP in IP and only the outer encapsulation would be observed and that
would not be the desired result. Basically tunneling breaks the whole idea.
>
> > Did this ambiguity prove useful? Yes! Because the source does not know
it all. SR is a clear proof there's value in adding applicable semantics to
the packet. There were others before (eg RPL) and there will be more.
> >
>
> The question isn't whether or not the added semantics have value.
>
> The question is what is the best way to add those semantics that doesn't
interact badly with or cause to fail existing, widely deployed mechanisms
(like PMTUD), doesn't violate established semantics of existing fields
(like a "multi-source packet" (meaning multiple devices are the source of
parts of the packet) with a single source address field would), and doesn't
make troubleshooting an operational network harder than it already is.
>
> >> So you=E2=80=99re opposing a general capability that could in fact be =
used to
instrument packets and help understand how the network is going? That could
be used to avoid a congestion that=E2=80=99s indeed hard to troubleshoot? W=
e do not
need a general ruling, we need a case by case and careful examination.
>
> In theory, these edited packets would never leak from the editing domain,
and devices that add or remove them would never need troubleshooting.
Practice and theory are rarely the same.
>
> >> FUD. If this group defines a new operation, I=E2=80=99m sure it will m=
ake it
properly.
>
> Regards,
> Mark.
>
> > Regards,
> >
> > Pascal
> >
> > > Le 11 mai 2016 =C3=A0 10:39, Stefano Previdi (sprevidi) <sprevidi@cis=
co.com>
a =C3=A9crit :
> > >
> > >
> > >> On May 11, 2016, at 10:22 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
> > >>
> > >> Ole,
> > >> On 11/05/2016 18:12, otroan@employees.org wrote:
> > >>>>> correct. I raised the point during IETF94 meeting and repeated it
in the mailing list. I=E2=80=99m a bit surprised about this =E2=80=9Cnobody=
 objected=E2=80=9D
statement.
> > >>>>
> > >>>> I agree (even though I support the proposed text). What we are
supposed to be doing
> > >>>> is making sure that 2460bis is an unambiguous statement of rough
consensus (and in
> > >>>> this case, we are arguing about the intention of 2460 where it
left some doubt).
> > >>>
> > >>> I don't see how finding the intention is particularly important nor
useful.
> > >>
> > >> Look way back in this thread to where I traced the WG rough
consensus on this
> > >> point in 1995; it's why I've read RFC1883/RFC2460 one way, but
others (e.g. the segment
> > >> routing people) read it differently. I really think we need to fix
that ambiguity
> > >> for the Internet Standard step.
> > >
> > >
> > > I don=E2=80=99t disagree with the idea of removing ambiguity from the=
 spec.
> > >
> > > However, I strongly advocate the fact that we are not in a position
to do it because we=E2=80=99re just at the beginning of EH usage and we lac=
k of
experience.
> > >
> > > We lived for more than 18 years with the current spec, I think we=E2=
=80=99ll
survive another few years during which the industry can acquire experience,
report it to ietf and then, if necessary, update the spec.
> > >
> > > Thanks.
> > > s.
> > >
> > >
> > >
> > >>
> > >> Regards
> > >>
> > >>   Brian
> > >
> > > --------------------------------------------------------------------
> > > IETF IPv6 working group mailing list
> > > ipv6@ietf.org
> > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > --------------------------------------------------------------------
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 12 May 2016 02:14, &quot;Pascal Thubert (pthubert)&quot; &lt;<a href=3D"=
mailto:pthubert@cisco.com">pthubert@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello Mark:<br>
&gt;<br>
&gt; =C2=A0</p>
<p dir=3D"ltr">If you think I&#39;m using FUD, then I wonder if you have ha=
d any experience troubleshooting the sorts of problems this could cause. Th=
at is why I argue strongly against it - I don&#39;t see the benefits are wo=
rth the cost when I think there is a much better alternative.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br><br></p>
<p dir=3D"ltr">&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; =C2=A0<br>
&gt;<br>
&gt; Pascal<br>
&gt;<br>
&gt; =C2=A0<br>
&gt;<br>
&gt; From: Mark Smith [mailto:<a href=3D"mailto:markzzzsmith@gmail.com">mar=
kzzzsmith@gmail.com</a>] <br>
&gt; Sent: mercredi 11 mai 2016 12:05<br>
&gt; To: Pascal Thubert (pthubert) &lt;<a href=3D"mailto:pthubert@cisco.com=
">pthubert@cisco.com</a>&gt;<br>
&gt; Cc: Fred Baker (fred) &lt;<a href=3D"mailto:fred@cisco.com">fred@cisco=
.com</a>&gt;; Bob Hinden &lt;<a href=3D"mailto:bob.hinden@gmail.com">bob.hi=
nden@gmail.com</a>&gt;; 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org">ipv6@i=
etf.org</a>&gt;; Stefano Previdi (sprevidi) &lt;<a href=3D"mailto:sprevidi@=
cisco.com">sprevidi@cisco.com</a>&gt;<br>
&gt; Subject: Re: Adding headers and adding options to headers<br>
&gt;<br>
&gt; =C2=A0<br>
&gt;<br>
&gt;<br>
&gt; On 11 May 2016 18:56, &quot;Pascal Thubert (pthubert)&quot; &lt;<a hre=
f=3D"mailto:pthubert@cisco.com">pthubert@cisco.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Agreed,<br>
&gt; &gt;<br>
&gt; &gt; the last thing we need is stronger rules without a deep proof tha=
t the stronger rule is really needed to get the systems work and interopera=
te.<br>
&gt; &gt;<br>
&gt;<br>
&gt; The thing I don&#39;t understand is the need for proof. Do we really n=
eed to *prove* that adding unexpected EHs mid-flight is going to break thin=
gs even though it is foreseeable that they will, because it is easy to see =
how it will interact badly with the existing mechanisms?<br>
&gt;<br>
&gt; =C2=A0<br>
&gt;<br>
&gt; &gt;&gt; Looks like FUD to me. Any addition must be done carefully and=
 ideally pass through this group for validation. =C2=A0<br>
&gt;<br>
&gt; &gt; =C2=A0Ambiguity has a good history of creating interop issues (no=
t the case here is it?). It has also provided the necessary elasticity for =
innovation and evolution. Sometimes the authors leave that ambiguity volunt=
ary and removing it for the sake of it is actually destroying their work (e=
g flow label).<br>
&gt; &gt;<br>
&gt; &gt; I may have missed one but my summary of why we&#39;d be removing =
this ambiguity comes from 2 issues, PMTUD (which is so broken anyway) and t=
raceability (who did what). My take is that those issues should be solved f=
or their own sake as opposed to killing the messenger.<br>
&gt; &gt;<br>
&gt;<br>
&gt; How? How are you going to trace who did what if the device silently di=
d it? If you don&#39;t have an answer, you&#39;re creating the problem and =
then making it somebody else&#39;s problem to fix. I think people who creat=
e problems are obligated to fix them.<br>
&gt;<br>
&gt; &gt;&gt; we could work on improving traceability. I=E2=80=99d support =
such work. This may mean more headers being modified on the fly ; )<br>
&gt;<br>
&gt; Tunneling already solves these problems and facilitates adding EHs. Wh=
y are people choosing to ignore this option? What is the unstated bias agai=
nst tunneling?<br>
&gt;<br>
&gt; &gt;&gt; tunnels are not exempt of problems. They can cause additional=
 fragmentation, add to loss and latency... And tunnels cannot solve everyth=
ing. If more than one router needs to add/mod stuff, there would be IP in I=
P in IP and only the outer encapsulation would be observed and that would n=
ot be the desired result. Basically tunneling breaks the whole idea.<br>
&gt;<br>
&gt; &gt; Did this ambiguity prove useful? Yes! Because the source does not=
 know it all. SR is a clear proof there&#39;s value in adding applicable se=
mantics to the packet. There were others before (eg RPL) and there will be =
more.<br>
&gt; &gt;<br>
&gt;<br>
&gt; The question isn&#39;t whether or not the added semantics have value.<=
br>
&gt;<br>
&gt; The question is what is the best way to add those semantics that doesn=
&#39;t interact badly with or cause to fail existing, widely deployed mecha=
nisms (like PMTUD), doesn&#39;t violate established semantics of existing f=
ields (like a &quot;multi-source packet&quot; (meaning multiple devices are=
 the source of parts of the packet) with a single source address field woul=
d), and doesn&#39;t make troubleshooting an operational network harder than=
 it already is.<br>
&gt;<br>
&gt; &gt;&gt; So you=E2=80=99re opposing a general capability that could in=
 fact be used to instrument packets and help understand how the network is =
going? That could be used to avoid a congestion that=E2=80=99s indeed hard =
to troubleshoot? We do not need a general ruling, we need a case by case an=
d careful examination.<br>
&gt;<br>
&gt; In theory, these edited packets would never leak from the editing doma=
in, and devices that add or remove them would never need troubleshooting. P=
ractice and theory are rarely the same.<br>
&gt;<br>
&gt; &gt;&gt; FUD. If this group defines a new operation, I=E2=80=99m sure =
it will make it properly.<br>
&gt;<br>
&gt; Regards,<br>
&gt; Mark.<br>
&gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt;<br>
&gt; &gt; Pascal<br>
&gt; &gt;<br>
&gt; &gt; &gt; Le 11 mai 2016 =C3=A0 10:39, Stefano Previdi (sprevidi) &lt;=
<a href=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>&gt; a =C3=A9cr=
it :<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; On May 11, 2016, at 10:22 AM, Brian E Carpenter &lt;<a h=
ref=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&=
gt; wrote:<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Ole,<br>
&gt; &gt; &gt;&gt; On 11/05/2016 18:12, <a href=3D"mailto:otroan@employees.=
org">otroan@employees.org</a> wrote:<br>
&gt; &gt; &gt;&gt;&gt;&gt;&gt; correct. I raised the point during IETF94 me=
eting and repeated it in the mailing list. I=E2=80=99m a bit surprised abou=
t this =E2=80=9Cnobody objected=E2=80=9D statement.<br>
&gt; &gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; I agree (even though I support the proposed text=
). What we are supposed to be doing<br>
&gt; &gt; &gt;&gt;&gt;&gt; is making sure that 2460bis is an unambiguous st=
atement of rough consensus (and in<br>
&gt; &gt; &gt;&gt;&gt;&gt; this case, we are arguing about the intention of=
 2460 where it left some doubt).<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; I don&#39;t see how finding the intention is particu=
larly important nor useful.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Look way back in this thread to where I traced the WG ro=
ugh consensus on this<br>
&gt; &gt; &gt;&gt; point in 1995; it&#39;s why I&#39;ve read RFC1883/RFC246=
0 one way, but others (e.g. the segment<br>
&gt; &gt; &gt;&gt; routing people) read it differently. I really think we n=
eed to fix that ambiguity<br>
&gt; &gt; &gt;&gt; for the Internet Standard step.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don=E2=80=99t disagree with the idea of removing ambiguity=
 from the spec.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; However, I strongly advocate the fact that we are not in a p=
osition to do it because we=E2=80=99re just at the beginning of EH usage an=
d we lack of experience.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; We lived for more than 18 years with the current spec, I thi=
nk we=E2=80=99ll survive another few years during which the industry can ac=
quire experience, report it to ietf and then, if necessary, update the spec=
.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Thanks.<br>
&gt; &gt; &gt; s.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Regards<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt;=C2=A0 =C2=A0Brian<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; ------------------------------------------------------------=
--------<br>
&gt; &gt; &gt; IETF IPv6 working group mailing list<br>
&gt; &gt; &gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; &gt; &gt; Administrative Requests: <a href=3D"https://www.ietf.org/mai=
lman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; &gt; &gt; ------------------------------------------------------------=
--------<br>
&gt; &gt;<br>
&gt; &gt; -----------------------------------------------------------------=
---<br>
&gt; &gt; IETF IPv6 working group mailing list<br>
&gt; &gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; &gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/=
listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; &gt; -----------------------------------------------------------------=
---</p>

--001a114dd5a069fe050532972654--


From nobody Wed May 11 14:45:55 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 3139412D5E4 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 14:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, 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 CCrjEhrFsQLc for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 14:45:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B44FE12D5DF for <ipv6@ietf.org>; Wed, 11 May 2016 14:45:52 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7F65C200A5; Wed, 11 May 2016 17:51:26 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EC22D63755; Wed, 11 May 2016 17:45:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adding headers and adding options to headers
In-Reply-To: <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 11 May 2016 17:45:51 -0400
Message-ID: <14024.1463003151@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e1zOcunBjUKjkjbthN88NqhP2EM>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, =?us-ascii?Q?=3D=3FUTF-8=3FB=3F56We5piO6YGU5ZOJ=3F=3D?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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, 11 May 2016 21:45:54 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> do you know of any interoperability problems with the current RFC2460?
    >> that has to be the driving issue in deciding this.

    > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
    > as "strongly recommended" so that is normative.

Again: I claim PMTUD is already broken and unfixable.
(and should be replaced by PLMTUD, which should be turned on by default)

What else does inserting headers break that isn't related to PMTU ICMPs?

(I'm not in favour of inserting headers.  I am in favour of having rational
and evidence based reasons in our specifications, or they will get ignored).


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVzOoDYCLcPvd0N1lAQLhuQf+PUCBHGxx6byHiLhdv8pl2qZoPO3dcrbZ
JW9BMv3+Jkhzn1a9gPDfYgWg10uSVMTm0uY51tCcGQc1cu/jpAvzeVG9geW54G4f
bBet1okTxHY79C2urQmpvHLYGNLnpSTtnSIQPJLNbxqqDRymSLqBbuY+voP6RYgx
KCxAkhsLCIFeskjygNeBI8xMFEAR7I34kkch7x9EvepwcSYzoN36WEpRCY3VqZtF
kjit9yUxtjUzVkL4Unr3akcXBsUjrTyK9RgJDxqKJWnK7N8ILhYQX/ew5/4PkRyw
Jtb9434lKsDv1LLumvQNt7/uFsIMKTSwMD2pEjegZ29YK0esxyJMhw==
=r1S7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed May 11 15:40:35 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 403CC12D18F for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 15:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 LBBk-CTXhqlp for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 15:40:31 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 D338312B049 for <ipv6@ietf.org>; Wed, 11 May 2016 15:40:30 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id s184so75899779vkb.3 for <ipv6@ietf.org>; Wed, 11 May 2016 15:40: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:date:message-id:subject:from:to :cc; bh=uLDnrFYp9HnFFZJED5YfHbyv2j2cL2IVLuDHaApqUVM=; b=sxz3srs47bGMdMBnWHHKQAXFL7QJ8dRYi5IhJfBCdNxSe/+mKyhSM6ZUm6Jdclrvvd sLN8Z9/a8GGNSn93nZgyBbCjL5+RWP+ueqaVI822ePcqbOBS5IbNnFgg+rqcDyZV945S FLPDjQp34chOzyfx++DxZDDeD0MBv9yHTvjuyliap88j4DmVNYzaml6wdf1dGDaUltOh 8RuMEgjVFEyinOBfwzraeI0yST4hBb5zNKIxZdaNaW9pb9YZgVQMS5V4M8gJ4APLn2kM z/EPkPMVVaRL2JYBALI+CZpfffGci+x7IBF9CNssciaD8UaZto7sFiNWrB0qckM9ZXEL mOww==
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:date :message-id:subject:from:to:cc; bh=uLDnrFYp9HnFFZJED5YfHbyv2j2cL2IVLuDHaApqUVM=; b=SAMaCVVQyB7m9s5LcZfwsmYOTMNByQIex0M8yL6Ktyc2w+A+YJN22klMlxjvae5kPw 8bmA8gDlKcuNfjWPmV3am6hq7J0QYK3US9KXMCklsU3/uiDBjwRIIFki4E/cAM9mPqZI jS4C9Q27LuYdE4q1p/WwcbTQWs5fMm6kDifmYHewRL0zc22BPcHq3mC2w29zGu0oXHLf VnL0T7npVlcIzG8a5uPzynazvBdpDuynzutGcpz8cXWMeTcljXFJFStS7UuO2WV5AxiQ iGQeNjPFHAkoZIbXrZP9hXqa0/MR/9id8skjP6Y2nrvQAsL/hr87qRWG5iggEcdtfuOn uqqQ==
X-Gm-Message-State: AOPr4FWG0GlyKhZvfCsJ2XORhjjqtObfR2qwc4pR2b/8/vwDHIsQ0P6U+gxYK9JhFc/PoFoUDrl9W1L199T+vw==
MIME-Version: 1.0
X-Received: by 10.31.146.144 with SMTP id u138mr3025454vkd.2.1463006429967; Wed, 11 May 2016 15:40:29 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 15:40:29 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Wed, 11 May 2016 15:40:29 -0700 (PDT)
In-Reply-To: <14024.1463003151@obiwan.sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca>
Date: Thu, 12 May 2016 08:40:29 +1000
Message-ID: <CAO42Z2w9JgAkdZ0AdC6Mkqn4Drfho5i0HyGoPVmx6GGCUAZJMw@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: Mark Smith <markzzzsmith@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a114374929001c2053298ba32
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LIuywGT-IcgeBo7RqN3cWb0LXww>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>, =?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: Wed, 11 May 2016 22:40:33 -0000

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

On 12 May 2016 07:46, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:
>
>
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> do you know of any interoperability problems with the current
RFC2460?
>     >> that has to be the driving issue in deciding this.
>
>     > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     > as "strongly recommended" so that is normative.
>
> Again: I claim PMTUD is already broken and unfixable.
> (and should be replaced by PLMTUD, which should be turned on by default)
>
> What else does inserting headers break that isn't related to PMTU ICMPs?
>

The name and purpose of the source address field in the packet.

If there can be multiple originators of parts of a packet, created by
multiple sources, the name of that field would now be incorrect. It would
now only be carrying the first source of the first part of the packet, with
no way to tell if the listed address created the whole or only part of the
packet.

That's how fundamental a change this would be. Anything that believes the
source address in a packet is the originator of all parts of the packet -
protocols, devices, troubleshooting tools and methods, and many network
operators - will now be relying on a falsehood.

So if adding EHs is to be permitted, then the source address field name and
description must be changed too, and everywhere this assumption about
source = whole of packet originator (RFCs, documentation, troubleshooting
tools etc.) also needs to be changed.

I think this discussion is really about whether to support multi-source
packets or not, and then the consequences of only encoding the first source
in the packet.

> (I'm not in favour of inserting headers.  I am in favour of having
rational
> and evidence based reasons in our specifications, or they will get
ignored).
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr"><br>
On 12 May 2016 07:46, &quot;Michael Richardson&quot; &lt;<a href=3D"mailto:=
mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">b=
rian.e.carpenter@gmail.com</a>&gt; wrote:<br>
&gt; =C2=A0 =C2=A0 &gt;&gt; do you know of any interoperability problems wi=
th the current RFC2460?<br>
&gt; =C2=A0 =C2=A0 &gt;&gt; that has to be the driving issue in deciding th=
is.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 &gt; Yes. Inserting extension headers breaks PMTUD. RFC2=
460 cites RFC1981<br>
&gt; =C2=A0 =C2=A0 &gt; as &quot;strongly recommended&quot; so that is norm=
ative.<br>
&gt;<br>
&gt; Again: I claim PMTUD is already broken and unfixable.<br>
&gt; (and should be replaced by PLMTUD, which should be turned on by defaul=
t)<br>
&gt;<br>
&gt; What else does inserting headers break that isn&#39;t related to PMTU =
ICMPs?<br>
&gt;</p>
<p dir=3D"ltr">The name and purpose of the source address field in the pack=
et. <br></p>
<p dir=3D"ltr">If there can be multiple originators of parts of a packet, c=
reated by multiple sources, the name of that field would now be incorrect. =
It would now only be carrying the first source of the first part of the pac=
ket, with no way to tell if the listed address created the whole or only pa=
rt of the packet.</p>
<p dir=3D"ltr">That&#39;s how fundamental a change this would be. Anything =
that believes the source address in a packet is the originator of all parts=
 of the packet - protocols, devices, troubleshooting tools and methods, and=
 many network operators - will now be relying on a falsehood.</p>
<p dir=3D"ltr">So if adding EHs is to be permitted, then the source address=
 field name and description must be changed too, and everywhere this assump=
tion about source =3D whole of packet originator (RFCs, documentation, trou=
bleshooting tools etc.) also needs to be changed.</p>
<p dir=3D"ltr">I think this discussion is really about whether to support m=
ulti-source packets or not, and then the consequences of only encoding the =
first source in the packet.</p>
<p dir=3D"ltr">&gt; (I&#39;m not in favour of inserting headers.=C2=A0 I am=
 in favour of having rational<br>
&gt; and evidence based reasons in our specifications, or they will get ign=
ored).<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+=
IETF@sandelman.ca</a>&gt;, Sandelman Software Works<br>
&gt; =C2=A0-=3D IPv6 IoT consulting =3D-<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/listin=
fo/ipv6"> https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
&gt;<br>
</p>

--001a114374929001c2053298ba32--


From nobody Wed May 11 19:57:37 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 B37F912D172 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 19:57:35 -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 QT0oNjE3w_19 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 19:57:32 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 1221212D0B7 for <ipv6@ietf.org>; Wed, 11 May 2016 19:57:30 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id 206so25479425pfu.0 for <ipv6@ietf.org>; Wed, 11 May 2016 19:57:30 -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=ltBmIuQ3NV5Vs3DpXctVM+unkOs+K1CsASJ47Wr1gzw=; b=GQNLp0MoKqHhHSmBH9Nrlnkd2yLMdcXw4hnMn1LLoQB9V7nXf7YtW80r10ERGx0i4n gE/LhR/l7n4FKl4Y/bR1MQSIajxjxkDQ6r2p2pOgepu5WWyexfxUtlMuJAmE8oDCOkTr tKITjYnSVlVL6JDbW9lrBnq8BY3ZaGhKW7c+ocUOYJFHVCVTYFhLQNNb0ejQaox1DsUP Osz5dXlhYbuVDsm9lUlZ+pNlQ8SrxctjHkQQkDNtCotfmaUt00J/PC4zVAw7LIfBMw1n fzMGMDfiv8qoB6z23dgKFkhrgsZWc5BAwgshpKD86HnOO63dTIa9sIJSg70BXxS9UEZ5 a5MA==
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=ltBmIuQ3NV5Vs3DpXctVM+unkOs+K1CsASJ47Wr1gzw=; b=F1joWNzw/l6OR8CGcMi8rTLaLyewE2ES1rpt6HBt766fC+f/Sy+F6tn+rDQ9Cz8BWx EivZzjtR3htzNn94k5pfqfunH4VhqNY3M2TFYB6DlPPPUZUqvTxLRyEXSTGVZI2Bx2YE VmgFsYyjQ5P5kpe27R2CkfAc2DJwQBt27YietlO7rfWY2PsCHqtBXMvBj5lyzCBuboVV UnAZ0mNt+FSwSRsmqsjCQB5Ktf939ynMa/K5Vej81cl0MPUDjOnlvEOiv4MjnaWtNx88 6fjPNdblLKxb2BE1LpXQjZKTMGL0Rhp8vL39/+EEKrg12vAG5UXt6siWorpp+AH7hT0R bQGQ==
X-Gm-Message-State: AOPr4FXF+K91Ef6dMqqChcFpHdIDRGU8eSWFcStgJyMcoSPfla6X6hu6gPfRGihWMW9ndw==
X-Received: by 10.98.85.194 with SMTP id j185mr10118930pfb.68.1463021849676; Wed, 11 May 2016 19:57:29 -0700 (PDT)
Received: from ?IPv6:2406:e007:5004:1:28cc:dc4c:9703:6781? ([2406:e007:5004:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id n190sm15409083pfn.23.2016.05.11.19.57.25 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2016 19:57:27 -0700 (PDT)
Subject: Re: Adding headers and adding options to headers
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com>
Date: Thu, 12 May 2016 14:57:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <14024.1463003151@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wVkr9RZAsMngflz7xsLdautp2hw>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 02:57:36 -0000

On 12/05/2016 09:45, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> do you know of any interoperability problems with the current RFC2460?
>     >> that has to be the driving issue in deciding this.
> 
>     > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     > as "strongly recommended" so that is normative.
> 
> Again: I claim PMTUD is already broken and unfixable.
> (and should be replaced by PLMTUD, which should be turned on by default)

But that's beside the point of what we should say in 2460bis, which is
supposed to be a consolidation of 2460 and nothing more.

[Agreed - there's more to be done on this topic, but it's a separate
issue from 2460bis.]

   Brian

> 
> What else does inserting headers break that isn't related to PMTU ICMPs?
> 
> (I'm not in favour of inserting headers.  I am in favour of having rational
> and evidence based reasons in our specifications, or they will get ignored).
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 


From nobody Wed May 11 20:19:08 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 8DD9712D7BA for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 20:19:07 -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 jJkg0HIquYjo for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 20:19:06 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 D408612D0EA for <ipv6@ietf.org>; Wed, 11 May 2016 20:19:05 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id o66so69413675ywc.3 for <ipv6@ietf.org>; Wed, 11 May 2016 20:19:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:date:cc:message-id:references:to;  bh=6bGsB/ok51MbOBWiJBcRh+o3IuGbGFQdn9iOFKrdfFY=; b=S0PtQsnbj3IIX1TwcZP5aTvfwNoE7NAtFDd5uPNXaeX0JnctAdXb+tE/m5OpwRH1Mc XqpHGbLu88n7Lx7Ge3RmXz72c/M9qeQwqK4527xuJq2Ali+B+1gRNMNi86On5wTnlIxE bonhhY080tTQ5yZDTZWnC3f55BdHZgT8lpD4MQAHPdFbDyFQh3700dJVJwfn8Pcyx5OZ 6NgP7YUBPn4qmgNRsa1BwyDNXQodhrZTUBkqbvF6gKzwciGVHwrznXukAN/uS6FkHsgJ /SVWNqqHZbsHo+kb1yGWvXqdz9MXeSiJYPKz7aosVD9vWEBcT8rHrExLbXlguDmubgGR A2ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:date:cc:message-id :references:to; bh=6bGsB/ok51MbOBWiJBcRh+o3IuGbGFQdn9iOFKrdfFY=; b=CX74jk7MpzvPS+9nJymgPp4TSp5FyqtBQEDA+LQrAf2TjQjy0cNefl2Q/mqUKJIOga VEkFwEm9jMsUQ61MeoWwiBUG+WQovgxobDe2P/yaz6+Rgc+0zZtkCadD7fAK/Brqzm2b TuKG6u1wAR5cuc7VBeOk9hwfeVSYldc7WayDYxGXsgIyZcrw9+j9JM0U7ATHlN+2cbnR 01LVtTg7KddYSQUnfSPHxMcYqSLbcYzuHaw1RPnG1l9mMKJC0fY2URY+6tXklM93/JOo YjGnInMfF7uqQnDqb6gYohDo0D9I8zuhVCBpN2fa5uBz9vp5DAlhi592jySGHQoHdNX4 dc0w==
X-Gm-Message-State: AOPr4FWRJV1mvhX/Lowe5nimkkOnqIbULRxeVUhL44p5YxOcoWpQ9z2GN6hEsxRlwZ7CEA==
X-Received: by 10.129.3.17 with SMTP id 17mr3899102ywd.288.1463023145139; Wed, 11 May 2016 20:19:05 -0700 (PDT)
Received: from ?IPv6:2601:647:4d00:abf0:7499:58ea:3946:5865? ([2601:647:4d00:abf0:7499:58ea:3946:5865]) by smtp.gmail.com with ESMTPSA id i188sm6189132ywc.19.2016.05.11.20.19.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 11 May 2016 20:19:04 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_77EE1A49-5D58-4D5E-A622-9467DC06FE78"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
Date: Wed, 11 May 2016 20:19:01 -0700
Message-Id: <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cLFiJGRlSFRvuslm7sEd9LGlGnw>
Cc: 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: Thu, 12 May 2016 03:19:07 -0000

--Apple-Mail=_77EE1A49-5D58-4D5E-A622-9467DC06FE78
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This message starts a two week 6MAN Working Group Last Call on =
advancing:

       Title           : Recommendation on Stable IPv6 Interface =
Identifiers
       Authors         : Fernando Gont
                         Alissa Cooper
                         Dave Thaler
                         Will Liu
	Filename        : draft-ietf-6man-default-iids-11.txt
	Pages           : 23
	Date            : 2016-04-27

        https://tools.ietf.org/html/draft-ietf-6man-default-iids-11

as a Proposed Standard.  Substantive comments and statements of support =
for publishing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 25 May 2016.

We also need two people to volunteer to do a detailed reviews, and a =
volunteer to be the document Shepard.

Thanks,

Bob & Ole




--Apple-Mail=_77EE1A49-5D58-4D5E-A622-9467DC06FE78
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

iQEcBAEBCgAGBQJXM/YlAAoJEK7rdBF357uonV4IAIDNcV9861QAFDm8Tmt5KuL1
MVfq28DH+A4PMkxpWYIxSnAfZzdhFlvPEJ7T+eLjS4a/1NwNaZDv42s38SOd51do
v/4RuJHWaDyjmOy4vUpDPzizbLgKKnPC18LFdqLBnKMFfpa7Ii3WyHi1Ri6Tooor
//2HI75F6DfzSb7ThUCVyUnQPO/h/smtBdbCNzAv/eRhnafQ1pZM69SusGwWW9eY
BAv4o021CFOG1Ks6O7DIChNftQRiIEsFnuioep1pXViiEOmQzjp6uyytAz8TsBAV
NuSq6bGCIr3FQVCKzoa/b/cnI6XwYJ/+acskHU7rjX/ts6nv3l8ROW0rvCKDfTM=
=XKgw
-----END PGP SIGNATURE-----

--Apple-Mail=_77EE1A49-5D58-4D5E-A622-9467DC06FE78--


From nobody Wed May 11 23:55:48 2016
Return-Path: <alexandre.petrescu@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 7551512D879 for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 23:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 Z8K1jcxog2QR for <ipv6@ietfa.amsl.com>; Wed, 11 May 2016 23:55:43 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74A0C12D782 for <ipv6@ietf.org>; Wed, 11 May 2016 23:55:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4C6tWnU031083; Thu, 12 May 2016 08:55:32 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E914B20512A; Thu, 12 May 2016 08:57:32 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D2D172046DC; Thu, 12 May 2016 08:57:32 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4C6tWbw031089; Thu, 12 May 2016 08:55:32 +0200
Subject: Re: Adding headers and adding options to headers
To: Michael Richardson <mcr+ietf@sandelman.ca>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d763d0a7-204d-46f1-022c-c6ad23b359c0@gmail.com>
Date: Thu, 12 May 2016 08:55:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <14024.1463003151@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WmHCPeo46MvmhGEKkctGad4nLjU>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 06:55:46 -0000

Le 11/05/2016 à 23:45, Michael Richardson a écrit :
>
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> do you know of any interoperability problems with the current RFC2460?
>     >> that has to be the driving issue in deciding this.
>
>     > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     > as "strongly recommended" so that is normative.
>
> Again: I claim PMTUD is already broken and unfixable.
> (and should be replaced by PLMTUD, which should be turned on by default)
>
> What else does inserting headers break that isn't related to PMTU ICMPs?

Maybe integrity values like ICMP CRC or AH ICV fields(?)

Alex

>
> (I'm not in favour of inserting headers.  I am in favour of having rational
> and evidence based reasons in our specifications, or they will get ignored).
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Thu May 12 00:05: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 387A712D782 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 00:05:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 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, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham 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 Uslv8L7OAQ02 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 00:05:47 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [65.50.211.142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C4B712D0AA for <ipv6@ietf.org>; Thu, 12 May 2016 00:05:47 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 6F25D9CC7C; Thu, 12 May 2016 00:05:46 -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=UInhhwDWWPKtES962aKi7XJU0QA=; b= aR/UxcGiqFCbIOD53tAiCcTUDw/VW3h/afnHbsYup05qZPKGygAEjYbCumRZ+nrH 14OvZHHm9vroPLXaM1teX64ZFfF1ppLejsuT7ztJ27Cysk9dITRVso4VvN/yuTNU KTIpjwgnOPAB+WXu4UW47g/RMCAZM4UjNbug5AzTb5E=
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=bMBRrLJHqJMRbuF3WDqsraHm90 CeI2DsjqvinRaFbK9I2k/AZMHukLR6vo+cxKvqLL+3Zg2imU6dMTCMJIiMm+AMyS h4gmtsTMGFhR2FILwBRqsUR7x7ThUArNmHhKbTqvHo/AKtSUeCWA/OJXG0Qfq0GW NUlaoC3HAzxGzg3j8=
Received: from h.hanazo.no (unknown [173.38.220.55]) (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 07AFF9CC51; Thu, 12 May 2016 00:05:46 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 037EE1652134; Thu, 12 May 2016 09:05:41 +0200 (CEST)
Subject: Re: Adding headers and adding options to headers
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6BB9D414-F987-492D-AE91-8079AF25AC1B"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
Date: Thu, 12 May 2016 09:05:36 +0200
Message-Id: <8CB2AF02-1114-48DF-8DC0-A9C0E073870C@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6Nppv5sh6Bf0XKnu6wze8MfSogs>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 07:05:49 -0000

--Apple-Mail=_6BB9D414-F987-492D-AE91-8079AF25AC1B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

> Trying to answer your specific comments concisely:

Thank you.

[...]

>> do you know of any interoperability problems with the current =
RFC2460?
>> that has to be the driving issue in deciding this.
>=20
> Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
> as "strongly recommended" so that is normative.

Yes, that would be a valid argument if we were discussing how to design =
header injection.
Describing header injection in RFC2460bis is not on the table.
My argument is about what we put in 2460bis.
I believe no interoperability issue has been shown in RFC2460. Do you =
concur with that?

(Future specifications can of course create as many interoperability =
issues they like, not much we can or should do about that in 2460).

>> with regards to making prohibitions on future work in current =
protocol specifications, can you cite any example of the IETF being =
successful with that? :-)
>>=20
>> RFC2460 already has this prohibition by the way:
>>=20
>>   With one exception, extension headers are not examined or processed
>>   by any node along a packet's delivery path, until the packet =
reaches
>>   the node (or each of the set of nodes, in the case of multicast)
>>   identified in the Destination Address field of the IPv6 header.
>>=20
>> I'm afraid I don't see the point in changing RFC2460 here.
>=20
> The word "processed" is the problem here - it is ambiguous. That is =
the
> spcific reason for adding "modified or inserted".

I don't think this text is ambiguous at all.
Every network on the planet seems to violate it though, which of course =
is a much larger problem than the one we're talking about here.

To summarise my view:
 - There has not been shown any interoperability issues caused by the =
extension header text in 2460
 - Adding a general prohibitions to avoid something we dislike happening =
in the future, does a) not belong in 2460, b) is not testable c) is  =
unlikely to have the desired effect

Best regards,
Ole

--Apple-Mail=_6BB9D414-F987-492D-AE91-8079AF25AC1B
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

iQEcBAEBCgAGBQJXNCtFAAoJED4aXnjSQuKWAagH/RhRUKb7hw/GqsaCnbXjCN5/
nGG/sfY/W+f26Hjb4Z9ems/EWcngYRunivCCEwDmtoKzTUBCUudoQKPPjHZh2a0L
KHGU8lq9tu3YV+QT63z/++gSvaeb5yYSxVEOIZp+/gsAFyqiKKrV/JCQul0l0oa8
qqYptXYg0ZcBQ6+f2m5nrZdKHKcIA4O8nosLSQh6RnKKxJ5d7/36zJaLDWQMp+av
kP1TheMrEj8WU6Br5mZf/P7ADK1yKmwAC5Q9kyU00hJcOyxW+jYqwccUTGK+NMhF
HWTCQDErD+or+XBdlmRruJQFWUWEyR9v+rkN4fuHpUB59O4UnVr28MKJNspsZLc=
=UzgE
-----END PGP SIGNATURE-----

--Apple-Mail=_6BB9D414-F987-492D-AE91-8079AF25AC1B--


From nobody Thu May 12 01:03:26 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 388EF12B059 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 01:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 tDm_dn7g1YKE for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 01:03:22 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::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 58B1112B02D for <ipv6@ietf.org>; Thu, 12 May 2016 01:03:22 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id f66so88025669vkh.2 for <ipv6@ietf.org>; Thu, 12 May 2016 01:03:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=95p9zz1yCK/ba9oHqGidoKYfpoSI3UAH12Be1YvY8PA=; b=rJoMnM3DZec9c/1+NEWxlI67rJAqor8yF1HkQmEJ15u8eq5AH79H0YNK+C06E7PBui cZSCEPIMo4vefJDGm/hI8XAp1JYrq5ON6hebaS7VXAXxinDP3AATvXaQLeKZnHCn3a0Y YNgL69GDojYLAUdAc1IqPLXVLfDAiXDRI10iSHakZfNyARIjFTbkEVpnXsVJsT5EgFub EwmlW6Ia9955+pwNBmJh9fLNv7aOTXTR9qQVCzWqNKFKOxhxZVvtUyETqOwWDaZd4sDt Zfupsr6VgJAY2EaP30IOdx6l4zk8FpeOqCT/tg7JCGFhAfOHYswIG0+NfqeE/qkQGpAr ZYug==
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:date :message-id:subject:from:to:cc; bh=95p9zz1yCK/ba9oHqGidoKYfpoSI3UAH12Be1YvY8PA=; b=lRQwG6+iVd7ouHHy8vh81xk6bw33LePN3ysewdGsne4PT0meCPv07QI3Z4PLt995hG U22hlUFbXRavguJy7p6kP6KyDEm1OnexKhB3LjzMdX4qdU4/iThLdqsBQ9SsqQYv+Vy4 P466emqRUxMCxK+uYA/1/BuG76YGOovWqpVcYAlOSYRCoxNre24EnzafnInapIu5WN+z sVdDW6YtblgLYh+2P/BjGkrmKW2Yl0myy7Ee+U9JXjqW8qTBNUwvXRiZpKCQTW/PsfMh L6CUdcQoX9mT4gtjDe+tJkNzIZG3paye8f5sidstu3GpPpeyU1D81xrGh6MF/ruvMaPu ks5g==
X-Gm-Message-State: AOPr4FXR/ioo7JRstxPzEMPvYrLNhIA5mdUAoqDCbdEwG8XHK/8lc98J1iJBRZmcJdsYQgmDwdBM24eJ4wNgHA==
MIME-Version: 1.0
X-Received: by 10.31.72.193 with SMTP id v184mr3974885vka.29.1463040201483; Thu, 12 May 2016 01:03:21 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Thu, 12 May 2016 01:03:21 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Thu, 12 May 2016 01:03:21 -0700 (PDT)
In-Reply-To: <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
Date: Thu, 12 May 2016 18:03:21 +1000
Message-ID: <CAO42Z2xRik5hPUGCKsmAwpMBUrXZE8SXCXTNSLp7RvznRp4_DA@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Mark Smith <markzzzsmith@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=001a114dba90806fb70532a09768
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Mmjnl-kLOCxf4NKmCkgfDep38oY>
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: Thu, 12 May 2016 08:03:25 -0000

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

Hi,

On 12 May 2016 1:19 PM, "Bob Hinden" <bob.hinden@gmail.com> wrote:
>
> This message starts a two week 6MAN Working Group Last Call on advancing:
>
>        Title           : Recommendation on Stable IPv6 Interface
Identifiers
>        Authors         : Fernando Gont
>                          Alissa Cooper
>                          Dave Thaler
>                          Will Liu
>         Filename        : draft-ietf-6man-default-iids-11.txt
>         Pages           : 23
>         Date            : 2016-04-27
>
>         https://tools.ietf.org/html/draft-ietf-6man-default-iids-11
>
> as a Proposed Standard.  Substantive comments and statements of support
for publishing this document should be directed to the mailing list.
Editorial suggestions can be sent to the authors.  This last call will end
on 25 May 2016.
>

I support publication.

> We also need two people to volunteer to do a detailed reviews, and a
volunteer to be the document Shepard.
>

I'm willing to be a detailed reviewer too.

Regards,
Mark.

> Thanks,
>
> Bob & Ole
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr">Hi,<br></p>
<p dir=3D"ltr">On 12 May 2016 1:19 PM, &quot;Bob Hinden&quot; &lt;<a href=
=3D"mailto:bob.hinden@gmail.com">bob.hinden@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; This message starts a two week 6MAN Working Group Last Call on advanci=
ng:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: Recommendation on Stable IPv6 Interface Identifiers<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: =
Fernando Gont<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=A0Alissa Cooper<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=A0Dave Thaler<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=A0Will Liu<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draf=
t-ietf-6man-default-iids-11.txt<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: 23<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2016-04-27<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://tools.ietf.org/html/dra=
ft-ietf-6man-default-iids-11">https://tools.ietf.org/html/draft-ietf-6man-d=
efault-iids-11</a><br>
&gt;<br>
&gt; as a Proposed Standard.=C2=A0 Substantive comments and statements of s=
upport for publishing this document should be directed to the mailing list.=
=C2=A0 Editorial suggestions can be sent to the authors.=C2=A0 This last ca=
ll will end on 25 May 2016.<br>
&gt;</p>
<p dir=3D"ltr">I support publication.</p>
<p dir=3D"ltr">&gt; We also need two people to volunteer to do a detailed r=
eviews, and a volunteer to be the document Shepard.<br>
&gt;</p>
<p dir=3D"ltr">I&#39;m willing to be a detailed reviewer too.</p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; Thanks,<br>
&gt;<br>
&gt; Bob &amp; Ole<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>
&gt;<br>
</p>

--001a114dba90806fb70532a09768--


From nobody Thu May 12 02:09:02 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 BB25312D139 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 02:09:00 -0700 (PDT)
X-Quarantine-ID: <1LAhcqoYFnvN>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 1LAhcqoYFnvN for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 02:08:58 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 14F2712D096 for <ipv6@ietf.org>; Thu, 12 May 2016 02:08:56 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1b0mc2-0000ESC; Thu, 12 May 2016 11:08:54 +0200
Message-Id: <m1b0mc2-0000ESC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Adding headers and adding options to headers 
From: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> 
In-reply-to: Your message of "Wed, 11 May 2016 17:45:51 -0400 ." <14024.1463003151@obiwan.sandelman.ca> 
Date: Thu, 12 May 2016 11:08:52 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lgzCMQyI4Cy24NVIzsgQq7fF2n8>
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, 12 May 2016 09:09:01 -0000

>Again: I claim PMTUD is already broken and unfixable.
>(and should be replaced by PLMTUD, which should be turned on by default)
>
>What else does inserting headers break that isn't related to PMTU ICMPs?
>
>(I'm not in favour of inserting headers.  I am in favour of having rational
>and evidence based reasons in our specifications, or they will get ignored).

By and large PMTUD works. It doesn't always work, which is an issue. But
it largely works.

That said in my opinion all hosts MUST do some form of PMTU blackhole
detection. Unfortunately we can't write that down.

Also unfortunately, very few stacks seem to ship with PLMTUD enabled by
default. So any new feature in IPv6 that break PMTUD more is going to put
IPv6 at a significant disadvantage compared to IPv4.

I think we should focus on PMTUD with a fallback to PLMTUD. As far as I
know there are no major stack running with just PLMTUD and we have
no idea how it would work in practice. 



From nobody Thu May 12 11:25:59 2016
Return-Path: <trac+6man@trac.tools.ietf.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 04A8712D538; Thu, 12 May 2016 11:25:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 3jaLGGxaVWaW; Thu, 12 May 2016 11:25:56 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 9826B12D0CD; Thu, 12 May 2016 11:25:56 -0700 (PDT)
Received: from localhost ([::1]:54061 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1b0vJ3-0001RR-D0; Thu, 12 May 2016 11:25:53 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org
X-Trac-Project: 6man
Date: Thu, 12 May 2016 18:25:53 -0000
X-URL: https://tools.ietf.org/wg/6man/
Subject: Re: [6man] #5 (draft-thubert-6man-flow-label-for-rpl): draft-thubert-6man-flow-label-for-rpl-03 Evidence about energy consumption
X-Trac-Ticket-URL: https://tools.ietf.org/wg/6man/trac/ticket/5#comment:2
Message-ID: <083.fe55df1fad9ab941136b0fb2c6542e30@trac.tools.ietf.org>
References: <068.671f8aa582afbd91ce328299dcfe05a4@trac.tools.ietf.org>
X-Trac-Ticket-ID: 5
In-Reply-To: <068.671f8aa582afbd91ce328299dcfe05a4@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org, roll@ietf.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_jom36IBqQfv4DnkByoIQaGyZiU>
Cc: roll@ietf.org, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 6man@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: Thu, 12 May 2016 18:25:58 -0000

#5: draft-thubert-6man-flow-label-for-rpl-03 Evidence about energy consumption

Changes (by otroan@employees.org):

 * status:  new => closed
 * resolution:   => wontfix


-- 
-------------------------------------------------+-------------------------
 Reporter:  mariainesrobles@gmail.com            |       Owner:
     Type:  defect                               |  pthubert@cisco.com
 Priority:  major                                |      Status:  closed
Component:  draft-thubert-6man-flow-label-for-   |   Milestone:
  rpl                                            |     Version:
 Severity:  In WG Last Call                      |  Resolution:  wontfix
 Keywords:                                       |
-------------------------------------------------+-------------------------

Ticket URL: <https://tools.ietf.org/wg/6man/trac/ticket/5#comment:2>
6man <https://tools.ietf.org/wg/6man/>


From nobody Thu May 12 11:26:40 2016
Return-Path: <trac+6man@trac.tools.ietf.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 C070212D6F8; Thu, 12 May 2016 11:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 C75ekjSD75El; Thu, 12 May 2016 11:26:35 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 48B0D12D0F4; Thu, 12 May 2016 11:26:34 -0700 (PDT)
Received: from localhost ([::1]:54124 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1b0vJh-00033N-4Z; Thu, 12 May 2016 11:26:33 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org
X-Trac-Project: 6man
Date: Thu, 12 May 2016 18:26:33 -0000
X-URL: https://tools.ietf.org/wg/6man/
Subject: Re: [6man] #6 (draft-thubert-6man-flow-label-for-rpl): draft-thubert-6man-flow-label-for-rpl-03 Updates: 6437 (if approved) - add section with explanation
X-Trac-Ticket-URL: https://tools.ietf.org/wg/6man/trac/ticket/6#comment:3
Message-ID: <083.55569b714435894d84343c022c8e07a8@trac.tools.ietf.org>
References: <068.3c73dacb1b9363819387808aa499fc8b@trac.tools.ietf.org>
X-Trac-Ticket-ID: 6
In-Reply-To: <068.3c73dacb1b9363819387808aa499fc8b@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org, roll@ietf.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Dh1ZYDiaEIegkuDBeBJ5nnlnwF8>
Cc: roll@ietf.org, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 6man@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: Thu, 12 May 2016 18:26:37 -0000

#6: draft-thubert-6man-flow-label-for-rpl-03  Updates: 6437 (if approved)  -
add section with explanation

Changes (by otroan@employees.org):

 * status:  new => closed
 * resolution:   => wontfix


-- 
-------------------------------------------------+-------------------------
 Reporter:  mariainesrobles@gmail.com            |       Owner:
     Type:  defect                               |  pthubert@cisco.com
 Priority:  major                                |      Status:  closed
Component:  draft-thubert-6man-flow-label-for-   |   Milestone:
  rpl                                            |     Version:
 Severity:  In WG Last Call                      |  Resolution:  wontfix
 Keywords:                                       |
-------------------------------------------------+-------------------------

Ticket URL: <https://tools.ietf.org/wg/6man/trac/ticket/6#comment:3>
6man <https://tools.ietf.org/wg/6man/>


From nobody Thu May 12 11:27:05 2016
Return-Path: <trac+6man@trac.tools.ietf.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 155E712D0F4; Thu, 12 May 2016 11:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 e3Ec0xSecLA2; Thu, 12 May 2016 11:27:00 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 2795C12D538; Thu, 12 May 2016 11:26:59 -0700 (PDT)
Received: from localhost ([::1]:54154 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1b0vK6-0004Jb-Hx; Thu, 12 May 2016 11:26:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org
X-Trac-Project: 6man
Date: Thu, 12 May 2016 18:26:58 -0000
X-URL: https://tools.ietf.org/wg/6man/
Subject: Re: [6man] #7 (draft-thubert-6man-flow-label-for-rpl): draft-thubert-6man-flow-label-for-rpl-03 Relation with RFC 6294
X-Trac-Ticket-URL: https://tools.ietf.org/wg/6man/trac/ticket/7#comment:2
Message-ID: <083.aa1e3373e7d67f531b2e6cda3ed0cceb@trac.tools.ietf.org>
References: <068.c7869b2e34ac214af78bf24f1219b6f8@trac.tools.ietf.org>
X-Trac-Ticket-ID: 7
In-Reply-To: <068.c7869b2e34ac214af78bf24f1219b6f8@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org, roll@ietf.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HAyyNobH3D9NO3LfNFGJ5W0SBrA>
Cc: roll@ietf.org, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 6man@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: Thu, 12 May 2016 18:27:02 -0000

#7: draft-thubert-6man-flow-label-for-rpl-03 Relation with RFC 6294

Changes (by otroan@employees.org):

 * status:  new => closed
 * resolution:   => wontfix


-- 
-------------------------------------------------+-------------------------
 Reporter:  mariainesrobles@gmail.com            |       Owner:
     Type:  defect                               |  pthubert@cisco.com
 Priority:  major                                |      Status:  closed
Component:  draft-thubert-6man-flow-label-for-   |   Milestone:
  rpl                                            |     Version:
 Severity:  In WG Last Call                      |  Resolution:  wontfix
 Keywords:                                       |
-------------------------------------------------+-------------------------

Ticket URL: <https://tools.ietf.org/wg/6man/trac/ticket/7#comment:2>
6man <https://tools.ietf.org/wg/6man/>


From nobody Thu May 12 11:27:26 2016
Return-Path: <trac+6man@trac.tools.ietf.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 8E41212D814; Thu, 12 May 2016 11:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 dP3Nx-be3bdL; Thu, 12 May 2016 11:27:23 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 34F3412D701; Thu, 12 May 2016 11:27:20 -0700 (PDT)
Received: from localhost ([::1]:54186 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1b0vKR-00052Y-Aa; Thu, 12 May 2016 11:27:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org
X-Trac-Project: 6man
Date: Thu, 12 May 2016 18:27:19 -0000
X-URL: https://tools.ietf.org/wg/6man/
Subject: Re: [6man] #8 (draft-thubert-6man-flow-label-for-rpl): draft-thubert-6man-flow-label-for-rpl-03 relation with draft-bormann-6lo-rpl-mesh-00
X-Trac-Ticket-URL: https://tools.ietf.org/wg/6man/trac/ticket/8#comment:2
Message-ID: <083.e51efa13cfbd74a0abd112fb718d17da@trac.tools.ietf.org>
References: <068.d868eca75329b76a18c979179b2bface@trac.tools.ietf.org>
X-Trac-Ticket-ID: 8
In-Reply-To: <068.d868eca75329b76a18c979179b2bface@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: pthubert@cisco.com, mariainesrobles@gmail.com, otroan@employees.org, roll@ietf.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SNueN2aYr5MfimSwJsYijLSR15E>
Cc: roll@ietf.org, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 6man@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: Thu, 12 May 2016 18:27:24 -0000

#8: draft-thubert-6man-flow-label-for-rpl-03 relation with draft-bormann-6lo-
rpl-mesh-00

Changes (by otroan@employees.org):

 * status:  new => closed
 * resolution:   => wontfix


-- 
-------------------------------------------------+-------------------------
 Reporter:  mariainesrobles@gmail.com            |       Owner:
     Type:  defect                               |  pthubert@cisco.com
 Priority:  major                                |      Status:  closed
Component:  draft-thubert-6man-flow-label-for-   |   Milestone:
  rpl                                            |     Version:
 Severity:  In WG Last Call                      |  Resolution:  wontfix
 Keywords:                                       |
-------------------------------------------------+-------------------------

Ticket URL: <https://tools.ietf.org/wg/6man/trac/ticket/8#comment:2>
6man <https://tools.ietf.org/wg/6man/>


From nobody Thu May 12 11:39:52 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 058C112D538 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 11:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, 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 GNH4pM1OW54m for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 11:39:49 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001: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 61F2812D965 for <ipv6@ietf.org>; Thu, 12 May 2016 11:39:37 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id 190so106475252iow.1 for <ipv6@ietf.org>; Thu, 12 May 2016 11:39:37 -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:date:message-id:subject :from:to:cc; bh=x/M3HQgc/43ecLUyz0Lq1sClIL4F9EgF2pqFGRJcuDQ=; b=p88zRjGQdO85aTdVesGhhblc8+2oai64Oz3GWvb4swcu0c0TaJQ5oO9jtahmUybgDB V8aVZeP37drRlBq0MYSFIWJ/zcCIvNmy3Lx8L3dvhbo2iNadNRqj1guiL6pIJ8FJCpAV IkMfAikwCDPlvTQrU3UwBJA7Ym5sacGvshR6vbyqs1AerXF6fWkhQ7OxEU7yAeuOJ31u xnQ7g83Lurq62WWeXjYtYVw/F8Zbvg0E77nP4SghXCdi7RYTQt9605Bbk64rR1OnOoLB Y8vvhr86ng3GIpA5hNDK88sv3NQCfQ7jqADsgCJgzdmCGNsfy12SWMzd6IFDL3rDwR9F pm0Q==
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:date :message-id:subject:from:to:cc; bh=x/M3HQgc/43ecLUyz0Lq1sClIL4F9EgF2pqFGRJcuDQ=; b=ml/1HDrFDUdY7WipBxVCJ8765eja6GuI6+fMPl0Ileb4TxkiYhM/DY1Diwh2qNCszC Eih1oIU+TC/ZhVz63hysH+qpBh/xzOO84iDE+7QTlUzu+D553H6IkyiAXpHwVRhHazcL G0iso21YnPdJYbudiHi4p1q3/CufKzyuBIDeGR0uZS2knJefwNdqdLkRBGcH5fk5XY72 8FaT8cBS+QpjuA3xKjL8R4kVUmda+wnACPBouWi2BBe52EURQjHf9vsQxXkvfdDm2VBs 5c+uMSqMDIVxHREL95z+f74axx3tYThIyprynygnNKGcLDCuUvpcGIbnmPL3qpGuafQp VrMA==
X-Gm-Message-State: AOPr4FW50jfG7sCVl6gRotB+mL9TwVip046FP9C98qGt6CNP1LUfy+0E4iRcsj7F+eduotHmqpEp/pGmss4ACQ==
MIME-Version: 1.0
X-Received: by 10.107.58.213 with SMTP id h204mr9362761ioa.172.1463078376409;  Thu, 12 May 2016 11:39:36 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Thu, 12 May 2016 11:39:36 -0700 (PDT)
In-Reply-To: <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
Date: Thu, 12 May 2016 11:39:36 -0700
X-Google-Sender-Auth: 4lEgdpTjBzXolLLHzM9ziJ067Ec
Message-ID: <CAJE_bqfkOvsuOGtP=rcPiMama9Gj2EoigAAKkbvy7o_uNDzGmw@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1XPd8TPCLqRoQvGpqi6BXpOWrC8>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 18:39:51 -0000

At Wed, 11 May 2016 20:38:54 +0200,
otroan@employees.org wrote:

> > It could be understandable, though I'm not convinced about it yet,
> > that someone who doesn't like the original intent (because it would
> > break some existing product of them?) wants to overturn it.  But in
> > any case it doesn't make sense to me at all to just leave the
> > ambiguity.  It will just result in more confusion and more possibility
> > of interoperability problems in the mean time.
>
> do you know of any interoperability problems with the current RFC2460?
> that has to be the driving issue in deciding this.

I guess this seems to be a fundamental difference on the view between
us - I don't think this has to be the driving issue on this at all.
IMO the onus is on those who want to keep the ambiguity by proving it
is actually safe for any combination of assumption mismatch: a sending
node believes no intermediate node inserts or deletes an EH while an
intermediate node believes it's allowed for them.

Nevertheless I can easily come up with a few such problems:

- As already pointed out, PMTUD
- As a corollary of this, some connection-less applications that
  assume they can safely send packets up to 1280 bytes without any
  drop due to a 'packet too big' issue.  DNS servers work on this
  assumption.
- Authentication Header

I suspect these "evidences" won't matter anyway, though.  It's easy to
pooh-pooh those (or any other) examples as weak.  As long as we have
the fundamental difference on how to view this I mentioned above, I
guess no such example will convince you.  So I think we should
probably simply agree to disagree.

> with regards to making prohibitions on future work in current protocol specifications, can you cite any example of the IETF being successful with that? :-)

Maybe this is just a rhetorical question, and an answer isn't
expected, but if it's trying to suggest something like "determined
developers/operators do whatever they want no matter what the IETF
says", I don't deny that.  But I also believe what's stated in the RFC
still has some (pretty strong) power to discourage people to do "the
wrong thing".

I'd also note that I didn't intend to prohibit future work that can
change what's written in the current specification.  In the context of
this discussion, my understanding is that the ambiguity and confusion
are real as we can see it in RFC4782 and that it's not unreasonable to
expect it will actually cause interoperability problems, while the
discussion on changing the current spec would be quite controversial
and can take long time.  So I believe it does make very sense to
eliminate the ambiguity at this point.

> RFC2460 already has this prohibition by the way:
>
>    With one exception, extension headers are not examined or processed
>    by any node along a packet's delivery path, until the packet reaches
>    the node (or each of the set of nodes, in the case of multicast)
>    identified in the Destination Address field of the IPv6 header.
>
> I'm afraid I don't see the point in changing RFC2460 here.

On the other hand, I'm afraid I don't see what's wrong with clarifying
obvious ambiguity as log as we all agree that that's actually the
original intent (even if some of them don't like the intent).  It will
just make the doc a couple of paragraphs longer and would completely
eliminate the ambiguity.

But again, this is probably just another case of how our views on this
are so fundamentally different.

--
JINMEI, Tatuya


From nobody Thu May 12 11:40:10 2016
Return-Path: <trac+6man@trac.tools.ietf.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 C0B4C12D6FD for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 11:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 I5VUE74SLZFD for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 11:39:54 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 7753A12D093 for <6man@ietf.org>; Thu, 12 May 2016 11:31:12 -0700 (PDT)
Received: from localhost ([::1]:54518 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1b0vOC-0008Ql-A6; Thu, 12 May 2016 11:31:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.5
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.5, by Edgewall Software
To: otroan@employees.org
X-Trac-Project: 6man
Date: Thu, 12 May 2016 18:31:12 -0000
X-URL: https://tools.ietf.org/wg/6man/
Subject: [6man] #9 (rfc2460bis): Header injection issue
X-Trac-Ticket-URL: https://tools.ietf.org/wg/6man/trac/ticket/9
Message-ID: <063.46dedc0eea831fdd4d5e2fa4afbad641@trac.tools.ietf.org>
X-Trac-Ticket-ID: 9
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: otroan@employees.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SheleBdElUVNKdhu4Y7inNBHLQw>
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: 6man@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: Thu, 12 May 2016 18:40:08 -0000

#9: Header injection issue

 Determine if this added paragraph in rfc2460bis should be in or out:

    Extension headers must never be inserted by any node other than the
    source of the packet.  IP Encapsulation must be used to meet any
    requirement for inserting headers, for example, as defined in
    [RFC2473].

-- 
----------------------------------+-----------------
 Reporter:  otroan@employees.org  |      Owner:
     Type:  defect                |     Status:  new
 Priority:  major                 |  Milestone:
Component:  rfc2460bis            |    Version:
 Severity:  In WG Last Call       |   Keywords:
----------------------------------+-----------------

Ticket URL: <https://tools.ietf.org/wg/6man/trac/ticket/9>
6man <https://tools.ietf.org/wg/6man/>


From nobody Thu May 12 13:39: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 B50F112D0ED for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 13:39:07 -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, FREEMAIL_FROM=0.001, 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 tmkZ89gdTQ1S for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 13:39:05 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::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 AB12412B011 for <ipv6@ietf.org>; Thu, 12 May 2016 13:39:05 -0700 (PDT)
Received: by mail-pa0-x229.google.com with SMTP id iv1so32788952pac.2 for <ipv6@ietf.org>; Thu, 12 May 2016 13:39:05 -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=w+Fl/ou1GuBGDU5eL8HEQs51uveqkYRtUr2B4veXNHE=; b=oDPOxl8x6tw8TbJgxIYDM0fvqtvCCj3EKVjMk9Xy6EjGjUldAFI/Z5eAkHXGkfPPTi Jw2m2lmVq6EzaU9ZCwhTlSqrXN2hrD1l0GGaFEinjB3YuKRFxSJ/CTMXipR98MukoDyx NAT3OoL/r2COq0V7hZPrFcJzYRr9TwX4MgVsfukQhQJ2A5FsWre3uVjEyOcV7WTztLAq +evgjN938VtKfManBqY9LkBhSfker6187GGpY5JiPkIlNuKsu0Uwx44/HzyqFuOyTDBF Ae4CLgAC17L/zSQaO+V7Ic80lRA+0LSl9Y9ojOiaN0BNRJr9iPHrfT0fBEKW3lGIUPAW 0Yfw==
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=w+Fl/ou1GuBGDU5eL8HEQs51uveqkYRtUr2B4veXNHE=; b=XV8xyQzFrE7ORMrqmGSaHB5kcGhFdr+qGo2MnOku/zC6d/DgnFkTqTO5KY1w9VRfmG XYHBzhAeMBtckILqVDfi7is97TnsaZpoUMSpxHFQRgrqnOGazCOrOmFJ+bcs5WKW5qb4 A+etY/6/vf3vcDb/9UqRUKbjMW1mAawIYl/7G8rLatmyPjMFEzSOMyh6rfZu4on46PrN FDp8aYd7XrMUsu+zSr82O4M8fW5BUEyf+bfExXKza8+/Wwrff0vIJYEWmHfN9lOyL9Ws Kt/PHdptG+k6UQOdWMd3Mo58GEdXmlupgTMwme8fsX2T5fWSYb/vBzZklYXc5zKvKfqj KcWw==
X-Gm-Message-State: AOPr4FW/5N8gO4pn7WgVAFB69uyrmiSZi1p/pbK49Y9TAAhaDDpccYF9ogwVg0LGhoCkoA==
X-Received: by 10.66.63.104 with SMTP id f8mr16879457pas.109.1463085545225; Thu, 12 May 2016 13:39:05 -0700 (PDT)
Received: from ?IPv6:2406:e007:69e1:1:28cc:dc4c:9703:6781? ([2406:e007:69e1:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id bf4sm21977008pac.4.2016.05.12.13.39.01 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 13:39:03 -0700 (PDT)
Subject: Question to the chair [Adding headers and adding options to headers]
To: otroan@employees.org
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <8CB2AF02-1114-48DF-8DC0-A9C0E073870C@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <e1127577-0ae2-79b0-dc93-0ff01a324a15@gmail.com>
Date: Fri, 13 May 2016 08:39:28 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <8CB2AF02-1114-48DF-8DC0-A9C0E073870C@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/spzZACAnv4HVexP2TlX7KZN-5e4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 20:39:08 -0000

Ole,

I think that I and some others disagree with you, and of course
we are all entitled to our opinions. I doubt we'll hear any new
arguments now.

However, what is your WG Chair's view of the *WG consensus*? Do you think
the rough consensus is to include or exclude these words:

   Extension headers must never be inserted by any node other than the
   source of the packet.  One approach to meet a requirement to add
   extension headers is to use IP Encapsulation, for example, as defined
   in [RFC2473].

   Extension headers must never be deleted or changed in size by any
   node on the path the packet takes.

   The contents of an Extension header or Option in an Extension header
   may be modified if this is permitted by the definition of the
   Extension header or option.

Regards
   Brian

On 12/05/2016 19:05, otroan@employees.org wrote:
> Brian,
> 
>> Trying to answer your specific comments concisely:
> 
> Thank you.
> 
> [...]
> 
>>> do you know of any interoperability problems with the current RFC2460?
>>> that has to be the driving issue in deciding this.
>>
>> Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>> as "strongly recommended" so that is normative.
> 
> Yes, that would be a valid argument if we were discussing how to design header injection.
> Describing header injection in RFC2460bis is not on the table.
> My argument is about what we put in 2460bis.
> I believe no interoperability issue has been shown in RFC2460. Do you concur with that?
> 
> (Future specifications can of course create as many interoperability issues they like, not much we can or should do about that in 2460).
> 
>>> with regards to making prohibitions on future work in current protocol specifications, can you cite any example of the IETF being successful with that? :-)
>>>
>>> RFC2460 already has this prohibition by the way:
>>>
>>>   With one exception, extension headers are not examined or processed
>>>   by any node along a packet's delivery path, until the packet reaches
>>>   the node (or each of the set of nodes, in the case of multicast)
>>>   identified in the Destination Address field of the IPv6 header.
>>>
>>> I'm afraid I don't see the point in changing RFC2460 here.
>>
>> The word "processed" is the problem here - it is ambiguous. That is the
>> spcific reason for adding "modified or inserted".
> 
> I don't think this text is ambiguous at all.
> Every network on the planet seems to violate it though, which of course is a much larger problem than the one we're talking about here.
> 
> To summarise my view:
>  - There has not been shown any interoperability issues caused by the extension header text in 2460
>  - Adding a general prohibitions to avoid something we dislike happening in the future, does a) not belong in 2460, b) is not testable c) is  unlikely to have the desired effect
> 
> Best regards,
> Ole
> 


From nobody Thu May 12 13:43:05 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 7235112D159 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 13:43: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 MIxkLruD19LG for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 13:43:02 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 13E0A12D0ED for <ipv6@ietf.org>; Thu, 12 May 2016 13:43:02 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id xk12so33135328pac.0 for <ipv6@ietf.org>; Thu, 12 May 2016 13:43:02 -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=gZMOZYWwbeg0oBeFqveX69HOanJhonaUqbBl4Wt350k=; b=K4QSHsolucHl8nBVSiGsPfPBazJLZY/HOwKZRFbcTzXipB6sy7NAa6KPoOa4a2KjS2 aMLuAOacuiLSuJ1kY1pDyP1F6/k/JbftdHkfQGP5jYBt4mPhyFqRm34BSIFWDhDqHKC5 7YJ1xKl0BKYXHUO15XsH9PSh+XnMpXZI2MsKGeAV3AjUkli7LYof5kYbC47b+b0JvvNQ d52TEM9L2WSISGUejsnjKoBCZ9YRiqEBfm9UksBjTnzRer1HpvJ3jJg874K3uzbZMDYK g5C0hh/UyqqipuyFEe0z4vcOhMSOepp+jJOEpGg4hK8EYQBgx0pzEG+YOzL3NNaCkAph Dh5Q==
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=gZMOZYWwbeg0oBeFqveX69HOanJhonaUqbBl4Wt350k=; b=VkHmF4+Llom2ilM9woy0IMCr1m9YCBgRF2E5tfhfIWR6tcHstNgd3T1hlVCtu4eHvM INYZJF9JqQ/Cubvj/emDBjzoai/g8Cmckoi22xaPsUSsRUI1vN4hBez5UzH6cNIgESAR bVIMPQgopyeoLtdThORkXUmXCoPe4Wqjgga5L6uyVC9EuAnjOnY0TtAbeuwLwAN/nGt3 pUuqTsm1AIBHAixVE6rAR5OJ8o/NuNzkBQ3pTUIZup4FGoSMoLj5bgNIvuPEmabb2et+ nUnyV2x5qLnsTX4jKLzF59yjc0klTSMfnfxJachSoMBMi/+/YLhm1bFHB3bbC93esSJn 2Hfg==
X-Gm-Message-State: AOPr4FVDTvplZilE8J3Y9dA4iyRm2zxyYOe+9Fwa9zJoqcg6lvBtZsuX8+ySUrvFtsZvLA==
X-Received: by 10.67.13.144 with SMTP id ey16mr16923716pad.147.1463085781739;  Thu, 12 May 2016 13:43:01 -0700 (PDT)
Received: from ?IPv6:2406:e007:69e1:1:28cc:dc4c:9703:6781? ([2406:e007:69e1:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 12sm14659413pfb.26.2016.05.12.13.42.58 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 13:42:59 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com>
Date: Fri, 13 May 2016 08:43:26 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/YmNR352WtwwJBI3g-9tA8Xqd8w8>
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, 12 May 2016 20:43:03 -0000

With the clarifying references to RFC4941, I think this document is
in good shape and ready to be advanced.

    Brian


From nobody Thu May 12 15:25:00 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 6B37E12D1A8 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 15:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, 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 Ugke5_JCl8zA for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 15:24:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA4B12B03C for <ipv6@ietf.org>; Thu, 12 May 2016 15:24:57 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 030A7200A5; Thu, 12 May 2016 18:30:34 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D3E7F638BD; Thu, 12 May 2016 18:24:55 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adding headers and adding options to headers
In-Reply-To: <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 12 May 2016 18:24:55 -0400
Message-ID: <12928.1463091895@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/euAFihSzYjuIcWk2j-V68jg6g7Y>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, =?us-ascii?Q?=3D=3FUTF-8=3FB=3F56We5piO6YGU5ZOJ=3F=3D?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Thu, 12 May 2016 22:24:59 -0000

--=-=-=
Content-Type: text/plain


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > On 12/05/2016 09:45, Michael Richardson wrote:
    >>
    >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> >> do you know of any interoperability problems with the current RFC2460?
    >> >> that has to be the driving issue in deciding this.
    >>
    >> > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
    >> > as "strongly recommended" so that is normative.
    >>
    >> Again: I claim PMTUD is already broken and unfixable.
    >> (and should be replaced by PLMTUD, which should be turned on by default)

    > But that's beside the point of what we should say in 2460bis, which is
    > supposed to be a consolidation of 2460 and nothing more.

I don't agree.
As part of the process towards Internet Standard, we are supposed to rip out
and/or clarify things which didn't work as expected.

I claim that PMTUD is such a thing, and it seems to be the key reason to
avoid header insertion/deletion.  (I hear Mark Smith's comments loudly; and I
have war wounds from debugging MPLS and all manner of 802.3 networks where
intermediate boxes do stuff mysteriously to packets).

{I would prefer that header insertion/deletion was impossible because 90% of
traffic had AH on it.... Hey, a person can dream, can't they?}


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVzUCsYCLcPvd0N1lAQI6UAgAsKPEOIzh7u7PmYgMfZLKUFWjDY67tDeM
4w/int4TyM+c8/9VOFN9GNwscC0GiNjqADtnxmvFB04hjg1zEH5zFBROlCnW9xsz
8HH/+7D7eZkab2UQaseE4DK7nuAC1X6e+jhKRu19iTeUUQVlNhSN2P8MRlxGGNnb
KuSV/elQJKR5EMtd6k//79czjHqWjLECQnq0w59uHb8TXmW0NyYW/VNPhdBXov7x
FJC4Kqj8Nrhsl/cIwK+mUT5Fiwl9uKSLnhQy+DRYBOwS7Dj55JLKzONM2JLGWdSo
xXez1Ca4qFodBg7MrJUNkf3ob8s8AEgCv9T+gUo4WZhXXSJ6QWV6iQ==
=DFWn
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu May 12 15:31:38 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 E3BC512D0D9 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 15:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, 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 QbQyClNGmAsK for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 15:31:35 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 411CB12B03C for <ipv6@ietf.org>; Thu, 12 May 2016 15:31:35 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 88F5C200A5; Thu, 12 May 2016 18:37:12 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 66172638BD; Thu, 12 May 2016 18:31:34 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Subject: Re: Adding headers and adding options to headers
In-Reply-To: <m1b0mc2-0000ESC@stereo.hq.phicoh.net>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <m1b0mc2-0000ESC@stereo.hq.phicoh.net>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 12 May 2016 18:31:34 -0400
Message-ID: <14356.1463092294@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/IpgyY0idK3lCUixepfGIhq2q8Rc>
Cc: 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, 12 May 2016 22:31:37 -0000

--=-=-=
Content-Type: text/plain


Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com> wrote:
    > By and large PMTUD works. It doesn't always work, which is an issue. But
    > it largely works.

How did you arrive at this conclusion?
I use native IPv6 through tunnels and PPPoE on a regular and continuous basis
throughout the day.  Without PLMTUD enabled, I get regular fails.

I have an IPsec tunnel to a one-armed router that I used from my laptop, and
somehow it just WILL NOT produce an ICMP message when it should.  And my
ISP's router seems to never produce ICMPs on incoming traffic to the PPPoE.
PLMTUD saves the day each time.

    > Also unfortunately, very few stacks seem to ship with PLMTUD enabled by
    > default.

yes, it's a mystery as to why not.
It works well.

    > I think we should focus on PMTUD with a fallback to PLMTUD. As far as I
    > know there are no major stack running with just PLMTUD and we have
    > no idea how it would work in practice.

I think that there was a lot of experience with PLMTUD from the people who
designed it 15 years ago.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVzUEQ4CLcPvd0N1lAQL8jwf5ARU6MJW3YV8Q+dZ8VJPfL20pu1mudalf
v12E1vzwmLkTmc3VeB1HX1c2cneXFO8HQoUk1JkWEYxPmlQGnIF5YTbwE9Y+nj1a
GgWH5sN6FdfwDaXZmmGyUr+My1Sqg3uQGkXD73WLNfiYxrv2C/C89EOgIsCfFUDJ
Lt4RzpIEvOYmfRqH1AxLb/IHISXhrccRW39PW3wx9XqlQ6wZXkZ/jBcYXHgz/3D7
VSC2SwGupvo4CW+Zf/a+Lid00o7flG/j8+QQkUabvy2UCNXp0DnyzvjQQEA1ugjf
mOWykUicdRiUTQi0+PyQ40YsatBehGHcls/6F36uM6URKD8303y1DQ==
=MSWf
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu May 12 17:24:05 2016
Return-Path: <marka@isc.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 6EFF812D157 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 17:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.897
X-Spam-Level: 
X-Spam-Status: No, score=-7.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 XVJgzZtJ8J21 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 17:24:01 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA2F12D0C4 for <ipv6@ietf.org>; Thu, 12 May 2016 17:24:01 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 6BC3434941E; Fri, 13 May 2016 00:23:54 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 6A6ED160047; Fri, 13 May 2016 00:23:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 545831600A9; Fri, 13 May 2016 00:23:54 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id J8NinNkDP8-j; Fri, 13 May 2016 00:23:54 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id CD50C160047; Fri, 13 May 2016 00:23:53 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id C28A648AB895; Fri, 13 May 2016 10:23:51 +1000 (EST)
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Mark Andrews <marka@isc.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <m1b0mc2-0000ESC@stereo.hq.phicoh.net> <14356.1463092294@obiwan.sandelman.ca>
Subject: Re: Adding headers and adding options to headers
In-reply-to: Your message of "Thu, 12 May 2016 18:31:34 -0400." <14356.1463092294@obiwan.sandelman.ca>
Date: Fri, 13 May 2016 10:23:51 +1000
Message-Id: <20160513002351.C28A648AB895@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EctYVl-HuCoT6MGUPioJX4V4eiA>
Cc: 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, 13 May 2016 00:24:04 -0000

In message <14356.1463092294@obiwan.sandelman.ca>, Michael Richardson writes:
> 
> Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com> wrote:
>     > By and large PMTUD works. It doesn't always work, which is an issue. But
>     > it largely works.
> 
> How did you arrive at this conclusion?

Is it a broken protocol or broken equipement.  PMTUD works with
equipement that implements IPv4 and IPv6.  Firewalls that drop PTB
indescriminately do not implement IPv4 and IPv6, they implement
some abomination they the incorrectly describe as IPv4 and IPv6.

Load balancers that don't look at the PTB payload to determine where
to send the ICMP message also don't implement IPv4 and IPv6

ICMP is a basic part of IP.

> I use native IPv6 through tunnels and PPPoE on a regular and continuous basis
> throughout the day.  Without PLMTUD enabled, I get regular fails.
> 
> I have an IPsec tunnel to a one-armed router that I used from my laptop, and
> somehow it just WILL NOT produce an ICMP message when it should.  And my
> ISP's router seems to never produce ICMPs on incoming traffic to the PPPoE.
> PLMTUD saves the day each time.
> 
>     > Also unfortunately, very few stacks seem to ship with PLMTUD enabled by
>     > default.
> 
> yes, it's a mystery as to why not.
> It works well.
> 
>     > I think we should focus on PMTUD with a fallback to PLMTUD. As far as I
>     > know there are no major stack running with just PLMTUD and we have
>     > no idea how it would work in practice.
> 
> I think that there was a lot of experience with PLMTUD from the people who
> designed it 15 years ago.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> --=-=-=
> Content-Type: application/pgp-signature; name="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> 
> iQEVAwUBVzUEQ4CLcPvd0N1lAQL8jwf5ARU6MJW3YV8Q+dZ8VJPfL20pu1mudalf
> v12E1vzwmLkTmc3VeB1HX1c2cneXFO8HQoUk1JkWEYxPmlQGnIF5YTbwE9Y+nj1a
> GgWH5sN6FdfwDaXZmmGyUr+My1Sqg3uQGkXD73WLNfiYxrv2C/C89EOgIsCfFUDJ
> Lt4RzpIEvOYmfRqH1AxLb/IHISXhrccRW39PW3wx9XqlQ6wZXkZ/jBcYXHgz/3D7
> VSC2SwGupvo4CW+Zf/a+Lid00o7flG/j8+QQkUabvy2UCNXp0DnyzvjQQEA1ugjf
> mOWykUicdRiUTQi0+PyQ40YsatBehGHcls/6F36uM6URKD8303y1DQ==
> =MSWf
> -----END PGP SIGNATURE-----
> --=-=-=--
> 
> 
> --===============3115220982506232764==
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> --===============3115220982506232764==--
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu May 12 19:11:53 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 3823512B038 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 19:11:52 -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 D_tnh0Pnm1lg for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 19:11:50 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::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 3E8A112B027 for <ipv6@ietf.org>; Thu, 12 May 2016 19:11:50 -0700 (PDT)
Received: by mail-pa0-x234.google.com with SMTP id xk12so35594166pac.0 for <ipv6@ietf.org>; Thu, 12 May 2016 19:11:50 -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=hQIYJmzmfqWf24fGFPRkqlpzJrLlta82okrtuvgfQYs=; b=QUC4OXRZ3z1n8E8h7WFCKEkvXz3JFDT94zXT8ssoGi63N0W6bs0azu/50FcT6ft3SJ TRrg0OW3b9g6yRGNZgXSLs5Y2I3uC3vQJdfa5B25F1BCfIjvVb/1QxILxcmg/F8AGd5K 0NZ1nt6DGYrOCGO9IJVoF0oRXmbo2hu5UeMkbHLLqHdSwrBLI/PH2lg+Z0EJUohntGRs FlX2Taj1LAiL3xnBZ1G2WkwnLu7ua1U5/PUxAcOyLDczEAi32F1In3OQOitB75Fc88U9 4lIbFOtzIMY3+OJGRttPVwfvfnFmRM3bWvc7wlXE/qMP+bucRtm7Kz3CXGk+8EkS5Iqg /L/A==
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=hQIYJmzmfqWf24fGFPRkqlpzJrLlta82okrtuvgfQYs=; b=DmtnBmJXsP6ghlBbxaSlI0BXu9lCUylagUgKgtVyy00AHa7NBS6NmT8Z/fgNpE0L5i TumGBvj413ii/rh6hww8086YlBJDx4Kf/WIDEDvpndbusa7w80CGf0bNGVoW/P1NSWwT 5Zgk7trVxUTQl/hThEsQjLfClhk2RvcE6mGE3Q4DqkJy2Vh8M1Ib5OxFtrLkBrsgFb6z yIgvKV+VrQJMT9ORn8sRESAXw+jTu6Xqzz7BP1xKW3lhhNW+CcjI1kRUuu7hpY60xOHY rZ3Sl0UbycrTu05VKWuQo27unFFBq8Vjv8Emg+7YWDEUUK91OyeASicCTOD/LyF05+NP yENA==
X-Gm-Message-State: AOPr4FW6NXlvwAScHtj2iLbXlaQPlA6+nyCqTZXMR4Lf6mhssfv+Gb38tRAAww2kiuAjeA==
X-Received: by 10.66.153.105 with SMTP id vf9mr18746048pab.47.1463105509824; Thu, 12 May 2016 19:11:49 -0700 (PDT)
Received: from ?IPv6:2406:e007:69e1:1:28cc:dc4c:9703:6781? ([2406:e007:69e1:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 7sm22741789pfe.88.2016.05.12.19.11.45 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 19:11:48 -0700 (PDT)
Subject: PMTUD in 2460bis [was Adding headers and adding options to headers]
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com> <12928.1463091895@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <eff0c16f-1fdf-a44f-73a6-22801388ddd6@gmail.com>
Date: Fri, 13 May 2016 14:12:13 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <12928.1463091895@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yDfIh7bxX0mPzfG0xbl_DOAxAv0>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Fri, 13 May 2016 02:11:52 -0000

Well, I changed the subject, since this is really a separate issue
about the text.

Currently 2460bis has exactly the same words about PMTUD as 2460, and
this is running code if all intermediate systems respect 2460 and 1981
and 4443.

Bob: ===>>> Presumably 2460bis should actually cite 1981bis

1981bis cites PLPMTUD, which is of course new text compared to 1981.

I think that covers it, within the rules for promotion to Internet Standard.

This doesn't fix the real world; that is v6ops territory, where a BCP on
IPv6 ops would belong.

    Brian
On 13/05/2016 10:24, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     > On 12/05/2016 09:45, Michael Richardson wrote:
>     >>
>     >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> >> do you know of any interoperability problems with the current RFC2460?
>     >> >> that has to be the driving issue in deciding this.
>     >>
>     >> > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     >> > as "strongly recommended" so that is normative.
>     >>
>     >> Again: I claim PMTUD is already broken and unfixable.
>     >> (and should be replaced by PLMTUD, which should be turned on by default)
> 
>     > But that's beside the point of what we should say in 2460bis, which is
>     > supposed to be a consolidation of 2460 and nothing more.
> 
> I don't agree.
> As part of the process towards Internet Standard, we are supposed to rip out
> and/or clarify things which didn't work as expected.
> 
> I claim that PMTUD is such a thing, and it seems to be the key reason to
> avoid header insertion/deletion.  (I hear Mark Smith's comments loudly; and I
> have war wounds from debugging MPLS and all manner of 802.3 networks where
> intermediate boxes do stuff mysteriously to packets).
> 
> {I would prefer that header insertion/deletion was impossible because 90% of
> traffic had AH on it.... Hey, a person can dream, can't they?}
> 
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 


From nobody Thu May 12 23:37:57 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 C55D612D0E1 for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 23:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 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=-0.996, SPF_PASS=-0.001] autolearn=ham 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 s7PKLVw0hegO for <ipv6@ietfa.amsl.com>; Thu, 12 May 2016 23:37:54 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0463D12D0C5 for <ipv6@ietf.org>; Thu, 12 May 2016 23:37:54 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id A3DC59CC7D; Thu, 12 May 2016 23:37:51 -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=TFPlLjUZdIVvS2ghbVI10uucvsM=; b= k/ajHueIVCbFquEcpg07HMqEOjiwcsTPykAEGUqETynsxxeuo71zlhs0nSYOB2Fk HyaJFURPQn9QD5hX3BOt9PsnVKM9nzPCKIEWrEDsO5XG3jZfM9wMX3gWfCVAqPvC VIlvCX+RUwXTEi0C0FYyRHUvE3tqXs+Ht0tDL58ryZg=
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=BgqeFGxDSp+wnsbTqSOaskAKah AtBriULrstptGdCku2Y6tCzaNtJbXdj0rOKv6hRgCg5Crzt5PLyM8GcrY0mrUUgB sPVMVkMREmNoCYmM2YKvlHZm9RCiTDzdpnfsf5RIARTUquXRLrcaz3Amu73137EW vldLiNkwlk6QL3tsA=
Received: from h.hanazo.no (unknown [173.38.220.49]) (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 2D9B09CC4F; Thu, 12 May 2016 23:37:51 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D3AE4166B6DE; Fri, 13 May 2016 08:37:48 +0200 (CEST)
Subject: Re: Question to the chair [Adding headers and adding options to headers]
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0991640E-BE27-4AB9-9A3F-5EFCA6450502"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <e1127577-0ae2-79b0-dc93-0ff01a324a15@gmail.com>
Date: Fri, 13 May 2016 08:37:44 +0200
Message-Id: <5113E551-9DDD-482F-AE44-ECBFC047ECF8@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <8CB2AF02-1114-48DF-8DC0-A9C0E073870C@employees.org> <e1127577-0ae2-79b0-dc93-0ff01a324a15@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dbBpuSWaxFSNr5BjwDAJAXwN3Go>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Fri, 13 May 2016 06:37:56 -0000

--Apple-Mail=_0991640E-BE27-4AB9-9A3F-5EFCA6450502
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

Thanks for the question.
What I plan to do is to start working group last calls of the 3 affected =
documents. In series unless someone thinks parallel will work better. We =
will track issues found in the issue tracker, and then work through the =
issues as they are raised.

I have already added a ticket to the tracker for the header insertion. =
While I don't see a clear consensus at the moment, I'm thinking of =
giving the working group (and myself) some time to mull this over now =
that the discussion has settled.
I do not want to make this an issue that blocks progress of 2460bis, so =
I hope we can have this settled by end of WGLC period.

Does that sound reasonable?

Best regards,
Ole

> On 12 May 2016, at 22:39, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> Ole,
>=20
> I think that I and some others disagree with you, and of course
> we are all entitled to our opinions. I doubt we'll hear any new
> arguments now.
>=20
> However, what is your WG Chair's view of the *WG consensus*? Do you =
think
> the rough consensus is to include or exclude these words:
>=20
>   Extension headers must never be inserted by any node other than the
>   source of the packet.  One approach to meet a requirement to add
>   extension headers is to use IP Encapsulation, for example, as =
defined
>   in [RFC2473].
>=20
>   Extension headers must never be deleted or changed in size by any
>   node on the path the packet takes.
>=20
>   The contents of an Extension header or Option in an Extension header
>   may be modified if this is permitted by the definition of the
>   Extension header or option.
>=20
> Regards
>   Brian
>=20
> On 12/05/2016 19:05, otroan@employees.org wrote:
>> Brian,
>>=20
>>> Trying to answer your specific comments concisely:
>>=20
>> Thank you.
>>=20
>> [...]
>>=20
>>>> do you know of any interoperability problems with the current =
RFC2460?
>>>> that has to be the driving issue in deciding this.
>>>=20
>>> Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>>> as "strongly recommended" so that is normative.
>>=20
>> Yes, that would be a valid argument if we were discussing how to =
design header injection.
>> Describing header injection in RFC2460bis is not on the table.
>> My argument is about what we put in 2460bis.
>> I believe no interoperability issue has been shown in RFC2460. Do you =
concur with that?
>>=20
>> (Future specifications can of course create as many interoperability =
issues they like, not much we can or should do about that in 2460).
>>=20
>>>> with regards to making prohibitions on future work in current =
protocol specifications, can you cite any example of the IETF being =
successful with that? :-)
>>>>=20
>>>> RFC2460 already has this prohibition by the way:
>>>>=20
>>>>  With one exception, extension headers are not examined or =
processed
>>>>  by any node along a packet's delivery path, until the packet =
reaches
>>>>  the node (or each of the set of nodes, in the case of multicast)
>>>>  identified in the Destination Address field of the IPv6 header.
>>>>=20
>>>> I'm afraid I don't see the point in changing RFC2460 here.
>>>=20
>>> The word "processed" is the problem here - it is ambiguous. That is =
the
>>> spcific reason for adding "modified or inserted".
>>=20
>> I don't think this text is ambiguous at all.
>> Every network on the planet seems to violate it though, which of =
course is a much larger problem than the one we're talking about here.
>>=20
>> To summarise my view:
>> - There has not been shown any interoperability issues caused by the =
extension header text in 2460
>> - Adding a general prohibitions to avoid something we dislike =
happening in the future, does a) not belong in 2460, b) is not testable =
c) is  unlikely to have the desired effect
>>=20
>> Best regards,
>> Ole
>>=20


--Apple-Mail=_0991640E-BE27-4AB9-9A3F-5EFCA6450502
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

iQEcBAEBCgAGBQJXNXY8AAoJED4aXnjSQuKWF9sH/2wnykwQiSuwKwaugkkPyPek
HcjooRF5jZPK9dC1AmDQgEWXZq7In9q4NEQRJL77R92LjIc8bHx/NjUGi3bkz9Xp
SB5TCRFQ7ffzhOmfM9EiTs/zrvoSOmMA9hCqegep2HLQR7m4ZLfIBka00vzhaQez
2FwQHm2KafZzfTIgrXg4bxN6ooBcT0LuwHqqB3bklv5+vWlIb0fhP7j0axJwJlrZ
Hc0TMghvWq6pNhlfwm0u7e3/JNz78wUVMS87Cqp3YBXKdKuT+Ih/TN5kwfQ9+mKN
x+1fMRBfASTOXjYtRq4GRsbWei7we5v2hq26svlkG0QYiobj5hB3m5lZByXhFLk=
=DPGK
-----END PGP SIGNATURE-----

--Apple-Mail=_0991640E-BE27-4AB9-9A3F-5EFCA6450502--


From nobody Fri May 13 00:09: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 D9C2E12D0F3 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 00:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.997
X-Spam-Level: 
X-Spam-Status: No, score=-2.997 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=-0.996, SPF_PASS=-0.001] autolearn=ham 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 kar7CS2kLHH9 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 00:09:53 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB56812D0F0 for <ipv6@ietf.org>; Fri, 13 May 2016 00:09:53 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 2D1999CC4E; Fri, 13 May 2016 00:09:52 -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=sJwkmslNaBr2ikxSmtNRIiO9O5A=; b= pBFddMeZUejohaEqDLITyxBqGcxYrbC1AERdKizGh2cA9hOGbZJszlXFdg86Uc6e 92CXdiuss2U+8wYgWrEPTO8+yXvEpWYVw2C/XMcw9qMBG1hsKP1mUJTieVtJ5IPX mLQETanK80Q08zB/jJif7cAEjuIrE4ei5ON9fDqtGD8=
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=PuM0iIaIgelYTHDz1Ie4hYoGJa pMn8X9MaJnuYE1S466KOzDZ6A53/tnUnO785bb2vzsU9iQYHVBmkluXGXZRhR/uE ls7Gm3Q3YOONfFSjd/uDUAdAyGxgrdnNdYH5jXJAHc9QIa0Hzp51shHWvCgZnFww Bg+qPBWdyPD1YU+Ps=
Received: from h.hanazo.no (unknown [173.38.220.49]) (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 AE4CB9CC0F; Fri, 13 May 2016 00:09:51 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 503D9166C7A3; Fri, 13 May 2016 09:09:49 +0200 (CEST)
Subject: PMTUD in 2460bis (Was: Adding headers and adding options to headers)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5702B548-1395-42AC-9FDD-2042B4C6DFBA"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <12928.1463091895@obiwan.sandelman.ca>
Date: Fri, 13 May 2016 09:09:46 +0200
Message-Id: <9D4BE731-6641-4842-B2EF-B4A06134201B@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com> <12928.1463091895@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8_TEopNqVYRNR6ioVMYxCBiWUN8>
Cc: 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>, =?us-ascii?Q?=3D=3FUTF-8=3FB=3F56We5piO6YGU5ZOJ=3F=3D?= <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: Fri, 13 May 2016 07:09:57 -0000

--Apple-Mail=_5702B548-1395-42AC-9FDD-2042B4C6DFBA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

[Replying to Michael's post with Brian's new subject]

>>>>> do you know of any interoperability problems with the current =
RFC2460?
>>>>> that has to be the driving issue in deciding this.
>>>=20
>>>> Yes. Inserting extension headers breaks PMTUD. RFC2460 cites =
RFC1981
>>>> as "strongly recommended" so that is normative.
>>>=20
>>> Again: I claim PMTUD is already broken and unfixable.
>>> (and should be replaced by PLMTUD, which should be turned on by =
default)
>=20
>> But that's beside the point of what we should say in 2460bis, which =
is
>> supposed to be a consolidation of 2460 and nothing more.
>=20
> I don't agree.
> As part of the process towards Internet Standard, we are supposed to =
rip out
> and/or clarify things which didn't work as expected.
>=20
> I claim that PMTUD is such a thing, and it seems to be the key reason =
to
> avoid header insertion/deletion.  (I hear Mark Smith's comments =
loudly; and I
> have war wounds from debugging MPLS and all manner of 802.3 networks =
where
> intermediate boxes do stuff mysteriously to packets).
>=20
> {I would prefer that header insertion/deletion was impossible because =
90% of
> traffic had AH on it.... Hey, a person can dream, can't they?}

We can state whatever we'd like in standards about not processing past =
the IPv6 header or banning middleboxes from inserting header or mangling =
the packet in general. The only true answer is encryption.

I largely agree with you that PMTUD is unreliable. Although this paper:
http://dl.acm.org/citation.cfm?id=3D1879155

Although somewhat old, and with limited data on IPv6, seems to suggest =
2-3% PMTUD drop on IPv6 and quite a bit higher on IPv4.
Anyone got newer measurements?
What about measurements on PLMTUD deployments?

With regards to 2460bis; if we look at the motivation of the section 5 =
text, I think it strongly recommends that a host implements path mtu =
discovery, in some form. Just that at the time 2460 was written PMTUD =
was the only one available.

Is your argument that 2460bis should cite both PMTUD and PLMTUD as the =
strongly recommended mechanisms to implement?

Another way of asking if we can add that to 2460bis, would be to ask "is =
4821 ready to be advanced to Internet standard?"

Best regards,
Ole

PS: Completely outside of 2460bis context. There are some other =
interesting ideas floating around. E.g. Andrew Yourtchenko suggested =
that routers truncate and forward instead of dropping and sending PMTUD =
ICMP. With that scheme you could detect full path MTU in one round trip. =
I don't know if he wrote that up anywhere or not.


--Apple-Mail=_5702B548-1395-42AC-9FDD-2042B4C6DFBA
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

iQEcBAEBCgAGBQJXNX29AAoJED4aXnjSQuKWegkH/RrcxGc5zf0ZR48G3JfB4440
3SUtVFPjIiBbBBQ2sCyodKkC5C657FP0EPWI8v586PGSfme2gZNaPbwbsMWBZNgI
IeNp5fzmjM81a73TxJuqzAZjD+uLszHkLPRBWNjbcMWulL5rafXrN3rvxFIGOraI
rzeFqr8Mw/V++QkDxOyJ91bLuHgL4az/5vOWSxHKC8DX5WH6o4WwpmMrWrHohTw1
ZrtMxRZUhas4sEHdAnYn4FBaAU7uz6mUkjq2NJOpAGeqBq1hH//sq/DWqiA7LJEO
suhS0qslVIrhzt149OZoGKTD2HQadVdOQtF9BxiB8dbkNuSqH5tayVoVH2RWsbI=
=e9Y8
-----END PGP SIGNATURE-----

--Apple-Mail=_5702B548-1395-42AC-9FDD-2042B4C6DFBA--


From nobody Fri May 13 05:02:43 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 D79AF12D19F for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 05:02:41 -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 7zWjOnivF9kG for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 05:02:39 -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 7648F12D17B for <ipv6@ietf.org>; Fri, 13 May 2016 05:02:38 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1b1Bnh-0000CCC; Fri, 13 May 2016 14:02:37 +0200
Message-Id: <m1b1Bnh-0000CCC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: Adding headers and adding options to headers 
From: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <m1b0mc2-0000ESC@stereo.hq.phicoh.net> <14356.1463092294@obiwan.sandelman.ca> 
In-reply-to: Your message of "Thu, 12 May 2016 18:31:34 -0400 ." <14356.1463092294@obiwan.sandelman.ca> 
Date: Fri, 13 May 2016 14:02:35 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/QvNvsmD6ZdIwz5JneJ96T4K8_kM>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>
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, 13 May 2016 12:02:42 -0000

>    > By and large PMTUD works. It doesn't always work, which is an issue. B
>ut
>    > it largely works.
>
>How did you arrive at this conclusion?
>I use native IPv6 through tunnels and PPPoE on a regular and continuous basi
>s
>throughout the day.  Without PLMTUD enabled, I get regular fails.

The way I see it that for as link smaller than 1500, most of the IPv6
internet can be reached.

There are some cases where ICMP are dropped, not generated at all, or
generated broken. But it is a small percentage.

The percentage is big enough that from an operational point of view it is
extremely annoying. But technically it mostly works.

>    > Also unfortunately, very few stacks seem to ship with PLMTUD enabled b
>y
>    > default.
>
>yes, it's a mystery as to why not.
>It works well.

Indeed, it's a mistery to me as well.

>I think that there was a lot of experience with PLMTUD from the people who
>designed it 15 years ago.

If we want to offically replace PMTUD with PLMTUD then we need large scale
experience on the current internet. 


From nobody Fri May 13 06:05:32 2016
Return-Path: <cb.list6@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 DF00112D514 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 06:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 AuhfQc3ZcT9O for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 06:05:29 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 6AB1B12D513 for <ipv6@ietf.org>; Fri, 13 May 2016 06:05:29 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id k142so169332542oib.1 for <ipv6@ietf.org>; Fri, 13 May 2016 06:05: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:date:message-id:subject:from:to :cc; bh=wzLJMCQo03EQU41JH3jtIdBtNDxCNahbu9swNGTSk+A=; b=pXi4ILg8oSLs58Jk2sMRkDvoBpm/65/Z8b6vhjvNu+lEJpJEcGPvxW3WIsfjP4LLHT GJrWw//SDEywFUZy+IJP6WcchYKWgt5wVVh9Vc1eYcvLCG7dJHRa+wThVXNkqV6PqXzt rkQAG441cfsVodGEZFeKbGV5xlrDeBLciXJdSKVoQSP0SvQcpxuJvZ4q3bpzTfhQomLe cs6t3/IFgI8bOtnOzN6fhPR8+pZSTJtxphZu1pY7XBGmVA4CPDl76bDfn5+SiiNSqP3p D3NX7E0OZV33uAO+VRmLztpMkk75EDRF3NXUDnIoY9WbqElCZwcleZ0tpAxy15Mp/y+U XGoA==
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:date :message-id:subject:from:to:cc; bh=wzLJMCQo03EQU41JH3jtIdBtNDxCNahbu9swNGTSk+A=; b=f1eOjXm1h5c1ePoWq8ebhwAYBkZ0DUCqov3aIBL3BPN1YK7E29L3ZPidGLkpQ2MxGA 5/w8tKDIEnUuw4MeLGoHPLAdx360HNHn5soCzHcs8q3JyWccVv27Zi/4iY2aVw2SvMfj ksvqwvojoZuytp4OlS/JVPGzV1EgGEpDAGlCWx6Ncx7TRLmUZelt4pBEit+rdbWMwfPK 2uvAnQhnmIq57DBijOXy1dwzRugY9Th3gRS5XKl7NKop83w9hvjUfzNS28U/EYHRggpE mFG0hPUHiGA5rt9s7Rh/whIW8bd6JVn/ukjNDD3SOEG2X/RaAKyW5FVipOynb1TnK2mP 0oIg==
X-Gm-Message-State: AOPr4FXjRzYDykY6eQEBltKzoZseIQ/CQTSZ/5DMnI8/H1NeNbZS5gqhp+YpUe/KVeCNhG2dS2DRLh7GOw1rLw==
MIME-Version: 1.0
X-Received: by 10.157.43.33 with SMTP id o30mr9153266otb.146.1463144728623; Fri, 13 May 2016 06:05:28 -0700 (PDT)
Received: by 10.157.42.70 with HTTP; Fri, 13 May 2016 06:05:28 -0700 (PDT)
In-Reply-To: <14024.1463003151@obiwan.sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca>
Date: Fri, 13 May 2016 06:05:28 -0700
Message-ID: <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: Ca By <cb.list6@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a113d1dbccdff920532b8ed90
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Mf_jP--_erpwzSe1DuUrwBQ4Lzc>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>, 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: Fri, 13 May 2016 13:05:31 -0000

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

On Wednesday, May 11, 2016, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Brian E Carpenter <brian.e.carpenter@gmail.com <javascript:;>> wrote:
>     >> do you know of any interoperability problems with the current
> RFC2460?
>     >> that has to be the driving issue in deciding this.
>
>     > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     > as "strongly recommended" so that is normative.
>
> Again: I claim PMTUD is already broken and unfixable.
> (and should be replaced by PLMTUD, which should be turned on by default)
>
>
Please cite current evidence ipv6 pmtud is broken.

I know the ipv4 situation is widely known, but the ipv6 deployers have been
eyes wide open on making pmtud work as a requirement on day 1


> What else does inserting headers break that isn't related to PMTU ICMPs?
>
> (I'm not in favour of inserting headers.  I am in favour of having rational
> and evidence based reasons in our specifications, or they will get
> ignored).
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca <javascript:;>>, Sandelman
> Software Works
>  -= IPv6 IoT consulting =-
>
>
>
>

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

<br><br>On Wednesday, May 11, 2016, Michael Richardson &lt;<a href=3D"mailt=
o:mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt; wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><br>
Brian E Carpenter &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cv=
ml&#39;, &#39;brian.e.carpenter@gmail.com&#39;)">brian.e.carpenter@gmail.co=
m</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt;&gt; do you know of any interoperability problems with th=
e current RFC2460?<br>
=C2=A0 =C2=A0 &gt;&gt; that has to be the driving issue in deciding this.<b=
r>
<br>
=C2=A0 =C2=A0 &gt; Yes. Inserting extension headers breaks PMTUD. RFC2460 c=
ites RFC1981<br>
=C2=A0 =C2=A0 &gt; as &quot;strongly recommended&quot; so that is normative=
.<br>
<br>
Again: I claim PMTUD is already broken and unfixable.<br>
(and should be replaced by PLMTUD, which should be turned on by default)<br=
>
<br></blockquote><div><br></div><div>Please cite current evidence ipv6 pmtu=
d is broken.=C2=A0</div><div><br></div><div>I know the ipv4 situation is wi=
dely known, but the ipv6 deployers have been eyes wide open on making pmtud=
 work as a requirement on day 1</div><div>=C2=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
What else does inserting headers break that isn&#39;t related to PMTU ICMPs=
?<br>
<br>
(I&#39;m not in favour of inserting headers.=C2=A0 I am in favour of having=
 rational<br>
and evidence based reasons in our specifications, or they will get ignored)=
.<br>
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;c=
vml&#39;, &#39;mcr+IETF@sandelman.ca&#39;)">mcr+IETF@sandelman.ca</a>&gt;, =
Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote>

--001a113d1dbccdff920532b8ed90--


From nobody Fri May 13 06:23:01 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 944D412D121 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 06:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.297
X-Spam-Level: 
X-Spam-Status: No, score=-5.297 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=-0.996, 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 hemxQKeViNz9 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 06:22:58 -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 39B1F12B062 for <ipv6@ietf.org>; Fri, 13 May 2016 06:22:58 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C32E6A2; Fri, 13 May 2016 15:22:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1463145775; bh=68IaFCVGPuI10vsM+TKjiXfepjBuL7VcnXr4SJGrZ2A=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=v9Fp+uyuJ9P01IiHujQu26IN49OxcOirCW1NioeKHNttErYx8OJBEwfkkop2ZwW+Q wUUy/vXSYqkK6JOT3aYKr/f4TpJTHtzqzCyWG+rEMcUgrMdGmDFZgMkUYjvKQe5V45 V0U7WIxiTTWOqsptVUvHuDDmicZlVttK9T6Xhvuw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BEAD6A1; Fri, 13 May 2016 15:22:55 +0200 (CEST)
Date: Fri, 13 May 2016 15:22:55 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ca By <cb.list6@gmail.com>
Subject: Re: Adding headers and adding options to headers
In-Reply-To: <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1605131509290.28372@uplift.swm.pp.se>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.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: <http://mailarchive.ietf.org/arch/msg/ipv6/CuhChNguGdfvSgSYid3NwByjGos>
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: Fri, 13 May 2016 13:23:01 -0000

On Fri, 13 May 2016, Ca By wrote:

> Please cite current evidence ipv6 pmtud is broken.

I know of non-zero amount of web sites where it's broken and doesn't work 
correctly, but I'd say this is not widespread.

My home (ipv6 path) network:

COMPUTER <MTU1500 LAN> ROUTER <MTU1280 tunnel> ROUTER <MTU1500 INTERNET>

I do not do MSS adjust in any of the routers. I rely on PMTUD to work.

Happy Eyeballs won't help me if PMTUD is broken.

I've been running this for years and it's my opinion that there were a lot 
more broken IPv6 enabled sites 3-4 years ago compared to now. I imagine I 
would have noticed if there was widespread PMTUD brokenness.

Otoh I like PLMTUD as well, I think we should have both.

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


From nobody Fri May 13 09:57:22 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 4BFA912D5FF for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 09:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, 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 4X3cbspMwhfM for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 09:57:18 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 81D7012D60C for <ipv6@ietf.org>; Fri, 13 May 2016 09:57:17 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id i75so134850261ioa.3 for <ipv6@ietf.org>; Fri, 13 May 2016 09:57:17 -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:date:message-id:subject :from:to:cc; bh=d4wakSfYz9gObvhqRyBQrb4qembJ4UvxmFTQw1hPa0Q=; b=yzTveWN013bXZVftIAuvphswClrgpqV9jK4qyuLv74qW5rtvVDH6+kHnNCYqzqmQrn u8mC/notFmq3eP21USm8qJRgEwguMQu/HO/7P688Hr1DGLG0Vwti0OK6+6TKty+mighW tTCg46tadDFtqFP9VxQviYNqKilYU06WFW28yprg4ickW10a+/oLnvH1NWt6Snyo83l0 sTp5hQwrcpPCcVcbM+zvmeC6d0cD3Trw1Hzz4O5PsBMNXvwap3VmHu90co/tFm7UPOey OLGzbDzx7nK4C2uZE3Efxx+p9ZF8GKjSq4dzmlfNwzR+E9ReG8w06Wf09cfPDBknL4e2 GOZQ==
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:date :message-id:subject:from:to:cc; bh=d4wakSfYz9gObvhqRyBQrb4qembJ4UvxmFTQw1hPa0Q=; b=kRowZeSent/Ic9q/Wg2ljOFFvChJyIV1NA2itavi8XS+KgIfWFdDy5gi+lxF2PpQ1p rmLjG8+RM+8a5XTj+5Bp8HxRf/AZe+gE6lBG46dTwIFSYqevkaYZ0kmePddmiCFFtXb3 11xHQpz7fTS6bbBRnK+Tk4sXC2r0cebZYifPbF66zZzYozkJRHGLZLJgOrIDLEu+otin jVdNrQhrKKar1+aXvqwvUCCR7gxBm5Th2pj0+pS3iFZmr47Nm1CgDzOOubIfdESM3Vl1 0cSS1ijtfbSgMGCDdvxtVwh7SjMDrLyOoi60+gQvfM4WM/0DHppopDXPjCTnTAoParHH lUBA==
X-Gm-Message-State: AOPr4FV4+2sdi33TEjQvLZcQtM+BEhHqvYIHkuAy7YYbWSG6/P8FfyiKxbCtiyxy3zJtcFW01lTyB94NKIPd/Q==
MIME-Version: 1.0
X-Received: by 10.107.58.213 with SMTP id h204mr13189505ioa.172.1463158636876;  Fri, 13 May 2016 09:57:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Fri, 13 May 2016 09:57:16 -0700 (PDT)
In-Reply-To: <12928.1463091895@obiwan.sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com> <12928.1463091895@obiwan.sandelman.ca>
Date: Fri, 13 May 2016 09:57:16 -0700
X-Google-Sender-Auth: T9yJoS4EC9sBbIkYfLEryfvKO74
Message-ID: <CAJE_bqcJ95g=y7VGi=WYutuiFLwazsmNPB7DaZwg6ztXfR4gGQ@mail.gmail.com>
Subject: Re: Adding headers and adding options to headers
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GvRoBvUhGrqcAq9y2ZPtTItFG-E>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@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: Fri, 13 May 2016 16:57:20 -0000

At Thu, 12 May 2016 18:24:55 -0400,
Michael Richardson <mcr+ietf@sandelman.ca> wrote:

>     >> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>     >> >> do you know of any interoperability problems with the current RFC2460?
>     >> >> that has to be the driving issue in deciding this.
>     >>
>     >> > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>     >> > as "strongly recommended" so that is normative.
>     >>
>     >> Again: I claim PMTUD is already broken and unfixable.
>     >> (and should be replaced by PLMTUD, which should be turned on by default)
>
>     > But that's beside the point of what we should say in 2460bis, which is
>     > supposed to be a consolidation of 2460 and nothing more.
>
> I don't agree.
> As part of the process towards Internet Standard, we are supposed to rip out
> and/or clarify things which didn't work as expected.

Two separate points seem to be conflated here:

A. Whether PMTUD is already broken and should be removed from 2460bis
B. Even if A is true, whether that can be a reason for not explicitly
   clarifying the EH insertion/deletion matter in 2460bis

Your second sentence ('As part of...') seems to simply focus on A, but
I'm not sure if the first sentence "disagreed" about A or B or both or
something else...

I don't have a strong opinion on point A although I feel it'd be
overkill to remove it.  But regarding point B, I'd list another
example that inserting extension headers breaks DNS server
implementations, which generally limit large response packets to up to
1280 bytes to avoid PMTUD overhead (even if PMTUD works).  This is the
case regardless of whether PMTUD really works or is broken or PLMTUD
is/will be widely implemented and deployed.  (in any case, though, I
personally don't think we have to show these specific cases just for
not being silent on the existing ambiguity in the first place, as I
said in my other message).

--
JINMEI, Tatuya


From nobody Fri May 13 10:00:43 2016
Return-Path: <joelja@bogus.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 5EE9C12D617 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 10:00:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.896
X-Spam-Level: 
X-Spam-Status: No, score=-7.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996] 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 lExIdei8qdd8 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 10:00:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 96D9812D5AB for <ipv6@ietf.org>; Fri, 13 May 2016 10:00:39 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4204:51:9054:da3e:6769:a455]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4DH0XEK030133 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 13 May 2016 17:00:34 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4204:51:9054:da3e:6769:a455] claimed to be mb-2.local
Subject: Re: Adding headers and adding options to headers
To: Ca By <cb.list6@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <fefbf8d3-92c5-df06-24dd-56907d1134a1@bogus.com>
Date: Fri, 13 May 2016 10:00:31 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1
MIME-Version: 1.0
In-Reply-To: <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2RuSreBwPDKJsklRjIQ1ClPFXFNTCeP9D"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TIEDDvAVhaRXNcxrxem4sNxKrJk>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>, =?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: Fri, 13 May 2016 17:00:41 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2RuSreBwPDKJsklRjIQ1ClPFXFNTCeP9D
Content-Type: multipart/mixed; boundary="2gEv8gE1oHmxjj7uh936drUj6WknllVHE"
From: joel jaeggli <joelja@bogus.com>
To: Ca By <cb.list6@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>,
 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Message-ID: <fefbf8d3-92c5-df06-24dd-56907d1134a1@bogus.com>
Subject: Re: Adding headers and adding options to headers
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com>
 <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com>
 <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com>
 <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org>
 <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com>
 <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com>
 <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org>
 <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com>
 <14024.1463003151@obiwan.sandelman.ca>
 <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>
In-Reply-To: <CAD6AjGTPLQ9ZHZc4OH+xL+6VTZOLBHdSxsgu+mM4Zy8aH2tZow@mail.gmail.com>

--2gEv8gE1oHmxjj7uh936drUj6WknllVHE
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/13/16 6:05 AM, Ca By wrote:
>=20
>=20
> On Wednesday, May 11, 2016, Michael Richardson <mcr+ietf@sandelman.ca
> <mailto:mcr%2Bietf@sandelman.ca>> wrote:
>=20
>=20
>     Brian E Carpenter <brian.e.carpenter@gmail.com <javascript:;>> wrot=
e:
>         >> do you know of any interoperability problems with the curren=
t
>     RFC2460?
>         >> that has to be the driving issue in deciding this.
>=20
>         > Yes. Inserting extension headers breaks PMTUD. RFC2460 cites
>     RFC1981
>         > as "strongly recommended" so that is normative.
>=20
>     Again: I claim PMTUD is already broken and unfixable.
>     (and should be replaced by PLMTUD, which should be turned on by def=
ault)
>=20
>=20
> Please cite current evidence ipv6 pmtud is broken.=20
>=20
> I know the ipv4 situation is widely known, but the ipv6 deployers have
> been eyes wide open on making pmtud work as a requirement on day 1

Hashing to endpoints is naturally really problematic irrespective
address family.

>=20
>     What else does inserting headers break that isn't related to PMTU I=
CMPs?
>=20
>     (I'm not in favour of inserting headers.  I am in favour of having
>     rational
>     and evidence based reasons in our specifications, or they will get
>     ignored).
>=20
>=20
>     --
>     Michael Richardson <mcr+IETF@sandelman.ca <javascript:;>>, Sandelma=
n
>     Software Works
>      -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20



--2gEv8gE1oHmxjj7uh936drUj6WknllVHE--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlc2CDAACgkQ8AA1q7Z/VrL1NwCdEakgel4nwwEVOAl4IDLCY/PS
iZkAnj0vNntrT45gRGVp20k8SHqq/Eiw
=tPl5
-----END PGP SIGNATURE-----

--2RuSreBwPDKJsklRjIQ1ClPFXFNTCeP9D--


From nobody Fri May 13 10:55:21 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 4750312D647 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 10:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, 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 ffja_EeTQFXN for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 10:55:17 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 2F11412D0C3 for <ipv6@ietf.org>; Fri, 13 May 2016 10:55:17 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id 190so142165119iow.1 for <ipv6@ietf.org>; Fri, 13 May 2016 10:55:17 -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:date:message-id:subject :from:to:cc; bh=ZbxMG3cU9Fsx9zI/FdPcRZInqjCeePMHhWFruNd066I=; b=0xOfbYi0pFzcPv66oirmdPqRGjSy1VbgFczhADw4Tsu8dJ/V55RsesXK1gn/zQdn7W b93RU3tAJpu9iX7rRq2bpMrBeiOnZ0dTVRj0myBZ4G4mZU105qPkusXHQ9h2giVvvsK0 C/gmF+Cc4w6RTKUqAV9KEjdkMJhjBFFsCdBOb079zJUL2Aj3EFipywvzF4uBt0qupv/u 0UVjHoOvoAcoKI1zFVrJ+yj9KBFobYh1bm+nt/tppX1/lPvuUAvLhVosGlqc38K03aPI 02u+X2/zQ2U0OVZIuUcETp3P8YfgSGjVMjlBlRcdNxeLdH2i59DXlPrukcRoMsD3vEkP IzdA==
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:date :message-id:subject:from:to:cc; bh=ZbxMG3cU9Fsx9zI/FdPcRZInqjCeePMHhWFruNd066I=; b=hUkplpCZSX0mftD3pN8eOJmOBvuNnGWasFjW5+k0z+oDxhVhdPBfuBVHdWCLCfXRCP VWjsFo41nkpR4prRbk4bLWE+f9mkjtU5mtAJr0+7w9RLiStjrbMwUhW93u6E+a41RHUV bjqcu3Kg3P0jub7C6S5qDyhLohYjlFadZcJfB6iryNKx83FfOyhrl72l1nQqN701wmUK 77RVRzsKjf//eeRq4LDEGFOebMXCrerwS3YRJ211pPkpu5KL98w9CvT21fJSk9Goydov hIjj5IavkFRW3+Gm4cfVuTCwwbovNuS0Y/I6E4gtrtXFcyq8zoBykIq1tkdrecNu+/Um vZpg==
X-Gm-Message-State: AOPr4FUCaHDngPt6klRYs3KJB2Vl8ewY4pJWxrYUg4A/69u3+M1X0bm1dO+CHqRsME3pHUZ1ZnrBUGqFupcjTw==
MIME-Version: 1.0
X-Received: by 10.107.35.66 with SMTP id j63mr13934906ioj.4.1463162116408; Fri, 13 May 2016 10:55:16 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Fri, 13 May 2016 10:55:16 -0700 (PDT)
In-Reply-To: <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
Date: Fri, 13 May 2016 10:55:16 -0700
X-Google-Sender-Auth: AjFWAI6NOMzbrBjS07kH_fEqgWI
Message-ID: <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/b1-TWV5w4syQpS7sxAEZeM6_tq4>
Cc: IPv6 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: Fri, 13 May 2016 17:55:19 -0000

At Wed, 11 May 2016 20:19:01 -0700,
Bob Hinden <bob.hinden@gmail.com> wrote:

>        Title           : Recommendation on Stable IPv6 Interface Identifiers
>        Authors         : Fernando Gont
>                          Alissa Cooper
>                          Dave Thaler
>                          Will Liu
>     Filename        : draft-ietf-6man-default-iids-11.txt
>     Pages           : 23
>     Date            : 2016-04-27
>
>         https://tools.ietf.org/html/draft-ietf-6man-default-iids-11
>
> as a Proposed Standard.  Substantive comments and statements of support for publishing this document should be directed to the mailing list.  Editorial suggestions can be sent to the authors.  This last call will end on 25 May 2016.

I've read version 11 of the document.  Personally I don't have a
strong objection to publishing it, but, if I understand the past
concerns correctly, I suspect this version don't fully address them.
I also have one non-trivial point, which I would like to be address
before publication.

If my understanding is correct, one major concern raised in the past
was that some implementors may simply not see the need for the
stability and just want to address the security/privacy issues in a
different way (such as just using randomized link-layer addresses).  I
don't have a strong opinion on this particular concern myself, but I
see the point of such concerns.  If the intent of this document is not
to refuse the concern (which I'm not sure about), the current tone
still seems to be too normative.  Again, I'm not sure if the intent is
to address the concern, but if it is, I think something like the
following will be necessary:

- clarify that this recommendation is only for environments where
  address stability is needed
- clarify that this document assumes "link layer addresses" are
  something permanent, such as MAC addresses that don't change
  throughout the lifetime of the node using the hardware
- update the requirement level and wording to existing RFCs.  For
  example, replaced text for RFC2462 provided in Section 6.1

   The Interface Identifier [AARCH] for an Ethernet interface MUST be
   generated as specified in [RFCXXXX].

  is probably too strong, since this would invalidate any
  implementation that doesn't implement or use RFCXXXX.  The same
  sense of comment applies to all similar changes.

And, one other point I want to be addressed: in Section 4 it states:

   By default, DHCPv6 server implementations SHOULD NOT generate
   predictable IPv6 addresses (such as IPv6 addresses where the IIDs are
   consecutive small numbers).  [I-D.ietf-dhc-stable-privacy-addresses]
   specifies one possible algorithm that could be employed to comply
   with this requirement.  Another possible algorithm would be to select
   a pseudo-random value chosen from a discrete uniform distribution,
   while avoiding the reserved IPv6 Interface Identifiers [RFC5453]
   [IANA-RESERVED-IID].

 I suggest just removing the second sentence.
 ietf-dhc-stable-privacy-addresses is not a dhc wg item anymore due to
 some controversy, and it's not clear what will happen to its
 successor in the form of individual submission:
 draft-gont-dhcpv6-stable-privacy-addresses-01
 Since this sentence is only to show an example, just showing the
 "another possible algorithm" would suffice.

Finally, one minor editorial nit: in section 6.14

   for instance, using a method described in [8], to autoconfigure one
   or more global unicast addresses.

there should be a 'cut here' line after this text.

--
JINMEI, Tatuya


From nobody Fri May 13 11:01:23 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 AABB612D658 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 11:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, 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 ONCfRGpUoToW for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 11:01:20 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9285D12D64D for <ipv6@ietf.org>; Fri, 13 May 2016 11:01:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 64C7D203BC for <ipv6@ietf.org>; Fri, 13 May 2016 14:07:00 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7322D638BE for <ipv6@ietf.org>; Fri, 13 May 2016 14:01:19 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: 6man WG <ipv6@ietf.org>
Subject: Re: PMTUD in 2460bis (Was: Adding headers and adding options to headers)
In-Reply-To: <9D4BE731-6641-4842-B2EF-B4A06134201B@employees.org>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <64868e21-7873-2e3f-2f69-18a4f565aeac@gmail.com> <12928.1463091895@obiwan.sandelman.ca> <9D4BE731-6641-4842-B2EF-B4A06134201B@employees.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 13 May 2016 14:01:19 -0400
Message-ID: <15316.1463162479@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9XyEITjHNOqZDeWszFG67vRs8E8>
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, 13 May 2016 18:01:23 -0000

--=-=-=
Content-Type: text/plain


otroan@employees.org wrote:
    mcr> {I would prefer that header insertion/deletion was impossible because 90% of
    mcr> traffic had AH on it.... Hey, a person can dream, can't they?}

    > We can state whatever we'd like in standards about not processing past
    > the IPv6 header or banning middleboxes from inserting header or
    > mangling the packet in general. The only true answer is encryption.

+1000.

    > With regards to 2460bis; if we look at the motivation of the section 5
    > text, I think it strongly recommends that a host implements path mtu
    > discovery, in some form. Just that at the time 2460 was written PMTUD
    > was the only one available.

    > Is your argument that 2460bis should cite both PMTUD and PLMTUD as the
    > strongly recommended mechanisms to implement?

Yes, I would be happier with this.

    > Another way of asking if we can add that to 2460bis, would be to ask
    > "is 4821 ready to be advanced to Internet standard?"

    > PS: Completely outside of 2460bis context. There are some other
    > interesting ideas floating around. E.g. Andrew Yourtchenko suggested
    > that routers truncate and forward instead of dropping and sending PMTUD
    > ICMP. With that scheme you could detect full path MTU in one round
    > trip. I don't know if he wrote that up anywhere or not.

okay, so transport checksums and AH would completely break at the receiving
host, which is probably no worse than not having the packet at all, but it
would be indistinguishable from an attack.

A more ECN-like mechanism along with the truncation of all the transport
data contents might be better; one has to keep the same originating IP in order to
pass through firewalls and ACLs, etc.  An interesting idea to discuss, though.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVzYWbICLcPvd0N1lAQLfZgf/RGXQP/cKGHw5sKQwi+6TwwT30fT9Gwzs
JeQxL14e7jFPPxf0q0p+/vhrHBzaZxFJsu6Eu3STpjXZRuqYf2GRvXibL+mUCQbs
2NU3rwm3rkQsqyTgtFTEiPoBjXZ8yVP3MHZdzU9w5qhm34D4P9dLn1Z5HdfvfH6D
kz644CDdBNMkh6THS3W6i1b2jAs9SKSSJJYkGhdc8q8D2IFsIEopPP8M7AZB/jpG
+9gv6qd84mO37Ly3/JTSqyDwBcCyhaXsIJOFJN26Y5XiSyACk3YDkUE2N2NkU3x+
9qawT4GT3NRdLjDtEO92sfYSySf+o8RH6BpWB+qz/lTe/WRj4BkF2w==
=X6bu
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 13 11:05:05 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 6351B12D66B for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 11:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996, 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 2AOReldmem9N for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 11:05:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FDE712D64D for <ipv6@ietf.org>; Fri, 13 May 2016 11:04:58 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6EDF1203BC; Fri, 13 May 2016 14:10:38 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 7A73D638BE; Fri, 13 May 2016 14:04:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Subject: Re: Adding headers and adding options to headers
In-Reply-To: <m1b1Bnh-0000CCC@stereo.hq.phicoh.net>
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <14024.1463003151@obiwan.sandelman.ca> <m1b0mc2-0000ESC@stereo.hq.phicoh.net> <14356.1463092294@obiwan.sandelman.ca> <m1b1Bnh-0000CCC@stereo.hq.phicoh.net>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 13 May 2016 14:04:57 -0400
Message-ID: <16143.1463162697@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/o4Y9ogDcqzOTv-4rK2NFE2CCKxI>
Cc: 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, 13 May 2016 18:05:04 -0000

--=-=-=
Content-Type: text/plain


Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com> wrote:
    >> I think that there was a lot of experience with PLMTUD from the people who
    >> designed it 15 years ago.

    > If we want to offically replace PMTUD with PLMTUD then we need large scale
    > experience on the current internet.

I agree.

It would be rather easy a thing to do for some big provider, maybe a CDN
could do an experiment.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBVzYXRoCLcPvd0N1lAQJ4kggAmEz6K+Yt10QxUsWc7M6XAaEbakTgD4pH
CteXEA4BbWZPO90wU9uua+mH52TWJgx7GlCd4jv/e94GFTuTvM8BH6vbkGL8pjbR
YVYl3hHs373PkBvSAjtzzEK0SWftJhXiiupkd8V1LeD87rZqzaJ08XnOCAcrZ7mL
UwIpq0cBDOclszjcaMsEWtJ4kis+9Gexx1iyQ0nBem2FdkS1m//zcLc5HUj7lhSd
bx+9O3d6ApI2RWPv4OWhEs4f4nCa7JmReRwEnjHn22x8l2RFR44B6buHmD+JIXgO
Vxuy8BigTHXkF6roog4Cx3RKLxRen+dgXFR8aGlIDzwI/T9MzqGNkg==
=MTVM
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri May 13 13:35:32 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 0469812D11E for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 13:35:30 -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 lr_l0PraAtV9 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 13:35:29 -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 E10E412D10A for <ipv6@ietf.org>; Fri, 13 May 2016 13:35:28 -0700 (PDT)
Received: by mail-pa0-x22f.google.com with SMTP id iv1so43973390pac.2 for <ipv6@ietf.org>; Fri, 13 May 2016 13:35:28 -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=oAAR9ljhSS0cS55WmXXTyAM+ggmQedOwzHYKiZJrQlQ=; b=NCQU1xC+NMMl3eOV/93Hbk3v81Cfu4RyT+mxKpU4q58hFk8W6+/EuTNzJ7ar0aOJJh z0LreR+0Lk36SgSh8isKSdwk41cEoo2IkRk6Owk8SbV6lleCwFNnUVNTAe3T689w3Gc+ ymRtDjK1m0T8ICnOsSLhP2yE8z1taI7wLUdbdSuH6lKNKUVho4a3BhGzscL/+b18w8Dh QB/PlahH6xYKx0MNT85JksFiiQ2CAuwkRMSCafO3YdGQ5ouUsbLB2jtI9M0HRSaVG2xg sMJXNT7pA1j1WqqGybGHDv52YR3HDTXn7HtQcXriJwPYgAzLnERuZhEwFWSrQ87tH5By KW4A==
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=oAAR9ljhSS0cS55WmXXTyAM+ggmQedOwzHYKiZJrQlQ=; b=g+RblphxYAQ94I1Ig7WujweA+qVwgj82wEoUOSaO/4YNPZM7TaAmyR5y7vwaqH6yzg roxytw1Ho4QwBVOcXBO21kdx2E58iFh/RaUbV8WVfuVDemKx3xgvjaPJW9cYG/RfDP0Q P25qUJFS8sZRcpmbsip5q4l+DuPy35naV52fmZN3oA9E1WrQaRneYW5x7qAw524yzWJg AKEb10UIWwtyPaOdQPGbQZPrBif64F6zCeSxDhvKwJG6IM7XgVaOVu3+MR0R9jIEulgO I+fITKSo2OueH73W3a/310EKYKmVcDgOrgqe5ROiFcv0yAk0lvJTMN7eIRB9yfa+2GGY DS4A==
X-Gm-Message-State: AOPr4FWs7y5lkIOVcMIBEHq1LHxq3b2rLl3IMDjyVYs9VvyQXBed3jkI66S4yn4JijX05Q==
X-Received: by 10.67.22.129 with SMTP id hs1mr26040079pad.105.1463171728513; Fri, 13 May 2016 13:35:28 -0700 (PDT)
Received: from ?IPv6:2406:e007:56d8:1:28cc:dc4c:9703:6781? ([2406:e007:56d8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d184sm29452854pfc.27.2016.05.13.13.35.24 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 13:35:27 -0700 (PDT)
Subject: Re: Question to the chair [Adding headers and adding options to headers]
To: otroan@employees.org
References: <A88D0044-5DB6-44B6-905F-925C156B18E0@cisco.com> <792E3875-2DB8-4A77-B7A1-3AC70400F371@cisco.com> <3c7d2448-3254-84e5-82f4-78e0a9aec332@gmail.com> <D04EF23B-3163-4DDB-B5AD-8FE6ACA35F9D@employees.org> <81014ff6-671d-1990-3050-57b05e2737fc@gmail.com> <CAJE_bqeS_Dg7n0Pu+BbO1L=Ee8_sRrH-5sGG-vVcEb9sswYELA@mail.gmail.com> <9B450B41-0E6E-47E6-B26B-936E44DFCBF6@employees.org> <dd297fa4-3c6a-e188-4e85-655b01371b07@gmail.com> <8CB2AF02-1114-48DF-8DC0-A9C0E073870C@employees.org> <e1127577-0ae2-79b0-dc93-0ff01a324a15@gmail.com> <5113E551-9DDD-482F-AE44-ECBFC047ECF8@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fe6eb0d9-8be1-19e0-a217-c00dd48d0511@gmail.com>
Date: Sat, 14 May 2016 08:35:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <5113E551-9DDD-482F-AE44-ECBFC047ECF8@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2mWb6d9PsigNfVNS1nkVzzuoTr4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Fred Baker \(fred\)" <fred@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: Fri, 13 May 2016 20:35:31 -0000

On 13/05/2016 18:37, otroan@employees.org wrote:
> Brian,
> 
> Thanks for the question.
> What I plan to do is to start working group last calls of the 3 affected documents. In series unless someone thinks parallel will work better. We will track issues found in the issue tracker, and then work through the issues as they are raised.
> 
> I have already added a ticket to the tracker for the header insertion. While I don't see a clear consensus at the moment, I'm thinking of giving the working group (and myself) some time to mull this over now that the discussion has settled.
> I do not want to make this an issue that blocks progress of 2460bis, so I hope we can have this settled by end of WGLC period.
> 
> Does that sound reasonable?

Yes, very reasonable.

Thanks,
       Brian

> 
> Best regards,
> Ole
> 
>> On 12 May 2016, at 22:39, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> Ole,
>>
>> I think that I and some others disagree with you, and of course
>> we are all entitled to our opinions. I doubt we'll hear any new
>> arguments now.
>>
>> However, what is your WG Chair's view of the *WG consensus*? Do you think
>> the rough consensus is to include or exclude these words:
>>
>>   Extension headers must never be inserted by any node other than the
>>   source of the packet.  One approach to meet a requirement to add
>>   extension headers is to use IP Encapsulation, for example, as defined
>>   in [RFC2473].
>>
>>   Extension headers must never be deleted or changed in size by any
>>   node on the path the packet takes.
>>
>>   The contents of an Extension header or Option in an Extension header
>>   may be modified if this is permitted by the definition of the
>>   Extension header or option.
>>
>> Regards
>>   Brian
>>
>> On 12/05/2016 19:05, otroan@employees.org wrote:
>>> Brian,
>>>
>>>> Trying to answer your specific comments concisely:
>>>
>>> Thank you.
>>>
>>> [...]
>>>
>>>>> do you know of any interoperability problems with the current RFC2460?
>>>>> that has to be the driving issue in deciding this.
>>>>
>>>> Yes. Inserting extension headers breaks PMTUD. RFC2460 cites RFC1981
>>>> as "strongly recommended" so that is normative.
>>>
>>> Yes, that would be a valid argument if we were discussing how to design header injection.
>>> Describing header injection in RFC2460bis is not on the table.
>>> My argument is about what we put in 2460bis.
>>> I believe no interoperability issue has been shown in RFC2460. Do you concur with that?
>>>
>>> (Future specifications can of course create as many interoperability issues they like, not much we can or should do about that in 2460).
>>>
>>>>> with regards to making prohibitions on future work in current protocol specifications, can you cite any example of the IETF being successful with that? :-)
>>>>>
>>>>> RFC2460 already has this prohibition by the way:
>>>>>
>>>>>  With one exception, extension headers are not examined or processed
>>>>>  by any node along a packet's delivery path, until the packet reaches
>>>>>  the node (or each of the set of nodes, in the case of multicast)
>>>>>  identified in the Destination Address field of the IPv6 header.
>>>>>
>>>>> I'm afraid I don't see the point in changing RFC2460 here.
>>>>
>>>> The word "processed" is the problem here - it is ambiguous. That is the
>>>> spcific reason for adding "modified or inserted".
>>>
>>> I don't think this text is ambiguous at all.
>>> Every network on the planet seems to violate it though, which of course is a much larger problem than the one we're talking about here.
>>>
>>> To summarise my view:
>>> - There has not been shown any interoperability issues caused by the extension header text in 2460
>>> - Adding a general prohibitions to avoid something we dislike happening in the future, does a) not belong in 2460, b) is not testable c) is  unlikely to have the desired effect
>>>
>>> Best regards,
>>> Ole
>>>
> 


From nobody Fri May 13 13:45:43 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 9E70D12D130 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 13:45:42 -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=PG/TQask; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=VLSKyG/Q
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 uPYlv6YFhtRK for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 13:45:39 -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 C9EB312B050 for <ipv6@ietf.org>; Fri, 13 May 2016 13:45:39 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 4461D20765 for <ipv6@ietf.org>; Fri, 13 May 2016 16:45:39 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 13 May 2016 16:45:39 -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=uwoMv A8ksYgg7yD9JSogj2E4oSI=; b=PG/TQaskTxpQtLS9xYydTRo11/IvE5ZAsL9c/ xEPG/x8eQjUjsNMVz75YbaeflTAyUfCQ9D7Gvy0CumNIWjwufX2o+s0ber3mSxRO +XEHTQbCN0Se0KwFoWNtiSqtBQ+/9Nmz05CU3/ubIuLWpbhO9DmJXVvYVZh8chW4 92B1jE=
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=uwoMvA8ksYgg7yD9JSogj2E4oSI=; b=VLSKy G/Q+GC1xwHuaStqey1NDoklNYRT77Mrz98kBj2RmB3IMMm5TiV3TWzzrLWugP0SJ nXGlTfE9PbUYdU8YsIOIqFMc4cIJEy2FDHM76fOIIjmI8r21kuLa0x+hylcckGW4 dtIzg1zoFqsLseYUxnfaunyjCHELs8W9mAWJ3I=
X-Sasl-enc: DOPQIlRfhha0TwdxHTc8iobD1OKdF0Fw0KFAEjABPRJo 1463172338
Received: from dhcp-171-68-20-154.cisco.com (dhcp-171-68-20-154.cisco.com [171.68.20.154]) by mail.messagingengine.com (Postfix) with ESMTPA id 86CDBC00012; Fri, 13 May 2016 16:45:38 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CEFAA15D-38CB-468F-B4CD-7B47AB84D72D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com>
Date: Fri, 13 May 2016 13:45:37 -0700
Message-Id: <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/g6TLu-e0Qcr1ZzV2lGn2_WEK2c8>
Cc: IPv6 List <ipv6@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: Fri, 13 May 2016 20:45:42 -0000

--Apple-Mail=_CEFAA15D-38CB-468F-B4CD-7B47AB84D72D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks for these comments. Responses are in-line.

> On May 13, 2016, at 10:55 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Wed, 11 May 2016 20:19:01 -0700,
> Bob Hinden <bob.hinden@gmail.com> wrote:
>=20
>>       Title           : Recommendation on Stable IPv6 Interface =
Identifiers
>>       Authors         : Fernando Gont
>>                         Alissa Cooper
>>                         Dave Thaler
>>                         Will Liu
>>    Filename        : draft-ietf-6man-default-iids-11.txt
>>    Pages           : 23
>>    Date            : 2016-04-27
>>=20
>>        https://tools.ietf.org/html/draft-ietf-6man-default-iids-11
>>=20
>> as a Proposed Standard.  Substantive comments and statements of =
support for publishing this document should be directed to the mailing =
list.  Editorial suggestions can be sent to the authors.  This last call =
will end on 25 May 2016.
>=20
> I've read version 11 of the document.  Personally I don't have a
> strong objection to publishing it, but, if I understand the past
> concerns correctly, I suspect this version don't fully address them.
> I also have one non-trivial point, which I would like to be address
> before publication.
>=20
> If my understanding is correct, one major concern raised in the past
> was that some implementors may simply not see the need for the
> stability and just want to address the security/privacy issues in a
> different way (such as just using randomized link-layer addresses).  I
> don't have a strong opinion on this particular concern myself, but I
> see the point of such concerns.  If the intent of this document is not
> to refuse the concern (which I'm not sure about), the current tone
> still seems to be too normative.  Again, I'm not sure if the intent is
> to address the concern, but if it is, I think something like the
> following will be necessary:
>=20
> - clarify that this recommendation is only for environments where
>  address stability is needed

The document says exactly this in the introduction:

The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  That is, this document does not
   change any existing recommendations concerning the use of temporary
   addresses as specified in [RFC4941 =
<https://tools.ietf.org/html/rfc4941>], nor does it introduce any new
   requirements regarding when stable addresses are to be configured.
   Thus, the recommendations in this document simply improve the
   security and privacy properties of stable addresses.

The two paragraphs prior to this one in the intro also serve to explain =
this.=20

> - clarify that this document assumes "link layer addresses" are
>  something permanent, such as MAC addresses that don't change
>  throughout the lifetime of the node using the hardware

The document purposefully does not assume that. We clarified this in the =
latest update to the introduction:

More generally, the reuse of identifiers that have their own
   semantics or properties across different contexts or scopes can be
   detrimental for security and privacy
   [I-D.gont-predictable-numeric-ids =
<https://tools.ietf.org/html/draft-ietf-6man-default-iids-11#ref-I-D.gont-=
predictable-numeric-ids>].  In the case of traditional
   stable IPv6 IIDs, some of the security and privacy implications are
   dependent on the properties of the underlying link-layer addresses
   (e.g., whether the link-layer address is ephemeral or randomly
   generated), while other implications (e.g., reduction of the entropy
   of the IID) depend on the algorithm for generating the IID itself.
   In standardized recommendations for IPv6 IID generation meant to
   achieve particular security and privacy properties, it is therefore
   necessary to recommend against embedding link-layer addresses in IPv6
   IIDs.


> - update the requirement level and wording to existing RFCs.  For
>  example, replaced text for RFC2462 provided in Section 6.1
>=20
>   The Interface Identifier [AARCH] for an Ethernet interface MUST be
>   generated as specified in [RFCXXXX].
>=20
>  is probably too strong, since this would invalidate any
>  implementation that doesn't implement or use RFCXXXX.  The same
>  sense of comment applies to all similar changes.

I=E2=80=99m not sure what you mean by =E2=80=9Cinvalidate,=E2=80=9D but =
the recommendations in Section 3 around which schemes to employ or not =
employ are all SHOULD-level requirements, by design.

>=20
> And, one other point I want to be addressed: in Section 4 it states:
>=20
>   By default, DHCPv6 server implementations SHOULD NOT generate
>   predictable IPv6 addresses (such as IPv6 addresses where the IIDs =
are
>   consecutive small numbers).  [I-D.ietf-dhc-stable-privacy-addresses]
>   specifies one possible algorithm that could be employed to comply
>   with this requirement.  Another possible algorithm would be to =
select
>   a pseudo-random value chosen from a discrete uniform distribution,
>   while avoiding the reserved IPv6 Interface Identifiers [RFC5453]
>   [IANA-RESERVED-IID].
>=20
> I suggest just removing the second sentence.
> ietf-dhc-stable-privacy-addresses is not a dhc wg item anymore due to
> some controversy, and it's not clear what will happen to its
> successor in the form of individual submission:
> draft-gont-dhcpv6-stable-privacy-addresses-01
> Since this sentence is only to show an example, just showing the
> "another possible algorithm" would suffice.

I=E2=80=99m fine with the above change.

>=20
> Finally, one minor editorial nit: in section 6.14
>=20
>   for instance, using a method described in [8], to autoconfigure one
>   or more global unicast addresses.
>=20
> there should be a 'cut here' line after this text.

Good catch, 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=_CEFAA15D-38CB-468F-B4CD-7B47AB84D72D
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"">Thanks for these comments. Responses are =
in-line.</div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 13, 2016, at 10:55 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 =
Wed, 11 May 2016 20:19:01 -0700,<br class=3D"">Bob Hinden &lt;<a =
href=3D"mailto:bob.hinden@gmail.com" =
class=3D"">bob.hinden@gmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
Recommendation on Stable IPv6 Interface Identifiers<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Fernando Gont<br =
class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Alis=
sa Cooper<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Dave=
 Thaler<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Will=
 Liu<br class=3D""> &nbsp;&nbsp;&nbsp;Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-6man-default-iids-11.txt<br class=3D""> =
&nbsp;&nbsp;&nbsp;Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 23<br =
class=3D""> &nbsp;&nbsp;&nbsp;Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2016-04-27<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-6man-default-iids-11" =
class=3D"">https://tools.ietf.org/html/draft-ietf-6man-default-iids-11</a>=
<br class=3D""><br class=3D"">as a Proposed Standard. &nbsp;Substantive =
comments and statements of support for publishing this document should =
be directed to the mailing list. &nbsp;Editorial suggestions can be sent =
to the authors. &nbsp;This last call will end on 25 May 2016.<br =
class=3D""></blockquote><br class=3D"">I've read version 11 of the =
document. &nbsp;Personally I don't have a<br class=3D"">strong objection =
to publishing it, but, if I understand the past<br class=3D"">concerns =
correctly, I suspect this version don't fully address them.<br =
class=3D"">I also have one non-trivial point, which I would like to be =
address<br class=3D"">before publication.<br class=3D""><br class=3D"">If =
my understanding is correct, one major concern raised in the past<br =
class=3D"">was that some implementors may simply not see the need for =
the<br class=3D"">stability and just want to address the =
security/privacy issues in a<br class=3D"">different way (such as just =
using randomized link-layer addresses). &nbsp;I<br class=3D"">don't have =
a strong opinion on this particular concern myself, but I<br =
class=3D"">see the point of such concerns. &nbsp;If the intent of this =
document is not<br class=3D"">to refuse the concern (which I'm not sure =
about), the current tone<br class=3D"">still seems to be too normative. =
&nbsp;Again, I'm not sure if the intent is<br class=3D"">to address the =
concern, but if it is, I think something like the<br class=3D"">following =
will be necessary:<br class=3D""><br class=3D"">- clarify that this =
recommendation is only for environments where<br class=3D""> =
&nbsp;address stability is needed<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>The =
document says exactly this in the introduction:</div><div><br =
class=3D""></div><div><pre class=3D"newpage" style=3D"font-size: =
13.3333px; margin-top: 0px; margin-bottom: 0px; font-variant-ligatures: =
normal; font-variant-position: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal; widows: 1;">The recommendations in this document =
apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  That is, this document does not
   change any existing recommendations concerning the use of temporary
   addresses as specified in [<a =
href=3D"https://tools.ietf.org/html/rfc4941" title=3D"&quot;Privacy =
Extensions for Stateless Address Autoconfiguration in IPv6&quot;" =
class=3D"">RFC4941</a>], nor does it introduce any new
   requirements regarding when stable addresses are to be configured.
   Thus, the recommendations in this document simply improve the
   security and privacy properties of stable addresses.</pre><div =
class=3D""><br class=3D""></div><div class=3D"">The two paragraphs prior =
to this one in the intro also serve to explain =
this.&nbsp;</div></div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">- clarify that this document =
assumes "link layer addresses" are<br class=3D""> &nbsp;something =
permanent, such as MAC addresses that don't change<br class=3D""> =
&nbsp;throughout the lifetime of the node using the hardware<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>The =
document purposefully does not assume that. We clarified this in the =
latest update to the introduction:</div><div><br =
class=3D""></div><div><pre class=3D"newpage" style=3D"font-size: =
13.3333px; margin-top: 0px; margin-bottom: 0px; font-variant-ligatures: =
normal; font-variant-position: normal; font-variant-numeric: normal; =
font-variant-alternates: normal; font-variant-east-asian: normal; =
line-height: normal; widows: 1;">More generally, the reuse of =
identifiers that have their own
   semantics or properties across different contexts or scopes can be
   detrimental for security and privacy
   [<a =
href=3D"https://tools.ietf.org/html/draft-ietf-6man-default-iids-11#ref-I-=
D.gont-predictable-numeric-ids" =
class=3D"">I-D.gont-predictable-numeric-ids</a>].  In the case of =
traditional
   stable IPv6 IIDs, some of the security and privacy implications are
   dependent on the properties of the underlying link-layer addresses
   (e.g., whether the link-layer address is ephemeral or randomly
   generated), while other implications (e.g., reduction of the entropy
   of the IID) depend on the algorithm for generating the IID itself.
   In standardized recommendations for IPv6 IID generation meant to
   achieve particular security and privacy properties, it is therefore
   necessary to recommend against embedding link-layer addresses in IPv6
   IIDs.</pre><div class=3D""><br class=3D""></div></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"">- update the requirement level and wording to existing RFCs. =
&nbsp;For<br class=3D""> &nbsp;example, replaced text for RFC2462 =
provided in Section 6.1<br class=3D""><br class=3D""> &nbsp;&nbsp;The =
Interface Identifier [AARCH] for an Ethernet interface MUST be<br =
class=3D""> &nbsp;&nbsp;generated as specified in [RFCXXXX].<br =
class=3D""><br class=3D""> &nbsp;is probably too strong, since this =
would invalidate any<br class=3D""> &nbsp;implementation that doesn't =
implement or use RFCXXXX. &nbsp;The same<br class=3D""> &nbsp;sense of =
comment applies to all similar changes.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I=E2=80=
=99m not sure what you mean by =E2=80=9Cinvalidate,=E2=80=9D but the =
recommendations in Section 3 around which schemes to employ or not =
employ are all SHOULD-level requirements, by design.</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D""><br class=3D"">And, one other point I want to be addressed: =
in Section 4 it states:<br class=3D""><br class=3D""> &nbsp;&nbsp;By =
default, DHCPv6 server implementations SHOULD NOT generate<br class=3D""> =
&nbsp;&nbsp;predictable IPv6 addresses (such as IPv6 addresses where the =
IIDs are<br class=3D""> &nbsp;&nbsp;consecutive small numbers). =
&nbsp;[I-D.ietf-dhc-stable-privacy-addresses]<br class=3D""> =
&nbsp;&nbsp;specifies one possible algorithm that could be employed to =
comply<br class=3D""> &nbsp;&nbsp;with this requirement. &nbsp;Another =
possible algorithm would be to select<br class=3D""> &nbsp;&nbsp;a =
pseudo-random value chosen from a discrete uniform distribution,<br =
class=3D""> &nbsp;&nbsp;while avoiding the reserved IPv6 Interface =
Identifiers [RFC5453]<br class=3D""> &nbsp;&nbsp;[IANA-RESERVED-IID].<br =
class=3D""><br class=3D""> I suggest just removing the second =
sentence.<br class=3D""> ietf-dhc-stable-privacy-addresses is not a dhc =
wg item anymore due to<br class=3D""> some controversy, and it's not =
clear what will happen to its<br class=3D""> successor in the form of =
individual submission:<br class=3D""> =
draft-gont-dhcpv6-stable-privacy-addresses-01<br class=3D""> Since this =
sentence is only to show an example, just showing the<br class=3D""> =
"another possible algorithm" would suffice.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>I=E2=80=
=99m fine with the above change.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><br =
class=3D"">Finally, one minor editorial nit: in section 6.14<br =
class=3D""><br class=3D""> &nbsp;&nbsp;for instance, using a method =
described in [8], to autoconfigure one<br class=3D""> &nbsp;&nbsp;or =
more global unicast addresses.<br class=3D""><br class=3D"">there should =
be a 'cut here' line after this text.<br =
class=3D""></div></div></blockquote><div><br class=3D""></div><div>Good =
catch, thanks.</div><div><br class=3D""></div><div>Alissa</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=_CEFAA15D-38CB-468F-B4CD-7B47AB84D72D--


From nobody Fri May 13 18:55:51 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 B631D12B011 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 18:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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=-0.996, 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 DroF9nFbGknh for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 18:55:47 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::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 6F15512B007 for <ipv6@ietf.org>; Fri, 13 May 2016 18:55:47 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id d62so153589457iof.2 for <ipv6@ietf.org>; Fri, 13 May 2016 18:55:47 -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=/tq1YaBD4agl/EvBbhzSdWZWtbcTGkgECE3qzoydVzg=; b=Hj2fPoSrwnOABSPnB5VXTYcghP20empapbv3wcu3u2xOUfygidYSC5E8qu0R+qHSog S82aZ4sFm6JPebTPP2bmhocwf9/r2kpLhwtUHY9nqXWFnAVo2HMPdtztFRLFNzXx5izC OXBdUC2Q9/vIjGa2UYoABI0TrH+Ac8B7yweOtYhKQ6jZXYm4S8f8kcWP1ffzlHp/ub+I GJvaYyuAdWPd9uqBI9Nlq2z71WtCus65i/HEUcI8FRjCyuzd2UQhB47po/crwS7RmYXG i8mADtlQk+02blA+NcVFo3tGrQsB477eHjpkpEDO4B0DuHAi5dFtP7u0/89bjH/IUsz4 DatA==
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=/tq1YaBD4agl/EvBbhzSdWZWtbcTGkgECE3qzoydVzg=; b=cYmi1RaTqxYtnfad4CmplrLUJvJ4WGQaT/1Sg1+2VqDxzn0Syw4POE+vUOly8+GhnY 9OuNx+k2yFEOCg9APRXcdS4AzD0x0+EidW7rD/YrqS/lhU2cZhh6DjmWhsXR3gn9qOCd Bd6mz9DLGu54y0DuE91+CZjouuP5xzZigqZLHGidaN+O2m1pT//FyMbuxljkDBls25ks V03FQ2ygHQvaiNmc9aQVIjzFps7qlo3oF0GAPPqNW0uZr/hMpschBR5ijZbBRo1dbJ6F oKhwh+jopab007i0QtKLD5ZC0G+9QpiI25ZjGhXFnNRYMmhWzLgufoG6jQrJembLFGxJ AuEQ==
X-Gm-Message-State: AOPr4FVL8tMvsshFpB2CmGl+HyO18DjSXRoItnLtiv2+eFzqLT54Zou+/1PuIlv6cug8Mhl3roO+ly6rH5C3HfPw
X-Received: by 10.107.175.67 with SMTP id y64mr3127474ioe.113.1463190946636; Fri, 13 May 2016 18:55:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.19.174 with HTTP; Fri, 13 May 2016 18:55:26 -0700 (PDT)
In-Reply-To: <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 14 May 2016 10:55:26 +0900
Message-ID: <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a114464fe9d71810532c3b06c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SjMkN4YS0vEhZN1lxf4LiYa98cw>
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: Sat, 14 May 2016 01:55:50 -0000

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

I continue to oppose this document.

This draft says that existing address generation mechanisms are bad for
privacy, and proceeds to change them. But there is nothing wrong with
the existing address generation mechanisms as if the link-layer addresses
are not stable, (e.g., random MAC addresses), and a growing body of IETF
work

This draft forbids implementations from using existing address generation
mechanisms using random MAC addresses, which is a perfectly valid way to
address the privacy problem this draft is purportedly solving, and is an
approach standardized in other IETF work, for example,
https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.1
(now in RFC editor queue).

Here are several examples of how this draft forbids using address
generation mechanisms with random MAC addresses.

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.
...
   In standardized recommendations for IPv6 IID generation meant to
   achieve particular security and privacy properties, it is therefore
   necessary to recommend against embedding link-layer addresses in IPv6
   IIDs.
...
   By default, nodes SHOULD NOT employ IPv6 address generation schemes
   that embed the underlying link-layer address in the IID.

These statements should not say "link-layer address". They should say
"stable link-layer-address" or "non-ephemeral link-layer-address" or
"link-layer address that are not known to be ephemeral".

Worse, consider this normative text:

   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 MUST be
   generated as specified in [RFCXXXX].

This explicitly prohibits an implementation from taking a random MAC
address and forming an EUI-64 address out of it.

On Fri, May 13, 2016 at 5:43 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> With the clarifying references to RFC4941, I think this document is
> in good shape and ready to be advanced.
>
>     Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<div dir=3D"ltr">I continue to oppose this document.<div><br></div><div>Thi=
s draft says that existing address generation mechanisms are bad for privac=
y, and proceeds to change them. But there is nothing wrong with the=C2=A0ex=
isting address generation mechanisms as if the link-layer addresses are not=
 stable, (e.g., random MAC addresses), and a growing body of IETF work=C2=
=A0</div><div><br></div><div>This draft forbids implementations from using =
existing address generation mechanisms using random MAC addresses, which is=
 a perfectly valid way to address the privacy problem this draft is purport=
edly solving, and is an approach standardized in other IETF work, for examp=
le, <a href=3D"https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile=
-08#section-2.1">https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profi=
le-08#section-2.1</a> (now in RFC editor queue).</div><div><br></div><div>H=
ere are several examples of how this draft forbids using address generation=
 mechanisms with random MAC addresses.<br></div><div><div><br></div><div><d=
iv>=C2=A0 =C2=A0The recommendations in this document apply only in cases wh=
ere</div><div>=C2=A0 =C2=A0implementations otherwise would have configured =
a stable IPv6 IID</div><div>=C2=A0 =C2=A0containing a link layer address.</=
div></div><div>...<br></div><div>=C2=A0 =C2=A0In standardized recommendatio=
ns for IPv6 IID generation meant to<br></div><div><div>=C2=A0 =C2=A0achieve=
 particular security and privacy properties, it is therefore</div><div>=C2=
=A0 =C2=A0necessary to recommend against embedding link-layer addresses in =
IPv6</div><div>=C2=A0 =C2=A0IIDs.</div></div><div>...<br></div><div>=C2=A0 =
=C2=A0By default, nodes SHOULD NOT employ IPv6 address generation schemes<b=
r></div><div><div>=C2=A0 =C2=A0that embed the underlying link-layer address=
 in the IID.</div></div><div><br></div><div>These statements should not say=
 &quot;link-layer address&quot;. They should say &quot;stable link-layer-ad=
dress&quot; or &quot;non-ephemeral link-layer-address&quot; or &quot;link-l=
ayer address that are not known to be ephemeral&quot;.<br></div><div><br></=
div><div>Worse, consider this normative text:</div><div><br></div><div><div=
>=C2=A0 =C2=A0The entire text of Section 4 of [RFC2464] is replaced with th=
e</div><div>=C2=A0 =C2=A0following text:</div><div><br></div><div>=C2=A0 =
=C2=A0---------------- cut here -------------- cut here ----------------</d=
iv><div>=C2=A0 =C2=A0The Interface Identifier [AARCH] for an Ethernet inter=
face MUST be</div><div>=C2=A0 =C2=A0generated as specified in [RFCXXXX].</d=
iv></div><div><br></div><div>This explicitly prohibits an implementation fr=
om taking a random MAC address and forming an EUI-64 address out of it.</di=
v></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Fri, May 13, 2016 at 5:43 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">With t=
he clarifying references to RFC4941, I think this document is<br>
in good shape and ready to be advanced.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
--------------------------------------------------------------------<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/list=
info/ipv6</a><br>
--------------------------------------------------------------------<br>
</div></div></blockquote></div><br></div>

--001a114464fe9d71810532c3b06c--


From nobody Fri May 13 19:32:12 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 37B6A12B00F for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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, 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 aK1w9-M_G1Ku for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:32:09 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::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 0E7CD12B007 for <ipv6@ietf.org>; Fri, 13 May 2016 19:32:09 -0700 (PDT)
Received: by mail-vk0-x22b.google.com with SMTP id s184so158040004vkb.3 for <ipv6@ietf.org>; Fri, 13 May 2016 19:32:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6QJxNscy/Z1aBRhvSau1nGF+sAW6gap5nXhlL414OtI=; b=JUHNTjzmLRlpNwdGM8TT3K2A11W5Qjp7atjkr09DBh7DYHDFFJG6nUAdaPKhUcnz5S OJ8+3srZfgQW2wvlAu0AzaxZaSrWlTiEDQiqL6bD470ORK147j0iV2xJizDLiDDtE1pG 4mhF4x7oqujIfaz6mN31eLN4spx/Pznp5JxgNYSxOibSVaCl5ZF3KPQYioi9z5IByvuo m/pAh93snwC0XQSQIccOY6toyH6xS/TgmQnrx/5d94usnjTsdwPzh3FnoDbiYifHyftB wCJbdeASqAqCm5ptJDTPCWihdAJ/DN30RqBEWB3k0v/f4WAFrDKflYPz9gvTxtW4GO8H p4Kg==
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:date :message-id:subject:from:to:cc; bh=6QJxNscy/Z1aBRhvSau1nGF+sAW6gap5nXhlL414OtI=; b=Wz0/eC7kwDxu5oswsJXWh/cJ0lmABgNMmRQvJAjtD4AJY/EBVYXAU/erH3r9bx/e5Q yKo+yNdqcYvoGmWsMd16IDwxzC82/vBJUtO9TaD47Y/xaKLH5s8SHvbN5nnQL3MM1eiF 7mI3Fbeq5QnXMIBEZCNd9wbNKLEt41JLQw5PFtj2QI/684THDRop7jFA6IJNgd1JmfNf W4qA2floEVoDsifmgdialzde16kYPG8VKtXELI8+Oh9AoqB0ltLFMGZrDljH80o4oMZO fyhX1E8y+owkgfCFvB4ccI+PIbVOrJ7tD8xc8hVlR/J4oN1tI0Oe6qpGAqjWlSBEH9wR A1qQ==
X-Gm-Message-State: AOPr4FVt/oFbctXgM+B/cupd8R4Fe0VgxQuY5jS5h21+28Ydq4XCGbjggQT1cNI3eIGDLnPbiO1NUN5JdN4ABw==
MIME-Version: 1.0
X-Received: by 10.159.39.106 with SMTP id a97mr9492950uaa.133.1463193128050; Fri, 13 May 2016 19:32:08 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Fri, 13 May 2016 19:32:07 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Fri, 13 May 2016 19:32:07 -0700 (PDT)
In-Reply-To: <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
Date: Sat, 14 May 2016 12:32:07 +1000
Message-ID: <CAO42Z2x-kzpo_=G=nTpEwCuaCd6SuTPV_Hu3azrGLSpyHjT8oA@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=94eb2c0481e8a2a7cc0532c43273
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/21eFGPpMGicbCrqUCISuyaKn5DU>
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: Sat, 14 May 2016 02:32:11 -0000

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

On 14 May 2016 11:56 AM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> I continue to oppose this document.
>
> This draft says that existing address generation mechanisms are bad for
privacy, and proceeds to change them. But there is nothing wrong with
the existing address generation mechanisms as if the link-layer addresses
are not stable, (e.g., random MAC addresses), and a growing body of IETF
work
>

The thing wrong with "solving" a layer 3 problem at layer 2 is that it
makes the effectiveness of the layer 3 outcome entirely dependent on the
attributes of another layer. It's fundamentally a layer violation.

I think we have layers to try to minimise or avoid these dependencies.
Having a layer 3 privacy solution to this layer 3 privacy problem means
that it doesn't matter if the layer 2 privacy is terrible or not.

I don't think this draft is forbidding layer 2 privacy at all - it is
forbidding relying on it at layer 3, because it can't and I don't think
should be relied on.

Regards,
Mark.

> This draft forbids implementations from using existing address generation
mechanisms using random MAC addresses, which is a perfectly valid way to
address the privacy problem this draft is purportedly solving, and is an
approach standardized in other IETF work, for example,
https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.1
(now in RFC editor queue).
>
> Here are several examples of how this draft forbids using address
generation mechanisms with random MAC addresses.
>
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.
> ...
>    In standardized recommendations for IPv6 IID generation meant to
>    achieve particular security and privacy properties, it is therefore
>    necessary to recommend against embedding link-layer addresses in IPv6
>    IIDs.
> ...
>    By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed the underlying link-layer address in the IID.
>
> These statements should not say "link-layer address". They should say
"stable link-layer-address" or "non-ephemeral link-layer-address" or
"link-layer address that are not known to be ephemeral".
>
> Worse, consider this normative text:
>
>    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 MUST be
>    generated as specified in [RFCXXXX].
>
> This explicitly prohibits an implementation from taking a random MAC
address and forming an EUI-64 address out of it.
>
> On Fri, May 13, 2016 at 5:43 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
>>
>> With the clarifying references to RFC4941, I think this document is
>> in good shape and ready to be advanced.
>>
>>     Brian
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr"><br>
On 14 May 2016 11:56 AM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I continue to oppose this document.<br>
&gt;<br>
&gt; This draft says that existing address generation mechanisms are bad fo=
r privacy, and proceeds to change them. But there is nothing wrong with the=
=C2=A0existing address generation mechanisms as if the link-layer addresses=
 are not stable, (e.g., random MAC addresses), and a growing body of IETF w=
ork=C2=A0<br>
&gt;</p>
<p dir=3D"ltr">The thing wrong with &quot;solving&quot; a layer 3 problem a=
t layer 2 is that it makes the effectiveness of the layer 3 outcome entirel=
y dependent on the attributes of another layer. It&#39;s fundamentally a la=
yer violation.</p>
<p dir=3D"ltr">I think we have layers to try to minimise or avoid these dep=
endencies. Having a layer 3 privacy solution to this layer 3 privacy proble=
m means that it doesn&#39;t matter if the layer 2 privacy is terrible or no=
t.</p>
<p dir=3D"ltr">I don&#39;t think this draft is forbidding layer 2 privacy a=
t all - it is forbidding relying on it at layer 3, because it can&#39;t and=
 I don&#39;t think should be relied on.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; This draft forbids implementations from using existing =
address generation mechanisms using random MAC addresses, which is a perfec=
tly valid way to address the privacy problem this draft is purportedly solv=
ing, and is an approach standardized in other IETF work, for example, <a hr=
ef=3D"https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#secti=
on-2.1">https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#sec=
tion-2.1</a> (now in RFC editor queue).<br>
&gt;<br>
&gt; Here are several examples of how this draft forbids using address gene=
ration mechanisms with random MAC addresses.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0The recommendations in this document apply only in cases =
where<br>
&gt; =C2=A0 =C2=A0implementations otherwise would have configured a stable =
IPv6 IID<br>
&gt; =C2=A0 =C2=A0containing a link layer address.<br>
&gt; ...<br>
&gt; =C2=A0 =C2=A0In standardized recommendations for IPv6 IID generation m=
eant to<br>
&gt; =C2=A0 =C2=A0achieve particular security and privacy properties, it is=
 therefore<br>
&gt; =C2=A0 =C2=A0necessary to recommend against embedding link-layer addre=
sses in IPv6<br>
&gt; =C2=A0 =C2=A0IIDs.<br>
&gt; ...<br>
&gt; =C2=A0 =C2=A0By default, nodes SHOULD NOT employ IPv6 address generati=
on schemes<br>
&gt; =C2=A0 =C2=A0that embed the underlying link-layer address in the IID.<=
br>
&gt;<br>
&gt; These statements should not say &quot;link-layer address&quot;. They s=
hould say &quot;stable link-layer-address&quot; or &quot;non-ephemeral link=
-layer-address&quot; or &quot;link-layer address that are not known to be e=
phemeral&quot;.<br>
&gt;<br>
&gt; Worse, consider this normative text:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0The entire text of Section 4 of [RFC2464] is replaced wit=
h the<br>
&gt; =C2=A0 =C2=A0following text:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0---------------- cut here -------------- cut here -------=
---------<br>
&gt; =C2=A0 =C2=A0The Interface Identifier [AARCH] for an Ethernet interfac=
e MUST be<br>
&gt; =C2=A0 =C2=A0generated as specified in [RFCXXXX].<br>
&gt;<br>
&gt; This explicitly prohibits an implementation from taking a random MAC a=
ddress and forming an EUI-64 address out of it.<br>
&gt;<br>
&gt; On Fri, May 13, 2016 at 5:43 AM, Brian E Carpenter &lt;<a href=3D"mail=
to:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt; wrote:<=
br>
&gt;&gt;<br>
&gt;&gt; With the clarifying references to RFC4941, I think this document i=
s<br>
&gt;&gt; in good shape and ready to be advanced.<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0 =C2=A0 Brian<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------------------------------------------=
--<br>
&gt;&gt; IETF IPv6 working group mailing list<br>
&gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/l=
istinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&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>
&gt;<br>
</p>

--94eb2c0481e8a2a7cc0532c43273--


From nobody Fri May 13 19:45:14 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 B1E9012B007 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:45:12 -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 bdNsrHw3lWQj for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:45:11 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::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 30F1212B009 for <ipv6@ietf.org>; Fri, 13 May 2016 19:45:11 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id c189so49766006pfb.3 for <ipv6@ietf.org>; Fri, 13 May 2016 19:45:11 -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=TIzz7DNb7bDeNgPvsqjb/Kx06ndpEG4BKF2d52nb1+M=; b=ls2/XNB8PYc8GRoH2xWKeRdQwgEznMCaDhNfqKmYnl1eTfgnw+68EC5Ds7JnNitY94 olkzDCCxHbU0l2hvu5Qwx7sVBWsz9D1Fe8kpl82f5Q5lVjxvW+/MXkExuttKHlfU9L+i KTqFeS75ieHQxJcWuy7YOHixe8h2P/lxXpMGP+Z31iQKtSkgSMl0rqZVkvnBGl7/ynuE p1CUEEf1ENcjOXPfMRDGVHwQ9QpQlQYUoifNP3B7KYlqxb3XNsNnuZGH1BileZrTmxkT cZEh+rt0rcYjz+9pCx4UQEMLi36i4aoSYzFKlmfhV3kLX/blE4CVGjh1vU4qaCA35hzH m+6w==
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=TIzz7DNb7bDeNgPvsqjb/Kx06ndpEG4BKF2d52nb1+M=; b=Jz0yByNO7steSwSUFbFcmRxhUd92BSVt7gNnjBKpwDNIjmw9B4xmhfv9ZzgxlOgITU hwKR6EhWFqTKAmNVD5OawDzMufAa8Cxnvs5CYU3XqJMN2rLyrp8gfVSZZEGCB3uLXzdL YRrGPAv2K9egulG6cbRQS0MIVjb71daWjcE13jWrtjFkeJwz+NRK2il4fekK7C9TKOXb zDO7ZSAWlzGFLh4oaa5CumrJvcVM+lT13YEdHx6Lk9ey3/gy2f2W1C56UD7g9z+tbRH1 Nvace7aNTuF8++CAgT0b0t3Q0jXrSaV+nTgPRmF1r9d25s/WgeLQj1nPVftihFObGACj 7Qpg==
X-Gm-Message-State: AOPr4FU3OaVxVCAH3kFFHSRxYNdN1PW8SPl2CrDl49RjLRhTPlzTab/XsQsOT78hn1dOxA==
X-Received: by 10.98.77.199 with SMTP id a190mr27505090pfb.37.1463193910778; Fri, 13 May 2016 19:45:10 -0700 (PDT)
Received: from ?IPv6:2406:e007:56d8:1:28cc:dc4c:9703:6781? ([2406:e007:56d8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id n66sm30436920pfb.17.2016.05.13.19.45.07 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 19:45:09 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com>
Date: Sat, 14 May 2016 14:45:37 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/S9uEROhhRljRjreir9V4B2YALsc>
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: Sat, 14 May 2016 02:45:13 -0000

On 14/05/2016 13:55, Lorenzo Colitti wrote:
...
> This explicitly prohibits an implementation from taking a random MAC
> address and forming an EUI-64 address out of it.

Which is a good thing, since otherwise a bad actor could correlate the
layer 2 and layer 3 addresses, which is actually impossible with IPv4
but a current weakness in IPv6.

   Brian


From nobody Fri May 13 19:46:33 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 4C67112B009 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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=-0.996, 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 35ZMfdqzBNmI for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:46:30 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 8848612B007 for <ipv6@ietf.org>; Fri, 13 May 2016 19:46:30 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id o66so134655575ywc.3 for <ipv6@ietf.org>; Fri, 13 May 2016 19:46:30 -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=XlK/I2RUf3+/4viWoaHGKJsUuJxkCHEkNK1EfOcL8LI=; b=ihO7rb33IMXkLQfwGsEtZggFBNYei4uH1PyZ7tPW2rSBrrbpgrbgapdIWGmKv4Ma6E WVoSR6KbI1VycQRQoHdz7cCkvX2UJzQD+ZUVWpY15EzDvqcMi+IXtjpyNbZQ1iPbfjuw eYYfY06sBG4WWd8No+ArmCY5Dwe2Apqg8c43GagRsNa9NXsC9ccfCJ3aF500uhDrhong lvIS4JzPQTD0HF69seSj+7SnpjCesN8+96S5Ma2VrdfsPwFhr/050DqjBBGEHZZSj9lj 1D677CuVKMKC3g7Wkfr8EZvmzpFh09EUNgabABGAjDbEbutliXwoo2c5ZFAdPNT91Pmo HoYA==
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=XlK/I2RUf3+/4viWoaHGKJsUuJxkCHEkNK1EfOcL8LI=; b=Z/zk8CWXJY55g3NBaEU/EGApjeCRtoUqyzh7o+vU46BmbLutf96sb7xS04X+zR8Na/ 9prZq1eydr7K9lxk8wrmefJqwSKRE/5+2sOuSP4QjuDaztqRtAegLMjE4aO0jHOBkHPl G2uwCYDKeSGgsaJP3oJ3Oq3Fyw3OTVQYlkl3oHEPPKuOBnXTyNboeT8HZ4r3ZfM2FLt1 Ad7m9766uwN/eZ7JR4W6jZh+DOMjeH2X1+WhBDx0Ot5u+9hYkMiH6NT3xIrIx2844ne4 TP8PlwjY6ySXiQ0d63rTu4bKrYDC88q12lAMtzv0WUOSnfZELWsT9QApAeUPZr9VfCyC 6lZA==
X-Gm-Message-State: AOPr4FWVdYaJJAM06A65Wn6L5PkL5ozGX9wj1v3eZkmPUDNdf3xsFUBwy8G2tVyYxzMhIDRqqrse7rNVBdo96o6U
X-Received: by 10.37.110.65 with SMTP id j62mr8860619ybc.155.1463193989637; Fri, 13 May 2016 19:46:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 13 May 2016 19:46:10 -0700 (PDT)
In-Reply-To: <CAO42Z2x-kzpo_=G=nTpEwCuaCd6SuTPV_Hu3azrGLSpyHjT8oA@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <CAO42Z2x-kzpo_=G=nTpEwCuaCd6SuTPV_Hu3azrGLSpyHjT8oA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 14 May 2016 11:46:10 +0900
Message-ID: <CAKD1Yr0HCQ7yhXe4Zh_YZabO9AHSmxf0-2=2yKqvTsb4r3zmZQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a1148acd2fe0c850532c46561
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-JFxb8d-e_xo0BWmV4KcoG20CgM>
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: Sat, 14 May 2016 02:46:32 -0000

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

On Sat, May 14, 2016 at 11:32 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> The thing wrong with "solving" a layer 3 problem at layer 2 is that it
> makes the effectiveness of the layer 3 outcome entirely dependent on the
> attributes of another layer. It's fundamentally a layer violation.
>
> I think we have layers to try to minimise or avoid these dependencies.
> Having a layer 3 privacy solution to this layer 3 privacy problem means
> that it doesn't matter if the layer 2 privacy is terrible or not.
>
Actually, it's the opposite: the reason we have layers is so that layer X
doesn't have to worry about reimplementing functionality provided by layer
X-1.

If we were to follow your argument, we would implement CRC checks, packet
retransmissions, and fragmentation into HTTP, because otherwise the
reliability of HTTP would be entirely dependent on the attributes of layers
2, 3, and 4. Guess what: the outcome of HTTP *is* entirely dependent on the
link-layer not scrambling data, on on TCP dealing with packet reordering
and packet loss by sequencing and retransmitting, etc.

--001a1148acd2fe0c850532c46561
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 S=
at, May 14, 2016 at 11:32 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:markzzzsmith@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-left:1px #ccc solid;padding-left:1ex"><span class=3D""><p dir=
=3D"ltr">The thing wrong with &quot;solving&quot; a layer 3 problem at laye=
r 2 is that it makes the effectiveness of the layer 3 outcome entirely depe=
ndent on the attributes of another layer. It&#39;s fundamentally a layer vi=
olation.<br></p></span>
<p dir=3D"ltr">I think we have layers to try to minimise or avoid these dep=
endencies. Having a layer 3 privacy solution to this layer 3 privacy proble=
m means that it doesn&#39;t matter if the layer 2 privacy is terrible or no=
t.</p></blockquote><div>Actually, it&#39;s the opposite: the reason we have=
 layers is so that layer X doesn&#39;t have to worry about reimplementing f=
unctionality provided by layer X-1.</div><div><br></div><div>If we were to =
follow your argument, we would implement CRC checks, packet retransmissions=
, and fragmentation into HTTP, because otherwise the reliability of HTTP wo=
uld be entirely dependent on the attributes of layers 2, 3, and 4. Guess wh=
at: the outcome of HTTP *is* entirely dependent on the link-layer not scram=
bling data, on on TCP dealing with packet reordering and packet loss by seq=
uencing and retransmitting, etc.</div></div></div></div>

--001a1148acd2fe0c850532c46561--


From nobody Fri May 13 19:47:11 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 262FE12D0B4 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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=-0.996, 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 pUdKne0QyLia for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:47:08 -0700 (PDT)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::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 A9BE312B01B for <ipv6@ietf.org>; Fri, 13 May 2016 19:47:08 -0700 (PDT)
Received: by mail-yw0-x22b.google.com with SMTP id j74so119062933ywg.1 for <ipv6@ietf.org>; Fri, 13 May 2016 19:47:08 -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=0yOoJSGrgaj4Aok9vY05pGw3JJ4nQH+Z4agPS4Dz72s=; b=Ev9D4C/Xgqjlj0+6izggdd9noSqkFVIzskrp36ryFzlYIsGKHCZyMo95O4bH9bsgWi hpNd2xxAz52aVj+qgKdfHIvriPbYUJyrXFZozNFuLtrxgY6krRiT+9uHgc1QNInnNwDZ y6cNDTnrg/MSML3C/P6QgWqOYBQpdUearkWEitpo6+kqkb7V7DaUYiuUF3aGyIXemUuE LqK/I3DZfumGg5RKXg++pI4Mnbj2wx8ItFeKDBQFJIL+8ddu97IvhnfbqlXsG3nztH1z Sw2njISTKND7HlJD1fLqB+ugbbBNraQJRl23IBsTia0+j6O6VeK1BVWsT5AQ7rnRcxW8 S5MQ==
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=0yOoJSGrgaj4Aok9vY05pGw3JJ4nQH+Z4agPS4Dz72s=; b=lqtyIbcsuWjfgC9hwqeYAm9pxWyREZgE6ZXDPSg8U7OPR++LLnv36O7Gns25wnfwEV rutHwx8AvZf7o/831A1yQXuNGuEsG9tAYhzIVw2U3DSH7nPBLg+XoGAvL3gMkQenk0OX 83FoHbldtADhWH1qzKmMtY0eLNBwt3Hheg/fWqc6YzRBr70Zq7U5nu907R7mikCNNUNE sILByTq22zDR3TGBryqe8BmjUUiJ6AwIkGK2IXrVAHXas9tN6/Ww4rf62NhWr7yFdkiZ gffgwTis42/noJ7ZW50ZMmy9licYhJFYos0KOxFLxz7EYey/31iiBiGUqSI1btBkxtAP E6Qw==
X-Gm-Message-State: AOPr4FW/iCTBi7e30MBIotrPdklYhyQoH0D+0E4BvohXK4e3B4DkDuOGGei73PcXXk34UT0Lb3mdKs+pBv5lxoel
X-Received: by 10.129.27.9 with SMTP id b9mr9122871ywb.173.1463194027896; Fri, 13 May 2016 19:47:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 13 May 2016 19:46:48 -0700 (PDT)
In-Reply-To: <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 14 May 2016 11:46:48 +0900
Message-ID: <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a1142a41a45bd4f0532c468ec
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ubDWR3KRVheWw0abkNf5GTlZG10>
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: Sat, 14 May 2016 02:47:10 -0000

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

On Sat, May 14, 2016 at 11:45 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > This explicitly prohibits an implementation from taking a random MAC
> > address and forming an EUI-64 address out of it.
>
> Which is a good thing, since otherwise a bad actor could correlate the
> layer 2 and layer 3 addresses, which is actually impossible with IPv4
> but a current weakness in IPv6.
>

And this is a weakness because...?

--001a1142a41a45bd4f0532c468ec
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 S=
at, May 14, 2016 at 11:45 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span =
class=3D"">&gt; This explicitly prohibits an implementation from taking a r=
andom MAC<br>
&gt; address and forming an EUI-64 address out of it.<br>
<br>
</span>Which is a good thing, since otherwise a bad actor could correlate t=
he<br>
layer 2 and layer 3 addresses, which is actually impossible with IPv4<br>
but a current weakness in IPv6.<br></blockquote><div><br>And this is a weak=
ness because...?=C2=A0</div></div></div></div>

--001a1142a41a45bd4f0532c468ec--


From nobody Fri May 13 19:59:45 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 723CF12B009 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:59:43 -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 QotXnxSm35y5 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 19:59:41 -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 AA31512B007 for <ipv6@ietf.org>; Fri, 13 May 2016 19:59:41 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id 206so48480789pfu.0 for <ipv6@ietf.org>; Fri, 13 May 2016 19:59:41 -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=gNdlnx9Q4xjRrhIfq4y0jWjNMdkH77hSzn4TvX8CICA=; b=AYmZX0JLA+Uc38M5jS7gKl1sNhFn5m3/LnChKv3u4b9HckeUjIQpMdnfnz450KaMsy mGuwji+GEgZo5532K9N4hIN48fasvTo/uO11Oq3Ko2o5cZbvyzgK1IeXnPWLs/IJnFTy TwVtGpnx55eO5dFo6AF6jjF6Tpa+Hoh3cY5pXbGOT5ez8pUX9UI8G9BbVmQNw4S3m5aK VjSTYso1GoRmeXYjPF8DecpYm9l+aBxHZF00T2anb8YGz/j/ReLL4x8UHEGBq1FmWsS7 hi2fDMEiKe+gCXXvKnOy+wwG/4tQ3GR8P4kkSJj5Br56nCea95a23DgNWJNVmRdV0qR9 bBzA==
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=gNdlnx9Q4xjRrhIfq4y0jWjNMdkH77hSzn4TvX8CICA=; b=CYQU75rxoU0Q0Mtt0qkLGRZUJculxqHUxxWoYN9soAUlp/aTt8zyDRheC4raBxp1CP uxSTlWmENbRACOYgRE09dM6QfCXFDd+Ao01Ita/vLko2oK/Yen4pJZ+Mt8lhZGeq3IeW 7WmKpIBq5tmrvfzSMZe77Ne24SSKduAMuPT879Ykd30xPU+xkzC4PwiqpoUUw8pUxUV1 wn4dQ8CTv/y7fNwmGt+LbaV5cbR4gOC2Jyxs3Bt6eVTyIbBXhGVJ2PbtTsl3NM5kMTcf 6AFD6kKNU/fRgqdGYTMzSLVIlrSo/P+5useLdoULwTOYFtia+iI3GdSvQi9ZFS30Vuo1 9f9w==
X-Gm-Message-State: AOPr4FWGVk9gAKtWLu3COrtn6xsY/SeN3o7qdvpIfMhtlva87tnUSOgNDojKfyL3DiV1zQ==
X-Received: by 10.98.100.71 with SMTP id y68mr28087240pfb.84.1463194781259; Fri, 13 May 2016 19:59:41 -0700 (PDT)
Received: from ?IPv6:2406:e007:56d8:1:28cc:dc4c:9703:6781? ([2406:e007:56d8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id y128sm30511395pfb.13.2016.05.13.19.59.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 19:59:40 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com>
Date: Sat, 14 May 2016 15:00:08 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/C73mE85PSU9SoX2pFfyCEnax1cU>
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: Sat, 14 May 2016 02:59:44 -0000

On 14/05/2016 14:46, Lorenzo Colitti wrote:
> On Sat, May 14, 2016 at 11:45 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>>> This explicitly prohibits an implementation from taking a random MAC
>>> address and forming an EUI-64 address out of it.
>>
>> Which is a good thing, since otherwise a bad actor could correlate the
>> layer 2 and layer 3 addresses, which is actually impossible with IPv4
>> but a current weakness in IPv6.
>>
> 
> And this is a weakness because...?

Because if someone is trying to correlate different types of my traffic,
let's say something sent over IPX and something sent over IPv6, the task
will be made easier if the lower 48 bits are the same in both types of
traffic. (Obviously, someone on-link can use ND to correlate MAC address
and IP address, so we're talking about someone observing off-link packets.)

Not that I use IPX, but that is one case where off-link packets definitely
contain the MAC address.

    Brian


From nobody Fri May 13 20:29:35 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 C1F7A12B053 for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 20:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 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=-0.996, 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 3HBXJkFXLehQ for <ipv6@ietfa.amsl.com>; Fri, 13 May 2016 20:29:32 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 1980212B02B for <ipv6@ietf.org>; Fri, 13 May 2016 20:29:32 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id o66so135199048ywc.3 for <ipv6@ietf.org>; Fri, 13 May 2016 20:29:32 -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=UvW6xsARcJGCC/ABTIppTgghv6Lpe8ubdQ5GVgdWoLg=; b=M+QsO5LzKUtxiHq3b0Uj8hmKi8nUJKow9qImLOUzEDIugmb4rxnOG0a9Z/bzq3aata 37+gapGsqOEm3z+ek5hm7R+IwVXnnOd3TJQVjPiOhPUI/g7p1f+dfJESp3ddQAzFp+p7 tGx23dX+QZIX9B09517Y3mfUsB36PdjwWGq2JBkt7dPodihiCDmbwTy5UfiCxk/Klzja 86idqQM7t4tLUg4weN2ibrPTdyXpOnp8ZSdunjO3Kw1Y5dUDWp8+ykAujjj0fFeovBSM U48WV3lOua3TohzrWDa4PXL+mkvo2WYKwpmuB2T5UDgxJ0GLXuhyR4u7s3FBH3cuISXJ 61JQ==
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=UvW6xsARcJGCC/ABTIppTgghv6Lpe8ubdQ5GVgdWoLg=; b=W6suxgFVOZ67sGyppJyDSN9ZIMry9erbbClJw5q0Mr1GZTtIcbcEBdAEG16Ar7/biD lZ6AUuBP49PtMGywKfLTq619XZB9lGh1rpgDMkHvuXb6Gndnq9GuXjvJjYmZ9pU0FRNU Q5ugsOyqJo7zw0dNGTmFI8ER0ZgS/cFXyRK7pS88TBEGo99M6DLLlvCJz/J+9UhKxOKp yXsEqouWRlRCJgR0jXeO920Q6eHrtsvR4qEAhzi0xmzmO/CIEHK8IPHIikowYTmkUezi BzHP6qC00tBZJVbIRxL0g+cWLLzomisJa2bfR+FN9LyqFKz0MbAlUHdCt8U70SNLzWGw 05Xg==
X-Gm-Message-State: AOPr4FVzfJCFOz12cb2W0CdLT3chsh2uudpUNJ0lZJrz7nXWSUNC7UZGCt9N9HGN9PpP5cQPX4ybZOOd4PEEUK7C
X-Received: by 10.13.220.69 with SMTP id f66mr10317991ywe.132.1463196571174; Fri, 13 May 2016 20:29:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 13 May 2016 20:29:11 -0700 (PDT)
In-Reply-To: <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 14 May 2016 12:29:11 +0900
Message-ID: <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c8dd1ea00532c4ffe5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zSSo32AobSD9gQsNVJOwChDutpk>
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: Sat, 14 May 2016 03:29:34 -0000

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

On Sat, May 14, 2016 at 12:00 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Because if someone is trying to correlate different types of my traffic,
> let's say something sent over IPX and something sent over IPv6, the task
> will be made easier if the lower 48 bits are the same in both types of
> traffic. (Obviously, someone on-link can use ND to correlate MAC address
> and IP address, so we're talking about someone observing off-link packets.)
>

That seems extremely unlikely to happen in practice, given that the vast
majority of hosts either don't have an IPX stack at all or have it disabled
by default, and embedding a MAC address in a protocol payload is not very
useful so people tend not to do it.

By contrast, here is one weakness that is pretty much mandated by this
draft as written: because addresses have to be stable, any remote attacker
anywhere on the Internet that ever exchanges a packet with that host can
track it every time the host visits the same network, *forever*, with no
recourse. Section 3 point 1.

Either we fix that or we stop asserting that this draft is motivated by
privacy considerations.

--94eb2c0815c8dd1ea00532c4ffe5
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 S=
at, May 14, 2016 at 12:00 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><=
div><span style=3D"color:rgb(34,34,34)">Because if someone is trying to cor=
relate different types of my traffic,</span><br></div></div>
let&#39;s say something sent over IPX and something sent over IPv6, the tas=
k<br>
will be made easier if the lower 48 bits are the same in both types of<br>
traffic. (Obviously, someone on-link can use ND to correlate MAC address<br=
>
and IP address, so we&#39;re talking about someone observing off-link packe=
ts.)<br></blockquote><div><br></div><div>That seems extremely unlikely to h=
appen in practice, given that the vast majority of hosts either don&#39;t h=
ave an IPX stack at all or have it disabled by default, and embedding a MAC=
 address in a protocol payload is not very useful so people tend not to do =
it.<br></div><div><br></div><div>By contrast, here is one weakness that is =
pretty much mandated by this draft as written: because addresses have to be=
 stable, any remote attacker anywhere on the Internet that ever exchanges a=
 packet with that host can track it every time the host visits the same net=
work, *forever*, with no recourse. Section 3 point 1.</div><div><br></div><=
div>Either we fix that or we stop asserting that this draft is motivated by=
 privacy considerations.</div></div></div></div>

--94eb2c0815c8dd1ea00532c4ffe5--


From nobody Sun May 15 03:04:47 2016
Return-Path: <talmi@marvell.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 9CEFC12D152; Sun, 15 May 2016 03:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 5rKgdxtz4QLy; Sun, 15 May 2016 03:04:44 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (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 5332B12D136; Sun, 15 May 2016 03:04:44 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4FA1vuj012922; Sun, 15 May 2016 03:04:39 -0700
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0b-0016f401.pphosted.com with ESMTP id 22x3hj1yk8-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 15 May 2016 03:04:39 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sun, 15 May 2016 13:04:36 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Sun, 15 May 2016 13:04:36 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>
Subject: L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQ==
Date: Sun, 15 May 2016 10:04:35 +0000
Message-ID: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
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: [10.4.102.210]
Content-Type: multipart/alternative; boundary="_000_eaf5cad817624c7a8758758aa058399bILEXCH02marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-15_04:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605150137
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FRWY6mACd_UZWuovrOJe3OYqs1k>
Cc: "spring@ietf.org" <spring@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: Sun, 15 May 2016 10:04:45 -0000

--_000_eaf5cad817624c7a8758758aa058399bILEXCH02marvellcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

[Apologies if this issue has been discussed before.]

According to draft-ietf-6man-segment-routing-header, an 'SR Segment Endpoin=
t Node' updates the Destination IP address.
Therefore, it must also update the Layer 4 Checksum, right?

I wonder if there is an upper bound on the size of the SRH. Otherwise, the =
L4 Checksum may be located in a pretty deep location.
Speaking from a chip vendor's perspective this may be a problem.

Thanks,
Tal Mizrahi.




--_000_eaf5cad817624c7a8758758aa058399bILEXCH02marvellcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0cm;
	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:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[Apologies if this issue has been discussed before.]=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">According to draft-ietf-6man-segment-routing-header,=
 an &#8216;SR Segment Endpoint Node&#8217; updates the Destination IP addre=
ss.
<o:p></o:p></p>
<p class=3D"MsoNormal">Therefore, it must also update the Layer 4 Checksum,=
 right?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I wonder if there is an upper bound on the size of t=
he SRH. Otherwise, the L4 Checksum may be located in a pretty deep location=
.
<o:p></o:p></p>
<p class=3D"MsoNormal">Speaking from a chip vendor&#8217;s perspective this=
 may be a problem.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Tal Mizrahi.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_eaf5cad817624c7a8758758aa058399bILEXCH02marvellcom_--


From nobody Sun May 15 11:06:54 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 231BA12D511; Sun, 15 May 2016 11:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.427
X-Spam-Level: 
X-Spam-Status: No, score=-3.427 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.426, SPF_PASS=-0.001] autolearn=ham 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 pXLfOZidThDp; Sun, 15 May 2016 11:06:49 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26B5012D129; Sun, 15 May 2016 11:06:48 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 455359CC7D; Sun, 15 May 2016 11:06:47 -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=EH/2uKbiZNT6T47Gz+Ug3EmXNlo=; b= OH/2lW0Ehmx9uFYF7OheObAb2QkAZFZJXKP9sNbWPEWZ9CD9vHK83KcCAhu6l/e5 V71Uld02Kh2f7YisUbYGMFeqhLNJi3ijdNxvuMqXsut1rSq0w32Myn4kZiHlOn/v 98hMaNmfjnkHnRN7W9nIptdhvvlrJKmYDXBqRKrPtYE=
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=kuAA9yZhhGSM81Ca8wdWBKSfZ9 SW6ydx9Vh8Mx9YxWsx/3SKWOnu8JhnqX6rucmakVblHklGWd+ZSwm43yAJhfdc4C baAyG/i0eAR3+U7DaVrArjNNDB4a90oCztOkZs44D2VIzc0VagjB9gSfCFZyTl/n rMPtyHASkm7mOExfY=
Received: from h.hanazo.no (77.16.5.38.tmi.telenormobil.no [77.16.5.38]) (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 E3CBA9CC4E; Sun, 15 May 2016 11:06:46 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 23D84167E7B6; Sun, 15 May 2016 20:06:38 +0200 (CEST)
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C20840B7-3E4A-4D72-98CA-E1E30531A0D6"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
Date: Sun, 15 May 2016 20:06:35 +0200
Message-Id: <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
To: Tal Mizrahi <talmi@marvell.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8HVImVsqkuKyGZ3Tpkchg18lTbQ>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Sun, 15 May 2016 18:06:51 -0000

--Apple-Mail=_C20840B7-3E4A-4D72-98CA-E1E30531A0D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Tal,

> [Apologies if this issue has been discussed before.]
>=20
> According to draft-ietf-6man-segment-routing-header, an =E2=80=98SR =
Segment Endpoint Node=E2=80=99 updates the Destination IP address.
> Therefore, it must also update the Layer 4 Checksum, right?
>=20
> I wonder if there is an upper bound on the size of the SRH. Otherwise, =
the L4 Checksum may be located in a pretty deep location.
> Speaking from a chip vendor=E2=80=99s perspective this may be a =
problem.

=46rom RFC2460, RH0:


      o  If the IPv6 packet contains a Routing header, the Destination
         Address used in the pseudo-header is that of the final
         destination.  At the originating node, that address will be in
         the last element of the Routing header; at the recipient(s),
         that address will be in the Destination Address field of the
         IPv6 header.

I would expect SR would work the same.

Cheers,
Ole


--Apple-Mail=_C20840B7-3E4A-4D72-98CA-E1E30531A0D6
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

iQEcBAEBCgAGBQJXOLqtAAoJED4aXnjSQuKWqN0H/3FPlB6LsDofJYZsVDXgTDtd
hjtet6iTrPxej9Wb3BA7/VKhpkzIlvVmeC4qvarPH6p48J8966ycsAl1GOcBfd4j
g4/tCz7xGx475rJ4FcwVVdAiRDfRO7RJr9QnQcXVgBsFFT4hDxtBFJI7LoT0x4mb
ptdi6HjjQrthNq58t/I2mEwrb7VnWZKul4X8hqYpNEAiiYPPuNkC4GB2AyODmTw/
Nz7dVc3xFL96n+j91oPbgbxGrtsqDuF+80HMKEhvoo9+oNgEzGA3KqacmuYdeWgK
KUVB3ujRYrsdEe0hBiaobGDHBiE3Pl6/DAzXOd9cE38wOE4ILf0i21UQnI/EGw4=
=8GVB
-----END PGP SIGNATURE-----

--Apple-Mail=_C20840B7-3E4A-4D72-98CA-E1E30531A0D6--


From nobody Sun May 15 23:11:46 2016
Return-Path: <weigengyu@bupt.edu.cn>
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 147D912D10A for <ipv6@ietfa.amsl.com>; Sun, 15 May 2016 23:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level: 
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, 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 LIhZiRbYn-Bf for <ipv6@ietfa.amsl.com>; Sun, 15 May 2016 23:11:42 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id EBD0712B019 for <ipv6@ietf.org>; Sun, 15 May 2016 23:11:41 -0700 (PDT)
Received: from mx1.bupt.edu.cn (unknown [127.0.0.1]) by mx1.bupt.edu.cn (AnyMacro(G7)) with SMTP id 8AE3A19F4D0 for <ipv6@ietf.org>; Mon, 16 May 2016 14:11:39 +0800 (HKT)
Received: from WeiGengyuPC (unknown [114.255.40.27]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id 1A65419F44E; Mon, 16 May 2016 14:11:38 +0800 (HKT)
Message-ID: <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Alissa Cooper" <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC>
In-Reply-To: <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
Date: Mon, 16 May 2016 14:11:38 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ARyXHrq23DyhVoUIZJOG--oSEh4>
Cc: 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, 16 May 2016 06:11:45 -0000

Hi all,

Is it not a problem to promote RFC7217 in which concept errors are existed?

RFC7217 did not only giving a definition of stable address, but also 
defining an algorithm to generate it.
The algorithm contains concept error in my opinion.

>
>        Title           : Recommendation on Stable IPv6 Interface 
> Identifiers
>        Authors         : Fernando Gont
>                          Alissa Cooper
>                          Dave Thaler
>                          Will Liu
> Filename        : draft-ietf-6man-default-iids-11.txt
> Pages           : 23
> Date            : 2016-04-27
>
> Abstract:
>   This document changes the default scheme for generating stable
>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>   recommends against embedding link-layer addresses in IPv6 Interface
>   Identifiers.


Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications

-----åŽŸå§‹é‚®ä»¶----- 
From: weigengyu
Sent: Monday, May 09, 2016 2:35 PM
To: Alissa Cooper
Cc: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt

Hiï¼Œ

> This document changes the default scheme for generating stable
   Interface Identifiers with SLAAC to that specified in RFC7217,

There is a question about RFC7217 as this draft is to promote it.
In RFC7217,  in Page 6 and page 7,  "5.  Algorithm Specification"
"1.  Compute a random (but stable) identifier with the expression:
       RID = F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key)
       Where:
       RID:
          Random (but stable) Identifier
       F():
          A pseudorandom function (PRF) that MUST NOT be computable from
          the outside (without knowledge of the secret key).  F() MUST
          also be difficult to reverse, such that it resists attempts to
          obtain the secret_key, even when given samples of the output
          of F() and knowledge or control of the other input parameters.
          F() SHOULD produce an output of at least 64 bits.  F() could
          be implemented as a cryptographic hash of the concatenation of
          each of the function parameters.  SHA-1 [FIPS-SHS] and SHA-256
          are two possible options for F().  Note: MD5 [RFC1321] is
          considered unacceptable for F() [RFC6151]. "

It seems it is a concept error for RID.
RID is not random or random identifier according to the context above.

F() is an inreverse function, not a pseudorandom function.
Within parameters of F(Prefix, Net_Iface, Network_ID, DAD_Counter,
secret_key),
only the secret_key is generated by a pseudorandom function.
But the secret_key is also a constant because it keeps unchanged after being
generated.

There are not random features.

The question is why it is called RID, Random ID?


Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----åŽŸå§‹é‚®ä»¶----- 
From: Alissa Cooper
Sent: Thursday, April 28, 2016 10:41 PM
To: IETF IPv6 Mailing List
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt

This version incorporates comments based on discussion before and during
IETF 95 (thanks to Fernando for spinning the rev). I think this version
addresses the comments received and should be ready to move forward.

Alissa


> On Apr 27, 2016, at 5:49 PM, 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           : Recommendation on Stable IPv6 Interface 
> Identifiers
>        Authors         : Fernando Gont
>                          Alissa Cooper
>                          Dave Thaler
>                          Will Liu
> Filename        : draft-ietf-6man-default-iids-11.txt
> Pages           : 23
> Date            : 2016-04-27
>
> Abstract:
>   This document changes the default scheme for generating stable
>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>   recommends against embedding 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, by removing the text in these RFCs
>   that required the IPv6 Interface Identifiers to be derived from the
>   underlying link-layer address, and replacing the aforementioned text
>   with a pointer to this document.  Additionally, this document updates
>   RFC3315 by specifying additional requirements on the generation of
>   Interface Identifiers used in Dynamic Host Configuration Protocol
>   version 6 (DHCPv6).  It also provides advice to system administrators
>   who employ manual configuration.  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-11
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-11
>
>
> 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
> --------------------------------------------------------------------

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


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



From nobody Sun May 15 23:21:37 2016
Return-Path: <talmi@marvell.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 072CA12D14B; Sun, 15 May 2016 23:21:33 -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 vXmwFJOLW6x4; Sun, 15 May 2016 23:21:31 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 C977312B017; Sun, 15 May 2016 23:21:31 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4G6HRSF003706; Sun, 15 May 2016 23:21:30 -0700
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0a-0016f401.pphosted.com with ESMTP id 22xc8c337j-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 15 May 2016 23:21:30 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 09:21:25 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 16 May 2016 09:21:25 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "otroan@employees.org" <otroan@employees.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAMTSCAAB/eFXA=
Date: Mon, 16 May 2016 06:21:25 +0000
Message-ID: <6ed6834bb1e343b287f0cc32428417ff@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
In-Reply-To: <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-16_02:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605160088
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0oJVarNxKOV1LmKywKaeVQkkFGY>
Cc: "spring@ietf.org" <spring@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: Mon, 16 May 2016 06:21:33 -0000

SGkgT2xlLA0KDQpUaGFua3MgZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuIA0KDQpJdCB3b3VsZCBi
ZSBoZWxwZnVsIGlmIHRoZSBhdXRob3JzIGFkZGVkIGEgY29tbWVudCBhYm91dCB0aGUgTDQgQ2hl
Y2tzdW0gdG8gdGhlIGN1cnJlbnQgZHJhZnQsIGV2ZW4gdGhvdWdoIHRoaXMgZnVuY3Rpb25hbGl0
eSB3YXMgZGVmaW5lZCBpbiBSRkMgMjQ2MC4NCg0KQmVzdCByZWdhcmRzLA0KVGFsLg0KDQo+LS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBvdHJvYW5AZW1wbG95ZWVzLm9yZyBbbWFp
bHRvOm90cm9hbkBlbXBsb3llZXMub3JnXQ0KPlNlbnQ6IFN1bmRheSwgTWF5IDE1LCAyMDE2IDk6
MDcgUE0NCj5UbzogVGFsIE1penJhaGkNCj5DYzogZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91
dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7IHNwcmluZ0BpZXRmLm9yZzsNCj42bWFuIFdHDQo+
U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2Vn
bWVudC1yb3V0aW5nLQ0KPmhlYWRlcg0KPg0KPlRhbCwNCj4NCj4+IFtBcG9sb2dpZXMgaWYgdGhp
cyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQgYmVmb3JlLl0NCj4+DQo+PiBBY2NvcmRpbmcgdG8g
ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSIFNlZ21lbnQN
Cj5FbmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQIGFkZHJlc3MuDQo+
PiBUaGVyZWZvcmUsIGl0IG11c3QgYWxzbyB1cGRhdGUgdGhlIExheWVyIDQgQ2hlY2tzdW0sIHJp
Z2h0Pw0KPj4NCj4+IEkgd29uZGVyIGlmIHRoZXJlIGlzIGFuIHVwcGVyIGJvdW5kIG9uIHRoZSBz
aXplIG9mIHRoZSBTUkguIE90aGVyd2lzZSwgdGhlIEw0DQo+Q2hlY2tzdW0gbWF5IGJlIGxvY2F0
ZWQgaW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlvbi4NCj4+IFNwZWFraW5nIGZyb20gYSBjaGlwIHZl
bmRvcuKAmXMgcGVyc3BlY3RpdmUgdGhpcyBtYXkgYmUgYSBwcm9ibGVtLg0KPg0KPkZyb20gUkZD
MjQ2MCwgUkgwOg0KPg0KPg0KPiAgICAgIG8gIElmIHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBh
IFJvdXRpbmcgaGVhZGVyLCB0aGUgRGVzdGluYXRpb24NCj4gICAgICAgICBBZGRyZXNzIHVzZWQg
aW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhhdCBvZiB0aGUgZmluYWwNCj4gICAgICAgICBkZXN0
aW5hdGlvbi4gIEF0IHRoZSBvcmlnaW5hdGluZyBub2RlLCB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBp
bg0KPiAgICAgICAgIHRoZSBsYXN0IGVsZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0
aGUgcmVjaXBpZW50KHMpLA0KPiAgICAgICAgIHRoYXQgYWRkcmVzcyB3aWxsIGJlIGluIHRoZSBE
ZXN0aW5hdGlvbiBBZGRyZXNzIGZpZWxkIG9mIHRoZQ0KPiAgICAgICAgIElQdjYgaGVhZGVyLg0K
Pg0KPkkgd291bGQgZXhwZWN0IFNSIHdvdWxkIHdvcmsgdGhlIHNhbWUuDQo+DQo+Q2hlZXJzLA0K
Pk9sZQ0KDQo=


From nobody Mon May 16 00:40:36 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 858A212B00D for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 00:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 hzW2cTGZcPuz for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 00:40:32 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::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 0728512B00C for <ipv6@ietf.org>; Mon, 16 May 2016 00:40:31 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id f66so203699512vkh.2 for <ipv6@ietf.org>; Mon, 16 May 2016 00:40: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:date:message-id:subject:from:to :cc; bh=xzw07h0WAbRn8l3jp919Mtc/3/XWnL5Z1nVOBIpbxgw=; b=GkexiNsbeYJXO9T66LRGoiDlW7Q4vnNuB3e+tVG1mCpixbhSLzdQSMyZEZFGQecNLV cg+dmVhPd6vt54Z9NuBwJ001v3WJu0u0JklR9bG2Q/ABZ/f/cWAOO6XOtAU4TFStrmLl rmGiRYjU7C0dOnyXJc1jzDdpTuxn1uBbJBQSXxcMBK1ZcWWvQkac9ggfeRd77FmRqVHS U5vir7BvNNbcPKRkvfGD3cQA66fH/qHqK4zztWYuAP1j2S3VD8Zp82/ymDUXYstEIj+H FjNKlgetF1nFWx6AE3F2fHPLJsg2pok7mmnmKtpN9kRFnfUhIwIWuV564vFC4xuvpRm6 60YA==
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:date :message-id:subject:from:to:cc; bh=xzw07h0WAbRn8l3jp919Mtc/3/XWnL5Z1nVOBIpbxgw=; b=kske12lmLdirvOzF2ZVklRyKUX0UFcCdn8s+qy5h72ZbOxVEWSs7F42S1c2VIqRNrT r9wy4xmmltySTBHvMSEeJOGn/yarBiaJH6nPu+ubvajL/El5tOAGwwTn2h/hMco5q6uh ErDiORpINYzolZUfDVkLDl0ObN4sGRyB/g9kiL1rPDiilCv7re5tyEGhKQ54JI2CFt84 raBwnBnQ3qVEgTF0BzJBTyT0n0i63KQWwG34IjDRjrqF+O58Jo/mhTSOEgrquLpAxuPi egHKY+JfljsKtwNVPa13aw7Vrbj/pZSYeIbT6Km1bTv+jBHnPGLld4xwXPE/KLO4Qkl5 ZIHA==
X-Gm-Message-State: AOPr4FWl4YoxnuAtxmiZKyKoDfeacUP3ozWQnse6zx1H2WQmZB9a0Zottscy5lPBnysVCx+E5coNnreiLpzekw==
MIME-Version: 1.0
X-Received: by 10.31.146.144 with SMTP id u138mr13961123vkd.2.1463384430989; Mon, 16 May 2016 00:40:30 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Mon, 16 May 2016 00:40:30 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Mon, 16 May 2016 00:40:30 -0700 (PDT)
In-Reply-To: <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC>
Date: Mon, 16 May 2016 17:40:30 +1000
Message-ID: <CAO42Z2zAjtPGuoU30hswFM+VM3M8VQb7hfx9VMX03e8W59pKNQ@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
From: Mark Smith <markzzzsmith@gmail.com>
To: weigengyu <weigengyu@bupt.edu.cn>
Content-Type: multipart/alternative; boundary=001a114374922dd9960532f0bde6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XfuGCyyD-oanN5gHYpe173LxcOk>
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, 16 May 2016 07:40:34 -0000

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

Hi,

Fernando would have usually popped in by now. As he hasn't, I'll have a go.

The IIDs in this RFC are random in comparison to MAC address derived ones.
MAC address derived ones have a structure and values that can be predicted.

The IIDs are stable in comparison to RFC4942  privacy addresses, that
change every 24 hours.

These addresses aren't meant to be an alternative to privacy addresses. A
host will likely have both, with privacy addresses preferred as source
addresses for outbound connections.

For cases where privacy addresses would cause issues because they change
relatively often, these addresses would be used eg. incoming (stable)
destination addresses for servers/services that are put in DNS (eg. HTTP
server), or router interface addresses, decoupling the router interface
address from the interface/line card MAC address, so that the interface
could be swapped (meaning new MAC address) without the router's IPv6
address charging.

Regards,
Mark.

On 9 May 2016 4:35 PM, "weigengyu" <weigengyu@bupt.edu.cn> wrote:
>
> Hi=EF=BC=8C
>
>
>> This document changes the default scheme for generating stable
>
>   Interface Identifiers with SLAAC to that specified in RFC7217,
>
> There is a question about RFC7217 as this draft is to promote it.
> In RFC7217,  in Page 6 and page 7,  "5.  Algorithm Specification"
> "1.  Compute a random (but stable) identifier with the expression:
>       RID =3D F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key)
>       Where:
>       RID:
>          Random (but stable) Identifier
>       F():
>          A pseudorandom function (PRF) that MUST NOT be computable from
>          the outside (without knowledge of the secret key).  F() MUST
>          also be difficult to reverse, such that it resists attempts to
>          obtain the secret_key, even when given samples of the output
>          of F() and knowledge or control of the other input parameters.
>          F() SHOULD produce an output of at least 64 bits.  F() could
>          be implemented as a cryptographic hash of the concatenation of
>          each of the function parameters.  SHA-1 [FIPS-SHS] and SHA-256
>          are two possible options for F().  Note: MD5 [RFC1321] is
>          considered unacceptable for F() [RFC6151]. "
>
> It seems it is a concept error for RID.
> RID is not random or random identifier according to the context above.
>
> F() is an inreverse function, not a pseudorandom function.
> Within parameters of F(Prefix, Net_Iface, Network_ID, DAD_Counter,
secret_key),
> only the secret_key is generated by a pseudorandom function.
> But the secret_key is also a constant because it keeps unchanged after
being generated.
>
> There are not random features.
>
> The question is why it is called RID, Random ID?
>
>
> Regards,
>
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Alissa Cooper
> Sent: Thursday, April 28, 2016 10:41 PM
> To: IETF IPv6 Mailing List
> Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
>
>
> This version incorporates comments based on discussion before and during
IETF 95 (thanks to Fernando for spinning the rev). I think this version
addresses the comments received and should be ready to move forward.
>
> Alissa
>
>
>> On Apr 27, 2016, at 5:49 PM, 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           : Recommendation on Stable IPv6 Interface
Identifiers
>>        Authors         : Fernando Gont
>>                          Alissa Cooper
>>                          Dave Thaler
>>                          Will Liu
>> Filename        : draft-ietf-6man-default-iids-11.txt
>> Pages           : 23
>> Date            : 2016-04-27
>>
>> Abstract:
>>   This document changes the default scheme for generating stable
>>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>>   recommends against embedding 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, by removing the text in these RFCs
>>   that required the IPv6 Interface Identifiers to be derived from the
>>   underlying link-layer address, and replacing the aforementioned text
>>   with a pointer to this document.  Additionally, this document updates
>>   RFC3315 by specifying additional requirements on the generation of
>>   Interface Identifiers used in Dynamic Host Configuration Protocol
>>   version 6 (DHCPv6).  It also provides advice to system administrators
>>   who employ manual configuration.  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-11
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-default-iids-11
>>
>>
>> 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
>> --------------------------------------------------------------------
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr">Hi,</p>
<p dir=3D"ltr">Fernando would have usually popped in by now. As he hasn&#39=
;t, I&#39;ll have a go.</p>
<p dir=3D"ltr">The IIDs in this RFC are random in comparison to MAC address=
 derived ones. MAC address derived ones have a structure and values that ca=
n be predicted.</p>
<p dir=3D"ltr">The IIDs are stable in comparison to RFC4942=C2=A0 privacy a=
ddresses, that change every 24 hours.</p>
<p dir=3D"ltr">These addresses aren&#39;t meant to be an alternative to pri=
vacy addresses. A host will likely have both, with privacy addresses prefer=
red as source addresses for outbound connections.</p>
<p dir=3D"ltr">For cases where privacy addresses would cause issues because=
 they change relatively often, these addresses would be used eg. incoming (=
stable) destination addresses for servers/services that are put in DNS (eg.=
 HTTP server), or router interface addresses, decoupling the router interfa=
ce address from the interface/line card MAC address, so that the interface =
could be swapped (meaning new MAC address) without the router&#39;s IPv6 ad=
dress charging.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">On 9 May 2016 4:35 PM, &quot;weigengyu&quot; &lt;<a href=3D"=
mailto:weigengyu@bupt.edu.cn">weigengyu@bupt.edu.cn</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi=EF=BC=8C<br>
&gt;<br>
&gt;<br>
&gt;&gt; This document changes the default scheme for generating stable<br>
&gt;<br>
&gt; =C2=A0 Interface Identifiers with SLAAC to that specified in RFC7217,<=
br>
&gt;<br>
&gt; There is a question about RFC7217 as this draft is to promote it.<br>
&gt; In RFC7217,=C2=A0 in Page 6 and page 7,=C2=A0 &quot;5.=C2=A0 Algorithm=
 Specification&quot;<br>
&gt; &quot;1.=C2=A0 Compute a random (but stable) identifier with the expre=
ssion:<br>
&gt; =C2=A0 =C2=A0 =C2=A0 RID =3D F(Prefix, Net_Iface, Network_ID, DAD_Coun=
ter, secret_key)<br>
&gt; =C2=A0 =C2=A0 =C2=A0 Where:<br>
&gt; =C2=A0 =C2=A0 =C2=A0 RID:<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Random (but stable) Identifier<br>
&gt; =C2=A0 =C2=A0 =C2=A0 F():<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0A pseudorandom function (PRF) that M=
UST NOT be computable from<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0the outside (without knowledge of th=
e secret key).=C2=A0 F() MUST<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0also be difficult to reverse, such t=
hat it resists attempts to<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0obtain the secret_key, even when giv=
en samples of the output<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0of F() and knowledge or control of t=
he other input parameters.<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0F() SHOULD produce an output of at l=
east 64 bits.=C2=A0 F() could<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0be implemented as a cryptographic ha=
sh of the concatenation of<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0each of the function parameters.=C2=
=A0 SHA-1 [FIPS-SHS] and SHA-256<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0are two possible options for F().=C2=
=A0 Note: MD5 [RFC1321] is<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0considered unacceptable for F() [RFC=
6151]. &quot;<br>
&gt;<br>
&gt; It seems it is a concept error for RID.<br>
&gt; RID is not random or random identifier according to the context above.=
<br>
&gt;<br>
&gt; F() is an inreverse function, not a pseudorandom function.<br>
&gt; Within parameters of F(Prefix, Net_Iface, Network_ID, DAD_Counter, sec=
ret_key),<br>
&gt; only the secret_key is generated by a pseudorandom function.<br>
&gt; But the secret_key is also a constant because it keeps unchanged after=
 being generated.<br>
&gt;<br>
&gt; There are not random features.<br>
&gt;<br>
&gt; The question is why it is called RID, Random ID?<br>
&gt;<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Gengyu WEI<br>
&gt; Network Technology Center<br>
&gt; School of Computer<br>
&gt; Beijing University of Posts and Telecommunications<br>
&gt; -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Alissa Cooper<br>
&gt; Sent: Thursday, April 28, 2016 10:41 PM<br>
&gt; To: IETF IPv6 Mailing List<br>
&gt; Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt<br>
&gt;<br>
&gt;<br>
&gt; This version incorporates comments based on discussion before and duri=
ng IETF 95 (thanks to Fernando for spinning the rev). I think this version =
addresses the comments received and should be ready to move forward.<br>
&gt;<br>
&gt; Alissa<br>
&gt;<br>
&gt;<br>
&gt;&gt; On Apr 27, 2016, at 5:49 PM, <a href=3D"mailto:internet-drafts@iet=
f.org">internet-drafts@ietf.org</a> wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; A New Internet-Draft is available from the on-line Internet-Drafts=
 directories.<br>
&gt;&gt; This draft is a work item of the IPv6 Maintenance of the IETF.<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0: Recommendation on Stable IPv6 Interface Identifiers<br>
&gt;&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: Fernando Gont<br>
&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=A0Alissa Cooper<br>
&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=A0Dave Thaler<br>
&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=A0Will Liu<br>
&gt;&gt; Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-ietf-6man-default-iids=
-11.txt<br>
&gt;&gt; Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: 23<br>
&gt;&gt; Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 2016-04-27<br>
&gt;&gt;<br>
&gt;&gt; Abstract:<br>
&gt;&gt; =C2=A0 This document changes the default scheme for generating sta=
ble<br>
&gt;&gt; =C2=A0 Interface Identifiers with SLAAC to that specified in RFC72=
17, and<br>
&gt;&gt; =C2=A0 recommends against embedding link-layer addresses in IPv6 I=
nterface<br>
&gt;&gt; =C2=A0 Identifiers.=C2=A0 It formally updates RFC2464, RFC2467, RF=
C2470, RFC2491,<br>
&gt;&gt; =C2=A0 RFC2492, RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC43=
38,<br>
&gt;&gt; =C2=A0 RFC4391, RFC5072, and RFC5121, by removing the text in thes=
e RFCs<br>
&gt;&gt; =C2=A0 that required the IPv6 Interface Identifiers to be derived =
from the<br>
&gt;&gt; =C2=A0 underlying link-layer address, and replacing the aforementi=
oned text<br>
&gt;&gt; =C2=A0 with a pointer to this document.=C2=A0 Additionally, this d=
ocument updates<br>
&gt;&gt; =C2=A0 RFC3315 by specifying additional requirements on the genera=
tion of<br>
&gt;&gt; =C2=A0 Interface Identifiers used in Dynamic Host Configuration Pr=
otocol<br>
&gt;&gt; =C2=A0 version 6 (DHCPv6).=C2=A0 It also provides advice to system=
 administrators<br>
&gt;&gt; =C2=A0 who employ manual configuration.=C2=A0 This document does n=
ot change any<br>
&gt;&gt; =C2=A0 existing recommendations concerning the use of temporary ad=
dresses as<br>
&gt;&gt; =C2=A0 specified in RFC 4941.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The IETF datatracker status page for this draft is:<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-defaul=
t-iids/">https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/</a>=
<br>
&gt;&gt;<br>
&gt;&gt; There&#39;s also a htmlized version available at:<br>
&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ietf-6man-default-iid=
s-11">https://tools.ietf.org/html/draft-ietf-6man-default-iids-11</a><br>
&gt;&gt;<br>
&gt;&gt; A diff from the previous version is available at:<br>
&gt;&gt; <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-def=
ault-iids-11">https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-default-i=
ids-11</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Please note that it may take a couple of minutes from the time of =
submission<br>
&gt;&gt; until the htmlized version and diff are available at <a href=3D"ht=
tp://tools.ietf.org">tools.ietf.org</a>.<br>
&gt;&gt;<br>
&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org=
/internet-drafts/</a><br>
&gt;&gt;<br>
&gt;&gt; ------------------------------------------------------------------=
--<br>
&gt;&gt; IETF IPv6 working group mailing list<br>
&gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/l=
istinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&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>
&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>

--001a114374922dd9960532f0bde6--


From nobody Mon May 16 01:59:00 2016
Return-Path: <sprevidi@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 A816612B034; Mon, 16 May 2016 01:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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.426, 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 k1sUMEe8H1sq; Mon, 16 May 2016 01:58:55 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9411612B030; Mon, 16 May 2016 01:58:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1602; q=dns/txt; s=iport; t=1463389135; x=1464598735; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=40wcBYMThDSXPHRV7cx/KiFPbKhVoH1M6+kEwzTN6Hs=; b=Mw76t6mk0UqdobDxS3PfVMbAwwMkc09GqtA/FIhp8K+eNVdOJbhSHcDJ kHEycNo2NwsCHUfA1RPhZYYhWGbXRCHM135dQHugi+R4VshgJiP2LLwOf Gn56C+T5lvJarDcxbYMjjqBHlGZR5ObkaqR3XK0QXe2mm/X1hgjuOVWLF Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BDAgAoizlX/4wNJK1egzeBUwa5YAENg?= =?us-ascii?q?XaGEQIcgQE4FAEBAQEBAQFlJ4RCAQEBAwEjEUUFCwIBCBgCAiYCAgIwFRABAQQ?= =?us-ascii?q?BDQWIJwisTJBRAQEBAQEBAQEBAQEBAQEBAQEBAQEBHIEBhSSBdoJXhD+DACuCL?= =?us-ascii?q?gEEkzCEdwGOHQqBX40whi2JEwEeAQFCg2xuhwd/AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,626,1454976000"; d="scan'208";a="273907936"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2016 08:58:54 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id u4G8ws9l013287 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 May 2016 08:58:54 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 04:58:53 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Mon, 16 May 2016 04:58:53 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: =?utf-8?B?T2xlIFRyw7hhbg==?= <otroan@employees.org>, Tal Mizrahi <talmi@marvell.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAa+DiAAB8pfIA=
Date: Mon, 16 May 2016 08:58:53 +0000
Message-ID: <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
In-Reply-To: <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.197.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <561024D8A5193A43A30ED01F989D02B1@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/e3vmi81OFj9eY4YhmEojfW44iAg>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 08:58:57 -0000

DQo+IE9uIE1heSAxNSwgMjAxNiwgYXQgODowNiBQTSwgb3Ryb2FuQGVtcGxveWVlcy5vcmcgd3Jv
dGU6DQo+IA0KPiBUYWwsDQo+IA0KPj4gW0Fwb2xvZ2llcyBpZiB0aGlzIGlzc3VlIGhhcyBiZWVu
IGRpc2N1c3NlZCBiZWZvcmUuXQ0KPj4gDQo+PiBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSIFNlZ21lbnQgRW5kcG9pbnQgTm9kZeKA
mSB1cGRhdGVzIHRoZSBEZXN0aW5hdGlvbiBJUCBhZGRyZXNzLg0KPj4gVGhlcmVmb3JlLCBpdCBt
dXN0IGFsc28gdXBkYXRlIHRoZSBMYXllciA0IENoZWNrc3VtLCByaWdodD8NCj4+IA0KPj4gSSB3
b25kZXIgaWYgdGhlcmUgaXMgYW4gdXBwZXIgYm91bmQgb24gdGhlIHNpemUgb2YgdGhlIFNSSC4g
T3RoZXJ3aXNlLCB0aGUgTDQgQ2hlY2tzdW0gbWF5IGJlIGxvY2F0ZWQgaW4gYSBwcmV0dHkgZGVl
cCBsb2NhdGlvbi4NCj4+IFNwZWFraW5nIGZyb20gYSBjaGlwIHZlbmRvcuKAmXMgcGVyc3BlY3Rp
dmUgdGhpcyBtYXkgYmUgYSBwcm9ibGVtLg0KPiANCj4gRnJvbSBSRkMyNDYwLCBSSDA6DQo+IA0K
PiANCj4gICAgICBvICBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFpbnMgYSBSb3V0aW5nIGhlYWRl
ciwgdGhlIERlc3RpbmF0aW9uDQo+ICAgICAgICAgQWRkcmVzcyB1c2VkIGluIHRoZSBwc2V1ZG8t
aGVhZGVyIGlzIHRoYXQgb2YgdGhlIGZpbmFsDQo+ICAgICAgICAgZGVzdGluYXRpb24uICBBdCB0
aGUgb3JpZ2luYXRpbmcgbm9kZSwgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4NCj4gICAgICAgICB0
aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5nIGhlYWRlcjsgYXQgdGhlIHJlY2lwaWVudChz
KSwNCj4gICAgICAgICB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBpbiB0aGUgRGVzdGluYXRpb24gQWRk
cmVzcyBmaWVsZCBvZiB0aGUNCj4gICAgICAgICBJUHY2IGhlYWRlci4NCj4gDQo+IEkgd291bGQg
ZXhwZWN0IFNSIHdvdWxkIHdvcmsgdGhlIHNhbWUuDQoNCg0KZXhhY3RseS4NCg0KTW9yZW92ZXIs
IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMgZW5jYXBzdWxh
dGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLg0KDQpzLg0KDQoN
Cj4gDQo+IENoZWVycywNCj4gT2xlDQo+IA0KDQo=


From nobody Mon May 16 02:01:01 2016
Return-Path: <sprevidi@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 8E12912B02A; Mon, 16 May 2016 02:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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.426, 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 6KYS-MzFvC0j; Mon, 16 May 2016 02:00:51 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADA7128E19; Mon, 16 May 2016 02:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2706; q=dns/txt; s=iport; t=1463389251; x=1464598851; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1BwkcvdxGdqq8UboN01zHz9wH7bE7ZMAT08xB16GAo4=; b=S5pJ4Z/lvLw65/8TcYXKrsgF8bVQ4XJPC2Ww0+TyN4NhlZ/mjgc5f3Yy ZeKC6oDpBgRLIUhm1dPtcuXRQFoUsbob7qh5f+/3m1hb2ME8jQ+KIMfYl vaYEtIEvgK4wDti0Q1culbb+HGHYPknfCpYRyUKWznT8AJif+/Q+AV2m3 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BDAgBLizlX/5hdJa1egzeBUwa5YAENg?= =?us-ascii?q?XaGEQIcgQE4FAEBAQEBAQFlJ4RCAQEBAwEjEUUFBwQCAQgRBAEBAQICIwMCAgI?= =?us-ascii?q?wFAEICAEBBA4FiCcIrEyQUgEBAQEBAQEBAQEBAQEBAQEBAQEBARyBAYUkgXaCV?= =?us-ascii?q?4Q/gwArgi4BBJgnAY4dgWmET4MqhTeGLYkTAR4BAUKDbG6HB38BAQE?=
X-IronPort-AV: E=Sophos;i="5.24,626,1454976000"; d="scan'208";a="104699737"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2016 09:00:50 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u4G90o1v014714 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 May 2016 09:00:50 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 05:00:49 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Mon, 16 May 2016 05:00:49 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAa+DiAABmp7IAABZDZgA==
Date: Mon, 16 May 2016 09:00:49 +0000
Message-ID: <B91DAD4F-6EC0-4F3D-A696-35B698B81D46@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <6ed6834bb1e343b287f0cc32428417ff@IL-EXCH02.marvell.com>
In-Reply-To: <6ed6834bb1e343b287f0cc32428417ff@IL-EXCH02.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.197.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4C17617FAE8A0D4784980607D02F72E1@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yW8doOF-wv8U3CA9NtLHfR-HlA8>
Cc: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 09:01:00 -0000

DQo+IE9uIE1heSAxNiwgMjAxNiwgYXQgODoyMSBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZl
bGwuY29tPiB3cm90ZToNCj4gDQo+IEhpIE9sZSwNCj4gDQo+IFRoYW5rcyBmb3IgdGhlIHByb21w
dCByZXNwb25zZS4gDQo+IA0KPiBJdCB3b3VsZCBiZSBoZWxwZnVsIGlmIHRoZSBhdXRob3JzIGFk
ZGVkIGEgY29tbWVudCBhYm91dCB0aGUgTDQgQ2hlY2tzdW0gdG8gdGhlIGN1cnJlbnQgZHJhZnQs
IGV2ZW4gdGhvdWdoIHRoaXMgZnVuY3Rpb25hbGl0eSB3YXMgZGVmaW5lZCBpbiBSRkMgMjQ2MC4N
Cg0KDQpwbGVhc2UgcmVhZCBjYXJlZnVsbHkgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGlu
Zy1oZWFkZXIuDQoNClRoZSBtb2RlbCBkZXNjcmliZWQgYXNzdW1lcyBlbmNhcHN1bGF0aW9uIG9m
IHRoZSBvcmlnaW5hbCBwYWNrZXQgaW50byBhbiBvdXRlciBpcHY2IGhlYWRlciBmb2xsb3dlZCBi
eSBhIFNSSC4gV2hlbiB0aGUgcGFja2V0IGxlYXZlcyB0aGUgU1IgdHVubmVsIHRoZXJlIGFyZSBu
byB0cmFjZXMgb2Ygc2VnbWVudCByb3V0aW5nIHdoYXRzb2V2ZXIuIEw0IGNsZWFybHkgZG9lcyBu
b3QgYXBwbHkgaGVyZSwgaXTigJlzIGJhc2ljIHR1bm5lbGluZy4NCg0Kcy4NCg0KDQo+IA0KPiBC
ZXN0IHJlZ2FyZHMsDQo+IFRhbC4NCj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
Pj4gRnJvbTogb3Ryb2FuQGVtcGxveWVlcy5vcmcgW21haWx0bzpvdHJvYW5AZW1wbG95ZWVzLm9y
Z10NCj4+IFNlbnQ6IFN1bmRheSwgTWF5IDE1LCAyMDE2IDk6MDcgUE0NCj4+IFRvOiBUYWwgTWl6
cmFoaQ0KPj4gQ2M6IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xz
LmlldGYub3JnOyBzcHJpbmdAaWV0Zi5vcmc7DQo+PiA2bWFuIFdHDQo+PiBTdWJqZWN0OiBSZTog
W3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmct
DQo+PiBoZWFkZXINCj4+IA0KPj4gVGFsLA0KPj4gDQo+Pj4gW0Fwb2xvZ2llcyBpZiB0aGlzIGlz
c3VlIGhhcyBiZWVuIGRpc2N1c3NlZCBiZWZvcmUuXQ0KPj4+IA0KPj4+IEFjY29yZGluZyB0byBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciwgYW4g4oCYU1IgU2VnbWVudA0K
Pj4gRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVzIHRoZSBEZXN0aW5hdGlvbiBJUCBhZGRyZXNzLg0K
Pj4+IFRoZXJlZm9yZSwgaXQgbXVzdCBhbHNvIHVwZGF0ZSB0aGUgTGF5ZXIgNCBDaGVja3N1bSwg
cmlnaHQ/DQo+Pj4gDQo+Pj4gSSB3b25kZXIgaWYgdGhlcmUgaXMgYW4gdXBwZXIgYm91bmQgb24g
dGhlIHNpemUgb2YgdGhlIFNSSC4gT3RoZXJ3aXNlLCB0aGUgTDQNCj4+IENoZWNrc3VtIG1heSBi
ZSBsb2NhdGVkIGluIGEgcHJldHR5IGRlZXAgbG9jYXRpb24uDQo+Pj4gU3BlYWtpbmcgZnJvbSBh
IGNoaXAgdmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0uDQo+PiAN
Cj4+IEZyb20gUkZDMjQ2MCwgUkgwOg0KPj4gDQo+PiANCj4+ICAgICBvICBJZiB0aGUgSVB2NiBw
YWNrZXQgY29udGFpbnMgYSBSb3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9uDQo+PiAgICAg
ICAgQWRkcmVzcyB1c2VkIGluIHRoZSBwc2V1ZG8taGVhZGVyIGlzIHRoYXQgb2YgdGhlIGZpbmFs
DQo+PiAgICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3JpZ2luYXRpbmcgbm9kZSwgdGhhdCBh
ZGRyZXNzIHdpbGwgYmUgaW4NCj4+ICAgICAgICB0aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0
aW5nIGhlYWRlcjsgYXQgdGhlIHJlY2lwaWVudChzKSwNCj4+ICAgICAgICB0aGF0IGFkZHJlc3Mg
d2lsbCBiZSBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVzcyBmaWVsZCBvZiB0aGUNCj4+ICAgICAg
ICBJUHY2IGhlYWRlci4NCj4+IA0KPj4gSSB3b3VsZCBleHBlY3QgU1Igd291bGQgd29yayB0aGUg
c2FtZS4NCj4+IA0KPj4gQ2hlZXJzLA0KPj4gT2xlDQo+IA0KDQo=


From nobody Mon May 16 02:29:12 2016
Return-Path: <talmi@marvell.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 1506A128E19; Mon, 16 May 2016 02:29:11 -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=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 uniFXC17PJ92; Mon, 16 May 2016 02:29:09 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (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 B101412B064; Mon, 16 May 2016 02:29:09 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4G93EX3017203; Mon, 16 May 2016 02:04:03 -0700
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0b-0016f401.pphosted.com with ESMTP id 22x3hj4a3p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 16 May 2016 02:04:03 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 12:04:00 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 16 May 2016 12:04:00 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, =?utf-8?B?T2xlIFRyw7hhbg==?= <otroan@employees.org>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAMTSCAAB8pyYAABk9dsA==
Date: Mon, 16 May 2016 09:04:00 +0000
Message-ID: <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com>
In-Reply-To: <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-16_03:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605160128
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WoLY2fejLk-z2PnwPubZWflKVG0>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 09:29:11 -0000

SGkgU3RlZmFubywNCg0KVGhhbmtzIGZvciB0aGUgcmVzcG9uc2VzLg0KDQo+ZXhhY3RseS4NCj4N
Cj5Nb3Jlb3ZlciwgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIgYXNzdW1l
cyBlbmNhcHN1bGF0aW9uDQo+c28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVy
ZS4NCj4NCj5zLg0KDQpUd28gcXVlc3Rpb25zOg0KMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlv
biBpcyBWWExBTj8gTDQgd291bGQgc3RpbGwgYmUgaW52b2x2ZWQsIHJpZ2h0Pw0KMi4gV2hlbiB5
b3Ugc2F5ICdhc3N1bWVzIGVuY2Fwc3VsYXRpb24nLCBkb2VzIGl0IG1lYW4gdGhhdCBhIGhvc3Qg
Y2Fubm90IHNlbmQgYW4gSVB2NiBwYWNrZXQgd2l0aCBhbiBTUkg/IFRoZSBjdXJyZW50IGRyYWZ0
IHNheXM6DQoNCiAgIEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFueSBub2RlIG9yaWdpbmF0aW5n
IGFuIElQdjYgcGFja2V0IHdpdGggaXRzDQogICBJUHY2IGFuZCBTZWdtZW50IFJvdXRpbmcgSGVh
ZGVycy4gIFRoaXMgaW5jbHVkZSBlaXRoZXI6DQoNCiAgICAgIEEgaG9zdCBvcmlnaW5hdGluZyBh
biBJUHY2IHBhY2tldC4NCg0KICAgICAgQW4gU1IgZG9tYWluIGluZ3Jlc3Mgcm91dGVyIGVuY2Fw
c3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldA0KICAgICAgaW50byBhbiBvdXRlciBJUHY2
IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguDQoNCg0KDQpXaWxsIGFwcHJlY2lhdGUgaWYgeW91
IGNhbiBjbGFyaWZ5IHRoYXQuDQoNClRoYW5rcywNClRhbC4NCg0KPi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJl
dmlkaUBjaXNjby5jb21dDQo+U2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYgMTE6NTkgQU0NCj5U
bzogT2xlIFRyw7hhbjsgVGFsIE1penJhaGkNCj5DYzogZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7IHNwcmluZ0BpZXRmLm9yZzsNCj42bWFuIFdH
DQo+U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLQ0KPmhlYWRlcg0KPg0KPg0KPj4gT24gTWF5IDE1LCAyMDE2LCBhdCA4
OjA2IFBNLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+DQo+PiBUYWwsDQo+Pg0KPj4+
IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQgYmVmb3JlLl0NCj4+
Pg0KPj4+IEFjY29yZGluZyB0byBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRl
ciwgYW4g4oCYU1IgU2VnbWVudA0KPkVuZHBvaW50IE5vZGXigJkgdXBkYXRlcyB0aGUgRGVzdGlu
YXRpb24gSVAgYWRkcmVzcy4NCj4+PiBUaGVyZWZvcmUsIGl0IG11c3QgYWxzbyB1cGRhdGUgdGhl
IExheWVyIDQgQ2hlY2tzdW0sIHJpZ2h0Pw0KPj4+DQo+Pj4gSSB3b25kZXIgaWYgdGhlcmUgaXMg
YW4gdXBwZXIgYm91bmQgb24gdGhlIHNpemUgb2YgdGhlIFNSSC4gT3RoZXJ3aXNlLCB0aGUNCj5M
NCBDaGVja3N1bSBtYXkgYmUgbG9jYXRlZCBpbiBhIHByZXR0eSBkZWVwIGxvY2F0aW9uLg0KPj4+
IFNwZWFraW5nIGZyb20gYSBjaGlwIHZlbmRvcuKAmXMgcGVyc3BlY3RpdmUgdGhpcyBtYXkgYmUg
YSBwcm9ibGVtLg0KPj4NCj4+IEZyb20gUkZDMjQ2MCwgUkgwOg0KPj4NCj4+DQo+PiAgICAgIG8g
IElmIHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBhIFJvdXRpbmcgaGVhZGVyLCB0aGUgRGVzdGlu
YXRpb24NCj4+ICAgICAgICAgQWRkcmVzcyB1c2VkIGluIHRoZSBwc2V1ZG8taGVhZGVyIGlzIHRo
YXQgb2YgdGhlIGZpbmFsDQo+PiAgICAgICAgIGRlc3RpbmF0aW9uLiAgQXQgdGhlIG9yaWdpbmF0
aW5nIG5vZGUsIHRoYXQgYWRkcmVzcyB3aWxsIGJlIGluDQo+PiAgICAgICAgIHRoZSBsYXN0IGVs
ZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMpLA0KPj4gICAg
ICAgICB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVzcyBmaWVs
ZCBvZiB0aGUNCj4+ICAgICAgICAgSVB2NiBoZWFkZXIuDQo+Pg0KPj4gSSB3b3VsZCBleHBlY3Qg
U1Igd291bGQgd29yayB0aGUgc2FtZS4NCj4NCj4NCj5leGFjdGx5Lg0KPg0KPk1vcmVvdmVyLCBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVzIGVuY2Fwc3VsYXRp
b24NCj5zbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLg0KPg0KPnMuDQo+
DQo+DQo+Pg0KPj4gQ2hlZXJzLA0KPj4gT2xlDQo+Pg0KDQo=


From nobody Mon May 16 04:13:17 2016
Return-Path: <sprevidi@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 2042D12D13E; Mon, 16 May 2016 04:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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.426, 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 LmevwZRe7qWA; Mon, 16 May 2016 04:13:14 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 620EA12D13C; Mon, 16 May 2016 04:13:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4418; q=dns/txt; s=iport; t=1463397194; x=1464606794; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=mw0wd6KH1JgmK7K8/Ju/HsAw5MeRqHW3QvfHAS/sMfE=; b=iRqEuLoU9hiVv6oIKconhHZkSkjIkRKtM0mUXe5NLiID+pASUX/+ySFB 9PN3K3tuxfGrC0OEtN5FQ+69mfxwCWm0/fIBIu3fFj4E1Btnrq5sMJEL4 nCZs0RREU3+zstMGQaHPnoQk5I2maBk8DaDOqDgtEWzY7ZxgX5G4ppRfd A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BFAgCdqjlX/5hdJa1dgzeBUwa5YAENg?= =?us-ascii?q?XaGEQIcgQU4FAEBAQEBAQFlJ4RCAQEBAwEjEUUFBwQCAQgRBAEBAQICERIDAgI?= =?us-ascii?q?CMBQBCAgBAQQOBYgnCK0AkFkBAQEBAQEBAQEBAQEBAQEBAQEBAQEcgQGFJIF2g?= =?us-ascii?q?leEViiCQSuCLgWTMIR3AY4dgWmNMIYtiRMBHgEBQoNsbocHfwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.24,627,1454976000"; d="scan'208";a="273954033"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 May 2016 11:13:13 +0000
Received: from XCH-RTP-008.cisco.com (xch-rtp-008.cisco.com [64.101.220.148]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u4GBDDOT008979 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 May 2016 11:13:13 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-008.cisco.com (64.101.220.148) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 07:13:12 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Mon, 16 May 2016 07:13:12 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAa+DiAAB8pfIAAAC4LAAAEgrGA
Date: Mon, 16 May 2016 11:13:12 +0000
Message-ID: <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com>
In-Reply-To: <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.197.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <34BA5EBA958F084CB5EB9CA9C3211F27@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DtNeAdHV529yKfKzA7GS45I5CEI>
Cc: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 11:13:16 -0000

SGksDQoNCk9uIE1heSAxNiwgMjAxNiwgYXQgMTE6MDQgQU0sIFRhbCBNaXpyYWhpIDx0YWxtaUBt
YXJ2ZWxsLmNvbT4gd3JvdGU6DQo+IA0KPiBIaSBTdGVmYW5vLA0KPiANCj4gVGhhbmtzIGZvciB0
aGUgcmVzcG9uc2VzLg0KPiANCj4+IGV4YWN0bHkuDQo+PiANCj4+IE1vcmVvdmVyLCBkcmFmdC1p
ZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVzIGVuY2Fwc3VsYXRpb24NCj4+
IHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+PiANCj4+IHMuDQo+
IA0KPiBUd28gcXVlc3Rpb25zOg0KPiAxLiBXaGF0IGlmIHRoZSBlbmNhcHN1bGF0aW9uIGlzIFZY
TEFOPyBMNCB3b3VsZCBzdGlsbCBiZSBpbnZvbHZlZCwgcmlnaHQ/DQoNCg0KU2VlIGJlbG93Lg0K
DQoNCj4gMi4gV2hlbiB5b3Ugc2F5ICdhc3N1bWVzIGVuY2Fwc3VsYXRpb24nLCBkb2VzIGl0IG1l
YW4gdGhhdCBhIGhvc3QgY2Fubm90IHNlbmQgYW4gSVB2NiBwYWNrZXQgd2l0aCBhbiBTUkg/IFRo
ZSBjdXJyZW50IGRyYWZ0IHNheXM6DQo+IA0KPiAgIEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFu
eSBub2RlIG9yaWdpbmF0aW5nIGFuIElQdjYgcGFja2V0IHdpdGggaXRzDQo+ICAgSVB2NiBhbmQg
U2VnbWVudCBSb3V0aW5nIEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0aGVyOg0KPiANCj4gICAg
ICBBIGhvc3Qgb3JpZ2luYXRpbmcgYW4gSVB2NiBwYWNrZXQuDQo+IA0KPiAgICAgIEFuIFNSIGRv
bWFpbiBpbmdyZXNzIHJvdXRlciBlbmNhcHN1bGF0aW5nIGEgcmVjZWl2ZWQgSVB2NiBwYWNrZXQN
Cj4gICAgICBpbnRvIGFuIG91dGVyIElQdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4NCj4g
DQo+IA0KPiANCj4gV2lsbCBhcHByZWNpYXRlIGlmIHlvdSBjYW4gY2xhcmlmeSB0aGF0Lg0KDQoN
Cm9rLCB0d28gY2FzZXM6DQoNCjEuIHRoZSBTUkggaXMgaW5zZXJ0ZWQgYXQgdGhlIHNvdXJjZS4g
DQogICB0aGUgc291cmNlIG9yaWdpbmF0ZXMgdGhlIHBhY2tldCwgdGhlIGlwdjYgaGVhZGVyIGFu
ZCANCiAgIHRoZSBTUkguIFRoZSBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tzdW0gdGFraW5nIGlu
dG8gDQogICBhY2NvdW50IHRoZSB3aG9sZSBJUHY2K1NSSC4gSGVyZSwgdGhlcmVz4oCZIG5vdGhp
bmcgbmV3IA0KICAgY29tcGFyZWQgdG8gcmZjMjQ2MC4NCg0KMi4gdGhlIFNSSCBpcyBvcmlnaW5h
dGVkIGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRvbWFpbi4NCiAgIFRoaXMgaXMgZG9u
ZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyIA0KICAgKGFkZGl0aW9u
YWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMyANCiAgIGVuY2Fw
c3VsYXRpb24gYW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSANCiAgIHBh
Y2tldCBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbiANCiAgIChp
bmNsdWRpbmcgdGhlIFNSSCkgaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51ZXMgDQog
ICBpdHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFwcGVuZWQuDQoNCnMuDQoNCg0KPiANCj4gVGhh
bmtzLA0KPiBUYWwuDQo+IA0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206
IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0K
Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYgMTE6NTkgQU0NCj4+IFRvOiBPbGUgVHLDuGFu
OyBUYWwgTWl6cmFoaQ0KPj4gQ2M6IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVh
ZGVyQHRvb2xzLmlldGYub3JnOyBzcHJpbmdAaWV0Zi5vcmc7DQo+PiA2bWFuIFdHDQo+PiBTdWJq
ZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50
LXJvdXRpbmctDQo+PiBoZWFkZXINCj4+IA0KPj4gDQo+Pj4gT24gTWF5IDE1LCAyMDE2LCBhdCA4
OjA2IFBNLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+PiANCj4+PiBUYWwsDQo+Pj4g
DQo+Pj4+IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQgYmVmb3Jl
Ll0NCj4+Pj4gDQo+Pj4+IEFjY29yZGluZyB0byBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0
aW5nLWhlYWRlciwgYW4g4oCYU1IgU2VnbWVudA0KPj4gRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVz
IHRoZSBEZXN0aW5hdGlvbiBJUCBhZGRyZXNzLg0KPj4+PiBUaGVyZWZvcmUsIGl0IG11c3QgYWxz
byB1cGRhdGUgdGhlIExheWVyIDQgQ2hlY2tzdW0sIHJpZ2h0Pw0KPj4+PiANCj4+Pj4gSSB3b25k
ZXIgaWYgdGhlcmUgaXMgYW4gdXBwZXIgYm91bmQgb24gdGhlIHNpemUgb2YgdGhlIFNSSC4gT3Ro
ZXJ3aXNlLCB0aGUNCj4+IEw0IENoZWNrc3VtIG1heSBiZSBsb2NhdGVkIGluIGEgcHJldHR5IGRl
ZXAgbG9jYXRpb24uDQo+Pj4+IFNwZWFraW5nIGZyb20gYSBjaGlwIHZlbmRvcuKAmXMgcGVyc3Bl
Y3RpdmUgdGhpcyBtYXkgYmUgYSBwcm9ibGVtLg0KPj4+IA0KPj4+IEZyb20gUkZDMjQ2MCwgUkgw
Og0KPj4+IA0KPj4+IA0KPj4+ICAgICBvICBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFpbnMgYSBS
b3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9uDQo+Pj4gICAgICAgIEFkZHJlc3MgdXNlZCBp
biB0aGUgcHNldWRvLWhlYWRlciBpcyB0aGF0IG9mIHRoZSBmaW5hbA0KPj4+ICAgICAgICBkZXN0
aW5hdGlvbi4gIEF0IHRoZSBvcmlnaW5hdGluZyBub2RlLCB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBp
bg0KPj4+ICAgICAgICB0aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5nIGhlYWRlcjsgYXQg
dGhlIHJlY2lwaWVudChzKSwNCj4+PiAgICAgICAgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4gdGhl
IERlc3RpbmF0aW9uIEFkZHJlc3MgZmllbGQgb2YgdGhlDQo+Pj4gICAgICAgIElQdjYgaGVhZGVy
Lg0KPj4+IA0KPj4+IEkgd291bGQgZXhwZWN0IFNSIHdvdWxkIHdvcmsgdGhlIHNhbWUuDQo+PiAN
Cj4+IA0KPj4gZXhhY3RseS4NCj4+IA0KPj4gTW9yZW92ZXIsIGRyYWZ0LWlldGYtNm1hbi1zZWdt
ZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMgZW5jYXBzdWxhdGlvbg0KPj4gc28gY2xlYXJseSB0
aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS4NCj4+IA0KPj4gcy4NCj4+IA0KPj4gDQo+Pj4g
DQo+Pj4gQ2hlZXJzLA0KPj4+IE9sZQ0KPj4+IA0KPiANCg0K


From nobody Mon May 16 04:19:58 2016
Return-Path: <talmi@marvell.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 0BBEF12D149; Mon, 16 May 2016 04:19:56 -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 siS_aUSdvEgr; Mon, 16 May 2016 04:19:54 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 AEE5C127058; Mon, 16 May 2016 04:19:54 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4GBBnBv015856; Mon, 16 May 2016 04:19:51 -0700
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0a-0016f401.pphosted.com with ESMTP id 22xc8c3rrx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 16 May 2016 04:19:51 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 14:19:47 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 16 May 2016 14:19:47 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAMTSCAAB8pyYAABk9dsP//8wwA///NLLA=
Date: Mon, 16 May 2016 11:19:46 +0000
Message-ID: <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com>
In-Reply-To: <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-16_05:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605160157
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/eNhG7rTvNJTbD4gd2Hsb26OR7CA>
Cc: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 11:19:56 -0000

SGkgU3RlZmFubywNCg0KVGhhbmtzIGFnYWluIGZvciB0aGUgcHJvbXB0IHJlc3BvbnNlLg0KDQo+
Mi4gdGhlIFNSSCBpcyBvcmlnaW5hdGVkIGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRv
bWFpbi4NCj4gICBUaGlzIGlzIGRvbmUgYnkgZW5jYXBzdWxhdGluZyB0aGUgcGFja2V0IGludG8g
YSBvdXRlcg0KPiAgIChhZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkgu
IFRoaXMgaXMgTDMNCj4gICBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZv
bHZlZC4gV2hlbiB0aGUNCj4gICBwYWNrZXQgbGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVy
IGVuY2Fwc3VsYXRpb24NCj4gICAoaW5jbHVkaW5nIHRoZSBTUkgpIGlzIHJlbW92ZWQgYW5kIHRo
ZSBwYWNrZXQgY29udGludWVzDQo+ICAgaXRzIGpvdXJuZXkgbGlrZSBub3RoaW5nIGhhcHBlbmVk
Lg0KDQpTbyBWWExBTiBpcyBvZmYgdGhlIHRhYmxlPyBJdCB3b3VsZCBiZSB3b3J0aHdoaWxlIHRv
IGNsYXJpZnkgdGhpcyBpbiB0aGUgZHJhZnQuIElmIHlvdSBoYXZlIGEgc3BlY2lmaWMgZW5jYXBz
dWxhdGlvbiBpbiBtaW5kLCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUgZHJhZnQgd291bGQgc3Bl
Y2lmeSBpdC4NCg0KVGhhbmtzLA0KVGFsLg0KDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPkZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lz
Y28uY29tXQ0KPlNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MTMgUE0NCj5UbzogVGFsIE1p
enJhaGkNCj5DYzogT2xlIFRyw7hhbjsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1o
ZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+c3ByaW5nQGlldGYub3JnOyA2bWFuIFdHDQo+U3ViamVj
dDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1y
b3V0aW5nLQ0KPmhlYWRlcg0KPg0KPkhpLA0KPg0KPk9uIE1heSAxNiwgMjAxNiwgYXQgMTE6MDQg
QU0sIFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbT4gd3JvdGU6DQo+Pg0KPj4gSGkgU3Rl
ZmFubywNCj4+DQo+PiBUaGFua3MgZm9yIHRoZSByZXNwb25zZXMuDQo+Pg0KPj4+IGV4YWN0bHku
DQo+Pj4NCj4+PiBNb3Jlb3ZlciwgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFk
ZXIgYXNzdW1lcw0KPj4+IGVuY2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQg
aW52b2x2ZWQgaGVyZS4NCj4+Pg0KPj4+IHMuDQo+Pg0KPj4gVHdvIHF1ZXN0aW9uczoNCj4+IDEu
IFdoYXQgaWYgdGhlIGVuY2Fwc3VsYXRpb24gaXMgVlhMQU4/IEw0IHdvdWxkIHN0aWxsIGJlIGlu
dm9sdmVkLCByaWdodD8NCj4NCj4NCj5TZWUgYmVsb3cuDQo+DQo+DQo+PiAyLiBXaGVuIHlvdSBz
YXkgJ2Fzc3VtZXMgZW5jYXBzdWxhdGlvbicsIGRvZXMgaXQgbWVhbiB0aGF0IGEgaG9zdCBjYW5u
b3QNCj5zZW5kIGFuIElQdjYgcGFja2V0IHdpdGggYW4gU1JIPyBUaGUgY3VycmVudCBkcmFmdCBz
YXlzOg0KPj4NCj4+ICAgQSBTb3VyY2UgU1IgTm9kZSBjYW4gYmUgYW55IG5vZGUgb3JpZ2luYXRp
bmcgYW4gSVB2NiBwYWNrZXQgd2l0aCBpdHMNCj4+ICAgSVB2NiBhbmQgU2VnbWVudCBSb3V0aW5n
IEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0aGVyOg0KPj4NCj4+ICAgICAgQSBob3N0IG9yaWdp
bmF0aW5nIGFuIElQdjYgcGFja2V0Lg0KPj4NCj4+ICAgICAgQW4gU1IgZG9tYWluIGluZ3Jlc3Mg
cm91dGVyIGVuY2Fwc3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldA0KPj4gICAgICBpbnRv
IGFuIG91dGVyIElQdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4NCj4+DQo+Pg0KPj4NCj4+
IFdpbGwgYXBwcmVjaWF0ZSBpZiB5b3UgY2FuIGNsYXJpZnkgdGhhdC4NCj4NCj4NCj5vaywgdHdv
IGNhc2VzOg0KPg0KPjEuIHRoZSBTUkggaXMgaW5zZXJ0ZWQgYXQgdGhlIHNvdXJjZS4NCj4gICB0
aGUgc291cmNlIG9yaWdpbmF0ZXMgdGhlIHBhY2tldCwgdGhlIGlwdjYgaGVhZGVyIGFuZA0KPiAg
IHRoZSBTUkguIFRoZSBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tzdW0gdGFraW5nIGludG8NCj4g
ICBhY2NvdW50IHRoZSB3aG9sZSBJUHY2K1NSSC4gSGVyZSwgdGhlcmVz4oCZIG5vdGhpbmcgbmV3
DQo+ICAgY29tcGFyZWQgdG8gcmZjMjQ2MC4NCj4NCj4yLiB0aGUgU1JIIGlzIG9yaWdpbmF0ZWQg
YnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWluLg0KPiAgIFRoaXMgaXMgZG9uZSBi
eSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyDQo+ICAgKGFkZGl0aW9uYWwp
IGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMw0KPiAgIGVuY2Fwc3Vs
YXRpb24gYW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZQ0KPiAgIHBhY2tl
dCBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbg0KPiAgIChpbmNs
dWRpbmcgdGhlIFNSSCkgaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51ZXMNCj4gICBp
dHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFwcGVuZWQuDQo+DQo+cy4NCj4NCj4NCj4+DQo+PiBU
aGFua3MsDQo+PiBUYWwuDQo+Pg0KPj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4g
RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJldmlkaUBjaXNjby5j
b21dDQo+Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYgMTE6NTkgQU0NCj4+PiBUbzogT2xl
IFRyw7hhbjsgVGFsIE1penJhaGkNCj4+PiBDYzogZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91
dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+Pj4gc3ByaW5nQGlldGYub3JnOyA2bWFuIFdH
DQo+Pj4gU3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+IGRyYWZ0LWll
dGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+DQo+Pj4NCj4+Pj4gT24gTWF5IDE1
LCAyMDE2LCBhdCA4OjA2IFBNLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+Pj4NCj4+
Pj4gVGFsLA0KPj4+Pg0KPj4+Pj4gW0Fwb2xvZ2llcyBpZiB0aGlzIGlzc3VlIGhhcyBiZWVuIGRp
c2N1c3NlZCBiZWZvcmUuXQ0KPj4+Pj4NCj4+Pj4+IEFjY29yZGluZyB0byBkcmFmdC1pZXRmLTZt
YW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciwgYW4g4oCYU1IgU2VnbWVudA0KPj4+IEVuZHBvaW50
IE5vZGXigJkgdXBkYXRlcyB0aGUgRGVzdGluYXRpb24gSVAgYWRkcmVzcy4NCj4+Pj4+IFRoZXJl
Zm9yZSwgaXQgbXVzdCBhbHNvIHVwZGF0ZSB0aGUgTGF5ZXIgNCBDaGVja3N1bSwgcmlnaHQ/DQo+
Pj4+Pg0KPj4+Pj4gSSB3b25kZXIgaWYgdGhlcmUgaXMgYW4gdXBwZXIgYm91bmQgb24gdGhlIHNp
emUgb2YgdGhlIFNSSC4NCj4+Pj4+IE90aGVyd2lzZSwgdGhlDQo+Pj4gTDQgQ2hlY2tzdW0gbWF5
IGJlIGxvY2F0ZWQgaW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlvbi4NCj4+Pj4+IFNwZWFraW5nIGZy
b20gYSBjaGlwIHZlbmRvcuKAmXMgcGVyc3BlY3RpdmUgdGhpcyBtYXkgYmUgYSBwcm9ibGVtLg0K
Pj4+Pg0KPj4+PiBGcm9tIFJGQzI0NjAsIFJIMDoNCj4+Pj4NCj4+Pj4NCj4+Pj4gICAgIG8gIElm
IHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBhIFJvdXRpbmcgaGVhZGVyLCB0aGUgRGVzdGluYXRp
b24NCj4+Pj4gICAgICAgIEFkZHJlc3MgdXNlZCBpbiB0aGUgcHNldWRvLWhlYWRlciBpcyB0aGF0
IG9mIHRoZSBmaW5hbA0KPj4+PiAgICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3JpZ2luYXRp
bmcgbm9kZSwgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4NCj4+Pj4gICAgICAgIHRoZSBsYXN0IGVs
ZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMpLA0KPj4+PiAg
ICAgICAgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4gdGhlIERlc3RpbmF0aW9uIEFkZHJlc3MgZmll
bGQgb2YgdGhlDQo+Pj4+ICAgICAgICBJUHY2IGhlYWRlci4NCj4+Pj4NCj4+Pj4gSSB3b3VsZCBl
eHBlY3QgU1Igd291bGQgd29yayB0aGUgc2FtZS4NCj4+Pg0KPj4+DQo+Pj4gZXhhY3RseS4NCj4+
Pg0KPj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBh
c3N1bWVzDQo+Pj4gZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBMNCBpbnZv
bHZlZCBoZXJlLg0KPj4+DQo+Pj4gcy4NCj4+Pg0KPj4+DQo+Pj4+DQo+Pj4+IENoZWVycywNCj4+
Pj4gT2xlDQo+Pj4+DQo+Pg0KDQo=


From nobody Mon May 16 04:24:11 2016
Return-Path: <sprevidi@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 5C89512D14D; Mon, 16 May 2016 04:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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.426, 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 NqlxjnYIk9Hb; Mon, 16 May 2016 04:24:08 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94A11127058; Mon, 16 May 2016 04:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6314; q=dns/txt; s=iport; t=1463397848; x=1464607448; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WLWoejAXhpj3o/KjUI2yPtaBTax5Y8VSlhoz5SgNEQY=; b=kGSwV3nqOhySlwwS2GolfNrYIeevCLCBcfliIDnScmC45MJ8ssHkvwx5 5QzwMx9OICbIUTIgBqmQ8Cmh4ToIq5dnh0FLfaudAPDDOK49qcJTZF3nY s2h2lRIW60sTO0MR8rbAY+yzmvQViK0/40Ev92RiSZGVaCiaK0MYD+Rds 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BFAgBtrTlX/4QNJK1dgzeBUwa5YAENg?= =?us-ascii?q?XaGEQIcgQU4FAEBAQEBAQFlJ4RCAQEBAwEjEUUFBwQCAQgRBAEBAQICERIDAgI?= =?us-ascii?q?CMBQBCAgCBA4FiCcIrQ6QWgEBAQEBAQEBAQEBAQEBAQEBAQEBARyBAYUkgXaCV?= =?us-ascii?q?4RWKIJBK4IuBZgnAY4dgWmNMIYtiRMBHgEBQoNsboZIBzh/AQEB?=
X-IronPort-AV: E=Sophos;i="5.24,627,1454976000"; d="scan'208";a="272170972"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 May 2016 11:24:07 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u4GBO7Ts007432 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 16 May 2016 11:24:07 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 07:24:06 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Mon, 16 May 2016 07:24:06 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAa+DiAAB8pfIAAAC4LAAAEgrGAAAA7KQAAACaYgA==
Date: Mon, 16 May 2016 11:24:06 +0000
Message-ID: <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com>
In-Reply-To: <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.197.212]
Content-Type: text/plain; charset="utf-8"
Content-ID: <09AA67C7F67D70478E750E79BA6A3BE5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/r9tHl-ibBzRiRxlxHpafGtus7pE>
Cc: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 11:24:10 -0000

DQo+IE9uIE1heSAxNiwgMjAxNiwgYXQgMToxOSBQTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZl
bGwuY29tPiB3cm90ZToNCj4gDQo+IEhpIFN0ZWZhbm8sDQo+IA0KPiBUaGFua3MgYWdhaW4gZm9y
IHRoZSBwcm9tcHQgcmVzcG9uc2UuDQo+IA0KPj4gMi4gdGhlIFNSSCBpcyBvcmlnaW5hdGVkIGJ5
IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRvbWFpbi4NCj4+ICBUaGlzIGlzIGRvbmUgYnkg
ZW5jYXBzdWxhdGluZyB0aGUgcGFja2V0IGludG8gYSBvdXRlcg0KPj4gIChhZGRpdGlvbmFsKSBp
cHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDMNCj4+ICBlbmNhcHN1bGF0
aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZvbHZlZC4gV2hlbiB0aGUNCj4+ICBwYWNrZXQg
bGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fwc3VsYXRpb24NCj4+ICAoaW5jbHVk
aW5nIHRoZSBTUkgpIGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVzDQo+PiAgaXRz
IGpvdXJuZXkgbGlrZSBub3RoaW5nIGhhcHBlbmVkLg0KPiANCj4gU28gVlhMQU4gaXMgb2ZmIHRo
ZSB0YWJsZT8NCg0KDQppdOKAmXMgYWxsIGFib3V0IElQLCBub3QgbGF5ZXItMi4NCg0Kcy4NCg0K
DQo+IEl0IHdvdWxkIGJlIHdvcnRod2hpbGUgdG8gY2xhcmlmeSB0aGlzIGluIHRoZSBkcmFmdC4g
SWYgeW91IGhhdmUgYSBzcGVjaWZpYyBlbmNhcHN1bGF0aW9uIGluIG1pbmQsIGl0IHdvdWxkIGJl
IGdyZWF0IGlmIHRoZSBkcmFmdCB3b3VsZCBzcGVjaWZ5IGl0Lg0KPiANCj4gVGhhbmtzLA0KPiBU
YWwuDQo+IA0KPiANCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBTdGVm
YW5vIFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbV0NCj4+IFNl
bnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MTMgUE0NCj4+IFRvOiBUYWwgTWl6cmFoaQ0KPj4g
Q2M6IE9sZSBUcsO4YW47IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRv
b2xzLmlldGYub3JnOw0KPj4gc3ByaW5nQGlldGYub3JnOyA2bWFuIFdHDQo+PiBTdWJqZWN0OiBS
ZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRp
bmctDQo+PiBoZWFkZXINCj4+IA0KPj4gSGksDQo+PiANCj4+IE9uIE1heSAxNiwgMjAxNiwgYXQg
MTE6MDQgQU0sIFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbT4gd3JvdGU6DQo+Pj4gDQo+
Pj4gSGkgU3RlZmFubywNCj4+PiANCj4+PiBUaGFua3MgZm9yIHRoZSByZXNwb25zZXMuDQo+Pj4g
DQo+Pj4+IGV4YWN0bHkuDQo+Pj4+IA0KPj4+PiBNb3Jlb3ZlciwgZHJhZnQtaWV0Zi02bWFuLXNl
Z21lbnQtcm91dGluZy1oZWFkZXIgYXNzdW1lcw0KPj4+PiBlbmNhcHN1bGF0aW9uIHNvIGNsZWFy
bHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+Pj4+IA0KPj4+PiBzLg0KPj4+IA0K
Pj4+IFR3byBxdWVzdGlvbnM6DQo+Pj4gMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlvbiBpcyBW
WExBTj8gTDQgd291bGQgc3RpbGwgYmUgaW52b2x2ZWQsIHJpZ2h0Pw0KPj4gDQo+PiANCj4+IFNl
ZSBiZWxvdy4NCj4+IA0KPj4gDQo+Pj4gMi4gV2hlbiB5b3Ugc2F5ICdhc3N1bWVzIGVuY2Fwc3Vs
YXRpb24nLCBkb2VzIGl0IG1lYW4gdGhhdCBhIGhvc3QgY2Fubm90DQo+PiBzZW5kIGFuIElQdjYg
cGFja2V0IHdpdGggYW4gU1JIPyBUaGUgY3VycmVudCBkcmFmdCBzYXlzOg0KPj4+IA0KPj4+ICBB
IFNvdXJjZSBTUiBOb2RlIGNhbiBiZSBhbnkgbm9kZSBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tl
dCB3aXRoIGl0cw0KPj4+ICBJUHY2IGFuZCBTZWdtZW50IFJvdXRpbmcgSGVhZGVycy4gIFRoaXMg
aW5jbHVkZSBlaXRoZXI6DQo+Pj4gDQo+Pj4gICAgIEEgaG9zdCBvcmlnaW5hdGluZyBhbiBJUHY2
IHBhY2tldC4NCj4+PiANCj4+PiAgICAgQW4gU1IgZG9tYWluIGluZ3Jlc3Mgcm91dGVyIGVuY2Fw
c3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldA0KPj4+ICAgICBpbnRvIGFuIG91dGVyIElQ
djYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4NCj4+PiANCj4+PiANCj4+PiANCj4+PiBXaWxs
IGFwcHJlY2lhdGUgaWYgeW91IGNhbiBjbGFyaWZ5IHRoYXQuDQo+PiANCj4+IA0KPj4gb2ssIHR3
byBjYXNlczoNCj4+IA0KPj4gMS4gdGhlIFNSSCBpcyBpbnNlcnRlZCBhdCB0aGUgc291cmNlLg0K
Pj4gIHRoZSBzb3VyY2Ugb3JpZ2luYXRlcyB0aGUgcGFja2V0LCB0aGUgaXB2NiBoZWFkZXIgYW5k
DQo+PiAgdGhlIFNSSC4gVGhlIHNvdXJjZSBjb21wdXRlcyBMNCBjaGVja3N1bSB0YWtpbmcgaW50
bw0KPj4gIGFjY291bnQgdGhlIHdob2xlIElQdjYrU1JILiBIZXJlLCB0aGVyZXPigJkgbm90aGlu
ZyBuZXcNCj4+ICBjb21wYXJlZCB0byByZmMyNDYwLg0KPj4gDQo+PiAyLiB0aGUgU1JIIGlzIG9y
aWdpbmF0ZWQgYnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWluLg0KPj4gIFRoaXMg
aXMgZG9uZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyDQo+PiAgKGFk
ZGl0aW9uYWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMw0KPj4g
IGVuY2Fwc3VsYXRpb24gYW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZQ0K
Pj4gIHBhY2tldCBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbg0K
Pj4gIChpbmNsdWRpbmcgdGhlIFNSSCkgaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51
ZXMNCj4+ICBpdHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFwcGVuZWQuDQo+PiANCj4+IHMuDQo+
PiANCj4+IA0KPj4+IA0KPj4+IFRoYW5rcywNCj4+PiBUYWwuDQo+Pj4gDQo+Pj4+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkp
IFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0KPj4+PiBTZW50OiBNb25kYXksIE1heSAxNiwg
MjAxNiAxMTo1OSBBTQ0KPj4+PiBUbzogT2xlIFRyw7hhbjsgVGFsIE1penJhaGkNCj4+Pj4gQ2M6
IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnOw0K
Pj4+PiBzcHJpbmdAaWV0Zi5vcmc7IDZtYW4gV0cNCj4+Pj4gU3ViamVjdDogUmU6IFtzcHJpbmdd
IEw0IENoZWNrc3VtIGFuZA0KPj4+PiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBo
ZWFkZXINCj4+Pj4gDQo+Pj4+IA0KPj4+Pj4gT24gTWF5IDE1LCAyMDE2LCBhdCA4OjA2IFBNLCBv
dHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+Pj4+IA0KPj4+Pj4gVGFsLA0KPj4+Pj4gDQo+
Pj4+Pj4gW0Fwb2xvZ2llcyBpZiB0aGlzIGlzc3VlIGhhcyBiZWVuIGRpc2N1c3NlZCBiZWZvcmUu
XQ0KPj4+Pj4+IA0KPj4+Pj4+IEFjY29yZGluZyB0byBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1y
b3V0aW5nLWhlYWRlciwgYW4g4oCYU1IgU2VnbWVudA0KPj4+PiBFbmRwb2ludCBOb2Rl4oCZIHVw
ZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQIGFkZHJlc3MuDQo+Pj4+Pj4gVGhlcmVmb3JlLCBpdCBt
dXN0IGFsc28gdXBkYXRlIHRoZSBMYXllciA0IENoZWNrc3VtLCByaWdodD8NCj4+Pj4+PiANCj4+
Pj4+PiBJIHdvbmRlciBpZiB0aGVyZSBpcyBhbiB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0
aGUgU1JILg0KPj4+Pj4+IE90aGVyd2lzZSwgdGhlDQo+Pj4+IEw0IENoZWNrc3VtIG1heSBiZSBs
b2NhdGVkIGluIGEgcHJldHR5IGRlZXAgbG9jYXRpb24uDQo+Pj4+Pj4gU3BlYWtpbmcgZnJvbSBh
IGNoaXAgdmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0uDQo+Pj4+
PiANCj4+Pj4+IEZyb20gUkZDMjQ2MCwgUkgwOg0KPj4+Pj4gDQo+Pj4+PiANCj4+Pj4+ICAgIG8g
IElmIHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBhIFJvdXRpbmcgaGVhZGVyLCB0aGUgRGVzdGlu
YXRpb24NCj4+Pj4+ICAgICAgIEFkZHJlc3MgdXNlZCBpbiB0aGUgcHNldWRvLWhlYWRlciBpcyB0
aGF0IG9mIHRoZSBmaW5hbA0KPj4+Pj4gICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3JpZ2lu
YXRpbmcgbm9kZSwgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4NCj4+Pj4+ICAgICAgIHRoZSBsYXN0
IGVsZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMpLA0KPj4+
Pj4gICAgICAgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4gdGhlIERlc3RpbmF0aW9uIEFkZHJlc3Mg
ZmllbGQgb2YgdGhlDQo+Pj4+PiAgICAgICBJUHY2IGhlYWRlci4NCj4+Pj4+IA0KPj4+Pj4gSSB3
b3VsZCBleHBlY3QgU1Igd291bGQgd29yayB0aGUgc2FtZS4NCj4+Pj4gDQo+Pj4+IA0KPj4+PiBl
eGFjdGx5Lg0KPj4+PiANCj4+Pj4gTW9yZW92ZXIsIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJv
dXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4gZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl
4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLg0KPj4+PiANCj4+Pj4gcy4NCj4+Pj4gDQo+Pj4+IA0K
Pj4+Pj4gDQo+Pj4+PiBDaGVlcnMsDQo+Pj4+PiBPbGUNCj4+Pj4+IA0KPj4+IA0KPiANCg0K


From nobody Mon May 16 04:32:32 2016
Return-Path: <talmi@marvell.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 9053812D133; Mon, 16 May 2016 04:32:28 -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 BgmY-9YXYJpz; Mon, 16 May 2016 04:32:26 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 6145812D0C2; Mon, 16 May 2016 04:32:26 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4GBW0Ji026986; Mon, 16 May 2016 04:32:25 -0700
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0a-0016f401.pphosted.com with ESMTP id 22xc8c3sp0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 16 May 2016 04:32:24 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 16 May 2016 14:32:20 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 16 May 2016 14:32:20 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAMTSCAAB8pyYAABk9dsP//8wwA///NLLCAADXfAP//zJ5w
Date: Mon, 16 May 2016 11:32:20 +0000
Message-ID: <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com>
In-Reply-To: <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-16_06:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605160160
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mmYUKAm4ziMA_VTJUSuR78xU-zk>
Cc: 6man WG <ipv6@ietf.org>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 11:32:28 -0000

Pml04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLg0KPg0KPnMuDQoNClJpZ2h0LiBIb3dl
dmVyLCBpdCBhcHBlYXJzIHRoYXQgYXQgbGVhc3QgaW4gc29tZSBjYXNlcyBhIFZYTEFOIFZURVAg
d2lsbCB1c2UgU1IuIEl0IGNlcnRhaW5seSBtYXkgYmUgdGhlIGNhc2UgaW4gU0ZDIHVzZSBjYXNl
cyAoc2VlIFNlY3Rpb24gMi4zIGluIGRyYWZ0LWlldGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzKS4N
Cg0KDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IFN0ZWZhbm8gUHJldmlk
aSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0KPlNlbnQ6IE1vbmRheSwg
TWF5IDE2LCAyMDE2IDI6MjQgUE0NCj5UbzogVGFsIE1penJhaGkNCj5DYzogT2xlIFRyw7hhbjsg
ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+
c3ByaW5nQGlldGYub3JnOyA2bWFuIFdHDQo+U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNr
c3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLQ0KPmhlYWRlcg0KPg0KPg0K
Pj4gT24gTWF5IDE2LCAyMDE2LCBhdCAxOjE5IFBNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFydmVs
bC5jb20+IHdyb3RlOg0KPj4NCj4+IEhpIFN0ZWZhbm8sDQo+Pg0KPj4gVGhhbmtzIGFnYWluIGZv
ciB0aGUgcHJvbXB0IHJlc3BvbnNlLg0KPj4NCj4+PiAyLiB0aGUgU1JIIGlzIG9yaWdpbmF0ZWQg
YnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWluLg0KPj4+ICBUaGlzIGlzIGRvbmUg
YnkgZW5jYXBzdWxhdGluZyB0aGUgcGFja2V0IGludG8gYSBvdXRlcg0KPj4+ICAoYWRkaXRpb25h
bCkgaXB2NiBoZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILiBUaGlzIGlzIEwzDQo+Pj4gZW5jYXBz
dWxhdGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlICBwYWNrZXQg
bGVhdmVzDQo+Pj4gdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbiAgKGluY2x1
ZGluZyB0aGUgU1JIKSBpcyByZW1vdmVkDQo+Pj4gYW5kIHRoZSBwYWNrZXQgY29udGludWVzICBp
dHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFwcGVuZWQuDQo+Pg0KPj4gU28gVlhMQU4gaXMgb2Zm
IHRoZSB0YWJsZT8NCj4NCj4NCj5pdOKAmXMgYWxsIGFib3V0IElQLCBub3QgbGF5ZXItMi4NCj4N
Cj5zLg0KPg0KPg0KPj4gSXQgd291bGQgYmUgd29ydGh3aGlsZSB0byBjbGFyaWZ5IHRoaXMgaW4g
dGhlIGRyYWZ0LiBJZiB5b3UgaGF2ZSBhIHNwZWNpZmljDQo+ZW5jYXBzdWxhdGlvbiBpbiBtaW5k
LCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUgZHJhZnQgd291bGQgc3BlY2lmeSBpdC4NCj4+DQo+
PiBUaGFua3MsDQo+PiBUYWwuDQo+Pg0KPj4NCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPj4+IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlA
Y2lzY28uY29tXQ0KPj4+IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MTMgUE0NCj4+PiBU
bzogVGFsIE1penJhaGkNCj4+PiBDYzogT2xlIFRyw7hhbjsgZHJhZnQtaWV0Zi02bWFuLXNlZ21l
bnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+Pj4gc3ByaW5nQGlldGYub3JnOyA2
bWFuIFdHDQo+Pj4gU3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+IGRy
YWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+DQo+Pj4gSGksDQo+Pj4N
Cj4+PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDExOjA0IEFNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFy
dmVsbC5jb20+IHdyb3RlOg0KPj4+Pg0KPj4+PiBIaSBTdGVmYW5vLA0KPj4+Pg0KPj4+PiBUaGFu
a3MgZm9yIHRoZSByZXNwb25zZXMuDQo+Pj4+DQo+Pj4+PiBleGFjdGx5Lg0KPj4+Pj4NCj4+Pj4+
IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVz
DQo+Pj4+PiBlbmNhcHN1bGF0aW9uIHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVk
IGhlcmUuDQo+Pj4+Pg0KPj4+Pj4gcy4NCj4+Pj4NCj4+Pj4gVHdvIHF1ZXN0aW9uczoNCj4+Pj4g
MS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlvbiBpcyBWWExBTj8gTDQgd291bGQgc3RpbGwgYmUg
aW52b2x2ZWQsIHJpZ2h0Pw0KPj4+DQo+Pj4NCj4+PiBTZWUgYmVsb3cuDQo+Pj4NCj4+Pg0KPj4+
PiAyLiBXaGVuIHlvdSBzYXkgJ2Fzc3VtZXMgZW5jYXBzdWxhdGlvbicsIGRvZXMgaXQgbWVhbiB0
aGF0IGEgaG9zdA0KPj4+PiBjYW5ub3QNCj4+PiBzZW5kIGFuIElQdjYgcGFja2V0IHdpdGggYW4g
U1JIPyBUaGUgY3VycmVudCBkcmFmdCBzYXlzOg0KPj4+Pg0KPj4+PiAgQSBTb3VyY2UgU1IgTm9k
ZSBjYW4gYmUgYW55IG5vZGUgb3JpZ2luYXRpbmcgYW4gSVB2NiBwYWNrZXQgd2l0aA0KPj4+PiBp
dHMNCj4+Pj4gIElQdjYgYW5kIFNlZ21lbnQgUm91dGluZyBIZWFkZXJzLiAgVGhpcyBpbmNsdWRl
IGVpdGhlcjoNCj4+Pj4NCj4+Pj4gICAgIEEgaG9zdCBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tl
dC4NCj4+Pj4NCj4+Pj4gICAgIEFuIFNSIGRvbWFpbiBpbmdyZXNzIHJvdXRlciBlbmNhcHN1bGF0
aW5nIGEgcmVjZWl2ZWQgSVB2NiBwYWNrZXQNCj4+Pj4gICAgIGludG8gYW4gb3V0ZXIgSVB2NiBo
ZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILg0KPj4+Pg0KPj4+Pg0KPj4+Pg0KPj4+PiBXaWxsIGFw
cHJlY2lhdGUgaWYgeW91IGNhbiBjbGFyaWZ5IHRoYXQuDQo+Pj4NCj4+Pg0KPj4+IG9rLCB0d28g
Y2FzZXM6DQo+Pj4NCj4+PiAxLiB0aGUgU1JIIGlzIGluc2VydGVkIGF0IHRoZSBzb3VyY2UuDQo+
Pj4gIHRoZSBzb3VyY2Ugb3JpZ2luYXRlcyB0aGUgcGFja2V0LCB0aGUgaXB2NiBoZWFkZXIgYW5k
ICB0aGUgU1JILiBUaGUNCj4+PiBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tzdW0gdGFraW5nIGlu
dG8gIGFjY291bnQgdGhlIHdob2xlIElQdjYrU1JILg0KPj4+IEhlcmUsIHRoZXJlc+KAmSBub3Ro
aW5nIG5ldyAgY29tcGFyZWQgdG8gcmZjMjQ2MC4NCj4+Pg0KPj4+IDIuIHRoZSBTUkggaXMgb3Jp
Z2luYXRlZCBieSB0aGUgaW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+Pj4gIFRoaXMg
aXMgZG9uZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyDQo+Pj4gIChh
ZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDMNCj4+
PiBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZvbHZlZC4gV2hlbiB0aGUg
IHBhY2tldCBsZWF2ZXMNCj4+PiB0aGUgU1IgdHVubmVsIHRoZSBvdXRlciBlbmNhcHN1bGF0aW9u
ICAoaW5jbHVkaW5nIHRoZSBTUkgpIGlzIHJlbW92ZWQNCj4+PiBhbmQgdGhlIHBhY2tldCBjb250
aW51ZXMgIGl0cyBqb3VybmV5IGxpa2Ugbm90aGluZyBoYXBwZW5lZC4NCj4+Pg0KPj4+IHMuDQo+
Pj4NCj4+Pg0KPj4+Pg0KPj4+PiBUaGFua3MsDQo+Pj4+IFRhbC4NCj4+Pj4NCj4+Pj4+IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+PiBGcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2
aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbV0NCj4+Pj4+IFNlbnQ6IE1vbmRheSwgTWF5
IDE2LCAyMDE2IDExOjU5IEFNDQo+Pj4+PiBUbzogT2xlIFRyw7hhbjsgVGFsIE1penJhaGkNCj4+
Pj4+IENjOiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRm
Lm9yZzsNCj4+Pj4+IHNwcmluZ0BpZXRmLm9yZzsgNm1hbiBXRw0KPj4+Pj4gU3ViamVjdDogUmU6
IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy0gaGVhZGVyDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+PiBPbiBNYXkgMTUsIDIwMTYsIGF0
IDg6MDYgUE0sIG90cm9hbkBlbXBsb3llZXMub3JnIHdyb3RlOg0KPj4+Pj4+DQo+Pj4+Pj4gVGFs
LA0KPj4+Pj4+DQo+Pj4+Pj4+IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNj
dXNzZWQgYmVmb3JlLl0NCj4+Pj4+Pj4NCj4+Pj4+Pj4gQWNjb3JkaW5nIHRvIGRyYWZ0LWlldGYt
Nm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyLCBhbiDigJhTUg0KPj4+Pj4+PiBTZWdtZW50DQo+
Pj4+PiBFbmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQIGFkZHJlc3Mu
DQo+Pj4+Pj4+IFRoZXJlZm9yZSwgaXQgbXVzdCBhbHNvIHVwZGF0ZSB0aGUgTGF5ZXIgNCBDaGVj
a3N1bSwgcmlnaHQ/DQo+Pj4+Pj4+DQo+Pj4+Pj4+IEkgd29uZGVyIGlmIHRoZXJlIGlzIGFuIHVw
cGVyIGJvdW5kIG9uIHRoZSBzaXplIG9mIHRoZSBTUkguDQo+Pj4+Pj4+IE90aGVyd2lzZSwgdGhl
DQo+Pj4+PiBMNCBDaGVja3N1bSBtYXkgYmUgbG9jYXRlZCBpbiBhIHByZXR0eSBkZWVwIGxvY2F0
aW9uLg0KPj4+Pj4+PiBTcGVha2luZyBmcm9tIGEgY2hpcCB2ZW5kb3LigJlzIHBlcnNwZWN0aXZl
IHRoaXMgbWF5IGJlIGEgcHJvYmxlbS4NCj4+Pj4+Pg0KPj4+Pj4+IEZyb20gUkZDMjQ2MCwgUkgw
Og0KPj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+PiAgICBvICBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFp
bnMgYSBSb3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9uDQo+Pj4+Pj4gICAgICAgQWRkcmVz
cyB1c2VkIGluIHRoZSBwc2V1ZG8taGVhZGVyIGlzIHRoYXQgb2YgdGhlIGZpbmFsDQo+Pj4+Pj4g
ICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3JpZ2luYXRpbmcgbm9kZSwgdGhhdCBhZGRyZXNz
IHdpbGwgYmUgaW4NCj4+Pj4+PiAgICAgICB0aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5n
IGhlYWRlcjsgYXQgdGhlIHJlY2lwaWVudChzKSwNCj4+Pj4+PiAgICAgICB0aGF0IGFkZHJlc3Mg
d2lsbCBiZSBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVzcyBmaWVsZCBvZiB0aGUNCj4+Pj4+PiAg
ICAgICBJUHY2IGhlYWRlci4NCj4+Pj4+Pg0KPj4+Pj4+IEkgd291bGQgZXhwZWN0IFNSIHdvdWxk
IHdvcmsgdGhlIHNhbWUuDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IGV4YWN0bHkuDQo+Pj4+Pg0KPj4+
Pj4gTW9yZW92ZXIsIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3Vt
ZXMNCj4+Pj4+IGVuY2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2
ZWQgaGVyZS4NCj4+Pj4+DQo+Pj4+PiBzLg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+PiBD
aGVlcnMsDQo+Pj4+Pj4gT2xlDQo+Pj4+Pj4NCj4+Pj4NCj4+DQoNCg==


From nobody Mon May 16 10:13:47 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 9EEB112D825 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:13:45 -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=NMvNpNms; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=HuGojL3h
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 90KHtDAYUpF4 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:13:42 -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 513EC12D828 for <ipv6@ietf.org>; Mon, 16 May 2016 10:13:42 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id BA171212D6 for <ipv6@ietf.org>; Mon, 16 May 2016 13:13:41 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 16 May 2016 13:13:41 -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=HXWkF 9t3BlsIxUmY83qnzdtxP0A=; b=NMvNpNms4UUAeEQHF7qVrobHSnK17M4Zq5fap r9H/zj8ETm2R8TuMydgg5kgOXFOpa2smb/hzcxnwTji2E428fKFLT9D+USZX6aBY 7sTalRWEQBDSQzP+n/yKeQ12GixxMvDg3ArSkW5FB7zPon8Go0isJOi8pVWDYy2p K7ezSM=
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=HXWkF9t3BlsIxUmY83qnzdtxP0A=; b=HuGoj L3hr3etpm0+YGY9bKTJHPIUcFbf0cVQGPFKYaMJ942c/fk4vbKjAXoCrgdBDqOB3 961y/uRKGM6k3b0C13KdVl5aLKR97VYAG5ACm7wnkRqACGWTRLWLAl5hIV9hVIBa IetJnIFD2Kx7rK79bWVoGTClj8xg5OqO9Uo50E=
X-Sasl-enc: DYqgBTWagYFV+ATOvyxIp//VzAqI1rm4vOlUkZ2NI9If 1463418821
Received: from dhcp-171-68-20-133.cisco.com (dhcp-171-68-20-133.cisco.com [171.68.20.133]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A6D8C00012; Mon, 16 May 2016 13:13:41 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DA76D871-CE7C-4182-9B17-3DB08D932D8D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
Date: Mon, 16 May 2016 10:13:43 -0700
Message-Id: <41533F2B-C2AC-46A9-BB67-511EFE9D3861@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/BJkhoy-2WgO85O1M-ap0SYKPRLg>
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: Mon, 16 May 2016 17:13:45 -0000

--Apple-Mail=_DA76D871-CE7C-4182-9B17-3DB08D932D8D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Lorenzo,

> On May 13, 2016, at 6:55 PM, Lorenzo Colitti <lorenzo@google.com> =
wrote:
>=20
> I continue to oppose this document.
>=20
> This draft says that existing address generation mechanisms are bad =
for privacy, and proceeds to change them. But there is nothing wrong =
with the existing address generation mechanisms as if the link-layer =
addresses are not stable, (e.g., random MAC addresses), and a growing =
body of IETF work=20
>=20
> This draft forbids implementations from using existing address =
generation mechanisms using random MAC addresses,

The draft does not forbid anything. It has two MUST-level requirements: =
that mechanisms be defined, and that those mechanisms meet certain =
requirements. The other requirements in the draft are SHOULD/SHOULD =
NOT-level requirements, about what nodes should and shouldn=E2=80=99t =
do. IIRC there was a bunch of discussion early on about the normative =
strength of these requirements and landed on SHOULD/SHOULD NOT rather =
than MUST/MUST NOT purposefully because there were known exception =
cases.

> which is a perfectly valid way to address the privacy problem this =
draft is purportedly solving, and is an approach standardized in other =
IETF work, for example, =
https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.=
1 =
<https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2=
.1> (now in RFC editor queue).
>=20
> Here are several examples of how this draft forbids using address =
generation mechanisms with random MAC addresses.
>=20
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.
> ...
>    In standardized recommendations for IPv6 IID generation meant to
>    achieve particular security and privacy properties, it is therefore
>    necessary to recommend against embedding link-layer addresses in =
IPv6
>    IIDs.
> ...
>    By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed the underlying link-layer address in the IID.

I disagree that any of the text above forbids anything, certainly not =
normatively.

>=20
> These statements should not say "link-layer address". They should say =
"stable link-layer-address" or "non-ephemeral link-layer-address" or =
"link-layer address that are not known to be ephemeral".
>=20
> Worse, consider this normative text:
>=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 MUST be
>    generated as specified in [RFCXXXX].
>=20
> This explicitly prohibits an implementation from taking a random MAC =
address and forming an EUI-64 address out of it.

Again, because the contents of Section 3 do not prohibit anything, I =
don=E2=80=99t see how this could be interpreted to prohibit anything.

Alissa

>=20
> On Fri, May 13, 2016 at 5:43 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> =
wrote:
> With the clarifying references to RFC4941, I think this document is
> in good shape and ready to be advanced.
>=20
>     Brian
>=20
> --------------------------------------------------------------------
> 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
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_DA76D871-CE7C-4182-9B17-3DB08D932D8D
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 Lorenzo,</div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
May 13, 2016, at 6:55 PM, Lorenzo Colitti &lt;<a =
href=3D"mailto:lorenzo@google.com" class=3D"">lorenzo@google.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">I continue to oppose this document.<div =
class=3D""><br class=3D""></div><div class=3D"">This draft says that =
existing address generation mechanisms are bad for privacy, and proceeds =
to change them. But there is nothing wrong with the&nbsp;existing =
address generation mechanisms as if the link-layer addresses are not =
stable, (e.g., random MAC addresses), and a growing body of IETF =
work&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">This =
draft forbids implementations from using existing address generation =
mechanisms using random MAC addresses, =
</div></div></div></blockquote><div><br class=3D""></div><div>The draft =
does not forbid anything. It has two MUST-level requirements: that =
mechanisms be defined, and that those mechanisms meet certain =
requirements. The other requirements in the draft are SHOULD/SHOULD =
NOT-level requirements, about what nodes should and shouldn=E2=80=99t =
do. IIRC there was a bunch of discussion early on about the normative =
strength of these requirements and landed on SHOULD/SHOULD NOT rather =
than MUST/MUST NOT purposefully because there were known exception =
cases.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"">which is a =
perfectly valid way to address the privacy problem this draft is =
purportedly solving, and is an approach standardized in other IETF work, =
for example, <a =
href=3D"https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#se=
ction-2.1" =
class=3D"">https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08=
#section-2.1</a> (now in RFC editor queue).</div><div class=3D""><br =
class=3D""></div><div class=3D"">Here are several examples of how this =
draft forbids using address generation mechanisms with random MAC =
addresses.<br class=3D""></div><div class=3D""><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">&nbsp; &nbsp;The =
recommendations in this document apply only in cases where</div><div =
class=3D"">&nbsp; &nbsp;implementations otherwise would have configured =
a stable IPv6 IID</div><div class=3D"">&nbsp; &nbsp;containing a link =
layer address.</div></div><div class=3D"">...<br class=3D""></div><div =
class=3D"">&nbsp; &nbsp;In standardized recommendations for IPv6 IID =
generation meant to<br class=3D""></div><div class=3D""><div =
class=3D"">&nbsp; &nbsp;achieve particular security and privacy =
properties, it is therefore</div><div class=3D"">&nbsp; &nbsp;necessary =
to recommend against embedding link-layer addresses in IPv6</div><div =
class=3D"">&nbsp; &nbsp;IIDs.</div></div><div class=3D"">...<br =
class=3D""></div><div class=3D"">&nbsp; &nbsp;By default, nodes SHOULD =
NOT employ IPv6 address generation schemes<br class=3D""></div><div =
class=3D""><div class=3D"">&nbsp; &nbsp;that embed the underlying =
link-layer address in the =
IID.</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>I disagree that any of the text above forbids =
anything, certainly not normatively.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">These =
statements should not say "link-layer address". They should say "stable =
link-layer-address" or "non-ephemeral link-layer-address" or "link-layer =
address that are not known to be ephemeral".<br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D"">Worse, consider this =
normative text:</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">&nbsp; &nbsp;The entire text of Section 4 of =
[RFC2464] is replaced with the</div><div class=3D"">&nbsp; =
&nbsp;following text:</div><div class=3D""><br class=3D""></div><div =
class=3D"">&nbsp; &nbsp;---------------- cut here -------------- cut =
here ----------------</div><div class=3D"">&nbsp; &nbsp;The Interface =
Identifier [AARCH] for an Ethernet interface MUST be</div><div =
class=3D"">&nbsp; &nbsp;generated as specified in =
[RFCXXXX].</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">This explicitly prohibits an implementation from taking a =
random MAC address and forming an EUI-64 address out of =
it.</div></div></div></div></blockquote><div><br =
class=3D""></div><div>Again, because the contents of Section 3 do not =
prohibit anything, I don=E2=80=99t see how this could be interpreted to =
prohibit anything.</div><div><br class=3D""></div><div>Alissa</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Fri, =
May 13, 2016 at 5:43 AM, Brian E Carpenter <span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
target=3D"_blank" class=3D"">brian.e.carpenter@gmail.com</a>&gt;</span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">With the =
clarifying references to RFC4941, I think this document is<br class=3D"">
in good shape and ready to be advanced.<br class=3D"">
<span class=3D"HOEnZb"><font color=3D"#888888" class=3D""><br class=3D"">
&nbsp; &nbsp; Brian<br class=3D"">
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><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: <a =
href=3D"https://www.ietf.org/mailman/listinfo/ipv6" rel=3D"noreferrer" =
target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipv6</a><br class=3D"">
--------------------------------------------------------------------<br =
class=3D"">
</div></div></blockquote></div><br class=3D""></div>
--------------------------------------------------------------------<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></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_DA76D871-CE7C-4182-9B17-3DB08D932D8D--


From nobody Mon May 16 10:15:30 2016
Return-Path: <tom@herbertland.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 CDD5212D83B for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 3_g_FXXe2mEQ for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:15:26 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001: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 DE7BC12D806 for <ipv6@ietf.org>; Mon, 16 May 2016 10:10:04 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id f89so217336348ioi.0 for <ipv6@ietf.org>; Mon, 16 May 2016 10:10:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=xwuMD+np3FVbrp3l1WmZQ0xoky7QCFAh5pwGFBvtGRM=; b=SF2wFEgQKVzb8Y4sdlG0CbOp8y67h3uvkc/efX/j9l4ePvYpnD96nLNXNY2vbPSi37 Op3hpMNe2n7N9/uZFulxh5vl421gR+TzPKDcEVsguxu7NS2d7AxegG7lBQzD9F1oy24J 6aATdS5WkGegdIzCVhMAA4bUgCJ/d00Gbn+/0uutXfpxHT1yBsSSsvp1peqdhDWdqfc8 5VCGx+J0N97JJ6AUj9Rlo6SZriQvV9vbPiF8LfbcwEyNWyDIodLcG6eZ33Vvz3LkepxG 9Rqfsls9p/2z1DKK4jrJcaHt90csBcr/we6x5NeNfPwBzj7W2mjTXdCjyoHF+EJX+9qZ uBeg==
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:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=xwuMD+np3FVbrp3l1WmZQ0xoky7QCFAh5pwGFBvtGRM=; b=fZN9DM3GIGhAUw7KtnBeSbSbEE8lc4MezECVSTTrYlrMKmjtSb//35zpF2bNMXLmNO MHZjBs9T7jAq0fFcy1TFTrVWHZCk8QAbW7DbdeuFxYtJLeGt968CBqMgmhoUt3ThkNSu QnYcQCMM3xRHTLLngniQseaz7xLA65+J/mHJAzh1thJP95ZyAL6qjsoB9BZ/LqVpcxwy 7eMKqga3M/EQobvV3ktY+XRkHN6/fDdpwvf6BZ+SUDGK3njxwcUXh+yYFXHKHizobo4Y TfNDtctY3+podleKwU2v08mxZnlNIu7crCZL1qVMGziK2EKhHShpzQnw0UvKu9xNVizg 5Rtw==
X-Gm-Message-State: AOPr4FU5QbCidgRtsv4jPyJGHesIIBiH5MlX3BKTmaUGeHm2Csf0CejQAfeJoxhWXhoo8A8o9ccQ+C8letp3Cw==
MIME-Version: 1.0
X-Received: by 10.36.110.143 with SMTP id w137mr10638294itc.37.1463418604053;  Mon, 16 May 2016 10:10:04 -0700 (PDT)
Received: by 10.107.56.67 with HTTP; Mon, 16 May 2016 10:10:03 -0700 (PDT)
In-Reply-To: <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com>
Date: Mon, 16 May 2016 10:10:03 -0700
Message-ID: <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
From: Tom Herbert <tom@herbertland.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gDoVy0ttN8X0_WDmEHTUoGgWSbo>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 16 May 2016 17:15:28 -0000

On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>>it=E2=80=99s all about IP, not layer-2.
>>
>>s.
>
> Right. However, it appears that at least in some cases a VXLAN VTEP will =
use SR. It certainly may be the case in SFC use cases (see Section 2.3 in d=
raft-ietf-spring-ipv6-use-cases).
>

draft-ietf-6man-segment-routing-header mentions that the packet is
encapsulated, but I don't think it is explicit as to exact
encapsulation format (I suppose simple ip6ip6 is implied). But, it
seems like any of several encapsulation techniques could work (VXLAN,
GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants to
do SR is already doing tunneling it seems reasonable to me to only
have one layer of encapsulation. Maybe this should be clarified in the
draft?

Tom

>
>
>>-----Original Message-----
>>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
>>Sent: Monday, May 16, 2016 2:24 PM
>>To: Tal Mizrahi
>>Cc: Ole Tr=C3=B8an; draft-ietf-6man-segment-routing-header@tools.ietf.org=
;
>>spring@ietf.org; 6man WG
>>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
>>header
>>
>>
>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com> wrote:
>>>
>>> Hi Stefano,
>>>
>>> Thanks again for the prompt response.
>>>
>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>  This is done by encapsulating the packet into a outer
>>>>  (additional) ipv6 header followed by an SRH. This is L3
>>>> encapsulation and no L4 checksum is involved. When the  packet leaves
>>>> the SR tunnel the outer encapsulation  (including the SRH) is removed
>>>> and the packet continues  its journey like nothing happened.
>>>
>>> So VXLAN is off the table?
>>
>>
>>it=E2=80=99s all about IP, not layer-2.
>>
>>s.
>>
>>
>>> It would be worthwhile to clarify this in the draft. If you have a spec=
ific
>>encapsulation in mind, it would be great if the draft would specify it.
>>>
>>> Thanks,
>>> Tal.
>>>
>>>
>>>> -----Original Message-----
>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
>>>> Sent: Monday, May 16, 2016 2:13 PM
>>>> To: Tal Mizrahi
>>>> Cc: Ole Tr=C3=B8an; draft-ietf-6man-segment-routing-header@tools.ietf.=
org;
>>>> spring@ietf.org; 6man WG
>>>> Subject: Re: [spring] L4 Checksum and
>>>> draft-ietf-6man-segment-routing- header
>>>>
>>>> Hi,
>>>>
>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>>>>>
>>>>> Hi Stefano,
>>>>>
>>>>> Thanks for the responses.
>>>>>
>>>>>> exactly.
>>>>>>
>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
>>>>>>
>>>>>> s.
>>>>>
>>>>> Two questions:
>>>>> 1. What if the encapsulation is VXLAN? L4 would still be involved, ri=
ght?
>>>>
>>>>
>>>> See below.
>>>>
>>>>
>>>>> 2. When you say 'assumes encapsulation', does it mean that a host
>>>>> cannot
>>>> send an IPv6 packet with an SRH? The current draft says:
>>>>>
>>>>>  A Source SR Node can be any node originating an IPv6 packet with
>>>>> its
>>>>>  IPv6 and Segment Routing Headers.  This include either:
>>>>>
>>>>>     A host originating an IPv6 packet.
>>>>>
>>>>>     An SR domain ingress router encapsulating a received IPv6 packet
>>>>>     into an outer IPv6 header followed by an SRH.
>>>>>
>>>>>
>>>>>
>>>>> Will appreciate if you can clarify that.
>>>>
>>>>
>>>> ok, two cases:
>>>>
>>>> 1. the SRH is inserted at the source.
>>>>  the source originates the packet, the ipv6 header and  the SRH. The
>>>> source computes L4 checksum taking into  account the whole IPv6+SRH.
>>>> Here, theres=E2=80=99 nothing new  compared to rfc2460.
>>>>
>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>  This is done by encapsulating the packet into a outer
>>>>  (additional) ipv6 header followed by an SRH. This is L3
>>>> encapsulation and no L4 checksum is involved. When the  packet leaves
>>>> the SR tunnel the outer encapsulation  (including the SRH) is removed
>>>> and the packet continues  its journey like nothing happened.
>>>>
>>>> s.
>>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>> Tal.
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
>>>>>> Sent: Monday, May 16, 2016 11:59 AM
>>>>>> To: Ole Tr=C3=B8an; Tal Mizrahi
>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org;
>>>>>> spring@ietf.org; 6man WG
>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>
>>>>>>
>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
>>>>>>>
>>>>>>> Tal,
>>>>>>>
>>>>>>>> [Apologies if this issue has been discussed before.]
>>>>>>>>
>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =E2=80=98S=
R
>>>>>>>> Segment
>>>>>> Endpoint Node=E2=80=99 updates the Destination IP address.
>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>>>>>
>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
>>>>>>>> Otherwise, the
>>>>>> L4 Checksum may be located in a pretty deep location.
>>>>>>>> Speaking from a chip vendor=E2=80=99s perspective this may be a pr=
oblem.
>>>>>>>
>>>>>>> From RFC2460, RH0:
>>>>>>>
>>>>>>>
>>>>>>>    o  If the IPv6 packet contains a Routing header, the Destination
>>>>>>>       Address used in the pseudo-header is that of the final
>>>>>>>       destination.  At the originating node, that address will be i=
n
>>>>>>>       the last element of the Routing header; at the recipient(s),
>>>>>>>       that address will be in the Destination Address field of the
>>>>>>>       IPv6 header.
>>>>>>>
>>>>>>> I would expect SR would work the same.
>>>>>>
>>>>>>
>>>>>> exactly.
>>>>>>
>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
>>>>>>
>>>>>> s.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Ole
>>>>>>>
>>>>>
>>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Mon May 16 10:25:27 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 358D112D871 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 v9Deb-X3y_g1 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:25:23 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001: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 EFB8D12D877 for <ipv6@ietf.org>; Mon, 16 May 2016 10:25:22 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id i75so213037554ioa.3 for <ipv6@ietf.org>; Mon, 16 May 2016 10:25:22 -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:date:message-id:subject :from:to:cc; bh=EtyREZUyy7BIss8WJHquvWm0lS/OktGP3K7wibI6/v0=; b=Iek08VSiaLy7YSwpy4Gg7GEfs2sVC8/sHgeBvYVkQhhIFuldyGg711Y3UOdc991hs6 u7i2LEjw0wA684Sow7WWYqjrtcymo/ZSl0Z8G7PXt4SnuoNQoN7fZnS3QrR/g+kN5jVo jM474TD06Zg3pbkNA23UhR/M6uSnXClGKkDGb9iLe4gIr0dVz+yp8imbDUupbfBNswhq pYC00IVFvOyMvoo9VDsx50xMg2SAODb/okgYGIRZktLGNOdqjOiGiJ981s4fP9u7Qf2i KDikcjBjAzDfUW2GmQOwLyTFYbYE1053yRskuEKzT6lEemB6va25Y80zvrVvUHXXSAM8 0htQ==
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:date :message-id:subject:from:to:cc; bh=EtyREZUyy7BIss8WJHquvWm0lS/OktGP3K7wibI6/v0=; b=XmFM0jnyzWk373fo76tdZiBteJv/wEJ/DbaV/SIE6Nd83I46bDKovMiV1YKGBf6GlA 0331qAAa0OXMF7RH7z+0vIcSPOJXqTgXZ0X3lVbuIFV8nqLkFH56zBQECXfofyCmabmH cH/hi3jhwhT3NOc30bZrAPDC7+UDMMDPFJcmYY39NvzoJpDCFvyS38JSGHATuEwDHk9s EbsdXIIAj2AcIpTdmiaknATzSttNGMHawAmjV/MWENoAXeHPPIge5rX5WT8JVepuu0hC 9xhrR0RJEqid//2LhVN76FIXGcosvFty58qqCACQ3utKIMIggsiHAGtrlSrm+PlkeNRE kPag==
X-Gm-Message-State: AOPr4FXKLTkd38zrMtB/BoRT5fDGQb0VGZCgdtsA9HO6Gjaf9GejQHyapjYMrPpu9RCq0u+L6vb3pgtkGJpg0w==
MIME-Version: 1.0
X-Received: by 10.36.120.131 with SMTP id p125mr9812131itc.7.1463419522288; Mon, 16 May 2016 10:25:22 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Mon, 16 May 2016 10:25:22 -0700 (PDT)
In-Reply-To: <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in>
Date: Mon, 16 May 2016 10:25:22 -0700
X-Google-Sender-Auth: a7euJAgyOSPirZJDc_mUlxVkxGs
Message-ID: <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jKBzO3IkJO9bjlrTKOZRSYoRPuU>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 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: Mon, 16 May 2016 17:25:25 -0000

At Fri, 13 May 2016 13:45:37 -0700,
Alissa Cooper <alissa@cooperw.in> wrote:

> > - clarify that this recommendation is only for environments where
> >  address stability is needed
>
> The document says exactly this in the introduction:
>
> The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.  That is, this document does not
>    change any existing recommendations concerning the use of temporary
>    addresses as specified in [RFC4941 <https://tools.ietf.org/html/rfc4941>], nor does it introduce any new
>    requirements regarding when stable addresses are to be configured.
>    Thus, the recommendations in this document simply improve the
>    security and privacy properties of stable addresses.

This text specifically talks about RFC4941 as the "environments where
address stability is NOT needed", and, with the 'That is,' only talks
about it.  On the other hand, my understanding of previous concerns in
this context is to also cover other types of such environments,
specifically the one using randomized link-layer addresses with the
traditional algorithm of forming the IID from such LL addresses.

>From this one, and your response to the next point, it seems you are
saying the decision was to refuse to address that concern.  Am I
understanding it correctly?

--
JINMEI, Tatuya


From nobody Mon May 16 10:29:22 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 0A46612D889 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:29:21 -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=jV4osRaG; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ZLuAImgK
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 Y3JLFsBr-4f5 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 10:29:19 -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 4084512D887 for <ipv6@ietf.org>; Mon, 16 May 2016 10:29:19 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A117B219E0 for <ipv6@ietf.org>; Mon, 16 May 2016 13:29:18 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 16 May 2016 13:29:18 -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=ZL8wR M/qXV19M7tbn+s3Be6WTEE=; b=jV4osRaGOtf5zuEmKOkJ3J6IvVr0JaRZxhlmc 6ixXTkvrf3fzWKIz3HAakOFGaimX/NSeAPdsj4w+PcumBcC9DCOti9+Fe6vGNCEv joHKzB5idl1S9vCtKPaY3Oq0VuprTvyAZwLDiyl/Xk4/eZA8f+RBHkm9V0ApaLBH KftQSQ=
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=ZL8wRM/qXV19M7tbn+s3Be6WTEE=; b=ZLuAI mgKaApcFY1MlYlrqR1Z++H1Uns9Ywa21MMX1QDyaEawYB42PyVJJceXaTI7VS4cI OgRsqHq5Mba6ni522XNbxnCBpKXKIKkIpjERZ81S5ut/cmx5TvirTtkGbiKgL/3X HraIVqQVgkRQq8kgVO5+ofWZqBoToQ4f2/SXR8=
X-Sasl-enc: nL4D3U7JeL0C2HBFoOwEA2qFsaifCNaN2WsmgP05vH1E 1463419758
Received: from dhcp-171-68-20-133.cisco.com (dhcp-171-68-20-133.cisco.com [171.68.20.133]) by mail.messagingengine.com (Postfix) with ESMTPA id 0E702C00012; Mon, 16 May 2016 13:29:17 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8310E8CF-D506-4445-B02F-9093C490F29C"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
Date: Mon, 16 May 2016 10:29:20 -0700
Message-Id: <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oYnK14_v-3qTe-D3_xJeeg7fRL8>
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: Mon, 16 May 2016 17:29:21 -0000

--Apple-Mail=_8310E8CF-D506-4445-B02F-9093C490F29C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Lorenzo,

> On May 13, 2016, at 8:29 PM, Lorenzo Colitti <lorenzo@google.com> =
wrote:
>=20
> On Sat, May 14, 2016 at 12:00 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> =
wrote:
> Because if someone is trying to correlate different types of my =
traffic,
> let's say something sent over IPX and something sent over IPv6, the =
task
> will be made easier if the lower 48 bits are the same in both types of
> traffic. (Obviously, someone on-link can use ND to correlate MAC =
address
> and IP address, so we're talking about someone observing off-link =
packets.)
>=20
> That seems extremely unlikely to happen in practice, given that the =
vast majority of hosts either don't have an IPX stack at all or have it =
disabled by default, and embedding a MAC address in a protocol payload =
is not very useful so people tend not to do it.
>=20
> By contrast, here is one weakness that is pretty much mandated by this =
draft as written: because addresses have to be stable,

The draft does not require addresses to be stable. It changes the =
recommendations about how to generate an address in cases where a stable =
address was desired anyway.

> any remote attacker anywhere on the Internet that ever exchanges a =
packet with that host can track it every time the host visits the same =
network, *forever*, with no recourse. Section 3 point 1.
>=20
> Either we fix that or we stop asserting that this draft is motivated =
by privacy considerations.

I would frankly be thrilled if we could get away from stable addresses =
altogether. But I=E2=80=99m skeptical about the feasibility of achieving =
consensus around that at present. Defining the approach in this draft in =
the meantime is certainly motivated by consideration for privacy =
improvement for me, even if that improvement is incremental.

Alissa

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


--Apple-Mail=_8310E8CF-D506-4445-B02F-9093C490F29C
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 Lorenzo,</div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
May 13, 2016, at 8:29 PM, Lorenzo Colitti &lt;<a =
href=3D"mailto:lorenzo@google.com" class=3D"">lorenzo@google.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On Sat, May 14, 2016 at 12:00 PM, Brian E =
Carpenter <span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank" =
class=3D"">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D""><div =
class=3D""><span style=3D"color:rgb(34,34,34)" class=3D"">Because if =
someone is trying to correlate different types of my traffic,</span><br =
class=3D""></div></div>
let's say something sent over IPX and something sent over IPv6, the =
task<br class=3D"">
will be made easier if the lower 48 bits are the same in both types =
of<br class=3D"">
traffic. (Obviously, someone on-link can use ND to correlate MAC =
address<br class=3D"">
and IP address, so we're talking about someone observing off-link =
packets.)<br class=3D""></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">That seems extremely unlikely to happen =
in practice, given that the vast majority of hosts either don't have an =
IPX stack at all or have it disabled by default, and embedding a MAC =
address in a protocol payload is not very useful so people tend not to =
do it.<br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D"">By contrast, here is one weakness that is pretty much =
mandated by this draft as written: because addresses have to be stable, =
</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>The draft does not require addresses to be stable. =
It changes the recommendations about how to generate an address in cases =
where a stable address was desired anyway.</div><br class=3D""><blockquote=
 type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"">any =
remote attacker anywhere on the Internet that ever exchanges a packet =
with that host can track it every time the host visits the same network, =
*forever*, with no recourse. Section 3 point 1.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Either we fix that or we stop asserting =
that this draft is motivated by privacy =
considerations.</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>I would frankly be thrilled if we could get away =
from stable addresses altogether. But I=E2=80=99m skeptical about the =
feasibility of achieving consensus around that at present. Defining the =
approach in this draft in the meantime is certainly motivated by =
consideration for privacy improvement for me, even if that improvement =
is incremental.</div><div><br class=3D""></div><div>Alissa</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div 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></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_8310E8CF-D506-4445-B02F-9093C490F29C--


From nobody Mon May 16 13:08:49 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 8F01412D9FE for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 13:08:47 -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 0JOammCd_JCy for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 13:08:45 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::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 7CFFF12DA02 for <ipv6@ietf.org>; Mon, 16 May 2016 13:08:45 -0700 (PDT)
Received: by mail-pa0-x229.google.com with SMTP id gj5so10236988pac.2 for <ipv6@ietf.org>; Mon, 16 May 2016 13:08:45 -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=L7UX6y99mgVDZeR+vc2kUn398qncI3SLW5jrli8qVBw=; b=jMw1iBI0Iw+mbN62tc1WAJYEOmsbF4jnfqMhUJPwbi9UyEFvW1MnoBvskY3vx/Yynu v15whR5DkprfSiHtmvYTEdglTg6IfAEjJ4sc14wH3CQKFOHKEiMprnHN9MlPVWS4pOAL V4cjxAuJl9FHg8x8x/OqjgWxoMv4oNjVBmUUO5owDj5Ol4/zc1QrCg8EugPhqUgG+wEZ XUtPrXI1IuJn9yGVMjJuhkfDazE9vwpYOnavsBSTPY2SWPfvdyMc/Jy7iONcJpvHE3yX 7x1z+D/TYbH7hyaYLGlexAOuInJy64FX0J/eqmGLoHaeqfC2cKSOK2OzcbeSQS8cpTor nLtg==
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=L7UX6y99mgVDZeR+vc2kUn398qncI3SLW5jrli8qVBw=; b=isYwPm0ZQUDQktjCWT1dtqLrz1U8XwW9uIIvsbi0xPjaZaa89s5QVaIyKd6Gx+GdAI w1B0jLeMa5eVaipBuTE/qEHLAM0+KNJwwDGaKLWvSJBhYq+IxIEuLgIUKY21RYcqwY0Y /oXuAJli4uVNLhoDXA4r+LlbhXXkX9KxKtKH4DMzFF7XVVI8Wrz+ZWK7gPeNUoreb4RG YyX4KRbmeamHiLbl9+B5jbjAtEmIbanANLhjzMClP36tDXgCqkkeuu1DO8Y+1UjdGyrO ExGe1ob70ElVNuywqy7CyNvzgUhUsGaSf/JR4JTtzsl22bUeditne2xPA6LdIpPKDRDI b28g==
X-Gm-Message-State: AOPr4FUw+kIZe9QReBRUO861djhgJ2IcP3eOPaQtIAsctcZegcKtOgo71z7qWg/recdsjQ==
X-Received: by 10.66.222.100 with SMTP id ql4mr48183646pac.137.1463429325036;  Mon, 16 May 2016 13:08:45 -0700 (PDT)
Received: from ?IPv6:2406:e007:442b:1:28cc:dc4c:9703:6781? ([2406:e007:442b:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id uw2sm49286532pac.10.2016.05.16.13.08.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 13:08:43 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
To: weigengyu <weigengyu@bupt.edu.cn>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC> <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com>
Date: Tue, 17 May 2016 08:08:41 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rcZ_cC1j6SfdqO_nXFlpiOzaEzo>
Cc: 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, 16 May 2016 20:08:47 -0000

Hi Gengyu,

>> RID is not random or random identifier according to the context above.=

>>=20
>> F() is an inreverse function, not a pseudorandom function.

I agree that this is incorrect use of terminology; an irreversible hash i=
s
not mathematically equivalent to a pseudo-random number generator. But th=
e
effect is the same: an attacker has no way to predict the next F(x) or to=

obtain the value of x. As far as practical engineering goes, F() can be t=
reated
as a random number. So I don't see why this invalidates the use of RFC 72=
17.

You could submit an erratum for RFC 7217 at http://www.rfc-editor.org/err=
ata.php#reportnew
so that the terminology can be corrected when the document is updated.

Regards
   Brian Carpenter

On 16/05/2016 18:11, weigengyu wrote:
> Hi all,
>=20
> Is it not a problem to promote RFC7217 in which concept errors are exis=
ted?
>=20
> RFC7217 did not only giving a definition of stable address, but also de=
fining an algorithm to generate it.
> The algorithm contains concept error in my opinion.
>=20
>>
>>        Title           : Recommendation on Stable IPv6 Interface Ident=
ifiers
>>        Authors         : Fernando Gont
>>                          Alissa Cooper
>>                          Dave Thaler
>>                          Will Liu
>> Filename        : draft-ietf-6man-default-iids-11.txt
>> Pages           : 23
>> Date            : 2016-04-27
>>
>> Abstract:
>>   This document changes the default scheme for generating stable
>>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>>   recommends against embedding link-layer addresses in IPv6 Interface
>>   Identifiers.
>=20
>=20
> Regards,
>=20
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
>=20
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: weigengyu
> Sent: Monday, May 09, 2016 2:35 PM
> To: Alissa Cooper
> Cc: ipv6@ietf.org
> Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
>=20
> Hi=EF=BC=8C
>=20
>> This document changes the default scheme for generating stable
>   Interface Identifiers with SLAAC to that specified in RFC7217,
>=20
> There is a question about RFC7217 as this draft is to promote it.
> In RFC7217,  in Page 6 and page 7,  "5.  Algorithm Specification"
> "1.  Compute a random (but stable) identifier with the expression:
>       RID =3D F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key)=

>       Where:
>       RID:
>          Random (but stable) Identifier
>       F():
>          A pseudorandom function (PRF) that MUST NOT be computable from=

>          the outside (without knowledge of the secret key).  F() MUST
>          also be difficult to reverse, such that it resists attempts to=

>          obtain the secret_key, even when given samples of the output
>          of F() and knowledge or control of the other input parameters.=

>          F() SHOULD produce an output of at least 64 bits.  F() could
>          be implemented as a cryptographic hash of the concatenation of=

>          each of the function parameters.  SHA-1 [FIPS-SHS] and SHA-256=

>          are two possible options for F().  Note: MD5 [RFC1321] is
>          considered unacceptable for F() [RFC6151]. "
>=20
> It seems it is a concept error for RID.
> RID is not random or random identifier according to the context above.
>=20
> F() is an inreverse function, not a pseudorandom function.
> Within parameters of F(Prefix, Net_Iface, Network_ID, DAD_Counter,
> secret_key),
> only the secret_key is generated by a pseudorandom function.
> But the secret_key is also a constant because it keeps unchanged after =
being
> generated.
>=20
> There are not random features.
>=20
> The question is why it is called RID, Random ID?
>=20
>=20
> Regards,
>=20
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Alissa Cooper
> Sent: Thursday, April 28, 2016 10:41 PM
> To: IETF IPv6 Mailing List
> Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
>=20
> This version incorporates comments based on discussion before and durin=
g
> IETF 95 (thanks to Fernando for spinning the rev). I think this version=

> addresses the comments received and should be ready to move forward.
>=20
> Alissa
>=20
>=20
>> On Apr 27, 2016, at 5:49 PM, internet-drafts@ietf.org wrote:
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts dir=
ectories.
>> This draft is a work item of the IPv6 Maintenance of the IETF.
>>
>>        Title           : Recommendation on Stable IPv6 Interface Ident=
ifiers
>>        Authors         : Fernando Gont
>>                          Alissa Cooper
>>                          Dave Thaler
>>                          Will Liu
>> Filename        : draft-ietf-6man-default-iids-11.txt
>> Pages           : 23
>> Date            : 2016-04-27
>>
>> Abstract:
>>   This document changes the default scheme for generating stable
>>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>>   recommends against embedding 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, by removing the text in these RFCs
>>   that required the IPv6 Interface Identifiers to be derived from the
>>   underlying link-layer address, and replacing the aforementioned text=

>>   with a pointer to this document.  Additionally, this document update=
s
>>   RFC3315 by specifying additional requirements on the generation of
>>   Interface Identifiers used in Dynamic Host Configuration Protocol
>>   version 6 (DHCPv6).  It also provides advice to system administrator=
s
>>   who employ manual configuration.  This document does not change any
>>   existing recommendations concerning the use of temporary addresses a=
s
>>   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-11
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-default-iids-11
>>
>>
>> Please note that it may take a couple of minutes from the time of subm=
ission
>> 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
>> --------------------------------------------------------------------
>=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
> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Mon May 16 13:30:33 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 0CEC412D1C0 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 13:30:31 -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 ZNQuqACgnUAz for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 13:30:29 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::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 C74B812D138 for <ipv6@ietf.org>; Mon, 16 May 2016 13:30:29 -0700 (PDT)
Received: by mail-pa0-x235.google.com with SMTP id qo8so25843333pab.1 for <ipv6@ietf.org>; Mon, 16 May 2016 13:30:29 -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=ZdzG3fzxxKW37qIeMCOog84RpWbH03kfJODhfhFU4Ug=; b=Pvu2pTTJY6qOa0DN+Fy/hjfTUe/pOpPhPt77ycl78o3vhiMMWjpfCA3LYElNSyhqmA a4O1pZI+M1jL6QUafeb5mCESdXB/iwapnSz0kQel7fdgSWc0A/l8qKVKI13fcTidR2X/ 2mLKP+FjhDfwG6XTQ6KGzyx6sZzfOUL8ra5qiQF2W051YTDAq4NCt2wafBc7Cv2UYTD0 b67lBrMxCvnNIgcnomE4k5tBooVdVi9jBBWOz/6kEBjWySFrwfzxV8ToKVIISP7lNFj5 V+TvyDNn7bZck9W587sw0BGTdV0nIVESKBoXeEt+Z9xtSGV0xPRyFs754aWj5qXVK5P5 ZVvw==
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=ZdzG3fzxxKW37qIeMCOog84RpWbH03kfJODhfhFU4Ug=; b=SudAeBU6SDtltuaF3MSMxsJNQGMJfrcwVOb5JTzWpKobsrDqi4bwl+azN5m1kdhYDW ekOG0J/0TDfmoNA4eazRT1yQeGppMJl/lu9tlyz4PKbypeF0SeFGG10ZHIfHgNA1t92k uHIz0Ff+bu4jflzWfOYFVfdDWK9sD0YVlAsXsP1R4Pb2WSMk3l5dOtdf8BvTzmWnin/I DpJ71I5mR5H4TKNMXj9+wjqcq4WnOKmSwdoMXjHk75lxnEZZun1bCo6rP4InHwZLyFn+ eF83Q9G+av8cg/CH5d8uznCY8l8lqhECtcVjfUDWpgQTSyWbVske4/yh/b7m/IkywKLq 7Zpg==
X-Gm-Message-State: AOPr4FWmtOw1Do3qYOLW8XgwWweR9F0aE+5Eiw3WvytYnXiIyxrXefbp0pfE8awm//6Ubg==
X-Received: by 10.66.139.70 with SMTP id qw6mr47811660pab.67.1463430629444; Mon, 16 May 2016 13:30:29 -0700 (PDT)
Received: from ?IPv6:2406:e007:442b:1:28cc:dc4c:9703:6781? ([2406:e007:442b:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id w187sm49222419pfw.50.2016.05.16.13.30.26 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 13:30:27 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
Date: Tue, 17 May 2016 08:30:27 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LzkX8VZQ8bmelo5ChQQ5zY2o9Lg>
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: Mon, 16 May 2016 20:30:31 -0000

On 17/05/2016 05:29, Alissa Cooper wrote:
> Hi Lorenzo,
>=20
>> On May 13, 2016, at 8:29 PM, Lorenzo Colitti <lorenzo@google.com> wrot=
e:

=2E..
>> any remote attacker anywhere on the Internet that ever exchanges a pac=
ket with that host can track it every time the host visits the same netwo=
rk, *forever*, with no recourse. Section 3 point 1.
>>
>> Either we fix that or we stop asserting that this draft is motivated b=
y privacy considerations.
>=20
> I would frankly be thrilled if we could get away from stable addresses =
altogether. But I=E2=80=99m skeptical about the feasibility of achieving =
consensus around that at present. Defining the approach in this draft in =
the meantime is certainly motivated by consideration for privacy improvem=
ent for me, even if that improvement is incremental.

Exactly. There is a tussle between enterprise or campus network operators=
 who
have a strong desire for stable addresses (such that they can identify mi=
screants)
and individuals who want to avoid tracking (such that they can avoid surv=
eillance).
That tussle is not going to go away any time soon, so stable client IIDs =
are not
going away either.

I don't expect enterprise or campus operators to react well to pseudo-ran=
dom MAC
addresses, either.

    Brian



From nobody Mon May 16 14:15:45 2016
Return-Path: <joelja@bogus.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 5C7E512DAA2 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 14:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 exX9syCIoXIN for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 14:15:42 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 BF89312DAB4 for <ipv6@ietf.org>; Mon, 16 May 2016 14:15:41 -0700 (PDT)
Received: from mb-2.local ([IPv6:2620:11a:c081:20:5dd6:919b:d3f7:5bc6]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4GLFZNA050344 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 16 May 2016 21:15:35 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:5dd6:919b:d3f7:5bc6] claimed to be mb-2.local
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <291def3f-bc2b-47bf-ffc6-371bbdde0bfe@bogus.com>
Date: Mon, 16 May 2016 14:15:34 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1
MIME-Version: 1.0
In-Reply-To: <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qnveRLwUsdVTv8g1iRA86ft22CUL557UD"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uED2LvFzzPC_Z-cYp3qQTiFjicA>
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: Mon, 16 May 2016 21:15:43 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--qnveRLwUsdVTv8g1iRA86ft22CUL557UD
Content-Type: multipart/mixed; boundary="FfrL68x91Ap0O35x4UMq8Gm9qv73r8LLh"
From: joel jaeggli <joelja@bogus.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,
 Alissa Cooper <alissa@cooperw.in>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Message-ID: <291def3f-bc2b-47bf-ffc6-371bbdde0bfe@bogus.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com>
 <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
 <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com>
 <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
 <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com>
 <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com>
 <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com>
 <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
 <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
 <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
In-Reply-To: <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>

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

On 5/16/16 1:30 PM, Brian E Carpenter wrote:
> On 17/05/2016 05:29, Alissa Cooper wrote:
>> Hi Lorenzo,
>>
>>> On May 13, 2016, at 8:29 PM, Lorenzo Colitti <lorenzo@google.com> wro=
te:
>=20
> ...
>>> any remote attacker anywhere on the Internet that ever exchanges a pa=
cket with that host can track it every time the host visits the same netw=
ork, *forever*, with no recourse. Section 3 point 1.
>>>
>>> Either we fix that or we stop asserting that this draft is motivated =
by privacy considerations.
>>
>> I would frankly be thrilled if we could get away from stable addresses=
 altogether. But I=E2=80=99m skeptical about the feasibility of achieving=
 consensus around that at present. Defining the approach in this draft in=
 the meantime is certainly motivated by consideration for privacy improve=
ment for me, even if that improvement is incremental.
>=20
> Exactly. There is a tussle between enterprise or campus network operato=
rs who
> have a strong desire for stable addresses (such that they can identify =
miscreants)
> and individuals who want to avoid tracking (such that they can avoid su=
rveillance).
> That tussle is not going to go away any time soon, so stable client IID=
s are not
> going away either.
>=20
> I don't expect enterprise or campus operators to react well to pseudo-r=
andom MAC
> addresses, either.

So long as they're as long lived as your 802.1x or wpa2 enterprise
association, it's not really a big deal what your mac address is.
port-security methods already get tetchy when you abandon your previous
identity in favor of a new one without disconnecting or re-authentication=
=2E

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



--FfrL68x91Ap0O35x4UMq8Gm9qv73r8LLh--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlc6OHcACgkQ8AA1q7Z/VrLxtACeNcdYaNeEnJEnWGreGNTzKGSi
VQgAniEmFgPojgBZD6SuGdwHEZKjv0hT
=FiT2
-----END PGP SIGNATURE-----

--qnveRLwUsdVTv8g1iRA86ft22CUL557UD--


From nobody Mon May 16 14:38:44 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 CDAD512D531 for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 14:38:42 -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 bBDHaku0cW3n for <ipv6@ietfa.amsl.com>; Mon, 16 May 2016 14:38:41 -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 AE97B12D162 for <ipv6@ietf.org>; Mon, 16 May 2016 14:38:41 -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 u4GLcebh017969; Mon, 16 May 2016 14:38:40 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4GLcXAi017908 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 16 May 2016 14:38:34 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 16 May 2016 14:38:33 -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; Mon, 16 May 2016 14:38:33 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Index: AQHRr5h6ds/q2L9cuUSJt7x/B74y5Z+8ebeA//+brGA=
Date: Mon, 16 May 2016 21:38:33 +0000
Message-ID: <bf8f2c4a42a14ce7a8dca1ade97e6963@XCH15-06-11.nw.nos.boeing.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
In-Reply-To: <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com>
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: <http://mailarchive.ietf.org/arch/msg/ipv6/_lN8ZYx-ntPjB11d4nug0u5BXoE>
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: Mon, 16 May 2016 21:38:43 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQnJpYW4gRSBDYXJwZW50ZXINCg0KPiBFeGFj
dGx5LiBUaGVyZSBpcyBhIHR1c3NsZSBiZXR3ZWVuIGVudGVycHJpc2Ugb3IgY2FtcHVzIG5ldHdv
cmsgb3BlcmF0b3JzIHdobw0KPiBoYXZlIGEgc3Ryb25nIGRlc2lyZSBmb3Igc3RhYmxlIGFkZHJl
c3NlcyAoc3VjaCB0aGF0IHRoZXkgY2FuIGlkZW50aWZ5DQo+IG1pc2NyZWFudHMpDQo+IGFuZCBp
bmRpdmlkdWFscyB3aG8gd2FudCB0byBhdm9pZCB0cmFja2luZyAoc3VjaCB0aGF0IHRoZXkgY2Fu
IGF2b2lkDQo+IHN1cnZlaWxsYW5jZSkuDQo+IFRoYXQgdHVzc2xlIGlzIG5vdCBnb2luZyB0byBn
byBhd2F5IGFueSB0aW1lIHNvb24sIHNvIHN0YWJsZSBjbGllbnQgSUlEcyBhcmUNCj4gbm90DQo+
IGdvaW5nIGF3YXkgZWl0aGVyLg0KPiANCj4gSSBkb24ndCBleHBlY3QgZW50ZXJwcmlzZSBvciBj
YW1wdXMgb3BlcmF0b3JzIHRvIHJlYWN0IHdlbGwgdG8gcHNldWRvLXJhbmRvbQ0KPiBNQUMNCj4g
YWRkcmVzc2VzLCBlaXRoZXIuDQoNCkFuZCBhbHNvLCBsZXQncyBub3QgZm9yZ2V0IHRoYXQgSVAg
bmV0cyBhcmUgbm90IHVzZWQgZXhjbHVzaXZlbHkgZm9yIGNvbnN1bWVyIG9yaWVudGVkIGFwcGxp
YW5jZXMuIEluIGFkZGl0aW9uIHRvIGVudGVycHJpc2UgbmV0cywgd2hpY2ggaGF2ZSBkaWZmZXJl
bnQgY3JpdGVyaWEgZnJvbSBwcml2YXRlIHVzZXJzIG92ZXIgSVNQcywgdGhlcmUgYXJlIGNvbnRy
b2wgc3lzdGVtIG5ldHdvcmtzLiBPbiBmYWN0b3J5IGZsb29ycywgaW4gYWxsIG1hbm5lciBvZiB2
ZWhpY2xlcywgYW5kIHNvIG9uLiBOZXR3b3JrcyBydW5uaW5nIG1hY2hpbmVyeSwgcHJvdmlkaW5n
IG5hdmlnYXRpb24gZGF0YSwgYW5kIG9uIGFuZCBvbi4NCg0KUHJpdmFjeSBvZiBhbiBpbmRpdmlk
dWFsIHVzZXIsIG9yIG9mIGFuIGluZGl2aWR1YWwgaG9zdCwgaXMgZXhhY3RseSB3aGF0IHRoZXNl
IG5ldHdvcmtzIGNhbm5vdCBhbGxvdy4gU28gbm8sIEkgZG9uJ3Qgc2VlIGEgZnV0dXJlIGluIHdo
aWNoIHRoZXJlIGFyZSBubyBzdGFibGUgYWRkcmVzc2VzLg0KDQpCZXJ0DQoNCg==


From nobody Tue May 17 00:41:11 2016
Return-Path: <sprevidi@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 E964112D59B; Tue, 17 May 2016 00:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 NQnQhamWxy5e; Tue, 17 May 2016 00:41:05 -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 1912F12D589; Tue, 17 May 2016 00:41:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9590; q=dns/txt; s=iport; t=1463470865; x=1464680465; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=6TjoHVIqnWQz3ISn+OUC6ZbrLQ4ARgP7GpIhwhqauTQ=; b=T53llUUjvD8bl31JCQLKjqSR2wQ8kFvinoMfluWte2NvggPugE9957G9 ibHDED9zrVrUzq+eGdKo74GF7PuSkfiPFWJfUVXzlomjl28Ga9cCJFgju h361QUt0BBaCe4ZZ9oxAHROxnLcxQHijPO9c40vaw+xRU6NLkxD9limZ6 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BkAgC3yTpX/5BdJa1dgzdVfga5agENg?= =?us-ascii?q?XYXC4VvAhyBFjgUAQEBAQEBAWUnhEIBAQEDAQEBASAROgsFBwQCAQgRBAEBAQI?= =?us-ascii?q?CERIDAgICJQsUAQgIAgQOBYgnCA6xCZFxAQEBAQEBAQEBAQEBAQEBAQEBAQEBF?= =?us-ascii?q?wWBAYUkgXYIgk+EViiCQSuCLgWHfpAqAY4dgWmNMIYtiRMBHgEBQoNsboZIBzh?= =?us-ascii?q?/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,324,1459814400"; d="scan'208";a="108797071"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 May 2016 07:41:04 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u4H7f3NE032017 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 May 2016 07:41:03 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 17 May 2016 03:41:03 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Tue, 17 May 2016 03:41:03 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Tom Herbert <tom@herbertland.com>
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAa+DiAAB8pfIAAAC4LAAAEgrGAAAA7KQAAACaYgAAAScIAAAvLbYAAHmtYgA==
Date: Tue, 17 May 2016 07:41:02 +0000
Message-ID: <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com>
In-Reply-To: <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.80.155]
Content-Type: text/plain; charset="utf-8"
Content-ID: <04F7E1B83AEA4546B7C3E96661CB11BF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/s_pu1IahwCE1x23JEmWki8pL9Dg>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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, 17 May 2016 07:41:07 -0000

DQo+IE9uIE1heSAxNiwgMjAxNiwgYXQgNzoxMCBQTSwgVG9tIEhlcmJlcnQgPHRvbUBoZXJiZXJ0
bGFuZC5jb20+IHdyb3RlOg0KPiANCj4gT24gTW9uLCBNYXkgMTYsIDIwMTYgYXQgNDozMiBBTSwg
VGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29tPiB3cm90ZToNCj4+PiBpdOKAmXMgYWxsIGFi
b3V0IElQLCBub3QgbGF5ZXItMi4NCj4+PiANCj4+PiBzLg0KPj4gDQo+PiBSaWdodC4gSG93ZXZl
ciwgaXQgYXBwZWFycyB0aGF0IGF0IGxlYXN0IGluIHNvbWUgY2FzZXMgYSBWWExBTiBWVEVQIHdp
bGwgdXNlIFNSLiBJdCBjZXJ0YWlubHkgbWF5IGJlIHRoZSBjYXNlIGluIFNGQyB1c2UgY2FzZXMg
KHNlZSBTZWN0aW9uIDIuMyBpbiBkcmFmdC1pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcykuDQo+
PiANCj4gDQo+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIG1lbnRpb25z
IHRoYXQgdGhlIHBhY2tldCBpcw0KPiBlbmNhcHN1bGF0ZWQNCg0KDQppbnRvIGFuIG91dGVyIGlw
djYgaGVhZGVyIHdoaWNoIG1ha2VzIGl0IGEgbGF5ZXItMyBlbmNhcC4NCg0KDQo+ICwgYnV0IEkg
ZG9uJ3QgdGhpbmsgaXQgaXMgZXhwbGljaXQgYXMgdG8gZXhhY3QNCj4gZW5jYXBzdWxhdGlvbiBm
b3JtYXQgKEkgc3VwcG9zZSBzaW1wbGUgaXA2aXA2IGlzIGltcGxpZWQpLg0KDQoNCnNlZSBzZWN0
aW9uIDIuMg0KDQoNCj4gQnV0LCBpdA0KPiBzZWVtcyBsaWtlIGFueSBvZiBzZXZlcmFsIGVuY2Fw
c3VsYXRpb24gdGVjaG5pcXVlcyBjb3VsZCB3b3JrIChWWExBTiwNCg0KDQpJIGhhdmUgc29tZSBw
cm9ibGVtcyB0byB1bmRlcnN0YW5kIHdoZXJlIHRvIGZpdCBhbiBleHRlbnNpb24gaGVhZGVyIGlu
dG8gYSB2eGxhbiBlbmNhcOKApg0KDQoNCj4gR1JFL0lQLCBFU1AvSVAsIEdVRSwgZm9vIG92ZXIg
VURQLCBldGMuKSBhbmQgaWYgYSBkZXZpY2UgdGhhdCB3YW50cyB0bw0KPiBkbyBTUiBpcyBhbHJl
YWR5IGRvaW5nIHR1bm5lbGluZyBpdCBzZWVtcyByZWFzb25hYmxlIHRvIG1lIHRvIG9ubHkNCj4g
aGF2ZSBvbmUgbGF5ZXIgb2YgZW5jYXBzdWxhdGlvbi4gTWF5YmUgdGhpcyBzaG91bGQgYmUgY2xh
cmlmaWVkIGluIHRoZQ0KPiBkcmFmdD8NCg0KDQp0aGUgZHJhZnQgaXMgYWJvdXQgSVB2NiBleHRl
bnNpb24gaGVhZGVyIGFuZCBtb3JlIHByZWNpc2VseSBhIG5ldyB0eXBlIG9mIHRoZSByb3V0aW5n
IGV4dGVuc2lvbiBoZWFkZXIgZGVmaW5lZCBpbiByZmMyNDYwLiBUaGF04oCZcyB0aGUgY29udGV4
dC4NCg0KDQpzLg0KDQoNCg0KDQo+IA0KPiBUb20NCj4gDQo+PiANCj4+IA0KPj4+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4gRnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkg
W21haWx0bzpzcHJldmlkaUBjaXNjby5jb21dDQo+Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYsIDIw
MTYgMjoyNCBQTQ0KPj4+IFRvOiBUYWwgTWl6cmFoaQ0KPj4+IENjOiBPbGUgVHLDuGFuOyBkcmFm
dC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsNCj4+PiBz
cHJpbmdAaWV0Zi5vcmc7IDZtYW4gV0cNCj4+PiBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hl
Y2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctDQo+Pj4gaGVhZGVyDQo+
Pj4gDQo+Pj4gDQo+Pj4+IE9uIE1heSAxNiwgMjAxNiwgYXQgMToxOSBQTSwgVGFsIE1penJhaGkg
PHRhbG1pQG1hcnZlbGwuY29tPiB3cm90ZToNCj4+Pj4gDQo+Pj4+IEhpIFN0ZWZhbm8sDQo+Pj4+
IA0KPj4+PiBUaGFua3MgYWdhaW4gZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuDQo+Pj4+IA0KPj4+
Pj4gMi4gdGhlIFNSSCBpcyBvcmlnaW5hdGVkIGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNS
IGRvbWFpbi4NCj4+Pj4+IFRoaXMgaXMgZG9uZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQg
aW50byBhIG91dGVyDQo+Pj4+PiAoYWRkaXRpb25hbCkgaXB2NiBoZWFkZXIgZm9sbG93ZWQgYnkg
YW4gU1JILiBUaGlzIGlzIEwzDQo+Pj4+PiBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1
bSBpcyBpbnZvbHZlZC4gV2hlbiB0aGUgIHBhY2tldCBsZWF2ZXMNCj4+Pj4+IHRoZSBTUiB0dW5u
ZWwgdGhlIG91dGVyIGVuY2Fwc3VsYXRpb24gIChpbmNsdWRpbmcgdGhlIFNSSCkgaXMgcmVtb3Zl
ZA0KPj4+Pj4gYW5kIHRoZSBwYWNrZXQgY29udGludWVzICBpdHMgam91cm5leSBsaWtlIG5vdGhp
bmcgaGFwcGVuZWQuDQo+Pj4+IA0KPj4+PiBTbyBWWExBTiBpcyBvZmYgdGhlIHRhYmxlPw0KPj4+
IA0KPj4+IA0KPj4+IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLg0KPj4+IA0KPj4+
IHMuDQo+Pj4gDQo+Pj4gDQo+Pj4+IEl0IHdvdWxkIGJlIHdvcnRod2hpbGUgdG8gY2xhcmlmeSB0
aGlzIGluIHRoZSBkcmFmdC4gSWYgeW91IGhhdmUgYSBzcGVjaWZpYw0KPj4+IGVuY2Fwc3VsYXRp
b24gaW4gbWluZCwgaXQgd291bGQgYmUgZ3JlYXQgaWYgdGhlIGRyYWZ0IHdvdWxkIHNwZWNpZnkg
aXQuDQo+Pj4+IA0KPj4+PiBUaGFua3MsDQo+Pj4+IFRhbC4NCj4+Pj4gDQo+Pj4+IA0KPj4+Pj4g
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+IEZyb206IFN0ZWZhbm8gUHJldmlkaSAo
c3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0KPj4+Pj4gU2VudDogTW9uZGF5
LCBNYXkgMTYsIDIwMTYgMjoxMyBQTQ0KPj4+Pj4gVG86IFRhbCBNaXpyYWhpDQo+Pj4+PiBDYzog
T2xlIFRyw7hhbjsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMu
aWV0Zi5vcmc7DQo+Pj4+PiBzcHJpbmdAaWV0Zi5vcmc7IDZtYW4gV0cNCj4+Pj4+IFN1YmplY3Q6
IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQNCj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdt
ZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+Pj4gDQo+Pj4+PiBIaSwNCj4+Pj4+IA0KPj4+Pj4gT24g
TWF5IDE2LCAyMDE2LCBhdCAxMTowNCBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29t
PiB3cm90ZToNCj4+Pj4+PiANCj4+Pj4+PiBIaSBTdGVmYW5vLA0KPj4+Pj4+IA0KPj4+Pj4+IFRo
YW5rcyBmb3IgdGhlIHJlc3BvbnNlcy4NCj4+Pj4+PiANCj4+Pj4+Pj4gZXhhY3RseS4NCj4+Pj4+
Pj4gDQo+Pj4+Pj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhl
YWRlciBhc3N1bWVzDQo+Pj4+Pj4+IGVuY2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMg
bm8gTDQgaW52b2x2ZWQgaGVyZS4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IHMuDQo+Pj4+Pj4gDQo+Pj4+
Pj4gVHdvIHF1ZXN0aW9uczoNCj4+Pj4+PiAxLiBXaGF0IGlmIHRoZSBlbmNhcHN1bGF0aW9uIGlz
IFZYTEFOPyBMNCB3b3VsZCBzdGlsbCBiZSBpbnZvbHZlZCwgcmlnaHQ/DQo+Pj4+PiANCj4+Pj4+
IA0KPj4+Pj4gU2VlIGJlbG93Lg0KPj4+Pj4gDQo+Pj4+PiANCj4+Pj4+PiAyLiBXaGVuIHlvdSBz
YXkgJ2Fzc3VtZXMgZW5jYXBzdWxhdGlvbicsIGRvZXMgaXQgbWVhbiB0aGF0IGEgaG9zdA0KPj4+
Pj4+IGNhbm5vdA0KPj4+Pj4gc2VuZCBhbiBJUHY2IHBhY2tldCB3aXRoIGFuIFNSSD8gVGhlIGN1
cnJlbnQgZHJhZnQgc2F5czoNCj4+Pj4+PiANCj4+Pj4+PiBBIFNvdXJjZSBTUiBOb2RlIGNhbiBi
ZSBhbnkgbm9kZSBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tldCB3aXRoDQo+Pj4+Pj4gaXRzDQo+
Pj4+Pj4gSVB2NiBhbmQgU2VnbWVudCBSb3V0aW5nIEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0
aGVyOg0KPj4+Pj4+IA0KPj4+Pj4+ICAgIEEgaG9zdCBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tl
dC4NCj4+Pj4+PiANCj4+Pj4+PiAgICBBbiBTUiBkb21haW4gaW5ncmVzcyByb3V0ZXIgZW5jYXBz
dWxhdGluZyBhIHJlY2VpdmVkIElQdjYgcGFja2V0DQo+Pj4+Pj4gICAgaW50byBhbiBvdXRlciBJ
UHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguDQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+Pj4g
DQo+Pj4+Pj4gV2lsbCBhcHByZWNpYXRlIGlmIHlvdSBjYW4gY2xhcmlmeSB0aGF0Lg0KPj4+Pj4g
DQo+Pj4+PiANCj4+Pj4+IG9rLCB0d28gY2FzZXM6DQo+Pj4+PiANCj4+Pj4+IDEuIHRoZSBTUkgg
aXMgaW5zZXJ0ZWQgYXQgdGhlIHNvdXJjZS4NCj4+Pj4+IHRoZSBzb3VyY2Ugb3JpZ2luYXRlcyB0
aGUgcGFja2V0LCB0aGUgaXB2NiBoZWFkZXIgYW5kICB0aGUgU1JILiBUaGUNCj4+Pj4+IHNvdXJj
ZSBjb21wdXRlcyBMNCBjaGVja3N1bSB0YWtpbmcgaW50byAgYWNjb3VudCB0aGUgd2hvbGUgSVB2
NitTUkguDQo+Pj4+PiBIZXJlLCB0aGVyZXPigJkgbm90aGluZyBuZXcgIGNvbXBhcmVkIHRvIHJm
YzI0NjAuDQo+Pj4+PiANCj4+Pj4+IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBieSB0aGUgaW5n
cmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+Pj4+PiBUaGlzIGlzIGRvbmUgYnkgZW5jYXBz
dWxhdGluZyB0aGUgcGFja2V0IGludG8gYSBvdXRlcg0KPj4+Pj4gKGFkZGl0aW9uYWwpIGlwdjYg
aGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMw0KPj4+Pj4gZW5jYXBzdWxhdGlv
biBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlICBwYWNrZXQgbGVhdmVz
DQo+Pj4+PiB0aGUgU1IgdHVubmVsIHRoZSBvdXRlciBlbmNhcHN1bGF0aW9uICAoaW5jbHVkaW5n
IHRoZSBTUkgpIGlzIHJlbW92ZWQNCj4+Pj4+IGFuZCB0aGUgcGFja2V0IGNvbnRpbnVlcyAgaXRz
IGpvdXJuZXkgbGlrZSBub3RoaW5nIGhhcHBlbmVkLg0KPj4+Pj4gDQo+Pj4+PiBzLg0KPj4+Pj4g
DQo+Pj4+PiANCj4+Pj4+PiANCj4+Pj4+PiBUaGFua3MsDQo+Pj4+Pj4gVGFsLg0KPj4+Pj4+IA0K
Pj4+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+Pj4+PiBGcm9tOiBTdGVmYW5v
IFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbV0NCj4+Pj4+Pj4g
U2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYgMTE6NTkgQU0NCj4+Pj4+Pj4gVG86IE9sZSBUcsO4
YW47IFRhbCBNaXpyYWhpDQo+Pj4+Pj4+IENjOiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0
aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsNCj4+Pj4+Pj4gc3ByaW5nQGlldGYub3JnOyA2bWFu
IFdHDQo+Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQNCj4+Pj4+
Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVhZGVyDQo+Pj4+Pj4+IA0KPj4+
Pj4+PiANCj4+Pj4+Pj4+IE9uIE1heSAxNSwgMjAxNiwgYXQgODowNiBQTSwgb3Ryb2FuQGVtcGxv
eWVlcy5vcmcgd3JvdGU6DQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+IFRhbCwNCj4+Pj4+Pj4+IA0KPj4+
Pj4+Pj4+IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQgYmVmb3Jl
Ll0NCj4+Pj4+Pj4+PiANCj4+Pj4+Pj4+PiBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0Zi02bWFuLXNl
Z21lbnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSDQo+Pj4+Pj4+Pj4gU2VnbWVudA0KPj4+Pj4+
PiBFbmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQIGFkZHJlc3MuDQo+
Pj4+Pj4+Pj4gVGhlcmVmb3JlLCBpdCBtdXN0IGFsc28gdXBkYXRlIHRoZSBMYXllciA0IENoZWNr
c3VtLCByaWdodD8NCj4+Pj4+Pj4+PiANCj4+Pj4+Pj4+PiBJIHdvbmRlciBpZiB0aGVyZSBpcyBh
biB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0aGUgU1JILg0KPj4+Pj4+Pj4+IE90aGVyd2lz
ZSwgdGhlDQo+Pj4+Pj4+IEw0IENoZWNrc3VtIG1heSBiZSBsb2NhdGVkIGluIGEgcHJldHR5IGRl
ZXAgbG9jYXRpb24uDQo+Pj4+Pj4+Pj4gU3BlYWtpbmcgZnJvbSBhIGNoaXAgdmVuZG9y4oCZcyBw
ZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0uDQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+IEZy
b20gUkZDMjQ2MCwgUkgwOg0KPj4+Pj4+Pj4gDQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+ICAgbyAgSWYg
dGhlIElQdjYgcGFja2V0IGNvbnRhaW5zIGEgUm91dGluZyBoZWFkZXIsIHRoZSBEZXN0aW5hdGlv
bg0KPj4+Pj4+Pj4gICAgICBBZGRyZXNzIHVzZWQgaW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhh
dCBvZiB0aGUgZmluYWwNCj4+Pj4+Pj4+ICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3JpZ2lu
YXRpbmcgbm9kZSwgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4NCj4+Pj4+Pj4+ICAgICAgdGhlIGxh
c3QgZWxlbWVudCBvZiB0aGUgUm91dGluZyBoZWFkZXI7IGF0IHRoZSByZWNpcGllbnQocyksDQo+
Pj4+Pj4+PiAgICAgIHRoYXQgYWRkcmVzcyB3aWxsIGJlIGluIHRoZSBEZXN0aW5hdGlvbiBBZGRy
ZXNzIGZpZWxkIG9mIHRoZQ0KPj4+Pj4+Pj4gICAgICBJUHY2IGhlYWRlci4NCj4+Pj4+Pj4+IA0K
Pj4+Pj4+Pj4gSSB3b3VsZCBleHBlY3QgU1Igd291bGQgd29yayB0aGUgc2FtZS4NCj4+Pj4+Pj4g
DQo+Pj4+Pj4+IA0KPj4+Pj4+PiBleGFjdGx5Lg0KPj4+Pj4+PiANCj4+Pj4+Pj4gTW9yZW92ZXIs
IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4+Pj4g
ZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLg0K
Pj4+Pj4+PiANCj4+Pj4+Pj4gcy4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IA0KPj4+Pj4+Pj4gDQo+Pj4+
Pj4+PiBDaGVlcnMsDQo+Pj4+Pj4+PiBPbGUNCj4+Pj4+Pj4+IA0KPj4+Pj4+IA0KPj4+PiANCj4+
IA0KPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCj4+IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlz
dA0KPj4gaXB2NkBpZXRmLm9yZw0KPj4gQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2Ng0KPj4gLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0K


From nobody Tue May 17 02:08:50 2016
Return-Path: <talmi@marvell.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 E948412D0B2; Tue, 17 May 2016 02:08:46 -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 YeR8OVrA51Wj; Tue, 17 May 2016 02:08:39 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 16F5C12B056; Tue, 17 May 2016 02:08:39 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4H97J0I029093; Tue, 17 May 2016 02:08:36 -0700
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0a-0016f401.pphosted.com with ESMTP id 22xc8c963k-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 May 2016 02:08:36 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 17 May 2016 12:08:32 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Tue, 17 May 2016 12:08:32 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, Tom Herbert <tom@herbertland.com>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@tools.ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AdGuiiq1HeAHjjuQREGOx9vVjNXiwQAMTSCAAB8pyYAABk9dsP//8wwA///NLLCAADXfAP//zJ5wgACUC4CAAPNZAP//xdYw
Date: Tue, 17 May 2016 09:08:32 +0000
Message-ID: <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com>
In-Reply-To: <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-17_03:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605170115
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/y3NMNsTm9eGBItkq0-X1WOaI1i0>
Cc: "spring@ietf.org" <spring@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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, 17 May 2016 09:08:47 -0000

U3RlZmFubywNCg0KSWYgSSB1bmRlcnN0YW5kIHlvdXIgcG9pbnQgY29ycmVjdGx5Og0KSVB2NiBz
ZWdtZW50IHJvdXRpbmcgZG9lcyBub3Qgd29yayB3aXRoIFZYTEFOIC8gVlhMQU4tR1BFIC8gR2Vu
ZXZlLCBzaW5jZSB0aGVzZSBlbmNhcHN1bGF0aW9ucyBkbyBub3QgY3VycmVudGx5IGFsbG93IHRo
ZSB1c2Ugb2YgSVB2NiBleHRlbnNpb24gaGVhZGVycy4NCg0KSSB3b25kZXIgaWYgdGhlIGF1dGhv
cnMgb2YgVlhMQU4tR1BFIGFuZCBHZW5ldmUgaGF2ZSBjb25zaWRlcmVkIHRoZSB1c2Ugb2Ygc2Vn
bWVudCByb3V0aW5nLg0KDQpUaGFua3MsDQpUYWwuDQoNCg0KDQo+LS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj5Gcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2
aWRpQGNpc2NvLmNvbV0NCj5TZW50OiBUdWVzZGF5LCBNYXkgMTcsIDIwMTYgMTA6NDEgQU0NCj5U
bzogVG9tIEhlcmJlcnQNCj5DYzogVGFsIE1penJhaGk7IDZtYW4gV0c7IHNwcmluZ0BpZXRmLm9y
ZzsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0NCj5oZWFkZXJAdG9vbHMuaWV0Zi5v
cmcNCj5TdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1h
bi1zZWdtZW50LXJvdXRpbmctDQo+aGVhZGVyDQo+DQo+DQo+PiBPbiBNYXkgMTYsIDIwMTYsIGF0
IDc6MTAgUE0sIFRvbSBIZXJiZXJ0IDx0b21AaGVyYmVydGxhbmQuY29tPiB3cm90ZToNCj4+DQo+
PiBPbiBNb24sIE1heSAxNiwgMjAxNiBhdCA0OjMyIEFNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFy
dmVsbC5jb20+DQo+d3JvdGU6DQo+Pj4+IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0y
Lg0KPj4+Pg0KPj4+PiBzLg0KPj4+DQo+Pj4gUmlnaHQuIEhvd2V2ZXIsIGl0IGFwcGVhcnMgdGhh
dCBhdCBsZWFzdCBpbiBzb21lIGNhc2VzIGEgVlhMQU4gVlRFUCB3aWxsDQo+dXNlIFNSLiBJdCBj
ZXJ0YWlubHkgbWF5IGJlIHRoZSBjYXNlIGluIFNGQyB1c2UgY2FzZXMgKHNlZSBTZWN0aW9uIDIu
MyBpbiBkcmFmdC0NCj5pZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcykuDQo+Pj4NCj4+DQo+PiBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBtZW50aW9ucyB0aGF0IHRoZSBw
YWNrZXQgaXMNCj4+IGVuY2Fwc3VsYXRlZA0KPg0KPg0KPmludG8gYW4gb3V0ZXIgaXB2NiBoZWFk
ZXIgd2hpY2ggbWFrZXMgaXQgYSBsYXllci0zIGVuY2FwLg0KPg0KPg0KPj4gLCBidXQgSSBkb24n
dCB0aGluayBpdCBpcyBleHBsaWNpdCBhcyB0byBleGFjdCBlbmNhcHN1bGF0aW9uIGZvcm1hdCAo
SQ0KPj4gc3VwcG9zZSBzaW1wbGUgaXA2aXA2IGlzIGltcGxpZWQpLg0KPg0KPg0KPnNlZSBzZWN0
aW9uIDIuMg0KPg0KPg0KPj4gQnV0LCBpdA0KPj4gc2VlbXMgbGlrZSBhbnkgb2Ygc2V2ZXJhbCBl
bmNhcHN1bGF0aW9uIHRlY2huaXF1ZXMgY291bGQgd29yayAoVlhMQU4sDQo+DQo+DQo+SSBoYXZl
IHNvbWUgcHJvYmxlbXMgdG8gdW5kZXJzdGFuZCB3aGVyZSB0byBmaXQgYW4gZXh0ZW5zaW9uIGhl
YWRlciBpbnRvIGENCj52eGxhbiBlbmNhcOKApg0KPg0KPg0KPj4gR1JFL0lQLCBFU1AvSVAsIEdV
RSwgZm9vIG92ZXIgVURQLCBldGMuKSBhbmQgaWYgYSBkZXZpY2UgdGhhdCB3YW50cyB0bw0KPj4g
ZG8gU1IgaXMgYWxyZWFkeSBkb2luZyB0dW5uZWxpbmcgaXQgc2VlbXMgcmVhc29uYWJsZSB0byBt
ZSB0byBvbmx5DQo+PiBoYXZlIG9uZSBsYXllciBvZiBlbmNhcHN1bGF0aW9uLiBNYXliZSB0aGlz
IHNob3VsZCBiZSBjbGFyaWZpZWQgaW4gdGhlDQo+PiBkcmFmdD8NCj4NCj4NCj50aGUgZHJhZnQg
aXMgYWJvdXQgSVB2NiBleHRlbnNpb24gaGVhZGVyIGFuZCBtb3JlIHByZWNpc2VseSBhIG5ldyB0
eXBlIG9mIHRoZQ0KPnJvdXRpbmcgZXh0ZW5zaW9uIGhlYWRlciBkZWZpbmVkIGluIHJmYzI0NjAu
IFRoYXTigJlzIHRoZSBjb250ZXh0Lg0KPg0KPg0KPnMuDQo+DQo+DQo+DQo+DQo+Pg0KPj4gVG9t
DQo+Pg0KPj4+DQo+Pj4NCj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4gRnJv
bTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJldmlkaUBjaXNjby5jb21d
DQo+Pj4+IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MjQgUE0NCj4+Pj4gVG86IFRhbCBN
aXpyYWhpDQo+Pj4+IENjOiBPbGUgVHLDuGFuOw0KPj4+PiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVu
dC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsNCj4+Pj4gc3ByaW5nQGlldGYub3JnOyA2
bWFuIFdHDQo+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQNCj4+Pj4g
ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVhZGVyDQo+Pj4+DQo+Pj4+DQo+Pj4+
PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDE6MTkgUE0sIFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxs
LmNvbT4gd3JvdGU6DQo+Pj4+Pg0KPj4+Pj4gSGkgU3RlZmFubywNCj4+Pj4+DQo+Pj4+PiBUaGFu
a3MgYWdhaW4gZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuDQo+Pj4+Pg0KPj4+Pj4+IDIuIHRoZSBT
UkggaXMgb3JpZ2luYXRlZCBieSB0aGUgaW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+
Pj4+Pj4gVGhpcyBpcyBkb25lIGJ5IGVuY2Fwc3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0
ZXINCj4+Pj4+PiAoYWRkaXRpb25hbCkgaXB2NiBoZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILiBU
aGlzIGlzIEwzDQo+Pj4+Pj4gZW5jYXBzdWxhdGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52
b2x2ZWQuIFdoZW4gdGhlICBwYWNrZXQNCj4+Pj4+PiBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUg
b3V0ZXIgZW5jYXBzdWxhdGlvbiAgKGluY2x1ZGluZyB0aGUgU1JIKQ0KPj4+Pj4+IGlzIHJlbW92
ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVzICBpdHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFw
cGVuZWQuDQo+Pj4+Pg0KPj4+Pj4gU28gVlhMQU4gaXMgb2ZmIHRoZSB0YWJsZT8NCj4+Pj4NCj4+
Pj4NCj4+Pj4gaXTigJlzIGFsbCBhYm91dCBJUCwgbm90IGxheWVyLTIuDQo+Pj4+DQo+Pj4+IHMu
DQo+Pj4+DQo+Pj4+DQo+Pj4+PiBJdCB3b3VsZCBiZSB3b3J0aHdoaWxlIHRvIGNsYXJpZnkgdGhp
cyBpbiB0aGUgZHJhZnQuIElmIHlvdSBoYXZlIGENCj4+Pj4+IHNwZWNpZmljDQo+Pj4+IGVuY2Fw
c3VsYXRpb24gaW4gbWluZCwgaXQgd291bGQgYmUgZ3JlYXQgaWYgdGhlIGRyYWZ0IHdvdWxkIHNw
ZWNpZnkgaXQuDQo+Pj4+Pg0KPj4+Pj4gVGhhbmtzLA0KPj4+Pj4gVGFsLg0KPj4+Pj4NCj4+Pj4+
DQo+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+PiBGcm9tOiBTdGVmYW5v
IFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbV0NCj4+Pj4+PiBT
ZW50OiBNb25kYXksIE1heSAxNiwgMjAxNiAyOjEzIFBNDQo+Pj4+Pj4gVG86IFRhbCBNaXpyYWhp
DQo+Pj4+Pj4gQ2M6IE9sZSBUcsO4YW47DQo+Pj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+Pj4+Pj4gc3ByaW5nQGlldGYub3JnOyA2
bWFuIFdHDQo+Pj4+Pj4gU3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+
Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+Pj4+DQo+Pj4+
Pj4gSGksDQo+Pj4+Pj4NCj4+Pj4+PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDExOjA0IEFNLCBUYWwg
TWl6cmFoaSA8dGFsbWlAbWFydmVsbC5jb20+DQo+d3JvdGU6DQo+Pj4+Pj4+DQo+Pj4+Pj4+IEhp
IFN0ZWZhbm8sDQo+Pj4+Pj4+DQo+Pj4+Pj4+IFRoYW5rcyBmb3IgdGhlIHJlc3BvbnNlcy4NCj4+
Pj4+Pj4NCj4+Pj4+Pj4+IGV4YWN0bHkuDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gTW9yZW92ZXIsIGRy
YWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4+Pj4+IGVu
Y2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS4NCj4+
Pj4+Pj4+DQo+Pj4+Pj4+PiBzLg0KPj4+Pj4+Pg0KPj4+Pj4+PiBUd28gcXVlc3Rpb25zOg0KPj4+
Pj4+PiAxLiBXaGF0IGlmIHRoZSBlbmNhcHN1bGF0aW9uIGlzIFZYTEFOPyBMNCB3b3VsZCBzdGls
bCBiZSBpbnZvbHZlZCwNCj5yaWdodD8NCj4+Pj4+Pg0KPj4+Pj4+DQo+Pj4+Pj4gU2VlIGJlbG93
Lg0KPj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+Pj4gMi4gV2hlbiB5b3Ugc2F5ICdhc3N1bWVzIGVuY2Fw
c3VsYXRpb24nLCBkb2VzIGl0IG1lYW4gdGhhdCBhIGhvc3QNCj4+Pj4+Pj4gY2Fubm90DQo+Pj4+
Pj4gc2VuZCBhbiBJUHY2IHBhY2tldCB3aXRoIGFuIFNSSD8gVGhlIGN1cnJlbnQgZHJhZnQgc2F5
czoNCj4+Pj4+Pj4NCj4+Pj4+Pj4gQSBTb3VyY2UgU1IgTm9kZSBjYW4gYmUgYW55IG5vZGUgb3Jp
Z2luYXRpbmcgYW4gSVB2NiBwYWNrZXQgd2l0aA0KPj4+Pj4+PiBpdHMNCj4+Pj4+Pj4gSVB2NiBh
bmQgU2VnbWVudCBSb3V0aW5nIEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0aGVyOg0KPj4+Pj4+
Pg0KPj4+Pj4+PiAgICBBIGhvc3Qgb3JpZ2luYXRpbmcgYW4gSVB2NiBwYWNrZXQuDQo+Pj4+Pj4+
DQo+Pj4+Pj4+ICAgIEFuIFNSIGRvbWFpbiBpbmdyZXNzIHJvdXRlciBlbmNhcHN1bGF0aW5nIGEg
cmVjZWl2ZWQgSVB2NiBwYWNrZXQNCj4+Pj4+Pj4gICAgaW50byBhbiBvdXRlciBJUHY2IGhlYWRl
ciBmb2xsb3dlZCBieSBhbiBTUkguDQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+
IFdpbGwgYXBwcmVjaWF0ZSBpZiB5b3UgY2FuIGNsYXJpZnkgdGhhdC4NCj4+Pj4+Pg0KPj4+Pj4+
DQo+Pj4+Pj4gb2ssIHR3byBjYXNlczoNCj4+Pj4+Pg0KPj4+Pj4+IDEuIHRoZSBTUkggaXMgaW5z
ZXJ0ZWQgYXQgdGhlIHNvdXJjZS4NCj4+Pj4+PiB0aGUgc291cmNlIG9yaWdpbmF0ZXMgdGhlIHBh
Y2tldCwgdGhlIGlwdjYgaGVhZGVyIGFuZCAgdGhlIFNSSC4NCj4+Pj4+PiBUaGUgc291cmNlIGNv
bXB1dGVzIEw0IGNoZWNrc3VtIHRha2luZyBpbnRvICBhY2NvdW50IHRoZSB3aG9sZQ0KPklQdjYr
U1JILg0KPj4+Pj4+IEhlcmUsIHRoZXJlc+KAmSBub3RoaW5nIG5ldyAgY29tcGFyZWQgdG8gcmZj
MjQ2MC4NCj4+Pj4+Pg0KPj4+Pj4+IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBieSB0aGUgaW5n
cmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+Pj4+Pj4gVGhpcyBpcyBkb25lIGJ5IGVuY2Fw
c3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0ZXINCj4+Pj4+PiAoYWRkaXRpb25hbCkgaXB2
NiBoZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILiBUaGlzIGlzIEwzDQo+Pj4+Pj4gZW5jYXBzdWxh
dGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlICBwYWNrZXQNCj4+
Pj4+PiBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbiAgKGluY2x1
ZGluZyB0aGUgU1JIKQ0KPj4+Pj4+IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVz
ICBpdHMgam91cm5leSBsaWtlIG5vdGhpbmcgaGFwcGVuZWQuDQo+Pj4+Pj4NCj4+Pj4+PiBzLg0K
Pj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gVGhhbmtzLA0KPj4+Pj4+PiBUYWwuDQo+
Pj4+Pj4+DQo+Pj4+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+Pj4+Pj4gRnJv
bTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJldmlkaUBjaXNjby5jb21d
DQo+Pj4+Pj4+PiBTZW50OiBNb25kYXksIE1heSAxNiwgMjAxNiAxMTo1OSBBTQ0KPj4+Pj4+Pj4g
VG86IE9sZSBUcsO4YW47IFRhbCBNaXpyYWhpDQo+Pj4+Pj4+PiBDYzogZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+Pj4+Pj4+PiBzcHJpbmdA
aWV0Zi5vcmc7IDZtYW4gV0cNCj4+Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVj
a3N1bSBhbmQNCj4+Pj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRl
cg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gT24gTWF5IDE1LCAyMDE2LCBhdCA4OjA2
IFBNLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IFRh
bCwNCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBbQXBvbG9naWVzIGlmIHRoaXMgaXNzdWUgaGFzIGJl
ZW4gZGlzY3Vzc2VkIGJlZm9yZS5dDQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IEFjY29yZGluZyB0
byBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciwgYW4g4oCYU1INCj4+Pj4+
Pj4+Pj4gU2VnbWVudA0KPj4+Pj4+Pj4gRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVzIHRoZSBEZXN0
aW5hdGlvbiBJUCBhZGRyZXNzLg0KPj4+Pj4+Pj4+PiBUaGVyZWZvcmUsIGl0IG11c3QgYWxzbyB1
cGRhdGUgdGhlIExheWVyIDQgQ2hlY2tzdW0sIHJpZ2h0Pw0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+
PiBJIHdvbmRlciBpZiB0aGVyZSBpcyBhbiB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0aGUg
U1JILg0KPj4+Pj4+Pj4+PiBPdGhlcndpc2UsIHRoZQ0KPj4+Pj4+Pj4gTDQgQ2hlY2tzdW0gbWF5
IGJlIGxvY2F0ZWQgaW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlvbi4NCj4+Pj4+Pj4+Pj4gU3BlYWtp
bmcgZnJvbSBhIGNoaXAgdmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2Js
ZW0uDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBGcm9tIFJGQzI0NjAsIFJIMDoNCj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gICBvICBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFpbnMgYSBS
b3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9uDQo+Pj4+Pj4+Pj4gICAgICBBZGRyZXNzIHVz
ZWQgaW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhhdCBvZiB0aGUgZmluYWwNCj4+Pj4+Pj4+PiAg
ICAgIGRlc3RpbmF0aW9uLiAgQXQgdGhlIG9yaWdpbmF0aW5nIG5vZGUsIHRoYXQgYWRkcmVzcyB3
aWxsIGJlIGluDQo+Pj4+Pj4+Pj4gICAgICB0aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5n
IGhlYWRlcjsgYXQgdGhlIHJlY2lwaWVudChzKSwNCj4+Pj4+Pj4+PiAgICAgIHRoYXQgYWRkcmVz
cyB3aWxsIGJlIGluIHRoZSBEZXN0aW5hdGlvbiBBZGRyZXNzIGZpZWxkIG9mIHRoZQ0KPj4+Pj4+
Pj4+ICAgICAgSVB2NiBoZWFkZXIuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBJIHdvdWxkIGV4cGVj
dCBTUiB3b3VsZCB3b3JrIHRoZSBzYW1lLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBl
eGFjdGx5Lg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2Vn
bWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVzDQo+Pj4+Pj4+PiBlbmNhcHN1bGF0aW9uIHNvIGNs
ZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4g
cy4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gQ2hlZXJzLA0KPj4+
Pj4+Pj4+IE9sZQ0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pg0KPj4+DQo+Pj4gLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4+PiBJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5nIGxpc3QNCj4+PiBpcHY2QGll
dGYub3JnDQo+Pj4gQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vaXB2Ng0KPj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCg==


From nobody Tue May 17 02:40:08 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 EC84612B061; Tue, 17 May 2016 02:39:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 anXzER3dSNKP; Tue, 17 May 2016 02:39:50 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 E571212B030; Tue, 17 May 2016 02:39:49 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id f66so12629573vkh.2; Tue, 17 May 2016 02:39:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Cg65WDz/u0M2yJZRe8MrG3Pcp1ONgS+axoc5dwXFXis=; b=p0/T+gV8Z0hE7rwTmvDD94s9V5jpEmk+HEPmcq3Tf3kmigEmUGicj0u6miw9+sxu3A cvaEJwGz5RMTw+zVxZH7LsQTgJa2tji4WbaxxL0sAvfsgYBijsv/sB0ack8xQDa1T5Y5 LnncGBg2Ir2t5U56gaAlXTPOOeV+zReHtOPC6EYcgnxlp+7D+cLo45xMau1h/UjDSrby bfQk0Df4/I964nwxEZC/YTLnbTdLFCjrxB7bvPbJ4ROfrtMv4njjBlaOMiEf48zxFnDP ZIQo2oWh5yG0cQFSpiuQwXoSO9RNwzicpFTFfTDG55ICEpe7KJHbT6D6b88Cv4ZMkOvK JoCQ==
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:date :message-id:subject:from:to:cc; bh=Cg65WDz/u0M2yJZRe8MrG3Pcp1ONgS+axoc5dwXFXis=; b=Q8IKuijRUTg1e0wWeC9D6J6I1L3d5zqpTB4sUvbbHmwLQx0kD0fY8mtyj7sKv7qWyQ vi9OufAVwhhHX3fpNAiDS7xurn6cuOBKutA1/6S70r9gR2l62JZPcAswdIAoToWkUY/4 7tmWpJ11VC8Yh+55n8H4pEZmFJf0omeFJ0DTfRassUQHEapM7VgEak8rO3ndnVFAZpT7 h1F9MwdETyxkPHGLZTZFQ96MDwQjJgRjzrH82zZ24i6TsgvvOBB/PABROAE6dmAb2E7b nc6CHT60NUGNEIVvrxCkUQlwLBsrm5UFky7mHJZ+FcgnzO6cpkno+uYeuG+XkcD6Dx2t Hrlw==
X-Gm-Message-State: AOPr4FXoH3SNQDGq0LABTw3podughYiJoiPltfoWng/QI0LfB+f+16ButmDRTYd9xRBcnlxCodKcELRC1paJCA==
MIME-Version: 1.0
X-Received: by 10.159.37.100 with SMTP id 91mr98594uaz.67.1463477988977; Tue, 17 May 2016 02:39:48 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Tue, 17 May 2016 02:39:48 -0700 (PDT)
Received: by 10.176.4.55 with HTTP; Tue, 17 May 2016 02:39:48 -0700 (PDT)
In-Reply-To: <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com>
Date: Tue, 17 May 2016 19:39:48 +1000
Message-ID: <CAO42Z2z5fAT+1w0i3WizcWTwTuXWOk9mxKQvMOx9dJTkh_uXag@mail.gmail.com>
Subject: RE: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
From: Mark Smith <markzzzsmith@gmail.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=94eb2c122da4ab742f05330685af
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wMFGfWK2-g832Qh4NZf45TgiObU>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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, 17 May 2016 09:39:53 -0000

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

On 17 May 2016 7:09 PM, "Tal Mizrahi" <talmi@marvell.com> wrote:
>
> Stefano,
>
> If I understand your point correctly:
> IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, since
these encapsulations do not currently allow the use of IPv6 extension
headers.
>

Do they specifically prohibit them after the outer fixed IPv6 header?

This is what I'd expect a SR+VXLAN packet to look like coming from a SR
enabled VXLAN tunnel end point.

[IPv6 HDR][SR EH][UDP][VXLAN][tunneled pkt.]

Regards,
Mark.

> I wonder if the authors of VXLAN-GPE and Geneve have considered the use
of segment routing.
>
> Thanks,
> Tal.
>
>
>
> >-----Original Message-----
> >From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >Sent: Tuesday, May 17, 2016 10:41 AM
> >To: Tom Herbert
> >Cc: Tal Mizrahi; 6man WG; spring@ietf.org;
draft-ietf-6man-segment-routing-
> >header@tools.ietf.org
> >Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
> >header
> >
> >
> >> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com> wrote:
> >>
> >> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com>
> >wrote:
> >>>> it=E2=80=99s all about IP, not layer-2.
> >>>>
> >>>> s.
> >>>
> >>> Right. However, it appears that at least in some cases a VXLAN VTEP
will
> >use SR. It certainly may be the case in SFC use cases (see Section 2.3
in draft-
> >ietf-spring-ipv6-use-cases).
> >>>
> >>
> >> draft-ietf-6man-segment-routing-header mentions that the packet is
> >> encapsulated
> >
> >
> >into an outer ipv6 header which makes it a layer-3 encap.
> >
> >
> >> , but I don't think it is explicit as to exact encapsulation format (I
> >> suppose simple ip6ip6 is implied).
> >
> >
> >see section 2.2
> >
> >
> >> But, it
> >> seems like any of several encapsulation techniques could work (VXLAN,
> >
> >
> >I have some problems to understand where to fit an extension header into
a
> >vxlan encap=E2=80=A6
> >
> >
> >> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants to
> >> do SR is already doing tunneling it seems reasonable to me to only
> >> have one layer of encapsulation. Maybe this should be clarified in the
> >> draft?
> >
> >
> >the draft is about IPv6 extension header and more precisely a new type
of the
> >routing extension header defined in rfc2460. That=E2=80=99s the context.
> >
> >
> >s.
> >
> >
> >
> >
> >>
> >> Tom
> >>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>> Sent: Monday, May 16, 2016 2:24 PM
> >>>> To: Tal Mizrahi
> >>>> Cc: Ole Tr=C3=B8an;
> >>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>> spring@ietf.org; 6man WG
> >>>> Subject: Re: [spring] L4 Checksum and
> >>>> draft-ietf-6man-segment-routing- header
> >>>>
> >>>>
> >>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com> wrote:
> >>>>>
> >>>>> Hi Stefano,
> >>>>>
> >>>>> Thanks again for the prompt response.
> >>>>>
> >>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>> This is done by encapsulating the packet into a outer
> >>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>> is removed and the packet continues  its journey like nothing
happened.
> >>>>>
> >>>>> So VXLAN is off the table?
> >>>>
> >>>>
> >>>> it=E2=80=99s all about IP, not layer-2.
> >>>>
> >>>> s.
> >>>>
> >>>>
> >>>>> It would be worthwhile to clarify this in the draft. If you have a
> >>>>> specific
> >>>> encapsulation in mind, it would be great if the draft would specify
it.
> >>>>>
> >>>>> Thanks,
> >>>>> Tal.
> >>>>>
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>> Sent: Monday, May 16, 2016 2:13 PM
> >>>>>> To: Tal Mizrahi
> >>>>>> Cc: Ole Tr=C3=B8an;
> >>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>> spring@ietf.org; 6man WG
> >>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com>
> >wrote:
> >>>>>>>
> >>>>>>> Hi Stefano,
> >>>>>>>
> >>>>>>> Thanks for the responses.
> >>>>>>>
> >>>>>>>> exactly.
> >>>>>>>>
> >>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>
> >>>>>>>> s.
> >>>>>>>
> >>>>>>> Two questions:
> >>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be involved=
,
> >right?
> >>>>>>
> >>>>>>
> >>>>>> See below.
> >>>>>>
> >>>>>>
> >>>>>>> 2. When you say 'assumes encapsulation', does it mean that a host
> >>>>>>> cannot
> >>>>>> send an IPv6 packet with an SRH? The current draft says:
> >>>>>>>
> >>>>>>> A Source SR Node can be any node originating an IPv6 packet with
> >>>>>>> its
> >>>>>>> IPv6 and Segment Routing Headers.  This include either:
> >>>>>>>
> >>>>>>>    A host originating an IPv6 packet.
> >>>>>>>
> >>>>>>>    An SR domain ingress router encapsulating a received IPv6
packet
> >>>>>>>    into an outer IPv6 header followed by an SRH.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Will appreciate if you can clarify that.
> >>>>>>
> >>>>>>
> >>>>>> ok, two cases:
> >>>>>>
> >>>>>> 1. the SRH is inserted at the source.
> >>>>>> the source originates the packet, the ipv6 header and  the SRH.
> >>>>>> The source computes L4 checksum taking into  account the whole
> >IPv6+SRH.
> >>>>>> Here, theres=E2=80=99 nothing new  compared to rfc2460.
> >>>>>>
> >>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>> This is done by encapsulating the packet into a outer
> >>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>> is removed and the packet continues  its journey like nothing
happened.
> >>>>>>
> >>>>>> s.
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Tal.
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
> >>>>>>>> To: Ole Tr=C3=B8an; Tal Mizrahi
> >>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>>> spring@ietf.org; 6man WG
> >>>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
> >>>>>>>>>
> >>>>>>>>> Tal,
> >>>>>>>>>
> >>>>>>>>>> [Apologies if this issue has been discussed before.]
> >>>>>>>>>>
> >>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =E2=80=
=98SR
> >>>>>>>>>> Segment
> >>>>>>>> Endpoint Node=E2=80=99 updates the Destination IP address.
> >>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
> >>>>>>>>>>
> >>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
> >>>>>>>>>> Otherwise, the
> >>>>>>>> L4 Checksum may be located in a pretty deep location.
> >>>>>>>>>> Speaking from a chip vendor=E2=80=99s perspective this may be =
a
problem.
> >>>>>>>>>
> >>>>>>>>> From RFC2460, RH0:
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>   o  If the IPv6 packet contains a Routing header, the
Destination
> >>>>>>>>>      Address used in the pseudo-header is that of the final
> >>>>>>>>>      destination.  At the originating node, that address will
be in
> >>>>>>>>>      the last element of the Routing header; at the
recipient(s),
> >>>>>>>>>      that address will be in the Destination Address field of
the
> >>>>>>>>>      IPv6 header.
> >>>>>>>>>
> >>>>>>>>> I would expect SR would work the same.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> exactly.
> >>>>>>>>
> >>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>
> >>>>>>>> s.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Cheers,
> >>>>>>>>> Ole
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> >>> --------------------------------------------------------------------
> >>> IETF IPv6 working group mailing list
> >>> ipv6@ietf.org
> >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 17 May 2016 7:09 PM, &quot;Tal Mizrahi&quot; &lt;<a href=3D"mailto:talmi=
@marvell.com">talmi@marvell.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Stefano,<br>
&gt;<br>
&gt; If I understand your point correctly:<br>
&gt; IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, si=
nce these encapsulations do not currently allow the use of IPv6 extension h=
eaders.<br>
&gt;</p>
<p dir=3D"ltr">Do they specifically prohibit them after the outer fixed IPv=
6 header?</p>
<p dir=3D"ltr">This is what I&#39;d expect a SR+VXLAN packet to look like c=
oming from a SR enabled VXLAN tunnel end point.</p>
<p dir=3D"ltr">[IPv6 HDR][SR EH][UDP][VXLAN][tunneled pkt.]<br></p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; I wonder if the authors of VXLAN-GPE and Geneve have co=
nsidered the use of segment routing.<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;-----Original Message-----<br>
&gt; &gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevid=
i@cisco.com">sprevidi@cisco.com</a>]<br>
&gt; &gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt; &gt;To: Tom Herbert<br>
&gt; &gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org">sprin=
g@ietf.org</a>; draft-ietf-6man-segment-routing-<br>
&gt; &gt;<a href=3D"mailto:header@tools.ietf.org">header@tools.ietf.org</a>=
<br>
&gt; &gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-rout=
ing-<br>
&gt; &gt;header<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailt=
o:tom@herbertland.com">tom@herbertland.com</a>&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"m=
ailto:talmi@marvell.com">talmi@marvell.com</a>&gt;<br>
&gt; &gt;wrote:<br>
&gt; &gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; s.<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; Right. However, it appears that at least in some cases a =
VXLAN VTEP will<br>
&gt; &gt;use SR. It certainly may be the case in SFC use cases (see Section=
 2.3 in draft-<br>
&gt; &gt;ietf-spring-ipv6-use-cases).<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; draft-ietf-6man-segment-routing-header mentions that the pack=
et is<br>
&gt; &gt;&gt; encapsulated<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; , but I don&#39;t think it is explicit as to exact encapsulat=
ion format (I<br>
&gt; &gt;&gt; suppose simple ip6ip6 is implied).<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;see section 2.2<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; But, it<br>
&gt; &gt;&gt; seems like any of several encapsulation techniques could work=
 (VXLAN,<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;I have some problems to understand where to fit an extension heade=
r into a<br>
&gt; &gt;vxlan encap=E2=80=A6<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that=
 wants to<br>
&gt; &gt;&gt; do SR is already doing tunneling it seems reasonable to me to=
 only<br>
&gt; &gt;&gt; have one layer of encapsulation. Maybe this should be clarifi=
ed in the<br>
&gt; &gt;&gt; draft?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;the draft is about IPv6 extension header and more precisely a new =
type of the<br>
&gt; &gt;routing extension header defined in rfc2460. That=E2=80=99s the co=
ntext.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;s.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Tom<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"m=
ailto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt; &gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt; &gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt; &gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-hea=
der@tools.ietf.org">draft-ietf-6man-segment-routing-header@tools.ietf.org</=
a>;<br>
&gt; &gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">spring@ietf.org</a=
>; 6man WG<br>
&gt; &gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt; &gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a h=
ref=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node =
of the SR domain.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into=
 a outer<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. =
This is L3<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved.=
 When the=C2=A0 packet<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its=
 journey like nothing happened.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; s.<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the dra=
ft. If you have a<br>
&gt; &gt;&gt;&gt;&gt;&gt; specific<br>
&gt; &gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft=
 would specify it.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a h=
ref=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rou=
ting-header@tools.ietf.org">draft-ietf-6man-segment-routing-header@tools.ie=
tf.org</a>;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">spring@iet=
f.org</a>; 6man WG<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt=
;<a href=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt;<br>
&gt; &gt;wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rou=
ting-header assumes<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4=
 would still be involved,<br>
&gt; &gt;right?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say &#39;assumes encapsulatio=
n&#39;, does it mean that a host<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; cannot<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current =
draft says:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originat=
ing an IPv6 packet with<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.=C2=A0 T=
his include either:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A host originating an IPv6 p=
acket.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 An SR domain ingress router =
encapsulating a received IPv6 packet<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 into an outer IPv6 header fo=
llowed by an SRH.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<=
br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 he=
ader and=C2=A0 the SRH.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into=
=C2=A0 account the whole<br>
&gt; &gt;IPv6+SRH.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; Here, theres=E2=80=99 nothing new=C2=A0 compa=
red to rfc2460.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node =
of the SR domain.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into=
 a outer<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. =
This is L3<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved.=
 When the=C2=A0 packet<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its=
 journey like nothing happened.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mai=
lto:<a href=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<b=
r>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=C3=B8an; Tal Mizrahi<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man=
-segment-routing-header@tools.ietf.org">draft-ietf-6man-segment-routing-hea=
der@tools.ietf.org</a>;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">sp=
ring@ietf.org</a>; 6man WG<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and=
<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- head=
er<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a h=
ref=3D"mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has =
been discussed before.]<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-=
segment-routing-header, an =E2=80=98SR<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node=E2=80=99 updates the De=
stination IP address.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also updat=
e the Layer 4 Checksum, right?<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper=
 bound on the size of the SRH.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a prett=
y deep location.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor=
=E2=80=99s perspective this may be a problem.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0o=C2=A0 If the IPv6 p=
acket contains a Routing header, the Destination<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Address used =
in the pseudo-header is that of the final<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 destination.=
=C2=A0 At the originating node, that address will be in<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 the last elem=
ent of the Routing header; at the recipient(s),<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 that address =
will be in the Destination Address field of the<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 IPv6 header.<=
br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the =
same.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rou=
ting-header assumes<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; ---------------------------------------------------------=
-----------<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">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; &gt;&gt;&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>

--94eb2c122da4ab742f05330685af--


From nobody Tue May 17 04:23:17 2016
Return-Path: <alexandre.petrescu@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 4AE0912D806 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 9i57M-cgufr9 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:23:14 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 355FA12D804 for <ipv6@ietf.org>; Tue, 17 May 2016 04:23:12 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4HBNB7U006401 for <ipv6@ietf.org>; Tue, 17 May 2016 13:23:11 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 21778203178 for <ipv6@ietf.org>; Tue, 17 May 2016 13:23:11 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 12C912030BC for <ipv6@ietf.org>; Tue, 17 May 2016 13:23:11 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4HBNArJ008792 for <ipv6@ietf.org>; Tue, 17 May 2016 13:23:10 +0200
Subject: Re: L4 Checksum and draft-ietf-6man-segment-routing-header
To: ipv6@ietf.org
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2f6e0e6e-0e5e-0b3b-10ce-09768e8b3791@gmail.com>
Date: Tue, 17 May 2016 13:23:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5caxTaBcuFsMj1r4rvApWpa8y2A>
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, 17 May 2016 11:23:16 -0000

Le 15/05/2016 à 12:04, Tal Mizrahi a écrit :
> Hi,
>
>
>
> [Apologies if this issue has been discussed before.]
>
>
>
> According to draft-ietf-6man-segment-routing-header, an ‘SR Segment
> Endpoint Node’ updates the Destination IP address.
>
>
> Therefore, it must also update the Layer 4 Checksum, right?

I guess yes.  I guess the draft assumes that only the end nodes create
and verify the checksum value.

(whether that is done correctly it is another matter;
draft-ietf-6man-segment-routing-header-01 tells that there are two
different ways of inserting an SRH: by the end nodes _or_ by
intermediary nodes; if it is done by the intermediary nodes there is a
need to make sure that overall the SRH concept makes sense).

> I wonder if there is an upper bound on the size of the SRH.

I think that size can be deduced from the length of the Hdr Ext Len
field of draft-ietf-6man-segment-routing-header-01: 8 bits would mean
the max size is 256 bytes (plus 1 by its definition).

One may wonder though whether there can be multiple SRHs in a packet?

> Otherwise, the L4 Checksum may be located in a pretty deep location.
>
> Speaking from a chip vendor’s perspective this may be a problem.

I think that is understandable.

Alex

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


From nobody Tue May 17 04:26:19 2016
Return-Path: <alexandre.petrescu@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 135F812D809 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 PrFMoSM2aS9q for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:26:17 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F10312D7EB for <ipv6@ietf.org>; Tue, 17 May 2016 04:26:16 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4HBQFjK010099 for <ipv6@ietf.org>; Tue, 17 May 2016 13:26:15 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4436B2030EF for <ipv6@ietf.org>; Tue, 17 May 2016 13:26:15 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3AE582030BC for <ipv6@ietf.org>; Tue, 17 May 2016 13:26:15 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4HBQEZw010596 for <ipv6@ietf.org>; Tue, 17 May 2016 13:26:15 +0200
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
To: ipv6@ietf.org
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <6ed6834bb1e343b287f0cc32428417ff@IL-EXCH02.marvell.com> <B91DAD4F-6EC0-4F3D-A696-35B698B81D46@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2ff20b81-4ff8-a51c-096d-587e99e4055c@gmail.com>
Date: Tue, 17 May 2016 13:26:14 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <B91DAD4F-6EC0-4F3D-A696-35B698B81D46@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/v19o4FMO7ccNy9vT91WFnr3jo6o>
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, 17 May 2016 11:26:19 -0000

Le 16/05/2016 Ã  11:00, Stefano Previdi (sprevidi) a Ã©crit :
>
>> On May 16, 2016, at 8:21 AM, Tal Mizrahi <talmi@marvell.com>
>> wrote:
>>
>> Hi Ole,
>>
>> Thanks for the prompt response.
>>
>> It would be helpful if the authors added a comment about the L4
>> Checksum to the current draft, even though this functionality was
>> defined in RFC 2460.
>
>
> please read carefully draft-ietf-6man-segment-routing-header.
>
> The model described assumes encapsulation of the original packet into
> an outer ipv6 header followed by a SRH. When the packet leaves the SR
> tunnel there are no traces of segment routing whatsoever. L4 clearly
> does not apply here, itâ€™s basic tunneling.

Ah, for myself, I didnt know that it's basic tunnelling plus SRH - I 
thought it was just SRH.  I wonder multiple encapsulation would not 
achieve same effect as SRH?

Alex

>
> s.
>
>
>>
>> Best regards, Tal.
>>
>>> -----Original Message----- From: otroan@employees.org
>>> [mailto:otroan@employees.org] Sent: Sunday, May 15, 2016 9:07 PM
>>> To: Tal Mizrahi Cc:
>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
>>> spring@ietf.org; 6man WG Subject: Re: [spring] L4 Checksum and
>>> draft-ietf-6man-segment-routing- header
>>>
>>> Tal,
>>>
>>>> [Apologies if this issue has been discussed before.]
>>>>
>>>> According to draft-ietf-6man-segment-routing-header, an â€˜SR
>>>> Segment
>>> Endpoint Nodeâ€™ updates the Destination IP address.
>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>
>>>> I wonder if there is an upper bound on the size of the SRH.
>>>> Otherwise, the L4
>>> Checksum may be located in a pretty deep location.
>>>> Speaking from a chip vendorâ€™s perspective this may be a
>>>> problem.
>>>
>>> From RFC2460, RH0:
>>>
>>>
>>> o  If the IPv6 packet contains a Routing header, the Destination
>>> Address used in the pseudo-header is that of the final
>>> destination.  At the originating node, that address will be in
>>> the last element of the Routing header; at the recipient(s), that
>>> address will be in the Destination Address field of the IPv6
>>> header.
>>>
>>> I would expect SR would work the same.
>>>
>>> Cheers, Ole
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Tue May 17 04:33:25 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 C69A112D829 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 V0nN4qf_iBfX for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:33:21 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 C32D912D824 for <ipv6@ietf.org>; Tue, 17 May 2016 04:33:21 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id x189so12027785ywe.3 for <ipv6@ietf.org>; Tue, 17 May 2016 04:33:21 -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=SNOEGmDabl1V+D+zwHGBynpZZZtapL2NhvnQHXjShww=; b=E+C9aKYJSIz8/7CvcSdWNTNk3UxxGuUU8/sDeOMbfJVy+XhNDUkwWHq1Eh+QFAG/z6 fB9aAhR10NvGFIOIt0HvNmQ8lyfKiSKiht+4C8ESJJk110xI8DM1wcIiMmcEeSGMZELK H0FOQjmfEIQLhTcRuJ9NBHZKr5zTiLnWvGo1jZFGUlTFl+M3/x+DB8O5fjqrUsOSi1Pn rgpykLDcqROeWZiAu3vvDlc10eqWriDtaGFjISjDiAv7SZY3uykQbmBWNMWt89cNUTSH HxzaIR6fjroGgWqSV0CKH3f8rfI/Y7rSSOyQPzxL23O4q4RG6jClQBzcxW2elwXF9VJt GHuQ==
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=SNOEGmDabl1V+D+zwHGBynpZZZtapL2NhvnQHXjShww=; b=kCGavZrE8NLGJJ4XoWqaY39Bfry7veRBItepIUrtP/byarR2m7n/sKGRBx+PZWL44Z I9+FUFHnUTZOn5Ih63rO+5DSkNFhbR9UdOLdSGF0y5GufVNaaOZ8Cx1alcvmA2jPTMxv mx/eNPPDwffLy+/qBdv8ICgAfSOn0zPM7hvA6R/OD5sMT+VaMZuekUW6EylRPnkOjNVA mMbUrchl5ojXXHMn6ULhovdLcsF+a3fncObXuRtfeuG/hTQdzXT+GvItt40G6GegsujN J9YhTh+V/zZ+IrA/HvrTO0Uq+qBkA+DdYIvVl2DYcfwtofuLnD3+S53iGPGdpJivySNM Qd1w==
X-Gm-Message-State: AOPr4FWa/wbJpwYl4jNO+sSmbrC3jhZRKVK5lI7b+6TqCEdUiEZZWd391B7SeGbEc0lQXdR/gJ5M1FyqoFV3cO17
X-Received: by 10.129.108.208 with SMTP id h199mr337316ywc.229.1463484800963;  Tue, 17 May 2016 04:33:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Tue, 17 May 2016 04:33:01 -0700 (PDT)
In-Reply-To: <41533F2B-C2AC-46A9-BB67-511EFE9D3861@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <41533F2B-C2AC-46A9-BB67-511EFE9D3861@cooperw.in>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 17 May 2016 20:33:01 +0900
Message-ID: <CAKD1Yr054-AkiA6=G4hCznPxdFFeMh7TZzKFyi+HfgLKVon_Jw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary=001a114db904b2962d0533081b79
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xkSlfUG-J23ayX3mDJSZCiDZ0C0>
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: Tue, 17 May 2016 11:33:24 -0000

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

On Tue, May 17, 2016 at 2:13 AM, Alissa Cooper <alissa@cooperw.in> wrote:

> This draft forbids implementations from using existing address generation
> mechanisms using random MAC addresses,
>
> The draft does not forbid anything.
>

Ok, then let me restate the objection:

The draft strongly recommends against implementations using existing
address generation mechanisms using random MAC addresses which is a
perfectly valid way to address the privacy problem this draft is
purportedly solving, and is an approach standardized in other IETF work,
for example,
https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.1
(now in RFC editor queue).


> It has two MUST-level requirements: that mechanisms be defined, and that
> those mechanisms meet certain requirements.
>

But that makes no sense at all. It's circular reasoning: this document says
that link layers MUST define mechanisms. To do so it proceeds to update a
number of RFCs, including RFC 2464, to say that interface identifiers MUST
be generated as specified in this document... which only says that
link-layers MUST define mechanisms. So the updated text violates the very
document you're updating it to refer to.

--001a114db904b2962d0533081b79
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, May 17, 2016 at 2:13 AM, Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D=
"mailto:alissa@cooperw.in">alissa@cooperw.in</a>&gt;</span> wrote:<br><bloc=
kquote 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);paddin=
g-left:1ex"><div style=3D"word-wrap:break-word"><div><span class=3D"gmail-"=
><blockquote type=3D"cite"><div><div dir=3D"ltr"><div>This draft forbids im=
plementations from using existing address generation mechanisms using rando=
m MAC addresses,</div></div></div></blockquote></span><div>The draft does n=
ot forbid anything.</div></div></div></blockquote><div><br></div><div><div>=
Ok, then let me restate the objection:</div><div><br></div><div>The draft s=
trongly recommends against implementations using existing address generatio=
n mechanisms using random MAC addresses which is a perfectly valid way to a=
ddress the privacy problem this draft is purportedly solving, and is an app=
roach standardized in other IETF work, for example, <a href=3D"https://tool=
s.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.1">https://to=
ols.ietf.org/html/draft-ietf-dhc-anonymity-profile-08#section-2.1</a> (now =
in RFC editor queue).</div></div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-lef=
t-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div sty=
le=3D"word-wrap:break-word"><div><div>It has two MUST-level requirements: t=
hat mechanisms be defined, and that those mechanisms meet certain requireme=
nts.</div></div></div></blockquote><div><br></div><div>But that makes no se=
nse at all. It&#39;s circular reasoning: this document says that link layer=
s MUST define mechanisms. To do so it proceeds to update a number of RFCs, =
including RFC 2464, to say that interface identifiers MUST be generated as =
specified in this document... which only says that link-layers MUST define =
mechanisms. So the updated text violates the very document you&#39;re updat=
ing it to refer to.</div></div></div></div>

--001a114db904b2962d0533081b79--


From nobody Tue May 17 04:37:53 2016
Return-Path: <alexandre.petrescu@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 976D412D843 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:37:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 ZRkodSLR8FJG for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:37:47 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0DB12D84A for <ipv6@ietf.org>; Tue, 17 May 2016 04:36:48 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4HBalDN011769 for <ipv6@ietf.org>; Tue, 17 May 2016 13:36:47 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 33A66203125 for <ipv6@ietf.org>; Tue, 17 May 2016 13:36:47 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 2A10D2030D2 for <ipv6@ietf.org>; Tue, 17 May 2016 13:36:47 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4HBakc3028304 for <ipv6@ietf.org>; Tue, 17 May 2016 13:36:47 +0200
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
To: ipv6@ietf.org
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6ef47403-5d39-548f-dd80-7b8af07e2d6f@gmail.com>
Date: Tue, 17 May 2016 13:36:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0I4vc3nJBRrBAM2l9jbaHZzNS9I>
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, 17 May 2016 11:37:49 -0000

Le 16/05/2016 Ã  13:13, Stefano Previdi (sprevidi) a Ã©crit :
> Hi,
>
> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>>
>> Hi Stefano,
>>
>> Thanks for the responses.
>>
>>> exactly.
>>>
>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>> encapsulation so clearly thereâ€™s no L4 involved here.
>>>
>>> s.
>>
>> Two questions: 1. What if the encapsulation is VXLAN? L4 would
>> still be involved, right?
>
>
> See below.
>
>
>> 2. When you say 'assumes encapsulation', does it mean that a host
>> cannot send an IPv6 packet with an SRH? The current draft says:
>>
>> A Source SR Node can be any node originating an IPv6 packet with
>> its IPv6 and Segment Routing Headers.  This include either:
>>
>> A host originating an IPv6 packet.
>>
>> An SR domain ingress router encapsulating a received IPv6 packet
>> into an outer IPv6 header followed by an SRH.
>>
>>
>>
>> Will appreciate if you can clarify that.
>
>
> ok, two cases:
>
> 1. the SRH is inserted at the source. the source originates the
> packet, the ipv6 header and the SRH. The source computes L4 checksum
> taking into account the whole IPv6+SRH. Here, theresâ€™ nothing new
> compared to rfc2460.

Well I think we should say _which_ L4.

Some L4 protocols like UDP will consider the 'pseudo-header' as defined
by RFC2460, and use only the final destination address of the RH (not
the entire RH).

Other L4 protocols like AH will cover only Routing Header Type 0 (which
obviously is not the case with SRH which may have another type).

> 2. the SRH is originated by the ingress node of the SR domain. This
> is done by encapsulating the packet into a outer (additional) ipv6
> header followed by an SRH. This is L3 encapsulation and no L4
> checksum is involved.

Yes, unless there is some security relationship between the end node and
the ingress node of the SR domain.  If yes, then we need ESP and AH, and
these do need cheksum, or integrity, calculation - at L4.

> When the packet leaves the SR tunnel the outer encapsulation
> (including the SRH) is removed and the packet continues its journey
> like nothing happened.

REad.

Alex


>
> s.
>
>
>>
>> Thanks, Tal.
>>
>>> -----Original Message----- From: Stefano Previdi (sprevidi)
>>> [mailto:sprevidi@cisco.com] Sent: Monday, May 16, 2016 11:59 AM
>>> To: Ole TrÃ¸an; Tal Mizrahi Cc:
>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
>>> spring@ietf.org; 6man WG Subject: Re: [spring] L4 Checksum and
>>> draft-ietf-6man-segment-routing- header
>>>
>>>
>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
>>>>
>>>> Tal,
>>>>
>>>>> [Apologies if this issue has been discussed before.]
>>>>>
>>>>> According to draft-ietf-6man-segment-routing-header, an â€˜SR
>>>>> Segment
>>> Endpoint Nodeâ€™ updates the Destination IP address.
>>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>>
>>>>> I wonder if there is an upper bound on the size of the SRH.
>>>>> Otherwise, the
>>> L4 Checksum may be located in a pretty deep location.
>>>>> Speaking from a chip vendorâ€™s perspective this may be a
>>>>> problem.
>>>>
>>>> From RFC2460, RH0:
>>>>
>>>>
>>>> o  If the IPv6 packet contains a Routing header, the
>>>> Destination Address used in the pseudo-header is that of the
>>>> final destination.  At the originating node, that address will
>>>> be in the last element of the Routing header; at the
>>>> recipient(s), that address will be in the Destination Address
>>>> field of the IPv6 header.
>>>>
>>>> I would expect SR would work the same.
>>>
>>>
>>> exactly.
>>>
>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>> encapsulation so clearly thereâ€™s no L4 involved here.
>>>
>>> s.
>>>
>>>
>>>>
>>>> Cheers, Ole
>>>>
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Tue May 17 04:49:54 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 79E3812D894 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 5XI7eiEAWtBN for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:49:51 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 6ED2312D861 for <ipv6@ietf.org>; Tue, 17 May 2016 04:49:13 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id x189so12374206ywe.3 for <ipv6@ietf.org>; Tue, 17 May 2016 04:49:13 -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=zOUWm+nIwiJdSzSd6pj5HCITrgfAlQ4TEje/M5myQ2o=; b=RPLHIw5iMJTiSzDYVKockOBB7ryyPFtoDBypgJkm0LaQzVpVnl+0n2G1TQmcSebn/e YuKgC3YIBdvOdrm2gYWSkXv+JUHNJbt7lQ+xYP5BZupi+dQDRzvtwwoIFoYlsYskmp8t 7IUh4b3qT9qWV3TTFD44NwdOqgAhUWZQJJeE594kAIwsElgMquq+YJrlDZPw2TONHoau 3zHhP0lxJiOr0mUspiAJXz9kQAUsyhuRUfmrLl3BWExjffrnNFYvQqEmo2aJ1FlR6iga YOnMV1fQBplhpybEJhv1vBEgl1iFTivvSocY/5GFJv1r4+PpDIo4IZfvXODtUGGz/vCR 8jow==
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=zOUWm+nIwiJdSzSd6pj5HCITrgfAlQ4TEje/M5myQ2o=; b=N1izo6yjCqQ1qa0AMeXiw9P22hVxpF/TADFT1EVfmvP9k5cOg58bt1QM8597h2PusP N707SSLWZkc6meEb/szgLTv1QdpalioRNdecU4/txNTqvYMCwwql0uX7ZgE0oda4js/S fUAb1vBWjj4LqwnIUnbbAbR8OFHFg1O0deUUwR0Eqfy/Sm7dQ5x0/sfdVietF+UhGiIi 7xdxfFzWM8QKY4/ADAtpo81hQhkNjuuDSHT9FI2JS/MAv8ji26M5gIFa/p5GPOhmeZDy tNDzSzc8422ZxTxFIXurKnJSHtb3hc1ZEptrYPqLKQq4m1VV8ZiYLUF4SLqMMR4gX3aB welg==
X-Gm-Message-State: AOPr4FX55yDPhathknf8+Odvwl6cSB4xvYFNyf3U7a5KFuLTgAepmPZog98gAHh0fXpcNO/f+DhSz/Jr1II9+9oB
X-Received: by 10.37.79.87 with SMTP id d84mr346475ybb.49.1463485752623; Tue, 17 May 2016 04:49:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Tue, 17 May 2016 04:48:52 -0700 (PDT)
In-Reply-To: <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 17 May 2016 20:48:52 +0900
Message-ID: <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary=001a113f5cd06bdec90533085452
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/JYkAUGduLaPuIHtJfIA6sK0BwNE>
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: Tue, 17 May 2016 11:49:53 -0000

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

On Tue, May 17, 2016 at 2:29 AM, Alissa Cooper <alissa@cooperw.in> wrote:

> By contrast, here is one weakness that is pretty much mandated by this
> draft as written: because addresses have to be stable,
>
> The draft does not require addresses to be stable. It changes the
> recommendations about how to generate an address in cases where a stable
> address was desired anyway.
>

No, that's not correct. This draft makes recommendations about how to
generate an address "where implementations otherwise would have configured
a stable IPv6 IID containing a link layer address". On many link layers
(e.g., Ethernet), it is currently the case that implementations MUST
generate IIDs based on link layer addresses. Therefore, the recommendations
apply 100% of the time on those link layers. In effect, this draft is
saying that Ethernet addresses SHOULD be stable.


> I would frankly be thrilled if we could get away from stable addresses
> altogether. But I=E2=80=99m skeptical about the feasibility of achieving =
consensus
> around that at present. Defining the approach in this draft in the meanti=
me
> is certainly motivated by consideration for privacy improvement for me,
> even if that improvement is incremental.
>

A much greater improvement in terms of privacy, and a much easier one in
terms of sheer number of RFCs that need to be updated, would derive from
forbidding or recommending against embedding *stable* link layer addresses
in IIDs.

--001a113f5cd06bdec90533085452
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, May 17, 2016 at 2:29 AM, Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D=
"mailto:alissa@cooperw.in" target=3D"_blank">alissa@cooperw.in</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-w=
ord"><div><span class=3D""><blockquote type=3D"cite"><div><div dir=3D"ltr">=
<div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>By contrast, her=
e is one weakness that is pretty much mandated by this draft as written: be=
cause addresses have to be stable,</div></div></div></div></div></blockquot=
e></span><div>The draft does not require addresses to be stable. It changes=
 the recommendations about how to generate an address in cases where a stab=
le address was desired anyway.</div></div></div></blockquote><div><br></div=
><div>No, that&#39;s not correct. This draft makes recommendations about ho=
w to generate an address &quot;where implementations otherwise would have c=
onfigured a stable IPv6 IID containing a link layer address&quot;. On many =
link layers (e.g., Ethernet), it is currently the case that implementations=
 MUST generate IIDs based on link layer addresses. Therefore, the recommend=
ations apply 100% of the time on those link layers. In effect, this draft i=
s saying that Ethernet addresses SHOULD be stable.<br></div><div>=C2=A0<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><d=
iv><span class=3D""><div>I would frankly be thrilled if we could get away f=
rom stable addresses altogether. But I=E2=80=99m skeptical about the feasib=
ility of achieving consensus around that at present. Defining the approach =
in this draft in the meantime is certainly motivated by consideration for p=
rivacy improvement for me, even if that improvement is incremental.</div></=
span></div></div></blockquote><div>=C2=A0</div><div>A much greater improvem=
ent in terms of privacy, and a much easier one in terms of sheer number of =
RFCs that need to be updated, would derive from forbidding or recommending =
against embedding *stable* link layer addresses in IIDs.</div></div></div><=
/div>

--001a113f5cd06bdec90533085452--


From nobody Tue May 17 04:50:09 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 5703D12D86E for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 c1y6AU4zn28J for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 04:50:06 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::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 73F4B12D855 for <ipv6@ietf.org>; Tue, 17 May 2016 04:49:39 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id c189so16136071vkb.1 for <ipv6@ietf.org>; Tue, 17 May 2016 04:49:39 -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=wIRbltRXyK1cdCHwCAVY3weeEfEI8WFAFeutODcLHRI=; b=iNm8Js0grHcE3PGd/QzcuCZHPTDLbKULDMC1JG4+m/6RRTKuJQlIj0uavBA2R+kpEI k0TGcF4qVXQLLwivtMW5xGoeF0Q0H+nRWFrjDrQloJ80ZcbJXpzjuEwnKBjC0tN6RJM2 jnBRLBwmJFPk4XPyy9X7pkEGtOORFVLorVVBXSmSUNFlNLHYZk0ImPbMIB9p+9F9To1Q 5dSmwablnT8WLRTC6lanjxuQcnxcXbUWHcYLb8lBL3oOOvL+JFzF88ZEf+9003Mq3s6g zoDPbbljpBpatHI1K2fSiHGkyectz9Yp+DLz16/lsHr/BQzDTM7DxY/VMumUJZhQRa+d CsXg==
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=wIRbltRXyK1cdCHwCAVY3weeEfEI8WFAFeutODcLHRI=; b=e2CmpIxxBaB3VzzSW+E29nGQfw2v7M20fOKOBBpkjhwYUMYD9Nllbd3DUqD0N1P7Nu SFfcvzlI0If33M2DlCHewTcNbhGE7MdFNhvYUWHthj6QheWPyU553OcGtXSZ5zqqa1bE nBdgysPRmLDCPubCo9lVGwkfPn0Veds6ksZK9CSiURSJEZc5EK+xEiNsqnFd7vHvrloo Rdb4akSXwPa8IMOCAZ3uEkfG21bFVyMIkEtJotHj5F9yvqK7NmGvuKueV6DDgPEqRa9i fYyOflOFDlOamVwYU8waRiyQ6R7HhC+A/JKwSrOhnvWce9A5UnEaCD9EVaqAykZCTa43 8s0w==
X-Gm-Message-State: AOPr4FWNYY5DZVzvE4FNrsud/4+cc7E2qDO2YvvtiYjsOy6lqQ6w+PrsyU+nZUFVbJezS6PF+6Y3Yf3oMapHvg==
X-Received: by 10.31.217.7 with SMTP id q7mr377859vkg.134.1463485778553; Tue, 17 May 2016 04:49:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.4.55 with HTTP; Tue, 17 May 2016 04:49:09 -0700 (PDT)
In-Reply-To: <2f6e0e6e-0e5e-0b3b-10ce-09768e8b3791@gmail.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <2f6e0e6e-0e5e-0b3b-10ce-09768e8b3791@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 17 May 2016 21:49:09 +1000
Message-ID: <CAO42Z2y3To1R+fYKv6uwbEFh26A5cgpihTbBAFFuDNmYKHTnNA@mail.gmail.com>
Subject: Re: L4 Checksum and draft-ietf-6man-segment-routing-header
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/RzDDkrgTxYjIBxrm2_ADszYXbok>
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, 17 May 2016 11:50:08 -0000

On 17 May 2016 at 21:23, Alexandre Petrescu
<alexandre.petrescu@gmail.com> wrote:
>
>
> Le 15/05/2016 =C3=A0 12:04, Tal Mizrahi a =C3=A9crit :
>>
>> Hi,
>>
>>
>>
>> [Apologies if this issue has been discussed before.]
>>
>>
>>
>> According to draft-ietf-6man-segment-routing-header, an =E2=80=98SR Segm=
ent
>> Endpoint Node=E2=80=99 updates the Destination IP address.
>>
>>
>> Therefore, it must also update the Layer 4 Checksum, right?
>
>
> I guess yes.  I guess the draft assumes that only the end nodes create
> and verify the checksum value.
>

It isn't an assumption, it is the way IPv6 works.

End-to-end checksums like the TCP or UDP ones are only calculated or
verified at the ends.

If the packet is mis-delivered to an upper layer TCP or UDP for one of
the intermediary DA hops, the packet will be thrown away because the
upper layer checksum validation should. If it was changed as the
intermediary DAs were swapped, then the packet could be considered
legitimate by intermediate TCP or UDP, and the could then payload
handed up to an application that wasn't expecting it at all.

Briefly looking at the SR draft, the SRH processing looks to be the
same or similar to the original IPv6 routing header.

https://tools.ietf.org/html/rfc2460#section-4.4




> (whether that is done correctly it is another matter;
> draft-ietf-6man-segment-routing-header-01 tells that there are two
> different ways of inserting an SRH: by the end nodes _or_ by
> intermediary nodes; if it is done by the intermediary nodes there is a
> need to make sure that overall the SRH concept makes sense).
>
>> I wonder if there is an upper bound on the size of the SRH.
>
>
> I think that size can be deduced from the length of the Hdr Ext Len
> field of draft-ietf-6man-segment-routing-header-01: 8 bits would mean
> the max size is 256 bytes (plus 1 by its definition).
>
> One may wonder though whether there can be multiple SRHs in a packet?
>
>> Otherwise, the L4 Checksum may be located in a pretty deep location.
>>
>> Speaking from a chip vendor=E2=80=99s perspective this may be a problem.
>

Which is why EHs are not intended to be examined or processed by
intermediate nodes, with exception to one of them, and that one is
always the first EH if present. Required processing of that is being
loosened a bit in:


IPv6 Hop-by-Hop Options Extension Header
https://tools.ietf.org/html/draft-ietf-6man-hbh-header-handling-03


Regards,
Mark.


>
> I think that is understandable.
>
> Alex
>
>>
>>
>>
>> Thanks,
>>
>> Tal Mizrahi.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --------------------------------------------------------------------
>>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue May 17 08:32:16 2016
Return-Path: <joelja@bogus.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 3561712D90E for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 08:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 26zTp5g5tcjQ for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 08:32:13 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 10FFD12B04E for <ipv6@ietf.org>; Tue, 17 May 2016 08:32:13 -0700 (PDT)
Received: from mb-2.local ([IPv6:2601:647:4204:51:591a:551d:2ead:2204]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4HFW79n055952 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 17 May 2016 15:32:07 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2601:647:4204:51:591a:551d:2ead:2204] claimed to be mb-2.local
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com>
Date: Tue, 17 May 2016 08:32:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PhnniIvoUNcpSU18Fu5F0MEDBAK27nsdW"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qzs7s8_4t1_VI28t5TzICWQ-KQ4>
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: Tue, 17 May 2016 15:32:14 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PhnniIvoUNcpSU18Fu5F0MEDBAK27nsdW
Content-Type: multipart/mixed; boundary="7Qjj81aPMrlwaJoWmN1vguNURnouJniBq"
From: joel jaeggli <joelja@bogus.com>
To: Lorenzo Colitti <lorenzo@google.com>, Alissa Cooper <alissa@cooperw.in>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Message-ID: <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com>
 <89CA2C18-AE61-4D40-8997-221201835944@gmail.com>
 <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com>
 <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
 <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com>
 <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com>
 <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com>
 <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
 <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
 <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com>
In-Reply-To: <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com>

--7Qjj81aPMrlwaJoWmN1vguNURnouJniBq
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/17/16 4:48 AM, Lorenzo Colitti wrote:
> On Tue, May 17, 2016 at 2:29 AM, Alissa Cooper <alissa@cooperw.in
> <mailto:alissa@cooperw.in>> wrote:
> =20
>=20
>     I would frankly be thrilled if we could get away from stable
>     addresses altogether. But I=92m skeptical about the feasibility of
>     achieving consensus around that at present. Defining the approach i=
n
>     this draft in the meantime is certainly motivated by consideration
>     for privacy improvement for me, even if that improvement is increme=
ntal.
>=20
> =20
> A much greater improvement in terms of privacy, and a much easier one i=
n
> terms of sheer number of RFCs that need to be updated, would derive fro=
m
> forbidding or recommending against embedding *stable* link layer
> addresses in IIDs.

which sounds fine by me.

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



--7Qjj81aPMrlwaJoWmN1vguNURnouJniBq--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlc7OXcACgkQ8AA1q7Z/VrLUVgCcDCyHNhgdxMMlnMmAQFw0GrK7
UMQAnRHp3is9+sYq2+1DrJKyfOnUsD83
=wp3+
-----END PGP SIGNATURE-----

--PhnniIvoUNcpSU18Fu5F0MEDBAK27nsdW--


From nobody Tue May 17 09:09:03 2016
Return-Path: <tom@herbertland.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 1BD0E12DA66 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 09:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 7Bl3L06bCyoy for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 09:09:00 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001: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 7F05012DA65 for <ipv6@ietf.org>; Tue, 17 May 2016 09:09:00 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id d62so29569117iof.2 for <ipv6@ietf.org>; Tue, 17 May 2016 09:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=/yTOA7cQpyNI4vByAYE+tRKpV2SY1hE5PhWWeFJaBv8=; b=oGvMvNz1N3kfwDgLjg75P9k5rBHBk7S+3cgSmPs3Umzy4sN82ZTVees4kvDJMxYZaP xgJywfQai2wI/jnifvly+CyDBi+Hd5iZzNR1hubCUhiGQijAAj5+xoEyggld7UOrPjdD sDjSOmi6rQ0p6mHJUBXqihVXy8JPfaU4iw4nyckADPApFf+ImIeJtV9E9a2Zh/vO1/cY KNtxxppka3r1EDwgwRF8euA657FA38Mb+8pYmZ4TIzS6YgUzQNF8gV9FSMnmG0RWJRkA ysq2rRrIAHEYhfvVKJ0VLF9wl8BUAT8iWwFbmTXnMWszxaCulkBQ4WrOb6MBpd2H94Ki QR0Q==
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:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=/yTOA7cQpyNI4vByAYE+tRKpV2SY1hE5PhWWeFJaBv8=; b=cXFd8lLI4f6rSZbPnPx3efrppKEt//X5P4owCJahtSQ/sWg1Oly1qX8yu9hKQg5Hxl FkxLQNke4JnoJ2waEajtMHSGHmUdKYfhTZ4Iflbo191E+FtJFkgV+wUn+/c1bMD+/VpA HRJM8ZngZgAmXHUKt7mQwBzf9svqFBdluRnGQf4apuxoD2U2/qQ10abO5CqbBXjVBYLw msW/LrQETrUBaZn+JebiYe0s5xw7K0P/GTRNcGksWYYZ+huIgvi2ryX3Tt8eft47KIPp WJ08bNah7oPtMB5k8h96gD9PM7hHnwIwsR/3BzUW7txiXoPX/ITCOOvrnAZla+Sqb6C1 p1rQ==
X-Gm-Message-State: AOPr4FVnHVARsBpMBL0qPX/HlZsejTBOZ0+n34y2kZqHM1n3II7RgPTfSgK7EMPN/jO/DtR5F7C/FgL6Ztd+Cg==
MIME-Version: 1.0
X-Received: by 10.36.33.131 with SMTP id e125mr1850001ita.37.1463501339811; Tue, 17 May 2016 09:08:59 -0700 (PDT)
Received: by 10.107.56.67 with HTTP; Tue, 17 May 2016 09:08:59 -0700 (PDT)
In-Reply-To: <CAO42Z2y3To1R+fYKv6uwbEFh26A5cgpihTbBAFFuDNmYKHTnNA@mail.gmail.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <2f6e0e6e-0e5e-0b3b-10ce-09768e8b3791@gmail.com> <CAO42Z2y3To1R+fYKv6uwbEFh26A5cgpihTbBAFFuDNmYKHTnNA@mail.gmail.com>
Date: Tue, 17 May 2016 09:08:59 -0700
Message-ID: <CALx6S35sQP8Z98ZWqfmkjchVvZMH2X4gow68LayphshQ4QUafw@mail.gmail.com>
Subject: Re: L4 Checksum and draft-ietf-6man-segment-routing-header
From: Tom Herbert <tom@herbertland.com>
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SGzM1k7kWAiqemY0Owkyuf4W6ik>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.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: Tue, 17 May 2016 16:09:02 -0000

On Tue, May 17, 2016 at 4:49 AM, Mark Smith <markzzzsmith@gmail.com> wrote:
> On 17 May 2016 at 21:23, Alexandre Petrescu
> <alexandre.petrescu@gmail.com> wrote:
>>
>>
>> Le 15/05/2016 =C3=A0 12:04, Tal Mizrahi a =C3=A9crit :
>>>
>>> Hi,
>>>
>>>
>>>
>>> [Apologies if this issue has been discussed before.]
>>>
>>>
>>>
>>> According to draft-ietf-6man-segment-routing-header, an =E2=80=98SR Seg=
ment
>>> Endpoint Node=E2=80=99 updates the Destination IP address.
>>>
>>>
>>> Therefore, it must also update the Layer 4 Checksum, right?
>>
>>
>> I guess yes.  I guess the draft assumes that only the end nodes create
>> and verify the checksum value.
>>
>
> It isn't an assumption, it is the way IPv6 works.
>
> End-to-end checksums like the TCP or UDP ones are only calculated or
> verified at the ends.
>
There are some host optimizations like checksum offload and
segmentation offload that are performed before the stack would set the
final address in the destination. If the checksum is not correct on
the wire for the addresses in the packet these optimizations can't be
used (but packets should not be dropped). In ILA we do a checksum
neutral translation that keeps the checksum correct and does not
require middelboxes to update L4 checksum fields.

Tom

> If the packet is mis-delivered to an upper layer TCP or UDP for one of
> the intermediary DA hops, the packet will be thrown away because the
> upper layer checksum validation should. If it was changed as the
> intermediary DAs were swapped, then the packet could be considered
> legitimate by intermediate TCP or UDP, and the could then payload
> handed up to an application that wasn't expecting it at all.
>
> Briefly looking at the SR draft, the SRH processing looks to be the
> same or similar to the original IPv6 routing header.
>
> https://tools.ietf.org/html/rfc2460#section-4.4
>
>
>
>
>> (whether that is done correctly it is another matter;
>> draft-ietf-6man-segment-routing-header-01 tells that there are two
>> different ways of inserting an SRH: by the end nodes _or_ by
>> intermediary nodes; if it is done by the intermediary nodes there is a
>> need to make sure that overall the SRH concept makes sense).
>>
>>> I wonder if there is an upper bound on the size of the SRH.
>>
>>
>> I think that size can be deduced from the length of the Hdr Ext Len
>> field of draft-ietf-6man-segment-routing-header-01: 8 bits would mean
>> the max size is 256 bytes (plus 1 by its definition).
>>
>> One may wonder though whether there can be multiple SRHs in a packet?
>>
>>> Otherwise, the L4 Checksum may be located in a pretty deep location.
>>>
>>> Speaking from a chip vendor=E2=80=99s perspective this may be a problem=
.
>>
>
> Which is why EHs are not intended to be examined or processed by
> intermediate nodes, with exception to one of them, and that one is
> always the first EH if present. Required processing of that is being
> loosened a bit in:
>
>
> IPv6 Hop-by-Hop Options Extension Header
> https://tools.ietf.org/html/draft-ietf-6man-hbh-header-handling-03
>
>
> Regards,
> Mark.
>
>
>>
>> I think that is understandable.
>>
>> Alex
>>
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Tal Mizrahi.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue May 17 15:23: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 DE8C212DAB2 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 15:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 LiegVvkuA6xZ for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 15:23:11 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::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 B4D6B12DAAC for <ipv6@ietf.org>; Tue, 17 May 2016 15:23:10 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id s184so38741862vkb.3 for <ipv6@ietf.org>; Tue, 17 May 2016 15:23: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:date:message-id:subject:from:to :cc; bh=rPJIKM1JDI8u9UOXBZIeqiTxLQnW4i0bgCfgpyTm/Jk=; b=nJhNZ51xTwODnMScVyljKuFYrEJNNSBMvnErKJ9Pk8j3AabWAzoQ59vJtk1E6gyP4O s+banyknIMbGg/O3sNfJFh9cGHmjXellSPcgRaQNSAIWtvLapvNbQxyyw2z+3RFvtnvI Vg1PbER9PFk1a1fQXEKvxd+bHI18EYJkFB+TePWKeDFHNJpwQak3fi0glAjsSka6ew/a 9IiCGoIEyNYsFgvx0WaqfbRIvb6cm2LxKTFqyCTVjSAM4Y7MvCW9a3v7Mge+LpYrVeCG vzf7zfxAG0TD1TKJWqGXQogTrJC5/FZ/DVhay+fUtoknlK3hqVt69Phx+5RXMZvvTD6u TEHg==
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:date :message-id:subject:from:to:cc; bh=rPJIKM1JDI8u9UOXBZIeqiTxLQnW4i0bgCfgpyTm/Jk=; b=UV8jCZc0ExTjIjDTJUmrZ3oBZIdGyPsStnZSTDRupswVofxTXfB8JurkifZup3YgnW AYiNXmNyAhgVrFyheeXt8wbZb9rCQHI4omaVvcJxxUb+H2jvL9ptVQw17Ps8ejIEEvIm aXnOmQ1PDQ3kCBKGWfuJ7p82Mxdi5Jy0HHRXx4xSHzEqMf66r2U+1rwF1+ET62BSgXP6 V+igSEGM6AS6uX4H73gArqrNyT6XfP037VtlhJ0usib/9QjHKWO0nciuh7EnI05KFQap wt01A+E0FLebgT1TxAEg0EDdNCjAbX50EJQiyFE9GADOKgSsmordXadalUaPsX78kfm5 3+SA==
X-Gm-Message-State: AOPr4FWSlmFsr6egcFCIx/D4h5GHnw9P3XTlQ7P0TEpHMsBNDhPYKVAVfncTE4RWoeIWuYDoc3Wk2x93jOe/6w==
MIME-Version: 1.0
X-Received: by 10.31.51.11 with SMTP id z11mr2018323vkz.150.1463523789769; Tue, 17 May 2016 15:23:09 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 17 May 2016 15:23:09 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 17 May 2016 15:23:09 -0700 (PDT)
In-Reply-To: <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
Date: Wed, 18 May 2016 08:23:09 +1000
Message-ID: <CAO42Z2yGEoHunw12fCKvQ=gBmE+M1MO-rSbVS94cGRTEk1zfog@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114475989c110a0533112f76
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xZDy4Iufee5Bl_MK8zMtd9VJ3ek>
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, 17 May 2016 22:23:14 -0000

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

On 14 May 2016 1:29 PM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Sat, May 14, 2016 at 12:00 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
>>
>> Because if someone is trying to correlate different types of my traffic,
>> let's say something sent over IPX and something sent over IPv6, the task
>> will be made easier if the lower 48 bits are the same in both types of
>> traffic. (Obviously, someone on-link can use ND to correlate MAC address
>> and IP address, so we're talking about someone observing off-link
packets.)
>
>
> That seems extremely unlikely to happen in practice, given that the vast
majority of hosts either don't have an IPX stack at all or have it disabled
by default, and embedding a MAC address in a protocol payload is not very
useful so people tend not to do it.
>
> By contrast, here is one weakness that is pretty much mandated by this
draft as written: because addresses have to be stable, any remote attacker
anywhere on the Internet that ever exchanges a packet with that host can
track it every time the host visits the same network, *forever*, with no
recourse. Section 3 point 1.
>

Already fixed, RFC6724:

"5. Changed the default recommendation for Source Address Selection Rule 7
to prefer temporary addresses rather than public addresses, while providing
an administrative override (in addition to the application-specific
override that was already specified). This change was made because of the
increasing importance of privacy considerations, as well as the fact that
widely deployed implementations have preferred temporary addresses for many
years without major application issues."

Most hosts that will use these addresses as source addresses for their
packets are unlikely to move around and will value stability - servers
providing services to clients and router and other infrastructure devices'
interfaces.

If a client hosts use these types of addresses for their out bound
connection source addresses, then privacy addresses have been actively
switched off for some reason or are not and have never been available (e.g.
router interfaces). In other words, a conscious choice has been made to
disable privacy. That may or may not be a good idea in that context and in
others' external opinion, however we can't stop people doing stupid things,
we've just got to encourage them to do the right thing either implicitly or
explicitly by choosing good defaults.

This is a better default than EUI-64 based IIDs for when privacy addresses
aren't used or available (by choice).

Regards,
Mark.

> Either we fix that or we stop asserting that this draft is motivated by
privacy considerations.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr"><br>
On 14 May 2016 1:29 PM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:l=
orenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sat, May 14, 2016 at 12:00 PM, Brian E Carpenter &lt;<a href=3D"mai=
lto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt; wrote:=
<br>
&gt;&gt;<br>
&gt;&gt; Because if someone is trying to correlate different types of my tr=
affic,<br>
&gt;&gt; let&#39;s say something sent over IPX and something sent over IPv6=
, the task<br>
&gt;&gt; will be made easier if the lower 48 bits are the same in both type=
s of<br>
&gt;&gt; traffic. (Obviously, someone on-link can use ND to correlate MAC a=
ddress<br>
&gt;&gt; and IP address, so we&#39;re talking about someone observing off-l=
ink packets.)<br>
&gt;<br>
&gt;<br>
&gt; That seems extremely unlikely to happen in practice, given that the va=
st majority of hosts either don&#39;t have an IPX stack at all or have it d=
isabled by default, and embedding a MAC address in a protocol payload is no=
t very useful so people tend not to do it.<br>
&gt;<br>
&gt; By contrast, here is one weakness that is pretty much mandated by this=
 draft as written: because addresses have to be stable, any remote attacker=
 anywhere on the Internet that ever exchanges a packet with that host can t=
rack it every time the host visits the same network, *forever*, with no rec=
ourse. Section 3 point 1.<br>
&gt;</p>
<p dir=3D"ltr">Already fixed, RFC6724:</p>
<p dir=3D"ltr">&quot;5. Changed the default recommendation for Source Addre=
ss Selection Rule 7 to prefer temporary addresses rather than public addres=
ses, while providing an administrative override (in addition to the applica=
tion-specific override that was already specified). This change was made be=
cause of the increasing importance of privacy considerations, as well as th=
e fact that widely deployed implementations have preferred temporary addres=
ses for many years without major application issues.&quot;</p>
<p dir=3D"ltr">Most hosts that will use these addresses as source addresses=
 for their packets are unlikely to move around and will value stability - s=
ervers providing services to clients and router and other infrastructure de=
vices&#39; interfaces.</p>
<p dir=3D"ltr">If a client hosts use these types of addresses for their out=
 bound connection source addresses, then privacy addresses have been active=
ly switched off for some reason or are not and have never been available (e=
.g. router interfaces). In other words, a conscious choice has been made to=
 disable privacy. That may or may not be a good idea in that context and in=
 others&#39; external opinion, however we can&#39;t stop people doing stupi=
d things, we&#39;ve just got to encourage them to do the right thing either=
 implicitly or explicitly by choosing good defaults.</p>
<p dir=3D"ltr">This is a better default than EUI-64 based IIDs for when pri=
vacy addresses aren&#39;t used or available (by choice).</p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; Either we fix that or we stop asserting that this draft=
 is motivated by privacy considerations.<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>
&gt;<br>
</p>

--001a114475989c110a0533112f76--


From nobody Tue May 17 15:27:45 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 BB5FC12DDE4 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 15:27:43 -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 7c3E5XsU9uZt for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 15:27:42 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 BE52512D538 for <ipv6@ietf.org>; Tue, 17 May 2016 15:27:31 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id 206so11193190pfu.0 for <ipv6@ietf.org>; Tue, 17 May 2016 15:27:31 -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=oI6vAYj2b7JoPuvTqj+qE1N+s5WdrN8tEK+fFvEidu8=; b=bidTw9EAif/917gAJ+sDhQjnSQpLSuh0UO3E3DThT7/N/E990Bs7q7xiLrApwjIyGt gwFvMDo204BeMSXip6iMFi+p4cBLb4t1sv2OXsCJ0BlKbLpgIBkVS8oI1R9undTUKj7l kbEbNuxYs8+H8f7Jyowbuc68Bavwm7ac2gYfJy2EFMI/zSfyZsVMQ0zW7hBT/5frXkAE Tmip00mc6kD91fQRAz9BBZYiSud7sJPtkKEX/H8ynERApsFQ4IvB7fSt6mjLaUKmOAih CTOGMejrzV/HIqz2VLTr34PP2KV45LWWxQ4W9JIU6BfFOTYcmG5DfTPimVurYmUPoA15 jqQA==
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=oI6vAYj2b7JoPuvTqj+qE1N+s5WdrN8tEK+fFvEidu8=; b=P9XSIYohBaK1ThKGrEfk9sP3GzmElRK0byNSkVoCeY6XqH5txTyxJZwusYCRvYlbp2 bIL2tvDW3fMdd/b90oD6qfMl1Qs8gQ3vBtosUf860NdBlEzPcfKdHroUv2X6KWG+mgGt Vj4viG/k8u85ftB9mGEKb5UFuj0Ys8dbXvB53P01YntVrdr9rMAWRUtTVOahtpMKLvcU aKQ2eG91JuA5sKUvpb6RTPxSCj1frER0ToCJWlPU3sDcq7FvLmJgkquDLKyDjAusdLfy WkKyUz+znAbYL+nncBHKD+WO8EqfBby9wYhiMDTNe2z2Eh7FSe0OAhNMT5ElMqEmjUGY 5OJw==
X-Gm-Message-State: AOPr4FW8VsBXgbxYygqHjeUya6pbrzuhvUdsBE0+4afVnY8/gc/0BzLtaz1nYkfkiJhnqQ==
X-Received: by 10.98.18.195 with SMTP id 64mr5695852pfs.152.1463524051454; Tue, 17 May 2016 15:27:31 -0700 (PDT)
Received: from ?IPv6:2406:e007:79a7:1:28cc:dc4c:9703:6781? ([2406:e007:79a7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id ba9sm7074485pab.24.2016.05.17.15.27.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 15:27:30 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: joel jaeggli <joelja@bogus.com>, Lorenzo Colitti <lorenzo@google.com>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com>
Date: Wed, 18 May 2016 10:27:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iuQjcTD23KyVAAVgsh_1osNAioA>
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: Tue, 17 May 2016 22:27:44 -0000

On 18/05/2016 03:32, joel jaeggli wrote:
> On 5/17/16 4:48 AM, Lorenzo Colitti wrote:
>> On Tue, May 17, 2016 at 2:29 AM, Alissa Cooper <alissa@cooperw.in
>> <mailto:alissa@cooperw.in>> wrote:
>> =20
>>
>>     I would frankly be thrilled if we could get away from stable
>>     addresses altogether. But I=E2=80=99m skeptical about the feasibil=
ity of
>>     achieving consensus around that at present. Defining the approach =
in
>>     this draft in the meantime is certainly motivated by consideration=

>>     for privacy improvement for me, even if that improvement is increm=
ental.
>>
>> =20
>> A much greater improvement in terms of privacy, and a much easier one =
in
>> terms of sheer number of RFCs that need to be updated, would derive fr=
om
>> forbidding or recommending against embedding *stable* link layer
>> addresses in IIDs.
>=20
> which sounds fine by me.

Well, we could have the draft say this, but I think it would still be a
normative update to all the v6-over-foo RFCs for the case where randomize=
d
MAC addresses are not active (i.e. basically 100% of the installed base).=


    Brian


From nobody Tue May 17 16:26:56 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 D632812DAD9 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 16:26:53 -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=2sjjoMLH; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=bF+mruqK
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 eXWDqpEtw0dt for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 16:26:52 -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 313EE12DAD8 for <ipv6@ietf.org>; Tue, 17 May 2016 16:26:52 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 86C822085E for <ipv6@ietf.org>; Tue, 17 May 2016 19:26:51 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 17 May 2016 19:26:51 -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=FBNAo m1/xuOv7UoNNg3L/gJ9+fw=; b=2sjjoMLHORvB9mTLEU6xcZasvXQIgWLHaKrc/ EDqscdQ/KYAT6KCWzdkMa/GRb0r6H/TL7Fzc2Mrel5kiN6m4Kgf1u9Kw22SzojcF IYo+tlR6EqsZRCvQ2frxgvl9/uq7pFGeVCBrMo/k+Z2vMpnbyXtC/80XXkQDgK5v +Eiv3k=
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=FBNAom1/xuOv7UoNNg3L/gJ9+fw=; b=bF+mr uqKL5w0zsNl/ZMnxgQm+m4RhQdxLfAisYO74wOlP3yk7BOQak8AMqNPqw1Cm+96B F5yhu+cNgSr4moduCXEgoRv6Ij7+n1FaeIO+GrkNa4nteYXbeqacAAX5h8cInKja 9IfKs3lSB2CtzwQFjpDl5HKZZ59isyH+vNWuak=
X-Sasl-enc: q/NCCJEmramIlLI99RokAfe+jGskyqwC75Edw3VgRg84 1463527611
Received: from dhcp-171-68-20-85.cisco.com (dhcp-171-68-20-85.cisco.com [171.68.20.85]) by mail.messagingengine.com (Postfix) with ESMTPA id D5CDA6800F3; Tue, 17 May 2016 19:26:50 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_CCC5576E-C3AF-4E3C-ADCE-EB2810749A9B"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com>
Date: Tue, 17 May 2016 16:26:55 -0700
Message-Id: <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TwsicRaHpF4gnsKNX-S5LG2ucz0>
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: Tue, 17 May 2016 23:26:54 -0000

--Apple-Mail=_CCC5576E-C3AF-4E3C-ADCE-EB2810749A9B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On May 17, 2016, at 3:27 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 18/05/2016 03:32, joel jaeggli wrote:
>> On 5/17/16 4:48 AM, Lorenzo Colitti wrote:
>>> On Tue, May 17, 2016 at 2:29 AM, Alissa Cooper <alissa@cooperw.in
>>> <mailto:alissa@cooperw.in>> wrote:
>>>=20
>>>=20
>>>    I would frankly be thrilled if we could get away from stable
>>>    addresses altogether. But I=E2=80=99m skeptical about the =
feasibility of
>>>    achieving consensus around that at present. Defining the approach =
in
>>>    this draft in the meantime is certainly motivated by =
consideration
>>>    for privacy improvement for me, even if that improvement is =
incremental.
>>>=20
>>>=20
>>> A much greater improvement in terms of privacy, and a much easier =
one in
>>> terms of sheer number of RFCs that need to be updated, would derive =
from
>>> forbidding or recommending against embedding *stable* link layer
>>> addresses in IIDs.
>>=20
>> which sounds fine by me.
>=20
> Well, we could have the draft say this, but I think it would still be =
a
> normative update to all the v6-over-foo RFCs for the case where =
randomized
> MAC addresses are not active (i.e. basically 100% of the installed =
base).

And the layer violation would still create the possibility for =
correlating activities between entities that see layer 3 identifiers and =
entities that see only layer 2 identifiers.

What if we dropped requirement #1 in Section 3, but left the rest the =
same? This would open the door such that people who wanted to comply =
with the SHOULD-level recommendation in this spec in the presence of =
randomized MAC addresses still could (e.g., by implementing 7217 and =
using the randomized MAC as the Net_Iface parameter), but directly =
embedding a MAC address in the IID would still go against the SHOULD NOT =
recommendation here.

Alissa

>=20
>    Brian


--Apple-Mail=_CCC5576E-C3AF-4E3C-ADCE-EB2810749A9B
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""><br class=3D""></div><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On May 17, 2016, at 3:27 PM, =
Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">On 18/05/2016 03:32, joel jaeggli =
wrote:</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">On =
5/17/16 4:48 AM, Lorenzo Colitti wrote:<br class=3D""><blockquote =
type=3D"cite" class=3D"">On Tue, May 17, 2016 at 2:29 AM, Alissa Cooper =
&lt;<a href=3D"mailto:alissa@cooperw.in" =
class=3D"">alissa@cooperw.in</a><br class=3D"">&lt;<a =
href=3D"mailto:alissa@cooperw.in" =
class=3D"">mailto:alissa@cooperw.in</a>&gt;&gt; wrote:<br class=3D""><br =
class=3D""><br class=3D"">&nbsp;&nbsp;&nbsp;I would frankly be thrilled =
if we could get away from stable<br class=3D"">&nbsp;&nbsp;&nbsp;addresses=
 altogether. But I=E2=80=99m skeptical about the feasibility of<br =
class=3D"">&nbsp;&nbsp;&nbsp;achieving consensus around that at present. =
Defining the approach in<br class=3D"">&nbsp;&nbsp;&nbsp;this draft in =
the meantime is certainly motivated by consideration<br =
class=3D"">&nbsp;&nbsp;&nbsp;for privacy improvement for me, even if =
that improvement is incremental.<br class=3D""><br class=3D""><br =
class=3D"">A much greater improvement in terms of privacy, and a much =
easier one in<br class=3D"">terms of sheer number of RFCs that need to =
be updated, would derive from<br class=3D"">forbidding or recommending =
against embedding *stable* link layer<br class=3D"">addresses in =
IIDs.<br class=3D""></blockquote><br class=3D"">which sounds fine by =
me.<br class=3D""></blockquote><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Well, we could have the draft say this, =
but I think it would still be a</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">normative update to all the v6-over-foo =
RFCs for the case where randomized</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">MAC addresses are not active (i.e. =
basically 100% of the installed base).</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""></div></blockquote><div><br class=3D""></div><div>And =
the layer violation would still create the possibility for correlating =
activities between entities that see layer 3 identifiers and entities =
that see only layer 2 identifiers.</div><div><br =
class=3D""></div><div>What if we dropped requirement #1 in Section 3, =
but left the rest the same? This would open the door such that people =
who wanted to comply with the SHOULD-level recommendation in this spec =
in the presence of randomized MAC addresses still could (e.g., by =
implementing 7217 and using the randomized MAC as the Net_Iface =
parameter), but directly embedding a MAC address in the IID would still =
go against the SHOULD NOT recommendation here.</div><div><br =
class=3D""></div><div>Alissa</div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" =
class=3D"">&nbsp;&nbsp;&nbsp;Brian</span></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_CCC5576E-C3AF-4E3C-ADCE-EB2810749A9B--


From nobody Tue May 17 17:24:17 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 C82E012D548 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:24:15 -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 FGRUMC6UmPw8 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:24:13 -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 BE52D12D15D for <ipv6@ietf.org>; Tue, 17 May 2016 17:24:12 -0700 (PDT)
Received: from [100.68.251.15] (unknown [152.206.104.174]) (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 BF10582886; Wed, 18 May 2016 02:23:22 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bob Hinden <bob.hinden@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573B36D3.8010502@si6networks.com>
Date: Tue, 17 May 2016 11:20:51 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/M_OKHJfc6Z_QYHn4z2ADVu_4tHQ>
Cc: IPv6 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, 18 May 2016 00:24:16 -0000

Hi, Jinmei,

Thanks so much for your feedback! Comments in-line....

On 05/13/2016 01:55 PM, ç¥žæ˜Žé�”å“‰ wrote:
[....]
> 
> I've read version 11 of the document.  Personally I don't have a
> strong objection to publishing it, but, if I understand the past
> concerns correctly, I suspect this version don't fully address them.
> I also have one non-trivial point, which I would like to be address
> before publication.
> 
> If my understanding is correct, one major concern raised in the past
> was that some implementors may simply not see the need for the
> stability and just want to address the security/privacy issues in a
> different way (such as just using randomized link-layer addresses).  I
> don't have a strong opinion on this particular concern myself, but I
> see the point of such concerns.  If the intent of this document is not
> to refuse the concern (which I'm not sure about), the current tone
> still seems to be too normative.

There are multiple reasons for which that is the wrong approach and/or
incorrect.

They are stated in the I-D as:
   More generally, the reuse of identifiers that have their own
   semantics or properties across different contexts or scopes can be
   detrimental for security and privacy
   [I-D.gont-predictable-numeric-ids].  In the case of traditional
   stable IPv6 IIDs, some of the security and privacy implications are
   dependent on the properties of the underlying link-layer addresses
   (e.g., whether the link-layer address is ephemeral or randomly
   generated), while other implications (e.g., reduction of the entropy
   of the IID) depend on the algorithm for generating the IID itself.


A more thorough explanation was provided by Alissa during the last IETF
meeting, and can be summarized as:

* Using an ID in a different context or different scope (than originally
meant for), or with additional semantics than those required for
interoperability results in security/privacy implications. Please read:
draft-gont-predictable-numeric-ids

* Sticking to MAC-based IIDs (when randomizing MAC addresses) is not a
good idea because:
  + Attempts to ignore a flaw, relying on something the host does not
control
     e.g. we do not control whether MAC addr randomization algorithm is
     appropriate or if it is actually possible Wastes 18 bits of entropy

 + Might even lead to interoperability problems
     There's no recovery strategy for DAD failures in traditional SLAAC


* RFC7217 and default-iids is about replacing the
default scheme for generating stable addresses

* Don't want stable addresses?
  1) Update RFC 4941 such that stable addresses are not required (huge
potential for interoperability problems)
  2) Use the randomized MAC address as the Net_Iface parameter of RFC7217.
  3) Note: IEEE has RFC7217-like stable per network MAC addresses



Besides the "concerns" raised by Lorenzo assume you use RFC7217-only. If
you care about privacy, you should be using RFC4941, in which all
outgoiing connections would prefer the temporary addresses, rather than
the stable ones -- that's what RFC4941 is about, anyway.


> Again, I'm not sure if the intent is
> to address the concern, but if it is, I think something like the
> following will be necessary:
> 
> - clarify that this recommendation is only for environments where
>   address stability is needed

This is already noted in the current version of this document.
That said, the current specs (see RFC4941) essentially require stable
addresses 8temp addresses are generated along the traditional/stable ones).

Another way to put is s that this recommendation applies where hosts
would otherwise embed a link-layer address in the IID (this is stated in
the draft already, anyway).


> - clarify that this document assumes "link layer addresses" are
>   something permanent, such as MAC addresses that don't change
>   throughout the lifetime of the node using the hardware
> - update the requirement level and wording to existing RFCs. 

We don't really need to make assumptions about layer-2
addresses/identifiers -- we're standardizing what we do at layer-3.

The root of this and many other flaws is making assumptions at layer N
regarding things at layer (N-1) where there's no reason at all to make
such assumptions.


>   For
>   example, replaced text for RFC2462 provided in Section 6.1
> 
>    The Interface Identifier [AARCH] for an Ethernet interface MUST be
>    generated as specified in [RFCXXXX].
> 
>   is probably too strong, since this would invalidate any
>   implementation that doesn't implement or use RFCXXXX.  The same
>   sense of comment applies to all similar changes.

RFCXXXX essentially just says what the default algorithm should be.



> And, one other point I want to be addressed: in Section 4 it states:
> 
>    By default, DHCPv6 server implementations SHOULD NOT generate
>    predictable IPv6 addresses (such as IPv6 addresses where the IIDs are
>    consecutive small numbers).  [I-D.ietf-dhc-stable-privacy-addresses]
>    specifies one possible algorithm that could be employed to comply
>    with this requirement.  Another possible algorithm would be to select
>    a pseudo-random value chosen from a discrete uniform distribution,
>    while avoiding the reserved IPv6 Interface Identifiers [RFC5453]
>    [IANA-RESERVED-IID].
> 
>  I suggest just removing the second sentence.
>  ietf-dhc-stable-privacy-addresses is not a dhc wg item anymore due to
>  some controversy, and it's not clear what will happen to its
>  successor in the form of individual submission:
>  draft-gont-dhcpv6-stable-privacy-addresses-01
>  Since this sentence is only to show an example, just showing the
>  "another possible algorithm" would suffice.

I will check what the status of the corresponding draft-gont version of
the I-D is. To the extent that is possible, I'd keep it, since
ietf-dhc-stable-privacy-addresses leads to stable addresses, while a
simple randomization scheme doesn't.


> Finally, one minor editorial nit: in section 6.14
> 
>    for instance, using a method described in [8], to autoconfigure one
>    or more global unicast addresses.
> 
> there should be a 'cut here' line after this text.

Good grief!

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 Tue May 17 17:24:57 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 61D3312D548 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:24:55 -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 tv-LiMbgkt6t for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:24:54 -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 87F1812DAF4 for <ipv6@ietf.org>; Tue, 17 May 2016 17:24:54 -0700 (PDT)
Received: from [100.68.251.15] (unknown [152.206.104.174]) (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 8631282886; Wed, 18 May 2016 02:24:48 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573B3BA8.70803@si6networks.com>
Date: Tue, 17 May 2016 11:41:28 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/UlqkhZXp0YywF--JsufxCM2Oo2k>
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, 18 May 2016 00:24:55 -0000

On 05/13/2016 11:29 PM, Lorenzo Colitti wrote:
> On Sat, May 14, 2016 at 12:00 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     Because if someone is trying to correlate different types of my traffic,
>     let's say something sent over IPX and something sent over IPv6, the task
>     will be made easier if the lower 48 bits are the same in both types of
>     traffic. (Obviously, someone on-link can use ND to correlate MAC address
>     and IP address, so we're talking about someone observing off-link
>     packets.)
> 
> That seems extremely unlikely to happen in practice,

Yes... as was "pervasive monitoring" and others. -- C'mon...

That's not how you think security&privacy wise: either provide numbers
that show that that can't happen (which you really can't), or assume it
will happen. You have to fail on the safe side, not on the other. And
since you cannot predict the standardization of other technologies
(either) -- which might happen outside the IETF --- I'm not sure how you
can make this sort of claim.




> By contrast, here is one weakness that is pretty much mandated by this
> draft as written: because addresses have to be stable, any remote
> attacker anywhere on the Internet that ever exchanges a packet with that
> host can track it every time the host visits the same network,
> *forever*, with no recourse. Section 3 point 1.

Use RFC4941 for that -- that's why they were standardized in the first
place. And you choose how you employ your addresses.

And if you just hate the fact of having a stable address, please write a
proposal to update RFC4941, such that stable addresses (alongside
temporary addresses) are not required.


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





From nobody Tue May 17 17:25:36 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 1DA3012DB03 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:25:17 -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 4Q6fwygb8hyX for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:25:16 -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 C31FF12DAF4 for <ipv6@ietf.org>; Tue, 17 May 2016 17:25:15 -0700 (PDT)
Received: from [100.68.251.15] (unknown [152.206.104.174]) (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 6C26A82888; Wed, 18 May 2016 02:25:11 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573B450F.3040700@si6networks.com>
Date: Tue, 17 May 2016 12:21:35 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tb77KoJQ1ZpzgvaHt6lkI2oUTq0>
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, 18 May 2016 00:25:17 -0000

Lorenzo,

On 05/13/2016 09:55 PM, Lorenzo Colitti wrote:
> 
> This draft says that existing address generation mechanisms are bad for
> privacy, and proceeds to change them. But there is nothing wrong with
> the existing address generation mechanisms as if the link-layer
> addresses are not stable, (e.g., random MAC addresses), and a growing
> body of IETF work 

Yes, there is *a lot* wrong about that. Actually, the fact that we've
been embedding MAC addresses in the IID is the reason why we're having
this discussion.

Please read: draft-gont-predictable-numeric-ids for a discussion of why
embedding MAC addresses in the IID is bad.

Among others (and besides the reasons Brian already mentioned):

* Attempts to ignore a flaw, relying on something that we do not
control, and that the host may not control
  + e.g. we do not control whether MAC addr randomization algorithm is
appropriate or if it is actually possible to randomize it
  + it may be impossible for the node to randomize the MAC address

* Wastes 18 bits of entropy

* May lead to interoperability issues



> This draft forbids implementations from using existing address
> generation mechanisms using random MAC addresses, which is a perfectly
> valid way to address the privacy problem this draft is purportedly
> solving, 

It is not, as noted above. And I'm puzzled that after 30+ years of
improper numeric ids (draft-gont-predictable-numeric-ids), you keep
insisting on this.




> Here are several examples of how this draft forbids using address
> generation mechanisms with random MAC addresses.
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.

Would "apply only in cases where implementations otherwise would embed a
link-layer address in the IID, as for traditional SLAAC addresses"?


> ...
>    In standardized recommendations for IPv6 IID generation meant to
>    achieve particular security and privacy properties, it is therefore
>    necessary to recommend against embedding link-layer addresses in IPv6
>    IIDs.
> ...

Yes, this is intended. And too bad that you seem to keep pushing a
flawed scheme.


>    By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed the underlying link-layer address in the IID.
> 
> These statements should not say "link-layer address". They should say
> "stable link-layer-address" or "non-ephemeral link-layer-address" or
> "link-layer address that are not known to be ephemeral".

No. It says what it is meant to say. Please read:
draft-gont-predictable-numeric-ids



> Worse, consider this normative text:
> 
>    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 MUST be
>    generated as specified in [RFCXXXX].
> 
> This explicitly prohibits an implementation from taking a random MAC
> address and forming an EUI-64 address out of it.

Exactly: you don't reuse identifiers in different layers, for different
scopes, etc. That's a horrible thing to do security&privacy-wise. I'm
glad that, at the very least, you're on record for proposing that and
that I'm on record for noting this is a bad idea. -- so that none can
say "we didn't know this could happen" when s* happens.

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





From nobody Tue May 17 17:26:15 2016
Return-Path: <fernando@gont.com.ar>
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 CFBB912D106 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:26:13 -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 YFq8eyOr__Fr for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 17:26:12 -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 7409212B032 for <6man@ietf.org>; Tue, 17 May 2016 17:26:12 -0700 (PDT)
Received: from [100.68.251.15] (unknown [152.206.104.174]) (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 49EC18288E; Wed, 18 May 2016 02:26:04 +0200 (CEST)
From: Fernando Gont <fernando@gont.com.ar>
Subject: default-iids and stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573B5FAC.7060300@gont.com.ar>
Date: Tue, 17 May 2016 14:15:08 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EpqPfYhk5k_ZRebru8SZaw7FE10>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 00:26:14 -0000

Lorenzo (and wg),

The two issues raised by Lorenzo regarding default-iids boil down to:

1) The ability to embed MAC addresses in the IID

2) The requirement to have stable addresses


This document does ban "1)" as the default algorithm for generating
IIDs, for the reasons discussed in RFC7721 and
draft-gont-predictable-numeric-ids. We have a very long history of
improper numeric IDs, and I guess that, regarding this one, we simply
disagree with Lorenzo.


Regarding "2)", this document does not specify any new requirements on
the topic. Essentially, nodes are implied to configure a stable
addresses as a result of SLAAC&traditional link-layer address
properties, and more explicitly by this text in RFC4941:

* Section 3, bullet #1:
   2.  Create additional addresses based on a random interface
       identifier for the purpose of initiating outgoing sessions.

* Section 3.3, bullet #1:
   1.  Process the Prefix Information Option as defined in [ADDRCONF],
       either creating a new public address or adjusting the lifetimes
       of existing addresses, both public and temporary.

* Section 3.3, bullet #3:
   3.  When a new public address is created as described in [ADDRCONF],
       the node SHOULD also create a new temporary address.

* Section 3.6, for instance, says (even recommending that temp addrs
default to "off"):
   The use of temporary addresses may cause unexpected difficulties with
   some applications.  As described below, some servers refuse to accept
   communications from clients for which they cannot map the IP address
   into a DNS name.  In addition, some applications may not behave
   robustly if temporary addresses are used and an address expires
   before the application has terminated, or if it opens multiple
   sessions, but expects them to all use the same addresses.
   Consequently, the use of temporary addresses SHOULD be disabled by
   default in order to minimize potential disruptions.



Our document simply requires implementations that their
stable addresses are RFC7721-friendly. But if anything, the requirement
of whether to have a stable address or not is not something introduced
by our document.

As a co-author of draft-ietf-6man-default-iids, I just wanted to check
that we're on the same page, because I have the feeling that the above
keeps getting misinterpreted.

I believe all of the co-authors of default-iids agree and understand
that there can be scenarios where you may want to do
temporary-addresses-only. However, that is orthogonal to this particular
document (default-iids), and would probably require an update to
RFC4941, such that temporary addresses can be employed as a replacement
of stable addresses, rather than as something that you do "in addition
to" them.

This document is about how to do stable addresses in a more
RFC7721-friendly way than we currently do.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Tue May 17 18:03:33 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 06AAD12D5C5 for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 18:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 WrNU_fcXU2pj for <ipv6@ietfa.amsl.com>; Tue, 17 May 2016 18:03:30 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 BF32F12D55D for <6man@ietf.org>; Tue, 17 May 2016 18:03:29 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id x189so33431393ywe.3 for <6man@ietf.org>; Tue, 17 May 2016 18:03:29 -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=Kx1xS8x+AT7H+QEnigNadZ+gZY+0fkHRfIlN/7Pu5vk=; b=CANtb5ANxcE6WM6104WggRPuVAOEQbHg+v+0dvviHlPxQZUxkScwMyHi4lWosf5RrP J5bguf+QyHxRIrFM9kSLfp1d2jMJQX7tH+zhq29GGWSvK8ASBhH7LO93mcxaSzAa0ObD djKmAfBza+rg/GQBNEAcU28tjyqxjFMz3nV2nk3ZxIojbiJ7IAbuIx9TsS4alH9BEUL4 2/NMyOR+AogJf4mNoC84ty9sPRXZ+N2jtlltTNLaiqVJnSz0786pH02RIJvUvoHMkhrX c5HwjTpKtSodxw03bKmiSMuDR8iyjBGDTody0Oc0FViVvrRj7ULMBZTnc5W+0YQ5w+uD R/yQ==
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=Kx1xS8x+AT7H+QEnigNadZ+gZY+0fkHRfIlN/7Pu5vk=; b=PqwPusF9rvg+xSFm8z6HJyA6V+JdznAi+1YeQOk4GdLRlh8StwfjHT7AY20D/d7h/g LyqIggctaAJ4NujYEbhFHUOXaD4+EhNWLkGP9T2Xa6j/3v0C1ijd35SaENcKo2qCUuG4 BhHrWNDph0yqHICkAQ64sf7fIsJ2pEe5BcVWOOhq0mn+9KPizELmSf4S6d3xWqFqf7nu uc7mfEp06s5ug9++7EX1QhZ2q39wZhPZtwFKNYlq+Toqh8IPx7Eq5wU+c1tNw65pqXmT OLkwkVQV9QOc/0n7HxN+B6a5j2BQiIMIW2b+LA4bYI9quV37eNd+cXmk7MPz83bydm6O 0PmA==
X-Gm-Message-State: AOPr4FX+ttHF+Y92yTm5pDlPO8UEozPkW/bLp0BgeYeQUP6CdSZElA112VpfzvMIUG9Q+N4mxuSU9wDlHtKaCNfO
X-Received: by 10.129.80.11 with SMTP id e11mr2666549ywb.197.1463533408965; Tue, 17 May 2016 18:03:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Tue, 17 May 2016 18:03:09 -0700 (PDT)
In-Reply-To: <573B5FAC.7060300@gont.com.ar>
References: <573B5FAC.7060300@gont.com.ar>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 18 May 2016 10:03:09 +0900
Message-ID: <CAKD1Yr3XUh-t8B_zKz9SPOdsG4Gyf-VhW33zDzb9PSNMo9uXTw@mail.gmail.com>
Subject: Re: default-iids and stable addresses
To: Fernando Gont <fernando@gont.com.ar>
Content-Type: multipart/alternative; boundary=001a1147d2b2f5d3f50533136c90
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8yRmzSpktabOjO0fYkhd2TWkoHE>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 01:03:32 -0000

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

Fernando,

your points are technically correct: from a standards perspective,
draft-default-iids makes things no worse than they are. In fact it's a mild
improvement.

However, we operate in a very different world than we did in 1996. We know
know that pervasive monitoring is a real threat, and other parts of the
IETF are explicitly working on randomizing link-layer addresses.

In such an environment, I believe this WG cannot credibly mount a major
overhaul of IPv6 IID generation rules, and simply say that privacy is "no
worse than it already was". If we mount a major overhaul (and it *is* a
major overhaul, both in terms of number of RFCs that are changed and in
terms of devices affected), we have to do better than that in addressing
the privacy concerns inherent in the existing specs.

In its current state, draft-default-iids still says that:

   - For every prefix, every host SHOULD configure addresses that never
   change - permanently, until the end of time.
   - Every link layer, past present and future, MUST define mechanisms that
   allow calculation of such per-link-permanent addresses.
   - Even though MAC address randomization is embraced by other parts of
   the IETF and explicitly dealt with in standards track RFCs, nodes SHOULD
   NOT use said random MAC addresses to form IPv6 IIDs - for no reason that I
   can see.

I don't think it's reasonable for us to make such a recommendation today.
We can and should do better than that.

Cheers,
Lorenzo

On Wed, May 18, 2016 at 3:15 AM, Fernando Gont <fernando@gont.com.ar> wrote:

> Lorenzo (and wg),
>
> The two issues raised by Lorenzo regarding default-iids boil down to:
>
> 1) The ability to embed MAC addresses in the IID
>
> 2) The requirement to have stable addresses
>
>
> This document does ban "1)" as the default algorithm for generating
> IIDs, for the reasons discussed in RFC7721 and
> draft-gont-predictable-numeric-ids. We have a very long history of
> improper numeric IDs, and I guess that, regarding this one, we simply
> disagree with Lorenzo.
>
>
> Regarding "2)", this document does not specify any new requirements on
> the topic. Essentially, nodes are implied to configure a stable
> addresses as a result of SLAAC&traditional link-layer address
> properties, and more explicitly by this text in RFC4941:
>
> * Section 3, bullet #1:
>    2.  Create additional addresses based on a random interface
>        identifier for the purpose of initiating outgoing sessions.
>
> * Section 3.3, bullet #1:
>    1.  Process the Prefix Information Option as defined in [ADDRCONF],
>        either creating a new public address or adjusting the lifetimes
>        of existing addresses, both public and temporary.
>
> * Section 3.3, bullet #3:
>    3.  When a new public address is created as described in [ADDRCONF],
>        the node SHOULD also create a new temporary address.
>
> * Section 3.6, for instance, says (even recommending that temp addrs
> default to "off"):
>    The use of temporary addresses may cause unexpected difficulties with
>    some applications.  As described below, some servers refuse to accept
>    communications from clients for which they cannot map the IP address
>    into a DNS name.  In addition, some applications may not behave
>    robustly if temporary addresses are used and an address expires
>    before the application has terminated, or if it opens multiple
>    sessions, but expects them to all use the same addresses.
>    Consequently, the use of temporary addresses SHOULD be disabled by
>    default in order to minimize potential disruptions.
>
>
>
> Our document simply requires implementations that their
> stable addresses are RFC7721-friendly. But if anything, the requirement
> of whether to have a stable address or not is not something introduced
> by our document.
>
> As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> that we're on the same page, because I have the feeling that the above
> keeps getting misinterpreted.
>
> I believe all of the co-authors of default-iids agree and understand
> that there can be scenarios where you may want to do
> temporary-addresses-only. However, that is orthogonal to this particular
> document (default-iids), and would probably require an update to
> RFC4941, such that temporary addresses can be employed as a replacement
> of stable addresses, rather than as something that you do "in addition
> to" them.
>
> This document is about how to do stable addresses in a more
> RFC7721-friendly way than we currently do.
>
> Thanks!
>
> Best regards,
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>
>
>
>

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

<div dir=3D"ltr">Fernando,<div><br></div><div>your points are technically c=
orrect: from a standards perspective, draft-default-iids makes things no wo=
rse than they are. In fact it&#39;s a mild improvement.</div><div><br></div=
><div>However, we operate in a very different world than we did in 1996. We=
 know know that pervasive monitoring is a real threat, and other parts of t=
he IETF are explicitly working on randomizing link-layer addresses.</div><d=
iv><br></div><div>In such an environment, I believe this WG cannot credibly=
 mount a major overhaul of IPv6 IID generation rules, and simply say that p=
rivacy is &quot;no worse than it already was&quot;. If we mount a major ove=
rhaul (and it *is* a major overhaul, both in terms of number of RFCs that a=
re changed and in terms of devices affected), we have to do better than tha=
t in addressing the privacy concerns inherent in the existing specs.</div><=
div><br></div><div>In its current state, draft-default-iids still says that=
:</div><div><ul><li>For every prefix, every host SHOULD configure addresses=
 that never change - permanently, until the end of time.</li><li>Every link=
 layer, past present and future, MUST define mechanisms that allow calculat=
ion of such per-link-permanent addresses.</li><li>Even though MAC address r=
andomization is embraced by other parts of the IETF and explicitly dealt wi=
th in standards track RFCs, nodes SHOULD NOT use said random MAC addresses =
to form IPv6 IIDs - for no reason that I can see.</li></ul><div>I don&#39;t=
 think it&#39;s reasonable for us to make such a recommendation today. We c=
an and should do better than that.</div></div><div><br></div><div>Cheers,</=
div><div>Lorenzo</div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Wed, May 18, 2016 at 3:15 AM, Fernando Gont <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:fernando@gont.com.ar" target=3D"_blank">fernando@gon=
t.com.ar</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">Lorenzo =
(and wg),<br>
<br>
The two issues raised by Lorenzo regarding default-iids boil down to:<br>
<br>
1) The ability to embed MAC addresses in the IID<br>
<br>
2) The requirement to have stable addresses<br>
<br>
<br>
This document does ban &quot;1)&quot; as the default algorithm for generati=
ng<br>
IIDs, for the reasons discussed in RFC7721 and<br>
draft-gont-predictable-numeric-ids. We have a very long history of<br>
improper numeric IDs, and I guess that, regarding this one, we simply<br>
disagree with Lorenzo.<br>
<br>
<br>
Regarding &quot;2)&quot;, this document does not specify any new requiremen=
ts on<br>
the topic. Essentially, nodes are implied to configure a stable<br>
addresses as a result of SLAAC&amp;traditional link-layer address<br>
properties, and more explicitly by this text in RFC4941:<br>
<br>
* Section 3, bullet #1:<br>
=C2=A0 =C2=A02.=C2=A0 Create additional addresses based on a random interfa=
ce<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0identifier for the purpose of initiating outgoin=
g sessions.<br>
<br>
* Section 3.3, bullet #1:<br>
=C2=A0 =C2=A01.=C2=A0 Process the Prefix Information Option as defined in [=
ADDRCONF],<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0either creating a new public address or adjustin=
g the lifetimes<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0of existing addresses, both public and temporary=
.<br>
<br>
* Section 3.3, bullet #3:<br>
=C2=A0 =C2=A03.=C2=A0 When a new public address is created as described in =
[ADDRCONF],<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0the node SHOULD also create a new temporary addr=
ess.<br>
<br>
* Section 3.6, for instance, says (even recommending that temp addrs<br>
default to &quot;off&quot;):<br>
=C2=A0 =C2=A0The use of temporary addresses may cause unexpected difficulti=
es with<br>
=C2=A0 =C2=A0some applications.=C2=A0 As described below, some servers refu=
se to accept<br>
=C2=A0 =C2=A0communications from clients for which they cannot map the IP a=
ddress<br>
=C2=A0 =C2=A0into a DNS name.=C2=A0 In addition, some applications may not =
behave<br>
=C2=A0 =C2=A0robustly if temporary addresses are used and an address expire=
s<br>
=C2=A0 =C2=A0before the application has terminated, or if it opens multiple=
<br>
=C2=A0 =C2=A0sessions, but expects them to all use the same addresses.<br>
=C2=A0 =C2=A0Consequently, the use of temporary addresses SHOULD be disable=
d by<br>
=C2=A0 =C2=A0default in order to minimize potential disruptions.<br>
<br>
<br>
<br>
Our document simply requires implementations that their<br>
stable addresses are RFC7721-friendly. But if anything, the requirement<br>
of whether to have a stable address or not is not something introduced<br>
by our document.<br>
<br>
As a co-author of draft-ietf-6man-default-iids, I just wanted to check<br>
that we&#39;re on the same page, because I have the feeling that the above<=
br>
keeps getting misinterpreted.<br>
<br>
I believe all of the co-authors of default-iids agree and understand<br>
that there can be scenarios where you may want to do<br>
temporary-addresses-only. However, that is orthogonal to this particular<br=
>
document (default-iids), and would probably require an update to<br>
RFC4941, such that temporary addresses can be employed as a replacement<br>
of stable addresses, rather than as something that you do &quot;in addition=
<br>
to&quot; them.<br>
<br>
This document is about how to do stable addresses in a more<br>
RFC7721-friendly way than we currently do.<br>
<br>
Thanks!<br>
<br>
Best regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Fernando Gont<br>
e-mail: <a href=3D"mailto:fernando@gont.com.ar">fernando@gont.com.ar</a> ||=
 <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a><br>
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a1147d2b2f5d3f50533136c90--


From nobody Wed May 18 04:13:38 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 646DA12B01F for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 04:13:37 -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 ovHyYgKoAk7q for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 04:13:35 -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 337A712B01A for <6man@ietf.org>; Wed, 18 May 2016 04:13:34 -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; 18 May 2016 11:13:32 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E64B99CC7C; Wed, 18 May 2016 04:13:31 -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=hZfM71IgE2zV8u/tYXXhAJhjYrE=; b= haG1GxKPI9HM48DMFzbS6ymIC+dwG+36OeK1hC1B5a6JWkmv4dFwcu5g1dEWL8oN GL3Q4NEprymu1r2lWrH74hvID9VLXMXcZQwCDjTEfEQKjuadtzeX3eSLFAPdVRR8 vNbTTcU2XEeu5LS9E/A/F7D/rWoDMUCkXnuhhni9vwc=
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=aeuu3yd98j4RiG5IrKzFhTlsPp RJzwVcejL71rxXMMdd/bq9xRg3LC/D8s/rLQlzzGHhFyYMhOT0ShCgSPLl6sbsZ5 erBjCxYxQmI6CABtWS/SU/rNYy4JsvT6BRh0acZLjxQn1uYlP9zjW+kBcWpprKfk bfp2s2r+cYUQRrAvg=
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 6E1D29CC4E; Wed, 18 May 2016 04:13:31 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 7953E1695FD8; Wed, 18 May 2016 13:13:30 +0200 (CEST)
Subject: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E4596AD5-F84F-42A9-B9A3-96BB4FCB66D4"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <573B5FAC.7060300@gont.com.ar>
Date: Wed, 18 May 2016 13:13:27 +0200
Message-Id: <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>
References: <573B5FAC.7060300@gont.com.ar>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9YPWa0AaZIfJhpqZaaNp7MsJujU>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Fernando Gont <fernando@gont.com.ar>
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, 18 May 2016 11:13:37 -0000

--Apple-Mail=_E4596AD5-F84F-42A9-B9A3-96BB4FCB66D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This email from Fernando provides a good introduction to an outstanding =
question from Buenos Aires.

The current plan is to take RFC4941 to Internet Standard unchanged.
A question was raised if 4941 requires public addresses or not, and if =
we have to update 4941 text, or if we can live with the current text, =
and still allow for interfaces with only temporary addresses.

Opinions?

Best regards,
Ole

> On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar> wrote:
>=20
> Lorenzo (and wg),
>=20
> The two issues raised by Lorenzo regarding default-iids boil down to:
>=20
> 1) The ability to embed MAC addresses in the IID
>=20
> 2) The requirement to have stable addresses
>=20
>=20
> This document does ban "1)" as the default algorithm for generating
> IIDs, for the reasons discussed in RFC7721 and
> draft-gont-predictable-numeric-ids. We have a very long history of
> improper numeric IDs, and I guess that, regarding this one, we simply
> disagree with Lorenzo.
>=20
>=20
> Regarding "2)", this document does not specify any new requirements on
> the topic. Essentially, nodes are implied to configure a stable
> addresses as a result of SLAAC&traditional link-layer address
> properties, and more explicitly by this text in RFC4941:
>=20
> * Section 3, bullet #1:
>   2.  Create additional addresses based on a random interface
>       identifier for the purpose of initiating outgoing sessions.
>=20
> * Section 3.3, bullet #1:
>   1.  Process the Prefix Information Option as defined in [ADDRCONF],
>       either creating a new public address or adjusting the lifetimes
>       of existing addresses, both public and temporary.
>=20
> * Section 3.3, bullet #3:
>   3.  When a new public address is created as described in [ADDRCONF],
>       the node SHOULD also create a new temporary address.
>=20
> * Section 3.6, for instance, says (even recommending that temp addrs
> default to "off"):
>   The use of temporary addresses may cause unexpected difficulties =
with
>   some applications.  As described below, some servers refuse to =
accept
>   communications from clients for which they cannot map the IP address
>   into a DNS name.  In addition, some applications may not behave
>   robustly if temporary addresses are used and an address expires
>   before the application has terminated, or if it opens multiple
>   sessions, but expects them to all use the same addresses.
>   Consequently, the use of temporary addresses SHOULD be disabled by
>   default in order to minimize potential disruptions.
>=20
>=20
>=20
> Our document simply requires implementations that their
> stable addresses are RFC7721-friendly. But if anything, the =
requirement
> of whether to have a stable address or not is not something introduced
> by our document.
>=20
> As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> that we're on the same page, because I have the feeling that the above
> keeps getting misinterpreted.
>=20
> I believe all of the co-authors of default-iids agree and understand
> that there can be scenarios where you may want to do
> temporary-addresses-only. However, that is orthogonal to this =
particular
> document (default-iids), and would probably require an update to
> RFC4941, such that temporary addresses can be employed as a =
replacement
> of stable addresses, rather than as something that you do "in addition
> to" them.
>=20
> This document is about how to do stable addresses in a more
> RFC7721-friendly way than we currently do.
>=20
> Thanks!
>=20
> Best regards,
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_E4596AD5-F84F-42A9-B9A3-96BB4FCB66D4
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

iQEcBAEBCgAGBQJXPE5aAAoJED4aXnjSQuKWhpMIAJq/KddhqbYi+OvzuXuw3NyD
G6M8mstM/VI71wbpjmisyqbRZ1uCV2MY+AhmZ2tiyFRc4PWjUjAJJQl8SlGjuSfb
559k4WEvNgWi3qRYSHkLpcv31HqNGr5fOOgEVi8PwFEbVm8s8xktTseqyBDDTpMl
l0t2bZ7Sxs447anF3xtH14Rdj1mG0sdDjU1mOY6lFVaza1l83KIT68P2+m+7UM6w
WHMgSvcqiusOOumIJ0dg5B6dUswl3qxB+R/QeD3pC4NJWF4/gOMQ6nm6bRxyZq5n
IdWqPgXWP+ImvSrSVgQpJnfZsee4bWFFaXxLkKHizJHnAGoBmBPWTxLwq/VdkDo=
=G3RC
-----END PGP SIGNATURE-----

--Apple-Mail=_E4596AD5-F84F-42A9-B9A3-96BB4FCB66D4--


From nobody Wed May 18 06:42:48 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 3DC9212D145 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 06:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 UmBVWEuW3RHj for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 06:42:40 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::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 D2E7012B050 for <6man@ietf.org>; Wed, 18 May 2016 06:42:39 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id g133so48000221ywb.2 for <6man@ietf.org>; Wed, 18 May 2016 06:42:39 -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=O6XZEUTVOYFO/hqsLD9hE9II5gBJarf+ba5ipkb3PNI=; b=ZgisztCFmtTogda39V8oayX98GENQv2hznaybB3fddmPNENW7bcMcjyM3XQGJoIhI5 b9JYJjzseyTh8sRnO4DDxhGagTgT/2Ol84u0P6V017tSHmA4NAcLfWg9Y+PL4WA6D2nG NEOeWqBwcFjDGwqt17XA5KihdxTo79xY+vW06bgVH343pSCjlrpgh8HS9p9j9PwcSzT8 A4BWc4JqZ9KKIJnyW4cOARuCTUit/lXYAH5zOV7nFABy5pSY4EBtQgyEyjTo/moxks0C aWl3An7xckVWqwJs0dUGVeFD400Vm7VWakcrYZEGIJ218/KF+EEfIcdeFGgACK/OjIh0 Qa7A==
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=O6XZEUTVOYFO/hqsLD9hE9II5gBJarf+ba5ipkb3PNI=; b=QWYODVUdnHe8f8E/23KaPODfOMUjf+6dKnR+f8dtYcqb1iWl9zkzB9QhkUA+y8EWXe hB2tU5rjGE8YXyqYM23/eTrzXfzZv3i2+c5PdqPF767skVNCX/DpXWTdap+JzzIF9JOP Mj1404QnCnvMXkhbZ9JQnLALC+8v7HQ3MfzRICK8sTww9R/yeOlIt1Op9Cmr+DOCby1P TOUzSlb8PPW7zO1TAjpzUkc1J+hQ7z/VMeCvrzfAX28aNaCeaUsrn012FTzch/OqExJ6 /CiAWexHoIFeisVhcGSnNGzYwUw0uhki01RhDDpR0MnLG4ehgwjyMo0e69zPtqwn2/P9 vbWg==
X-Gm-Message-State: AOPr4FV5uXM8m2VjtXfjdBNToGMvinu4sNLmTZ28Gq8AT7seHmKSIO2hQDzKr+RZNgu/CUeuebvioKO5YXEAvpY9
X-Received: by 10.13.234.11 with SMTP id t11mr4335167ywe.66.1463578958896; Wed, 18 May 2016 06:42:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 18 May 2016 06:42:14 -0700 (PDT)
In-Reply-To: <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 18 May 2016 22:42:14 +0900
Message-ID: <CAKD1Yr2aWnRVvL6KEheWb1fKn3RPGdYewdb3QVf9w3A1V1wTUQ@mail.gmail.com>
Subject: Re: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=94eb2c0866a0f2be4505331e0746
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/g2NlR3MaQk0U560M00k-i8a0du0>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 13:42:47 -0000

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

As written, RFC 4941 seems to require public addresses. For example:

       If a received
       option will extend the lifetime of a public address, the
       lifetimes of temporary addresses should be extended
...
   3.  When a new public address is created as described in [ADDRCONF],
       the node SHOULD also create a new temporary address.
...
       *  Its Preferred Lifetime is the lower of the Preferred Lifetime
          of the public address or TEMP_PREFERRED_LIFETIME -
          DESYNC_FACTOR.

On Wed, May 18, 2016 at 8:13 PM, <otroan@employees.org> wrote:

> This email from Fernando provides a good introduction to an outstanding
> question from Buenos Aires.
>
> The current plan is to take RFC4941 to Internet Standard unchanged.
> A question was raised if 4941 requires public addresses or not, and if we
> have to update 4941 text, or if we can live with the current text, and
> still allow for interfaces with only temporary addresses.
>
> Opinions?
>
> Best regards,
> Ole
>
> > On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar> wrote:
> >
> > Lorenzo (and wg),
> >
> > The two issues raised by Lorenzo regarding default-iids boil down to:
> >
> > 1) The ability to embed MAC addresses in the IID
> >
> > 2) The requirement to have stable addresses
> >
> >
> > This document does ban "1)" as the default algorithm for generating
> > IIDs, for the reasons discussed in RFC7721 and
> > draft-gont-predictable-numeric-ids. We have a very long history of
> > improper numeric IDs, and I guess that, regarding this one, we simply
> > disagree with Lorenzo.
> >
> >
> > Regarding "2)", this document does not specify any new requirements on
> > the topic. Essentially, nodes are implied to configure a stable
> > addresses as a result of SLAAC&traditional link-layer address
> > properties, and more explicitly by this text in RFC4941:
> >
> > * Section 3, bullet #1:
> >   2.  Create additional addresses based on a random interface
> >       identifier for the purpose of initiating outgoing sessions.
> >
> > * Section 3.3, bullet #1:
> >   1.  Process the Prefix Information Option as defined in [ADDRCONF],
> >       either creating a new public address or adjusting the lifetimes
> >       of existing addresses, both public and temporary.
> >
> > * Section 3.3, bullet #3:
> >   3.  When a new public address is created as described in [ADDRCONF],
> >       the node SHOULD also create a new temporary address.
> >
> > * Section 3.6, for instance, says (even recommending that temp addrs
> > default to "off"):
> >   The use of temporary addresses may cause unexpected difficulties with
> >   some applications.  As described below, some servers refuse to accept
> >   communications from clients for which they cannot map the IP address
> >   into a DNS name.  In addition, some applications may not behave
> >   robustly if temporary addresses are used and an address expires
> >   before the application has terminated, or if it opens multiple
> >   sessions, but expects them to all use the same addresses.
> >   Consequently, the use of temporary addresses SHOULD be disabled by
> >   default in order to minimize potential disruptions.
> >
> >
> >
> > Our document simply requires implementations that their
> > stable addresses are RFC7721-friendly. But if anything, the requirement
> > of whether to have a stable address or not is not something introduced
> > by our document.
> >
> > As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> > that we're on the same page, because I have the feeling that the above
> > keeps getting misinterpreted.
> >
> > I believe all of the co-authors of default-iids agree and understand
> > that there can be scenarios where you may want to do
> > temporary-addresses-only. However, that is orthogonal to this particular
> > document (default-iids), and would probably require an update to
> > RFC4941, such that temporary addresses can be employed as a replacement
> > of stable addresses, rather than as something that you do "in addition
> > to" them.
> >
> > This document is about how to do stable addresses in a more
> > RFC7721-friendly way than we currently do.
> >
> > Thanks!
> >
> > Best regards,
> > --
> > Fernando Gont
> > e-mail: fernando@gont.com.ar || fgont@si6networks.com
> > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>

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

<div dir=3D"ltr">As written, RFC 4941 seems to require public addresses. Fo=
r example:<div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0If a received=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0option will extend the lifetime of a =
public address, the</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0lifetimes of tempo=
rary addresses should be extended</div></div><div>...</div><div>=C2=A0 =C2=
=A03.=C2=A0 When a new public address is created as described in [ADDRCONF]=
,<br></div><div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the node SHOULD also create=
 a new temporary address.</div></div><div>...<br></div><div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0* =C2=A0Its Preferred Lifetime is the lower of the Preferr=
ed Lifetime<br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 of the public =
address or TEMP_PREFERRED_LIFETIME -</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 DESYNC_FACTOR.</div></div></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Wed, May 18, 2016 at 8:13 PM,  <span dir=3D"ltr">&=
lt;<a href=3D"mailto:otroan@employees.org" target=3D"_blank">otroan@employe=
es.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">This email f=
rom Fernando provides a good introduction to an outstanding question from B=
uenos Aires.<br>
<br>
The current plan is to take RFC4941 to Internet Standard unchanged.<br>
A question was raised if 4941 requires public addresses or not, and if we h=
ave to update 4941 text, or if we can live with the current text, and still=
 allow for interfaces with only temporary addresses.<br>
<br>
Opinions?<br>
<br>
Best regards,<br>
Ole<br>
<br>
&gt; On 17 May 2016, at 20:15, Fernando Gont &lt;<a href=3D"mailto:fernando=
@gont.com.ar">fernando@gont.com.ar</a>&gt; wrote:<br>
&gt;<br>
&gt; Lorenzo (and wg),<br>
&gt;<br>
&gt; The two issues raised by Lorenzo regarding default-iids boil down to:<=
br>
&gt;<br>
&gt; 1) The ability to embed MAC addresses in the IID<br>
&gt;<br>
&gt; 2) The requirement to have stable addresses<br>
&gt;<br>
&gt;<br>
&gt; This document does ban &quot;1)&quot; as the default algorithm for gen=
erating<br>
&gt; IIDs, for the reasons discussed in RFC7721 and<br>
&gt; draft-gont-predictable-numeric-ids. We have a very long history of<br>
&gt; improper numeric IDs, and I guess that, regarding this one, we simply<=
br>
&gt; disagree with Lorenzo.<br>
&gt;<br>
&gt;<br>
&gt; Regarding &quot;2)&quot;, this document does not specify any new requi=
rements on<br>
&gt; the topic. Essentially, nodes are implied to configure a stable<br>
&gt; addresses as a result of SLAAC&amp;traditional link-layer address<br>
&gt; properties, and more explicitly by this text in RFC4941:<br>
&gt;<br>
&gt; * Section 3, bullet #1:<br>
&gt;=C2=A0 =C2=A02.=C2=A0 Create additional addresses based on a random int=
erface<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0identifier for the purpose of initiating out=
going sessions.<br>
&gt;<br>
&gt; * Section 3.3, bullet #1:<br>
&gt;=C2=A0 =C2=A01.=C2=A0 Process the Prefix Information Option as defined =
in [ADDRCONF],<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0either creating a new public address or adju=
sting the lifetimes<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0of existing addresses, both public and tempo=
rary.<br>
&gt;<br>
&gt; * Section 3.3, bullet #3:<br>
&gt;=C2=A0 =C2=A03.=C2=A0 When a new public address is created as described=
 in [ADDRCONF],<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0the node SHOULD also create a new temporary =
address.<br>
&gt;<br>
&gt; * Section 3.6, for instance, says (even recommending that temp addrs<b=
r>
&gt; default to &quot;off&quot;):<br>
&gt;=C2=A0 =C2=A0The use of temporary addresses may cause unexpected diffic=
ulties with<br>
&gt;=C2=A0 =C2=A0some applications.=C2=A0 As described below, some servers =
refuse to accept<br>
&gt;=C2=A0 =C2=A0communications from clients for which they cannot map the =
IP address<br>
&gt;=C2=A0 =C2=A0into a DNS name.=C2=A0 In addition, some applications may =
not behave<br>
&gt;=C2=A0 =C2=A0robustly if temporary addresses are used and an address ex=
pires<br>
&gt;=C2=A0 =C2=A0before the application has terminated, or if it opens mult=
iple<br>
&gt;=C2=A0 =C2=A0sessions, but expects them to all use the same addresses.<=
br>
&gt;=C2=A0 =C2=A0Consequently, the use of temporary addresses SHOULD be dis=
abled by<br>
&gt;=C2=A0 =C2=A0default in order to minimize potential disruptions.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Our document simply requires implementations that their<br>
&gt; stable addresses are RFC7721-friendly. But if anything, the requiremen=
t<br>
&gt; of whether to have a stable address or not is not something introduced=
<br>
&gt; by our document.<br>
&gt;<br>
&gt; As a co-author of draft-ietf-6man-default-iids, I just wanted to check=
<br>
&gt; that we&#39;re on the same page, because I have the feeling that the a=
bove<br>
&gt; keeps getting misinterpreted.<br>
&gt;<br>
&gt; I believe all of the co-authors of default-iids agree and understand<b=
r>
&gt; that there can be scenarios where you may want to do<br>
&gt; temporary-addresses-only. However, that is orthogonal to this particul=
ar<br>
&gt; document (default-iids), and would probably require an update to<br>
&gt; RFC4941, such that temporary addresses can be employed as a replacemen=
t<br>
&gt; of stable addresses, rather than as something that you do &quot;in add=
ition<br>
&gt; to&quot; them.<br>
&gt;<br>
&gt; This document is about how to do stable addresses in a more<br>
&gt; RFC7721-friendly way than we currently do.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Best regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">&gt; --<br>
&gt; Fernando Gont<br>
&gt; e-mail: <a href=3D"mailto:fernando@gont.com.ar">fernando@gont.com.ar</=
a> || <a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a><br=
>
&gt; PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1<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" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
<br>
</font></span></blockquote></div><br></div>

--94eb2c0866a0f2be4505331e0746--


From nobody Wed May 18 06:56:54 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 82CC312D1DC for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 06:56:52 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-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=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 h_xPHHU-6H7a for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 06:56:50 -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 003D512D1D9 for <6man@ietf.org>; Wed, 18 May 2016 06:56:49 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lrp0082.outbound.protection.outlook.com [213.199.154.82]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-21-iNropkRIQoWVA9vyxKiLnQ-1; Wed, 18 May 2016 14:56:40 +0100
X-MC-Unique: iNropkRIQoWVA9vyxKiLnQ-1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=1DstbcVjYSAjMpItU412onp8sr3GfOU0NpGJcAhzNtA=; b=C+dojTgIHwPKoIvSrZFvQhZV+7pclD6QxoZmB7SFvDBsGB5K/5sT1iRsLsUTClf3dfM3D5DvDkDtD4rFCrRddGz3LQ05ERA0Isvp5efTzy04d7ibVJPWIRJs09H6XaeoBTfDe9ZfdFmeJmUB7GhPHPPllfs/0Gnoct0HQ+LJ8Cw=
Received: from DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) by DBXPR07MB464.eurprd07.prod.outlook.com (10.141.231.152) with Microsoft SMTP Server (TLS) id 15.1.492.11; Wed, 18 May 2016 13:56:39 +0000
Received: from DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) by DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) with mapi id 15.01.0497.019; Wed, 18 May 2016 13:56:39 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: =?Windows-1252?Q?Ole_Tr=F8an?= <otroan@employees.org>
Subject: Re: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Topic: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Index: AQHRsPZkK/0fZSIioUSqb/GzSJ5nE5++uDeA
Date: Wed, 18 May 2016 13:56:39 +0000
Message-ID: <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>
In-Reply-To: <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3124)
authentication-results: employees.org; dkim=none (message not signed) header.d=none;employees.org; dmarc=none action=none header.from=jisc.ac.uk;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [194.82.140.195]
x-ms-office365-filtering-correlation-id: 72e816bf-287f-4e10-a16f-08d37f243c0d
x-microsoft-exchange-diagnostics: 1; DBXPR07MB464; 5:X5qKRZ+ypmY64XYW3qKg96tZ/9IUTNqMWdaMNRTrijWLIzpsD0YQvtkFM/j2nQpJS4dBGRrjG0vSD7PyLRTAVgyQn76WkMENh09NdEEYSoWOwHx4WW0KsYsEDgDdAsZYeU55r54p5werATfXKpfJzA==; 24:1geiQHVKnw96j5YcumggJsv+tKrgcVJntJMkhmsFh5FAKxCer8SPG/lqg2jNMNf5KvJWn4C4DhNAjVbWA16gXhyErE0RMJhdlakDN0vVS9E=; 7:kxIhJphnh6DQw6zq8jvE6nlNttDPUSYNQFEjFS26r//PFYs4WvtZ9cXO+0gGyR1Y1CVPt9G/h4D71VoLi7kxmwbqu0L2xINXXFKPpvritY+2gI4HMqAusDfbrUJo0dwTB8+jI/QL3h69WRs4+EcSVN5CRzjU1qkTxSUuPJqUKT+ZnTkTc2q+vaZrDVbvrvU3; 20:aDOv9PCvoQPI5vNlXQouamfZNmJUs/UoarZfj6smU4JzorLaeiY7aMiCPEOv7UX6/N7Ghq3juKycAbgimtHlqrJHg1UddNAJWmkcz8lJXhfMrURbrQ5VWAaxUQKAn9Z9FkO2msIdi9+Fte/8X8/4ZhaEdW0in0JU3VS7ZunOIbw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB464;
x-microsoft-antispam-prvs: <DBXPR07MB4643F50B1A1C2D8C5CEBC76D6490@DBXPR07MB464.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415293)(102615271)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DBXPR07MB464; BCL:0; PCL:0; RULEID:; SRVR:DBXPR07MB464; 
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51694002)(252514010)(24454002)(92566002)(4326007)(2906002)(33656002)(50226002)(77096005)(86362001)(81166006)(83716003)(76176999)(5002640100001)(15975445007)(87936001)(8676002)(36756003)(5004730100002)(66066001)(110136002)(8936002)(106116001)(57306001)(6116002)(2950100001)(2900100001)(10400500002)(586003)(5008740100001)(1220700001)(74482002)(102836003)(3280700002)(11100500001)(19580405001)(19580395003)(189998001)(122556002)(50986999)(99936001)(3660700001)(82746002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DBXPR07MB464; H:DBXPR07MB462.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_CC43FE0B-9DB7-4A65-8BD4-72033D6640E8"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 13:56:39.0885 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB464
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dPPf63Qtn53ptHmYPdUt5tJ4TA4>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 13:56:52 -0000

--Apple-Mail=_CC43FE0B-9DB7-4A65-8BD4-72033D6640E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>=20
> This email from Fernando provides a good introduction to an =
outstanding question from Buenos Aires.
>=20
> The current plan is to take RFC4941 to Internet Standard unchanged.
> A question was raised if 4941 requires public addresses or not, and if =
we have to update 4941 text, or if we can live with the current text, =
and still allow for interfaces with only temporary addresses.
>=20
> Opinions?

The intro to RFC 4941 section 3 says that RFC 4941 would not affect =
normal SLAAC operation, so you would expect a public address to be =
created by SLAAC. Further, section 3.3 says quite explicitly that a =
public address MUST be generated as per RFC 4862, and that a temporary =
address SHOULD also be generated.

So if we want to support having ONLY temporary addresses, I think the =
document will need updating. At the very best, it would be confusing to =
leave it as is if we want interfaces with only temporary addresses.

Personally, I would support such a change. When I last looked at the =
activity log for my desktop over a one month period, it showed global =
IPv4, LL IPv6, and many temporary IPv6 addresses in use, but there was =
no activity to/from the desktop=92s public IPv6 address.  That=92s =
probably not uncommon in an enterprise environment where RFC 4941 is =
enabled. So why require that such an address be generated?

Tim

> Best regards,
> Ole
>=20
>> On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar> wrote:
>>=20
>> Lorenzo (and wg),
>>=20
>> The two issues raised by Lorenzo regarding default-iids boil down to:
>>=20
>> 1) The ability to embed MAC addresses in the IID
>>=20
>> 2) The requirement to have stable addresses
>>=20
>>=20
>> This document does ban "1)" as the default algorithm for generating
>> IIDs, for the reasons discussed in RFC7721 and
>> draft-gont-predictable-numeric-ids. We have a very long history of
>> improper numeric IDs, and I guess that, regarding this one, we simply
>> disagree with Lorenzo.
>>=20
>>=20
>> Regarding "2)", this document does not specify any new requirements =
on
>> the topic. Essentially, nodes are implied to configure a stable
>> addresses as a result of SLAAC&traditional link-layer address
>> properties, and more explicitly by this text in RFC4941:
>>=20
>> * Section 3, bullet #1:
>>  2.  Create additional addresses based on a random interface
>>      identifier for the purpose of initiating outgoing sessions.
>>=20
>> * Section 3.3, bullet #1:
>>  1.  Process the Prefix Information Option as defined in [ADDRCONF],
>>      either creating a new public address or adjusting the lifetimes
>>      of existing addresses, both public and temporary.
>>=20
>> * Section 3.3, bullet #3:
>>  3.  When a new public address is created as described in [ADDRCONF],
>>      the node SHOULD also create a new temporary address.
>>=20
>> * Section 3.6, for instance, says (even recommending that temp addrs
>> default to "off"):
>>  The use of temporary addresses may cause unexpected difficulties =
with
>>  some applications.  As described below, some servers refuse to =
accept
>>  communications from clients for which they cannot map the IP address
>>  into a DNS name.  In addition, some applications may not behave
>>  robustly if temporary addresses are used and an address expires
>>  before the application has terminated, or if it opens multiple
>>  sessions, but expects them to all use the same addresses.
>>  Consequently, the use of temporary addresses SHOULD be disabled by
>>  default in order to minimize potential disruptions.
>>=20
>>=20
>>=20
>> Our document simply requires implementations that their
>> stable addresses are RFC7721-friendly. But if anything, the =
requirement
>> of whether to have a stable address or not is not something =
introduced
>> by our document.
>>=20
>> As a co-author of draft-ietf-6man-default-iids, I just wanted to =
check
>> that we're on the same page, because I have the feeling that the =
above
>> keeps getting misinterpreted.
>>=20
>> I believe all of the co-authors of default-iids agree and understand
>> that there can be scenarios where you may want to do
>> temporary-addresses-only. However, that is orthogonal to this =
particular
>> document (default-iids), and would probably require an update to
>> RFC4941, such that temporary addresses can be employed as a =
replacement
>> of stable addresses, rather than as something that you do "in =
addition
>> to" them.
>>=20
>> This document is about how to do stable addresses in a more
>> RFC7721-friendly way than we currently do.
>>=20
>> Thanks!
>>=20
>> Best regards,
>> --
>> Fernando Gont
>> e-mail: fernando@gont.com.ar || fgont@si6networks.com
>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>=20
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_CC43FE0B-9DB7-4A65-8BD4-72033D6640E8
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

iQIcBAEBCgAGBQJXPHSWAAoJELg9LkJo0sOW3XQP/iB5w9cUK0gbPi6Loir6Fs6T
+ZdDceEqe23Sb+0IGok8RXzERPCGsb243SbVnbHgldNA1vrZTVvX2d/XqJWscgHP
cEV/ZHkbYz3fYsKX7k7mCEnyp2L04XT7Z8NKtQtVAI+/icqZwvRmqIAFEEnqvdsF
wKdFrjXQuR22u3NKWGRhGBl91AdkUrdDrdEPZQmlBoVN4BbvedThZrU2TbnUi0Dh
o8z2e9ODzMnQm20KAIgUb+9EbIygoxm9Z4ArdG1y5hAswDeVZToFNvfNzI/fFYPD
vMRZ1adezscG971n2T9m3DZ31NxfS9c42gR2Dh92EtxkpjI14JnjOypNF5/zaXia
+Q+PD8RRNwWLWKXYRnetfFigOBp4EKJ10Xkcl4FJKNBd/sL3JBRSCD5Yy+KQ0TiV
eXfIsJj4eMl9JVO8cUUXfIBQb0swQG754OjLhr2pA8Z70uxYoE/YuN6+V3Aq6WxM
XC+9ZuzTnc2sqj39dURtNPdnGp8tu+bUNhS5gTouaWJyt6xLpnJHkhWmSdOsyIaj
3SvZq/ubhdQ3Q7bsWspfHhrjF82nxBITAVH9smwmUo1i5bhXBBUpFrBTL81H/i5a
gEfiiggJh7650lT6VrdS9wcchVfkdgrcdW1jnSwuGVUC+zRTZSds23jd3WINLYy9
A07rB4mCfejhaRP5ZXM+
=jfKp
-----END PGP SIGNATURE-----

--Apple-Mail=_CC43FE0B-9DB7-4A65-8BD4-72033D6640E8--


From nobody Wed May 18 07:03:42 2016
Return-Path: <JUllrich@sba-research.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 135D612D167 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level: 
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, 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 cmZjqZVTksyM for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:03:37 -0700 (PDT)
Received: from mail.sba-research.org (mail.sba-research.org [188.21.236.108]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C7C212D1E9 for <6man@ietf.org>; Wed, 18 May 2016 07:03:34 -0700 (PDT)
Received: from SATVIEEX03.securityresearch.local (172.16.0.17) by SATVIEEX03.securityresearch.local (172.16.0.17) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 18 May 2016 16:03:31 +0200
Received: from SATVIEEX03.securityresearch.local ([fe80::e114:ce37:a118:bda4]) by SATVIEEX03.securityresearch.local ([fe80::e114:ce37:a118:bda4%12]) with mapi id 15.00.1044.021; Wed, 18 May 2016 16:03:31 +0200
From: Johanna Ullrich <JUllrich@sba-research.org>
To: Tim Chown <Tim.Chown@jisc.ac.uk>, =?Windows-1252?Q?Ole_Tr=F8an?= <otroan@employees.org>
Subject: AW: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Topic: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Index: AQHRsPZXUrfaXz/THkGEuvb2po7hz5++lr+AgAAh6wM=
Date: Wed, 18 May 2016 14:03:31 +0000
Message-ID: <1463580210719.65028@sba-research.org>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org>, <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk>
In-Reply-To: <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk>
Accept-Language: de-DE, de-AT, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.109.2]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZqAhPdabb0lMenKHR9aoby04XoM>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 14:03:41 -0000

=0A=
In case of an RFC 4941 update, I would further reconsider the algorithm for=
 temporary address generation.=0A=
=0A=
Concatenation of successive MD5 hashes as specified at the moment makes the=
 privacy extension vulnerable:=0A=
An adversary could synchronize to the history value, and predict all future=
 interface identifiers.=0A=
=0A=
=0A=
Best Regards,=0A=
Johanna=0A=
=0A=
=0A=
=0A=
DI Johanna Ullrich=0A=
Researcher=0A=
http://www.sba-research.org/=0A=
=0A=
Identifizierung gem=E4=DF =A7 14 UGB=0A=
 Firmenname: SBA Research gGmbH=0A=
 Firmensitz: Favoritenstra=DFe 16, 1040 Wien=0A=
 Firmenbuchnummer: 345659y=0A=
 Firmenbuchgericht: Handelsgericht Wien=0A=
 DVR-Nummer: 4012257=0A=
=0A=
=0A=
________________________________________=0A=
Von: ipv6 <ipv6-bounces@ietf.org> im Auftrag von Tim Chown <Tim.Chown@jisc.=
ac.uk>=0A=
Gesendet: Mittwoch, 18. Mai 2016 15:56=0A=
An: Ole Tr=F8an=0A=
Cc: 6man@ietf.org; Fernando Gont; draft-ietf-6man-default-iids@tools.ietf.o=
rg=0A=
Betreff: Re: RFC4941 text on requirement for public addresses (was: Re: def=
ault-iids and stable addresses)=0A=
=0A=
Hi,=0A=
=0A=
> On 18 May 2016, at 12:13, otroan@employees.org wrote:=0A=
>=0A=
> This email from Fernando provides a good introduction to an outstanding q=
uestion from Buenos Aires.=0A=
>=0A=
> The current plan is to take RFC4941 to Internet Standard unchanged.=0A=
> A question was raised if 4941 requires public addresses or not, and if we=
 have to update 4941 text, or if we can live with the current text, and sti=
ll allow for interfaces with only temporary addresses.=0A=
>=0A=
> Opinions?=0A=
=0A=
The intro to RFC 4941 section 3 says that RFC 4941 would not affect normal =
SLAAC operation, so you would expect a public address to be created by SLAA=
C. Further, section 3.3 says quite explicitly that a public address MUST be=
 generated as per RFC 4862, and that a temporary address SHOULD also be gen=
erated.=0A=
=0A=
So if we want to support having ONLY temporary addresses, I think the docum=
ent will need updating. At the very best, it would be confusing to leave it=
 as is if we want interfaces with only temporary addresses.=0A=
=0A=
Personally, I would support such a change. When I last looked at the activi=
ty log for my desktop over a one month period, it showed global IPv4, LL IP=
v6, and many temporary IPv6 addresses in use, but there was no activity to/=
from the desktop=92s public IPv6 address.  That=92s probably not uncommon i=
n an enterprise environment where RFC 4941 is enabled. So why require that =
such an address be generated?=0A=
=0A=
Tim=0A=
=0A=
> Best regards,=0A=
> Ole=0A=
>=0A=
>> On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar> wrote:=0A=
>>=0A=
>> Lorenzo (and wg),=0A=
>>=0A=
>> The two issues raised by Lorenzo regarding default-iids boil down to:=0A=
>>=0A=
>> 1) The ability to embed MAC addresses in the IID=0A=
>>=0A=
>> 2) The requirement to have stable addresses=0A=
>>=0A=
>>=0A=
>> This document does ban "1)" as the default algorithm for generating=0A=
>> IIDs, for the reasons discussed in RFC7721 and=0A=
>> draft-gont-predictable-numeric-ids. We have a very long history of=0A=
>> improper numeric IDs, and I guess that, regarding this one, we simply=0A=
>> disagree with Lorenzo.=0A=
>>=0A=
>>=0A=
>> Regarding "2)", this document does not specify any new requirements on=
=0A=
>> the topic. Essentially, nodes are implied to configure a stable=0A=
>> addresses as a result of SLAAC&traditional link-layer address=0A=
>> properties, and more explicitly by this text in RFC4941:=0A=
>>=0A=
>> * Section 3, bullet #1:=0A=
>>  2.  Create additional addresses based on a random interface=0A=
>>      identifier for the purpose of initiating outgoing sessions.=0A=
>>=0A=
>> * Section 3.3, bullet #1:=0A=
>>  1.  Process the Prefix Information Option as defined in [ADDRCONF],=0A=
>>      either creating a new public address or adjusting the lifetimes=0A=
>>      of existing addresses, both public and temporary.=0A=
>>=0A=
>> * Section 3.3, bullet #3:=0A=
>>  3.  When a new public address is created as described in [ADDRCONF],=0A=
>>      the node SHOULD also create a new temporary address.=0A=
>>=0A=
>> * Section 3.6, for instance, says (even recommending that temp addrs=0A=
>> default to "off"):=0A=
>>  The use of temporary addresses may cause unexpected difficulties with=
=0A=
>>  some applications.  As described below, some servers refuse to accept=
=0A=
>>  communications from clients for which they cannot map the IP address=0A=
>>  into a DNS name.  In addition, some applications may not behave=0A=
>>  robustly if temporary addresses are used and an address expires=0A=
>>  before the application has terminated, or if it opens multiple=0A=
>>  sessions, but expects them to all use the same addresses.=0A=
>>  Consequently, the use of temporary addresses SHOULD be disabled by=0A=
>>  default in order to minimize potential disruptions.=0A=
>>=0A=
>>=0A=
>>=0A=
>> Our document simply requires implementations that their=0A=
>> stable addresses are RFC7721-friendly. But if anything, the requirement=
=0A=
>> of whether to have a stable address or not is not something introduced=
=0A=
>> by our document.=0A=
>>=0A=
>> As a co-author of draft-ietf-6man-default-iids, I just wanted to check=
=0A=
>> that we're on the same page, because I have the feeling that the above=
=0A=
>> keeps getting misinterpreted.=0A=
>>=0A=
>> I believe all of the co-authors of default-iids agree and understand=0A=
>> that there can be scenarios where you may want to do=0A=
>> temporary-addresses-only. However, that is orthogonal to this particular=
=0A=
>> document (default-iids), and would probably require an update to=0A=
>> RFC4941, such that temporary addresses can be employed as a replacement=
=0A=
>> of stable addresses, rather than as something that you do "in addition=
=0A=
>> to" them.=0A=
>>=0A=
>> This document is about how to do stable addresses in a more=0A=
>> RFC7721-friendly way than we currently do.=0A=
>>=0A=
>> Thanks!=0A=
>>=0A=
>> Best regards,=0A=
>> --=0A=
>> Fernando Gont=0A=
>> e-mail: fernando@gont.com.ar || fgont@si6networks.com=0A=
>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1=0A=
>>=0A=
>>=0A=
>>=0A=
>> --------------------------------------------------------------------=0A=
>> IETF IPv6 working group mailing list=0A=
>> ipv6@ietf.org=0A=
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A=
>> --------------------------------------------------------------------=0A=
>=0A=
> --------------------------------------------------------------------=0A=
> IETF IPv6 working group mailing list=0A=
> ipv6@ietf.org=0A=
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A=
> --------------------------------------------------------------------=0A=
=0A=


From nobody Wed May 18 07:16:03 2016
Return-Path: <alexandre.petrescu@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 A14AB12D4FD for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 BYdhx3RmWgIL for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:15:54 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FC0E12D4FB for <ipv6@ietf.org>; Wed, 18 May 2016 07:15:54 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4IEFqkJ007463 for <ipv6@ietf.org>; Wed, 18 May 2016 16:15:52 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BEB12206051 for <ipv6@ietf.org>; Wed, 18 May 2016 16:15:53 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id B508620604D for <ipv6@ietf.org>; Wed, 18 May 2016 16:15:53 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4IEFqFM003527 for <ipv6@ietf.org>; Wed, 18 May 2016 16:15:52 +0200
Subject: Re: RFC4941 text on requirement for public addresses
To: ipv6@ietf.org
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com>
Date: Wed, 18 May 2016 16:15:52 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FWfdlCQ5G94NaX6NP6770C5AfwY>
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, 18 May 2016 14:15:58 -0000

Le 18/05/2016 à 15:56, Tim Chown a écrit :
> Hi,
>
>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>
>> This email from Fernando provides a good introduction to an
>> outstanding question from Buenos Aires.
>>
>> The current plan is to take RFC4941 to Internet Standard
>> unchanged. A question was raised if 4941 requires public addresses
>> or not, and if we have to update 4941 text, or if we can live with
>> the current text, and still allow for interfaces with only
>> temporary addresses.
>>
>> Opinions?
>
> The intro to RFC 4941 section 3 says that RFC 4941 would not affect
> normal SLAAC operation, so you would expect a public address to be
> created by SLAAC. Further, section 3.3 says quite explicitly that a
> public address MUST be generated as per RFC 4862, and that a
> temporary address SHOULD also be generated.
>
> So if we want to support having ONLY temporary addresses, I think the
> document will need updating. At the very best, it would be confusing
> to leave it as is if we want interfaces with only temporary
> addresses.
>
> Personally, I would support such a change. When I last looked at the
> activity log for my desktop over a one month period, it showed global
> IPv4, LL IPv6, and many temporary IPv6 addresses in use, but there
> was no activity to/from the desktop’s public IPv6 address.  That’s
> probably not uncommon in an enterprise environment where RFC 4941 is
> enabled. So why require that such an address be generated?

If there's no fixed address then there's no DNS name for that machine.

Updating DNS for each temporary IP address may not be that easy.

Alex

>
> Tim
>
>> Best regards, Ole
>>
>>> On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar>
>>> wrote:
>>>
>>> Lorenzo (and wg),
>>>
>>> The two issues raised by Lorenzo regarding default-iids boil down
>>> to:
>>>
>>> 1) The ability to embed MAC addresses in the IID
>>>
>>> 2) The requirement to have stable addresses
>>>
>>>
>>> This document does ban "1)" as the default algorithm for
>>> generating IIDs, for the reasons discussed in RFC7721 and
>>> draft-gont-predictable-numeric-ids. We have a very long history
>>> of improper numeric IDs, and I guess that, regarding this one, we
>>> simply disagree with Lorenzo.
>>>
>>>
>>> Regarding "2)", this document does not specify any new
>>> requirements on the topic. Essentially, nodes are implied to
>>> configure a stable addresses as a result of SLAAC&traditional
>>> link-layer address properties, and more explicitly by this text
>>> in RFC4941:
>>>
>>> * Section 3, bullet #1: 2.  Create additional addresses based on
>>> a random interface identifier for the purpose of initiating
>>> outgoing sessions.
>>>
>>> * Section 3.3, bullet #1: 1.  Process the Prefix Information
>>> Option as defined in [ADDRCONF], either creating a new public
>>> address or adjusting the lifetimes of existing addresses, both
>>> public and temporary.
>>>
>>> * Section 3.3, bullet #3: 3.  When a new public address is
>>> created as described in [ADDRCONF], the node SHOULD also create a
>>> new temporary address.
>>>
>>> * Section 3.6, for instance, says (even recommending that temp
>>> addrs default to "off"): The use of temporary addresses may cause
>>> unexpected difficulties with some applications.  As described
>>> below, some servers refuse to accept communications from clients
>>> for which they cannot map the IP address into a DNS name.  In
>>> addition, some applications may not behave robustly if temporary
>>> addresses are used and an address expires before the application
>>> has terminated, or if it opens multiple sessions, but expects
>>> them to all use the same addresses. Consequently, the use of
>>> temporary addresses SHOULD be disabled by default in order to
>>> minimize potential disruptions.
>>>
>>>
>>>
>>> Our document simply requires implementations that their stable
>>> addresses are RFC7721-friendly. But if anything, the requirement
>>> of whether to have a stable address or not is not something
>>> introduced by our document.
>>>
>>> As a co-author of draft-ietf-6man-default-iids, I just wanted to
>>> check that we're on the same page, because I have the feeling
>>> that the above keeps getting misinterpreted.
>>>
>>> I believe all of the co-authors of default-iids agree and
>>> understand that there can be scenarios where you may want to do
>>> temporary-addresses-only. However, that is orthogonal to this
>>> particular document (default-iids), and would probably require an
>>> update to RFC4941, such that temporary addresses can be employed
>>> as a replacement of stable addresses, rather than as something
>>> that you do "in addition to" them.
>>>
>>> This document is about how to do stable addresses in a more
>>> RFC7721-friendly way than we currently do.
>>>
>>> Thanks!
>>>
>>> Best regards, -- Fernando Gont e-mail: fernando@gont.com.ar ||
>>> fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9
>>> 3945 96EE A9EF D076 FFF1
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>>
>>>
IETF IPv6 working group mailing list
>>> ipv6@ietf.org Administrative Requests:
>>> https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>
>>
>>>
--------------------------------------------------------------------
>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Wed May 18 07:23:49 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 2E8FA12D52B for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:23:22 -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 vTnJAyyBK1j8 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:23:10 -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 570C112D51B for <ipv6@ietf.org>; Wed, 18 May 2016 07:23:10 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0240.outbound.protection.outlook.com [213.199.154.240]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-44-b9UuhxY3TLC8L41DClB6fg-1; Wed, 18 May 2016 15:23:03 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9BZ6z6gKNiWGc07DxClCFUkAXi2PtYRVyPBCdukU1LA=; b=NWxKXTcUYIHySnlEOBSF66HNVRLZPnpE8D+KFyDyvwusu1ti1/o+Nsdtin2+drLqHmlEPVWuatdxDhxE5aJzviva+Vm18X01z4U1UjWIfoZuuXWxDdeFXNUCTxDFYqv61J8032VSm/lO+Sc+qSoRznxnUYYD4OQZD6sgkrk3v8U=
Received: from DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) by DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) with Microsoft SMTP Server (TLS) id 15.1.497.12; Wed, 18 May 2016 14:23:02 +0000
Received: from DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) by DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) with mapi id 15.01.0497.019; Wed, 18 May 2016 14:23:02 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: RFC4941 text on requirement for public addresses
Thread-Topic: RFC4941 text on requirement for public addresses
Thread-Index: AQHRsQ/upavhfDHCwU+NjueDdmm28J++v3CA
Date: Wed, 18 May 2016 14:23:02 +0000
Message-ID: <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com>
In-Reply-To: <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@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: [194.82.140.195]
x-ms-office365-filtering-correlation-id: 55b2d42c-c0f7-4e5b-8920-08d37f27eb93
x-microsoft-exchange-diagnostics: 1; DBXPR07MB462; 5:36uPaXCthzx9FBc7d4jIM2LqBzhwwb5yx8T/jNCKxhjyEaWecUHCfyYRzcsxUDozlzEwbuAkP3BcW8uMKxtenWPY0Ht+KwOs9mkvBvbCqAzlty5hSr+0SENSufdHsi9R4YOfDWGhR7+6gqeoCFBMDQ==; 24:rwYWvrvpDB0pZS7Qo20lYvxAYebXDUQtex/EbFq/y/Oi/OboEaccNVIxRKq5ZrTgSY0NllXo50zDMaf/eWgetBRtoyoFkNnc729PVid5TYk=; 7:fbOSzOtfmtKZI9/ar++H/Sdp6zbkD2mp5EtSJdpnPqOyFZGhKfYBNNQDsrGwnckOfofthfaLPmbHu3xkVtIfdrtwGrJZlE4l/xH3Ievmiq+XCRcZJpoi8WvCpPYE98GqDGRREXELmZKkyzKS452y0t9UrDOP37wbjPJ7/HXhhmXjBArg9VAsTLQYiqOtS6yn; 20:ny91KpyQt9Lekb4WQpi2Ulqe/n9P0aNSgR1cTBQ9sLHoESmD+HKJOsjCoZAF5RtX/yx/Y6LRuJJwnxIEcDA44cOrn4xOe8AmwdYtN/r4GV/e03HxSYZ5KYTNNfXkgUzbkt+bOnHsQf4akHej8m5Z/klvm6vA+gcyW0WEhp1cTHQ=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB462;
x-microsoft-antispam-prvs: <DBXPR07MB46230574428E1735206B535D6490@DBXPR07MB462.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DBXPR07MB462; BCL:0; PCL:0; RULEID:; SRVR:DBXPR07MB462; 
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(51694002)(24454002)(252514010)(74482002)(33656002)(10400500002)(76176999)(50986999)(110136002)(83716003)(66066001)(86362001)(1220700001)(3660700001)(3280700002)(50226002)(8676002)(2906002)(87936001)(4326007)(36756003)(102836003)(6116002)(5008740100001)(586003)(57306001)(82746002)(2900100001)(92566002)(5004730100002)(11100500001)(93886004)(81166006)(8936002)(122556002)(19580405001)(106116001)(19580395003)(189998001)(15975445007)(2950100001)(77096005)(5002640100001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DBXPR07MB462; H:DBXPR07MB462.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-ID: <963C9F93E6816149990B6D96655DDC29@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 14:23:02.0419 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB462
X-MC-Unique: b9UuhxY3TLC8L41DClB6fg-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HUe1kgBJU1RR2vPGsfHEezS89HE>
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: Wed, 18 May 2016 14:23:22 -0000

> On 18 May 2016, at 15:15, Alexandre Petrescu <alexandre.petrescu@gmail.co=
m> wrote:
>=20
> Le 18/05/2016 =E0 15:56, Tim Chown a =E9crit :
>> Hi,
>>=20
>>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>>=20
>>> This email from Fernando provides a good introduction to an
>>> outstanding question from Buenos Aires.
>>>=20
>>> The current plan is to take RFC4941 to Internet Standard
>>> unchanged. A question was raised if 4941 requires public addresses
>>> or not, and if we have to update 4941 text, or if we can live with
>>> the current text, and still allow for interfaces with only
>>> temporary addresses.
>>>=20
>>> Opinions?
>>=20
>> The intro to RFC 4941 section 3 says that RFC 4941 would not affect
>> normal SLAAC operation, so you would expect a public address to be
>> created by SLAAC. Further, section 3.3 says quite explicitly that a
>> public address MUST be generated as per RFC 4862, and that a
>> temporary address SHOULD also be generated.
>>=20
>> So if we want to support having ONLY temporary addresses, I think the
>> document will need updating. At the very best, it would be confusing
>> to leave it as is if we want interfaces with only temporary
>> addresses.
>>=20
>> Personally, I would support such a change. When I last looked at the
>> activity log for my desktop over a one month period, it showed global
>> IPv4, LL IPv6, and many temporary IPv6 addresses in use, but there
>> was no activity to/from the desktop=92s public IPv6 address.  That=92s
>> probably not uncommon in an enterprise environment where RFC 4941 is
>> enabled. So why require that such an address be generated?
>=20
> If there's no fixed address then there's no DNS name for that machine.
>=20
> Updating DNS for each temporary IP address may not be that easy.

But that=92s not necessarily needed. Was certainly fine without it in the c=
ampus environment I was in, where all comms initiated outbound were from pr=
ivacy addresses with no associated DNS info.

Tim

> Alex
>=20
>>=20
>> Tim
>>=20
>>> Best regards, Ole
>>>=20
>>>> On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar>
>>>> wrote:
>>>>=20
>>>> Lorenzo (and wg),
>>>>=20
>>>> The two issues raised by Lorenzo regarding default-iids boil down
>>>> to:
>>>>=20
>>>> 1) The ability to embed MAC addresses in the IID
>>>>=20
>>>> 2) The requirement to have stable addresses
>>>>=20
>>>>=20
>>>> This document does ban "1)" as the default algorithm for
>>>> generating IIDs, for the reasons discussed in RFC7721 and
>>>> draft-gont-predictable-numeric-ids. We have a very long history
>>>> of improper numeric IDs, and I guess that, regarding this one, we
>>>> simply disagree with Lorenzo.
>>>>=20
>>>>=20
>>>> Regarding "2)", this document does not specify any new
>>>> requirements on the topic. Essentially, nodes are implied to
>>>> configure a stable addresses as a result of SLAAC&traditional
>>>> link-layer address properties, and more explicitly by this text
>>>> in RFC4941:
>>>>=20
>>>> * Section 3, bullet #1: 2.  Create additional addresses based on
>>>> a random interface identifier for the purpose of initiating
>>>> outgoing sessions.
>>>>=20
>>>> * Section 3.3, bullet #1: 1.  Process the Prefix Information
>>>> Option as defined in [ADDRCONF], either creating a new public
>>>> address or adjusting the lifetimes of existing addresses, both
>>>> public and temporary.
>>>>=20
>>>> * Section 3.3, bullet #3: 3.  When a new public address is
>>>> created as described in [ADDRCONF], the node SHOULD also create a
>>>> new temporary address.
>>>>=20
>>>> * Section 3.6, for instance, says (even recommending that temp
>>>> addrs default to "off"): The use of temporary addresses may cause
>>>> unexpected difficulties with some applications.  As described
>>>> below, some servers refuse to accept communications from clients
>>>> for which they cannot map the IP address into a DNS name.  In
>>>> addition, some applications may not behave robustly if temporary
>>>> addresses are used and an address expires before the application
>>>> has terminated, or if it opens multiple sessions, but expects
>>>> them to all use the same addresses. Consequently, the use of
>>>> temporary addresses SHOULD be disabled by default in order to
>>>> minimize potential disruptions.
>>>>=20
>>>>=20
>>>>=20
>>>> Our document simply requires implementations that their stable
>>>> addresses are RFC7721-friendly. But if anything, the requirement
>>>> of whether to have a stable address or not is not something
>>>> introduced by our document.
>>>>=20
>>>> As a co-author of draft-ietf-6man-default-iids, I just wanted to
>>>> check that we're on the same page, because I have the feeling
>>>> that the above keeps getting misinterpreted.
>>>>=20
>>>> I believe all of the co-authors of default-iids agree and
>>>> understand that there can be scenarios where you may want to do
>>>> temporary-addresses-only. However, that is orthogonal to this
>>>> particular document (default-iids), and would probably require an
>>>> update to RFC4941, such that temporary addresses can be employed
>>>> as a replacement of stable addresses, rather than as something
>>>> that you do "in addition to" them.
>>>>=20
>>>> This document is about how to do stable addresses in a more
>>>> RFC7721-friendly way than we currently do.
>>>>=20
>>>> Thanks!
>>>>=20
>>>> Best regards, -- Fernando Gont e-mail: fernando@gont.com.ar ||
>>>> fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9
>>>> 3945 96EE A9EF D076 FFF1
>>>>=20
>>>>=20
>>>>=20
>>>> --------------------------------------------------------------------
>>>>=20
>>>>=20
> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org Administrative Requests:
>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>=20
>>>=20
>>>>=20
> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>>>=20
>>=20
>>=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
> --------------------------------------------------------------------


From nobody Wed May 18 07:38:43 2016
Return-Path: <alexandre.petrescu@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 6811F12D516 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 1EJ8LIdCKzFr for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:38:40 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFA0212D530 for <ipv6@ietf.org>; Wed, 18 May 2016 07:38:39 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4IEcb6T001262; Wed, 18 May 2016 16:38:37 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 55DE0205F06; Wed, 18 May 2016 16:38:38 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 48B4C2060BD; Wed, 18 May 2016 16:38:38 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4IEcaZj018846; Wed, 18 May 2016 16:38:36 +0200
Subject: Re: RFC4941 text on requirement for public addresses
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <f185260a-6041-607a-bc9c-fcacdd59ab78@gmail.com>
Date: Wed, 18 May 2016 16:38:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/H-QGg2f5o09yQ1Zj0fg9gVJPAQw>
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: Wed, 18 May 2016 14:38:42 -0000

Le 18/05/2016 à 16:23, Tim Chown a écrit :
>> On 18 May 2016, at 15:15, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com> wrote:
>>
>> Le 18/05/2016 à 15:56, Tim Chown a écrit :
>>> Hi,
>>>
>>>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>>>
>>>> This email from Fernando provides a good introduction to an
>>>> outstanding question from Buenos Aires.
>>>>
>>>> The current plan is to take RFC4941 to Internet Standard
>>>> unchanged. A question was raised if 4941 requires public
>>>> addresses or not, and if we have to update 4941 text, or if we
>>>> can live with the current text, and still allow for interfaces
>>>> with only temporary addresses.
>>>>
>>>> Opinions?
>>>
>>> The intro to RFC 4941 section 3 says that RFC 4941 would not
>>> affect normal SLAAC operation, so you would expect a public
>>> address to be created by SLAAC. Further, section 3.3 says quite
>>> explicitly that a public address MUST be generated as per RFC
>>> 4862, and that a temporary address SHOULD also be generated.
>>>
>>> So if we want to support having ONLY temporary addresses, I
>>> think the document will need updating. At the very best, it would
>>> be confusing to leave it as is if we want interfaces with only
>>> temporary addresses.
>>>
>>> Personally, I would support such a change. When I last looked at
>>> the activity log for my desktop over a one month period, it
>>> showed global IPv4, LL IPv6, and many temporary IPv6 addresses
>>> in use, but there was no activity to/from the desktop’s public
>>> IPv6 address.  That’s probably not uncommon in an enterprise
>>> environment where RFC 4941 is enabled. So why require that such
>>> an address be generated?
>>
>> If there's no fixed address then there's no DNS name for that
>> machine.
>>
>> Updating DNS for each temporary IP address may not be that easy.
>
> But that’s not necessarily needed. Was certainly fine without it in
> the campus environment I was in, where all comms initiated outbound
> were from privacy addresses with no associated DNS info.

Hmm... I guess the machine was doing the important things on IPv4 (not
IPv6)(?)

A machine w/o a DNS name is segregated, half-connected to the Internet.

It's a machine that can live with NATs.

It's a machine that can't do video-over-IP live streaming for too long.

It's a machine that can't be an ADSL box which has same IP address since
many years now.

Alex

>
> Tim
>
>> Alex
>>
>>>
>>> Tim
>>>
>>>> Best regards, Ole
>>>>
>>>>> On 17 May 2016, at 20:15, Fernando Gont
>>>>> <fernando@gont.com.ar> wrote:
>>>>>
>>>>> Lorenzo (and wg),
>>>>>
>>>>> The two issues raised by Lorenzo regarding default-iids boil
>>>>> down to:
>>>>>
>>>>> 1) The ability to embed MAC addresses in the IID
>>>>>
>>>>> 2) The requirement to have stable addresses
>>>>>
>>>>>
>>>>> This document does ban "1)" as the default algorithm for
>>>>> generating IIDs, for the reasons discussed in RFC7721 and
>>>>> draft-gont-predictable-numeric-ids. We have a very long
>>>>> history of improper numeric IDs, and I guess that, regarding
>>>>> this one, we simply disagree with Lorenzo.
>>>>>
>>>>>
>>>>> Regarding "2)", this document does not specify any new
>>>>> requirements on the topic. Essentially, nodes are implied to
>>>>>  configure a stable addresses as a result of
>>>>> SLAAC&traditional link-layer address properties, and more
>>>>> explicitly by this text in RFC4941:
>>>>>
>>>>> * Section 3, bullet #1: 2.  Create additional addresses
>>>>> based on a random interface identifier for the purpose of
>>>>> initiating outgoing sessions.
>>>>>
>>>>> * Section 3.3, bullet #1: 1.  Process the Prefix Information
>>>>>  Option as defined in [ADDRCONF], either creating a new
>>>>> public address or adjusting the lifetimes of existing
>>>>> addresses, both public and temporary.
>>>>>
>>>>> * Section 3.3, bullet #3: 3.  When a new public address is
>>>>> created as described in [ADDRCONF], the node SHOULD also
>>>>> create a new temporary address.
>>>>>
>>>>> * Section 3.6, for instance, says (even recommending that
>>>>> temp addrs default to "off"): The use of temporary addresses
>>>>> may cause unexpected difficulties with some applications.
>>>>> As described below, some servers refuse to accept
>>>>> communications from clients for which they cannot map the IP
>>>>> address into a DNS name.  In addition, some applications may
>>>>> not behave robustly if temporary addresses are used and an
>>>>> address expires before the application has terminated, or if
>>>>> it opens multiple sessions, but expects them to all use the
>>>>> same addresses. Consequently, the use of temporary addresses
>>>>> SHOULD be disabled by default in order to minimize potential
>>>>> disruptions.
>>>>>
>>>>>
>>>>>
>>>>> Our document simply requires implementations that their
>>>>> stable addresses are RFC7721-friendly. But if anything, the
>>>>> requirement of whether to have a stable address or not is
>>>>> not something introduced by our document.
>>>>>
>>>>> As a co-author of draft-ietf-6man-default-iids, I just
>>>>> wanted to check that we're on the same page, because I have
>>>>> the feeling that the above keeps getting misinterpreted.
>>>>>
>>>>> I believe all of the co-authors of default-iids agree and
>>>>> understand that there can be scenarios where you may want to
>>>>> do temporary-addresses-only. However, that is orthogonal to
>>>>> this particular document (default-iids), and would probably
>>>>> require an update to RFC4941, such that temporary addresses
>>>>> can be employed as a replacement of stable addresses, rather
>>>>> than as something that you do "in addition to" them.
>>>>>
>>>>> This document is about how to do stable addresses in a more
>>>>> RFC7721-friendly way than we currently do.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Best regards, -- Fernando Gont e-mail: fernando@gont.com.ar
>>>>> || fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E
>>>>> 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------
>>>>>
>>>>>
>>
>>>>>
>>>>>
IETF IPv6 working group mailing list
>>>>> ipv6@ietf.org Administrative Requests:
>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>
>>>>
>>>>>
>>
>>>>>
>>>>>
--------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>> Administrative Requests:
>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>
>>>>
>>>
>>>
>>>
>>>>
>>>>
--------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
>>
>>
>>>
>>>
--------------------------------------------------------------------
>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
>>
>


From nobody Wed May 18 07:48: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 DDBB412D165 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:47:59 -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 2WRSSPpuTyna for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 07:47:58 -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 A2FF312D164 for <ipv6@ietf.org>; Wed, 18 May 2016 07:47:57 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0208.outbound.protection.outlook.com [213.199.154.208]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-38-tSvjyYwlTzuTbNwx0XUHlA-1; Wed, 18 May 2016 15:47:52 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=d3UcFib6+Xei4IvB4hzlDLEY6tC80eNZfIIjBe4+reA=; b=CdjrqVN+FzxrIik7+oHNTuyodnaS0mgCtQ3KxvBvRpjb5A6iNo8eqgj06DYMvKXJtNL06gGeaYfZwP8IDNwV8XvYxJ2zjo4GpvW/3raaktgg3ca9ikbiSCYu+6wzpePQ8klSWCdXd1uTygV5XqIoEtB67LDL5D7W0RetQ1m5Rvo=
Received: from DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) by DBXPR07MB461.eurprd07.prod.outlook.com (10.141.231.139) with Microsoft SMTP Server (TLS) id 15.1.497.12; Wed, 18 May 2016 14:47:51 +0000
Received: from DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) by DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) with mapi id 15.01.0497.019; Wed, 18 May 2016 14:47:51 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: RFC4941 text on requirement for public addresses
Thread-Topic: RFC4941 text on requirement for public addresses
Thread-Index: AQHRsQ/upavhfDHCwU+NjueDdmm28J++v3CAgAAEWwCAAAKUAA==
Date: Wed, 18 May 2016 14:47:51 +0000
Message-ID: <AA62DD34-9484-4AB2-81C5-DBC3263C040F@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk> <f185260a-6041-607a-bc9c-fcacdd59ab78@gmail.com>
In-Reply-To: <f185260a-6041-607a-bc9c-fcacdd59ab78@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: [194.82.140.195]
x-ms-office365-filtering-correlation-id: 0b29694a-4f02-42a2-a370-08d37f2b6330
x-microsoft-exchange-diagnostics: 1; DBXPR07MB461; 5:59sklBAXdrQJWjeNfmKgMCqLM/twBIh5U7RHoqKl1SDYgIF2XDlzbkS/0nMynZzNGRqA3VkID5ktjhKUfQcylsmUhXqPojgl4d34wDbSOUA/5zaa4wglfs4yFWNyjn6teYFOy+pZ2gZEfp80fVx/SQ==; 24:s4EIp3XcRC3xxI826D1qEN2JzD1JuQDSh/ZpDRhHvxByRSvW+Ku2cpxydRvdpU3T1k6KycHKP8p8XlAvXZcUMXUzt+mGaW5kAbY9wxelF5E=; 7:NkqPM7kSN3fIaMgbkxrTJWzCPoFOdniMJgZ8yiJ/tShdBB7T7m8j+bKVwAali04muVUwUkD6hs5LnkV871FqgUTp1x77lqo8F9ZTYrY8mwu+x4SvlUKhAeug/PtAYEH5DfZBUYUabXGjIVCINOathvG6w5EvaOP9sM4p1YTUG6i5HdUn/T3AlB+cauPZjIJ0; 20:n5mszKVWHFoziXMpEwoRI6I2PbBlbQlmythUk7MAosheX7lnejGrQ9Xaclo09v62P3T+WayRJvzAeCA3ub4Anb0G8dejlptbV0hOC2g9qvBVeGUJw94sE4MsjEPLzf1Yf39MuFRPGGUADon3O1pKMgVBLZx1R7j+9IIGl0/VoCc=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB461;
x-microsoft-antispam-prvs: <DBXPR07MB461AC9ED4C9DE1329B64AD1D6490@DBXPR07MB461.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:DBXPR07MB461; BCL:0; PCL:0; RULEID:; SRVR:DBXPR07MB461; 
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(252514010)(5008740100001)(102836003)(586003)(66066001)(2950100001)(2900100001)(87936001)(74482002)(6116002)(4326007)(82746002)(93886004)(92566002)(5002640100001)(81166006)(50986999)(76176999)(19580395003)(106116001)(1220700001)(19580405001)(10400500002)(2906002)(189998001)(8936002)(8676002)(110136002)(57306001)(3660700001)(77096005)(122556002)(50226002)(15975445007)(86362001)(3280700002)(5004730100002)(11100500001)(36756003)(33656002)(83716003)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DBXPR07MB461; H:DBXPR07MB462.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-ID: <C27F67082AA0964EBBC834AF29E8526F@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 14:47:51.2418 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB461
X-MC-Unique: tSvjyYwlTzuTbNwx0XUHlA-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1F57IqyE5oC-sGLKPx9VfAdXHCQ>
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: Wed, 18 May 2016 14:48:00 -0000

> On 18 May 2016, at 15:38, Alexandre Petrescu <alexandre.petrescu@gmail.co=
m> wrote:
>=20
> Le 18/05/2016 =E0 16:23, Tim Chown a =E9crit :
>>> On 18 May 2016, at 15:15, Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com> wrote:
>>>=20
>>> Le 18/05/2016 =E0 15:56, Tim Chown a =E9crit :
>>>> Hi,
>>>>=20
>>>>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>>>>=20
>>>>> This email from Fernando provides a good introduction to an
>>>>> outstanding question from Buenos Aires.
>>>>>=20
>>>>> The current plan is to take RFC4941 to Internet Standard
>>>>> unchanged. A question was raised if 4941 requires public
>>>>> addresses or not, and if we have to update 4941 text, or if we
>>>>> can live with the current text, and still allow for interfaces
>>>>> with only temporary addresses.
>>>>>=20
>>>>> Opinions?
>>>>=20
>>>> The intro to RFC 4941 section 3 says that RFC 4941 would not
>>>> affect normal SLAAC operation, so you would expect a public
>>>> address to be created by SLAAC. Further, section 3.3 says quite
>>>> explicitly that a public address MUST be generated as per RFC
>>>> 4862, and that a temporary address SHOULD also be generated.
>>>>=20
>>>> So if we want to support having ONLY temporary addresses, I
>>>> think the document will need updating. At the very best, it would
>>>> be confusing to leave it as is if we want interfaces with only
>>>> temporary addresses.
>>>>=20
>>>> Personally, I would support such a change. When I last looked at
>>>> the activity log for my desktop over a one month period, it
>>>> showed global IPv4, LL IPv6, and many temporary IPv6 addresses
>>>> in use, but there was no activity to/from the desktop=92s public
>>>> IPv6 address.  That=92s probably not uncommon in an enterprise
>>>> environment where RFC 4941 is enabled. So why require that such
>>>> an address be generated?
>>>=20
>>> If there's no fixed address then there's no DNS name for that
>>> machine.
>>>=20
>>> Updating DNS for each temporary IP address may not be that easy.
>>=20
>> But that=92s not necessarily needed. Was certainly fine without it in
>> the campus environment I was in, where all comms initiated outbound
>> were from privacy addresses with no associated DNS info.
>=20
> Hmm... I guess the machine was doing the important things on IPv4 (not
> IPv6)(?)
>=20
> A machine w/o a DNS name is segregated, half-connected to the Internet.
>=20
> It's a machine that can live with NATs.
>=20
> It's a machine that can't do video-over-IP live streaming for too long.
>=20
> It's a machine that can't be an ADSL box which has same IP address since
> many years now.

It=92s a desktop that I used in various forms for many years, with privacy =
addresses on, as my day to day desktop, accessing anything offering an AAAA=
 record by IPv6, and of course the rest by IPv4. I didn=92t see any evidenc=
e of anything broken as a result.  But then I had no services on the deskto=
p which needed to be accessed externally.

I=92m not saying hosts MUST have a public address to be able to have a temp=
orary address, but there=92s no reason in many scenarios why they can=92t j=
ust run with temporary addresses. I think the discussion here is about rela=
xing the MUST in 4941 about public addresses to a SHOULD (or MAY).

As an aside are you aware of applications that will try to use a public add=
ress in the presence of a temporary one? =20

RFC 6724 is quite explicit about this now:

Rule 7: Prefer temporary addresses.
   If SA is a temporary address and SB is a public address, then prefer
   SA.  Similarly, if SB is a temporary address and SA is a public
   address, then prefer SB.

Tim

> Alex
>=20
>>=20
>> Tim
>>=20
>>> Alex
>>>=20
>>>>=20
>>>> Tim
>>>>=20
>>>>> Best regards, Ole
>>>>>=20
>>>>>> On 17 May 2016, at 20:15, Fernando Gont
>>>>>> <fernando@gont.com.ar> wrote:
>>>>>>=20
>>>>>> Lorenzo (and wg),
>>>>>>=20
>>>>>> The two issues raised by Lorenzo regarding default-iids boil
>>>>>> down to:
>>>>>>=20
>>>>>> 1) The ability to embed MAC addresses in the IID
>>>>>>=20
>>>>>> 2) The requirement to have stable addresses
>>>>>>=20
>>>>>>=20
>>>>>> This document does ban "1)" as the default algorithm for
>>>>>> generating IIDs, for the reasons discussed in RFC7721 and
>>>>>> draft-gont-predictable-numeric-ids. We have a very long
>>>>>> history of improper numeric IDs, and I guess that, regarding
>>>>>> this one, we simply disagree with Lorenzo.
>>>>>>=20
>>>>>>=20
>>>>>> Regarding "2)", this document does not specify any new
>>>>>> requirements on the topic. Essentially, nodes are implied to
>>>>>> configure a stable addresses as a result of
>>>>>> SLAAC&traditional link-layer address properties, and more
>>>>>> explicitly by this text in RFC4941:
>>>>>>=20
>>>>>> * Section 3, bullet #1: 2.  Create additional addresses
>>>>>> based on a random interface identifier for the purpose of
>>>>>> initiating outgoing sessions.
>>>>>>=20
>>>>>> * Section 3.3, bullet #1: 1.  Process the Prefix Information
>>>>>> Option as defined in [ADDRCONF], either creating a new
>>>>>> public address or adjusting the lifetimes of existing
>>>>>> addresses, both public and temporary.
>>>>>>=20
>>>>>> * Section 3.3, bullet #3: 3.  When a new public address is
>>>>>> created as described in [ADDRCONF], the node SHOULD also
>>>>>> create a new temporary address.
>>>>>>=20
>>>>>> * Section 3.6, for instance, says (even recommending that
>>>>>> temp addrs default to "off"): The use of temporary addresses
>>>>>> may cause unexpected difficulties with some applications.
>>>>>> As described below, some servers refuse to accept
>>>>>> communications from clients for which they cannot map the IP
>>>>>> address into a DNS name.  In addition, some applications may
>>>>>> not behave robustly if temporary addresses are used and an
>>>>>> address expires before the application has terminated, or if
>>>>>> it opens multiple sessions, but expects them to all use the
>>>>>> same addresses. Consequently, the use of temporary addresses
>>>>>> SHOULD be disabled by default in order to minimize potential
>>>>>> disruptions.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> Our document simply requires implementations that their
>>>>>> stable addresses are RFC7721-friendly. But if anything, the
>>>>>> requirement of whether to have a stable address or not is
>>>>>> not something introduced by our document.
>>>>>>=20
>>>>>> As a co-author of draft-ietf-6man-default-iids, I just
>>>>>> wanted to check that we're on the same page, because I have
>>>>>> the feeling that the above keeps getting misinterpreted.
>>>>>>=20
>>>>>> I believe all of the co-authors of default-iids agree and
>>>>>> understand that there can be scenarios where you may want to
>>>>>> do temporary-addresses-only. However, that is orthogonal to
>>>>>> this particular document (default-iids), and would probably
>>>>>> require an update to RFC4941, such that temporary addresses
>>>>>> can be employed as a replacement of stable addresses, rather
>>>>>> than as something that you do "in addition to" them.
>>>>>>=20
>>>>>> This document is about how to do stable addresses in a more
>>>>>> RFC7721-friendly way than we currently do.
>>>>>>=20
>>>>>> Thanks!
>>>>>>=20
>>>>>> Best regards, -- Fernando Gont e-mail: fernando@gont.com.ar
>>>>>> || fgont@si6networks.com PGP Fingerprint: 7809 84F5 322E
>>>>>> 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> --------------------------------------------------------------------
>>>>>>=20
>>>>>>=20
>>>=20
>>>>>>=20
>>>>>>=20
> IETF IPv6 working group mailing list
>>>>>> ipv6@ietf.org Administrative Requests:
>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>>>>>=20
>>>>>=20
>>>>>>=20
>>>=20
>>>>>>=20
>>>>>>=20
> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>> Administrative Requests:
>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>=20
>>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>>=20
>>>>>=20
> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>>>>=20
>>>=20
>>>=20
>>>>=20
>>>>=20
> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------


From nobody Wed May 18 08:53:46 2016
Return-Path: <alexandre.petrescu@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 A9F9012D14E for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 08:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 1jb5zHkyNq98 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 08:53:41 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D59512D113 for <ipv6@ietf.org>; Wed, 18 May 2016 08:53:41 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4IFrdlo031021; Wed, 18 May 2016 17:53:39 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6C0262061D4; Wed, 18 May 2016 17:53:40 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5DE89205FCE; Wed, 18 May 2016 17:53:40 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4IFrcFq027506; Wed, 18 May 2016 17:53:38 +0200
Subject: Re: RFC4941 text on requirement for public addresses
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk> <f185260a-6041-607a-bc9c-fcacdd59ab78@gmail.com> <AA62DD34-9484-4AB2-81C5-DBC3263C040F@jisc.ac.uk>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e69d3c42-b496-4e06-76ae-4206b6a3f245@gmail.com>
Date: Wed, 18 May 2016 17:53:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <AA62DD34-9484-4AB2-81C5-DBC3263C040F@jisc.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Xmbm72QmZuZ8wYsHlQ8uadOV-Vw>
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: Wed, 18 May 2016 15:53:45 -0000

Le 18/05/2016 à 16:47, Tim Chown a écrit :
>> On 18 May 2016, at 15:38, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com> wrote:
>>
>> Le 18/05/2016 à 16:23, Tim Chown a écrit :
>>>> On 18 May 2016, at 15:15, Alexandre Petrescu
>>>> <alexandre.petrescu@gmail.com> wrote:
>>>>
>>>> Le 18/05/2016 à 15:56, Tim Chown a écrit :
>>>>> Hi,
>>>>>
>>>>>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>>>>>
>>>>>> This email from Fernando provides a good introduction to an
>>>>>> outstanding question from Buenos Aires.
>>>>>>
>>>>>> The current plan is to take RFC4941 to Internet Standard
>>>>>> unchanged. A question was raised if 4941 requires public
>>>>>> addresses or not, and if we have to update 4941 text, or
>>>>>> if we can live with the current text, and still allow for
>>>>>> interfaces with only temporary addresses.
>>>>>>
>>>>>> Opinions?
>>>>>
>>>>> The intro to RFC 4941 section 3 says that RFC 4941 would not
>>>>>  affect normal SLAAC operation, so you would expect a public
>>>>>  address to be created by SLAAC. Further, section 3.3 says
>>>>> quite explicitly that a public address MUST be generated as
>>>>> per RFC 4862, and that a temporary address SHOULD also be
>>>>> generated.
>>>>>
>>>>> So if we want to support having ONLY temporary addresses, I
>>>>> think the document will need updating. At the very best, it
>>>>> would be confusing to leave it as is if we want interfaces
>>>>> with only temporary addresses.
>>>>>
>>>>> Personally, I would support such a change. When I last
>>>>> looked at the activity log for my desktop over a one month
>>>>> period, it showed global IPv4, LL IPv6, and many temporary
>>>>> IPv6 addresses in use, but there was no activity to/from the
>>>>> desktop’s public IPv6 address.  That’s probably not uncommon
>>>>> in an enterprise environment where RFC 4941 is enabled. So
>>>>> why require that such an address be generated?
>>>>
>>>> If there's no fixed address then there's no DNS name for that
>>>> machine.
>>>>
>>>> Updating DNS for each temporary IP address may not be that
>>>> easy.
>>>
>>> But that’s not necessarily needed. Was certainly fine without it
>>> in the campus environment I was in, where all comms initiated
>>> outbound were from privacy addresses with no associated DNS
>>> info.
>>
>> Hmm... I guess the machine was doing the important things on IPv4
>> (not IPv6)(?)
>>
>> A machine w/o a DNS name is segregated, half-connected to the
>> Internet.
>>
>> It's a machine that can live with NATs.
>>
>> It's a machine that can't do video-over-IP live streaming for too
>> long.
>>
>> It's a machine that can't be an ADSL box which has same IP address
>> since many years now.
>
> It’s a desktop that I used in various forms for many years, with
> privacy addresses on, as my day to day desktop, accessing anything
> offering an AAAA record by IPv6, and of course the rest by IPv4. I
> didn’t see any evidence of anything broken as a result.  But then I
> had no services on the desktop which needed to be accessed
> externally.
>
> I’m not saying hosts MUST have a public address to be able to have a
> temporary address, but there’s no reason in many scenarios why they
> can’t just run with temporary addresses.

It very much depends on what the application is about.

An html browsing application will only need bursts of data exchange,
maybe each issued from distinct IP address, that may change every second.

But an ftp transferring an Ultra-HD Bluray on a cellular link may need
an address to last for many hours; please dont change that!

> I think the discussion here is about relaxing the MUST in 4941 about
> public addresses to a SHOULD (or MAY).

I am tempted to say "SHOULD" rather than "MAY".

But I also worry that the perspective may be wrong altogether.

Until now applications assumed the IP address is fixed stable.  Efforts 
like Mobile IP tried to accommodate network-induced variation in that IP 
address.

Now we say privacy is important, and so we want the address to change. 
This looks strange.

> As an aside are you aware of applications that will try to use a
> public address in the presence of a temporary one?

No, I am not aware.  I guess you are?

I think applications should not request some kind of IP address - that 
may be layer violation.  Applications should use application-layer 
identifiers.

Let me diverge on an argument - over in DMM WG, there is a developping 
perspective in which the application _does_ require the kind of IP 
address to use (stable, transient, etc.)  In this perspective the 
cellular network operator provides a Static IP address if the UE 
application requests one (e.g. "Static" in 
https://www.wireless.att.com/businesscenter/solutions/connectivity/ip-addressing.jsp) 


If the network offers a Static ("stable", "fixed") IP address to the 
node, will the node refuse it?  I doubt so, because the operator thinks 
(see that web page) that the end user is even ready to pay money for 
that Static address - i.e. there is value in a Static address.

So the perspective in this RFC4941 (there is no value in a static 
address) is contradictory to some operator's interests.

I think this contradiction stems from the ability of an application to 
require some particular kind network-layer identifier (IP address) - 
layer violation.

Privacy is an application matter: "this site uses cookies, do you agree"

Privacy is not an IP matter: unreadable address, return to sender

> RFC 6724 is quite explicit about this now:
>
> Rule 7: Prefer temporary addresses. If SA is a temporary address and
> SB is a public address, then prefer SA.  Similarly, if SB is a
> temporary address and SA is a public address, then prefer SB.

I take this as such out of the RFC.

There are multiple problems with 'public' and 'temporary' address terms 
in IPv6 addressing.

First, 'public' and 'temporary' addresses are not disjoint.  It's not 
like in IPv4, where a public IPv4 address is disjoint from private IPv4 
address (1.1.1.1 vs 192.168.1.1).  An IPv6 'temporary' address can very 
well be a GUA.

Second, there is a pitfall in assuming that a 'temporary' changing IPv6 
address offers more privacy than a 'public' stable IPv6 address.  True, 
it changes more often than a 'public', but the surveillant still sees it 
(even if it is not called 'public') and may adapt to change too - keep a 
list keyed on some other stable identifier; each identifier in 
draft-ietf-intarea-hostname-practice-02, plus the unique prefix 
delivered by cellular operator to user terminal, plus more in link-layer 
messaging.  We couldnt randomize each of these, right?

Alex


>
> Tim
>
>> Alex
>>
>>>
>>> Tim
>>>
>>>> Alex
>>>>
>>>>>
>>>>> Tim
>>>>>
>>>>>> Best regards, Ole
>>>>>>
>>>>>>> On 17 May 2016, at 20:15, Fernando Gont
>>>>>>> <fernando@gont.com.ar> wrote:
>>>>>>>
>>>>>>> Lorenzo (and wg),
>>>>>>>
>>>>>>> The two issues raised by Lorenzo regarding default-iids
>>>>>>> boil down to:
>>>>>>>
>>>>>>> 1) The ability to embed MAC addresses in the IID
>>>>>>>
>>>>>>> 2) The requirement to have stable addresses
>>>>>>>
>>>>>>>
>>>>>>> This document does ban "1)" as the default algorithm for
>>>>>>>  generating IIDs, for the reasons discussed in RFC7721
>>>>>>> and draft-gont-predictable-numeric-ids. We have a very
>>>>>>> long history of improper numeric IDs, and I guess that,
>>>>>>> regarding this one, we simply disagree with Lorenzo.
>>>>>>>
>>>>>>>
>>>>>>> Regarding "2)", this document does not specify any new
>>>>>>> requirements on the topic. Essentially, nodes are
>>>>>>> implied to configure a stable addresses as a result of
>>>>>>> SLAAC&traditional link-layer address properties, and more
>>>>>>> explicitly by this text in RFC4941:
>>>>>>>
>>>>>>> * Section 3, bullet #1: 2.  Create additional addresses
>>>>>>> based on a random interface identifier for the purpose of
>>>>>>> initiating outgoing sessions.
>>>>>>>
>>>>>>> * Section 3.3, bullet #1: 1.  Process the Prefix
>>>>>>> Information Option as defined in [ADDRCONF], either
>>>>>>> creating a new public address or adjusting the lifetimes
>>>>>>> of existing addresses, both public and temporary.
>>>>>>>
>>>>>>> * Section 3.3, bullet #3: 3.  When a new public address
>>>>>>> is created as described in [ADDRCONF], the node SHOULD
>>>>>>> also create a new temporary address.
>>>>>>>
>>>>>>> * Section 3.6, for instance, says (even recommending that
>>>>>>> temp addrs default to "off"): The use of temporary
>>>>>>> addresses may cause unexpected difficulties with some
>>>>>>> applications. As described below, some servers refuse to
>>>>>>> accept communications from clients for which they cannot
>>>>>>> map the IP address into a DNS name.  In addition, some
>>>>>>> applications may not behave robustly if temporary
>>>>>>> addresses are used and an address expires before the
>>>>>>> application has terminated, or if it opens multiple
>>>>>>> sessions, but expects them to all use the same
>>>>>>> addresses. Consequently, the use of temporary addresses
>>>>>>> SHOULD be disabled by default in order to minimize
>>>>>>> potential disruptions.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Our document simply requires implementations that their
>>>>>>> stable addresses are RFC7721-friendly. But if anything,
>>>>>>> the requirement of whether to have a stable address or
>>>>>>> not is not something introduced by our document.
>>>>>>>
>>>>>>> As a co-author of draft-ietf-6man-default-iids, I just
>>>>>>> wanted to check that we're on the same page, because I
>>>>>>> have the feeling that the above keeps getting
>>>>>>> misinterpreted.
>>>>>>>
>>>>>>> I believe all of the co-authors of default-iids agree and
>>>>>>> understand that there can be scenarios where you may want
>>>>>>> to do temporary-addresses-only. However, that is
>>>>>>> orthogonal to this particular document (default-iids),
>>>>>>> and would probably require an update to RFC4941, such
>>>>>>> that temporary addresses can be employed as a
>>>>>>> replacement of stable addresses, rather than as something
>>>>>>> that you do "in addition to" them.
>>>>>>>
>>>>>>> This document is about how to do stable addresses in a
>>>>>>> more RFC7721-friendly way than we currently do.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Best regards, -- Fernando Gont e-mail:
>>>>>>> fernando@gont.com.ar || fgont@si6networks.com PGP
>>>>>>> Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF
>>>>>>> D076 FFF1
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>
>>>>>>>
>>>>>>>
>>
>>>>>>>
>>>>>>>
IETF IPv6 working group mailing list
>>>>>>> ipv6@ietf.org Administrative Requests:
>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>> --------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>>
>>>>
>>>>>>>
>>>>>>>
>>
>>>>>>>
>>>>>>>
--------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>> Administrative Requests:
>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>
>>
>>>>>>
>>>>>>
--------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>> Administrative Requests:
>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------
>>>>>
>>>>
>>>>
>>>>>
>>>>>
>>
>>>>>
>>>>>
--------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>> Administrative Requests:
>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>
>>>>
>>>>
>


From nobody Wed May 18 09:08:09 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 AE42712D1CD for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 09:08:08 -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_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 (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 VeWjvwcBCu2c for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 09:08:00 -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 4739E12D16D for <ipv6@ietf.org>; Wed, 18 May 2016 09:08:00 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lrp0079.outbound.protection.outlook.com [213.199.154.79]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-59-70Bqjs0UT1q0yaxRmD4Luw-1; Wed, 18 May 2016 17:07:54 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=GcFI2hjoSiWcQW/k9w+ocm2g1QTnnqQX1Wywlpkhn5I=; b=ebNRuTa+T5DVB+9RkNvDYZYav+skQKkDPw59BvsuHe92LymO2eG9uHm6jOLaTL2n9kMNmvkeJaIsbOcvRrUvCcNenIlDlHYUTaNPVdZDFNr5N7ho0TnLUlEh9gCUYzKUvwNkMgkgsexHsFpZtqhs7aqZZFZMJb0+MejaOagu6NU=
Received: from DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) by DBXPR07MB462.eurprd07.prod.outlook.com (10.141.231.140) with Microsoft SMTP Server (TLS) id 15.1.497.12; Wed, 18 May 2016 16:07:53 +0000
Received: from DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) by DBXPR07MB462.eurprd07.prod.outlook.com ([10.141.231.140]) with mapi id 15.01.0497.019; Wed, 18 May 2016 16:07:53 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: RFC4941 text on requirement for public addresses
Thread-Topic: RFC4941 text on requirement for public addresses
Thread-Index: AQHRsQ/upavhfDHCwU+NjueDdmm28J++v3CAgAAEWwCAAAKUAIAAEmMAgAAD+gA=
Date: Wed, 18 May 2016 16:07:53 +0000
Message-ID: <3C4C7992-8343-4F5E-A43C-13C8183E8E85@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk> <f185260a-6041-607a-bc9c-fcacdd59ab78@gmail.com> <AA62DD34-9484-4AB2-81C5-DBC3263C040F@jisc.ac.uk> <e69d3c42-b496-4e06-76ae-4206b6a3f245@gmail.com>
In-Reply-To: <e69d3c42-b496-4e06-76ae-4206b6a3f245@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: [194.82.140.195]
x-ms-office365-filtering-correlation-id: 7caa9ec5-ba76-4a6e-051c-08d37f369160
x-microsoft-exchange-diagnostics: 1; DBXPR07MB462; 5:TMj9dAQNTaFFW/LQ/sIOOUgK9K9ZHkLGpzXfGC9S5uzWU0sqZ0q8QS/PyjHPO5Cf2UqvIjrtZWzZ8sK9wDXOilS/FV3m4MZzvr63Hv8kdRQy5vRDZBNrksCJOmPPFBQU2qGhuo6iGK2PPghI473hug==; 24:jA+4vvKQyJrfEj3eIDgPq5SyYBREGcpU7C1Hn4JVL0AdXnk3OTZQFsSyUIVSTBLkyifXi1pVXvQsFZgtPVlNUcBcObIPwjqFNkMIOiBafdo=; 7:7XaZBN4yB/8YZ34A5Vl95Fy39zJRb2OuRX8xKZYSKIzM49J1+c451eR/TCW1mnF49V8jParKQjAzSReD3balbJbMR3KdjRDVoSWPRSAnA4tH16ZbmruGnSJf/KS1HfC+//015E1gXNLAT1x1x7FQZsSutve+A+PXb3ki13QwGHeN4Bh5BgChtXD86eswVhUV; 20:FIceHeRbYwh9Mwhqw+xacH4rb62VCtMRyNw6YR6Hs+k/AZHwRoWLQb6Noy2WW++5YgfQASr0XSW7NsRsiVU6Ykz2dO8xHzyXMlmtDeCq+RBdj3OGAd450wHGU8VjrMyOEii3FdG7B/mMffPX/qpOGm+fPoBVRgVKcwRY41QT97g=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DBXPR07MB462;
x-microsoft-antispam-prvs: <DBXPR07MB4620D78C0747E819E8BCA54D6490@DBXPR07MB462.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001); SRVR:DBXPR07MB462; BCL:0; PCL:0; RULEID:; SRVR:DBXPR07MB462; 
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(24454002)(81166006)(93886004)(8936002)(5004730100002)(92566002)(11100500001)(122556002)(57306001)(2900100001)(82746002)(19580395003)(15975445007)(189998001)(106116001)(5002640100001)(2950100001)(77096005)(19580405001)(4326007)(110136002)(83716003)(76176999)(50986999)(86362001)(66066001)(74482002)(33656002)(10400500002)(36756003)(5008740100001)(102836003)(586003)(6116002)(3280700002)(1220700001)(3660700001)(2906002)(87936001)(8676002)(50226002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:DBXPR07MB462; H:DBXPR07MB462.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-ID: <2D818B57528BFF46980BF866D0E4EB9F@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 16:07:53.2385 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBXPR07MB462
X-MC-Unique: 70Bqjs0UT1q0yaxRmD4Luw-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1PS2Vb8S44fvX1oTqpHfJjjsR4I>
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: Wed, 18 May 2016 16:08:08 -0000

> On 18 May 2016, at 16:53, Alexandre Petrescu <alexandre.petrescu@gmail.co=
m> wrote:
>=20
> Le 18/05/2016 =E0 16:47, Tim Chown a =E9crit :
>>> On 18 May 2016, at 15:38, Alexandre Petrescu
>>> <alexandre.petrescu@gmail.com> wrote:
>>>=20
>>> Le 18/05/2016 =E0 16:23, Tim Chown a =E9crit :
>>>>> On 18 May 2016, at 15:15, Alexandre Petrescu
>>>>> <alexandre.petrescu@gmail.com> wrote:
>>>>>=20
>>>>> Le 18/05/2016 =E0 15:56, Tim Chown a =E9crit :
>>>>>> Hi,
>>>>>>=20
>>>>>>> On 18 May 2016, at 12:13, otroan@employees.org wrote:
>>>>>>>=20
>>>>>>> This email from Fernando provides a good introduction to an
>>>>>>> outstanding question from Buenos Aires.
>>>>>>>=20
>>>>>>> The current plan is to take RFC4941 to Internet Standard
>>>>>>> unchanged. A question was raised if 4941 requires public
>>>>>>> addresses or not, and if we have to update 4941 text, or
>>>>>>> if we can live with the current text, and still allow for
>>>>>>> interfaces with only temporary addresses.
>>>>>>>=20
>>>>>>> Opinions?
>>>>>>=20
>>>>>> The intro to RFC 4941 section 3 says that RFC 4941 would not
>>>>>> affect normal SLAAC operation, so you would expect a public
>>>>>> address to be created by SLAAC. Further, section 3.3 says
>>>>>> quite explicitly that a public address MUST be generated as
>>>>>> per RFC 4862, and that a temporary address SHOULD also be
>>>>>> generated.
>>>>>>=20
>>>>>> So if we want to support having ONLY temporary addresses, I
>>>>>> think the document will need updating. At the very best, it
>>>>>> would be confusing to leave it as is if we want interfaces
>>>>>> with only temporary addresses.
>>>>>>=20
>>>>>> Personally, I would support such a change. When I last
>>>>>> looked at the activity log for my desktop over a one month
>>>>>> period, it showed global IPv4, LL IPv6, and many temporary
>>>>>> IPv6 addresses in use, but there was no activity to/from the
>>>>>> desktop=92s public IPv6 address.  That=92s probably not uncommon
>>>>>> in an enterprise environment where RFC 4941 is enabled. So
>>>>>> why require that such an address be generated?
>>>>>=20
>>>>> If there's no fixed address then there's no DNS name for that
>>>>> machine.
>>>>>=20
>>>>> Updating DNS for each temporary IP address may not be that
>>>>> easy.
>>>>=20
>>>> But that=92s not necessarily needed. Was certainly fine without it
>>>> in the campus environment I was in, where all comms initiated
>>>> outbound were from privacy addresses with no associated DNS
>>>> info.
>>>=20
>>> Hmm... I guess the machine was doing the important things on IPv4
>>> (not IPv6)(?)
>>>=20
>>> A machine w/o a DNS name is segregated, half-connected to the
>>> Internet.
>>>=20
>>> It's a machine that can live with NATs.
>>>=20
>>> It's a machine that can't do video-over-IP live streaming for too
>>> long.
>>>=20
>>> It's a machine that can't be an ADSL box which has same IP address
>>> since many years now.
>>=20
>> It=92s a desktop that I used in various forms for many years, with
>> privacy addresses on, as my day to day desktop, accessing anything
>> offering an AAAA record by IPv6, and of course the rest by IPv4. I
>> didn=92t see any evidence of anything broken as a result.  But then I
>> had no services on the desktop which needed to be accessed
>> externally.
>>=20
>> I=92m not saying hosts MUST have a public address to be able to have a
>> temporary address, but there=92s no reason in many scenarios why they
>> can=92t just run with temporary addresses.
>=20
> It very much depends on what the application is about.
>=20
> An html browsing application will only need bursts of data exchange,
> maybe each issued from distinct IP address, that may change every second.
>=20
> But an ftp transferring an Ultra-HD Bluray on a cellular link may need
> an address to last for many hours; please dont change that!

Right. And the default address refresh on most OSes is 24 hours.

>> I think the discussion here is about relaxing the MUST in 4941 about
>> public addresses to a SHOULD (or MAY).
>=20
> I am tempted to say "SHOULD" rather than "MAY=94.

Agreed.

> But I also worry that the perspective may be wrong altogether.
>=20
> Until now applications assumed the IP address is fixed stable.  Efforts l=
ike Mobile IP tried to accommodate network-induced variation in that IP add=
ress.
>=20
> Now we say privacy is important, and so we want the address to change. Th=
is looks strange.

We should be supporting privacy. Whether by changing MAC addresses or IP ad=
dresses over time.  Both concepts are =91strange=92 to those familiar with =
the practices of the past 20+ years.

>> As an aside are you aware of applications that will try to use a
>> public address in the presence of a temporary one?
>=20
> No, I am not aware.  I guess you are?

No, I=92m not, in theory RFC 6724 should avoid it.

> I think applications should not request some kind of IP address - that ma=
y be layer violation.  Applications should use application-layer identifier=
s.
>=20
> Let me diverge on an argument - over in DMM WG, there is a developping pe=
rspective in which the application _does_ require the kind of IP address to=
 use (stable, transient, etc.)  In this perspective the cellular network op=
erator provides a Static IP address if the UE application requests one (e.g=
. "Static" in https://www.wireless.att.com/businesscenter/solutions/connect=
ivity/ip-addressing.jsp)=20
>=20
> If the network offers a Static ("stable", "fixed") IP address to the node=
, will the node refuse it?  I doubt so, because the operator thinks (see th=
at web page) that the end user is even ready to pay money for that Static a=
ddress - i.e. there is value in a Static address.

And I=92d agree that this mode should be supported when required. It=92s a =
trade-off.

> So the perspective in this RFC4941 (there is no value in a static address=
) is contradictory to some operator's interests.

All we=92re discussing here (I think!) is whether 4941 should be changed to=
 no longer say that SLAAC is a MUST, so that we open the possibility for a =
node to use temporary addresses only. I don=92t think we need to widen the =
discussion - if you want to do that, the default-iids WGLC thread is probab=
ly the place to do so...

> I think this contradiction stems from the ability of an application to re=
quire some particular kind network-layer identifier (IP address) - layer vi=
olation.
>=20
> Privacy is an application matter: "this site uses cookies, do you agree"
>=20
> Privacy is not an IP matter: unreadable address, return to sender
>=20
>> RFC 6724 is quite explicit about this now:
>>=20
>> Rule 7: Prefer temporary addresses. If SA is a temporary address and
>> SB is a public address, then prefer SA.  Similarly, if SB is a
>> temporary address and SA is a public address, then prefer SB.
>=20
> I take this as such out of the RFC.
>=20
> There are multiple problems with 'public' and 'temporary' address terms i=
n IPv6 addressing.
>=20
> First, 'public' and 'temporary' addresses are not disjoint.  It's not lik=
e in IPv4, where a public IPv4 address is disjoint from private IPv4 addres=
s (1.1.1.1 vs 192.168.1.1).  An IPv6 'temporary' address can very well be a=
 GUA.
>=20
> Second, there is a pitfall in assuming that a 'temporary' changing IPv6 a=
ddress offers more privacy than a 'public' stable IPv6 address.  True, it c=
hanges more often than a 'public', but the surveillant still sees it (even =
if it is not called 'public') and may adapt to change too - keep a list key=
ed on some other stable identifier; each identifier in draft-ietf-intarea-h=
ostname-practice-02, plus the unique prefix delivered by cellular operator =
to user terminal, plus more in link-layer messaging.  We couldnt randomize =
each of these, right?

Well, there=92s also, as I=92m sure Lorenzo would point out, the option to =
run SLAAC with underlying dynamic MAC addresses.  Which I think is a perfec=
tly valid mode, though default-iids seems to be saying it isn't. Is that th=
en formally a public or temporary address?

But let=92s focus on the topic Ole opened - should 4941 change the requirem=
ent for a public address from a MUST to something less, i.e. SHOULD, so we =
can very clearly support a mode where nodes can have just temporary address=
es and no public address.

Tim

>=20
> Alex
>=20
>=20
>>=20
>> Tim
>>=20
>>> Alex
>>>=20
>>>>=20
>>>> Tim
>>>>=20
>>>>> Alex
>>>>>=20
>>>>>>=20
>>>>>> Tim
>>>>>>=20
>>>>>>> Best regards, Ole
>>>>>>>=20
>>>>>>>> On 17 May 2016, at 20:15, Fernando Gont
>>>>>>>> <fernando@gont.com.ar> wrote:
>>>>>>>>=20
>>>>>>>> Lorenzo (and wg),
>>>>>>>>=20
>>>>>>>> The two issues raised by Lorenzo regarding default-iids
>>>>>>>> boil down to:
>>>>>>>>=20
>>>>>>>> 1) The ability to embed MAC addresses in the IID
>>>>>>>>=20
>>>>>>>> 2) The requirement to have stable addresses
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> This document does ban "1)" as the default algorithm for
>>>>>>>> generating IIDs, for the reasons discussed in RFC7721
>>>>>>>> and draft-gont-predictable-numeric-ids. We have a very
>>>>>>>> long history of improper numeric IDs, and I guess that,
>>>>>>>> regarding this one, we simply disagree with Lorenzo.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Regarding "2)", this document does not specify any new
>>>>>>>> requirements on the topic. Essentially, nodes are
>>>>>>>> implied to configure a stable addresses as a result of
>>>>>>>> SLAAC&traditional link-layer address properties, and more
>>>>>>>> explicitly by this text in RFC4941:
>>>>>>>>=20
>>>>>>>> * Section 3, bullet #1: 2.  Create additional addresses
>>>>>>>> based on a random interface identifier for the purpose of
>>>>>>>> initiating outgoing sessions.
>>>>>>>>=20
>>>>>>>> * Section 3.3, bullet #1: 1.  Process the Prefix
>>>>>>>> Information Option as defined in [ADDRCONF], either
>>>>>>>> creating a new public address or adjusting the lifetimes
>>>>>>>> of existing addresses, both public and temporary.
>>>>>>>>=20
>>>>>>>> * Section 3.3, bullet #3: 3.  When a new public address
>>>>>>>> is created as described in [ADDRCONF], the node SHOULD
>>>>>>>> also create a new temporary address.
>>>>>>>>=20
>>>>>>>> * Section 3.6, for instance, says (even recommending that
>>>>>>>> temp addrs default to "off"): The use of temporary
>>>>>>>> addresses may cause unexpected difficulties with some
>>>>>>>> applications. As described below, some servers refuse to
>>>>>>>> accept communications from clients for which they cannot
>>>>>>>> map the IP address into a DNS name.  In addition, some
>>>>>>>> applications may not behave robustly if temporary
>>>>>>>> addresses are used and an address expires before the
>>>>>>>> application has terminated, or if it opens multiple
>>>>>>>> sessions, but expects them to all use the same
>>>>>>>> addresses. Consequently, the use of temporary addresses
>>>>>>>> SHOULD be disabled by default in order to minimize
>>>>>>>> potential disruptions.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Our document simply requires implementations that their
>>>>>>>> stable addresses are RFC7721-friendly. But if anything,
>>>>>>>> the requirement of whether to have a stable address or
>>>>>>>> not is not something introduced by our document.
>>>>>>>>=20
>>>>>>>> As a co-author of draft-ietf-6man-default-iids, I just
>>>>>>>> wanted to check that we're on the same page, because I
>>>>>>>> have the feeling that the above keeps getting
>>>>>>>> misinterpreted.
>>>>>>>>=20
>>>>>>>> I believe all of the co-authors of default-iids agree and
>>>>>>>> understand that there can be scenarios where you may want
>>>>>>>> to do temporary-addresses-only. However, that is
>>>>>>>> orthogonal to this particular document (default-iids),
>>>>>>>> and would probably require an update to RFC4941, such
>>>>>>>> that temporary addresses can be employed as a
>>>>>>>> replacement of stable addresses, rather than as something
>>>>>>>> that you do "in addition to" them.
>>>>>>>>=20
>>>>>>>> This document is about how to do stable addresses in a
>>>>>>>> more RFC7721-friendly way than we currently do.
>>>>>>>>=20
>>>>>>>> Thanks!
>>>>>>>>=20
>>>>>>>> Best regards, -- Fernando Gont e-mail:
>>>>>>>> fernando@gont.com.ar || fgont@si6networks.com PGP
>>>>>>>> Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF
>>>>>>>> D076 FFF1
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> ------------------------------------------------------------------=
--
>>>>>>>>=20
>>>>>>>>=20
>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>=20
>>>>>>>>=20
>>>>>>>>=20
> IETF IPv6 working group mailing list
>>>>>>>> ipv6@ietf.org Administrative Requests:
>>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>>> ------------------------------------------------------------------=
--
>>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>=20
>>>>>>>>=20
>>>>>>>>=20
> --------------------------------------------------------------------
>>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>>> Administrative Requests:
>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>> -------------------------------------------------------------------=
-
>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>=20
>>>>>>>=20
>>>>>>>=20
> --------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>> Administrative Requests:
>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>>>>>>=20
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>=20
>>>>>>=20
>>>>>>=20
> --------------------------------------------------------------------
>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>> Administrative Requests:
>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>> --------------------------------------------------------------------


From nobody Wed May 18 09:45:31 2016
Return-Path: <dthaler@microsoft.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 43A6C12D16D for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 09:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 nksvxKY57KFh for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 09:45:27 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0123.outbound.protection.outlook.com [207.46.100.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8DB012D5B7 for <6man@ietf.org>; Wed, 18 May 2016 09:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=fly89Ra4GrxW+iTSctd3dttXsokiO4s341wlbdMMuXg=; b=X29zRZkOkR5398jeS5FHstL650Zm4Ww5k01O7jnuOxp7tmU2MArd4F7lgoGI3j6X0CfF6GMPEWCbN+CGF42dyNdeXG2/SZ3pz/qiJbBj515fmPvuQCoIhKd2BUEIhdVw7/M/7vxPc9E1fY84Eu3tqmfbT2ZQBe1XKO0ySQBdLGM=
Received: from DM2PR0301MB0717.namprd03.prod.outlook.com (10.160.97.13) by DM2PR0301MB0719.namprd03.prod.outlook.com (10.160.97.14) with Microsoft SMTP Server (TLS) id 15.1.497.12; Wed, 18 May 2016 16:45:25 +0000
Received: from DM2PR0301MB0717.namprd03.prod.outlook.com ([10.160.97.13]) by DM2PR0301MB0717.namprd03.prod.outlook.com ([10.160.97.13]) with mapi id 15.01.0497.017; Wed, 18 May 2016 16:45:25 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Lorenzo Colitti <lorenzo@google.com>, Ole Troan <otroan@employees.org>
Subject: RE: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Topic: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
Thread-Index: AQHRsPZbSSmbpzz5P0G2XDGXcEU5R5++tD8AgAAy3FA=
Date: Wed, 18 May 2016 16:45:25 +0000
Message-ID: <DM2PR0301MB0717D5EA3FD289A7894E3AC0A3490@DM2PR0301MB0717.namprd03.prod.outlook.com>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <CAKD1Yr2aWnRVvL6KEheWb1fKn3RPGdYewdb3QVf9w3A1V1wTUQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr2aWnRVvL6KEheWb1fKn3RPGdYewdb3QVf9w3A1V1wTUQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: google.com; dkim=none (message not signed) header.d=none;google.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [168.159.213.209]
x-ms-office365-filtering-correlation-id: d1a2f4c7-838f-41ab-9272-08d37f3bcfd9
x-microsoft-exchange-diagnostics: 1; DM2PR0301MB0719; 5:RPltl8oKNTKkZ4mO090tRpACb88RKXPVqAcG6tiy4kAeZdV08DcBEvXDr66JIeCUDyh4ZYT4P2MMC7BbBneszmPwphQPhwh+cwfitG3ox0QZ0Yfe0h8UBnQl2sY28pRzJu43pJ9qOHZBDOjZYnwqdQ==; 24:ozRZ5yplKqIWXmoVgbyxeNpFIngZuTaOY3+n+qX8b8qwUOTFLj2l9/rxCupLIaJ21YBUu1nF2TMWlxDtYnbg5iJhz0SR0lRS7EHXce8je5U=; 7:iQyl9Sb5hW/Ixvktkd1gBT9vN+muwWhoBP1x0tB/nZ038DcepZXbu08p5R+0+A7Gprkt7QG9uZWVQNHx84pR7tO1MYIKtiFrTAcxYwpXT4IKE0PzGPgSYOyB+ZtauvhwcIMzturXwgrJFh7O9NeDb/XZwUHXKbqHbfqtR34AT41eEUJBC9RRzW85MWs4lWXHWjphoo3RNfrx7vyMu02zKQ==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB0719;
x-microsoft-antispam-prvs: <DM2PR0301MB0719AACF363C7B2B0E86FFC9A3490@DM2PR0301MB0719.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(61426038)(61427038); SRVR:DM2PR0301MB0719; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0301MB0719; 
x-forefront-prvs: 0946DC87A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(51694002)(24454002)(377454003)(252514010)(790700001)(99286002)(66066001)(19617315012)(8676002)(4326007)(9686002)(2906002)(16236675004)(76576001)(1220700001)(8936002)(5005710100001)(10290500002)(11100500001)(6116002)(586003)(19300405004)(106116001)(81166006)(122556002)(10400500002)(3660700001)(33656002)(19609705001)(2900100001)(19580395003)(2950100001)(50986999)(189998001)(74316001)(77096005)(3280700002)(5002640100001)(76176999)(92566002)(19625215002)(54356999)(5008740100001)(86362001)(15975445007)(5004730100002)(87936001)(5001770100001)(102836003)(5003600100002)(19580405001)(86612001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB0719; H:DM2PR0301MB0717.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM2PR0301MB0717D5EA3FD289A7894E3AC0A3490DM2PR0301MB0717_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 May 2016 16:45:25.5374 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0301MB0719
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CSlN6QVL8Rvrx7dIZLsNoIr4zGU>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 16:45:29 -0000

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

SSBhZ3JlZSB3aXRoIE9sZSB0aGF0IFJGQyA0OTQxIGRvZXMgbm90IHJlcXVpcmUgcHVibGljIGFk
ZHJlc3Nlcy4NCkZvciBleGFtcGxlLCBuZWl0aGVyIG9mIHRoZSB0d28gc25pcHBldHMgcXVvdGVk
IGJ5IExvcmVuem8gcmVxdWlyZXMgcHVibGljIGFkZHJlc3Nlcy4NClRoZXkganVzdCBzdGF0ZSB3
aGF0IHRoZSBiZWhhdmlvciBpcyBJRiB5b3UgaGF2ZSBwdWJsaWMgYWRkcmVzc2VzLg0KDQpGcm9t
OiBMb3JlbnpvIENvbGl0dGkgW21haWx0bzpsb3JlbnpvQGdvb2dsZS5jb21dDQpTZW50OiBXZWRu
ZXNkYXksIE1heSAxOCwgMjAxNiA5OjQyIEFNDQpUbzogT2xlIFRyb2FuIDxvdHJvYW5AZW1wbG95
ZWVzLm9yZz4NCkNjOiA2bWFuQGlldGYub3JnOyBGZXJuYW5kbyBHb250IDxmZXJuYW5kb0Bnb250
LmNvbS5hcj47IGRyYWZ0LWlldGYtNm1hbi1kZWZhdWx0LWlpZHNAdG9vbHMuaWV0Zi5vcmcNClN1
YmplY3Q6IFJlOiBSRkM0OTQxIHRleHQgb24gcmVxdWlyZW1lbnQgZm9yIHB1YmxpYyBhZGRyZXNz
ZXMgKHdhczogUmU6IGRlZmF1bHQtaWlkcyBhbmQgc3RhYmxlIGFkZHJlc3NlcykNCg0KQXMgd3Jp
dHRlbiwgUkZDIDQ5NDEgc2VlbXMgdG8gcmVxdWlyZSBwdWJsaWMgYWRkcmVzc2VzLiBGb3IgZXhh
bXBsZToNCg0KICAgICAgIElmIGEgcmVjZWl2ZWQNCiAgICAgICBvcHRpb24gd2lsbCBleHRlbmQg
dGhlIGxpZmV0aW1lIG9mIGEgcHVibGljIGFkZHJlc3MsIHRoZQ0KICAgICAgIGxpZmV0aW1lcyBv
ZiB0ZW1wb3JhcnkgYWRkcmVzc2VzIHNob3VsZCBiZSBleHRlbmRlZA0KLi4uDQogICAzLiAgV2hl
biBhIG5ldyBwdWJsaWMgYWRkcmVzcyBpcyBjcmVhdGVkIGFzIGRlc2NyaWJlZCBpbiBbQUREUkNP
TkZdLA0KICAgICAgIHRoZSBub2RlIFNIT1VMRCBhbHNvIGNyZWF0ZSBhIG5ldyB0ZW1wb3Jhcnkg
YWRkcmVzcy4NCi4uLg0KICAgICAgICogIEl0cyBQcmVmZXJyZWQgTGlmZXRpbWUgaXMgdGhlIGxv
d2VyIG9mIHRoZSBQcmVmZXJyZWQgTGlmZXRpbWUNCiAgICAgICAgICBvZiB0aGUgcHVibGljIGFk
ZHJlc3Mgb3IgVEVNUF9QUkVGRVJSRURfTElGRVRJTUUgLQ0KICAgICAgICAgIERFU1lOQ19GQUNU
T1IuDQoNCk9uIFdlZCwgTWF5IDE4LCAyMDE2IGF0IDg6MTMgUE0sIDxvdHJvYW5AZW1wbG95ZWVz
Lm9yZzxtYWlsdG86b3Ryb2FuQGVtcGxveWVlcy5vcmc+PiB3cm90ZToNClRoaXMgZW1haWwgZnJv
bSBGZXJuYW5kbyBwcm92aWRlcyBhIGdvb2QgaW50cm9kdWN0aW9uIHRvIGFuIG91dHN0YW5kaW5n
IHF1ZXN0aW9uIGZyb20gQnVlbm9zIEFpcmVzLg0KDQpUaGUgY3VycmVudCBwbGFuIGlzIHRvIHRh
a2UgUkZDNDk0MSB0byBJbnRlcm5ldCBTdGFuZGFyZCB1bmNoYW5nZWQuDQpBIHF1ZXN0aW9uIHdh
cyByYWlzZWQgaWYgNDk0MSByZXF1aXJlcyBwdWJsaWMgYWRkcmVzc2VzIG9yIG5vdCwgYW5kIGlm
IHdlIGhhdmUgdG8gdXBkYXRlIDQ5NDEgdGV4dCwgb3IgaWYgd2UgY2FuIGxpdmUgd2l0aCB0aGUg
Y3VycmVudCB0ZXh0LCBhbmQgc3RpbGwgYWxsb3cgZm9yIGludGVyZmFjZXMgd2l0aCBvbmx5IHRl
bXBvcmFyeSBhZGRyZXNzZXMuDQoNCk9waW5pb25zPw0KDQpCZXN0IHJlZ2FyZHMsDQpPbGUNCg0K
PiBPbiAxNyBNYXkgMjAxNiwgYXQgMjA6MTUsIEZlcm5hbmRvIEdvbnQgPGZlcm5hbmRvQGdvbnQu
Y29tLmFyPG1haWx0bzpmZXJuYW5kb0Bnb250LmNvbS5hcj4+IHdyb3RlOg0KPg0KPiBMb3Jlbnpv
IChhbmQgd2cpLA0KPg0KPiBUaGUgdHdvIGlzc3VlcyByYWlzZWQgYnkgTG9yZW56byByZWdhcmRp
bmcgZGVmYXVsdC1paWRzIGJvaWwgZG93biB0bzoNCj4NCj4gMSkgVGhlIGFiaWxpdHkgdG8gZW1i
ZWQgTUFDIGFkZHJlc3NlcyBpbiB0aGUgSUlEDQo+DQo+IDIpIFRoZSByZXF1aXJlbWVudCB0byBo
YXZlIHN0YWJsZSBhZGRyZXNzZXMNCj4NCj4NCj4gVGhpcyBkb2N1bWVudCBkb2VzIGJhbiAiMSki
IGFzIHRoZSBkZWZhdWx0IGFsZ29yaXRobSBmb3IgZ2VuZXJhdGluZw0KPiBJSURzLCBmb3IgdGhl
IHJlYXNvbnMgZGlzY3Vzc2VkIGluIFJGQzc3MjEgYW5kDQo+IGRyYWZ0LWdvbnQtcHJlZGljdGFi
bGUtbnVtZXJpYy1pZHMuIFdlIGhhdmUgYSB2ZXJ5IGxvbmcgaGlzdG9yeSBvZg0KPiBpbXByb3Bl
ciBudW1lcmljIElEcywgYW5kIEkgZ3Vlc3MgdGhhdCwgcmVnYXJkaW5nIHRoaXMgb25lLCB3ZSBz
aW1wbHkNCj4gZGlzYWdyZWUgd2l0aCBMb3JlbnpvLg0KPg0KPg0KPiBSZWdhcmRpbmcgIjIpIiwg
dGhpcyBkb2N1bWVudCBkb2VzIG5vdCBzcGVjaWZ5IGFueSBuZXcgcmVxdWlyZW1lbnRzIG9uDQo+
IHRoZSB0b3BpYy4gRXNzZW50aWFsbHksIG5vZGVzIGFyZSBpbXBsaWVkIHRvIGNvbmZpZ3VyZSBh
IHN0YWJsZQ0KPiBhZGRyZXNzZXMgYXMgYSByZXN1bHQgb2YgU0xBQUMmdHJhZGl0aW9uYWwgbGlu
ay1sYXllciBhZGRyZXNzDQo+IHByb3BlcnRpZXMsIGFuZCBtb3JlIGV4cGxpY2l0bHkgYnkgdGhp
cyB0ZXh0IGluIFJGQzQ5NDE6DQo+DQo+ICogU2VjdGlvbiAzLCBidWxsZXQgIzE6DQo+ICAgMi4g
IENyZWF0ZSBhZGRpdGlvbmFsIGFkZHJlc3NlcyBiYXNlZCBvbiBhIHJhbmRvbSBpbnRlcmZhY2UN
Cj4gICAgICAgaWRlbnRpZmllciBmb3IgdGhlIHB1cnBvc2Ugb2YgaW5pdGlhdGluZyBvdXRnb2lu
ZyBzZXNzaW9ucy4NCj4NCj4gKiBTZWN0aW9uIDMuMywgYnVsbGV0ICMxOg0KPiAgIDEuICBQcm9j
ZXNzIHRoZSBQcmVmaXggSW5mb3JtYXRpb24gT3B0aW9uIGFzIGRlZmluZWQgaW4gW0FERFJDT05G
XSwNCj4gICAgICAgZWl0aGVyIGNyZWF0aW5nIGEgbmV3IHB1YmxpYyBhZGRyZXNzIG9yIGFkanVz
dGluZyB0aGUgbGlmZXRpbWVzDQo+ICAgICAgIG9mIGV4aXN0aW5nIGFkZHJlc3NlcywgYm90aCBw
dWJsaWMgYW5kIHRlbXBvcmFyeS4NCj4NCj4gKiBTZWN0aW9uIDMuMywgYnVsbGV0ICMzOg0KPiAg
IDMuICBXaGVuIGEgbmV3IHB1YmxpYyBhZGRyZXNzIGlzIGNyZWF0ZWQgYXMgZGVzY3JpYmVkIGlu
IFtBRERSQ09ORl0sDQo+ICAgICAgIHRoZSBub2RlIFNIT1VMRCBhbHNvIGNyZWF0ZSBhIG5ldyB0
ZW1wb3JhcnkgYWRkcmVzcy4NCj4NCj4gKiBTZWN0aW9uIDMuNiwgZm9yIGluc3RhbmNlLCBzYXlz
IChldmVuIHJlY29tbWVuZGluZyB0aGF0IHRlbXAgYWRkcnMNCj4gZGVmYXVsdCB0byAib2ZmIik6
DQo+ICAgVGhlIHVzZSBvZiB0ZW1wb3JhcnkgYWRkcmVzc2VzIG1heSBjYXVzZSB1bmV4cGVjdGVk
IGRpZmZpY3VsdGllcyB3aXRoDQo+ICAgc29tZSBhcHBsaWNhdGlvbnMuICBBcyBkZXNjcmliZWQg
YmVsb3csIHNvbWUgc2VydmVycyByZWZ1c2UgdG8gYWNjZXB0DQo+ICAgY29tbXVuaWNhdGlvbnMg
ZnJvbSBjbGllbnRzIGZvciB3aGljaCB0aGV5IGNhbm5vdCBtYXAgdGhlIElQIGFkZHJlc3MNCj4g
ICBpbnRvIGEgRE5TIG5hbWUuICBJbiBhZGRpdGlvbiwgc29tZSBhcHBsaWNhdGlvbnMgbWF5IG5v
dCBiZWhhdmUNCj4gICByb2J1c3RseSBpZiB0ZW1wb3JhcnkgYWRkcmVzc2VzIGFyZSB1c2VkIGFu
ZCBhbiBhZGRyZXNzIGV4cGlyZXMNCj4gICBiZWZvcmUgdGhlIGFwcGxpY2F0aW9uIGhhcyB0ZXJt
aW5hdGVkLCBvciBpZiBpdCBvcGVucyBtdWx0aXBsZQ0KPiAgIHNlc3Npb25zLCBidXQgZXhwZWN0
cyB0aGVtIHRvIGFsbCB1c2UgdGhlIHNhbWUgYWRkcmVzc2VzLg0KPiAgIENvbnNlcXVlbnRseSwg
dGhlIHVzZSBvZiB0ZW1wb3JhcnkgYWRkcmVzc2VzIFNIT1VMRCBiZSBkaXNhYmxlZCBieQ0KPiAg
IGRlZmF1bHQgaW4gb3JkZXIgdG8gbWluaW1pemUgcG90ZW50aWFsIGRpc3J1cHRpb25zLg0KPg0K
Pg0KPg0KPiBPdXIgZG9jdW1lbnQgc2ltcGx5IHJlcXVpcmVzIGltcGxlbWVudGF0aW9ucyB0aGF0
IHRoZWlyDQo+IHN0YWJsZSBhZGRyZXNzZXMgYXJlIFJGQzc3MjEtZnJpZW5kbHkuIEJ1dCBpZiBh
bnl0aGluZywgdGhlIHJlcXVpcmVtZW50DQo+IG9mIHdoZXRoZXIgdG8gaGF2ZSBhIHN0YWJsZSBh
ZGRyZXNzIG9yIG5vdCBpcyBub3Qgc29tZXRoaW5nIGludHJvZHVjZWQNCj4gYnkgb3VyIGRvY3Vt
ZW50Lg0KPg0KPiBBcyBhIGNvLWF1dGhvciBvZiBkcmFmdC1pZXRmLTZtYW4tZGVmYXVsdC1paWRz
LCBJIGp1c3Qgd2FudGVkIHRvIGNoZWNrDQo+IHRoYXQgd2UncmUgb24gdGhlIHNhbWUgcGFnZSwg
YmVjYXVzZSBJIGhhdmUgdGhlIGZlZWxpbmcgdGhhdCB0aGUgYWJvdmUNCj4ga2VlcHMgZ2V0dGlu
ZyBtaXNpbnRlcnByZXRlZC4NCj4NCj4gSSBiZWxpZXZlIGFsbCBvZiB0aGUgY28tYXV0aG9ycyBv
ZiBkZWZhdWx0LWlpZHMgYWdyZWUgYW5kIHVuZGVyc3RhbmQNCj4gdGhhdCB0aGVyZSBjYW4gYmUg
c2NlbmFyaW9zIHdoZXJlIHlvdSBtYXkgd2FudCB0byBkbw0KPiB0ZW1wb3JhcnktYWRkcmVzc2Vz
LW9ubHkuIEhvd2V2ZXIsIHRoYXQgaXMgb3J0aG9nb25hbCB0byB0aGlzIHBhcnRpY3VsYXINCj4g
ZG9jdW1lbnQgKGRlZmF1bHQtaWlkcyksIGFuZCB3b3VsZCBwcm9iYWJseSByZXF1aXJlIGFuIHVw
ZGF0ZSB0bw0KPiBSRkM0OTQxLCBzdWNoIHRoYXQgdGVtcG9yYXJ5IGFkZHJlc3NlcyBjYW4gYmUg
ZW1wbG95ZWQgYXMgYSByZXBsYWNlbWVudA0KPiBvZiBzdGFibGUgYWRkcmVzc2VzLCByYXRoZXIg
dGhhbiBhcyBzb21ldGhpbmcgdGhhdCB5b3UgZG8gImluIGFkZGl0aW9uDQo+IHRvIiB0aGVtLg0K
Pg0KPiBUaGlzIGRvY3VtZW50IGlzIGFib3V0IGhvdyB0byBkbyBzdGFibGUgYWRkcmVzc2VzIGlu
IGEgbW9yZQ0KPiBSRkM3NzIxLWZyaWVuZGx5IHdheSB0aGFuIHdlIGN1cnJlbnRseSBkby4NCj4N
Cj4gVGhhbmtzIQ0KPg0KPiBCZXN0IHJlZ2FyZHMsDQo+IC0tDQo+IEZlcm5hbmRvIEdvbnQNCj4g
ZS1tYWlsOiBmZXJuYW5kb0Bnb250LmNvbS5hcjxtYWlsdG86ZmVybmFuZG9AZ29udC5jb20uYXI+
IHx8IGZnb250QHNpNm5ldHdvcmtzLmNvbTxtYWlsdG86ZmdvbnRAc2k2bmV0d29ya3MuY29tPg0K
PiBQR1AgRmluZ2VycHJpbnQ6IDc4MDkgODRGNSAzMjJFIDQ1QzcgRjFDOSAzOTQ1IDk2RUUgQTlF
RiBEMDc2IEZGRjENCj4NCj4NCj4NCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gSUVURiBJUHY2IHdvcmtpbmcg
Z3JvdXAgbWFpbGluZyBsaXN0DQo+IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+
DQo+IEFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2lwdjYNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLmhvZW56Yg0KCXttc28t
c3R5bGUtbmFtZTpob2VuemI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29s
b3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25s
eTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGlu
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNw
aWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBk
YXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K
PGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEIj5JIGFncmVlIHdpdGggT2xlIHRoYXQgUkZDIDQ5NDEgZG9lcyBub3QgcmVx
dWlyZSBwdWJsaWMgYWRkcmVzc2VzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj5Gb3IgZXhhbXBsZSwgbmVp
dGhlciBvZiB0aGUgdHdvIHNuaXBwZXRzIHF1b3RlZCBieSBMb3JlbnpvIHJlcXVpcmVzIHB1Ymxp
YyBhZGRyZXNzZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPlRoZXkganVzdCBzdGF0ZSB3aGF0IHRoZSBi
ZWhhdmlvciBpcyBJRiB5b3UgaGF2ZSBwdWJsaWMgYWRkcmVzc2VzLjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWlsRW5kQ29tcG9zZSI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48
L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0
O3BhZGRpbmc6MGluIDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpu
b25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4g
MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IExvcmVuem8gQ29saXR0aSBbbWFpbHRvOmxvcmVuem9A
Z29vZ2xlLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIE1heSAxOCwgMjAxNiA5
OjQyIEFNPGJyPg0KPGI+VG86PC9iPiBPbGUgVHJvYW4gJmx0O290cm9hbkBlbXBsb3llZXMub3Jn
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gNm1hbkBpZXRmLm9yZzsgRmVybmFuZG8gR29udCAmbHQ7ZmVy
bmFuZG9AZ29udC5jb20uYXImZ3Q7OyBkcmFmdC1pZXRmLTZtYW4tZGVmYXVsdC1paWRzQHRvb2xz
LmlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBSRkM0OTQxIHRleHQgb24gcmVxdWly
ZW1lbnQgZm9yIHB1YmxpYyBhZGRyZXNzZXMgKHdhczogUmU6IGRlZmF1bHQtaWlkcyBhbmQgc3Rh
YmxlIGFkZHJlc3Nlcyk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+QXMgd3JpdHRlbiwgUkZDIDQ5NDEgc2VlbXMgdG8gcmVxdWlyZSBwdWJsaWMg
YWRkcmVzc2VzLiBGb3IgZXhhbXBsZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtJZiBhIHJlY2Vp
dmVkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtvcHRpb24gd2lsbCBleHRlbmQgdGhlIGxpZmV0aW1l
IG9mIGEgcHVibGljIGFkZHJlc3MsIHRoZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7bGlmZXRpbWVz
IG9mIHRlbXBvcmFyeSBhZGRyZXNzZXMgc2hvdWxkIGJlIGV4dGVuZGVkPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi4uLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNw
OzMuJm5ic3A7IFdoZW4gYSBuZXcgcHVibGljIGFkZHJlc3MgaXMgY3JlYXRlZCBhcyBkZXNjcmli
ZWQgaW4gW0FERFJDT05GXSw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDt0aGUgbm9kZSBT
SE9VTEQgYWxzbyBjcmVhdGUgYSBuZXcgdGVtcG9yYXJ5IGFkZHJlc3MuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi4uLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyogJm5ic3A7SXRzIFByZWZlcnJlZCBMaWZldGltZSBpcyB0
aGUgbG93ZXIgb2YgdGhlIFByZWZlcnJlZCBMaWZldGltZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBvZiB0aGUgcHVibGljIGFkZHJlc3Mgb3IgVEVNUF9QUkVGRVJSRURfTElGRVRJTUUg
LTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBERVNZTkNfRkFDVE9SLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFdl
ZCwgTWF5IDE4LCAyMDE2IGF0IDg6MTMgUE0sICZsdDs8YSBocmVmPSJtYWlsdG86b3Ryb2FuQGVt
cGxveWVlcy5vcmciIHRhcmdldD0iX2JsYW5rIj5vdHJvYW5AZW1wbG95ZWVzLm9yZzwvYT4mZ3Q7
IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+VGhpcyBlbWFpbCBmcm9tIEZlcm5hbmRvIHBy
b3ZpZGVzIGEgZ29vZCBpbnRyb2R1Y3Rpb24gdG8gYW4gb3V0c3RhbmRpbmcgcXVlc3Rpb24gZnJv
bSBCdWVub3MgQWlyZXMuPGJyPg0KPGJyPg0KVGhlIGN1cnJlbnQgcGxhbiBpcyB0byB0YWtlIFJG
QzQ5NDEgdG8gSW50ZXJuZXQgU3RhbmRhcmQgdW5jaGFuZ2VkLjxicj4NCkEgcXVlc3Rpb24gd2Fz
IHJhaXNlZCBpZiA0OTQxIHJlcXVpcmVzIHB1YmxpYyBhZGRyZXNzZXMgb3Igbm90LCBhbmQgaWYg
d2UgaGF2ZSB0byB1cGRhdGUgNDk0MSB0ZXh0LCBvciBpZiB3ZSBjYW4gbGl2ZSB3aXRoIHRoZSBj
dXJyZW50IHRleHQsIGFuZCBzdGlsbCBhbGxvdyBmb3IgaW50ZXJmYWNlcyB3aXRoIG9ubHkgdGVt
cG9yYXJ5IGFkZHJlc3Nlcy48YnI+DQo8YnI+DQpPcGluaW9ucz88YnI+DQo8YnI+DQpCZXN0IHJl
Z2FyZHMsPGJyPg0KT2xlPGJyPg0KPGJyPg0KJmd0OyBPbiAxNyBNYXkgMjAxNiwgYXQgMjA6MTUs
IEZlcm5hbmRvIEdvbnQgJmx0OzxhIGhyZWY9Im1haWx0bzpmZXJuYW5kb0Bnb250LmNvbS5hciI+
ZmVybmFuZG9AZ29udC5jb20uYXI8L2E+Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7PGJyPg0KJmd0OyBM
b3JlbnpvIChhbmQgd2cpLDxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZSB0d28gaXNzdWVzIHJhaXNl
ZCBieSBMb3JlbnpvIHJlZ2FyZGluZyBkZWZhdWx0LWlpZHMgYm9pbCBkb3duIHRvOjxicj4NCiZn
dDs8YnI+DQomZ3Q7IDEpIFRoZSBhYmlsaXR5IHRvIGVtYmVkIE1BQyBhZGRyZXNzZXMgaW4gdGhl
IElJRDxicj4NCiZndDs8YnI+DQomZ3Q7IDIpIFRoZSByZXF1aXJlbWVudCB0byBoYXZlIHN0YWJs
ZSBhZGRyZXNzZXM8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgVGhpcyBkb2N1bWVudCBk
b2VzIGJhbiAmcXVvdDsxKSZxdW90OyBhcyB0aGUgZGVmYXVsdCBhbGdvcml0aG0gZm9yIGdlbmVy
YXRpbmc8YnI+DQomZ3Q7IElJRHMsIGZvciB0aGUgcmVhc29ucyBkaXNjdXNzZWQgaW4gUkZDNzcy
MSBhbmQ8YnI+DQomZ3Q7IGRyYWZ0LWdvbnQtcHJlZGljdGFibGUtbnVtZXJpYy1pZHMuIFdlIGhh
dmUgYSB2ZXJ5IGxvbmcgaGlzdG9yeSBvZjxicj4NCiZndDsgaW1wcm9wZXIgbnVtZXJpYyBJRHMs
IGFuZCBJIGd1ZXNzIHRoYXQsIHJlZ2FyZGluZyB0aGlzIG9uZSwgd2Ugc2ltcGx5PGJyPg0KJmd0
OyBkaXNhZ3JlZSB3aXRoIExvcmVuem8uPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IFJl
Z2FyZGluZyAmcXVvdDsyKSZxdW90OywgdGhpcyBkb2N1bWVudCBkb2VzIG5vdCBzcGVjaWZ5IGFu
eSBuZXcgcmVxdWlyZW1lbnRzIG9uPGJyPg0KJmd0OyB0aGUgdG9waWMuIEVzc2VudGlhbGx5LCBu
b2RlcyBhcmUgaW1wbGllZCB0byBjb25maWd1cmUgYSBzdGFibGU8YnI+DQomZ3Q7IGFkZHJlc3Nl
cyBhcyBhIHJlc3VsdCBvZiBTTEFBQyZhbXA7dHJhZGl0aW9uYWwgbGluay1sYXllciBhZGRyZXNz
PGJyPg0KJmd0OyBwcm9wZXJ0aWVzLCBhbmQgbW9yZSBleHBsaWNpdGx5IGJ5IHRoaXMgdGV4dCBp
biBSRkM0OTQxOjxicj4NCiZndDs8YnI+DQomZ3Q7ICogU2VjdGlvbiAzLCBidWxsZXQgIzE6PGJy
Pg0KJmd0OyZuYnNwOyAmbmJzcDsyLiZuYnNwOyBDcmVhdGUgYWRkaXRpb25hbCBhZGRyZXNzZXMg
YmFzZWQgb24gYSByYW5kb20gaW50ZXJmYWNlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwO2lkZW50aWZpZXIgZm9yIHRoZSBwdXJwb3NlIG9mIGluaXRpYXRpbmcgb3V0Z29pbmcg
c2Vzc2lvbnMuPGJyPg0KJmd0Ozxicj4NCiZndDsgKiBTZWN0aW9uIDMuMywgYnVsbGV0ICMxOjxi
cj4NCiZndDsmbmJzcDsgJm5ic3A7MS4mbmJzcDsgUHJvY2VzcyB0aGUgUHJlZml4IEluZm9ybWF0
aW9uIE9wdGlvbiBhcyBkZWZpbmVkIGluIFtBRERSQ09ORl0sPGJyPg0KJmd0OyZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwO2VpdGhlciBjcmVhdGluZyBhIG5ldyBwdWJsaWMgYWRkcmVzcyBvciBh
ZGp1c3RpbmcgdGhlIGxpZmV0aW1lczxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDtvZiBleGlzdGluZyBhZGRyZXNzZXMsIGJvdGggcHVibGljIGFuZCB0ZW1wb3JhcnkuPGJyPg0K
Jmd0Ozxicj4NCiZndDsgKiBTZWN0aW9uIDMuMywgYnVsbGV0ICMzOjxicj4NCiZndDsmbmJzcDsg
Jm5ic3A7My4mbmJzcDsgV2hlbiBhIG5ldyBwdWJsaWMgYWRkcmVzcyBpcyBjcmVhdGVkIGFzIGRl
c2NyaWJlZCBpbiBbQUREUkNPTkZdLDxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDt0aGUgbm9kZSBTSE9VTEQgYWxzbyBjcmVhdGUgYSBuZXcgdGVtcG9yYXJ5IGFkZHJlc3MuPGJy
Pg0KJmd0Ozxicj4NCiZndDsgKiBTZWN0aW9uIDMuNiwgZm9yIGluc3RhbmNlLCBzYXlzIChldmVu
IHJlY29tbWVuZGluZyB0aGF0IHRlbXAgYWRkcnM8YnI+DQomZ3Q7IGRlZmF1bHQgdG8gJnF1b3Q7
b2ZmJnF1b3Q7KTo8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwO1RoZSB1c2Ugb2YgdGVtcG9yYXJ5IGFk
ZHJlc3NlcyBtYXkgY2F1c2UgdW5leHBlY3RlZCBkaWZmaWN1bHRpZXMgd2l0aDxicj4NCiZndDsm
bmJzcDsgJm5ic3A7c29tZSBhcHBsaWNhdGlvbnMuJm5ic3A7IEFzIGRlc2NyaWJlZCBiZWxvdywg
c29tZSBzZXJ2ZXJzIHJlZnVzZSB0byBhY2NlcHQ8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwO2NvbW11
bmljYXRpb25zIGZyb20gY2xpZW50cyBmb3Igd2hpY2ggdGhleSBjYW5ub3QgbWFwIHRoZSBJUCBh
ZGRyZXNzPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDtpbnRvIGEgRE5TIG5hbWUuJm5ic3A7IEluIGFk
ZGl0aW9uLCBzb21lIGFwcGxpY2F0aW9ucyBtYXkgbm90IGJlaGF2ZTxicj4NCiZndDsmbmJzcDsg
Jm5ic3A7cm9idXN0bHkgaWYgdGVtcG9yYXJ5IGFkZHJlc3NlcyBhcmUgdXNlZCBhbmQgYW4gYWRk
cmVzcyBleHBpcmVzPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDtiZWZvcmUgdGhlIGFwcGxpY2F0aW9u
IGhhcyB0ZXJtaW5hdGVkLCBvciBpZiBpdCBvcGVucyBtdWx0aXBsZTxicj4NCiZndDsmbmJzcDsg
Jm5ic3A7c2Vzc2lvbnMsIGJ1dCBleHBlY3RzIHRoZW0gdG8gYWxsIHVzZSB0aGUgc2FtZSBhZGRy
ZXNzZXMuPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDtDb25zZXF1ZW50bHksIHRoZSB1c2Ugb2YgdGVt
cG9yYXJ5IGFkZHJlc3NlcyBTSE9VTEQgYmUgZGlzYWJsZWQgYnk8YnI+DQomZ3Q7Jm5ic3A7ICZu
YnNwO2RlZmF1bHQgaW4gb3JkZXIgdG8gbWluaW1pemUgcG90ZW50aWFsIGRpc3J1cHRpb25zLjxi
cj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgT3VyIGRvY3VtZW50IHNpbXBs
eSByZXF1aXJlcyBpbXBsZW1lbnRhdGlvbnMgdGhhdCB0aGVpcjxicj4NCiZndDsgc3RhYmxlIGFk
ZHJlc3NlcyBhcmUgUkZDNzcyMS1mcmllbmRseS4gQnV0IGlmIGFueXRoaW5nLCB0aGUgcmVxdWly
ZW1lbnQ8YnI+DQomZ3Q7IG9mIHdoZXRoZXIgdG8gaGF2ZSBhIHN0YWJsZSBhZGRyZXNzIG9yIG5v
dCBpcyBub3Qgc29tZXRoaW5nIGludHJvZHVjZWQ8YnI+DQomZ3Q7IGJ5IG91ciBkb2N1bWVudC48
YnI+DQomZ3Q7PGJyPg0KJmd0OyBBcyBhIGNvLWF1dGhvciBvZiBkcmFmdC1pZXRmLTZtYW4tZGVm
YXVsdC1paWRzLCBJIGp1c3Qgd2FudGVkIHRvIGNoZWNrPGJyPg0KJmd0OyB0aGF0IHdlJ3JlIG9u
IHRoZSBzYW1lIHBhZ2UsIGJlY2F1c2UgSSBoYXZlIHRoZSBmZWVsaW5nIHRoYXQgdGhlIGFib3Zl
PGJyPg0KJmd0OyBrZWVwcyBnZXR0aW5nIG1pc2ludGVycHJldGVkLjxicj4NCiZndDs8YnI+DQom
Z3Q7IEkgYmVsaWV2ZSBhbGwgb2YgdGhlIGNvLWF1dGhvcnMgb2YgZGVmYXVsdC1paWRzIGFncmVl
IGFuZCB1bmRlcnN0YW5kPGJyPg0KJmd0OyB0aGF0IHRoZXJlIGNhbiBiZSBzY2VuYXJpb3Mgd2hl
cmUgeW91IG1heSB3YW50IHRvIGRvPGJyPg0KJmd0OyB0ZW1wb3JhcnktYWRkcmVzc2VzLW9ubHku
IEhvd2V2ZXIsIHRoYXQgaXMgb3J0aG9nb25hbCB0byB0aGlzIHBhcnRpY3VsYXI8YnI+DQomZ3Q7
IGRvY3VtZW50IChkZWZhdWx0LWlpZHMpLCBhbmQgd291bGQgcHJvYmFibHkgcmVxdWlyZSBhbiB1
cGRhdGUgdG88YnI+DQomZ3Q7IFJGQzQ5NDEsIHN1Y2ggdGhhdCB0ZW1wb3JhcnkgYWRkcmVzc2Vz
IGNhbiBiZSBlbXBsb3llZCBhcyBhIHJlcGxhY2VtZW50PGJyPg0KJmd0OyBvZiBzdGFibGUgYWRk
cmVzc2VzLCByYXRoZXIgdGhhbiBhcyBzb21ldGhpbmcgdGhhdCB5b3UgZG8gJnF1b3Q7aW4gYWRk
aXRpb248YnI+DQomZ3Q7IHRvJnF1b3Q7IHRoZW0uPGJyPg0KJmd0Ozxicj4NCiZndDsgVGhpcyBk
b2N1bWVudCBpcyBhYm91dCBob3cgdG8gZG8gc3RhYmxlIGFkZHJlc3NlcyBpbiBhIG1vcmU8YnI+
DQomZ3Q7IFJGQzc3MjEtZnJpZW5kbHkgd2F5IHRoYW4gd2UgY3VycmVudGx5IGRvLjxicj4NCiZn
dDs8YnI+DQomZ3Q7IFRoYW5rcyE8YnI+DQomZ3Q7PGJyPg0KJmd0OyBCZXN0IHJlZ2FyZHMsPGJy
Pg0KPHNwYW4gY2xhc3M9ImhvZW56YiI+PHNwYW4gc3R5bGU9ImNvbG9yOiM4ODg4ODgiPiZndDsg
LS08L3NwYW4+PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48YnI+DQo8c3BhbiBj
bGFzcz0iaG9lbnpiIj4mZ3Q7IEZlcm5hbmRvIEdvbnQ8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9
ImhvZW56YiI+Jmd0OyBlLW1haWw6IDxhIGhyZWY9Im1haWx0bzpmZXJuYW5kb0Bnb250LmNvbS5h
ciI+ZmVybmFuZG9AZ29udC5jb20uYXI8L2E+IHx8DQo8YSBocmVmPSJtYWlsdG86ZmdvbnRAc2k2
bmV0d29ya3MuY29tIj5mZ29udEBzaTZuZXR3b3Jrcy5jb208L2E+PC9zcGFuPjxicj4NCjxzcGFu
IGNsYXNzPSJob2VuemIiPiZndDsgUEdQIEZpbmdlcnByaW50OiA3ODA5IDg0RjUgMzIyRSA0NUM3
IEYxQzkgMzk0NSA5NkVFIEE5RUYgRDA3NiBGRkYxPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJo
b2VuemIiPiZndDs8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9ImhvZW56YiI+Jmd0Ozwvc3Bhbj48
YnI+DQo8c3BhbiBjbGFzcz0iaG9lbnpiIj4mZ3Q7PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJo
b2VuemIiPiZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9ImhvZW56YiI+
Jmd0OyBJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyPg0KPHNw
YW4gY2xhc3M9ImhvZW56YiI+Jmd0OyA8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2
NkBpZXRmLm9yZzwvYT48L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9ImhvZW56YiI+Jmd0OyBBZG1p
bmlzdHJhdGl2ZSBSZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pcHY2IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2lwdjY8L2E+PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJob2VuemIi
PiZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_DM2PR0301MB0717D5EA3FD289A7894E3AC0A3490DM2PR0301MB0717_--


From nobody Wed May 18 10:55:25 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 0DBBF12D624 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 10:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 ZmG6bg9W_ZTh for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 10:55:09 -0700 (PDT)
Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::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 A02EE12D5F0 for <ipv6@ietf.org>; Wed, 18 May 2016 10:55:08 -0700 (PDT)
Received: by mail-ig0-x230.google.com with SMTP id qe5so95321448igc.1 for <ipv6@ietf.org>; Wed, 18 May 2016 10:55:08 -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:date:message-id:subject :from:to:cc; bh=n1k7jc/VTDhUbDBJKE38+lyX8nHnoudi1tp5ntFym9o=; b=DhOyfgds4I0n7T/7dViPb0SDFmcJYiDF7XGH8NxDnqiwk05DaHK2caPYy/po7o6aCT Wiudulpz8ZTQJetghBH5Ab37McvDHj9d75U81fcoq7WPvhesm/SMDtiee9y4NlgsIX/5 4IRz+CZOofPVjQCh7sUjrH0zbZ/h6Hor+D8jJYyri8N2Vyb6/EG+d200DXi7+UXytYcJ r9v915f5Ay3XS7zchAFHIkD+gxwiuWSFI6Wedw/Cemv35B5YbhEwJQQ9Nhncbp2fUirF bOalYU986+J38MWSB9AzebyrpO6dru29KGkTdSc764q1BMR7keyW005rky24+V4VYSag gZ/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:date :message-id:subject:from:to:cc; bh=n1k7jc/VTDhUbDBJKE38+lyX8nHnoudi1tp5ntFym9o=; b=eWsGVcVjwMENIsP8hzfv4/OVJDsxPX7QyNQCBKBcR25mlBbtNSVYtX6LrRur3uwG2x 7jB4Bwm9Rg8Emd4pEQMOTf1zGK8QL2auIryzEylBwLl/qK64BNLU24uD4AN+Mc7Ffeff xXBNO32crrRNCs6wKzwvQbcBnHh5RCZmvgnauMdgk5VSb/fSEFkrUr/T+nXf8nAXl+Bu 8meUHpoPoK+H8voWF/nSVEn/MdCO1z5J2YorJaJRD09yu+m1ziVAp1nLR0vpoQ6vRBjV xwOcY6DUaORGndyyKJqQg0gyEnkFtNHHTjRAsnX/UkBSqqEwMlu8DL4uOR1bUBrMvrzB 7teQ==
X-Gm-Message-State: AOPr4FVugZa+eKCdXS4J5zZSWme7cINjoGuiC+b6+7n5BDJt+0pG8OYdV+udyuvbtAtCaO1v30v6yCbyXKXfzQ==
MIME-Version: 1.0
X-Received: by 10.50.160.41 with SMTP id xh9mr6303635igb.64.1463594108020; Wed, 18 May 2016 10:55:08 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Wed, 18 May 2016 10:55:07 -0700 (PDT)
In-Reply-To: <573B36D3.8010502@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <573B36D3.8010502@si6networks.com>
Date: Wed, 18 May 2016 10:55:07 -0700
X-Google-Sender-Auth: yI5lIxqeIa56N7qcBxsk77hp1PM
Message-ID: <CAJE_bqfy5tMA1xu1w5g+vx8nJfDQe4zz6BbDQes42wdtmj_hHg@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jXHAdTK6gQziBig4UGe8T-qkN90>
Cc: IPv6 List <ipv6@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, 18 May 2016 17:55:12 -0000

At Tue, 17 May 2016 11:20:51 -0400,
Fernando Gont <fgont@si6networks.com> wrote:

> There are multiple reasons for which that is the wrong approach and/or
> incorrect.
>
> They are stated in the I-D as:
>    More generally, the reuse of identifiers that have their own
>    semantics or properties across different contexts or scopes can be
>    detrimental for security and privacy
>    [I-D.gont-predictable-numeric-ids].  In the case of traditional
>    stable IPv6 IIDs, some of the security and privacy implications are
>    dependent on the properties of the underlying link-layer addresses
>    (e.g., whether the link-layer address is ephemeral or randomly
>    generated), while other implications (e.g., reduction of the entropy
>    of the IID) depend on the algorithm for generating the IID itself.

I know there's this text, but it's too vague to me to interpret it as
this draft tries to reject the concern.  That's why I've been asking
the intent of the draft several times.  And this vagueness is the main
point of mine, rather than the specific claims themselves.  So I'm
not going to respond to each defense arguments for the claims, but
rather focusing on the higher level point: to me, the current form of
draft is vague about the following two points:

1. Whether it assumes (or introduces itself) that a stable address is
   required to be configured (banning non-stable only operation).
2. Whether the case where "link-layer addresses" are randomized is
   also covered by this draft (in that it prohibits embedding such
   addresses in IID)

According to the discussion in this thread, my latest understanding is
that the answer is "yes" to both points.  In that case, I'd then
request these points to be stated more explicitly and clearly in the
draft, and see clear wg consensus on these points.

I myself don't have a strong opinion (yet) on these points, but I see
some controversy in the wg.  For example, some responses in the latest
sub-thread on RFC4941 seem to indicate opinions on point #1 vary (and
some people even say RFC4941 does not necessarily require a public
address).  I also see that some people think that point #2 can be
loosened so that it only covers "permanent-and-predictable link-layer
addresses".  So I don't think we have a clear wg consensus on these
yet.  And, if this draft tries to achieve something that relies on
these points, IMO it can't pass the wg last call yet.


> > And, one other point I want to be addressed: in Section 4 it states:
> >
> >    By default, DHCPv6 server implementations SHOULD NOT generate
> >    predictable IPv6 addresses (such as IPv6 addresses where the IIDs are
> >    consecutive small numbers).  [I-D.ietf-dhc-stable-privacy-addresses]
> >    specifies one possible algorithm that could be employed to comply
> >    with this requirement.  Another possible algorithm would be to select
> >    a pseudo-random value chosen from a discrete uniform distribution,
> >    while avoiding the reserved IPv6 Interface Identifiers [RFC5453]
> >    [IANA-RESERVED-IID].
> >
> >  I suggest just removing the second sentence.
> >  ietf-dhc-stable-privacy-addresses is not a dhc wg item anymore due to
> >  some controversy, and it's not clear what will happen to its
> >  successor in the form of individual submission:
> >  draft-gont-dhcpv6-stable-privacy-addresses-01
> >  Since this sentence is only to show an example, just showing the
> >  "another possible algorithm" would suffice.
>
> I will check what the status of the corresponding draft-gont version of
> the I-D is. To the extent that is possible, I'd keep it, since
> ietf-dhc-stable-privacy-addresses leads to stable addresses, while a
> simple randomization scheme doesn't.

This logic seems awkward to me.  For
draft-gont-dhcpv6-stable-privacy-addresses-01 to be a better example
despite its uncertain future for that reason, I'd expect the stability
is also included in the updated text of RFC3315.  Otherwise, just
showing a simple randomization is a far better example since it
exactly meets the revised text.  I'd also note another recent trend in
dhc, where randomizing DUID may become a new norm as described in
RFC7844 (a standards track RFC).  Since the stability of
draft-gont-dhcpv6-stable-privacy-addresses depends on the stability of
DUID, the stability argument doesn't hold for client implementations
supporting and enabling RFC7844.

For all these reasons, I'd still suggest just removing the reference.
But if the idea of draft-gont-dhcpv6-stable-privacy-addresses is too
loved to be removed, my secondary suggestion is to move it to an
auxiliary example after the simple randomization, noting that it's
listed because it has an additional property of stability and that it
has a limitation that it's not compatible with RFC7844.

--
JINMEI, Tatuya


From nobody Wed May 18 11:10:00 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 303C812D620 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 11:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 e1i1_D7yEQpQ for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 11:09:58 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::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 D617612D5FB for <6man@ietf.org>; Wed, 18 May 2016 11:09:57 -0700 (PDT)
Received: by mail-ig0-x232.google.com with SMTP id s8so31860411ign.0 for <6man@ietf.org>; Wed, 18 May 2016 11:09:57 -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:date:message-id:subject :from:to:cc; bh=jamfIgv8GrGLGbYqoCkYgcFcWYm1734XqTVyDMAHuTs=; b=gqtJ2EDaDvJqTc1AC6TTXNt2Sw0R0wstAeGxZqpiBbhl3Vunp8b4f7eW0B50rbFWWv ZiwCqZUng5kY82kSmnmyqG3tf/ptvQytkV41zX2F2kZJS5M+/8PMdjtqUB4jDn48Wahd uMOoGXlC9i07OKugXG4/u7PAi5wrOdErokZcjXe4FWPOwJNoq76l3VN4yM5iIy8TAGHw nwrhcjLMJwlTHRrDz7Bh+F+Q6XIujgke7TqacRO/P3HDzneK27sWucBe+sziTLFcsl23 C40+3z3SkyKIrA42Ef8Ht72A/BSMMyzRF4AIpxK//YAI257/FNsg/1qAGAWj8W2wkyGv PCdQ==
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:date :message-id:subject:from:to:cc; bh=jamfIgv8GrGLGbYqoCkYgcFcWYm1734XqTVyDMAHuTs=; b=dL3Lg+J8Ax1MtEnOmoq7rSij71BMVdi4MN7szTNyB2C1s3Z0WRMqKI/fWAvGiljZOe bMqjpDlNJPkQG26veKQnPFE17y6odLEA3BBUlB5vDGAnQ38J1aAwPZeesmhH6/CunExP rOS57D+s8o+1aFDQlSJdhDu4IER7iEP+gUbdYmIURLFz3rVo7eJ/WUIv15md/ZUajsxn 0ZLsCej7L0f6SO1lqkrmo39eqhzizuo6rpv/bRP8Agglldy2oem+hNyGTIVfPzjYvY0R JQg/MlILH/jnaaF0gXo62+KbqYBsaMG1JYozsyMs0+1Nqjw/F0WWFrXIMHwacoapN2b7 /2Kg==
X-Gm-Message-State: AOPr4FW1pSzMZ6lB82Rhu1EI8Zyit9nZ9DbJH+P1qe+KNHD4YMpYE2PUgHfIg3ZSV9KHddSFOB75dd/81luIkg==
MIME-Version: 1.0
X-Received: by 10.50.160.41 with SMTP id xh9mr6366074igb.64.1463594997266; Wed, 18 May 2016 11:09:57 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Wed, 18 May 2016 11:09:57 -0700 (PDT)
In-Reply-To: <573B5FAC.7060300@gont.com.ar>
References: <573B5FAC.7060300@gont.com.ar>
Date: Wed, 18 May 2016 11:09:57 -0700
X-Google-Sender-Auth: onkFqHKTcEtRXNs7ijMtxzB0pMU
Message-ID: <CAJE_bqdXt_jC2GCc-SRXAfRTybYd88ZdSMpnny2oJUMnscnyOQ@mail.gmail.com>
Subject: Re: default-iids and stable addresses
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fernando@gont.com.ar>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uU59MMjxulrfreRAvrmV6pieeGs>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 18 May 2016 18:10:00 -0000

At Tue, 17 May 2016 14:15:08 -0400,
Fernando Gont <fernando@gont.com.ar> wrote:

> The two issues raised by Lorenzo regarding default-iids boil down to:
>
> 1) The ability to embed MAC addresses in the IID
>
> 2) The requirement to have stable addresses

[...]

> Our document simply requires implementations that their
> stable addresses are RFC7721-friendly. But if anything, the requirement
> of whether to have a stable address or not is not something introduced
> by our document.
>
> As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> that we're on the same page, because I have the feeling that the above
> keeps getting misinterpreted.

Misinterpretation (I'd call it confusion in this context, though) of a
document often happens because the document isn't clear enough, rather
than because there's an issue at the readers' side (as the wording
"getting misinterpreted" seems to indicate).  And I think that's
actually what's happening for this document right now.  In fact, it's
not clear at least to me from the current draft how it answers the
above two points.  Its current vagueness may come from attempts of
addressing previous controversy, but, for this fresh reader of the
document, the resulting text is very confusing.

--
JINMEI, Tatuya


From nobody Wed May 18 14:43:26 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 5B54A12D770 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 14:43:24 -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 fp_-cV9DSv0M for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 14:43:22 -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 27D3412D773 for <ipv6@ietf.org>; Wed, 18 May 2016 14:43:22 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id y69so22385318pfb.1 for <ipv6@ietf.org>; Wed, 18 May 2016 14:43:22 -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=Ccbtp/Eu7Hrynwjx964mvVHPSoz7hjokL5fpoRX4qG4=; b=hkVa6+Xdu/rAuhYUg0ZzxbYvE32uJv7MX5rpnt9OoCxTB/YZprSu/p7pGUVX/r2PFl 1Z6oMGIWB/TOHrL1yjGwaOsYbonADrwizl/+zGk0ef4r/IRPlvSK1RxHShaZMdF/RW45 SjFoGdmVe8tiQyDvlIPLFTPZDVW5JMwD//WVtwQL0uQmF6h9Sl8IB1yWoUuhm0Tkf4sL IEgrN1HwoNQC6onNXVLu1g23NuHDMAwmwGMjDC3RxEPDu+p3T3jwdJuHX/lfOrCGrG89 RTjJnv+IWV8d6Hra/arF7/6wIyXmC6LgDkZ/0s4xtsmNJz3Ra37raVSy93wW7hsipznY h7Mw==
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=Ccbtp/Eu7Hrynwjx964mvVHPSoz7hjokL5fpoRX4qG4=; b=EKErvL6c8wLQg1x3JQWz2xpnOYUwm1/5Cq3Sqwephe9+hqsQC7Lt7A32RXYStAkS9a C7esiVrjSZWCYqJLqr1pGFDjia+dzZ+H8Y2FmmqihE4A/fxWnNPpqKIJsr48Ec80QjgE y6IOLt7a+MDVANYJPlst4M7z16Us9IbmdKDaxtPNjhVa89Sj7xK+JesGud4nKDG3a/6H MTLRTGmdWAjaxFSo9XCrevlFjdnT8DTGu6EzJVEIZbrcbu0Qzzfp6DCaim9jqB0jTmy8 tSuIu2NhDUdmSlD1Mr0lvqHHWEw0fhTWHl6VYR2W290vQSxWG5A1JsDTV/Volv/k9DBe tDag==
X-Gm-Message-State: AOPr4FXpXsNQgmpMhOj+M7rK7XlVlA56hhL3Xkjm8IjyXl5rsEZ2vjOMD/1QCzXSN5pQHg==
X-Received: by 10.98.65.90 with SMTP id o87mr14022962pfa.151.1463607801684; Wed, 18 May 2016 14:43:21 -0700 (PDT)
Received: from ?IPv6:2406:e007:6b9a:1:28cc:dc4c:9703:6781? ([2406:e007:6b9a:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id xn3sm14483720pab.32.2016.05.18.14.43.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 May 2016 14:43:19 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Fernando Gont <fgont@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <573B36D3.8010502@si6networks.com> <CAJE_bqfy5tMA1xu1w5g+vx8nJfDQe4zz6BbDQes42wdtmj_hHg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1e71de8d-3f59-eba3-6d86-c8d04c175523@gmail.com>
Date: Thu, 19 May 2016 09:43:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqfy5tMA1xu1w5g+vx8nJfDQe4zz6BbDQes42wdtmj_hHg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ncgh7gJ2DGREsPPRzq1C46Ws_jg>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 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, 18 May 2016 21:43:25 -0000

Hi,
On 19/05/2016 05:55, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
=2E..
> ...but
> rather focusing on the higher level point: to me, the current form of
> draft is vague about the following two points:
>=20
> 1. Whether it assumes (or introduces itself) that a stable address is
>    required to be configured (banning non-stable only operation).

I think this draft is correct to leave this question open. It's
a deployment decision which will be very different for (e.g.) a
tablet connected for half an hour in a coffee shop versus a desktop
connected indefinitely in an office of a large enterprise.

> 2. Whether the case where "link-layer addresses" are randomized is
>    also covered by this draft (in that it prohibits embedding such
>    addresses in IID)

I agree, I think the text should allow (but not require) the traditional
form of modified EUI-64 in the case of pseudo-random MAC addresses.

    Brian


From nobody Wed May 18 15:51:20 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 BC76612D79E for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 CFCHCTD3nTAk for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:16 -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 5240612D79D for <ipv6@ietf.org>; Wed, 18 May 2016 15:51:16 -0700 (PDT)
Received: from [100.92.254.184] (unknown [152.206.74.129]) (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 7DF4F80257; Thu, 19 May 2016 00:51:12 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alissa Cooper <alissa@cooperw.in>, Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573BD0E3.4030407@si6networks.com>
Date: Tue, 17 May 2016 22:18:11 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PT6TvBN239RlaYP51EFQ0b_0nY0>
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, 18 May 2016 22:51:18 -0000

On 05/16/2016 01:29 PM, Alissa Cooper wrote:
>>
>> Either we fix that or we stop asserting that this draft is motivated
>> by privacy considerations.
> 
> I would frankly be thrilled if we could get away from stable addresses
> altogether. But I’m skeptical about the feasibility of achieving
> consensus around that at present. Defining the approach in this draft in
> the meantime is certainly motivated by consideration for privacy
> improvement for me, even if that improvement is incremental.

There are scenarios in which you simply don't want that.

It might be desirable in the "roaming" case, but certainly not in others
(that's why RFC4941 keeps being disabled in enterprise deployments, for
instance).

Side note: Curiously enough, I'm told that:

* Some folks ding MAC address randomization randomize the layer-2
address when prbing networks, but employ a real address when associating
with the AP.

* OTOH, other folks implement RFC7217-like scheme for layer-2, but
rather than getting the RFC7217 outcome statelesly, they keep track of
networks visited, and the MAC addresses employed in each of them.

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





From nobody Wed May 18 15:51:23 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 090E512D79D for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 GPspFxa2qGHa for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:16 -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 16E3512D79C for <ipv6@ietf.org>; Wed, 18 May 2016 15:51:15 -0700 (PDT)
Received: from [100.92.254.184] (unknown [152.206.74.129]) (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 2E9EA800EF; Thu, 19 May 2016 00:51:05 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573BCFD0.8090801@si6networks.com>
Date: Tue, 17 May 2016 22:13:36 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lvnPGlEKTZKhikg_3PQfvlJqxj4>
Cc: IPv6 List <ipv6@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, 18 May 2016 22:51:18 -0000

On 05/16/2016 01:25 PM, ç¥žæ˜Žé�”å“‰ wrote:
> 
>>> - clarify that this recommendation is only for environments where
>>>  address stability is needed
>>
>> The document says exactly this in the introduction:
>>
>> The recommendations in this document apply only in cases where
>>    implementations otherwise would have configured a stable IPv6 IID
>>    containing a link layer address.  That is, this document does not
>>    change any existing recommendations concerning the use of temporary
>>    addresses as specified in [RFC4941 <https://tools.ietf.org/html/rfc4941>], nor does it introduce any new
>>    requirements regarding when stable addresses are to be configured.
>>    Thus, the recommendations in this document simply improve the
>>    security and privacy properties of stable addresses.
> 
> This text specifically talks about RFC4941 as the "environments where
> address stability is NOT needed",

Please let me clarify this.

IPv6 nodes employ, by default, stable addresses. The only standardized
things that's different from that is temporary addresses, which
essentially specify how to generate temporary addresses *in addition* to
the stable ones.

If you want to do temporary-addresses-only, you need to update RFC4941,
because it says that you should have both stable and temporary addresses.

What we say in our document is: "where you'd configure a stable
addresses, do RFC7217 rather than embed link-layer addresses". We do not
argue whether you should have/use stable addresses in the first place.
Such requirements are elsewhere, and not in this document.


>  and, with the 'That is,' only talks
> about it.  On the other hand, my understanding of previous concerns in
> this context is to also cover other types of such environments,
> specifically the one using randomized link-layer addresses with the
> traditional algorithm of forming the IID from such LL addresses.
> 
>>From this one, and your response to the next point, it seems you are
> saying the decision was to refuse to address that concern.  Am I
> understanding it correctly?

No. My take is that the concern is flawed. Please read
draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
length about security and privacy issues regarding reusing identifiers
in different context, for different scopes, etc.

Let's call a lemon a lemon: Asking to embed a layer-2 identifier/address
in a layer-3 address is extremely bad.

After 30+ years of experience with flaws related to improper selection
of numeric identifiers, it's really bad that people keep pushing this
sort of thing.


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





From nobody Wed May 18 15:51: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 5C74012D7B3 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 fAsHUwUcCMFQ for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:21 -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 5F0E412D7A6 for <ipv6@ietf.org>; Wed, 18 May 2016 15:51:21 -0700 (PDT)
Received: from [100.92.254.184] (unknown [152.206.74.129]) (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 7D3B48026F; Thu, 19 May 2016 00:51:18 +0200 (CEST)
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, weigengyu <weigengyu@bupt.edu.cn>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC> <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC> <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573BD140.8000607@si6networks.com>
Date: Tue, 17 May 2016 22:19:44 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EQem3Xod70zcyeTdi_G5taAR_9k>
Cc: 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, 18 May 2016 22:51:22 -0000

On 05/16/2016 04:08 PM, Brian E Carpenter wrote:
> Hi Gengyu,
> 
>>> RID is not random or random identifier according to the context above.
>>>
>>> F() is an inreverse function, not a pseudorandom function.
> 
> I agree that this is incorrect use of terminology; an irreversible hash is
> not mathematically equivalent to a pseudo-random number generator. But the
> effect is the same: an attacker has no way to predict the next F(x) or to
> obtain the value of x. As far as practical engineering goes, F() can be treated
> as a random number. So I don't see why this invalidates the use of RFC 7217.
> 
> You could submit an erratum for RFC 7217 at http://www.rfc-editor.org/errata.php#reportnew
> so that the terminology can be corrected when the document is updated.

FWIW, the term "PRF" (as *opposed*) to PRNG was suggested by Alfred
Hoenes -- IIRC, a mathematician. IIRC, he noted that a hash function is
simply one possible way of a PRF.


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





From nobody Wed May 18 15:51:42 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 A506F12D7BB for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 52R5BiDaGQIG for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 15:51:30 -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 AFFA612D7B0 for <ipv6@ietf.org>; Wed, 18 May 2016 15:51:29 -0700 (PDT)
Received: from [100.92.254.184] (unknown [152.206.74.129]) (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 55D3E80324; Thu, 19 May 2016 00:51:24 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <04271b8d-efc9-7a3f-6200-42cbc3daf919@gmail.com> <bf8f2c4a42a14ce7a8dca1ade97e6963@XCH15-06-11.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573BD264.6070604@si6networks.com>
Date: Tue, 17 May 2016 22:24:36 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <bf8f2c4a42a14ce7a8dca1ade97e6963@XCH15-06-11.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ESlXtgfryS0BdoomvvonH4xfydY>
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, 18 May 2016 22:51:32 -0000

Hi, Bert,

Thanks for the note. Comments in-line...

On 05/16/2016 05:38 PM, Manfredi, Albert E wrote:
> 
> And also, let's not forget that IP nets are not used exclusively for consumer oriented appliances. In addition to enterprise nets, which have different criteria from private users over ISPs, there are control system networks. On factory floors, in all manner of vehicles, and so on. Networks running machinery, providing navigation data, and on and on.
> 
> Privacy of an individual user, or of an individual host, is exactly what these networks cannot allow. So no, I don't see a future in which there are no stable addresses.

That's what this document is all about: to improve stable addresses such
that, from an operational pov, they are still stable, while they prevent
address scanning and network tracking.

We do not mandate thier use. We just say that, by default, folks should
stop using a scheme with known flaws.

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 Wed May 18 16:22:28 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 7FCDB12B04E for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 16:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 6-zekIKPC6fV for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 16:22:26 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 394D212B046 for <ipv6@ietf.org>; Wed, 18 May 2016 16:22:26 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id d62so85765383iof.2 for <ipv6@ietf.org>; Wed, 18 May 2016 16:22:26 -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:date:message-id:subject :from:to:cc; bh=tpi63uaZR577z1tIGhstwJM2LIjk4Jx58i8fpPkmQIU=; b=ECQi+/WH5S4PJ4gd+NxKrS5q8H6tCX6dvHBkXVehv7tmpXoGmYOtg7mzA5H7TDGdlX tpRqcF/JHSWLysAlLNbmgUGNL9WFyT1WDkqywUkTYIeYTPWB99znZOw6U+v5P8TFUdtF gGefuujejzWyFcYJPWRc42jbUarlI2Z2KXvxMmVHewd466aEbqFFkBeOgpx9ldKxG4qJ Uc99dNM3zclwLeyY2hf3fK7zMClDuGkLOs9DBaKhb5ACSORT4nTbaS3oviqyQOxKvRWC 8PInA+QTggLhI8sDvvHLb9eP62N46Y30WngW7KFIqM8TSvoMRRJA8tKQfUbbNposjm+A hP6Q==
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:date :message-id:subject:from:to:cc; bh=tpi63uaZR577z1tIGhstwJM2LIjk4Jx58i8fpPkmQIU=; b=DK7710gLfAjqgiqEyM0cDtMbL8pOOXyupcUxacitIht91CIE3YSanESfETdR2MrQUb f9BP38jn+T/xTkGEPUQ+Dr4QXAH/sHwG1nDN05Ggq5M65T0sTpdQ9RBnUva0n/Y5sqTC mXWmc4I6wjPlPbUupjecVNFVwWzZBClQ31W7y4QP1M+G05NGyb3vonoDPrswuE38BA/Y x1UJdwRHpiRq+YPEE9eXolX5uZfvdrqi/jxpGKkT2YInrzqZIEG8RUfpRQd0Rmub8HEZ 6vYLoSdYzUn3F2+Qlsh2CTZX/4Qh6M+C9YhWkN2Fp8MPnCwtERI2qq6x3zKqwlISmqlu ng+A==
X-Gm-Message-State: AOPr4FVAiA/R/RjMTOt+gVDSQqT7aPb65SqX5dczrtu3n2WddZroLR+1yfVBQTRCa8+/lu0Q4iNgqRicp4k1mA==
MIME-Version: 1.0
X-Received: by 10.36.54.12 with SMTP id l12mr408870itl.79.1463613745662; Wed, 18 May 2016 16:22:25 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Wed, 18 May 2016 16:22:25 -0700 (PDT)
In-Reply-To: <573BCFD0.8090801@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com>
Date: Wed, 18 May 2016 16:22:25 -0700
X-Google-Sender-Auth: ioETbpQLiMLTHpXDVRyyUkaLHQg
Message-ID: <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sE8iTrFW5F61FUJrcg3ZB9aJ4SQ>
Cc: IPv6 List <ipv6@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, 18 May 2016 23:22:27 -0000

At Tue, 17 May 2016 22:13:36 -0400,
Fernando Gont <fgont@si6networks.com> wrote:

> > From this one, and your response to the next point, it seems you are
> > saying the decision was to refuse to address that concern.  Am I
> > understanding it correctly?
>
> No. My take is that the concern is flawed. Please read
> draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
> length about security and privacy issues regarding reusing identifiers
> in different context, for different scopes, etc.
>
> Let's call a lemon a lemon: Asking to embed a layer-2 identifier/address
> in a layer-3 address is extremely bad.

I don't have a strong position on this matter itself, but my
understanding of the sense of the wg is that this is controversial,
and at least far from a clear consensus.  To repeat myself, *my*
concern on this last call is that it's not even clear, at least to me,
if this draft tries to say embedding a link-layer address is, whether
it's randomized or not, "extremely bad" (and must therefore be
prohibited).  If that's the intent, it should be clearly stated and
backed by a clear consensus from the wg.  Right now I don't see either
such a clear statement or clear wg consensus.

--
JINMEI, Tatuya


From nobody Wed May 18 16:31:24 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 3150412D7C7 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 16:31: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 eBbNLbT0b1rE for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 16:31:20 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::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 8C27A12D7B5 for <ipv6@ietf.org>; Wed, 18 May 2016 16:31:20 -0700 (PDT)
Received: by mail-pa0-x229.google.com with SMTP id qo8so22601105pab.1 for <ipv6@ietf.org>; Wed, 18 May 2016 16:31: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=2a9quUtB17a6cQtEtnUKiCM4G85Ljsn7XfM52MrCt18=; b=me4DHDqTAxTaHHrKT/AUgi+Afb3IdDlEgp0NSew4Vr8BBdI6UGAG2W/GZMelxJCEv9 NXJVpA1wRT5F60YmkdD2n7atzRH/7EtASKScVdM8TCnSRRQ2X4z59s27Kg2D5gm86Sbd 38JgNhAGFUZJ1KYdTRUdTzcfPZ/AULSoKR7f7nnTzsH3mz5u8YFBdpuNo+CUUjZtSyK9 YWiYVc1BEMyAJiYWU94Xrg8yjV0sOtVmHRPt0MVTsXuFGLbsxnneE71TPyrM0JU3pdW1 iLjYLQ90QI97K4TkSmjLPS1kF1y8z0KTrt52DevmgL1Qc0WJTHcJ+nRKcpVqvwxIfSom D/jA==
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=2a9quUtB17a6cQtEtnUKiCM4G85Ljsn7XfM52MrCt18=; b=TDItvsZFEDGcORI+OEDbPevf7pB1uk8HVb6clWJzz1iY8JzAK84GFlSOXlexQrCciw z1OfOt0fqjRMcP/0Mm3uw/TFIAC0NzUNml0XxVNpepBMn0GSOi0KABk9juHO77DGhXE8 41mvEzKO442iErC2khutGyvmyDsoty1TR67IZLhZwuea5pGbnZjGpcOmSq86Ie4N9Auv X1bW5PX1o+dSYuQ/I64hWxbtTdw2Bd+zlL2+QFwIuf+Her+xYrOZrA2L+CI7YGUJn1aX NpFiH4tPxIdkV6O4lt6RZUGPBNlHHGxKCEH+wRaB8t6SOYDRrQzDY1gofn4VNsEGxEnH XBgA==
X-Gm-Message-State: AOPr4FVa/ze+7VBg/us5AcN2LRQpnYTYhQEY+omyTknZi1hLFFXi5VypXnM4TWEWNiTnVg==
X-Received: by 10.67.21.177 with SMTP id hl17mr14675690pad.39.1463614280154; Wed, 18 May 2016 16:31:20 -0700 (PDT)
Received: from ?IPv6:2406:e007:6b9a:1:5483:9b95:28ce:1d34? ([2406:e007:6b9a:1:5483:9b95:28ce:1d34]) by smtp.gmail.com with ESMTPSA id o2sm14710457pfi.85.2016.05.18.16.31.17 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 May 2016 16:31:19 -0700 (PDT)
Subject: Re: RFC4941 text on requirement for public addresses
To: Tim Chown <Tim.Chown@jisc.ac.uk>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5f9f0c91-1087-21d7-8b9a-a9d38a7bd1af@gmail.com>
Date: Thu, 19 May 2016 11:31:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6g5uEuQGudJnrdobn3am4Ql-cmI>
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: Wed, 18 May 2016 23:31:22 -0000

On 19/05/2016 02:23, Tim Chown wrote:
>> On 18 May 2016, at 15:15, Alexandre Petrescu <alexandre.petrescu@gmail=
=2Ecom> wrote:

=2E..
>> If there's no fixed address then there's no DNS name for that machine.=

>>
>> Updating DNS for each temporary IP address may not be that easy.
>=20
> But that=E2=80=99s not necessarily needed. Was certainly fine without i=
t in the campus environment I was in, where all comms initiated outbound =
were from privacy addresses with no associated DNS info.

I just experimented at home, with privacy addressing enabled and my SLAAC=
-assigned address
deleted manually(*). As far as I can see everything works as normal so fa=
r. Why wouldn't
it? DNS names are pointless for pure clients, for IPv-anything.

* netsh interface ipv6 del address 12 <address> active
I can't find a way in Windows to simply switch SLAAC off without
defining a static address.

   Brian


From nobody Wed May 18 17:03: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 59D5212D532 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 17:03: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 r-2LaGJdA7_v for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 17:03:06 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 8A27D12D1DD for <ipv6@ietf.org>; Wed, 18 May 2016 17:03:06 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id tb2so5169045pac.2 for <ipv6@ietf.org>; Wed, 18 May 2016 17:03:06 -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=pT+Dw0H/DmWNkx6diKMXxsOuvjkSZrx/+F3IW+ftioA=; b=htmJrL55gbnEw/ZMNtmzmqP9XeUnPFRofWMNqxC+ctJpY4efq8G3zxZc02dxKfEw0v uVdnIwRanQWH90p/+3sLMbZ8OZDEVtnsN2zrkzKVEtScv/DAVSDZxP2dq9jZ5vQkLd1C Hxc+aF3b3FtE2SO9Qw+80XtygVXUoo1ba8ABg9H9yopnkusAiYM7DiBTzh7ECoF6/PZd msFdLqu5LQ4PwgMh14iZzSoES25nenxKdW2N/8aEtG6sHuBqP424MPmwzqF1w2cm8Z3z wp3OB6KfxGcmjR865UIRf5dujdkqLKgT6yy5RhR1B6SdGXQ+4evAAaOVGKL3u+eVBQiu WJLg==
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=pT+Dw0H/DmWNkx6diKMXxsOuvjkSZrx/+F3IW+ftioA=; b=Ft6aHRxlJIL9Z5PEbVWJrf2Fz5vS/O5L1YSzJ9jOQVTV2AO28bMeceTIMecHpymJVv KqAeA3Mxr3AEJ9VouxJ9Dv0UMhbOzfxcixeeVAB7Akj6tIT542zBEtG+KQd9F4IUo4yR wiG3Xdfijv7+zTmPCVwgSiPDb55D/P32ZSfLQfPFON4fdRRXtbK8cvtjI8v79wqKQS6L 4o1EycRbI1L9XO7SMcK563D0Xd/bNAUKnrWBgMgmN3hP0LcKEC4yNl7P3gVAMeqAiHnN 1PPg2zXG3Y8/mXiO0VpfZJjwlClNkqXkrjzS8RmJSPYOubVIZXLRVTB383lFYCHOvJkv GJ2A==
X-Gm-Message-State: AOPr4FUQkf6c7kViSeE91P1A5CWY/OeuWV8Wtnb2dorNjP+Pvsa3m6UaGgA+CUEGhNO59w==
X-Received: by 10.66.152.164 with SMTP id uz4mr15061025pab.9.1463616185955; Wed, 18 May 2016 17:03:05 -0700 (PDT)
Received: from ?IPv6:2406:e007:6b9a:1:5483:9b95:28ce:1d34? ([2406:e007:6b9a:1:5483:9b95:28ce:1d34]) by smtp.gmail.com with ESMTPSA id t8sm14845350paw.16.2016.05.18.17.03.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 May 2016 17:03:05 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
To: Fernando Gont <fgont@si6networks.com>, weigengyu <weigengyu@bupt.edu.cn>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC> <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC> <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com> <573BD140.8000607@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2d547146-0c37-ed43-ab0b-4506336e850b@gmail.com>
Date: Thu, 19 May 2016 12:03:10 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <573BD140.8000607@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/MnPHLOHs7IYY3grvjSsC-2VzK1k>
Cc: 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, 19 May 2016 00:03:08 -0000

On 18/05/2016 14:19, Fernando Gont wrote:
> On 05/16/2016 04:08 PM, Brian E Carpenter wrote:
>> Hi Gengyu,
>>
>>>> RID is not random or random identifier according to the context above.
>>>>
>>>> F() is an inreverse function, not a pseudorandom function.
>>
>> I agree that this is incorrect use of terminology; an irreversible hash is
>> not mathematically equivalent to a pseudo-random number generator. But the
>> effect is the same: an attacker has no way to predict the next F(x) or to
>> obtain the value of x. As far as practical engineering goes, F() can be treated
>> as a random number. So I don't see why this invalidates the use of RFC 7217.
>>
>> You could submit an erratum for RFC 7217 at http://www.rfc-editor.org/errata.php#reportnew
>> so that the terminology can be corrected when the document is updated.
> 
> FWIW, the term "PRF" (as *opposed*) to PRNG was suggested by Alfred
> Hoenes -- IIRC, a mathematician. IIRC, he noted that a hash function is
> simply one possible way of a PRF.

Well, it's complicated (https://en.wikipedia.org/wiki/Pseudorandom_function_family).
As engineers, I think we do better to focus on what matters to us: we need
an unpredictable and unguessable bit string, which we carelessly call 'random'.

   Brian


From nobody Wed May 18 17:28:32 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 8E81612D542 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 17:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 CTWLlPJfFX_7 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 17:28:29 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 CD0C112D17B for <6man@ietf.org>; Wed, 18 May 2016 17:28:28 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id g133so62959254ywb.2 for <6man@ietf.org>; Wed, 18 May 2016 17:28:28 -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=thsfvS59CGsMvBIDYoqUW8Vo08CmqsqNzYc/Ks513yU=; b=pSTc4KlDHUtXJuXfbBK21+EWrvfFYlGqMsIXSTVRdW/ao8nIBt47ZnCibwWBQL8dLz GMiPRrigY580YEHnyGnC2Gee98/IMYqZPcC5MX3jYsFgst4ooDvKDgqKOdCsiGv4DwQK x1Nhr3ahZItaf5SQ4fUjQvsy2wMNCiwcJruSTB9y/w1mzKHpSI++Fet33TKNvkCXeHeU Oucw44m7IoUacv70ls8UoOu/WQYPsxnS3LieuXUa9PKwhTb0vKGnj3F46908PpPdxJxV sEuRsMKfPJtko3sTMVE9AVNEqs19/7OO6FzJdXcvdAwaFFeSMApRw9z2cw3I+rE4NgHT Qpgg==
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=thsfvS59CGsMvBIDYoqUW8Vo08CmqsqNzYc/Ks513yU=; b=kp47046nxQM9dXPatJL8dxJroFoOMvD5Otjshd0ki/sdx84GTdcvmM3K+mJzMNDsPo soi7WUYbBxdhx7fWBbjK8fo4FQfaGtU45WyTyPEx4/La2EViL+XfJqnZoQ5gdBuV+RdC Szv0cYOK1sQnaDT/kBNH3/3uNpng6NlfLNENif8e7TqrwWbe7Mqys06dhUbnEPHqjamf /epTIDGU9S0SnKOCpWAQU4Hl+IzKTDfg7pjv+Pa4a+VCskUV5vAX17plBojWBVIojgBX eQ6e5Ii25yYbMKtkMssrDVFNUzwW1eK1VmeMPbFhFzeLodP78QkPUw8T1i6V5+nVt43O XUBw==
X-Gm-Message-State: AOPr4FWiRQ69ZM54208o/A90IMui5rmh4x3pF06l96n7pWRIJVF3UFhBM3vW/8RwA6B426yQvFl4X8fdzOud8HKu
X-Received: by 10.13.220.69 with SMTP id f66mr6247728ywe.132.1463617707848; Wed, 18 May 2016 17:28:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 18 May 2016 17:28:06 -0700 (PDT)
In-Reply-To: <DM2PR0301MB0717D5EA3FD289A7894E3AC0A3490@DM2PR0301MB0717.namprd03.prod.outlook.com>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <CAKD1Yr2aWnRVvL6KEheWb1fKn3RPGdYewdb3QVf9w3A1V1wTUQ@mail.gmail.com> <DM2PR0301MB0717D5EA3FD289A7894E3AC0A3490@DM2PR0301MB0717.namprd03.prod.outlook.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 19 May 2016 09:28:06 +0900
Message-ID: <CAKD1Yr1uTHO8zm_E9Dy6tk_mjSHqSX4Z9tjZ9Osrv72gL9QVJw@mail.gmail.com>
Subject: Re: RFC4941 text on requirement for public addresses (was: Re: default-iids and stable addresses)
To: Dave Thaler <dthaler@microsoft.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c89107f00533270d31
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CR3EuvPzmPE5LhHlfSF7p85BJzc>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 19 May 2016 00:28:31 -0000

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

Dave, so how are implementers to interpret this text in the presence of no
public address?

       If a received
       option will extend the lifetime of a public address, the
       lifetimes of temporary addresses should be extended, subject to
       the overall constraint that no temporary addresses should ever
       remain "valid" or "preferred" for a time longer than
       (TEMP_VALID_LIFETIME) or (TEMP_PREFERRED_LIFETIME -
       DESYNC_FACTOR), respectively.

Should the implementer conclude that the lifetimes of the temporary
addresses should also be extended, even though the text does not require
it? If so, what of the TEMP_VALID_LIFETIME and TEMP_PREFERRED_LIFETIME -
DESYNC_FACTOR constraints? The text does not require those constraints to
be observed if there is no public address.

On Thu, May 19, 2016 at 1:45 AM, Dave Thaler <dthaler@microsoft.com> wrote:

> I agree with Ole that RFC 4941 does not require public addresses.
>
> For example, neither of the two snippets quoted by Lorenzo requires public
> addresses.
>
> They just state what the behavior is IF you have public addresses.
>
>
>
> *From:* Lorenzo Colitti [mailto:lorenzo@google.com]
> *Sent:* Wednesday, May 18, 2016 9:42 AM
> *To:* Ole Troan <otroan@employees.org>
> *Cc:* 6man@ietf.org; Fernando Gont <fernando@gont.com.ar>;
> draft-ietf-6man-default-iids@tools.ietf.org
> *Subject:* Re: RFC4941 text on requirement for public addresses (was: Re:
> default-iids and stable addresses)
>
>
>
> As written, RFC 4941 seems to require public addresses. For example:
>
>
>
>        If a received
>
>        option will extend the lifetime of a public address, the
>
>        lifetimes of temporary addresses should be extended
>
> ...
>
>    3.  When a new public address is created as described in [ADDRCONF],
>
>        the node SHOULD also create a new temporary address.
>
> ...
>
>        *  Its Preferred Lifetime is the lower of the Preferred Lifetime
>
>           of the public address or TEMP_PREFERRED_LIFETIME -
>
>           DESYNC_FACTOR.
>
>
>
> On Wed, May 18, 2016 at 8:13 PM, <otroan@employees.org> wrote:
>
> This email from Fernando provides a good introduction to an outstanding
> question from Buenos Aires.
>
> The current plan is to take RFC4941 to Internet Standard unchanged.
> A question was raised if 4941 requires public addresses or not, and if we
> have to update 4941 text, or if we can live with the current text, and
> still allow for interfaces with only temporary addresses.
>
> Opinions?
>
> Best regards,
> Ole
>
> > On 17 May 2016, at 20:15, Fernando Gont <fernando@gont.com.ar> wrote:
> >
> > Lorenzo (and wg),
> >
> > The two issues raised by Lorenzo regarding default-iids boil down to:
> >
> > 1) The ability to embed MAC addresses in the IID
> >
> > 2) The requirement to have stable addresses
> >
> >
> > This document does ban "1)" as the default algorithm for generating
> > IIDs, for the reasons discussed in RFC7721 and
> > draft-gont-predictable-numeric-ids. We have a very long history of
> > improper numeric IDs, and I guess that, regarding this one, we simply
> > disagree with Lorenzo.
> >
> >
> > Regarding "2)", this document does not specify any new requirements on
> > the topic. Essentially, nodes are implied to configure a stable
> > addresses as a result of SLAAC&traditional link-layer address
> > properties, and more explicitly by this text in RFC4941:
> >
> > * Section 3, bullet #1:
> >   2.  Create additional addresses based on a random interface
> >       identifier for the purpose of initiating outgoing sessions.
> >
> > * Section 3.3, bullet #1:
> >   1.  Process the Prefix Information Option as defined in [ADDRCONF],
> >       either creating a new public address or adjusting the lifetimes
> >       of existing addresses, both public and temporary.
> >
> > * Section 3.3, bullet #3:
> >   3.  When a new public address is created as described in [ADDRCONF],
> >       the node SHOULD also create a new temporary address.
> >
> > * Section 3.6, for instance, says (even recommending that temp addrs
> > default to "off"):
> >   The use of temporary addresses may cause unexpected difficulties with
> >   some applications.  As described below, some servers refuse to accept
> >   communications from clients for which they cannot map the IP address
> >   into a DNS name.  In addition, some applications may not behave
> >   robustly if temporary addresses are used and an address expires
> >   before the application has terminated, or if it opens multiple
> >   sessions, but expects them to all use the same addresses.
> >   Consequently, the use of temporary addresses SHOULD be disabled by
> >   default in order to minimize potential disruptions.
> >
> >
> >
> > Our document simply requires implementations that their
> > stable addresses are RFC7721-friendly. But if anything, the requirement
> > of whether to have a stable address or not is not something introduced
> > by our document.
> >
> > As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> > that we're on the same page, because I have the feeling that the above
> > keeps getting misinterpreted.
> >
> > I believe all of the co-authors of default-iids agree and understand
> > that there can be scenarios where you may want to do
> > temporary-addresses-only. However, that is orthogonal to this particular
> > document (default-iids), and would probably require an update to
> > RFC4941, such that temporary addresses can be employed as a replacement
> > of stable addresses, rather than as something that you do "in addition
> > to" them.
> >
> > This document is about how to do stable addresses in a more
> > RFC7721-friendly way than we currently do.
> >
> > Thanks!
> >
> > Best regards,
> > --
> > Fernando Gont
> > e-mail: fernando@gont.com.ar || fgont@si6networks.com
> > PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
>
>

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

<div dir=3D"ltr">Dave, so how are implementers to interpret this text in th=
e presence of no public address?<div><br></div><div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0If a received</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0option will ex=
tend the lifetime of a public address, the</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0lifetimes of temporary addresses should be extended, subject to</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0the overall constraint that no temporary ad=
dresses should ever</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0remain &quot;valid=
&quot; or &quot;preferred&quot; for a time longer than</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0(TEMP_VALID_LIFETIME) or (TEMP_PREFERRED_LIFETIME -</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0DESYNC_FACTOR), respectively.</div><div><br>=
</div><div>Should the implementer conclude that the lifetimes of the tempor=
ary addresses should also be extended, even though the text does not requir=
e it? If so, what of the=C2=A0TEMP_VALID_LIFETIME and TEMP_PREFERRED_LIFETI=
ME - DESYNC_FACTOR constraints? The text does not require those constraints=
 to be observed if there is no public address.</div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Thu, May 19, 2016 at 1:45 AM, Dave Th=
aler <span dir=3D"ltr">&lt;<a href=3D"mailto:dthaler@microsoft.com">dthaler=
@microsoft.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"gmail-MsoNormal"><span style=3D"font-size:11pt;font-family:cali=
bri,sans-serif;color:rgb(31,73,125)">I agree with Ole that RFC 4941 does no=
t require public addresses.<u></u><u></u></span></p>
<p class=3D"gmail-MsoNormal"><span style=3D"font-size:11pt;font-family:cali=
bri,sans-serif;color:rgb(31,73,125)">For example, neither of the two snippe=
ts quoted by Lorenzo requires public addresses.<u></u><u></u></span></p>
<p class=3D"gmail-MsoNormal"><span style=3D"font-size:11pt;font-family:cali=
bri,sans-serif;color:rgb(31,73,125)">They just state what the behavior is I=
F you have public addresses.<u></u><u></u></span></p>
<p class=3D"gmail-MsoNormal"><a name=3D"m_-3714699321276082314__MailEndComp=
ose"><span style=3D"font-size:11pt;font-family:calibri,sans-serif;color:rgb=
(31,73,125)"><u></u>=C2=A0<u></u></span></a></p>
<div style=3D"border-top-width:initial;border-right-width:initial;border-bo=
ttom-width:initial;border-style:none none none solid;border-top-color:initi=
al;border-right-color:initial;border-bottom-color:initial;border-left-width=
:1.5pt;border-left-color:blue;padding:0in 0in 0in 4pt">
<div>
<div style=3D"border-right-width:initial;border-bottom-width:initial;border=
-left-width:initial;border-style:solid none none;border-right-color:initial=
;border-bottom-color:initial;border-left-color:initial;border-top-width:1pt=
;border-top-color:rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"gmail-MsoNormal"><b><span style=3D"font-size:11pt;font-family:c=
alibri,sans-serif">From:</span></b><span style=3D"font-size:11pt;font-famil=
y:calibri,sans-serif"> Lorenzo Colitti [mailto:<a href=3D"mailto:lorenzo@go=
ogle.com">lorenzo@google.com</a>]
<br>
<b>Sent:</b> Wednesday, May 18, 2016 9:42 AM<br>
<b>To:</b> Ole Troan &lt;<a href=3D"mailto:otroan@employees.org">otroan@emp=
loyees.org</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:6man@ietf.org">6man@ietf.org</a>; Fernando Gon=
t &lt;<a href=3D"mailto:fernando@gont.com.ar">fernando@gont.com.ar</a>&gt;;=
 <a href=3D"mailto:draft-ietf-6man-default-iids@tools.ietf.org">draft-ietf-=
6man-default-iids@tools.ietf.org</a><br>
<b>Subject:</b> Re: RFC4941 text on requirement for public addresses (was: =
Re: default-iids and stable addresses)<u></u><u></u></span></p>
</div>
</div><div><div class=3D"gmail-h5">
<p class=3D"gmail-MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"gmail-MsoNormal">As written, RFC 4941 seems to require public a=
ddresses. For example:<u></u><u></u></p>
<div>
<p class=3D"gmail-MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0If a received<u></u=
><u></u></p>
</div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0option will extend =
the lifetime of a public address, the<u></u><u></u></p>
</div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0lifetimes of tempor=
ary addresses should be extended<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"gmail-MsoNormal">...<u></u><u></u></p>
</div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A03.=C2=A0 When a new public addres=
s is created as described in [ADDRCONF],<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0the node SHOULD als=
o create a new temporary address.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"gmail-MsoNormal">...<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0* =C2=A0Its Preferr=
ed Lifetime is the lower of the Preferred Lifetime<u></u><u></u></p>
</div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 of the publ=
ic address or TEMP_PREFERRED_LIFETIME -<u></u><u></u></p>
</div>
<div>
<p class=3D"gmail-MsoNormal">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 DESYNC_FACT=
OR.<u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"gmail-MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"gmail-MsoNormal">On Wed, May 18, 2016 at 8:13 PM, &lt;<a href=
=3D"mailto:otroan@employees.org">otroan@employees.org</a>&gt; wrote:<u></u>=
<u></u></p>
<blockquote style=3D"border-top-width:initial;border-right-width:initial;bo=
rder-bottom-width:initial;border-style:none none none solid;border-top-colo=
r:initial;border-right-color:initial;border-bottom-color:initial;border-lef=
t-width:1pt;border-left-color:rgb(204,204,204);padding:0in 0in 0in 6pt;marg=
in-left:4.8pt;margin-right:0in">
<p class=3D"gmail-MsoNormal" style=3D"margin-bottom:12pt">This email from F=
ernando provides a good introduction to an outstanding question from Buenos=
 Aires.<br>
<br>
The current plan is to take RFC4941 to Internet Standard unchanged.<br>
A question was raised if 4941 requires public addresses or not, and if we h=
ave to update 4941 text, or if we can live with the current text, and still=
 allow for interfaces with only temporary addresses.<br>
<br>
Opinions?<br>
<br>
Best regards,<br>
Ole<br>
<br>
&gt; On 17 May 2016, at 20:15, Fernando Gont &lt;<a href=3D"mailto:fernando=
@gont.com.ar">fernando@gont.com.ar</a>&gt; wrote:<br>
&gt;<br>
&gt; Lorenzo (and wg),<br>
&gt;<br>
&gt; The two issues raised by Lorenzo regarding default-iids boil down to:<=
br>
&gt;<br>
&gt; 1) The ability to embed MAC addresses in the IID<br>
&gt;<br>
&gt; 2) The requirement to have stable addresses<br>
&gt;<br>
&gt;<br>
&gt; This document does ban &quot;1)&quot; as the default algorithm for gen=
erating<br>
&gt; IIDs, for the reasons discussed in RFC7721 and<br>
&gt; draft-gont-predictable-numeric-ids. We have a very long history of<br>
&gt; improper numeric IDs, and I guess that, regarding this one, we simply<=
br>
&gt; disagree with Lorenzo.<br>
&gt;<br>
&gt;<br>
&gt; Regarding &quot;2)&quot;, this document does not specify any new requi=
rements on<br>
&gt; the topic. Essentially, nodes are implied to configure a stable<br>
&gt; addresses as a result of SLAAC&amp;traditional link-layer address<br>
&gt; properties, and more explicitly by this text in RFC4941:<br>
&gt;<br>
&gt; * Section 3, bullet #1:<br>
&gt;=C2=A0 =C2=A02.=C2=A0 Create additional addresses based on a random int=
erface<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0identifier for the purpose of initiating out=
going sessions.<br>
&gt;<br>
&gt; * Section 3.3, bullet #1:<br>
&gt;=C2=A0 =C2=A01.=C2=A0 Process the Prefix Information Option as defined =
in [ADDRCONF],<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0either creating a new public address or adju=
sting the lifetimes<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0of existing addresses, both public and tempo=
rary.<br>
&gt;<br>
&gt; * Section 3.3, bullet #3:<br>
&gt;=C2=A0 =C2=A03.=C2=A0 When a new public address is created as described=
 in [ADDRCONF],<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0the node SHOULD also create a new temporary =
address.<br>
&gt;<br>
&gt; * Section 3.6, for instance, says (even recommending that temp addrs<b=
r>
&gt; default to &quot;off&quot;):<br>
&gt;=C2=A0 =C2=A0The use of temporary addresses may cause unexpected diffic=
ulties with<br>
&gt;=C2=A0 =C2=A0some applications.=C2=A0 As described below, some servers =
refuse to accept<br>
&gt;=C2=A0 =C2=A0communications from clients for which they cannot map the =
IP address<br>
&gt;=C2=A0 =C2=A0into a DNS name.=C2=A0 In addition, some applications may =
not behave<br>
&gt;=C2=A0 =C2=A0robustly if temporary addresses are used and an address ex=
pires<br>
&gt;=C2=A0 =C2=A0before the application has terminated, or if it opens mult=
iple<br>
&gt;=C2=A0 =C2=A0sessions, but expects them to all use the same addresses.<=
br>
&gt;=C2=A0 =C2=A0Consequently, the use of temporary addresses SHOULD be dis=
abled by<br>
&gt;=C2=A0 =C2=A0default in order to minimize potential disruptions.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Our document simply requires implementations that their<br>
&gt; stable addresses are RFC7721-friendly. But if anything, the requiremen=
t<br>
&gt; of whether to have a stable address or not is not something introduced=
<br>
&gt; by our document.<br>
&gt;<br>
&gt; As a co-author of draft-ietf-6man-default-iids, I just wanted to check=
<br>
&gt; that we&#39;re on the same page, because I have the feeling that the a=
bove<br>
&gt; keeps getting misinterpreted.<br>
&gt;<br>
&gt; I believe all of the co-authors of default-iids agree and understand<b=
r>
&gt; that there can be scenarios where you may want to do<br>
&gt; temporary-addresses-only. However, that is orthogonal to this particul=
ar<br>
&gt; document (default-iids), and would probably require an update to<br>
&gt; RFC4941, such that temporary addresses can be employed as a replacemen=
t<br>
&gt; of stable addresses, rather than as something that you do &quot;in add=
ition<br>
&gt; to&quot; them.<br>
&gt;<br>
&gt; This document is about how to do stable addresses in a more<br>
&gt; RFC7721-friendly way than we currently do.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Best regards,<br>
<span><span style=3D"color:rgb(136,136,136)">&gt; --</span></span><span sty=
le=3D"color:rgb(136,136,136)"><br>
<span>&gt; Fernando Gont</span><br>
<span>&gt; e-mail: <a href=3D"mailto:fernando@gont.com.ar">fernando@gont.co=
m.ar</a> ||
<a href=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a></span><b=
r>
<span>&gt; PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FF=
F1</span><br>
<span>&gt;</span><br>
<span>&gt;</span><br>
<span>&gt;</span><br>
<span>&gt; ----------------------------------------------------------------=
----</span><br>
<span>&gt; IETF IPv6 working group mailing list</span><br>
<span>&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a></span><br>
<span>&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman=
/listinfo/ipv6">
https://www.ietf.org/mailman/listinfo/ipv6</a></span><br>
<span>&gt; ----------------------------------------------------------------=
----</span></span><u></u><u></u></p>
</blockquote>
</div>
<p class=3D"gmail-MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div></div></div>

--94eb2c0815c89107f00533270d31--


From nobody Wed May 18 18:00:34 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 5798912D0BA for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 18:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 0pCzt7r5d9HF for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 18:00:31 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 F422512B068 for <ipv6@ietf.org>; Wed, 18 May 2016 18:00:30 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id j74so63595689ywg.1 for <ipv6@ietf.org>; Wed, 18 May 2016 18:00:30 -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=FkQDlUctxYCNQdgSWHykBcIFBmc03YaBN5tTjUHF7qc=; b=LKVy143apcOtCXq+0wMXC4RsEwro6mprd9SJq7xMFlLQORtNlzVh5JvWWEcfjjeUgZ nD5UkZ3H5eXowMF03A1xpdrggWvGKYBLmFPdKOuWhTfMiuO32HJpnI7toN+IxHm6nsde u/kZtkfblS4HvI+IVCUhXDXmE4YUNS+y2GNIdartKTPzqOZSKryI48AY9lecz/7+sJlT 5woJLi762tMZcbBf+WbOGvZU1f0HM91H5LilorhIKRGRaSDfWLJjbd/VzNxoHru14w+K nGLoPl4+sqf5z/wf2W4cYd4u9uQFAUpdk+8y/1uFnJjT0/zybVnCpuMQrKqb+p90o7XN 1XLQ==
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=FkQDlUctxYCNQdgSWHykBcIFBmc03YaBN5tTjUHF7qc=; b=TNPDyA1cCxy0yRiNA7YOKCdM9FthhJOyb9OEbln/Ygu9joQFauD8DgcAx4vSoVE5QS 10huzYIOcgEKgXoLgOGIH6AcPkAPidwguwgSzJ/w35zxuyv/sWDMiaUH+UI8wcnNrS9G Ig5KsDSR60MRoP1/0Px4pWgRJvRv/LKfMI6+8s/bxBXxSTNiuI26Beo38om8vxWAIsjj 316jGQLok6PiEDtFvTNfdHOVO99xvUPfyiLCYV9kw5SlzXxrOHjY41f/OxcWuJl4XjuZ zENTMz9th/qcFCi/hlIyZX1Sebpk/bLChQvzOy50cq+xkK3BMPj77ey2SkP4/IEjvqFe aX7w==
X-Gm-Message-State: AOPr4FU/+RsAhZmQkNpFWbd/vP1UVOXspXL+NiglzIM6hhcoqj2DwkDazyCEP00BwY+D565Aff6NYOUPYPytrDY5
X-Received: by 10.13.220.69 with SMTP id f66mr6306630ywe.132.1463619630116; Wed, 18 May 2016 18:00:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 18 May 2016 18:00:10 -0700 (PDT)
In-Reply-To: <573BCFD0.8090801@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 19 May 2016 10:00:10 +0900
Message-ID: <CAKD1Yr3heGg1GjhU1VghMHfg08q6RuK6Ls4M==ppgg6Eg1G_Wg@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c82448240533278093
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pNTugpdXDOT8rPaUjbvwhVdCYxM>
Cc: IPv6 List <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, 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: Thu, 19 May 2016 01:00:32 -0000

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

On Wed, May 18, 2016 at 11:13 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> No. My take is that the concern is flawed. Please read
> draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
> length about security and privacy issues regarding reusing identifiers
> in different context, for different scopes, etc.
>

Fernando, please stop arguing that a random MAC address is a "predictable
ID". That statement is false and continuing to argue for it is not helping
this document advance.

--94eb2c0815c82448240533278093
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 W=
ed, May 18, 2016 at 11:13 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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">No. My take is that =
the concern is flawed. Please read<br>
draft-gont-predictable-protocol-ids, and even RFC4941, which talks at<br>
length about security and privacy issues regarding reusing identifiers<br>
in different context, for different scopes, etc.<br></blockquote><div><br><=
/div><div>Fernando, please stop arguing that a random MAC address is a &quo=
t;predictable ID&quot;. That statement is false and continuing to argue for=
 it is not helping this document advance.</div></div></div></div>

--94eb2c0815c82448240533278093--


From nobody Wed May 18 18:49:52 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 0D88512D5C5 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 18:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 3HhuqshnCeuN for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 18:49:49 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 625CC12D5A0 for <6man@ietf.org>; Wed, 18 May 2016 18:49:49 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id g133so64393255ywb.2 for <6man@ietf.org>; Wed, 18 May 2016 18:49:49 -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=EvgalZwq8vpkZ7Twq01rXGzrJJVZw/KmWtChs3D1ipw=; b=khZtWmwAW+shQ8W1BNpFd5eKzsCVwU3lVEqErgIx2iLbtkMPMd27R9ixNa44iEQB02 5rFyhMVACkwCbflP2TtDWNbHajc6bBxRX4W9iDF9PTqHU+2jWJR1LmuOjdvKh3vuL7W9 siRWyhL6t9ANXhFStjnYBKsbwWLXqsLPZjiZpK3ykKEyWDKauKYjeAj6xs9EHdXcH0b2 wsOBMkQWpYAoWy7PPDMe72Pa3I4S0wlAhmYICMyP41sQ5ZFgxlfEymwGHwHXcItdb+xG 3yV41iP/ogfPETRwt0uVHyrxw4PcpMD4cNnkVYBsfPGszEIB8+c/RG/VM+HaWsVwx48Y aWIQ==
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=EvgalZwq8vpkZ7Twq01rXGzrJJVZw/KmWtChs3D1ipw=; b=hAVWjioJm6pqrhAxCRQQ+4j4IWXxrbKB7bU3w4Joq8aFFBdACslUHh2Bp0MQ9UHroi zHJ7HrnLLbhZiVmKyQ+eX+0nGcO9dR6NlgRzE1CJL41rcESQrvOHG6ofQmmcZEeximFe DGKN8me8dBwFL1VJ1faYZmNiYXjS3EygS5WgNEmGXZA76H7RN4loB/7pAynq9/RfgAp/ LTFt2LgzPW4paL6Q6Ee1PB11rA7anlWU4xCzQgSXT1RQCsAMRw+1K48EINO5wgS8wZVr UR3jFNXTuX2PVuNEw2xzyLxQjO2WrRSHiAsiQB7ZZPdz5Bby/ZSZO1JDMDY5oKEAbe7B MVzQ==
X-Gm-Message-State: AOPr4FXxeCRV2CHTPbYWAdeL1jq1uAYURtsEnGjg42H2VREX0I7cS7juu9yCNTXyc1E0Mz1PBkmZme/pG/1Si5x9
X-Received: by 10.129.108.208 with SMTP id h199mr6156321ywc.229.1463622588582;  Wed, 18 May 2016 18:49:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 18 May 2016 18:49:28 -0700 (PDT)
In-Reply-To: <CAJE_bqdXt_jC2GCc-SRXAfRTybYd88ZdSMpnny2oJUMnscnyOQ@mail.gmail.com>
References: <573B5FAC.7060300@gont.com.ar> <CAJE_bqdXt_jC2GCc-SRXAfRTybYd88ZdSMpnny2oJUMnscnyOQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 19 May 2016 10:49:28 +0900
Message-ID: <CAKD1Yr3U+UwopiXA9SgMGHm6BHGVmSMistyUhqqYpxYNZC4tUg@mail.gmail.com>
Subject: Re: default-iids and stable addresses
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=001a114db9047ad4e50533283005
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GQSXddoojk-wL82mUpSYRhO8Hrw>
Cc: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fernando@gont.com.ar>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 19 May 2016 01:49:51 -0000

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

On Thu, May 19, 2016 at 3:09 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinm=
ei@wide.ad.jp> wrote:

> > As a co-author of draft-ietf-6man-default-iids, I just wanted to check
> > that we're on the same page, because I have the feeling that the above
> > keeps getting misinterpreted.
>
> Misinterpretation (I'd call it confusion in this context, though) of a
> document often happens because the document isn't clear enough


+1

--001a114db9047ad4e50533283005
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=
hu, May 19, 2016 at 3:09 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jinmei@wide.ad.jp" target=3D"_blank">jinmei@=
wide.ad.jp</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 cl=
ass=3D"">&gt; As a co-author of draft-ietf-6man-default-iids, I just wanted=
 to check<br>
&gt; that we&#39;re on the same page, because I have the feeling that the a=
bove<br>
&gt; keeps getting misinterpreted.<br>
<br>
</span>Misinterpretation (I&#39;d call it confusion in this context, though=
) of a<br>
document often happens because the document isn&#39;t clear enough</blockqu=
ote><div><br></div><div>+1=C2=A0</div></div></div></div>

--001a114db9047ad4e50533283005--


From nobody Wed May 18 22:19:53 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 37FD212B057 for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 22:19:51 -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=y6O9hvxs; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=ddqEhVLe
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 EHstx-OtiQ8u for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 22:19:49 -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 5B99F12B022 for <ipv6@ietf.org>; Wed, 18 May 2016 22:19:49 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B8831205E1 for <ipv6@ietf.org>; Thu, 19 May 2016 01:19:48 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 19 May 2016 01:19:48 -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=FSultIOKu4M5U6Gt9WrTLyU+qIc=; b=y6O9hv xsnvf+0k54A20VCptg8tDyHsfRF7l4bn73Z2iaH8ZTxtA2uvy0d4iEdSOAwF8dOz tJAXg3E4Q34ZiBk39t1PkYDneLIsWKS0pRob3TMpMzMqvmzaFnIvyh/5Vf/atOw7 qM5pSuT4b3mVajWXoI4CDJQLz5sezToeaWUP4=
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=FSultIOKu4M5U6G t9WrTLyU+qIc=; b=ddqEhVLecDmGEBk9s5kBhGuxNfpJc2Yj3ocpoXX2hG8Lgsg SM202b/AKLlmP0VZOhlZBFoYJLkFsVqJK169GAO6hPE/+rkNHBckjEa6S4l2wffq BChdMxPIZbNFI/693zkTgSveQitLuZoYg42rYraCLdT30t4VqZQNeL7+ECks=
X-Sasl-enc: v3AyL4xnG4sTE5jYV3spTf6pr5LzL6ThOCvLcekTsGO5 1463635188
Received: from sjc-alcoop-8814.cisco.com (unknown [128.107.241.171]) by mail.messagingengine.com (Postfix) with ESMTPA id 1005EC0001E; Thu, 19 May 2016 01:19:47 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
Date: Wed, 18 May 2016 22:19:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-v5wEci7WJCkqA9T_GQzLJw1BtI>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 List <ipv6@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: Thu, 19 May 2016 05:19:51 -0000

> On May 18, 2016, at 4:22 PM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 =
<jinmei@wide.ad.jp> wrote:
>=20
> At Tue, 17 May 2016 22:13:36 -0400,
> Fernando Gont <fgont@si6networks.com> wrote:
>=20
>>> =46rom this one, and your response to the next point, it seems you =
are
>>> saying the decision was to refuse to address that concern.  Am I
>>> understanding it correctly?
>>=20
>> No. My take is that the concern is flawed. Please read
>> draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
>> length about security and privacy issues regarding reusing =
identifiers
>> in different context, for different scopes, etc.
>>=20
>> Let's call a lemon a lemon: Asking to embed a layer-2 =
identifier/address
>> in a layer-3 address is extremely bad.
>=20
> I don't have a strong position on this matter itself, but my
> understanding of the sense of the wg is that this is controversial,
> and at least far from a clear consensus.  To repeat myself, *my*
> concern on this last call is that it's not even clear, at least to me,
> if this draft tries to say embedding a link-layer address is, whether
> it's randomized or not, "extremely bad" (and must therefore be
> prohibited).  If that's the intent, it should be clearly stated

The draft makes just about a clear a statement in this vein as is =
possible:

"By default, nodes SHOULD NOT employ IPv6 address generation schemes
   that embed the underlying link-layer address in the IID.=E2=80=9D

Note that this statement does not prohibit anything, nor does it make a =
normative (in the moral sense) judgment. It just states the =
recommendation, which is the point of the document.

I appreciate that not everyone on the list agrees with this =
recommendation. But I find the claim that this recommendation is unclear =
to be difficult to understand. That is, I can=E2=80=99t think of a way =
to convey the same recommendation that would be clearer. If you can, =
please suggest text.

Alissa


> and
> backed by a clear consensus from the wg.  Right now I don't see either
> such a clear statement or clear wg consensus.
>=20
> --
> JINMEI, Tatuya


From nobody Wed May 18 23:10:55 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 9CDB512B04D for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 23:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 eLipEQsSZ_lT for <ipv6@ietfa.amsl.com>; Wed, 18 May 2016 23:10:53 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::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 0636612B025 for <ipv6@ietf.org>; Wed, 18 May 2016 23:10:52 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id j74so68566800ywg.1 for <ipv6@ietf.org>; Wed, 18 May 2016 23:10:52 -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=uxiudrfkRMBtnUW4eGk3+VY6C66XzVWDDTKniraWyeQ=; b=gBj6ohJNnTxBqJhfelU4wVCyb8WGjRBCz8j8x+78D0SuKJ1TIQ2Ls3XcGpUaxCwS9q L0aOenZZ+MnPfOOoxgRLSIfisqUFfHgMkG87uqLs208hFZTMuWynJ7JnY6H9nkQSSckv ViQtdTL0aKZEMmX3PF36mtylJTqmIlgPXlXk8JXfMFq8lnujIemQsL9jD1rhDX3MwmSF VeVg+h1xopidwULmqdf3fi4ipwG4IJMRzewXwnefoySLtQkSo8WETrRQ3062e3nVdJGD tvGX7oK0r5SG1ew+zBOnvAVDZS7H9Rdlk8foYPwF3tKjnNstbB3a5oWAnWwic8uUbTpi fu4A==
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=uxiudrfkRMBtnUW4eGk3+VY6C66XzVWDDTKniraWyeQ=; b=DVZz/KJMI4rnMFst3YikHaOLtKb2Z1FJOENSG2t+/TCo/wbEeX9CSOO1FlrGwOYOPG CzN4DbhuJIvBsKcmgyzr3yRCH8GaGX9x55E8Oc54S08JK0B7GQC5QoiO/JP1xBXqY7VN n/ZoVT7wXXWPne17iFzTbDb/FnVydveEszJ05lCfig4aEPI+kg/vX+dgAQcMvi5dIUte 8/d4K5L1GQtj6+DgQEPmvC1YOWA6VdbuEfU4frkO4tE1ER+ycSUQuH5HDrsDDchWuoxz cOzOtO+P7h5iZyatRXZHaeBae7yGtw5/epgmtWhDzpSacEUSZA1+dJb9PHNDBVsGbs/Z NAHw==
X-Gm-Message-State: AOPr4FU7JoY/RMj1XTtk3NWziHC6AjjsmJz/FJvEMOQ3Qddkwiem2uJFy0h4A0KUmJc5sAUgzvtxLDbD2bgxSbJw
X-Received: by 10.37.80.145 with SMTP id e139mr6065219ybb.152.1463638252030; Wed, 18 May 2016 23:10:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 18 May 2016 23:10:32 -0700 (PDT)
In-Reply-To: <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 19 May 2016 15:10:32 +0900
Message-ID: <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary=001a113e89ea18495e05332bd6c4
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1TEkzvqMdMNUYXIRZkTwCRHAw_U>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 List <ipv6@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, 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: Thu, 19 May 2016 06:10:54 -0000

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

On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper <alissa@cooperw.in> wrote:

> The draft makes just about a clear a statement in this vein as is possibl=
e:
>
> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed the underlying link-layer address in the IID.=E2=80=9D
>
> Note that this statement does not prohibit anything, nor does it make a
> normative (in the moral sense) judgment. It just states the recommendatio=
n,
> which is the point of the document.
>
> I appreciate that not everyone on the list agrees with this
> recommendation. But I find the claim that this recommendation is unclear =
to
> be difficult to understand. That is, I can=E2=80=99t think of a way to co=
nvey the
> same recommendation that would be clearer. If you can, please suggest tex=
t.
>

Alissa,

I don't think anybody is claiming that the recommendation itself is
difficult to understand. What is difficult to understand is how the
document justifies that claim.

It looks like the main argument used to justify this recommendation is
major privacy risks. But embedding a link layer identifier into an IP
address is not a major [1] privacy risk. It is only embedding a *STABLE*
link-layer address that is a major privacy risk.

Recommending that link-layer address be embedded only if they are ephemeral
would address the privacy concerns just as well as (or maybe even better)
than the approach proposed in this document.

I think what people are do not understand is why this document recommends
one but not the other. I certainly don't.

Cheers,
Lorenzo

[1] I argue that cross-referencing IPX traffic to IP traffic is not a major
privacy risk because IPX is so uncommon.

--001a113e89ea18495e05332bd6c4
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=
hu, May 19, 2016 at 2:19 PM, Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D=
"mailto:alissa@cooperw.in">alissa@cooperw.in</a>&gt;</span> wrote:<br><bloc=
kquote 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);paddin=
g-left:1ex">The draft makes just about a clear a statement in this vein as =
is possible:<br>
<span class=3D"gmail-"><br>
&quot;By default, nodes SHOULD NOT employ IPv6 address generation schemes<b=
r>
</span>=C2=A0 =C2=A0that embed the underlying link-layer address in the IID=
.=E2=80=9D<br>
<br>
Note that this statement does not prohibit anything, nor does it make a nor=
mative (in the moral sense) judgment. It just states the recommendation, wh=
ich is the point of the document.<br>
<br>
I appreciate that not everyone on the list agrees with this recommendation.=
 But I find the claim that this recommendation is unclear to be difficult t=
o understand. That is, I can=E2=80=99t think of a way to convey the same re=
commendation that would be clearer. If you can, please suggest text.<br></b=
lockquote><div><br></div><div>Alissa,</div><div><br></div><div>I don&#39;t =
think anybody is claiming that the recommendation itself is difficult to un=
derstand. What is difficult to understand is how the document justifies tha=
t claim.</div><div><br></div><div>It looks like the main argument used to j=
ustify this recommendation is major privacy risks. But embedding a link lay=
er identifier into an IP address is not a major [1]=C2=A0privacy risk. It i=
s only embedding a *STABLE* link-layer address that is a major privacy risk=
.</div><div><br></div><div>Recommending that link-layer address be embedded=
 only if they are ephemeral would address the privacy concerns just as well=
 as (or maybe even better) than the approach proposed in this document.</di=
v><div><br></div><div>I think what people are do not understand is why this=
 document recommends one but not the other. I certainly don&#39;t.</div><di=
v><br></div><div>Cheers,</div><div>Lorenzo</div><div><br></div><div>[1] I a=
rgue that cross-referencing IPX traffic to IP traffic is not a major privac=
y risk because IPX is so uncommon.<br></div></div></div></div>

--001a113e89ea18495e05332bd6c4--


From nobody Thu May 19 00:10:07 2016
Return-Path: <alexandre.petrescu@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 E817812B011 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 00:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 i5kbxuPl0kUP for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 00:10:05 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7481C12B047 for <ipv6@ietf.org>; Thu, 19 May 2016 00:10:04 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4J7A20F004791; Thu, 19 May 2016 09:10:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2C25C205B4F; Thu, 19 May 2016 09:10:04 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 1ED73200C4D; Thu, 19 May 2016 09:10:04 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4J7A1up006821; Thu, 19 May 2016 09:10:01 +0200
Subject: Re: RFC4941 text on requirement for public addresses
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <FBFC5456-E42D-4E52-BBE2-0ADC898516B0@employees.org> <3BDDD246-C889-4AB5-9C21-62E4BF284192@jisc.ac.uk> <d17cdbc3-0cc3-800c-a08d-dc3cd2895a1c@gmail.com> <AE7E6DF8-9281-49BC-A010-09E93B754EDC@jisc.ac.uk> <f185260a-6041-607a-bc9c-fcacdd59ab78@gmail.com> <AA62DD34-9484-4AB2-81C5-DBC3263C040F@jisc.ac.uk> <e69d3c42-b496-4e06-76ae-4206b6a3f245@gmail.com> <3C4C7992-8343-4F5E-A43C-13C8183E8E85@jisc.ac.uk>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <7aced586-d88f-9aaf-c603-326104586222@gmail.com>
Date: Thu, 19 May 2016 09:10:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <3C4C7992-8343-4F5E-A43C-13C8183E8E85@jisc.ac.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5H05h8ruF0TlGW0VX_SDSR2WEBI>
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: Thu, 19 May 2016 07:10:07 -0000

Le 18/05/2016 Ã  18:07, Tim Chown a Ã©crit :
[...]

>> So the perspective in this RFC4941 (there is no value in a static
>> address) is contradictory to some operator's interests.
>
> All weâ€™re discussing here (I think!) is whether 4941 should be
> changed to no longer say that SLAAC is a MUST, so that we open the
> possibility for a node to use temporary addresses only.

In practice the SLAAC is not a MUST.  There are many IPv6 computers 
which dont SLAAC - they DHCPv6, or manually configure, or use only LLs.

[...]

> But letâ€™s focus on the topic Ole opened - should 4941 change the
> requirement for a public address from a MUST to something less, i.e.
> SHOULD, so we can very clearly support a mode where nodes can have
> just temporary addresses and no public address.

Is the Ole's SHOULD/MUST topic on public address use?  Or on SLAAC use?

Alex
(also, nit: may update RFC4941 to no longer say 'privacy addresses'
  on its pp. 12).

>
> Tim
>
>>
>> Alex
>>
>>
>>>
>>> Tim
>>>
>>>> Alex
>>>>
>>>>>
>>>>> Tim
>>>>>
>>>>>> Alex
>>>>>>
>>>>>>>
>>>>>>> Tim
>>>>>>>
>>>>>>>> Best regards, Ole
>>>>>>>>
>>>>>>>>> On 17 May 2016, at 20:15, Fernando Gont
>>>>>>>>> <fernando@gont.com.ar> wrote:
>>>>>>>>>
>>>>>>>>> Lorenzo (and wg),
>>>>>>>>>
>>>>>>>>> The two issues raised by Lorenzo regarding
>>>>>>>>> default-iids boil down to:
>>>>>>>>>
>>>>>>>>> 1) The ability to embed MAC addresses in the IID
>>>>>>>>>
>>>>>>>>> 2) The requirement to have stable addresses
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> This document does ban "1)" as the default algorithm
>>>>>>>>> for generating IIDs, for the reasons discussed in
>>>>>>>>> RFC7721 and draft-gont-predictable-numeric-ids. We
>>>>>>>>> have a very long history of improper numeric IDs, and
>>>>>>>>> I guess that, regarding this one, we simply disagree
>>>>>>>>> with Lorenzo.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regarding "2)", this document does not specify any
>>>>>>>>> new requirements on the topic. Essentially, nodes
>>>>>>>>> are implied to configure a stable addresses as a
>>>>>>>>> result of SLAAC&traditional link-layer address
>>>>>>>>> properties, and more explicitly by this text in
>>>>>>>>> RFC4941:
>>>>>>>>>
>>>>>>>>> * Section 3, bullet #1: 2.  Create additional
>>>>>>>>> addresses based on a random interface identifier for
>>>>>>>>> the purpose of initiating outgoing sessions.
>>>>>>>>>
>>>>>>>>> * Section 3.3, bullet #1: 1.  Process the Prefix
>>>>>>>>> Information Option as defined in [ADDRCONF], either
>>>>>>>>> creating a new public address or adjusting the
>>>>>>>>> lifetimes of existing addresses, both public and
>>>>>>>>> temporary.
>>>>>>>>>
>>>>>>>>> * Section 3.3, bullet #3: 3.  When a new public
>>>>>>>>> address is created as described in [ADDRCONF], the
>>>>>>>>> node SHOULD also create a new temporary address.
>>>>>>>>>
>>>>>>>>> * Section 3.6, for instance, says (even recommending
>>>>>>>>> that temp addrs default to "off"): The use of
>>>>>>>>> temporary addresses may cause unexpected difficulties
>>>>>>>>> with some applications. As described below, some
>>>>>>>>> servers refuse to accept communications from clients
>>>>>>>>> for which they cannot map the IP address into a DNS
>>>>>>>>> name.  In addition, some applications may not behave
>>>>>>>>> robustly if temporary addresses are used and an
>>>>>>>>> address expires before the application has
>>>>>>>>> terminated, or if it opens multiple sessions, but
>>>>>>>>> expects them to all use the same addresses.
>>>>>>>>> Consequently, the use of temporary addresses SHOULD
>>>>>>>>> be disabled by default in order to minimize potential
>>>>>>>>> disruptions.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Our document simply requires implementations that
>>>>>>>>> their stable addresses are RFC7721-friendly. But if
>>>>>>>>> anything, the requirement of whether to have a stable
>>>>>>>>> address or not is not something introduced by our
>>>>>>>>> document.
>>>>>>>>>
>>>>>>>>> As a co-author of draft-ietf-6man-default-iids, I
>>>>>>>>> just wanted to check that we're on the same page,
>>>>>>>>> because I have the feeling that the above keeps
>>>>>>>>> getting misinterpreted.
>>>>>>>>>
>>>>>>>>> I believe all of the co-authors of default-iids agree
>>>>>>>>> and understand that there can be scenarios where you
>>>>>>>>> may want to do temporary-addresses-only. However,
>>>>>>>>> that is orthogonal to this particular document
>>>>>>>>> (default-iids), and would probably require an update
>>>>>>>>> to RFC4941, such that temporary addresses can be
>>>>>>>>> employed as a replacement of stable addresses, rather
>>>>>>>>> than as something that you do "in addition to" them.
>>>>>>>>>
>>>>>>>>> This document is about how to do stable addresses in
>>>>>>>>> a more RFC7721-friendly way than we currently do.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> Best regards, -- Fernando Gont e-mail:
>>>>>>>>> fernando@gont.com.ar || fgont@si6networks.com PGP
>>>>>>>>> Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF
>>>>>>>>> D076 FFF1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>
>>>>>>>>>
>>
>>>>>>>>>
IETF IPv6 working group mailing list
>>>>>>>>> ipv6@ietf.org Administrative Requests:
>>>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>>>> --------------------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>
>>>>>>>>>
>>>>>>>>>
>>
>>>>>>>>>
--------------------------------------------------------------------
>>>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>>>> Administrative Requests:
>>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>>> --------------------------------------------------------------------
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>>>>>
>>>>>>>>
>>
>>>>>>>>
--------------------------------------------------------------------
>>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>>> Administrative Requests:
>>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>>> --------------------------------------------------------------------
>>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>
>>>>>>>
>>>>>>>
>>
>>>>>>>
--------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list ipv6@ietf.org
>>>>>> Administrative Requests:
>>>>>> https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>
>>>>>>
>


From nobody Thu May 19 00:51:02 2016
Return-Path: <alexandre.petrescu@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 6023F12B029 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 00:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 fGPkhRbDm8CF for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 00:50:59 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF6712B017 for <ipv6@ietf.org>; Thu, 19 May 2016 00:50:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4J7ovNU023239 for <ipv6@ietf.org>; Thu, 19 May 2016 09:50:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A236020246D for <ipv6@ietf.org>; Thu, 19 May 2016 09:50:59 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 98135201BC4 for <ipv6@ietf.org>; Thu, 19 May 2016 09:50:59 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4J7oux7005612 for <ipv6@ietf.org>; Thu, 19 May 2016 09:50:57 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5349d862-1920-3137-617d-11ad75209e73@gmail.com>
Date: Thu, 19 May 2016 09:50:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_jT75Cg9jPNVrEuNvllxaRYKYno>
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, 19 May 2016 07:51:01 -0000

Le 19/05/2016 Ã  01:22, ç¥žæ˜Žé�”å“‰ a Ã©crit :
> At Tue, 17 May 2016 22:13:36 -0400, Fernando Gont
> <fgont@si6networks.com> wrote:
>
>>> From this one, and your response to the next point, it seems you
>>>  are saying the decision was to refuse to address that concern.
>>> Am I understanding it correctly?
>>
>> No. My take is that the concern is flawed. Please read
>> draft-gont-predictable-protocol-ids, and even RFC4941, which talks
>>  at length about security and privacy issues regarding reusing
>> identifiers in different context, for different scopes, etc.
>>
>> Let's call a lemon a lemon: Asking to embed a layer-2
>> identifier/address in a layer-3 address is extremely bad.
>
> I don't have a strong position on this matter itself, but my
> understanding of the sense of the wg is that this is controversial,
> and at least far from a clear consensus.  To repeat myself, *my*
> concern on this last call is that it's not even clear, at least to
> me, if this draft tries to say embedding a link-layer address is,
> whether it's randomized or not, "extremely bad" (and must therefore
> be prohibited).

This explanation makes me think of the following.

A true link-layer address, or a randomized link-layer address, embedded
(or not) in an Interface ID - is a matter of Ethernet only.  That could
lead to update "IPv6 over Ethernet" RFC 2464, and not create a new RFC
default-iids.

Moreover, it may be that people on cable Ethernet in Enterprise have
less privacy concern.  It's people on WiFi who do because they're more
mobile and no subject to internal codes of conduct.  And, unfortunately,
there is no "IPv6 over WiFi" RFC to update with this true link-layer vs
randomized link-layer address.  First, one should write an "IPv6 over
802.11" RFC.  Then we can talk about link-layer vs randomized in IID for
WiFi.

Second, this (true link-layer or radomized link-layer address in IID)
is not relevant for other link layers such as USB, or cellular wireless
access links, or others.  There is no worry here about 'true' vs
'random' link-layer address in the first place (whether in IID or not),
because there is no 'true' (i.e. IEEE-assisgned) link-layer address.  In
addition, on cellular links the prefix advertised in RA is unique per
terminal - so _that_ could be a privacy issue (not the IID).

Before privacy concerns, there is an issue to make IPv6 does run on
these links: people struggle to create 48bit addresses which can fill
the structures needed in IPv6 programming.  These addresses may look
random, but are actually based on hints, thus creating something
predictable.  The issue here is that is not standardized and may lead to
conflicts.  _After_ that conflict issue is solved, can we talk about
IID privacy issues of true-vs-random link-layer address in these links.

Alex


From nobody Thu May 19 01:09:35 2016
Return-Path: <alexandre.petrescu@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 D714F12B03E for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 01:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 zpFHlT7gnPcj for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 01:09:32 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42ECB12D0CA for <ipv6@ietf.org>; Thu, 19 May 2016 01:09:32 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4J89Uer011665 for <ipv6@ietf.org>; Thu, 19 May 2016 10:09:30 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 53A8E206856 for <ipv6@ietf.org>; Thu, 19 May 2016 10:09:32 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4A8D1206827 for <ipv6@ietf.org>; Thu, 19 May 2016 10:09:32 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4J89TNg005224 for <ipv6@ietf.org>; Thu, 19 May 2016 10:09:29 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e50d97c2-5fd3-a73b-355a-093814750d40@gmail.com>
Date: Thu, 19 May 2016 10:09:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fzEtgzoLBU1rLLVTg4Ct2WfN5X8>
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, 19 May 2016 08:09:35 -0000

Le 19/05/2016 Ã  07:19, Alissa Cooper a Ã©crit :
>
>> On May 18, 2016, at 4:22 PM, ç¥žæ˜Žé�”å“‰ <jinmei@wide.ad.jp> wrote:
>>
>> At Tue, 17 May 2016 22:13:36 -0400, Fernando Gont
>> <fgont@si6networks.com> wrote:
>>
>>>> From this one, and your response to the next point, it seems
>>>> you are saying the decision was to refuse to address that
>>>> concern.  Am I understanding it correctly?
>>>
>>> No. My take is that the concern is flawed. Please read
>>> draft-gont-predictable-protocol-ids, and even RFC4941, which
>>> talks at length about security and privacy issues regarding
>>> reusing identifiers in different context, for different scopes,
>>> etc.
>>>
>>> Let's call a lemon a lemon: Asking to embed a layer-2
>>> identifier/address in a layer-3 address is extremely bad.
>>
>> I don't have a strong position on this matter itself, but my
>> understanding of the sense of the wg is that this is
>> controversial, and at least far from a clear consensus.  To repeat
>> myself, *my* concern on this last call is that it's not even clear,
>> at least to me, if this draft tries to say embedding a link-layer
>> address is, whether it's randomized or not, "extremely bad" (and
>> must therefore be prohibited).  If that's the intent, it should be
>> clearly stated
>
> The draft makes just about a clear a statement in this vein as is
> possible:
>
> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
> that embed the underlying link-layer address in the IID.â€�
>
> Note that this statement does not prohibit anything, nor does it make
> a normative (in the moral sense) judgment. It just states the
> recommendation, which is the point of the document.
>
> I appreciate that not everyone on the list agrees with this
> recommendation. But I find the claim that this recommendation is
> unclear

I think that recommendation is too generic.

I think it should say:
"If a human user can be reassured during a privacy worry (avoid
  traceability of IP address by surveillance or commercial interests) -
  the EUI-64 SHOULD NOT contain the company_id (the first three octets),
  nor 0xFFFE, nor the last three octets of the Ethernet address"
  - and add it to RFC2464 section 4:
    https://tools.ietf.org/html/rfc2464#section4

I think on some non-Ethernet links there are some 48bit identifiers
which are not assigned by IEEE, but imagined by programmers. They are
not used as a link-layer address (they are not in src/dst headers of
link-layer messaging), but are there only to fill in IPv6 data
structures. Some times they are based on hints, other times they are
random. When they are Unix rand(), and if this can reassure the privacy
worry of a user: they could be put in the IID.

Alex

> to be difficult to understand. That is, I canâ€™t think of a way to
> convey the same recommendation that would be clearer. If you can,
> please suggest text.
>
> Alissa
>
>
>> and backed by a clear consensus from the wg.  Right now I don't see
>> either such a clear statement or clear wg consensus.
>>
>> -- JINMEI, Tatuya
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Thu May 19 01:38:27 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 4834B12D0CA for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 01:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 OjVeAp8KmrYO for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 01:38:23 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 2C3DE12B03F for <ipv6@ietf.org>; Thu, 19 May 2016 01:38:23 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id y2so23153501vka.3 for <ipv6@ietf.org>; Thu, 19 May 2016 01:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=XYw/4AmoOaVGVzBTp/io1rozTE6xflD+LEah9rif1vE=; b=lUiQZiL231VxHe3ZFkw+AgJj97cKjRVbSQZs4LAnKnp9l5Aw8fCSgnTDNjyuU5IWmg /doPAgLyQNUq9h1m3PnblEV7K+/fs/8e+386pwWbJfHhxsqOriQZ/qZRvjpFyYVG4MW3 4AP1z5ExLkRBAOqId/w9ueAPL2rKiwVdH4wISJvUDoEFhgBO5YLxj86rufP0mZrh/++I hkuUPr6tPfd2P2mvp6C8/1ta1BPjDPDncFGpcU0mynbcoYUf6AVU1seyPmXW4oKYDxOk GHKU5ZDiYLOb0urd8Y5HuDxSATzZUYVxzB7+/PXXLeoQYh/KpzRvCSSfJCsWL3e2gYMe 5FPg==
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:date :message-id:subject:from:to:cc; bh=XYw/4AmoOaVGVzBTp/io1rozTE6xflD+LEah9rif1vE=; b=OFXrSuq1GnbY/Ui+cuqJxjat9mu8TKc8tPDxN5aRddavN+z//eTu7ltf/TMK48xk4O 9t7CGfP6JEuzOWnwna262JdaTn+UVVLbTBqW3iPViSDnJOMw/Ueai1UqW9x7xilXG83u G/1gEqxefVt+Nq9Gj5uuJi/7iMLsRBMaRYe5gwK14PXnuyZdj4qEwkB0lp3oYWJWwFX0 lRAqWHgHa2n5YXlLIL8uavQ07UMI9eUyuzRDk/z1y2RLB2uMk99YyFWInNBahwf1yl4o HUSoF0hnZ8bJ2Z5rh3ua3vxPzdgvd/TEliCMLCBtqZnNTUtQddiEWtainPJcG9dZuXIL r8hQ==
X-Gm-Message-State: AOPr4FVeAkWxu4BhC0COTWA2mOLaGQDpcKc6Dconyl2F4zk2RyrwdwikaGIp5EjpAGhSeQbsToclIi99VyRxLw==
MIME-Version: 1.0
X-Received: by 10.159.34.9 with SMTP id 9mr3508090uad.25.1463647102204; Thu, 19 May 2016 01:38:22 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 19 May 2016 01:38:21 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 19 May 2016 01:38:21 -0700 (PDT)
In-Reply-To: <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
Date: Thu, 19 May 2016 18:38:21 +1000
Message-ID: <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a113dfd349a84f005332de5b9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tgDuF8kbvwPedOeYJm1TGmev-Yg>
Cc: Fernando Gont <fgont@si6networks.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bob Hinden <bob.hinden@gmail.com>, IPv6 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: Thu, 19 May 2016 08:38:25 -0000

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

On 19 May 2016 4:11 PM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>> The draft makes just about a clear a statement in this vein as is
possible:
>>
>> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
>>    that embed the underlying link-layer address in the IID.=E2=80=9D
>>
>> Note that this statement does not prohibit anything, nor does it make a
normative (in the moral sense) judgment. It just states the recommendation,
which is the point of the document.
>>
>> I appreciate that not everyone on the list agrees with this
recommendation. But I find the claim that this recommendation is unclear to
be difficult to understand. That is, I can=E2=80=99t think of a way to conv=
ey the
same recommendation that would be clearer. If you can, please suggest text.
>
>
> Alissa,
>
> I don't think anybody is claiming that the recommendation itself is
difficult to understand. What is difficult to understand is how the
document justifies that claim.
>
> It looks like the main argument used to justify this recommendation is
major privacy risks. But embedding a link layer identifier into an IP
address is not a major [1] privacy risk. It is only embedding a *STABLE*
link-layer address that is a major privacy risk.
>
> Recommending that link-layer address be embedded only if they are
ephemeral would address the privacy concerns just as well as (or maybe even
better) than the approach proposed in this document.
>

So how would the IPv6 layer test that, and if it was tested properly, what
happens if the test fails?

I think the testing of layer 2 address randomisation, and coming up with a
both a user acceptable and friendly scheme to deal with a test failure is
harder and more complex that just universally applying RFC7217 to all past,
current and future link layers, regardless of how good or bad their link
layer addresses are.

It fits the principle of having a single and general solution for all cases
rather than having tests, dealing with exceptions and individual
case-by-case solutions.

IPv6 has followed a theme of trying to generalise functions from layer 2
into layer 3 (e.g.,  ND over ICMPv6 rather than link specific versions of
ND, DHCPv6 over IPv6 over PPP rather than DNS etc. in IPV6CP etc.).

This IPv6 address privacy problem exists at the IPv6 layer. Solve it at the
IPv6 layer and it has only needed to be solved once, rather than
repeatedly, and has been solved universally.

> I think what people are do not understand is why this document recommends
one but not the other. I certainly don't.

RFC1958 explains it:

"The Internet level protocol must be independent of the hardware medium and
hardware addressing."

RFC7217 is fixing a mistake as well as increasing privacy.

Regards,
Mark.

> Cheers,
> Lorenzo
>
> [1] I argue that cross-referencing IPX traffic to IP traffic is not a
major privacy risk because IPX is so uncommon.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<p dir=3D"ltr"><br>
On 19 May 2016 4:11 PM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:l=
orenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper &lt;<a href=3D"mailto:a=
lissa@cooperw.in">alissa@cooperw.in</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; The draft makes just about a clear a statement in this vein as is =
possible:<br>
&gt;&gt;<br>
&gt;&gt; &quot;By default, nodes SHOULD NOT employ IPv6 address generation =
schemes<br>
&gt;&gt; =C2=A0 =C2=A0that embed the underlying link-layer address in the I=
ID.=E2=80=9D<br>
&gt;&gt;<br>
&gt;&gt; Note that this statement does not prohibit anything, nor does it m=
ake a normative (in the moral sense) judgment. It just states the recommend=
ation, which is the point of the document.<br>
&gt;&gt;<br>
&gt;&gt; I appreciate that not everyone on the list agrees with this recomm=
endation. But I find the claim that this recommendation is unclear to be di=
fficult to understand. That is, I can=E2=80=99t think of a way to convey th=
e same recommendation that would be clearer. If you can, please suggest tex=
t.<br>
&gt;<br>
&gt;<br>
&gt; Alissa,<br>
&gt;<br>
&gt; I don&#39;t think anybody is claiming that the recommendation itself i=
s difficult to understand. What is difficult to understand is how the docum=
ent justifies that claim.<br>
&gt;<br>
&gt; It looks like the main argument used to justify this recommendation is=
 major privacy risks. But embedding a link layer identifier into an IP addr=
ess is not a major [1]=C2=A0privacy risk. It is only embedding a *STABLE* l=
ink-layer address that is a major privacy risk.<br>
&gt;<br>
&gt; Recommending that link-layer address be embedded only if they are ephe=
meral would address the privacy concerns just as well as (or maybe even bet=
ter) than the approach proposed in this document.<br>
&gt;</p>
<p dir=3D"ltr">So how would the IPv6 layer test that, and if it was tested =
properly, what happens if the test fails?</p>
<p dir=3D"ltr">I think the testing of layer 2 address randomisation, and co=
ming up with a both a user acceptable and friendly scheme to deal with a te=
st failure is harder and more complex that just universally applying RFC721=
7 to all past, current and future link layers, regardless of how good or ba=
d their link layer addresses are.</p>
<p dir=3D"ltr">It fits the principle of having a single and general solutio=
n for all cases rather than having tests, dealing with exceptions and indiv=
idual case-by-case solutions.</p>
<p dir=3D"ltr">IPv6 has followed a theme of trying to generalise functions =
from layer 2 into layer 3 (e.g.,=C2=A0 ND over ICMPv6 rather than link spec=
ific versions of ND, DHCPv6 over IPv6 over PPP rather than DNS etc. in IPV6=
CP etc.).</p>
<p dir=3D"ltr">This IPv6 address privacy problem exists at the IPv6 layer. =
Solve it at the IPv6 layer and it has only needed to be solved once, rather=
 than repeatedly, and has been solved universally.<br></p>
<p dir=3D"ltr">&gt; I think what people are do not understand is why this d=
ocument recommends one but not the other. I certainly don&#39;t.</p>
<p dir=3D"ltr">RFC1958 explains it:</p>
<p dir=3D"ltr">&quot;The Internet level protocol must be independent of the=
 hardware medium and hardware addressing.&quot;</p>
<p dir=3D"ltr">RFC7217 is fixing a mistake as well as increasing privacy.</=
p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; Cheers,<br>
&gt; Lorenzo<br>
&gt;<br>
&gt; [1] I argue that cross-referencing IPX traffic to IP traffic is not a =
major privacy risk because IPX is so uncommon.<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>
&gt;<br>
</p>

--001a113dfd349a84f005332de5b9--


From nobody Thu May 19 02:04:17 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 2950212D135 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 BiC_UJI7D3Hz for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:04:14 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 940A712D0F6 for <ipv6@ietf.org>; Thu, 19 May 2016 02:04:14 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id j74so71731515ywg.1 for <ipv6@ietf.org>; Thu, 19 May 2016 02:04:14 -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=e9WUsVF6Dm8Q35y/3THRh9LSHWTTcNdD2a9fgAsxdaU=; b=oqZUkV/jgcKDKwDi/n570J2qK7oVVGDGeZqGWgZLItvtLpO5CekAAzL8vc08N8R92B 8e75d8ksDaoYM/gY5WFnNplZen2mpeCEufSyhzTuURfqJZkEyOh9d4oQjFDvcIVk74Sr UId9GQESrvaWBG9eKUsXfIJjb+GKUQDcMoSq5UwLCOJ9d+qTVH52o3TYzfy9Ap2fipVz n6nIKzscGpuz+7k+RgXRZlpIqOwhJchCS9MZis9AAVKOM+RxFR4zzJsvlLd2L1osaQc4 kc4xXj2ZLEx74v7ufVqubhyQKeCFWTppi0UWquTesXom7GPId13VzvbhvOitsD9VQFlw B3rQ==
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=e9WUsVF6Dm8Q35y/3THRh9LSHWTTcNdD2a9fgAsxdaU=; b=KqctOkblOLDHiArt3F4SwBa1XtwiQ+wrBoqCx1BHXj1M8hoVGgulAsYZ9qhFTStX35 tK1ODzr6iiph3mNBGUNGTcKoOdDzzy/qhr1I9UqTvQnXLxdU2BecIpT2dYv8gXE1MwgB IcDfvDd0bXlqtFptcXSSmMpkUPbtZHKYZu3PYtJGYfSB8BlzbZqDnczoT154n0RYOQMQ NmwiAi7X1YP7Yu0p/G5jB5I3Emfg7ANUicNGgPXQqEVmfA0v4hNcOSAA0dkIJ4ZHPUpL +zkMskz2fsZhs1lXew2+l4JCDH/KPEBS7ecxa9qasdUztiOsKq9uZ7naPAGmoZhO0Agt R8fw==
X-Gm-Message-State: AOPr4FVieAJ94dvyGF8JwbbfZfPhIKufhzQ9RzsF4MIZQMtK3dG5M3pFbYLJPS8HvylYBSYam/1SofyKVSD8KYWc
X-Received: by 10.129.80.11 with SMTP id e11mr7029241ywb.197.1463648653665; Thu, 19 May 2016 02:04:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 19 May 2016 02:03:53 -0700 (PDT)
In-Reply-To: <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 19 May 2016 18:03:53 +0900
Message-ID: <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a1147d2b214674305332e4257
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Pfb48v-G33u1Hn1-S6C9o93p0ik>
Cc: Fernando Gont <fgont@si6networks.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bob Hinden <bob.hinden@gmail.com>, IPv6 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: Thu, 19 May 2016 09:04:16 -0000

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

On Thu, May 19, 2016 at 5:38 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

> So how would the IPv6 layer test that, and if it was tested properly, what
> happens if the test fails?
>
The code that configures both layer 2 and layer 3 can simply call
arc4random_buf (or your favourite random function) and then "ifconfig wlan0
hw ether <foo>", and then pick an EUI-64 IID based on that. Even if the
hardware does not support the hardware address and does not return an
error, but silently continues to use the hardware MAC address, the
resulting IPv6 address is still random and free from privacy concerns.

> I think the testing of layer 2 address randomisation, and coming up with a
> both a user acceptable and friendly scheme to deal with a test failure is
> harder and more complex that just universally applying RFC7217 to all past,
> current and future link layers, regardless of how good or bad their link
> layer addresses are.
>
This is really not hard to test in any hardware qualification lab. Really,
it isn't.

--001a1147d2b214674305332e4257
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=
hu, May 19, 2016 at 5:38 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&g=
t;</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""><p dir=
=3D"ltr">So how would the IPv6 layer test that, and if it was tested proper=
ly, what happens if the test fails?<br></p></span></blockquote><div>The cod=
e that configures both layer 2 and layer 3 can simply call arc4random_buf (=
or your favourite random function) and then &quot;ifconfig wlan0 hw ether &=
lt;foo&gt;&quot;, and then pick an EUI-64 IID based on that. Even if the ha=
rdware does not support the hardware address and does not return an error, =
but silently continues to use the hardware MAC address, the resulting IPv6 =
address is still random and free from privacy concerns.</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><span class=3D""><p dir=3D"ltr"></p></span>
<p dir=3D"ltr">I think the testing of layer 2 address randomisation, and co=
ming up with a both a user acceptable and friendly scheme to deal with a te=
st failure is harder and more complex that just universally applying RFC721=
7 to all past, current and future link layers, regardless of how good or ba=
d their link layer addresses are.</p></blockquote><div>This is really not h=
ard to test in any hardware qualification lab. Really, it isn&#39;t.</div><=
/div></div></div>

--001a1147d2b214674305332e4257--


From nobody Thu May 19 02:10:28 2016
Return-Path: <alexandre.petrescu@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 8BB4912D124 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.333
X-Spam-Level: 
X-Spam-Status: No, score=-4.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 GZ3hZPkCbM5E for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 02:10:26 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8F3012B00E for <ipv6@ietf.org>; Thu, 19 May 2016 02:10:25 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4J9ANrf016387 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:23 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C4A61206988 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:25 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BAA912069C0 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:25 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4J9ANj4007060 for <ipv6@ietf.org>; Thu, 19 May 2016 11:10:23 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
Date: Thu, 19 May 2016 11:10:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GsT93papqlKMy5bnC7bLzXNTGBY>
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, 19 May 2016 09:10:27 -0000

Le 19/05/2016 à 11:03, Lorenzo Colitti a écrit :
> On Thu, May 19, 2016 at 5:38 PM, Mark Smith <markzzzsmith@gmail.com
> <mailto:markzzzsmith@gmail.com>> wrote:
>
> So how would the IPv6 layer test that, and if it was tested properly,
> what happens if the test fails?
>
> The code that configures both layer 2 and layer 3 can simply call
> arc4random_buf (or your favourite random function)

I think the question is to decide when to call that random
function.

A 48bit identifier is often there already, but we need to use if it's
random, or generate one if it's not random.  So how to test whether it's
random?

> and then "ifconfig wlan0 hw ether <foo>", and then pick an EUI-64 IID
> based on that. Even if the hardware does not support the hardware
> address and does not return an error, but silently continues to use
> the hardware MAC address, the resulting IPv6 address is still random
> and free from privacy concerns.
>
> I think the testing of layer 2 address randomisation, and coming up
> with a both a user acceptable and friendly scheme to deal with a test
> failure is harder and more complex that just universally applying
> RFC7217 to all past, current and future link layers, regardless of
> how good or bad their link layer addresses are.
>
> This is really not hard to test in any hardware qualification lab.
> Really, it isn't.

On the contrary, I think it is very hard to test a number to see whether
it's random - you need a very expensive lab and out-of-band info.

Alex

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


From nobody Thu May 19 03:36:24 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 0DA7212B058 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 03:36:22 -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_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 (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 5cZbIRdtWfvd for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 03:36:18 -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 EB51712D8A5 for <6man@ietf.org>; Thu, 19 May 2016 03:36:15 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0176.outbound.protection.outlook.com [213.199.154.176]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-44-CHCGtfitTOODcocx7OSbLw-1; Thu, 19 May 2016 11:36:07 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CASksf0dWzf493SGZmABIxtDPPaD+Cw+U1OwunCQBVM=; b=kfMf+BWUEFU87gXX5ey3tG03ovRLX7/Hn6mGTvAp2r4qb03ksCjM52XsoMxmJdA7NJ4huLmCLs+MXGqr+dOL806StdIYS3cAdjDayNEP9mzka8iEHCTpEsU9BfKc6XswdtgzNxRSbZdlJx59rrqeXDC6aVM/Cfjh1KQis/OuUyI=
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) with Microsoft SMTP Server (TLS) id 15.1.501.7; Thu, 19 May 2016 10:36:06 +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.0501.007; Thu, 19 May 2016 10:36:06 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: default-iids and stable addresses
Thread-Topic: default-iids and stable addresses
Thread-Index: AQHRsJvx2z8IgTbOiU+7vY3x6SBpsJ++/8CAgACAYwCAAJMjgA==
Date: Thu, 19 May 2016 10:36:05 +0000
Message-ID: <19F2546A-5EB0-45D9-A827-AC81A4C8BCD9@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <CAJE_bqdXt_jC2GCc-SRXAfRTybYd88ZdSMpnny2oJUMnscnyOQ@mail.gmail.com> <CAKD1Yr3U+UwopiXA9SgMGHm6BHGVmSMistyUhqqYpxYNZC4tUg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3U+UwopiXA9SgMGHm6BHGVmSMistyUhqqYpxYNZC4tUg@mail.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:a1f2:d0e0:e998:fd6b]
x-ms-office365-filtering-correlation-id: 290639e6-7067-40ef-7fe5-08d37fd16218
x-microsoft-exchange-diagnostics: 1; AMSPR07MB455; 5:NmL059WR16e1IOd/1nmjT0VqpNN9F+ra43rdbDIeIAya84VUjV3wUAFdvFInedIlXpHrgKxp/tPKQ2TVIoIvD48UNky35Q82S4oAWNHbmW/j4Bz7/ECh9/s8NgHeDqNGhegB+xiAMzePTxTZtGA78A==; 24:QRDtUUXzbCYMQRAV8PpUs1m+eQvuQztUFSc1Ek+h560fw7RNOKMECzswaHO1cL80GCo1npX6Uejr99s1rJ38JeOQDFpWKBOMt3zBSX07RWc=; 7:0yK/SMqF7g2HlZWPVP/RqqW9pK5AZiCmAcrpKGVjkYgJLTuIkJ+blhjSC4HShZDlSqC32afHAMxP5QGytD+HZTCuOTHh2eLqKuKKxjx4GIWRls+FmHzV7A0LWCapM5F/VLE/T/MrSbE1P31IAxbANLzvAlH/BosB/mw/lT2+L/jtyUDpPuoVy8dHaFMtFwPa; 20:UmWDVs2y5CgiJgr2mYRP4nz5hPSgG/GlTP8tnyupTsV99lixVxVROFtuVOGw/V1t9kWbWc5oHtR3J/qRmbqMKKlRlmyOMbUemenFhpRIygqblYRdXSBI6qxqtenVQPdIgM35DViQM22nGFKfbKBeoEdJJyoS1AbvMA+tvMWxYcg=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB455;
x-microsoft-antispam-prvs: <AMSPR07MB455B8ADBA35A3F3D136EE94D64A0@AMSPR07MB455.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046); SRVR:AMSPR07MB455; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB455; 
x-forefront-prvs: 094700CA91
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(51694002)(377454003)(24454002)(11100500001)(74482002)(5002640100001)(110136002)(4326007)(86362001)(57306001)(189998001)(92566002)(19617315012)(77096005)(15975445007)(5008740100001)(87936001)(83716003)(2950100001)(81166006)(5004730100002)(2900100001)(33656002)(76176999)(8676002)(10400500002)(50986999)(16236675004)(8936002)(3480700004)(50226002)(122556002)(19580405001)(102836003)(6116002)(36756003)(19580395003)(1220700001)(2906002)(586003)(82746002)(106116001)(3826002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB455; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 May 2016 10:36:05.8162 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB455
X-MC-Unique: CHCGtfitTOODcocx7OSbLw-1
Content-Type: multipart/alternative; boundary="_000_19F2546A5EB045D9A827AC81A4C8BCD9jiscacuk_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Axm3sJjRyIXj5cqD8uzDdxBlkVQ>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Fernando Gont <fernando@gont.com.ar>
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, 19 May 2016 10:36:22 -0000

--_000_19F2546A5EB045D9A827AC81A4C8BCD9jiscacuk_
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

T24gMTkgTWF5IDIwMTYsIGF0IDAyOjQ5LCBMb3JlbnpvIENvbGl0dGkgPGxvcmVuem9AZ29vZ2xl
LmNvbTxtYWlsdG86bG9yZW56b0Bnb29nbGUuY29tPj4gd3JvdGU6DQoNCk9uIFRodSwgTWF5IDE5
LCAyMDE2IGF0IDM6MDkgQU0sIOelnuaYjumBlOWTiSA8amlubWVpQHdpZGUuYWQuanA8bWFpbHRv
Omppbm1laUB3aWRlLmFkLmpwPj4gd3JvdGU6DQo+IEFzIGEgY28tYXV0aG9yIG9mIGRyYWZ0LWll
dGYtNm1hbi1kZWZhdWx0LWlpZHMsIEkganVzdCB3YW50ZWQgdG8gY2hlY2sNCj4gdGhhdCB3ZSdy
ZSBvbiB0aGUgc2FtZSBwYWdlLCBiZWNhdXNlIEkgaGF2ZSB0aGUgZmVlbGluZyB0aGF0IHRoZSBh
Ym92ZQ0KPiBrZWVwcyBnZXR0aW5nIG1pc2ludGVycHJldGVkLg0KDQpNaXNpbnRlcnByZXRhdGlv
biAoSSdkIGNhbGwgaXQgY29uZnVzaW9uIGluIHRoaXMgY29udGV4dCwgdGhvdWdoKSBvZiBhDQpk
b2N1bWVudCBvZnRlbiBoYXBwZW5zIGJlY2F1c2UgdGhlIGRvY3VtZW50IGlzbid0IGNsZWFyIGVu
b3VnaA0KDQorMQ0KDQpJIGFncmVlIHRoYXQgaXTigJlzIGF0IGJlc3QgYW1iaWd1b3VzLg0KDQpT
ZWN0aW9uIDMgc2F5czoNCg0KIjEuIERvIG5vdCByZXN1bHQgaW4gYW55IGNoYW5nZXMgdG8gdGhl
IGJhc2ljIGJlaGF2aW9yIG9mIGFkZHJlc3Nlcw0KDQogICAgICAgZ2VuZXJhdGVkIHZpYSBzdGF0
ZWxlc3MgYWRkcmVzcyBhdXRvY29uZmlndXJhdGlvbiBbQUREUkNPTkY8aHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL3JmYzQ5NDEjcmVmLUFERFJDT05GPl0uDQoNCg0Kd2hpY2ggaW1wbGllcyB0
aGF0IFNMQUFDIHN0aWxsIHJ1bnMgYXMgbm9ybWFsLCBzbyB5b3UgZ2V0IGEgcHVibGljIGFkZHJl
c3MgZnJvbSB0aGF0LCBhbmQNCg0KDQoyLiAgQ3JlYXRlIGFkZGl0aW9uYWwgYWRkcmVzc2VzIGJh
c2VkIG9uIGEgcmFuZG9tIGludGVyZmFjZQ0KICAgICAgIGlkZW50aWZpZXIgZm9yIHRoZSBwdXJw
b3NlIG9mIGluaXRpYXRpbmcgb3V0Z29pbmcgc2Vzc2lvbnMuIg0KDQp3aGljaCBpbXBsaWVzIHRo
ZSB0ZW1wb3JhcnkgYWRkcmVzcyBpcyAqaW4gYWRkaXRpb24qIHRvIHRoZSBTTEFBQy1kZXJpdmVk
IGFkZHJlc3MsIHVubGVzcyB5b3UgaG9sZCB0aGUg4oCcVGFrZSBzb21lIG1vcmUgdGVhIEFsaWNl
4oCdIHZpZXcgb2YgYWRkaXRpb25hbC4NCg0KVGhlbiAzLjEgc2F5czoNCg0KIltBRERSX1NFTEVD
VDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDk0MSNyZWYtQUREUl9TRUxFQ1Q+XSBt
YW5kYXRlcyBpbXBsZW1lbnRhdGlvbnMgdG8gcHJvdmlkZSBhIG1lY2hhbmlzbSwgd2hpY2gNCg0K
ICAgYWxsb3dzIGFuIGFwcGxpY2F0aW9uIHRvIGNvbmZpZ3VyZSBpdHMgcHJlZmVyZW5jZSBmb3Ig
dGVtcG9yYXJ5DQogICBhZGRyZXNzZXMgb3ZlciBwdWJsaWMgYWRkcmVzc2VzLuKAnA0KDQp3aGlj
aCBpbXBsaWVzIGJvdGggYXJlIGNvbmZpZ3VyZWQuDQoNCkFuZCB0aGVuIHNlY3Rpb24gMy4zIHNh
eXMgdGhlIG5vZGUgTVVTVDoNCg0KIlByb2Nlc3MgdGhlIFByZWZpeCBJbmZvcm1hdGlvbiBPcHRp
b24gYXMgZGVmaW5lZCBpbiBbQUREUkNPTkY8aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3Jm
YzQ5NDEjcmVmLUFERFJDT05GPl0NCmVpdGhlciBjcmVhdGluZyBhIG5ldyBwdWJsaWMgYWRkcmVz
cyBvciBhZGp1c3RpbmcgdGhlIGxpZmV0aW1lcw0KDQogICAgICAgb2YgZXhpc3RpbmcgYWRkcmVz
c2VzLCBib3RoIHB1YmxpYyBhbmQgdGVtcG9yYXJ5LuKAnA0KDQpTbyB0aGVyZeKAmXMgYSBsb3Qg
b2YgdGV4dCBpbXBseWluZyB0ZW1wb3JhcnkgYWRkcmVzc2VzIGFyZSB1c2VkIGFsb25nc2lkZSBw
dWJsaWMgb25lcywgYW5kIHRodXMgdGhhdCBhbWJpZ3VpdHkgc2hvdWxkIGJlIGNsYXJpZmllZC4N
Cg0KQnV0IGFnYWluIEkgYWdyZWUgd2Ugc2hvdWxkIG1ha2UgaXQgY2xlYXIgdGhhdCB0aGF0IG5l
ZWQgbm90IGJlIHRoZSBjYXNlLg0KDQpUaW0NCg0KDQo=
--_000_19F2546A5EB045D9A827AC81A4C8BCD9jiscacuk_
Content-Type: text/html; charset=UTF-8
Content-ID: <06ED5131BFF0BE48ABE500384E83EA05@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdj4NCjxibG9ja3F1b3RlIHR5
cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiAxOSBNYXkgMjAxNiwgYXQgMDI6
NDksIExvcmVuem8gQ29saXR0aSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxvcmVuem9AZ29vZ2xlLmNv
bSIgY2xhc3M9IiI+bG9yZW56b0Bnb29nbGUuY29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIg
Y2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYg
ZGlyPSJsdHIiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPg0KPGRpdiBjbGFz
cz0iZ21haWxfcXVvdGUiPk9uIFRodSwgTWF5IDE5LCAyMDE2IGF0IDM6MDkgQU0sIOelnuaYjumB
lOWTiSA8c3BhbiBkaXI9Imx0ciIgY2xhc3M9IiI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOmppbm1l
aUB3aWRlLmFkLmpwIiB0YXJnZXQ9Il9ibGFuayIgY2xhc3M9IiI+amlubWVpQHdpZGUuYWQuanA8
L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgY2xhc3M9Imdt
YWlsX3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mg
c29saWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8c3BhbiBjbGFzcz0iIj4mZ3Q7IEFzIGEgY28tYXV0
aG9yIG9mIGRyYWZ0LWlldGYtNm1hbi1kZWZhdWx0LWlpZHMsIEkganVzdCB3YW50ZWQgdG8gY2hl
Y2s8YnIgY2xhc3M9IiI+DQomZ3Q7IHRoYXQgd2UncmUgb24gdGhlIHNhbWUgcGFnZSwgYmVjYXVz
ZSBJIGhhdmUgdGhlIGZlZWxpbmcgdGhhdCB0aGUgYWJvdmU8YnIgY2xhc3M9IiI+DQomZ3Q7IGtl
ZXBzIGdldHRpbmcgbWlzaW50ZXJwcmV0ZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
PC9zcGFuPk1pc2ludGVycHJldGF0aW9uIChJJ2QgY2FsbCBpdCBjb25mdXNpb24gaW4gdGhpcyBj
b250ZXh0LCB0aG91Z2gpIG9mIGE8YnIgY2xhc3M9IiI+DQpkb2N1bWVudCBvZnRlbiBoYXBwZW5z
IGJlY2F1c2UgdGhlIGRvY3VtZW50IGlzbid0IGNsZWFyIGVub3VnaDwvYmxvY2txdW90ZT4NCjxk
aXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiYjNDM7MSZu
YnNwOzwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+SSBhZ3JlZSB0aGF0IGl04oCZcyBhdCBiZXN0
IGFtYmlndW91cy48L2Rpdj4NCjxkaXY+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2PlNlY3Rp
b24gMyBzYXlzOjwvZGl2Pg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+JnF1b3Q7
PHNwYW4gc3R5bGU9IndpZG93czogMTsiIGNsYXNzPSIiPjEuIERvIG5vdCByZXN1bHQgaW4gYW55
IGNoYW5nZXMgdG8gdGhlIGJhc2ljIGJlaGF2aW9yIG9mIGFkZHJlc3Nlczwvc3Bhbj48L2Rpdj4N
CjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0
b206IDBweDsgZm9udC12YXJpYW50LWxpZ2F0dXJlczogbm9ybWFsOyBmb250LXZhcmlhbnQtcG9z
aXRpb246IG5vcm1hbDsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50
LWFsdGVybmF0ZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGlu
ZS1oZWlnaHQ6IG5vcm1hbDsgd2lkb3dzOiAxOyI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFz
cz0iIj4gICAgICAgZ2VuZXJhdGVkIHZpYSBzdGF0ZWxlc3MgYWRkcmVzcyBhdXRvY29uZmlndXJh
dGlvbiBbPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ5NDEjcmVmLUFE
RFJDT05GIiB0aXRsZT0iJnF1b3Q7SVB2NiBTdGF0ZWxlc3MgQWRkcmVzcyBBdXRvY29uZmlndXJh
dGlvbiZxdW90OyIgY2xhc3M9IiI+QUREUkNPTkY8L2E+XS48L2ZvbnQ+PC9wcmU+DQo8cHJlIGNs
YXNzPSJuZXdwYWdlIiBzdHlsZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7
IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LXBvc2l0aW9uOiBu
b3JtYWw7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1hbHRlcm5h
dGVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0
OiBub3JtYWw7IHdpZG93czogMTsiPjxmb250IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+PGJy
IGNsYXNzPSIiPjwvZm9udD48L3ByZT4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJtYXJn
aW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgZm9udC12YXJpYW50LWxpZ2F0dXJlczog
bm9ybWFsOyBmb250LXZhcmlhbnQtcG9zaXRpb246IG5vcm1hbDsgZm9udC12YXJpYW50LW51bWVy
aWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWFsdGVybmF0ZXM6IG5vcm1hbDsgZm9udC12YXJpYW50
LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgd2lkb3dzOiAxOyI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IiBjbGFzcz0iIj53aGljaCBpbXBsaWVz
IHRoYXQgU0xBQUMgc3RpbGwgcnVucyBhcyBub3JtYWwsIHNvIHlvdSBnZXQgYSBwdWJsaWMgYWRk
cmVzcyBmcm9tIHRoYXQsIGFuZDwvc3Bhbj48L3ByZT4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0
eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgZm9udC12YXJpYW50LWxp
Z2F0dXJlczogbm9ybWFsOyBmb250LXZhcmlhbnQtcG9zaXRpb246IG5vcm1hbDsgZm9udC12YXJp
YW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWFsdGVybmF0ZXM6IG5vcm1hbDsgZm9u
dC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgd2lkb3dz
OiAxOyI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+PC9zcGFuPjwvcHJlPg0KPHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9Im1hcmdp
bi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBu
b3JtYWw7IGZvbnQtdmFyaWFudC1wb3NpdGlvbjogbm9ybWFsOyBmb250LXZhcmlhbnQtbnVtZXJp
Yzogbm9ybWFsOyBmb250LXZhcmlhbnQtYWx0ZXJuYXRlczogbm9ybWFsOyBmb250LXZhcmlhbnQt
ZWFzdC1hc2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDogbm9ybWFsOyB3aWRvd3M6IDE7Ij48cHJl
IGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAw
cHg7IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LXBvc2l0aW9u
OiBub3JtYWw7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1hbHRl
cm5hdGVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVp
Z2h0OiBub3JtYWw7Ij48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjIuICBDcmVhdGUg
YWRkaXRpb25hbCBhZGRyZXNzZXMgYmFzZWQgb24gYSByYW5kb20gaW50ZXJmYWNlDQogICAgICAg
aWRlbnRpZmllciBmb3IgdGhlIHB1cnBvc2Ugb2YgaW5pdGlhdGluZyBvdXRnb2luZyBzZXNzaW9u
cy4mcXVvdDs8L2ZvbnQ+PC9wcmU+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2Ei
IGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNzPSIiPndoaWNoIGltcGxpZXMgdGhl
IHRlbXBvcmFyeSBhZGRyZXNzIGlzICppbiBhZGRpdGlvbiogdG8gdGhlIFNMQUFDLWRlcml2ZWQg
YWRkcmVzcywgdW5sZXNzIHlvdSBob2xkIHRoZSDigJxUYWtlIHNvbWUgbW9yZSB0ZWEgQWxpY2Xi
gJ0gdmlldyBvZiBhZGRpdGlvbmFsLjwvc3Bhbj48L2Rpdj48ZGl2IGNsYXNzPSIiPjxmb250IGZh
Y2U9IkhlbHZldGljYSIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPjwvZm9udD48L2Rpdj48ZGl2IGNs
YXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+VGhlbiAzLjEgc2F5czo8L2Zv
bnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRp
Y2EiIGNsYXNzPSIiPiZxdW90O1s8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
cmZjNDk0MSNyZWYtQUREUl9TRUxFQ1QiIHRpdGxlPSImcXVvdDtEZWZhdWx0IEFkZHJlc3MgU2Vs
ZWN0aW9uIGZvciBJbnRlcm5ldCBQcm90b2NvbCB2ZXJzaW9uIDYgKElQdjYpJnF1b3Q7IiBjbGFz
cz0iIj5BRERSX1NFTEVDVDwvYT5dIG1hbmRhdGVzIGltcGxlbWVudGF0aW9ucyB0byBwcm92aWRl
IGEgbWVjaGFuaXNtLCB3aGljaDwvZm9udD48L2Rpdj48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHls
ZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IGZvbnQtdmFyaWFudC1saWdh
dHVyZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LXBvc2l0aW9uOiBub3JtYWw7IGZvbnQtdmFyaWFu
dC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1hbHRlcm5hdGVzOiBub3JtYWw7IGZvbnQt
dmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij48Zm9udCBm
YWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPiAgIGFsbG93cyBhbiBhcHBsaWNhdGlvbiB0byBjb25m
aWd1cmUgaXRzIHByZWZlcmVuY2UgZm9yIHRlbXBvcmFyeQ0KICAgYWRkcmVzc2VzIG92ZXIgcHVi
bGljIGFkZHJlc3Nlcy7igJw8L2ZvbnQ+PC9wcmU+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJI
ZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0i
Ij48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPndoaWNoIGltcGxpZXMgYm90aCBhcmUg
Y29uZmlndXJlZC48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRp
Y2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9u
dCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPkFuZCB0aGVuIHNlY3Rpb24gMy4zIHNheXMgdGhl
IG5vZGUgTVVTVDo8L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRp
Y2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9u
dCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPiZxdW90O1Byb2Nlc3MgdGhlIFByZWZpeCBJbmZv
cm1hdGlvbiBPcHRpb24gYXMgZGVmaW5lZCBpbiZuYnNwOzwvZm9udD48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNzPSIiPls8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL3JmYzQ5NDEjcmVmLUFERFJDT05GIiB0aXRsZT0iJnF1b3Q7SVB2
NiBTdGF0ZWxlc3MgQWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbiZxdW90OyIgc3R5bGU9ImZvbnQt
ZmFtaWx5OiBIZWx2ZXRpY2E7IiBjbGFzcz0iIj5BRERSQ09ORjwvYT48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNzPSIiPl08L3NwYW4+PC9kaXY+PGRpdiBjbGFzcz0i
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNzPSIiPiAgICAgICBl
aXRoZXIgY3JlYXRpbmcgYSBuZXcgcHVibGljIGFkZHJlc3Mgb3IgYWRqdXN0aW5nIHRoZSBsaWZl
dGltZXM8L3NwYW4+PC9kaXY+PHByZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9Im1hcmdpbi10b3A6
IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7
IGZvbnQtdmFyaWFudC1wb3NpdGlvbjogbm9ybWFsOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9y
bWFsOyBmb250LXZhcmlhbnQtYWx0ZXJuYXRlczogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1h
c2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDogbm9ybWFsOyI+PGZvbnQgZmFjZT0iSGVsdmV0aWNh
IiBjbGFzcz0iIj4gICAgICAgb2YgZXhpc3RpbmcgYWRkcmVzc2VzLCBib3RoIHB1YmxpYyBhbmQg
dGVtcG9yYXJ5LjwvZm9udD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNs
YXNzPSIiPuKAnDwvc3Bhbj48L3ByZT48ZGl2IGNsYXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGlj
YSIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPjwvZm9udD48L2Rpdj48ZGl2IGNsYXNzPSIiPjxmb250
IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+U28gdGhlcmXigJlzIGEgbG90IG9mIHRleHQgaW1w
bHlpbmcgdGVtcG9yYXJ5IGFkZHJlc3NlcyBhcmUgdXNlZCBhbG9uZ3NpZGUgcHVibGljIG9uZXMs
IGFuZCB0aHVzIHRoYXQgYW1iaWd1aXR5IHNob3VsZCBiZSBjbGFyaWZpZWQuPC9mb250PjwvZGl2
PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj48YnIgY2xhc3M9
IiI+PC9mb250PjwvZGl2PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFz
cz0iIj5CdXQgYWdhaW4gSSBhZ3JlZSB3ZSBzaG91bGQgbWFrZSBpdCBjbGVhciB0aGF0IHRoYXQg
bmVlZCBub3QgYmUgdGhlIGNhc2UuPC9mb250PjwvZGl2PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFj
ZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+PC9mb250PjwvZGl2PjxkaXYgY2xh
c3M9IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj5UaW08L2ZvbnQ+PC9kaXY+PC9w
cmU+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0K
PC9ib2R5Pg0KPC9odG1sPg0K
--_000_19F2546A5EB045D9A827AC81A4C8BCD9jiscacuk_--


From nobody Thu May 19 03:46:55 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 627D712D8E4 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 03:46:53 -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 n64NKjyADS6o for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 03:46:51 -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 B4DE112D8C3 for <6man@ietf.org>; Thu, 19 May 2016 03:46:42 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lrp0019.outbound.protection.outlook.com [213.199.154.19]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-5-U6mc5BbRTvuR2grszfnesw-1; Thu, 19 May 2016 11:46:32 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc365.onmicrosoft.com; s=selector1-jisc-ac-uk; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=NDOQDGlMcLCCJntAjH50drn7LJsoItynwjFH6n2KDhg=; b=auPVXDaFCi6VOAFvn+O35CSTVDtTiIFj4sBq5HK/g8A1Cybwm/0PytTdC5S9s6HWEU+NRpl76A6XvqYmMg2iBx2Yk+2NfQ4ywcDBfW27qPMYFmwV/i3AvA2VIUP8tShq7KNoWT3BTXQExa7VQN6Cs9lDPMD4s4zgRXwN2tEAC2o=
Received: from AMSPR07MB455.eurprd07.prod.outlook.com (10.242.106.148) by AMSPR07MB453.eurprd07.prod.outlook.com (10.242.106.143) with Microsoft SMTP Server (TLS) id 15.1.497.12; Thu, 19 May 2016 10:46:31 +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.0501.007; Thu, 19 May 2016 10:46:31 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: default-iids and stable addresses
Thread-Topic: default-iids and stable addresses
Thread-Index: AQHRsJvx2z8IgTbOiU+7vY3x6SBpsJ++/8CAgACAYwCAAJMjgIAAAukA
Date: Thu, 19 May 2016 10:46:31 +0000
Message-ID: <71FF1D1B-647A-4E85-AF4C-B7283BE2A961@jisc.ac.uk>
References: <573B5FAC.7060300@gont.com.ar> <CAJE_bqdXt_jC2GCc-SRXAfRTybYd88ZdSMpnny2oJUMnscnyOQ@mail.gmail.com> <CAKD1Yr3U+UwopiXA9SgMGHm6BHGVmSMistyUhqqYpxYNZC4tUg@mail.gmail.com> <19F2546A-5EB0-45D9-A827-AC81A4C8BCD9@jisc.ac.uk>
In-Reply-To: <19F2546A-5EB0-45D9-A827-AC81A4C8BCD9@jisc.ac.uk>
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:a1f2:d0e0:e998:fd6b]
x-ms-office365-filtering-correlation-id: a8127d5d-af06-4885-7a23-08d37fd2d6ed
x-microsoft-exchange-diagnostics: 1; AMSPR07MB453; 5:fCWE9BuXZRW1XppLZ4f6hCM8W8x7vfq9I0xT0tUWSDlpENPRU4VEluUPBp8xJQqm5s0zfKaQKvsSpmh33ewPp/YZg3WGkbE42M+wvmWXwEj3wxp+npfRVkZIrtiiaArredixVQAKdGQv81ri3cv7Fg==; 24:kfJwBedlgtsJlR6ipEtOTDmBPbHxEnDad0qzl5ihC+1XYhyHfI4qG6WPBoNDXWfQM5qHP46k4INT+ihV8WxU4rzdeO2ydQXoXwzdHmZGcJI=; 7:d2KmNJGmJWXTnijMZVcynRbrp2Bdo9tGsQn/oEZX6DYMP7b6GdeWxUiodI51gziV2+xpcwPs+KAjS8hU8Cgu/bD8qVV29SaJnMBV76+e9WOt8LB5oPQ7B6AWNiabx+gEhxKPDEOZ5TPM9A7WYKlQMssj+YCdw02U0RbyBgRDn6tm8OWacqhQn1fxmdR7zWNZ; 20:L3+aZPyRDy4lNKcRWT0iotRjhAMLm6eL0FePUp9NN7WpNJX5YvljzkxobqoUf9XHluxlzcAemLDD7U422naVlniPlAscmBndXbqhAPRRjUTxogoWZWjS5l55l9NLYJeqAG8UclQeBoR99mE2lt9h3HELSAh4R6Xq185BJVBv1dM=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AMSPR07MB453;
x-microsoft-antispam-prvs: <AMSPR07MB45329302FD17EBDE891A7D5D64A0@AMSPR07MB453.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046); SRVR:AMSPR07MB453; BCL:0; PCL:0; RULEID:; SRVR:AMSPR07MB453; 
x-forefront-prvs: 094700CA91
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(377454003)(51694002)(24454002)(81166006)(19617315012)(92566002)(3480700004)(8676002)(8936002)(87936001)(106116001)(6116002)(5008740100001)(86362001)(83716003)(19580395003)(4326007)(10400500002)(102836003)(586003)(189998001)(82746002)(5002640100001)(110136002)(19580405001)(76176999)(50986999)(1220700001)(16236675004)(36756003)(93886004)(33656002)(5004730100002)(11100500001)(122556002)(2900100001)(3660700001)(3280700002)(2950100001)(74482002)(50226002)(57306001)(2906002)(15975445007)(77096005)(3826002)(104396002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB453; H:AMSPR07MB455.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 May 2016 10:46:31.4337 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AMSPR07MB453
X-MC-Unique: U6mc5BbRTvuR2grszfnesw-1
Content-Type: multipart/alternative; boundary="_000_71FF1D1B647A4E85AF4CB7283BE2A961jiscacuk_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_giIC-9ubURDj58XmdkzGqiCOiA>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Fernando Gont <fernando@gont.com.ar>
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, 19 May 2016 10:46:53 -0000

--_000_71FF1D1B647A4E85AF4CB7283BE2A961jiscacuk_
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

QXBvbG9naWVzLCB0aGlzIHdhcyBwYXN0ZWQgdG8gdGhlIHdyb25nIHRocmVhZCA6KQ0KDQpUaW0N
Cg0KT24gMTkgTWF5IDIwMTYsIGF0IDExOjM2LCBUaW0gQ2hvd24gPFRpbS5DaG93bkBqaXNjLmFj
LnVrPG1haWx0bzpUaW0uQ2hvd25AamlzYy5hYy51az4+IHdyb3RlOg0KDQpPbiAxOSBNYXkgMjAx
NiwgYXQgMDI6NDksIExvcmVuem8gQ29saXR0aSA8bG9yZW56b0Bnb29nbGUuY29tPG1haWx0bzps
b3JlbnpvQGdvb2dsZS5jb20+PiB3cm90ZToNCg0KT24gVGh1LCBNYXkgMTksIDIwMTYgYXQgMzow
OSBBTSwg56We5piO6YGU5ZOJIDxqaW5tZWlAd2lkZS5hZC5qcDxtYWlsdG86amlubWVpQHdpZGUu
YWQuanA+PiB3cm90ZToNCj4gQXMgYSBjby1hdXRob3Igb2YgZHJhZnQtaWV0Zi02bWFuLWRlZmF1
bHQtaWlkcywgSSBqdXN0IHdhbnRlZCB0byBjaGVjaw0KPiB0aGF0IHdlJ3JlIG9uIHRoZSBzYW1l
IHBhZ2UsIGJlY2F1c2UgSSBoYXZlIHRoZSBmZWVsaW5nIHRoYXQgdGhlIGFib3ZlDQo+IGtlZXBz
IGdldHRpbmcgbWlzaW50ZXJwcmV0ZWQuDQoNCk1pc2ludGVycHJldGF0aW9uIChJJ2QgY2FsbCBp
dCBjb25mdXNpb24gaW4gdGhpcyBjb250ZXh0LCB0aG91Z2gpIG9mIGENCmRvY3VtZW50IG9mdGVu
IGhhcHBlbnMgYmVjYXVzZSB0aGUgZG9jdW1lbnQgaXNuJ3QgY2xlYXIgZW5vdWdoDQoNCisxDQoN
CkkgYWdyZWUgdGhhdCBpdOKAmXMgYXQgYmVzdCBhbWJpZ3VvdXMuDQoNClNlY3Rpb24gMyBzYXlz
Og0KDQoiMS4gRG8gbm90IHJlc3VsdCBpbiBhbnkgY2hhbmdlcyB0byB0aGUgYmFzaWMgYmVoYXZp
b3Igb2YgYWRkcmVzc2VzDQoNCiAgICAgICBnZW5lcmF0ZWQgdmlhIHN0YXRlbGVzcyBhZGRyZXNz
IGF1dG9jb25maWd1cmF0aW9uIFtBRERSQ09ORjxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
cmZjNDk0MSNyZWYtQUREUkNPTkY+XS4NCg0KDQp3aGljaCBpbXBsaWVzIHRoYXQgU0xBQUMgc3Rp
bGwgcnVucyBhcyBub3JtYWwsIHNvIHlvdSBnZXQgYSBwdWJsaWMgYWRkcmVzcyBmcm9tIHRoYXQs
IGFuZA0KDQoNCjIuICBDcmVhdGUgYWRkaXRpb25hbCBhZGRyZXNzZXMgYmFzZWQgb24gYSByYW5k
b20gaW50ZXJmYWNlDQogICAgICAgaWRlbnRpZmllciBmb3IgdGhlIHB1cnBvc2Ugb2YgaW5pdGlh
dGluZyBvdXRnb2luZyBzZXNzaW9ucy4iDQoNCndoaWNoIGltcGxpZXMgdGhlIHRlbXBvcmFyeSBh
ZGRyZXNzIGlzICppbiBhZGRpdGlvbiogdG8gdGhlIFNMQUFDLWRlcml2ZWQgYWRkcmVzcywgdW5s
ZXNzIHlvdSBob2xkIHRoZSDigJxUYWtlIHNvbWUgbW9yZSB0ZWEgQWxpY2XigJ0gdmlldyBvZiBh
ZGRpdGlvbmFsLg0KDQpUaGVuIDMuMSBzYXlzOg0KDQoiW0FERFJfU0VMRUNUPGh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9yZmM0OTQxI3JlZi1BRERSX1NFTEVDVD5dIG1hbmRhdGVzIGltcGxl
bWVudGF0aW9ucyB0byBwcm92aWRlIGEgbWVjaGFuaXNtLCB3aGljaA0KDQogICBhbGxvd3MgYW4g
YXBwbGljYXRpb24gdG8gY29uZmlndXJlIGl0cyBwcmVmZXJlbmNlIGZvciB0ZW1wb3JhcnkNCiAg
IGFkZHJlc3NlcyBvdmVyIHB1YmxpYyBhZGRyZXNzZXMu4oCcDQoNCndoaWNoIGltcGxpZXMgYm90
aCBhcmUgY29uZmlndXJlZC4NCg0KQW5kIHRoZW4gc2VjdGlvbiAzLjMgc2F5cyB0aGUgbm9kZSBN
VVNUOg0KDQoiUHJvY2VzcyB0aGUgUHJlZml4IEluZm9ybWF0aW9uIE9wdGlvbiBhcyBkZWZpbmVk
IGluIFtBRERSQ09ORjxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDk0MSNyZWYtQURE
UkNPTkY+XQ0KZWl0aGVyIGNyZWF0aW5nIGEgbmV3IHB1YmxpYyBhZGRyZXNzIG9yIGFkanVzdGlu
ZyB0aGUgbGlmZXRpbWVzDQoNCiAgICAgICBvZiBleGlzdGluZyBhZGRyZXNzZXMsIGJvdGggcHVi
bGljIGFuZCB0ZW1wb3Jhcnku4oCcDQoNClNvIHRoZXJl4oCZcyBhIGxvdCBvZiB0ZXh0IGltcGx5
aW5nIHRlbXBvcmFyeSBhZGRyZXNzZXMgYXJlIHVzZWQgYWxvbmdzaWRlIHB1YmxpYyBvbmVzLCBh
bmQgdGh1cyB0aGF0IGFtYmlndWl0eSBzaG91bGQgYmUgY2xhcmlmaWVkLg0KDQpCdXQgYWdhaW4g
SSBhZ3JlZSB3ZSBzaG91bGQgbWFrZSBpdCBjbGVhciB0aGF0IHRoYXQgbmVlZCBub3QgYmUgdGhl
IGNhc2UuDQoNClRpbQ0KDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpJRVRGIElQdjYgd29ya2luZyBncm91cCBt
YWlsaW5nIGxpc3QNCmlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpBZG1pbmlz
dHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
cHY2DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KDQo=
--_000_71FF1D1B647A4E85AF4CB7283BE2A961jiscacuk_
Content-Type: text/html; charset=UTF-8
Content-ID: <0AE663BC11F830409CD7DFA07A597F94@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KQXBvbG9naWVzLCB0aGlzIHdhcyBw
YXN0ZWQgdG8gdGhlIHdyb25nIHRocmVhZCA6KQ0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGltPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
PGRpdj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5P
biAxOSBNYXkgMjAxNiwgYXQgMTE6MzYsIFRpbSBDaG93biAmbHQ7PGEgaHJlZj0ibWFpbHRvOlRp
bS5DaG93bkBqaXNjLmFjLnVrIiBjbGFzcz0iIj5UaW0uQ2hvd25AamlzYy5hYy51azwvYT4mZ3Q7
IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1pbnRlcmNoYW5nZS1uZXdsaW5lIj4NCjxk
aXYgY2xhc3M9IiI+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQt
bmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsi
IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNz
PSIiPg0KPGRpdiBjbGFzcz0iIj5PbiAxOSBNYXkgMjAxNiwgYXQgMDI6NDksIExvcmVuem8gQ29s
aXR0aSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmxvcmVuem9AZ29vZ2xlLmNvbSIgY2xhc3M9IiI+bG9y
ZW56b0Bnb29nbGUuY29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWlu
dGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgZGlyPSJsdHIiIGNsYXNz
PSIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUi
Pk9uIFRodSwgTWF5IDE5LCAyMDE2IGF0IDM6MDkgQU0sIOelnuaYjumBlOWTiSA8c3BhbiBkaXI9
Imx0ciIgY2xhc3M9IiI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOmppbm1laUB3aWRlLmFkLmpwIiB0
YXJnZXQ9Il9ibGFuayIgY2xhc3M9IiI+amlubWVpQHdpZGUuYWQuanA8L2E+Jmd0Ozwvc3Bhbj4g
d3JvdGU6PGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHls
ZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1s
ZWZ0OjFleCI+DQo8c3BhbiBjbGFzcz0iIj4mZ3Q7IEFzIGEgY28tYXV0aG9yIG9mIGRyYWZ0LWll
dGYtNm1hbi1kZWZhdWx0LWlpZHMsIEkganVzdCB3YW50ZWQgdG8gY2hlY2s8YnIgY2xhc3M9IiI+
DQomZ3Q7IHRoYXQgd2UncmUgb24gdGhlIHNhbWUgcGFnZSwgYmVjYXVzZSBJIGhhdmUgdGhlIGZl
ZWxpbmcgdGhhdCB0aGUgYWJvdmU8YnIgY2xhc3M9IiI+DQomZ3Q7IGtlZXBzIGdldHRpbmcgbWlz
aW50ZXJwcmV0ZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9zcGFuPk1pc2ludGVy
cHJldGF0aW9uIChJJ2QgY2FsbCBpdCBjb25mdXNpb24gaW4gdGhpcyBjb250ZXh0LCB0aG91Z2gp
IG9mIGE8YnIgY2xhc3M9IiI+DQpkb2N1bWVudCBvZnRlbiBoYXBwZW5zIGJlY2F1c2UgdGhlIGRv
Y3VtZW50IGlzbid0IGNsZWFyIGVub3VnaDwvYmxvY2txdW90ZT4NCjxkaXYgY2xhc3M9IiI+PGJy
IGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiYjNDM7MSZuYnNwOzwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+SSBhZ3JlZSB0aGF0IGl04oCZcyBhdCBiZXN0IGFtYmln
dW91cy48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPlNlY3Rpb24gMyBzYXlzOjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+JnF1b3Q7PHNwYW4gc3R5bGU9IndpZG93czogMTsiIGNs
YXNzPSIiPjEuIERvIG5vdCByZXN1bHQgaW4gYW55IGNoYW5nZXMgdG8gdGhlIGJhc2ljIGJlaGF2
aW9yIG9mIGFkZHJlc3Nlczwvc3Bhbj48L2Rpdj4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxl
PSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsgZm9udC12YXJpYW50LWxpZ2F0
dXJlczogbm9ybWFsOyBmb250LXZhcmlhbnQtcG9zaXRpb246IG5vcm1hbDsgZm9udC12YXJpYW50
LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWFsdGVybmF0ZXM6IG5vcm1hbDsgZm9udC12
YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgd2lkb3dzOiAx
OyI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj4gICAgICAgZ2VuZXJhdGVkIHZpYSBz
dGF0ZWxlc3MgYWRkcmVzcyBhdXRvY29uZmlndXJhdGlvbiBbPGEgaHJlZj0iaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL3JmYzQ5NDEjcmVmLUFERFJDT05GIiB0aXRsZT0iJnF1b3Q7SVB2NiBT
dGF0ZWxlc3MgQWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbiZxdW90OyIgY2xhc3M9IiI+QUREUkNP
TkY8L2E+XS48L2ZvbnQ+PC9wcmU+DQo8cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0ibWFyZ2lu
LXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5v
cm1hbDsgZm9udC12YXJpYW50LXBvc2l0aW9uOiBub3JtYWw7IGZvbnQtdmFyaWFudC1udW1lcmlj
OiBub3JtYWw7IGZvbnQtdmFyaWFudC1hbHRlcm5hdGVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1l
YXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IHdpZG93czogMTsiPjxmb250
IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPjwvZm9udD48L3ByZT4NCjxw
cmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206
IDBweDsgZm9udC12YXJpYW50LWxpZ2F0dXJlczogbm9ybWFsOyBmb250LXZhcmlhbnQtcG9zaXRp
b246IG5vcm1hbDsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWFs
dGVybmF0ZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1o
ZWlnaHQ6IG5vcm1hbDsgd2lkb3dzOiAxOyI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBIZWx2
ZXRpY2E7IiBjbGFzcz0iIj53aGljaCBpbXBsaWVzIHRoYXQgU0xBQUMgc3RpbGwgcnVucyBhcyBu
b3JtYWwsIHNvIHlvdSBnZXQgYSBwdWJsaWMgYWRkcmVzcyBmcm9tIHRoYXQsIGFuZDwvc3Bhbj48
L3ByZT4NCjxwcmUgY2xhc3M9Im5ld3BhZ2UiIHN0eWxlPSJtYXJnaW4tdG9wOiAwcHg7IG1hcmdp
bi1ib3R0b206IDBweDsgZm9udC12YXJpYW50LWxpZ2F0dXJlczogbm9ybWFsOyBmb250LXZhcmlh
bnQtcG9zaXRpb246IG5vcm1hbDsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12
YXJpYW50LWFsdGVybmF0ZXM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1h
bDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgd2lkb3dzOiAxOyI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiBIZWx2ZXRpY2E7IiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+PC9zcGFuPjwvcHJlPg0KPHBy
ZSBjbGFzcz0ibmV3cGFnZSIgc3R5bGU9Im1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTog
MHB4OyBmb250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1wb3NpdGlv
bjogbm9ybWFsOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtYWx0
ZXJuYXRlczogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFsOyBsaW5lLWhl
aWdodDogbm9ybWFsOyB3aWRvd3M6IDE7Ij48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0ibWFy
Z2luLXRvcDogMHB4OyBtYXJnaW4tYm90dG9tOiAwcHg7IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6
IG5vcm1hbDsgZm9udC12YXJpYW50LXBvc2l0aW9uOiBub3JtYWw7IGZvbnQtdmFyaWFudC1udW1l
cmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1hbHRlcm5hdGVzOiBub3JtYWw7IGZvbnQtdmFyaWFu
dC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij48Zm9udCBmYWNlPSJI
ZWx2ZXRpY2EiIGNsYXNzPSIiPjIuICBDcmVhdGUgYWRkaXRpb25hbCBhZGRyZXNzZXMgYmFzZWQg
b24gYSByYW5kb20gaW50ZXJmYWNlDQogICAgICAgaWRlbnRpZmllciBmb3IgdGhlIHB1cnBvc2Ug
b2YgaW5pdGlhdGluZyBvdXRnb2luZyBzZXNzaW9ucy4mcXVvdDs8L2ZvbnQ+PC9wcmU+PGRpdiBj
bGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2Zv
bnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGlj
YTsiIGNsYXNzPSIiPndoaWNoIGltcGxpZXMgdGhlIHRlbXBvcmFyeSBhZGRyZXNzIGlzICppbiBh
ZGRpdGlvbiogdG8gdGhlIFNMQUFDLWRlcml2ZWQgYWRkcmVzcywgdW5sZXNzIHlvdSBob2xkIHRo
ZSDigJxUYWtlIHNvbWUgbW9yZSB0ZWEgQWxpY2XigJ0gdmlldyBvZiBhZGRpdGlvbmFsLjwvc3Bh
bj48L2Rpdj48ZGl2IGNsYXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+PGJy
IGNsYXNzPSIiPjwvZm9udD48L2Rpdj48ZGl2IGNsYXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGlj
YSIgY2xhc3M9IiI+VGhlbiAzLjEgc2F5czo8L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9u
dCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48L2ZvbnQ+PC9kaXY+PGRp
diBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPiZxdW90O1s8YSBocmVm
PSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNDk0MSNyZWYtQUREUl9TRUxFQ1QiIHRp
dGxlPSImcXVvdDtEZWZhdWx0IEFkZHJlc3MgU2VsZWN0aW9uIGZvciBJbnRlcm5ldCBQcm90b2Nv
bCB2ZXJzaW9uIDYgKElQdjYpJnF1b3Q7IiBjbGFzcz0iIj5BRERSX1NFTEVDVDwvYT5dIG1hbmRh
dGVzIGltcGxlbWVudGF0aW9ucyB0byBwcm92aWRlIGEgbWVjaGFuaXNtLCB3aGljaDwvZm9udD48
L2Rpdj48cHJlIGNsYXNzPSJuZXdwYWdlIiBzdHlsZT0ibWFyZ2luLXRvcDogMHB4OyBtYXJnaW4t
Ym90dG9tOiAwcHg7IGZvbnQtdmFyaWFudC1saWdhdHVyZXM6IG5vcm1hbDsgZm9udC12YXJpYW50
LXBvc2l0aW9uOiBub3JtYWw7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFy
aWFudC1hbHRlcm5hdGVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7
IGxpbmUtaGVpZ2h0OiBub3JtYWw7Ij48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPiAg
IGFsbG93cyBhbiBhcHBsaWNhdGlvbiB0byBjb25maWd1cmUgaXRzIHByZWZlcmVuY2UgZm9yIHRl
bXBvcmFyeQ0KICAgYWRkcmVzc2VzIG92ZXIgcHVibGljIGFkZHJlc3Nlcy7igJw8L2ZvbnQ+PC9w
cmU+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFz
cz0iIj48L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNs
YXNzPSIiPndoaWNoIGltcGxpZXMgYm90aCBhcmUgY29uZmlndXJlZC48L2ZvbnQ+PC9kaXY+PGRp
diBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48
L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIi
PkFuZCB0aGVuIHNlY3Rpb24gMy4zIHNheXMgdGhlIG5vZGUgTVVTVDo8L2ZvbnQ+PC9kaXY+PGRp
diBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIiPjxiciBjbGFzcz0iIj48
L2ZvbnQ+PC9kaXY+PGRpdiBjbGFzcz0iIj48Zm9udCBmYWNlPSJIZWx2ZXRpY2EiIGNsYXNzPSIi
PiZxdW90O1Byb2Nlc3MgdGhlIFByZWZpeCBJbmZvcm1hdGlvbiBPcHRpb24gYXMgZGVmaW5lZCBp
biZuYnNwOzwvZm9udD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNz
PSIiPls8L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzQ5NDEj
cmVmLUFERFJDT05GIiB0aXRsZT0iJnF1b3Q7SVB2NiBTdGF0ZWxlc3MgQWRkcmVzcyBBdXRvY29u
ZmlndXJhdGlvbiZxdW90OyIgc3R5bGU9ImZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7IiBjbGFzcz0i
Ij5BRERSQ09ORjwvYT48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNz
PSIiPl08L3NwYW4+PC9kaXY+PGRpdiBjbGFzcz0iIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
IEhlbHZldGljYTsiIGNsYXNzPSIiPiAgICAgICBlaXRoZXIgY3JlYXRpbmcgYSBuZXcgcHVibGlj
IGFkZHJlc3Mgb3IgYWRqdXN0aW5nIHRoZSBsaWZldGltZXM8L3NwYW4+PC9kaXY+PHByZSBjbGFz
cz0ibmV3cGFnZSIgc3R5bGU9Im1hcmdpbi10b3A6IDBweDsgbWFyZ2luLWJvdHRvbTogMHB4OyBm
b250LXZhcmlhbnQtbGlnYXR1cmVzOiBub3JtYWw7IGZvbnQtdmFyaWFudC1wb3NpdGlvbjogbm9y
bWFsOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtYWx0ZXJuYXRl
czogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDog
bm9ybWFsOyI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj4gICAgICAgb2YgZXhpc3Rp
bmcgYWRkcmVzc2VzLCBib3RoIHB1YmxpYyBhbmQgdGVtcG9yYXJ5LjwvZm9udD48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsiIGNsYXNzPSIiPuKAnDwvc3Bhbj48L3ByZT48ZGl2
IGNsYXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPjwv
Zm9udD48L2Rpdj48ZGl2IGNsYXNzPSIiPjxmb250IGZhY2U9IkhlbHZldGljYSIgY2xhc3M9IiI+
U28gdGhlcmXigJlzIGEgbG90IG9mIHRleHQgaW1wbHlpbmcgdGVtcG9yYXJ5IGFkZHJlc3NlcyBh
cmUgdXNlZCBhbG9uZ3NpZGUgcHVibGljIG9uZXMsIGFuZCB0aHVzIHRoYXQgYW1iaWd1aXR5IHNo
b3VsZCBiZSBjbGFyaWZpZWQuPC9mb250PjwvZGl2PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFjZT0i
SGVsdmV0aWNhIiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+PC9mb250PjwvZGl2PjxkaXYgY2xhc3M9
IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj5CdXQgYWdhaW4gSSBhZ3JlZSB3ZSBz
aG91bGQgbWFrZSBpdCBjbGVhciB0aGF0IHRoYXQgbmVlZCBub3QgYmUgdGhlIGNhc2UuPC9mb250
PjwvZGl2PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNhIiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+PC9mb250PjwvZGl2PjxkaXYgY2xhc3M9IiI+PGZvbnQgZmFjZT0iSGVsdmV0aWNh
IiBjbGFzcz0iIj5UaW08L2ZvbnQ+PC9kaXY+PC9wcmU+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxiciBjbGFz
cz0iIj4NCklFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdDxiciBjbGFzcz0iIj4N
CjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIiBjbGFzcz0iIj5pcHY2QGlldGYub3JnPC9h
PjxiciBjbGFzcz0iIj4NCkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjY8YnIgY2xhc3M9IiI+DQotLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxiciBj
bGFzcz0iIj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==
--_000_71FF1D1B647A4E85AF4CB7283BE2A961jiscacuk_--


From nobody Thu May 19 08:27:18 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 6589912D1A2 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 08:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 vG9JfUNhz1tz for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 08:27:15 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::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 4767812D122 for <ipv6@ietf.org>; Thu, 19 May 2016 08:27:15 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id x194so81510220ywd.0 for <ipv6@ietf.org>; Thu, 19 May 2016 08:27:15 -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=fbhGrEiY2T9s5EY44g+PmtcD23e6KdbuB+bJ0udIcPo=; b=ibaWO1bfiXhlbJHYTAL6bDDnlksFoz9gaYJYxDFgJcYtVWSfZkGFG0JRQ5N9nLeBHd 62KFJRjdBJUoMfVN1ktpcVFfaBcsJaeDrqpe8zhQ9Ge+PVwwe0ZHGd4AKXAfqXrWyYrx Jet8jMN9VQUoHOroBnXFbvDOMa/43PsZP5Ux3lbYYjWkCAddvsZ/dct7ty+oXkHLEHQd 9RoMuLaKkr6AT4tQom7ENiV8CxXWpv5tB/Ynrh2SRnAMnnsc0NDu1/I2KG/m+7kGJw1/ LIqBzYj0XERwj1r2uEBMviI/f1JblKzy6QnlSw18iPq6fQEfmYxRepQ/8yhCA2Kzp78y G7eg==
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=fbhGrEiY2T9s5EY44g+PmtcD23e6KdbuB+bJ0udIcPo=; b=I6Goo0Vr9WEFdLDRFOKTzgdJFF+Agtm3VgMRorumtVQr+JA7KynYosIkFpvZ6RansL k0lsDcrqmcFaM0clpC/fXKoFfRA05HatcGdGG9GGe9ME0jfMmxFDQ0JbZAnnszTtIsNi LXaZclfeW7i+Gw4ippGhezd9rymBzc0U7tIrL2N+TY8bHHKKAxaZYx47SXQKC4uIE6bi +tVD/0+PorOgXAGSJXFtqdYhNh30zDdYnY2Aj5Tkhqi0gHNOCwDkO0fxQQM2PSVXlRUS Kau8H/vy20CVg8gbYPiorxeiJP3fdvNfHdKzWDndMFftCxtOaFFxLXxj70fQvqbNYM1R 6/jA==
X-Gm-Message-State: AOPr4FVijnufAZYhVBx4PcuSo9dz8dBb+ijDQ1AGoWPfNonCaHVlHveC3sApoHmTFHn3/Jqs77+lJ9leVbh0l0pq
X-Received: by 10.37.228.198 with SMTP id b189mr7486711ybh.25.1463671634338; Thu, 19 May 2016 08:27:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 19 May 2016 08:26:54 -0700 (PDT)
In-Reply-To: <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com> <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 20 May 2016 00:26:54 +0900
Message-ID: <CAKD1Yr3h48PU1n7KgeM=APgeWiJqv0XG77sB2_xP5zJ4eCc5LQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a114bc1c6d5dfdb0533339b53
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_GOOsZZzdmchbjWqtmrUSPMHIY8>
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: Thu, 19 May 2016 15:27:16 -0000

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

On Thu, May 19, 2016 at 6:10 PM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

> This is really not hard to test in any hardware qualification lab.
>> Really, it isn't.
>>
>
> On the contrary, I think it is very hard to test a number to see whether
> it's random - you need a very expensive lab and out-of-band info.
>

Sure, but the same can be said of any RFC 7217 implementation. Doing
blackbox testing of that sort of thing is hard.

On the other hand, it is very easy to test that when the device
disconnects/reconnects, the new connection has a different MAC address and
a different IPv6 address. That's the most important thing.

--001a114bc1c6d5dfdb0533339b53
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=
hu, May 19, 2016 at 6:10 PM, Alexandre Petrescu <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexandre.petr=
escu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><spa=
n><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">This is really not hard to test in any har=
dware qualification lab.<br>
Really, it isn&#39;t.<br>
</blockquote>
<br></span>
On the contrary, I think it is very hard to test a number to see whether<br=
>
it&#39;s random - you need a very expensive lab and out-of-band info.<br></=
blockquote><div><br></div><div>Sure, but the same can be said of any RFC 72=
17 implementation. Doing blackbox testing of that sort of thing is hard.</d=
iv><div><br></div><div>On the other hand, it is very easy to test that when=
 the device disconnects/reconnects, the new connection has a different MAC =
address and a different IPv6 address. That&#39;s the most important thing.<=
/div></div></div></div>

--001a114bc1c6d5dfdb0533339b53--


From nobody Thu May 19 08:34:15 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 F07A812D51B for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 08:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 iWmWbBhlHIi0 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 08:33:58 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001: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 5E34F12D505 for <ipv6@ietf.org>; Thu, 19 May 2016 08:33:58 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id 190so111761596iow.1 for <ipv6@ietf.org>; Thu, 19 May 2016 08:33: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:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=ulYJ9dHOLbRD5xxAuCZvPeLlu5h5/atvr3JiVgrLBUA=; b=GG+wTx57ZltrtEKeCfLTUagWaO5Xul9BIJyBnPo//8Yb2/jo8rtuMFxdbbgPZf9GPo O+VXrPrQ0Nv/2nbwbpBi620pXnNvYzIy4FkSQiV0kZhRdg0jZrCG0mKWGtO/8KVjSOSg eGG0p85joTGpt/a3hFvaU75l07D0jEKlSkzGUmI9XySCZ0HoUgHPlyG5BXPjgyOkE169 5n2o2vz0gT1gf5ZBZlfb4ZrACL13D2lG9saxUYxZo2g0udhn4x8HQ5G0U1La/+dZL8ZL +o9n9qY3dUqThiuHYPB9oXa0v9Zd7p3exzVl2VdWiOb1bdEUgHkQhcYmH47GBbR1fd22 d/TA==
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:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=ulYJ9dHOLbRD5xxAuCZvPeLlu5h5/atvr3JiVgrLBUA=; b=ZZ5BjcTd2Ttvfx3kjGuuR74/1cCmBWJ93kBTkwVbmg3yQuKwWEdJotwbJGHe+njxoH /WDfJmNLEo4F8XUOTfmeYnLVhWQW8CVodSjsC+sBolg21BLzOMugNBeVhPtigtMqJQMy i2ePp0lbj7hspzfrUCEt8v7NCkEJ1byFvnmj5uYlgfxTisIugCI/7i0h+r7ZxO6L1vVu 0ePaapDd6JtDEnJrsGlCruYBkWlHQf0KbU1UN1+F7/jCTw2FelIin2WQ+M/5UCpMvH2g XH24WDspk72sDXwx4kI0l2l8Bp4c1r2EErXnX6LJMw8xLCgOSgb3ZklHKQ4COozwYYK1 soyQ==
X-Gm-Message-State: AOPr4FUnJvHwN/M0squXWNHBa8dP9yHEUf91iFAgDrmavpYRfOgkDBnoZVcSXTUQPOE83YNxhlUkvhzxrwT/yw==
MIME-Version: 1.0
X-Received: by 10.107.35.66 with SMTP id j63mr11420019ioj.4.1463672037731; Thu, 19 May 2016 08:33:57 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Thu, 19 May 2016 08:33:57 -0700 (PDT)
In-Reply-To: <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in>
Date: Thu, 19 May 2016 08:33:57 -0700
X-Google-Sender-Auth: pUkyxHgRB_SREQHtVF7G4duZVtM
Message-ID: <CAJE_bqcpDoc3DVz3+Kfng=DOuQATRHkMFUBUR5P=KMToA4Udnw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SE2Tf0O-GKkBMUIw5GMvZqvXZLI>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 List <ipv6@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: Thu, 19 May 2016 15:34:15 -0000

At Wed, 18 May 2016 22:19:57 -0700,
Alissa Cooper <alissa@cooperw.in> wrote:

> >> Let's call a lemon a lemon: Asking to embed a layer-2 identifier/addre=
ss
> >> in a layer-3 address is extremely bad.
> >
> > I don't have a strong position on this matter itself, but my
> > understanding of the sense of the wg is that this is controversial,
> > and at least far from a clear consensus.  To repeat myself, *my*
> > concern on this last call is that it's not even clear, at least to me,
> > if this draft tries to say embedding a link-layer address is, whether
> > it's randomized or not, "extremely bad" (and must therefore be
> > prohibited).  If that's the intent, it should be clearly stated
>
> The draft makes just about a clear a statement in this vein as is possibl=
e:
>
> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
>    that embed the underlying link-layer address in the IID.=E2=80=9D
>
> Note that this statement does not prohibit anything, nor does it
> make a normative (in the moral sense) judgment. It just states the
> recommendation, which is the point of the document.

I've heard phrases like "it does not prohibit anything", and it always
confused me.  So let me ask essentially the same question again.
Assume there's an implementation that uses randomized link-layer
addresses and that implementation builds the IID for IPv6 address by
embedding that link-layer addresses by default.  Would that
implementation be considered to be non-compliant to the above SHOULD
NOT?  Without any qualifier to the link-layer address, I would
interpret it as such implementation is non-compliant.  But if so, that
contradicts statements like "it doesn't prohibit anything".  Hence my
confusion.  So, what's the author's intent?  Would such an
implementation be considered non-compliant to this SHOULD NOT?

> I appreciate that not everyone on the list agrees with this
> recommendation. But I find the claim that this recommendation is
> unclear to be difficult to understand. That is, I can=E2=80=99t think of =
a
> way to convey the same recommendation that would be clearer. If you
> can, please suggest text.

See above, it's not about agree or disagree with a recommendation.  I
didn't even know a particular type of implementation would be
considered non-compliant to a specific normative text of this draft.
Once I understand the intent, then I can agree or disagree with it,
or, if we agree with the intent but the text isn't clear enough I'm
willing to suggest alternative text.

--
JINMEI, Tatuya


From nobody Thu May 19 13:34:24 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 B91EB12D670 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 13:34: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 9jbWUr1G6HSD for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 13:34:21 -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 5B2A812D5CB for <ipv6@ietf.org>; Thu, 19 May 2016 13:34:21 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id bt5so32077546pac.3 for <ipv6@ietf.org>; Thu, 19 May 2016 13:34:21 -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=0CpAm+9YXo30pzRpXceuG1dCdRMltXDq2eD5KjqU9gs=; b=lIppjKjpHxu+pN3mnzxSxZI5uxAS8x8T2bSuYS5u+ZP297i9b9QCbA/BBpaDLkUHxT GujlZW7rGo4tBywX9XUfSVx6IZLxVah3qBEVXjgLY5adrEyJnoVuDrC3TeXWKmcI3+WR b+nz3Awu1EM7gfq2Te9tsrNMXT99FETZNeBYz5746N8w2bu9V1nLsxv0xY+iekj66GB3 HBi0Uvb+MKsKwecV8WIvE9bUEit+kf53w0M5N09I9+HjE7mclI5htRKerrC5qaEQUDal IVUQcTJ7t2fdAFzeIvMNYXVuP3sMxOvKsAfgJvM6MIlLj/yhjY7iUPiStH0zVHj2Vu+J CFsQ==
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=0CpAm+9YXo30pzRpXceuG1dCdRMltXDq2eD5KjqU9gs=; b=NlkhQm8xej7CrYzGOHC5GYFm6/CcKX7d+rujAlTI6wUz7NDT2kJKaZ8UEWFLAXeFv4 ns/6oe9TqSHgzhqBlbanLlcbY202BsjMV8RySIbJc7AQTzciQoEGPKp1Z6I8yKee2OW+ aUL552k1cW4L+WEtUFLMWqYcOqD7Jlhxt4UngXnDdX9waV225mZooUIsjLtjVBugKFNg wxy5nAIcyG20vpbwmlqqE6yhYBJ15xdAOHV6B+oOZgHS0TObwD+xfP7NxlN7a1U2lA2d v0YcXdfVqz2xSQtjmnBq1iUIwGXZoVM6jdYaOM+KcKmEMw6dbPiDPYBhYvDpvS3O8Dmz /pUQ==
X-Gm-Message-State: AOPr4FXt3EuRz0uEn6ABPTFQ1P9zNM7c4E8mRlS0Qfux3Q4od0FKBGucmVCXxNbnvYDmkA==
X-Received: by 10.66.191.100 with SMTP id gx4mr8478872pac.128.1463690060889; Thu, 19 May 2016 13:34:20 -0700 (PDT)
Received: from ?IPv6:2406:e007:48d6:1:a891:a15c:40a7:eb21? ([2406:e007:48d6:1:a891:a15c:40a7:eb21]) by smtp.gmail.com with ESMTPSA id c25sm21838989pfd.67.2016.05.19.13.34.18 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 May 2016 13:34:19 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: 6man <ipv6@ietf.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com> <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <44291aa1-a340-a119-8651-9b91b8b2a817@gmail.com>
Date: Fri, 20 May 2016 08:34:27 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/R2I2zwOXhykxNLL5T6R6kbeAtiM>
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, 19 May 2016 20:34:23 -0000

On 19/05/2016 21:10, Alexandre Petrescu wrote:
...
> So how to test whether it's random?

Answering your question in case anybody doesn't realise that it is rhetorical:

It is impossible (actually, meaningless) to test whether a single value is random.

1234 is a perfectly fine random decimal number. So 14159265358979323846.

0xE8039A3C677A is a perfectly fine random hexadecimal number. It might be
an Ethernet address. Or not.

   Brian


From nobody Thu May 19 13:43:17 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 0948812D67C for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 13:43:16 -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 LA_PpjLAJ6XO for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 13:43:14 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 79C2612D665 for <ipv6@ietf.org>; Thu, 19 May 2016 13:43:14 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id c189so34632155pfb.3 for <ipv6@ietf.org>; Thu, 19 May 2016 13:43:14 -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=9h1fJsSR8nf6e0IGi16Twk9txeTmsvMhWDE/XdxLtuU=; b=IejhwnhtfLe7/5RzF1oxGmw+6Q6emC1S9Tl4DQiyhVxg7Z+hbqJYrsVsalpAak/2RL OFLzULI97PI5tZHrFh2JvtylbeK49lHOnbCZPkKdXOKUrOo2Rmz5fzqAD5rn2oDWf/DY +WMZaR6h/PGcwgOjT2iKl0j6ticRikdZAYqOC/yirSeV2/Jb6cSR1hOWNpCdw6+kdqQK gxPzO5F0KaKJ+DHxCDZqOzh2ymWKfPFCksRiiETsp+stXi5Fp7hTxZ2o+QPpm1CAcxdb 1tGGMC+EG3FK4LiD+HcDSeFo04wV6vi/nFc4bQd3jGcVf8rDApYFULLQx2e4BSA8CmH7 UM5Q==
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=9h1fJsSR8nf6e0IGi16Twk9txeTmsvMhWDE/XdxLtuU=; b=QlE2WHjK+Wkgqz+E2tcnvN9WQF/ta5r8x4UIpfqxd3MjUk13ox/mqUQ2Fcy/SsGELF SRL9m7R5E/PK92TodRajBnJGG+SN9YyGNfMNqY7zQxEvVm9c7Mr5lg7g23wzL6HXS3ax I4sTK+rqAuAPs1RPVh7LdU8OP0YjPPZuBbJ/RXTOCKpbOfEbdsAVU3N94yPs2Jg7Vfo/ a4E8sXDAkv8FpjbzhP3lC2tBxEj7Hx1L/lgdoqL2i1omb+W+BHAN/qbRwYJVOfNm0jpu UqDs7IyAqL26k6CI2jCWdYxoRkOlQP2meERNYnVE2HGzNbQdDWytAGOIveZqJ+RlD9cN q6iw==
X-Gm-Message-State: AOPr4FV8mfNwXLxdp6NNd/XwWBBrGA6VhsHOFmiuc9WUn5OmVWFBuITK4Zz9oEmMd25qQA==
X-Received: by 10.98.30.132 with SMTP id e126mr23004667pfe.109.1463690594108;  Thu, 19 May 2016 13:43:14 -0700 (PDT)
Received: from ?IPv6:2406:e007:48d6:1:a891:a15c:40a7:eb21? ([2406:e007:48d6:1:a891:a15c:40a7:eb21]) by smtp.gmail.com with ESMTPSA id ba9sm21913423pab.24.2016.05.19.13.43.12 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 May 2016 13:43:13 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com>
Date: Fri, 20 May 2016 08:43:20 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/235oDtvY7mPDNgL-O16UIMnF4TE>
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, 19 May 2016 20:43:16 -0000

On 19/05/2016 18:10, Lorenzo Colitti wrote:
> On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper <alissa@cooperw.in> wrot=
e:
>=20
>> The draft makes just about a clear a statement in this vein as is poss=
ible:
>>
>> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
>>    that embed the underlying link-layer address in the IID.=E2=80=9D
>>
>> Note that this statement does not prohibit anything, nor does it make =
a
>> normative (in the moral sense) judgment. It just states the recommenda=
tion,
>> which is the point of the document.
>>
>> I appreciate that not everyone on the list agrees with this
>> recommendation. But I find the claim that this recommendation is uncle=
ar to
>> be difficult to understand. That is, I can=E2=80=99t think of a way to=
 convey the
>> same recommendation that would be clearer. If you can, please suggest =
text.
>>
>=20
> Alissa,
>=20
> I don't think anybody is claiming that the recommendation itself is
> difficult to understand. What is difficult to understand is how the
> document justifies that claim.
>=20
> It looks like the main argument used to justify this recommendation is
> major privacy risks. But embedding a link layer identifier into an IP
> address is not a major [1] privacy risk. It is only embedding a *STABLE=
*
> link-layer address that is a major privacy risk.
>=20
> Recommending that link-layer address be embedded only if they are ephem=
eral
> would address the privacy concerns just as well as (or maybe even bette=
r)
> than the approach proposed in this document.
>=20
> I think what people are do not understand is why this document recommen=
ds
> one but not the other. I certainly don't.
>=20
> Cheers,
> Lorenzo
>=20
> [1] I argue that cross-referencing IPX traffic to IP traffic is not a m=
ajor
> privacy risk because IPX is so uncommon.

I only chose that example because it's an obvious one. Do we know all the=
 contexts
in which a MAC address may appear in an off-link packet? I doubt it.

A privacy risk doesn't have to be "major" to be important. If we are conc=
erned
about massive-scale surveillance, where the opponent is using Hadoop and =
machine
learning technologies to glean information, minor risks become significan=
t. So
I support the draft as it stands: any case in which a layer 2 identifier =
is
embedded *in clear* in a higher layer identifier is a bad thing, even if =
it's
a temporary and pseudo-random bit string.

[I hadn't remembered that RFC1958 already said that ;-)]

I think this is completely orthogonal to whether stable IIDs should be us=
ed
by clients at all - that's an operational choice that we can only leave t=
o site
operators.

Regards
   Brian


From nobody Thu May 19 17:48:43 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 438EE12D545 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 17:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 7tEr5cjo-rla for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 17:48:39 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 B399312B04A for <ipv6@ietf.org>; Thu, 19 May 2016 17:48:39 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id x194so95341014ywd.0 for <ipv6@ietf.org>; Thu, 19 May 2016 17:48:39 -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=9FF/tgYlRAr3y2Xq75qNbjEmF4mUvU0LHtDwR3gnK3Y=; b=cgurN/9LWUDKfCEbskIisubnnsQkXqRlZWgBF8S3n/boQfhZuianxmo2l61ec7Qlwo eE7Z9VH7V3WJvA3mSWdM3LrpI8gSXq+eDWyqblSz6ddrJ3Q0cvWXFoAL7H7LGaMMTHuf sYpPY2F0mReMFF9VcyAJ0It0p+3enm76NTcFrle5XFAkOtOsXDOpcRw6VykQLLtf0FPs 9igzNRCy250XE5CkgZJbr6vWb6bpTyp7ZDRqAywqxIzYkruRppqLSzgUGA0o9ilutKFM /DstluwidnmEVfz8GAYdwfLautZuaovoRESUvbQcIgghWqgLorS2D4LQBEhq2kxrd8en EcCQ==
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=9FF/tgYlRAr3y2Xq75qNbjEmF4mUvU0LHtDwR3gnK3Y=; b=Ve7Dw49z/38xebkCgmXk2I8h77dshp/Z0mRgbvhDf+sni9KDJOVxlYsEsS20HNw2Lb 21j74R1dHfGnJEvBBNeXC1w/Qrhmgbduu4bCp9ht36NeLJjGzeorv3OBy07EaTn9dVQM VZgXgrD1ySHcdZnNIqNjzHSZG4BrrKMXi2gb5XTa8dCxWnAX3IwrrzoeMS600sF0cyJl BdXFloxgMoESEP+8YiVCkhUHrQ1Nx3j9QkA/yKnsMsRfx/gojjozbOMnQr0UIhkJxgoB 70+U7DSCk+SZ1AC8yUXfUqhieFqsK65haC/d4bbrqvo0+zQuVD2UXwqZvvSrQ9ubNiLa p+Gg==
X-Gm-Message-State: AOPr4FXkXM3beg/A8nCecTA5RiCiaWgxmJDWCQjneNXLiWdqC9VcX06eKxEa4ZuUfQg4U4sNharPpeJd/inSmMDX
X-Received: by 10.37.79.87 with SMTP id d84mr130821ybb.49.1463705318567; Thu, 19 May 2016 17:48:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 19 May 2016 17:48:18 -0700 (PDT)
In-Reply-To: <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 20 May 2016 09:48:18 +0900
Message-ID: <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113f5cd0925d2605333b7368
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nOrCdNARtaf5Y9yfXAUoipTmSLs>
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: Fri, 20 May 2016 00:48:42 -0000

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

Brian,

I will concede that there might be theoretical threats involving ephemeral
link layer addresses and non-IP protocols that we have not yet thought of.
However, the key thing to note is that even if these threats exist, their
impact is limited in time. By contrast, any threat involving a stable IP
address, in addition to being much easier to carry out because it's
available off-link, causes permanent impact because the stable address
never changes.

So if you think about it, your argument is actually in favour of link layer
address randomization, not against it. Assuming that the link layer address
will leak sometimes (here's a real-world example that's affects a lot more
people than IPX: captive portal redirect URLs that contain the MAC address
in the clear), it's much safer for that link address to be ephemeral than
to be permanent.

As to your statement that "whether people use stable IIDs is an operational
choice we can only leave to site operators" - this document is not leaving
it to site operators.

Let's all always keep in mind that the current text of the draft says that
on every network, hosts SHOULD configure an IPv6 address that never changes
until the end of time. I think that recommendation is irresponsible.

Cheers,
Lorenzo

On Fri, May 20, 2016 at 5:43 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 19/05/2016 18:10, Lorenzo Colitti wrote:
> > On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper <alissa@cooperw.in>
> wrote:
> >
> >> The draft makes just about a clear a statement in this vein as is
> possible:
> >>
> >> "By default, nodes SHOULD NOT employ IPv6 address generation schemes
> >>    that embed the underlying link-layer address in the IID.=E2=80=9D
> >>
> >> Note that this statement does not prohibit anything, nor does it make =
a
> >> normative (in the moral sense) judgment. It just states the
> recommendation,
> >> which is the point of the document.
> >>
> >> I appreciate that not everyone on the list agrees with this
> >> recommendation. But I find the claim that this recommendation is
> unclear to
> >> be difficult to understand. That is, I can=E2=80=99t think of a way to=
 convey
> the
> >> same recommendation that would be clearer. If you can, please suggest
> text.
> >>
> >
> > Alissa,
> >
> > I don't think anybody is claiming that the recommendation itself is
> > difficult to understand. What is difficult to understand is how the
> > document justifies that claim.
> >
> > It looks like the main argument used to justify this recommendation is
> > major privacy risks. But embedding a link layer identifier into an IP
> > address is not a major [1] privacy risk. It is only embedding a *STABLE=
*
> > link-layer address that is a major privacy risk.
> >
> > Recommending that link-layer address be embedded only if they are
> ephemeral
> > would address the privacy concerns just as well as (or maybe even bette=
r)
> > than the approach proposed in this document.
> >
> > I think what people are do not understand is why this document recommen=
ds
> > one but not the other. I certainly don't.
> >
> > Cheers,
> > Lorenzo
> >
> > [1] I argue that cross-referencing IPX traffic to IP traffic is not a
> major
> > privacy risk because IPX is so uncommon.
>
> I only chose that example because it's an obvious one. Do we know all the
> contexts
> in which a MAC address may appear in an off-link packet? I doubt it.
>
> A privacy risk doesn't have to be "major" to be important. If we are
> concerned
> about massive-scale surveillance, where the opponent is using Hadoop and
> machine
> learning technologies to glean information, minor risks become
> significant. So
> I support the draft as it stands: any case in which a layer 2 identifier =
is
> embedded *in clear* in a higher layer identifier is a bad thing, even if
> it's
> a temporary and pseudo-random bit string.
>
> [I hadn't remembered that RFC1958 already said that ;-)]
>
> I think this is completely orthogonal to whether stable IIDs should be us=
ed
> by clients at all - that's an operational choice that we can only leave t=
o
> site
> operators.
>
> Regards
>    Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<div dir=3D"ltr">Brian,<div><br></div><div>I will concede that there might =
be theoretical threats involving ephemeral link layer addresses and non-IP =
protocols that we have not yet thought of. However, the key thing to note i=
s that even if these threats exist, their impact is limited in time. By con=
trast, any threat involving a stable IP address, in addition to being much =
easier to carry out because it&#39;s available off-link, causes permanent i=
mpact because the stable address never changes.</div><div><br></div><div>So=
 if you think about it, your argument is actually in favour of link layer a=
ddress randomization, not against it. Assuming that the link layer address =
will leak sometimes (here&#39;s a real-world example that&#39;s affects a l=
ot more people than IPX: captive portal redirect URLs that contain the MAC =
address in the clear), it&#39;s much safer for that link address to be ephe=
meral than to be permanent.</div><div><br></div><div>As to your statement t=
hat &quot;whether people use stable IIDs is an operational choice we can on=
ly leave to site operators&quot; - this document is not leaving it to site =
operators.</div><div><br></div><div>Let&#39;s all always keep in mind that =
the current text of the draft says that on every network, hosts SHOULD conf=
igure an IPv6 address that never changes until the end of time. I think tha=
t recommendation is irresponsible.</div><div><br></div><div>Cheers,</div><d=
iv>Lorenzo</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Fri, May 20, 2016 at 5:43 AM, Brian E Carpenter <span dir=3D"ltr">&=
lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e=
.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div class=3D"HOEnZb"><div class=3D"h5">On 19/05/2016 18:10, Lorenzo Coli=
tti wrote:<br>
&gt; On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper &lt;<a href=3D"mailto:a=
lissa@cooperw.in">alissa@cooperw.in</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; The draft makes just about a clear a statement in this vein as is =
possible:<br>
&gt;&gt;<br>
&gt;&gt; &quot;By default, nodes SHOULD NOT employ IPv6 address generation =
schemes<br>
&gt;&gt;=C2=A0 =C2=A0 that embed the underlying link-layer address in the I=
ID.=E2=80=9D<br>
&gt;&gt;<br>
&gt;&gt; Note that this statement does not prohibit anything, nor does it m=
ake a<br>
&gt;&gt; normative (in the moral sense) judgment. It just states the recomm=
endation,<br>
&gt;&gt; which is the point of the document.<br>
&gt;&gt;<br>
&gt;&gt; I appreciate that not everyone on the list agrees with this<br>
&gt;&gt; recommendation. But I find the claim that this recommendation is u=
nclear to<br>
&gt;&gt; be difficult to understand. That is, I can=E2=80=99t think of a wa=
y to convey the<br>
&gt;&gt; same recommendation that would be clearer. If you can, please sugg=
est text.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Alissa,<br>
&gt;<br>
&gt; I don&#39;t think anybody is claiming that the recommendation itself i=
s<br>
&gt; difficult to understand. What is difficult to understand is how the<br=
>
&gt; document justifies that claim.<br>
&gt;<br>
&gt; It looks like the main argument used to justify this recommendation is=
<br>
&gt; major privacy risks. But embedding a link layer identifier into an IP<=
br>
&gt; address is not a major [1] privacy risk. It is only embedding a *STABL=
E*<br>
&gt; link-layer address that is a major privacy risk.<br>
&gt;<br>
&gt; Recommending that link-layer address be embedded only if they are ephe=
meral<br>
&gt; would address the privacy concerns just as well as (or maybe even bett=
er)<br>
&gt; than the approach proposed in this document.<br>
&gt;<br>
&gt; I think what people are do not understand is why this document recomme=
nds<br>
&gt; one but not the other. I certainly don&#39;t.<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Lorenzo<br>
&gt;<br>
&gt; [1] I argue that cross-referencing IPX traffic to IP traffic is not a =
major<br>
&gt; privacy risk because IPX is so uncommon.<br>
<br>
</div></div>I only chose that example because it&#39;s an obvious one. Do w=
e know all the contexts<br>
in which a MAC address may appear in an off-link packet? I doubt it.<br>
<br>
A privacy risk doesn&#39;t have to be &quot;major&quot; to be important. If=
 we are concerned<br>
about massive-scale surveillance, where the opponent is using Hadoop and ma=
chine<br>
learning technologies to glean information, minor risks become significant.=
 So<br>
I support the draft as it stands: any case in which a layer 2 identifier is=
<br>
embedded *in clear* in a higher layer identifier is a bad thing, even if it=
&#39;s<br>
a temporary and pseudo-random bit string.<br>
<br>
[I hadn&#39;t remembered that RFC1958 already said that ;-)]<br>
<br>
I think this is completely orthogonal to whether stable IIDs should be used=
<br>
by clients at all - that&#39;s an operational choice that we can only leave=
 to site<br>
operators.<br>
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">=C2=A0 =C2=A0Brian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
--------------------------------------------------------------------<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/list=
info/ipv6</a><br>
--------------------------------------------------------------------<br>
</div></div></blockquote></div><br></div>

--001a113f5cd0925d2605333b7368--


From nobody Thu May 19 18:17:14 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 040CA12B036 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 18:17:11 -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 fPr23ZxIyrm1 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 18:17:09 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 D337712B039 for <ipv6@ietf.org>; Thu, 19 May 2016 18:17:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4K1H9IN018628; Thu, 19 May 2016 18:17:09 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4K1H6L0018620 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 19 May 2016 18:17:06 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 19 May 2016 18:17:05 -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, 19 May 2016 18:17:05 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Index: AQHRsY4f419LL1+Mi06VUE+filz+t5/APIgAgADz3ACAAERxAP//kZeg
Date: Fri, 20 May 2016 01:17:05 +0000
Message-ID: <2c9d95e18e694eb48a90cd939a171bef@XCH15-06-11.nw.nos.boeing.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com>
In-Reply-To: <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@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
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: <http://mailarchive.ietf.org/arch/msg/ipv6/gKFNMS25Yh9rmKYx8LiMgfx3hKg>
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: Fri, 20 May 2016 01:17:11 -0000

SSdtIG5vdCBzdXJlIHdoeSB0aGlzIGlzIHN0aWxsIGJlaW5nIGRlYmF0ZWQuIExvcmVuem8ncyBz
dWdnZXN0aW9uLCBJIHRob3VnaHQsIHdhcyByZWFsbHkgY2xlYXIgYW5kIHRvIHRoZSBwb2ludC4g
VGhlIGlzc3VlIGhlcmUgaXMgbm90IHdoYXQgNjQtYml0IGdldHMgdXNlZCBpbiB0aGUgSUlELiBU
aGUgb25seSBxdWVzdGlvbiBpcyB3aGV0aGVyIGEgcGVybWFuZW50IDY0LWJpdCBJSUQgaXMgZGVz
aXJhYmxlIGZvciBzZWN1cml0eSBjb25jZXJucy4NCg0KV2h5IGlzIGl0IGRpZmZpY3VsdCB0byBv
bmx5IG1ha2UgdGhhdCBwb2ludD8NCg0KQmVydA0KDQo=


From nobody Thu May 19 19:18:12 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 528ED12D517 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 19:18:11 -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 vZzx60I-5YNn for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 19:18:10 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 053AA12D1D7 for <ipv6@ietf.org>; Thu, 19 May 2016 19:18:10 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id c189so37173550pfb.3 for <ipv6@ietf.org>; Thu, 19 May 2016 19:18:10 -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=sugVEOVSY/UPODY2jB0Fc5me0eoP9yYhqiGt09N3o2k=; b=JtkDQ9XUzlXiFaXe8n/56P0Dc8NbTiTshoEJ7jH31dy8yjsbfkh2DW+FxqYQ/OOJDB 8nEjmqRRqOgnMfip41EfUino+smht/3mUYkt9x6U6b1+j8s9fIIfj1u/Y1V4Ow0UNmYJ MZoL/HqXuENv1ZBoUh6UUgP0RmcO9SoiivMfl65qQhnJGKD6SreRFdEfYFPPcKWqx3N2 gQPu9yxWKPI6tglczrHGAFUc+e2tkQuYHfbD3E42RZe9vq3QJGd83DDFoQs+Fo1+TuYZ S6AAvNTxT2jwEoZnxsxJOUiJAVZu7X5eaAoadGRqZW+tsZLXAJZz3uJ81Je1ASGgxyPG tbfw==
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=sugVEOVSY/UPODY2jB0Fc5me0eoP9yYhqiGt09N3o2k=; b=VmI24H0zV66xt+DjKERfEknIdO1uNX4Q8Jn6b3h8I3UMf/pGTln96U7NPSguLpJDXP u77MaCbuJetPgzvtJoQMS8OhRycb4phDPlvPf7RyCLghRuaa3QuzlZoCpy3Re7a/yp1+ l18CVRglEE1Xb9Uld+K+sow7cjsOx/M/v7mmlpnKl2u1wW/YcmadGVbuTL9Ym5PjTzPA 1G72VUDHK0GUXarCkXxbYr+ed6pPsXLAMH1mXEmQIUhw/epnSdyFEO/BIajixOPZpU4v R/WuIGaGSzDH0Jcj1TD5jTiT75ZfnU5U/8D1tRK0zPpuB2O5yHWgpYEGu4zqb9vcrxOT rzJw==
X-Gm-Message-State: AOPr4FV/8xgPdwY0FD0M3JnjZ65CWbnNaz4MZ2G4zMQlNz+78ahy9ymlBYRUgTD85PMWnw==
X-Received: by 10.98.82.19 with SMTP id g19mr825259pfb.157.1463710689389; Thu, 19 May 2016 19:18:09 -0700 (PDT)
Received: from ?IPv6:2406:e007:48d6:1:51e8:ffb1:b414:c6c5? ([2406:e007:48d6:1:51e8:ffb1:b414:c6c5]) by smtp.gmail.com with ESMTPSA id p187sm22761541pfb.3.2016.05.19.19.18.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 May 2016 19:18:08 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a65c2157-044e-6207-314e-833313e5d458@gmail.com>
Date: Fri, 20 May 2016 14:18:15 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/r033ObCKNfn3LsdrDmTtAFqEzaU>
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: Fri, 20 May 2016 02:18:11 -0000

On 20/05/2016 12:48, Lorenzo Colitti wrote:
...
> Let's all always keep in mind that the current text of the draft says that
> on every network, hosts SHOULD configure an IPv6 address that never changes
> until the end of time. I think that recommendation is irresponsible.

Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
days to see whether it has any negative impact at all. So far, so good.

   Brian


From nobody Thu May 19 23:19:47 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 9FDA512B035 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 23:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 dxfIUSHb20n0 for <ipv6@ietfa.amsl.com>; Thu, 19 May 2016 23:19:45 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 3D8BE12B031 for <ipv6@ietf.org>; Thu, 19 May 2016 23:19:45 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id x189so100336519ywe.3 for <ipv6@ietf.org>; Thu, 19 May 2016 23:19:45 -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=zcIoQI+hgXKIcx4IAMM6qH39jo2VhDHkzYIKV0hpK/E=; b=JQnWz3HX4mVQvAUDgP1Bl0irZ9NdZqi4WmG7OPaluvozZ5D30CoX0wMts9FQhIJW6F Z6YBAzYBzbtglmxkdyxkSdIZ73bv9aQPBtdXgyosU4hN+/bqsSPWQJpD5FWUxpz1GsuT UCufXVpT8PDYyxIw1vgcWJFJX6EDl0Dk9eeifB/FJRL88Jn10gSpOt6NWx+f0NaZIHiu yL9U8T4O3kP+af1MgpeJGhM8mbZxj4wL2EXRv4k7uV3K5YVSShvoQOls8ky1uSEiBQpe kCH4EKHyM0Y8uti02cmYmP+QR1zphowpetzECVVHbgcaRiyiua7lNTKv9m8oGDcgqnux 0hkw==
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=zcIoQI+hgXKIcx4IAMM6qH39jo2VhDHkzYIKV0hpK/E=; b=V0E6RIEmnJ4SC+p9NyhDe36ZfwlUl+Fp0p7MvfMO1AqspQu9OgctrXYDeayNERggNt xbJL4qtfZCHaKEqV5WUiWqYOWcrEMwjpTzRrblElg2BMZCTmByiMpcmc/JpMmIH3nJCj VutCIv6wGmieF9FmU/EkyXTB7TKXqloiDdPnPzMYWvgXQX4iptWGf3yy6Dbr3aju1GeB QlqD/IMDIOfc0AspYZJdKK6KdsqjEV5XQDHiC7FXJ8/RgdjH+bB80lK2YIpiqYedPKP+ BmP36iuITLMggLwrGjJ/DXpUQyT5ntsrvWHIFB6ODeQ5OaxQHFMXwOwZ18wn60AGkRIZ wlww==
X-Gm-Message-State: AOPr4FXwdH0yPxww5aO996ulTmWxeS/nMBEMlTO45b9xgmgkJFaA7JCRcsJP/7+KstAQe+st/XiR1nKJCa9KhtRg
X-Received: by 10.129.80.11 with SMTP id e11mr795233ywb.197.1463725184192; Thu, 19 May 2016 23:19:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 19 May 2016 23:19:23 -0700 (PDT)
In-Reply-To: <a65c2157-044e-6207-314e-833313e5d458@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 20 May 2016 15:19:23 +0900
Message-ID: <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a1147d2b2a796f3053340134b
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7y-yT-1DPGLUcbDPJ8ZDr2PeD7o>
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: Fri, 20 May 2016 06:19:46 -0000

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

On Fri, May 20, 2016 at 11:18 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > Let's all always keep in mind that the current text of the draft says
> that
> > on every network, hosts SHOULD configure an IPv6 address that never
> changes
> > until the end of time. I think that recommendation is irresponsible.
>
> Thus, I'm continuing to run my laptop with only an RFC4941 address for a
> few
> days to see whether it has any negative impact at all. So far, so good.
>

Excellent! Now, if we can only make this draft stop saying that that you
SHOULD NOT do that...  :-)

--001a1147d2b2a796f3053340134b
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 F=
ri, May 20, 2016 at 11:18 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>=
&gt; Let&#39;s all always keep in mind that the current text of the draft s=
ays that<br>
&gt; on every network, hosts SHOULD configure an IPv6 address that never ch=
anges<br>
&gt; until the end of time. I think that recommendation is irresponsible.<b=
r>
<br>
</span>Thus, I&#39;m continuing to run my laptop with only an RFC4941 addre=
ss for a few<br>
days to see whether it has any negative impact at all. So far, so good.<br>=
</blockquote><div><br></div><div>Excellent! Now, if we can only make this d=
raft stop saying that that you SHOULD NOT do that... =C2=A0:-)</div></div><=
/div></div>

--001a1147d2b2a796f3053340134b--


From nobody Fri May 20 00:04:29 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 71EDB12B060 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 00:04:27 -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 JurQseFqNA5d for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 00:04:26 -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 EAB8012B03B for <ipv6@ietf.org>; Fri, 20 May 2016 00:04:25 -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; 20 May 2016 07:04:16 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id AE3669CC4E; Fri, 20 May 2016 00:04:15 -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=LKw4estoAkBOINbO7ZfMNI8O6ys=; b= NIC8Ut1slGkDp5JPip8S4znreiSVTLXO+uSqFhiurKvGtqrW5z1sF89H62mUeOVp EnrkwYjYwsfnUOs8VORX6m+yoTkO7LxF0u5jQlC25BBBpAeZeNqmzkf1aETZ89q1 dM5kODs41kPZ2WIYpbIVWHzYeeQOryKVWT3JMaD4cH8=
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=ljqm2KBfjKe+C6+g7M+JaBECH4 gHMURaxgTRKc+uGWwBV3D86ELVeA1X8Z1tavj3bcIInRL2dqjXK2UvIWNW73pIJ4 cP7M1K9RlPkz4Qj3oJxPKAJS62Up0sp0Ni+5EgVEBMN5Acyg4Ykj7uRAYWynmpfA HV7cMT73txLpa26ek=
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 6E5AE9CC7C; Fri, 20 May 2016 00:04:15 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C965816B6A00; Fri, 20 May 2016 09:04:12 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6EB2A0F8-41A0-4E1D-9135-0DE1880B2201"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com>
Date: Fri, 20 May 2016 09:04:09 +0200
Message-Id: <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Epy4ZfCxQvmvglZfb2ACBCbnIxU>
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: Fri, 20 May 2016 07:04:27 -0000

--Apple-Mail=_6EB2A0F8-41A0-4E1D-9135-0DE1880B2201
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> > Let's all always keep in mind that the current text of the draft =
says that
> > on every network, hosts SHOULD configure an IPv6 address that never =
changes
> > until the end of time. I think that recommendation is irresponsible.
>=20
> Thus, I'm continuing to run my laptop with only an RFC4941 address for =
a few
> days to see whether it has any negative impact at all. So far, so =
good.
>=20
> Excellent! Now, if we can only make this draft stop saying that that =
you SHOULD NOT do that...  :-)

Everything has to be read in context. My reading of this document is =
that it says what an implementation SHOULD do _iff_ a stable IID is to =
be generated. It says nothing about what to do if a stable IID is not =
required.

I find the current text quite clear on that, but clearly you don't.
Would it help with some sort of clearer applicability statement in this =
document? Can you propose text?

Cheers,
Ole

--Apple-Mail=_6EB2A0F8-41A0-4E1D-9135-0DE1880B2201
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

iQEcBAEBCgAGBQJXPrbsAAoJED4aXnjSQuKWiUIH/ibqKdFq58EV/j4Ibghfbydy
p1f56knnAliuSmZKsvPRZ0twrWX5JgSh2lIdU/mhXdWVR1rKPej4zbD5hkLEN9Zh
GEP1uzSwvVyoD7t88UMy9aGI13t4rt7G/mTEtGUSKbI3LyRWorlaIoaYnjY/qRev
UkAc0lN+Vebm1gYfMPynh7oYUcJvewo3Fj/Di9XrQEQEk2utYppUBQc7n0D1NYH+
XF49XsOZdyp+pMWk3atX3f8izaDNIxkS+1qJvFmF5kTstXXR/5cyF21c5zGJiCvB
xivJNXO9soWMEbuGadbh3MqNTXtLelQfuX/wfq1M0iEBxXMUwWcZPw5x79O32TA=
=MvBF
-----END PGP SIGNATURE-----

--Apple-Mail=_6EB2A0F8-41A0-4E1D-9135-0DE1880B2201--


From nobody Fri May 20 00:30:29 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 1E36212D6BD for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 00:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, SPF_PASS=-0.001] autolearn=unavailable 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 BeOwHScmZnSK for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 00:30:27 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 502E612B014 for <ipv6@ietf.org>; Fri, 20 May 2016 00:21:05 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id x189so101358892ywe.3 for <ipv6@ietf.org>; Fri, 20 May 2016 00:21:05 -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=/1DU0DyJm152ZfPrk4xmHrfOhzTvqDwGPhOCoF46Cfc=; b=KCP2Ux5Ic6e/SlBLF/86SYd74TPAHeI+2EQsyT33/Igwk2YtA4bHkBOoiD0Az8atmX AYprqgSftyOOMx/aAJbEQHgv/5EsENK81919hACC/dKoGDVkoOxzTU6GJprCNgalAQ/F NF30D076wcC8BRK35NtIscdYerczJ8XDHTotK6v0c89yJu5DcR2eFxhmFKopqJ5bAf4T Uqva+5CsIFxRW0ZvbqG5IiO9BhcaIrOBiB+aRFJrn+IIPdVyezkeehlKHlGwG4Ma7jp3 tvP/wg0G1b5QbU4XTr3AZOA6dYDSjok6U484wTsuwnsDjf8O6l53ldnt8h8n+spYW2lG GMUA==
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=/1DU0DyJm152ZfPrk4xmHrfOhzTvqDwGPhOCoF46Cfc=; b=Ew8IitH1F6Ps85ielDycMnQ0/m1iscssJIw9q9K6rqKqrrQWPel6bq26u2EFxir8BQ nCAVB7c0sKDL6+iySIThRCbtHcmXCzfEqxbviT11rNn5npZtdq74mMW2OJ+OI3rSDfo0 8sMI4/50Jp7oasWHeC4uHKpafMWBzBMeDAWvAO2w3KSq+4q62nO0E96mjxJz9HaeFr5V C7WZf9ejbSkdeAxDFCK0CMmZMQIqCdWwRQTToWCet6yFebzqCMpnK2QG1wBKhZ+wCqf4 LN7Yc4JG3pfPsQHvXuGPP6nVxNjx6SLLsui1qjwlQrYgcKqqDbt1iJphexwh8VPkq2Q8 q7JQ==
X-Gm-Message-State: AOPr4FVI4op9aCcOjD66qjlebECbo46ZVLHC9BDhLUQmXAd6Bqq9bwKd+LazMt8ikoShHvd2kxP8k39vV8f0tSKf
X-Received: by 10.129.27.9 with SMTP id b9mr863198ywb.173.1463728864301; Fri, 20 May 2016 00:21:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 20 May 2016 00:20:44 -0700 (PDT)
In-Reply-To: <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 20 May 2016 16:20:44 +0900
Message-ID: <CAKD1Yr3uz2ddGArKGh2GGf=pBadx-C-0RG2VhsStSsrPfeqdOQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a1142a41a01e0b1053340ef70
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Z2aPfIaPHz8EWospdrD5YoiFqK4>
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: Fri, 20 May 2016 07:30:28 -0000

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

On Fri, May 20, 2016 at 4:04 PM, <otroan@employees.org> wrote:

> > Excellent! Now, if we can only make this draft stop saying that that you
> SHOULD NOT do that...  :-)
>
> Everything has to be read in context. My reading of this document is that
> it says what an implementation SHOULD do _iff_ a stable IID is to be
> generated. It says nothing about what to do if a stable IID is not required.
>

On Ethernet, it is always required. The reason is this text:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.

Currently, implementations must configure a EUI-64 IID, per RFC 2464
section 4. Thus, by definition any currently-compliant implementation of
RFC 2464 "configures a stable IPv6 IID", all the time. If this document
becomes an RFC, a compliant implementation will thus have to follow the
recommendations of this document all the time.

If we want to clarify this, then I propose this text:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address. Configuring a stable IPv6 IID is
   OPTIONAL.

Cheers,
Lorenzo

--001a1142a41a01e0b1053340ef70
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 F=
ri, May 20, 2016 at 4:04 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otroa=
n@employees.org">otroan@employees.org</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex"><span class=3D"gmail-">&gt; Excellent! Now, if we can only make this d=
raft stop saying that that you SHOULD NOT do that...=C2=A0 :-)<br>
<br>
</span>Everything has to be read in context. My reading of this document is=
 that it says what an implementation SHOULD do _iff_ a stable IID is to be =
generated. It says nothing about what to do if a stable IID is not required=
.<br></blockquote><div><br></div><div>On Ethernet, it is always required. T=
he reason is this text:</div><div><br></div><div><div>=C2=A0 =C2=A0The reco=
mmendations in this document apply only in cases where</div><div>=C2=A0 =C2=
=A0implementations otherwise would have configured a stable IPv6 IID</div><=
div>=C2=A0 =C2=A0containing a link layer address.</div></div><div><br></div=
><div>Currently, implementations must configure a EUI-64 IID, per RFC 2464 =
section 4. Thus, by definition any currently-compliant implementation of RF=
C 2464 &quot;configures a stable IPv6 IID&quot;, all the time. If this docu=
ment becomes an RFC, a compliant implementation will thus have to follow th=
e recommendations of this document all the time.</div><div><br></div><div>I=
f we want to clarify this, then I propose this text:</div><div><br></div><d=
iv><div>=C2=A0 =C2=A0The recommendations in this document apply only in cas=
es where</div><div>=C2=A0 =C2=A0implementations otherwise would have config=
ured a stable IPv6 IID</div><div>=C2=A0 =C2=A0containing a link layer addre=
ss. Configuring a stable IPv6 IID is</div></div><div>=C2=A0 =C2=A0OPTIONAL.=
</div><div><br></div><div>Cheers,</div><div>Lorenzo</div></div></div></div>

--001a1142a41a01e0b1053340ef70--


From nobody Fri May 20 01:00:06 2016
Return-Path: <alexandre.petrescu@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 E216712D6D7 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 01:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 LM8MYlxsG1fg for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 01:00:03 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C76DB12D6DC for <ipv6@ietf.org>; Fri, 20 May 2016 01:00:02 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4K7xxcS032231; Fri, 20 May 2016 09:59:59 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6BA152028BF; Fri, 20 May 2016 10:00:03 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 5A84C20281D; Fri, 20 May 2016 10:00:03 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4K7xxpe011363; Fri, 20 May 2016 09:59:59 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com> <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com> <CAKD1Yr3h48PU1n7KgeM=APgeWiJqv0XG77sB2_xP5zJ4eCc5LQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <76684ac5-66e8-a046-ec1f-66186ba64364@gmail.com>
Date: Fri, 20 May 2016 09:59:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3h48PU1n7KgeM=APgeWiJqv0XG77sB2_xP5zJ4eCc5LQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CCnJcYee05fRimhuKd9nZeGQBqE>
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: Fri, 20 May 2016 08:00:05 -0000

Le 19/05/2016 Ã  17:26, Lorenzo Colitti a Ã©crit :
> On Thu, May 19, 2016 at 6:10 PM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>
>         This is really not hard to test in any hardware qualification lab.
>         Really, it isn't.
>
>
>     On the contrary, I think it is very hard to test a number to see whether
>     it's random - you need a very expensive lab and out-of-band info.
>
>
> Sure, but the same can be said of any RFC 7217 implementation. Doing
> blackbox testing of that sort of thing is hard.
>
> On the other hand, it is very easy to test that when the device
> disconnects/reconnects, the new connection has a different MAC address
> and a different IPv6 address. That's the most important thing.

I agree, it is easy to test the Interface ID changes or not upon 
reconnection (possibly delivered by ppp).

As an exception, this 'connection' tends to no longer be that simple 
yes/no state of earlier ppp.  These days an M2M module has multiple 
states of being connected.  Some-times it is connected yet it receives 
different prefixes in Router Advertisements.  In that case the privacy 
could be respected despite the IID being the same.

In these cases I noticed that the computer forms multiple different IIDs 
for each prefix in a received RA.  The computer ends with with about 10 
addresses in little time (depends on movement, and connectivity). 
That's not good either - too many addresses.

Alex


From nobody Fri May 20 01:06:26 2016
Return-Path: <alexandre.petrescu@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 BA92912D649 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 01:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 CoucTeAOo2fu for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 01:06:24 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3099412B047 for <ipv6@ietf.org>; Fri, 20 May 2016 01:06:24 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4K86MWL011004 for <ipv6@ietf.org>; Fri, 20 May 2016 10:06:22 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id DB298201D7C for <ipv6@ietf.org>; Fri, 20 May 2016 10:06:25 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id D1764201BCF for <ipv6@ietf.org>; Fri, 20 May 2016 10:06:25 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4K86LHW018454 for <ipv6@ietf.org>; Fri, 20 May 2016 10:06:22 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <CAO42Z2xNOyYfqjM9s6YgjWrCAscp6bH0cG-cyLraDJAof8GGMg@mail.gmail.com> <CAKD1Yr26N_YMhQQqnj=fqQZt5vY=E_6RnuwJtqTKUBgsvrFaBA@mail.gmail.com> <0e9f887a-a8b3-4ff5-fad3-0c3904830051@gmail.com> <44291aa1-a340-a119-8651-9b91b8b2a817@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <eaaecfb1-f0ef-2e63-05cf-bc0855ba6c4d@gmail.com>
Date: Fri, 20 May 2016 10:06:21 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <44291aa1-a340-a119-8651-9b91b8b2a817@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wuud-5VD3fosM43W8t0v08ofuJk>
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, 20 May 2016 08:06:25 -0000

Le 19/05/2016 à 22:34, Brian E Carpenter a écrit :
> On 19/05/2016 21:10, Alexandre Petrescu wrote: ...
>> So how to test whether it's random?
>
> Answering your question in case anybody doesn't realise that it is
> rhetorical:
>
> It is impossible (actually, meaningless) to test whether a single
> value is random.
>
> 1234 is a perfectly fine random decimal number. So
> 14159265358979323846.
>
> 0xE8039A3C677A is a perfectly fine random hexadecimal number. It
> might be an Ethernet address. Or not.

Yes, and the surveillant knows it: seeing a number does not mean it's a
MAC address.  Always seeing the same number does not mean it's the same
person (maybe it's someone pretending to be that poor person, in order
to fool the surveillant).

Alex

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


From nobody Fri May 20 09:06:02 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 4C80912B011 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 09:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 DK2EAczr_gpH for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 09:05:57 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::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 B3E4212D50F for <ipv6@ietf.org>; Fri, 20 May 2016 09:04:56 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id f8so18609641ioe.3 for <ipv6@ietf.org>; Fri, 20 May 2016 09:04:56 -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:date:message-id:subject :from:to:cc; bh=AyxW7z1ThFRD0WGuoo1lnnUjDgYdMWpljbnUKpBxwZw=; b=fx8Kq84U6ZEQxBYkOlWJJ5CJIrbE8CBUregZmHslhNIWhwdg+sO4aPdA3kEwrGN3sE KtUgVc6uLBCpjw3BYEaa4k16jy/nIy0d5T5LB2iRQHU4m4jSIgUOz0i+NxEawRL9G1D8 KAxtXuhDx3/ouU5NaDNrflmSfvfvcbeJUgzezDQUaVku5BMMrXxfqJQffPsdDy/GzheO VluLl3ytmdQHJlCZHXPHZhC/Wc3HdMZooE0K98uh9qYXgRkrnXtsdXsIO7GcipRdkksq uOkK+zxb8v4MwHPMI/kbTVFTWI2uulVvoO/GygrJNIarlKNoKTbpGoggismglHfb59Gl uBgA==
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:date :message-id:subject:from:to:cc; bh=AyxW7z1ThFRD0WGuoo1lnnUjDgYdMWpljbnUKpBxwZw=; b=LkjWub2z8SWsQuoeYDhicpz8w+zxEocoFlDv/BDXgNPH6ZWBBl+5URF9JC2Cbdk8Ve fmtVSmQ3/SY0nEv3rU59aqFVhBkACfkuzzj+KoZekZ4rG1MBC1bvcLW6lubK25+P/05K OP8tt/GiImiC6phizDZb6blXORzsCyqEZsyyf0Jrw+jQb8rBneV0tSKC44e21ve7YqIK T8YfG1eRitjKKeoa+w12VHE55VpOAMop/jUzOHnE5Wze1iOTQroj4EN/hlM2M5YmAFpB IkiJtB7/TUVAFzG8MjoXEHhfo6Bkeal4yFuutrH9uQLHb6ro7NXXj4hezbgG1nKB+dpa EWxw==
X-Gm-Message-State: AOPr4FV7uPqtz2a0ZBrV087ZjxV5/7DNxBM2qDInwej8rvzcGUqcSVM/jo3OVrh0QP9kcS5xVcrr7U6csqdxTg==
MIME-Version: 1.0
X-Received: by 10.107.58.213 with SMTP id h204mr3860734ioa.172.1463760295990;  Fri, 20 May 2016 09:04:55 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Fri, 20 May 2016 09:04:55 -0700 (PDT)
In-Reply-To: <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
Date: Fri, 20 May 2016 09:04:55 -0700
X-Google-Sender-Auth: SG78eBBh9yu-qaRxXzCPiOpyF4w
Message-ID: <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_dvd5B1uF7QRH0gskuK0KYIdFrE>
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: Fri, 20 May 2016 16:06:00 -0000

At Fri, 20 May 2016 09:04:09 +0200,
otroan@employees.org wrote:

> > > Let's all always keep in mind that the current text of the draft says that
> > > on every network, hosts SHOULD configure an IPv6 address that never changes
> > > until the end of time. I think that recommendation is irresponsible.
> >
> > Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
> > days to see whether it has any negative impact at all. So far, so good.
> >
> > Excellent! Now, if we can only make this draft stop saying that that you SHOULD NOT do that...  :-)
>
> Everything has to be read in context. My reading of this document is that it says what an implementation SHOULD do _iff_ a stable IID is to be generated. It says nothing about what to do if a stable IID is not required.
>
> I find the current text quite clear on that, but clearly you don't.

It's not clear to me either.  I commented on this exact point in my
first response to the last call.  Its followup discussion actually
confused me further:
http://www.ietf.org/mail-archive/web/ipv6/current/msg24391.html

In this discussion, I suggested "clarifying that this recommendation
is only for environments where address stability is needed".  The
response to that part of comment refers to a paragraph of the
introduction section:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  That is, this document does not
   change any existing recommendations concerning the use of temporary
   addresses as specified in [RFC4941], nor does it introduce any new
   requirements regarding when stable addresses are to be configured.
   Thus, the recommendations in this document simply improve the
   security and privacy properties of stable addresses.

At least to me, this is not the same as "this recommendation is only
for environments where address stability is needed".  So I tried to
understand the actual intent with followup questions, but the
subsequent discussions only introduced more confusion for me (because
of discussions on other points like whether using randomized
link-layer address is "extremely bad").

> Would it help with some sort of clearer applicability statement in
> this document? Can you propose text?

I've been unwilling to propose text as I didn't even understand the
authors' actual intent, but if it's actually that "it says what an
implementation SHOULD do _iff_ a stable IID is to be generated", I'd
suggest revising the above paragraph as follows:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  For example, this document does
   not change any existing recommendations concerning the use of
   temporary addresses as specified in [RFC4941], nor do the
   recommendations apply to cases where the link layer address is not
   stable (e.g., it is periodically randomized) in the first place,
   nor does it introduce any new requirements regarding when stable
   addresses are to be configured.  Thus, the recommendations in this
   document simply improve the security and privacy properties of
   stable addresses.

If the intent of this document is really just that it applies iff a
stable IID is to be generated and does not make any judgment on, e.g.,
use of randomized link-layer addresses, this proposed text shouldn't
be a problem for anyone. (for some, it may seem to say the obvious and
therefore redundant, but given that whether randomized LL address is
good or bad was so controversial here, I think it's helpful to
explicitly clarify that).  But I was not sure if it's really
acceptable, especially for the authors, by seeing opinions like
the "extremely bad" comment.

To be clear, I'm not particularly an advocator of the use of
randomized link-layer addresses.  But I've seen this as one central
point concerning how to move forward for this document, so I believe
we should be at least clear on this in the document text.

--
JINMEI, Tatuya


From nobody Fri May 20 14:06:13 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 9249012D62C for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 14:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, 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=HTDpSFl+; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=rCW+Ol84
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 CMlGFQqzZp4g for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 14:06:11 -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 DFAD312D13B for <ipv6@ietf.org>; Fri, 20 May 2016 14:06:10 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id CD71D20D7C for <ipv6@ietf.org>; Fri, 20 May 2016 17:06:07 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 20 May 2016 17:06:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= 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=X1trs3YWtMngWN0ouAQfGRimYrg=; b=HTDpSF l+aLcIDeZljhJQf3cpLilLtyywNEVwsHNteHGxwAYwbt8Rkz2Fp4/7E0ltAGciyb wNnpQSj+SxaPT+U6TcnWqV5LlxTNysvDaNYw2ZtnyWuO5BulX9WdwE6mHz4K8sDo WPWhHV02KgawTjanMUQj/ekvbrg04Wurqrx0c=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=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=X1trs3YWtMngWN0 ouAQfGRimYrg=; b=rCW+Ol84XqJv/hEBe/a1D3ahBByJ8/aZ9vEyTsg7RaC+ZK9 4sqRG9DrUNKxRz8I2rVbBVr5AW8+YW0/Ke55qBlK5Y5dRk/kiLV37tZkmZf6Vb5i KEKUDuRBROLKkNWuz8MP0re+k0+JIb/lK4PJGjXDu7/lJc5sLtguNoP6wZKY=
X-Sasl-enc: W3+HGtyR1i7PppbIUmMIIqQ3VxJx4onpmZ9UPv9QyLzv 1463778367
Received: from [10.24.28.47] (unknown [128.107.241.180]) by mail.messagingengine.com (Postfix) with ESMTPA id 02AFBF29E5 for <ipv6@ietf.org>; Fri, 20 May 2016 17:06:06 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: default-iids: dropping requirement 1 in Section 3
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in>
Date: Fri, 20 May 2016 23:06:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in>
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6Y8hDVKO4MIi4m6LW53Uz0I1QHI>
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, 20 May 2016 21:06:12 -0000

> On May 18, 2016, at 1:26 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> What if we dropped requirement #1 in Section 3, but left the rest the =
same? This would open the door such that people who wanted to comply =
with the SHOULD-level recommendation in this spec in the presence of =
randomized MAC addresses still could (e.g., by implementing 7217 and =
using the randomized MAC as the Net_Iface parameter), but directly =
embedding a MAC address in the IID would still go against the SHOULD NOT =
recommendation here.

I don=E2=80=99t think I saw anyone respond to this suggestion, so I=E2=80=99=
d like to ask again for people=E2=80=99s opinions about this.

To my eye this is a nice compromise.

Alissa=


From nobody Fri May 20 15:42:14 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 D4FC012D633 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 15:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 VFcWQlx-54gg for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 15:42:10 -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 21F9012D140 for <6man@ietf.org>; Fri, 20 May 2016 15:42:10 -0700 (PDT)
Received: from [100.92.233.6] (unknown [152.206.74.203]) (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 8312E8011B; Sat, 21 May 2016 00:41:45 +0200 (CEST)
To: "6man@ietf.org" <6man@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?= <jinmei@isc.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: default-iids: Clarifying the use of stable addresses
X-Enigmail-Draft-Status: N1110
Message-ID: <573F3F49.9090107@si6networks.com>
Date: Fri, 20 May 2016 12:46:01 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cBeTctG_CHt6G1NhjdhMgoW6M-A>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Fri, 20 May 2016 22:42:12 -0000

Folks,

In the hopes of making this document more clear regarding whether this
document is requiring the use of stable addresses, how about adding the
following text:

"SLAAC has traditionally resulted in stable addresses, since the IID
 has been generated by embedding a stable layer-2 numeric identifier
 (e.g., a MAC address). [RFC4941] implies, throughout the
 specification, that temporary addresses are generated and employed
 along with temporary addresses.

 We note that depending on the specific device type and/or operating
 environment, a host may or may not want to configure and/or use a
 stable address, but may e.g., exclusively use temporary addresses.

 This document does not require that stable addresses be actively
 employed or even generated, but simply provides a recommendation
 regarding how stable addresses should be generated when a node decides
 to do so.

 Similarly, this document is orthogonal to other privacy improvements
 such as MAC address randomization. This document aims to mitigate known
 security and privacy implications of stable IPv6 addresses in a
 hardware/protocol-independent manner, without any assumptions on the
 security/privacy properties of the underlying layers.
"

If you have suggestions for improvement, please do let me know, and send
proposed tweaks.

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 May 20 15:43:09 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 9F7EC12D65F for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 15:43:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 E5Bu1Lbw_kJJ for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 15:43:04 -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 4275412D140 for <ipv6@ietf.org>; Fri, 20 May 2016 15:43:04 -0700 (PDT)
Received: from [100.92.233.6] (unknown [152.206.74.203]) (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 66D748011B; Sat, 21 May 2016 00:42:44 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAKD1Yr3heGg1GjhU1VghMHfg08q6RuK6Ls4M==ppgg6Eg1G_Wg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573F419F.8080602@si6networks.com>
Date: Fri, 20 May 2016 12:55:59 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3heGg1GjhU1VghMHfg08q6RuK6Ls4M==ppgg6Eg1G_Wg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pDNHY9zaUdmRx7igf1FLLDHcQ3Q>
Cc: IPv6 List <ipv6@ietf.org>, "privsec-program@iab.org" <privsec-program@iab.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, 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, 20 May 2016 22:43:05 -0000

On 05/18/2016 09:00 PM, Lorenzo Colitti wrote:
> On Wed, May 18, 2016 at 11:13 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     No. My take is that the concern is flawed. Please read
>     draft-gont-predictable-protocol-ids, and even RFC4941, which talks at
>     length about security and privacy issues regarding reusing identifiers
>     in different context, for different scopes, etc.
> 
> 
> Fernando, please stop arguing that a random MAC address is a
> "predictable ID". That statement is false and continuing to argue for it
> is not helping this document advance.

I simply referenced a draft. When I referred to embedding MAC addresses
in IPv6 IIDs, I said "improper" IDs, rather than "predictable".

Reusing IDs in different layers for different scopes, etc., is a bad
thing. It just takes some else making the same bad decision, an now an
attacker can correlate traffic because you and other guy thought that
embedding an identifier from a lower layer in your own protocol, in a
different context, with a different scope, for a different purpose.

Brian noted, just as an example, the ability to correlate IPv6 and IPX
traffic. But this is obviously just an example that shows why something
that might seem benign in some environment may show up as being a real
bad idea.

The fact that you'd be wasting 18 bits of entropy in your IIDs (if you
generate them by embedding a MAC address -- even if randomized) is yet
another datapoint that you're doing the wrong thing: an indication that
you're trying to combat the symptom, rather than the disease.

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 May 20 16:10:23 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 407D512D674 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 16:10:22 -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 bXkYbTuGf8BJ for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 16:10:20 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 C38DA12D672 for <6man@ietf.org>; Fri, 20 May 2016 16:10:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4KNAKGI009995; Fri, 20 May 2016 16:10:20 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4KNAGTE009985 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 20 May 2016 16:10:16 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 20 May 2016 16:10:15 -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; Fri, 20 May 2016 16:10:16 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
Subject: RE: default-iids: Clarifying the use of stable addresses
Thread-Topic: default-iids: Clarifying the use of stable addresses
Thread-Index: AQHRsujkuYlKZjWWvUaG4reiTet4Wp/CcCZQ
Date: Fri, 20 May 2016 23:10:15 +0000
Message-ID: <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com>
In-Reply-To: <573F3F49.9090107@si6networks.com>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KFByWxMjJIceF4TEhBgPqztzx_4>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Fri, 20 May 2016 23:10:22 -0000

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Fernando Gont
=20
> "SLAAC has traditionally resulted in stable addresses, since the IID
>  has been generated by embedding a stable layer-2 numeric identifier
>  (e.g., a MAC address). [RFC4941] implies, throughout the
>  specification, that temporary addresses are generated and employed
>  along with temporary addresses.
>=20
>  We note that depending on the specific device type and/or operating
>  environment, a host may or may not want to configure and/or use a
>  stable address, but may e.g., exclusively use temporary addresses.
>=20
>  This document does not require that stable addresses be actively
>  employed or even generated, but simply provides a recommendation
>  regarding how stable addresses should be generated when a node decides
>  to do so.
>=20
>  Similarly, this document is orthogonal to other privacy improvements
>  such as MAC address randomization. This document aims to mitigate known
>  security and privacy implications of stable IPv6 addresses in a
>  hardware/protocol-independent manner, without any assumptions on the
>  security/privacy properties of the underlying layers.

Fernando, it seems to me that the I-D as written, on this particular subjec=
t, is already abundantly clear. And it seems to me that your additional tex=
t would sound more like a lobbying effort to keep people from using stable =
addresses. Why the extra pitch? The whole point of this document is to prov=
ide guidance when people do want to use stable addresses. Presumably, they =
already know whatever security implications, and have other security implic=
ations that outweigh those of the more general public Internet client-serve=
r model.

The messages in this I-D are already clear. Normally, security in client-se=
rver interactions is improved when the clients have unpredictable and unsta=
ble addresses. However this I-D explains that when stable addresses are req=
uired, it's a bad idea to embed MAC addresses or any other stable address t=
hat belongs to a different layer, in the IPv6 address. Furthermore, when st=
able addresses are used, multiple stable addresses are used by an individua=
l host, different IIDs should be used with each prefix.

Bert



From nobody Fri May 20 16:23:33 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 2E61812D523 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 16:23:32 -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 M6HmcvfNBcod for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 16:23:30 -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 8E33D12D1C0 for <ipv6@ietf.org>; Fri, 20 May 2016 16:23:30 -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 u4KNNU9j009010; Fri, 20 May 2016 16:23:30 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4KNNNVr008997 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 20 May 2016 16:23:23 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 20 May 2016 16:23:22 -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; Fri, 20 May 2016 16:23:22 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Alissa Cooper <alissa@cooperw.in>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: RE: default-iids: dropping requirement 1 in Section 3
Thread-Topic: default-iids: dropping requirement 1 in Section 3
Thread-Index: AQHRstt62ttfBf6fakWjjlA/rFwH2Z/Cdjqw
Date: Fri, 20 May 2016 23:23:22 +0000
Message-ID: <28b406bf74574094b78212efe90c63f3@XCH15-06-11.nw.nos.boeing.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
In-Reply-To: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
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: <http://mailarchive.ietf.org/arch/msg/ipv6/QWv-EaHybp11tf3IQCo4gqZoB7U>
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, 20 May 2016 23:23:32 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWxpc3NhIENvb3Blcg0KDQo+ID4gV2hhdCBp
ZiB3ZSBkcm9wcGVkIHJlcXVpcmVtZW50ICMxIGluIFNlY3Rpb24gMywgYnV0IGxlZnQgdGhlIHJl
c3QgdGhlIHNhbWU/DQo+IFRoaXMgd291bGQgb3BlbiB0aGUgZG9vciBzdWNoIHRoYXQgcGVvcGxl
IHdobyB3YW50ZWQgdG8gY29tcGx5IHdpdGggdGhlDQo+IFNIT1VMRC1sZXZlbCByZWNvbW1lbmRh
dGlvbiBpbiB0aGlzIHNwZWMgaW4gdGhlIHByZXNlbmNlIG9mIHJhbmRvbWl6ZWQgTUFDDQo+IGFk
ZHJlc3NlcyBzdGlsbCBjb3VsZCAoZS5nLiwgYnkgaW1wbGVtZW50aW5nIDcyMTcgYW5kIHVzaW5n
IHRoZSByYW5kb21pemVkDQo+IE1BQyBhcyB0aGUgTmV0X0lmYWNlIHBhcmFtZXRlciksIGJ1dCBk
aXJlY3RseSBlbWJlZGRpbmcgYSBNQUMgYWRkcmVzcyBpbiB0aGUNCj4gSUlEIHdvdWxkIHN0aWxs
IGdvIGFnYWluc3QgdGhlIFNIT1VMRCBOT1QgcmVjb21tZW5kYXRpb24gaGVyZS4NCj4gDQo+IEkg
ZG9u4oCZdCB0aGluayBJIHNhdyBhbnlvbmUgcmVzcG9uZCB0byB0aGlzIHN1Z2dlc3Rpb24sIHNv
IEnigJlkIGxpa2UgdG8gYXNrDQo+IGFnYWluIGZvciBwZW9wbGXigJlzIG9waW5pb25zIGFib3V0
IHRoaXMuDQo+IA0KPiBUbyBteSBleWUgdGhpcyBpcyBhIG5pY2UgY29tcHJvbWlzZS4NCg0KQWxp
c3NhLCBJJ20gc3RhcnRpbmcgdG8gdGhpbmsgdGhhdCBTTEFBQyBpcyBhbmFsb2dvdXMgdG8gZGll
c2VsIGVuZ2luZXMuIEV2ZXJ5b25lIHRob3VnaHQgaXQgd2FzIGEgZ3JlYXQgaWRlYSBmb3IgdGhl
IGxvbmdlc3QgdGltZSwgYW5kIG5vdyBpdCdzIGdldHRpbmcgYSBiYWQgcmFwLg0KDQpUaGUgcmVx
dWlyZW1lbnQgaW4gU2VjdGlvbiAzICMxIHN0aWxsIGhhcyB0byBob2xkLCBmb3IgYW55IGZvcm0g
b2Ygc3RhYmxlIGFkZHJlc3MgZGV2ZWxvcGVkIHdpdGggU0xBQUMsIEkgd291bGQgdGhpbmsuIElm
IG9uZSByZWJvb3RzIHRoZSBob3N0LCB0aGUgYWRkcmVzcyBvbiB0aGF0IHN1Ym5ldCBoYXMgdG8g
cmVhcHBlYXIgYXMgaXQgd2FzIGJlZm9yZS4gSWYgeW91IGRyb3AgdGhlIHJlcXVpcmVtZW50LCBw
ZW9wbGUgd2lsbCBqdXN0IGFzc3VtZSB0aGF0IGl0J3Mgb2J2aW91cyBhbnl3YXksIEkgd291bGQg
dGhpbmsuDQoNCkJlcnQNCg0K


From nobody Fri May 20 18:40:39 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 BECEB12B04A for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 18:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 K9jhQOKFf88S for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 18:40:36 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 2175212B005 for <ipv6@ietf.org>; Fri, 20 May 2016 18:40:36 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id o16so7644798ywd.2 for <ipv6@ietf.org>; Fri, 20 May 2016 18:40:36 -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=/m1oRK/lPG090SwOyxWE6YaUNBFjkYjNImrR88KWHPM=; b=SF4P4l4EJYxk97l7mKox97qETbhBWNpfRNSQbUKGADPcN0l95dNy9fAuuQuec8veNR dnNLFny+VgXzzuRm+xGeCCek36XzauO8jHFxNja3IqZRBNqiXJTUaK346qK+rdlZfC30 SxJM5Rha2TAfF4+0tj2xMZC/jPSRuSJhABNz18O/ot8lUaWYNhD8r5ZbqmIoIcoDBBN0 k+um4YDa314OX0v6rs0aswg7nNukray1IEbi7XC/r83OD7ZzX4Cw/Gf0fCOVP2W3MB1R Caq1zpPOHm/9r25iGOr98LEtSxKnoTjCCVEhdT2AEJpU6ISJfC+xvDp+jmNY0i9wd3Hp 4Htg==
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=/m1oRK/lPG090SwOyxWE6YaUNBFjkYjNImrR88KWHPM=; b=ZM2oF7ZVjIEIlinSD4SXgU0klVxbeTP6FHNLWS9wWeWvJ0FCWFlLipkqqtMIgZjP5C m7XtdX1znqjcl4DuKvUrIkVcVeSnMOkaCRsPzBiXWYwrme9Xji2D42DZtZs1I0grJ0iG kQw2VEhvTAipluatJ1GkZE/zVLlXIbPxEBjsUJMYtor9NoxVW69s0B4LcGCx0vGmPsHh dej6LOd76VH+hOAAqD+oDViKhYDFw5voW/2F/cikS0DuKNXqJ+28/h8iUDqPXN/JVWWB arw24bC3Q+UZeq7QL1cmeMdQzfanruZp5zvhyPOKcNg4PGS1NX9jg1lOn7hZMnvtHO2m Cwbg==
X-Gm-Message-State: AOPr4FXOgSzByKrw+YXqH9CdYF/9EVjiEyYC5rPQyLSqUqFNcgwK/uxc+AHR4wZxX0RMMQt3iWo1C7V+jvH8J7Vr
X-Received: by 10.129.108.208 with SMTP id h199mr3931043ywc.229.1463794835045;  Fri, 20 May 2016 18:40:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 20 May 2016 18:40:15 -0700 (PDT)
In-Reply-To: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 21 May 2016 10:40:15 +0900
Message-ID: <CAKD1Yr1B75Y9owqyB=krMS_GfiyqowgaRD2TBetP96N5ANoYtA@mail.gmail.com>
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary=001a114db9042b2f2d0533504bf8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KvbpFdh7xvjj4mzOo6hdOckPT4Y>
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: Sat, 21 May 2016 01:40:38 -0000

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

On Sat, May 21, 2016 at 6:06 AM, Alissa Cooper <alissa@cooperw.in> wrote:

> (e.g., by implementing 7217 and using the randomized MAC as the Net_Iface
> parameter)


An implementer can't do that because it would be a violation of RFC 7217,
which explicitly defines Net_Iface as "An implementation-dependent stable
identifier". (The key word here being "stable").

--001a114db9042b2f2d0533504bf8
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 S=
at, May 21, 2016 at 6:06 AM, Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D=
"mailto:alissa@cooperw.in">alissa@cooperw.in</a>&gt;</span> wrote:<br><bloc=
kquote 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);paddin=
g-left:1ex">(e.g., by implementing 7217 and using the randomized MAC as the=
 Net_Iface parameter)</blockquote><div><br></div><div>An implementer can&#3=
9;t do that because it would be a violation of RFC 7217, which explicitly d=
efines Net_Iface as &quot;An implementation-dependent stable identifier&quo=
t;. (The key word here being &quot;stable&quot;).</div></div></div></div>

--001a114db9042b2f2d0533504bf8--


From nobody Fri May 20 18:47:40 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 6BEBA12D0DF for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 18:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 DYx8xWeGQmP6 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 18:47:37 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 D61DD12D0BE for <6man@ietf.org>; Fri, 20 May 2016 18:47:36 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id c127so8563989ywb.1 for <6man@ietf.org>; Fri, 20 May 2016 18:47:36 -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=jz3tFfxG0/vccYAHti0fW0TfUjljwR8Xoqs70xN3uKE=; b=hTouh3Io92v0gQbVPMKjT1GmEtE1XyTCSrFfs4uteC3tFx/YgBgJrDJt81Uq/rPiwd d1SLjnuRnpKhaPWYslMTRyp8MnigWGnP7y50Jchb3pJBTruvYw3zbhzJ6TE89Bj8Yq5L D+8FnnmHHs4v1mfFHmuCgGBu/hslk9cD+YJEdJgofLNZrOrxsQ8q/bhsTjS01ac8+bGi nR4viRwtV8uyK7QAtTQreppnxemfaG5kmYhl6LAoR9PEmlkwHPV1+bvMDmVwLiuZKSes FsaD3/7HVi738UEv6YLpJSgTu67p4Nuun5EbmXcLo9HrDq9v7HFl2iJYduwBxk57T0Eo 32MA==
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=jz3tFfxG0/vccYAHti0fW0TfUjljwR8Xoqs70xN3uKE=; b=gh+stk2PiJS7oXiRs+rVF97XNfVfDdMrzDLOMRN4IU91h2tRHMB7S0KssXy+tjFIJX fMAVCqa7n62iwLn0iiHkPXOFud3gRy3venZbIZ3BXAW6FiFJPEv5VJCYpl0YhNbgE0s/ OKt3YZma5bQMhm6zUiwrqKh4BRlNxI2lbz2ZtRcTy3H1eOget/z51+V52dHBoF1alOHc yKRESXwjtcr+3dVNEnggekU3w+UO/Gkw/1k4tbgww8ZECSLi1poAs/FLlN5uGHW7GoHr tO/ApspswQY+48CGEsqbX/RBWLBzIlYZftHa5QU8BHgdVkRiNYwF+KZAK13kddFueFUZ WOcw==
X-Gm-Message-State: AOPr4FXxfewmy0+vdi02g+JYY3yavTOMS1Wa2XPbMiJmooujUWuLR75Eed0D9HJfQdnfwdVEwUStimJyrrXcIXtq
X-Received: by 10.13.220.69 with SMTP id f66mr4017715ywe.132.1463795255810; Fri, 20 May 2016 18:47:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 20 May 2016 18:47:16 -0700 (PDT)
In-Reply-To: <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 21 May 2016 10:47:16 +0900
Message-ID: <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c83f98c50533506496
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3KfaC5WAv6wxNc5eu79zVWYKLN4>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sat, 21 May 2016 01:47:38 -0000

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

On Sat, May 21, 2016 at 8:10 AM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> The messages in this I-D are already clear.


I disagree that they were already clear, and I think that something like
Fernando's text will help a lot to clarify them.

I will note, though, that this draft does the following:

   1. Deletes the text in RFC 2464 and other documents that defines how the
   IID is constructed, and replaces it with a pointer to this draft
   2. Makes it very clear that an implementation that does not choose to
   use a stable IID does not need to follow this draft

The combination of #1 and #2 means that an implementation that does not
choose to use a stable IID can legitimately form whatever IID it so chooses.

--94eb2c0815c83f98c50533506496
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 S=
at, May 21, 2016 at 8:10 AM, Manfredi, Albert E <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_blank">albert.e.manfr=
edi@boeing.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The =
messages in this I-D are already clear.</blockquote><div><br></div><div>I d=
isagree that they were already clear, and I think that something like Ferna=
ndo&#39;s text will help a lot to clarify them.</div><div><br></div><div>I =
will note, though, that this draft does the following:</div><div><ol><li>De=
letes the text in RFC 2464 and other documents that defines how the IID is =
constructed, and replaces it with a pointer to this draft</li><li>Makes it =
very clear that an implementation that does not choose to use a stable IID =
does not need to follow this draft</li></ol><div>The combination of #1 and =
#2 means that an implementation that does not choose to use a stable IID ca=
n legitimately form whatever IID it so chooses.</div></div></div></div></di=
v>

--94eb2c0815c83f98c50533506496--


From nobody Fri May 20 19:15:40 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 1863812D1D1 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 19:15:39 -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 q6A03Qj9zFF0 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 19:15:37 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 98F6F12D0BE for <6man@ietf.org>; Fri, 20 May 2016 19:15:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4L2Faff023453; Fri, 20 May 2016 19:15:36 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4L2FQpa023319 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 20 May 2016 19:15:26 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 20 May 2016 19:15:25 -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; Fri, 20 May 2016 19:15:25 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: default-iids: Clarifying the use of stable addresses
Thread-Topic: default-iids: Clarifying the use of stable addresses
Thread-Index: AQHRsujkuYlKZjWWvUaG4reiTet4Wp/CcCZQgACkyAD//45xEA==
Date: Sat, 21 May 2016 02:15:25 +0000
Message-ID: <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@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
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: <http://mailarchive.ietf.org/arch/msg/ipv6/9GlqoMh76M6phhhxhASgmjGWCu8>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sat, 21 May 2016 02:15:39 -0000

RnJvbTogTG9yZW56byBDb2xpdHRpIFttYWlsdG86bG9yZW56b0Bnb29nbGUuY29tXSANCg0KPiBJ
IHdpbGwgbm90ZSwgdGhvdWdoLCB0aGF0IHRoaXMgZHJhZnQgZG9lcyB0aGUgZm9sbG93aW5nOg0K
Pg0KPiAxLiBEZWxldGVzIHRoZSB0ZXh0IGluIFJGQyAyNDY0IGFuZCBvdGhlciBkb2N1bWVudHMg
dGhhdCBkZWZpbmVzIGhvdyB0aGUgSUlEIGlzIGNvbnN0cnVjdGVkLCBhbmQgcmVwbGFjZXMgaXQg
d2l0aCBhIHBvaW50ZXIgdG8gdGhpcyBkcmFmdA0KDQpZZXMsIGNsZWFybHkgZG9lcyB0aGF0LCBz
cGVjaWZpY2FsbHkgZm9yIGFkZHJlc3NlcyB0aGF0IG11c3QgYmUgc3RhYmxlLg0KDQo+IDIuIE1h
a2VzIGl0IHZlcnkgY2xlYXIgdGhhdCBhbiBpbXBsZW1lbnRhdGlvbiB0aGF0IGRvZXMgbm90IGNo
b29zZSB0byB1c2UgYSBzdGFibGUgSUlEIGRvZXMgbm90IG5lZWQgdG8gZm9sbG93IHRoaXMgZHJh
ZnQNCg0KTm9uLXN0YWJsZSBhZGRyZXNzZXMgYXJlIHZlcnkgY2xlYXJseSBvdXQgb2Ygc2NvcGUg
b2YgdGhpcyBkcmFmdCwgYWdyZWVkLiBXYW50IGFkZHJlc3NlcyB0aGF0IGNoYW5nZSBmcmVxdWVu
dGx5PyBMb29rIGVsc2V3aGVyZS4NCg0KPiBUaGUgY29tYmluYXRpb24gb2YgIzEgYW5kICMyIG1l
YW5zIHRoYXQgYW4gaW1wbGVtZW50YXRpb24gdGhhdCBkb2VzIG5vdCBjaG9vc2UgdG8gdXNlIGEg
c3RhYmxlIElJRCBjYW4gbGVnaXRpbWF0ZWx5IGZvcm0gd2hhdGV2ZXIgSUlEIGl0IHNvIGNob29z
ZXMuDQoNCldlbGwsIGFnYWluLCB0aGF0J3Mgb3V0IG9mIHNjb3BlLiBUaGlzIGRyYWZ0IHNob3Vs
ZCBub3QgYmUgdXNlZCBmb3IgZ3VpZGFuY2UgY29uY2VybmluZyBub24tc3RhYmxlIGFkZHJlc3Nl
cywgc28gd2h5IGlzIHRoaXMgY29udGludWluZyB0byBiZSBzdWNoIGEgYm9uZSBvZiBjb250ZW50
aW9uPyBJdCBzZWVtcyBsaWtlIGFsbCB0aGUgYWRkaXRpb25hbCB0ZXh0IGJlaW5nIHByb3Bvc2Vk
IGhhcyB0byBkbyB3aXRoIHRoaW5ncyB0aGF0IGRvbuKAmXQgcmVsYXRlIHRvIHRoaXMgZHJhZnQg
YXQgYWxsLiBUaGVuLCBkb24ndCB1c2UgdGhpcyBkcmFmdCENCg0KRm9yIGV4YW1wbGUsIHRoZSB3
aG9sZSB0aHJlYWQgYWJvdXQgd2hldGhlciBvciBub3QgaXQgaXMgYXBwcm9wcmlhdGUgdG8gdXNl
IHJhcGlkbHkgY2hhbmdpbmcgTUFDIGFkZHJlc3NlcyBhcyBJSUQsIGZvciBub24tc3RhYmxlIElQ
djYgYWRkcmVzc2VzLCBpcyBhIHRvcGljIGZvciBzb21lIG90aGVyIGRyYWZ0LCBJTU8uIE5vdCB0
aGlzIG9uZS4gVGhvc2UgY29uc2lkZXJhdGlvbnMgZG8gbm90IG5lZWQgdG8gZmluZCB0aGVpciB3
YXkgaW4gdGhpcyBkcmFmdCBhdCBhbGwuDQoNCkJlcnQNCg0K


From nobody Fri May 20 20:23:37 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 47B1D12D51C for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 20:23:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.426
X-Spam-Level: 
X-Spam-Status: No, score=-3.426 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, RP_MATCHES_RCVD=-1.426, 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 OQ_hWjKzF1Df for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 20:23:34 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 5F20712D52C for <6man@ietf.org>; Fri, 20 May 2016 20:23:34 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id o16so8878475ywd.2 for <6man@ietf.org>; Fri, 20 May 2016 20:23:34 -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=QgNiGPEoju+msMzZNMx7PgwsGXXfPX/nvupEEJRAKZA=; b=M/MqFFUIAVM/oioyw8Itax2PRZbfYBH4q4XH5EL+txD9ZU1DAVV0bhov/x8Dp7zBng N+M1ZHSUr3/FvOczsM2x3Ec5WImcZ8IdJ6ltvKNj2oUUGAwKb2VJ8jeaMfQpfW3FLQXV fNDrcIv+lgwpwrsfEhchov44blMN/h2hIygCii99JzUCE8KSZsLWHr9ecxNIy1WB0jSQ XafX+J3R2hxLWN/KWBZs/zYcDUDR14PkeOYdcNcEgwY60jes2fY8p9RmRf+GXinv/NTx aJoQC9CEJl022gi1OiFGu3330j9SXjm4wkW959ancngq6g8iioLAXadrBfeZB16Sddqw oaZQ==
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=QgNiGPEoju+msMzZNMx7PgwsGXXfPX/nvupEEJRAKZA=; b=dpzehb976qlg6lbi7FWEon+Ui5Kiqyzf0K6cbxLoDwu2KWok8RI/q7pTk8bM0QwIih cBO3GiTKWgiDzATPkuqHRuVsmutmwxFhtevl3lYnjmeZnPPULocFQOJiHFui2ePlSNOD MJsxgLkhoKRPUPyuEe3lODX4fvs9o39SvQYa78A5Sj9Y8qIl8YTnPnI4U+amHJaRMN5G fWbgyomBrwBqPUn+/CIT0suBdSM8N2SXsD9eXNtI6oU4URxL5X18g7vHTCUSSlgiGqdw vCYpkA/yp5GiSuYzcTNtxcgx/vXmgvTX515KMjhwjHP6jiOOrnHLMnxURh2T1B9leuYj hkIg==
X-Gm-Message-State: AOPr4FWjH8iBufS/5EgHToKZk1/hh+jRa/IiLGYiWHtAA8MVBkGHkCIXVkRcSRrl9ix6q9jxJ4lMfGGr2+As5ei5
X-Received: by 10.129.27.9 with SMTP id b9mr3813810ywb.173.1463801013161; Fri, 20 May 2016 20:23:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Fri, 20 May 2016 20:23:13 -0700 (PDT)
In-Reply-To: <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 21 May 2016 12:23:13 +0900
Message-ID: <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=001a1142a41a69e996053351bbef
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lCzI1J35E4VpcIxnVnPsqYNFiiQ>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sat, 21 May 2016 03:23:36 -0000

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

On Sat, May 21, 2016 at 11:15 AM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> > The combination of #1 and #2 means that an implementation that does not
> choose to use a stable IID can legitimately form whatever IID it so choos=
es.
>
> Well, again, that's out of scope. This draft should not be used for
> guidance concerning non-stable addresses, so why is this continuing to be
> such a bone of contention? It seems like all the additional text being
> proposed has to do with things that don=E2=80=99t relate to this draft at=
 all.
> Then, don't use this draft!
>

All I'm saying is that if we publish this draft, then the formation of IPv6
IIDs on many link layers, including ethernet and wifi, becomes completely
unspecified, and implementations (well - implementations that don't want to
use stable IIDs) can do whatever they want with no recommendations or
guidance from the IETF.

--001a1142a41a69e996053351bbef
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 S=
at, May 21, 2016 at 11:15 AM, Manfredi, Albert E <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_blank">albert.e.manf=
redi@boeing.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"><sp=
an class=3D"">&gt; The combination of #1 and #2 means that an implementatio=
n that does not choose to use a stable IID can legitimately form whatever I=
ID it so chooses.<br>
<br>
</span>Well, again, that&#39;s out of scope. This draft should not be used =
for guidance concerning non-stable addresses, so why is this continuing to =
be such a bone of contention? It seems like all the additional text being p=
roposed has to do with things that don=E2=80=99t relate to this draft at al=
l. Then, don&#39;t use this draft!<br></blockquote><div><br></div><div>All =
I&#39;m saying is that if we publish this draft, then the formation of IPv6=
 IIDs on many link layers, including ethernet and wifi, becomes completely =
unspecified, and implementations (well - implementations that don&#39;t wan=
t to use stable IIDs) can do whatever they want with no recommendations or =
guidance from the IETF.</div></div></div></div>

--001a1142a41a69e996053351bbef--


From nobody Fri May 20 20:29:45 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 E1DBB12D1D7 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 20:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 iLKtmrcTSVCW for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 20:29:43 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 E510F12D14B for <6man@ietf.org>; Fri, 20 May 2016 20:29:42 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id z184so165955669vkg.0 for <6man@ietf.org>; Fri, 20 May 2016 20:29: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=vBT28YOszr9SuYscRv0fuLAoWkLVgOhfL7OvgHHBKoE=; b=Rg+nNjcp4TfPw8rnuic7vFQK83WkTNq5gyYSkr/bCFHBdGufe17kj8Qe9JXuNTOgkk umbg+lx6wc7uSSjMAMjKYnGkEWN7x1T7Gbo7WYkVpS9ksbGsSalwyyleR5YWUa+Q9tPY QnY7s13V+sFukiO++KuRK+2+emTHGFBP9LX5dVefhPUJTdwIW/asON9jhA5KZkzQnYf1 9Os+rOvm61rapoDg2iSyM10sxqLvwBoF/t5orH1+37kW8A8EvFcFGID0jvG9nJT2xUtd W5t+wPPGIDDy0HIhd1aMLmKM1d6gUPJHP67AOHkLKyLLS0/NtAAvhq5dxbSTF0iZRINS pHJw==
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=vBT28YOszr9SuYscRv0fuLAoWkLVgOhfL7OvgHHBKoE=; b=PPSWGIXv45wOhBoGa2db2eEGjIqZ7ZfDfJQysaMACnPrFwKKHv3FlswkJcpbqpKmsz 8qQa7ovgoeRFC+ukLhfatpOQmi1rISf8Egp5i4fVI1iXlLXZSKgG8yjYT9bKbVAyX8gs H2p+CHtg4JYgnSMiyVqXTKJLz5wGQN5krwUBG8T4BRDQZrPKD9kVyu91B59MNMndTzk3 URHeqelORTrUIxRtEavXutuQLMzPphbWu7sy1MAyZ80cW4WsyOFJvlWMbYkBS29EoIeA y38A9hxos9d/ahLSh7wBpTmevFz4so1AN6nOC4ukw16qa6ZaqEZrKuHGtu0QjjSl1nRe STRg==
X-Gm-Message-State: AOPr4FWwjmVSsLUuBF7OVnU850MBskN5+LilSd30h21EGijukHYtWxXdpJsMfqR0vmZoRL/R3ctcneBteouKQQ==
X-Received: by 10.31.146.144 with SMTP id u138mr3568216vkd.2.1463801381904; Fri, 20 May 2016 20:29:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Fri, 20 May 2016 20:29:12 -0700 (PDT)
In-Reply-To: <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 21 May 2016 13:29:12 +1000
Message-ID: <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WPsiNH-sxBnlEsYpiBhWg0gE-54>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sat, 21 May 2016 03:29:45 -0000

On 21 May 2016 at 11:47, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Sat, May 21, 2016 at 8:10 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com> wrote:
>>
>> The messages in this I-D are already clear.
>
>
> I disagree that they were already clear, and I think that something like
> Fernando's text will help a lot to clarify them.
>
> I will note, though, that this draft does the following:
>
> Deletes the text in RFC 2464 and other documents that defines how the IID is
> constructed, and replaces it with a pointer to this draft
> Makes it very clear that an implementation that does not choose to use a
> stable IID does not need to follow this draft
>
> The combination of #1 and #2 means that an implementation that does not
> choose to use a stable IID can legitimately form whatever IID it so chooses.
>

Which I think is consistent with

"Significance of IPv6 Interface Identifiers"
https://tools.ietf.org/html/rfc7136


(without looking this draft being discussed because I'm about to go
out the door, it might be worth referencing that RFC if it usefully
supports some of the clarifications made).


Regards,
Mark.


From nobody Fri May 20 22:41:08 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 7A7F412B026 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 22:41:07 -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 gHJUsPmttr4w for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 22:41:06 -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 E603712D1B2 for <ipv6@ietf.org>; Fri, 20 May 2016 22:41:05 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id xk12so45748233pac.0 for <ipv6@ietf.org>; Fri, 20 May 2016 22:41:05 -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=X5R5pYVzP/+V91zF2purL2q9ssw3f4drd1UizdeLfso=; b=AWBHs7iS+PKfpKvcevg1/YbTSq7Ktdhlh5BtS4vCc+1Fa+jr7lZMS2YPfUtp8SYJzO 1EmPNL14HmNhkCUo8ptriy2IPxa1QbniCsRV93qpnzuNFfgGx9QRn0PpNNVycT60b3Ty iYgWzqOQERj71Ij2ZxfAmsJ7Q1jjsqBvN0xYafZ8jle1pYY2N9Qk0eF3sCt+LEjKtVSD 6Z9MqtEqaPvwtTAHaIgNbCXzBVO4Qqy72/2pKMmeA9J5OSyPPUCtmOf0sjgcJRy6BjKJ yRoIYpfjBPpXVZcG+sxlbgw5QJ275oCrhFm3DCkg7n3+0dhAOqBsfpUpjNr3GItQth+Q c1vA==
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=X5R5pYVzP/+V91zF2purL2q9ssw3f4drd1UizdeLfso=; b=ZFkk4aRalYUWYfp1eO+vcFK8CMVGuPlLwHH0ItDznGrkhdAw2WWghkOBsGMZWrckVF +Jwwleaw7skWbUce4KTPyRKCut934Il8QIHc2OOQ8O9HLHui2qXBPiLQq9xu4x0cphnK Mh06FiIH5BIu6haQmuU/HT6NJWDbQN43DWCDLa7WjGSe9Qypyhf2O5mwNmwcDiz0ISUE i2q/o/xg1VjITI1GG/MyiX3uLjNl9oqbFywG5NxKbELG6ertaoXCy8WJ4rwCsftEZQMx fZ5Nl9BmHMQa+u/2k8d/Aw0/UDv7c1H5dKeFnrpCcx1tMwAridOrw8qwHqsg1/yNh6cG N8SA==
X-Gm-Message-State: AOPr4FVnl3qXLSWji3J8yUNjvLQ36lVcPgRaNZtTvzONZx8kncdvDUaImFb/56TtLBERDQ==
X-Received: by 10.66.84.164 with SMTP id a4mr10385657paz.90.1463809265170; Fri, 20 May 2016 22:41:05 -0700 (PDT)
Received: from ?IPv6:2406:e007:490e:1:592f:5aea:c70f:9aae? ([2406:e007:490e:1:592f:5aea:c70f:9aae]) by smtp.gmail.com with ESMTPSA id o87sm1275160pfa.75.2016.05.20.22.41.02 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 May 2016 22:41:04 -0700 (PDT)
Subject: Re: default-iids: Clarifying the use of temporary addresses
To: ipv6@ietf.org
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <02499023-aa6d-3022-3d84-5a2a9f63fcee@gmail.com>
Date: Sat, 21 May 2016 17:41:14 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3KlfoKDgRaMRuK8mMGiBAqBMfjU>
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, 21 May 2016 05:41:07 -0000

On 21/05/2016 15:29, Mark Smith wrote:
> On 21 May 2016 at 11:47, Lorenzo Colitti <lorenzo@google.com> wrote:
>> On Sat, May 21, 2016 at 8:10 AM, Manfredi, Albert E
>> <albert.e.manfredi@boeing.com> wrote:
>>>
>>> The messages in this I-D are already clear.
>>
>> I disagree that they were already clear, and I think that something like
>> Fernando's text will help a lot to clarify them.
>>
>> I will note, though, that this draft does the following:
>>
>> Deletes the text in RFC 2464 and other documents that defines how the IID is
>> constructed, and replaces it with a pointer to this draft
>> Makes it very clear that an implementation that does not choose to use a
>> stable IID does not need to follow this draft
>>
>> The combination of #1 and #2 means that an implementation that does not
>> choose to use a stable IID can legitimately form whatever IID it so chooses.
> 
> Which I think is consistent with
> 
> "Significance of IPv6 Interface Identifiers"
> https://tools.ietf.org/html/rfc7136
> 
> (without looking this draft being discussed because I'm about to go
> out the door, it might be worth referencing that RFC if it usefully
> supports some of the clarifications made).

So, reviewing the thread, I think we've been barking up the
wrong tree to some extent (hence the new subject header above).

RFC4941 aims to be compatible with SLAAC but it includes this
near the beginning of the protocol description:

'  2.  Create additional addresses based on a random interface
       identifier...'

In other words it's *explicit* that there is always an existing
address, which I think we agree is actually completely unnecessary
for client computers. (It's also at variance with some of the wording
in RFC4862, which frequently refers to IIDs as 'unique' per interface,
which can't be right, otherwise RFC4941 simply wouldn't work.)

So, I think some RFC needs to state that it is legitimate to have a host
with only RFC4941 global addresses.

Apart from that I'm quite happy with Lorenzo's comment above. Once
the IID bits have no semantics, anything goes.

Regards
   Brian


From nobody Fri May 20 22:44:24 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 A1B2812D1B2 for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 22:44: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 S0TDKPalBroG for <ipv6@ietfa.amsl.com>; Fri, 20 May 2016 22:44:21 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 D598E12B026 for <ipv6@ietf.org>; Fri, 20 May 2016 22:44:20 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id c189so49158422pfb.3 for <ipv6@ietf.org>; Fri, 20 May 2016 22:44:20 -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=NKXVJHIg+qEHMfiWkHSArgb6xVgdMUSZnQSHH+PcH9g=; b=gxD5ixk7lL8tZbUJTB+7J0qQQxEMGRSMahko5MFUWPzz1M8plPgPDCvL3FOxu149kQ Yv17T4WL+8+Uwh/IPxw/bjQ7IdyrCR/90NFqalN6tAmFwjRctiV2yBfZ8m6BQw6WZnyY vU70BN9k4PasCBDXUkcAJxcm3RuVvwjB608YIrcH014NxjTajuqqjWC6/lb3ciMJj64w pA0Jlzghah37UI2iOySrDJwZAiOb1GsvHbUUxANq1qZgN52IHqQWpVvONtD2hX6njT93 lPAviM2Qzgj+Bk91cSFn1tX1zIj6BwILlrGIJkBpNN1dgkh8VlAQcFHmwx6KXYtv0BTy Dm8g==
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=NKXVJHIg+qEHMfiWkHSArgb6xVgdMUSZnQSHH+PcH9g=; b=FelLKmnVboUTxdCA2oDWC3vvswADpLrSpkDnDAFrhnId1tChHIl5yMqJx9yWF+eBDM rB13GFOWQZR4Xz5YjUK4Rsjt+ybK6jZHNLnQD9Fr/5xyaQouB7FBB10IJ7BvlvPZy3M7 u7kk/IXvSWDvaRoWwv1kb3mkShvTFF+gfJmWjS4V0F5gNbRnhagB57A2jUL563tvoim3 k2KM9jubPpHmraY5qYC8s2cEbhrEum72lLnXpKbP50Wk27Rpb50+JQQik8OOprz1FtTz R9k0XCbbu0hGHwsJvkEbfKhocJp97hrNDfXeFbFu//3WOq7iFNnw5tpneFrVA/eSXTy2 PLVw==
X-Gm-Message-State: AOPr4FVuVsYBN5jDZHOaZVnUdwH/jkeChZFp0bLCdXbwjykKFcQq56i4pr1SMzg/A7NZqg==
X-Received: by 10.98.93.7 with SMTP id r7mr10556378pfb.66.1463809460446; Fri, 20 May 2016 22:44:20 -0700 (PDT)
Received: from ?IPv6:2406:e007:490e:1:592f:5aea:c70f:9aae? ([2406:e007:490e:1:592f:5aea:c70f:9aae]) by smtp.gmail.com with ESMTPSA id e184sm31019496pfe.14.2016.05.20.22.44.18 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 May 2016 22:44:19 -0700 (PDT)
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Alissa Cooper <alissa@cooperw.in>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a6b9536d-2851-ed23-3d58-98bf0fd3c551@gmail.com>
Date: Sat, 21 May 2016 17:44:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/khPPQs7OYpvXEQDHNlZ1XHT4N_w>
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, 21 May 2016 05:44:22 -0000

On 21/05/2016 09:06, Alissa Cooper wrote:
>=20
>> On May 18, 2016, at 1:26 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>> What if we dropped requirement #1 in Section 3, but left the rest the =
same? This would open the door such that people who wanted to comply with=
 the SHOULD-level recommendation in this spec in the presence of randomiz=
ed MAC addresses still could (e.g., by implementing 7217 and using the ra=
ndomized MAC as the Net_Iface parameter), but directly embedding a MAC ad=
dress in the IID would still go against the SHOULD NOT recommendation her=
e.
>=20
> I don=E2=80=99t think I saw anyone respond to this suggestion, so I=E2=80=
=99d like to ask again for people=E2=80=99s opinions about this.
>=20
> To my eye this is a nice compromise.

Unfortunately I'm not sure it would change anything. The requirement 1 pr=
operty
seems to be exactly what a site operator who wants stable addresses will =
need.

   Brian


From nobody Sat May 21 03:09:08 2016
Return-Path: <alexandru.petrescu@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 18D0912D09F for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 03:09:07 -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 y_uzIbCAW41E for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 03:09:05 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 72F4E12B05D for <ipv6@ietf.org>; Sat, 21 May 2016 03:09:05 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id n129so14070530wmn.1 for <ipv6@ietf.org>; Sat, 21 May 2016 03:09:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=49DY3ggt4p9MDjNiqwELAvHcNO+b6m3k5Q4sWy3d2hw=; b=xapU5bfuTpkz0Ru8b8g/yPMEbL9gvBKkaOvEeibrshQJ0UpVoKaaZQUvFtQ7kRUMSW Zj+Y1atVoznWH6T4rqjxXSK0rb9rpFLPJZyUmHlk40CHd72JNoRGq+sPW3j5TPyRVAoE bt5VGLgXwagRKjgXyvBmr+c0Wm0rXRslzINYG9Nz19ZF33WBhVgWwmb4j6hZrSPtEzEI QVr8Zr4CoP2+33NkeRdWivWMhVRuxe17573cQYrF8eef4sv6MRifwJk8x1OwxOkppwOB ACoSmf2beUKhQKTgshf26p0C7Wh6DDj1rsXDul3jX8p7Dhyf/CkY72Z/GRhi9mLs1db8 1Ydw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=49DY3ggt4p9MDjNiqwELAvHcNO+b6m3k5Q4sWy3d2hw=; b=hl3jbAgGQVIoptrdfCHeZyv27/kKgZl+17fEXu3Zxym3bww8TOu85XR2n+qHKTww3y r9fdGmVK8UI9v5TyK2OfHj1ty0p8CjR53oEcQkEIfPjhglY17P32kIDorlaRWCV9mdvh +jxUErDsFdapBWMVldD6u+IVkvJAmECB6MbIrxUOt6WvE3zPxvS1tdxhfj4/7CuxikH9 hupqZkSlZ0thqasv32uNch5HKCH2XXXQ+UIPbj7KpFx09u9hjjc8f6pm9SoFwPPUy6K8 Ondwdh2VVdBgP0KIhcFFftMSrMe0SHVjL0KBOQ41YuVgYo/UZHpgDPdsjX6Vs4iJJcaz 5sRQ==
X-Gm-Message-State: AOPr4FXKIZanG3vMZRaMgmqpLS/unGLr3KtX7Q1k7pjk/6EF0y8g71mOlO4r4Q4zxXXtyA==
X-Received: by 10.28.213.137 with SMTP id m131mr8276123wmg.24.1463825343944; Sat, 21 May 2016 03:09:03 -0700 (PDT)
Received: from [192.168.0.26] (mry91-1-82-229-156-225.fbx.proxad.net. [82.229.156.225]) by smtp.googlemail.com with ESMTPSA id g3sm24239703wjb.47.2016.05.21.03.09.02 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2016 03:09:02 -0700 (PDT)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: ipv6@ietf.org
References: <573F3F49.9090107@si6networks.com>
Message-ID: <ce73a827-a137-eab3-3b1e-9e4895d9b6bd@gmail.com>
Date: Sat, 21 May 2016 12:09:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <573F3F49.9090107@si6networks.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/suxYJEA4y9aHOFuJPHiLXTSHDmU>
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, 21 May 2016 10:09:07 -0000

Le 20/05/2016 à 18:46, Fernando Gont a écrit :
> Folks,
>
> In the hopes of making this document more clear regarding whether
> this document is requiring the use of stable addresses, how about
> adding the following text:
>
> "SLAAC has traditionally resulted in stable addresses, since the IID
> has been generated by embedding a stable layer-2 numeric identifier
> (e.g., a MAC address)

Add [RFC2464] as a reference; dont allude to SLAAC, because:

> [RFC4941] implies, throughout the specification, that temporary
> addresses are generated and employed along with temporary addresses.

RFC4941 has a problem in that it treats the privacy problem of SLAAC 
only by looking at the IID.  But SLAAC is made of two parts: IID and 
prefix.  RFC4941 does not treat of the prefix randomization.

As such it is wrongly titled "Privacy Extensions of SLAAC" - it is 
"Privacy extensions in the IID" actually.

(RFC4191 has more problems, but we can discuss separately).

> We note that depending on the specific device type and/or operating
> environment, a host may or may not want to configure and/or use a
> stable address, but may e.g., exclusively use temporary addresses.

I agree.  They are called "client-only" devices.

> This document does not require that stable addresses be actively
> employed or even generated, but simply provides a recommendation
> regarding how stable addresses should be generated when a node
> decides to do so.
>
> Similarly, this document is orthogonal to other privacy improvements
> such as MAC address randomization.

I dont understand - an IID based on a random 48bit 'MAC' address has the 
same effect as randomizing an IID.  This is not orthogonal.

> This document aims to mitigate
> known security and privacy implications of stable IPv6 addresses in
> a hardware/protocol-independent manner, without any assumptions on
> the security/privacy properties of the underlying layers. "

I agree, but  we still dont have a problem description of what to 
mitigate - a risk analysis.

Alex

>
> If you have suggestions for improvement, please do let me know, and
> send proposed tweaks.
>
> Thanks,
>


From nobody Sat May 21 03:12:18 2016
Return-Path: <alexandru.petrescu@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 0C5BF12D09F for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 03:12:17 -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 QR1Lj7cmJVUn for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 03:12:15 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::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 4D71E12B029 for <ipv6@ietf.org>; Sat, 21 May 2016 03:12:15 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id i142so14162604wmf.0 for <ipv6@ietf.org>; Sat, 21 May 2016 03:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=cy0FXCmJz9xmiqojBYkjLYq0yWOl5SIZ7wLCwLESjWY=; b=a5ylb8K6VGDXZodRggi70am/CJjEIwDa3n/5Mn+/QZMZjVo5UkolrkYKtfmmfXy6py FLQh1ksDHjj2k1dFOBAeFwUMIMQ54qwILgnnarQYqo0Mqv5Kmrf5C+eYpUa46rAKxd0H h/uYIAPpt0JpcrZESs4M5n44OdVCqer3obPEYITDrQMaW5PygXx2zSWZjj8L8MLkRXRF LOUBloORFnhJ7MQ+6H5H48gy8DY2yTDirIGdRut7PpBs3k0rLsyFhOhrTEN2zKRcRzpI z3yTuJ8NK+HCL9vFA66hHuxA37PrvQ5ZHWSuDZV70teE2gaoI4udfBIL7mArXLf5M0F3 e+vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=cy0FXCmJz9xmiqojBYkjLYq0yWOl5SIZ7wLCwLESjWY=; b=V5tm1QeMjuPEgeSTGgH3lM6E3MW8ST+gjHSmsWLVmSY/xftAqjnGM0allANl/7IgHZ FiWSVj2u8hHb/HpHbNW0XIh1T88p8tDV5v5ZlnxPvtgyoR4ynYppzcQ67cGC1D8LuOhw ewGsfLekQCLwZfd9czsWX5s6DFkSpJGQIiKCH9T9LMlW9C1g+bv/QbNz7EMo4xV7rYAW xAKLpBJpo2UOqPX4eV0cpPkGBbhydNzUAbN76uawZyGbY2ByF5V3niZH85bbFfvrzc3h FC4nIhcM0xATrpIjNxi1OXhgLRAc+8PO9H8dtakloqYFSu7B3Yh55g52KrfcnuXEdk4q PsHQ==
X-Gm-Message-State: AOPr4FWnyfSig66mIPpb5//+Xp+Re5BIe8DNTPcQFeJPtuBA/3KiIIsHFx0XCXu6XC9X8w==
X-Received: by 10.194.249.36 with SMTP id yr4mr8606999wjc.59.1463825533821; Sat, 21 May 2016 03:12:13 -0700 (PDT)
Received: from [192.168.0.26] (mry91-1-82-229-156-225.fbx.proxad.net. [82.229.156.225]) by smtp.googlemail.com with ESMTPSA id jp2sm24298895wjc.16.2016.05.21.03.12.12 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2016 03:12:13 -0700 (PDT)
From: Alexandre Petrescu <alexandru.petrescu@gmail.com>
X-Google-Original-From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: ipv6@ietf.org
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com>
Message-ID: <efa88c4b-5c08-ea72-34e3-23aa2c5fbbe8@gmail.com>
Date: Sat, 21 May 2016 12:12:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/76C6hlllBRpBEMorVboYtLSpeQQ>
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, 21 May 2016 10:12:18 -0000

Le 21/05/2016 à 05:29, Mark Smith a écrit :
> On 21 May 2016 at 11:47, Lorenzo Colitti <lorenzo@google.com> wrote:
>> On Sat, May 21, 2016 at 8:10 AM, Manfredi, Albert E
>> <albert.e.manfredi@boeing.com> wrote:
>>>
>>> The messages in this I-D are already clear.
>>
>>
>> I disagree that they were already clear, and I think that something like
>> Fernando's text will help a lot to clarify them.
>>
>> I will note, though, that this draft does the following:
>>
>> Deletes the text in RFC 2464 and other documents that defines how the IID is
>> constructed, and replaces it with a pointer to this draft
>> Makes it very clear that an implementation that does not choose to use a
>> stable IID does not need to follow this draft
>>
>> The combination of #1 and #2 means that an implementation that does not
>> choose to use a stable IID can legitimately form whatever IID it so chooses.
>>
>
> Which I think is consistent with
>
> "Significance of IPv6 Interface Identifiers"
> https://tools.ietf.org/html/rfc7136
>
>
> (without looking this draft being discussed because I'm about to go
> out the door, it might be worth referencing that RFC if it usefully
> supports some of the clarifications made).

I agree with this point.  It is good to refer to that RFC about 
significance of IID...

Alex

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


From nobody Sat May 21 16:58:54 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 51F3812D140 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 16:58:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 Qq4aP7y_wPlO for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 16:58:51 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::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 8D83212D0A5 for <ipv6@ietf.org>; Sat, 21 May 2016 16:58:51 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id c189so184673414vkb.1 for <ipv6@ietf.org>; Sat, 21 May 2016 16:58:51 -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=ll4XxPGglFcFn9/XRmRxubvwzVf1ttGF4OPswACLxZc=; b=GeYFGYkFS7ioBSWnusebQ4p+ZE60nL8i1sz0EU+r50G/Fl19p6yL7SO7jIU/VoNX7n ZdO1dF+Wk5S6f4cAYCq/bU9xsRX/nfVaUWv8XeDIxs2nwjkFvmQ7t43htHUou4rPLDa0 D9YV+TZxa701ihdIsF3Meo+vQOnz0zkDvrTvuEzw/6LWeK2fmVl+XtLCxFgfnl/tfyAb lKjAWvrfboRwQ2dMHczsfk8LVyTyVK2VlU9+B2R5Q5Y7ihfKlGXOEN7kB7j1djM5hURD SCHuSZDmyo1i9sKt1vY0DdgqkYBjTo1q8My/weCOLX5jx8L7mfxuPdS4nMZAlxZ/jHDn fsBA==
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=ll4XxPGglFcFn9/XRmRxubvwzVf1ttGF4OPswACLxZc=; b=QWAO7jRxoli8N2GgxesBODntTa0YGabF4BtPodUnB1tgLhNsL7A1AA0OpNxyvf+A+6 7LxugXmGKzRLIgB98q/zyeJZgzjrxqJsguTMLSwlXCBtW0+0oikh6SRAqgYMuNpfX04r xZp9NwOVwBAqi84hw9kqVRekHlvNE+MQ8NBjmw7cDzIU8NVGlTyMUH7YBz3nHh/hh/32 bKY45IwHBv86UYCZKDVrp2xmqjKLOZ1gTypg8trvmxeQZ3dhHH4sm9v0E/KCmaQmc+Tf ZL+2HldZ1xGLBXpMJwYjlYvizBI1YTJI6JY+A501qDDCFP5/NDGx9Ywk2EkF+kFCgf7G f2cw==
X-Gm-Message-State: AOPr4FV0ZtbXDFkDnXXM8dQ2t3Z2Psg0uF+CbDLBXeGwpkBiRPz7gSeu1ilDMtaeURCaxujDW43hEY/8IoEKJQ==
X-Received: by 10.31.73.132 with SMTP id w126mr5796070vka.94.1463875130603; Sat, 21 May 2016 16:58:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Sat, 21 May 2016 16:58:21 -0700 (PDT)
In-Reply-To: <ce73a827-a137-eab3-3b1e-9e4895d9b6bd@gmail.com>
References: <573F3F49.9090107@si6networks.com> <ce73a827-a137-eab3-3b1e-9e4895d9b6bd@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 22 May 2016 09:58:21 +1000
Message-ID: <CAO42Z2yg9pGFrzf69LHAhKxrZ0dOH3=FUP0k3ZjeGN8dMp3Xww@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Alexandre Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/JlKI8pkB6HbwfsR51p-lOtVuM4s>
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: Sat, 21 May 2016 23:58:53 -0000

On 21 May 2016 at 20:09, Alexandre Petrescu
<alexandru.petrescu@gmail.com> wrote:
>
>
> Le 20/05/2016 =C3=A0 18:46, Fernando Gont a =C3=A9crit :
>>
>> Folks,
>>
>> In the hopes of making this document more clear regarding whether
>> this document is requiring the use of stable addresses, how about
>> adding the following text:
>>

<snip>

> RFC4941 has a problem in that it treats the privacy problem of SLAAC only=
 by
> looking at the IID.  But SLAAC is made of two parts: IID and prefix.
> RFC4941 does not treat of the prefix randomization.
>
> As such it is wrongly titled "Privacy Extensions of SLAAC" - it is "Priva=
cy
> extensions in the IID" actually.
>

I see your point, however that RFC is describing how privacy
extensions work with the SLAAC address configuration method, where as
a title of "Privacy extensions in the IID" would imply that it is not
address configuration method specific (in other words, would equally
apply to using DHCPv6 for address configuration.)


> (RFC4191 has more problems, but we can discuss separately).
>
>> We note that depending on the specific device type and/or operating
>> environment, a host may or may not want to configure and/or use a
>> stable address, but may e.g., exclusively use temporary addresses.
>
>
> I agree.  They are called "client-only" devices.
>

Actually, I wouldn't be so specific about their role.

For example, a file transfer between two smartphones would mean one of
them, for the purpose of the application, is acting as a server
(sender) while the other, for the purpose of the application, is
acting as a client (receiver). For the duration of the transfer, both
application server and client could be using temporary addresses, with
the application client discovering the application server's temporary
address via an application layer referral or announcement mechanism.

The temporary addresses only need to persist for as long as the file
transfer is taking place. RFC4941's default preferred lifetime of 1
day, and a valid lifetime of 1 week for temporary addresses is likely
to be long enough for most if not all of these types of applications
on personal devices like smartphones, tablets and PCs.

The roles of 'client' and 'server' don't exist at the IPv6 (and IPv4)
layer - devices at that layer are just packet senders or receivers -
or peers of each other. (I read [1] a while back, and it described
DECnet as the "first networking product to provide general-purpose,
peer-to-peer communications". The other popular layer 3 protocols
since have all been peer-to-peer.)

The roles of 'client' or 'server' are application layer concepts. It
is only IPv4 NAT that has created the requirement to consider devices
at the network layer to be 'clients' or 'servers'. As we don't need to
do NAT in IPv6, we don't need to both classify and constrain ourselves
to thinking of devices as exclusively being only one of either a
'client' or a 'server'.


[1] - "Overview of Digital's Open Networking" -
http://www.hpl.hp.com/hpjournal/dtj/vol5num1/vol5num1art1.txt


>> This document does not require that stable addresses be actively
>> employed or even generated, but simply provides a recommendation
>> regarding how stable addresses should be generated when a node
>> decides to do so.
>>
>> Similarly, this document is orthogonal to other privacy improvements
>> such as MAC address randomization.
>
>
> I dont understand - an IID based on a random 48bit 'MAC' address has the
> same effect as randomizing an IID.  This is not orthogonal.
>

It's orthogonal because this group isn't trying to solve privacy
issues at both layer 3 and layer 2 at the same time. Tthey're separate
problems, because they occur at separate layers. The privacy and
functional issues at the different layers may be different - assuming
they aren't may result in a lack of privacy at one or both of the
layers because the proper problem analysis won't have been done.


>> This document aims to mitigate
>> known security and privacy implications of stable IPv6 addresses in
>> a hardware/protocol-independent manner, without any assumptions on
>> the security/privacy properties of the underlying layers. "
>
>
> I agree, but  we still dont have a problem description of what to mitigat=
e -
> a risk analysis.
>
> Alex
>
>>
>> If you have suggestions for improvement, please do let me know, and
>> send proposed tweaks.
>>
>> Thanks,
>>


Regards,
Mark.


From nobody Sat May 21 18:28:10 2016
Return-Path: <fernando@gont.com.ar>
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 B171212D1AE for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:09 -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 aygeEaTXB4OB for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:07 -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 9BBE512B05C for <6man@ietf.org>; Sat, 21 May 2016 18:28:07 -0700 (PDT)
Received: from [152.207.83.17] (unknown [152.207.83.17]) (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 7168280243; Sun, 22 May 2016 03:27:52 +0200 (CEST)
Subject: Re: default-iids and stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
References: <573B5FAC.7060300@gont.com.ar> <CAKD1Yr3XUh-t8B_zKz9SPOdsG4Gyf-VhW33zDzb9PSNMo9uXTw@mail.gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
X-Enigmail-Draft-Status: N1110
Message-ID: <573E5B00.1010401@gont.com.ar>
Date: Thu, 19 May 2016 20:32:00 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3XUh-t8B_zKz9SPOdsG4Gyf-VhW33zDzb9PSNMo9uXTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5WnO8vdx6Rc1rxq6r8gFxOYDqKg>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 01:28:09 -0000

On 05/17/2016 09:03 PM, Lorenzo Colitti wrote:
> Fernando,
> 
> your points are technically correct: from a standards perspective,
> draft-default-iids makes things no worse than they are. In fact it's a
> mild improvement.

It makes things way better. It is a god way to produce stable addresses
for those scenarios in which you need them. It mitigates network
tracking, address scanning, and device speific attacks.



> However, we operate in a very different world than we did in 1996. We
> know know that pervasive monitoring is a real threat, and other parts of
> the IETF are explicitly working on randomizing link-layer addresses.
> 
> In such an environment, I believe this WG cannot credibly mount a major
> overhaul of IPv6 IID generation rules, and simply say that privacy is
> "no worse than it already was".

Huh?

This document just says "if you need stable addresses, use RFC7217".
That's it.


> If we mount a major overhaul (and it
> *is* a major overhaul, both in terms of number of RFCs that are changed
> and in terms of devices affected), we have to do better than that in
> addressing the privacy concerns inherent in the existing specs.
> 
> In its current state, draft-default-iids still says that:
> 
>   * For every prefix, every host SHOULD configure addresses that never
>     change - permanently, until the end of time.

No. The document says t very clearly, up front, that you do this just in
scenarios where you would be generating stable addresses.


>   * Every link layer, past present and future, MUST define mechanisms
>     that allow calculation of such per-link-permanent addresses.

Yes. Because you cannot tell beforehand if an ap or environment using
that link-layer technology will need/require stable address. -- that's
an operational decision.


>   * Even though MAC address randomization is embraced by other parts of
>     the IETF and explicitly dealt with in standards track RFCs, nodes
>     SHOULD NOT use said random MAC addresses to form IPv6 IIDs - for no
>     reason that I can see.

I referenced the same I-D a hundred of times, already:
draft-gont-predictable-numeric-ids

Please also the discussion on identifiers in RFC4941.

After reading those two documents, could you please tell me what's still
not clear?

(FWIW, I've posted a summary of the issues a number of times, already).


And again: I'm all for link-layer address randomization. I'm not for
embedding a link-layer ID in an IPv6 IID. The above two documents
explain why, and Brian Carpenter has provided yet another explanation
and sample scenario.

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Sat May 21 18:28:26 2016
Return-Path: <fernando@gont.com.ar>
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 6C43012D5D1 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:24 -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 d00xcQiGfggp for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:23 -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 39D2412B05C for <6man@ietf.org>; Sat, 21 May 2016 18:28:21 -0700 (PDT)
Received: from [152.207.83.17] (unknown [152.207.83.17]) (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 E833C800BC; Sun, 22 May 2016 03:28:06 +0200 (CEST)
Subject: Re: default-iids and stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
References: <573B5FAC.7060300@gont.com.ar> <CAKD1Yr3XUh-t8B_zKz9SPOdsG4Gyf-VhW33zDzb9PSNMo9uXTw@mail.gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <573E5B4F.6030408@gont.com.ar>
Date: Thu, 19 May 2016 20:33:19 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3XUh-t8B_zKz9SPOdsG4Gyf-VhW33zDzb9PSNMo9uXTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/40xIJlIsAZuFrwoEjzazezMAn-w>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 01:28:25 -0000

On 05/17/2016 09:03 PM, Lorenzo Colitti wrote:
> 
> In its current state, draft-default-iids still says that:
> 
>   * For every prefix, every host SHOULD configure addresses that never
>     change - permanently, until the end of time.

We noted a lot of times that that is not the case. Could you please
quote the text in default-iids that requires this?

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Sat May 21 18:28:32 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 B781112D5D7 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:31 -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 VX5Oc2QccBik for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:28 -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 9D5BB12D5D1 for <ipv6@ietf.org>; Sat, 21 May 2016 18:28:27 -0700 (PDT)
Received: from [152.207.83.17] (unknown [152.207.83.17]) (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 CB001803E3; Sun, 22 May 2016 03:28:22 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Alissa Cooper <alissa@cooperw.in>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <573E5C54.6040504@si6networks.com>
Date: Thu, 19 May 2016 20:37:40 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KTqGNoIr9COO0J_58FkSosnI82o>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <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: Sun, 22 May 2016 01:28:32 -0000

On 05/19/2016 02:10 AM, Lorenzo Colitti wrote:
> On Thu, May 19, 2016 at 2:19 PM, Alissa Cooper <alissa@cooperw.in
> <mailto:alissa@cooperw.in>> wrote:
> 
>     The draft makes just about a clear a statement in this vein as is
>     possible:
> 
>     "By default, nodes SHOULD NOT employ IPv6 address generation schemes
>        that embed the underlying link-layer address in the IID.â€�
> 
>     Note that this statement does not prohibit anything, nor does it
>     make a normative (in the moral sense) judgment. It just states the
>     recommendation, which is the point of the document.
> 
>     I appreciate that not everyone on the list agrees with this
>     recommendation. But I find the claim that this recommendation is
>     unclear to be difficult to understand. That is, I canâ€™t think of a
>     way to convey the same recommendation that would be clearer. If you
>     can, please suggest text.
> 
> 
> Alissa,
> 
> I don't think anybody is claiming that the recommendation itself is
> difficult to understand. What is difficult to understand is how the
> document justifies that claim.
> 
> It looks like the main argument used to justify this recommendation is
> major privacy risks. But embedding a link layer identifier into an IP
> address is not a major [1] privacy risk. It is only embedding a *STABLE*
> link-layer address that is a major privacy risk.
> 
> Recommending that link-layer address be embedded only if they are
> ephemeral would address the privacy concerns just as well as (or maybe
> even better) than the approach proposed in this document.
> 
> I think what people are do not understand is why this document
> recommends one but not the other. I certainly don't.
> 
> Cheers,
> Lorenzo
> 
> [1] I argue that cross-referencing IPX traffic to IP traffic is not a
> major privacy risk because IPX is so uncommon.

1) Do you have data to back the claim that such traffic is uncommon?

2) As noted by Brian, this was just an example. You cannot tell e.g.
what other protocols will do in the future, where they might also embed
the same link-layer address, etc.

3) Your approach wastes 18 bits of entropy for no reason. RFC7217 doesn't

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





From nobody Sat May 21 18:28:59 2016
Return-Path: <fernando@gont.com.ar>
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 EE67012D5D3 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:56 -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 uzy6A6LJDCP5 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:28:56 -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 1560B12B05C for <ipv6@ietf.org>; Sat, 21 May 2016 18:28:56 -0700 (PDT)
Received: from [152.207.83.17] (unknown [152.207.83.17]) (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 5B8B9800BC; Sun, 22 May 2016 03:28:43 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <573F947E.7020108@gont.com.ar>
Date: Fri, 20 May 2016 18:49:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_GrvPvjIH_bflJX2c-Bgxp65L1Q>
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: Sun, 22 May 2016 01:28:58 -0000

On 05/20/2016 02:19 AM, Lorenzo Colitti wrote:
> On Fri, May 20, 2016 at 11:18 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     > Let's all always keep in mind that the current text of the draft says that
>     > on every network, hosts SHOULD configure an IPv6 address that never changes
>     > until the end of time. I think that recommendation is irresponsible.
> 
>     Thus, I'm continuing to run my laptop with only an RFC4941 address
>     for a few
>     days to see whether it has any negative impact at all. So far, so good.
> 
> 
> Excellent! Now, if we can only make this draft stop saying that that you
> SHOULD NOT do that...  :-)

This draft does not say and never say that. Please stop saying that, or
quote the offending text, such that we remove it, and we can make progress.

Ok?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Sat May 21 18:29:17 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 4FE9212D5CC for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:29:16 -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 fH-c0empP44H for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:29:15 -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 8840212D5C8 for <ipv6@ietf.org>; Sat, 21 May 2016 18:29:15 -0700 (PDT)
Received: from [152.207.83.17] (unknown [152.207.83.17]) (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 29DF0800BC; Sun, 22 May 2016 03:29:00 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57407BBB.4030804@si6networks.com>
Date: Sat, 21 May 2016 11:16:11 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <a65c2157-044e-6207-314e-833313e5d458@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/foS6eTabjV5bno8p8KXaQGhdrgE>
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: Sun, 22 May 2016 01:29:16 -0000

On 05/19/2016 10:18 PM, Brian E Carpenter wrote:
> On 20/05/2016 12:48, Lorenzo Colitti wrote:
> ...
>> Let's all always keep in mind that the current text of the draft says that
>> on every network, hosts SHOULD configure an IPv6 address that never changes
>> until the end of time. I think that recommendation is irresponsible.
> 
> Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
> days to see whether it has any negative impact at all. So far, so good.

This is a key test: Open a bunch of ssh sessions, and check if they
break overnight.

RFC4941 would make them break. That's an interoperability problem that,
in the general case, you don't want to have, I think.

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





From nobody Sat May 21 18:49:09 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 E290112D0F7 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 Vz19rsU8TFh2 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 18:49:06 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::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 1A8C812B011 for <ipv6@ietf.org>; Sat, 21 May 2016 18:49:06 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id r140so8220521vkf.0 for <ipv6@ietf.org>; Sat, 21 May 2016 18:49:06 -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=aidl7Foga4BFBy3Yo4c8nkA3oXtRQpFZugqnEnjPptc=; b=UJ191xkzOzpys3H3UagPXGZmLu5gq1R4SBUkCmaauK861W6EaIwoo3eaUPe4kpDCOD tmE/qOJ7+ObfZjklRjERuNfSly9GNfOciyq9uPEuXn1D0UbC/Vup6HW9PM+5pzF4mWcH G+i2th69jvLBJUb3X2WWUqvbReBGSOGZeZ0GP91i46g4bo6RAEPJ5VG6P5DlXipFkL28 rVgruku50J28qwDq74lI1TeRXThgf2J74TkfYBtqyS+ic50+uxvDdR14YbDqIoWRAcMh huvukeMBOb0aqzUuRAc+c4bXQAbBORGRU9xXk0r/Qo7XTiNzgsP25na1qeeKSGeaylsC w9ag==
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=aidl7Foga4BFBy3Yo4c8nkA3oXtRQpFZugqnEnjPptc=; b=dUADDsrL67mw0/p2J+HJ+oED+bDtpmPkqUKp9IBIcuQTGIw9uF7EK0hbpCOctcdUB2 u5fu5fttOEbsUtAvWhxJxINhyGL75a47SDPjxYD+Nal73xiKbv6/ixkM4l6g6rUIScvV yRdHw9w+y8zvPvQBA7bbgYx8nXqm0YweLCOawDOz3sxqrn5OAH6TahL7gybPS1W3o3Mb ZbI5DbtYYsA9tNj3/Cz8S/78RohxItUlZyTaXaNUVi9lavYrMCK1qtZS7giT9hjG3I9g HYSOzx/umZB6KBIOAdORSmSV0rVmRdqiUkTYm6VA5NFS5R9vzSsPSldx7U9moZgWfHbM z5Zw==
X-Gm-Message-State: AOPr4FX6DsBiivZ4fNGq/rHHRVnHIWu2Q4rn4XSxa3iJZfsvfmnLWO9VS2i15ubRCaMcoKzivItLyLFKmuImjg==
X-Received: by 10.159.53.42 with SMTP id o39mr6094626uao.133.1463881745185; Sat, 21 May 2016 18:49:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Sat, 21 May 2016 18:48:35 -0700 (PDT)
In-Reply-To: <57407BBB.4030804@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <57407BBB.4030804@si6networks.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 22 May 2016 11:48:35 +1000
Message-ID: <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xQhTcjD4RkU5I6w_09lMQ812Mc4>
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: Sun, 22 May 2016 01:49:08 -0000

On 22 May 2016 at 01:16, Fernando Gont <fgont@si6networks.com> wrote:
> On 05/19/2016 10:18 PM, Brian E Carpenter wrote:
>> On 20/05/2016 12:48, Lorenzo Colitti wrote:
>> ...
>>> Let's all always keep in mind that the current text of the draft says that
>>> on every network, hosts SHOULD configure an IPv6 address that never changes
>>> until the end of time. I think that recommendation is irresponsible.
>>
>> Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
>> days to see whether it has any negative impact at all. So far, so good.
>
> This is a key test: Open a bunch of ssh sessions, and check if they
> break overnight.
>
> RFC4941 would make them break. That's an interoperability problem that,
> in the general case, you don't want to have, I think.
>

I think there would be a lot of very persistent connections (e.g.,
last weeks and months) within Enterprise networks that aren't typical
on the Internet e.g., long lived connections between database clients
and servers, where the database client in this example is part of the
application middle tier.

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
> --------------------------------------------------------------------


From nobody Sat May 21 19:10:53 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 B4A8F12D5D3 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 19:10:51 -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 hD62_SCTNuaN for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 19:10:50 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::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 1D7EF12D0F5 for <ipv6@ietf.org>; Sat, 21 May 2016 19:10:50 -0700 (PDT)
Received: by mail-pa0-x22c.google.com with SMTP id tb2so34291071pac.2 for <ipv6@ietf.org>; Sat, 21 May 2016 19:10:50 -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=Z/3FI+YuujAv6l2sAImKs9ZjZXYcMiVcr/tOnrABeRU=; b=QMKpGkLdG31BtXRrGyURWza3PgKfehJOGe1BdLrKpkFjlFkdeNKC5KEiISAbRo1N0n ZEJGLqvOVI2SwENoWrb8460kZ1Gt8n6unPWR/seUEuaGsa8rFNP7zgBxuf7roJSa6IRw r7PlmEOKuHT9Lsky6px+JX5pmxurdaxqHInDVsD/YBunAwHVyS2eb+8iTXys5n7LJxMG 7d7eI/EP/IHg1a7sB9EK4wusKoxAWq4y4GvjXFVmGDuElCXWJ3ILHtdnOw1o8tvlcGzM CMgWH6Ylm6aROOMYVtNVMFmeE2pwx1X072WZiLciQQj3hqZP/MJLP8LHMVcgsXfO0KKu G7ZQ==
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=Z/3FI+YuujAv6l2sAImKs9ZjZXYcMiVcr/tOnrABeRU=; b=gQjJbiRWYekykCUjSWb1DJX4hoBEs6el3Ld9O2jkqyLXozCaaoOu245dH0115FNCQK rWbDy3rZ0Yhi1GtE6dkfmvwNWbwTe6CGPjpWSbq64YVOVfudAAMUtjR/698EAZw5It/G fjs4vOVfRt+g8cRe9REHS/CyWv3Aft6zv55037s3/I7HlhRjzcBSJrGwqlDC0uO2ahOR v+efdx340JNLpBP9z9thhF5CfOp1CKk5bG5KqkuS7LQ2ElEDU0eNex/o0SKjLEs49BnM iGcgABAe06f67v8dx5m3a3rhmUh94J3ZuJDyffGNlxhFFdH5gfdJaHFkF6cd86GZchnY aa4g==
X-Gm-Message-State: AOPr4FUSluVHjOWoxmwZ9y/n5bGlkCySHyupEpsMrM80qzHPA/E/96yFizabVGoX9mYpNA==
X-Received: by 10.66.142.199 with SMTP id ry7mr16819047pab.14.1463883049537; Sat, 21 May 2016 19:10:49 -0700 (PDT)
Received: from ?IPv6:2406:e007:4c59:1:19dd:39df:fae9:8a1d? ([2406:e007:4c59:1:19dd:39df:fae9:8a1d]) by smtp.gmail.com with ESMTPSA id zj2sm2506348pac.6.2016.05.21.19.10.46 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 21 May 2016 19:10:48 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Mark Smith <markzzzsmith@gmail.com>, Fernando Gont <fgont@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <57407BBB.4030804@si6networks.com> <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ff4732bc-704a-8ae7-90fe-28b7722017aa@gmail.com>
Date: Sun, 22 May 2016 14:10:44 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/m3fjqFHzxbIVJcK-XN315k86ohA>
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: Sun, 22 May 2016 02:10:52 -0000

On 22/05/2016 13:48, Mark Smith wrote:
> On 22 May 2016 at 01:16, Fernando Gont <fgont@si6networks.com> wrote:
>> On 05/19/2016 10:18 PM, Brian E Carpenter wrote:
>>> On 20/05/2016 12:48, Lorenzo Colitti wrote:
>>> ...
>>>> Let's all always keep in mind that the current text of the draft says that
>>>> on every network, hosts SHOULD configure an IPv6 address that never changes
>>>> until the end of time. I think that recommendation is irresponsible.
>>>
>>> Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
>>> days to see whether it has any negative impact at all. So far, so good.
>>
>> This is a key test: Open a bunch of ssh sessions, and check if they
>> break overnight.
>>
>> RFC4941 would make them break. That's an interoperability problem that,
>> in the general case, you don't want to have, I think.

Well, my SSH sessions seem to time out anyway, because the server end
is unhappy about long sessions with no traffic. Look, it all depends on
the user scenario. It's pretty clear that for casual (coffee shop or
such like) use stable addresses are pointless. But for any scenario
with connections that might last for days, it's different.

Anyway, my point is that this is an issue with RFC4941. Since your draft
is an if statement with no else clause:
 if stable_address_wanted
   then RFC7217
issues in RFC4941 are out of scope.

>>
> 
> I think there would be a lot of very persistent connections (e.g.,
> last weeks and months) within Enterprise networks that aren't typical
> on the Internet e.g., long lived connections between database clients
> and servers, where the database client in this example is part of the
> application middle tier.

Yes. In that case stable_address_wanted == True.

    Brian


From nobody Sat May 21 21:21:09 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 9AED412D1AE for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 21:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.426
X-Spam-Level: 
X-Spam-Status: No, score=-3.426 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, RP_MATCHES_RCVD=-1.426, 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 voei2yvbrXYr for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 21:21:06 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 45FAD12D1A9 for <ipv6@ietf.org>; Sat, 21 May 2016 21:21:06 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id c127so26940896ywb.1 for <ipv6@ietf.org>; Sat, 21 May 2016 21:21:06 -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=qW5GdMAcFxRpyjHfKZVmXS4oYXMkz6gwi/myvgGGFLU=; b=lDpZhye5tSj/ZQ4F/qUoZGZ1ZWAYkQvc9CAaFJ+y1/IviOgv+kBDs2pdtxc3mOAFkv W754GW481kuuaAHMt/4clwPK1sTOiumsdB5QJzg4xOgdCFhKm702nJGOqiHMX0CRd3sq fT7w5wpAsrZ9b4CsEz4Pj7tw8Y21UDqWYNHngkYykuQAImcKlzhxPw1YCjO99H40rIwu VP3fhic5nyNQRb3MiXe5u24OHt3SUGvlogkuqw+i9QtFNUls0ixtrUj+cRIb2P/z8Iiu poNfeHRtzDtAO/JGHbi2Ody1DU19VShpflZ32kDtztO2ZGQJbeajdYTNBCR4nm0B1MEU M1RA==
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=qW5GdMAcFxRpyjHfKZVmXS4oYXMkz6gwi/myvgGGFLU=; b=SJmL3rTRahjjEevfQrkJAOnRqQk/6excUH8ZAcxcSAy4xF6KFChEJRAKRmD9Z7RRL3 WfyCWILaGhjR58l63nUfVrbTp1comnXYKfoi+qb3hGL2/r05T9D2Us44OtQ3pqLYJtl0 50tYqeSoEfrogzFd8SjvomIeedgjXkXkBQ04Aasp340ABfdQZGBfEK3IxYWgvF6EBkBR uD1ykefIX+6+UZu1bHVVm+IWO1cruBNkJ0ltbthXLTqXNxZtlfPUonenlgandriINhLi JX9nG21JTpNVDF2+j7jNX4wSV85i2F2yKG6ONydnc0jEwNlZmgCMzSCpdDoRgE2iAvTg 98Gw==
X-Gm-Message-State: AOPr4FU8bZMVx7FyjBtjOqpSIOKe6Rvhf145mJSzsz8AflB5BQzVa4sAH9D+xaqHhVmJBPN3TC5P4Bz8BYKq7/iq
X-Received: by 10.129.166.214 with SMTP id d205mr5977110ywh.323.1463890865412;  Sat, 21 May 2016 21:21:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sat, 21 May 2016 21:20:45 -0700 (PDT)
In-Reply-To: <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 22 May 2016 13:20:45 +0900
Message-ID: <CAKD1Yr03rXjj4X6ubVabRPaePSQwWQT7czfvPZDV8wzu5oVfiw@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=94eb2c128e540683a4053366a7ec
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3NL0Eme93zg5jYtbkw2McON6l4Q>
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: Sun, 22 May 2016 04:21:07 -0000

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

On Sat, May 21, 2016 at 1:04 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinm=
ei@wide.ad.jp> wrote:

> I've been unwilling to propose text as I didn't even understand the
> authors' actual intent, but if it's actually that "it says what an
> implementation SHOULD do _iff_ a stable IID is to be generated", I'd
> suggest revising the above paragraph as follows:
>
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.  For example, this document does
>    not change any existing recommendations concerning the use of
>    temporary addresses as specified in [RFC4941], nor do the
>    recommendations apply to cases where the link layer address is not
>    stable (e.g., it is periodically randomized) in the first place,
>    nor does it introduce any new requirements regarding when stable
>    addresses are to be configured.  Thus, the recommendations in this
>    document simply improve the security and privacy properties of
>    stable addresses.
>

+1 to Jinmei's proposed text.

--94eb2c128e540683a4053366a7ec
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 S=
at, May 21, 2016 at 1:04 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jinmei@wide.ad.jp" target=3D"_blank">jinmei@=
wide.ad.jp</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">I&#39;ve=
 been unwilling to propose text as I didn&#39;t even understand the<br>
authors&#39; actual intent, but if it&#39;s actually that &quot;it says wha=
t an<br>
implementation SHOULD do _iff_ a stable IID is to be generated&quot;, I&#39=
;d<br>
suggest revising the above paragraph as follows:<br>
<span class=3D""><br>
=C2=A0 =C2=A0The recommendations in this document apply only in cases where=
<br>
=C2=A0 =C2=A0implementations otherwise would have configured a stable IPv6 =
IID<br>
</span>=C2=A0 =C2=A0containing a link layer address.=C2=A0 For example, thi=
s document does<br>
<span class=3D"">=C2=A0 =C2=A0not change any existing recommendations conce=
rning the use of<br>
</span>=C2=A0 =C2=A0temporary addresses as specified in [RFC4941], nor do t=
he<br>
=C2=A0 =C2=A0recommendations apply to cases where the link layer address is=
 not<br>
=C2=A0 =C2=A0stable (e.g., it is periodically randomized) in the first plac=
e,<br>
<span class=3D"">=C2=A0 =C2=A0nor does it introduce any new requirements re=
garding when stable<br>
=C2=A0 =C2=A0addresses are to be configured.=C2=A0 Thus, the recommendation=
s in this<br>
=C2=A0 =C2=A0document simply improve the security and privacy properties of=
<br>
=C2=A0 =C2=A0stable addresses.<br></span></blockquote><div><br></div><div>+=
1 to Jinmei&#39;s proposed text.=C2=A0</div></div></div></div>

--94eb2c128e540683a4053366a7ec--


From nobody Sat May 21 21:24:21 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 E81F512D1D7 for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 21:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 B9UV1goS9jvy for <ipv6@ietfa.amsl.com>; Sat, 21 May 2016 21:24:18 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 312CA12D141 for <ipv6@ietf.org>; Sat, 21 May 2016 21:24:18 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id c127so26968078ywb.1 for <ipv6@ietf.org>; Sat, 21 May 2016 21:24: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=J2i5EDOqiJUiIoo/X36VDMyy/ML0yj9TNotmv/dCt6I=; b=faJGtW9rjCFKUaUKgslW8IUXZxz7kCk0WpaxYOldq4dhKmaIEMUDBqe1V/u6Vim4Dv UQrc+5PvI7Yn9/Khs7lZmWUi7O+MXsT1fbeBwFebxEdPXn1tCCZMH+xPItpJxmqDgUA3 DSxB2+1SJOFgd4lcLMfP2QpoIYE/by1FxgO/M5gnASnLYkH5bmrQS+lBaQQtpgRUJ9Qm 9C9HicH6Tfmr+Qvk26pKTGcz3wDCZ41LVHXSVm39V0OnFPu31paMkd6DRx5K9mXnrHcV t0lnQBHSIwe6QDbdiASnE9KnG1cT1TacYzru1FiuVn4tyyLzwLoQS0EmWAmhQr+eNu7A nAwg==
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=J2i5EDOqiJUiIoo/X36VDMyy/ML0yj9TNotmv/dCt6I=; b=DBkv59clbynLEwH7iAy9ccP31hXGYs+e2uj81WaRIC7T8hvzKjUFY0j1k2OUXzxplI IraEFxeljtP39iYUm43wI9SEdyzh913hDv9L+Rq12H3TAVDdJ11OStSpJrxgVAf2i19H ytYFeaifSwj09sBIYtoHMaDT/6sP222ZMnekhXmlOtI6/hhcE4wBEz1rrAOu+9JGT6T5 xsKreeYF0Wez4rLIouFrRjAg2jjo1OoERKWyMMzW7pD4Y1hCsFf+MlUQBbIfO2KQhQF5 uREKlo8upC6apEh+wdMU9RpwIW1471IBITfiM6JuYBq0B3HKMXOzQD46Za3QCEcVrlvp 847g==
X-Gm-Message-State: ALyK8tKdJLc8gr6g2QELj3ArXOQNAQ/otk3XMmYisdYyyeI/1rQxiV0G14ubgFqhjlRJuiFNC6JNJdPKpnGgMl+j
X-Received: by 10.129.108.211 with SMTP id h202mr275806ywc.229.1463891057390;  Sat, 21 May 2016 21:24:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sat, 21 May 2016 21:23:56 -0700 (PDT)
In-Reply-To: <573F947E.7020108@gont.com.ar>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <573F947E.7020108@gont.com.ar>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 22 May 2016 13:23:56 +0900
Message-ID: <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Fernando Gont <fernando@gont.com.ar>
Content-Type: multipart/alternative; boundary=001a114da74677c558053366b253
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LbWAELSsi2e_kb_5lbyhmYzzeW8>
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: Sun, 22 May 2016 04:24:20 -0000

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

On Sat, May 21, 2016 at 7:49 AM, Fernando Gont <fernando@gont.com.ar> wrote:

> > Excellent! Now, if we can only make this draft stop saying that that you
> > SHOULD NOT do that...  :-)
>
> This draft does not say and never say that. Please stop saying that, or
> quote the offending text, such that we remove it, and we can make progress.
>

Let me restate it again: the draft says "hosts SHOULD use RFC7217 when they
would otherwise have configured a stable IID". By my reading, that is
equivalent to saying "hosts SHOULD use RFC7217 all the time", because
currently hosts MUST configure stable IIDs all the time.

I already proposed a solution: say that generating a stable IID is OPTIONAL.

--001a114da74677c558053366b253
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 S=
at, May 21, 2016 at 7:49 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fernando@gont.com.ar">fernando@gont.com.ar</a>&gt;</span> wrote:<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"><span class=3D"gmail-">&gt; Excellent! Now, if we can onl=
y make this draft stop saying that that you<br>
&gt; SHOULD NOT do that...=C2=A0 :-)<br>
<br>
</span>This draft does not say and never say that. Please stop saying that,=
 or<br>
quote the offending text, such that we remove it, and we can make progress.=
<br></blockquote><div><br></div><div>Let me restate it again: the draft say=
s &quot;hosts SHOULD use RFC7217 when they would otherwise have configured =
a stable IID&quot;. By my reading, that is equivalent to saying &quot;hosts=
 SHOULD use RFC7217 all the time&quot;, because currently hosts MUST config=
ure stable IIDs all the time.</div><div><br></div><div><div>I already propo=
sed a solution: say that generating a stable IID is OPTIONAL.</div></div></=
div></div></div>

--001a114da74677c558053366b253--


From nobody Sun May 22 12:17:40 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 E9DE612D0A6 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:17:38 -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 B0jHpNxYUA0Y for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:17:37 -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 BA66212D55E for <ipv6@ietf.org>; Sun, 22 May 2016 12:17:37 -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 u4MJHawc041566; Sun, 22 May 2016 12:17:36 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4MJHVPB041458 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Sun, 22 May 2016 12:17:31 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sun, 22 May 2016 12:17:30 -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; Sun, 22 May 2016 12:17:30 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Topic: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Thread-Index: AQHRsung0w2Prv3/LkGZ3J1oRnnpZJ/E0wcAgACAO5A=
Date: Sun, 22 May 2016 19:17:30 +0000
Message-ID: <af6efe99c9d640e3a866d1257002c645@XCH15-06-11.nw.nos.boeing.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <573F947E.7020108@gont.com.ar> <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
In-Reply-To: <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@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
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: <http://mailarchive.ietf.org/arch/msg/ipv6/ebWYcl4qqItA-s44UEsgDC0orRs>
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: Sun, 22 May 2016 19:17:39 -0000

RnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIExv
cmVuem8gQ29saXR0aQ0KDQo+IExldCBtZSByZXN0YXRlIGl0IGFnYWluOiB0aGUgZHJhZnQgc2F5
cyAiaG9zdHMgU0hPVUxEIHVzZSBSRkM3MjE3IHdoZW4NCj4gdGhleSB3b3VsZCBvdGhlcndpc2Ug
aGF2ZSBjb25maWd1cmVkIGEgc3RhYmxlIElJRCIuIEJ5IG15IHJlYWRpbmcsDQo+IHRoYXQgaXMg
ZXF1aXZhbGVudCB0byBzYXlpbmcgImhvc3RzIFNIT1VMRCB1c2UgUkZDNzIxNyBhbGwgdGhlIHRp
bWUiLA0KPiBiZWNhdXNlIGN1cnJlbnRseSBob3N0cyBNVVNUIGNvbmZpZ3VyZSBzdGFibGUgSUlE
cyBhbGwgdGhlIHRpbWUuDQoNClRoYXQncyBub3Qgc3RhdGVkIGluIHRoaXMgZHJhZnQsIHRob3Vn
aC4gVGhpcyBkcmFmdCBvbmx5IGFwcGxpZXMgdG8gaG9zdHMgd2hpY2ggbXVzdCB1c2Ugc3RhYmxl
IGFkZHJlc3Nlcy4gSXQgZG9lc24ndCB0YWxrIGFib3V0IGFueXRoaW5nIGVsc2UuIEFzIGEgbWF0
dGVyIG9mIGZhY3QsIHRoZSB1c2Ugb2Ygc3RhYmxlIGFkZHJlc3NlcyBoYXMgYWxyZWFkeSBiZWVu
IGRlLWVtcGhhc2l6ZWQgaW4gdGhpcyBkcmFmdCwgYnkgdGhpcyB0ZXh0Og0KDQogICBGdXJ0aGVy
bW9yZSwgc29tZSBwb3B1bGFyIElQdjYgaW1wbGVtZW50YXRpb25zIGhhdmUgYWxyZWFkeSBkZXZp
YXRlZA0KICAgZnJvbSB0aGUgdHJhZGl0aW9uYWwgc3RhYmxlIElJRCBnZW5lcmF0aW9uIHNjaGVt
ZSB0byBtaXRpZ2F0ZSB0aGUNCiAgIGFmb3JlbWVudGlvbmVkIHNlY3VyaXR5IGFuZCBwcml2YWN5
IGltcGxpY2F0aW9ucyBbTWljcm9zb2Z0XS4NCg0KICAgQXMgYSByZXN1bHQgb2YgdGhlIGFmb3Jl
bWVudGlvbmVkIGlzc3VlcywgdGhpcyBkb2N1bWVudCBjaGFuZ2VzIHRoZQ0KICAgZGVmYXVsdCBJ
SUQgZ2VuZXJhdGlvbiBzY2hlbWUgZm9yIFNMQUFDIHRvIHRoYXQgc3BlY2lmaWVkIGluDQogICBb
UkZDNzIxN10sIGFuZCByZWNvbW1lbmRzIGFnYWluc3QgZW1iZWRkaW5nIGxpbmstbGF5ZXIgYWRk
cmVzc2VzIGluDQogICBJUHY2IEludGVyZmFjZSBJZGVudGlmaWVycywgc3VjaCB0aGF0IHRoZSBh
Zm9yZW1lbnRpb25lZCBpc3N1ZXMgYXJlDQogICBtaXRpZ2F0ZWQuICBUaGF0IGlzLCB0aGlzIGRv
Y3VtZW50IHNpbXBseSByZXBsYWNlcyB0aGUgZGVmYXVsdA0KICAgYWxnb3JpdGhtIHRoYXQgbXVz
dCBiZSBlbXBsb3llZCB3aGVuIGdlbmVyYXRpbmcgc3RhYmxlIElQdjYgSUlEcy4NCg0KU28gdGhp
cyB0YW5nZW50aWFsIGRpc2N1c3Npb24sIGEgInNpZGUgYmFyIiB3cnQgdGhpcyBkcmFmdCwgc2hv
dWxkIGJlIGxlZnQgYXQgdGhhdCwgYXMgZmFyIGFzIEknbSBjb25jZXJuZWQuDQoNCj4gSSBhbHJl
YWR5IHByb3Bvc2VkIGEgc29sdXRpb246IHNheSB0aGF0IGdlbmVyYXRpbmcgYSBzdGFibGUgSUlE
IGlzDQo+IE9QVElPTkFMLg0KDQpUaGF0IHBvaW50IHNob3VsZCBiZSBtYWRlLCBpZiBhbnl3aGVy
ZSBhdCBhbGwsIGluIFJGQyAyNDYwLWJpcy4gTm90IGhlcmUuIFdoeSBub3QgaGVyZT8gQmVjYXVz
ZSB0aG9zZSB3aG8gcmVhZCB0aGlzIGRyYWZ0IGNvdWxkbid0IGNhcmUgbGVzcy4gVGhleSBhcmUg
cmVhZGluZyB0aGlzIGRyYWZ0IG9ubHkgYmVjYXVzZSB0aGV5IGtub3cgdGhleSB3YW50IHN0YWJs
ZSBhZGRyZXNzZXMuIFRoYXQgaW50cm9kdWN0b3J5IHBhcmFncmFwaCBzYXlzIGFzIG11Y2ggYXMg
bmVlZHMgdG8gYmUgc2FpZCwgSSB0aGluaywgYWJvdXQgdGhpcyBzaWRlIGJhciBkaXNjdXNzaW9u
Lg0KDQpCZXJ0DQoNCg==


From nobody Sun May 22 12:30:23 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 C44B712D577 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:30:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 VVtAX3dz1XCv for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:30:20 -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 306F712D575 for <ipv6@ietf.org>; Sun, 22 May 2016 12:30:18 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 501AE8017E; Sun, 22 May 2016 21:30:04 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Ole Troan <otroan@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAKD1Yr3uz2ddGArKGh2GGf=pBadx-C-0RG2VhsStSsrPfeqdOQ@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57414555.10909@si6networks.com>
Date: Sun, 22 May 2016 01:36:21 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3uz2ddGArKGh2GGf=pBadx-C-0RG2VhsStSsrPfeqdOQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5et61jhxgyUmnQKVcHAfsjA-mas>
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: Sun, 22 May 2016 19:30:22 -0000

Lorenzo,

On 05/20/2016 03:20 AM, Lorenzo Colitti wrote:
> On Fri, May 20, 2016 at 4:04 PM, <otroan@employees.org
> <mailto:otroan@employees.org>> wrote:
> 
>     > Excellent! Now, if we can only make this draft stop saying that that you SHOULD NOT do that...  :-)
> 
>     Everything has to be read in context. My reading of this document is
>     that it says what an implementation SHOULD do _iff_ a stable IID is
>     to be generated. It says nothing about what to do if a stable IID is
>     not required.
> 
> 
> On Ethernet, it is always required. The reason is this text:
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.
> 
> Currently, implementations must configure a EUI-64 IID, per RFC 2464
> section 4. Thus, by definition any currently-compliant implementation of
> RFC 2464 "configures a stable IPv6 IID", all the time. If this document
> becomes an RFC, a compliant implementation will thus have to follow the
> recommendations of this document all the time.

Your assessment is kind of correct.

Note, that we noted multiple times that what we try to do with this
document is to improve stable addresses, and that we're not changing any
requirements regarding whether one should configure stable addresses in
the first place.

You're asking this document to do more than what it was meant to do.
That's not a bad thing. But this is not the document to blame for the
"requirement to configure stable addresses". If anything, we're just
relaying the requirement that's in RFC2464 and RFC4941.



> If we want to clarify this, then I propose this text:
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address. Configuring a stable IPv6 IID is
>    OPTIONAL.

I'm not necessarily opposed to your text. Actually, I think making
stable addresses optional could be a good thing for scenarios (e.g.,
roaming/coffee store) where you might live without them.

However, please note this is a different change from the one we have
been pursuing with this document. I'm not saying that I'm opposed to the
change, nor that I'm opposed to "augment" this I-D to relax the
requirement regarding stable address. I'm just saying that this I-D was
not meant to do that.

I guess a document that gets rid off stable addresses should analyze the
tradeoffs involved, and the possible implications. e.g., relying on
temp-only could make long-lived ssh connections fail, and a requirement
of "OPTIONAL" would mean that that's just fine.

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





From nobody Sun May 22 12:30:35 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 915D312D57D for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.852
X-Spam-Level: 
X-Spam-Status: No, score=-0.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, 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 Npxl3paJln6y for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:30:26 -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 B3F3112D57C for <ipv6@ietf.org>; Sun, 22 May 2016 12:30:26 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 39A1280D8B; Sun, 22 May 2016 21:30:19 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: otroan@employees.org, Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5741460A.5040304@si6networks.com>
Date: Sun, 22 May 2016 01:39:22 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aggBXifv8Z_AORc1LdHzNIoefq0>
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: Sun, 22 May 2016 19:30:27 -0000

On 05/20/2016 03:04 AM, otroan@employees.org wrote:
>>> Let's all always keep in mind that the current text of the draft
>>> says that on every network, hosts SHOULD configure an IPv6
>>> address that never changes until the end of time. I think that
>>> recommendation is irresponsible.
>> 
>> Thus, I'm continuing to run my laptop with only an RFC4941 address
>> for a few days to see whether it has any negative impact at all. So
>> far, so good.
>> 
>> Excellent! Now, if we can only make this draft stop saying that
>> that you SHOULD NOT do that...  :-)
> 
> Everything has to be read in context. My reading of this document is
> that it says what an implementation SHOULD do _iff_ a stable IID is
> to be generated. It says nothing about what to do if a stable IID is
> not required.
> 
> I find the current text quite clear on that, but clearly you don't. 
> Would it help with some sort of clearer applicability statement in
> this document? Can you propose text?

It turns out that Lorenzo wants this I-D to make an additional change:
flag stable addresses as optional. Currently, such a change is out of
the scope for this document.

I'm not saying that this dcument should not make that change or the
like... but rather noting that Lorenzo concern is not really about what
this document is meant to do (improve stable addresses *if* you're going
to configure one).

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





From nobody Sun May 22 12:31:30 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 B3E8312D577 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:31:29 -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 Po5rVLkXibjz for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:31:28 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 7C40812D0A6 for <ipv6@ietf.org>; Sun, 22 May 2016 12:31:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4MJVSH0020304; Sun, 22 May 2016 12:31:28 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4MJVOWU019929 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Sun, 22 May 2016 12:31:24 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sun, 22 May 2016 12:31:23 -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; Sun, 22 May 2016 12:31:23 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: RE: default-iids: Clarifying the use of stable addresses
Thread-Topic: default-iids: Clarifying the use of stable addresses
Thread-Index: AQHRs0jLxj/v0dfn8kaK3QK+z/oQZ5/EiBWAgADQSrA=
Date: Sun, 22 May 2016 19:31:23 +0000
Message-ID: <3c68ee5b9ff748c8bddcff7ad8ed7a31@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <ce73a827-a137-eab3-3b1e-9e4895d9b6bd@gmail.com> <CAO42Z2yg9pGFrzf69LHAhKxrZ0dOH3=FUP0k3ZjeGN8dMp3Xww@mail.gmail.com>
In-Reply-To: <CAO42Z2yg9pGFrzf69LHAhKxrZ0dOH3=FUP0k3ZjeGN8dMp3Xww@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
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: <http://mailarchive.ietf.org/arch/msg/ipv6/x1_pdNiRuRJHBfEskGQURBmXBqg>
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: Sun, 22 May 2016 19:31:30 -0000

LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlwdjYgW21haWx0bzppcHY2LWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYXJrIFNtaXRoDQoNCj4gVGhlIHJvbGVzIG9mICdj
bGllbnQnIG9yICdzZXJ2ZXInIGFyZSBhcHBsaWNhdGlvbiBsYXllciBjb25jZXB0cy4NCj4gSXQg
aXMgb25seSBJUHY0IE5BVCB0aGF0IGhhcyBjcmVhdGVkIHRoZSByZXF1aXJlbWVudCB0byBjb25z
aWRlcg0KPiBkZXZpY2VzIGF0IHRoZSBuZXR3b3JrIGxheWVyIHRvIGJlICdjbGllbnRzJyBvciAn
c2VydmVycycuIEFzIHdlDQo+IGRvbid0IG5lZWQgdG8gZG8gTkFUIGluIElQdjYsIHdlIGRvbid0
IG5lZWQgdG8gYm90aCBjbGFzc2lmeSBhbmQNCj4gY29uc3RyYWluIG91cnNlbHZlcyB0byB0aGlu
a2luZyBvZiBkZXZpY2VzIGFzIGV4Y2x1c2l2ZWx5IGJlaW5nDQo+IG9ubHkgb25lIG9mIGVpdGhl
ciBhICdjbGllbnQnIG9yIGEgJ3NlcnZlcicuDQoNCkV4Y2VwdCB0aGF0IE5BVCBhbHNvIGV4aXN0
cyB3aXRoIElQdjYsIGFuZCB0aGF0IHN0YWJsZSBhZGRyZXNzZXMgYXJlIG5pY2UgdG8gaGF2ZSBm
b3IgSVB2NiBzZXJ2ZXJzIGFueXdheSwgZXZlbiB3aXRob3V0IHVzaW5nIE5BVC4gQW5kIGZvciBv
dGhlciB0eXBlcyBvZiBuZXR3b3JrcyB0aGFuIHRoZSBwdWJsaWMgSW50ZXJuZXQuIEUuZy4sIHNv
bWUgbmV0d29ya3MgYXJlIHBlZXItcGVlciBuZXRzLCBzYW5zIEROUy4gVGhleSBhbHNvIHdhbnQg
c3RhYmxlIGFkZHJlc3Nlcy4NCg0KQmVydA0KDQo=


From nobody Sun May 22 12:41:04 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 8F0F512D119 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41: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, 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 eD5I77wrlVhp for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41:01 -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 C8EB312D0A6 for <6man@ietf.org>; Sun, 22 May 2016 12:41:00 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 A0402809E2; Sun, 22 May 2016 21:40:52 +0200 (CEST)
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Lorenzo Colitti <lorenzo@google.com>, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57420ADB.1040203@si6networks.com>
Date: Sun, 22 May 2016 15:39:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Robagk4vCI3oRsbZ5N87ZLvVh4s>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 19:41:02 -0000

On 05/20/2016 11:23 PM, Lorenzo Colitti wrote:
> On Sat, May 21, 2016 at 11:15 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>> wrote:
> 
>     > The combination of #1 and #2 means that an implementation that does not choose to use a stable IID can legitimately form whatever IID it so chooses.
> 
>     Well, again, that's out of scope. This draft should not be used for
>     guidance concerning non-stable addresses, so why is this continuing
>     to be such a bone of contention? It seems like all the additional
>     text being proposed has to do with things that don’t relate to this
>     draft at all. Then, don't use this draft!
> 
> 
> All I'm saying is that if we publish this draft, then the formation of
> IPv6 IIDs on many link layers, including ethernet and wifi, becomes
> completely unspecified, and implementations (well - implementations that
> don't want to use stable IIDs) can do whatever they want with no
> recommendations or guidance from the IETF.

Huh?

Right now you have specs for stable adresses and RFC4941. This I-D
simply improves how you generate stable addresses. WHerever you'd embed
a link-layer id, you use RFC7217. That's it.

Where's the lack of guidance??

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





From nobody Sun May 22 12:41:15 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 7D81912D592 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41:13 -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 zfbYdMrjU1u5 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 12:41:08 -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 4591D12D583 for <ipv6@ietf.org>; Sun, 22 May 2016 12:41:08 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 B4FAD80A53; Sun, 22 May 2016 21:41:03 +0200 (CEST)
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Alissa Cooper <alissa@cooperw.in>, IETF IPv6 Mailing List <ipv6@ietf.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57420B44.6080209@si6networks.com>
Date: Sun, 22 May 2016 15:40:52 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EPDUeCfhD8y0ZIKrKTcNH_1yHbs>
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, 22 May 2016 19:41:13 -0000

On 05/20/2016 05:06 PM, Alissa Cooper wrote:
> 
>> On May 18, 2016, at 1:26 AM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>> What if we dropped requirement #1 in Section 3, but left the rest the same? This would open the door such that people who wanted to comply with the SHOULD-level recommendation in this spec in the presence of randomized MAC addresses still could (e.g., by implementing 7217 and using the randomized MAC as the Net_Iface parameter), but directly embedding a MAC address in the IID would still go against the SHOULD NOT recommendation here.
> 
> I donâ€™t think I saw anyone respond to this suggestion, so Iâ€™d like to ask again for peopleâ€™s opinions about this.
> 
> To my eye this is a nice compromise.

That's a bad idea.

The reason why is  draft-gont-predictable-numeric-ids-00, RFC4941, and
even some RFC (?) by the IAB.

The root of this whole problem is embedding a layer-2 id in a layer-3
field in the first place.

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





From nobody Sun May 22 13:24:22 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 2338812D577 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:20 -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 fWFKFpycKb2u for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:18 -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 6034912B037 for <ipv6@ietf.org>; Sun, 22 May 2016 13:24:18 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 D104C809E2; Sun, 22 May 2016 22:24:12 +0200 (CEST)
Subject: Re: default-iids: Clarifying the use of temporary addresses
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ipv6@ietf.org
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <CAO42Z2xrKpnaXPVfkG7jdpT2Ko1tD6tmZ_k7Xttsw0_jLLq=fA@mail.gmail.com> <02499023-aa6d-3022-3d84-5a2a9f63fcee@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57420D0B.2070405@si6networks.com>
Date: Sun, 22 May 2016 15:48:27 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <02499023-aa6d-3022-3d84-5a2a9f63fcee@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Khf_JO5jwfnKS16or5iD-bzTLIs>
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, 22 May 2016 20:24:20 -0000

On 05/21/2016 01:41 AM, Brian E Carpenter wrote:
> On 21/05/2016 15:29, Mark Smith wrote:
>> On 21 May 2016 at 11:47, Lorenzo Colitti <lorenzo@google.com> wrote:
>>> On Sat, May 21, 2016 at 8:10 AM, Manfredi, Albert E
>>> <albert.e.manfredi@boeing.com> wrote:
>>>>
>>>> The messages in this I-D are already clear.
>>>
>>> I disagree that they were already clear, and I think that something like
>>> Fernando's text will help a lot to clarify them.
>>>
>>> I will note, though, that this draft does the following:
>>>
>>> Deletes the text in RFC 2464 and other documents that defines how the IID is
>>> constructed, and replaces it with a pointer to this draft
>>> Makes it very clear that an implementation that does not choose to use a
>>> stable IID does not need to follow this draft
>>>
>>> The combination of #1 and #2 means that an implementation that does not
>>> choose to use a stable IID can legitimately form whatever IID it so chooses.
>>
>> Which I think is consistent with
>>
>> "Significance of IPv6 Interface Identifiers"
>> https://tools.ietf.org/html/rfc7136
>>
>> (without looking this draft being discussed because I'm about to go
>> out the door, it might be worth referencing that RFC if it usefully
>> supports some of the clarifications made).
> 
> So, reviewing the thread, I think we've been barking up the
> wrong tree to some extent (hence the new subject header above).
> 
> RFC4941 aims to be compatible with SLAAC but it includes this
> near the beginning of the protocol description:
> 
> '  2.  Create additional addresses based on a random interface
>        identifier...'
> 
> In other words it's *explicit* that there is always an existing
> address, which I think we agree is actually completely unnecessary
> for client computers. (It's also at variance with some of the wording
> in RFC4862, which frequently refers to IIDs as 'unique' per interface,
> which can't be right, otherwise RFC4941 simply wouldn't work.)
> 
> So, I think some RFC needs to state that it is legitimate to have a host
> with only RFC4941 global addresses.
> 
> Apart from that I'm quite happy with Lorenzo's comment above. Once
> the IID bits have no semantics, anything goes.

Exactly. So this is not the document to blame for "requiring" stable
addresses. If anything, such requirement comes from elsewhere (e.g.
RFC4941), and *that* "elsewhere" is the document to complain about and
to update.

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





From nobody Sun May 22 13:24:34 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 E26AA12B037 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:21 -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 BvtY1-qLtCGR for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:19 -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 7870B12D1DA for <ipv6@ietf.org>; Sun, 22 May 2016 13:24:19 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 DD8B780A53; Sun, 22 May 2016 22:24:16 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Lorenzo Colitti <lorenzo@google.com>, Fernando Gont <fernando@gont.com.ar>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <573F947E.7020108@gont.com.ar> <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
Message-ID: <57420E50.2050007@si6networks.com>
Date: Sun, 22 May 2016 15:53:52 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3SkDkL3Yxc6nmC5ZbKngt99E=kM4V=qMB7vE-2JQfdgA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Aw15zm6IyP2MGjVKfLr7wp5_Zp0>
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: Sun, 22 May 2016 20:24:22 -0000

On 05/22/2016 12:23 AM, Lorenzo Colitti wrote:
> On Sat, May 21, 2016 at 7:49 AM, Fernando Gont <fernando@gont.com.ar
> <mailto:fernando@gont.com.ar>> wrote:
> 
>     > Excellent! Now, if we can only make this draft stop saying that that you
>     > SHOULD NOT do that...  :-)
> 
>     This draft does not say and never say that. Please stop saying that, or
>     quote the offending text, such that we remove it, and we can make
>     progress.
> 
> 
> Let me restate it again: the draft says "hosts SHOULD use RFC7217 when
> they would otherwise have configured a stable IID". By my reading, that
> is equivalent to saying "hosts SHOULD use RFC7217 all the time", because
> currently hosts MUST configure stable IIDs all the time.
> 
> I already proposed a solution: say that generating a stable IID is OPTIONAL.

This goes beyond what this document was meant to do. BUt if the wg wants
this document to also do that, I'm fine. I guess that if we were to do
that, this document now also needs to update RFC4941, or can we keep it
otherwise "as is"?

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





From nobody Sun May 22 13:24:45 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 71E1412D52A for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:34 -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 Ke996HCDTUMz for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:24 -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 F2AEF12D58F for <ipv6@ietf.org>; Sun, 22 May 2016 13:24:23 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 0B1DD80D8B; Sun, 22 May 2016 22:24:20 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Ole Troan <otroan@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <574210D2.9030903@si6networks.com>
Date: Sun, 22 May 2016 16:04:34 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ufBUJb7aiWG_IFCniZQlFMqhOOA>
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: Sun, 22 May 2016 20:24:34 -0000

Jinmei,

On 05/20/2016 12:04 PM, ç¥žæ˜Žé�”å“‰ wrote:
>>> Thus, I'm continuing to run my laptop with only an RFC4941
>>> address for a few days to see whether it has any negative impact
>>> at all. So far, so good.
>>> 
>>> Excellent! Now, if we can only make this draft stop saying that
>>> that you SHOULD NOT do that...  :-)
>> 
>> Everything has to be read in context. My reading of this document
>> is that it says what an implementation SHOULD do _iff_ a stable IID
>> is to be generated. It says nothing about what to do if a stable
>> IID is not required.
>> 
>> I find the current text quite clear on that, but clearly you
>> don't.
> 
> It's not clear to me either.  I commented on this exact point in my 
> first response to the last call.  Its followup discussion actually 
> confused me further: 
> http://www.ietf.org/mail-archive/web/ipv6/current/msg24391.html
> 
> In this discussion, I suggested "clarifying that this recommendation 
> is only for environments where address stability is needed".

FWIW, that's fine with me (including Lorenzo's suggestion of
"OPTIONAL"). The only thing I tried to note is that saying so goes
beyond the original intent of this ID: we were just improving stable
addresses, without saying any word regarding whether you should use
them, whether they are optional, or whatever.


>  The 
> response to that part of comment refers to a paragraph of the 
> introduction section:
> 
> The recommendations in this document apply only in cases where 
> implementations otherwise would have configured a stable IPv6 IID 
> containing a link layer address.  That is, this document does not 
> change any existing recommendations concerning the use of temporary 
> addresses as specified in [RFC4941], nor does it introduce any new 
> requirements regarding when stable addresses are to be configured. 
> Thus, the recommendations in this document simply improve the 
> security and privacy properties of stable addresses.
> 
> At least to me, this is not the same as "this recommendation is only 
> for environments where address stability is needed".

We were not saying that because the current specs say/assume that they
are always needed, and "changing" that was ging one step further. That
said, I'm not opposed to this document going that step further.


>  So I tried to 
> understand the actual intent with followup questions, but the 
> subsequent discussions only introduced more confusion for me
> (because of discussions on other points like whether using
> randomized link-layer address is "extremely bad").

That's orthogonal. Again, please read:
draft-gont-predictable-numeric-ids-00



>> Would it help with some sort of clearer applicability statement in 
>> this document? Can you propose text?
> 
> I've been unwilling to propose text as I didn't even understand the 
> authors' actual intent, but if it's actually that "it says what an 
> implementation SHOULD do _iff_ a stable IID is to be generated", I'd 
> suggest revising the above paragraph as follows:

Yes, that's the intent of this I-D (but please note my comment above
regarding the *current* specs assumming stable addresses are always there).



> The recommendations in this document apply only in cases where 
> implementations otherwise would have configured a stable IPv6 IID 
> containing a link layer address.  For example, this document does not
> change any existing recommendations concerning the use of temporary
> addresses as specified in [RFC4941], nor do the recommendations apply
> to cases where the link layer address is not stable (e.g., it is
> periodically randomized) in the first place, nor does it introduce
> any new requirements regarding when stable addresses are to be
> configured.

The root of this problem is reusing a link-yaer ID at layer-3. THat's
bad, and we have to recommend against that.

Brian already provided an example of IPv6/IPX traffic correlation... and
there could be other protocols reusing the MAC address which, even if
randomized, allows for correlation.

REusing IDs a different places, ifor different scopes, etc., is bad, and
is the root of all of this. Please check:
draft-gont-predictable-numeric-ids-00



> If the intent of this document is really just that it applies iff a 
> stable IID is to be generated and does not make any judgment on,
> e.g., use of randomized link-layer addresses, this proposed text
> shouldn't be a problem for anyone. 

We don't care about what you do at layer-2. Randomie as much as you
want. Just don't include layer-2 IDs in layer-3 IIDs.



> To be clear, I'm not particularly an advocator of the use of 
> randomized link-layer addresses.

I'm fine with layer-2 adddr randomization. Could even consider myself
and advocator of that (in a number of scenarios). HOwever, I'm against
reusing numeric IDs in different places, for the reasons stated above.

Thughts?

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





From nobody Sun May 22 13:24:48 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 9354F12D5A0 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:44 -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 ozS6APcg-EjQ for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:24:37 -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 73FCF12D59A for <6man@ietf.org>; Sun, 22 May 2016 13:24:29 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 7C7BE809E2; Sun, 22 May 2016 22:24:25 +0200 (CEST)
To: "6man@ietf.org" <6man@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: default-iids: Closing concern regarding stable address requirement
X-Enigmail-Draft-Status: N1110
Message-ID: <5742118B.6020308@si6networks.com>
Date: Sun, 22 May 2016 16:07:39 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XogJ5YkwOH3Ix2bWy2C-mivtDFs>
Cc: "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.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: Sun, 22 May 2016 20:24:44 -0000

Folks,

Lorenzo suggested this text:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address. Configuring a stable IPv6 IID is
   OPTIONAL.


IMHO this goes one step further than what this I-D was meant to do (just
improve stable addresses), but I guess most of us (all?) agree that
there are scenarios where you might want to use e.g. temporary-addresses
*only*.

Is anyone opposed to adding the above text, suggested by Lorenzo?

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





From nobody Sun May 22 13:33:16 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 698E712D562 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:33:14 -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 mNpFZ_2P9k6q for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:33:12 -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 87C7012D177 for <ipv6@ietf.org>; Sun, 22 May 2016 13:33:12 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 CA214809E2; Sun, 22 May 2016 22:24:36 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Mark Smith <markzzzsmith@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <57407BBB.4030804@si6networks.com> <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <574212F2.7030607@si6networks.com>
Date: Sun, 22 May 2016 16:13:38 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/BSuG9bR1-i-XqNc2_V0LdA57PDg>
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: Sun, 22 May 2016 20:33:14 -0000

On 05/21/2016 09:48 PM, Mark Smith wrote:
> On 22 May 2016 at 01:16, Fernando Gont <fgont@si6networks.com> wrote:
>> On 05/19/2016 10:18 PM, Brian E Carpenter wrote:
>>> On 20/05/2016 12:48, Lorenzo Colitti wrote:
>>> ...
>>>> Let's all always keep in mind that the current text of the draft says that
>>>> on every network, hosts SHOULD configure an IPv6 address that never changes
>>>> until the end of time. I think that recommendation is irresponsible.
>>>
>>> Thus, I'm continuing to run my laptop with only an RFC4941 address for a few
>>> days to see whether it has any negative impact at all. So far, so good.
>>
>> This is a key test: Open a bunch of ssh sessions, and check if they
>> break overnight.
>>
>> RFC4941 would make them break. That's an interoperability problem that,
>> in the general case, you don't want to have, I think.
>>
> 
> I think there would be a lot of very persistent connections (e.g.,
> last weeks and months) within Enterprise networks that aren't typical
> on the Internet e.g., long lived connections between database clients
> and servers, where the database client in this example is part of the
> application middle tier.

*Exactly*. S, the question is: can we really flag stable addresses as
optional when such connections might break as a result of that? aybe we
should note that if we flag them as optional?

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





From nobody Sun May 22 13:33: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 70C7512D1B3 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:33:15 -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 BzhT88qLjZMr for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 13:33:14 -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 A1E7812D1DA for <ipv6@ietf.org>; Sun, 22 May 2016 13:33:12 -0700 (PDT)
Received: from [100.68.225.77] (unknown [152.206.104.203]) (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 E19C280D95; Sun, 22 May 2016 22:24:30 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Smith <markzzzsmith@gmail.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <57407BBB.4030804@si6networks.com> <CAO42Z2zVpkZwQkFE0gGZTsS6hPh_=NSbcouzuzeCy=qmGyOamg@mail.gmail.com> <ff4732bc-704a-8ae7-90fe-28b7722017aa@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57421285.6010005@si6networks.com>
Date: Sun, 22 May 2016 16:11:49 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <ff4732bc-704a-8ae7-90fe-28b7722017aa@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/VkJYaZjURwNJ8xAp_-8Kr8M7gJY>
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: Sun, 22 May 2016 20:33:15 -0000

On 05/21/2016 10:10 PM, Brian E Carpenter wrote:
>>>
>>> RFC4941 would make them break. That's an interoperability problem that,
>>> in the general case, you don't want to have, I think.
> 
> Well, my SSH sessions seem to time out anyway, because the server end
> is unhappy about long sessions with no traffic. 

The question is (*question*, not objection) is whether one can really
say that stable addresses are optional when using temp addresses only
might cause w.g., breakage of ssh sessions.


> Look, it all depends on
> the user scenario. It's pretty clear that for casual (coffee shop or
> such like) use stable addresses are pointless. But for any scenario
> with connections that might last for days, it's different.
> 
> Anyway, my point is that this is an issue with RFC4941. Since your draft
> is an if statement with no else clause:
>  if stable_address_wanted
>    then RFC7217
> issues in RFC4941 are out of scope.

*Exactly*!

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 May 22 15:21:50 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 1AC1612D16F for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 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.001, 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 J3hUpNCeevjb for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:21:48 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 BDE6512D100 for <ipv6@ietf.org>; Sun, 22 May 2016 15:21:47 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id f66so202392066vkh.2 for <ipv6@ietf.org>; Sun, 22 May 2016 15:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=zKzVqPJ8Zn8plCrFnd+8GZwY1BoIzA4SB5QB4XbXAtk=; b=K3YvbZJkoZBwcF0opWoftWIh4ub6OifXDgz2yPVooWfyWn/QQGNEgBGyTnARbT0DAb rYRl8L5pAz2lk+NHlp5Q206ERIlCNHx2snbzvTAlT4UYM5Zd6JDsIcdg085sbo0VgjhZ JSZMpmSwnT+kjUAFzMJNfuy/UK2h0OvaWNXOxfXh7TA/dlUeaqniOSQOgGK9/VATJ0tf 6LdjNA75mxXZR+l2XXeL5noAtNAfk0925oL68fGi5tECcz7LwIBYk0GJqLaxSjojcKwx gdgp68llbzgtyve068cS0caBjg+kYYYB8ifKbkoLj7kchYLQcvVatKfP8LwDsqKGUhV4 y0DQ==
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:date :message-id:subject:from:to:cc; bh=zKzVqPJ8Zn8plCrFnd+8GZwY1BoIzA4SB5QB4XbXAtk=; b=josCGnjP3Rs+ysNweNLBWm9tVCvMCSn8O4Yn6WKNFHmw8/WHoQj4Alnl6MOygnAPre VdsT9Z+rHO9xaRQ8u1GR/TJ+jHncFD7xn6dVmYQtSG/BBBzU0f2oTqYTxIoyD4imXoPX PSIxLEsZwItvF2WuL2TRG2567a18ZrDT3/WtHIgdk0rOGhX4sOI8wnwdiWsGO31YGgMB TyLWHeKk7QonOq7cBiAe41LW+J9h9Mmi3Qg2QtEdWt8ZA88lQKFJiSNSL6oYxeVt3SNR dHNBhLKWEDAbsF1cRqwHXB/bHaCykxjng8gldB2YxlQTfJV3nE2GiWk0MbKbTWZhgegG 1GYA==
X-Gm-Message-State: AOPr4FV+/D2B7ATk9lC8v8cKRVAYSeSQvxhlyz6mHONMDU356AG3q7EGPbWSZvVLQolBAuhoyinTQVClXxfYYQ==
MIME-Version: 1.0
X-Received: by 10.159.37.100 with SMTP id 91mr7041231uaz.67.1463955706653; Sun, 22 May 2016 15:21:46 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 22 May 2016 15:21:46 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 22 May 2016 15:21:46 -0700 (PDT)
In-Reply-To: <CAO42Z2wtpns24PW2P0-TayEWcB1ar2Ez8a997Sf-vvin8z3fMQ@mail.gmail.com>
References: <573F3F49.9090107@si6networks.com> <ce73a827-a137-eab3-3b1e-9e4895d9b6bd@gmail.com> <CAO42Z2yg9pGFrzf69LHAhKxrZ0dOH3=FUP0k3ZjeGN8dMp3Xww@mail.gmail.com> <3c68ee5b9ff748c8bddcff7ad8ed7a31@XCH15-06-11.nw.nos.boeing.com> <CAO42Z2wtpns24PW2P0-TayEWcB1ar2Ez8a997Sf-vvin8z3fMQ@mail.gmail.com>
Date: Mon, 23 May 2016 08:21:46 +1000
Message-ID: <CAO42Z2wfbRPsZqwRFfkeUw6ZoNqXMoUyr5-4D4GXkkYfgStnWQ@mail.gmail.com>
Subject: RE: default-iids: Clarifying the use of stable addresses
From: Mark Smith <markzzzsmith@gmail.com>
To: Albert E Manfredi <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=94eb2c122da4dcb25f053375bfca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9iPGRzuhdeZhqfHtrP2GEV7KQAc>
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: Sun, 22 May 2016 22:21:49 -0000

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

On 23 May 2016 5:31 AM, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
wrote:
>
> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Mark Smith
>
> > The roles of 'client' or 'server' are application layer concepts.
> > It is only IPv4 NAT that has created the requirement to consider
> > devices at the network layer to be 'clients' or 'servers'. As we
> > don't need to do NAT in IPv6, we don't need to both classify and
> > constrain ourselves to thinking of devices as exclusively being
> > only one of either a 'client' or a 'server'.
>
> Except that NAT also exists with IPv6,

So it is experimental.

The terms ''client' and 'server' don't exist in RFC2460 nor RFC791, so
there are no such roles in these protocols. Hosts are only packet senders
or receivers to or from their network layer peers.

I'm not arguing against stable addresses. I see use cases relevant to me
for temporary only (my smart phone), temporary + stable (my tower PC at
home that I use as both a client and a server for different apps) and
stable only (routers that I need to login to to administer and whose
interface addresses are used by hosts and other routers).

I think the mistake Lorenzo might be making is confusing stable with
permanent and unchangeable "to the end of time".

RFC7217 addresses are not permanent. An operator can cause one to change at
any time, by reinitialising the algorithm with a different secret key or
other parameters that will cause the IID to change. A fresh OS install will
cause new ones to be generated. The computer itself will be replaced at
some point, and that should cause new RFC7217s to be generated.

A virtual machine will be able to persist in operation much longer than
hardware, however at some point its operating system and software is likely
to become obsolete and replaced. If that possible time span is too long,  a
policy of generating new addresses every 5 years could be put in place.

MAC addresses are permanent, as they're burnt into the card. Yet how many
permanent MAC addresses from the NICs in the 2000s, 1990s or earlier would
be in use today? Permanence in computing isn't very permanent.

I think very few RFC7217 addresses will exist for any longer than 10 years.
The few that do can be easily changed if necessary, for the use cases where
stable addresses are necessary or desirable.

Regards,
Mark.

> Bert
>

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

<p dir=3D"ltr"><br>
On 23 May 2016 5:31 AM, &quot;Manfredi, Albert E&quot; &lt;<a href=3D"mailt=
o:albert.e.manfredi@boeing.com">albert.e.manfredi@boeing.com</a>&gt; wrote:=
<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: ipv6 [mailto:<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounc=
es@ietf.org</a>] On Behalf Of Mark Smith<br>
&gt;<br>
&gt; &gt; The roles of &#39;client&#39; or &#39;server&#39; are application=
 layer concepts.<br>
&gt; &gt; It is only IPv4 NAT that has created the requirement to consider<=
br>
&gt; &gt; devices at the network layer to be &#39;clients&#39; or &#39;serv=
ers&#39;. As we<br>
&gt; &gt; don&#39;t need to do NAT in IPv6, we don&#39;t need to both class=
ify and<br>
&gt; &gt; constrain ourselves to thinking of devices as exclusively being<b=
r>
&gt; &gt; only one of either a &#39;client&#39; or a &#39;server&#39;.<br>
&gt;<br>
&gt; Except that NAT also exists with IPv6,</p>
<p dir=3D"ltr">So it is experimental.</p>
<p dir=3D"ltr">The terms &#39;&#39;client&#39; and &#39;server&#39; don&#39=
;t exist in RFC2460 nor RFC791, so there are no such roles in these protoco=
ls. Hosts are only packet senders or receivers to or from their network lay=
er peers.<br></p>
<p dir=3D"ltr">I&#39;m not arguing against stable addresses. I see use case=
s relevant to me for temporary only (my smart phone), temporary + stable (m=
y tower PC at home that I use as both a client and a server for different a=
pps) and stable only (routers that I need to login to to administer and who=
se interface addresses are used by hosts and other routers).</p>
<p dir=3D"ltr">I think the mistake Lorenzo might be making is confusing sta=
ble with permanent and unchangeable &quot;to the end of time&quot;.</p>
<p dir=3D"ltr">RFC7217 addresses are not permanent. An operator can cause o=
ne to change at any time, by reinitialising the algorithm with a different =
secret key or other parameters that will cause the IID to change. A fresh O=
S install will cause new ones to be generated. The computer itself will be =
replaced at some point, and that should cause new RFC7217s to be generated.=
</p>
<p dir=3D"ltr">A virtual machine will be able to persist in operation much =
longer than hardware, however at some point its operating system and softwa=
re is likely to become obsolete and replaced. If that possible time span is=
 too long,=C2=A0 a policy of generating new addresses every 5 years could b=
e put in place.</p>
<p dir=3D"ltr">MAC addresses are permanent, as they&#39;re burnt into the c=
ard. Yet how many permanent MAC addresses from the NICs in the 2000s, 1990s=
 or earlier would be in use today? Permanence in computing isn&#39;t very p=
ermanent.</p>
<p dir=3D"ltr">I think very few RFC7217 addresses will exist for any longer=
 than 10 years. The few that do can be easily changed if necessary, for the=
 use cases where stable addresses are necessary or desirable.</p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; Bert<br>
&gt;<br>
</p>

--94eb2c122da4dcb25f053375bfca--


From nobody Sun May 22 15:27:52 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 0C98B12D5DC for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level: 
X-Spam-Status: No, score=-1.497 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.001, 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 QgBnYdoW6nAU for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:27:49 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 B337512D500 for <6man@ietf.org>; Sun, 22 May 2016 15:27:49 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id c189so202481589vkb.1 for <6man@ietf.org>; Sun, 22 May 2016 15:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=63t4U6UW7JBCdegpfD/vzR++9OiGf7WTs7j5i8ImwYI=; b=LfvlVbtCEWf4beYuAJ+D3FVvceIR7yJg9mNyBi/zoqzwJK+ugpoOZP7D9dhgCYO0a6 kLyS0ytEa1IFYJHXdUt1Mcy+p0LlpOV++bQAPele/OgaU58SmCTfxJRxbg7SxCOBNVC5 ltSJwqkj+pBZhB6qMPxM7qgP4U3lhCqKQLuDNYjQz/h0JBg+zVh9xDvgn2ez/7bQ86w/ +1/xrZsejNNwXOOqbv5jDq9N7jkeDqpPMRLtPSE/OZxKa898kCaXO74w5DjL08+aRjcg qEAjzsjspKfQh1but3R1x4XGTNMcj2sOng8jV7ucbtH8/uklDiQ/MXzOu4ezIR1KdLfs DEzA==
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:date :message-id:subject:from:to:cc; bh=63t4U6UW7JBCdegpfD/vzR++9OiGf7WTs7j5i8ImwYI=; b=jSpj64Nom0+T/MR2Uh9qv70TGDdFIXs4GxLzabkoUDn8OFa/GFWy0XrLtEq/MhEf/X gCKMaC4OgLoZCUHNt/3oU4eIdKiNNuPhiXz2/d4D0QU2kiUE+Mhn/UPQ349UXMs0UPlZ KQKi/GVmYxg0G334HztiY+h0I2RrYTW5TzkgEW+tZZ0Joxf8iKt+P0/kpnTGQRUkJ+By fugSF4f9cpUyfVuxpw5JZzmABN15/jft8E5ZtPudefveaSTVwZ1SvDXgJA1CrOjEf625 VcB3kNTCVS3aNqj/LLQHS+sh0KHVIzROsmUOImhROedlKR1LVTZPmT57GG98prt3cYq+ y7eQ==
X-Gm-Message-State: AOPr4FXJoDKIVsEfY3t9Fz6aQhHnMi2SmUeGKxTnTHOEHwXiGS9vuaZsEptHCofRGLPCZPk+f7K1R3kVDcWOpQ==
MIME-Version: 1.0
X-Received: by 10.159.37.100 with SMTP id 91mr7049486uaz.67.1463956068782; Sun, 22 May 2016 15:27:48 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 22 May 2016 15:27:48 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 22 May 2016 15:27:48 -0700 (PDT)
In-Reply-To: <CAO42Z2xeG3-EwcN1Aa7JTb=aiC-zinp_Gj=iEmGbeEMM8Pg+yA@mail.gmail.com>
References: <5742118B.6020308@si6networks.com> <CAO42Z2xeG3-EwcN1Aa7JTb=aiC-zinp_Gj=iEmGbeEMM8Pg+yA@mail.gmail.com>
Date: Mon, 23 May 2016 08:27:48 +1000
Message-ID: <CAO42Z2x-FUoAbk+N32OarM1siJMeNhV_RQU7HpR71+p-KBYOog@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Mark Smith <markzzzsmith@gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c122da4725c50053375d584
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/g5JhG6FPKBHuU11Ehu6YHh04cwM>
Cc: "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-default-iids@tools.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: Sun, 22 May 2016 22:27:51 -0000

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

On 23 May 2016 6:25 AM, "Fernando Gont" <fgont@si6networks.com> wrote:
>
> Folks,
>
> Lorenzo suggested this text:
>
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address. Configuring a stable IPv6 IID is
>    OPTIONAL.
>
>
> IMHO this goes one step further than what this I-D was meant to do (just
> improve stable addresses), but I guess most of us (all?) agree that
> there are scenarios where you might want to use e.g. temporary-addresses
> *only*.
>
> Is anyone opposed to adding the above text, suggested by Lorenzo?
>

I think it is OK.

I think it would be useful to add some text to say that temporary only
hosts needs some further work due to RFC4941 saying that temporary
addresses co-exist with the host's existing stable addresses.

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
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 23 May 2016 6:25 AM, &quot;Fernando Gont&quot; &lt;<a href=3D"mailto:fgo=
nt@si6networks.com">fgont@si6networks.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Folks,<br>
&gt;<br>
&gt; Lorenzo suggested this text:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0The recommendations in this document apply only in cases =
where<br>
&gt; =C2=A0 =C2=A0implementations otherwise would have configured a stable =
IPv6 IID<br>
&gt; =C2=A0 =C2=A0containing a link layer address. Configuring a stable IPv=
6 IID is<br>
&gt; =C2=A0 =C2=A0OPTIONAL.<br>
&gt;<br>
&gt;<br>
&gt; IMHO this goes one step further than what this I-D was meant to do (ju=
st<br>
&gt; improve stable addresses), but I guess most of us (all?) agree that<br=
>
&gt; there are scenarios where you might want to use e.g. temporary-address=
es<br>
&gt; *only*.<br>
&gt;<br>
&gt; Is anyone opposed to adding the above text, suggested by Lorenzo?<br>
&gt;<br></p>
<p dir=3D"ltr">I think it is OK.</p>
<p dir=3D"ltr">I think it would be useful to add some text to say that temp=
orary only hosts needs some further work due to RFC4941 saying that tempora=
ry addresses co-exist with the host&#39;s existing stable addresses.</p>
<p dir=3D"ltr">Regards,<br>
Mark.</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>

--94eb2c122da4725c50053375d584--


From nobody Sun May 22 15:29:26 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 D6DB312D5DC for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:29:23 -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=EjYHXNey; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=V8vHCPdy
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 CRl3ht6Lkz92 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 15:29:22 -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 9321E12D500 for <6man@ietf.org>; Sun, 22 May 2016 15:29:22 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 0BEE220B57 for <6man@ietf.org>; Sun, 22 May 2016 18:29:22 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Sun, 22 May 2016 18:29:22 -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=szZLmXdjf631Xx+Y/WAasdOqqSg=; b=EjYHXN eymNkvgVnzdz2hX07M8eQVxXVEUOFDPNf76IhbacUTJnobyeoGQX41JbYzRBMpvX vG+HubZEyWue2xckO9PZ7E+NopWrrnXQj9LDr5lnfuqbnGmqtKCWvlILq6OroUze AojZFRXQuO037ZqlDMznIqQujIZAcbVUDP/1M=
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=szZLmXdjf631Xx+ Y/WAasdOqqSg=; b=V8vHCPdykv975zajzq2WWnyuZ9w2G2vhbj5sfPA2BjdceZN 8aklN/rg4WoTtioFTYYPxzmPqYWXITqohvCpQTwwU7x9V3z+9yhbPJEu3qhrWuoX NwFOMjoB3ndaZN7hs3AAAeI6+9fBmPwDeo4wGrtLTZu5xa1nvZvMKrYWvsd4=
X-Sasl-enc: ANokUY8BMdBSIvxMoX+rzVGFzzurYC/hBSabOpJm8Wgs 1463956161
Received: from [10.24.118.75] (unknown [128.107.241.167]) by mail.messagingengine.com (Postfix) with ESMTPA id 40F4C680100; Sun, 22 May 2016 18:29:20 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <5742118B.6020308@si6networks.com>
Date: Mon, 23 May 2016 00:29:17 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <B669CF93-F57D-4569-91D7-F4B76B8AB8C6@cooperw.in>
References: <5742118B.6020308@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hnF_uVQkoWrGa0h4HzbCmllSvJ8>
Cc: "6man@ietf.org" <6man@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 22:29:24 -0000

> On May 22, 2016, at 10:07 PM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> Folks,
> 
> Lorenzo suggested this text:
> 
>   The recommendations in this document apply only in cases where
>   implementations otherwise would have configured a stable IPv6 IID
>   containing a link layer address. Configuring a stable IPv6 IID is
>   OPTIONAL.

WFM

Alissa

> 
> 
> IMHO this goes one step further than what this I-D was meant to do (just
> improve stable addresses), but I guess most of us (all?) agree that
> there are scenarios where you might want to use e.g. temporary-addresses
> *only*.
> 
> Is anyone opposed to adding the above text, suggested by Lorenzo?
> 
> 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
> --------------------------------------------------------------------


From nobody Sun May 22 16:08:59 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 1649712D5F9 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 16:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 RgIVBRkhwzvd for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 16:08:56 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 BDDF012D5F8 for <6man@ietf.org>; Sun, 22 May 2016 16:08:56 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id h19so2971760ywc.0 for <6man@ietf.org>; Sun, 22 May 2016 16:08:56 -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=NkoaVEzgLJH4glPgk78j3fgpdS2TRc6J7NawYm2OWeU=; b=EbqHepzjjn+UVYA3kI1lPP1JwbAqVqxkkU5tOJzdOSW66fg3+t5XaPgHGAfFuVQZK3 BnEPV6beO39lNqrYRZNQGD6CrPk/WSyD+skEpQY8N4c4+NMNK2dJhmSmAmKHHPdlXikM bNbiYcWvR7tG2Ca2NZnpzzAd18mnj/bCOveCC4ZaB8zqyxuzioAQu4QVvyZaQybgvEOB VuVr4hMd8D5AgJZ6h+MYo6ODOK/5/+YUHPA5dwXv3DvSGr+HUgwQ0+WDOhn6pNYxrsVP WtI9hTGb90DO1BGvkSlThFYTiTaz1w0P5ryUL9Axg0DbROrEtHlUgoKXun81EOebf1H/ eyCg==
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=NkoaVEzgLJH4glPgk78j3fgpdS2TRc6J7NawYm2OWeU=; b=BD8Nzu7IuwWaQnem7vfyjXAh8Gn/JSkqIoed0CwUrurkgt6+A3dBwcG5ec76qllpW5 bSqZacqq9r8Cr1TlcM52NswO+2zaz3BIidXcU0kTyRK85bsTFdDH1YFMHDRnJ15RnB9L C97qfNvZ+GRISzZeccBTJghNuK2xu8G3EWutN9B+v3gy5zBtYcwEL6bDSCAF/djndgKU wYE3jyEhWaOnOjessFbdBhquLKBiMJLtKGE/Dm8mz6tMI2NHZ+IwPLsIL2iuA7SAE/X+ MFMP8oTusG/EoIOGf0YMMgzhsm2kxsuhjstrjFfajKHZkoycIPb066N2U+mu0mYJz9T0 uppg==
X-Gm-Message-State: AOPr4FVEslJUYsUJSelO+ylOzbeSF7cvv82VrKkLzfSyH2xvPOgOpBxYCaE2P+5F0NEOcYABCL1yJBJyOlNQYpeE
X-Received: by 10.129.80.11 with SMTP id e11mr8425629ywb.197.1463958535789; Sun, 22 May 2016 16:08:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sun, 22 May 2016 16:08:36 -0700 (PDT)
In-Reply-To: <57420ADB.1040203@si6networks.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 23 May 2016 08:08:36 +0900
Message-ID: <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1147d2b27e741105337668ef
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0M3g8ysFe44NaYM2Sbq7alSGjyE>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 23:08:58 -0000

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

On Mon, May 23, 2016 at 4:39 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> > All I'm saying is that if we publish this draft, then the formation of
> > IPv6 IIDs on many link layers, including ethernet and wifi, becomes
> > completely unspecified, and implementations (well - implementations that
> > don't want to use stable IIDs) can do whatever they want with no
> > recommendations or guidance from the IETF.
>
> Huh?
>
> Right now you have specs for stable adresses and RFC4941. This I-D
> simply improves how you generate stable addresses. WHerever you'd embed
> a link-layer id, you use RFC7217. That's it.
>
> Where's the lack of guidance??


Here's the lack of guidance. Take Ethernet. After this document is
published, all the text in RFC 2464 is replaced by this text:

   The Interface Identifier [AARCH] for an Ethernet interface MUST be
   generated as specified in [RFCXXXX].

RFCXXXX says that it applies only if an implementation wants to create a
stable address, and that that is OPTIONAL.

If an implementation does not want to create a stable address, there is no
guidance as to what it should do. I assume that means it can do whatever it
wants.

--001a1147d2b27e741105337668ef
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 M=
on, May 23, 2016 at 4:39 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com">fgont@si6networks.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204=
);padding-left:1ex"><span class=3D"gmail-">&gt; All I&#39;m saying is that =
if we publish this draft, then the formation of<br>
&gt; IPv6 IIDs on many link layers, including ethernet and wifi, becomes<br=
>
&gt; completely unspecified, and implementations (well - implementations th=
at<br>
&gt; don&#39;t want to use stable IIDs) can do whatever they want with no<b=
r>
&gt; recommendations or guidance from the IETF.<br>
<br>
</span>Huh?<br>
<br>
Right now you have specs for stable adresses and RFC4941. This I-D<br>
simply improves how you generate stable addresses. WHerever you&#39;d embed=
<br>
a link-layer id, you use RFC7217. That&#39;s it.<br>
<br>
Where&#39;s the lack of guidance??</blockquote><div><br></div><div>Here&#39=
;s the lack of guidance. Take Ethernet. After this document is published, a=
ll the text in RFC 2464 is replaced by this text:<br></div><div><br></div><=
div><div>=C2=A0 =C2=A0The Interface Identifier [AARCH] for an Ethernet inte=
rface MUST be</div><div>=C2=A0 =C2=A0generated as specified in [RFCXXXX].</=
div></div><div><br></div><div>RFCXXXX says that it applies only if an imple=
mentation wants to create a stable address, and that that is OPTIONAL.</div=
><div><br></div><div>If an implementation does not want to create a stable =
address, there is no guidance as to what it should do. I assume that means =
it can do whatever it wants.</div></div></div></div>

--001a1147d2b27e741105337668ef--


From nobody Sun May 22 16:31:21 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 A584912B017 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 16:31:19 -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 gfzY4Zbe4w1U for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 16:31:18 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 62A5912B00D for <6man@ietf.org>; Sun, 22 May 2016 16:31:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u4MNVHgM047300; Sun, 22 May 2016 16:31:17 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4MNVBA6047295 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Sun, 22 May 2016 16:31:11 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Sun, 22 May 2016 16:31: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; Sun, 22 May 2016 16:31:11 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: default-iids: Clarifying the use of stable addresses
Thread-Topic: default-iids: Clarifying the use of stable addresses
Thread-Index: AQHRsxAyxj/v0dfn8kaK3QK+z/oQZ5/F0m2AgAA6iAD//48j4A==
Date: Sun, 22 May 2016 23:31:10 +0000
Message-ID: <fc5434a2e202424ab49cfe55d2561076@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@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
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: <http://mailarchive.ietf.org/arch/msg/ipv6/-NEaODSygl9-Vp9_WkcULhyvsKg>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Sun, 22 May 2016 23:31:19 -0000

RnJvbTogTG9yZW56byBDb2xpdHRpIFttYWlsdG86bG9yZW56b0Bnb29nbGUuY29tXSANCg0KPiBS
RkNYWFhYIHNheXMgdGhhdCBpdCBhcHBsaWVzIG9ubHkgaWYgYW4gaW1wbGVtZW50YXRpb24gd2Fu
dHMgdG8gY3JlYXRlIGEgc3RhYmxlDQo+IGFkZHJlc3MsIGFuZCB0aGF0IHRoYXQgaXMgT1BUSU9O
QUwuDQoNCkl0J3Mgb25seSAib3B0aW9uYWwiIGluIHRoZSBzZW5zZSB0aGF0IFJGQyAyNDYwLWJp
cyBtaWdodCBzYXkgaXQncyBvcHRpb25hbC4gU3RhYmxlIGFkZHJlc3NlcyBhcmUgbWFuZGF0b3J5
IGluIHNvbWUgbmV0d29ya3MsIHdpdGggc29tZSBzZWN1cml0eSBwcm90b2NvbHMsIGluIHNvbWUg
bmV0d29ya3MgZnVuY3Rpb25zLCBhbmQgc28gb24uIFNvIEknbSBub3Qgc29sZCBvbiB0aGlzICJv
cHRpb25hbCwiIGV4Y2VwdCBpbiB0aGUgc2Vuc2UgdGhhdCBhIGdlbmVyYWwgSVB2NiBTdGFuZGFy
ZCBtaWdodCBzYXkuDQoNCj4gSWYgYW4gaW1wbGVtZW50YXRpb24gZG9lcyBub3Qgd2FudCB0byBj
cmVhdGUgYSBzdGFibGUgYWRkcmVzcywgdGhlcmUgaXMgbm8NCj4gZ3VpZGFuY2UgYXMgdG8gd2hh
dCBpdCBzaG91bGQgZG8uIEkgYXNzdW1lIHRoYXQgbWVhbnMgaXQgY2FuIGRvIHdoYXRldmVyIGl0
IHdhbnRzLg0KDQpCdXQgdGhhdCBndWlkYW5jZSBzaG91bGQgbm90IGJlIGluIHRoaXMgZHJhZnQg
YW55d2F5LCBzbyBpdCdzIG5vdCBuZWNlc3NhcmlseSBjb3JyZWN0IHRvIHNheSB0aGF0IHRoZXkg
Y2FuIGRvIHdoYXRldmVyIHRoZXkgd2FudC4gVGhleSBjYW4gZG8gd2hhdGV2ZXIgdGhlIGd1aWRh
bmNlIGZvciBub24tc3RhYmxlIGFkZHJlc3NlcyBpcywgaW4gb3RoZXIgUkZDcy4gVGhpcyBkcmFm
dCBkb2VzIG5vdCBuZWVkIHRvIGNhcmUuDQoNCkJlcnQNCg0K


From nobody Sun May 22 18:10: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 71D1E12D57A for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 5CgoTUELob8L for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:10:17 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 3917D12D589 for <6man@ietf.org>; Sun, 22 May 2016 18:10:17 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id h19so4470135ywc.0 for <6man@ietf.org>; Sun, 22 May 2016 18:10:17 -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=qXAG0fWvf2XKL6gKV20bbzAn24P7erds9EpYBACHN1c=; b=XXLqdXtRiL1IHP1LSRltc00e2yT513i2g96UfBOt7Q10FM2NHYFUOfWeJIe6auLkyK WMvLvEaTO+RjWzpE2ev3Lw61rzq/rs0ofVOq6lzxVN0eNZT9nP82qCSca1756FjkYM1G MS1qhpNpU4mgURf2AKVZex8yIRECFvy//evmKd5BXOD1feuwn7NinOY7Til0FlvZ+Fh+ gFv7XLljsio2QSLAsI0+E9xxLXy3fIkPUkU6erp44lEgQvU3+F+L8GFrIc7tE0me/ccQ RMQrc4GCMkEZ9Qns8boo4o+IU2bD6xIGsSoXDTeVVYiWGK5P9a35FMEUHSaBahhsaOAK DiJQ==
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=qXAG0fWvf2XKL6gKV20bbzAn24P7erds9EpYBACHN1c=; b=BYsxpItL3Anu8QVPnsNaiYWkmmX+5Y+uZPZ4/7UjWzmsK4px+PgSs+Rh0c+lIj7vVd 1aJhlzmsdAyUPoQkrDaPtoBdPMPecibHViszSrmuAFygS8qEOscBj7Rn5fIeS4RcSOEe Yop++6whF0yINtg+qjNtFRKC8U/xnGSNGrDWlVnXyF8F4a9FCtXYfznbd8bh0EBjQfBp B391bPZWqf/XYpxSWruYhR2CjNBpiHmBfVd2EwQEMz7YpzvzLE3lZSxyDYWmJLEKHD1/ PJ/uvrgkpkt/iNuSZIsb6liegP/zS42hSP+3wBxwqiK5aP0QBP4NiBsrzYBw3sT+5gLR bD1w==
X-Gm-Message-State: ALyK8tIioPaPvULcpLzKb3nOVsY3cLUFCBqPT1f/p2R4FkZ5CYTc+pNg+DVAjTGpFe11ICxXNXy2pwwHZEB8Ske0
X-Received: by 10.129.108.211 with SMTP id h202mr2448248ywc.229.1463965815391;  Sun, 22 May 2016 18:10:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sun, 22 May 2016 18:09:55 -0700 (PDT)
In-Reply-To: <fc5434a2e202424ab49cfe55d2561076@XCH15-06-11.nw.nos.boeing.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com> <fc5434a2e202424ab49cfe55d2561076@XCH15-06-11.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 23 May 2016 10:09:55 +0900
Message-ID: <CAKD1Yr0XqpQVcnFF=W3wdekyB2K46R4OpAOgjJhMoKd8OyJ9ew@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=001a114da7466440460533781ab9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_So9D3ir6j9pKGQRlI7pkRtiRoE>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 01:10:18 -0000

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

On Mon, May 23, 2016 at 8:31 AM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> But that guidance should not be in this draft anyway, so it's not
> necessarily correct to say that they can do whatever they want. They can do
> whatever the guidance for non-stable addresses is, in other RFCs. This
> draft does not need to care.
>

If we all understand that this draft is removing all existing guidance, and
we have WG consensus to do so, that's fine.

Personally I think we can't just leave this up to host implementations. If
some ill-considered implementation decides that its IID generation
algorithm is "pick a random IID between :: and ::ff", it would satisfy this
draft, but I think we need to be able to say that that implementation is
broken.

--001a114da7466440460533781ab9
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 M=
on, May 23, 2016 at 8:31 AM, Manfredi, Albert E <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_blank">albert.e.manfr=
edi@boeing.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But =
that guidance should not be in this draft anyway, so it&#39;s not necessari=
ly correct to say that they can do whatever they want. They can do whatever=
 the guidance for non-stable addresses is, in other RFCs. This draft does n=
ot need to care.<br></blockquote><div><br></div><div>If we all understand t=
hat this draft is removing all existing guidance, and we have WG consensus =
to do so, that&#39;s fine.</div><div><br></div><div>Personally I think we c=
an&#39;t just leave this up to host implementations. If some ill-considered=
 implementation decides that its IID generation algorithm is &quot;pick a r=
andom IID between :: and ::ff&quot;, it would satisfy this draft, but I thi=
nk we need to be able to say that that implementation is broken.<br></div><=
/div></div></div>

--001a114da7466440460533781ab9--


From nobody Sun May 22 18:11: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 A738F12D15C for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 v9fAdIlR4yfq for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:11:17 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 6617D12D0DA for <6man@ietf.org>; Sun, 22 May 2016 18:11:17 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id h19so4484328ywc.0 for <6man@ietf.org>; Sun, 22 May 2016 18:11:17 -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=v8v9jilhLmWuJa6BjZRQOLKchIJyZeZ7ZII8ZvN2Gs0=; b=nMixT1YXf1XgqroXtSsOi7FuNCb+V+yAqmqm7v5UTSBGBSOG8M3jiGviRXDtHMKD1O sOEhzzIzheUOScM6o8pADBfuZ5yXg4CPLGua3UrR8B+/mESFMSH7VSJVc555k4HrLEqP cNPUCLUJ1QCgaN2fmC0ZKOviR4kb2A4XP4S18FAOS9h2zIRmTj+AFYQK2DIkWUPnnxCY iACI90GJJA1jp0iAYf/eDztJ5p0QD7NCyJFwd3KJYYR0D0BFxZKBHT4xk0VsVJNdF5ZU bOlh/uyaeuwvwXOdiWNHUITkPbUBqs7TKLYkYqroKPUCgB8atVxhQfq0Gl+y0GyGD4rr Q3rA==
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=v8v9jilhLmWuJa6BjZRQOLKchIJyZeZ7ZII8ZvN2Gs0=; b=PP4T/88zR7cUubb9gNRmZfsM5YQM4GtdMhXA7/X4/qSliitt5UdXu4tjizu1DfdxRs c2WtgCtTyO0+b2ZhTe8+FcGDqwqfYWRhQIt398SJ2mqLpvT3jaKDNMP/Cuh6jHivUT7S SSBGHcc8/6jMW34PaiD98xWy3LoREoyOT8Duo7HB9vTFgAhliZBFY6oLnkDvLhH8QqkV blXWnkw2xfmoHObx+mcsdOFSNRSPTmQTwlKLSkX/sA8rJjt8CkFtJGMU7ZIrfmXhV0eZ CyUWwcLbgtk1RORxRs+idVKKNUdmylFn0VNWg6BETogJYlZYNpT4faJ5o2i5FXXTCRcD 3U3Q==
X-Gm-Message-State: AOPr4FXiJYsnj92ETJCfbc5xShTPkhRP3vGbpw9w1yqAvzsNsyN93lxcyDM7UL9RTV2TmYL+ICDSXXLkCbiZJpGV
X-Received: by 10.129.80.11 with SMTP id e11mr8600519ywb.197.1463965876634; Sun, 22 May 2016 18:11:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sun, 22 May 2016 18:10:57 -0700 (PDT)
In-Reply-To: <5742118B.6020308@si6networks.com>
References: <5742118B.6020308@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 23 May 2016 10:10:57 +0900
Message-ID: <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1147d2b20acb1d0533781e8c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xR-PpWpfeYK55IXffx6hLQhdaqY>
Cc: "6man@ietf.org" <6man@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 01:11:18 -0000

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

On Mon, May 23, 2016 at 5:07 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> Lorenzo suggested this text:
>
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address. Configuring a stable IPv6 IID is
>    OPTIONAL.
>

Jinmei had some better text, IIRC. Jinmei?

--001a1147d2b20acb1d0533781e8c
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 M=
on, May 23, 2016 at 5:07 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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">Lorenzo suggested this =
text:<br>
<br>
=C2=A0 =C2=A0The recommendations in this document apply only in cases where=
<br>
=C2=A0 =C2=A0implementations otherwise would have configured a stable IPv6 =
IID<br>
=C2=A0 =C2=A0containing a link layer address. Configuring a stable IPv6 IID=
 is<br>
=C2=A0 =C2=A0OPTIONAL.<br></blockquote><div><br></div><div>Jinmei had some =
better text, IIRC. Jinmei?=C2=A0</div></div></div></div>

--001a1147d2b20acb1d0533781e8c--


From nobody Sun May 22 18:12:31 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 7A04012D566 for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 O6rgnMYz47GJ for <ipv6@ietfa.amsl.com>; Sun, 22 May 2016 18:12:29 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 4E43D12D4FE for <ipv6@ietf.org>; Sun, 22 May 2016 18:12:29 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id x189so157427759ywe.3 for <ipv6@ietf.org>; Sun, 22 May 2016 18:12:29 -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=GRCVa/yz9JqFtZfW8QgvfOJCs1GFdqx+PJSNS8SMLGM=; b=XbJDax5x//j4qJgy0ww/SMHf487tA60jXtNHjH/C5Jepu9TF7/lru8+sKscE37MW/o KRAO0N9zYZKcPmQ8sp9AnyXFZ8Wfw3e87+U8NH0cg1xUWwV26s5BOdrSqASDXD1UQICq 00VMdjTFyAioox3dd8kB/gwm7B8K+wTO4xClS4AuGORNQLJwAazVPt/xT+ZxhUDYZU9p UVDjikFZAc5UmNA6J+HgBBwXYRMCC9RZzLuf4re753MKQ1Al8NMkwaAjZpsttSskbq48 OlkErHEu37GWb5RaErjXwQoM47/wogRTCJ5+EcA41hwwUYEl9i+y09xRy8VvSTITfa3T A71A==
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=GRCVa/yz9JqFtZfW8QgvfOJCs1GFdqx+PJSNS8SMLGM=; b=W05v28dtmwA5ponZJsWMGP2QKwBMZioysivhXe4/xzPEgBqGAQql9NUZIZly71qmLN LC6SbWV5oPzQanAqrv7HmLWkl15bqPPHngiCVpGHxeKJmeY8HB90HicikukJ5/nxKtcB e+4PDTLLKodbVake/Ir+fylyO8BUTR/Kl45kQorBYOqoWr3IIeZnntOS3ItXNAFp94HH iq6ADScC7aIM/bKC/bm7831YJAEFoEx89Uof/UGC3ZB0yc03JkzUKzXRiE1HkHFg9JHt rJx23ZKWtJALItJ4jSVg2d9aY2608BF93pmetAXorA/k3A634TSQxpTzUQqCJ6h0k8+r ScKg==
X-Gm-Message-State: AOPr4FWtd6Ua7qeRvGnWZgQSfwDE9DmL2/N1ZOg13SZe5uWpuI2XTH83DTOj7/EMBgv0wJ+BmSPgge8soUpJ+/J4
X-Received: by 10.13.220.69 with SMTP id f66mr8847196ywe.132.1463965948494; Sun, 22 May 2016 18:12:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Sun, 22 May 2016 18:12:08 -0700 (PDT)
In-Reply-To: <57420B44.6080209@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in> <57420B44.6080209@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 23 May 2016 10:12:08 +0900
Message-ID: <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com>
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c8533dd50533782299
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fx5Sqs8Mqb5vBd8HAsOPHtKBXyg>
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: Mon, 23 May 2016 01:12:30 -0000

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

On Mon, May 23, 2016 at 4:40 AM, Fernando Gont <fgont@si6networks.com>
wrote:
>
> The root of this whole problem is embedding a layer-2 id in a layer-3
> field in the first place.
>

No, the root of this whole problem is embedding a *stable* layer-2 ID in a
layer-3 field.

--94eb2c0815c8533dd50533782299
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 M=
on, May 23, 2016 at 4:40 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
The root of this whole problem is embedding a layer-2 id in a layer-3<br>
field in the first place.<br></blockquote><div><br></div><div>No, the root =
of this whole problem is embedding a *stable* layer-2 ID in a layer-3 field=
.</div></div></div></div>

--94eb2c0815c8533dd50533782299--


From nobody Sun May 22 22:50:21 2016
Return-Path: <talmi@marvell.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 B0B7912D14D; Sun, 22 May 2016 22:50:13 -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 EX5SbPmj_Yo8; Sun, 22 May 2016 22:50:11 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 E4EB612B010; Sun, 22 May 2016 22:50:11 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4N5ktoD020604; Sun, 22 May 2016 22:50:10 -0700
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0a-0016f401.pphosted.com with ESMTP id 232n1jn3hd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sun, 22 May 2016 22:50:10 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 23 May 2016 08:50:06 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 23 May 2016 08:50:06 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: Tal Mizrahi <talmi@marvell.com>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@tools.ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Subject: RE: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRsBu8SjhvsjgfU0qMOZhBsheu65/GDEKg
Date: Mon, 23 May 2016 05:50:05 +0000
Message-ID: <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com>
In-Reply-To: <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com>
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: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-23_02:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605230068
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1XietRFTGRUAF8BN3aHKiDIi1k8>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 23 May 2016 05:50:13 -0000

RGVhciBBdXRob3JzIG9mIFZYTEFOLUdQRSAvIEdlbmV2ZSwNCg0KSSBhbSByZWl0ZXJhdGluZyBv
biB0aGlzIHF1ZXN0aW9uLCBhcyBJIGhhdmVuJ3Qgc2VlbiBhIHJlc3BvbnNlIHlldDoNCg0KSGF2
ZSB5b3UgY29uc2lkZXJlZCB0aGUgdXNlIG9mIFNlZ21lbnQgUm91dGluZyB3aXRoIFZYTEFOLUdQ
RSAvIEdlbmV2ZT8gVGhlIGN1cnJlbnQgVlhMQU4tR1BFIC8gR2VuZXZlIGRyYWZ0cyBzZWVtIHRv
IGltcGx5IHRoYXQgSVB2NiBleHRlbnNpb24gaGVhZGVycyBhcmUgY3VycmVudGx5IG5vdCBzdXBw
b3J0ZWQuDQoNClRoYW5rcywNClRhbC4NCg0KDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t
LQ0KPkZyb206IG52bzMgW21haWx0bzpudm8zLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBUYWwgTWl6cmFoaQ0KPlNlbnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAxMjowOSBQTQ0KPlRv
OiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKTsgVG9tIEhlcmJlcnQ7IGRyYWZ0LWlldGYtbnZv
My0NCj5nZW5ldmVAdG9vbHMuaWV0Zi5vcmc7IGRyYWZ0LWlldGYtbnZvMy12eGxhbi1ncGVAdG9v
bHMuaWV0Zi5vcmcNCj5DYzogc3ByaW5nQGlldGYub3JnOyBudm8zQGlldGYub3JnOyA2bWFuIFdH
OyBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC0NCj5yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9y
Zw0KPlN1YmplY3Q6IFJlOiBbbnZvM10gW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWll
dGYtNm1hbi1zZWdtZW50LQ0KPnJvdXRpbmctaGVhZGVyDQo+DQo+U3RlZmFubywNCj4NCj5JZiBJ
IHVuZGVyc3RhbmQgeW91ciBwb2ludCBjb3JyZWN0bHk6DQo+SVB2NiBzZWdtZW50IHJvdXRpbmcg
ZG9lcyBub3Qgd29yayB3aXRoIFZYTEFOIC8gVlhMQU4tR1BFIC8gR2VuZXZlLCBzaW5jZQ0KPnRo
ZXNlIGVuY2Fwc3VsYXRpb25zIGRvIG5vdCBjdXJyZW50bHkgYWxsb3cgdGhlIHVzZSBvZiBJUHY2
IGV4dGVuc2lvbg0KPmhlYWRlcnMuDQo+DQo+SSB3b25kZXIgaWYgdGhlIGF1dGhvcnMgb2YgVlhM
QU4tR1BFIGFuZCBHZW5ldmUgaGF2ZSBjb25zaWRlcmVkIHRoZSB1c2Ugb2YNCj5zZWdtZW50IHJv
dXRpbmcuDQo+DQo+VGhhbmtzLA0KPlRhbC4NCj4NCj4NCj4NCj4+LS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4+RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJl
dmlkaUBjaXNjby5jb21dDQo+PlNlbnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAxMDo0MSBBTQ0K
Pj5UbzogVG9tIEhlcmJlcnQNCj4+Q2M6IFRhbCBNaXpyYWhpOyA2bWFuIFdHOyBzcHJpbmdAaWV0
Zi5vcmc7DQo+PmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlckB0b29scy5p
ZXRmLm9yZw0KPj5TdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWll
dGYtNm1hbi1zZWdtZW50LXJvdXRpbmctDQo+PmhlYWRlcg0KPj4NCj4+DQo+Pj4gT24gTWF5IDE2
LCAyMDE2LCBhdCA3OjEwIFBNLCBUb20gSGVyYmVydCA8dG9tQGhlcmJlcnRsYW5kLmNvbT4NCj53
cm90ZToNCj4+Pg0KPj4+IE9uIE1vbiwgTWF5IDE2LCAyMDE2IGF0IDQ6MzIgQU0sIFRhbCBNaXpy
YWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbT4NCj4+d3JvdGU6DQo+Pj4+PiBpdOKAmXMgYWxsIGFib3V0
IElQLCBub3QgbGF5ZXItMi4NCj4+Pj4+DQo+Pj4+PiBzLg0KPj4+Pg0KPj4+PiBSaWdodC4gSG93
ZXZlciwgaXQgYXBwZWFycyB0aGF0IGF0IGxlYXN0IGluIHNvbWUgY2FzZXMgYSBWWExBTiBWVEVQ
DQo+Pj4+IHdpbGwNCj4+dXNlIFNSLiBJdCBjZXJ0YWlubHkgbWF5IGJlIHRoZSBjYXNlIGluIFNG
QyB1c2UgY2FzZXMgKHNlZSBTZWN0aW9uIDIuMw0KPj5pbiBkcmFmdC0gaWV0Zi1zcHJpbmctaXB2
Ni11c2UtY2FzZXMpLg0KPj4+Pg0KPj4+DQo+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91
dGluZy1oZWFkZXIgbWVudGlvbnMgdGhhdCB0aGUgcGFja2V0IGlzDQo+Pj4gZW5jYXBzdWxhdGVk
DQo+Pg0KPj4NCj4+aW50byBhbiBvdXRlciBpcHY2IGhlYWRlciB3aGljaCBtYWtlcyBpdCBhIGxh
eWVyLTMgZW5jYXAuDQo+Pg0KPj4NCj4+PiAsIGJ1dCBJIGRvbid0IHRoaW5rIGl0IGlzIGV4cGxp
Y2l0IGFzIHRvIGV4YWN0IGVuY2Fwc3VsYXRpb24gZm9ybWF0DQo+Pj4gKEkgc3VwcG9zZSBzaW1w
bGUgaXA2aXA2IGlzIGltcGxpZWQpLg0KPj4NCj4+DQo+PnNlZSBzZWN0aW9uIDIuMg0KPj4NCj4+
DQo+Pj4gQnV0LCBpdA0KPj4+IHNlZW1zIGxpa2UgYW55IG9mIHNldmVyYWwgZW5jYXBzdWxhdGlv
biB0ZWNobmlxdWVzIGNvdWxkIHdvcmsgKFZYTEFOLA0KPj4NCj4+DQo+PkkgaGF2ZSBzb21lIHBy
b2JsZW1zIHRvIHVuZGVyc3RhbmQgd2hlcmUgdG8gZml0IGFuIGV4dGVuc2lvbiBoZWFkZXINCj4+
aW50byBhIHZ4bGFuIGVuY2Fw4oCmDQo+Pg0KPj4NCj4+PiBHUkUvSVAsIEVTUC9JUCwgR1VFLCBm
b28gb3ZlciBVRFAsIGV0Yy4pIGFuZCBpZiBhIGRldmljZSB0aGF0IHdhbnRzDQo+Pj4gdG8gZG8g
U1IgaXMgYWxyZWFkeSBkb2luZyB0dW5uZWxpbmcgaXQgc2VlbXMgcmVhc29uYWJsZSB0byBtZSB0
byBvbmx5DQo+Pj4gaGF2ZSBvbmUgbGF5ZXIgb2YgZW5jYXBzdWxhdGlvbi4gTWF5YmUgdGhpcyBz
aG91bGQgYmUgY2xhcmlmaWVkIGluDQo+Pj4gdGhlIGRyYWZ0Pw0KPj4NCj4+DQo+PnRoZSBkcmFm
dCBpcyBhYm91dCBJUHY2IGV4dGVuc2lvbiBoZWFkZXIgYW5kIG1vcmUgcHJlY2lzZWx5IGEgbmV3
IHR5cGUNCj4+b2YgdGhlIHJvdXRpbmcgZXh0ZW5zaW9uIGhlYWRlciBkZWZpbmVkIGluIHJmYzI0
NjAuIFRoYXTigJlzIHRoZSBjb250ZXh0Lg0KPj4NCj4+DQo+PnMuDQo+Pg0KPj4NCj4+DQo+Pg0K
Pj4+DQo+Pj4gVG9tDQo+Pj4NCj4+Pj4NCj4+Pj4NCj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+Pj4+PiBGcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNw
cmV2aWRpQGNpc2NvLmNvbV0NCj4+Pj4+IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MjQg
UE0NCj4+Pj4+IFRvOiBUYWwgTWl6cmFoaQ0KPj4+Pj4gQ2M6IE9sZSBUcsO4YW47DQo+Pj4+PiBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsNCj4+
Pj4+IHNwcmluZ0BpZXRmLm9yZzsgNm1hbiBXRw0KPj4+Pj4gU3ViamVjdDogUmU6IFtzcHJpbmdd
IEw0IENoZWNrc3VtIGFuZA0KPj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0g
aGVhZGVyDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDE6MTkgUE0s
IFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbT4gd3JvdGU6DQo+Pj4+Pj4NCj4+Pj4+PiBI
aSBTdGVmYW5vLA0KPj4+Pj4+DQo+Pj4+Pj4gVGhhbmtzIGFnYWluIGZvciB0aGUgcHJvbXB0IHJl
c3BvbnNlLg0KPj4+Pj4+DQo+Pj4+Pj4+IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBieSB0aGUg
aW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+Pj4+Pj4+IFRoaXMgaXMgZG9uZSBieSBl
bmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyDQo+Pj4+Pj4+IChhZGRpdGlvbmFs
KSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDMNCj4+Pj4+Pj4gZW5j
YXBzdWxhdGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlICBwYWNr
ZXQNCj4+Pj4+Pj4gbGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fwc3VsYXRpb24g
IChpbmNsdWRpbmcgdGhlIFNSSCkNCj4+Pj4+Pj4gaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBj
b250aW51ZXMgIGl0cyBqb3VybmV5IGxpa2Ugbm90aGluZw0KPmhhcHBlbmVkLg0KPj4+Pj4+DQo+
Pj4+Pj4gU28gVlhMQU4gaXMgb2ZmIHRoZSB0YWJsZT8NCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4gaXTi
gJlzIGFsbCBhYm91dCBJUCwgbm90IGxheWVyLTIuDQo+Pj4+Pg0KPj4+Pj4gcy4NCj4+Pj4+DQo+
Pj4+Pg0KPj4+Pj4+IEl0IHdvdWxkIGJlIHdvcnRod2hpbGUgdG8gY2xhcmlmeSB0aGlzIGluIHRo
ZSBkcmFmdC4gSWYgeW91IGhhdmUgYQ0KPj4+Pj4+IHNwZWNpZmljDQo+Pj4+PiBlbmNhcHN1bGF0
aW9uIGluIG1pbmQsIGl0IHdvdWxkIGJlIGdyZWF0IGlmIHRoZSBkcmFmdCB3b3VsZCBzcGVjaWZ5
IGl0Lg0KPj4+Pj4+DQo+Pj4+Pj4gVGhhbmtzLA0KPj4+Pj4+IFRhbC4NCj4+Pj4+Pg0KPj4+Pj4+
DQo+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+Pj4+IEZyb206IFN0ZWZh
bm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0KPj4+Pj4+
PiBTZW50OiBNb25kYXksIE1heSAxNiwgMjAxNiAyOjEzIFBNDQo+Pj4+Pj4+IFRvOiBUYWwgTWl6
cmFoaQ0KPj4+Pj4+PiBDYzogT2xlIFRyw7hhbjsNCj4+Pj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNl
Z21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7DQo+Pj4+Pj4+IHNwcmluZ0BpZXRm
Lm9yZzsgNm1hbiBXRw0KPj4+Pj4+PiBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0g
YW5kDQo+Pj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+
Pj4+Pg0KPj4+Pj4+PiBIaSwNCj4+Pj4+Pj4NCj4+Pj4+Pj4gT24gTWF5IDE2LCAyMDE2LCBhdCAx
MTowNCBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29tPg0KPj53cm90ZToNCj4+Pj4+
Pj4+DQo+Pj4+Pj4+PiBIaSBTdGVmYW5vLA0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IFRoYW5rcyBmb3Ig
dGhlIHJlc3BvbnNlcy4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gZXhhY3RseS4NCj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRl
ciBhc3N1bWVzDQo+Pj4+Pj4+Pj4gZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBu
byBMNCBpbnZvbHZlZCBoZXJlLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gcy4NCj4+Pj4+Pj4+DQo+
Pj4+Pj4+PiBUd28gcXVlc3Rpb25zOg0KPj4+Pj4+Pj4gMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxh
dGlvbiBpcyBWWExBTj8gTDQgd291bGQgc3RpbGwgYmUNCj4+Pj4+Pj4+IGludm9sdmVkLA0KPj5y
aWdodD8NCj4+Pj4+Pj4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gU2VlIGJlbG93Lg0KPj4+Pj4+Pg0KPj4+
Pj4+Pg0KPj4+Pj4+Pj4gMi4gV2hlbiB5b3Ugc2F5ICdhc3N1bWVzIGVuY2Fwc3VsYXRpb24nLCBk
b2VzIGl0IG1lYW4gdGhhdCBhDQo+Pj4+Pj4+PiBob3N0IGNhbm5vdA0KPj4+Pj4+PiBzZW5kIGFu
IElQdjYgcGFja2V0IHdpdGggYW4gU1JIPyBUaGUgY3VycmVudCBkcmFmdCBzYXlzOg0KPj4+Pj4+
Pj4NCj4+Pj4+Pj4+IEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFueSBub2RlIG9yaWdpbmF0aW5n
IGFuIElQdjYgcGFja2V0IHdpdGgNCj4+Pj4+Pj4+IGl0cw0KPj4+Pj4+Pj4gSVB2NiBhbmQgU2Vn
bWVudCBSb3V0aW5nIEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0aGVyOg0KPj4+Pj4+Pj4NCj4+
Pj4+Pj4+ICAgIEEgaG9zdCBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tldC4NCj4+Pj4+Pj4+DQo+
Pj4+Pj4+PiAgICBBbiBTUiBkb21haW4gaW5ncmVzcyByb3V0ZXIgZW5jYXBzdWxhdGluZyBhIHJl
Y2VpdmVkIElQdjYgcGFja2V0DQo+Pj4+Pj4+PiAgICBpbnRvIGFuIG91dGVyIElQdjYgaGVhZGVy
IGZvbGxvd2VkIGJ5IGFuIFNSSC4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+
Pj4+IFdpbGwgYXBwcmVjaWF0ZSBpZiB5b3UgY2FuIGNsYXJpZnkgdGhhdC4NCj4+Pj4+Pj4NCj4+
Pj4+Pj4NCj4+Pj4+Pj4gb2ssIHR3byBjYXNlczoNCj4+Pj4+Pj4NCj4+Pj4+Pj4gMS4gdGhlIFNS
SCBpcyBpbnNlcnRlZCBhdCB0aGUgc291cmNlLg0KPj4+Pj4+PiB0aGUgc291cmNlIG9yaWdpbmF0
ZXMgdGhlIHBhY2tldCwgdGhlIGlwdjYgaGVhZGVyIGFuZCAgdGhlIFNSSC4NCj4+Pj4+Pj4gVGhl
IHNvdXJjZSBjb21wdXRlcyBMNCBjaGVja3N1bSB0YWtpbmcgaW50byAgYWNjb3VudCB0aGUgd2hv
bGUNCj4+SVB2NitTUkguDQo+Pj4+Pj4+IEhlcmUsIHRoZXJlc+KAmSBub3RoaW5nIG5ldyAgY29t
cGFyZWQgdG8gcmZjMjQ2MC4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gMi4gdGhlIFNSSCBpcyBvcmlnaW5h
dGVkIGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRvbWFpbi4NCj4+Pj4+Pj4gVGhpcyBp
cyBkb25lIGJ5IGVuY2Fwc3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0ZXINCj4+Pj4+Pj4g
KGFkZGl0aW9uYWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMw0K
Pj4+Pj4+PiBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZvbHZlZC4gV2hl
biB0aGUgIHBhY2tldA0KPj4+Pj4+PiBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5j
YXBzdWxhdGlvbiAgKGluY2x1ZGluZyB0aGUgU1JIKQ0KPj4+Pj4+PiBpcyByZW1vdmVkIGFuZCB0
aGUgcGFja2V0IGNvbnRpbnVlcyAgaXRzIGpvdXJuZXkgbGlrZSBub3RoaW5nDQo+aGFwcGVuZWQu
DQo+Pj4+Pj4+DQo+Pj4+Pj4+IHMuDQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4gVGhhbmtzLA0KPj4+Pj4+Pj4gVGFsLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+PiAtLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPj4+Pj4+Pj4+IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZp
ZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tXQ0KPj4+Pj4+Pj4+IFNlbnQ6IE1vbmRheSwg
TWF5IDE2LCAyMDE2IDExOjU5IEFNDQo+Pj4+Pj4+Pj4gVG86IE9sZSBUcsO4YW47IFRhbCBNaXpy
YWhpDQo+Pj4+Pj4+Pj4gQ2M6IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVy
QHRvb2xzLmlldGYub3JnOw0KPj4+Pj4+Pj4+IHNwcmluZ0BpZXRmLm9yZzsgNm1hbiBXRw0KPj4+
Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQNCj4+Pj4+Pj4+PiBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXINCj4+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4+DQo+Pj4+Pj4+Pj4+IE9uIE1heSAxNSwgMjAxNiwgYXQgODowNiBQTSwgb3Ryb2FuQGVtcGxv
eWVlcy5vcmcgd3JvdGU6DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IFRhbCwNCj4+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+Pj4+IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQg
YmVmb3JlLl0NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0
Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSDQo+Pj4+Pj4+Pj4+PiBTZWdt
ZW50DQo+Pj4+Pj4+Pj4gRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVzIHRoZSBEZXN0aW5hdGlvbiBJ
UCBhZGRyZXNzLg0KPj4+Pj4+Pj4+Pj4gVGhlcmVmb3JlLCBpdCBtdXN0IGFsc28gdXBkYXRlIHRo
ZSBMYXllciA0IENoZWNrc3VtLCByaWdodD8NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBJIHdv
bmRlciBpZiB0aGVyZSBpcyBhbiB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0aGUgU1JILg0K
Pj4+Pj4+Pj4+Pj4gT3RoZXJ3aXNlLCB0aGUNCj4+Pj4+Pj4+PiBMNCBDaGVja3N1bSBtYXkgYmUg
bG9jYXRlZCBpbiBhIHByZXR0eSBkZWVwIGxvY2F0aW9uLg0KPj4+Pj4+Pj4+Pj4gU3BlYWtpbmcg
ZnJvbSBhIGNoaXAgdmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0u
DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IEZyb20gUkZDMjQ2MCwgUkgwOg0KPj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiAgIG8gIElmIHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBh
IFJvdXRpbmcgaGVhZGVyLCB0aGUgRGVzdGluYXRpb24NCj4+Pj4+Pj4+Pj4gICAgICBBZGRyZXNz
IHVzZWQgaW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhhdCBvZiB0aGUgZmluYWwNCj4+Pj4+Pj4+
Pj4gICAgICBkZXN0aW5hdGlvbi4gIEF0IHRoZSBvcmlnaW5hdGluZyBub2RlLCB0aGF0IGFkZHJl
c3Mgd2lsbCBiZSBpbg0KPj4+Pj4+Pj4+PiAgICAgIHRoZSBsYXN0IGVsZW1lbnQgb2YgdGhlIFJv
dXRpbmcgaGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMpLA0KPj4+Pj4+Pj4+PiAgICAgIHRoYXQg
YWRkcmVzcyB3aWxsIGJlIGluIHRoZSBEZXN0aW5hdGlvbiBBZGRyZXNzIGZpZWxkIG9mIHRoZQ0K
Pj4+Pj4+Pj4+PiAgICAgIElQdjYgaGVhZGVyLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBJIHdv
dWxkIGV4cGVjdCBTUiB3b3VsZCB3b3JrIHRoZSBzYW1lLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+PiBleGFjdGx5Lg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gTW9yZW92ZXIsIGRyYWZ0
LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4+Pj4+PiBlbmNh
cHN1bGF0aW9uIHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+Pj4+
Pj4+Pj4NCj4+Pj4+Pj4+PiBzLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4NCj4+
Pj4+Pj4+Pj4gQ2hlZXJzLA0KPj4+Pj4+Pj4+PiBPbGUNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+
Pj4+Pj4NCj4+Pj4NCj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+Pj4gSUVURiBJUHY2IHdvcmtpbmcgZ3Jv
dXAgbWFpbGluZyBsaXN0IGlwdjZAaWV0Zi5vcmcgQWRtaW5pc3RyYXRpdmUNCj4+Pj4gUmVxdWVz
dHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2Ng0KPj4+PiAtLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+bnZvMyBtYWlsaW5nIGxpc3QNCj5udm8zQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9udm8zDQo=


From nobody Mon May 23 00:29:13 2016
Return-Path: <rraszuk@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 68FA712D0BF; Mon, 23 May 2016 00:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 lRGNprOEz4-z; Mon, 23 May 2016 00:29:08 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::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 A242812D099; Mon, 23 May 2016 00:29:07 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id e131so20829956lfb.0; Mon, 23 May 2016 00:29:07 -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:date:message-id:subject :from:to:cc; bh=s4B5Rh9/mUUCqsmhxguw5triCijipJL/6g/nmkbOSBc=; b=ZN6s+Tet48hSnWaXaTnUIB6FU07OvforVhgr3veAul1fBMfMhTiVRwYnn7MAJBOj1q y3I2WxNsimz25cu5/ZTkrcfahFL816dV08bnou6kLwJhjMfBgyHuhuUseL2UOVOwR7LS QahDj2968LWifUmOureL3DOkuVC7kfwAyPMfTi0FthPaf7yTor0gvvgsfswQfdkU1KP8 ArzWssA0xg8a8Iv2HHbC7Um24Hj9/dKiwa5FXqpPf/XLOPCISAPMrJIFay5mvfZinR/L dPkgt4XLHIlX5xUGzXuJ83Gyk7zevYY1lwPvNoL2gMV76Tqe8F35TrKbKPwzVyQHo6VO Avfw==
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:date :message-id:subject:from:to:cc; bh=s4B5Rh9/mUUCqsmhxguw5triCijipJL/6g/nmkbOSBc=; b=cmjR3jZQf7biexQpzd3tqp8r8Ansdz1ZwOw+dC8OzY93w6lM6LX+C464y+gOuMaMKI XAmkwMzVJr4amUq6H2kztzxEsirfYAwy4z7tEhv1qqN9P3dROJy6NJfAV/vWoYB8yA7U 5G1Nmn3UdS1/+rbWwCB1FkqgpZzb2oqmGitAJ7PXkMt6VgiZpwcbyelbxGLY6nl/XPNm wHk91CQSPYpT8Xguow3+YGueFPF6fF/o4ei2lKJv+XLwTXh2Wym5JvQKtNPno75q7eAh zR52V+VR5+1EKEwDhQ05HvgsKUdg78YfsW9asXzOP54VaFwnKteaUk2ygoA3Dn4fMw8N lUAg==
X-Gm-Message-State: AOPr4FVRzu0qoBCnZ2na0R3sEIF3j2eQW4VP0Eg40+NcfVIs6LliwSwXRHRcZ+JWmcIzoAhpD94jdH4QXO2vew==
MIME-Version: 1.0
X-Received: by 10.25.21.156 with SMTP id 28mr4948594lfv.124.1463988545643; Mon, 23 May 2016 00:29:05 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.25.126.210 with HTTP; Mon, 23 May 2016 00:29:05 -0700 (PDT)
In-Reply-To: <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com>
Date: Mon, 23 May 2016 09:29:05 +0200
X-Google-Sender-Auth: Gwlpm2S0do1YjcmM6l2AwkMR__E
Message-ID: <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com>
Subject: Re: [spring] [nvo3] L4 Checksum and draft-ietf-6man-segment-routing-header
From: Robert Raszuk <robert@raszuk.net>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=001a1140677637ee3c05337d65c8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bBNLy5vqZmSuPLiHGkffLv0hxgA>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 07:29:11 -0000

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

Hi Tal,

> drafts seem to imply

Where say in draft draft-quinn-vxlan-gpe do you see such statement that
would imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a
pointer to any other type of extension header further followed by UDP ?

Thx,
R.


On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com> wrote:

> Dear Authors of VXLAN-GPE / Geneve,
>
> I am reiterating on this question, as I haven't seen a response yet:
>
> Have you considered the use of Segment Routing with VXLAN-GPE / Geneve?
> The current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension
> headers are currently not supported.
>
> Thanks,
> Tal.
>
>
>
> >-----Original Message-----
> >From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Tal Mizrahi
> >Sent: Tuesday, May 17, 2016 12:09 PM
> >To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
> >geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org
> >Cc: spring@ietf.org; nvo3@ietf.org; 6man WG; draft-ietf-6man-segment-
> >routing-header@tools.ietf.org
> >Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
> >routing-header
> >
> >Stefano,
> >
> >If I understand your point correctly:
> >IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sinc=
e
> >these encapsulations do not currently allow the use of IPv6 extension
> >headers.
> >
> >I wonder if the authors of VXLAN-GPE and Geneve have considered the use =
of
> >segment routing.
> >
> >Thanks,
> >Tal.
> >
> >
> >
> >>-----Original Message-----
> >>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>Sent: Tuesday, May 17, 2016 10:41 AM
> >>To: Tom Herbert
> >>Cc: Tal Mizrahi; 6man WG; spring@ietf.org;
> >>draft-ietf-6man-segment-routing- header@tools.ietf.org
> >>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
> >>header
> >>
> >>
> >>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com>
> >wrote:
> >>>
> >>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>
> >>>> Right. However, it appears that at least in some cases a VXLAN VTEP
> >>>> will
> >>use SR. It certainly may be the case in SFC use cases (see Section 2.3
> >>in draft- ietf-spring-ipv6-use-cases).
> >>>>
> >>>
> >>> draft-ietf-6man-segment-routing-header mentions that the packet is
> >>> encapsulated
> >>
> >>
> >>into an outer ipv6 header which makes it a layer-3 encap.
> >>
> >>
> >>> , but I don't think it is explicit as to exact encapsulation format
> >>> (I suppose simple ip6ip6 is implied).
> >>
> >>
> >>see section 2.2
> >>
> >>
> >>> But, it
> >>> seems like any of several encapsulation techniques could work (VXLAN,
> >>
> >>
> >>I have some problems to understand where to fit an extension header
> >>into a vxlan encap=E2=80=A6
> >>
> >>
> >>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
> >>> to do SR is already doing tunneling it seems reasonable to me to only
> >>> have one layer of encapsulation. Maybe this should be clarified in
> >>> the draft?
> >>
> >>
> >>the draft is about IPv6 extension header and more precisely a new type
> >>of the routing extension header defined in rfc2460. That=E2=80=99s the =
context.
> >>
> >>
> >>s.
> >>
> >>
> >>
> >>
> >>>
> >>> Tom
> >>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>> Sent: Monday, May 16, 2016 2:24 PM
> >>>>> To: Tal Mizrahi
> >>>>> Cc: Ole Tr=C3=B8an;
> >>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>> spring@ietf.org; 6man WG
> >>>>> Subject: Re: [spring] L4 Checksum and
> >>>>> draft-ietf-6man-segment-routing- header
> >>>>>
> >>>>>
> >>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com> wrote=
:
> >>>>>>
> >>>>>> Hi Stefano,
> >>>>>>
> >>>>>> Thanks again for the prompt response.
> >>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>
> >>>>>> So VXLAN is off the table?
> >>>>>
> >>>>>
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>>
> >>>>>
> >>>>>> It would be worthwhile to clarify this in the draft. If you have a
> >>>>>> specific
> >>>>> encapsulation in mind, it would be great if the draft would specify
> it.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Tal.
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>> Sent: Monday, May 16, 2016 2:13 PM
> >>>>>>> To: Tal Mizrahi
> >>>>>>> Cc: Ole Tr=C3=B8an;
> >>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>> spring@ietf.org; 6man WG
> >>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>>>>>
> >>>>>>>> Hi Stefano,
> >>>>>>>>
> >>>>>>>> Thanks for the responses.
> >>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>
> >>>>>>>> Two questions:
> >>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
> >>>>>>>> involved,
> >>right?
> >>>>>>>
> >>>>>>>
> >>>>>>> See below.
> >>>>>>>
> >>>>>>>
> >>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
> >>>>>>>> host cannot
> >>>>>>> send an IPv6 packet with an SRH? The current draft says:
> >>>>>>>>
> >>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
> >>>>>>>> its
> >>>>>>>> IPv6 and Segment Routing Headers.  This include either:
> >>>>>>>>
> >>>>>>>>    A host originating an IPv6 packet.
> >>>>>>>>
> >>>>>>>>    An SR domain ingress router encapsulating a received IPv6
> packet
> >>>>>>>>    into an outer IPv6 header followed by an SRH.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Will appreciate if you can clarify that.
> >>>>>>>
> >>>>>>>
> >>>>>>> ok, two cases:
> >>>>>>>
> >>>>>>> 1. the SRH is inserted at the source.
> >>>>>>> the source originates the packet, the ipv6 header and  the SRH.
> >>>>>>> The source computes L4 checksum taking into  account the whole
> >>IPv6+SRH.
> >>>>>>> Here, theres=E2=80=99 nothing new  compared to rfc2460.
> >>>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>>
> >>>>>>> s.
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Tal.
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
> >>>>>>>>> To: Ole Tr=C3=B8an; Tal Mizrahi
> >>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>>>> spring@ietf.org; 6man WG
> >>>>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
> >>>>>>>>>>
> >>>>>>>>>> Tal,
> >>>>>>>>>>
> >>>>>>>>>>> [Apologies if this issue has been discussed before.]
> >>>>>>>>>>>
> >>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =E2=
=80=98SR
> >>>>>>>>>>> Segment
> >>>>>>>>> Endpoint Node=E2=80=99 updates the Destination IP address.
> >>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
> >>>>>>>>>>>
> >>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
> >>>>>>>>>>> Otherwise, the
> >>>>>>>>> L4 Checksum may be located in a pretty deep location.
> >>>>>>>>>>> Speaking from a chip vendor=E2=80=99s perspective this may be=
 a
> problem.
> >>>>>>>>>>
> >>>>>>>>>> From RFC2460, RH0:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>   o  If the IPv6 packet contains a Routing header, the
> Destination
> >>>>>>>>>>      Address used in the pseudo-header is that of the final
> >>>>>>>>>>      destination.  At the originating node, that address will
> be in
> >>>>>>>>>>      the last element of the Routing header; at the
> recipient(s),
> >>>>>>>>>>      that address will be in the Destination Address field of
> the
> >>>>>>>>>>      IPv6 header.
> >>>>>>>>>>
> >>>>>>>>>> I would expect SR would work the same.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Ole
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> >>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>>> --------------------------------------------------------------------
> >
> >_______________________________________________
> >nvo3 mailing list
> >nvo3@ietf.org
> >https://www.ietf.org/mailman/listinfo/nvo3
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Tal,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small">&gt;=C2=A0<span style=3D"font-size:12.8px;font-family=
:arial,sans-serif">drafts seem to imply</span></div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br>=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small">Where say in draft=C2=A0draft-quinn-vxlan-gpe do y=
ou see such statement that would imply that v6 NxtHdr must be only equal to=
 17 (UDP) and not be a pointer to any other type of extension header furthe=
r followed by UDP ?=C2=A0</div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll">Thx,<br>R.</div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small"><br></div></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Mon, May 23, 2016 at 7:50 AM, Tal =
Mizrahi <span dir=3D"ltr">&lt;<a href=3D"mailto:talmi@marvell.com" target=
=3D"_blank">talmi@marvell.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">Dear Authors of VXLAN-GPE / Geneve,<br>
<br>
I am reiterating on this question, as I haven&#39;t seen a response yet:<br=
>
<br>
Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.<br>
<br>
Thanks,<br>
Tal.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org">nvo3-bounce=
s@ietf.org</a>] On Behalf Of Tal Mizrahi<br>
&gt;Sent: Tuesday, May 17, 2016 12:09 PM<br>
&gt;To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-<br>
&gt;<a href=3D"mailto:geneve@tools.ietf.org">geneve@tools.ietf.org</a>; <a =
href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org">draft-ietf-nvo3-vx=
lan-gpe@tools.ietf.org</a><br>
&gt;Cc: <a href=3D"mailto:spring@ietf.org">spring@ietf.org</a>; <a href=3D"=
mailto:nvo3@ietf.org">nvo3@ietf.org</a>; 6man WG; draft-ietf-6man-segment-<=
br>
&gt;<a href=3D"mailto:routing-header@tools.ietf.org">routing-header@tools.i=
etf.org</a><br>
&gt;Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-<b=
r>
&gt;routing-header<br>
&gt;<br>
&gt;Stefano,<br>
&gt;<br>
&gt;If I understand your point correctly:<br>
&gt;IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sin=
ce<br>
&gt;these encapsulations do not currently allow the use of IPv6 extension<b=
r>
&gt;headers.<br>
&gt;<br>
&gt;I wonder if the authors of VXLAN-GPE and Geneve have considered the use=
 of<br>
&gt;segment routing.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;-----Original Message-----<br>
&gt;&gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevidi=
@cisco.com">sprevidi@cisco.com</a>]<br>
&gt;&gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt;&gt;To: Tom Herbert<br>
&gt;&gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org">spring=
@ietf.org</a>;<br>
&gt;&gt;draft-ietf-6man-segment-routing- <a href=3D"mailto:header@tools.iet=
f.org">header@tools.ietf.org</a><br>
&gt;&gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routi=
ng-<br>
&gt;&gt;header<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailto=
:tom@herbertland.com">tom@herbertland.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"ma=
ilto:talmi@marvell.com">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Right. However, it appears that at least in some cases a V=
XLAN VTEP<br>
&gt;&gt;&gt;&gt; will<br>
&gt;&gt;use SR. It certainly may be the case in SFC use cases (see Section =
2.3<br>
&gt;&gt;in draft- ietf-spring-ipv6-use-cases).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; draft-ietf-6man-segment-routing-header mentions that the packe=
t is<br>
&gt;&gt;&gt; encapsulated<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; , but I don&#39;t think it is explicit as to exact encapsulati=
on format<br>
&gt;&gt;&gt; (I suppose simple ip6ip6 is implied).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;see section 2.2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; But, it<br>
&gt;&gt;&gt; seems like any of several encapsulation techniques could work =
(VXLAN,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;I have some problems to understand where to fit an extension header=
<br>
&gt;&gt;into a vxlan encap=E2=80=A6<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that =
wants<br>
&gt;&gt;&gt; to do SR is already doing tunneling it seems reasonable to me =
to only<br>
&gt;&gt;&gt; have one layer of encapsulation. Maybe this should be clarifie=
d in<br>
&gt;&gt;&gt; the draft?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;the draft is about IPv6 extension header and more precisely a new t=
ype<br>
&gt;&gt;of the routing extension header defined in rfc2460. That=E2=80=99s =
the context.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Tom<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"ma=
ilto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-head=
er@tools.ietf.org">draft-ietf-6man-segment-routing-header@tools.ietf.org</a=
>;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">spring@ietf.org</a>=
; 6man WG<br>
&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a hr=
ef=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the draf=
t. If you have a<br>
&gt;&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft =
would specify it.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a hr=
ef=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org">draft-ietf-6man-segment-routing-header@tools.iet=
f.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">spring@ietf=
.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt;=
<a href=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4 =
would still be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; involved,<br>
&gt;&gt;right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say &#39;assumes encapsulation=
&#39;, does it mean that a<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; host cannot<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current d=
raft says:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originati=
ng an IPv6 packet with<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.=C2=A0 Th=
is include either:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A host originating an IPv6 pa=
cket.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 An SR domain ingress router e=
ncapsulating a received IPv6 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 into an outer IPv6 header fol=
lowed by an SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 hea=
der and=C2=A0 the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into=C2=
=A0 account the whole<br>
&gt;&gt;IPv6+SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Here, theres=E2=80=99 nothing new=C2=A0 compar=
ed to rfc2460.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mail=
to:<a href=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<br=
>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=C3=B8an; Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man-=
segment-routing-header@tools.ietf.org">draft-ietf-6man-segment-routing-head=
er@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org">spr=
ing@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- heade=
r<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a hr=
ef=3D"mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has b=
een discussed before.]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-s=
egment-routing-header, an =E2=80=98SR<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node=E2=80=99 updates the Des=
tination IP address.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also update=
 the Layer 4 Checksum, right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper =
bound on the size of the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a pretty=
 deep location.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor=E2=
=80=99s perspective this may be a problem.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0o=C2=A0 If the IPv6 pa=
cket contains a Routing header, the Destination<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Address used i=
n the pseudo-header is that of the final<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 destination.=
=C2=A0 At the originating node, that address will be in<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 the last eleme=
nt of the Routing header; at the recipient(s),<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 that address w=
ill be in the Destination Address field of the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 IPv6 header.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the s=
ame.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;&gt;&gt;&gt; IETF IPv6 working group mailing list <a href=3D"mailto:ipv=
6@ietf.org">ipv6@ietf.org</a> Administrative<br>
&gt;&gt;&gt;&gt; Requests: <a href=3D"https://www.ietf.org/mailman/listinfo=
/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/li=
stinfo/ipv6</a><br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;nvo3 mailing list<br>
&gt;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/nvo3</a><br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">_______________________=
________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org">spring@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/spring</a><br>
</div></div></blockquote></div><br></div>

--001a1140677637ee3c05337d65c8--


From nobody Mon May 23 00:35:19 2016
Return-Path: <talmi@marvell.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 0BF9612D567; Mon, 23 May 2016 00:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 xO9Pt7FwYQnR; Mon, 23 May 2016 00:35:10 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (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 82A9812B032; Mon, 23 May 2016 00:35:10 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4N7VJ1v017327; Mon, 23 May 2016 00:35:09 -0700
Received: from il-exch02.marvell.com ([199.203.130.102]) by mx0b-0016f401.pphosted.com with ESMTP id 232q6e4vap-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 23 May 2016 00:35:08 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH02.marvell.com (10.4.102.221) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 23 May 2016 10:35:05 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 23 May 2016 10:35:05 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: Robert Raszuk <robert@raszuk.net>
Subject: RE: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMThJCvw5mf6XUe954CmH3IV2Z/GIJVA
Date: Mon, 23 May 2016 07:35:04 +0000
Message-ID: <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com>
In-Reply-To: <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@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
x-originating-ip: [10.4.102.210]
Content-Type: multipart/alternative; boundary="_000_bb99730deb8348bcac4f5c433e88d435ILEXCH02marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-23_02:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605230091
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jYPxxl-kNfRyrRrJ_NmMvs2lcMs>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 07:35:17 -0000

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

SGkgUm9iZXJ0LA0KDQoNCj4gV2hlcmUgc2F5IGluIGRyYWZ0IGRyYWZ0LXF1aW5uLXZ4bGFuLWdw
ZSBkbyB5b3Ugc2VlIHN1Y2ggc3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkNCj4gdGhhdCB2NiBO
eHRIZHIgbXVzdCBiZSBvbmx5IGVxdWFsIHRvIDE3IChVRFApIGFuZCBub3QgYmUgYSBwb2ludGVy
IHRvIGFueSBvdGhlciB0eXBlDQo+IG9mIGV4dGVuc2lvbiBoZWFkZXIgZnVydGhlciBmb2xsb3dl
ZCBieSBVRFAgPw0KDQoNClRoZSBmb2xsb3dpbmcgdGV4dCBpcyBmcm9tIEZpZ3VyZSA0IGluIGRy
YWZ0LWlldGYtbnZvMy12eGxhbi1ncGU6DQoNCiAgICAgIE91dGVyIElQdjYgSGVhZGVyOg0KICAg
ICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSsNCiAgICAgIHxWZXJzaW9ufCBUcmFmZmljIENsYXNzIHwgICAgICAgICAgIEZs
b3cgTGFiZWwgICAgICAgICAgICAgICAgICB8DQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAgfCAgICAg
ICAgIFBheWxvYWQgTGVuZ3RoICAgICAgICB8IE54dEhkcj0xNyhVRFApfCAgIEhvcCBMaW1pdCAg
IHwNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rDQogICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KDQoNClRoZXJlIGlzIGEgc2ltaWxh
ciBmaWd1cmUgaW4gZHJhZnQtaWV0Zi1udm8zLWdlbmV2ZS4NCg0KQmVzdCByZWdhcmRzLA0KVGFs
Lg0KDQpGcm9tOiBudm8zIFttYWlsdG86bnZvMy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYg
T2YgUm9iZXJ0IFJhc3p1aw0KU2VudDogTW9uZGF5LCBNYXkgMjMsIDIwMTYgMTA6MjkgQU0NClRv
OiBUYWwgTWl6cmFoaQ0KQ2M6IHNwcmluZ0BpZXRmLm9yZzsgNm1hbiBXRzsgZHJhZnQtaWV0Zi1u
dm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9yZzsgbnZvM0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi02
bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc7IGRyYWZ0LWlldGYtbnZv
My1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc7IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpDQpTdWJq
ZWN0OiBSZTogW252bzNdIFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLWhlYWRlcg0KDQpIaSBUYWwsDQoNCj4gZHJhZnRzIHNlZW0gdG8gaW1w
bHkNCg0KV2hlcmUgc2F5IGluIGRyYWZ0IGRyYWZ0LXF1aW5uLXZ4bGFuLWdwZSBkbyB5b3Ugc2Vl
IHN1Y2ggc3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkgdGhhdCB2NiBOeHRIZHIgbXVzdCBiZSBv
bmx5IGVxdWFsIHRvIDE3IChVRFApIGFuZCBub3QgYmUgYSBwb2ludGVyIHRvIGFueSBvdGhlciB0
eXBlIG9mIGV4dGVuc2lvbiBoZWFkZXIgZnVydGhlciBmb2xsb3dlZCBieSBVRFAgPw0KDQpUaHgs
DQpSLg0KDQoNCk9uIE1vbiwgTWF5IDIzLCAyMDE2IGF0IDc6NTAgQU0sIFRhbCBNaXpyYWhpIDx0
YWxtaUBtYXJ2ZWxsLmNvbTxtYWlsdG86dGFsbWlAbWFydmVsbC5jb20+PiB3cm90ZToNCkRlYXIg
QXV0aG9ycyBvZiBWWExBTi1HUEUgLyBHZW5ldmUsDQoNCkkgYW0gcmVpdGVyYXRpbmcgb24gdGhp
cyBxdWVzdGlvbiwgYXMgSSBoYXZlbid0IHNlZW4gYSByZXNwb25zZSB5ZXQ6DQoNCkhhdmUgeW91
IGNvbnNpZGVyZWQgdGhlIHVzZSBvZiBTZWdtZW50IFJvdXRpbmcgd2l0aCBWWExBTi1HUEUgLyBH
ZW5ldmU/IFRoZSBjdXJyZW50IFZYTEFOLUdQRSAvIEdlbmV2ZSBkcmFmdHMgc2VlbSB0byBpbXBs
eSB0aGF0IElQdjYgZXh0ZW5zaW9uIGhlYWRlcnMgYXJlIGN1cnJlbnRseSBub3Qgc3VwcG9ydGVk
Lg0KDQpUaGFua3MsDQpUYWwuDQoNCg0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5G
cm9tOiBudm8zIFttYWlsdG86bnZvMy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpudm8zLWJvdW5j
ZXNAaWV0Zi5vcmc+XSBPbiBCZWhhbGYgT2YgVGFsIE1penJhaGkNCj5TZW50OiBUdWVzZGF5LCBN
YXkgMTcsIDIwMTYgMTI6MDkgUE0NCj5UbzogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSk7IFRv
bSBIZXJiZXJ0OyBkcmFmdC1pZXRmLW52bzMtDQo+Z2VuZXZlQHRvb2xzLmlldGYub3JnPG1haWx0
bzpnZW5ldmVAdG9vbHMuaWV0Zi5vcmc+OyBkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3Jn
Pg0KPkNjOiBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0BpZXRmLm9yZz47IG52bzNAaWV0
Zi5vcmc8bWFpbHRvOm52bzNAaWV0Zi5vcmc+OyA2bWFuIFdHOyBkcmFmdC1pZXRmLTZtYW4tc2Vn
bWVudC0NCj5yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzxtYWlsdG86cm91dGluZy1oZWFk
ZXJAdG9vbHMuaWV0Zi5vcmc+DQo+U3ViamVjdDogUmU6IFtudm8zXSBbc3ByaW5nXSBMNCBDaGVj
a3N1bSBhbmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtDQo+cm91dGluZy1oZWFkZXINCj4NCj5T
dGVmYW5vLA0KPg0KPklmIEkgdW5kZXJzdGFuZCB5b3VyIHBvaW50IGNvcnJlY3RseToNCj5JUHY2
IHNlZ21lbnQgcm91dGluZyBkb2VzIG5vdCB3b3JrIHdpdGggVlhMQU4gLyBWWExBTi1HUEUgLyBH
ZW5ldmUsIHNpbmNlDQo+dGhlc2UgZW5jYXBzdWxhdGlvbnMgZG8gbm90IGN1cnJlbnRseSBhbGxv
dyB0aGUgdXNlIG9mIElQdjYgZXh0ZW5zaW9uDQo+aGVhZGVycy4NCj4NCj5JIHdvbmRlciBpZiB0
aGUgYXV0aG9ycyBvZiBWWExBTi1HUEUgYW5kIEdlbmV2ZSBoYXZlIGNvbnNpZGVyZWQgdGhlIHVz
ZSBvZg0KPnNlZ21lbnQgcm91dGluZy4NCj4NCj5UaGFua3MsDQo+VGFsLg0KPg0KPg0KPg0KPj4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2
aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbTxtYWlsdG86c3ByZXZpZGlAY2lzY28uY29t
Pl0NCj4+U2VudDogVHVlc2RheSwgTWF5IDE3LCAyMDE2IDEwOjQxIEFNDQo+PlRvOiBUb20gSGVy
YmVydA0KPj5DYzogVGFsIE1penJhaGk7IDZtYW4gV0c7IHNwcmluZ0BpZXRmLm9yZzxtYWlsdG86
c3ByaW5nQGlldGYub3JnPjsNCj4+ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVh
ZGVyQHRvb2xzLmlldGYub3JnPG1haWx0bzpoZWFkZXJAdG9vbHMuaWV0Zi5vcmc+DQo+PlN1Ympl
Y3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy0NCj4+aGVhZGVyDQo+Pg0KPj4NCj4+PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDc6MTAg
UE0sIFRvbSBIZXJiZXJ0IDx0b21AaGVyYmVydGxhbmQuY29tPG1haWx0bzp0b21AaGVyYmVydGxh
bmQuY29tPj4NCj53cm90ZToNCj4+Pg0KPj4+IE9uIE1vbiwgTWF5IDE2LCAyMDE2IGF0IDQ6MzIg
QU0sIFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbTxtYWlsdG86dGFsbWlAbWFydmVsbC5j
b20+Pg0KPj53cm90ZToNCj4+Pj4+IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLg0K
Pj4+Pj4NCj4+Pj4+IHMuDQo+Pj4+DQo+Pj4+IFJpZ2h0LiBIb3dldmVyLCBpdCBhcHBlYXJzIHRo
YXQgYXQgbGVhc3QgaW4gc29tZSBjYXNlcyBhIFZYTEFOIFZURVANCj4+Pj4gd2lsbA0KPj51c2Ug
U1IuIEl0IGNlcnRhaW5seSBtYXkgYmUgdGhlIGNhc2UgaW4gU0ZDIHVzZSBjYXNlcyAoc2VlIFNl
Y3Rpb24gMi4zDQo+PmluIGRyYWZ0LSBpZXRmLXNwcmluZy1pcHY2LXVzZS1jYXNlcykuDQo+Pj4+
DQo+Pj4NCj4+PiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBtZW50aW9u
cyB0aGF0IHRoZSBwYWNrZXQgaXMNCj4+PiBlbmNhcHN1bGF0ZWQNCj4+DQo+Pg0KPj5pbnRvIGFu
IG91dGVyIGlwdjYgaGVhZGVyIHdoaWNoIG1ha2VzIGl0IGEgbGF5ZXItMyBlbmNhcC4NCj4+DQo+
Pg0KPj4+ICwgYnV0IEkgZG9uJ3QgdGhpbmsgaXQgaXMgZXhwbGljaXQgYXMgdG8gZXhhY3QgZW5j
YXBzdWxhdGlvbiBmb3JtYXQNCj4+PiAoSSBzdXBwb3NlIHNpbXBsZSBpcDZpcDYgaXMgaW1wbGll
ZCkuDQo+Pg0KPj4NCj4+c2VlIHNlY3Rpb24gMi4yDQo+Pg0KPj4NCj4+PiBCdXQsIGl0DQo+Pj4g
c2VlbXMgbGlrZSBhbnkgb2Ygc2V2ZXJhbCBlbmNhcHN1bGF0aW9uIHRlY2huaXF1ZXMgY291bGQg
d29yayAoVlhMQU4sDQo+Pg0KPj4NCj4+SSBoYXZlIHNvbWUgcHJvYmxlbXMgdG8gdW5kZXJzdGFu
ZCB3aGVyZSB0byBmaXQgYW4gZXh0ZW5zaW9uIGhlYWRlcg0KPj5pbnRvIGEgdnhsYW4gZW5jYXDi
gKYNCj4+DQo+Pg0KPj4+IEdSRS9JUCwgRVNQL0lQLCBHVUUsIGZvbyBvdmVyIFVEUCwgZXRjLikg
YW5kIGlmIGEgZGV2aWNlIHRoYXQgd2FudHMNCj4+PiB0byBkbyBTUiBpcyBhbHJlYWR5IGRvaW5n
IHR1bm5lbGluZyBpdCBzZWVtcyByZWFzb25hYmxlIHRvIG1lIHRvIG9ubHkNCj4+PiBoYXZlIG9u
ZSBsYXllciBvZiBlbmNhcHN1bGF0aW9uLiBNYXliZSB0aGlzIHNob3VsZCBiZSBjbGFyaWZpZWQg
aW4NCj4+PiB0aGUgZHJhZnQ/DQo+Pg0KPj4NCj4+dGhlIGRyYWZ0IGlzIGFib3V0IElQdjYgZXh0
ZW5zaW9uIGhlYWRlciBhbmQgbW9yZSBwcmVjaXNlbHkgYSBuZXcgdHlwZQ0KPj5vZiB0aGUgcm91
dGluZyBleHRlbnNpb24gaGVhZGVyIGRlZmluZWQgaW4gcmZjMjQ2MC4gVGhhdOKAmXMgdGhlIGNv
bnRleHQuDQo+Pg0KPj4NCj4+cy4NCj4+DQo+Pg0KPj4NCj4+DQo+Pj4NCj4+PiBUb20NCj4+Pg0K
Pj4+Pg0KPj4+Pg0KPj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+IEZyb206
IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tPG1h
aWx0bzpzcHJldmlkaUBjaXNjby5jb20+XQ0KPj4+Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYsIDIw
MTYgMjoyNCBQTQ0KPj4+Pj4gVG86IFRhbCBNaXpyYWhpDQo+Pj4+PiBDYzogT2xlIFRyw7hhbjsN
Cj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYu
b3JnPG1haWx0bzpkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5p
ZXRmLm9yZz47DQo+Pj4+PiBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0BpZXRmLm9yZz47
IDZtYW4gV0cNCj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQNCj4+
Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+Pj4NCj4+Pj4+
DQo+Pj4+Pj4gT24gTWF5IDE2LCAyMDE2LCBhdCAxOjE5IFBNLCBUYWwgTWl6cmFoaSA8dGFsbWlA
bWFydmVsbC5jb208bWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tPj4gd3JvdGU6DQo+Pj4+Pj4NCj4+
Pj4+PiBIaSBTdGVmYW5vLA0KPj4+Pj4+DQo+Pj4+Pj4gVGhhbmtzIGFnYWluIGZvciB0aGUgcHJv
bXB0IHJlc3BvbnNlLg0KPj4+Pj4+DQo+Pj4+Pj4+IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBi
eSB0aGUgaW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uDQo+Pj4+Pj4+IFRoaXMgaXMgZG9u
ZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyDQo+Pj4+Pj4+IChhZGRp
dGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDMNCj4+Pj4+
Pj4gZW5jYXBzdWxhdGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhl
ICBwYWNrZXQNCj4+Pj4+Pj4gbGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fwc3Vs
YXRpb24gIChpbmNsdWRpbmcgdGhlIFNSSCkNCj4+Pj4+Pj4gaXMgcmVtb3ZlZCBhbmQgdGhlIHBh
Y2tldCBjb250aW51ZXMgIGl0cyBqb3VybmV5IGxpa2Ugbm90aGluZw0KPmhhcHBlbmVkLg0KPj4+
Pj4+DQo+Pj4+Pj4gU28gVlhMQU4gaXMgb2ZmIHRoZSB0YWJsZT8NCj4+Pj4+DQo+Pj4+Pg0KPj4+
Pj4gaXTigJlzIGFsbCBhYm91dCBJUCwgbm90IGxheWVyLTIuDQo+Pj4+Pg0KPj4+Pj4gcy4NCj4+
Pj4+DQo+Pj4+Pg0KPj4+Pj4+IEl0IHdvdWxkIGJlIHdvcnRod2hpbGUgdG8gY2xhcmlmeSB0aGlz
IGluIHRoZSBkcmFmdC4gSWYgeW91IGhhdmUgYQ0KPj4+Pj4+IHNwZWNpZmljDQo+Pj4+PiBlbmNh
cHN1bGF0aW9uIGluIG1pbmQsIGl0IHdvdWxkIGJlIGdyZWF0IGlmIHRoZSBkcmFmdCB3b3VsZCBz
cGVjaWZ5IGl0Lg0KPj4+Pj4+DQo+Pj4+Pj4gVGhhbmtzLA0KPj4+Pj4+IFRhbC4NCj4+Pj4+Pg0K
Pj4+Pj4+DQo+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+Pj4+IEZyb206
IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tPG1h
aWx0bzpzcHJldmlkaUBjaXNjby5jb20+XQ0KPj4+Pj4+PiBTZW50OiBNb25kYXksIE1heSAxNiwg
MjAxNiAyOjEzIFBNDQo+Pj4+Pj4+IFRvOiBUYWwgTWl6cmFoaQ0KPj4+Pj4+PiBDYzogT2xlIFRy
w7hhbjsNCj4+Pj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9v
bHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVy
QHRvb2xzLmlldGYub3JnPjsNCj4+Pj4+Pj4gc3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdA
aWV0Zi5vcmc+OyA2bWFuIFdHDQo+Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVj
a3N1bSBhbmQNCj4+Pj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVhZGVy
DQo+Pj4+Pj4+DQo+Pj4+Pj4+IEhpLA0KPj4+Pj4+Pg0KPj4+Pj4+PiBPbiBNYXkgMTYsIDIwMTYs
IGF0IDExOjA0IEFNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFydmVsbC5jb208bWFpbHRvOnRhbG1p
QG1hcnZlbGwuY29tPj4NCj4+d3JvdGU6DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gSGkgU3RlZmFubywN
Cj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBUaGFua3MgZm9yIHRoZSByZXNwb25zZXMuDQo+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+IGV4YWN0bHkuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBNb3Jlb3ZlciwgZHJhZnQt
aWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIgYXNzdW1lcw0KPj4+Pj4+Pj4+IGVuY2Fw
c3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS4NCj4+Pj4+
Pj4+Pg0KPj4+Pj4+Pj4+IHMuDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gVHdvIHF1ZXN0aW9uczoNCj4+
Pj4+Pj4+IDEuIFdoYXQgaWYgdGhlIGVuY2Fwc3VsYXRpb24gaXMgVlhMQU4/IEw0IHdvdWxkIHN0
aWxsIGJlDQo+Pj4+Pj4+PiBpbnZvbHZlZCwNCj4+cmlnaHQ/DQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+
Pj4+Pj4+IFNlZSBiZWxvdy4NCj4+Pj4+Pj4NCj4+Pj4+Pj4NCj4+Pj4+Pj4+IDIuIFdoZW4geW91
IHNheSAnYXNzdW1lcyBlbmNhcHN1bGF0aW9uJywgZG9lcyBpdCBtZWFuIHRoYXQgYQ0KPj4+Pj4+
Pj4gaG9zdCBjYW5ub3QNCj4+Pj4+Pj4gc2VuZCBhbiBJUHY2IHBhY2tldCB3aXRoIGFuIFNSSD8g
VGhlIGN1cnJlbnQgZHJhZnQgc2F5czoNCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBBIFNvdXJjZSBTUiBO
b2RlIGNhbiBiZSBhbnkgbm9kZSBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tldCB3aXRoDQo+Pj4+
Pj4+PiBpdHMNCj4+Pj4+Pj4+IElQdjYgYW5kIFNlZ21lbnQgUm91dGluZyBIZWFkZXJzLiAgVGhp
cyBpbmNsdWRlIGVpdGhlcjoNCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiAgICBBIGhvc3Qgb3JpZ2luYXRp
bmcgYW4gSVB2NiBwYWNrZXQuDQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gICAgQW4gU1IgZG9tYWluIGlu
Z3Jlc3Mgcm91dGVyIGVuY2Fwc3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldA0KPj4+Pj4+
Pj4gICAgaW50byBhbiBvdXRlciBJUHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguDQo+Pj4+
Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBXaWxsIGFwcHJlY2lhdGUgaWYgeW91
IGNhbiBjbGFyaWZ5IHRoYXQuDQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+IG9rLCB0d28gY2Fz
ZXM6DQo+Pj4+Pj4+DQo+Pj4+Pj4+IDEuIHRoZSBTUkggaXMgaW5zZXJ0ZWQgYXQgdGhlIHNvdXJj
ZS4NCj4+Pj4+Pj4gdGhlIHNvdXJjZSBvcmlnaW5hdGVzIHRoZSBwYWNrZXQsIHRoZSBpcHY2IGhl
YWRlciBhbmQgIHRoZSBTUkguDQo+Pj4+Pj4+IFRoZSBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tz
dW0gdGFraW5nIGludG8gIGFjY291bnQgdGhlIHdob2xlDQo+PklQdjYrU1JILg0KPj4+Pj4+PiBI
ZXJlLCB0aGVyZXPigJkgbm90aGluZyBuZXcgIGNvbXBhcmVkIHRvIHJmYzI0NjAuDQo+Pj4+Pj4+
DQo+Pj4+Pj4+IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBieSB0aGUgaW5ncmVzcyBub2RlIG9m
IHRoZSBTUiBkb21haW4uDQo+Pj4+Pj4+IFRoaXMgaXMgZG9uZSBieSBlbmNhcHN1bGF0aW5nIHRo
ZSBwYWNrZXQgaW50byBhIG91dGVyDQo+Pj4+Pj4+IChhZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBm
b2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDMNCj4+Pj4+Pj4gZW5jYXBzdWxhdGlvbiBhbmQg
bm8gTDQgY2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlICBwYWNrZXQNCj4+Pj4+Pj4gbGVh
dmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fwc3VsYXRpb24gIChpbmNsdWRpbmcgdGhl
IFNSSCkNCj4+Pj4+Pj4gaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51ZXMgIGl0cyBq
b3VybmV5IGxpa2Ugbm90aGluZw0KPmhhcHBlbmVkLg0KPj4+Pj4+Pg0KPj4+Pj4+PiBzLg0KPj4+
Pj4+Pg0KPj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IFRoYW5rcywNCj4+Pj4+Pj4+IFRhbC4N
Cj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+Pj4+
PiBGcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2Nv
LmNvbTxtYWlsdG86c3ByZXZpZGlAY2lzY28uY29tPl0NCj4+Pj4+Pj4+PiBTZW50OiBNb25kYXks
IE1heSAxNiwgMjAxNiAxMTo1OSBBTQ0KPj4+Pj4+Pj4+IFRvOiBPbGUgVHLDuGFuOyBUYWwgTWl6
cmFoaQ0KPj4+Pj4+Pj4+IENjOiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRl
ckB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1o
ZWFkZXJAdG9vbHMuaWV0Zi5vcmc+Ow0KPj4+Pj4+Pj4+IHNwcmluZ0BpZXRmLm9yZzxtYWlsdG86
c3ByaW5nQGlldGYub3JnPjsgNm1hbiBXRw0KPj4+Pj4+Pj4+IFN1YmplY3Q6IFJlOiBbc3ByaW5n
XSBMNCBDaGVja3N1bSBhbmQNCj4+Pj4+Pj4+PiBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0
aW5nLSBoZWFkZXINCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IE9uIE1heSAxNSwg
MjAxNiwgYXQgODowNiBQTSwgb3Ryb2FuQGVtcGxveWVlcy5vcmc8bWFpbHRvOm90cm9hbkBlbXBs
b3llZXMub3JnPiB3cm90ZToNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4gVGFsLA0KPj4+Pj4+Pj4+
Pg0KPj4+Pj4+Pj4+Pj4gW0Fwb2xvZ2llcyBpZiB0aGlzIGlzc3VlIGhhcyBiZWVuIGRpc2N1c3Nl
ZCBiZWZvcmUuXQ0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+IEFjY29yZGluZyB0byBkcmFmdC1p
ZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciwgYW4g4oCYU1INCj4+Pj4+Pj4+Pj4+IFNl
Z21lbnQNCj4+Pj4+Pj4+PiBFbmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9u
IElQIGFkZHJlc3MuDQo+Pj4+Pj4+Pj4+PiBUaGVyZWZvcmUsIGl0IG11c3QgYWxzbyB1cGRhdGUg
dGhlIExheWVyIDQgQ2hlY2tzdW0sIHJpZ2h0Pw0KPj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4+IEkg
d29uZGVyIGlmIHRoZXJlIGlzIGFuIHVwcGVyIGJvdW5kIG9uIHRoZSBzaXplIG9mIHRoZSBTUkgu
DQo+Pj4+Pj4+Pj4+PiBPdGhlcndpc2UsIHRoZQ0KPj4+Pj4+Pj4+IEw0IENoZWNrc3VtIG1heSBi
ZSBsb2NhdGVkIGluIGEgcHJldHR5IGRlZXAgbG9jYXRpb24uDQo+Pj4+Pj4+Pj4+PiBTcGVha2lu
ZyBmcm9tIGEgY2hpcCB2ZW5kb3LigJlzIHBlcnNwZWN0aXZlIHRoaXMgbWF5IGJlIGEgcHJvYmxl
bS4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4gRnJvbSBSRkMyNDYwLCBSSDA6DQo+Pj4+Pj4+Pj4+
DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+ICAgbyAgSWYgdGhlIElQdjYgcGFja2V0IGNvbnRhaW5z
IGEgUm91dGluZyBoZWFkZXIsIHRoZSBEZXN0aW5hdGlvbg0KPj4+Pj4+Pj4+PiAgICAgIEFkZHJl
c3MgdXNlZCBpbiB0aGUgcHNldWRvLWhlYWRlciBpcyB0aGF0IG9mIHRoZSBmaW5hbA0KPj4+Pj4+
Pj4+PiAgICAgIGRlc3RpbmF0aW9uLiAgQXQgdGhlIG9yaWdpbmF0aW5nIG5vZGUsIHRoYXQgYWRk
cmVzcyB3aWxsIGJlIGluDQo+Pj4+Pj4+Pj4+ICAgICAgdGhlIGxhc3QgZWxlbWVudCBvZiB0aGUg
Um91dGluZyBoZWFkZXI7IGF0IHRoZSByZWNpcGllbnQocyksDQo+Pj4+Pj4+Pj4+ICAgICAgdGhh
dCBhZGRyZXNzIHdpbGwgYmUgaW4gdGhlIERlc3RpbmF0aW9uIEFkZHJlc3MgZmllbGQgb2YgdGhl
DQo+Pj4+Pj4+Pj4+ICAgICAgSVB2NiBoZWFkZXIuDQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IEkg
d291bGQgZXhwZWN0IFNSIHdvdWxkIHdvcmsgdGhlIHNhbWUuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+
Pg0KPj4+Pj4+Pj4+IGV4YWN0bHkuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+PiBNb3Jlb3ZlciwgZHJh
ZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIgYXNzdW1lcw0KPj4+Pj4+Pj4+IGVu
Y2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS4NCj4+
Pj4+Pj4+Pg0KPj4+Pj4+Pj4+IHMuDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+PiBDaGVlcnMsDQo+Pj4+Pj4+Pj4+IE9sZQ0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4N
Cj4+Pj4+Pg0KPj4+Pg0KPj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4+PiBJRVRGIElQdjYgd29ya2luZyBn
cm91cCBtYWlsaW5nIGxpc3QgaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4gQWRt
aW5pc3RyYXRpdmUNCj4+Pj4gUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vaXB2Ng0KPj4+PiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+bnZvMyBtYWlsaW5nIGxpc3QNCj5udm8zQGll
dGYub3JnPG1haWx0bzpudm8zQGlldGYub3JnPg0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbnZvMw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCnNwcmluZyBtYWlsaW5nIGxpc3QNCnNwcmluZ0BpZXRmLm9yZzxtYWlsdG86c3By
aW5nQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zcHJp
bmcNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4w
cHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRT
ZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVk
ZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0t
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0K
PG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+
PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxp
bms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIFJvYmVy
dCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mZ3Q7PC9z
cGFuPg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPldoZXJlIHNh
eSBpbiBkcmFmdCBkcmFmdC1xdWlubi12eGxhbi1ncGUgZG8geW91IHNlZSBzdWNoIHN0YXRlbWVu
dCB0aGF0IHdvdWxkIGltcGx5DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jmd0OyB0
aGF0IHY2IE54dEhkciBtdXN0IGJlIG9ubHkgZXF1YWwgdG8gMTcgKFVEUCkgYW5kIG5vdCBiZSBh
IHBvaW50ZXIgdG8gYW55IG90aGVyIHR5cGUNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij4mZ3Q7IG9mIGV4dGVuc2lvbiBoZWFkZXIgZnVydGhlciBmb2xsb3dlZCBieSBVRFAgPzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoZSBmb2xsb3dpbmcg
dGV4dCBpcyBmcm9tIEZpZ3VyZSA0IGluIGRyYWZ0LWlldGYtbnZvMy12eGxhbi1ncGU6PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBPdXRlciBJUHY2IEhlYWRlcjo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMUY0OTdE
Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfFZlcnNpb258IFRyYWZmaWMgQ2xhc3Mg
fCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBGbG93IExhYmVsJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IHw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0Mzs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgfCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBQYXls
b2FkIExlbmd0aCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8IE54
dEhkcj0xNyhVRFApfCZuYnNwOyZuYnNwOyBIb3AgTGltaXQmbmJzcDsmbmJzcDsgfDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmIzQzOy0mIzQzOy0mIzQzOy0mIzQz
Oy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0m
IzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQz
Oy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0m
IzQzOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwO3w8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj5UaGVyZSBpcyBhIHNpbWlsYXIgZmlndXJlIGluIGRyYWZ0LWlldGYtbnZv
My1nZW5ldmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPlRhbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
Ymx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBw
dCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4g
bnZvMyBbbWFpbHRvOm52bzMtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+
Um9iZXJ0IFJhc3p1azxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIE1heSAyMywgMjAxNiAxMDoy
OSBBTTxicj4NCjxiPlRvOjwvYj4gVGFsIE1penJhaGk8YnI+DQo8Yj5DYzo8L2I+IHNwcmluZ0Bp
ZXRmLm9yZzsgNm1hbiBXRzsgZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9y
ZzsgbnZvM0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJA
dG9vbHMuaWV0Zi5vcmc7IGRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc7IFN0
ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbnZvM10g
W3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmct
aGVhZGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+SGkgVGFsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+Jmd0OyZuYnNwOzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPmRyYWZ0cyBzZWVt
IHRvIGltcGx5PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PldoZXJlIHNheSBpbiBkcmFmdCZuYnNwO2RyYWZ0LXF1aW5uLXZ4bGFuLWdwZSBkbyB5b3Ugc2Vl
IHN1Y2ggc3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkgdGhhdCB2NiBOeHRIZHIgbXVzdCBiZSBv
bmx5IGVxdWFsIHRvIDE3IChVRFApIGFuZCBub3QgYmUgYSBwb2ludGVyIHRvIGFueSBvdGhlciB0
eXBlIG9mIGV4dGVuc2lvbiBoZWFkZXINCiBmdXJ0aGVyIGZvbGxvd2VkIGJ5IFVEUCA/Jm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UaHgsPGJyPg0KUi48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5PbiBNb24sIE1heSAyMywgMjAxNiBhdCA3OjUwIEFNLCBUYWwgTWl6cmFoaSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGFs
bWlAbWFydmVsbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkRlYXIgQXV0aG9ycyBvZiBWWExBTi1HUEUgLyBHZW5ldmUsPGJyPg0KPGJyPg0K
SSBhbSByZWl0ZXJhdGluZyBvbiB0aGlzIHF1ZXN0aW9uLCBhcyBJIGhhdmVuJ3Qgc2VlbiBhIHJl
c3BvbnNlIHlldDo8YnI+DQo8YnI+DQpIYXZlIHlvdSBjb25zaWRlcmVkIHRoZSB1c2Ugb2YgU2Vn
bWVudCBSb3V0aW5nIHdpdGggVlhMQU4tR1BFIC8gR2VuZXZlPyBUaGUgY3VycmVudCBWWExBTi1H
UEUgLyBHZW5ldmUgZHJhZnRzIHNlZW0gdG8gaW1wbHkgdGhhdCBJUHY2IGV4dGVuc2lvbiBoZWFk
ZXJzIGFyZSBjdXJyZW50bHkgbm90IHN1cHBvcnRlZC48YnI+DQo8YnI+DQpUaGFua3MsPGJyPg0K
VGFsLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
YnI+DQo8YnI+DQo8YnI+DQomZ3Q7LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7
RnJvbTogbnZvMyBbbWFpbHRvOjxhIGhyZWY9Im1haWx0bzpudm8zLWJvdW5jZXNAaWV0Zi5vcmci
Pm52bzMtYm91bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBUYWwgTWl6cmFoaTxicj4N
CiZndDtTZW50OiBUdWVzZGF5LCBNYXkgMTcsIDIwMTYgMTI6MDkgUE08YnI+DQomZ3Q7VG86IFN0
ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpOyBUb20gSGVyYmVydDsgZHJhZnQtaWV0Zi1udm8zLTxi
cj4NCiZndDs8YSBocmVmPSJtYWlsdG86Z2VuZXZlQHRvb2xzLmlldGYub3JnIj5nZW5ldmVAdG9v
bHMuaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdw
ZUB0b29scy5pZXRmLm9yZyI+DQpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYu
b3JnPC9hPjxicj4NCiZndDtDYzogPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0BpZXRmLm9yZyI+c3By
aW5nQGlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOm52bzNAaWV0Zi5vcmciPg0KbnZvM0Bp
ZXRmLm9yZzwvYT47IDZtYW4gV0c7IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LTxicj4NCiZndDs8
YSBocmVmPSJtYWlsdG86cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciPnJvdXRpbmctaGVh
ZGVyQHRvb2xzLmlldGYub3JnPC9hPjxicj4NCiZndDtTdWJqZWN0OiBSZTogW252bzNdIFtzcHJp
bmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC08YnI+DQomZ3Q7cm91
dGluZy1oZWFkZXI8YnI+DQomZ3Q7PGJyPg0KJmd0O1N0ZWZhbm8sPGJyPg0KJmd0Ozxicj4NCiZn
dDtJZiBJIHVuZGVyc3RhbmQgeW91ciBwb2ludCBjb3JyZWN0bHk6PGJyPg0KJmd0O0lQdjYgc2Vn
bWVudCByb3V0aW5nIGRvZXMgbm90IHdvcmsgd2l0aCBWWExBTiAvIFZYTEFOLUdQRSAvIEdlbmV2
ZSwgc2luY2U8YnI+DQomZ3Q7dGhlc2UgZW5jYXBzdWxhdGlvbnMgZG8gbm90IGN1cnJlbnRseSBh
bGxvdyB0aGUgdXNlIG9mIElQdjYgZXh0ZW5zaW9uPGJyPg0KJmd0O2hlYWRlcnMuPGJyPg0KJmd0
Ozxicj4NCiZndDtJIHdvbmRlciBpZiB0aGUgYXV0aG9ycyBvZiBWWExBTi1HUEUgYW5kIEdlbmV2
ZSBoYXZlIGNvbnNpZGVyZWQgdGhlIHVzZSBvZjxicj4NCiZndDtzZWdtZW50IHJvdXRpbmcuPGJy
Pg0KJmd0Ozxicj4NCiZndDtUaGFua3MsPGJyPg0KJmd0O1RhbC48YnI+DQomZ3Q7PGJyPg0KJmd0
Ozxicj4NCiZndDs8YnI+DQomZ3Q7Jmd0Oy0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0K
Jmd0OyZndDtGcm9tOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOjxhIGhyZWY9
Im1haWx0bzpzcHJldmlkaUBjaXNjby5jb20iPnNwcmV2aWRpQGNpc2NvLmNvbTwvYT5dPGJyPg0K
Jmd0OyZndDtTZW50OiBUdWVzZGF5LCBNYXkgMTcsIDIwMTYgMTA6NDEgQU08YnI+DQomZ3Q7Jmd0
O1RvOiBUb20gSGVyYmVydDxicj4NCiZndDsmZ3Q7Q2M6IFRhbCBNaXpyYWhpOyA2bWFuIFdHOyA8
YSBocmVmPSJtYWlsdG86c3ByaW5nQGlldGYub3JnIj5zcHJpbmdAaWV0Zi5vcmc8L2E+Ozxicj4N
CiZndDsmZ3Q7ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gPGEgaHJlZj0ibWFpbHRv
OmhlYWRlckB0b29scy5pZXRmLm9yZyI+aGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjxicj4NCiZn
dDsmZ3Q7U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZt
YW4tc2VnbWVudC1yb3V0aW5nLTxicj4NCiZndDsmZ3Q7aGVhZGVyPGJyPg0KJmd0OyZndDs8YnI+
DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDc6MTAgUE0s
IFRvbSBIZXJiZXJ0ICZsdDs8YSBocmVmPSJtYWlsdG86dG9tQGhlcmJlcnRsYW5kLmNvbSI+dG9t
QGhlcmJlcnRsYW5kLmNvbTwvYT4mZ3Q7PGJyPg0KJmd0O3dyb3RlOjxicj4NCiZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyBPbiBNb24sIE1heSAxNiwgMjAxNiBhdCA0OjMyIEFNLCBUYWwg
TWl6cmFoaSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tIj50YWxtaUBtYXJ2
ZWxsLmNvbTwvYT4mZ3Q7PGJyPg0KJmd0OyZndDt3cm90ZTo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBpdOKAmXMgYWxsIGFib3V0IElQLCBub3QgbGF5ZXItMi48YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHMuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgUmlnaHQuIEhvd2V2ZXIsIGl0IGFwcGVhcnMgdGhhdCBh
dCBsZWFzdCBpbiBzb21lIGNhc2VzIGEgVlhMQU4gVlRFUDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsg
d2lsbDxicj4NCiZndDsmZ3Q7dXNlIFNSLiBJdCBjZXJ0YWlubHkgbWF5IGJlIHRoZSBjYXNlIGlu
IFNGQyB1c2UgY2FzZXMgKHNlZSBTZWN0aW9uIDIuMzxicj4NCiZndDsmZ3Q7aW4gZHJhZnQtIGll
dGYtc3ByaW5nLWlwdjYtdXNlLWNhc2VzKS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRp
bmctaGVhZGVyIG1lbnRpb25zIHRoYXQgdGhlIHBhY2tldCBpczxicj4NCiZndDsmZ3Q7Jmd0OyBl
bmNhcHN1bGF0ZWQ8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDtpbnRv
IGFuIG91dGVyIGlwdjYgaGVhZGVyIHdoaWNoIG1ha2VzIGl0IGEgbGF5ZXItMyBlbmNhcC48YnI+
DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7ICwgYnV0IEkgZG9uJ3Qg
dGhpbmsgaXQgaXMgZXhwbGljaXQgYXMgdG8gZXhhY3QgZW5jYXBzdWxhdGlvbiBmb3JtYXQ8YnI+
DQomZ3Q7Jmd0OyZndDsgKEkgc3VwcG9zZSBzaW1wbGUgaXA2aXA2IGlzIGltcGxpZWQpLjxicj4N
CiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0O3NlZSBzZWN0aW9uIDIuMjxicj4N
CiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgQnV0LCBpdDxicj4NCiZn
dDsmZ3Q7Jmd0OyBzZWVtcyBsaWtlIGFueSBvZiBzZXZlcmFsIGVuY2Fwc3VsYXRpb24gdGVjaG5p
cXVlcyBjb3VsZCB3b3JrIChWWExBTiw8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDtJIGhhdmUgc29tZSBwcm9ibGVtcyB0byB1bmRlcnN0YW5kIHdoZXJlIHRvIGZpdCBh
biBleHRlbnNpb24gaGVhZGVyPGJyPg0KJmd0OyZndDtpbnRvIGEgdnhsYW4gZW5jYXDigKY8YnI+
DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IEdSRS9JUCwgRVNQL0lQ
LCBHVUUsIGZvbyBvdmVyIFVEUCwgZXRjLikgYW5kIGlmIGEgZGV2aWNlIHRoYXQgd2FudHM8YnI+
DQomZ3Q7Jmd0OyZndDsgdG8gZG8gU1IgaXMgYWxyZWFkeSBkb2luZyB0dW5uZWxpbmcgaXQgc2Vl
bXMgcmVhc29uYWJsZSB0byBtZSB0byBvbmx5PGJyPg0KJmd0OyZndDsmZ3Q7IGhhdmUgb25lIGxh
eWVyIG9mIGVuY2Fwc3VsYXRpb24uIE1heWJlIHRoaXMgc2hvdWxkIGJlIGNsYXJpZmllZCBpbjxi
cj4NCiZndDsmZ3Q7Jmd0OyB0aGUgZHJhZnQ/PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7dGhlIGRyYWZ0IGlzIGFib3V0IElQdjYgZXh0ZW5zaW9uIGhlYWRlciBhbmQg
bW9yZSBwcmVjaXNlbHkgYSBuZXcgdHlwZTxicj4NCiZndDsmZ3Q7b2YgdGhlIHJvdXRpbmcgZXh0
ZW5zaW9uIGhlYWRlciBkZWZpbmVkIGluIHJmYzI0NjAuIFRoYXTigJlzIHRoZSBjb250ZXh0Ljxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0O3MuPGJyPg0KJmd0OyZndDs8
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsgVG9tPGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAt
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEZyb206
IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86PGEgaHJlZj0ibWFpbHRvOnNwcmV2
aWRpQGNpc2NvLmNvbSI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBTZW50OiBNb25kYXksIE1heSAxNiwgMjAxNiAyOjI0IFBNPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsgVG86IFRhbCBNaXpyYWhpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6
IE9sZSBUcsO4YW47PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOmRy
YWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnIj5kcmFm
dC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzwvYT47PGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0BpZXRmLm9yZyI+
c3ByaW5nQGlldGYub3JnPC9hPjsgNm1hbiBXRzxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFN1
YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQ8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXI8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7IE9uIE1heSAxNiwgMjAxNiwgYXQgMToxOSBQTSwgVGFsIE1penJhaGkgJmx0
OzxhIGhyZWY9Im1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbSI+dGFsbWlAbWFydmVsbC5jb208L2E+
Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgSGkgU3RlZmFubyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhhbmtzIGFnYWluIGZvciB0aGUgcHJvbXB0
IHJlc3BvbnNlLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsgMi4gdGhlIFNSSCBpcyBvcmlnaW5hdGVkIGJ5IHRoZSBpbmdyZXNz
IG5vZGUgb2YgdGhlIFNSIGRvbWFpbi48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
IFRoaXMgaXMgZG9uZSBieSBlbmNhcHN1bGF0aW5nIHRoZSBwYWNrZXQgaW50byBhIG91dGVyPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAoYWRkaXRpb25hbCkgaXB2NiBoZWFkZXIg
Zm9sbG93ZWQgYnkgYW4gU1JILiBUaGlzIGlzIEwzPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZvbHZlZC4gV2hl
biB0aGUmbmJzcDsgcGFja2V0PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBsZWF2
ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbiZuYnNwOyAoaW5jbHVkaW5n
IHRoZSBTUkgpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBpcyByZW1vdmVkIGFu
ZCB0aGUgcGFja2V0IGNvbnRpbnVlcyZuYnNwOyBpdHMgam91cm5leSBsaWtlIG5vdGhpbmc8YnI+
DQomZ3Q7aGFwcGVuZWQuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IFNvIFZYTEFOIGlzIG9mZiB0aGUgdGFibGU/PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLjxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgcy48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IEl0IHdvdWxkIGJlIHdvcnRod2hpbGUgdG8gY2xhcmlmeSB0aGlzIGluIHRoZSBk
cmFmdC4gSWYgeW91IGhhdmUgYTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBzcGVjaWZp
Yzxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRpb24gaW4gbWluZCwgaXQgd291
bGQgYmUgZ3JlYXQgaWYgdGhlIGRyYWZ0IHdvdWxkIHNwZWNpZnkgaXQuPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRoYW5rcyw8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGFsLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86
PGEgaHJlZj0ibWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbSI+c3ByZXZpZGlAY2lzY28uY29tPC9h
Pl08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFNlbnQ6IE1vbmRheSwgTWF5IDE2
LCAyMDE2IDI6MTMgUE08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRvOiBUYWwg
TWl6cmFoaTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6IE9sZSBUcsO4YW47
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQt
aWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWll
dGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0Zi5v
cmciPnNwcmluZ0BpZXRmLm9yZzwvYT47IDZtYW4gV0c8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQ8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmct
IGhlYWRlcjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IEhpLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IE9uIE1heSAxNiwgMjAxNiwgYXQgMTE6
MDQgQU0sIFRhbCBNaXpyYWhpICZsdDs8YSBocmVmPSJtYWlsdG86dGFsbWlAbWFydmVsbC5jb20i
PnRhbG1pQG1hcnZlbGwuY29tPC9hPiZndDs8YnI+DQomZ3Q7Jmd0O3dyb3RlOjxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsgSGkgU3RlZmFubyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRoYW5rcyBmb3IgdGhlIHJl
c3BvbnNlcy48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBleGFjdGx5Ljxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyBNb3Jlb3ZlciwgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFk
ZXIgYXNzdW1lczxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBlbmNh
cHN1bGF0aW9uIHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHMuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUd28gcXVlc3Rpb25z
Ojxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDEuIFdoYXQgaWYgdGhlIGVu
Y2Fwc3VsYXRpb24gaXMgVlhMQU4/IEw0IHdvdWxkIHN0aWxsIGJlPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgaW52b2x2ZWQsPGJyPg0KJmd0OyZndDtyaWdodD88YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU2VlIGJlbG93Ljxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgMi4gV2hlbiB5b3Ugc2F5
ICdhc3N1bWVzIGVuY2Fwc3VsYXRpb24nLCBkb2VzIGl0IG1lYW4gdGhhdCBhPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgaG9zdCBjYW5ub3Q8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7IHNlbmQgYW4gSVB2NiBwYWNrZXQgd2l0aCBhbiBTUkg/IFRoZSBjdXJy
ZW50IGRyYWZ0IHNheXM6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBBIFNvdXJjZSBTUiBOb2RlIGNhbiBi
ZSBhbnkgbm9kZSBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tldCB3aXRoPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgaXRzPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsgSVB2NiBhbmQgU2VnbWVudCBSb3V0aW5nIEhlYWRlcnMuJm5ic3A7IFRoaXMgaW5j
bHVkZSBlaXRoZXI6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgQSBob3N0IG9yaWdp
bmF0aW5nIGFuIElQdjYgcGFja2V0Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsgJm5ic3A7IEFu
IFNSIGRvbWFpbiBpbmdyZXNzIHJvdXRlciBlbmNhcHN1bGF0aW5nIGEgcmVjZWl2ZWQgSVB2NiBw
YWNrZXQ8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsg
aW50byBhbiBvdXRlciBJUHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgV2lsbCBhcHByZWNpYXRlIGlmIHlvdSBjYW4gY2xh
cmlmeSB0aGF0Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBv
aywgdHdvIGNhc2VzOjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDEuIHRoZSBTUkggaXMgaW5zZXJ0ZWQgYXQgdGhlIHNv
dXJjZS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHRoZSBzb3VyY2Ugb3JpZ2lu
YXRlcyB0aGUgcGFja2V0LCB0aGUgaXB2NiBoZWFkZXIgYW5kJm5ic3A7IHRoZSBTUkguPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUaGUgc291cmNlIGNvbXB1dGVzIEw0IGNoZWNr
c3VtIHRha2luZyBpbnRvJm5ic3A7IGFjY291bnQgdGhlIHdob2xlPGJyPg0KJmd0OyZndDtJUHY2
JiM0MztTUkguPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIZXJlLCB0aGVyZXPi
gJkgbm90aGluZyBuZXcmbmJzcDsgY29tcGFyZWQgdG8gcmZjMjQ2MC48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAyLiB0
aGUgU1JIIGlzIG9yaWdpbmF0ZWQgYnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWlu
Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhpcyBpcyBkb25lIGJ5IGVuY2Fw
c3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0ZXI8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IChhZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRo
aXMgaXMgTDM8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRpb24g
YW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSZuYnNwOyBwYWNrZXQ8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGxlYXZlcyB0aGUgU1IgdHVubmVsIHRoZSBv
dXRlciBlbmNhcHN1bGF0aW9uJm5ic3A7IChpbmNsdWRpbmcgdGhlIFNSSCk8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVz
Jm5ic3A7IGl0cyBqb3VybmV5IGxpa2Ugbm90aGluZzxicj4NCiZndDtoYXBwZW5lZC48YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBzLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUaGFua3MsPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGFsLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86PGEgaHJl
Zj0ibWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbSI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU2VudDogTW9uZGF5LCBNYXkg
MTYsIDIwMTYgMTE6NTkgQU08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsgVG86IE9sZSBUcsO4YW47IFRhbCBNaXpyYWhpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7IENjOiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21l
bnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciPg0KZHJhZnQtaWV0Zi02bWFuLXNlZ21l
bnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc8L2E+Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86c3ByaW5nQGlldGYub3JnIj5z
cHJpbmdAaWV0Zi5vcmc8L2E+OyA2bWFuIFdHPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7IFN1YmplY3Q6IFJlOiBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQ8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgZHJhZnQtaWV0Zi02bWFuLXNlZ21l
bnQtcm91dGluZy0gaGVhZGVyPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPbiBNYXkgMTUsIDIwMTYsIGF0IDg6
MDYgUE0sIDxhIGhyZWY9Im1haWx0bzpvdHJvYW5AZW1wbG95ZWVzLm9yZyI+b3Ryb2FuQGVtcGxv
eWVlcy5vcmc8L2E+IHdyb3RlOjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRh
bCw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgW0Fwb2xvZ2llcyBpZiB0
aGlzIGlzc3VlIGhhcyBiZWVuIGRpc2N1c3NlZCBiZWZvcmUuXTxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgQWNjb3JkaW5nIHRvIGRyYWZ0LWlldGYtNm1hbi1zZWdt
ZW50LXJvdXRpbmctaGVhZGVyLCBhbiDigJhTUjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFNlZ21lbnQ8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVzIHRoZSBEZXN0aW5hdGlvbiBJ
UCBhZGRyZXNzLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7IFRoZXJlZm9yZSwgaXQgbXVzdCBhbHNvIHVwZGF0ZSB0aGUgTGF5ZXIgNCBDaGVja3N1bSwg
cmlnaHQ/PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBJIHdvbmRl
ciBpZiB0aGVyZSBpcyBhbiB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0aGUgU1JILjxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IE90aGVyd2lzZSwg
dGhlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEw0IENoZWNrc3Vt
IG1heSBiZSBsb2NhdGVkIGluIGEgcHJldHR5IGRlZXAgbG9jYXRpb24uPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU3BlYWtpbmcgZnJvbSBhIGNoaXAg
dmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0uPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgRnJvbSBSRkMyNDYwLCBSSDA6PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwO28mbmJzcDsgSWYgdGhlIElQdjYgcGFja2V0IGNvbnRhaW5z
IGEgUm91dGluZyBoZWFkZXIsIHRoZSBEZXN0aW5hdGlvbjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBBZGRyZXNzIHVzZWQg
aW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhhdCBvZiB0aGUgZmluYWw8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgZGVzdGlu
YXRpb24uJm5ic3A7IEF0IHRoZSBvcmlnaW5hdGluZyBub2RlLCB0aGF0IGFkZHJlc3Mgd2lsbCBi
ZSBpbjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsg
Jm5ic3A7ICZuYnNwOyB0aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5nIGhlYWRlcjsgYXQg
dGhlIHJlY2lwaWVudChzKSw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4gdGhlIERl
c3RpbmF0aW9uIEFkZHJlc3MgZmllbGQgb2YgdGhlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IElQdjYgaGVhZGVyLjxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEkgd291bGQgZXhwZWN0IFNSIHdvdWxkIHdv
cmsgdGhlIHNhbWUuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGV4YWN0bHkuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1
bWVzPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRp
b24gc28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS48YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgcy48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBDaGVlcnMsPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPbGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgSUVURiBJUHY2IHdv
cmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0IDxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5p
cHY2QGlldGYub3JnPC9hPiBBZG1pbmlzdHJhdGl2ZTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgUmVx
dWVzdHM6IDxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2
NiIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pcHY2PC9hPjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7PGJy
Pg0KJmd0O19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJy
Pg0KJmd0O252bzMgbWFpbGluZyBsaXN0PGJyPg0KJmd0OzxhIGhyZWY9Im1haWx0bzpudm8zQGll
dGYub3JnIj5udm8zQGlldGYub3JnPC9hPjxicj4NCiZndDs8YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL252bzMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL252bzM8L2E+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnNwcmluZyBtYWlsaW5n
IGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86c3ByaW5nQGlldGYub3JnIj5zcHJpbmdAaWV0Zi5v
cmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zcHJpbmciIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3NwcmluZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_bb99730deb8348bcac4f5c433e88d435ILEXCH02marvellcom_--


From nobody Mon May 23 00:46:42 2016
Return-Path: <rraszuk@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 DF3F812B032; Mon, 23 May 2016 00:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 wZ_tsxR_DKrj; Mon, 23 May 2016 00:46:34 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::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 DB2E112B026; Mon, 23 May 2016 00:46:33 -0700 (PDT)
Received: by mail-lb0-x234.google.com with SMTP id ww9so52598159lbc.2; Mon, 23 May 2016 00:46:33 -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:date:message-id:subject :from:to:cc; bh=B4oxaX6DRA2r9VJn2xToxGDH+AIs3ZwxTXd5Wm/5SCM=; b=rUsdE4UUJU0oNg6KEhcFaoVzf3tApsDaJZZ0XSj4UAXrJW+zf7N8raNhud9DOucz1v XuhwhPSeUXx9c45UlSanaK9cDQnBkTl+YDgNlnAn5cnyIwuipjVhHkBRXfiyrDs4NDEo Qwa+3Yb06BeKAy8qIeidkzWE3gzuR8nvA0YkWaMdrQfSdDBClc/U/UDa1fxRSV2/samc MnapYDiOF3M74xtEP+gvO4D0rseyoLs193JjVa2Y5TIHr7/AjS4vNGGdtopgBw0y/EPy RuUpj5gPQO597dK9tWJNnDGvFG9a/qg9weuXPcIM9uq4VUHdoCTxJHJgkFIyYAuImMKz j6lQ==
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:date :message-id:subject:from:to:cc; bh=B4oxaX6DRA2r9VJn2xToxGDH+AIs3ZwxTXd5Wm/5SCM=; b=fSvwCwQzaiT2AQhQ7Q9l8V+Ifo/S3GBxM9piQYYgGim4WemLtDU9Q7e+8X/WIY5Sz5 /HaPEwHJdovRGO3TMI7IgalQMebuyO2+GE14Ho2pdssnIHMWHaoo0SC+NMq4DdfADJYZ flossFydGhGgDMCg2W7/dv3HnbthUmwzvyPKww6c3OU5LJa3EmHRpVdTA6XaMOaVTeSH iZ0OmffnF9be648ukjpC2rmAD31IJd8E1Ze7MZQFYRXhGX6siHjfNvEI5a9bMnVZ6GOb lVt7+1E6H56nuqI+9yNfwv8AS0ZtccuN9U6jUBxkkX1fGg+AZc84fFgPkbECJzDnXY3a KjbQ==
X-Gm-Message-State: AOPr4FVxC56GBYkiV7f2pE/zY6WK0acJWJvleQS8Cp9ZJeplS/x9srC/PRDCzbWFJK/KqEeG+aIuXeYTAhIIgg==
MIME-Version: 1.0
X-Received: by 10.112.171.229 with SMTP id ax5mr5252428lbc.115.1463989591915;  Mon, 23 May 2016 00:46:31 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.25.126.210 with HTTP; Mon, 23 May 2016 00:46:31 -0700 (PDT)
In-Reply-To: <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com>
Date: Mon, 23 May 2016 09:46:31 +0200
X-Google-Sender-Auth: S03UTLdSiksFcXh_oSiaaMUB0lg
Message-ID: <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
From: Robert Raszuk <robert@raszuk.net>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=001a11c36ed694c48705337da31d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/heY727eNQqCuXxZJJiIwQ2skAxo>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 07:46:38 -0000

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

Hi Tal,

Indeed .. I saw the figures, but figures are non normative in any draft/rfc
unless text below specifically spells it out.

For example from vxlan-gpe:

"When the outer IP header is IPv4, VTEPs MUST set the DF bit."

Besides it is pretty challenging to add animation to the current draft
formats to illustrate all possibly allowed field values/combinations in any
figure :)  Figures just illustrate one use example.

To me the current specs permit any value of IPv6 NxtHdr field as permitted
in both encapsulations.

Best,
Robert.


On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <talmi@marvell.com> wrote:

> Hi Robert,
>
>
>
>
>
> > Where say in draft draft-quinn-vxlan-gpe do you see such statement that
> would imply
>
> > that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer to
> any other type
>
> > of extension header further followed by UDP ?
>
>
>
>
>
> The following text is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:
>
>
>
>       Outer IPv6 Header:
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |Version| Traffic Class |           Flow Label                  |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |         Payload Length        | NxtHdr=3D17(UDP)|   Hop Limit   |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |                                                               |
>
>
>
>
>
> There is a similar figure in draft-ietf-nvo3-geneve.
>
>
>
> Best regards,
>
> Tal.
>
>
>
> *From:* nvo3 [mailto:nvo3-bounces@ietf.org] *On Behalf Of *Robert Raszuk
> *Sent:* Monday, May 23, 2016 10:29 AM
> *To:* Tal Mizrahi
> *Cc:* spring@ietf.org; 6man WG; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org;
> nvo3@ietf.org; draft-ietf-6man-segment-routing-header@tools.ietf.org;
> draft-ietf-nvo3-geneve@tools.ietf.org; Stefano Previdi (sprevidi)
>
> *Subject:* Re: [nvo3] [spring] L4 Checksum and
> draft-ietf-6man-segment-routing-header
>
>
>
> Hi Tal,
>
>
>
> > drafts seem to imply
>
>
>
> Where say in draft draft-quinn-vxlan-gpe do you see such statement that
> would imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a
> pointer to any other type of extension header further followed by UDP ?
>
>
>
> Thx,
> R.
>
>
>
>
>
> On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>
> Dear Authors of VXLAN-GPE / Geneve,
>
> I am reiterating on this question, as I haven't seen a response yet:
>
> Have you considered the use of Segment Routing with VXLAN-GPE / Geneve?
> The current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension
> headers are currently not supported.
>
> Thanks,
> Tal.
>
>
>
>
> >-----Original Message-----
> >From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Tal Mizrahi
> >Sent: Tuesday, May 17, 2016 12:09 PM
> >To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
> >geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org
> >Cc: spring@ietf.org; nvo3@ietf.org; 6man WG; draft-ietf-6man-segment-
> >routing-header@tools.ietf.org
> >Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
> >routing-header
> >
> >Stefano,
> >
> >If I understand your point correctly:
> >IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sinc=
e
> >these encapsulations do not currently allow the use of IPv6 extension
> >headers.
> >
> >I wonder if the authors of VXLAN-GPE and Geneve have considered the use =
of
> >segment routing.
> >
> >Thanks,
> >Tal.
> >
> >
> >
> >>-----Original Message-----
> >>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>Sent: Tuesday, May 17, 2016 10:41 AM
> >>To: Tom Herbert
> >>Cc: Tal Mizrahi; 6man WG; spring@ietf.org;
> >>draft-ietf-6man-segment-routing- header@tools.ietf.org
> >>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
> >>header
> >>
> >>
> >>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com>
> >wrote:
> >>>
> >>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>
> >>>> Right. However, it appears that at least in some cases a VXLAN VTEP
> >>>> will
> >>use SR. It certainly may be the case in SFC use cases (see Section 2.3
> >>in draft- ietf-spring-ipv6-use-cases).
> >>>>
> >>>
> >>> draft-ietf-6man-segment-routing-header mentions that the packet is
> >>> encapsulated
> >>
> >>
> >>into an outer ipv6 header which makes it a layer-3 encap.
> >>
> >>
> >>> , but I don't think it is explicit as to exact encapsulation format
> >>> (I suppose simple ip6ip6 is implied).
> >>
> >>
> >>see section 2.2
> >>
> >>
> >>> But, it
> >>> seems like any of several encapsulation techniques could work (VXLAN,
> >>
> >>
> >>I have some problems to understand where to fit an extension header
> >>into a vxlan encap=E2=80=A6
> >>
> >>
> >>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
> >>> to do SR is already doing tunneling it seems reasonable to me to only
> >>> have one layer of encapsulation. Maybe this should be clarified in
> >>> the draft?
> >>
> >>
> >>the draft is about IPv6 extension header and more precisely a new type
> >>of the routing extension header defined in rfc2460. That=E2=80=99s the =
context.
> >>
> >>
> >>s.
> >>
> >>
> >>
> >>
> >>>
> >>> Tom
> >>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>> Sent: Monday, May 16, 2016 2:24 PM
> >>>>> To: Tal Mizrahi
> >>>>> Cc: Ole Tr=C3=B8an;
> >>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>> spring@ietf.org; 6man WG
> >>>>> Subject: Re: [spring] L4 Checksum and
> >>>>> draft-ietf-6man-segment-routing- header
> >>>>>
> >>>>>
> >>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com> wrote=
:
> >>>>>>
> >>>>>> Hi Stefano,
> >>>>>>
> >>>>>> Thanks again for the prompt response.
> >>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>
> >>>>>> So VXLAN is off the table?
> >>>>>
> >>>>>
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>>
> >>>>>
> >>>>>> It would be worthwhile to clarify this in the draft. If you have a
> >>>>>> specific
> >>>>> encapsulation in mind, it would be great if the draft would specify
> it.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Tal.
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>> Sent: Monday, May 16, 2016 2:13 PM
> >>>>>>> To: Tal Mizrahi
> >>>>>>> Cc: Ole Tr=C3=B8an;
> >>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>> spring@ietf.org; 6man WG
> >>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>>>>>
> >>>>>>>> Hi Stefano,
> >>>>>>>>
> >>>>>>>> Thanks for the responses.
> >>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>
> >>>>>>>> Two questions:
> >>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
> >>>>>>>> involved,
> >>right?
> >>>>>>>
> >>>>>>>
> >>>>>>> See below.
> >>>>>>>
> >>>>>>>
> >>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
> >>>>>>>> host cannot
> >>>>>>> send an IPv6 packet with an SRH? The current draft says:
> >>>>>>>>
> >>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
> >>>>>>>> its
> >>>>>>>> IPv6 and Segment Routing Headers.  This include either:
> >>>>>>>>
> >>>>>>>>    A host originating an IPv6 packet.
> >>>>>>>>
> >>>>>>>>    An SR domain ingress router encapsulating a received IPv6
> packet
> >>>>>>>>    into an outer IPv6 header followed by an SRH.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Will appreciate if you can clarify that.
> >>>>>>>
> >>>>>>>
> >>>>>>> ok, two cases:
> >>>>>>>
> >>>>>>> 1. the SRH is inserted at the source.
> >>>>>>> the source originates the packet, the ipv6 header and  the SRH.
> >>>>>>> The source computes L4 checksum taking into  account the whole
> >>IPv6+SRH.
> >>>>>>> Here, theres=E2=80=99 nothing new  compared to rfc2460.
> >>>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>>
> >>>>>>> s.
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Tal.
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
> >>>>>>>>> To: Ole Tr=C3=B8an; Tal Mizrahi
> >>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>>>> spring@ietf.org; 6man WG
> >>>>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
> >>>>>>>>>>
> >>>>>>>>>> Tal,
> >>>>>>>>>>
> >>>>>>>>>>> [Apologies if this issue has been discussed before.]
> >>>>>>>>>>>
> >>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =E2=
=80=98SR
> >>>>>>>>>>> Segment
> >>>>>>>>> Endpoint Node=E2=80=99 updates the Destination IP address.
> >>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
> >>>>>>>>>>>
> >>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
> >>>>>>>>>>> Otherwise, the
> >>>>>>>>> L4 Checksum may be located in a pretty deep location.
> >>>>>>>>>>> Speaking from a chip vendor=E2=80=99s perspective this may be=
 a
> problem.
> >>>>>>>>>>
> >>>>>>>>>> From RFC2460, RH0:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>   o  If the IPv6 packet contains a Routing header, the
> Destination
> >>>>>>>>>>      Address used in the pseudo-header is that of the final
> >>>>>>>>>>      destination.  At the originating node, that address will
> be in
> >>>>>>>>>>      the last element of the Routing header; at the
> recipient(s),
> >>>>>>>>>>      that address will be in the Destination Address field of
> the
> >>>>>>>>>>      IPv6 header.
> >>>>>>>>>>
> >>>>>>>>>> I would expect SR would work the same.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Ole
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> >>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>>> --------------------------------------------------------------------
> >
> >_______________________________________________
> >nvo3 mailing list
> >nvo3@ietf.org
> >https://www.ietf.org/mailman/listinfo/nvo3
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Tal,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small">Indeed .. I saw the figures, but figures are non norm=
ative in any draft/rfc unless text below specifically spells it out.=C2=A0<=
/div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans=
-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small">For example from vxlan=
-gpe:=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small">&quot;<spa=
n style=3D"color:rgb(0,0,0);white-space:pre-wrap;font-family:arial,sans-ser=
if">When the outer IP header is IPv4, VTEPs MUST set the DF bit.&quot;</spa=
n></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif;font-size:small">Besides it is prett=
y challenging to add animation to the current draft formats to illustrate a=
ll possibly allowed field values/combinations in any figure :) =C2=A0Figure=
s just illustrate one use example.=C2=A0<br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif;font-size:small">To me the current specs permit any value of IPv6 Nxt=
Hdr field as permitted in both encapsulations.</div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br>=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small">Best,</div><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif;font-size:small">Robert.</div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <span dir=3D"ltr">&=
lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.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">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Robert,<u></u><u></u><=
/span></p><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;</span>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">Where say in draft draft-quinn-vxlan-gpe do you =
see such statement that would imply
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt; that v6 NxtHdr must =
be only equal to 17 (UDP) and not be a pointer to any other type
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt; of extension header =
further followed by UDP ?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">The following text=
 is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Outer IPv6 He=
ader:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Version| Tra=
ffic Class |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Fl=
ow Label=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 |<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=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 Payload Length=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 | NxtHdr=3D17(UDP)|=C2=A0=C2=A0 Hop Limit=C2=A0=C2=A0 |<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=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=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=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=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a similar figure=
 in draft-ietf-nvo3-geneve.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best regards,<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Tal.<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> nvo3 [ma=
ilto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_blank">nvo3-bounce=
s@ietf.org</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:29 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG; <a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.o=
rg" target=3D"_blank">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>; <a href=
=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a href=3D"m=
ailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=3D"_bla=
nk">draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"m=
ailto:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">draft-ietf-n=
vo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)</span></p><div><d=
iv class=3D"h5"><br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Hi Tal,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">&gt;=C2=A0</span><span style=3D"font-size:9.5pt;font-famil=
y:&quot;Arial&quot;,&quot;sans-serif&quot;">drafts seem to imply</span><spa=
n style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot;"><u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Where say in draft=C2=A0draft-quinn-vxlan-gpe do you see s=
uch statement that would imply that v6 NxtHdr must be only equal to 17 (UDP=
) and not be a pointer to any other type of extension header
 further followed by UDP ?=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Thx,<br>
R.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Dear Authors of VXLAN-GPE / Geneve,<br>
<br>
I am reiterating on this question, as I haven&#39;t seen a response yet:<br=
>
<br>
Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.<br>
<br>
Thanks,<br>
Tal.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_=
blank">nvo3-bounces@ietf.org</a>] On Behalf Of Tal Mizrahi<br>
&gt;Sent: Tuesday, May 17, 2016 12:09 PM<br>
&gt;To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-<br>
&gt;<a href=3D"mailto:geneve@tools.ietf.org" target=3D"_blank">geneve@tools=
.ietf.org</a>; <a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" =
target=3D"_blank">
draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a><br>
&gt;Cc: <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.or=
g</a>; <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">
nvo3@ietf.org</a>; 6man WG; draft-ietf-6man-segment-<br>
&gt;<a href=3D"mailto:routing-header@tools.ietf.org" target=3D"_blank">rout=
ing-header@tools.ietf.org</a><br>
&gt;Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-<b=
r>
&gt;routing-header<br>
&gt;<br>
&gt;Stefano,<br>
&gt;<br>
&gt;If I understand your point correctly:<br>
&gt;IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sin=
ce<br>
&gt;these encapsulations do not currently allow the use of IPv6 extension<b=
r>
&gt;headers.<br>
&gt;<br>
&gt;I wonder if the authors of VXLAN-GPE and Geneve have considered the use=
 of<br>
&gt;segment routing.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;-----Original Message-----<br>
&gt;&gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevidi=
@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt;&gt;To: Tom Herbert<br>
&gt;&gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org" target=
=3D"_blank">spring@ietf.org</a>;<br>
&gt;&gt;draft-ietf-6man-segment-routing- <a href=3D"mailto:header@tools.iet=
f.org" target=3D"_blank">header@tools.ietf.org</a><br>
&gt;&gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routi=
ng-<br>
&gt;&gt;header<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailto=
:tom@herbertland.com" target=3D"_blank">tom@herbertland.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"ma=
ilto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Right. However, it appears that at least in some cases a V=
XLAN VTEP<br>
&gt;&gt;&gt;&gt; will<br>
&gt;&gt;use SR. It certainly may be the case in SFC use cases (see Section =
2.3<br>
&gt;&gt;in draft- ietf-spring-ipv6-use-cases).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; draft-ietf-6man-segment-routing-header mentions that the packe=
t is<br>
&gt;&gt;&gt; encapsulated<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; , but I don&#39;t think it is explicit as to exact encapsulati=
on format<br>
&gt;&gt;&gt; (I suppose simple ip6ip6 is implied).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;see section 2.2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; But, it<br>
&gt;&gt;&gt; seems like any of several encapsulation techniques could work =
(VXLAN,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;I have some problems to understand where to fit an extension header=
<br>
&gt;&gt;into a vxlan encap=E2=80=A6<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that =
wants<br>
&gt;&gt;&gt; to do SR is already doing tunneling it seems reasonable to me =
to only<br>
&gt;&gt;&gt; have one layer of encapsulation. Maybe this should be clarifie=
d in<br>
&gt;&gt;&gt; the draft?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;the draft is about IPv6 extension header and more precisely a new t=
ype<br>
&gt;&gt;of the routing extension header defined in rfc2460. That=E2=80=99s =
the context.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Tom<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"ma=
ilto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-head=
er@tools.ietf.org" target=3D"_blank">draft-ietf-6man-segment-routing-header=
@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_blank">s=
pring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a hr=
ef=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;=
 wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the draf=
t. If you have a<br>
&gt;&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft =
would specify it.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a hr=
ef=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org" target=3D"_blank">draft-ietf-6man-segment-routin=
g-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_=
blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt;=
<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a=
>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4 =
would still be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; involved,<br>
&gt;&gt;right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say &#39;assumes encapsulation=
&#39;, does it mean that a<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; host cannot<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current d=
raft says:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originati=
ng an IPv6 packet with<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.=C2=A0 Th=
is include either:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A host originating an IPv6 pa=
cket.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 An SR domain ingress router e=
ncapsulating a received IPv6 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 into an outer IPv6 header fol=
lowed by an SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 hea=
der and=C2=A0 the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into=C2=
=A0 account the whole<br>
&gt;&gt;IPv6+SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Here, theres=E2=80=99 nothing new=C2=A0 compar=
ed to rfc2460.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mail=
to:<a href=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.c=
om</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<br=
>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=C3=B8an; Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man-=
segment-routing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- heade=
r<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a hr=
ef=3D"mailto:otroan@employees.org" target=3D"_blank">otroan@employees.org</=
a> wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has b=
een discussed before.]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-s=
egment-routing-header, an =E2=80=98SR<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node=E2=80=99 updates the Des=
tination IP address.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also update=
 the Layer 4 Checksum, right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper =
bound on the size of the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a pretty=
 deep location.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor=E2=
=80=99s perspective this may be a problem.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0o=C2=A0 If the IPv6 pa=
cket contains a Routing header, the Destination<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Address used i=
n the pseudo-header is that of the final<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 destination.=
=C2=A0 At the originating node, that address will be in<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 the last eleme=
nt of the Routing header; at the recipient(s),<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 that address w=
ill be in the Destination Address field of the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 IPv6 header.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the s=
ame.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;&gt;&gt;&gt; IETF IPv6 working group mailing list <a href=3D"mailto:ipv=
6@ietf.org" target=3D"_blank">ipv6@ietf.org</a> Administrative<br>
&gt;&gt;&gt;&gt; Requests: <a href=3D"https://www.ietf.org/mailman/listinfo=
/ipv6" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;nvo3 mailing list<br>
&gt;<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br=
>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/nvo3</a><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/spring</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--001a11c36ed694c48705337da31d--


From nobody Mon May 23 00:54:49 2016
Return-Path: <talmi@marvell.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 41CBC12D61D; Mon, 23 May 2016 00:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 7gWHX8jgo45X; Mon, 23 May 2016 00:54:25 -0700 (PDT)
Received: from mx0a-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 1472112B00E; Mon, 23 May 2016 00:54:25 -0700 (PDT)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4N7pb10005541; Mon, 23 May 2016 00:54:24 -0700
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0a-0016f401.pphosted.com with ESMTP id 232n1jncr3-3 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 23 May 2016 00:54:23 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 23 May 2016 10:54:16 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Mon, 23 May 2016 10:54:16 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: Robert Raszuk <robert@raszuk.net>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@tools.ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>
Subject: RE: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMThJCvw5mf6XUe954CmH3IV2Z/GIJVA///SB4CAADJs4A==
Date: Mon, 23 May 2016 07:54:15 +0000
Message-ID: <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com>
In-Reply-To: <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@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
x-originating-ip: [10.4.102.210]
Content-Type: multipart/alternative; boundary="_000_1c27bb3513bc48889ec310e8d143784cILEXCH02marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-23_02:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605230094
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/g6OCp97mvpOrjk19kCgCDL_sim4>
Cc: "spring@ietf.org" <spring@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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: Mon, 23 May 2016 07:54:28 -0000
X-List-Received-Date: Mon, 23 May 2016 07:54:28 -0000

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

SGkgUm9iZXJ0LA0KDQpUaGF0IG1ha2VzIHNlbnNlLg0KSG93ZXZlciwgaW4gdGhpcyBjYXNlIHRo
ZSBmaWd1cmVzIG1heSBiZSBhIGJpdCBjb25mdXNpbmcgV1JUIHRoZSBwb3NzaWJsZSBleGlzdGVu
Y2Ugb2YgZXh0ZW5zaW9uIGhlYWRlcnMuIFRoaXMgY29uZnVzaW9uIGlzIHdoYXQgbGVkIHRvIHRo
ZSBkaXNjdXNzaW9uIGluIHRoaXMgdGhyZWFkIGFib3V0IHdoZXRoZXIgc2VnbWVudCByb3V0aW5n
IGlzIHBvc3NpYmxlIHdpdGggVlhMQU4vVlhMQU4tR1BFL0dlbmV2ZSBlbmNhcHN1bGF0aW9ucy4N
Cg0KSW4gb3JkZXIgdG8gYXZvaWQgYW1iaWd1aXR5LCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUg
YXV0aG9ycyBjb3VsZCBleHBsaWNpdGx5IG1lbnRpb24gdGhhdCBJUHY2IGV4dGVuc2lvbiBoZWFk
ZXJzIGFyZSBwZXJtaXR0ZWQuDQoNClJlZ2FyZHMsDQpUYWwuDQoNCkZyb206IHJyYXN6dWtAZ21h
aWwuY29tIFttYWlsdG86cnJhc3p1a0BnbWFpbC5jb21dIE9uIEJlaGFsZiBPZiBSb2JlcnQgUmFz
enVrDQpTZW50OiBNb25kYXksIE1heSAyMywgMjAxNiAxMDo0NyBBTQ0KVG86IFRhbCBNaXpyYWhp
DQpDYzogc3ByaW5nQGlldGYub3JnOyA2bWFuIFdHOyBkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3Bl
QHRvb2xzLmlldGYub3JnOyBudm8zQGlldGYub3JnOyBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1y
b3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsgZHJhZnQtaWV0Zi1udm8zLWdlbmV2ZUB0b29s
cy5pZXRmLm9yZzsgU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkNClN1YmplY3Q6IFJlOiBbbnZv
M10gW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRp
bmctaGVhZGVyDQoNCkhpIFRhbCwNCg0KSW5kZWVkIC4uIEkgc2F3IHRoZSBmaWd1cmVzLCBidXQg
ZmlndXJlcyBhcmUgbm9uIG5vcm1hdGl2ZSBpbiBhbnkgZHJhZnQvcmZjIHVubGVzcyB0ZXh0IGJl
bG93IHNwZWNpZmljYWxseSBzcGVsbHMgaXQgb3V0Lg0KDQpGb3IgZXhhbXBsZSBmcm9tIHZ4bGFu
LWdwZToNCg0KIldoZW4gdGhlIG91dGVyIElQIGhlYWRlciBpcyBJUHY0LCBWVEVQcyBNVVNUIHNl
dCB0aGUgREYgYml0LiINCg0KQmVzaWRlcyBpdCBpcyBwcmV0dHkgY2hhbGxlbmdpbmcgdG8gYWRk
IGFuaW1hdGlvbiB0byB0aGUgY3VycmVudCBkcmFmdCBmb3JtYXRzIHRvIGlsbHVzdHJhdGUgYWxs
IHBvc3NpYmx5IGFsbG93ZWQgZmllbGQgdmFsdWVzL2NvbWJpbmF0aW9ucyBpbiBhbnkgZmlndXJl
IDopICBGaWd1cmVzIGp1c3QgaWxsdXN0cmF0ZSBvbmUgdXNlIGV4YW1wbGUuDQoNClRvIG1lIHRo
ZSBjdXJyZW50IHNwZWNzIHBlcm1pdCBhbnkgdmFsdWUgb2YgSVB2NiBOeHRIZHIgZmllbGQgYXMg
cGVybWl0dGVkIGluIGJvdGggZW5jYXBzdWxhdGlvbnMuDQoNCkJlc3QsDQpSb2JlcnQuDQoNCg0K
T24gTW9uLCBNYXkgMjMsIDIwMTYgYXQgOTozNSBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZl
bGwuY29tPG1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbT4+IHdyb3RlOg0KSGkgUm9iZXJ0LA0KDQoN
Cj4gV2hlcmUgc2F5IGluIGRyYWZ0IGRyYWZ0LXF1aW5uLXZ4bGFuLWdwZSBkbyB5b3Ugc2VlIHN1
Y2ggc3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkNCj4gdGhhdCB2NiBOeHRIZHIgbXVzdCBiZSBv
bmx5IGVxdWFsIHRvIDE3IChVRFApIGFuZCBub3QgYmUgYSBwb2ludGVyIHRvIGFueSBvdGhlciB0
eXBlDQo+IG9mIGV4dGVuc2lvbiBoZWFkZXIgZnVydGhlciBmb2xsb3dlZCBieSBVRFAgPw0KDQoN
ClRoZSBmb2xsb3dpbmcgdGV4dCBpcyBmcm9tIEZpZ3VyZSA0IGluIGRyYWZ0LWlldGYtbnZvMy12
eGxhbi1ncGU6DQoNCiAgICAgIE91dGVyIElQdjYgSGVhZGVyOg0KICAgICAgKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAg
ICAgIHxWZXJzaW9ufCBUcmFmZmljIENsYXNzIHwgICAgICAgICAgIEZsb3cgTGFiZWwgICAgICAg
ICAgICAgICAgICB8DQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAgfCAgICAgICAgIFBheWxvYWQgTGVu
Z3RoICAgICAgICB8IE54dEhkcj0xNyhVRFApfCAgIEhvcCBMaW1pdCAgIHwNCiAgICAgICstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rDQogICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfA0KDQoNClRoZXJlIGlzIGEgc2ltaWxhciBmaWd1cmUgaW4gZHJh
ZnQtaWV0Zi1udm8zLWdlbmV2ZS4NCg0KQmVzdCByZWdhcmRzLA0KVGFsLg0KDQpGcm9tOiBudm8z
IFttYWlsdG86bnZvMy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpudm8zLWJvdW5jZXNAaWV0Zi5v
cmc+XSBPbiBCZWhhbGYgT2YgUm9iZXJ0IFJhc3p1aw0KU2VudDogTW9uZGF5LCBNYXkgMjMsIDIw
MTYgMTA6MjkgQU0NClRvOiBUYWwgTWl6cmFoaQ0KQ2M6IHNwcmluZ0BpZXRmLm9yZzxtYWlsdG86
c3ByaW5nQGlldGYub3JnPjsgNm1hbiBXRzsgZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29s
cy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9y
Zz47IG52bzNAaWV0Zi5vcmc8bWFpbHRvOm52bzNAaWV0Zi5vcmc+OyBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi02
bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc+OyBkcmFmdC1pZXRmLW52
bzMtZ2VuZXZlQHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLW52bzMtZ2VuZXZlQHRv
b2xzLmlldGYub3JnPjsgU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkNCg0KU3ViamVjdDogUmU6
IFtudm8zXSBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy1oZWFkZXINCg0KSGkgVGFsLA0KDQo+IGRyYWZ0cyBzZWVtIHRvIGltcGx5DQoNCldo
ZXJlIHNheSBpbiBkcmFmdCBkcmFmdC1xdWlubi12eGxhbi1ncGUgZG8geW91IHNlZSBzdWNoIHN0
YXRlbWVudCB0aGF0IHdvdWxkIGltcGx5IHRoYXQgdjYgTnh0SGRyIG11c3QgYmUgb25seSBlcXVh
bCB0byAxNyAoVURQKSBhbmQgbm90IGJlIGEgcG9pbnRlciB0byBhbnkgb3RoZXIgdHlwZSBvZiBl
eHRlbnNpb24gaGVhZGVyIGZ1cnRoZXIgZm9sbG93ZWQgYnkgVURQID8NCg0KVGh4LA0KUi4NCg0K
DQpPbiBNb24sIE1heSAyMywgMjAxNiBhdCA3OjUwIEFNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFy
dmVsbC5jb208bWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tPj4gd3JvdGU6DQpEZWFyIEF1dGhvcnMg
b2YgVlhMQU4tR1BFIC8gR2VuZXZlLA0KDQpJIGFtIHJlaXRlcmF0aW5nIG9uIHRoaXMgcXVlc3Rp
b24sIGFzIEkgaGF2ZW4ndCBzZWVuIGEgcmVzcG9uc2UgeWV0Og0KDQpIYXZlIHlvdSBjb25zaWRl
cmVkIHRoZSB1c2Ugb2YgU2VnbWVudCBSb3V0aW5nIHdpdGggVlhMQU4tR1BFIC8gR2VuZXZlPyBU
aGUgY3VycmVudCBWWExBTi1HUEUgLyBHZW5ldmUgZHJhZnRzIHNlZW0gdG8gaW1wbHkgdGhhdCBJ
UHY2IGV4dGVuc2lvbiBoZWFkZXJzIGFyZSBjdXJyZW50bHkgbm90IHN1cHBvcnRlZC4NCg0KVGhh
bmtzLA0KVGFsLg0KDQoNCg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogbnZv
MyBbbWFpbHRvOm52bzMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86bnZvMy1ib3VuY2VzQGlldGYu
b3JnPl0gT24gQmVoYWxmIE9mIFRhbCBNaXpyYWhpDQo+U2VudDogVHVlc2RheSwgTWF5IDE3LCAy
MDE2IDEyOjA5IFBNDQo+VG86IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpOyBUb20gSGVyYmVy
dDsgZHJhZnQtaWV0Zi1udm8zLQ0KPmdlbmV2ZUB0b29scy5pZXRmLm9yZzxtYWlsdG86Z2VuZXZl
QHRvb2xzLmlldGYub3JnPjsgZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9y
ZzxtYWlsdG86ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9yZz4NCj5DYzog
c3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+OyBudm8zQGlldGYub3JnPG1h
aWx0bzpudm8zQGlldGYub3JnPjsgNm1hbiBXRzsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtDQo+
cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOnJvdXRpbmctaGVhZGVyQHRvb2xz
LmlldGYub3JnPg0KPlN1YmplY3Q6IFJlOiBbbnZvM10gW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5k
IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LQ0KPnJvdXRpbmctaGVhZGVyDQo+DQo+U3RlZmFubywN
Cj4NCj5JZiBJIHVuZGVyc3RhbmQgeW91ciBwb2ludCBjb3JyZWN0bHk6DQo+SVB2NiBzZWdtZW50
IHJvdXRpbmcgZG9lcyBub3Qgd29yayB3aXRoIFZYTEFOIC8gVlhMQU4tR1BFIC8gR2VuZXZlLCBz
aW5jZQ0KPnRoZXNlIGVuY2Fwc3VsYXRpb25zIGRvIG5vdCBjdXJyZW50bHkgYWxsb3cgdGhlIHVz
ZSBvZiBJUHY2IGV4dGVuc2lvbg0KPmhlYWRlcnMuDQo+DQo+SSB3b25kZXIgaWYgdGhlIGF1dGhv
cnMgb2YgVlhMQU4tR1BFIGFuZCBHZW5ldmUgaGF2ZSBjb25zaWRlcmVkIHRoZSB1c2Ugb2YNCj5z
ZWdtZW50IHJvdXRpbmcuDQo+DQo+VGhhbmtzLA0KPlRhbC4NCj4NCj4NCj4NCj4+LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4+RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21h
aWx0bzpzcHJldmlkaUBjaXNjby5jb208bWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbT5dDQo+PlNl
bnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAxMDo0MSBBTQ0KPj5UbzogVG9tIEhlcmJlcnQNCj4+
Q2M6IFRhbCBNaXpyYWhpOyA2bWFuIFdHOyBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0Bp
ZXRmLm9yZz47DQo+PmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlckB0b29s
cy5pZXRmLm9yZzxtYWlsdG86aGVhZGVyQHRvb2xzLmlldGYub3JnPg0KPj5TdWJqZWN0OiBSZTog
W3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmct
DQo+PmhlYWRlcg0KPj4NCj4+DQo+Pj4gT24gTWF5IDE2LCAyMDE2LCBhdCA3OjEwIFBNLCBUb20g
SGVyYmVydCA8dG9tQGhlcmJlcnRsYW5kLmNvbTxtYWlsdG86dG9tQGhlcmJlcnRsYW5kLmNvbT4+
DQo+d3JvdGU6DQo+Pj4NCj4+PiBPbiBNb24sIE1heSAxNiwgMjAxNiBhdCA0OjMyIEFNLCBUYWwg
TWl6cmFoaSA8dGFsbWlAbWFydmVsbC5jb208bWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tPj4NCj4+
d3JvdGU6DQo+Pj4+PiBpdOKAmXMgYWxsIGFib3V0IElQLCBub3QgbGF5ZXItMi4NCj4+Pj4+DQo+
Pj4+PiBzLg0KPj4+Pg0KPj4+PiBSaWdodC4gSG93ZXZlciwgaXQgYXBwZWFycyB0aGF0IGF0IGxl
YXN0IGluIHNvbWUgY2FzZXMgYSBWWExBTiBWVEVQDQo+Pj4+IHdpbGwNCj4+dXNlIFNSLiBJdCBj
ZXJ0YWlubHkgbWF5IGJlIHRoZSBjYXNlIGluIFNGQyB1c2UgY2FzZXMgKHNlZSBTZWN0aW9uIDIu
Mw0KPj5pbiBkcmFmdC0gaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMpLg0KPj4+Pg0KPj4+DQo+
Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIgbWVudGlvbnMgdGhhdCB0
aGUgcGFja2V0IGlzDQo+Pj4gZW5jYXBzdWxhdGVkDQo+Pg0KPj4NCj4+aW50byBhbiBvdXRlciBp
cHY2IGhlYWRlciB3aGljaCBtYWtlcyBpdCBhIGxheWVyLTMgZW5jYXAuDQo+Pg0KPj4NCj4+PiAs
IGJ1dCBJIGRvbid0IHRoaW5rIGl0IGlzIGV4cGxpY2l0IGFzIHRvIGV4YWN0IGVuY2Fwc3VsYXRp
b24gZm9ybWF0DQo+Pj4gKEkgc3VwcG9zZSBzaW1wbGUgaXA2aXA2IGlzIGltcGxpZWQpLg0KPj4N
Cj4+DQo+PnNlZSBzZWN0aW9uIDIuMg0KPj4NCj4+DQo+Pj4gQnV0LCBpdA0KPj4+IHNlZW1zIGxp
a2UgYW55IG9mIHNldmVyYWwgZW5jYXBzdWxhdGlvbiB0ZWNobmlxdWVzIGNvdWxkIHdvcmsgKFZY
TEFOLA0KPj4NCj4+DQo+PkkgaGF2ZSBzb21lIHByb2JsZW1zIHRvIHVuZGVyc3RhbmQgd2hlcmUg
dG8gZml0IGFuIGV4dGVuc2lvbiBoZWFkZXINCj4+aW50byBhIHZ4bGFuIGVuY2Fw4oCmDQo+Pg0K
Pj4NCj4+PiBHUkUvSVAsIEVTUC9JUCwgR1VFLCBmb28gb3ZlciBVRFAsIGV0Yy4pIGFuZCBpZiBh
IGRldmljZSB0aGF0IHdhbnRzDQo+Pj4gdG8gZG8gU1IgaXMgYWxyZWFkeSBkb2luZyB0dW5uZWxp
bmcgaXQgc2VlbXMgcmVhc29uYWJsZSB0byBtZSB0byBvbmx5DQo+Pj4gaGF2ZSBvbmUgbGF5ZXIg
b2YgZW5jYXBzdWxhdGlvbi4gTWF5YmUgdGhpcyBzaG91bGQgYmUgY2xhcmlmaWVkIGluDQo+Pj4g
dGhlIGRyYWZ0Pw0KPj4NCj4+DQo+PnRoZSBkcmFmdCBpcyBhYm91dCBJUHY2IGV4dGVuc2lvbiBo
ZWFkZXIgYW5kIG1vcmUgcHJlY2lzZWx5IGEgbmV3IHR5cGUNCj4+b2YgdGhlIHJvdXRpbmcgZXh0
ZW5zaW9uIGhlYWRlciBkZWZpbmVkIGluIHJmYzI0NjAuIFRoYXTigJlzIHRoZSBjb250ZXh0Lg0K
Pj4NCj4+DQo+PnMuDQo+Pg0KPj4NCj4+DQo+Pg0KPj4+DQo+Pj4gVG9tDQo+Pj4NCj4+Pj4NCj4+
Pj4NCj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+PiBGcm9tOiBTdGVmYW5v
IFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbTxtYWlsdG86c3By
ZXZpZGlAY2lzY28uY29tPl0NCj4+Pj4+IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MjQg
UE0NCj4+Pj4+IFRvOiBUYWwgTWl6cmFoaQ0KPj4+Pj4gQ2M6IE9sZSBUcsO4YW47DQo+Pj4+PiBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzxtYWls
dG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc+
Ow0KPj4+Pj4gc3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+OyA2bWFuIFdH
DQo+Pj4+PiBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kDQo+Pj4+PiBkcmFm
dC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXINCj4+Pj4+DQo+Pj4+Pg0KPj4+Pj4+
IE9uIE1heSAxNiwgMjAxNiwgYXQgMToxOSBQTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwu
Y29tPG1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbT4+IHdyb3RlOg0KPj4+Pj4+DQo+Pj4+Pj4gSGkg
U3RlZmFubywNCj4+Pj4+Pg0KPj4+Pj4+IFRoYW5rcyBhZ2FpbiBmb3IgdGhlIHByb21wdCByZXNw
b25zZS4NCj4+Pj4+Pg0KPj4+Pj4+PiAyLiB0aGUgU1JIIGlzIG9yaWdpbmF0ZWQgYnkgdGhlIGlu
Z3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWluLg0KPj4+Pj4+PiBUaGlzIGlzIGRvbmUgYnkgZW5j
YXBzdWxhdGluZyB0aGUgcGFja2V0IGludG8gYSBvdXRlcg0KPj4+Pj4+PiAoYWRkaXRpb25hbCkg
aXB2NiBoZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILiBUaGlzIGlzIEwzDQo+Pj4+Pj4+IGVuY2Fw
c3VsYXRpb24gYW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSAgcGFja2V0
DQo+Pj4+Pj4+IGxlYXZlcyB0aGUgU1IgdHVubmVsIHRoZSBvdXRlciBlbmNhcHN1bGF0aW9uICAo
aW5jbHVkaW5nIHRoZSBTUkgpDQo+Pj4+Pj4+IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29u
dGludWVzICBpdHMgam91cm5leSBsaWtlIG5vdGhpbmcNCj5oYXBwZW5lZC4NCj4+Pj4+Pg0KPj4+
Pj4+IFNvIFZYTEFOIGlzIG9mZiB0aGUgdGFibGU/DQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IGl04oCZ
cyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLg0KPj4+Pj4NCj4+Pj4+IHMuDQo+Pj4+Pg0KPj4+
Pj4NCj4+Pj4+PiBJdCB3b3VsZCBiZSB3b3J0aHdoaWxlIHRvIGNsYXJpZnkgdGhpcyBpbiB0aGUg
ZHJhZnQuIElmIHlvdSBoYXZlIGENCj4+Pj4+PiBzcGVjaWZpYw0KPj4+Pj4gZW5jYXBzdWxhdGlv
biBpbiBtaW5kLCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUgZHJhZnQgd291bGQgc3BlY2lmeSBp
dC4NCj4+Pj4+Pg0KPj4+Pj4+IFRoYW5rcywNCj4+Pj4+PiBUYWwuDQo+Pj4+Pj4NCj4+Pj4+Pg0K
Pj4+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+Pj4+PiBGcm9tOiBTdGVmYW5v
IFByZXZpZGkgKHNwcmV2aWRpKSBbbWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbTxtYWlsdG86c3By
ZXZpZGlAY2lzY28uY29tPl0NCj4+Pj4+Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYgMjox
MyBQTQ0KPj4+Pj4+PiBUbzogVGFsIE1penJhaGkNCj4+Pj4+Pj4gQ2M6IE9sZSBUcsO4YW47DQo+
Pj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYu
b3JnPG1haWx0bzpkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5p
ZXRmLm9yZz47DQo+Pj4+Pj4+IHNwcmluZ0BpZXRmLm9yZzxtYWlsdG86c3ByaW5nQGlldGYub3Jn
PjsgNm1hbiBXRw0KPj4+Pj4+PiBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5k
DQo+Pj4+Pj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+Pj4+
Pg0KPj4+Pj4+PiBIaSwNCj4+Pj4+Pj4NCj4+Pj4+Pj4gT24gTWF5IDE2LCAyMDE2LCBhdCAxMTow
NCBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29tPG1haWx0bzp0YWxtaUBtYXJ2ZWxs
LmNvbT4+DQo+Pndyb3RlOg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IEhpIFN0ZWZhbm8sDQo+Pj4+Pj4+
Pg0KPj4+Pj4+Pj4gVGhhbmtzIGZvciB0aGUgcmVzcG9uc2VzLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+
PiBleGFjdGx5Lg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gTW9yZW92ZXIsIGRyYWZ0LWlldGYtNm1h
bi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4+Pj4+PiBlbmNhcHN1bGF0aW9u
IHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+Pj4+Pj4+Pj4NCj4+
Pj4+Pj4+PiBzLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IFR3byBxdWVzdGlvbnM6DQo+Pj4+Pj4+PiAx
LiBXaGF0IGlmIHRoZSBlbmNhcHN1bGF0aW9uIGlzIFZYTEFOPyBMNCB3b3VsZCBzdGlsbCBiZQ0K
Pj4+Pj4+Pj4gaW52b2x2ZWQsDQo+PnJpZ2h0Pw0KPj4+Pj4+Pg0KPj4+Pj4+Pg0KPj4+Pj4+PiBT
ZWUgYmVsb3cuDQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+PiAyLiBXaGVuIHlvdSBzYXkgJ2Fz
c3VtZXMgZW5jYXBzdWxhdGlvbicsIGRvZXMgaXQgbWVhbiB0aGF0IGENCj4+Pj4+Pj4+IGhvc3Qg
Y2Fubm90DQo+Pj4+Pj4+IHNlbmQgYW4gSVB2NiBwYWNrZXQgd2l0aCBhbiBTUkg/IFRoZSBjdXJy
ZW50IGRyYWZ0IHNheXM6DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gQSBTb3VyY2UgU1IgTm9kZSBjYW4g
YmUgYW55IG5vZGUgb3JpZ2luYXRpbmcgYW4gSVB2NiBwYWNrZXQgd2l0aA0KPj4+Pj4+Pj4gaXRz
DQo+Pj4+Pj4+PiBJUHY2IGFuZCBTZWdtZW50IFJvdXRpbmcgSGVhZGVycy4gIFRoaXMgaW5jbHVk
ZSBlaXRoZXI6DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gICAgQSBob3N0IG9yaWdpbmF0aW5nIGFuIElQ
djYgcGFja2V0Lg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+ICAgIEFuIFNSIGRvbWFpbiBpbmdyZXNzIHJv
dXRlciBlbmNhcHN1bGF0aW5nIGEgcmVjZWl2ZWQgSVB2NiBwYWNrZXQNCj4+Pj4+Pj4+ICAgIGlu
dG8gYW4gb3V0ZXIgSVB2NiBoZWFkZXIgZm9sbG93ZWQgYnkgYW4gU1JILg0KPj4+Pj4+Pj4NCj4+
Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4gV2lsbCBhcHByZWNpYXRlIGlmIHlvdSBjYW4gY2xh
cmlmeSB0aGF0Lg0KPj4+Pj4+Pg0KPj4+Pj4+Pg0KPj4+Pj4+PiBvaywgdHdvIGNhc2VzOg0KPj4+
Pj4+Pg0KPj4+Pj4+PiAxLiB0aGUgU1JIIGlzIGluc2VydGVkIGF0IHRoZSBzb3VyY2UuDQo+Pj4+
Pj4+IHRoZSBzb3VyY2Ugb3JpZ2luYXRlcyB0aGUgcGFja2V0LCB0aGUgaXB2NiBoZWFkZXIgYW5k
ICB0aGUgU1JILg0KPj4+Pj4+PiBUaGUgc291cmNlIGNvbXB1dGVzIEw0IGNoZWNrc3VtIHRha2lu
ZyBpbnRvICBhY2NvdW50IHRoZSB3aG9sZQ0KPj5JUHY2K1NSSC4NCj4+Pj4+Pj4gSGVyZSwgdGhl
cmVz4oCZIG5vdGhpbmcgbmV3ICBjb21wYXJlZCB0byByZmMyNDYwLg0KPj4+Pj4+Pg0KPj4+Pj4+
PiAyLiB0aGUgU1JIIGlzIG9yaWdpbmF0ZWQgYnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1Ig
ZG9tYWluLg0KPj4+Pj4+PiBUaGlzIGlzIGRvbmUgYnkgZW5jYXBzdWxhdGluZyB0aGUgcGFja2V0
IGludG8gYSBvdXRlcg0KPj4+Pj4+PiAoYWRkaXRpb25hbCkgaXB2NiBoZWFkZXIgZm9sbG93ZWQg
YnkgYW4gU1JILiBUaGlzIGlzIEwzDQo+Pj4+Pj4+IGVuY2Fwc3VsYXRpb24gYW5kIG5vIEw0IGNo
ZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSAgcGFja2V0DQo+Pj4+Pj4+IGxlYXZlcyB0aGUg
U1IgdHVubmVsIHRoZSBvdXRlciBlbmNhcHN1bGF0aW9uICAoaW5jbHVkaW5nIHRoZSBTUkgpDQo+
Pj4+Pj4+IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVzICBpdHMgam91cm5leSBs
aWtlIG5vdGhpbmcNCj5oYXBwZW5lZC4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gcy4NCj4+Pj4+Pj4NCj4+
Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+PiBUaGFua3MsDQo+Pj4+Pj4+PiBUYWwuDQo+Pj4+Pj4+
Pg0KPj4+Pj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+Pj4+Pj4gRnJvbTog
U3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzpzcHJldmlkaUBjaXNjby5jb208bWFp
bHRvOnNwcmV2aWRpQGNpc2NvLmNvbT5dDQo+Pj4+Pj4+Pj4gU2VudDogTW9uZGF5LCBNYXkgMTYs
IDIwMTYgMTE6NTkgQU0NCj4+Pj4+Pj4+PiBUbzogT2xlIFRyw7hhbjsgVGFsIE1penJhaGkNCj4+
Pj4+Pj4+PiBDYzogZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMu
aWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRv
b2xzLmlldGYub3JnPjsNCj4+Pj4+Pj4+PiBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0Bp
ZXRmLm9yZz47IDZtYW4gV0cNCj4+Pj4+Pj4+PiBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hl
Y2tzdW0gYW5kDQo+Pj4+Pj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVh
ZGVyDQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBPbiBNYXkgMTUsIDIwMTYsIGF0
IDg6MDYgUE0sIG90cm9hbkBlbXBsb3llZXMub3JnPG1haWx0bzpvdHJvYW5AZW1wbG95ZWVzLm9y
Zz4gd3JvdGU6DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IFRhbCwNCj4+Pj4+Pj4+Pj4NCj4+Pj4+
Pj4+Pj4+IFtBcG9sb2dpZXMgaWYgdGhpcyBpc3N1ZSBoYXMgYmVlbiBkaXNjdXNzZWQgYmVmb3Jl
Ll0NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSDQo+Pj4+Pj4+Pj4+PiBTZWdtZW50DQo+
Pj4+Pj4+Pj4gRW5kcG9pbnQgTm9kZeKAmSB1cGRhdGVzIHRoZSBEZXN0aW5hdGlvbiBJUCBhZGRy
ZXNzLg0KPj4+Pj4+Pj4+Pj4gVGhlcmVmb3JlLCBpdCBtdXN0IGFsc28gdXBkYXRlIHRoZSBMYXll
ciA0IENoZWNrc3VtLCByaWdodD8NCj4+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBJIHdvbmRlciBp
ZiB0aGVyZSBpcyBhbiB1cHBlciBib3VuZCBvbiB0aGUgc2l6ZSBvZiB0aGUgU1JILg0KPj4+Pj4+
Pj4+Pj4gT3RoZXJ3aXNlLCB0aGUNCj4+Pj4+Pj4+PiBMNCBDaGVja3N1bSBtYXkgYmUgbG9jYXRl
ZCBpbiBhIHByZXR0eSBkZWVwIGxvY2F0aW9uLg0KPj4+Pj4+Pj4+Pj4gU3BlYWtpbmcgZnJvbSBh
IGNoaXAgdmVuZG9y4oCZcyBwZXJzcGVjdGl2ZSB0aGlzIG1heSBiZSBhIHByb2JsZW0uDQo+Pj4+
Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IEZyb20gUkZDMjQ2MCwgUkgwOg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+
Pj4+Pg0KPj4+Pj4+Pj4+PiAgIG8gIElmIHRoZSBJUHY2IHBhY2tldCBjb250YWlucyBhIFJvdXRp
bmcgaGVhZGVyLCB0aGUgRGVzdGluYXRpb24NCj4+Pj4+Pj4+Pj4gICAgICBBZGRyZXNzIHVzZWQg
aW4gdGhlIHBzZXVkby1oZWFkZXIgaXMgdGhhdCBvZiB0aGUgZmluYWwNCj4+Pj4+Pj4+Pj4gICAg
ICBkZXN0aW5hdGlvbi4gIEF0IHRoZSBvcmlnaW5hdGluZyBub2RlLCB0aGF0IGFkZHJlc3Mgd2ls
bCBiZSBpbg0KPj4+Pj4+Pj4+PiAgICAgIHRoZSBsYXN0IGVsZW1lbnQgb2YgdGhlIFJvdXRpbmcg
aGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMpLA0KPj4+Pj4+Pj4+PiAgICAgIHRoYXQgYWRkcmVz
cyB3aWxsIGJlIGluIHRoZSBEZXN0aW5hdGlvbiBBZGRyZXNzIGZpZWxkIG9mIHRoZQ0KPj4+Pj4+
Pj4+PiAgICAgIElQdjYgaGVhZGVyLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBJIHdvdWxkIGV4
cGVjdCBTUiB3b3VsZCB3b3JrIHRoZSBzYW1lLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4NCj4+Pj4+
Pj4+PiBleGFjdGx5Lg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gTW9yZW92ZXIsIGRyYWZ0LWlldGYt
Nm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXMNCj4+Pj4+Pj4+PiBlbmNhcHN1bGF0
aW9uIHNvIGNsZWFybHkgdGhlcmXigJlzIG5vIEw0IGludm9sdmVkIGhlcmUuDQo+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+PiBzLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+
Pj4gQ2hlZXJzLA0KPj4+Pj4+Pj4+PiBPbGUNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+DQo+Pj4+Pj4N
Cj4+Pj4NCj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+Pj4gSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFp
bGluZyBsaXN0IGlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+IEFkbWluaXN0cmF0
aXZlDQo+Pj4+IFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2lwdjYNCj4+Pj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPm52bzMgbWFpbGluZyBsaXN0DQo+bnZvM0BpZXRmLm9yZzxt
YWlsdG86bnZvM0BpZXRmLm9yZz4NCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL252bzMNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQpzcHJpbmcgbWFpbGluZyBsaXN0DQpzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0BpZXRm
Lm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3ByaW5nDQoNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsNCgltc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9udC1zaXplOjEy
LjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnAuTXNvQWNl
dGF0ZSwgbGkuTXNvQWNldGF0ZSwgZGl2Lk1zb0FjZXRhdGUNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBjbTsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjguMHB0Ow0KCWZvbnQtZmFtaWx5
OiJUYWhvbWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5
bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCglt
c28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fu
cy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwt
cmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0
OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4w
cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxl
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIg
c3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48
eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQi
IGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+
DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNs
YXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIFJvYmVydCw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoYXQgbWFr
ZXMgc2Vuc2UuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhvd2V2ZXIsIGluIHRoaXMg
Y2FzZSB0aGUgZmlndXJlcyBtYXkgYmUgYSBiaXQgY29uZnVzaW5nIFdSVCB0aGUgcG9zc2libGUg
ZXhpc3RlbmNlIG9mIGV4dGVuc2lvbiBoZWFkZXJzLiBUaGlzIGNvbmZ1c2lvbiBpcyB3aGF0IGxl
ZCB0byB0aGUgZGlzY3Vzc2lvbiBpbiB0aGlzDQogdGhyZWFkIGFib3V0IHdoZXRoZXIgc2VnbWVu
dCByb3V0aW5nIGlzIHBvc3NpYmxlIHdpdGggVlhMQU4vVlhMQU4tR1BFL0dlbmV2ZSBlbmNhcHN1
bGF0aW9ucy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPkluIG9yZGVyIHRvIGF2b2lkIGFtYmlndWl0eSwgaXQgd291bGQg
YmUgZ3JlYXQgaWYgdGhlIGF1dGhvcnMgY291bGQgZXhwbGljaXRseSBtZW50aW9uIHRoYXQgSVB2
NiBleHRlbnNpb24gaGVhZGVycyBhcmUgcGVybWl0dGVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+UmVnYXJkcyw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGFsLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQi
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDsiPiBycmFzenVrQGdtYWlsLmNvbSBbbWFpbHRvOnJyYXN6dWtAZ21h
aWwuY29tXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5Sb2JlcnQgUmFzenVrPGJyPg0KPGI+U2VudDo8
L2I+IE1vbmRheSwgTWF5IDIzLCAyMDE2IDEwOjQ3IEFNPGJyPg0KPGI+VG86PC9iPiBUYWwgTWl6
cmFoaTxicj4NCjxiPkNjOjwvYj4gc3ByaW5nQGlldGYub3JnOyA2bWFuIFdHOyBkcmFmdC1pZXRm
LW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3JnOyBudm8zQGlldGYub3JnOyBkcmFmdC1pZXRm
LTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzsgZHJhZnQtaWV0Zi1u
dm8zLWdlbmV2ZUB0b29scy5pZXRmLm9yZzsgU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSk8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtudm8zXSBbc3ByaW5nXSBMNCBDaGVja3N1bSBhbmQgZHJh
ZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5IaSBUYWws
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5JbmRlZWQgLi4gSSBzYXcgdGhlIGZpZ3Vy
ZXMsIGJ1dCBmaWd1cmVzIGFyZSBub24gbm9ybWF0aXZlIGluIGFueSBkcmFmdC9yZmMgdW5sZXNz
IHRleHQgYmVsb3cgc3BlY2lmaWNhbGx5IHNwZWxscyBpdCBvdXQuJm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gb3IgZXhhbXBsZSBmcm9tIHZ4bGFuLWdwZTombmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZxdW90OzxzcGFuIHN0eWxlPSJjb2xvcjpibGFj
ayI+V2hlbiB0aGUgb3V0ZXIgSVAgaGVhZGVyIGlzIElQdjQsIFZURVBzIE1VU1Qgc2V0IHRoZSBE
RiBiaXQuJnF1b3Q7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+QmVzaWRl
cyBpdCBpcyBwcmV0dHkgY2hhbGxlbmdpbmcgdG8gYWRkIGFuaW1hdGlvbiB0byB0aGUgY3VycmVu
dCBkcmFmdCBmb3JtYXRzIHRvIGlsbHVzdHJhdGUgYWxsIHBvc3NpYmx5IGFsbG93ZWQgZmllbGQg
dmFsdWVzL2NvbWJpbmF0aW9ucyBpbiBhbnkgZmlndXJlIDopICZuYnNwO0ZpZ3VyZXMganVzdCBp
bGx1c3RyYXRlIG9uZSB1c2UNCiBleGFtcGxlLiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+VG8gbWUgdGhlIGN1cnJlbnQgc3BlY3MgcGVybWl0IGFueSB2YWx1ZSBvZiBJUHY2
IE54dEhkciBmaWVsZCBhcyBwZXJtaXR0ZWQgaW4gYm90aCBlbmNhcHN1bGF0aW9ucy48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkJlc3QsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlJvYmVydC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5PbiBNb24sIE1heSAyMywgMjAxNiBhdCA5OjM1IEFNLCBUYWwgTWl6
cmFoaSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFu
ayI+dGFsbWlAbWFydmVsbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+SGkgUm9iZXJ0LDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZndDs8L3NwYW4+DQo8c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+V2hlcmUgc2F5IGluIGRyYWZ0IGRyYWZ0LXF1aW5uLXZ4
bGFuLWdwZSBkbyB5b3Ugc2VlIHN1Y2ggc3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkNCjwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZndDsgdGhhdCB2NiBOeHRIZHIgbXVzdCBiZSBv
bmx5IGVxdWFsIHRvIDE3IChVRFApIGFuZCBub3QgYmUgYSBwb2ludGVyIHRvIGFueSBvdGhlciB0
eXBlDQo8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mZ3Q7IG9mIGV4dGVuc2lvbiBo
ZWFkZXIgZnVydGhlciBmb2xsb3dlZCBieSBVRFAgPzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoZSBmb2xsb3dpbmcgdGV4dCBpcyBmcm9tIEZp
Z3VyZSA0IGluIGRyYWZ0LWlldGYtbnZvMy12eGxhbi1ncGU6PC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgT3V0ZXIgSVB2NiBIZWFkZXI6PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzs8L3NwYW4+PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8VmVyc2lvbnwgVHJhZmZpYyBDbGFzcyB8Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEZs
b3cgTGFiZWwmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfDwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICYjNDM7LSYjNDM7LSYj
NDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7
LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYj
NDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7
LSYjNDM7LSYjNDM7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
fCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBQYXlsb2Fk
IExlbmd0aCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8IE54dEhk
cj0xNyhVRFApfCZuYnNwOyZuYnNwOyBIb3AgTGltaXQmbmJzcDsmbmJzcDsgfDwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7
LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYj
NDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7
LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYjNDM7LSYj
NDM7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjojMUY0OTdEIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfCZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDt8PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlcmUgaXMgYSBzaW1pbGFyIGZpZ3VyZSBpbiBkcmFmdC1p
ZXRmLW52bzMtZ2VuZXZlLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJlc3QgcmVnYXJkcyw8L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5UYWwuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxk
aXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4w
cHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPiBudm8zIFttYWlsdG86PGEgaHJlZj0ibWFpbHRvOm52bzMtYm91bmNl
c0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzMtYm91bmNlc0BpZXRmLm9yZzwvYT5dDQo8
Yj5PbiBCZWhhbGYgT2YgPC9iPlJvYmVydCBSYXN6dWs8YnI+DQo8Yj5TZW50OjwvYj4gTW9uZGF5
LCBNYXkgMjMsIDIwMTYgMTA6MjkgQU08YnI+DQo8Yj5Ubzo8L2I+IFRhbCBNaXpyYWhpPGJyPg0K
PGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86c3ByaW5nQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFu
ayI+c3ByaW5nQGlldGYub3JnPC9hPjsgNm1hbiBXRzsNCjxhIGhyZWY9Im1haWx0bzpkcmFmdC1p
ZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZHJhZnQt
aWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86
bnZvM0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzNAaWV0Zi5vcmc8L2E+OyA8YSBocmVm
PSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0
Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmct
aGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtbnZv
My1nZW5ldmVAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWlldGYtbnZv
My1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc8L2E+OyBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKTwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbnZvM10gW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5k
IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+SGkgVGFsLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDsiPiZndDsmbmJzcDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5kcmFm
dHMgc2VlbSB0byBpbXBseTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPldoZXJl
IHNheSBpbiBkcmFmdCZuYnNwO2RyYWZ0LXF1aW5uLXZ4bGFuLWdwZSBkbyB5b3Ugc2VlIHN1Y2gg
c3RhdGVtZW50IHRoYXQgd291bGQgaW1wbHkgdGhhdCB2NiBOeHRIZHIgbXVzdCBiZSBvbmx5IGVx
dWFsIHRvIDE3IChVRFApDQogYW5kIG5vdCBiZSBhIHBvaW50ZXIgdG8gYW55IG90aGVyIHR5cGUg
b2YgZXh0ZW5zaW9uIGhlYWRlciBmdXJ0aGVyIGZvbGxvd2VkIGJ5IFVEUCA/Jm5ic3A7PC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90OyI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+VGh4LDxicj4NClIuPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+T24gTW9uLCBNYXkgMjMsIDIwMTYgYXQgNzo1MCBBTSwgVGFsIE1penJh
aGkgJmx0OzxhIGhyZWY9Im1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbSIgdGFyZ2V0PSJfYmxhbmsi
PnRhbG1pQG1hcnZlbGwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPkRlYXIgQXV0aG9ycyBvZiBWWExBTi1HUEUgLyBHZW5ldmUsPGJyPg0K
PGJyPg0KSSBhbSByZWl0ZXJhdGluZyBvbiB0aGlzIHF1ZXN0aW9uLCBhcyBJIGhhdmVuJ3Qgc2Vl
biBhIHJlc3BvbnNlIHlldDo8YnI+DQo8YnI+DQpIYXZlIHlvdSBjb25zaWRlcmVkIHRoZSB1c2Ug
b2YgU2VnbWVudCBSb3V0aW5nIHdpdGggVlhMQU4tR1BFIC8gR2VuZXZlPyBUaGUgY3VycmVudCBW
WExBTi1HUEUgLyBHZW5ldmUgZHJhZnRzIHNlZW0gdG8gaW1wbHkgdGhhdCBJUHY2IGV4dGVuc2lv
biBoZWFkZXJzIGFyZSBjdXJyZW50bHkgbm90IHN1cHBvcnRlZC48YnI+DQo8YnI+DQpUaGFua3Ms
PGJyPg0KVGFsLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxicj4NCjxicj4NCjxicj4NCiZndDstLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxi
cj4NCiZndDtGcm9tOiBudm8zIFttYWlsdG86PGEgaHJlZj0ibWFpbHRvOm52bzMtYm91bmNlc0Bp
ZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzMtYm91bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJl
aGFsZiBPZiBUYWwgTWl6cmFoaTxicj4NCiZndDtTZW50OiBUdWVzZGF5LCBNYXkgMTcsIDIwMTYg
MTI6MDkgUE08YnI+DQomZ3Q7VG86IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpOyBUb20gSGVy
YmVydDsgZHJhZnQtaWV0Zi1udm8zLTxicj4NCiZndDs8YSBocmVmPSJtYWlsdG86Z2VuZXZlQHRv
b2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+Z2VuZXZlQHRvb2xzLmlldGYub3JnPC9hPjsN
CjxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayI+ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9y
ZzwvYT48YnI+DQomZ3Q7Q2M6IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0Zi5vcmciIHRhcmdl
dD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86bnZvM0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0KbnZvM0BpZXRmLm9yZzwvYT47IDZtYW4gV0c7IGRyYWZ0
LWlldGYtNm1hbi1zZWdtZW50LTxicj4NCiZndDs8YSBocmVmPSJtYWlsdG86cm91dGluZy1oZWFk
ZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5yb3V0aW5nLWhlYWRlckB0b29scy5p
ZXRmLm9yZzwvYT48YnI+DQomZ3Q7U3ViamVjdDogUmU6IFtudm8zXSBbc3ByaW5nXSBMNCBDaGVj
a3N1bSBhbmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtPGJyPg0KJmd0O3JvdXRpbmctaGVhZGVy
PGJyPg0KJmd0Ozxicj4NCiZndDtTdGVmYW5vLDxicj4NCiZndDs8YnI+DQomZ3Q7SWYgSSB1bmRl
cnN0YW5kIHlvdXIgcG9pbnQgY29ycmVjdGx5Ojxicj4NCiZndDtJUHY2IHNlZ21lbnQgcm91dGlu
ZyBkb2VzIG5vdCB3b3JrIHdpdGggVlhMQU4gLyBWWExBTi1HUEUgLyBHZW5ldmUsIHNpbmNlPGJy
Pg0KJmd0O3RoZXNlIGVuY2Fwc3VsYXRpb25zIGRvIG5vdCBjdXJyZW50bHkgYWxsb3cgdGhlIHVz
ZSBvZiBJUHY2IGV4dGVuc2lvbjxicj4NCiZndDtoZWFkZXJzLjxicj4NCiZndDs8YnI+DQomZ3Q7
SSB3b25kZXIgaWYgdGhlIGF1dGhvcnMgb2YgVlhMQU4tR1BFIGFuZCBHZW5ldmUgaGF2ZSBjb25z
aWRlcmVkIHRoZSB1c2Ugb2Y8YnI+DQomZ3Q7c2VnbWVudCByb3V0aW5nLjxicj4NCiZndDs8YnI+
DQomZ3Q7VGhhbmtzLDxicj4NCiZndDtUYWwuPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7
PGJyPg0KJmd0OyZndDstLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsmZ3Q7RnJv
bTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86c3By
ZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08
YnI+DQomZ3Q7Jmd0O1NlbnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAxMDo0MSBBTTxicj4NCiZn
dDsmZ3Q7VG86IFRvbSBIZXJiZXJ0PGJyPg0KJmd0OyZndDtDYzogVGFsIE1penJhaGk7IDZtYW4g
V0c7IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5zcHJp
bmdAaWV0Zi5vcmc8L2E+Ozxicj4NCiZndDsmZ3Q7ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91
dGluZy0gPGEgaHJlZj0ibWFpbHRvOmhlYWRlckB0b29scy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxh
bmsiPg0KaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjxicj4NCiZndDsmZ3Q7U3ViamVjdDogUmU6
IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5n
LTxicj4NCiZndDsmZ3Q7aGVhZGVyPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZn
dDsmZ3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDc6MTAgUE0sIFRvbSBIZXJiZXJ0ICZsdDs8
YSBocmVmPSJtYWlsdG86dG9tQGhlcmJlcnRsYW5kLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnRvbUBo
ZXJiZXJ0bGFuZC5jb208L2E+Jmd0Ozxicj4NCiZndDt3cm90ZTo8YnI+DQomZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsgT24gTW9uLCBNYXkgMTYsIDIwMTYgYXQgNDozMiBBTSwgVGFsIE1p
enJhaGkgJmx0OzxhIGhyZWY9Im1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbSIgdGFyZ2V0PSJfYmxh
bmsiPnRhbG1pQG1hcnZlbGwuY29tPC9hPiZndDs8YnI+DQomZ3Q7Jmd0O3dyb3RlOjxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5vdCBsYXllci0yLjxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgcy48YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBSaWdodC4gSG93ZXZlciwgaXQg
YXBwZWFycyB0aGF0IGF0IGxlYXN0IGluIHNvbWUgY2FzZXMgYSBWWExBTiBWVEVQPGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyB3aWxsPGJyPg0KJmd0OyZndDt1c2UgU1IuIEl0IGNlcnRhaW5seSBtYXkg
YmUgdGhlIGNhc2UgaW4gU0ZDIHVzZSBjYXNlcyAoc2VlIFNlY3Rpb24gMi4zPGJyPg0KJmd0OyZn
dDtpbiBkcmFmdC0gaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMpLjxicj4NCiZndDsmZ3Q7Jmd0
OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXIgbWVudGlvbnMgdGhhdCB0aGUgcGFja2V0IGlzPGJyPg0K
Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRlZDxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+
DQomZ3Q7Jmd0O2ludG8gYW4gb3V0ZXIgaXB2NiBoZWFkZXIgd2hpY2ggbWFrZXMgaXQgYSBsYXll
ci0zIGVuY2FwLjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsg
LCBidXQgSSBkb24ndCB0aGluayBpdCBpcyBleHBsaWNpdCBhcyB0byBleGFjdCBlbmNhcHN1bGF0
aW9uIGZvcm1hdDxicj4NCiZndDsmZ3Q7Jmd0OyAoSSBzdXBwb3NlIHNpbXBsZSBpcDZpcDYgaXMg
aW1wbGllZCkuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7c2VlIHNl
Y3Rpb24gMi4yPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBC
dXQsIGl0PGJyPg0KJmd0OyZndDsmZ3Q7IHNlZW1zIGxpa2UgYW55IG9mIHNldmVyYWwgZW5jYXBz
dWxhdGlvbiB0ZWNobmlxdWVzIGNvdWxkIHdvcmsgKFZYTEFOLDxicj4NCiZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0O0kgaGF2ZSBzb21lIHByb2JsZW1zIHRvIHVuZGVyc3RhbmQg
d2hlcmUgdG8gZml0IGFuIGV4dGVuc2lvbiBoZWFkZXI8YnI+DQomZ3Q7Jmd0O2ludG8gYSB2eGxh
biBlbmNhcOKApjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsg
R1JFL0lQLCBFU1AvSVAsIEdVRSwgZm9vIG92ZXIgVURQLCBldGMuKSBhbmQgaWYgYSBkZXZpY2Ug
dGhhdCB3YW50czxicj4NCiZndDsmZ3Q7Jmd0OyB0byBkbyBTUiBpcyBhbHJlYWR5IGRvaW5nIHR1
bm5lbGluZyBpdCBzZWVtcyByZWFzb25hYmxlIHRvIG1lIHRvIG9ubHk8YnI+DQomZ3Q7Jmd0OyZn
dDsgaGF2ZSBvbmUgbGF5ZXIgb2YgZW5jYXBzdWxhdGlvbi4gTWF5YmUgdGhpcyBzaG91bGQgYmUg
Y2xhcmlmaWVkIGluPGJyPg0KJmd0OyZndDsmZ3Q7IHRoZSBkcmFmdD88YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDt0aGUgZHJhZnQgaXMgYWJvdXQgSVB2NiBleHRlbnNp
b24gaGVhZGVyIGFuZCBtb3JlIHByZWNpc2VseSBhIG5ldyB0eXBlPGJyPg0KJmd0OyZndDtvZiB0
aGUgcm91dGluZyBleHRlbnNpb24gaGVhZGVyIGRlZmluZWQgaW4gcmZjMjQ2MC4gVGhhdOKAmXMg
dGhlIGNvbnRleHQuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7cy48
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBUb208YnI+DQomZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsgRnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVm
PSJtYWlsdG86c3ByZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lz
Y28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTZW50OiBNb25kYXksIE1heSAx
NiwgMjAxNiAyOjI0IFBNPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgVG86IFRhbCBNaXpyYWhp
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6IE9sZSBUcsO4YW47PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRp
bmctaGVhZGVyQHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+DQpkcmFmdC1pZXRmLTZt
YW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzwvYT47PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0BpZXRmLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiPnNwcmluZ0BpZXRmLm9yZzwvYT47IDZtYW4gV0c8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5kPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy0gaGVhZGVyPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDE6MTkgUE0sIFRhbCBNaXpy
YWhpICZsdDs8YSBocmVmPSJtYWlsdG86dGFsbWlAbWFydmVsbC5jb20iIHRhcmdldD0iX2JsYW5r
Ij50YWxtaUBtYXJ2ZWxsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIaSBTdGVmYW5vLDxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUaGFu
a3MgYWdhaW4gZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAyLiB0aGUgU1JIIGlzIG9y
aWdpbmF0ZWQgYnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9tYWluLjxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhpcyBpcyBkb25lIGJ5IGVuY2Fwc3VsYXRpbmcgdGhl
IHBhY2tldCBpbnRvIGEgb3V0ZXI8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IChh
ZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkguIFRoaXMgaXMgTDM8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRpb24gYW5kIG5vIEw0IGNo
ZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSZuYnNwOyBwYWNrZXQ8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IGxlYXZlcyB0aGUgU1IgdHVubmVsIHRoZSBvdXRlciBlbmNhcHN1
bGF0aW9uJm5ic3A7IChpbmNsdWRpbmcgdGhlIFNSSCk8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGludWVzJm5ic3A7IGl0cyBq
b3VybmV5IGxpa2Ugbm90aGluZzxicj4NCiZndDtoYXBwZW5lZC48YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU28gVlhMQU4gaXMgb2Zm
IHRoZSB0YWJsZT88YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgaXTigJlzIGFsbCBhYm91dCBJUCwgbm90
IGxheWVyLTIuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyBzLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgSXQgd291bGQgYmUgd29ydGh3aGlsZSB0
byBjbGFyaWZ5IHRoaXMgaW4gdGhlIGRyYWZ0LiBJZiB5b3UgaGF2ZSBhPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7IHNwZWNpZmljPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgZW5jYXBz
dWxhdGlvbiBpbiBtaW5kLCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUgZHJhZnQgd291bGQgc3Bl
Y2lmeSBpdC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsgVGhhbmtzLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUYWwuPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgRnJvbTogU3RlZmFubyBQcmV2
aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86c3ByZXZpZGlAY2lzY28uY29t
IiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MTMgUE08YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRvOiBUYWwgTWl6cmFoaTxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6IE9sZSBUcsO4YW47PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQt
cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWll
dGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0Zi5v
cmciIHRhcmdldD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+OyA2bWFuIFdHPGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tz
dW0gYW5kPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLSBoZWFkZXI8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIaSw8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPbiBNYXkg
MTYsIDIwMTYsIGF0IDExOjA0IEFNLCBUYWwgTWl6cmFoaSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRh
bG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGFsbWlAbWFydmVsbC5jb208L2E+Jmd0
Ozxicj4NCiZndDsmZ3Q7d3JvdGU6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIaSBTdGVmYW5vLDxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgVGhhbmtzIGZvciB0aGUgcmVzcG9uc2VzLjxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7IGV4YWN0bHkuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IE1vcmVvdmVyLCBkcmFm
dC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVzPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRpb24gc28gY2xlYXJseSB0aGVy
ZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgcy48
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IFR3byBxdWVzdGlvbnM6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlvbiBpcyBWWExBTj8gTDQg
d291bGQgc3RpbGwgYmU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBpbnZv
bHZlZCw8YnI+DQomZ3Q7Jmd0O3JpZ2h0Pzxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyBTZWUgYmVsb3cuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyAyLiBXaGVuIHlvdSBzYXkgJ2Fzc3VtZXMgZW5jYXBzdWxhdGlvbics
IGRvZXMgaXQgbWVhbiB0aGF0IGE8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyBob3N0IGNhbm5vdDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgc2VuZCBhbiBJ
UHY2IHBhY2tldCB3aXRoIGFuIFNSSD8gVGhlIGN1cnJlbnQgZHJhZnQgc2F5czo8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFueSBub2RlIG9yaWdpbmF0aW5nIGFu
IElQdjYgcGFja2V0IHdpdGg8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBp
dHM8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBJUHY2IGFuZCBTZWdtZW50
IFJvdXRpbmcgSGVhZGVycy4mbmJzcDsgVGhpcyBpbmNsdWRlIGVpdGhlcjo8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jm5ic3A7ICZuYnNwOyBBIGhvc3Qgb3JpZ2luYXRpbmcgYW4gSVB2NiBwYWNrZXQuPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgQW4gU1IgZG9tYWluIGluZ3Jlc3Mgcm91dGVy
IGVuY2Fwc3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldDxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyBpbnRvIGFuIG91dGVyIElQdjYgaGVhZGVy
IGZvbGxvd2VkIGJ5IGFuIFNSSC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyBXaWxsIGFwcHJlY2lhdGUgaWYgeW91IGNhbiBjbGFyaWZ5IHRoYXQuPGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IG9rLCB0d28gY2FzZXM6PGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsg
MS4gdGhlIFNSSCBpcyBpbnNlcnRlZCBhdCB0aGUgc291cmNlLjxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgdGhlIHNvdXJjZSBvcmlnaW5hdGVzIHRoZSBwYWNrZXQsIHRoZSBpcHY2
IGhlYWRlciBhbmQmbmJzcDsgdGhlIFNSSC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7IFRoZSBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tzdW0gdGFraW5nIGludG8mbmJzcDsgYWNj
b3VudCB0aGUgd2hvbGU8YnI+DQomZ3Q7Jmd0O0lQdjYmIzQzO1NSSC48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IEhlcmUsIHRoZXJlc+KAmSBub3RoaW5nIG5ldyZuYnNwOyBjb21w
YXJlZCB0byByZmMyNDYwLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDIuIHRoZSBTUkggaXMgb3JpZ2luYXRlZCBieSB0
aGUgaW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyBUaGlzIGlzIGRvbmUgYnkgZW5jYXBzdWxhdGluZyB0aGUgcGFja2V0IGludG8g
YSBvdXRlcjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgKGFkZGl0aW9uYWwpIGlw
djYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMzxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsgZW5jYXBzdWxhdGlvbiBhbmQgbm8gTDQgY2hlY2tzdW0gaXMgaW52
b2x2ZWQuIFdoZW4gdGhlJm5ic3A7IHBhY2tldDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsgbGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fwc3VsYXRpb24mbmJzcDsg
KGluY2x1ZGluZyB0aGUgU1JIKTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgaXMg
cmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51ZXMmbmJzcDsgaXRzIGpvdXJuZXkgbGlrZSBu
b3RoaW5nPGJyPg0KJmd0O2hhcHBlbmVkLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHMuPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7IFRoYW5rcyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyBUYWwuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgRnJvbTogU3RlZmFubyBQ
cmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86c3ByZXZpZGlAY2lzY28u
Y29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU2VudDogTW9uZGF5LCBNYXkgMTYsIDIwMTYg
MTE6NTkgQU08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVG86IE9s
ZSBUcsO4YW47IFRhbCBNaXpyYWhpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7IENjOiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGlu
Zy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWlldGYtNm1h
bi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjs8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnNwcmluZ0BpZXRmLm9yZzwvYT47IDZtYW4gV0c8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU3ViamVjdDogUmU6IFtzcHJpbmdd
IEw0IENoZWNrc3VtIGFuZDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXI8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
IE9uIE1heSAxNSwgMjAxNiwgYXQgODowNiBQTSwgPGEgaHJlZj0ibWFpbHRvOm90cm9hbkBlbXBs
b3llZXMub3JnIiB0YXJnZXQ9Il9ibGFuayI+DQpvdHJvYW5AZW1wbG95ZWVzLm9yZzwvYT4gd3Jv
dGU6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGFsLDxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBbQXBvbG9naWVzIGlmIHRoaXMgaXNzdWUgaGFzIGJl
ZW4gZGlzY3Vzc2VkIGJlZm9yZS5dPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFk
ZXIsIGFuIOKAmFNSPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsgU2VnbWVudDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBF
bmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQIGFkZHJlc3MuPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhlcmVmb3JlLCBp
dCBtdXN0IGFsc28gdXBkYXRlIHRoZSBMYXllciA0IENoZWNrc3VtLCByaWdodD88YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEkgd29uZGVyIGlmIHRoZXJlIGlzIGFu
IHVwcGVyIGJvdW5kIG9uIHRoZSBzaXplIG9mIHRoZSBTUkguPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgT3RoZXJ3aXNlLCB0aGU8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgTDQgQ2hlY2tzdW0gbWF5IGJlIGxvY2F0ZWQg
aW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlvbi48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTcGVha2luZyBmcm9tIGEgY2hpcCB2ZW5kb3LigJlzIHBlcnNw
ZWN0aXZlIHRoaXMgbWF5IGJlIGEgcHJvYmxlbS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBGcm9tIFJGQzI0NjAsIFJIMDo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsg
Jm5ic3A7byZuYnNwOyBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFpbnMgYSBSb3V0aW5nIGhlYWRl
ciwgdGhlIERlc3RpbmF0aW9uPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IEFkZHJlc3MgdXNlZCBpbiB0aGUgcHNldWRvLWhl
YWRlciBpcyB0aGF0IG9mIHRoZSBmaW5hbDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBkZXN0aW5hdGlvbi4mbmJzcDsgQXQg
dGhlIG9yaWdpbmF0aW5nIG5vZGUsIHRoYXQgYWRkcmVzcyB3aWxsIGJlIGluPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IHRo
ZSBsYXN0IGVsZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0aGUgcmVjaXBpZW50KHMp
LDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsgJm5i
c3A7ICZuYnNwOyB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVz
cyBmaWVsZCBvZiB0aGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgSVB2NiBoZWFkZXIuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgSSB3b3VsZCBleHBlY3QgU1Igd291bGQgd29yayB0aGUgc2FtZS48YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsgZXhhY3RseS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgTW9yZW92ZXIsIGRy
YWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3VtZXM8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRo
ZXJl4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBz
Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7IENoZWVycyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7IE9sZTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IC0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWls
aW5nIGxpc3QgPGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4N
CmlwdjZAaWV0Zi5vcmc8L2E+IEFkbWluaXN0cmF0aXZlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBS
ZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
cHY2IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL2lwdjY8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDs8
YnI+DQomZ3Q7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188
YnI+DQomZ3Q7bnZvMyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7PGEgaHJlZj0ibWFpbHRvOm52bzNA
aWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5udm8zQGlldGYub3JnPC9hPjxicj4NCiZndDs8YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL252bzMiIHRhcmdldD0i
X2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL252bzM8L2E+PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
PGJyPg0Kc3ByaW5nIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0
Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0i
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9zcHJpbmciIHRhcmdldD0iX2Js
YW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3NwcmluZzwvYT48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_1c27bb3513bc48889ec310e8d143784cILEXCH02marvellcom_--


From nobody Mon May 23 00:59:56 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 835A812D5FA for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 00:59: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 2zVJUuE9M7Zp for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 00:59: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 2D44412D129 for <ipv6@ietf.org>; Mon, 23 May 2016 00:59:52 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 May 2016 07:59:50 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 5036E9CC4F; Mon, 23 May 2016 00:59: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=CgKeZ57SmmIuxxG8rwRe9nOBrUg=; b= Z9QRPqXBsbPXMix0uEGCYjYLJIBhY2hx4HJe+VHRzgvcKrNPD5sazzti5psc94Jl NJuBP4yNxB1At6mQPJyFdj88cqDVFex2jP+r+OV5e7SNdhc9dL4iF2YOFI1er7+j jdK7o2Cjgdrb1s/fzEJ5V2shbsY0Xy8QdkMIOHTvjpk=
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=oGHhBh8kbdsCO3VZc8gNPCR3uf 3+bnfC7AK7tWAt4GmAJ7+CGvWhdFXr/AE2fJPHgwfhf7FxcxJm1nxSIXnpiJkArt 5aVL+ag+bmnJtgBNVGNoPf+/isX2QmTPs8ndlhCUlv5RmG/BgfZ7OWayibiwax/n WVHPEk6el0z3yvjPg=
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 D1F5A9CC4E; Mon, 23 May 2016 00:59:48 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id CFA0416C9EAB; Mon, 23 May 2016 09:59:41 +0200 (CEST)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_36AD1B1E-D92C-4175-9CBD-ABE61231CFEC"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
Date: Mon, 23 May 2016 09:59:37 +0200
Message-Id: <2C580655-9E56-422C-A346-1978CF5B162C@employees.org>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com>
To: =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4PLslKXh1sWyuj8cABcNonVL04g>
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, 23 May 2016 07:59:53 -0000

--Apple-Mail=_36AD1B1E-D92C-4175-9CBD-ABE61231CFEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

[...]

> I've been unwilling to propose text as I didn't even understand the
> authors' actual intent, but if it's actually that "it says what an
> implementation SHOULD do _iff_ a stable IID is to be generated", I'd
> suggest revising the above paragraph as follows:
>=20
>   The recommendations in this document apply only in cases where
>   implementations otherwise would have configured a stable IPv6 IID
>   containing a link layer address.  For example, this document does
>   not change any existing recommendations concerning the use of
>   temporary addresses as specified in [RFC4941], nor do the
>   recommendations apply to cases where the link layer address is not
>   stable (e.g., it is periodically randomized) in the first place,
>   nor does it introduce any new requirements regarding when stable
>   addresses are to be configured.  Thus, the recommendations in this
>   document simply improve the security and privacy properties of
>   stable addresses.
>=20
> If the intent of this document is really just that it applies iff a
> stable IID is to be generated and does not make any judgment on, e.g.,
> use of randomized link-layer addresses, this proposed text shouldn't
> be a problem for anyone. (for some, it may seem to say the obvious and
> therefore redundant, but given that whether randomized LL address is
> good or bad was so controversial here, I think it's helpful to
> explicitly clarify that).  But I was not sure if it's really
> acceptable, especially for the authors, by seeing opinions like
> the "extremely bad" comment.

I think we have an assumption embedded in most of our documents that a =
stable IID is generated on all interfaces.
I don't think this document is the place to to clarify that there might =
be interfaces with only short-lived IIDs.

This document tries to improve the security and privacy of the default =
IID generation mechanism. I think it is clear on that. It's in the =
title, it is in the abstract. I'm not sure how much clearer it is =
possible to make it.

The other consequence of this document is that it forces changes in =
implementations that don't necessarily benefit from the privacy =
improvements. Public servers, router interfaces and so on. Is a =
consequence of updating 2464 that I now have to go and retrofit 7217 =
style IID generation in lots of code? I'm not sure I want to accept the =
collateral damage.

> To be clear, I'm not particularly an advocator of the use of
> randomized link-layer addresses.  But I've seen this as one central
> point concerning how to move forward for this document, so I believe
> we should be at least clear on this in the document text.

With regards to random MAC addresses, I see the arguments that we in =
general shouldn't couple the L3 address with the L2 address.
In that aspect randomized MAC should not have any implication on this =
document.
On the other hand I do see how it would make for a very easy =
implementation change to do random MACs (which you probably have to do =
on certain devices anyway), and keep the current IID generation =
mechanism.

I have to admit that I'm unsure of what the right thing to do is. I'm =
uncomfortable with removing the existing mechanism from all the IPv6 =
over foo documents. I'm not convinced that we are in a position to make =
a recommendation for all scenarios and all devices at this point.=C3=8E

cheers,
Ole


--Apple-Mail=_36AD1B1E-D92C-4175-9CBD-ABE61231CFEC
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

iQEcBAEBCgAGBQJXQrhtAAoJED4aXnjSQuKWqOMH/1/rHvqiYwXxyMyTLSaO+bcg
M7Ov13c8iYml2UGORQpjkO/q8PRMzB96A4VtXtY7clqS8IugzI1KQ17lfCCx544n
8FdUqQhKiupxAP5j5fBuX0SfKghuzxNKGbXPh4c++LokZExwEZ+z9En5eXfLbyx2
54fksJaIKesp77bAIidrqztZeWsA3O7veHtLgmxAPQNp4NZW84ow9UZQSaI1opIO
Bz/BRKMjxfDxa+01tAHAbglMolDGm58b9WHnwMcpcbHyT+dEx6AWJMjOaZPqYSz5
lezlQxxe7+PcyvZJiCQZ9nYba7+QVbc25RcJKYwhWj4HMaJaqG388FZOpTHB0aI=
=2YcM
-----END PGP SIGNATURE-----

--Apple-Mail=_36AD1B1E-D92C-4175-9CBD-ABE61231CFEC--


From nobody Mon May 23 01:10:02 2016
Return-Path: <rraszuk@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 C3BD212D656; Mon, 23 May 2016 01:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 8ABO1pXu2Z_1; Mon, 23 May 2016 01:09:57 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 980C212D64D; Mon, 23 May 2016 01:09:56 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id e126so44207777lfg.2; Mon, 23 May 2016 01:09:56 -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:date:message-id:subject :from:to:cc; bh=NhDnD1GyBvFkk7+CJsCHm+pJ0i0/uudnKCMtzcQnHAc=; b=tQ1wW2hrNHibAUZKT/Jg8JwIYp5RZ4ktiRf0stkGP1xoX0MHlsKVk+78uODRyiqylY jzJ+/7Iw39olhskrbz6zTxSTAKsJryYN1/hrNvcKmeZqkzqzswwA3LtJCjafBBl84U9U EE7o9BfEuI/MxwZ4aA7JH7Z0KSuMpiNOs79q6YW5uoqt8LJN0BlSBh0xfSjOHYDyQYoD CSw7oUNcqR2xmEpxs5k2wbenTmfdBDunv3hSx55k3klWmjyR5H57HkpHOBD3hkcm/Qc+ 4+OZaAD60aVPgIUaX2MUUHjZRUQ0/5oD9RZp/l+rIu2NlFaURIhnvGsGo9ZHKFMVYMWt IeAg==
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:date :message-id:subject:from:to:cc; bh=NhDnD1GyBvFkk7+CJsCHm+pJ0i0/uudnKCMtzcQnHAc=; b=M349/Q5HOpfq/5TffQMQZPlTuqoczRC1YyBsMmjg2+Uata6cVRs3NFVKg3ZnhEyew1 k8Y7MTjJqxbf6inL1hqgNdZKnVoko7nPR7nTzGuZ1VnaF9DQ52PS/1sbT1q03ZJEQ+Hx SSgcy6UBWg7FAmLaWQNb7tD6FJ0JSqNwZUbZt0pxk12k18iP4MmMpyzIYYt4Az6nmx8O 1RNxnHIEKIxdo3GA0536l+6/9LmDq7/Mjth8dZLHOYpkunbD0wugWEsZL74NDyPRKMZe GcH8p9ijCJQhfLzxM5uTgxN6aE9CMnnP20Iws8SeFflCTEkrZJgrQI6sYf6MwRTTuXyg Xjdw==
X-Gm-Message-State: AOPr4FXsVJUdAYPXSn7dXaaGxHRSIRCNx4GtzWCuFH96mtrlyz9FZ5pNn9IuyFFAgJ5KChg6xQa1WPw026Gl5w==
MIME-Version: 1.0
X-Received: by 10.25.152.136 with SMTP id a130mr4597765lfe.104.1463990994609;  Mon, 23 May 2016 01:09:54 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.25.126.210 with HTTP; Mon, 23 May 2016 01:09:54 -0700 (PDT)
In-Reply-To: <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com> <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com>
Date: Mon, 23 May 2016 10:09:54 +0200
X-Google-Sender-Auth: aIS4qnwx_37XzLTxkimaoLI7LWQ
Message-ID: <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
From: Robert Raszuk <robert@raszuk.net>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary=001a11402cb830354505337df7cc
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/trK5OZqboktH_AQd6aLWKsAxIco>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 08:10:01 -0000

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

Hi Tal,

> In order to avoid ambiguity, it would be great if the
> authors could explicitly mention that IPv6 extension
> headers are permitted.

Well the drafts are complaint to RFC2119 (normative reference) so unless
the text excludes elements with MUST/MUST NOT - everything else defined in
the building blocks they (re)use is permitted.

However as you say perhaps for clarity what could be added to those drafts
is a normative reference to IPv4 and IPv6 base RFCs.

Best,
R.


On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <talmi@marvell.com> wrote:

> Hi Robert,
>
>
>
> That makes sense.
>
> However, in this case the figures may be a bit confusing WRT the possible
> existence of extension headers. This confusion is what led to the
> discussion in this thread about whether segment routing is possible with
> VXLAN/VXLAN-GPE/Geneve encapsulations.
>
>
>
> In order to avoid ambiguity, it would be great if the authors could
> explicitly mention that IPv6 extension headers are permitted.
>
>
>
> Regards,
>
> Tal.
>
>
>
> *From:* rraszuk@gmail.com [mailto:rraszuk@gmail.com] *On Behalf Of *Rober=
t
> Raszuk
> *Sent:* Monday, May 23, 2016 10:47 AM
>
> *To:* Tal Mizrahi
> *Cc:* spring@ietf.org; 6man WG; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org;
> nvo3@ietf.org; draft-ietf-6man-segment-routing-header@tools.ietf.org;
> draft-ietf-nvo3-geneve@tools.ietf.org; Stefano Previdi (sprevidi)
> *Subject:* Re: [nvo3] [spring] L4 Checksum and
> draft-ietf-6man-segment-routing-header
>
>
>
> Hi Tal,
>
>
>
> Indeed .. I saw the figures, but figures are non normative in any
> draft/rfc unless text below specifically spells it out.
>
>
>
> For example from vxlan-gpe:
>
>
>
> "When the outer IP header is IPv4, VTEPs MUST set the DF bit."
>
>
>
> Besides it is pretty challenging to add animation to the current draft
> formats to illustrate all possibly allowed field values/combinations in a=
ny
> figure :)  Figures just illustrate one use example.
>
>
>
> To me the current specs permit any value of IPv6 NxtHdr field as permitte=
d
> in both encapsulations.
>
>
>
> Best,
>
> Robert.
>
>
>
>
>
> On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>
> Hi Robert,
>
>
>
>
>
> > Where say in draft draft-quinn-vxlan-gpe do you see such statement that
> would imply
>
> > that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer to
> any other type
>
> > of extension header further followed by UDP ?
>
>
>
>
>
> The following text is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:
>
>
>
>       Outer IPv6 Header:
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |Version| Traffic Class |           Flow Label                  |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |         Payload Length        | NxtHdr=3D17(UDP)|   Hop Limit   |
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>       |                                                               |
>
>
>
>
>
> There is a similar figure in draft-ietf-nvo3-geneve.
>
>
>
> Best regards,
>
> Tal.
>
>
>
> *From:* nvo3 [mailto:nvo3-bounces@ietf.org] *On Behalf Of *Robert Raszuk
> *Sent:* Monday, May 23, 2016 10:29 AM
> *To:* Tal Mizrahi
> *Cc:* spring@ietf.org; 6man WG; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org;
> nvo3@ietf.org; draft-ietf-6man-segment-routing-header@tools.ietf.org;
> draft-ietf-nvo3-geneve@tools.ietf.org; Stefano Previdi (sprevidi)
>
>
> *Subject:* Re: [nvo3] [spring] L4 Checksum and
> draft-ietf-6man-segment-routing-header
>
>
>
> Hi Tal,
>
>
>
> > drafts seem to imply
>
>
>
> Where say in draft draft-quinn-vxlan-gpe do you see such statement that
> would imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a
> pointer to any other type of extension header further followed by UDP ?
>
>
>
> Thx,
> R.
>
>
>
>
>
> On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com> wrote:
>
> Dear Authors of VXLAN-GPE / Geneve,
>
> I am reiterating on this question, as I haven't seen a response yet:
>
> Have you considered the use of Segment Routing with VXLAN-GPE / Geneve?
> The current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension
> headers are currently not supported.
>
> Thanks,
> Tal.
>
>
>
>
> >-----Original Message-----
> >From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Tal Mizrahi
> >Sent: Tuesday, May 17, 2016 12:09 PM
> >To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
> >geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe@tools.ietf.org
> >Cc: spring@ietf.org; nvo3@ietf.org; 6man WG; draft-ietf-6man-segment-
> >routing-header@tools.ietf.org
> >Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
> >routing-header
> >
> >Stefano,
> >
> >If I understand your point correctly:
> >IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sinc=
e
> >these encapsulations do not currently allow the use of IPv6 extension
> >headers.
> >
> >I wonder if the authors of VXLAN-GPE and Geneve have considered the use =
of
> >segment routing.
> >
> >Thanks,
> >Tal.
> >
> >
> >
> >>-----Original Message-----
> >>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>Sent: Tuesday, May 17, 2016 10:41 AM
> >>To: Tom Herbert
> >>Cc: Tal Mizrahi; 6man WG; spring@ietf.org;
> >>draft-ietf-6man-segment-routing- header@tools.ietf.org
> >>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
> >>header
> >>
> >>
> >>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com>
> >wrote:
> >>>
> >>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>
> >>>> Right. However, it appears that at least in some cases a VXLAN VTEP
> >>>> will
> >>use SR. It certainly may be the case in SFC use cases (see Section 2.3
> >>in draft- ietf-spring-ipv6-use-cases).
> >>>>
> >>>
> >>> draft-ietf-6man-segment-routing-header mentions that the packet is
> >>> encapsulated
> >>
> >>
> >>into an outer ipv6 header which makes it a layer-3 encap.
> >>
> >>
> >>> , but I don't think it is explicit as to exact encapsulation format
> >>> (I suppose simple ip6ip6 is implied).
> >>
> >>
> >>see section 2.2
> >>
> >>
> >>> But, it
> >>> seems like any of several encapsulation techniques could work (VXLAN,
> >>
> >>
> >>I have some problems to understand where to fit an extension header
> >>into a vxlan encap=E2=80=A6
> >>
> >>
> >>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
> >>> to do SR is already doing tunneling it seems reasonable to me to only
> >>> have one layer of encapsulation. Maybe this should be clarified in
> >>> the draft?
> >>
> >>
> >>the draft is about IPv6 extension header and more precisely a new type
> >>of the routing extension header defined in rfc2460. That=E2=80=99s the =
context.
> >>
> >>
> >>s.
> >>
> >>
> >>
> >>
> >>>
> >>> Tom
> >>>
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>> Sent: Monday, May 16, 2016 2:24 PM
> >>>>> To: Tal Mizrahi
> >>>>> Cc: Ole Tr=C3=B8an;
> >>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>> spring@ietf.org; 6man WG
> >>>>> Subject: Re: [spring] L4 Checksum and
> >>>>> draft-ietf-6man-segment-routing- header
> >>>>>
> >>>>>
> >>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com> wrote=
:
> >>>>>>
> >>>>>> Hi Stefano,
> >>>>>>
> >>>>>> Thanks again for the prompt response.
> >>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>
> >>>>>> So VXLAN is off the table?
> >>>>>
> >>>>>
> >>>>> it=E2=80=99s all about IP, not layer-2.
> >>>>>
> >>>>> s.
> >>>>>
> >>>>>
> >>>>>> It would be worthwhile to clarify this in the draft. If you have a
> >>>>>> specific
> >>>>> encapsulation in mind, it would be great if the draft would specify
> it.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Tal.
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>> Sent: Monday, May 16, 2016 2:13 PM
> >>>>>>> To: Tal Mizrahi
> >>>>>>> Cc: Ole Tr=C3=B8an;
> >>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>> spring@ietf.org; 6man WG
> >>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>
> >>>>>>> Hi,
> >>>>>>>
> >>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com>
> >>wrote:
> >>>>>>>>
> >>>>>>>> Hi Stefano,
> >>>>>>>>
> >>>>>>>> Thanks for the responses.
> >>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>
> >>>>>>>> Two questions:
> >>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
> >>>>>>>> involved,
> >>right?
> >>>>>>>
> >>>>>>>
> >>>>>>> See below.
> >>>>>>>
> >>>>>>>
> >>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
> >>>>>>>> host cannot
> >>>>>>> send an IPv6 packet with an SRH? The current draft says:
> >>>>>>>>
> >>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
> >>>>>>>> its
> >>>>>>>> IPv6 and Segment Routing Headers.  This include either:
> >>>>>>>>
> >>>>>>>>    A host originating an IPv6 packet.
> >>>>>>>>
> >>>>>>>>    An SR domain ingress router encapsulating a received IPv6
> packet
> >>>>>>>>    into an outer IPv6 header followed by an SRH.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Will appreciate if you can clarify that.
> >>>>>>>
> >>>>>>>
> >>>>>>> ok, two cases:
> >>>>>>>
> >>>>>>> 1. the SRH is inserted at the source.
> >>>>>>> the source originates the packet, the ipv6 header and  the SRH.
> >>>>>>> The source computes L4 checksum taking into  account the whole
> >>IPv6+SRH.
> >>>>>>> Here, theres=E2=80=99 nothing new  compared to rfc2460.
> >>>>>>>
> >>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
> >>>>>>> This is done by encapsulating the packet into a outer
> >>>>>>> (additional) ipv6 header followed by an SRH. This is L3
> >>>>>>> encapsulation and no L4 checksum is involved. When the  packet
> >>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
> >>>>>>> is removed and the packet continues  its journey like nothing
> >happened.
> >>>>>>>
> >>>>>>> s.
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Tal.
> >>>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com]
> >>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
> >>>>>>>>> To: Ole Tr=C3=B8an; Tal Mizrahi
> >>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org;
> >>>>>>>>> spring@ietf.org; 6man WG
> >>>>>>>>> Subject: Re: [spring] L4 Checksum and
> >>>>>>>>> draft-ietf-6man-segment-routing- header
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org wrote:
> >>>>>>>>>>
> >>>>>>>>>> Tal,
> >>>>>>>>>>
> >>>>>>>>>>> [Apologies if this issue has been discussed before.]
> >>>>>>>>>>>
> >>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =E2=
=80=98SR
> >>>>>>>>>>> Segment
> >>>>>>>>> Endpoint Node=E2=80=99 updates the Destination IP address.
> >>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
> >>>>>>>>>>>
> >>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
> >>>>>>>>>>> Otherwise, the
> >>>>>>>>> L4 Checksum may be located in a pretty deep location.
> >>>>>>>>>>> Speaking from a chip vendor=E2=80=99s perspective this may be=
 a
> problem.
> >>>>>>>>>>
> >>>>>>>>>> From RFC2460, RH0:
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>   o  If the IPv6 packet contains a Routing header, the
> Destination
> >>>>>>>>>>      Address used in the pseudo-header is that of the final
> >>>>>>>>>>      destination.  At the originating node, that address will
> be in
> >>>>>>>>>>      the last element of the Routing header; at the
> recipient(s),
> >>>>>>>>>>      that address will be in the Destination Address field of
> the
> >>>>>>>>>>      IPv6 header.
> >>>>>>>>>>
> >>>>>>>>>> I would expect SR would work the same.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> exactly.
> >>>>>>>>>
> >>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
> >>>>>>>>> encapsulation so clearly there=E2=80=99s no L4 involved here.
> >>>>>>>>>
> >>>>>>>>> s.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Cheers,
> >>>>>>>>>> Ole
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> >>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>>> --------------------------------------------------------------------
> >
> >_______________________________________________
> >nvo3 mailing list
> >nvo3@ietf.org
> >https://www.ietf.org/mailman/listinfo/nvo3
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>
>
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small">Hi Tal,</div><div class=3D"gmail_defaul=
t" style=3D"font-family:arial,helvetica,sans-serif;font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif;font-size:small"><span style=3D"color:rgb(31,73,125);font-family:Calib=
ri,sans-serif;font-size:14.6667px">&gt; In order to avoid ambiguity, it wou=
ld be great if the=C2=A0</span></div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif;font-size:small"><span style=3D"colo=
r:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6667px">&gt; a=
uthors could explicitly mention that IPv6 extension=C2=A0</span></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fon=
t-size:small"><span style=3D"color:rgb(31,73,125);font-family:Calibri,sans-=
serif;font-size:14.6667px">&gt; headers are permitted.</span><br></div><div=
 class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fo=
nt-size:small"><br></div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small">Well the drafts are complaint t=
o RFC2119 (normative reference) so unless the text excludes elements with M=
UST/MUST NOT - everything else defined in the building blocks they (re)use =
is permitted.=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif;font-size:small"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">Ho=
wever as you say perhaps for clarity what could be added to those drafts is=
 a normative reference to IPv4 and IPv6 base RFCs.</div><div class=3D"gmail=
_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small">=
<br></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica=
,sans-serif;font-size:small">Best,</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small">R.</div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small"><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <span dir=3D"ltr">&=
lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.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">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Robert,<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">That makes sense.<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">However, in this case the=
 figures may be a bit confusing WRT the possible existence of extension hea=
ders. This confusion is what led to the discussion in this
 thread about whether segment routing is possible with VXLAN/VXLAN-GPE/Gene=
ve encapsulations.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">In order to avoid ambigui=
ty, it would be great if the authors could explicitly mention that IPv6 ext=
ension headers are permitted.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Tal.<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> <a href=
=3D"mailto:rraszuk@gmail.com" target=3D"_blank">rraszuk@gmail.com</a> [mail=
to:<a href=3D"mailto:rraszuk@gmail.com" target=3D"_blank">rraszuk@gmail.com=
</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:47 AM</span></p><div><div class=3D"h5"=
><br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG; <a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.o=
rg" target=3D"_blank">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>; <a href=
=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a href=3D"m=
ailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=3D"_bla=
nk">draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"m=
ailto:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">draft-ietf-n=
vo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)<br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<u></u><u></u></div></div><p></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Hi Tal,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Indeed .. I saw the figures, but figures are non normative=
 in any draft/rfc unless text below specifically spells it out.=C2=A0<u></u=
><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">For example from vxlan-gpe:=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">&quot;<span style=3D"color:black">When the outer IP header=
 is IPv4, VTEPs MUST set the DF bit.&quot;</span><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Besides it is pretty challenging to add animation to the c=
urrent draft formats to illustrate all possibly allowed field values/combin=
ations in any figure :) =C2=A0Figures just illustrate one use
 example.=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">To me the current specs permit any value of IPv6 NxtHdr fi=
eld as permitted in both encapsulations.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Best,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Robert.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Robert,</span><u></u><=
u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt;</span>
<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:#1f497d">Where say in draft draft-quinn-vxlan-gpe do you =
see such statement that would imply
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt; that v6 NxtHdr must =
be only equal to 17 (UDP) and not be a pointer to any other type
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&gt; of extension header =
further followed by UDP ?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">The following text is fro=
m Figure 4 in draft-ietf-nvo3-vxlan-gpe:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Outer IPv6 He=
ader:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</span><u></u><u></u></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |Version| Tra=
ffic Class |=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Fl=
ow Label=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 |</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</span><u></u><u></u></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=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 Payload Length=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 | NxtHdr=3D17(UDP)|=C2=A0=C2=A0 Hop Limit=C2=A0=C2=A0 |<=
/span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</span><u></u><u></u></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Co=
urier New&quot;;color:#1f497d">=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=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=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=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0|</span><u><=
/u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">There is a similar figure=
 in draft-ietf-nvo3-geneve.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Best regards,</span><u></=
u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Tal.</span><u></u><u></u>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><u></u><u></=
u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> nvo3 [ma=
ilto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_blank">nvo3-bounce=
s@ietf.org</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:29 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>;
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a hr=
ef=3D"mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=
=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">
draft-ietf-nvo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)</span=
><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Hi Tal,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">&gt;=C2=A0</span><span style=3D"font-size:9.5pt;font-famil=
y:&quot;Arial&quot;,&quot;sans-serif&quot;">drafts seem to imply</span><u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Where say in draft=C2=A0draft-quinn-vxlan-gpe do you see s=
uch statement that would imply that v6 NxtHdr must be only equal to 17 (UDP=
)
 and not be a pointer to any other type of extension header further followe=
d by UDP ?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">Thx,<br>
R.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;">=C2=A0</span><u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Dear Authors of VXLAN-GPE / Geneve,<br>
<br>
I am reiterating on this question, as I haven&#39;t seen a response yet:<br=
>
<br>
Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.<br>
<br>
Thanks,<br>
Tal.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_=
blank">nvo3-bounces@ietf.org</a>] On Behalf Of Tal Mizrahi<br>
&gt;Sent: Tuesday, May 17, 2016 12:09 PM<br>
&gt;To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-<br>
&gt;<a href=3D"mailto:geneve@tools.ietf.org" target=3D"_blank">geneve@tools=
.ietf.org</a>;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a><br>
&gt;Cc: <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.or=
g</a>; <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">
nvo3@ietf.org</a>; 6man WG; draft-ietf-6man-segment-<br>
&gt;<a href=3D"mailto:routing-header@tools.ietf.org" target=3D"_blank">rout=
ing-header@tools.ietf.org</a><br>
&gt;Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-<b=
r>
&gt;routing-header<br>
&gt;<br>
&gt;Stefano,<br>
&gt;<br>
&gt;If I understand your point correctly:<br>
&gt;IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sin=
ce<br>
&gt;these encapsulations do not currently allow the use of IPv6 extension<b=
r>
&gt;headers.<br>
&gt;<br>
&gt;I wonder if the authors of VXLAN-GPE and Geneve have considered the use=
 of<br>
&gt;segment routing.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;-----Original Message-----<br>
&gt;&gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevidi=
@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt;&gt;To: Tom Herbert<br>
&gt;&gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org" target=
=3D"_blank">spring@ietf.org</a>;<br>
&gt;&gt;draft-ietf-6man-segment-routing- <a href=3D"mailto:header@tools.iet=
f.org" target=3D"_blank">
header@tools.ietf.org</a><br>
&gt;&gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routi=
ng-<br>
&gt;&gt;header<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailto=
:tom@herbertland.com" target=3D"_blank">tom@herbertland.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"ma=
ilto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Right. However, it appears that at least in some cases a V=
XLAN VTEP<br>
&gt;&gt;&gt;&gt; will<br>
&gt;&gt;use SR. It certainly may be the case in SFC use cases (see Section =
2.3<br>
&gt;&gt;in draft- ietf-spring-ipv6-use-cases).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; draft-ietf-6man-segment-routing-header mentions that the packe=
t is<br>
&gt;&gt;&gt; encapsulated<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; , but I don&#39;t think it is explicit as to exact encapsulati=
on format<br>
&gt;&gt;&gt; (I suppose simple ip6ip6 is implied).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;see section 2.2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; But, it<br>
&gt;&gt;&gt; seems like any of several encapsulation techniques could work =
(VXLAN,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;I have some problems to understand where to fit an extension header=
<br>
&gt;&gt;into a vxlan encap=E2=80=A6<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that =
wants<br>
&gt;&gt;&gt; to do SR is already doing tunneling it seems reasonable to me =
to only<br>
&gt;&gt;&gt; have one layer of encapsulation. Maybe this should be clarifie=
d in<br>
&gt;&gt;&gt; the draft?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;the draft is about IPv6 extension header and more precisely a new t=
ype<br>
&gt;&gt;of the routing extension header defined in rfc2460. That=E2=80=99s =
the context.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Tom<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"ma=
ilto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-head=
er@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_blank">s=
pring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a hr=
ef=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;=
 wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; it=E2=80=99s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the draf=
t. If you have a<br>
&gt;&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft =
would specify it.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a hr=
ef=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=C3=B8an;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_=
blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt;=
<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a=
>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4 =
would still be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; involved,<br>
&gt;&gt;right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say &#39;assumes encapsulation=
&#39;, does it mean that a<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; host cannot<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current d=
raft says:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originati=
ng an IPv6 packet with<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.=C2=A0 Th=
is include either:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 A host originating an IPv6 pa=
cket.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 An SR domain ingress router e=
ncapsulating a received IPv6 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 into an outer IPv6 header fol=
lowed by an SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 hea=
der and=C2=A0 the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into=C2=
=A0 account the whole<br>
&gt;&gt;IPv6+SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Here, theres=E2=80=99 nothing new=C2=A0 compar=
ed to rfc2460.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the=C2=A0 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation=
=C2=A0 (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues=C2=A0 its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mail=
to:<a href=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.c=
om</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<br=
>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=C3=B8an; Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man-=
segment-routing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- heade=
r<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a hr=
ef=3D"mailto:otroan@employees.org" target=3D"_blank">
otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has b=
een discussed before.]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-s=
egment-routing-header, an =E2=80=98SR<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node=E2=80=99 updates the Des=
tination IP address.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also update=
 the Layer 4 Checksum, right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper =
bound on the size of the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a pretty=
 deep location.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor=E2=
=80=99s perspective this may be a problem.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0o=C2=A0 If the IPv6 pa=
cket contains a Routing header, the Destination<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Address used i=
n the pseudo-header is that of the final<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 destination.=
=C2=A0 At the originating node, that address will be in<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 the last eleme=
nt of the Routing header; at the recipient(s),<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 that address w=
ill be in the Destination Address field of the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 IPv6 header.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the s=
ame.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=E2=80=
=99s no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;&gt;&gt;&gt; IETF IPv6 working group mailing list <a href=3D"mailto:ipv=
6@ietf.org" target=3D"_blank">
ipv6@ietf.org</a> Administrative<br>
&gt;&gt;&gt;&gt; Requests: <a href=3D"https://www.ietf.org/mailman/listinfo=
/ipv6" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;nvo3 mailing list<br>
&gt;<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br=
>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/nvo3</a><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/spring</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--001a11402cb830354505337df7cc--


From nobody Mon May 23 01:56:30 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 C015512B019 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 01:56:28 -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 AnSnrRDrT8UL for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 01:56:27 -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 4931112B01D for <ipv6@ietf.org>; Mon, 23 May 2016 01:56:27 -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; 23 May 2016 08:56:26 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 2A93C9CC7C for <ipv6@ietf.org>; Mon, 23 May 2016 01:56:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:to:mime-version; s= selector1; bh=81f3UP3UJ5GXUZh6/I7HAKLz6Rw=; b=nq+58gLA4uAZum5tlt 74rCpwwWWwoce5GCttqW6EJVwyWggUhhWB0Y5fEw/+XxxbAY9g8qi6Rbam9pTQaP YIPjf2UOd1OmqRze0FFCowosZLIrQjGGYBwLSnvDRT94hiptCvuKxK9UvcuZVxSV 7YIkceS5FfrwuADLzj4WdeyOY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:to:mime-version; q=dns; s= selector1; b=BGKGC7BI5NC+qinhFgy38xrcVbLahLGBi2cmPJM8jRgMn7cFQIi 6bbQAuTaOD7eT51XsanshOfI4bo/hDEwiAzINMgu2sRk2/PrJoRYsG7sZaxB6k/Q +yFWyuLVGE48B3wodUvt9WCh+iKHIx+irEldAerFb3ZwrepeXflcQy+s=
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 EDB209CC51 for <ipv6@ietf.org>; Mon, 23 May 2016 01:56:24 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 31FB716CDC21 for <ipv6@ietf.org>; Mon, 23 May 2016 10:56:22 +0200 (CEST)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_3462F7F3-C442-414F-A719-7B7BFE90A39F"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN IETF96 Call for agenda items
Date: Mon, 23 May 2016 10:56:21 +0200
Message-Id: <961B1861-BC96-411F-A579-4BB3F4EE27E7@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: <http://mailarchive.ietf.org/arch/msg/ipv6/U1CtoxPIXOxG1gJmgRMnODj76gc>
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, 23 May 2016 08:56:29 -0000

--Apple-Mail=_3462F7F3-C442-414F-A719-7B7BFE90A39F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The 6MAN chairs are planning the meeting in Berlin at IETF96.

If you have a draft you would like to discuss, please send your request =
for agenda time to the 6man chairs.   Please include in the request, the =
title of the presentation, file name of the draft, the speaker's name =
(and email), and how much time you would like.

We will prioritise drafts that are working group items and drafts that =
have been actively discussed on the list.

We expect at least half of each talk=E2=80=99s presentation time to be =
used for open discussion,
please plan your presentation accordingly.

New drafts not discussed on the mailing list prior to the meeting,
or drafts that do not appear to have support from the working group are =
unlikely to get time at the meeting.

Please have agenda items to us by 15 June 2016.

Note: Bob has chosen to prioritise sailing to Hawaii over being with us =
in Berlin this time.

Regards,

Bob & Ole


--Apple-Mail=_3462F7F3-C442-414F-A719-7B7BFE90A39F
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

iQIcBAEBCgAGBQJXQsW1AAoJEL7aWKiYQt92SygP/21rwdk7dTkwiAWb/zD0YReP
fEeAGjiEE6Dvi1ihluNrhR4v7pbeRWyWifaSoX0uPMXh/CcmWaHHYvzWvdU0u36J
m6njP9OVf3kWhNKjjenqtty5a9IZI10HjbK3F+c9EiGdmwC9HRS2hE3MQ31c1tE+
p0IVm/4YwdkjPkwXxSiiIDA17u6aOUnA0qTkHXt8Mt5AneUs/J37OjJn7DvimVOY
UmpO6VDerKAmTTqTADNaeC7U2z4+FruJFDoS4AvBNzIArSUKb4yR7PNqv6OmSe4C
paBQOn68eCsU26gJ5XFDBvGt4ZHqbrdVewq6RSSxtx0QzurVTQEH4tTjlCC/Rf/l
JEUFdrIqeA5Yr7GiyMkP3OOgYxiw9YlQ9VnjEAR28Eedphu0jPffnh0CvyPi2xGW
4GHBUNjBY7V+/Y40T6EwKBz1UDFNhYge0Ou/MfaIvw7HNYb06t1olTMSbWEDBQjD
C2kTs2B0y0R0wKLY4JsKxXzbxhX0lfUMfo1GgfOer3uK8YD+waNzNtFMkWWf6pB1
rRoX3FP8ZBrAip806qSSPpMu5CJOgHfMLSW9/WnuxM4FlQtobelzoqd6Ufn5dufl
k3m7tRpssH2UTUR9o9sUu90PYpclwVvY/c2yblnbYmksUZ3+MGe+4Aa3MqExbN4I
G1W3bE7m/N8FossZJ++B
=EE5g
-----END PGP SIGNATURE-----

--Apple-Mail=_3462F7F3-C442-414F-A719-7B7BFE90A39F--


From nobody Mon May 23 01:58:49 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 C932B12D15F; Mon, 23 May 2016 01:58:47 -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 96
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160523085847.6204.57792.idtracker@ietfa.amsl.com>
Date: Mon, 23 May 2016 01:58:47 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ski4HIF0uKbdLkuG0u_3b0YBPXc>
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: Mon, 23 May 2016 08:58:48 -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 Mon May 23 02:13:26 2016
Return-Path: <alexandre.petrescu@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 7F9FF12B04C for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 02:13:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 8az5yqakTmBl for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 02:13:23 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04C7512B009 for <ipv6@ietf.org>; Mon, 23 May 2016 02:13:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4N9DLW3021204 for <ipv6@ietf.org>; Mon, 23 May 2016 11:13:21 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1F8EC2044D3 for <ipv6@ietf.org>; Mon, 23 May 2016 11:13:29 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0D2852037EF for <ipv6@ietf.org>; Mon, 23 May 2016 11:13:29 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4N9DKUu007211 for <ipv6@ietf.org>; Mon, 23 May 2016 11:13:20 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt> - hybrid addresses
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com> <574210D2.9030903@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <fbfac489-f56a-0ece-d1c6-b17cdc6846d8@gmail.com>
Date: Mon, 23 May 2016 11:13:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <574210D2.9030903@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2wO1C-1v7eCCHIR5gxyjEGme7lU>
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, 23 May 2016 09:13:24 -0000

Le 22/05/2016 Ã  22:04, Fernando Gont a Ã©crit :
[...]

> I'm fine with layer-2 adddr randomization. Could even consider myself
> and advocator of that (in a number of scenarios). HOwever, I'm
> against reusing numeric IDs in different places, for the reasons
> stated above.
>
> Thughts?

Do you think of other reasons than privacy for not including numeric
IDs in different places (e.g. use L2 address in L3 address)?

(privacy may be a valid reason; but hybrid addresses mixing IDs from
different layers is common elsewhere, wonder why opposing)

Alex

>
> Thanks,
>


From nobody Mon May 23 02:17:02 2016
Return-Path: <alexandre.petrescu@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 CD21B12B04C for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 02:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 foQvbjJtHbJH for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 02:16:59 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F59512B02D for <ipv6@ietf.org>; Mon, 23 May 2016 02:16:58 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4N9GvJB023595 for <ipv6@ietf.org>; Mon, 23 May 2016 11:16:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 92C97204AF3 for <ipv6@ietf.org>; Mon, 23 May 2016 11:17:05 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 89AEF204A8E for <ipv6@ietf.org>; Mon, 23 May 2016 11:17:05 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4N9Gvwt010307 for <ipv6@ietf.org>; Mon, 23 May 2016 11:16:57 +0200
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in> <57420B44.6080209@si6networks.com> <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <0e39d885-c1a8-a461-f867-f70b89ab4fd3@gmail.com>
Date: Mon, 23 May 2016 11:16:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/OrGIXUU0m63VDvaDJF6gutx3v1s>
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, 23 May 2016 09:17:01 -0000

Le 23/05/2016 à 03:12, Lorenzo Colitti a écrit :
> On Mon, May 23, 2016 at 4:40 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
>
>     The root of this whole problem is embedding a layer-2 id in a layer-3
>     field in the first place.
>
>
> No, the root of this whole problem is embedding a *stable* layer-2 ID in
> a layer-3 field.

We can move away from this problem by increasing the size of that 
layer-2 ID (rather than destabilizing it) such that it no loger fits 
into a layer-3 address.

Alex

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


From nobody Mon May 23 04:17: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 9C0E212D685 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 04:17:54 -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 lhxZcwCHND8h for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 04:17:53 -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 D5BE412D615 for <ipv6@ietf.org>; Mon, 23 May 2016 04:17: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; 23 May 2016 11:17:50 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B43389CC51; Mon, 23 May 2016 04:17:49 -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=tkPItQLFm+LltAOoDh6RzS051rY=; b=oE4NelLYqTSie23kFg WH1k3d6rCMUKyvR2ofFjmaKpFrq9EYrLlfOquk257+dUH3XuhKATameXLCqE3VGS qfL0pFTAp0nvIh2NMycbfKTVQMwAWNk3g9bAE3JHt7imMNamjwYXDGR9a6HRr5Am 3HnsQjbQlTom8fWN/IrCg0lCU=
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=iTI5A4nCFXLsFBMdROCVQ6QaqnFqAZBEgyNezKjG/P29C59Z Twn0OAaaHiWrA8Q3vyJvTX3Xm7z+h7pEd45CJYyzilKnSMlGPpjX8jn5yl8PAgR7 F/QNkaJoNtdMbLcOC0Bjgxl3ZcPearnpkhKrkrAskt15iCRBFza3jcKJxx0=
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 736E09CC4E; Mon, 23 May 2016 04:17:49 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C859E16D347C; Mon, 23 May 2016 13:17:46 +0200 (CEST)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_544B8D93-2AA5-422D-8D79-3CFF2CFE05F1"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Next steps: IPv6 core specifications to Internet Standard.
Date: Mon, 23 May 2016 13:17:45 +0200
Message-Id: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@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: <http://mailarchive.ietf.org/arch/msg/ipv6/jmgHzk7mn7VzJrXq9vamCZZCtjw>
Cc: 6man-chairs@tools.ietf.org, int-ads@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: Mon, 23 May 2016 11:17:54 -0000

--Apple-Mail=_544B8D93-2AA5-422D-8D79-3CFF2CFE05F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


The 6MAN working group has been working on advancing the core IPv6 =
specifications to Internet Standard.  The next steps to achieve this =
goal is described here.

As we=E2=80=99re finishing the edits on the RFC2460bis, RFC1981bis and =
RFC4291bis, we will initiate working group last calls with the intended =
status of Internet Standard.
We will do a single last call for the updated documents (RFC2460, =
RFC4291, RFC1981) and a separate working group last call for the =
unchanged documents (RFC3596, RFC4443, RFC4941).

The focus of the working group last call is on the RFC6410 requirements =
and implementation status of the updated text.

When the changed documents are advanced to the IESG, we will also ask =
the IESG to reclassify RFC3596, RFC4941, RFC4443 in-place as Internet =
Standards.

The result will be for all six of these documents to be Internet =
Standards.

As part of the working group last call we are asking for reviewers for =
each document set.

Best regards,
Ole and Bob


--Apple-Mail=_544B8D93-2AA5-422D-8D79-3CFF2CFE05F1
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

iQIcBAEBCgAGBQJXQubaAAoJEL7aWKiYQt92rWkQALqkUs8T5/o0Dg0lSFp8j34b
//vSTDttjSHHMH8gp8ZRn3Bnrhy0AzIlUVmdqDafdxqHqji5/iKBBU26Y6j/h6LV
EJ3GyO5C2iz3GxbIVo8lwSnYJP1ZrMEalU2QXTgpR89ki4jKUsuKfS7cziryHfpF
dy8hDTlCn+Gp3GD5a7p3jFdZFAIhxcs4LH7d74MeTaiukTrpk/L86HtyajXbFapD
O88lHrD6hueMsdK5mrCOhs5cmB8JOvGWekmwlPFoT5OKB5/QLIRoMksQ0/EpU8+P
uis8B+MSRZq3UVphF3nr1dbQU0CtAQ3wayXt8b3i99nUwJl3EFGxnKOkUu4Ez2G+
AfyfMq5nkFY6aHeoj+Icnnex8qdqZK1Z/7n4jTu5qyQtqncv38LzhKGBqxNyw1Bw
bOs3uQX7V60vH4YjhNvT8uluoQbqEwauKqQFQFtWrjPnt6zo366P7lO+I5IHjpkG
C4LsgFWS2n7xDXlyzBmFomUVM6Su1lc9KkH+e9djSSjdockNrH+owWFwCKS5jZqj
0x800kSafnYkWuQ4gEl791rUK3U8kRX8O4q2tyDtSo1Ruq+677vuhr2k2wZDYcfr
p/VpF7I2sNTGS+fqkNO/WWCeWMOZqTC5UNBgwIkL3gJ5SGWKhb7QixjUYj8yn+dT
7ir0C1vOpYykK53lwgdH
=6TWi
-----END PGP SIGNATURE-----

--Apple-Mail=_544B8D93-2AA5-422D-8D79-3CFF2CFE05F1--


From nobody Mon May 23 08:14: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 E7AA912D955 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 kG4xSO4cIgIP for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:14:04 -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 E51B012D0F3 for <6man@ietf.org>; Mon, 23 May 2016 08:14:03 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 8A15480DAA; Mon, 23 May 2016 17:13:54 +0200 (CEST)
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5742F051.7000507@si6networks.com>
Date: Mon, 23 May 2016 07:58:09 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SqaabAnN0Mu4jleGhwGxnbyY2sQ>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 15:14:06 -0000

On 05/22/2016 07:08 PM, Lorenzo Colitti wrote:
> On Mon, May 23, 2016 at 4:39 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > All I'm saying is that if we publish this draft, then the formation of
>     > IPv6 IIDs on many link layers, including ethernet and wifi, becomes
>     > completely unspecified, and implementations (well - implementations that
>     > don't want to use stable IIDs) can do whatever they want with no
>     > recommendations or guidance from the IETF.
> 
>     Huh?
> 
>     Right now you have specs for stable adresses and RFC4941. This I-D
>     simply improves how you generate stable addresses. WHerever you'd embed
>     a link-layer id, you use RFC7217. That's it.
> 
>     Where's the lack of guidance??
> 
> 
> Here's the lack of guidance. Take Ethernet. After this document is
> published, all the text in RFC 2464 is replaced by this text:
> 
>    The Interface Identifier [AARCH] for an Ethernet interface MUST be
>    generated as specified in [RFCXXXX].
> 
> RFCXXXX says that it applies only if an implementation wants to create a
> stable address, and that that is OPTIONAL.
> 
> If an implementation does not want to create a stable address, there is
> no guidance as to what it should do. I assume that means it can do
> whatever it wants.

That is not because of this document, but because of the additional step
you want this document to make.

Right now this document just improves stable addresses. And such
addresses are required to be there because of RFC2464 and RFC4941.

If you want to remove such requirement (which is *not* introduced by our
document), you'll obviously have to provide advice on what to do if you
don't want stable addresses (temp-addr only?).

That's why I stressed that the inclusing of your text "...OPTIONAL" is
an additional step, and not what this document is meant to do.

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 May 23 08:14:17 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 9AC5112D961 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 OcSsM02mLwLO for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:14:10 -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 C2E3A12D95E for <ipv6@ietf.org>; Mon, 23 May 2016 08:14:09 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 8EA8B80DAF; Mon, 23 May 2016 17:14:03 +0200 (CEST)
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in> <57420B44.6080209@si6networks.com> <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <5742F0B9.7020504@si6networks.com>
Date: Mon, 23 May 2016 07:59:53 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/73cDWeRJ_16JbkC_Vr4e9x65Psw>
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: Mon, 23 May 2016 15:14:11 -0000

On 05/22/2016 09:12 PM, Lorenzo Colitti wrote:
> On Mon, May 23, 2016 at 4:40 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     The root of this whole problem is embedding a layer-2 id in a layer-3
>     field in the first place.
> 
> 
> No, the root of this whole problem is embedding a *stable* layer-2 ID in
> a layer-3 field.

You're wrong. I've provided references that explain why, and Brian has
provided examples. There's not much I can do other than that.

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 May 23 08:20:28 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 2C79312D0F0 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:20:27 -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=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 d9wwiZ6R5-Y9 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:20:26 -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 A68F412D96B for <6man@ietf.org>; Mon, 23 May 2016 08:14:20 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 9F22180DB5; Mon, 23 May 2016 17:14:10 +0200 (CEST)
Subject: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com>
To: "6man@ietf.org" <6man@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
X-Forwarded-Message-Id: <20160523150736.10739.56619.idtracker@ietfa.amsl.com>
Message-ID: <57431E27.8090209@si6networks.com>
Date: Mon, 23 May 2016 11:13:43 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160523150736.10739.56619.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tP60SCLN0CTO9CpOpVS575mjqqU>
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, 23 May 2016 15:20:27 -0000

Folks,

We've drafted this:
<https://www.ietf.org/internet-drafts/draft-gont-6man-non-stable-iids-00.txt>

For the most part, the idea is to illustrate how I think Lorenzo's
concern should be addressed.

This document essentially removes the requirement for stable addresses
(such that folks willing to do temp-addr-only can do so), specifies
requirements for such addresses, and updates RFC4941 such that a node
can use temp-addr-only.

This is orthogonal to default-iids, which provides recommendations for
stable addresses iff you decide to configure them. This way default-iids
just does what it has always meant to do (improve stable addresses), and
this document opens the door to temp-addr only.

Thoughts?

Thanks,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for draft-gont-6man-non-stable-iids-00.txt
Date: Mon, 23 May 2016 08:07:36 -0700
From: internet-drafts@ietf.org
To: Will Liu <liushucheng@huawei.com>, Fernando Gont
<fgont@si6networks.com>, Shucheng LIU (Will) <liushucheng@huawei.com>


A new version of I-D, draft-gont-6man-non-stable-iids-00.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-non-stable-iids
Revision:	00
Title:		Recommendation on Non-Stable IPv6 Interface Identifiers
Document date:	2016-05-23
Group:		Individual Submission
Pages:		6
URL:
https://www.ietf.org/internet-drafts/draft-gont-6man-non-stable-iids-00.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-6man-non-stable-iids/
Htmlized:
https://tools.ietf.org/html/draft-gont-6man-non-stable-iids-00


Abstract:
   This document clarifies the stability requirements for IP6 addresses,
   and provides recommendations regarding the generation of non-stable
   addresses.  Finally, it formally updates RFC4941 such that nodes are
   allowed to configure only temporary addresses.





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.

The IETF Secretariat





From nobody Mon May 23 08:26:17 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 AC13C12D095 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 wFTWYvV5XcQE for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:26:12 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 6541E12D96A for <6man@ietf.org>; Mon, 23 May 2016 08:26:11 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id o16so56225115ywd.2 for <6man@ietf.org>; Mon, 23 May 2016 08:26:11 -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=+HyEWi0ZjoqgCFr8wakrchjd40f9J5CPFtxMTsis+ao=; b=b+Maj3e8er5fQ8p5Uogi8xvqtnIp3F5A0qHBMJM03gOro4JurDK8EJJUDThq/0skpN jYr/fhdN/pl07ioIfVrOOvPvSP7FSh/OG/7k4uiQyWSJfdpjDN+xN3iQ8XY8Q3/9gpTu 4hU8j3soZm6fKIUYNxBHqXL7u1ZMNCiY/tsVadj1YcQK601l9ABuGJ10HV+fNQ+f3YW0 /ryxQ75P+60P7fPwnsKg7u/PrJkcHWFrZskzhIJOLxUBT7ZlxHX9ag71cTY7/NM6OcDv B6DoVOt6rcQIS5P+nyj2XSK/rW3qW+0RWC+PODiTKAqSI+o/WIyzhF7/SA2onwjKF/hU dSDQ==
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=+HyEWi0ZjoqgCFr8wakrchjd40f9J5CPFtxMTsis+ao=; b=ZMpzFEg7U9+OyF1imonbkNTZoWWpf74bjdDUkJ+yjWNKQALvGtnZsKwZQEA35In3vn MoGL3+t9s3srpUTt3pl/FiCGrFH9qd/2txQllxEe+43R3ndEW4eoOP4Z/+X465Gl0p3U C/HgR2S2VRQxvuavhtdeu34D91hm9nxK+v8MwqBQmXzUXKS/iU6usogs2Gda9hdMQGIL h+5Lz2HwO/EJtU5kZ2h/7wZgHgca8mveMo5c/Kay+CKDEVdgF887sX3fdrl5aOvqwTQF dvTpNqTcq0joRn14vWWii/Z0qJp2FagM4TiNklwIBOMbm7Cz7g386dsWqJ348NOb/3bC X3kg==
X-Gm-Message-State: AOPr4FVEz6gaDxD5jYve9XROSDQa1ofF1JaSjQce2bNmWeE/PsuW7+69XRVRU54J6JtALA+VrsKNb/RXEMHNQg5/
X-Received: by 10.37.79.87 with SMTP id d84mr9454032ybb.49.1464017170448; Mon, 23 May 2016 08:26:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Mon, 23 May 2016 08:25:49 -0700 (PDT)
In-Reply-To: <5742F051.7000507@si6networks.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com> <5742F051.7000507@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 24 May 2016 00:25:49 +0900
Message-ID: <CAKD1Yr0W-5igiFd4Uteb7y7CF8oFQwVY-SQ1xsp+mLusQtJp4g@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a113f5cd0645ea70533840f40
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yAJ8VyQeQYArT9xqd9HnpA97Ins>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 15:26:16 -0000

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

On Mon, May 23, 2016 at 8:58 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> > If an implementation does not want to create a stable address, there is
> > no guidance as to what it should do. I assume that means it can do
> > whatever it wants.
>
> That is not because of this document, but because of the additional step
> you want this document to make.
>

If you're saying that this is "because of the additional step I want this
document to make", then you must be saying that the document as it is now
says that implementations SHOULD create stable addresses all the time.
Which was one of my points all along.

Not sure how that fits with your continued previous assertions that "this
document only affects implementations that want to create stable
addresses", but... good to see that you, as one of the authors, agrees with
me on what the document currently says about this.

Now that we agree on what the document says about this, let me repeat my
concern: it is not acceptable, in 2016, to say that implementations SHOULD
create stable addresses all the time.

Cheers,
Lorenzo

--001a113f5cd0645ea70533840f40
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 M=
on, May 23, 2016 at 8:58 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-col=
or:rgb(204,204,204);padding-left:1ex"><span>&gt; If an implementation does =
not want to create a stable address, there is<br>
&gt; no guidance as to what it should do. I assume that means it can do<br>
&gt; whatever it wants.<br>
<br>
</span>That is not because of this document, but because of the additional =
step<br>
you want this document to make.<br></blockquote><div><br></div><div>If you&=
#39;re saying that this is &quot;because of the additional step I want this=
 document to make&quot;, then you must be saying that the document as it is=
 now says that implementations SHOULD create stable addresses all the time.=
 Which was one of my points all along.</div><div><br></div><div>Not sure ho=
w that fits with your continued previous assertions that &quot;this documen=
t only affects implementations that want to create stable addresses&quot;, =
but... good to see that you, as one of the authors, agrees with me on what =
the document currently says about this.</div><div><br></div><div>Now that w=
e agree on what the document says about this, let me repeat my concern: it =
is not acceptable, in 2016, to say that implementations SHOULD create stabl=
e addresses all the time.</div><div><br></div><div>Cheers,</div><div>Lorenz=
o</div></div></div></div>

--001a113f5cd0645ea70533840f40--


From nobody Mon May 23 08:40:16 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 A0A8712D99E for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 uakeNjQH5MEW for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:40:14 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 0FDF212D0AA for <6man@ietf.org>; Mon, 23 May 2016 08:40:14 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id o16so56659717ywd.2 for <6man@ietf.org>; Mon, 23 May 2016 08:40:14 -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=R6sStLwp6w9fR6FkvU1mHMzdWV/Yqr6QxdZZ2t30Wz8=; b=PMYNxU6ZBjFstqeDcSBA2letOK3/tZwCKCaYFOhOLsfAMG1L0/0gLCwFZ+05+aaXEn lm2A/lHKNKGL8u8W45FQMtx+cPzss/8t960yEbHDpOyDDTWsxoOFiVgSPAU+2dR9ZNLE rruLF5qB7/WQfcx1m2CO30eq+3xtLSUc+NfSRkEvU0ymax95ZSqijfriqt0ldDB24416 4fsfv7OYb5gEUmDr/mkY9l64wjBJMFMB7ZgQ9jPo92ThnH8gtyRPbTVhYEyARHD1diX3 2G5taODfccNeJ2ZhrFC/5d32VgASvG7TzGBzRlGWBh1s5UUxJXOUsvuJuV9VDutlG3Lb IYkg==
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=R6sStLwp6w9fR6FkvU1mHMzdWV/Yqr6QxdZZ2t30Wz8=; b=VDtfxS/+ExircTj7TQlYthU06eUstUpeAlyP5TgIqjqZ7KI5qdmE+WYEENvckYiHuD C0OSaXJWBpqjwtFXAt890/v+Ats+fkc1gjuUgZEDQCnA9bs6R8cRypr91hD/E8SWtTew 5D3jqtExe3x/CxzlUXPuwQqGHtm/h6OpL9GlCsyJyxVPlIeqxFKjZyVQMgf4g7tVEJ5/ drAgOhSAx5GYFiDUpJ8h2shbJelYf3LjaDb6ZhiPS9A9DZ2wUcxkfzYTSB3JbncV7wAb cnFmrlppf5BQR2Og1CeMNXjzLbUziDDD3qYHkW/wym9/hjUaiA6DNqRJRCuF7KdCrAX+ Kl8A==
X-Gm-Message-State: ALyK8tIWyoVHj3RJllPE16Xm6E2SUPOOeXiFNyy/og9pjrDkNohGNBUjMTSAfdo7VAp2ciDuV6gza3561ig5gLDw
X-Received: by 10.129.108.211 with SMTP id h202mr4371273ywc.229.1464018013208;  Mon, 23 May 2016 08:40:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Mon, 23 May 2016 08:39:53 -0700 (PDT)
In-Reply-To: <57431E27.8090209@si6networks.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 24 May 2016 00:39:53 +0900
Message-ID: <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a114da7469fd01a0533844106
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0fCq4f5JUIN0S_J4wsrBDCeEwzM>
Cc: "6man@ietf.org" <6man@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: Mon, 23 May 2016 15:40:15 -0000

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

On Tue, May 24, 2016 at 12:13 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> This is orthogonal to default-iids, which provides recommendations for
> stable addresses iff you decide to configure them. This way default-iids
> just does what it has always meant to do (improve stable addresses), and
> this document opens the door to temp-addr only.
>

SGTM, except for the "must not embed MAC addresses". I think it's a
perfectly good engineering tradeoff to embed a random MAC address in an
IPv6 IID as long as it's truly random.

For mobile devices that only support IP and no other L3 protocols, and on
networks with only one prefix (i.e., the vast majority), it's pretty much
as good as 4941-only.

--001a114da7469fd01a0533844106
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, May 24, 2016 at 12:13 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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">This is orthogonal t=
o default-iids, which provides recommendations for<br>
stable addresses iff you decide to configure them. This way default-iids<br=
>
just does what it has always meant to do (improve stable addresses), and<br=
>
this document opens the door to temp-addr only.<br></blockquote><div><br></=
div><div>SGTM, except for the &quot;must not embed MAC addresses&quot;. I t=
hink it&#39;s a perfectly good engineering tradeoff to embed a random MAC a=
ddress in an IPv6 IID as long as it&#39;s truly random.</div><div><br></div=
><div>For mobile devices that only support IP and no other L3 protocols, an=
d on networks with only one prefix (i.e., the vast majority), it&#39;s pret=
ty much as good as 4941-only.<br></div></div></div></div>

--001a114da7469fd01a0533844106--


From nobody Mon May 23 08:41:50 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 09B5612D9A7 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:41:47 -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 t53yHZRntViG for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:41:45 -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 73F6112D9A4 for <6man@ietf.org>; Mon, 23 May 2016 08:41:41 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 D3849801B6; Mon, 23 May 2016 17:41:36 +0200 (CEST)
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com> <5742F051.7000507@si6networks.com> <CAKD1Yr0W-5igiFd4Uteb7y7CF8oFQwVY-SQ1xsp+mLusQtJp4g@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57432495.5090506@si6networks.com>
Date: Mon, 23 May 2016 11:41:09 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0W-5igiFd4Uteb7y7CF8oFQwVY-SQ1xsp+mLusQtJp4g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/et564R-xCkVs8mj3Fk_MY8FZFhA>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 15:41:48 -0000

On 05/23/2016 11:25 AM, Lorenzo Colitti wrote:
> On Mon, May 23, 2016 at 8:58 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > If an implementation does not want to create a stable address, there is
>     > no guidance as to what it should do. I assume that means it can do
>     > whatever it wants.
> 
>     That is not because of this document, but because of the additional step
>     you want this document to make.
> 
> If you're saying that this is "because of the additional step I want
> this document to make", then you must be saying that the document as it
> is now says that implementations SHOULD create stable addresses all the
> time. Which was one of my points all along.

This document doesn't say anything in that respect. Whatever was the
requirement, is not changed. If there's any requirement for stable
addresses, that's *inherited* from the existing specs. (Please see the
other document I just posted, which might help).

This document does not say anything regarding whether you should create
stable addresses or not. It says that if you do, you should employ, by
default, RFC7112.


Right now, all nodes configure stable addresses. If our document gets
published, all nodes still configure stable addresses -- *no changes
here*! (modulo that the stable addresses will now be based on RFC7217).

If you want to (optionally) get rid of stable addresses, that's
orthogonal with default-iids. I personally symphatize with the idea. I
just think that this is not what default-iids is about. But since I
symphatize with the idea, I've saved you time and posted this:
<https://www.ietf.org/internet-drafts/draft-gont-6man-non-stable-iids-00.txt>

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 May 23 08:42:03 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 0454C12D9A3 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 6pb5rVodgkps for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:41:55 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::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 02CEF12D9A6 for <ipv6@ietf.org>; Mon, 23 May 2016 08:41:50 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id x189so174319048ywe.3 for <ipv6@ietf.org>; Mon, 23 May 2016 08:41:49 -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=ytaHHRzVx9iNkrnTTwYsf0CGnTYZvWBRNYkM14CTDSc=; b=lLcXBgK3JWvo0LQhdZJ9eL/3cLMIrZXO19jkfg9WVNqAsR5Bkj41YVKhGl70IlcL1D rGfchvQsb53jyzgdFARV1lr66uSwlSJQd7s2qzlQVdjxpORyl/5HpSrhGJJyQGZXdRZN gleJEBmkSMnWmoNjVk3zTgnKNpygvsnysQzzDGWQbvJ/7BXuxw1eueWF8VmMp2PGbgs3 rMZJF7CkpmgrAN1TqGH6/dcXHJnNQC+pf5zkj8rIv4wbPUMe7gBfjbP8GMeMEafYIkbl CaUgbEkLnHioBuSGLwDDuJt+zuzxHvfLbiKssmEWKeDygXWjqkwj8ZV8pvyUb3AEyLmc y3mQ==
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=ytaHHRzVx9iNkrnTTwYsf0CGnTYZvWBRNYkM14CTDSc=; b=ll/ZUKez/3ghT8/JJhKOrFrBkkInX6O8o0n/92wAxJfWwPG/GlSjwvXLC90YkTB+cO W1yt8Gn6ZA90iAH8vffTZo+Px/grXpaTSpctK/TX0o5kKKYf8OVMZYrw7h/tUvC8ADTO wM/gPxq6691eREosmHKBiOdN5M0CXYZVGFp+GKsIuvye6kH7DeZPaMvSAeU1spMiCGBR MNlEtqihta5ufrQDxjJ3ncGFIOf/6mbSge4YxbIJxcjZhyIfgqu7xmYgA4xN9uGNsLY1 261NPkHTfHZgldQajrQn5gvbO0N4NK8fOOXL1f1h9cirBof6m5ibtKnOZWCKHgMm0gak GMQg==
X-Gm-Message-State: AOPr4FV+12fZXCUaVzblGDmmMkiHyWq35O//c/hhMImSC5IRPmT5OAzAzY/SQq86Vtk+agcu3eHfY4Igs1CrfIco
X-Received: by 10.129.80.11 with SMTP id e11mr10465186ywb.197.1464018109110; Mon, 23 May 2016 08:41:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Mon, 23 May 2016 08:41:29 -0700 (PDT)
In-Reply-To: <5742F0B9.7020504@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in> <57420B44.6080209@si6networks.com> <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com> <5742F0B9.7020504@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 24 May 2016 00:41:29 +0900
Message-ID: <CAKD1Yr37doBwSKoqM9PYezfYeOVo1XVx024BB1ZQXKMsnQKM3Q@mail.gmail.com>
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1147d2b2574948053384472a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6ixXBQF9-sGhNE6jXDfRSsW-Vf4>
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: Mon, 23 May 2016 15:42:02 -0000

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

On Mon, May 23, 2016 at 8:59 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> > No, the root of this whole problem is embedding a *stable* layer-2 ID in
> > a layer-3 field.
>
> You're wrong. I've provided references that explain why, and Brian has
> provided examples. There's not much I can do other than that.


Instead of telling me I'm wrong, I would suggest convincing the WG that I'm
wrong, because if you do, it doesn't matter what I think.

--001a1147d2b2574948053384472a
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 M=
on, May 23, 2016 at 8:59 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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"">&gt; N=
o, the root of this whole problem is embedding a *stable* layer-2 ID in<br>
&gt; a layer-3 field.<br>
<br>
</span>You&#39;re wrong. I&#39;ve provided references that explain why, and=
 Brian has<br>
provided examples. There&#39;s not much I can do other than that.</blockquo=
te><div><br></div><div>Instead of telling me I&#39;m wrong, I would suggest=
 convincing the WG that I&#39;m wrong, because if you do, it doesn&#39;t ma=
tter what I think.=C2=A0</div></div></div></div>

--001a1147d2b2574948053384472a--


From nobody Mon May 23 08:49:00 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 207B012D993 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 p1Zwy9R5n8Uz for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:48:45 -0700 (PDT)
Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 EAAF012D995 for <6man@ietf.org>; Mon, 23 May 2016 08:48:44 -0700 (PDT)
Received: by mail-yw0-x235.google.com with SMTP id o16so56920655ywd.2 for <6man@ietf.org>; Mon, 23 May 2016 08:48: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=cNNiDdzGD5qfoasMs2vWbGnbw3zN3Ie6pbXeI1mDQ10=; b=Y11sLMxjPAWfu8lJHSw7j4MAy/0fNTkQ1BD1A5ZZOnxuoWRgDvZSx5DZvAa2SK6MSC +ixDLG+P47+ZIdQuiy9iN7lhvHrDTdPWTlQwQ1hlxI1J/w8grkqaA58pIgeBmj0lqm+y yZQlvXJdVyyK8abB9mB2n0XVReIMu2fx8oSgScLydoq+Q1CrhNC+B47Gj2RthothfLFk WlqhMfc6a7VhrctoViU0Yzb4EZLWmkWmDnZqyOAhFny39mglkh19uCvSBzUtqs2C3mTr FqyNqxxe0G+QnoX35q7xz2AmUbIMwTYLCOrUu84E+LjBSQsVEhD17cj5VYlT6undF03g OWwA==
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=cNNiDdzGD5qfoasMs2vWbGnbw3zN3Ie6pbXeI1mDQ10=; b=SO8mZvmd/PvdzJZ/Q2IPaK2PoVobjDXt9xtKvOq5+7liuEZxOD4TUHoZPJvofw0WSi Moz70aQ5zsSV1YnkCRiOX8zEAwsZIAw3fHFGHFCyUebTRDh6NCDJjUIuK/hWXMw5GOTV q8qlvf4LOVAHPGnE2DvDfKKyQb9cqlfm73E+NxbpKJz01nAexB9/tPHW7uI/993rMhVC GVdrB3NSLAb3ipiG8LOd7pyrEQ5rCKJFfPrH+vPpbXkr3527WV65B9Ww8qfksiBi+MoD SoOOiCrBIMNYaLIwz1wDOIXWC72zTVEueKRT7juIRCdU4n1o9ruJHxRYW6hUE0WhKFNZ lc8Q==
X-Gm-Message-State: AOPr4FU7AiGzegYF5OObFzNnSlDduX2WCpx1o3kjzLmMJRhfWIihj9lEUgJgKTzF9PhR/fPlZdmwNdk9S6sv6TH9
X-Received: by 10.129.27.9 with SMTP id b9mr9784563ywb.173.1464018524000; Mon, 23 May 2016 08:48:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Mon, 23 May 2016 08:48:24 -0700 (PDT)
In-Reply-To: <57432495.5090506@si6networks.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com> <5742F051.7000507@si6networks.com> <CAKD1Yr0W-5igiFd4Uteb7y7CF8oFQwVY-SQ1xsp+mLusQtJp4g@mail.gmail.com> <57432495.5090506@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 24 May 2016 00:48:24 +0900
Message-ID: <CAKD1Yr3+qa4gyoaYZUAxNGGBG=8uvqHEO4vGotSbYSxqT+Jaew@mail.gmail.com>
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1142a41a11d0fb05338460f0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GnDqV9hJBbS4pd0nppcEY1GVpvc>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 15:48:48 -0000
X-List-Received-Date: Mon, 23 May 2016 15:48:48 -0000

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

On Tue, May 24, 2016 at 12:41 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> > If you're saying that this is "because of the additional step I want
> > this document to make", then you must be saying that the document as it
> > is now says that implementations SHOULD create stable addresses all the
> > time. Which was one of my points all along.
>
> This document doesn't say anything in that respect. Whatever was the
> requirement, is not changed. If there's any requirement for stable
> addresses, that's *inherited* from the existing specs. (Please see the
> other document I just posted, which might help).
>

Yes, the document does not say anything about this. But the fact remains:
if the document is published as is, then that is what the IETF standards
will say: SHOULD create stable addresses.

Like I said, I think this is not something this WG can credibly do in 2016.
A major overhaul of all the IPv6-over-foo specs, as proposed in this
document, *must* have a much higher bar for privacy than "a little bit
better than 1996".

--001a1142a41a11d0fb05338460f0
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, May 24, 2016 at 12:41 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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"">&gt=
; If you&#39;re saying that this is &quot;because of the additional step I =
want<br>
&gt; this document to make&quot;, then you must be saying that the document=
 as it<br>
&gt; is now says that implementations SHOULD create stable addresses all th=
e<br>
&gt; time. Which was one of my points all along.<br>
<br>
</span>This document doesn&#39;t say anything in that respect. Whatever was=
 the<br>
requirement, is not changed. If there&#39;s any requirement for stable<br>
addresses, that&#39;s *inherited* from the existing specs. (Please see the<=
br>
other document I just posted, which might help).<br></blockquote><div><br><=
/div><div>Yes, the document does not say anything about this. But the fact =
remains: if the document is published as is, then that is what the IETF sta=
ndards will say: SHOULD create stable addresses.</div><div><br></div><div>L=
ike I said, I think this is not something this WG can credibly do in 2016. =
A major overhaul of all the IPv6-over-foo specs, as proposed in this docume=
nt, *must* have a much higher bar for privacy than &quot;a little bit bette=
r than 1996&quot;.</div></div></div></div>

--001a1142a41a11d0fb05338460f0--


From nobody Mon May 23 08:50:24 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 8BBD412D993 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:50:22 -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 77g_2w6peYW1 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:50:20 -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 3723312D97C for <6man@ietf.org>; Mon, 23 May 2016 08:50:17 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 01703801B6; Mon, 23 May 2016 17:49:56 +0200 (CEST)
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57432678.7050901@si6networks.com>
Date: Mon, 23 May 2016 11:49:12 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KNj39hBLhjL5kRGnd5JrMhU5UGI>
Cc: "6man@ietf.org" <6man@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: Mon, 23 May 2016 15:50:22 -0000

On 05/23/2016 11:39 AM, Lorenzo Colitti wrote:
> On Tue, May 24, 2016 at 12:13 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     This is orthogonal to default-iids, which provides recommendations for
>     stable addresses iff you decide to configure them. This way default-iids
>     just does what it has always meant to do (improve stable addresses), and
>     this document opens the door to temp-addr only.
> 
> 
> SGTM, except for the "must not embed MAC addresses". I think it's a
> perfectly good engineering tradeoff to embed a random MAC address in an
> IPv6 IID as long as it's truly random.

So... let me ask an obvious question (which I just didn't ask before):

Say you like generating addresses with traditional SLAAC iff MAC
addresses are randomized.

Say two autoconfiguration prefixes are advertised on the link.

Is it okay for you that addresses for each prefix will employ the same
IID? -- because that would allow for correlation between traffic
corresponding to those two prefixes.

This is yet another example of why embedding a link-layer address in the
IID is a bad idea. If you do, you will not comply with the requirement
that "addresses for different prefixes should employ different IIDs"


> For mobile devices that only support IP and no other L3 protocols, and
> on networks with only one prefix (i.e., the vast majority), it's pretty
> much as good as 4941-only.

That's bad engineering: so you argue in favor of a flawed scheme, which,
when you evaluate it for the general case (multiple layer-3 protocols
and/or multiple prefixes) becomes clear that is flawed.

I want something that is still as good when multiple addresses are
employed and/or when multiple prefixes are used. Embedding a link-layer
address does not allow for that.

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





From nobody Mon May 23 08:52:21 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 95F3F12D1AD for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:52: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 JpCo3QtZH46g for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:52:09 -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 A6B2A12D995 for <ipv6@ietf.org>; Mon, 23 May 2016 08:52:09 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 9F566801B6; Mon, 23 May 2016 17:51:58 +0200 (CEST)
Subject: Re: default-iids: dropping requirement 1 in Section 3
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <6f2edbbc-d208-03a0-3c33-503a05c0bee8@gmail.com> <CAKD1Yr1So_tFFSr=sk8ew-UJG-dWK=U6N9mwJnwkZdNX=__SVQ@mail.gmail.com> <11cf3f90-e693-a640-a372-f419a8f7a1a0@gmail.com> <CAKD1Yr0OPuSmp-OWG-+ZjDsHucQYTG2PMZw7jdiU=4kQqK+tyQ@mail.gmail.com> <663debf7-cfba-b19b-92ef-89cc66b452d8@gmail.com> <CAKD1Yr2Km2A6XO8nvNv31Ti_Rr2j4gse1KLadJPcrgFMKyzszw@mail.gmail.com> <31E1F934-FEA2-4338-8F2C-04E7302F3170@cooperw.in> <CAKD1Yr052q0-xTkgLmL8UM=bXAEypDiGHuEhtOhwc3qpoZWbDw@mail.gmail.com> <53e5543b-ebc2-9ca7-5275-693027d44088@bogus.com> <44990b39-65df-79b6-7074-7f53ba4fe035@gmail.com> <351E5A99-235D-4CD8-A237-3C70FB8EBB12@cooperw.in> <96468F91-2C94-4337-89CA-5AEEBB183ADD@cooperw.in> <57420B44.6080209@si6networks.com> <CAKD1Yr3HOcbErk7D7ppxKa8Fd905-ynB1OiDLBBnQ0NCYfbV+w@mail.gmail.com> <5742F0B9.7020504@si6networks.com> <CAKD1Yr37doBwSKoqM9PYezfYeOVo1XVx024BB1ZQXKMsnQKM3Q@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5743271A.6080008@si6networks.com>
Date: Mon, 23 May 2016 11:51:54 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr37doBwSKoqM9PYezfYeOVo1XVx024BB1ZQXKMsnQKM3Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2VpFYenkZAHM_lxvAGrWRORyC2A>
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: Mon, 23 May 2016 15:52:19 -0000

Lorenzo,

On 05/23/2016 11:41 AM, Lorenzo Colitti wrote:
> On Mon, May 23, 2016 at 8:59 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > No, the root of this whole problem is embedding a *stable* layer-2 ID in
>     > a layer-3 field.
> 
>     You're wrong. I've provided references that explain why, and Brian has
>     provided examples. There's not much I can do other than that.
> 
> 
> Instead of telling me I'm wrong, I would suggest convincing the WG that
> I'm wrong, because if you do, it doesn't matter what I think. 

The fact that your scheme wastes 18 bits of entropy, and requires that
only a single layer-3 protocol is used, and only a single IPv6 prefix is
employed (so that its exploitation for correlation does not become
obvious) shows that the scheme is flawed, and that the scheme itself is
what allows for correlation.

My apologies for my writing style. My goal is not to prove you wrong.
But rather than there's a reason for not wanting the layer-2 id in the
IPv6 address.


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





From nobody Mon May 23 08:54:12 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 0094112D128 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:54: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 9u-IZzJACIb2 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:54:10 -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 EC52512D0AA for <ipv6@ietf.org>; Mon, 23 May 2016 08:54:09 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 BF2FD80616; Mon, 23 May 2016 17:54:03 +0200 (CEST)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57432795.4070602@si6networks.com>
Date: Mon, 23 May 2016 11:53:57 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cxm-gDQ5NqNRQOSxjBzpNN-ZCf4>
Cc: 6man-chairs@tools.ietf.org, int-ads@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: Mon, 23 May 2016 15:54:11 -0000

Ole,

On 05/23/2016 07:17 AM, otroan@employees.org wrote:
>
> As we’re finishing the edits on the RFC2460bis, RFC1981bis and
> RFC4291bis, we will initiate working group last calls with the
> intended status of Internet Standard. We will do a single last call
> for the updated documents (RFC2460, RFC4291, RFC1981) and a separate
> working group last call for the unchanged documents (RFC3596,
> RFC4443, RFC4941).

After reading RFC4941, it looks like it really needs to be updated, and
also that if one were to publish RFC4941 in 2016, a fair share of text
would be edited.

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 May 23 08:57:24 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 077AC12B004 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:57:23 -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 Mh3Z9k_2ETDi for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 08:57:22 -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 12B8012D147 for <6man@ietf.org>; Mon, 23 May 2016 08:57:22 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 4F3BE8078E; Mon, 23 May 2016 17:57:11 +0200 (CEST)
Subject: Re: default-iids: Clarifying the use of stable addresses
To: Lorenzo Colitti <lorenzo@google.com>
References: <573F3F49.9090107@si6networks.com> <a8e95b829d224f1ba0a6d00e12595d3b@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr3TgV_rOX0jiCHx4uY-oSyvd2sHkdOp-ex++fsJw8MDRQ@mail.gmail.com> <93aefbd23ecf476faa81986db842b19d@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr0ke7vEXCg_SQTUpj87Csz7NLqgM2g3ZeXhCkCVCf+uFw@mail.gmail.com> <57420ADB.1040203@si6networks.com> <CAKD1Yr3GzwJUjQOFZtxS_AOhuno7ciLMJZrsCMmBc+xsr3bqUw@mail.gmail.com> <5742F051.7000507@si6networks.com> <CAKD1Yr0W-5igiFd4Uteb7y7CF8oFQwVY-SQ1xsp+mLusQtJp4g@mail.gmail.com> <57432495.5090506@si6networks.com> <CAKD1Yr3+qa4gyoaYZUAxNGGBG=8uvqHEO4vGotSbYSxqT+Jaew@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57432848.7050808@si6networks.com>
Date: Mon, 23 May 2016 11:56:56 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3+qa4gyoaYZUAxNGGBG=8uvqHEO4vGotSbYSxqT+Jaew@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AMe8PU0oQig3huyWg2g-LvTAPqQ>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 15:57:23 -0000

On 05/23/2016 11:48 AM, Lorenzo Colitti wrote:
> On Tue, May 24, 2016 at 12:41 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > If you're saying that this is "because of the additional step I want
>     > this document to make", then you must be saying that the document as it
>     > is now says that implementations SHOULD create stable addresses all the
>     > time. Which was one of my points all along.
> 
>     This document doesn't say anything in that respect. Whatever was the
>     requirement, is not changed. If there's any requirement for stable
>     addresses, that's *inherited* from the existing specs. (Please see the
>     other document I just posted, which might help).
> 
> Yes, the document does not say anything about this. But the fact
> remains: if the document is published as is, then that is what the IETF
> standards will say: SHOULD create stable addresses.

Exactly. The other document we posted changes that fact.

And changing that fact is orthogonal.



> Like I said, I think this is not something this WG can credibly do in
> 2016. A major overhaul of all the IPv6-over-foo specs, as proposed in
> this document, *must* have a much higher bar for privacy than "a little
> bit better than 1996".

They are separate issues. default-iids is "iff you do stable addresses,
do this". The other document we posted is more of "should we do stable
addresses?".

There are scenarios where stable addresses (only, or +temp addresses)
are desirable. So improving them is valuable.

Obviously, it's also valuable to allow for temp addr only. But divide
and conquer.


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





From nobody Mon May 23 10:58:39 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 B93A112DA1E for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 10:58:37 -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 Dcl2uYhqC134 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 10:58:36 -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 274A512D8D8 for <ipv6@ietf.org>; Mon, 23 May 2016 10:58:36 -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; 23 May 2016 17:58:34 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E400D9CC51; Mon, 23 May 2016 10:58:33 -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=cmkzgxwq6jIkoVjE+q12waZdTPY=; b= MYBTTC09ycgemtIuqWlEbeMJKeILTQ5eyTwN7ivig99420cYtgCDP6or53MrMgbo HHQFn0SoXY+f2qFCtSzc3cLqAtOXPQkCTpbG7qhGIFRpzAdmVflcPEjGHN/gZMHf pir3BmkLIUDr/9zSnlGQS9JcTJi+jdIR1F56Sgo0Qis=
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=YJCZ/xaD4WY7SlpKywxUJ6jS3G 55jiEvnPeo6z2sR3GkfpHdSRwmQS595/ss1SOztW+bUonxdnFdNlLh+tSjOSLAIH S9GoJ9j27aoha02BPh4pkHOZKj/CKZR8ukRcsa8HBR3zleQUd25oVMUjbENObNPS SZ29ymMhXZwhMTgao=
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 A4ABC9CC7C; Mon, 23 May 2016 10:58:33 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id EB13D16DBA3D; Mon, 23 May 2016 19:58:30 +0200 (CEST)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_329A6A63-05F2-429B-985D-AE41E2E83BD3"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <57432795.4070602@si6networks.com>
Date: Mon, 23 May 2016 19:58:27 +0200
Message-Id: <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Qw_yHlNacvaCfFNno1uCOzaDCBs>
Cc: 6man-chairs@tools.ietf.org, int-ads@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: Mon, 23 May 2016 17:58:38 -0000

--Apple-Mail=_329A6A63-05F2-429B-985D-AE41E2E83BD3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Fernando,

>> As we=92re finishing the edits on the RFC2460bis, RFC1981bis and
>> RFC4291bis, we will initiate working group last calls with the
>> intended status of Internet Standard. We will do a single last call
>> for the updated documents (RFC2460, RFC4291, RFC1981) and a separate
>> working group last call for the unchanged documents (RFC3596,
>> RFC4443, RFC4941).
>=20
> After reading RFC4941, it looks like it really needs to be updated, =
and
> also that if one were to publish RFC4941 in 2016, a fair share of text
> would be edited.

Yes, but we're not. We're reclassifying it as Internet Standard.

Best regards,
Ole

--Apple-Mail=_329A6A63-05F2-429B-985D-AE41E2E83BD3
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

iQEcBAEBCgAGBQJXQ0TGAAoJED4aXnjSQuKWU4oH/3PlsylRMwk8WvlJfYS2MUwo
YnGMBfyUV8cnSEvYNdcaXtFNucwtGMJMVFvPPJnw6bs33vbfOmCMVYrw+wQxGWad
o2yLCA0+rggsCwxKAXmnEpLnsSMQFx7bePwsGY43GWpFWqB34quTcn7+MZjTFdPo
ZoJ5F1+G2cUzQiTQndQN67uE/YmUQEud3THTnvAEozbUJJcw5FvovrId+Kdu90Wa
ffmBoeyvYDB5HqUaL90dSDTTrISG6ODVmaLPNRbvNnWKtUCyO7iooQ8h2gB99/TA
GOf1BsiaDKyYo+F2eIaJpg8gRe48sJjJvkysqGiMNQjOkEshnvx5fGDAgTEqap0=
=Bq9Z
-----END PGP SIGNATURE-----

--Apple-Mail=_329A6A63-05F2-429B-985D-AE41E2E83BD3--


From nobody Mon May 23 11:37:08 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 9EA9612D15D for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 11:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 qgwpCEXjtLrs for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 11:37:04 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001: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 93C4D12D150 for <6man@ietf.org>; Mon, 23 May 2016 11:37:03 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id 190so199149817iow.1 for <6man@ietf.org>; Mon, 23 May 2016 11:37:03 -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:date:message-id:subject :from:to:cc; bh=8yi2EcoaVRiYDEwEnlTpuYiOblKYNVWPIwh0UtCw7i0=; b=awoTW7rzEws2zPbbTSx0oweaOo6UZDM8Ja/D93vAZ4bom76g8xYp6n2CRa+yO8ap44 tjn68VBK1hLVQe9KtZ9BkZmEgahezrDfFIyfbBn1aExZ6nJo/AUC1Fy7RG5XgTesJ1NS p5IboGDQPCLy6ejw6ibWYxUchZIMyFSB70fUV1guIHK5iSUle/9YFtWu1Bha/GFwSmlA 6LYFg5aA42AkrRSc5c0ULGaeJTvZzhmrGL0Z1DzZlSfH1IqtAMSQrGKlVBJjf/rPC7a+ sv7nGQmO7BtoFPIaWWqUSwUoC8ppC4r7oT20nP6VynU4mo49sldXdHqGNmxV4OUVeP5W tUvA==
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:date :message-id:subject:from:to:cc; bh=8yi2EcoaVRiYDEwEnlTpuYiOblKYNVWPIwh0UtCw7i0=; b=hW5+Ra6An30ZJgm8+icJ4xT8J7PsSTVPQ5WjREfIlN140TI2H68iVxvS0EUHWVzjnb yUKX7yLFzCj549UyDNRYFhOsHl+4CcqvePiUqMaahyTXYXtjON+6SwOYNvw7BplQaBCN 2EmL1ywgXr97m5gxEVu6IDeVy2FHJEK14fm8vVUSG+8DW5i8tDep+Swn6yxEuYq2MHHf FVeOzjwc+TqQ9f+qsGIFsMHzosCMLaLlrIZRzSYlKdja0rQmfy1jJWn/Qr7F2dQtIDfx vHCAVFjOr0FHmr/rLkuDGIIxEgPli9yG+CLQUuvUEVg9Egwh3j0BtJqCK2T3c0/FKg/I T8Yw==
X-Gm-Message-State: AOPr4FXzqFPPZSFqB7N2tA3C3lWEHT/jPVeTUZymv1scBj3//X6fZ2+zrefBN90z9hhodbUA/f/kRX46cXoWPw==
MIME-Version: 1.0
X-Received: by 10.107.35.66 with SMTP id j63mr15282923ioj.4.1464028622883; Mon, 23 May 2016 11:37:02 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.19.218 with HTTP; Mon, 23 May 2016 11:37:02 -0700 (PDT)
In-Reply-To: <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com>
Date: Mon, 23 May 2016 11:37:02 -0700
X-Google-Sender-Auth: c7gJhjhgV-nitv5n-I-OZoi7cmc
Message-ID: <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CG313KLq22dSoxD3XWSUbfcmPt8>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 18:37:07 -0000

At Mon, 23 May 2016 10:10:57 +0900,
Lorenzo Colitti <lorenzo@google.com> wrote:

> > Lorenzo suggested this text:
> >
> >    The recommendations in this document apply only in cases where
> >    implementations otherwise would have configured a stable IPv6 IID
> >    containing a link layer address. Configuring a stable IPv6 IID is
> >    OPTIONAL.
>
> Jinmei had some better text, IIRC. Jinmei?

My suggested text was this:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  For example, this document does
   not change any existing recommendations concerning the use of
   temporary addresses as specified in [RFC4941], nor do the
   recommendations apply to cases where the link layer address is not
   stable (e.g., it is periodically randomized) in the first place,
   nor does it introduce any new requirements regarding when stable
   addresses are to be configured.  Thus, the recommendations in this
   document simply improve the security and privacy properties of
   stable addresses.

I've seen two responses to my suggestion, one from Fernando:
http://www.ietf.org/mail-archive/web/ipv6/current/msg24495.html

and the other from Ole:
http://www.ietf.org/mail-archive/web/ipv6/current/msg24512.html

And, basically, they didn't seem to be happy about it.  In the above
text I just tried to make the scope of this document super clear
(i.e., cases where the link-layer address is not stable are out of
scope of this document), but it looks like Fernando didn't even like
to mention it at all, or may even think we should explicitly recommend
against that:

> The root of this problem is reusing a link-yaer ID at layer-3. THat's
> bad, and we have to recommend against that.

If this is a very important point of this document, all I can say is
that this document should be revised to say this position explicitly
and that revised version will have to get wg consensus.

On the other hand, Ole seemed to say my additional text itself is out
of scope of this document:

> I don't think this document is the place to to clarify that there
> might be interfaces with only short-lived IIDs.

In a sense, I agree.  But as I said in my response, since this has
been a central point of controversy in this last call discussion, I
thought an explicit clarification on the specific case (that it's out
of scope of this document) was one promising way to move forward.

I don't know the general sense of the wg on my suggested text.  If
it's just deemed to be redundant or possibly out-of-scope but
otherwise acceptable while it makes some others much happier (on which
I'm quite sure) I think it's still worth considering.  But I'm not
pushing my specific agenda in proposing this text, so if the text
itself is so controversial I won't argue for it.

--
JINMEI, Tatuya


From nobody Mon May 23 12:34:14 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 44BBD12DAE0 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 12:34:13 -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 s1-VgXAJ3LdI for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 12:34:11 -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 4CE6812DAE6 for <6man@ietf.org>; Mon, 23 May 2016 12:34:07 -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 u4NJY5Dw019276; Mon, 23 May 2016 12:34:06 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4NJY31U019187 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 23 May 2016 12:34:03 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 23 May 2016 12:34:02 -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; Mon, 23 May 2016 12:34:02 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: =?iso-2022-jp?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: RE: default-iids: Closing concern regarding stable address requirement
Thread-Topic: default-iids: Closing concern regarding stable address requirement
Thread-Index: AQHRtSIiJ6C773JTdUmOICjeyeiVsJ/G3kwQ
Date: Mon, 23 May 2016 19:34:02 +0000
Message-ID: <4810b9f0abda43b89579fd366e327c2b@XCH15-06-11.nw.nos.boeing.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com>
In-Reply-To: <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@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
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/beSyVhO4U9rc0PiW08fh1pnk6iE>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Mon, 23 May 2016 19:34:13 -0000

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of [Tatuya Jinmei]

> and the other from Ole:

>> The root of this problem is reusing a link-yaer ID at layer-3.
>> THat's bad, and we have to recommend against that.
>
> If this is a very important point of this document, all I can say
> is that this document should be revised to say this position
> explicitly and that revised version will have to get wg consensus.

We seem to get continually dragged into the tangential discussion, out of s=
cope, about temporary addresses.

My feeling is that the case against use of short-lived MAC addresses, in te=
mp IP address IIDs, was not made convincingly. In part, because the IETF do=
es not control how temp MAC addresses are created. So some of the assertion=
s made might not be true. For example, in a multihomed host, do we know for=
 sure that the temp MAC addresses would be identical for each interface?

So, for the purposes of this draft, I think we should only emphasize what i=
t addresses, and not dwell on what it does not cover. In Section 1, the dra=
ft already says more than it needs to say, on tangential subjects. Plus, it=
 also says:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.  That is, this document does not
   change any existing recommendations concerning the use of temporary
   addresses as specified in [RFC4941], nor does it introduce any new
   requirements regarding when stable addresses are to be configured.
   Thus, the recommendations in this document simply improve the
   security and privacy properties of stable addresses.

So, I'm not sure how to be more explicit than this. "If you have objections=
 to the way temp addresses are formed, refer to the relevant documents," is=
 in essence what the draft says.

Since we keep getting bogged down on temp addresses, in this draft, perhaps=
 text should be subtracted rather than added. E.g., also from Section 1, th=
is text might be leading people to go off on the tangential discussions:

   More generally, the reuse of identifiers that have their own
   semantics or properties across different contexts or scopes can be
   detrimental for security and privacy
   [I-D.gont-predictable-numeric-ids].  In the case of traditional
   stable IPv6 IIDs, some of the security and privacy implications are
   dependent on the properties of the underlying link-layer addresses
   (e.g., whether the link-layer address is ephemeral or randomly
   generated), while other implications (e.g., reduction of the entropy
   of the IID) depend on the algorithm for generating the IID itself.
   In standardized recommendations for IPv6 IID generation meant to
   achieve particular security and privacy properties, it is therefore
   necessary to recommend against embedding link-layer addresses in IPv6
   IIDs.

Perhaps that should be shortened to say more simply:

   More generally, the reuse of identifiers that have their own
   semantics or properties across different contexts or scopes can be
   detrimental for security and privacy
   [I-D.gont-predictable-numeric-ids].  In the case of traditional
   stable IPv6 IIDs, some of the security and privacy implications are
   dependent on the properties of the underlying link-layer addresses.
   In addition, the algorithm to produce the IID reduces the entropy
   by 16 bits, which may also be undesirable. It is therefore
   recommended against embedding link-layer addresses in IPv6 IIDs.

No MUST NOT, just a general recommendation. And only as relates to stable a=
ddresses.

Bert



From nobody Mon May 23 13:20:07 2016
Return-Path: <jgross@vmware.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 9491D12DB60; Mon, 23 May 2016 13:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.346
X-Spam-Level: 
X-Spam-Status: No, score=-8.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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.426, 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 UgO_AtcIg0l9; Mon, 23 May 2016 13:20:00 -0700 (PDT)
Received: from smtp-outbound-1.vmware.com (smtp-outbound-1.vmware.com [208.91.2.12]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE09D12DB5C; Mon, 23 May 2016 13:20:00 -0700 (PDT)
Received: from sc9-mailhost3.vmware.com (sc9-mailhost3.vmware.com [10.113.161.73]) by smtp-outbound-1.vmware.com (Postfix) with ESMTP id 67E0C98602; Mon, 23 May 2016 13:19:59 -0700 (PDT)
Received: from EX13-CAS-002.vmware.com (ex13-cas-002.vmware.com [10.113.191.52]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id 344A4405D9; Mon, 23 May 2016 13:20:00 -0700 (PDT)
Received: from EX13-MBX-005.vmware.com (10.113.191.25) by EX13-MBX-020.vmware.com (10.113.191.40) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Mon, 23 May 2016 13:19:59 -0700
Received: from EX13-MBX-005.vmware.com ([fe80::e806:206:d943:a7c9]) by EX13-MBX-005.vmware.com ([fe80::e806:206:d943:a7c9%15]) with mapi id 15.00.1156.000; Mon, 23 May 2016 13:19:59 -0700
From: Jesse Gross <jgross@vmware.com>
To: Robert Raszuk <robert@raszuk.net>, Tal Mizrahi <talmi@marvell.com>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMWqMRO7Jj7qMECzlvUXO0D9Pp/Gmj6AgAACKYCAAARfAIAAVqIA
Date: Mon, 23 May 2016 20:19:58 +0000
Message-ID: <36D9FCF0-382C-4669-85A5-C782636A85BB@vmware.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com> <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com> <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com>
In-Reply-To: <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.113.170.11]
Content-Type: multipart/alternative; boundary="_000_36D9FCF0382C466985A5C782636A85BBvmwarecom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EAvNCSiaeNOg37t0WV6rR8R1yJc>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 20:20:04 -0000

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

SSBhZ3JlZSB0aGF0IEkgZG9u4oCZdCBiZWxpZXZlIHRoYXQgdGhlcmUgaXMgYW55dGhpbmcgaW4g
dGhlc2UgZHJhZnRzIHRoYXQgcHJlY2x1ZGVzIHRoZSB1c2Ugb2YgZXh0ZW5zaW9uIGhlYWRlcnMg
b3Igc2VnbWVudCByb3V0aW5nIOKAkyBJUCBpcyBzaW1wbHkgdGhlIGxheWVyIHVuZGVybmVhdGgg
dGhhdCB0aGVzZSBwcm90b2NvbHMgYXJlIGJ1aWxkaW5nIG9uLiBUaGUgZmlndXJlcyBhcmUgZGVm
aW5pdGVseSBqdXN0IGV4YW1wbGVzIOKAkyB0aGV5IGFsc28gc2hvdyBvdXRlciBFdGhlcm5ldCBo
ZWFkZXJzLCB3aGljaCBpcyBub3QgYSByZXF1aXJlbWVudC4NCg0KSSB3b3VsZG7igJl0IHdhbnQg
dG8gYWRkIHRleHQgc3BlY2lmaWNhbGx5IHN0YXRpbmcgdGhhdCBleHRlbnNpb24gaGVhZGVycyBh
cmUgcGVybWlzc2libGUuIEl0IHNlZW1zIGxpa2UgdGhhdCBjb3VsZCBsZWFkIHRvIHNpbWlsYXIg
cXVlc3Rpb25zIGluIHRoZSBmdXR1cmUgd2hlcmUgb25lIG1pZ2h0IHdvbmRlciBpZiBvdGhlciBm
ZWF0dXJlcyBvZiBJUCBhcmUgYWxsb3dlZCBiZWNhdXNlIG9uZSBpcyBleHBsaWNpdGx5IGxpc3Rl
ZCBhbmQgb3RoZXJzIGFyZSBub3QsIGV0Yy4gSW4gbXkgb3BpbmlvbiwgdGhlIGRyYWZ0cyBhcmUg
YWJvdXQgYXMgY2xlYXIgYXMgdGhleSBjYW4gYmUgb24gdGhpcyBwb2ludC4NCg0KSmVzc2UNCg0K
T24gNS8yMy8xNiwgMTowOSBBTSwgInJyYXN6dWtAZ21haWwuY29tPG1haWx0bzpycmFzenVrQGdt
YWlsLmNvbT4gb24gYmVoYWxmIG9mIFJvYmVydCBSYXN6dWsiIDxycmFzenVrQGdtYWlsLmNvbTxt
YWlsdG86cnJhc3p1a0BnbWFpbC5jb20+IG9uIGJlaGFsZiBvZiByb2JlcnRAcmFzenVrLm5ldDxt
YWlsdG86cm9iZXJ0QHJhc3p1ay5uZXQ+PiB3cm90ZToNCg0KSGkgVGFsLA0KDQo+IEluIG9yZGVy
IHRvIGF2b2lkIGFtYmlndWl0eSwgaXQgd291bGQgYmUgZ3JlYXQgaWYgdGhlDQo+IGF1dGhvcnMg
Y291bGQgZXhwbGljaXRseSBtZW50aW9uIHRoYXQgSVB2NiBleHRlbnNpb24NCj4gaGVhZGVycyBh
cmUgcGVybWl0dGVkLg0KDQpXZWxsIHRoZSBkcmFmdHMgYXJlIGNvbXBsYWludCB0byBSRkMyMTE5
IChub3JtYXRpdmUgcmVmZXJlbmNlKSBzbyB1bmxlc3MgdGhlIHRleHQgZXhjbHVkZXMgZWxlbWVu
dHMgd2l0aCBNVVNUL01VU1QgTk9UIC0gZXZlcnl0aGluZyBlbHNlIGRlZmluZWQgaW4gdGhlIGJ1
aWxkaW5nIGJsb2NrcyB0aGV5IChyZSl1c2UgaXMgcGVybWl0dGVkLg0KDQpIb3dldmVyIGFzIHlv
dSBzYXkgcGVyaGFwcyBmb3IgY2xhcml0eSB3aGF0IGNvdWxkIGJlIGFkZGVkIHRvIHRob3NlIGRy
YWZ0cyBpcyBhIG5vcm1hdGl2ZSByZWZlcmVuY2UgdG8gSVB2NCBhbmQgSVB2NiBiYXNlIFJGQ3Mu
DQoNCkJlc3QsDQpSLg0KDQoNCk9uIE1vbiwgTWF5IDIzLCAyMDE2IGF0IDk6NTQgQU0sIFRhbCBN
aXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbTxtYWlsdG86dGFsbWlAbWFydmVsbC5jb20+PiB3cm90
ZToNCkhpIFJvYmVydCwNCg0KVGhhdCBtYWtlcyBzZW5zZS4NCkhvd2V2ZXIsIGluIHRoaXMgY2Fz
ZSB0aGUgZmlndXJlcyBtYXkgYmUgYSBiaXQgY29uZnVzaW5nIFdSVCB0aGUgcG9zc2libGUgZXhp
c3RlbmNlIG9mIGV4dGVuc2lvbiBoZWFkZXJzLiBUaGlzIGNvbmZ1c2lvbiBpcyB3aGF0IGxlZCB0
byB0aGUgZGlzY3Vzc2lvbiBpbiB0aGlzIHRocmVhZCBhYm91dCB3aGV0aGVyIHNlZ21lbnQgcm91
dGluZyBpcyBwb3NzaWJsZSB3aXRoIFZYTEFOL1ZYTEFOLUdQRS9HZW5ldmUgZW5jYXBzdWxhdGlv
bnMuDQoNCkluIG9yZGVyIHRvIGF2b2lkIGFtYmlndWl0eSwgaXQgd291bGQgYmUgZ3JlYXQgaWYg
dGhlIGF1dGhvcnMgY291bGQgZXhwbGljaXRseSBtZW50aW9uIHRoYXQgSVB2NiBleHRlbnNpb24g
aGVhZGVycyBhcmUgcGVybWl0dGVkLg0KDQpSZWdhcmRzLA0KVGFsLg0KDQpGcm9tOnJyYXN6dWtA
Z21haWwuY29tPG1haWx0bzpycmFzenVrQGdtYWlsLmNvbT4gW21haWx0bzpycmFzenVrQGdtYWls
LmNvbTxtYWlsdG86cnJhc3p1a0BnbWFpbC5jb20+XSBPbiBCZWhhbGYgT2YgUm9iZXJ0IFJhc3p1
aw0KU2VudDogTW9uZGF5LCBNYXkgMjMsIDIwMTYgMTA6NDcgQU0NCg0KVG86IFRhbCBNaXpyYWhp
DQpDYzogc3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+OyA2bWFuIFdHOyBk
cmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRm
LW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3JnPjsgbnZvM0BpZXRmLm9yZzxtYWlsdG86bnZv
M0BpZXRmLm9yZz47IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0
b29scy5pZXRmLm9yZz47IGRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc8bWFp
bHRvOmRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc+OyBTdGVmYW5vIFByZXZp
ZGkgKHNwcmV2aWRpKQ0KU3ViamVjdDogUmU6IFtudm8zXSBbc3ByaW5nXSBMNCBDaGVja3N1bSBh
bmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXINCg0KSGkgVGFsLA0KDQpJ
bmRlZWQgLi4gSSBzYXcgdGhlIGZpZ3VyZXMsIGJ1dCBmaWd1cmVzIGFyZSBub24gbm9ybWF0aXZl
IGluIGFueSBkcmFmdC9yZmMgdW5sZXNzIHRleHQgYmVsb3cgc3BlY2lmaWNhbGx5IHNwZWxscyBp
dCBvdXQuDQoNCkZvciBleGFtcGxlIGZyb20gdnhsYW4tZ3BlOg0KDQoiV2hlbiB0aGUgb3V0ZXIg
SVAgaGVhZGVyIGlzIElQdjQsIFZURVBzIE1VU1Qgc2V0IHRoZSBERiBiaXQuIg0KDQpCZXNpZGVz
IGl0IGlzIHByZXR0eSBjaGFsbGVuZ2luZyB0byBhZGQgYW5pbWF0aW9uIHRvIHRoZSBjdXJyZW50
IGRyYWZ0IGZvcm1hdHMgdG8gaWxsdXN0cmF0ZSBhbGwgcG9zc2libHkgYWxsb3dlZCBmaWVsZCB2
YWx1ZXMvY29tYmluYXRpb25zIGluIGFueSBmaWd1cmUgOikgIEZpZ3VyZXMganVzdCBpbGx1c3Ry
YXRlIG9uZSB1c2UgZXhhbXBsZS4NCg0KVG8gbWUgdGhlIGN1cnJlbnQgc3BlY3MgcGVybWl0IGFu
eSB2YWx1ZSBvZiBJUHY2IE54dEhkciBmaWVsZCBhcyBwZXJtaXR0ZWQgaW4gYm90aCBlbmNhcHN1
bGF0aW9ucy4NCg0KQmVzdCwNClJvYmVydC4NCg0KDQpPbiBNb24sIE1heSAyMywgMjAxNiBhdCA5
OjM1IEFNLCBUYWwgTWl6cmFoaSA8dGFsbWlAbWFydmVsbC5jb208bWFpbHRvOnRhbG1pQG1hcnZl
bGwuY29tPj4gd3JvdGU6DQpIaSBSb2JlcnQsDQoNCg0KPldoZXJlIHNheSBpbiBkcmFmdCBkcmFm
dC1xdWlubi12eGxhbi1ncGUgZG8geW91IHNlZSBzdWNoIHN0YXRlbWVudCB0aGF0IHdvdWxkIGlt
cGx5DQo+IHRoYXQgdjYgTnh0SGRyIG11c3QgYmUgb25seSBlcXVhbCB0byAxNyAoVURQKSBhbmQg
bm90IGJlIGEgcG9pbnRlciB0byBhbnkgb3RoZXIgdHlwZQ0KPiBvZiBleHRlbnNpb24gaGVhZGVy
IGZ1cnRoZXIgZm9sbG93ZWQgYnkgVURQID8NCg0KDQpUaGUgZm9sbG93aW5nIHRleHQgaXMgZnJv
bSBGaWd1cmUgNCBpbiBkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlOg0KDQogICAgICBPdXRlciBJ
UHY2IEhlYWRlcjoNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICAgICB8VmVyc2lvbnwgVHJhZmZpYyBDbGFz
cyB8ICAgICAgICAgICBGbG93IExhYmVsICAgICAgICAgICAgICAgICAgfA0KICAgICAgKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSsNCiAgICAgIHwgICAgICAgICBQYXlsb2FkIExlbmd0aCAgICAgICAgfCBOeHRIZHI9MTcoVURQ
KXwgICBIb3AgTGltaXQgICB8DQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAgfCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCg0KDQpU
aGVyZSBpcyBhIHNpbWlsYXIgZmlndXJlIGluIGRyYWZ0LWlldGYtbnZvMy1nZW5ldmUuDQoNCkJl
c3QgcmVnYXJkcywNClRhbC4NCg0KRnJvbTogbnZvMyBbbWFpbHRvOm52bzMtYm91bmNlc0BpZXRm
Lm9yZzxtYWlsdG86bnZvMy1ib3VuY2VzQGlldGYub3JnPl0gT24gQmVoYWxmIE9mIFJvYmVydCBS
YXN6dWsNClNlbnQ6IE1vbmRheSwgTWF5IDIzLCAyMDE2IDEwOjI5IEFNDQpUbzogVGFsIE1penJh
aGkNCkNjOiBzcHJpbmdAaWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0BpZXRmLm9yZz47IDZtYW4gV0c7
IGRyYWZ0LWlldGYtbnZvMy12eGxhbi1ncGVAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWll
dGYtbnZvMy12eGxhbi1ncGVAdG9vbHMuaWV0Zi5vcmc+OyBudm8zQGlldGYub3JnPG1haWx0bzpu
dm8zQGlldGYub3JnPjsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9v
bHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVy
QHRvb2xzLmlldGYub3JnPjsgZHJhZnQtaWV0Zi1udm8zLWdlbmV2ZUB0b29scy5pZXRmLm9yZzxt
YWlsdG86ZHJhZnQtaWV0Zi1udm8zLWdlbmV2ZUB0b29scy5pZXRmLm9yZz47IFN0ZWZhbm8gUHJl
dmlkaSAoc3ByZXZpZGkpDQoNClN1YmplY3Q6IFJlOiBbbnZvM10gW3NwcmluZ10gTDQgQ2hlY2tz
dW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyDQoNCkhpIFRhbCwN
Cg0KPiBkcmFmdHMgc2VlbSB0byBpbXBseQ0KDQpXaGVyZSBzYXkgaW4gZHJhZnQgZHJhZnQtcXVp
bm4tdnhsYW4tZ3BlIGRvIHlvdSBzZWUgc3VjaCBzdGF0ZW1lbnQgdGhhdCB3b3VsZCBpbXBseSB0
aGF0IHY2IE54dEhkciBtdXN0IGJlIG9ubHkgZXF1YWwgdG8gMTcgKFVEUCkgYW5kIG5vdCBiZSBh
IHBvaW50ZXIgdG8gYW55IG90aGVyIHR5cGUgb2YgZXh0ZW5zaW9uIGhlYWRlciBmdXJ0aGVyIGZv
bGxvd2VkIGJ5IFVEUCA/DQoNClRoeCwNClIuDQoNCg0KT24gTW9uLCBNYXkgMjMsIDIwMTYgYXQg
Nzo1MCBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29tPG1haWx0bzp0YWxtaUBtYXJ2
ZWxsLmNvbT4+IHdyb3RlOg0KRGVhciBBdXRob3JzIG9mIFZYTEFOLUdQRSAvIEdlbmV2ZSwNCg0K
SSBhbSByZWl0ZXJhdGluZyBvbiB0aGlzIHF1ZXN0aW9uLCBhcyBJIGhhdmVuJ3Qgc2VlbiBhIHJl
c3BvbnNlIHlldDoNCg0KSGF2ZSB5b3UgY29uc2lkZXJlZCB0aGUgdXNlIG9mIFNlZ21lbnQgUm91
dGluZyB3aXRoIFZYTEFOLUdQRSAvIEdlbmV2ZT8gVGhlIGN1cnJlbnQgVlhMQU4tR1BFIC8gR2Vu
ZXZlIGRyYWZ0cyBzZWVtIHRvIGltcGx5IHRoYXQgSVB2NiBleHRlbnNpb24gaGVhZGVycyBhcmUg
Y3VycmVudGx5IG5vdCBzdXBwb3J0ZWQuDQoNClRoYW5rcywNClRhbC4NCg0KDQoNCj4tLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IG52bzMgW21haWx0bzpudm8zLWJvdW5jZXNAaWV0
Zi5vcmc8bWFpbHRvOm52bzMtYm91bmNlc0BpZXRmLm9yZz5dIE9uIEJlaGFsZiBPZiBUYWwgTWl6
cmFoaQ0KPlNlbnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAxMjowOSBQTQ0KPlRvOiBTdGVmYW5v
IFByZXZpZGkgKHNwcmV2aWRpKTsgVG9tIEhlcmJlcnQ7IGRyYWZ0LWlldGYtbnZvMy0NCj5nZW5l
dmVAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmdlbmV2ZUB0b29scy5pZXRmLm9yZz47IGRyYWZ0LWll
dGYtbnZvMy12eGxhbi1ncGVAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtbnZvMy12
eGxhbi1ncGVAdG9vbHMuaWV0Zi5vcmc+DQo+Q2M6IHNwcmluZ0BpZXRmLm9yZzxtYWlsdG86c3By
aW5nQGlldGYub3JnPjsgbnZvM0BpZXRmLm9yZzxtYWlsdG86bnZvM0BpZXRmLm9yZz47IDZtYW4g
V0c7IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LQ0KPnJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYu
b3JnPG1haWx0bzpyb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZz4NCj5TdWJqZWN0OiBSZTog
W252bzNdIFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC0N
Cj5yb3V0aW5nLWhlYWRlcg0KPg0KPlN0ZWZhbm8sDQo+DQo+SWYgSSB1bmRlcnN0YW5kIHlvdXIg
cG9pbnQgY29ycmVjdGx5Og0KPklQdjYgc2VnbWVudCByb3V0aW5nIGRvZXMgbm90IHdvcmsgd2l0
aCBWWExBTiAvIFZYTEFOLUdQRSAvIEdlbmV2ZSwgc2luY2UNCj50aGVzZSBlbmNhcHN1bGF0aW9u
cyBkbyBub3QgY3VycmVudGx5IGFsbG93IHRoZSB1c2Ugb2YgSVB2NiBleHRlbnNpb24NCj5oZWFk
ZXJzLg0KPg0KPkkgd29uZGVyIGlmIHRoZSBhdXRob3JzIG9mIFZYTEFOLUdQRSBhbmQgR2VuZXZl
IGhhdmUgY29uc2lkZXJlZCB0aGUgdXNlIG9mDQo+c2VnbWVudCByb3V0aW5nLg0KPg0KPlRoYW5r
cywNCj5UYWwuDQo+DQo+DQo+DQo+Pi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PkZyb206
IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tPG1h
aWx0bzpzcHJldmlkaUBjaXNjby5jb20+XQ0KPj5TZW50OiBUdWVzZGF5LCBNYXkgMTcsIDIwMTYg
MTA6NDEgQU0NCj4+VG86IFRvbSBIZXJiZXJ0DQo+PkNjOiBUYWwgTWl6cmFoaTsgNm1hbiBXRzsg
c3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+Ow0KPj5kcmFmdC1pZXRmLTZt
YW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXJAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmhlYWRlckB0
b29scy5pZXRmLm9yZz4NCj4+U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLQ0KPj5oZWFkZXINCj4+DQo+Pg0KPj4+IE9u
IE1heSAxNiwgMjAxNiwgYXQgNzoxMCBQTSwgVG9tIEhlcmJlcnQgPHRvbUBoZXJiZXJ0bGFuZC5j
b208bWFpbHRvOnRvbUBoZXJiZXJ0bGFuZC5jb20+Pg0KPndyb3RlOg0KPj4+DQo+Pj4gT24gTW9u
LCBNYXkgMTYsIDIwMTYgYXQgNDozMiBBTSwgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29t
PG1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNvbT4+DQo+Pndyb3RlOg0KPj4+Pj4gaXTigJlzIGFsbCBh
Ym91dCBJUCwgbm90IGxheWVyLTIuDQo+Pj4+Pg0KPj4+Pj4gcy4NCj4+Pj4NCj4+Pj4gUmlnaHQu
IEhvd2V2ZXIsIGl0IGFwcGVhcnMgdGhhdCBhdCBsZWFzdCBpbiBzb21lIGNhc2VzIGEgVlhMQU4g
VlRFUA0KPj4+PiB3aWxsDQo+PnVzZSBTUi4gSXQgY2VydGFpbmx5IG1heSBiZSB0aGUgY2FzZSBp
biBTRkMgdXNlIGNhc2VzIChzZWUgU2VjdGlvbiAyLjMNCj4+aW4gZHJhZnQtIGlldGYtc3ByaW5n
LWlwdjYtdXNlLWNhc2VzKS4NCj4+Pj4NCj4+Pg0KPj4+IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50
LXJvdXRpbmctaGVhZGVyIG1lbnRpb25zIHRoYXQgdGhlIHBhY2tldCBpcw0KPj4+IGVuY2Fwc3Vs
YXRlZA0KPj4NCj4+DQo+PmludG8gYW4gb3V0ZXIgaXB2NiBoZWFkZXIgd2hpY2ggbWFrZXMgaXQg
YSBsYXllci0zIGVuY2FwLg0KPj4NCj4+DQo+Pj4gLCBidXQgSSBkb24ndCB0aGluayBpdCBpcyBl
eHBsaWNpdCBhcyB0byBleGFjdCBlbmNhcHN1bGF0aW9uIGZvcm1hdA0KPj4+IChJIHN1cHBvc2Ug
c2ltcGxlIGlwNmlwNiBpcyBpbXBsaWVkKS4NCj4+DQo+Pg0KPj5zZWUgc2VjdGlvbiAyLjINCj4+
DQo+Pg0KPj4+IEJ1dCwgaXQNCj4+PiBzZWVtcyBsaWtlIGFueSBvZiBzZXZlcmFsIGVuY2Fwc3Vs
YXRpb24gdGVjaG5pcXVlcyBjb3VsZCB3b3JrIChWWExBTiwNCj4+DQo+Pg0KPj5JIGhhdmUgc29t
ZSBwcm9ibGVtcyB0byB1bmRlcnN0YW5kIHdoZXJlIHRvIGZpdCBhbiBleHRlbnNpb24gaGVhZGVy
DQo+PmludG8gYSB2eGxhbiBlbmNhcOKApg0KPj4NCj4+DQo+Pj4gR1JFL0lQLCBFU1AvSVAsIEdV
RSwgZm9vIG92ZXIgVURQLCBldGMuKSBhbmQgaWYgYSBkZXZpY2UgdGhhdCB3YW50cw0KPj4+IHRv
IGRvIFNSIGlzIGFscmVhZHkgZG9pbmcgdHVubmVsaW5nIGl0IHNlZW1zIHJlYXNvbmFibGUgdG8g
bWUgdG8gb25seQ0KPj4+IGhhdmUgb25lIGxheWVyIG9mIGVuY2Fwc3VsYXRpb24uIE1heWJlIHRo
aXMgc2hvdWxkIGJlIGNsYXJpZmllZCBpbg0KPj4+IHRoZSBkcmFmdD8NCj4+DQo+Pg0KPj50aGUg
ZHJhZnQgaXMgYWJvdXQgSVB2NiBleHRlbnNpb24gaGVhZGVyIGFuZCBtb3JlIHByZWNpc2VseSBh
IG5ldyB0eXBlDQo+Pm9mIHRoZSByb3V0aW5nIGV4dGVuc2lvbiBoZWFkZXIgZGVmaW5lZCBpbiBy
ZmMyNDYwLiBUaGF04oCZcyB0aGUgY29udGV4dC4NCj4+DQo+Pg0KPj5zLg0KPj4NCj4+DQo+Pg0K
Pj4NCj4+Pg0KPj4+IFRvbQ0KPj4+DQo+Pj4+DQo+Pj4+DQo+Pj4+PiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPj4+Pj4gRnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0
bzpzcHJldmlkaUBjaXNjby5jb208bWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbT5dDQo+Pj4+PiBT
ZW50OiBNb25kYXksIE1heSAxNiwgMjAxNiAyOjI0IFBNDQo+Pj4+PiBUbzogVGFsIE1penJhaGkN
Cj4+Pj4+IENjOiBPbGUgVHLDuGFuOw0KPj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91
dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50
LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPjsNCj4+Pj4+IHNwcmluZ0BpZXRmLm9yZzxt
YWlsdG86c3ByaW5nQGlldGYub3JnPjsgNm1hbiBXRw0KPj4+Pj4gU3ViamVjdDogUmU6IFtzcHJp
bmddIEw0IENoZWNrc3VtIGFuZA0KPj4+Pj4gZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGlu
Zy0gaGVhZGVyDQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+PiBPbiBNYXkgMTYsIDIwMTYsIGF0IDE6MTkg
UE0sIFRhbCBNaXpyYWhpIDx0YWxtaUBtYXJ2ZWxsLmNvbTxtYWlsdG86dGFsbWlAbWFydmVsbC5j
b20+PiB3cm90ZToNCj4+Pj4+Pg0KPj4+Pj4+IEhpIFN0ZWZhbm8sDQo+Pj4+Pj4NCj4+Pj4+PiBU
aGFua3MgYWdhaW4gZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuDQo+Pj4+Pj4NCj4+Pj4+Pj4gMi4g
dGhlIFNSSCBpcyBvcmlnaW5hdGVkIGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRvbWFp
bi4NCj4+Pj4+Pj4gVGhpcyBpcyBkb25lIGJ5IGVuY2Fwc3VsYXRpbmcgdGhlIHBhY2tldCBpbnRv
IGEgb3V0ZXINCj4+Pj4+Pj4gKGFkZGl0aW9uYWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFu
IFNSSC4gVGhpcyBpcyBMMw0KPj4+Pj4+PiBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1
bSBpcyBpbnZvbHZlZC4gV2hlbiB0aGUgIHBhY2tldA0KPj4+Pj4+PiBsZWF2ZXMgdGhlIFNSIHR1
bm5lbCB0aGUgb3V0ZXIgZW5jYXBzdWxhdGlvbiAgKGluY2x1ZGluZyB0aGUgU1JIKQ0KPj4+Pj4+
PiBpcyByZW1vdmVkIGFuZCB0aGUgcGFja2V0IGNvbnRpbnVlcyAgaXRzIGpvdXJuZXkgbGlrZSBu
b3RoaW5nDQo+aGFwcGVuZWQuDQo+Pj4+Pj4NCj4+Pj4+PiBTbyBWWExBTiBpcyBvZmYgdGhlIHRh
YmxlPw0KPj4+Pj4NCj4+Pj4+DQo+Pj4+PiBpdOKAmXMgYWxsIGFib3V0IElQLCBub3QgbGF5ZXIt
Mi4NCj4+Pj4+DQo+Pj4+PiBzLg0KPj4+Pj4NCj4+Pj4+DQo+Pj4+Pj4gSXQgd291bGQgYmUgd29y
dGh3aGlsZSB0byBjbGFyaWZ5IHRoaXMgaW4gdGhlIGRyYWZ0LiBJZiB5b3UgaGF2ZSBhDQo+Pj4+
Pj4gc3BlY2lmaWMNCj4+Pj4+IGVuY2Fwc3VsYXRpb24gaW4gbWluZCwgaXQgd291bGQgYmUgZ3Jl
YXQgaWYgdGhlIGRyYWZ0IHdvdWxkIHNwZWNpZnkgaXQuDQo+Pj4+Pj4NCj4+Pj4+PiBUaGFua3Ms
DQo+Pj4+Pj4gVGFsLg0KPj4+Pj4+DQo+Pj4+Pj4NCj4+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4+Pj4+Pj4gRnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0
bzpzcHJldmlkaUBjaXNjby5jb208bWFpbHRvOnNwcmV2aWRpQGNpc2NvLmNvbT5dDQo+Pj4+Pj4+
IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDI6MTMgUE0NCj4+Pj4+Pj4gVG86IFRhbCBNaXpy
YWhpDQo+Pj4+Pj4+IENjOiBPbGUgVHLDuGFuOw0KPj4+Pj4+PiBkcmFmdC1pZXRmLTZtYW4tc2Vn
bWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmc+Ow0KPj4+Pj4+PiBzcHJpbmdA
aWV0Zi5vcmc8bWFpbHRvOnNwcmluZ0BpZXRmLm9yZz47IDZtYW4gV0cNCj4+Pj4+Pj4gU3ViamVj
dDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+Pj4+PiBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLSBoZWFkZXINCj4+Pj4+Pj4NCj4+Pj4+Pj4gSGksDQo+Pj4+Pj4+DQo+
Pj4+Pj4+IE9uIE1heSAxNiwgMjAxNiwgYXQgMTE6MDQgQU0sIFRhbCBNaXpyYWhpIDx0YWxtaUBt
YXJ2ZWxsLmNvbTxtYWlsdG86dGFsbWlAbWFydmVsbC5jb20+Pg0KPj53cm90ZToNCj4+Pj4+Pj4+
DQo+Pj4+Pj4+PiBIaSBTdGVmYW5vLA0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+IFRoYW5rcyBmb3IgdGhl
IHJlc3BvbnNlcy4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gZXhhY3RseS4NCj4+Pj4+Pj4+Pg0KPj4+
Pj4+Pj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBh
c3N1bWVzDQo+Pj4+Pj4+Pj4gZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBM
NCBpbnZvbHZlZCBoZXJlLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gcy4NCj4+Pj4+Pj4+DQo+Pj4+
Pj4+PiBUd28gcXVlc3Rpb25zOg0KPj4+Pj4+Pj4gMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlv
biBpcyBWWExBTj8gTDQgd291bGQgc3RpbGwgYmUNCj4+Pj4+Pj4+IGludm9sdmVkLA0KPj5yaWdo
dD8NCj4+Pj4+Pj4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gU2VlIGJlbG93Lg0KPj4+Pj4+Pg0KPj4+Pj4+
Pg0KPj4+Pj4+Pj4gMi4gV2hlbiB5b3Ugc2F5ICdhc3N1bWVzIGVuY2Fwc3VsYXRpb24nLCBkb2Vz
IGl0IG1lYW4gdGhhdCBhDQo+Pj4+Pj4+PiBob3N0IGNhbm5vdA0KPj4+Pj4+PiBzZW5kIGFuIElQ
djYgcGFja2V0IHdpdGggYW4gU1JIPyBUaGUgY3VycmVudCBkcmFmdCBzYXlzOg0KPj4+Pj4+Pj4N
Cj4+Pj4+Pj4+IEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFueSBub2RlIG9yaWdpbmF0aW5nIGFu
IElQdjYgcGFja2V0IHdpdGgNCj4+Pj4+Pj4+IGl0cw0KPj4+Pj4+Pj4gSVB2NiBhbmQgU2VnbWVu
dCBSb3V0aW5nIEhlYWRlcnMuICBUaGlzIGluY2x1ZGUgZWl0aGVyOg0KPj4+Pj4+Pj4NCj4+Pj4+
Pj4+ICAgIEEgaG9zdCBvcmlnaW5hdGluZyBhbiBJUHY2IHBhY2tldC4NCj4+Pj4+Pj4+DQo+Pj4+
Pj4+PiAgICBBbiBTUiBkb21haW4gaW5ncmVzcyByb3V0ZXIgZW5jYXBzdWxhdGluZyBhIHJlY2Vp
dmVkIElQdjYgcGFja2V0DQo+Pj4+Pj4+PiAgICBpbnRvIGFuIG91dGVyIElQdjYgaGVhZGVyIGZv
bGxvd2VkIGJ5IGFuIFNSSC4NCj4+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+
IFdpbGwgYXBwcmVjaWF0ZSBpZiB5b3UgY2FuIGNsYXJpZnkgdGhhdC4NCj4+Pj4+Pj4NCj4+Pj4+
Pj4NCj4+Pj4+Pj4gb2ssIHR3byBjYXNlczoNCj4+Pj4+Pj4NCj4+Pj4+Pj4gMS4gdGhlIFNSSCBp
cyBpbnNlcnRlZCBhdCB0aGUgc291cmNlLg0KPj4+Pj4+PiB0aGUgc291cmNlIG9yaWdpbmF0ZXMg
dGhlIHBhY2tldCwgdGhlIGlwdjYgaGVhZGVyIGFuZCAgdGhlIFNSSC4NCj4+Pj4+Pj4gVGhlIHNv
dXJjZSBjb21wdXRlcyBMNCBjaGVja3N1bSB0YWtpbmcgaW50byAgYWNjb3VudCB0aGUgd2hvbGUN
Cj4+SVB2NitTUkguDQo+Pj4+Pj4+IEhlcmUsIHRoZXJlc+KAmSBub3RoaW5nIG5ldyAgY29tcGFy
ZWQgdG8gcmZjMjQ2MC4NCj4+Pj4+Pj4NCj4+Pj4+Pj4gMi4gdGhlIFNSSCBpcyBvcmlnaW5hdGVk
IGJ5IHRoZSBpbmdyZXNzIG5vZGUgb2YgdGhlIFNSIGRvbWFpbi4NCj4+Pj4+Pj4gVGhpcyBpcyBk
b25lIGJ5IGVuY2Fwc3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0ZXINCj4+Pj4+Pj4gKGFk
ZGl0aW9uYWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMw0KPj4+
Pj4+PiBlbmNhcHN1bGF0aW9uIGFuZCBubyBMNCBjaGVja3N1bSBpcyBpbnZvbHZlZC4gV2hlbiB0
aGUgIHBhY2tldA0KPj4+Pj4+PiBsZWF2ZXMgdGhlIFNSIHR1bm5lbCB0aGUgb3V0ZXIgZW5jYXBz
dWxhdGlvbiAgKGluY2x1ZGluZyB0aGUgU1JIKQ0KPj4+Pj4+PiBpcyByZW1vdmVkIGFuZCB0aGUg
cGFja2V0IGNvbnRpbnVlcyAgaXRzIGpvdXJuZXkgbGlrZSBub3RoaW5nDQo+aGFwcGVuZWQuDQo+
Pj4+Pj4+DQo+Pj4+Pj4+IHMuDQo+Pj4+Pj4+DQo+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+Pj4g
VGhhbmtzLA0KPj4+Pj4+Pj4gVGFsLg0KPj4+Pj4+Pj4NCj4+Pj4+Pj4+PiAtLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPj4+Pj4+Pj4+IEZyb206IFN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkp
IFttYWlsdG86c3ByZXZpZGlAY2lzY28uY29tPG1haWx0bzpzcHJldmlkaUBjaXNjby5jb20+XQ0K
Pj4+Pj4+Pj4+IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAyMDE2IDExOjU5IEFNDQo+Pj4+Pj4+Pj4g
VG86IE9sZSBUcsO4YW47IFRhbCBNaXpyYWhpDQo+Pj4+Pj4+Pj4gQ2M6IGRyYWZ0LWlldGYtNm1h
bi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRm
LTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZz47DQo+Pj4+Pj4+Pj4g
c3ByaW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+OyA2bWFuIFdHDQo+Pj4+Pj4+
Pj4gU3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZA0KPj4+Pj4+Pj4+IGRyYWZ0
LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctIGhlYWRlcg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4N
Cj4+Pj4+Pj4+Pj4gT24gTWF5IDE1LCAyMDE2LCBhdCA4OjA2IFBNLCBvdHJvYW5AZW1wbG95ZWVz
Lm9yZzxtYWlsdG86b3Ryb2FuQGVtcGxveWVlcy5vcmc+IHdyb3RlOg0KPj4+Pj4+Pj4+Pg0KPj4+
Pj4+Pj4+PiBUYWwsDQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+PiBbQXBvbG9naWVzIGlmIHRoaXMg
aXNzdWUgaGFzIGJlZW4gZGlzY3Vzc2VkIGJlZm9yZS5dDQo+Pj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+
Pj4gQWNjb3JkaW5nIHRvIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyLCBh
biDigJhTUg0KPj4+Pj4+Pj4+Pj4gU2VnbWVudA0KPj4+Pj4+Pj4+IEVuZHBvaW50IE5vZGXigJkg
dXBkYXRlcyB0aGUgRGVzdGluYXRpb24gSVAgYWRkcmVzcy4NCj4+Pj4+Pj4+Pj4+IFRoZXJlZm9y
ZSwgaXQgbXVzdCBhbHNvIHVwZGF0ZSB0aGUgTGF5ZXIgNCBDaGVja3N1bSwgcmlnaHQ/DQo+Pj4+
Pj4+Pj4+Pg0KPj4+Pj4+Pj4+Pj4gSSB3b25kZXIgaWYgdGhlcmUgaXMgYW4gdXBwZXIgYm91bmQg
b24gdGhlIHNpemUgb2YgdGhlIFNSSC4NCj4+Pj4+Pj4+Pj4+IE90aGVyd2lzZSwgdGhlDQo+Pj4+
Pj4+Pj4gTDQgQ2hlY2tzdW0gbWF5IGJlIGxvY2F0ZWQgaW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlv
bi4NCj4+Pj4+Pj4+Pj4+IFNwZWFraW5nIGZyb20gYSBjaGlwIHZlbmRvcuKAmXMgcGVyc3BlY3Rp
dmUgdGhpcyBtYXkgYmUgYSBwcm9ibGVtLg0KPj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+PiBGcm9tIFJG
QzI0NjAsIFJIMDoNCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4gICBvICBJZiB0
aGUgSVB2NiBwYWNrZXQgY29udGFpbnMgYSBSb3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9u
DQo+Pj4+Pj4+Pj4+ICAgICAgQWRkcmVzcyB1c2VkIGluIHRoZSBwc2V1ZG8taGVhZGVyIGlzIHRo
YXQgb2YgdGhlIGZpbmFsDQo+Pj4+Pj4+Pj4+ICAgICAgZGVzdGluYXRpb24uICBBdCB0aGUgb3Jp
Z2luYXRpbmcgbm9kZSwgdGhhdCBhZGRyZXNzIHdpbGwgYmUgaW4NCj4+Pj4+Pj4+Pj4gICAgICB0
aGUgbGFzdCBlbGVtZW50IG9mIHRoZSBSb3V0aW5nIGhlYWRlcjsgYXQgdGhlIHJlY2lwaWVudChz
KSwNCj4+Pj4+Pj4+Pj4gICAgICB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBpbiB0aGUgRGVzdGluYXRp
b24gQWRkcmVzcyBmaWVsZCBvZiB0aGUNCj4+Pj4+Pj4+Pj4gICAgICBJUHY2IGhlYWRlci4NCj4+
Pj4+Pj4+Pj4NCj4+Pj4+Pj4+Pj4gSSB3b3VsZCBleHBlY3QgU1Igd291bGQgd29yayB0aGUgc2Ft
ZS4NCj4+Pj4+Pj4+Pg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gZXhhY3RseS4NCj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRl
ciBhc3N1bWVzDQo+Pj4+Pj4+Pj4gZW5jYXBzdWxhdGlvbiBzbyBjbGVhcmx5IHRoZXJl4oCZcyBu
byBMNCBpbnZvbHZlZCBoZXJlLg0KPj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4gcy4NCj4+Pj4+Pj4+Pg0K
Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pj4+IENoZWVycywNCj4+Pj4+Pj4+Pj4gT2xl
DQo+Pj4+Pj4+Pj4+DQo+Pj4+Pj4+Pg0KPj4+Pj4+DQo+Pj4+DQo+Pj4+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+
Pj4+IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdCBpcHY2QGlldGYub3JnPG1h
aWx0bzppcHY2QGlldGYub3JnPiBBZG1pbmlzdHJhdGl2ZQ0KPj4+PiBSZXF1ZXN0czogaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2DQo+Pj4+IC0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+
DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5udm8z
IG1haWxpbmcgbGlzdA0KPm52bzNAaWV0Zi5vcmc8bWFpbHRvOm52bzNAaWV0Zi5vcmc+DQo+aHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9udm8zDQpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kc3ByaW5nIG1haWxpbmcgbGlzdA0Kc3By
aW5nQGlldGYub3JnPG1haWx0bzpzcHJpbmdAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3NwcmluZw0KDQoNCg0K

--_000_36D9FCF0382C466985A5C782636A85BBvmwarecom_
Content-Type: text/html; charset="utf-8"
Content-ID: <6A9EBD032C29354894041B3C81807234@vmware.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+DQo8
ZGl2PkkgYWdyZWUgdGhhdCBJIGRvbuKAmXQgYmVsaWV2ZSB0aGF0IHRoZXJlIGlzIGFueXRoaW5n
IGluIHRoZXNlIGRyYWZ0cyB0aGF0IHByZWNsdWRlcyB0aGUgdXNlIG9mIGV4dGVuc2lvbiBoZWFk
ZXJzIG9yIHNlZ21lbnQgcm91dGluZyDigJMgSVAgaXMgc2ltcGx5IHRoZSBsYXllciB1bmRlcm5l
YXRoIHRoYXQgdGhlc2UgcHJvdG9jb2xzIGFyZSBidWlsZGluZyBvbi4gVGhlIGZpZ3VyZXMgYXJl
IGRlZmluaXRlbHkganVzdCBleGFtcGxlcyDigJMgdGhleQ0KIGFsc28gc2hvdyBvdXRlciBFdGhl
cm5ldCBoZWFkZXJzLCB3aGljaCBpcyBub3QgYSByZXF1aXJlbWVudC48L2Rpdj4NCjxkaXY+PGJy
Pg0KPC9kaXY+DQo8ZGl2Pkkgd291bGRu4oCZdCB3YW50IHRvIGFkZCB0ZXh0IHNwZWNpZmljYWxs
eSBzdGF0aW5nIHRoYXQgZXh0ZW5zaW9uIGhlYWRlcnMgYXJlIHBlcm1pc3NpYmxlLiBJdCBzZWVt
cyBsaWtlIHRoYXQgY291bGQgbGVhZCB0byBzaW1pbGFyIHF1ZXN0aW9ucyBpbiB0aGUgZnV0dXJl
IHdoZXJlIG9uZSBtaWdodCB3b25kZXIgaWYgb3RoZXIgZmVhdHVyZXMgb2YgSVAgYXJlIGFsbG93
ZWQgYmVjYXVzZSBvbmUgaXMgZXhwbGljaXRseSBsaXN0ZWQgYW5kIG90aGVycw0KIGFyZSBub3Qs
IGV0Yy4gSW4gbXkgb3BpbmlvbiwgdGhlIGRyYWZ0cyBhcmUgYWJvdXQgYXMgY2xlYXIgYXMgdGhl
eSBjYW4gYmUgb24gdGhpcyBwb2ludC48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pkpl
c3NlPC9kaXY+DQo8ZGl2Pg0KPGRpdiBpZD0iTUFDX09VVExPT0tfU0lHTkFUVVJFIj48L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xL
X1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdj4NCjxkaXY+T24gNS8yMy8xNiwgMTowOSBBTSwgJnF1
b3Q7PGEgaHJlZj0ibWFpbHRvOnJyYXN6dWtAZ21haWwuY29tIj5ycmFzenVrQGdtYWlsLmNvbTwv
YT4gb24gYmVoYWxmIG9mIFJvYmVydCBSYXN6dWsmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpy
cmFzenVrQGdtYWlsLmNvbSI+cnJhc3p1a0BnbWFpbC5jb208L2E+IG9uIGJlaGFsZiBvZg0KPGEg
aHJlZj0ibWFpbHRvOnJvYmVydEByYXN6dWsubmV0Ij5yb2JlcnRAcmFzenVrLm5ldDwvYT4mZ3Q7
IHdyb3RlOjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgaWQ9
Ik1BQ19PVVRMT09LX0FUVFJJQlVUSU9OX0JMT0NLUVVPVEUiIHN0eWxlPSJCT1JERVItTEVGVDog
I2I1YzRkZiA1IHNvbGlkOyBQQURESU5HOjAgMCAwIDU7IE1BUkdJTjowIDAgMCA1OyI+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5
bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFs
bCI+DQpIaSBUYWwsPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9u
dC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxi
cj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5
OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8c3BhbiBzdHls
ZT0iY29sb3I6cmdiKDMxLDczLDEyNSk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmO2Zv
bnQtc2l6ZToxNC42NjY3cHgiPiZndDsgSW4gb3JkZXIgdG8gYXZvaWQgYW1iaWd1aXR5LCBpdCB3
b3VsZCBiZSBncmVhdCBpZiB0aGUmbmJzcDs8L3NwYW4+PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFp
bF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7
Zm9udC1zaXplOnNtYWxsIj4NCjxzcGFuIHN0eWxlPSJjb2xvcjpyZ2IoMzEsNzMsMTI1KTtmb250
LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0LjY2NjdweCI+Jmd0OyBhdXRo
b3JzIGNvdWxkIGV4cGxpY2l0bHkgbWVudGlvbiB0aGF0IElQdjYgZXh0ZW5zaW9uJm5ic3A7PC9z
cGFuPjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5
OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQo8c3BhbiBzdHls
ZT0iY29sb3I6cmdiKDMxLDczLDEyNSk7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmO2Zv
bnQtc2l6ZToxNC42NjY3cHgiPiZndDsgaGVhZGVycyBhcmUgcGVybWl0dGVkLjwvc3Bhbj48YnI+
DQo8L2Rpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2RlZmF1bHQiIHN0eWxlPSJmb250LWZhbWlseTph
cmlhbCxoZWx2ZXRpY2Esc2Fucy1zZXJpZjtmb250LXNpemU6c21hbGwiPg0KPGJyPg0KPC9kaXY+
DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJpYWwsaGVs
dmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCldlbGwgdGhlIGRyYWZ0cyBhcmUg
Y29tcGxhaW50IHRvIFJGQzIxMTkgKG5vcm1hdGl2ZSByZWZlcmVuY2UpIHNvIHVubGVzcyB0aGUg
dGV4dCBleGNsdWRlcyBlbGVtZW50cyB3aXRoIE1VU1QvTVVTVCBOT1QgLSBldmVyeXRoaW5nIGVs
c2UgZGVmaW5lZCBpbiB0aGUgYnVpbGRpbmcgYmxvY2tzIHRoZXkgKHJlKXVzZSBpcyBwZXJtaXR0
ZWQuJm5ic3A7PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1m
YW1pbHk6YXJpYWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4N
CjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFy
aWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpIb3dldmVyIGFzIHlv
dSBzYXkgcGVyaGFwcyBmb3IgY2xhcml0eSB3aGF0IGNvdWxkIGJlIGFkZGVkIHRvIHRob3NlIGRy
YWZ0cyBpcyBhIG5vcm1hdGl2ZSByZWZlcmVuY2UgdG8gSVB2NCBhbmQgSVB2NiBiYXNlIFJGQ3Mu
PC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9kZWZhdWx0IiBzdHlsZT0iZm9udC1mYW1pbHk6YXJp
YWwsaGVsdmV0aWNhLHNhbnMtc2VyaWY7Zm9udC1zaXplOnNtYWxsIj4NCjxicj4NCjwvZGl2Pg0K
PGRpdiBjbGFzcz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZl
dGljYSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpCZXN0LDwvZGl2Pg0KPGRpdiBjbGFz
cz0iZ21haWxfZGVmYXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5z
LXNlcmlmO2ZvbnQtc2l6ZTpzbWFsbCI+DQpSLjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZGVm
YXVsdCIgc3R5bGU9ImZvbnQtZmFtaWx5OmFyaWFsLGhlbHZldGljYSxzYW5zLXNlcmlmO2ZvbnQt
c2l6ZTpzbWFsbCI+DQo8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0
cmEiPjxicj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBNb24sIE1heSAyMywgMjAxNiBh
dCA5OjU0IEFNLCBUYWwgTWl6cmFoaSA8c3BhbiBkaXI9Imx0ciI+DQombHQ7PGEgaHJlZj0ibWFp
bHRvOnRhbG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGFsbWlAbWFydmVsbC5jb208
L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3Rl
IiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFk
ZGluZy1sZWZ0OjFleCI+DQo8ZGl2IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwg
NzMsIDEyNSk7Ij5IaSBSb2JlcnQsPHU+PC91Pjx1PjwvdT48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENh
bGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+PHU+PC91PiZuYnNw
Ozx1PjwvdT48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiBy
Z2IoMzEsIDczLCAxMjUpOyI+VGhhdCBtYWtlcyBzZW5zZS48dT48L3U+PHU+PC91Pjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBm
b250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7
Ij5Ib3dldmVyLCBpbiB0aGlzIGNhc2UgdGhlIGZpZ3VyZXMgbWF5IGJlIGEgYml0IGNvbmZ1c2lu
ZyBXUlQgdGhlIHBvc3NpYmxlIGV4aXN0ZW5jZSBvZiBleHRlbnNpb24gaGVhZGVycy4gVGhpcyBj
b25mdXNpb24gaXMgd2hhdCBsZWQgdG8gdGhlIGRpc2N1c3Npb24NCiBpbiB0aGlzIHRocmVhZCBh
Ym91dCB3aGV0aGVyIHNlZ21lbnQgcm91dGluZyBpcyBwb3NzaWJsZSB3aXRoIFZYTEFOL1ZYTEFO
LUdQRS9HZW5ldmUgZW5jYXBzdWxhdGlvbnMuPHU+PC91Pjx1PjwvdT48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1p
bHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+PHU+PC91
PiZuYnNwOzx1PjwvdT48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNv
bG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+SW4gb3JkZXIgdG8gYXZvaWQgYW1iaWd1aXR5LCBpdCB3
b3VsZCBiZSBncmVhdCBpZiB0aGUgYXV0aG9ycyBjb3VsZCBleHBsaWNpdGx5IG1lbnRpb24gdGhh
dCBJUHY2IGV4dGVuc2lvbiBoZWFkZXJzIGFyZSBwZXJtaXR0ZWQuPHU+PC91Pjx1PjwvdT48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFw
dDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAx
MjUpOyI+PHU+PC91PiZuYnNwOzx1PjwvdT48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh
bnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+UmVnYXJkcyw8dT48L3U+PHU+PC91
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwg
NzMsIDEyNSk7Ij5UYWwuPHU+PC91Pjx1PjwvdT48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmks
IHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+PHU+PC91PiZuYnNwOzx1Pjwv
dT48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
Ymx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNiNWM0ZGYgMS4wcHQ7cGFkZGluZzozLjBw
dCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOiAxMHB0OyBmb250LWZhbWlseTogVGFob21hLCBzYW5zLXNlcmlmOyI+RnJvbTo8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEwcHQ7IGZvbnQtZmFtaWx5OiBUYWhvbWEs
IHNhbnMtc2VyaWY7Ij48YSBocmVmPSJtYWlsdG86cnJhc3p1a0BnbWFpbC5jb20iIHRhcmdldD0i
X2JsYW5rIj5ycmFzenVrQGdtYWlsLmNvbTwvYT4gW21haWx0bzo8YSBocmVmPSJtYWlsdG86cnJh
c3p1a0BnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5ycmFzenVrQGdtYWlsLmNvbTwvYT5dDQo8
Yj5PbiBCZWhhbGYgT2YgPC9iPlJvYmVydCBSYXN6dWs8YnI+DQo8Yj5TZW50OjwvYj4gTW9uZGF5
LCBNYXkgMjMsIDIwMTYgMTA6NDcgQU08L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgY2xhc3M9Img1
Ij48YnI+DQo8Yj5Ubzo8L2I+IFRhbCBNaXpyYWhpPGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJt
YWlsdG86c3ByaW5nQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+c3ByaW5nQGlldGYub3JnPC9h
PjsgNm1hbiBXRzsNCjxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRv
b2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0
b29scy5pZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86bnZvM0BpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPm52bzNAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02
bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5r
Ij4NCmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3Jn
PC9hPjsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5v
cmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5v
cmc8L2E+OyBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKTxicj4NCjxiPlN1YmplY3Q6PC9iPiBS
ZTogW252bzNdIFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVu
dC1yb3V0aW5nLWhlYWRlcjx1PjwvdT48dT48L3U+PC9kaXY+DQo8L2Rpdj4NCjxwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBjbGFzcz0iaDUiPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHU+PC91PiZuYnNwOzx1PjwvdT48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7Ij5IaSBU
YWwsPHU+PC91Pjx1PjwvdT48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsiPjx1
PjwvdT4mbmJzcDs8dT48L3U+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7Ij5J
bmRlZWQgLi4gSSBzYXcgdGhlIGZpZ3VyZXMsIGJ1dCBmaWd1cmVzIGFyZSBub24gbm9ybWF0aXZl
IGluIGFueSBkcmFmdC9yZmMgdW5sZXNzIHRleHQgYmVsb3cgc3BlY2lmaWNhbGx5IHNwZWxscyBp
dCBvdXQuJm5ic3A7PHU+PC91Pjx1PjwvdT48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1z
ZXJpZjsiPjx1PjwvdT4mbmJzcDs8dT48L3U+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMt
c2VyaWY7Ij5Gb3IgZXhhbXBsZSBmcm9tIHZ4bGFuLWdwZTombmJzcDs8dT48L3U+PHU+PC91Pjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyI+PHU+PC91PiZuYnNwOzx1PjwvdT48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsiPiZxdW90OzxzcGFuIHN0eWxlPSJj
b2xvcjpibGFjayI+V2hlbiB0aGUgb3V0ZXIgSVAgaGVhZGVyIGlzIElQdjQsIFZURVBzIE1VU1Qg
c2V0IHRoZSBERiBiaXQuJnF1b3Q7PC9zcGFuPjx1PjwvdT48dT48L3U+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTogQXJpYWwsIHNhbnMtc2VyaWY7Ij48dT48L3U+Jm5ic3A7PHU+PC91Pjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6IEFyaWFsLCBzYW5zLXNlcmlmOyI+QmVzaWRlcyBpdCBpcyBwcmV0dHkgY2hhbGxlbmdpbmcg
dG8gYWRkIGFuaW1hdGlvbiB0byB0aGUgY3VycmVudCBkcmFmdCBmb3JtYXRzIHRvIGlsbHVzdHJh
dGUgYWxsIHBvc3NpYmx5IGFsbG93ZWQgZmllbGQgdmFsdWVzL2NvbWJpbmF0aW9ucyBpbiBhbnkg
ZmlndXJlIDopICZuYnNwO0ZpZ3VyZXMganVzdCBpbGx1c3RyYXRlIG9uZSB1c2UNCiBleGFtcGxl
LiZuYnNwOzx1PjwvdT48dT48L3U+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7
Ij48dT48L3U+Jm5ic3A7PHU+PC91Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlm
OyI+VG8gbWUgdGhlIGN1cnJlbnQgc3BlY3MgcGVybWl0IGFueSB2YWx1ZSBvZiBJUHY2IE54dEhk
ciBmaWVsZCBhcyBwZXJtaXR0ZWQgaW4gYm90aCBlbmNhcHN1bGF0aW9ucy48dT48L3U+PHU+PC91
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyI+PHU+PC91PiZuYnNwOzx1Pjwv
dT48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsiPkJlc3QsPHU+PC91Pjx1Pjwv
dT48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsiPlJvYmVydC48dT48L3U+PHU+
PC91Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlmOyI+PHU+PC91PiZuYnNwOzx1
PjwvdT48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48dT48L3U+Jm5ic3A7PHU+PC91PjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBNb24sIE1heSAyMywgMjAxNiBhdCA5OjM1IEFNLCBUYWwgTWl6cmFoaSAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGFsbWlAbWFydmVs
bC5jb208L2E+Jmd0OyB3cm90ZTo8dT48L3U+PHU+PC91PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1p
bHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+SGkgUm9i
ZXJ0LDwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlm
OyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsiPiZuYnNwOzwvc3Bhbj48dT48L3U+PHU+PC91Pjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDExcHQ7IGZv
bnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsi
PiZuYnNwOzwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNl
cmlmOyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsiPiZndDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiBy
Z2IoMzEsIDczLCAxMjUpOyI+V2hlcmUgc2F5IGluIGRyYWZ0IGRyYWZ0LXF1aW5uLXZ4bGFuLWdw
ZSBkbyB5b3UNCiBzZWUgc3VjaCBzdGF0ZW1lbnQgdGhhdCB3b3VsZCBpbXBseSA8L3NwYW4+PHU+
PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigz
MSwgNzMsIDEyNSk7Ij4mZ3Q7IHRoYXQgdjYgTnh0SGRyIG11c3QgYmUgb25seSBlcXVhbCB0byAx
NyAoVURQKSBhbmQgbm90IGJlIGEgcG9pbnRlciB0byBhbnkgb3RoZXIgdHlwZQ0KPC9zcGFuPjx1
PjwvdT48dT48L3U+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2Io
MzEsIDczLCAxMjUpOyI+Jmd0OyBvZiBleHRlbnNpb24gaGVhZGVyIGZ1cnRoZXIgZm9sbG93ZWQg
YnkgVURQID88L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1z
ZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij4mbmJzcDs8L3NwYW4+PHU+PC91Pjx1Pjwv
dT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0
OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEy
NSk7Ij4mbmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu
cy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij5UaGUgZm9sbG93aW5nIHRleHQgaXMg
ZnJvbSBGaWd1cmUgNCBpbiBkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlOjwvc3Bhbj48dT48L3U+
PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBjb2xvcjogcmdiKDMxLCA3
MywgMTI1KTsiPiZuYnNwOzwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMxZjQ5N2QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBPdXRlciBJUHY2IEhlYWRlcjo8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMWY0OTdkIj4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzs8L3NwYW4+PHU+PC91Pjx1Pjwv
dT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjojMWY0OTdkIj4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfFZlcnNpb258IFRyYWZmaWMgQ2xhc3MgfCZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBG
bG93IExhYmVsJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHw8
L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjojMWY0OTdkIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0Mzst
JiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0MzstJiM0
MzstJiM0MzstJiM0Mzs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3Vy
aWVyIE5ldyZxdW90Oztjb2xvcjojMWY0OTdkIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgfCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBQYXls
b2FkIExlbmd0aCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8IE54
dEhkcj0xNyhVRFApfCZuYnNwOyZuYnNwOyBIb3AgTGltaXQmbmJzcDsmbmJzcDsgfDwvc3Bhbj48
dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOiMx
ZjQ5N2QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmIzQzOy0mIzQzOy0mIzQzOy0m
IzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQz
Oy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0m
IzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQzOy0mIzQz
Oy0mIzQzOzwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOiMxZjQ5N2QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB8Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO3w8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250LWZh
bWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij4mbmJz
cDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsg
Y29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij4mbmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250
LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij5U
aGVyZSBpcyBhIHNpbWlsYXIgZmlndXJlIGluIGRyYWZ0LWlldGYtbnZvMy1nZW5ldmUuPC9zcGFu
Pjx1PjwvdT48dT48L3U+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiBy
Z2IoMzEsIDczLCAxMjUpOyI+Jm5ic3A7PC9zcGFuPjx1PjwvdT48dT48L3U+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6
IENhbGlicmksIHNhbnMtc2VyaWY7IGNvbG9yOiByZ2IoMzEsIDczLCAxMjUpOyI+QmVzdCByZWdh
cmRzLDwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlm
OyBjb2xvcjogcmdiKDMxLCA3MywgMTI1KTsiPlRhbC48L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBmb250
LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgY29sb3I6IHJnYigzMSwgNzMsIDEyNSk7Ij4m
bmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0K
PGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI2I1YzRkZiAx
LjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEwcHQ7IGZvbnQtZmFtaWx5OiBUYWhvbWEsIHNhbnMt
c2VyaWY7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTBwdDsgZm9u
dC1mYW1pbHk6IFRhaG9tYSwgc2Fucy1zZXJpZjsiPiBudm8zIFttYWlsdG86PGEgaHJlZj0ibWFp
bHRvOm52bzMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzMtYm91bmNlc0Bp
ZXRmLm9yZzwvYT5dDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPlJvYmVydCBSYXN6dWs8YnI+DQo8Yj5T
ZW50OjwvYj4gTW9uZGF5LCBNYXkgMjMsIDIwMTYgMTA6MjkgQU08YnI+DQo8Yj5Ubzo8L2I+IFRh
bCBNaXpyYWhpPGJyPg0KPGI+Q2M6PC9iPiA8YSBocmVmPSJtYWlsdG86c3ByaW5nQGlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayI+c3ByaW5nQGlldGYub3JnPC9hPjsgNm1hbiBXRzsNCjxhIGhyZWY9
Im1haWx0bzpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3BlQHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9
Il9ibGFuayI+ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdwZUB0b29scy5pZXRmLm9yZzwvYT47DQo8
YSBocmVmPSJtYWlsdG86bnZvM0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzNAaWV0Zi5v
cmc8L2E+OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1o
ZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCmRyYWZ0LWlldGYtNm1hbi1z
ZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRv
OmRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4N
CmRyYWZ0LWlldGYtbnZvMy1nZW5ldmVAdG9vbHMuaWV0Zi5vcmc8L2E+OyBTdGVmYW5vIFByZXZp
ZGkgKHNwcmV2aWRpKTwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbbnZvM10gW3Nwcmlu
Z10gTDQgQ2hlY2tzdW0gYW5kIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVy
PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PHU+PC91Pjx1PjwvdT48L3A+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTogQXJpYWwsIHNhbnMtc2VyaWY7Ij5IaSBUYWwsPC9zcGFuPjx1PjwvdT48dT48L3U+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiBBcmlhbCwgc2Fucy1zZXJpZjsiPiZuYnNwOzwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTogQXJpYWwsIHNhbnMtc2VyaWY7Ij4mZ3Q7Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6IDkuNXB0OyBmb250LWZhbWlseTogQXJpYWwsIHNhbnMtc2VyaWY7Ij5kcmFmdHMg
c2VlbSB0byBpbXBseTwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNhbnMt
c2VyaWY7Ij4mbmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5z
LXNlcmlmOyI+V2hlcmUgc2F5IGluIGRyYWZ0Jm5ic3A7ZHJhZnQtcXVpbm4tdnhsYW4tZ3BlIGRv
IHlvdSBzZWUgc3VjaCBzdGF0ZW1lbnQgdGhhdCB3b3VsZCBpbXBseSB0aGF0IHY2IE54dEhkciBt
dXN0IGJlIG9ubHkgZXF1YWwgdG8gMTcgKFVEUCkgYW5kIG5vdCBiZSBhIHBvaW50ZXIgdG8gYW55
IG90aGVyIHR5cGUgb2YgZXh0ZW5zaW9uIGhlYWRlciBmdXJ0aGVyDQogZm9sbG93ZWQgYnkgVURQ
ID8mbmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6IEFyaWFsLCBzYW5zLXNlcmlm
OyI+Jm5ic3A7PC9zcGFuPjx1PjwvdT48dT48L3U+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCwgc2Fucy1zZXJp
ZjsiPlRoeCw8YnI+DQpSLjwvc3Bhbj48dT48L3U+PHU+PC91PjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTogQXJpYWwsIHNh
bnMtc2VyaWY7Ij4mbmJzcDs8L3NwYW4+PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzx1PjwvdT48dT48L3U+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIE1vbiwgTWF5IDIzLCAyMDE2IGF0IDc6NTAg
QU0sIFRhbCBNaXpyYWhpICZsdDs8YSBocmVmPSJtYWlsdG86dGFsbWlAbWFydmVsbC5jb20iIHRh
cmdldD0iX2JsYW5rIj50YWxtaUBtYXJ2ZWxsLmNvbTwvYT4mZ3Q7IHdyb3RlOjx1PjwvdT48dT48
L3U+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RGVhciBBdXRob3JzIG9mIFZYTEFOLUdQRSAv
IEdlbmV2ZSw8YnI+DQo8YnI+DQpJIGFtIHJlaXRlcmF0aW5nIG9uIHRoaXMgcXVlc3Rpb24sIGFz
IEkgaGF2ZW4ndCBzZWVuIGEgcmVzcG9uc2UgeWV0Ojxicj4NCjxicj4NCkhhdmUgeW91IGNvbnNp
ZGVyZWQgdGhlIHVzZSBvZiBTZWdtZW50IFJvdXRpbmcgd2l0aCBWWExBTi1HUEUgLyBHZW5ldmU/
IFRoZSBjdXJyZW50IFZYTEFOLUdQRSAvIEdlbmV2ZSBkcmFmdHMgc2VlbSB0byBpbXBseSB0aGF0
IElQdjYgZXh0ZW5zaW9uIGhlYWRlcnMgYXJlIGN1cnJlbnRseSBub3Qgc3VwcG9ydGVkLjxicj4N
Cjxicj4NClRoYW5rcyw8YnI+DQpUYWwuPHU+PC91Pjx1PjwvdT48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxicj4NCiZndDstLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLTxicj4NCiZndDtGcm9tOiBudm8zIFttYWlsdG86PGEgaHJlZj0ibWFpbHRv
Om52bzMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm52bzMtYm91bmNlc0BpZXRm
Lm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBUYWwgTWl6cmFoaTxicj4NCiZndDtTZW50OiBUdWVzZGF5
LCBNYXkgMTcsIDIwMTYgMTI6MDkgUE08YnI+DQomZ3Q7VG86IFN0ZWZhbm8gUHJldmlkaSAoc3By
ZXZpZGkpOyBUb20gSGVyYmVydDsgZHJhZnQtaWV0Zi1udm8zLTxicj4NCiZndDs8YSBocmVmPSJt
YWlsdG86Z2VuZXZlQHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+Z2VuZXZlQHRvb2xz
LmlldGYub3JnPC9hPjsNCjxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLW52bzMtdnhsYW4tZ3Bl
QHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZHJhZnQtaWV0Zi1udm8zLXZ4bGFuLWdw
ZUB0b29scy5pZXRmLm9yZzwvYT48YnI+DQomZ3Q7Q2M6IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdA
aWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJt
YWlsdG86bnZvM0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0KbnZvM0BpZXRmLm9yZzwvYT47
IDZtYW4gV0c7IGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LTxicj4NCiZndDs8YSBocmVmPSJtYWls
dG86cm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5yb3V0aW5n
LWhlYWRlckB0b29scy5pZXRmLm9yZzwvYT48YnI+DQomZ3Q7U3ViamVjdDogUmU6IFtudm8zXSBb
c3ByaW5nXSBMNCBDaGVja3N1bSBhbmQgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtPGJyPg0KJmd0
O3JvdXRpbmctaGVhZGVyPGJyPg0KJmd0Ozxicj4NCiZndDtTdGVmYW5vLDxicj4NCiZndDs8YnI+
DQomZ3Q7SWYgSSB1bmRlcnN0YW5kIHlvdXIgcG9pbnQgY29ycmVjdGx5Ojxicj4NCiZndDtJUHY2
IHNlZ21lbnQgcm91dGluZyBkb2VzIG5vdCB3b3JrIHdpdGggVlhMQU4gLyBWWExBTi1HUEUgLyBH
ZW5ldmUsIHNpbmNlPGJyPg0KJmd0O3RoZXNlIGVuY2Fwc3VsYXRpb25zIGRvIG5vdCBjdXJyZW50
bHkgYWxsb3cgdGhlIHVzZSBvZiBJUHY2IGV4dGVuc2lvbjxicj4NCiZndDtoZWFkZXJzLjxicj4N
CiZndDs8YnI+DQomZ3Q7SSB3b25kZXIgaWYgdGhlIGF1dGhvcnMgb2YgVlhMQU4tR1BFIGFuZCBH
ZW5ldmUgaGF2ZSBjb25zaWRlcmVkIHRoZSB1c2Ugb2Y8YnI+DQomZ3Q7c2VnbWVudCByb3V0aW5n
Ljxicj4NCiZndDs8YnI+DQomZ3Q7VGhhbmtzLDxicj4NCiZndDtUYWwuPGJyPg0KJmd0Ozxicj4N
CiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyZndDstLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxi
cj4NCiZndDsmZ3Q7RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBo
cmVmPSJtYWlsdG86c3ByZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlA
Y2lzY28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0O1NlbnQ6IFR1ZXNkYXksIE1heSAxNywgMjAxNiAx
MDo0MSBBTTxicj4NCiZndDsmZ3Q7VG86IFRvbSBIZXJiZXJ0PGJyPg0KJmd0OyZndDtDYzogVGFs
IE1penJhaGk7IDZtYW4gV0c7IDxhIGhyZWY9Im1haWx0bzpzcHJpbmdAaWV0Zi5vcmciIHRhcmdl
dD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+Ozxicj4NCiZndDsmZ3Q7ZHJhZnQtaWV0Zi02
bWFuLXNlZ21lbnQtcm91dGluZy0gPGEgaHJlZj0ibWFpbHRvOmhlYWRlckB0b29scy5pZXRmLm9y
ZyIgdGFyZ2V0PSJfYmxhbmsiPg0KaGVhZGVyQHRvb2xzLmlldGYub3JnPC9hPjxicj4NCiZndDsm
Z3Q7U3ViamVjdDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZCBkcmFmdC1pZXRmLTZtYW4t
c2VnbWVudC1yb3V0aW5nLTxicj4NCiZndDsmZ3Q7aGVhZGVyPGJyPg0KJmd0OyZndDs8YnI+DQom
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDc6MTAgUE0sIFRv
bSBIZXJiZXJ0ICZsdDs8YSBocmVmPSJtYWlsdG86dG9tQGhlcmJlcnRsYW5kLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPnRvbUBoZXJiZXJ0bGFuZC5jb208L2E+Jmd0Ozxicj4NCiZndDt3cm90ZTo8YnI+
DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgT24gTW9uLCBNYXkgMTYsIDIwMTYgYXQg
NDozMiBBTSwgVGFsIE1penJhaGkgJmx0OzxhIGhyZWY9Im1haWx0bzp0YWxtaUBtYXJ2ZWxsLmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPnRhbG1pQG1hcnZlbGwuY29tPC9hPiZndDs8YnI+DQomZ3Q7Jmd0
O3dyb3RlOjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGl04oCZcyBhbGwgYWJvdXQgSVAsIG5v
dCBsYXllci0yLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsgcy48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBSaWdo
dC4gSG93ZXZlciwgaXQgYXBwZWFycyB0aGF0IGF0IGxlYXN0IGluIHNvbWUgY2FzZXMgYSBWWExB
TiBWVEVQPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyB3aWxsPGJyPg0KJmd0OyZndDt1c2UgU1IuIEl0
IGNlcnRhaW5seSBtYXkgYmUgdGhlIGNhc2UgaW4gU0ZDIHVzZSBjYXNlcyAoc2VlIFNlY3Rpb24g
Mi4zPGJyPg0KJmd0OyZndDtpbiBkcmFmdC0gaWV0Zi1zcHJpbmctaXB2Ni11c2UtY2FzZXMpLjxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsg
ZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXIgbWVudGlvbnMgdGhhdCB0aGUg
cGFja2V0IGlzPGJyPg0KJmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRlZDxicj4NCiZndDsmZ3Q7PGJy
Pg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0O2ludG8gYW4gb3V0ZXIgaXB2NiBoZWFkZXIgd2hpY2gg
bWFrZXMgaXQgYSBsYXllci0zIGVuY2FwLjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsgLCBidXQgSSBkb24ndCB0aGluayBpdCBpcyBleHBsaWNpdCBhcyB0byBl
eGFjdCBlbmNhcHN1bGF0aW9uIGZvcm1hdDxicj4NCiZndDsmZ3Q7Jmd0OyAoSSBzdXBwb3NlIHNp
bXBsZSBpcDZpcDYgaXMgaW1wbGllZCkuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7c2VlIHNlY3Rpb24gMi4yPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7Jmd0OyBCdXQsIGl0PGJyPg0KJmd0OyZndDsmZ3Q7IHNlZW1zIGxpa2UgYW55IG9m
IHNldmVyYWwgZW5jYXBzdWxhdGlvbiB0ZWNobmlxdWVzIGNvdWxkIHdvcmsgKFZYTEFOLDxicj4N
CiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0O0kgaGF2ZSBzb21lIHByb2JsZW1z
IHRvIHVuZGVyc3RhbmQgd2hlcmUgdG8gZml0IGFuIGV4dGVuc2lvbiBoZWFkZXI8YnI+DQomZ3Q7
Jmd0O2ludG8gYSB2eGxhbiBlbmNhcOKApjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsgR1JFL0lQLCBFU1AvSVAsIEdVRSwgZm9vIG92ZXIgVURQLCBldGMuKSBh
bmQgaWYgYSBkZXZpY2UgdGhhdCB3YW50czxicj4NCiZndDsmZ3Q7Jmd0OyB0byBkbyBTUiBpcyBh
bHJlYWR5IGRvaW5nIHR1bm5lbGluZyBpdCBzZWVtcyByZWFzb25hYmxlIHRvIG1lIHRvIG9ubHk8
YnI+DQomZ3Q7Jmd0OyZndDsgaGF2ZSBvbmUgbGF5ZXIgb2YgZW5jYXBzdWxhdGlvbi4gTWF5YmUg
dGhpcyBzaG91bGQgYmUgY2xhcmlmaWVkIGluPGJyPg0KJmd0OyZndDsmZ3Q7IHRoZSBkcmFmdD88
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDt0aGUgZHJhZnQgaXMgYWJv
dXQgSVB2NiBleHRlbnNpb24gaGVhZGVyIGFuZCBtb3JlIHByZWNpc2VseSBhIG5ldyB0eXBlPGJy
Pg0KJmd0OyZndDtvZiB0aGUgcm91dGluZyBleHRlbnNpb24gaGVhZGVyIGRlZmluZWQgaW4gcmZj
MjQ2MC4gVGhhdOKAmXMgdGhlIGNvbnRleHQuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7cy48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBUb208YnI+
DQomZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgRnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkg
W21haWx0bzo8YSBocmVmPSJtYWlsdG86c3ByZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFu
ayI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTZW50
OiBNb25kYXksIE1heSAxNiwgMjAxNiAyOjI0IFBNPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsg
VG86IFRhbCBNaXpyYWhpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6IE9sZSBUcsO4YW47
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtNm1h
bi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+
DQpkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlckB0b29scy5pZXRmLm9yZzwv
YT47PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFpbHRvOnNwcmluZ0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnNwcmluZ0BpZXRmLm9yZzwvYT47IDZtYW4gV0c8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTdWJqZWN0OiBSZTogW3NwcmluZ10gTDQgQ2hlY2tzdW0gYW5k
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgZHJhZnQtaWV0Zi02bWFuLXNlZ21lbnQtcm91dGlu
Zy0gaGVhZGVyPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDE6
MTkgUE0sIFRhbCBNaXpyYWhpICZsdDs8YSBocmVmPSJtYWlsdG86dGFsbWlAbWFydmVsbC5jb20i
IHRhcmdldD0iX2JsYW5rIj50YWxtaUBtYXJ2ZWxsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIaSBT
dGVmYW5vLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyBUaGFua3MgYWdhaW4gZm9yIHRoZSBwcm9tcHQgcmVzcG9uc2UuPGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAy
LiB0aGUgU1JIIGlzIG9yaWdpbmF0ZWQgYnkgdGhlIGluZ3Jlc3Mgbm9kZSBvZiB0aGUgU1IgZG9t
YWluLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhpcyBpcyBkb25lIGJ5IGVu
Y2Fwc3VsYXRpbmcgdGhlIHBhY2tldCBpbnRvIGEgb3V0ZXI8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7IChhZGRpdGlvbmFsKSBpcHY2IGhlYWRlciBmb2xsb3dlZCBieSBhbiBTUkgu
IFRoaXMgaXMgTDM8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRp
b24gYW5kIG5vIEw0IGNoZWNrc3VtIGlzIGludm9sdmVkLiBXaGVuIHRoZSZuYnNwOyBwYWNrZXQ8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGxlYXZlcyB0aGUgU1IgdHVubmVsIHRo
ZSBvdXRlciBlbmNhcHN1bGF0aW9uJm5ic3A7IChpbmNsdWRpbmcgdGhlIFNSSCk8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGlzIHJlbW92ZWQgYW5kIHRoZSBwYWNrZXQgY29udGlu
dWVzJm5ic3A7IGl0cyBqb3VybmV5IGxpa2Ugbm90aGluZzxicj4NCiZndDtoYXBwZW5lZC48YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsg
U28gVlhMQU4gaXMgb2ZmIHRoZSB0YWJsZT88YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgaXTigJlzIGFs
bCBhYm91dCBJUCwgbm90IGxheWVyLTIuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBzLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgSXQgd291bGQg
YmUgd29ydGh3aGlsZSB0byBjbGFyaWZ5IHRoaXMgaW4gdGhlIGRyYWZ0LiBJZiB5b3UgaGF2ZSBh
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHNwZWNpZmljPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsgZW5jYXBzdWxhdGlvbiBpbiBtaW5kLCBpdCB3b3VsZCBiZSBncmVhdCBpZiB0aGUg
ZHJhZnQgd291bGQgc3BlY2lmeSBpdC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhhbmtzLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBUYWwuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgRnJv
bTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86c3By
ZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lzY28uY29tPC9hPl08
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFNlbnQ6IE1vbmRheSwgTWF5IDE2LCAy
MDE2IDI6MTMgUE08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRvOiBUYWwgTWl6
cmFoaTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgQ2M6IE9sZSBUcsO4YW47PGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0
Zi02bWFuLXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2Js
YW5rIj4NCmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYu
b3JnPC9hPjs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDxhIGhyZWY9Im1haWx0
bzpzcHJpbmdAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5zcHJpbmdAaWV0Zi5vcmc8L2E+OyA2
bWFuIFdHPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTdWJqZWN0OiBSZTogW3Nw
cmluZ10gTDQgQ2hlY2tzdW0gYW5kPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBk
cmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXI8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBIaSw8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyBPbiBNYXkgMTYsIDIwMTYsIGF0IDExOjA0IEFNLCBUYWwgTWl6cmFoaSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnRhbG1pQG1hcnZlbGwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGFsbWlAbWFy
dmVsbC5jb208L2E+Jmd0Ozxicj4NCiZndDsmZ3Q7d3JvdGU6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBI
aSBTdGVmYW5vLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGhhbmtzIGZvciB0aGUgcmVzcG9uc2VzLjxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGV4YWN0bHkuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
IE1vcmVvdmVyLCBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLWhlYWRlciBhc3N1bWVz
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IGVuY2Fwc3VsYXRpb24g
c28gY2xlYXJseSB0aGVyZeKAmXMgbm8gTDQgaW52b2x2ZWQgaGVyZS48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsgcy48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFR3byBxdWVzdGlvbnM6PGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgMS4gV2hhdCBpZiB0aGUgZW5jYXBzdWxhdGlv
biBpcyBWWExBTj8gTDQgd291bGQgc3RpbGwgYmU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyBpbnZvbHZlZCw8YnI+DQomZ3Q7Jmd0O3JpZ2h0Pzxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTZWUgYmVsb3cuPGJyPg0KJmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyAyLiBXaGVuIHlvdSBzYXkgJ2Fzc3VtZXMg
ZW5jYXBzdWxhdGlvbicsIGRvZXMgaXQgbWVhbiB0aGF0IGE8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyBob3N0IGNhbm5vdDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsgc2VuZCBhbiBJUHY2IHBhY2tldCB3aXRoIGFuIFNSSD8gVGhlIGN1cnJlbnQgZHJhZnQg
c2F5czo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEEgU291cmNlIFNSIE5vZGUgY2FuIGJlIGFueSBub2Rl
IG9yaWdpbmF0aW5nIGFuIElQdjYgcGFja2V0IHdpdGg8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyBpdHM8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBJ
UHY2IGFuZCBTZWdtZW50IFJvdXRpbmcgSGVhZGVycy4mbmJzcDsgVGhpcyBpbmNsdWRlIGVpdGhl
cjo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyBBIGhvc3Qgb3JpZ2luYXRpbmcgYW4g
SVB2NiBwYWNrZXQuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgQW4gU1IgZG9tYWlu
IGluZ3Jlc3Mgcm91dGVyIGVuY2Fwc3VsYXRpbmcgYSByZWNlaXZlZCBJUHY2IHBhY2tldDxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyBpbnRvIGFuIG91
dGVyIElQdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyBXaWxsIGFwcHJlY2lhdGUgaWYgeW91IGNhbiBjbGFyaWZ5IHRoYXQu
PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IG9rLCB0d28gY2Fz
ZXM6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsgMS4gdGhlIFNSSCBpcyBpbnNlcnRlZCBhdCB0aGUgc291cmNlLjxicj4N
CiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgdGhlIHNvdXJjZSBvcmlnaW5hdGVzIHRoZSBw
YWNrZXQsIHRoZSBpcHY2IGhlYWRlciBhbmQmbmJzcDsgdGhlIFNSSC48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRoZSBzb3VyY2UgY29tcHV0ZXMgTDQgY2hlY2tzdW0gdGFraW5n
IGludG8mbmJzcDsgYWNjb3VudCB0aGUgd2hvbGU8YnI+DQomZ3Q7Jmd0O0lQdjYmIzQzO1NSSC48
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEhlcmUsIHRoZXJlc+KAmSBub3RoaW5n
IG5ldyZuYnNwOyBjb21wYXJlZCB0byByZmMyNDYwLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IDIuIHRoZSBTUkggaXMg
b3JpZ2luYXRlZCBieSB0aGUgaW5ncmVzcyBub2RlIG9mIHRoZSBTUiBkb21haW4uPGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBUaGlzIGlzIGRvbmUgYnkgZW5jYXBzdWxhdGluZyB0
aGUgcGFja2V0IGludG8gYSBvdXRlcjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsg
KGFkZGl0aW9uYWwpIGlwdjYgaGVhZGVyIGZvbGxvd2VkIGJ5IGFuIFNSSC4gVGhpcyBpcyBMMzxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgZW5jYXBzdWxhdGlvbiBhbmQgbm8gTDQg
Y2hlY2tzdW0gaXMgaW52b2x2ZWQuIFdoZW4gdGhlJm5ic3A7IHBhY2tldDxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgbGVhdmVzIHRoZSBTUiB0dW5uZWwgdGhlIG91dGVyIGVuY2Fw
c3VsYXRpb24mbmJzcDsgKGluY2x1ZGluZyB0aGUgU1JIKTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsgaXMgcmVtb3ZlZCBhbmQgdGhlIHBhY2tldCBjb250aW51ZXMmbmJzcDsgaXRz
IGpvdXJuZXkgbGlrZSBub3RoaW5nPGJyPg0KJmd0O2hhcHBlbmVkLjxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHMuPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IFRoYW5rcyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyBUYWwuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsg
RnJvbTogU3RlZmFubyBQcmV2aWRpIChzcHJldmlkaSkgW21haWx0bzo8YSBocmVmPSJtYWlsdG86
c3ByZXZpZGlAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+c3ByZXZpZGlAY2lzY28uY29tPC9h
Pl08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU2VudDogTW9uZGF5
LCBNYXkgMTYsIDIwMTYgMTE6NTkgQU08YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsgVG86IE9sZSBUcsO4YW47IFRhbCBNaXpyYWhpPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IENjOiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFu
LXNlZ21lbnQtcm91dGluZy1oZWFkZXJAdG9vbHMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4N
CmRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyQHRvb2xzLmlldGYub3JnPC9h
Pjs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgPGEgaHJlZj0ibWFp
bHRvOnNwcmluZ0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnNwcmluZ0BpZXRmLm9yZzwvYT47
IDZtYW4gV0c8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU3ViamVj
dDogUmU6IFtzcHJpbmddIEw0IENoZWNrc3VtIGFuZDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyBkcmFmdC1pZXRmLTZtYW4tc2VnbWVudC1yb3V0aW5nLSBoZWFkZXI8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7IE9uIE1heSAxNSwgMjAxNiwgYXQgODowNiBQTSwgPGEgaHJlZj0ibWFp
bHRvOm90cm9hbkBlbXBsb3llZXMub3JnIiB0YXJnZXQ9Il9ibGFuayI+DQpvdHJvYW5AZW1wbG95
ZWVzLm9yZzwvYT4gd3JvdGU6PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGFs
LDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBbQXBvbG9naWVzIGlmIHRo
aXMgaXNzdWUgaGFzIGJlZW4gZGlzY3Vzc2VkIGJlZm9yZS5dPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBBY2NvcmRpbmcgdG8gZHJhZnQtaWV0Zi02bWFuLXNlZ21l
bnQtcm91dGluZy1oZWFkZXIsIGFuIOKAmFNSPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgU2VnbWVudDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyBFbmRwb2ludCBOb2Rl4oCZIHVwZGF0ZXMgdGhlIERlc3RpbmF0aW9uIElQ
IGFkZHJlc3MuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsgVGhlcmVmb3JlLCBpdCBtdXN0IGFsc28gdXBkYXRlIHRoZSBMYXllciA0IENoZWNrc3VtLCBy
aWdodD88YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IEkgd29uZGVy
IGlmIHRoZXJlIGlzIGFuIHVwcGVyIGJvdW5kIG9uIHRoZSBzaXplIG9mIHRoZSBTUkguPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgT3RoZXJ3aXNlLCB0
aGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgTDQgQ2hlY2tzdW0g
bWF5IGJlIGxvY2F0ZWQgaW4gYSBwcmV0dHkgZGVlcCBsb2NhdGlvbi48YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBTcGVha2luZyBmcm9tIGEgY2hpcCB2
ZW5kb3LigJlzIHBlcnNwZWN0aXZlIHRoaXMgbWF5IGJlIGEgcHJvYmxlbS48YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBGcm9tIFJGQzI0NjAsIFJIMDo8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7
Jmd0OyZndDsmbmJzcDsgJm5ic3A7byZuYnNwOyBJZiB0aGUgSVB2NiBwYWNrZXQgY29udGFpbnMg
YSBSb3V0aW5nIGhlYWRlciwgdGhlIERlc3RpbmF0aW9uPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7IEFkZHJlc3MgdXNlZCBp
biB0aGUgcHNldWRvLWhlYWRlciBpcyB0aGF0IG9mIHRoZSBmaW5hbDxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBkZXN0aW5h
dGlvbi4mbmJzcDsgQXQgdGhlIG9yaWdpbmF0aW5nIG5vZGUsIHRoYXQgYWRkcmVzcyB3aWxsIGJl
IGluPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZuYnNwOyAm
bmJzcDsgJm5ic3A7IHRoZSBsYXN0IGVsZW1lbnQgb2YgdGhlIFJvdXRpbmcgaGVhZGVyOyBhdCB0
aGUgcmVjaXBpZW50KHMpLDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyB0aGF0IGFkZHJlc3Mgd2lsbCBiZSBpbiB0aGUgRGVz
dGluYXRpb24gQWRkcmVzcyBmaWVsZCBvZiB0aGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgSVB2NiBoZWFkZXIuPGJyPg0K
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgSSB3b3VsZCBleHBlY3QgU1Igd291bGQgd29y
ayB0aGUgc2FtZS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgZXhhY3RseS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsgTW9yZW92ZXIsIGRyYWZ0LWlldGYtNm1hbi1zZWdtZW50LXJvdXRpbmctaGVhZGVyIGFzc3Vt
ZXM8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgZW5jYXBzdWxhdGlv
biBzbyBjbGVhcmx5IHRoZXJl4oCZcyBubyBMNCBpbnZvbHZlZCBoZXJlLjxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyBzLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IENoZWVycyw8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IE9sZTxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBJRVRGIElQdjYgd29y
a2luZyBncm91cCBtYWlsaW5nIGxpc3QgPGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj4NCmlwdjZAaWV0Zi5vcmc8L2E+IEFkbWluaXN0cmF0aXZlPGJyPg0KJmd0
OyZndDsmZ3Q7Jmd0OyBSZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9pcHY2IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2lwdjY8L2E+PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyAtLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLTxicj4NCiZndDs8YnI+DQomZ3Q7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX188YnI+DQomZ3Q7bnZvMyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7PGEgaHJl
Zj0ibWFpbHRvOm52bzNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5udm8zQGlldGYub3JnPC9h
Pjxicj4NCiZndDs8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L252bzMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL252bzM8L2E+PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxicj4NCnNwcmluZyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJt
YWlsdG86c3ByaW5nQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+c3ByaW5nQGlldGYub3JnPC9h
Pjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3By
aW5nIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9zcHJpbmc8L2E+PHU+PC91Pjx1PjwvdT48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8dT48L3U+PHU+PC91PjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHU+PC91PiZuYnNwOzx1PjwvdT48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvc3Bhbj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_36D9FCF0382C466985A5C782636A85BBvmwarecom_--


From nobody Mon May 23 13:33: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 081BA12DB66 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 13:32:59 -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, FREEMAIL_FROM=0.001, 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 4CWMR3lmY8T6 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 13:32:57 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::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 8349312DB77 for <ipv6@ietf.org>; Mon, 23 May 2016 13:32:57 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id y69so68016904pfb.1 for <ipv6@ietf.org>; Mon, 23 May 2016 13:32:57 -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=NsY+PiJ5kiSdpKAyAEUscTczeqlqe4JDACSNYa+Zf08=; b=xXmngPFNKmVXiTTwpoVQy5S3l9+ewFV4URMI/QihFfz/ehOiaTJaDQ6SBYp5LykWcs BzXgwPnDHu1NCDha/igcyF/1ZUp/l3875jmPWjgtMR7gBl04eddy9DBxTNyvEsmf9ywV m6aC51GaASVyHlWAwbxvyb7fOx+PGJBn4n/D/KJCK/Kgd1t1yo2IZmobQ8JcBSrfSAZP eo6hMWts1i1ichCeEUyKBXn91l+q9vMDOHKExW6NT0McEhosafjluHGUxEGHDFyrxkfR SSOhLx5EkpI980xavLscEyggigl60ez9KlilOZdaKxyP2BNdri2IHjaWirhCkyWaoqUL L3Nw==
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=NsY+PiJ5kiSdpKAyAEUscTczeqlqe4JDACSNYa+Zf08=; b=Qr78+8j/tAKm+SaTv/XYzdzgnFE/WuTNK9qevYy3bI6CpFGfR66QMERzsyn1ti4gQq XcPP7HKYyUptm0fNkOWTiJHAxlxph2kZi3qZ5ypWQbaKva+pETRYn6Dsy+rVoFLEO25B uuYNzLdzbPtiHzbYYCAWqEIvrxZFJ+cy89LRPkQlHVL4F7pVlPjvJB6cGhDVXiNdoUEk eEws/7TWfYlPPFPmvqwffiJhQa2AKoAKGB2DXPweFT2+1AlTfgNNSWD9SFRx1rXmVl5D bCc/rKV99QQK834wXL/Ob0Jewan9DfkZ2qlHbnMHlUyAqX28UbThRFg46VR3IJJAx1gB ZCug==
X-Gm-Message-State: ALyK8tLPNbT8Xh6St4ipMeig9MLXUo19v7DUTVUam+YIQ1l4/XFMICBOnsezmBH0RjEMBA==
X-Received: by 10.98.21.210 with SMTP id 201mr1080509pfv.51.1464035576986; Mon, 23 May 2016 13:32:56 -0700 (PDT)
Received: from ?IPv6:2406:e007:5038:1:78b2:4cf2:d9b2:556a? ([2406:e007:5038:1:78b2:4cf2:d9b2:556a]) by smtp.gmail.com with ESMTPSA id e184sm48685129pfe.14.2016.05.23.13.32.54 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 May 2016 13:32:55 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: 6man <ipv6@ietf.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com>
Date: Tue, 24 May 2016 08:32:56 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <20160523150736.10739.19307.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NbGeazAd99ugzVF6F6GQ7ExKu8w>
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, 23 May 2016 20:32:59 -0000

>    [RFC4941] implies,
>    throughout the specification, that temporary addresses are generated
>    and employed along with temporary addresses.

s/temporary/stable/ in the last line.

Apart from that, I suspect that this draft tries to do too much and will
therefore be controversial.

An alternative is for it to say much less, e.g. only this, replacing
sections 3 through 7 and most of 9.

3. Update to RFC4941

   The temporary addresses specified in [RFC4941] MAY be used alone,
   without configuring any stable addresses. In particular the word
   'additional' is deleted from bullet 2 in Section 3 of RFC 4941.

Regards
   Brian

P.S. My personal experiment in running my laptop for several days
with no stable address has been completely successful. Including the
fact that my prototype of the Anima signaling protocol crashed after
a while, because the address it was relying on went away, which is of
course the expected behaviour.


From nobody Mon May 23 13:55:21 2016
Return-Path: <kreeger@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 66BDF12DBC7; Mon, 23 May 2016 13:55:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 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.426, 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 16OOq_86cGVA; Mon, 23 May 2016 13:55:15 -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 B27BA12DBC4; Mon, 23 May 2016 13:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=57395; q=dns/txt; s=iport; t=1464036914; x=1465246514; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PLenvxdbG4nPwZf8epfCRAqRUNJP8G4ISd07LKf8Lyw=; b=KEJFX+0fB7crAx21kfxZcdPyr1OQpZUg4g4tWA8OJ17wYGFbAp5VW6MP LFD3JBcbKyP21NMvxNAp7mu3F0b78uakve2WMo2jo+oLYrGM+9B6bfejj CW+GyYJ0Rvrp7+VCTTfimvg4vbHs/UUMiVJPHE3hdwEGbCYMfkwRQ3Dwv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AZAgB6bUNX/4QNJK1cgmxLVn0GrgyLb?= =?us-ascii?q?wENgXMEFwEKhSVKAoE2OBQBAQEBAQEBZSeEQgEBAQMBAQEBF1QLBQcEAgEIEQM?= =?us-ascii?q?BAQEBFQsBBgchBgsUCQgCBA4FiBUDDwcBDr88DYQmAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBFwWJcYEDgkOBWUMWCYUbBYgEizOETTMBiHeDL4F5gWmNM4YzgTGHZwE?= =?us-ascii?q?eAQFCg21uiBMBBhkfAX4BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,357,1459814400";  d="scan'208,217";a="110219371"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 May 2016 20:55:12 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u4NKtCs4011481 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 23 May 2016 20:55:12 GMT
Received: from xch-rtp-007.cisco.com (64.101.220.147) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 23 May 2016 16:55:11 -0400
Received: from xch-rtp-007.cisco.com ([64.101.220.147]) by XCH-RTP-007.cisco.com ([64.101.220.147]) with mapi id 15.00.1104.009; Mon, 23 May 2016 16:55:11 -0400
From: "Larry Kreeger (kreeger)" <kreeger@cisco.com>
To: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMWtEanFs1cLO0Wbr2+S/VrgGZ/GZ/OAgAACKYCAAARgAIAAy/oA//+UdAA=
Date: Mon, 23 May 2016 20:55:11 +0000
Message-ID: <D368BC04.19BA29%kreeger@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com> <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com> <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com> <36D9FCF0-382C-4669-85A5-C782636A85BB@vmware.com>
In-Reply-To: <36D9FCF0-382C-4669-85A5-C782636A85BB@vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [171.71.35.113]
Content-Type: multipart/alternative; boundary="_000_D368BC0419BA29kreegerciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yRnnYMMOWLS9InRA34j3-vE1UM8>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" <draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>, "draft-ietf-nvo3-geneve@tools.ietf.org" <draft-ietf-nvo3-geneve@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: Mon, 23 May 2016 20:55:18 -0000

--_000_D368BC0419BA29kreegerciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I agree with Robert and Jesse. - Larry

From: Jesse Gross <jgross@vmware.com<mailto:jgross@vmware.com>>
Date: Monday, May 23, 2016 at 1:19 PM
To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>, Tal Mizrah=
i <talmi@marvell.com<mailto:talmi@marvell.com>>
Cc: "draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@to=
ols.ietf.org>" <draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo=
3-geneve@tools.ietf.org>>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org<mailto=
:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>" <draft-ietf-nvo3-vxlan-gpe@tool=
s.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>>, "spring@ietf.=
org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, 6ma=
n WG <ipv6@ietf.org<mailto:ipv6@ietf.org>>, "nvo3@ietf.org<mailto:nvo3@ietf=
.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>>, "draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org<mailto:draft-ietf-6man-segment-routing-header@too=
ls.ietf.org>" <draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto=
:draft-ietf-6man-segment-routing-header@tools.ietf.org>>, "Stefano Previdi =
(sprevidi)" <sprevidi@cisco.com<mailto:sprevidi@cisco.com>>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>, <jgro=
ss@vmware.com<mailto:jgross@vmware.com>>
Resent-To: Larry Kreeger <kreeger@cisco.com<mailto:kreeger@cisco.com>>, <ur=
i.elzur@intel.com<mailto:uri.elzur@intel.com>>, <draft-ietf-6man-segment-ro=
uting-header@ietf.org<mailto:draft-ietf-6man-segment-routing-header@ietf.or=
g>>
Resent-Date: Monday, May 23, 2016 at 1:20 PM

I agree that I don=92t believe that there is anything in these drafts that =
precludes the use of extension headers or segment routing =96 IP is simply =
the layer underneath that these protocols are building on. The figures are =
definitely just examples =96 they also show outer Ethernet headers, which i=
s not a requirement.

I wouldn=92t want to add text specifically stating that extension headers a=
re permissible. It seems like that could lead to similar questions in the f=
uture where one might wonder if other features of IP are allowed because on=
e is explicitly listed and others are not, etc. In my opinion, the drafts a=
re about as clear as they can be on this point.

Jesse

On 5/23/16, 1:09 AM, "rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf=
 of Robert Raszuk" <rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf o=
f robert@raszuk.net<mailto:robert@raszuk.net>> wrote:

Hi Tal,

> In order to avoid ambiguity, it would be great if the
> authors could explicitly mention that IPv6 extension
> headers are permitted.

Well the drafts are complaint to RFC2119 (normative reference) so unless th=
e text excludes elements with MUST/MUST NOT - everything else defined in th=
e building blocks they (re)use is permitted.

However as you say perhaps for clarity what could be added to those drafts =
is a normative reference to IPv4 and IPv6 base RFCs.

Best,
R.


On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Robert,

That makes sense.
However, in this case the figures may be a bit confusing WRT the possible e=
xistence of extension headers. This confusion is what led to the discussion=
 in this thread about whether segment routing is possible with VXLAN/VXLAN-=
GPE/Geneve encapsulations.

In order to avoid ambiguity, it would be great if the authors could explici=
tly mention that IPv6 extension headers are permitted.

Regards,
Tal.

From:rraszuk@gmail.com<mailto:rraszuk@gmail.com> [mailto:rraszuk@gmail.com<=
mailto:rraszuk@gmail.com>] On Behalf Of Robert Raszuk
Sent: Monday, May 23, 2016 10:47 AM

To: Tal Mizrahi
Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo3@=
ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@tool=
s.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>; d=
raft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.ie=
tf.org>; Stefano Previdi (sprevidi)
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header

Hi Tal,

Indeed .. I saw the figures, but figures are non normative in any draft/rfc=
 unless text below specifically spells it out.

For example from vxlan-gpe:

"When the outer IP header is IPv4, VTEPs MUST set the DF bit."

Besides it is pretty challenging to add animation to the current draft form=
ats to illustrate all possibly allowed field values/combinations in any fig=
ure :)  Figures just illustrate one use example.

To me the current specs permit any value of IPv6 NxtHdr field as permitted =
in both encapsulations.

Best,
Robert.


On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Robert,


>Where say in draft draft-quinn-vxlan-gpe do you see such statement that wo=
uld imply
> that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer to any=
 other type
> of extension header further followed by UDP ?


The following text is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:

      Outer IPv6 Header:
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Version| Traffic Class |           Flow Label                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Payload Length        | NxtHdr=3D17(UDP)|   Hop Limit   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |


There is a similar figure in draft-ietf-nvo3-geneve.

Best regards,
Tal.

From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] On =
Behalf Of Robert Raszuk
Sent: Monday, May 23, 2016 10:29 AM
To: Tal Mizrahi
Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo3@=
ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@tool=
s.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>; d=
raft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.ie=
tf.org>; Stefano Previdi (sprevidi)

Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header

Hi Tal,

> drafts seem to imply

Where say in draft draft-quinn-vxlan-gpe do you see such statement that wou=
ld imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer=
 to any other type of extension header further followed by UDP ?

Thx,
R.


On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Dear Authors of VXLAN-GPE / Geneve,

I am reiterating on this question, as I haven't seen a response yet:

Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.

Thanks,
Tal.



>-----Original Message-----
>From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] On=
 Behalf Of Tal Mizrahi
>Sent: Tuesday, May 17, 2016 12:09 PM
>To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
>geneve@tools.ietf.org<mailto:geneve@tools.ietf.org>; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>
>Cc: spring@ietf.org<mailto:spring@ietf.org>; nvo3@ietf.org<mailto:nvo3@iet=
f.org>; 6man WG; draft-ietf-6man-segment-
>routing-header@tools.ietf.org<mailto:routing-header@tools.ietf.org>
>Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
>routing-header
>
>Stefano,
>
>If I understand your point correctly:
>IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, since
>these encapsulations do not currently allow the use of IPv6 extension
>headers.
>
>I wonder if the authors of VXLAN-GPE and Geneve have considered the use of
>segment routing.
>
>Thanks,
>Tal.
>
>
>
>>-----Original Message-----
>>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:sprevi=
di@cisco.com>]
>>Sent: Tuesday, May 17, 2016 10:41 AM
>>To: Tom Herbert
>>Cc: Tal Mizrahi; 6man WG; spring@ietf.org<mailto:spring@ietf.org>;
>>draft-ietf-6man-segment-routing- header@tools.ietf.org<mailto:header@tool=
s.ietf.org>
>>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
>>header
>>
>>
>>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com<mailto:to=
m@herbertland.com>>
>wrote:
>>>
>>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com<mailto:=
talmi@marvell.com>>
>>wrote:
>>>>> it=92s all about IP, not layer-2.
>>>>>
>>>>> s.
>>>>
>>>> Right. However, it appears that at least in some cases a VXLAN VTEP
>>>> will
>>use SR. It certainly may be the case in SFC use cases (see Section 2.3
>>in draft- ietf-spring-ipv6-use-cases).
>>>>
>>>
>>> draft-ietf-6man-segment-routing-header mentions that the packet is
>>> encapsulated
>>
>>
>>into an outer ipv6 header which makes it a layer-3 encap.
>>
>>
>>> , but I don't think it is explicit as to exact encapsulation format
>>> (I suppose simple ip6ip6 is implied).
>>
>>
>>see section 2.2
>>
>>
>>> But, it
>>> seems like any of several encapsulation techniques could work (VXLAN,
>>
>>
>>I have some problems to understand where to fit an extension header
>>into a vxlan encap=85
>>
>>
>>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
>>> to do SR is already doing tunneling it seems reasonable to me to only
>>> have one layer of encapsulation. Maybe this should be clarified in
>>> the draft?
>>
>>
>>the draft is about IPv6 extension header and more precisely a new type
>>of the routing extension header defined in rfc2460. That=92s the context.
>>
>>
>>s.
>>
>>
>>
>>
>>>
>>> Tom
>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:sp=
revidi@cisco.com>]
>>>>> Sent: Monday, May 16, 2016 2:24 PM
>>>>> To: Tal Mizrahi
>>>>> Cc: Ole Tr=F8an;
>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft-ie=
tf-6man-segment-routing-header@tools.ietf.org>;
>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>> Subject: Re: [spring] L4 Checksum and
>>>>> draft-ietf-6man-segment-routing- header
>>>>>
>>>>>
>>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com<mailto:t=
almi@marvell.com>> wrote:
>>>>>>
>>>>>> Hi Stefano,
>>>>>>
>>>>>> Thanks again for the prompt response.
>>>>>>
>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>> is removed and the packet continues  its journey like nothing
>happened.
>>>>>>
>>>>>> So VXLAN is off the table?
>>>>>
>>>>>
>>>>> it=92s all about IP, not layer-2.
>>>>>
>>>>> s.
>>>>>
>>>>>
>>>>>> It would be worthwhile to clarify this in the draft. If you have a
>>>>>> specific
>>>>> encapsulation in mind, it would be great if the draft would specify i=
t.
>>>>>>
>>>>>> Thanks,
>>>>>> Tal.
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:=
sprevidi@cisco.com>]
>>>>>>> Sent: Monday, May 16, 2016 2:13 PM
>>>>>>> To: Tal Mizrahi
>>>>>>> Cc: Ole Tr=F8an;
>>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft-=
ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com<mailto=
:talmi@marvell.com>>
>>wrote:
>>>>>>>>
>>>>>>>> Hi Stefano,
>>>>>>>>
>>>>>>>> Thanks for the responses.
>>>>>>>>
>>>>>>>>> exactly.
>>>>>>>>>
>>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>>>>> encapsulation so clearly there=92s no L4 involved here.
>>>>>>>>>
>>>>>>>>> s.
>>>>>>>>
>>>>>>>> Two questions:
>>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
>>>>>>>> involved,
>>right?
>>>>>>>
>>>>>>>
>>>>>>> See below.
>>>>>>>
>>>>>>>
>>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
>>>>>>>> host cannot
>>>>>>> send an IPv6 packet with an SRH? The current draft says:
>>>>>>>>
>>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
>>>>>>>> its
>>>>>>>> IPv6 and Segment Routing Headers.  This include either:
>>>>>>>>
>>>>>>>>    A host originating an IPv6 packet.
>>>>>>>>
>>>>>>>>    An SR domain ingress router encapsulating a received IPv6 packe=
t
>>>>>>>>    into an outer IPv6 header followed by an SRH.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Will appreciate if you can clarify that.
>>>>>>>
>>>>>>>
>>>>>>> ok, two cases:
>>>>>>>
>>>>>>> 1. the SRH is inserted at the source.
>>>>>>> the source originates the packet, the ipv6 header and  the SRH.
>>>>>>> The source computes L4 checksum taking into  account the whole
>>IPv6+SRH.
>>>>>>> Here, theres=92 nothing new  compared to rfc2460.
>>>>>>>
>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>> is removed and the packet continues  its journey like nothing
>happened.
>>>>>>>
>>>>>>> s.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Tal.
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailt=
o:sprevidi@cisco.com>]
>>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
>>>>>>>>> To: Ole Tr=F8an; Tal Mizrahi
>>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:=
draft-ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org<mailto:otroan@=
employees.org> wrote:
>>>>>>>>>>
>>>>>>>>>> Tal,
>>>>>>>>>>
>>>>>>>>>>> [Apologies if this issue has been discussed before.]
>>>>>>>>>>>
>>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an =91SR
>>>>>>>>>>> Segment
>>>>>>>>> Endpoint Node=92 updates the Destination IP address.
>>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>>>>>>>>
>>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
>>>>>>>>>>> Otherwise, the
>>>>>>>>> L4 Checksum may be located in a pretty deep location.
>>>>>>>>>>> Speaking from a chip vendor=92s perspective this may be a probl=
em.
>>>>>>>>>>
>>>>>>>>>> From RFC2460, RH0:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>   o  If the IPv6 packet contains a Routing header, the Destinati=
on
>>>>>>>>>>      Address used in the pseudo-header is that of the final
>>>>>>>>>>      destination.  At the originating node, that address will be=
 in
>>>>>>>>>>      the last element of the Routing header; at the recipient(s)=
,
>>>>>>>>>>      that address will be in the Destination Address field of th=
e
>>>>>>>>>>      IPv6 header.
>>>>>>>>>>
>>>>>>>>>> I would expect SR would work the same.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> exactly.
>>>>>>>>>
>>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>>>>> encapsulation so clearly there=92s no L4 involved here.
>>>>>>>>>
>>>>>>>>> s.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Ole
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.or=
g> Administrative
>>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>
>_______________________________________________
>nvo3 mailing list
>nvo3@ietf.org<mailto:nvo3@ietf.org>
>https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring




--_000_D368BC0419BA29kreegerciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <1478E4122B4C8841A17A302DFFF113C3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>I agree with Robert and Jesse. - Larry</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Jesse Gross &lt;<a href=3D"ma=
ilto:jgross@vmware.com">jgross@vmware.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, May 23, 2016 at 1:19 =
PM<br>
<span style=3D"font-weight:bold">To: </span>Robert Raszuk &lt;<a href=3D"ma=
ilto:robert@raszuk.net">robert@raszuk.net</a>&gt;, Tal Mizrahi &lt;<a href=
=3D"mailto:talmi@marvell.com">talmi@marvell.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:draft-i=
etf-nvo3-geneve@tools.ietf.org">draft-ietf-nvo3-geneve@tools.ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:draft-ietf-nvo3-geneve@tools.ietf.org">draft-iet=
f-nvo3-geneve@tools.ietf.org</a>&gt;, &quot;<a href=3D"mailto:draft-ietf-nv=
o3-vxlan-gpe@tools.ietf.org">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>&q=
uot;
 &lt;<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org">draft-ietf=
-nvo3-vxlan-gpe@tools.ietf.org</a>&gt;, &quot;<a href=3D"mailto:spring@ietf=
.org">spring@ietf.org</a>&quot; &lt;<a href=3D"mailto:spring@ietf.org">spri=
ng@ietf.org</a>&gt;, 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf=
.org</a>&gt;,
 &quot;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&gt;, &quot;<a href=3D"mailto:dr=
aft-ietf-6man-segment-routing-header@tools.ietf.org">draft-ietf-6man-segmen=
t-routing-header@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-=
6man-segment-routing-header@tools.ietf.org">draft-ietf-6man-segment-routing=
-header@tools.ietf.org</a>&gt;,
 &quot;Stefano Previdi (sprevidi)&quot; &lt;<a href=3D"mailto:sprevidi@cisc=
o.com">sprevidi@cisco.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [nvo3] [spring] L4 Che=
cksum and draft-ietf-6man-segment-routing-header<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
alias-bounces@ietf.org">alias-bounces@ietf.org</a>&gt;, &lt;<a href=3D"mail=
to:jgross@vmware.com">jgross@vmware.com</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-To: </span>Larry Kreeger &lt;<a hre=
f=3D"mailto:kreeger@cisco.com">kreeger@cisco.com</a>&gt;, &lt;<a href=3D"ma=
ilto:uri.elzur@intel.com">uri.elzur@intel.com</a>&gt;, &lt;<a href=3D"mailt=
o:draft-ietf-6man-segment-routing-header@ietf.org">draft-ietf-6man-segment-=
routing-header@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Monday, May 23, 2016 a=
t 1:20 PM<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div>
<div>
<div>I agree that I don=92t believe that there is anything in these drafts =
that precludes the use of extension headers or segment routing =96 IP is si=
mply the layer underneath that these protocols are building on. The figures=
 are definitely just examples =96 they
 also show outer Ethernet headers, which is not a requirement.</div>
<div><br>
</div>
<div>I wouldn=92t want to add text specifically stating that extension head=
ers are permissible. It seems like that could lead to similar questions in =
the future where one might wonder if other features of IP are allowed becau=
se one is explicitly listed and others
 are not, etc. In my opinion, the drafts are about as clear as they can be =
on this point.</div>
<div><br>
</div>
<div>Jesse</div>
<div>
<div id=3D"MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div>On 5/23/16, 1:09 AM, &quot;<a href=3D"mailto:rraszuk@gmail.com">rraszu=
k@gmail.com</a> on behalf of Robert Raszuk&quot; &lt;<a href=3D"mailto:rras=
zuk@gmail.com">rraszuk@gmail.com</a> on behalf of
<a href=3D"mailto:robert@raszuk.net">robert@raszuk.net</a>&gt; wrote:</div>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
Hi Tal,</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<br>
</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<span style=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; f=
ont-size: 14.6667px;">&gt; In order to avoid ambiguity, it would be great i=
f the&nbsp;</span></div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<span style=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; f=
ont-size: 14.6667px;">&gt; authors could explicitly mention that IPv6 exten=
sion&nbsp;</span></div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<span style=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; f=
ont-size: 14.6667px;">&gt; headers are permitted.</span><br>
</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<br>
</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
Well the drafts are complaint to RFC2119 (normative reference) so unless th=
e text excludes elements with MUST/MUST NOT - everything else defined in th=
e building blocks they (re)use is permitted.&nbsp;</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<br>
</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
However as you say perhaps for clarity what could be added to those drafts =
is a normative reference to IPv4 and IPv6 base RFCs.</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<br>
</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
Best,</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
R.</div>
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small">
<br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <sp=
an dir=3D"ltr">
&lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Hi Robert,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">That makes sense.<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">However, in this case the figures m=
ay be a bit confusing WRT the possible existence of extension headers. This=
 confusion is what led to the discussion
 in this thread about whether segment routing is possible with VXLAN/VXLAN-=
GPE/Geneve encapsulations.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">In order to avoid ambiguity, it wou=
ld be great if the authors could explicitly mention that IPv6 extension hea=
ders are permitted.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Regards,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Tal.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);"><u></u>&nbsp;<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"><a href=3D"mailto:rraszuk@gmail.com" target=3D"_bla=
nk">rraszuk@gmail.com</a> [mailto:<a href=3D"mailto:rraszuk@gmail.com" targ=
et=3D"_blank">rraszuk@gmail.com</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:47 AM</span></p>
<div>
<div class=3D"h5"><br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>;
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a hr=
ef=3D"mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=
=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">
draft-ietf-nvo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)<br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<u></u><u></u></div>
</div>
<p></p>
</div>
</div>
<div>
<div class=3D"h5">
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Hi T=
al,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Inde=
ed .. I saw the figures, but figures are non normative in any draft/rfc unl=
ess text below specifically spells it out.&nbsp;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">For =
example from vxlan-gpe:&nbsp;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&quo=
t;<span style=3D"color:black">When the outer IP header is IPv4, VTEPs MUST =
set the DF bit.&quot;</span><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Besi=
des it is pretty challenging to add animation to the current draft formats =
to illustrate all possibly allowed field values/combinations in any figure =
:) &nbsp;Figures just illustrate one use
 example.&nbsp;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">To m=
e the current specs permit any value of IPv6 NxtHdr field as permitted in b=
oth encapsulations.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Best=
,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Robe=
rt.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;"><u><=
/u>&nbsp;<u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Hi Robert,</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&gt;</span><span style=3D"font-size=
: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Where s=
ay in draft draft-quinn-vxlan-gpe do you
 see such statement that would imply </span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&gt; that v6 NxtHdr must be only eq=
ual to 17 (UDP) and not be a pointer to any other type
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&gt; of extension header further fo=
llowed by UDP ?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">The following text is from Figure 4=
 in draft-ietf-nvo3-vxlan-gpe:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Outer IPv6=
 Header:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Version| =
Traffic Class |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Flow Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Payload Length&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; | NxtHdr=3D17(UDP)|&nbsp;&nbsp; Hop Limit&nbsp;&nbsp;=
 |</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&=
#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43=
;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: 'Courie=
r New'; color: rgb(31, 73, 125);">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</span><u>=
</u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">There is a similar figure in draft-=
ietf-nvo3-geneve.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Best regards,</span><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">Tal.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; font-family: Calibri=
, sans-serif; color: rgb(31, 73, 125);">&nbsp;</span><u></u><u></u></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size: 10pt; font-family: Taho=
ma, sans-serif;">From:</span></b><span style=3D"font-size: 10pt; font-famil=
y: Tahoma, sans-serif;"> nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.o=
rg" target=3D"_blank">nvo3-bounces@ietf.org</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:29 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>;
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a hr=
ef=3D"mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=
=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">
draft-ietf-nvo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)</span=
><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<u></u><u></u></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Hi T=
al,</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&nbs=
p;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&gt;=
&nbsp;</span><span style=3D"font-size: 9.5pt; font-family: Arial, sans-seri=
f;">drafts seem to imply</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&nbs=
p;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Wher=
e say in draft&nbsp;draft-quinn-vxlan-gpe do you see such statement that wo=
uld imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointe=
r to any other type of extension header further
 followed by UDP ?&nbsp;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&nbs=
p;</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">Thx,=
<br>
R.</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family: Arial, sans-serif;">&nbs=
p;</span><u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi &lt;<a =
href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&g=
t; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Dear Authors of VXLAN-GPE / Geneve,<br>
<br>
I am reiterating on this question, as I haven't seen a response yet:<br>
<br>
Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.<br>
<br>
Thanks,<br>
Tal.<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_=
blank">nvo3-bounces@ietf.org</a>] On Behalf Of Tal Mizrahi<br>
&gt;Sent: Tuesday, May 17, 2016 12:09 PM<br>
&gt;To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-<br>
&gt;<a href=3D"mailto:geneve@tools.ietf.org" target=3D"_blank">geneve@tools=
.ietf.org</a>;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a><br>
&gt;Cc: <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.or=
g</a>; <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">
nvo3@ietf.org</a>; 6man WG; draft-ietf-6man-segment-<br>
&gt;<a href=3D"mailto:routing-header@tools.ietf.org" target=3D"_blank">rout=
ing-header@tools.ietf.org</a><br>
&gt;Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-<b=
r>
&gt;routing-header<br>
&gt;<br>
&gt;Stefano,<br>
&gt;<br>
&gt;If I understand your point correctly:<br>
&gt;IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sin=
ce<br>
&gt;these encapsulations do not currently allow the use of IPv6 extension<b=
r>
&gt;headers.<br>
&gt;<br>
&gt;I wonder if the authors of VXLAN-GPE and Geneve have considered the use=
 of<br>
&gt;segment routing.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;-----Original Message-----<br>
&gt;&gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevidi=
@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt;&gt;To: Tom Herbert<br>
&gt;&gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org" target=
=3D"_blank">spring@ietf.org</a>;<br>
&gt;&gt;draft-ietf-6man-segment-routing- <a href=3D"mailto:header@tools.iet=
f.org" target=3D"_blank">
header@tools.ietf.org</a><br>
&gt;&gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routi=
ng-<br>
&gt;&gt;header<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailto=
:tom@herbertland.com" target=3D"_blank">tom@herbertland.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"ma=
ilto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt; it=92s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Right. However, it appears that at least in some cases a V=
XLAN VTEP<br>
&gt;&gt;&gt;&gt; will<br>
&gt;&gt;use SR. It certainly may be the case in SFC use cases (see Section =
2.3<br>
&gt;&gt;in draft- ietf-spring-ipv6-use-cases).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; draft-ietf-6man-segment-routing-header mentions that the packe=
t is<br>
&gt;&gt;&gt; encapsulated<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; , but I don't think it is explicit as to exact encapsulation f=
ormat<br>
&gt;&gt;&gt; (I suppose simple ip6ip6 is implied).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;see section 2.2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; But, it<br>
&gt;&gt;&gt; seems like any of several encapsulation techniques could work =
(VXLAN,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;I have some problems to understand where to fit an extension header=
<br>
&gt;&gt;into a vxlan encap=85<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that =
wants<br>
&gt;&gt;&gt; to do SR is already doing tunneling it seems reasonable to me =
to only<br>
&gt;&gt;&gt; have one layer of encapsulation. Maybe this should be clarifie=
d in<br>
&gt;&gt;&gt; the draft?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;the draft is about IPv6 extension header and more precisely a new t=
ype<br>
&gt;&gt;of the routing extension header defined in rfc2460. That=92s the co=
ntext.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Tom<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"ma=
ilto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=F8an;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-head=
er@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_blank">s=
pring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a hr=
ef=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;=
 wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the&nbsp; packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation&n=
bsp; (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues&nbsp; its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; it=92s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the draf=
t. If you have a<br>
&gt;&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft =
would specify it.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a hr=
ef=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=F8an;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_=
blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt;=
<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a=
>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=92s no =
L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4 =
would still be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; involved,<br>
&gt;&gt;right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say 'assumes encapsulation', d=
oes it mean that a<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; host cannot<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current d=
raft says:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originati=
ng an IPv6 packet with<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.&nbsp; Th=
is include either:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; A host originating an IPv6 pa=
cket.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; An SR domain ingress router e=
ncapsulating a received IPv6 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; into an outer IPv6 header fol=
lowed by an SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 hea=
der and&nbsp; the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into&nb=
sp; account the whole<br>
&gt;&gt;IPv6&#43;SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Here, theres=92 nothing new&nbsp; compared to =
rfc2460.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the&nbsp; packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation&n=
bsp; (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues&nbsp; its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mail=
to:<a href=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.c=
om</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<br=
>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=F8an; Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man-=
segment-routing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- heade=
r<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a hr=
ef=3D"mailto:otroan@employees.org" target=3D"_blank">
otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has b=
een discussed before.]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-s=
egment-routing-header, an =91SR<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node=92 updates the Destinati=
on IP address.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also update=
 the Layer 4 Checksum, right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper =
bound on the size of the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a pretty=
 deep location.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor=92=
s perspective this may be a problem.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;o&nbsp; If the IPv6 pa=
cket contains a Routing header, the Destination<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Address used i=
n the pseudo-header is that of the final<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; destination.&n=
bsp; At the originating node, that address will be in<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; the last eleme=
nt of the Routing header; at the recipient(s),<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; that address w=
ill be in the Destination Address field of the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; IPv6 header.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the s=
ame.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there=92s no =
L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;&gt;&gt;&gt; IETF IPv6 working group mailing list <a href=3D"mailto:ipv=
6@ietf.org" target=3D"_blank">
ipv6@ietf.org</a> Administrative<br>
&gt;&gt;&gt;&gt; Requests: <a href=3D"https://www.ietf.org/mailman/listinfo=
/ipv6" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;nvo3 mailing list<br>
&gt;<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br=
>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/nvo3</a><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">_______________________________________________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/spring</a><u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</span></div>
</div>
</span>
</body>
</html>

--_000_D368BC0419BA29kreegerciscocom_--


From nobody Mon May 23 16:41:41 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 A42C012D4FB for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 16:41:39 -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 goAy3DC3M5yX for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 16:41:38 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 528A712D154 for <ipv6@ietf.org>; Mon, 23 May 2016 16:41:38 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id c189so239760pfb.3 for <ipv6@ietf.org>; Mon, 23 May 2016 16:41:38 -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=3lpbsnal7vWpZ8URVuwnLcIJOdKxy0z7ffgDST3it5Y=; b=CuWn79XTdMIEeCk3C4greJZmadN9CIR8B36329E2YXBTmx6S17Z7J4GQVIHV5UEexZ qw+0dlEGE01nwW4cYOE3I8w7M+wUfF2e+LNNdpV2PuwXXL8Xo/E/PuW63ZGMqqhRp5SH a6sCCgymGT//QFEJ92N3iNJMqRMauB59Vj1BXXCFFCL744h5KJ25DIz3S7judDM3p/g4 keMs8aGPpA768t2altGDdTrUReSX5FB8iM/TfaVTlbg+csngJJV30gr/mfiO1iyg21I4 hQNkjZkEqeGtw2Uay6S0zRBRu2jFGZ0HvWG/gQbEu+juuORh+RPWeSq0sAVcIJF2lW8x gZvg==
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=3lpbsnal7vWpZ8URVuwnLcIJOdKxy0z7ffgDST3it5Y=; b=Vqq6yBUKY1kGlBid1CAd6D0z6n8DNHsub/ixZ7vf/ZJ28Wfs5mF31Wke6KyqXiWcKo yJBr7a81ygH2q/Cgn5gGQZ6FYdghPj/VLvEtZGZXlWzljy0u5xGH08OruYctQOoqCPlt dooRicWTW2bdZAiI4FeR7aDqRn4JBrxcmCXZoGGBoxU0xui/w2CfMm3onBx42CrLFTZG jO2ZigUMXjfsLwlEcpmIcM3sMopJIZSwxujdz6IwHD6CFe0uKpHSMh+iHvCxS3yfeifM JwgWedRRlgVT2L5/N/VpHxfsjp+QR5V73tc0SvxzdEjB29lE8kGVp/qlvb8oiyH10Hvh deeQ==
X-Gm-Message-State: ALyK8tKFR7wjJaU+XUcyOXxwhdZoVN6RvQeEbrZos09YTfcAIu7T5cHi6E6z6Z+S9T7DNw==
X-Received: by 10.98.51.2 with SMTP id z2mr2177126pfz.118.1464046897868; Mon, 23 May 2016 16:41:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:5038:1:152f:4f07:edf6:7b96? ([2406:e007:5038:1:152f:4f07:edf6:7b96]) by smtp.gmail.com with ESMTPSA id s8sm19368pav.39.2016.05.23.16.41.36 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 May 2016 16:41:37 -0700 (PDT)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: ipv6@ietf.org
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com>
Date: Tue, 24 May 2016 11:41:38 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/V-tIOUfW6LoTm1fHZP7yLUdO1dE>
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, 23 May 2016 23:41:39 -0000

On 24/05/2016 05:58, otroan@employees.org wrote:
> Fernando,
>=20
>>> As we=E2=80=99re finishing the edits on the RFC2460bis, RFC1981bis an=
d
>>> RFC4291bis, we will initiate working group last calls with the
>>> intended status of Internet Standard. We will do a single last call
>>> for the updated documents (RFC2460, RFC4291, RFC1981) and a separate
>>> working group last call for the unchanged documents (RFC3596,
>>> RFC4443, RFC4941).
>>
>> After reading RFC4941, it looks like it really needs to be updated, an=
d
>> also that if one were to publish RFC4941 in 2016, a fair share of text=

>> would be edited.
>=20
> Yes, but we're not. We're reclassifying it as Internet Standard.

And that's a problem, because it directly implies that temporary addresse=
s
are *additional* and that is, from recent discussions, a MAY not a MUST.

I suggest removing 4941 from the list.

   Brian


From nobody Mon May 23 16:51: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 9DE9912D100 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 16:51: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 yWgjF1qC5TZK for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 16:51:08 -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 A5DC812D5DE for <ipv6@ietf.org>; Mon, 23 May 2016 16:51:08 -0700 (PDT)
Received: by mail-pa0-x22e.google.com with SMTP id xk12so327276pac.0 for <ipv6@ietf.org>; Mon, 23 May 2016 16:51:08 -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=MXxQ7SsSPurd8AbQ6SSidNzwv//ggUniAsa1usAXbHY=; b=Sq8MVPhB5nzZPVGewkRtD+SvFWaII2JkBPZCwCL0yGPYZ9WSRZE9+VX3W9V5EHQHyk gt+CypV4KLd7W9BuFCxapanDVhlXAtpBvIf94vdMmDjFIXmtjMnpN236CTxr0nbzeKAx phsRW9q5/UzdLoGku15gHp0wBA3eVthKGqAmjWRU6c80Fc4NAxJrLMw+c8J9mPn9BvT0 yZrZ8urTIo7csQUEE5lM+GAkFtEWeJBthBeRsrGG00fYd+Yyl97qRVwsdGZoaZjpg6wS C7No4qkRzj555zZh4g2URZPLEYlBtx1ULjpu3h1aLz2lLuTaPhXj39cxfvOuCHm3kx9F KXtQ==
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=MXxQ7SsSPurd8AbQ6SSidNzwv//ggUniAsa1usAXbHY=; b=R2G+3uElB7z96H39nWDy8zT0RA6J5yLc5Ji+OpanLfpiBj9cXKuLCgWDK64Vobt1Uq e/bc1gM6EWU1ITFKHJhdFX2tg6Efw333a4j/3gaK0vnfDvXKOD0irrQHS+x4CX7esNT/ LdiHHr839p22qhnpRBXrP7s1gBhSAyeXGkewNQg2GMrcM1jKTgnhA09qTemqDpNFUCAE mCjohUtchImRzPPni0dcDSAKSAEB9GVgZfDv2yCdtxmQfkUrmggEk4EFvhIlaRu9WJan EhPsZFnpyws/hlO9MtaLbFa09mH5WJx8KTNj4D2ma6JVKNc9vIOLYZIA/GVn3SPVk1V0 VLmA==
X-Gm-Message-State: ALyK8tJWnaa9vnl34YsL+tcbo3gsK05fDhJycti/K/avrqf/T6TOW+UKvXQulzZ/RefNgg==
X-Received: by 10.66.140.17 with SMTP id rc17mr2179706pab.79.1464047468292; Mon, 23 May 2016 16:51:08 -0700 (PDT)
Received: from ?IPv6:2406:e007:5038:1:152f:4f07:edf6:7b96? ([2406:e007:5038:1:152f:4f07:edf6:7b96]) by smtp.gmail.com with ESMTPSA id z63sm49203970pfb.47.2016.05.23.16.51.06 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 May 2016 16:51:07 -0700 (PDT)
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt> - hybrid addresses
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <89CA2C18-AE61-4D40-8997-221201835944@gmail.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com> <574210D2.9030903@si6networks.com> <fbfac489-f56a-0ece-d1c6-b17cdc6846d8@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6df1567c-88a9-3995-7017-da71bc5dcea4@gmail.com>
Date: Tue, 24 May 2016 11:51:09 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <fbfac489-f56a-0ece-d1c6-b17cdc6846d8@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4UkvVdS_YEBaIWJq0-NVxVY8n84>
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, 23 May 2016 23:51:09 -0000

Alex,
On 23/05/2016 21:13, Alexandre Petrescu wrote:
...
> (privacy may be a valid reason; but hybrid addresses mixing IDs from
> different layers is common elsewhere, wonder why opposing)

Well yes, it seems to be that we have all followed the OSI method,
where a TSAP is an NSAP+something, etc. But that isn't actually a
rqeuirement of the OSI model, iirc. Privacy would indeed argue for
a layer N+1 address not to be a simple extension of a layer N address.
That was not a big consideration in the past, unfortunately.

    Brian


From nobody Mon May 23 23:59: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 86AC012D527 for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 23:59:47 -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 J-59TnjHwPPk for <ipv6@ietfa.amsl.com>; Mon, 23 May 2016 23:59: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 85E6712D51C for <ipv6@ietf.org>; Mon, 23 May 2016 23:59:45 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2016 06:59:44 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 9EC6A9CC4F; Mon, 23 May 2016 23:59:43 -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=ORfLKSWBeRCcHHoAzdCY+/Da2ow=; b= rNI20OD9so9rRKPRkBbHZSgfAcqtMYU/2MZCoqaEustv2CbG8Wplp6VGvbAt9DM6 nFIGxg4suS1l7Awf4E4Rfdx+nyETI8F886foWm2UgAXrbSEbFEYLlX/RZeR/aUqe /z/D5uNCjIkg8rQavP4YmmLk6WnNi4JFcEKWbTD6uXY=
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=GKCF10Y+ZjOz2bATmJI6UrxuXi K/wEewBuLLf0V8a9dcxSDZHXBsU0GAHi8A92BqwTYuw1P3dANRSB39AfBoIOexGH gZZLoSvUsA1fpbrjWUT+s7yQF5EbMKPUvLItqtcwlXDvBiO49OQs2vnJfbIfyVN4 RhEmWZOCqm/31WDeE=
Received: from h.hanazo.no (unknown [173.38.220.37]) (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 686B99CC4E; Mon, 23 May 2016 23:59:43 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B17FC16E07D0; Tue, 24 May 2016 08:59:40 +0200 (CEST)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard. 
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_804AC0E6-DA97-419D-86E7-7A14B2A9AAE5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com>
Date: Tue, 24 May 2016 08:59:39 +0200
Message-Id: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9DEJumMvVQKAI0e1y6ST-2-j69o>
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, 24 May 2016 06:59:47 -0000

--Apple-Mail=_804AC0E6-DA97-419D-86E7-7A14B2A9AAE5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Brian,

>>>> As we=E2=80=99re finishing the edits on the RFC2460bis, RFC1981bis =
and
>>>> RFC4291bis, we will initiate working group last calls with the
>>>> intended status of Internet Standard. We will do a single last call
>>>> for the updated documents (RFC2460, RFC4291, RFC1981) and a =
separate
>>>> working group last call for the unchanged documents (RFC3596,
>>>> RFC4443, RFC4941).
>>>=20
>>> After reading RFC4941, it looks like it really needs to be updated, =
and
>>> also that if one were to publish RFC4941 in 2016, a fair share of =
text
>>> would be edited.
>>=20
>> Yes, but we're not. We're reclassifying it as Internet Standard.
>=20
> And that's a problem, because it directly implies that temporary =
addresses
> are *additional* and that is, from recent discussions, a MAY not a =
MUST.

I don't think 4941 _requires_ public addresses. it specifies the =
behaviour _if_ you have them.
it is up to applications how the use the available addresses.

(somewhat tangentially, you can also argue that a lot of the benefits =
and point of doing IPv6 in the first place goes away if you don't have =
stable addresses, oh well.).

> I suggest removing 4941 from the list.

is there a cultural shift in the IETF? are we trying to make standards =
much more prescriptive in specifying _how_ we want people to use them? =
as opposed to containing ourselves to specifying protocols and =
mechanisms?

are there real problems with 4941? or are we unhappy with how =
users/implementors are using the resulting addresses? or are we worried =
about _how_ they might use them or not use them in the future?

what are you trying to achieve by not making 4941 Internet Standard?

cheers,
Ole

--Apple-Mail=_804AC0E6-DA97-419D-86E7-7A14B2A9AAE5
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

iQIcBAEBCgAGBQJXQ/vcAAoJEL7aWKiYQt92Zn0P/0JGbBZDqX1vS1qrsaaIdG9R
dY3bbwJPhcMqxEMiOqAwTHDhMo/cNISWME9UxzW7Fd8M7tCvUhkHz0uplMOQ7vA4
1QdSfB9uXw4TEIAEHRlvbUZpNRJ3cYIZXJ8kiUDdkgW7ZUsL61xwAMdIooJnZq8N
IkIRdI+DirQ/p2Crfms8T1lOB4+OlZwRomL/z6fmbCF/2hDKY1Os2y+xeQDhSN/0
ULpcNsikmK/7aZV17XkIshrA0FzPrr1BbjKsYw6sLz9Eej+Epxb1a5AjHWNwGh58
Mgt1U0EmfM91UAyvDSOTrJ/DVqlTexfoaZl+Lkxj7x0q+VU+ka7L0Ha9rG713MPH
eSLFotgLCo+qKl+tSTYQIozoQ9gGb9cYtmW1x6ATI+byW+ByH/BAi1PrFm1/NfH2
RlnhaQZcNg8mnPxvxnctllbYmgJZJRqSdc2uy1AWydYVzEoOIWunlf+78WNzcv0c
Ch0rGwNnJCvE+6mxAEwvbL3DgeMsibwS60aPqG8L8dQg7H4wAmT7d+BUiXkZmfGo
fDUXYmuvu3pp/5cQ4aFVLK7O6TlCLg4Eney4+nxaZKUuOJYoe1KhWa71lmEksefV
YXi6MCHGAW7JysjYUGu6+uealjr6z0Y94gx9IFiVHPO56N6eaNMAyynllTj/4ttc
mNzOBoMxlxfJ6xULzL8v
=QdZx
-----END PGP SIGNATURE-----

--Apple-Mail=_804AC0E6-DA97-419D-86E7-7A14B2A9AAE5--


From nobody Tue May 24 01:37:44 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 3F1AA12D1B9 for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:37:43 -0700 (PDT)
X-Quarantine-ID: <adZE-1_HlcSn>
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 adZE-1_HlcSn for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:37:41 -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 0A11512D09D for <ipv6@ietf.org>; Tue, 24 May 2016 01:37:39 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1b57qM-0000HYC; Tue, 24 May 2016 10:37:38 +0200
Message-Id: <m1b57qM-0000HYC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: default-iids: Closing concern regarding stable address requirement 
From: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> 
In-reply-to: Your message of "Mon, 23 May 2016 11:37:02 -0700 ." <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> 
Date: Tue, 24 May 2016 10:37:35 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fajuZRVPnCDsAL2RCXKPGdT6Izw>
Cc: draft-ietf-6man-default-iids@tools.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, 24 May 2016 08:37:43 -0000

In your letter dated Mon, 23 May 2016 11:37:02 -0700 you wrote:
>I don't know the general sense of the wg on my suggested text.  If
>it's just deemed to be redundant or possibly out-of-scope but
>otherwise acceptable while it makes some others much happier (on which
>I'm quite sure) I think it's still worth considering.  But I'm not
>pushing my specific agenda in proposing this text, so if the text
>itself is so controversial I won't argue for it.

The problem I have with this draft and the discussion surrounding the draft
is that it starts somewhere in the middle.

A particular device, say server or laptop, in a particular environment,
trusted, untrusted, etc. results in a set of requirements for what addresses
the device should have.

Then we can map those requirements to particular technologies.

Instead we describe and discuss a number of things we can do, but then it is
upto the operating system software vendor or the operator or the user to
figure out what goes where.

We create an endless maze of SHOULDs where everything is possible. But
too many options lead to non-experts getting lost.

So in my opinion, a default-iids document should start with set of example
configuration that map to a set of features that we want to support
and then to a set of IID options.

Then an implementor can start at the top, look up the type of device to
support and find what needs to be done.

For a selected class of devices, I'm a huge fan of using EUI-64 based IIDs.
I agree that in general EUI-64 based IIDs are bad, but we can just as
well write down when they make life easier. 


From nobody Tue May 24 01:37:47 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 7E2B712D09D for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 LJJHIfRRlG5D for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:37:41 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 04E4D12B032 for <ipv6@ietf.org>; Tue, 24 May 2016 01:37:41 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id c189so12477560vkb.1 for <ipv6@ietf.org>; Tue, 24 May 2016 01:37:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=R1qNzc1knlFQvYtE+UfC++GVTeseRnhTXv3ulmTLyCc=; b=ONtYYnC9reLC7PV5/XfMkM64hsS8CK8ET5u2dfh8tzK7/cC92lkHpJICfQNxwKbdNa NOtz3b+VRaLiCHOuekpFXTENlBU4A0gjMRqWssOFeO34kkPEr3m2RAdpl3xNNd9hquRy NA8tB3nAVOAJkXk1qm+0JVPPC9CiFE78E+67cjPMx+zhbuvWfMgFt/j04lAHzKpGVCT1 P9rnIB69osrLEll2YE2BqJoKqiViBB1oN4cyKrOAYs/rDYQwNkF/dEcmm+Bb2k7oCCo8 m7cWYrdEMRvoQ80hkFFPSG63NTHmbO6xzRi2xo9Jsi44dgVroXfoO2mmVQ3yED81NgHU ibOg==
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:date :message-id:subject:from:to:cc; bh=R1qNzc1knlFQvYtE+UfC++GVTeseRnhTXv3ulmTLyCc=; b=QGRvg14h1JZ3qZkZ0FpgCz2tu/VtNt2nfQQ6W+8GGi/ZdbHc8V+6z3QjkSRYJSCPnr YMu3+lKLpI+MCX9zHi1aSOCcujQPsImTdHjyO0fFJQl2+pqPMk/yZPe34ykq9hHNg8yb +nbkTiMY/T8mAPy7kORBqvQu65WtyJNTffBL9cNJOfFAVmGTWbIKTj/SPnTlWy+mtJYA tngeu6Ec40WEGmTuf/3XNzO9jvOq120sOosO5FoEXE4yeBf4ZNoILmNf9nB0FnCTIlNb EcX1jGfXQyI2JiQFJrAeDzej8nxtUTCUrV4E8daiYietAlfR1FyfIcE1+fGScJSLD3hx pw0g==
X-Gm-Message-State: ALyK8tI9X0rXL+D77CzAzwW/1C7DkaUvirR8Rtz20U57lhxLWAfkhnwtNk4J278KeetJFITtQ2QO14IfsV9Zsg==
MIME-Version: 1.0
X-Received: by 10.31.73.132 with SMTP id w126mr1845666vka.94.1464079060058; Tue, 24 May 2016 01:37:40 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 24 May 2016 01:37:39 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 24 May 2016 01:37:39 -0700 (PDT)
In-Reply-To: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
Date: Tue, 24 May 2016 18:37:39 +1000
Message-ID: <CAO42Z2zR6H1r-6aspyhVJLvoEJ25RhYOOnfMmxui8VUr530-Mw@mail.gmail.com>
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
From: Mark Smith <markzzzsmith@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114dd5a04c4cea0533927821
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5V-jmRzKDqBPX4oAJjYCGiqc1FU>
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, 24 May 2016 08:37:44 -0000

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

On 24 May 2016 4:59 PM, <otroan@employees.org> wrote:
>
> Brian,
>
> >>>> As we=E2=80=99re finishing the edits on the RFC2460bis, RFC1981bis a=
nd
> >>>> RFC4291bis, we will initiate working group last calls with the
> >>>> intended status of Internet Standard. We will do a single last call
> >>>> for the updated documents (RFC2460, RFC4291, RFC1981) and a separate
> >>>> working group last call for the unchanged documents (RFC3596,
> >>>> RFC4443, RFC4941).
> >>>
> >>> After reading RFC4941, it looks like it really needs to be updated,
and
> >>> also that if one were to publish RFC4941 in 2016, a fair share of tex=
t
> >>> would be edited.
> >>
> >> Yes, but we're not. We're reclassifying it as Internet Standard.
> >
> > And that's a problem, because it directly implies that temporary
addresses
> > are *additional* and that is, from recent discussions, a MAY not a MUST=
.
>
> I don't think 4941 _requires_ public addresses. it specifies the
behaviour _if_ you have them.
> it is up to applications how the use the available addresses.
>
> (somewhat tangentially, you can also argue that a lot of the benefits and
point of doing IPv6 in the first place goes away if you don't have stable
addresses, oh well.).
>
> > I suggest removing 4941 from the list.
>
> is there a cultural shift in the IETF? are we trying to make standards
much more prescriptive in specifying _how_ we want people to use them?

I think in the security and privacy domains, being prescriptive or close to
it is probably necessary to try to ensure things aren't used incorrectly or
past when they should be.

This RFC is certainly prescriptive.

"Deprecating Secure Sockets Layer Version 3.0"
https://tools.ietf.org/html/rfc7568

>as opposed to containing >ourselves to specifying protocols and
>mechanisms?
>
> are there real problems with 4941? or are we unhappy with how
users/implementors are using the resulting addresses? or are we worried
about _how_ they might use them or not use them in the future?
>
> what are you trying to achieve by not making 4941 Internet Standard?
>
> cheers,
> Ole
>

Regards,
Mark.

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

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

<p dir=3D"ltr"><br>
On 24 May 2016 4:59 PM, &lt;<a href=3D"mailto:otroan@employees.org">otroan@=
employees.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Brian,<br>
&gt;<br>
&gt; &gt;&gt;&gt;&gt; As we=E2=80=99re finishing the edits on the RFC2460bi=
s, RFC1981bis and<br>
&gt; &gt;&gt;&gt;&gt; RFC4291bis, we will initiate working group last calls=
 with the<br>
&gt; &gt;&gt;&gt;&gt; intended status of Internet Standard. We will do a si=
ngle last call<br>
&gt; &gt;&gt;&gt;&gt; for the updated documents (RFC2460, RFC4291, RFC1981)=
 and a separate<br>
&gt; &gt;&gt;&gt;&gt; working group last call for the unchanged documents (=
RFC3596,<br>
&gt; &gt;&gt;&gt;&gt; RFC4443, RFC4941).<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; After reading RFC4941, it looks like it really needs to b=
e updated, and<br>
&gt; &gt;&gt;&gt; also that if one were to publish RFC4941 in 2016, a fair =
share of text<br>
&gt; &gt;&gt;&gt; would be edited.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Yes, but we&#39;re not. We&#39;re reclassifying it as Interne=
t Standard.<br>
&gt; &gt;<br>
&gt; &gt; And that&#39;s a problem, because it directly implies that tempor=
ary addresses<br>
&gt; &gt; are *additional* and that is, from recent discussions, a MAY not =
a MUST.<br>
&gt;<br>
&gt; I don&#39;t think 4941 _requires_ public addresses. it specifies the b=
ehaviour _if_ you have them.<br>
&gt; it is up to applications how the use the available addresses.<br>
&gt;<br>
&gt; (somewhat tangentially, you can also argue that a lot of the benefits =
and point of doing IPv6 in the first place goes away if you don&#39;t have =
stable addresses, oh well.).<br>
&gt;<br>
&gt; &gt; I suggest removing 4941 from the list.<br>
&gt;<br>
&gt; is there a cultural shift in the IETF? are we trying to make standards=
 much more prescriptive in specifying _how_ we want people to use them?</p>
<p dir=3D"ltr">I think in the security and privacy domains, being prescript=
ive or close to it is probably necessary to try to ensure things aren&#39;t=
 used incorrectly or past when they should be.</p>
<p dir=3D"ltr">This RFC is certainly prescriptive.</p>
<p dir=3D"ltr">&quot;Deprecating Secure Sockets Layer Version 3.0&quot;<br>
<a href=3D"https://tools.ietf.org/html/rfc7568">https://tools.ietf.org/html=
/rfc7568</a><br></p>
<p dir=3D"ltr">&gt;as opposed to containing &gt;ourselves to specifying pro=
tocols and &gt;mechanisms?<br>
&gt;<br>
&gt; are there real problems with 4941? or are we unhappy with how users/im=
plementors are using the resulting addresses? or are we worried about _how_=
 they might use them or not use them in the future?<br>
&gt;<br>
&gt; what are you trying to achieve by not making 4941 Internet Standard?<b=
r>
&gt;<br>
&gt; cheers,<br>
&gt; Ole<br>
&gt;</p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt; -------------------------------------------------------=
-------------<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/listin=
fo/ipv6"> https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
&gt;<br>
</p>

--001a114dd5a04c4cea0533927821--


From nobody Tue May 24 01:50:49 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 2734A12D0BA for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:50:45 -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 xnKZFXc9dMHv for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:50:43 -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 B2A2612D09D for <ipv6@ietf.org>; Tue, 24 May 2016 01:50: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; 24 May 2016 08:50:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 50F7E9CC4F; Tue, 24 May 2016 01:50: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=DoiUUdEbDLMMltrLfYbmxoZyax4=; b= DH5OthSjpDJo8T02J3Yyf1w4nNjsINkDl5vCFDa8pBWpZI/PGgG71FX2vHT0hwZu W5q1cu8VElDsdiAcUvLUz36EEDr6exQAuSSXKem+e6B/ItCF+9D3ddA8nLVhIUsx aqApa0nfaqCA1xAe9KBlGg+Z7dVTr5FntRzPN+/Bb18=
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=Z4r3BpsCoB+OuNQjyH/mCCn+Kn uGerL6mo/JHe2ycJNBv89s6Bub5YfjAt00uRQ0wAN73wwkzrh1fCHzGLMLu3/Dhg we328R5xk8k8XK+3Z0MZNn10ktU/L1V4ai3nihMjUfnhESQfmlJ5CpKBq6h+76RV 1dkxSHHX0HQ3NNz9A=
Received: from h.hanazo.no (unknown [173.38.220.37]) (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 CF1D89CC4E; Tue, 24 May 2016 01:50:40 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 114B316E3FC2; Tue, 24 May 2016 10:50:38 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement 
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_358959C6-A286-41E5-94A6-8357725CC574"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <m1b57qM-0000HYC@stereo.hq.phicoh.net>
Date: Tue, 24 May 2016 10:50:37 +0200
Message-Id: <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HMjLBgt31O8rKZ9ss3qRg-M5JXw>
Cc: draft-ietf-6man-default-iids@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, 24 May 2016 08:50:45 -0000

--Apple-Mail=_358959C6-A286-41E5-94A6-8357725CC574
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Philip,

> In your letter dated Mon, 23 May 2016 11:37:02 -0700 you wrote:
>> I don't know the general sense of the wg on my suggested text.  If
>> it's just deemed to be redundant or possibly out-of-scope but
>> otherwise acceptable while it makes some others much happier (on =
which
>> I'm quite sure) I think it's still worth considering.  But I'm not
>> pushing my specific agenda in proposing this text, so if the text
>> itself is so controversial I won't argue for it.
>=20
> The problem I have with this draft and the discussion surrounding the =
draft
> is that it starts somewhere in the middle.
>=20
> A particular device, say server or laptop, in a particular =
environment,
> trusted, untrusted, etc. results in a set of requirements for what =
addresses
> the device should have.
>=20
> Then we can map those requirements to particular technologies.
>=20
> Instead we describe and discuss a number of things we can do, but then =
it is
> upto the operating system software vendor or the operator or the user =
to
> figure out what goes where.
>=20
> We create an endless maze of SHOULDs where everything is possible. But
> too many options lead to non-experts getting lost.
>=20
> So in my opinion, a default-iids document should start with set of =
example
> configuration that map to a set of features that we want to support
> and then to a set of IID options.
>=20
> Then an implementor can start at the top, look up the type of device =
to
> support and find what needs to be done.
>=20
> For a selected class of devices, I'm a huge fan of using EUI-64 based =
IIDs.
> I agree that in general EUI-64 based IIDs are bad, but we can just as
> well write down when they make life easier.

are you saying that you'd rather have seen a v6ops style document giving =
recommendations for what type of IIDs should be used for an enumerated =
set of scenarios?

Best regards,
Ole

--Apple-Mail=_358959C6-A286-41E5-94A6-8357725CC574
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

iQIcBAEBCgAGBQJXRBXdAAoJEL7aWKiYQt92IhMP/A9ATXK/JmVNRClAnlB2tRJ2
UYAxHwg0kv9fbyAbpwnxZpWupADPYdAyfWZzlK14m3vJcjp+oa8PPuKyb+82XNMy
rbQfA7A7bdOnhi0gRgwA5He0DO+mzzRb0Eh4Cr45ER7PER+SWFl0NDjE0tsVC4uG
3xBBzPHwj6Ze3g3J2XgfJygBfKiOj7Yjv052Bmtets3JiyhZTiW9W6+yuw30r6W3
pEp/cEmAQn3JKrZTFcbMFfKa1Q+ugL9rDcQp5nsb+eQZIgs8I7Ikh0Pmux3dGD8E
C9PKT2k9/hfNpJoW5+6clZicohOPiPZCcvPphUtzhJhnrEMBOqVzvpi5X8Xd6NQp
9MD9t9jptqFz8iXyXZ2e8ibQAYYt+Q3zPQR5PrFFWRnjKBj3+tqG+ONaOnkSLYNc
iHT+rUXjtfSBPgGqioxDG4BI93ose8pv6fhInfRyRN55jQttKI1/Z1AqiKntcCko
d1s6zFs54+FiyFBOMsyhTYz7hZWgaZh/2ak8uC6e65J7y+d8hbf7AKwVtLWWyu9y
2o9mPMU/vsaHQk4+lxfD2DiKfE8qXwfg/r8CRvRrAnCFFkD9cArnOmZSWYHc4NtZ
sbygM4FSW7hWA18Xk79ytJJ9HsuaK6iu4PZ5YEYxuMhy5OUvkJdKoE8UEQEdt0/a
kN0yCrCHDvweMhuA32Bm
=u2bq
-----END PGP SIGNATURE-----

--Apple-Mail=_358959C6-A286-41E5-94A6-8357725CC574--


From nobody Tue May 24 01:55:06 2016
Return-Path: <alexandre.petrescu@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 991D512D0EB for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 3D4aAdHLoNmf for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 01:55:03 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EB4E12D0BA for <ipv6@ietf.org>; Tue, 24 May 2016 01:55:03 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4O8t1RK013779 for <ipv6@ietf.org>; Tue, 24 May 2016 10:55:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 99BB5207485 for <ipv6@ietf.org>; Tue, 24 May 2016 10:55:10 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8FFD5201DD3 for <ipv6@ietf.org>; Tue, 24 May 2016 10:55:10 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4O8t066007465 for <ipv6@ietf.org>; Tue, 24 May 2016 10:55:01 +0200
Subject: Re: 6man w.g. last call for <draft-ietf-6man-default-iids-11.txt> - hybrid addresses
To: ipv6@ietf.org
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CAJE_bqdZ_D7jsDdWQ2FJpLH9cXveYfcye0W2J_mSi-7bYBrOKA@mail.gmail.com> <B849F263-9F99-48E8-B903-8FE7D2CDF277@cooperw.in> <CAJE_bqd1AWOuwvQcGzHg+dAWoump29g14HEA1BoVErXDXSMxaw@mail.gmail.com> <573BCFD0.8090801@si6networks.com> <CAJE_bqfKUbO7C6LnxOOUCVBU9e679_=159Yu6Ti0zhOGDuw98Q@mail.gmail.com> <A1111BEA-C14C-4574-9214-3D9B5500FEA1@cooperw.in> <CAKD1Yr23S4yHM=31VXTJq7t11P3__GEbbRhM0c085gBjQEGi-Q@mail.gmail.com> <19ae94cd-849f-0622-54bc-42cbad51368a@gmail.com> <CAKD1Yr1YN6SnUNp0HKqTNg6G0egkLveCOTG_7pHo9Zq3OFP4=g@mail.gmail.com> <a65c2157-044e-6207-314e-833313e5d458@gmail.com> <CAKD1Yr0e3NuLCFK2N35FymoQmx4UUH-83rkQxtUB1RJbwNzY9A@mail.gmail.com> <E13EFAE7-2191-4B19-957D-B7DBA78B6C78@employees.org> <CAJE_bqczeopdc2qRU2aiY9-+6zS3oKzhJVPWQyQHJ-k46Nr5KQ@mail.gmail.com> <574210D2.9030903@si6networks.com> <fbfac489-f56a-0ece-d1c6-b17cdc6846d8@gmail.com> <6df1567c-88a9-3995-7017-da71bc5dcea4@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2242a4d9-88e0-0167-9abe-36b78feb6b78@gmail.com>
Date: Tue, 24 May 2016 10:55:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <6df1567c-88a9-3995-7017-da71bc5dcea4@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/u88CNXRF3hd-m6AGgIAYb83jEBs>
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, 24 May 2016 08:55:05 -0000

Le 24/05/2016 à 01:51, Brian E Carpenter a écrit :
> Alex, On 23/05/2016 21:13, Alexandre Petrescu wrote: ...
>> (privacy may be a valid reason; but hybrid addresses mixing IDs
>> from different layers is common elsewhere, wonder why opposing)
>
> Well yes, it seems to be that we have all followed the OSI method,
> where a TSAP is an NSAP+something, etc. But that isn't actually a
> rqeuirement of the OSI model, iirc. Privacy would indeed argue for a
> layer N+1 address not to be a simple extension of a layer N address.
> That was not a big consideration in the past, unfortunately.

Is it only about [N; N+1] or also about [N; N] (e.g. an IPv6 address 
embedding an IPv4 address)?

Alex

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


From nobody Tue May 24 02:40:26 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 6E17912D64E for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 02:40:25 -0700 (PDT)
X-Quarantine-ID: <m9fBB2kTo88c>
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 m9fBB2kTo88c for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 02:40:23 -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 73BD112D0CE for <ipv6@ietf.org>; Tue, 24 May 2016 02:40:22 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #91) id m1b58oz-0000EoC; Tue, 24 May 2016 11:40:17 +0200
Message-Id: <m1b58oz-0000EoC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: default-iids: Closing concern regarding stable address requirement 
From: Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
Sender: pch-bBB316E3E@u-1.phicoh.com
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> 
In-reply-to: Your message of "Tue, 24 May 2016 10:50:37 +0200 ." <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> 
Date: Tue, 24 May 2016 11:40:03 +0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8mTJaNg7ZWUnhuWnT21P08tw80U>
Cc: draft-ietf-6man-default-iids@tools.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, 24 May 2016 09:40:25 -0000

>are you saying that you'd rather have seen a v6ops style document giving 
>recommendations for what type of IIDs should be used for an enumerated 
>set of scenarios?

Yes. I think we need such a document. There are too many options to 
configure IIDs. 

And I think that would also structure the current discussion. I.e, what
requirements do we have with respect to addresses for mobile devices and
what technologies do we use for that. 


From nobody Tue May 24 02:49:40 2016
Return-Path: <rogerj@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 4FDE012D0CE for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 02:49:38 -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 Y7zP2U-qh2KW for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 02:49:36 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::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 688F912D0A8 for <6man@ietf.org>; Tue, 24 May 2016 02:49:36 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id e126so4097724lfg.2 for <6man@ietf.org>; Tue, 24 May 2016 02:49:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to; bh=wrrDQ4y5IyxUe2ueMio/eH46s1ElavIcbtnukf60QoU=; b=skrwA/pvlznLrUtnc9ovl9Y22uOkyImnEvmmAyniD6khB0xFOtBsIypq6Akb3b8D/C SkFge/szWKPsfyQ921tOBBsqSE+lolvJj1tpj9L5scLg47MnbPs9E5X3h6IpEslLQwvt o+9GL2J0C7HI14XRjkG+qRx+5aueQcE2ol7m3hK/5dnFaFxRoOac8oxu3WcB+Qp7HLzM xalTxkObhH4tc0u6in3Ej3F7gUBxjH3F3xrg93I9+Ba794P9eupLymCF1UkKsM3Ll28l /C8lnsi1Z+bm17QqzPY2LHlvm3ZlrFYhrnSKnnglYyw54CCYVG0L0afDjDnXv2xAdUY4 uy4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=wrrDQ4y5IyxUe2ueMio/eH46s1ElavIcbtnukf60QoU=; b=A1eVqtsLm6bdb6EqoQ6amtLT9uOG4tDNh4Deqr+wnqGThpESdhTJ8t1LsQI1JpqfZE wzgAdfHMYTs6TxvG0m3aNj4wg2G+johXmaE2fO71TiXyTmtn7bVjDs6qrHjGXR1zqbyn l7Mgg0hELVMFX30povqoCpPDM/LzYAYxiI2TZ0WwNM522K4gI8Ss+bBsdrn0SYcV2uYE j7vQ25zaGcc0VW/c3xK4sjjb5wJDJmIKHttiiBR3q+L1LyD0QHc/A03SQzR2YVEhZ2Km 9MTD4PuM06RGDkJYvw9E5nmJFrGOAguQZnvDiRtH442oxn0wlzgKlCIktpT6UVIZI2B0 FcQg==
X-Gm-Message-State: AOPr4FVfOqTHsBz2e/8IYVlP/ora69uDGmU4gU4e7S7cHJ4QoEjeHMybp3jfA3AbWHESvHHV/oHtA+1FfEFypg==
MIME-Version: 1.0
X-Received: by 10.25.86.137 with SMTP id k131mr7581977lfb.97.1464083374462; Tue, 24 May 2016 02:49:34 -0700 (PDT)
Received: by 10.25.21.232 with HTTP; Tue, 24 May 2016 02:49:34 -0700 (PDT)
Date: Tue, 24 May 2016 11:49:34 +0200
Message-ID: <CAKFn1SGs2NRF4Kb4wS8srG1fAEEHWFz_ERktsH0dCSDO3up+Mw@mail.gmail.com>
Subject: FYI - a MLD presentation done at RIPE72 @Copenhagen
From: =?UTF-8?Q?Roger_J=C3=B8rgensen?= <rogerj@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2YIjqDLUt1bK24MvkPOA9tDVyx0>
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, 24 May 2016 09:49:38 -0000

Enno Rey holds a presentation on "MLD Considered Harmful" here at
RIPE72, might be of interest for some of you?

https://ripe72.ripe.net/programme/meeting-plan/plenary/
https://ripe72.ripe.net/presentations/64-ERNW_RIPE72_MLD_Considered_Harmful_short.pptx



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no


From nobody Tue May 24 11:45:24 2016
Return-Path: <mcr+ietf@sandelman.ca>
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 DF87712D994 for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 11:45:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.327
X-Spam-Level: 
X-Spam-Status: No, score=-3.327 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, 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 DuuCzBMT-poW for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 11:45:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E5D12D99D for <ipv6@ietf.org>; Tue, 24 May 2016 11:44:09 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 3DEE92009E; Tue, 24 May 2016 14:50:27 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 46D2D638BF; Tue, 24 May 2016 14:44:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: otroan@employees.org
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
In-Reply-To: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 24 May 2016 14:44:08 -0400
Message-ID: <6332.1464115448@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/A4ommikgt99-ZUcx9hmvaseneZ8>
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, 24 May 2016 18:45:23 -0000

--=-=-=
Content-Type: text/plain


otroan@employees.org wrote:
    > I don't think 4941 _requires_ public addresses. it specifies the
    > behaviour _if_ you have them.  it is up to applications how the use the
    > available addresses.

I think that we need to, after this effort is over, come back and ask if we
have the right APIs for applications to actually do this.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEVAwUBV0Sg9ICLcPvd0N1lAQJzcAf/c53fXHo6Dykmvwalt0DIwXtZL3kAjzZv
LtB9YCGgh3In5HbW/ymS6jpusUnm9XKNvlVdZQxoWhHTBGPFSYdrFDGiHnD26CJO
upXpq7XbZizyTEMvZjwy5PP77pYOAoMawtJnLGYyo9aOod7F/yXdidCLzx1ZwutR
/5bn058KfiHZHkmJ4DAI3udE1iVBfpafSpxY4vJLKJJ+fUvCjtmdyg6IuHJoP/50
kQK2/+KY3xfaheIRlCIRQBeeESNoQ3/xkdwN5pcywiZIC/96gxEm/2+3CwsiUFRx
sXxjNSOowWKVAh5qqB4D/bVF1XEuhHbUq+NyXQqWHVn06K5vJDx7EA==
=AcOP
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue May 24 13:43:18 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 AD86712D54B for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 13:43:16 -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 x2t1VQtCn1os for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 13:43:15 -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 018B212D552 for <ipv6@ietf.org>; Tue, 24 May 2016 13:43:14 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id qo8so10023640pab.1 for <ipv6@ietf.org>; Tue, 24 May 2016 13:43:14 -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=OZlHk58No7MUSwMOSV28qOwI9qGsKvWe16ckNEJ3AfE=; b=f2LEvJnsVTUEn8XUgsVbQynTSUHkxcE1KwrhPFAocsfeq2sv0MYRUWGvMjzrFpD0zs uUweAOLV8RQAIfh8HYhtTXQaDaKpOkQwNe3JivwJyzhmddTBhdXI/720Wr7qW+NHuZZq I/6GGAYkPvveVYfXPky6MmfIqZg1IFYmTjir/WWaF1TRVPVxdvCqy/DrnoldnKUIcgxR 3lLR/F5qAPpk9WFUULBpzgxFWRGtCvR04saV2WJYnQCXH+aqcEdDbNEnduZWHsyt6B/N qtjL1P7IjR2+ShD05YNw/w9n8QtY5YKQdrQFVKNpe2VHBkzs0M9HrAotfpkxyARkPhqZ /VLg==
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=OZlHk58No7MUSwMOSV28qOwI9qGsKvWe16ckNEJ3AfE=; b=ER5DB9FwTP72WU+nI3gz3WNphaa+jEKgO2RzhrdJOEsU6D6iltzSnbhID6oEtAJWuI ZJlhaKp8TIVyloP4SQKQhY+QrlJTflzEbf9GZHVW7YVtTFUy7CndPXyDW3pZfF/ZiKPv g/C4Xp3P/w4FXHi2yXLD4wPJbX+lnhvdeHrQxi/irsXwEdG/fZVFmBbXVq1/7pw5mgW7 r62aYLn1656u80pPba6ea40e8ko0FX3z+mwcIjFzcNY+of+fpJLDYaLpQHDBeS0zS5ow OMWS/8E3tipyJ2tezJ3XJPyMU5VCSfQ0jxTc1PKSw29YhvahjyjkeX0LB0F3kIBcjyIF rYwQ==
X-Gm-Message-State: ALyK8tKZxzPxHWAoBN/h4l8jV9Q07pMSgTCz9cvBr7oQZmWoXohF+lPlLuIEzXdrH7LB2Q==
X-Received: by 10.66.237.66 with SMTP id va2mr284758pac.2.1464122594473; Tue, 24 May 2016 13:43:14 -0700 (PDT)
Received: from ?IPv6:2406:e007:51cc:1:100e:1d3f:97a2:62d3? ([2406:e007:51cc:1:100e:1d3f:97a2:62d3]) by smtp.gmail.com with ESMTPSA id l123sm56444971pfl.36.2016.05.24.13.43.12 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 13:43:13 -0700 (PDT)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: otroan@employees.org
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2542106f-1e54-9aaa-bac0-6792b5783cc6@gmail.com>
Date: Wed, 25 May 2016 08:43:17 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AciNz7sQh6n-adA5Sp6JpBVW_TM>
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, 24 May 2016 20:43:17 -0000

Ole,
On 24/05/2016 18:59, otroan@employees.org wrote:
> Brian,
>=20
>>>>> As we=E2=80=99re finishing the edits on the RFC2460bis, RFC1981bis =
and
>>>>> RFC4291bis, we will initiate working group last calls with the
>>>>> intended status of Internet Standard. We will do a single last call=

>>>>> for the updated documents (RFC2460, RFC4291, RFC1981) and a separat=
e
>>>>> working group last call for the unchanged documents (RFC3596,
>>>>> RFC4443, RFC4941).
>>>>
>>>> After reading RFC4941, it looks like it really needs to be updated, =
and
>>>> also that if one were to publish RFC4941 in 2016, a fair share of te=
xt
>>>> would be edited.
>>>
>>> Yes, but we're not. We're reclassifying it as Internet Standard.
>>
>> And that's a problem, because it directly implies that temporary addre=
sses
>> are *additional* and that is, from recent discussions, a MAY not a MUS=
T.
>=20
> I don't think 4941 _requires_ public addresses. it specifies the behavi=
our _if_ you have them.
> it is up to applications how the use the available addresses.

It directly states that 4941 addresses are *additional* to "normal" SLAAC=

addresses. That's exactly the point that Lorenzo has been, er, going on
about. So I really don't believe we have consensus that this is desirable=
=2E

> (somewhat tangentially, you can also argue that a lot of the benefits a=
nd point of doing IPv6 in the first place goes away if you don't have sta=
ble addresses, oh well.).

Yes, in many scenarios, but not in the coffee shop type of roaming scenar=
io.

>=20
>> I suggest removing 4941 from the list.
>=20
> is there a cultural shift in the IETF? are we trying to make standards =
much more prescriptive in specifying _how_ we want people to use them? as=
 opposed to containing ourselves to specifying protocols and mechanisms?

In this case I'd like 4941 to be *less* prescriptive, by removing the sta=
tement
that these are *additional* addresses.

> are there real problems with 4941? or are we unhappy with how users/imp=
lementors are using the resulting addresses? or are we worried about _how=
_ they might use them or not use them in the future?
>=20
> what are you trying to achieve by not making 4941 Internet Standard?

I would like to see 4941bis as Internet Standard, with the bit that
doesn't have consensus removed.

    Brian


From nobody Tue May 24 15:26:23 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 ABD6512D1DA for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 15:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 ZSdkLItFf43U for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 15:26:21 -0700 (PDT)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::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 839F812D175 for <6man@ietf.org>; Tue, 24 May 2016 15:26:21 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id r140so41376052vkf.0 for <6man@ietf.org>; Tue, 24 May 2016 15:26:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to;  bh=GY8nGMcwdVzc9i++Hd3vP8Z42SC2G30RP9816epBiZU=; b=kqSuHsyNAbiDt5rPYfqnjhhrTS3vbTo3klm3OFAbzLZeqWLEv5WoKVke0sxsD3t/DY p7OjihCGuX7qObioi5ekjA9OQpeoEfvXY/Tiri/U8ic6WiMXEncNgIseHQn/Kalu4oXc Q9qF3z3kBL0LbEAmx2pxzZMoLTXl0H3c0PZ1Y6tX/p3czoVPlNKOggO23SvxpSrLOvyM QBGX1zZjFLNb3J9kfblRtorgxxWHsRohVGZTa3hQwi/VgaIrNhrujdhjbk3UHF9qWhKs 41qymFMYAexRyCNRQMx1VrXMDqdEuEiVGytnshLkIyMDZaJlnWC32jbI9gv8q9bETPZj xZZQ==
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:date :message-id:subject:from:to; bh=GY8nGMcwdVzc9i++Hd3vP8Z42SC2G30RP9816epBiZU=; b=NRckPqXU96w/s0lhf2OsI2VhimPUX7MF4sHwGABbD4EOkiIP0shpJbxC77b9OkIVpg ew9oWKFeiLCpHh5/dClRfo5pXYid7W7vDAcVqzDjbd8mprZLjkl+ZVTdCPqVy+voSGdH GkJtSxl79xTxFYa++SwJyOUj7KY6EfQuOCx+87MPtFKbB0rt1fZc4mHFrMZPq8RCzuvk WFvwRajvOInjstDHXSQu9mKDS776TnK3mdnXpDXUdtENcOC94UTdmxWNOcBHIqexm//4 11QW0a1XqSKm9X9lWKs+L7yMDH2eHChZKo3FJJPKjwTSduh2sMDkrW9UQHDCF7ZuhMhT rEQA==
X-Gm-Message-State: ALyK8tK1EPKbfl+JFwFQsYHEYmkiEYB+YIcczlXJ9sIHrXcAFJFBUotg9Zm/Pv2g64yu9OEgvPE5exlW9gZ1Sw==
MIME-Version: 1.0
X-Received: by 10.176.2.151 with SMTP id 23mr297876uah.106.1464128780589; Tue, 24 May 2016 15:26:20 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 24 May 2016 15:26:20 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 24 May 2016 15:26:20 -0700 (PDT)
In-Reply-To: <CAO42Z2xwcaU+KyZ-W1+GJzQyvY4Bvax=uiP48WEsesu-ufhscg@mail.gmail.com>
References: <CAO42Z2ypgRfFxWhmeq0WLg_n=ufA5c5mROJjsC-z2766_4242g@mail.gmail.com> <CAO42Z2wqwm4zXe5QKQqAP7DPP=-kxUL5ceuDhSKndBPHM+DVFQ@mail.gmail.com> <CAO42Z2y6aSLDRHHDmRK58rJ2RwFaTazscTkVC1YVT5xd7mUB6w@mail.gmail.com> <CAO42Z2x=ARtxrznFERZA__APnwSkYk6NE_z-YknkWPEkh1Vovg@mail.gmail.com> <CAO42Z2zk3ZX2bGYT3G9_TCgeQMbsx2GJQ7TdgSBKZFL60xV2DA@mail.gmail.com> <CAO42Z2z5KYUg8N7ptZ6ga2H3SoZRMCRdOfP1Q4s8Ay9PmaSHzw@mail.gmail.com> <CAO42Z2yQnN_6D-f9xTde2WgJzGP=mkEo-PPHjnXN6h6FL_ud7w@mail.gmail.com> <CAO42Z2yFVDriOn9uAHzNgkFLjQf_2Qs0FHNPQcbj2k70C5ztDg@mail.gmail.com> <CAO42Z2yWPCz438H8b8CcACptciU80etn8w6m2POX8H6tVR9xRg@mail.gmail.com> <CAO42Z2y4_BVBLHxmRwtg2c7F3gjqE=mV3pn4ZYFByfxTp2HiRw@mail.gmail.com> <CAO42Z2zCx1ZCFqyDmt64LvX9YV_1aAd4q=CyTEGq13b+gFm06Q@mail.gmail.com> <CAO42Z2xS_6z_0HvYotM2mCd=RSMNqUv_dC91LiCO8VVPYE9_yQ@mail.gmail.com> <CAO42Z2y2xJ2k_ig5xBRxfiUrag-9mXhdxpS7gw-2fXuCMicAZA@mail.gmail.com> <CAO42Z2wK-TUPc_BDoimivE_hKNrSiUOQDWtu0b6YtMCUZCGHBA@mail.gmail.com> <CAO42Z2y258yrf37eHeg7f4Y==Wzg_q5onizLRPf40RaZef4fJw@mail.gmail.com> <CAO42Z2y3KCi00SsqM63U0vigDNk-RxOhpWAeXGBuazzaeu+szw@mail.gmail.com> <CAO42Z2w0o6kbECBfRD5MSH36Cc-s8CzbAgKi8HLxuQj8GLYCdw@mail.gmail.com> <CAO42Z2yV+HG7r3oLiRF5-azjY3UwBAkFyYK2Sr2cRQY0L3Qf0A@mail.gmail.com> <CAO42Z2xRcCmxGztKzpXcs+_QMb=nipijJ=y+rOhAg1_29zT11g@mail.gmail.com> <CAO42Z2xEC5+yVjw8xFh9axvt5djyj3XXuU-_-dBCaUJCMwOjdQ@mail.gmail.com> <CAO42Z2zKhwrnCte_15M7D2fvP-bo9fkZjX3skPNN=XEOg58exA@mail.gmail.com> <CAO42Z2xLxPeAS67gcJiRQU7=mH9cpV=2n3FuXkkzqhCV=1z71A@mail.gmail.com> <CAO42Z2xZzfuwY7HR1qu3T12yrHr3idqEo_KmY0sW6R1i48RvRA@mail.gmail.com> <CAO42Z2xwcaU+KyZ-W1+GJzQyvY4Bvax=uiP48WEsesu-ufhscg@mail.gmail.com>
Date: Wed, 25 May 2016 08:26:20 +1000
Message-ID: <CAO42Z2zf+S-BchXTcwUh8VYu5orFmLzN5CBSCcfE3eoG5wxG5Q@mail.gmail.com>
Subject: Results of my detailed review of draft-ietf-6man-default-iids-11
From: Mark Smith <markzzzsmith@gmail.com>
To: 6man@ietf.org
Content-Type: multipart/alternative; boundary=001a113d0fc8df5fc005339e0bb9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/D4hwJKbaSl50FvFSv3fraXtMwHg>
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, 24 May 2016 22:26:22 -0000

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

Hi,

So I said I'd do a detailed review of it. I haven't done it yet however,
because going by the recent discussions, I now don't think it is close
enough to its final form or working group acceptance to be worth the time
I'd spend unfortunately.

Regards,
Mark.

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

<p dir=3D"ltr">Hi,</p>
<p dir=3D"ltr">So I said I&#39;d do a detailed review of it. I haven&#39;t =
done it yet however, because going by the recent discussions, I now don&#39=
;t think it is close enough to its final form or working group acceptance t=
o be worth the time I&#39;d spend unfortunately.<br></p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>

--001a113d0fc8df5fc005339e0bb9--


From nobody Tue May 24 19:58:34 2016
Return-Path: <weigengyu@bupt.edu.cn>
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 634FC12D1C0 for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 19:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.888
X-Spam-Level: 
X-Spam-Status: No, score=-2.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, STOX_REPLY_TYPE=0.439] 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 cCaiFTvK1Jrz for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 19:58:32 -0700 (PDT)
Received: from mx1.bupt.edu.cn (mx1.bupt.edu.cn [211.68.68.2]) by ietfa.amsl.com (Postfix) with ESMTP id D019A12D0FD for <ipv6@ietf.org>; Tue, 24 May 2016 19:58:31 -0700 (PDT)
Received: from mx1.bupt.edu.cn (unknown [127.0.0.1]) by mx1.bupt.edu.cn (AnyMacro(G7)) with SMTP id 7BC5C19F404 for <ipv6@ietf.org>; Wed, 25 May 2016 10:58:30 +0800 (HKT)
Received: from WeiGengyuPC (unknown [114.255.40.27]) by mx1.bupt.edu.cn (AnyMacro(G7)) with ESMTPA id CA3E519F3DC; Wed, 25 May 2016 10:58:29 +0800 (HKT)
Message-ID: <E87615B9D8A8479CB545BA12980A7225@WeiGengyuPC>
From: "weigengyu" <weigengyu@bupt.edu.cn>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Fernando Gont" <fgont@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC> <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC> <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com> <573BD140.8000607@si6networks.com>
In-Reply-To: <573BD140.8000607@si6networks.com>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
Date: Wed, 25 May 2016 10:58:29 +0800
Organization: BUPT
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pAIfSUcQot4I3cpwnonhql2jYTk>
Cc: 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, 25 May 2016 02:58:33 -0000

Hi Fernando,

Would you please provide the published refereces of Alfred Hoenes -- IIRC, a 
mathematician.
IIRC, he noted that a hash function is simply one possible way of a PRF.

It is interested for the proof of Hash function to be a PRF.

Regards,

Gengyu WEI
Network Technology Center
School of Computer
Beijing University of Posts and Telecommunications
-----åŽŸå§‹é‚®ä»¶----- 
From: Fernando Gont
Sent: Wednesday, May 18, 2016 10:19 AM
To: Brian E Carpenter ; weigengyu
Cc: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt

On 05/16/2016 04:08 PM, Brian E Carpenter wrote:
> Hi Gengyu,
>
>>> RID is not random or random identifier according to the context above.
>>>
>>> F() is an inreverse function, not a pseudorandom function.
>
> I agree that this is incorrect use of terminology; an irreversible hash is
> not mathematically equivalent to a pseudo-random number generator. But the
> effect is the same: an attacker has no way to predict the next F(x) or to
> obtain the value of x. As far as practical engineering goes, F() can be 
> treated
> as a random number. So I don't see why this invalidates the use of RFC 
> 7217.
>
> You could submit an erratum for RFC 7217 at 
> http://www.rfc-editor.org/errata.php#reportnew
> so that the terminology can be corrected when the document is updated.

FWIW, the term "PRF" (as *opposed*) to PRNG was suggested by Alfred
Hoenes -- IIRC, a mathematician. IIRC, he noted that a hash function is
simply one possible way of a PRF.


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







From nobody Tue May 24 21:22:23 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 168DE12D5FE for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 qRhDQN0gRLPz for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:22:21 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 6261612D5D8 for <ipv6@ietf.org>; Tue, 24 May 2016 21:22:21 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id h19so36656578ywc.0 for <ipv6@ietf.org>; Tue, 24 May 2016 21:22:21 -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=0EBVE7ojv9Xo2ZDHlKEoNZVbHAu0AgV+oOXkGuNTkjk=; b=Q6qKnlDGjNoDpwwOE7LOHbzEP6gak5vGNId22X99i+OHSxMl5gpvVm9s9rXdpMKJjU Oe9xCx8IyAb1P/xGaoQi7ogyf25MxJboAEEsSHwlIamOXqxNApghCdZHZ3cHMSaCJN5J q97PZewX2mBrgT/Sphy/T/XhqVy3CdaSRVhALx3cLmDUxr4kkIlsb3GkNCvltNYMRKTg 0OYJAy6dbOc43KiBhsCY5KeeXiWcrOLZt3x5I3mWPN16nrqAQE1m71vzhjd/4Lqnk+pb nn5Cw8OzA491ept9PXRdx2N6+GN/mInpzagRl6twNn0Ry4O0oIsJlQ2GWw4Sr4ZhaonY O59Q==
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=0EBVE7ojv9Xo2ZDHlKEoNZVbHAu0AgV+oOXkGuNTkjk=; b=bKcbhUhVC7X5dnuCBQTNvbh8G4SAaUxPj4gJMGNPcKJJ+HkxABtR/WA90tumSoVm48 ETb7raHowzHxsxCRyPDG1y6xltDhyCuc+xTZGAgdMdD28lc9o+ZQeiMNWmTeI9lk80cd R6zO5uUMoRoHnLZJIjrveHgUBC6RPIlyDXRfl2qz26ZzV82GJbDgV36Yb4903SNC23iC mmnhYwTxHOEypCqhiwBlCEwLyRu9qKh85Pdvq8DSssSq1sTbegqjbhnqADUlNSBEVp5A 40NAXKrQF1eZyw3PvcafKBsbW5Qc94RIyhqnVccAIdiDdzCrYcFKGICeOYdEp+BWAUc5 dn0g==
X-Gm-Message-State: ALyK8tLIZ8clarTn6KwKLTH3u9nGGNpcZV/xgQxGFkdjN/xRyMh7YJbrfqslw+/JJGTBHvVqHOqdEcOp6h/KqFLC
X-Received: by 10.37.194.197 with SMTP id s188mr1060560ybf.186.1464150140369;  Tue, 24 May 2016 21:22:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Tue, 24 May 2016 21:21:59 -0700 (PDT)
In-Reply-To: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 25 May 2016 13:21:59 +0900
Message-ID: <CAKD1Yr0ciXOeKjXx0vw+vtxhsUr-BwecL7uV=MKupSH4X4CskA@mail.gmail.com>
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=94eb2c054ace047d0d0533a305a9
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PYaCdlx_tzxhNkeD3-vbJ-2qMkY>
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, 25 May 2016 04:22:23 -0000

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

On Tue, May 24, 2016 at 3:59 PM, <otroan@employees.org> wrote:

> I don't think 4941 _requires_ public addresses. it specifies the behaviour
> _if_ you have them.
>

RFC 4941 does require public addresses:

   1. The text explicitly says in several places that privacy addresses are
   "in addition to" public addresses.
   2. If you don't have a public address, critical parts of the
   specification, such as how to extend the lifetime of privacy addresses when
   receiving an RA, are undefined. An example is the text that says, in
   effect, "when an RA would extend the lifetime of a public address, then
   also extend the lifetime of temporary addresses".

If we want to reclassify it as is, we'll have to accept that the resulting
Internet standard document will only a) define the behaviour for privacy
addresses with a public address, b) say that privacy addresses should be
depreferred by default.

--94eb2c054ace047d0d0533a305a9
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, May 24, 2016 at 3:59 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">I don&#39;t think 4941 _requires_ publ=
ic addresses. it specifies the behaviour _if_ you have them.<br></blockquot=
e><div><br></div><div>RFC 4941 does require public addresses:</div><div><ol=
><li>The text explicitly says in several places that privacy addresses are =
&quot;in addition to&quot; public addresses.<br></li><li>If you don&#39;t h=
ave a public address, critical parts of the specification, such as how to e=
xtend the lifetime of privacy addresses when receiving an RA, are undefined=
. An example is the text that says, in effect, &quot;when an RA would exten=
d the lifetime of a public address, then also extend the lifetime of tempor=
ary addresses&quot;.</li></ol></div><div>If we want to reclassify it as is,=
 we&#39;ll have to accept that the resulting Internet standard document wil=
l only a) define the behaviour for privacy addresses with a public address,=
 b) say that privacy addresses should be depreferred by default.<br></div><=
/div></div></div>

--94eb2c054ace047d0d0533a305a9--


From nobody Tue May 24 21:27:42 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 0F49912D60E for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:27:40 -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 eeQ7Q-i6m4Pc for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:27:38 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::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 761F112D602 for <ipv6@ietf.org>; Tue, 24 May 2016 21:27:38 -0700 (PDT)
Received: by mail-pa0-x22b.google.com with SMTP id qo8so13529549pab.1 for <ipv6@ietf.org>; Tue, 24 May 2016 21:27:38 -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=N66cih9zkXmMszPNlGBhVlaIbMOvC63VR0ciACtorS8=; b=Ej5nYpJIvVbTjA79Xf6zZCaBciWFgJSBFnqjIPXgpfZ9ATIX0o75seTNlASmxh4vK1 xhluaajOWSLGjdcO1fyuZTN5MiNvZpO7njrFZgKs9CTxpR4mAocw5InuRo9Ec40kYPE3 4zxi2U1kO+QpOX7SPLY+y6oLbVdWwQ3yLFrD73NC7tTrLtwyDwNjiKHk/XpbEW24WtGU gX38RJmlQpGHGgkSUVZB8mrwjKsFxZ9Au4AL371y19z+9fGg0NjfaqoiBpIWP5wub+yC yAdCFKPnYR3qmc4Q9ZfeCJzbFkGKs33oB/PRW5WY5clCsXPOV/K7t99yBUFBYggIeDwU LSlg==
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=N66cih9zkXmMszPNlGBhVlaIbMOvC63VR0ciACtorS8=; b=fPvGLAyUMIx9992MIQt+n7YH/BIaC+ORAo5kMLxnhk/1iQZfr4vNiYbQV7eu1hd9C6 A6he44ThmTP6ToXiIWSolpkay+Mm72ZeNX79J+jLsfN/wGMX13K6ea0zWDNcFbUFMnzu x0HMBbW2sWVG3DPKFIFLSzVrKa535ZfMV6GpNQQl+mZNSrECZgE3rAvA+UPjrA/M2IGu uy2A8OhwN8a8fY/FgfaYBS9KhvGcS3m65ckaekWIX4q7nXFa/NuzohfF8ZUPY7Oke7zU MNj17dXuRXgrm5eBxguQ3vCUwMscAxlgz3xHMq20+z4mcJaOZKBG5/oMYjokp4qBm1jV YGFw==
X-Gm-Message-State: ALyK8tJUXyvp0i1miMVEFAkYm/nMUGLOGbzB6wMKDYRGua01+NOl7f0BnAGa0Fm1Maq1yg==
X-Received: by 10.66.21.102 with SMTP id u6mr2678514pae.118.1464150457963; Tue, 24 May 2016 21:27:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:51cc:1:7452:e067:b14f:2733? ([2406:e007:51cc:1:7452:e067:b14f:2733]) by smtp.gmail.com with ESMTPSA id 7sm57862081pfe.88.2016.05.24.21.27.35 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 21:27:37 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
To: weigengyu <weigengyu@bupt.edu.cn>, Fernando Gont <fgont@si6networks.com>
References: <20160428004904.25189.43047.idtracker@ietfa.amsl.com> <CD39E9F1-4060-4884-91B3-5A974C3FFFF7@cooperw.in> <8E1CCE051EDF4491953D6E093809DA68@WeiGengyuPC> <2157FA8F808D4997BBF9AECD1B8DA52A@WeiGengyuPC> <0d4da5aa-ff7b-6d90-8a9e-f4cf5f2fe50f@gmail.com> <573BD140.8000607@si6networks.com> <E87615B9D8A8479CB545BA12980A7225@WeiGengyuPC>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <67c67a11-2c60-88e9-b00b-b29c19e705be@gmail.com>
Date: Wed, 25 May 2016 16:27:41 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <E87615B9D8A8479CB545BA12980A7225@WeiGengyuPC>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oflcBs4ReWHfdv59dCtnRFgEWQQ>
Cc: 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, 25 May 2016 04:27:40 -0000

A few years ago I found that the academic literature on hash functions se=
ems
extremely weak. Actually a very good theoretician of randomness that I kn=
ow
referred me to a paper from 1951*. Most of the "literature" appears
to be experimental results ("this algorithm seems to work better than
that algorithm").

http://www.isthe.com/chongo/tech/comp/fnv/index.html for example.

Regards
   Brian

* J. von Neumann, Various techniques used in connection with random digit=
s, National
Bureau of Standards Applied Math Series 12, 36-38, 1951.


On 25/05/2016 14:58, weigengyu wrote:
> Hi Fernando,
>=20
> Would you please provide the published refereces of Alfred Hoenes -- II=
RC, a mathematician.
> IIRC, he noted that a hash function is simply one possible way of a PRF=
=2E
>=20
> It is interested for the proof of Hash function to be a PRF.
>=20
> Regards,
>=20
> Gengyu WEI
> Network Technology Center
> School of Computer
> Beijing University of Posts and Telecommunications
> -----=E5=8E=9F=E5=A7=8B=E9=82=AE=E4=BB=B6----- From: Fernando Gont
> Sent: Wednesday, May 18, 2016 10:19 AM
> To: Brian E Carpenter ; weigengyu
> Cc: ipv6@ietf.org
> Subject: Re: I-D Action: draft-ietf-6man-default-iids-11.txt
>=20
> On 05/16/2016 04:08 PM, Brian E Carpenter wrote:
>> Hi Gengyu,
>>
>>>> RID is not random or random identifier according to the context abov=
e.
>>>>
>>>> F() is an inreverse function, not a pseudorandom function.
>>
>> I agree that this is incorrect use of terminology; an irreversible has=
h is
>> not mathematically equivalent to a pseudo-random number generator. But=
 the
>> effect is the same: an attacker has no way to predict the next F(x) or=
 to
>> obtain the value of x. As far as practical engineering goes, F() can b=
e treated
>> as a random number. So I don't see why this invalidates the use of RFC=
 7217.
>>
>> You could submit an erratum for RFC 7217 at http://www.rfc-editor.org/=
errata.php#reportnew
>> so that the terminology can be corrected when the document is updated.=

>=20
> FWIW, the term "PRF" (as *opposed*) to PRNG was suggested by Alfred
> Hoenes -- IIRC, a mathematician. IIRC, he noted that a hash function is=

> simply one possible way of a PRF.
>=20
>=20


From nobody Wed May 25 14:28:53 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 C59E412DDB7 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:28:51 -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 iPLWt2PChw0h for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:28:50 -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 0E05C12DDB2 for <ipv6@ietf.org>; Wed, 25 May 2016 14:28:50 -0700 (PDT)
Received: from [192.168.123.130] (unknown [179.40.185.202]) (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 B181880099; Wed, 25 May 2016 23:28:41 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5743864F.2080705@si6networks.com>
Date: Mon, 23 May 2016 18:38:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Dn8owwJQLTgaJA1uEENW473d-EU>
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, 25 May 2016 21:28:52 -0000

On 05/23/2016 04:32 PM, Brian E Carpenter wrote:
>>    [RFC4941] implies,
>>    throughout the specification, that temporary addresses are generated
>>    and employed along with temporary addresses.
> 
> s/temporary/stable/ in the last line.
> 
> Apart from that, I suspect that this draft tries to do too much and will
> therefore be controversial.
> 
> An alternative is for it to say much less, e.g. only this, replacing
> sections 3 through 7 and most of 9.
> 
> 3. Update to RFC4941
> 
>    The temporary addresses specified in [RFC4941] MAY be used alone,
>    without configuring any stable addresses. In particular the word
>    'additional' is deleted from bullet 2 in Section 3 of RFC 4941.

If we don't set requirements, then using the same IID in multiple
prefixes is fine, and  activities that employ different addresses
configured on the same interface could be correlated.

Besides, there would be no guidance other than RFC4941.


> P.S. My personal experiment in running my laptop for several days
> with no stable address has been completely successful. Including the
> fact that my prototype of the Anima signaling protocol crashed after
> a while, because the address it was relying on went away, which is of
> course the expected behaviour.

So, the question is: can this be considered "acceptable" behavior?

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





From nobody Wed May 25 14:29:08 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 6A44212DDC7 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:29:06 -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 0qASE97kRh-C for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:29: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 57F7212DDC0 for <6man@ietf.org>; Wed, 25 May 2016 14:29:01 -0700 (PDT)
Received: from [192.168.123.130] (unknown [179.40.185.202]) (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 0F2F680099; Wed, 25 May 2016 23:28:54 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Lorenzo Colitti <lorenzo@google.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57438806.9010902@si6networks.com>
Date: Mon, 23 May 2016 18:45:26 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1MWrHeMt2DAzf63gGu7irubX9SM>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 25 May 2016 21:29:06 -0000

On 05/23/2016 02:37 PM, ç¥žæ˜Žé�”å“‰ wrote:
> At Mon, 23 May 2016 10:10:57 +0900,
> Lorenzo Colitti <lorenzo@google.com> wrote:
> 
>>> Lorenzo suggested this text:
>>>
>>>    The recommendations in this document apply only in cases where
>>>    implementations otherwise would have configured a stable IPv6 IID
>>>    containing a link layer address. Configuring a stable IPv6 IID is
>>>    OPTIONAL.
>>
>> Jinmei had some better text, IIRC. Jinmei?
> 
> My suggested text was this:
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.  For example, this document does
>    not change any existing recommendations concerning the use of
>    temporary addresses as specified in [RFC4941], nor do the
>    recommendations apply to cases where the link layer address is not
>    stable (e.g., it is periodically randomized) in the first place,
>    nor does it introduce any new requirements regarding when stable
>    addresses are to be configured.

DO you consider the scenario where a hsot configures an address for
multiple prefixes, using the same IID? -- But that's one possible
outcome if you allow link-layer identifiers in IPv6 addresses -- even if
they are andomized.


  Thus, the recommendations in this
>    document simply improve the security and privacy properties of
>    stable addresses.
> 
> I've seen two responses to my suggestion, one from Fernando:
> http://www.ietf.org/mail-archive/web/ipv6/current/msg24495.html
> 
> and the other from Ole:
> http://www.ietf.org/mail-archive/web/ipv6/current/msg24512.html
> 
> And, basically, they didn't seem to be happy about it.  In the above
> text I just tried to make the scope of this document super clear
> (i.e., cases where the link-layer address is not stable are out of
> scope of this document), but it looks like Fernando didn't even like
> to mention it at all, or may even think we should explicitly recommend
> against that:
> 
>> The root of this problem is reusing a link-yaer ID at layer-3. THat's
>> bad, and we have to recommend against that.
> 

Please see my comment above, besides Brian's example of two different
layer-3 protocols embedding link-layer addresses....


> If this is a very important point of this document, all I can say is
> that this document should be revised to say this position explicitly
> and that revised version will have to get wg consensus.

Hasn't it always been the case of this document to recommend against
embedding link-layer addresses in the IPv6 IID?



> On the other hand, Ole seemed to say my additional text itself is out
> of scope of this document:
> 
>> I don't think this document is the place to to clarify that there
>> might be interfaces with only short-lived IIDs.
> 
> In a sense, I agree.  But as I said in my response, since this has
> been a central point of controversy in this last call discussion, I
> thought an explicit clarification on the specific case (that it's out
> of scope of this document) was one promising way to move forward.

Your text -- modulo the text about randomized link-layer addresses --
looks good to me.



> I don't know the general sense of the wg on my suggested text.  If
> it's just deemed to be redundant or possibly out-of-scope but
> otherwise acceptable while it makes some others much happier (on which
> I'm quite sure) I think it's still worth considering.  But I'm not
> pushing my specific agenda in proposing this text, so if the text
> itself is so controversial I won't argue for it.

Fine with me, modulo the link-lyer addresse stuff...

Thoughts?

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





From nobody Wed May 25 14:40:15 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 BD4C112D1E2 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:40:14 -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 VxQuVNDNu1fJ for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 14:40:13 -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 EEC7812D9EB for <ipv6@ietf.org>; Wed, 25 May 2016 14:40:12 -0700 (PDT)
Received: from [192.168.123.130] (unknown [179.40.185.202]) (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 8E27D80539; Wed, 25 May 2016 23:40:07 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: otroan@employees.org, Philip Homburg <pch-ipv6-ietf-2@u-1.phicoh.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <57461B9D.2080001@si6networks.com>
Date: Wed, 25 May 2016 17:39:41 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7EVeEjb9eLeN6HrktHDZSxnvHws>
Cc: draft-ietf-6man-default-iids@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: Wed, 25 May 2016 21:40:14 -0000

On 05/24/2016 04:50 AM, otroan@employees.org wrote:
>>
>> For a selected class of devices, I'm a huge fan of using EUI-64 based IIDs.
>> I agree that in general EUI-64 based IIDs are bad, but we can just as
>> well write down when they make life easier.
> 
> are you saying that you'd rather have seen a v6ops style document giving recommendations for what type of IIDs should be used for an enumerated set of scenarios?

SUch a document, whether inv6ops or 6man would be useful. BUt
default-iids is orthogonal to that. It improves stable addresses where
such addresses are to be used.

Since there *are* scenarios where stable addresses are required and/or
desirable (whether -only or in addition to temp addresses), the work in
this document is of value, and orthogonal to any further advice
regarding of when/where you do stable addresses and/or temp addresses.

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





From nobody Wed May 25 20:41:39 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 9E88312D583 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 20:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 I8OidceD6idi for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 20:41:36 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 E8CE612D170 for <6man@ietf.org>; Wed, 25 May 2016 20:41:35 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id f66so86735245vkh.2 for <6man@ietf.org>; Wed, 25 May 2016 20:41:35 -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=tMp4zxZSXwoN/w3h8dA5Cy50ulr1zJavoBZZ7+cpBBM=; b=h1QRS6AwL+4snMNvgAa9AnYct6LzzPnNFUsNtHwdS2NO/JXMq6R0bqy/tZm0naWPMt MPgMZr8F6YXEd5DJnJYQ+pwA7qvWvnanz4aSBuGMHFRYutpQrVyU2cCaHOmuxDmakWyY 6gjoc2AlywAY5U6njbbDRH/0XK7ssEGXSe+tVV3inuu6nwry0GNZM47N9wXUIq6j/VP5 mpTB9BcqV47QNUA2bCqpPcuYeLgy75KwLOGLzhHRbMnwb5ZPD6BBX0lQYqNU4rMM8NMU tARAHPOOLPkBjuyVEDhk1MI94+EPCHQ68unAD/ocCiHgQgDbU0ihXDYYLHIk1iwRlOzt XvsQ==
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=tMp4zxZSXwoN/w3h8dA5Cy50ulr1zJavoBZZ7+cpBBM=; b=k/MNjtvMk6aUrFF5+hUCuW0zwrwA36ha78ky9gBffDKkYpuA07csiemTYFiLl70Vhn XQgq3mWsVItS+CKLG6PMwu4uKLsW+RaoFnSxcZQyu1Nk4nKJnlA8BlVyAaO5VIF/jCo2 iYvyGbuRA3a6KN4jhGiJY2ocBZEZmxt95Y5rqoK4asJuIq2ufGRGTv/4GUyvyGUo6GRS 6hL9E/oD6du/mQN7ex3orNj9HHrdWXbnkAS7j7SyBTLlhpscGseTmgyYhmCZ9MTvi3nC P8ze2jOxsqwcJ3PCMgHCu+SCzAgHfswDFdLQdjOzthICiXpV7UqUtE4kusGT//Ibxyh/ HFFA==
X-Gm-Message-State: ALyK8tIYO4y6iD2WF1yl5rW4GRKVk1pnziElYmKvZYjKQesr6FFpzzl4wc+RlX8BF8KRnbcPnrw7lIOVOg5rjQ==
X-Received: by 10.31.217.7 with SMTP id q7mr4343702vkg.134.1464234094835; Wed, 25 May 2016 20:41:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Wed, 25 May 2016 20:41:05 -0700 (PDT)
In-Reply-To: <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 26 May 2016 13:41:05 +1000
Message-ID: <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gXyRM9ly93_0DOi-47ejBNl2-as>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Thu, 26 May 2016 03:41:37 -0000

On 24 May 2016 at 01:39, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Tue, May 24, 2016 at 12:13 AM, Fernando Gont <fgont@si6networks.com>
> wrote:
>>
>> This is orthogonal to default-iids, which provides recommendations for
>> stable addresses iff you decide to configure them. This way default-iids
>> just does what it has always meant to do (improve stable addresses), and
>> this document opens the door to temp-addr only.
>
>
> SGTM, except for the "must not embed MAC addresses". I think it's a
> perfectly good engineering tradeoff to embed a random MAC address in an IPv6
> IID as long as it's truly random.
>
> For mobile devices that only support IP and no other L3 protocols, and on
> networks with only one prefix (i.e., the vast majority)

Most IPv6 networks have two prefixes - link-local and something else.

Link-locals must not be dismissed when it comes to privacy, because
you can be attached to a link where there may be others who have an
interest in violating your privacy.

For example, it wouldn't be hard to have a device attached a public
cafe wifi network that collected LL addresses from e.g. DAD packets
(the device could be the Wifi AP itself or the default router, so
they'll always see LLs and don't need to snoop them), that then
uploads those addresses to an Internet database. If that same type of
LL address collection device was present at another public cafe wifi
network, and your LL IID didn't change when you moved between them,
the database now has a record of your movements.

>, it's pretty much as
> good as 4941-only.
>

So when do you randomise the MAC address?

I think there are at least 4 options:

(a) at boot
(b) attachment to a new link
(c) reattachment to the same link (i.e., interface down/up event)
(d) periodically while the interface continues to be connected to the same link

Having automated (a) on my desktops and laptops more than a year ago,
and having also thought about the other options, all of them have a
number of privacy limitations and operational trade-offs such that I
don't think there is a clear winner.

For example, a flapping interface with a (c) implementation, or many
(d) implementations attached to the same link could fill up switch
FDBs, causing traffic to be unnecessarily layer 2 flooded, degrading
performance and reducing the privacy inherent in switched rather than
flooded unicast traffic.

At boot MAC addresses actually persist for quite a long time on my
devices because I suspend/hibernate them rather than reboot them every
time I use them. I know that is a risk, however I've got far more
private MAC addresses that most people who've still got unchanging MAC
addresses from the NIC vendor (and I'll assume my 5 Google produced
devices).

The privacy limitations are some of the reasons why I still want
RFC7217 to be the default, because sharing a random MAC derived IID
across different prefixes on the same link still allows correlation.
Completely decoupling layer 3 addresses from layer 2 addresses means
that different privacy factors can be prioritised at the different
layers.

I don't think it is enough to say random MAC addresses in IIDs provide
adequate or equivalent security to RFC7217s when it is known what
factors influence and therefore when RFC7217 IIDs will change, where
as the same factors haven't been described for random MAC addresses. I
haven't seen in this discussion a fully articulated basis for
comparison between random MAC IIDs and RFC7217 IIDs, and there needs
to be one.

Regards,
Mark.


From nobody Wed May 25 21:35:29 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 9D17312D4FC for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 AMkjC7p9sqPD for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:35:25 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 C24A112D0B6 for <6man@ietf.org>; Wed, 25 May 2016 21:35:25 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id h19so66502877ywc.0 for <6man@ietf.org>; Wed, 25 May 2016 21:35:25 -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=Hxji9QXwXJzcN+zME0iyb9k/8LOdmroL7+BhBrq23/M=; b=G762nyG0lqEP3ws/NVrlLDh9iciB169TWgUV3bMPC6v84CE8t2SeQVuDK8iVNGQGhf gxRqmsLWTHz7+Eb3oOfAXztDw8FNUWX4B9j6bjy5UPxdB0Ria0h1/I5+j17BbXYyj3y9 8DnbyawLh8sgkzH7sEeP2L6XG6nebIY32ClKgN1UljidoTicYifxGXgCeOxKkxKGyyFX fR4nJqWhIhjY2Q10kHWMVbyfJzDWZza6U2xd8LbQjHnSqsFsOwphVgyji6nNcBQsgCPt HNSGxhw/hV76KfPdQGCJWdU7TElBq1RBjkgr/Jx7ikpee1YpoArHsTqjQtde61wRI5EF BAXw==
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=Hxji9QXwXJzcN+zME0iyb9k/8LOdmroL7+BhBrq23/M=; b=O3xyRS/ZXUcqY2gHXGEoY20Wl3oxjaj0bgHeOKBvu+zT14CfKVR0A59lGax2Gf/GNF t9FoqeCUsiMPXgwUJr8xUpu+dmRbYB1J1+3LQiDT6W940QU2cmF3OcZ9IUmRUUUj9qnU KRY+MAoln3ybE6SdF8n2uk6ftTL5GccrfWnukGLDVI517HeaVyQkIgHL8+UdgsCRbSRa E9xWS9Bczqq+zOuDOCoSLNTuOBiRIc/nFavSwkZ/DsDRqSAW7lkYJRQ06Q1MAN/ujDeh z3SvqbYypHKXjRDHnoHzp2dTkw0yTar2XaPJ/jmzGXs4awMf9sf3FVZ/s9DzGVHGHX2h +eZw==
X-Gm-Message-State: ALyK8tJyo4DEJdW8jRL7Y/n5Dl6Ngr6/aMVsFtLA/s261efwhkZNrf6Co+KSwxBLWs1YRKn+2weVsNvfFB7ir0aw
X-Received: by 10.129.82.214 with SMTP id g205mr5022908ywb.66.1464237324888; Wed, 25 May 2016 21:35:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 25 May 2016 21:35:05 -0700 (PDT)
In-Reply-To: <57432678.7050901@si6networks.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <57432678.7050901@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 26 May 2016 13:35:05 +0900
Message-ID: <CAKD1Yr0x9o5BzC3a-5ZH47g7i7ROkmsEYJc2UJyWdX6=Hcxcrg@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a114dc6949e5aad0533b751ed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XYCaAe8PljpZVNL5_h5RNZ8eUPc>
Cc: "6man@ietf.org" <6man@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: Thu, 26 May 2016 04:35:27 -0000

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

On Tue, May 24, 2016 at 12:49 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> Say two autoconfiguration prefixes are advertised on the link.
>

As I said in the part of my email that you did not quote, most networks
only have one prefix that is used for off-network traffic. That is why I
said it's a good engineering tradeoff, not a perfect solution.

You're right that it has flaws. Every scheme has correlation flaws unless
it uses a different source address for every packet. The question is where
do we make the tradeoff.

For example, your proposal to using different IIDs for different prefixes
still has correlation opportunities if the host network stack uses both
addresses to go to the same destination. OTOH, if the host stack only uses
one of the addresses (like, say, Linux does), then using a different IID
for each prefix has the same properties as using the same IID on every
prefix since only one of the addresses will be used.

--001a114dc6949e5aad0533b751ed
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, May 24, 2016 at 12:49 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=
=3D"mailto:fgont@si6networks.com">fgont@si6networks.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,=
204);padding-left:1ex">Say two autoconfiguration prefixes are advertised on=
 the link.<br></blockquote><div><br></div><div>As I said in the part of my =
email that you did not quote, most networks only have one prefix that is us=
ed for off-network traffic. That is why I said it&#39;s a good engineering =
tradeoff, not a perfect solution.</div><div><br></div><div>You&#39;re right=
 that it has flaws. Every scheme has correlation flaws unless it uses a dif=
ferent source address for every packet.=C2=A0The question is where do we ma=
ke the tradeoff.</div><div><br></div><div>For example, your proposal to usi=
ng different IIDs for different prefixes still has correlation opportunitie=
s if the host network stack uses both addresses to go to the same destinati=
on. OTOH, if the host stack only uses one of the addresses (like, say, Linu=
x does), then using a different IID for each prefix has the same properties=
 as using the same IID on every prefix since only one of the addresses will=
 be used.</div></div></div></div>

--001a114dc6949e5aad0533b751ed--


From nobody Wed May 25 21:37:53 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 0D45112D4FC for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 FGYnBV_zYGjF for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:37:50 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 6725512D1B5 for <6man@ietf.org>; Wed, 25 May 2016 21:37:50 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id x189so66305138ywe.3 for <6man@ietf.org>; Wed, 25 May 2016 21:37:50 -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=dEBu11BXA0+qIWUvPM8BDIp9VgFzKLXIakyGurCQwyU=; b=XIoJi6LO0VL+UYDjEtawbsETAM2WLzk8GgU2PgZcy5snUtbIvdzNlGcUTyyhuteiDB hmPxYbp3jhjvDeeuOT+grfPZZXjTpwkq/hT8uECfC7kKEixIOLwNBB8VNg5ggTaa8UjP lWkGL+0FLmVYjm94lQ+VY7eyXAGztrvC/zKjgdybq/yJOdBzqtStGIpRtyzExNPMh6Xx UAHxUmYt3RvC3b04EEvBeJzBdiVGypfVI06uk/g+Ht3IU8PNurnCdY5If4sW0ULRD1aO WF+cTJby0rypw+POZdnDwztxkSZejYS9xts9zJDsHubIJIFIzhpq4qK14SwcC/LxD2fR 4l/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=dEBu11BXA0+qIWUvPM8BDIp9VgFzKLXIakyGurCQwyU=; b=ITUFAjjiuzUp9/8JHiIigLY9TTdhqsySAYYWgQDUEOJDbOPIz6boXNYjhvrPg3MoJd OFm5fV73OxRoOW2st552OKFdMok0eR/tkZ8cnE7n3lt/1Ki6BhFpsAOqsVqQV5iISiNV ZKlfwub17vbkTJr4vllx3TuqFoqZcez3BzUxvRfRz9QHuIXLWtWozX6Eah0yUecftsgO +iMSj6ydxjLKQhKNaWa0wA2LLKYQyEnEBOZNx16JORrZrzidyZLsFQrJUIScW3Ko3uAQ NaKEf1FO7JjTL1o1eeH8Ogjc7HYSfl5AX5AmbMKKfgNvjvWkXL0eOBteF0eAiJaCOFg8 tvXw==
X-Gm-Message-State: ALyK8tIapaL0L7Acccv2QvIyxQLNktJgmt/a8TAOm5RqVAbWbYLqnEsa8ZGzRjzVoPZy8IvMa5gMet1TgNGwtFL+
X-Received: by 10.129.27.9 with SMTP id b9mr4505561ywb.173.1464237469496; Wed, 25 May 2016 21:37:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 25 May 2016 21:37:30 -0700 (PDT)
In-Reply-To: <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 26 May 2016 13:37:30 +0900
Message-ID: <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a1142a41a3cf5b10533b75a6e
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DUVuMB1NJLmxp81ldctWJqUrxrA>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Thu, 26 May 2016 04:37:52 -0000

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

On Thu, May 26, 2016 at 12:41 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

> (a) at boot
> (b) attachment to a new link
> (c) reattachment to the same link (i.e., interface down/up event)
> (d) periodically while the interface continues to be connected to the same
> link
>
> Having automated (a) on my desktops and laptops more than a year ago,
> and having also thought about the other options, all of them have a
> number of privacy limitations and operational trade-offs such that I
> don't think there is a clear winner.
>

What's wrong with (c) coupled with a flap dampening mechanism, such that if
you disconnect and reconnect after less than some minimum period of time
you keep the same MAC?

--001a1142a41a3cf5b10533b75a6e
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=
hu, May 26, 2016 at 12:41 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:markzzzsmith@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-left:1px #ccc solid;padding-left:1ex">(a) at boot<br>
(b) attachment to a new link<br>
(c) reattachment to the same link (i.e., interface down/up event)<br>
(d) periodically while the interface continues to be connected to the same =
link<br>
<br>
Having automated (a) on my desktops and laptops more than a year ago,<br>
and having also thought about the other options, all of them have a<br>
number of privacy limitations and operational trade-offs such that I<br>
don&#39;t think there is a clear winner.<br></blockquote><div><br></div><di=
v>What&#39;s wrong with (c) coupled with a flap dampening mechanism, such t=
hat if you disconnect and reconnect after less than some minimum period of =
time you keep the same MAC?</div></div></div></div>

--001a1142a41a3cf5b10533b75a6e--


From nobody Wed May 25 21:46:08 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 208C912D1B5 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 XHYpakBzBH4c for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:46:05 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 81D4612D0B6 for <ipv6@ietf.org>; Wed, 25 May 2016 21:46:05 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id c127so66482554ywb.1 for <ipv6@ietf.org>; Wed, 25 May 2016 21:46:05 -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=Zl8OtzTcQkIoT8aCgyricoq3C6+WuuU3TX0Gkk2Sl4E=; b=EZOd/Bmb4evPwH2kidpRr0CahR8uAH/MUJ+OIzaYubQ1IkGrE5xNfrI7a6dbKc0deR 1svOuKpwabwrhlenfKXf6lrfqxyGGe309H/EJSTA9+8OBKcxzx4Qv4qfAxSIXPqU/FuH lbqjoKQ2VNf3sIlDR8ZpdjRyeUZ2jcvUD6oo+aGpuW1m4/t6swKeRhK70ICwHZmOAR8n RNaiUaEnoK0FB2Iu9TOQRx3pqR0B1Dzt2LlYyZIurg+qzJuG+uYhaEshvyPB930ymQJa JCIEToKn2C9t7u2hpgQ25LZVV/Oyp242UitGqGn0QcqMWOVohFLCLJS9EXcbnzpNAOBl MG4g==
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=Zl8OtzTcQkIoT8aCgyricoq3C6+WuuU3TX0Gkk2Sl4E=; b=jqiKk1b4ERxmlhIx+i1XXWOJy0Wxv8YQiy4L7IC9/ZmYZO2hqg39zlGsksdiPx41QY 0/biLmLjP9P2ugsAmUPsi0CBD2jRFylvTIR/AhavIiDxL5g6FSn++pdljouR7Fji6+Cx 24iqcmM840F6h+F6lQ9zLWr2ASw7OX0p7r46fcP1bHO+P1kF9h2g6xNymqV0VzgzJ01S 9MMKZ+MHecVxbIzu2JoU8R/iHiIMdVPQ5SBLGxsUF0kAhqpy4pcavEOT9sa25z8goy8u b9dnBddHW7eDp3JtZ8ehU56CacIAplkPP+U03YQg/GzFRA/3/4nRgxkymtZiDlKqwVaD 7lgw==
X-Gm-Message-State: ALyK8tKtJ2/h3ZlDR75xcFXa2B/y1YIYBSwBqRuhqrAq6946CZoax+ZHjA3Bk7LVY20o/vd9/rfGndhZIpp5SwT5
X-Received: by 10.37.112.134 with SMTP id l128mr4503236ybc.152.1464237964185;  Wed, 25 May 2016 21:46:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Wed, 25 May 2016 21:45:44 -0700 (PDT)
In-Reply-To: <5743864F.2080705@si6networks.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 26 May 2016 13:45:44 +0900
Message-ID: <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a114bba62b94e800533b7778d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zd4DZllccCMkXFApTvvUUWPgkeo>
Cc: 6man <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, 26 May 2016 04:46:07 -0000

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

On Tue, May 24, 2016 at 7:38 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> > P.S. My personal experiment in running my laptop for several days
> > with no stable address has been completely successful. Including the
> > fact that my prototype of the Anima signaling protocol crashed after
> > a while, because the address it was relying on went away, which is of
> > course the expected behaviour.
>
> So, the question is: can this be considered "acceptable" behavior?
>

Yes, because IPv6 address can expire and be replaced at any time in a
renumbering event.

--001a114bba62b94e800533b7778d
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, May 24, 2016 at 7:38 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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"">&gt; P=
.S. My personal experiment in running my laptop for several days<br>
&gt; with no stable address has been completely successful. Including the<b=
r>
&gt; fact that my prototype of the Anima signaling protocol crashed after<b=
r>
&gt; a while, because the address it was relying on went away, which is of<=
br>
&gt; course the expected behaviour.<br>
<br>
</span>So, the question is: can this be considered &quot;acceptable&quot; b=
ehavior?<br></blockquote><div><br></div><div>Yes, because IPv6 address can =
expire and be replaced at any time in a renumbering event.</div></div></div=
></div>

--001a114bba62b94e800533b7778d--


From nobody Wed May 25 21:54:22 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 A15F612D5E8 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:54: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 tfiWKChDAvET for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 21:54:17 -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 7BA9212D1B5 for <ipv6@ietf.org>; Wed, 25 May 2016 21:54:17 -0700 (PDT)
Received: by mail-pa0-x230.google.com with SMTP id fy7so9367713pac.2 for <ipv6@ietf.org>; Wed, 25 May 2016 21:54:17 -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=YlimzeIl7wB1eqmUbwbGcG7Pd0bmJAxVzT6YZ8WLI7I=; b=GMXb03i9WYXfpnVpZXlo2tLGSaYvkpIMnqL09rPcafRbSE4oIXJpAMwFeNB0VkiNkA MIh/llBFQ3iBYRohbHmZbCMQo4JyhEXve0sukJYqYKIgGZWGgQVzZKFiFV79XD9pVk7P C2CD7+hup9hj4x8ghfYhhFxiFnOkVJVQYUZjxcSGmAQYrRDbEeLIdCC/fQ+v6ZhUl3G1 4kirsOK0yZ1ZG/EB4XBR5iASTCaAp3Z3q1M2Ml6wkX5ZAffS+3HWYKp78aZ+z6jbfnCH E9Fcp1M9qLU3+BsJX9gbUjsQ549wry3lVBfxuZVBkShR4Fl78M2dQRlOvrwVNUiqIT+m ml3g==
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=YlimzeIl7wB1eqmUbwbGcG7Pd0bmJAxVzT6YZ8WLI7I=; b=QM4BId06vgQBiz4h5f5cox6+4ePqq9f+UucRJqrWZOqLb/Qmc9rgMl5I10+bX48pzn kSkMXEOHWCXeGF818/vp18Sths6MOD5ZSAHF0N4kcapsDFhg7YOwH6kPFijF0d7BwujB Rq/bvCbiJzqd+HXr3h4xXlyLIhT0ZhF81P5VGjKzVWjw6DeGW/Xoiz9KLDClYfkUpcLc TE2yjvZc5+Ae0yocI4vGVzNxO9UWoaskqJ4ISvZAZMCNsIV7L5EcrsUHY/IKHGKYtMCL duASb/L5RdrhL+YnFOZR59EBPSus0zLyHCETOhrUnKaUYYacibv7WVJ4dkzgMozffERP oFBg==
X-Gm-Message-State: ALyK8tLby4rh3r33TpbGyVjPe89MXC1NrHdCwUTstRimIuIxxoBKnHEpKzpFX+Q9lk59Ww==
X-Received: by 10.66.25.236 with SMTP id f12mr11208945pag.35.1464238456185; Wed, 25 May 2016 21:54:16 -0700 (PDT)
Received: from ?IPv6:2406:e007:61a8:1:391c:ab3f:1734:7bd5? ([2406:e007:61a8:1:391c:ab3f:1734:7bd5]) by smtp.gmail.com with ESMTPSA id s23sm2087656pfj.86.2016.05.25.21.54.13 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 25 May 2016 21:54:15 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Lorenzo Colitti <lorenzo@google.com>, Fernando Gont <fgont@si6networks.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a6d03e19-6a83-b4e5-9118-8edf26b867ab@gmail.com>
Date: Thu, 26 May 2016 16:54:21 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/k5nWZ8USeftnsoasYG5ZFi5Qshg>
Cc: 6man <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, 26 May 2016 04:54:20 -0000

On 26/05/2016 16:45, Lorenzo Colitti wrote:
> On Tue, May 24, 2016 at 7:38 AM, Fernando Gont <fgont@si6networks.com>
> wrote:
> 
>>> P.S. My personal experiment in running my laptop for several days
>>> with no stable address has been completely successful. Including the
>>> fact that my prototype of the Anima signaling protocol crashed after
>>> a while, because the address it was relying on went away, which is of
>>> course the expected behaviour.
>>
>> So, the question is: can this be considered "acceptable" behavior?
>>
> 
> Yes, because IPv6 address can expire and be replaced at any time in a
> renumbering event.

Need I add that we will be putting some words about address stability or
its absence into the appropriate Anima documents. Obviously, we want the
autonomic networking infrastructure to be both stable and self-repairing.
But then I think we'd like all applications to have those properties.

    Brian


From nobody Wed May 25 23:16:55 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 E422B12D689 for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 23:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 L8aWyoQDGVwK for <ipv6@ietfa.amsl.com>; Wed, 25 May 2016 23:16:40 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::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 BE5D912D692 for <6man@ietf.org>; Wed, 25 May 2016 23:16:07 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id r140so90044899vkf.0 for <6man@ietf.org>; Wed, 25 May 2016 23:16:07 -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=Nza1noJu4TqjDVtdsLqbEwohWYvRBbk5hy4UB/hXTO0=; b=tTxL3mu76WfLQvVuNcESJXx326Yo6R/cJ1zwsPNvGg+dJElo8A2ATZ6XLz6V4UfsXH mzrLNAkx8CjJK1zk4usLGQCdV/DVT3FBsmSZhxhDWn18LoPIhcIuVwtKFwXZrkUgImrX VM39oewm6XVOclD1UA1sBlUm3WDZuufumXR9lA1xYXq4nvpZuPoGnSFLptq5E5GWkUDd dUPdxctU2HOakYQ7yUxzoUwuHJ/ryU1CWbe/Ae933Hex0z6UCBQLYkj5Mve29OC68F3B SsG2LW4nQRDnZ7UWcBSbWgordcrv7j/P681g2WchEMn3X7Y7xuyD9s340wsw1zn48XkD 6/nQ==
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=Nza1noJu4TqjDVtdsLqbEwohWYvRBbk5hy4UB/hXTO0=; b=CHwoB9J3JmqV/KJEMlOp4Enw0m1dl+wVe1Br9bB9VH4C+Dp997FQvHYHzvIoiCNvP0 ZHGerR/WIEgpuoFy3CyIZvpbxSmI1XTTQRuiKQKaSaz9XQzbFmuea6yUTHXRI74t9LnQ oYUKWT80GDBWYDkukR8N8/dpFqCL5CAmBeGq5dAZs8JmtuiDkGbUzmUq2O0NYzm4gU/N 6U8EM8K9kc2UQvvx9+UGIPwu1jPS7a9IrGvzN+bu+/+2Sceqmd+yFmSlOJSHasmB8JVp 7fHtKj6qKjGhbPwzCKQkpzKUUJXz8QbWF/HJ2QIBSk4l0mrUmAEEsZdW2E7wAdjjFzCL wQsA==
X-Gm-Message-State: ALyK8tIgeFpY9MlxwvCRCx8PnAgvL7G5PVxN7MbwobUYTAEs+qlNZJB5/srMDaWUBY4Yxpj9zev7bXY7vSQ0xQ==
X-Received: by 10.159.32.131 with SMTP id 3mr4772466uaa.75.1464243366803; Wed, 25 May 2016 23:16:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Wed, 25 May 2016 23:15:37 -0700 (PDT)
In-Reply-To: <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 26 May 2016 16:15:37 +1000
Message-ID: <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/85ehtUr2SCi-xPwQyN1S1km4yg8>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Thu, 26 May 2016 06:16:43 -0000

On 26 May 2016 at 14:37, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Thu, May 26, 2016 at 12:41 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
>>
>> (a) at boot
>> (b) attachment to a new link
>> (c) reattachment to the same link (i.e., interface down/up event)
>> (d) periodically while the interface continues to be connected to the same
>> link
>>
>> Having automated (a) on my desktops and laptops more than a year ago,
>> and having also thought about the other options, all of them have a
>> number of privacy limitations and operational trade-offs such that I
>> don't think there is a clear winner.
>
>
> What's wrong with (c) coupled with a flap dampening mechanism, such that if
> you disconnect and reconnect after less than some minimum period of time you
> keep the same MAC?

Nothing in itself, except there is nothing specifying it, and millions
of devices that are currently vulnerable to this sort of fault.

There are these sorts issues with all of the above, and I'm not even
completely sure that the above is the complete list of times that it
would be useful or valid to change MAC address.

Here is another example.

(b) and (c) are fundamentally the same mechanism - change MAC address
upon link up.

In the case of (c), the host would send an unsolicited NA to update
other on-link devices' neighbor caches with the interfaces' new
link-layer address (note, I've been assuming the IPv6 address would
stay the same across this event to ensure TCP etc. connections
survive.)

In the case of (b), when attached to the new link, it is very
important not to send this unsolicited NA, because the NA may contain
global or ULA prefixe addresses, which would disclose to any device
capturing them on the new network what past network the device was
just attached to (ULAs less so, although they're still supposed to be
globally unique).

So the problem is how to distinguish between attaching to a new link
and re-attaching to the same link?

I understand this sort of detection may be addressed by RFC6059,
"Simple Procedures for Detecting Network Attachment in IPv6". I
haven't looked at it in detail, however it seems to be assuming that a
router's link-layer address will stay constant to create a Router
Identifier. So if router link-layer addresses change periodically
(when?) and their IIDs change too because the MAC is embedded in the
IID, I think DNA would think there was attachment to a new network
more often than is actually the case.

If unsolicited NDs aren't sent when reattaching to the same network
(because DNA thinks it is a new network),  then existing TCP
connections would either fail, or at least be disrupted, usually
visibly to the application user, until NUD detected the failure and
then issued new NSes to discover the new MAC address for the
destination IPv6 address.


Regards,
Mark.


From nobody Thu May 26 01:15:02 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 507E012D63C for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 01:15: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 Uig4fjxQR1EU for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 01:14:58 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::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 5229912D568 for <ipv6@ietf.org>; Thu, 26 May 2016 01:14:58 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id z87so89219154wmh.0 for <ipv6@ietf.org>; Thu, 26 May 2016 01:14:58 -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=9v9vWZlGCnzJFEoRfzlm+UdHVxBZElQIQWdAxISYj60=; b=o82Tp68r1ZH69kkcVo/Pb0HdneOrZGTT2a/0WefF/aJfb9qBthDwp1uQlqZ6gu4tRv osFvociSAGjuoCICPOPs4UFKjhfitpirtCvl5IIS4ltO9CDpNTsqKf5vCO6FxF4FBodu 9v7jM4ZEe4m8q4aod+4e+bPYInNSUrQdgkLM/1iT6FQOsNd37O3dPEWlCopp7tK6KPbh D2FxsJmERNMpajAIlYkchI2yyEVMQO8ItHNooaOw0B+qNBMOsbFlsLhTOOliOJkylvZm 3L8Xwqm48qNKWNl824F+8incSReeIey/kLQkTGs3a170T4GuNfCsT8VarO60JekI1Rwx goVg==
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=9v9vWZlGCnzJFEoRfzlm+UdHVxBZElQIQWdAxISYj60=; b=KF+Op+X/KvT3P5IfnRK6TRmetbHFH/lo0qosOFzXJfEoOymW/BU1iMhj5TpMePovsS pA+PgGjRf93jwoGPbq+/L/Je1Fbnc5CThCxyP7SP1sD7LnWkNUkRel8/ZGKtVbCcZf+Z HBWE2xQknaL9RRXXFZPvORm287V2hzYJP6Ct894WN4Kl8Th3LqRvAlPIx8tg5XlGsf9k JD5L9KfsD6FOv5sKwPHdhyarTYv4oWZCllpBa1dhJX8+mqDYN10JOIU8R1xr/CqvshX2 qsHxTiIav5VgZCcnp/WfNCfK9YCWKTs70BwG/4vBDN9EdjORtKGEVSwS6xKsU1FJXQ3z oYfg==
X-Gm-Message-State: ALyK8tI1c707JZHTg3SZMoZSeCJ3CHqEmF5hnvDE1Z2J2DJ2DXy4Nhk8quTBi5K2ZzfW7g==
X-Received: by 10.28.63.5 with SMTP id m5mr2357269wma.24.1464250496769; Thu, 26 May 2016 01:14:56 -0700 (PDT)
Received: from [172.24.250.201] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id a75sm2201476wme.18.2016.05.26.01.14.55 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 01:14:55 -0700 (PDT)
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5C22BD58-70EE-4BC6-8432-265715551262"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAKD1Yr0ciXOeKjXx0vw+vtxhsUr-BwecL7uV=MKupSH4X4CskA@mail.gmail.com>
Date: Thu, 26 May 2016 11:14:53 +0300
Message-Id: <6EBBE43A-4943-403B-8773-858477C921A0@gmail.com>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org> <CAKD1Yr0ciXOeKjXx0vw+vtxhsUr-BwecL7uV=MKupSH4X4CskA@mail.gmail.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cUiCZI5ddbBc_BJ1xRGhNxPc1bk>
Cc: 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: Thu, 26 May 2016 08:15:00 -0000

--Apple-Mail=_5C22BD58-70EE-4BC6-8432-265715551262
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

Based on the discussion regarding advancing RFC4941, we think that the =
w.g. should not plan to advance RFC4941 in place to Internet Standard.  =
We can move this RFC to the list of documents that can be advanced =
later.  The w.g. can decide if an update is needed, or if it should be =
advanced at all.

Thanks,
Bob & Ole

> On May 25, 2016, at 7:21 AM, Lorenzo Colitti <lorenzo@google.com> =
wrote:
>=20
> On Tue, May 24, 2016 at 3:59 PM, <otroan@employees.org> wrote:
> I don't think 4941 _requires_ public addresses. it specifies the =
behaviour _if_ you have them.
>=20
> RFC 4941 does require public addresses:
> 	=E2=80=A2 The text explicitly says in several places that =
privacy addresses are "in addition to" public addresses.
> 	=E2=80=A2 If you don't have a public address, critical parts of =
the specification, such as how to extend the lifetime of privacy =
addresses when receiving an RA, are undefined. An example is the text =
that says, in effect, "when an RA would extend the lifetime of a public =
address, then also extend the lifetime of temporary addresses".
> If we want to reclassify it as is, we'll have to accept that the =
resulting Internet standard document will only a) define the behaviour =
for privacy addresses with a public address, b) say that privacy =
addresses should be depreferred by default.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_5C22BD58-70EE-4BC6-8432-265715551262
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

iQEcBAEBCgAGBQJXRrB+AAoJEK7rdBF357uoPIQIAI44uEHhLQTfw9wKqL4dMh46
AAVDprUw1CeA+Lph5UTmsWWgZ4cUt7Nz67dpiHmvNUVALM97q1NDPpFZhLuIRyve
05kyDhJ7g0yrx0a3IpR5lRVooLzH3nUX+qX12gn8+cTgnb3ET7h33alIgLt+ikqX
P31A/79yjY7n2k9/8ZJL0TVkq7MG6IO8M4R8XAQ6csp1rRfHeNlN8CRRaFp9XLQP
OsH2nTCJuPTLNZb+SalgEvqRqTSaZ/8azOn7WO6c58D8vS4dS99cHEvbarhD41co
HRaF0f7xvmlDov0TVKeuZbjIaHdTo69A0t1MmOJcYBLuiaD3mZHcofiK7jtn2fc=
=X9dj
-----END PGP SIGNATURE-----

--Apple-Mail=_5C22BD58-70EE-4BC6-8432-265715551262--


From nobody Thu May 26 01:23:24 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 0E3DE12D63C for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 01:23:23 -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 wCRfVwR7XZue for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 01:23:21 -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 11AE612D609 for <ipv6@ietf.org>; Thu, 26 May 2016 01:23:20 -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; 26 May 2016 08:23:19 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 9BE349CC4F; Thu, 26 May 2016 01:23:18 -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=uxshRCUF3rOgzWdPNOE6bxpyHAs=; b= oBiqikVKJKsXh124oOImb5Gy7dmKgq4XEZdls4jt/HsUxkx9HAuk78+wim8oQOfs u2s0qrEE15BsZy6bb0CJQMkQRgS/tfk6Z/SvGTnHb0FBPd+IyPs48qZ4OQf21UBP qcrzB58HW9At614MIJA3u9ipMVQKxNFUCn1CSepPsfQ=
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=eyJS9x4z6jSPQBlbnNOdvgEfoS 77/2jgEgsD6E/fd3GfL74I9TcUhUOji89h/vrBHEIf9KYV4znYvB0kst/MGutCbi cG9p45E0CqCfD7fsbyycAZJldJ0DDaIpz/iF1P7Jkrxv2oDDaBCqz2O37Dr5m/4D +fthixDYq10TIb1bY=
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 2F1D09CC4E; Thu, 26 May 2016 01:23:18 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 934DB1718D6A; Thu, 26 May 2016 10:23:12 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D23673B6-D7F2-4948-8FAE-60C0918E6737"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <57461B9D.2080001@si6networks.com>
Date: Thu, 26 May 2016 10:23:12 +0200
Message-Id: <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ut_ST29tdH_joxU5zsmPGADIW2c>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@tools.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: Thu, 26 May 2016 08:23:23 -0000

--Apple-Mail=_D23673B6-D7F2-4948-8FAE-60C0918E6737
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

>>> For a selected class of devices, I'm a huge fan of using EUI-64 =
based IIDs.
>>> I agree that in general EUI-64 based IIDs are bad, but we can just =
as
>>> well write down when they make life easier.
>>=20
>> are you saying that you'd rather have seen a v6ops style document =
giving recommendations for what type of IIDs should be used for an =
enumerated set of scenarios?
>=20
> SUch a document, whether inv6ops or 6man would be useful. BUt
> default-iids is orthogonal to that. It improves stable addresses where
> such addresses are to be used.
>=20
> Since there *are* scenarios where stable addresses are required and/or
> desirable (whether -only or in addition to temp addresses), the work =
in
> this document is of value, and orthogonal to any further advice
> regarding of when/where you do stable addresses and/or temp addresses.

RFC7217 covers that.

Given the recent discussions on RFC4941, random MACs and on this =
document, I'm more and more leaning towards the opinion that we (as in =
the IETF) shouldn't have gotten into the business of trying to declare =
what people should put in the lower 64 bits. :-)

We cannot all IPv6 implementations non-compliant by removing section 4 =
of RFC2464 as this document proposes.

Thought experiment. What if we abandon this document, and instead start =
work on updates to the IPv6 over foo documents? 2464bis specifically.

Cheers,
Ole

--Apple-Mail=_D23673B6-D7F2-4948-8FAE-60C0918E6737
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

iQEcBAEBCgAGBQJXRrJwAAoJED4aXnjSQuKWNpsIAJl8/lBKvlSa634sn+LNwjQm
/017nTzROOtkJmJ+5O4TgCrdf6kSWEot/2n1t7iLpHWZezZzyCk58lK/sKXMoufF
RlcyOnnP1lHuKFwwFIwCJXK1jcPJFiEIakHay8EQJF20ROFZPgEvaHLdztZ7kvMP
2N2SLlFHVVW+rlyg9exrlt7TveDWdxLfOiDm5Y9OqWdPxWtF5DMEB2MFEO0YGobZ
tNhvUFgz3s+g0OisF+X8uJC0DmwQYCar9A+jGekgPNJbV/rPpOxarXEHRLKcmeqE
yZgyAvxRIf7HYp+vEd3DhQcItqndz6zJVeTZu3o3ILI1YCrTC6EDLW+g5J6z7lQ=
=a7Uf
-----END PGP SIGNATURE-----

--Apple-Mail=_D23673B6-D7F2-4948-8FAE-60C0918E6737--


From nobody Thu May 26 02:08:52 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 1E1DE12D0B9 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 G6DZt7FnItdt for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:08:48 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 C1CAE12D1D7 for <ipv6@ietf.org>; Thu, 26 May 2016 02:08:46 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id k1so39025790vka.3 for <ipv6@ietf.org>; Thu, 26 May 2016 02:08: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=H6B+3rc+aE2EReFI/OLcdlJgXGMezqW9vru2+19Vgxg=; b=EzIOz+hCxr+YVr9qBPya6r742FlmIE9hT1hfyb/CpdDVOZ8FGMU/klgJZ2eO9GtORv oFCngFdzPYxryWbdgqmPb7b2uYt5n+54TahGVodcG6iVIPRxixnUsiMgn7tOfcTDf7Mu ypvfaUO3Tqn9z1UkLbRcaLlWz8onCiMMRUW2iOwJbdDQ8qOrXs4UAeqhb/hw5p8Ec1iU yO+K5GeVdJf0Tp/7DmTc96g7rCPFzgTTVmo6EtRtLXsdhR1ENA0zVC2OiRYdb0LTTY+a wh9ne8ri1+ADOxalYVIxOVtea++0OQ91ZSfNdST7Z5V2rIutPdnnBScfKxprJlTn5YmB v6Sg==
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=H6B+3rc+aE2EReFI/OLcdlJgXGMezqW9vru2+19Vgxg=; b=IzPtPw+mziM7MfjFsy8RQB9WtW8Gf0VoxKflpsB9OlHpX+AYI0nBMqJItoYZP75LvN n/nVBB8Clk59gckZpAliJpCE9tjESpno1EmYoXXHw+a3/4JhgssDRW0/31UmkWBsuK22 xyL7fxLSD7E8FsHQ663EWEDPn61EMvAntuo5dDocHcS9d8ertn+uJnqyoRUlYvRLfRbX y8IAGHRP6pzLgqqMYp5fOs3xJcX6+YcJ4myavnhSksv/l8xX98nMTYmHPhHHTsdN6V8g xv4Ugytxkzarp61RClL3A029y1WlOjz0nQ0L+QB1jziyqbX1/T3PO+dooHxr+lFDkxRv qhLg==
X-Gm-Message-State: ALyK8tLM7p9XUyiStyrEFoCI2ZnAHyCY8hl74qJdlKpQDKOmCfE4r+Gh2kxtUf1RtQO9+opJOOoXlfWekTOceA==
X-Received: by 10.31.217.7 with SMTP id q7mr4922671vkg.134.1464253725855; Thu, 26 May 2016 02:08:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 02:08:16 -0700 (PDT)
In-Reply-To: <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 26 May 2016 19:08:16 +1000
Message-ID: <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=94eb2c07c41030d53b0533bb2376
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DdHRx89y-ZaOV42dPKRjOQk1-SU>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Thu, 26 May 2016 09:08:51 -0000

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

On 26 May 2016 at 18:23,  <otroan@employees.org> wrote:
>>>> For a selected class of devices, I'm a huge fan of using EUI-64 based
IIDs.
>>>> I agree that in general EUI-64 based IIDs are bad, but we can just as
>>>> well write down when they make life easier.
>>>
>>> are you saying that you'd rather have seen a v6ops style document
giving recommendations for what type of IIDs should be used for an
enumerated set of scenarios?
>>
>> SUch a document, whether inv6ops or 6man would be useful. BUt
>> default-iids is orthogonal to that. It improves stable addresses where
>> such addresses are to be used.
>>
>> Since there *are* scenarios where stable addresses are required and/or
>> desirable (whether -only or in addition to temp addresses), the work in
>> this document is of value, and orthogonal to any further advice
>> regarding of when/where you do stable addresses and/or temp addresses.
>
> RFC7217 covers that.
>
> Given the recent discussions on RFC4941, random MACs and on this
document, I'm more and more leaning towards the opinion that we (as in the
IETF) shouldn't have gotten into the business of trying to declare what
people should put in the lower 64 bits. :-)
>

I think we should. What shouldn't have happened is embedding forms of layer
2 addresses in layer 3 IIDs.

> We cannot all IPv6 implementations non-compliant by removing section 4 of
RFC2464 as this document proposes.
>

I think "deprecated" would be a better term for them.


> Thought experiment. What if we abandon this document, and instead start
work on updates to the IPv6 over foo documents? 2464bis specifically.
>

Don't we try to decouple layer 2 and 3 as much as possible, so we can slot
in new layer 2s as they become available, and layer 3 hides those changes?

RFC6272, "Internet Protocols for the Smart Grid"


"2. The Internet Protocol Suite"

"2.1.3.1. Internet Protocol"
[...]

"The Internet layer provides a uniform network abstraction network
   that hides the differences between various network technologies.
   This is the layer that allows diverse networks such as Ethernet,
   802.15.4, etc. to be combined into a uniform IP network.  New network
   technologies can be introduced into the IP Protocol Suite by defining
   how IP is carried over those technologies, leaving the other layers
   of the IPS and applications that use those protocol unchanged."


RFC7217 creates that addressing abstraction for stable addresses, as well
as localising the IID meaning to a specific prefix, which is also the scope
of an IID for the purposes of sending or receiving packets. Doing it once
now means never having to do it again for IPv6-over-future-foo documents.

Regards,
Mark.

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

<div dir=3D"ltr"><br><br>On 26 May 2016 at 18:23, =C2=A0&lt;<a href=3D"mail=
to:otroan@employees.org">otroan@employees.org</a>&gt; wrote:<br>&gt;&gt;&gt=
;&gt; For a selected class of devices, I&#39;m a huge fan of using EUI-64 b=
ased IIDs.<br>&gt;&gt;&gt;&gt; I agree that in general EUI-64 based IIDs ar=
e bad, but we can just as<br>&gt;&gt;&gt;&gt; well write down when they mak=
e life easier.<br>&gt;&gt;&gt;<br>&gt;&gt;&gt; are you saying that you&#39;=
d rather have seen a v6ops style document giving recommendations for what t=
ype of IIDs should be used for an enumerated set of scenarios?<br>&gt;&gt;<=
br>&gt;&gt; SUch a document, whether inv6ops or 6man would be useful. BUt<b=
r>&gt;&gt; default-iids is orthogonal to that. It improves stable addresses=
 where<br>&gt;&gt; such addresses are to be used.<br>&gt;&gt;<br>&gt;&gt; S=
ince there *are* scenarios where stable addresses are required and/or<br>&g=
t;&gt; desirable (whether -only or in addition to temp addresses), the work=
 in<br>&gt;&gt; this document is of value, and orthogonal to any further ad=
vice<br>&gt;&gt; regarding of when/where you do stable addresses and/or tem=
p addresses.<br>&gt;<br>&gt; RFC7217 covers that.<br>&gt;<br>&gt; Given the=
 recent discussions on RFC4941, random MACs and on this document, I&#39;m m=
ore and more leaning towards the opinion that we (as in the IETF) shouldn&#=
39;t have gotten into the business of trying to declare what people should =
put in the lower 64 bits. :-)<br>&gt;<div><br></div><div>I think we should.=
 What shouldn&#39;t have happened is embedding forms of layer 2 addresses i=
n layer 3 IIDs.</div><div><br>&gt; We cannot all IPv6 implementations non-c=
ompliant by removing section 4 of RFC2464 as this document proposes.<br>&gt=
;<div><br></div><div>I think &quot;deprecated&quot; would be a better term =
for them.</div><div><br></div><div><br>&gt; Thought experiment. What if we =
abandon this document, and instead start work on updates to the IPv6 over f=
oo documents? 2464bis specifically.<br>&gt;<br><br>Don&#39;t we try to deco=
uple layer 2 and 3 as much as possible, so we can slot in new layer 2s as t=
hey become available, and layer 3 hides those changes?<br><br>RFC6272, &quo=
t;<span style=3D"color:rgb(0,0,0);white-space:pre-wrap">Internet Protocols =
for the Smart Grid&quot;</span><div><font color=3D"#000000"><span style=3D"=
white-space:pre-wrap"><br></span></font></div><div><font color=3D"#000000">=
<span style=3D"white-space:pre-wrap"><br></span></font></div><div><font col=
or=3D"#000000"><span style=3D"white-space:pre-wrap">&quot;2.  The Internet =
Protocol Suite&quot;</span></font></div><div><br></div><div><font color=3D"=
#000000"><span style=3D"white-space:pre-wrap">&quot;2.1.3.1.  Internet Prot=
ocol&quot;
</span></font><br>[...]<br><br>&quot;The Internet layer provides a uniform =
network abstraction network<br>=C2=A0 =C2=A0that hides the differences betw=
een various network technologies.<br>=C2=A0 =C2=A0This is the layer that al=
lows diverse networks such as Ethernet,<br>=C2=A0 =C2=A0802.15.4, etc. to b=
e combined into a uniform IP network.=C2=A0 New network<br>=C2=A0 =C2=A0tec=
hnologies can be introduced into the IP Protocol Suite by defining<br>=C2=
=A0 =C2=A0how IP is carried over those technologies, leaving the other laye=
rs<br>=C2=A0 =C2=A0of the IPS and applications that use those protocol unch=
anged.&quot;<br><br><br>RFC7217 creates that addressing abstraction for sta=
ble addresses, as well as localising the IID meaning to a specific prefix, =
which is also the scope of an IID for the purposes of sending or receiving =
packets. Doing it once now means never having to do it again for IPv6-over-=
future-foo documents.<br><br>Regards,</div></div></div><div>Mark.</div></di=
v>

--94eb2c07c41030d53b0533bb2376--


From nobody Thu May 26 02:40:14 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 A61F812D54B for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:40:13 -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 Uqbx-b872o-b for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:40:12 -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 9025912D18E for <ipv6@ietf.org>; Thu, 26 May 2016 02:40:12 -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; 26 May 2016 09:40:11 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 6F4049CC51; Thu, 26 May 2016 02:39:51 -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=Yde3sEvlLMNd2HazpKPahUebMo8=; b= nsltnfwPBs4nVg9zbbA2olKpWMe4CXsOJ9CDKP8Yh+VY4SU3O6NDw1WC3JIG/LYr XgfhkbPlSHVjrVMP+XJsP4XbZifWjFhIv+GoeZia8byr7Yi2cbfZkrC7QAPTJZ3l EPWippjLcTAhaN5/RtVC4zPUNQ4WtVV1ioqN9AM5Rcc=
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=K5QwEgSj/l2agiEFxbx2mRbZFd krEC+FCWJLmj2nv2lz/gL2vBkgEQVx0SAl9pOdyouQjzNQV+cO3tim3CEQC12K/f 7fzR8DQLwg9mRbmBGyVQVqRLLNOe58xSbUeUYb8CBz+AUYVTzEta7eUhgN6xWTwe VgjAHGdwPAKEH4BsE=
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 F1D5C9CC4E; Thu, 26 May 2016 02:39:50 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 0F043171B703; Thu, 26 May 2016 11:39:49 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D1353D6C-A2CC-40B7-8A93-29BCFFFE7466"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
Date: Thu, 26 May 2016 11:39:45 +0200
Message-Id: <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wKt2ffJfnXOIizQE-hJ3OwrCUvk>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Thu, 26 May 2016 09:40:13 -0000

--Apple-Mail=_D1353D6C-A2CC-40B7-8A93-29BCFFFE7466
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark,

> >>>> For a selected class of devices, I'm a huge fan of using EUI-64 =
based IIDs.
> >>>> I agree that in general EUI-64 based IIDs are bad, but we can =
just as
> >>>> well write down when they make life easier.
> >>>
> >>> are you saying that you'd rather have seen a v6ops style document =
giving recommendations for what type of IIDs should be used for an =
enumerated set of scenarios?
> >>
> >> SUch a document, whether inv6ops or 6man would be useful. BUt
> >> default-iids is orthogonal to that. It improves stable addresses =
where
> >> such addresses are to be used.
> >>
> >> Since there *are* scenarios where stable addresses are required =
and/or
> >> desirable (whether -only or in addition to temp addresses), the =
work in
> >> this document is of value, and orthogonal to any further advice
> >> regarding of when/where you do stable addresses and/or temp =
addresses.
> >
> > RFC7217 covers that.
> >
> > Given the recent discussions on RFC4941, random MACs and on this =
document, I'm more and more leaning towards the opinion that we (as in =
the IETF) shouldn't have gotten into the business of trying to declare =
what people should put in the lower 64 bits. :-)
> >
>=20
> I think we should. What shouldn't have happened is embedding forms of =
layer 2 addresses in layer 3 IIDs.

it was convenient at the time.
it's still convenient in certain cases, but not as the default for _all_ =
devices.

> > We cannot all IPv6 implementations non-compliant by removing section =
4 of RFC2464 as this document proposes.
> >
>=20
> I think "deprecated" would be a better term for them.

I'm not even sure we should do that.
there are valid uses for the current scheme.
it's implemented, deployed, understood and well tested.
the company I work for have tens of IPv6 implementations and hundreds of =
different products with IPv6 stacks in them. it's unlikely I'm going to =
champion making a change from EUI-64 to 7217 in cases where it doesn't =
provide value.

there are 2^64 ways to generate an IID, we can only provide general =
advice.
for mobile devices it is clearly not a good idea to embed L2 addresses =
in L3 addresses.
but for those devices a lot of other things aren't good ideas either. if =
you really care about privacy I'm not quite sure if any of this would =
really help you, but oh well.

when we want to make recommendations that should apply to _all_ devices, =
that's when we get into trouble. that's incredibly hard to do, because =
the only answer we can agree on is: it depends.

> > Thought experiment. What if we abandon this document, and instead =
start work on updates to the IPv6 over foo documents? 2464bis =
specifically.
> >
>=20
> Don't we try to decouple layer 2 and 3 as much as possible, so we can =
slot in new layer 2s as they become available, and layer 3 hides those =
changes?
>=20
> RFC6272, "Internet Protocols for the Smart Grid"
>=20
>=20
> "2.  The Internet Protocol Suite"
>=20
> "2.1.3.1.  Internet Protocol"
>=20
>=20
> [...]
>=20
> "The Internet layer provides a uniform network abstraction network
>    that hides the differences between various network technologies.
>    This is the layer that allows diverse networks such as Ethernet,
>    802.15.4, etc. to be combined into a uniform IP network.  New =
network
>    technologies can be introduced into the IP Protocol Suite by =
defining
>    how IP is carried over those technologies, leaving the other layers
>    of the IPS and applications that use those protocol unchanged."
>=20
>=20
> RFC7217 creates that addressing abstraction for stable addresses, as =
well as localising the IID meaning to a specific prefix, which is also =
the scope of an IID for the purposes of sending or receiving packets. =
Doing it once now means never having to do it again for =
IPv6-over-future-foo documents.

L2 and L3 are decoupled in the current model. an example of them being =
coupled would have been if we had used the IID to determine the MAC =
address instead of doing ND address resolution.

This is not an argument against 7217. I think the default should be to =
use 7217. If you want stable addresses. I don't want to make other =
schemes non-compliant. And I think we have to remember that these are =
just defaults. For SLAAC. People can and do configure IIDs any which way =
they like.

My point given that there is a level of uncomfortableness with this =
document was to try to do the reverse. Can we find some updates to 2464 =
there is consensus on?

Cheers,
Ole


--Apple-Mail=_D1353D6C-A2CC-40B7-8A93-29BCFFFE7466
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

iQEcBAEBCgAGBQJXRsRkAAoJED4aXnjSQuKWg30H/132i4eQtGfMZBElt8ARvXaA
1GH3OOa/8WCv0XzgurLOzfwWrgTkXjqYidCQrbXK75pLIJlt8cRPWXgEi18z9OUn
VmfIafLP5LA9VZrEkSsXwdcBO8mdaQE5YD8VHbdWEvkl8B2zYgJmnOAwj36n7GLA
nR0k3yBkbaGfDGZdBbl3xNJaZDOLvII6u9Mbkv9Nf+ts9YcFxtHP8bOvGa7pUIHd
7lhGfwXMTMokoUk53yTmP6lnh7qGzQ9MyJ7PGYZje+1uZJTDz4NQi40EZMIYMnDM
vbYqfg8UNtPAy6DqwSC6oUuAv/89+9Z9zo2WEDQhY0pZZkSekLC78s4EyCvZwkQ=
=hdmo
-----END PGP SIGNATURE-----

--Apple-Mail=_D1353D6C-A2CC-40B7-8A93-29BCFFFE7466--


From nobody Thu May 26 02:59:02 2016
Return-Path: <alexandre.petrescu@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 EB81312D916 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 VzLbRczKRgxe for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 02:58:58 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66F612D5A4 for <ipv6@ietf.org>; Thu, 26 May 2016 02:58:57 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4Q9wtpM010643 for <ipv6@ietf.org>; Thu, 26 May 2016 11:58:55 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C9A1A2052DF for <ipv6@ietf.org>; Thu, 26 May 2016 11:59:07 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BF8DF2050A5 for <ipv6@ietf.org>; Thu, 26 May 2016 11:59:07 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4Q9wtWQ023782 for <ipv6@ietf.org>; Thu, 26 May 2016 11:58:55 +0200
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: ipv6@ietf.org
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <121858cc-3970-e380-ea92-2c4b2d49d1fb@gmail.com>
Date: Thu, 26 May 2016 11:58:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oGFfaBHVjUztWDgEuNx441pB-qU>
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, 26 May 2016 09:59:01 -0000

Le 26/05/2016 à 11:08, Mark Smith a écrit :
>
>
> On 26 May 2016 at 18:23,  <otroan@employees.org
> <mailto:otroan@employees.org>> wrote:
>>>>> For a selected class of devices, I'm a huge fan of using EUI-64
> based IIDs.
>>>>> I agree that in general EUI-64 based IIDs are bad, but we can just as
>>>>> well write down when they make life easier.
>>>>
>>>> are you saying that you'd rather have seen a v6ops style document
> giving recommendations for what type of IIDs should be used for an
> enumerated set of scenarios?
>>>
>>> SUch a document, whether inv6ops or 6man would be useful. BUt
>>> default-iids is orthogonal to that. It improves stable addresses where
>>> such addresses are to be used.
>>>
>>> Since there *are* scenarios where stable addresses are required and/or
>>> desirable (whether -only or in addition to temp addresses), the work in
>>> this document is of value, and orthogonal to any further advice
>>> regarding of when/where you do stable addresses and/or temp addresses.
>>
>> RFC7217 covers that.
>>
>> Given the recent discussions on RFC4941, random MACs and on this
> document, I'm more and more leaning towards the opinion that we (as in
> the IETF) shouldn't have gotten into the business of trying to declare
> what people should put in the lower 64 bits. :-)
>>
>
> I think we should. What shouldn't have happened is embedding forms of
> layer 2 addresses in layer 3 IIDs.
>
>> We cannot all IPv6 implementations non-compliant by removing section 4
> of RFC2464 as this document proposes.
>>
>
> I think "deprecated" would be a better term for them.
>
>
>> Thought experiment. What if we abandon this document, and instead
> start work on updates to the IPv6 over foo documents? 2464bis specifically.
>>
>
> Don't we try to decouple layer 2 and 3 as much as possible, so we can
> slot in new layer 2s as they become available, and layer 3 hides those
> changes?

I can agree there can be a need to decouple layer 3 IDs from layer 2 
IDs.  One reason is this privacy concern.

Decoupling can be realized by offering a common interface between layer; 
and that's what IPv6-over-foo documents do: all link-layers look the 
same to an IP layer, because there is this interface described in an 
IPv6-over-foo document for each link-layer.

Such an interface should answer at least these questions:
- what is the MTU?  who fragments?
- what are the headers preceding and following the IP packet?
- how is the IID formed?
- how is a IP address mapped into that link-layer's address?
   (uni- and muti-cast).

Of these, only the IID formation has a privacy concern because of that 
layer2-in-3 aspect.

Without these multiple IPv6-over-foo documents the IP layer would not be 
that simple as it is.

> RFC6272, "Internet Protocols for the Smart Grid"
>
>
> "2. The Internet Protocol Suite"
>
> "2.1.3.1. Internet Protocol"
> [...]
>
> "The Internet layer provides a uniform network abstraction network
>    that hides the differences between various network technologies.
>    This is the layer that allows diverse networks such as Ethernet,
>    802.15.4, etc. to be combined into a uniform IP network.  New network
>    technologies can be introduced into the IP Protocol Suite by defining
>    how IP is carried over those technologies, leaving the other layers
>    of the IPS and applications that use those protocol unchanged."
>
>
> RFC7217 creates that addressing abstraction for stable addresses, as
> well as localising the IID meaning to a specific prefix, which is also
> the scope of an IID for the purposes of sending or receiving packets.
> Doing it once now means never having to do it again for
> IPv6-over-future-foo documents.

The notion of doing it once in a single place and impact positively many 
other parts of the system can be achieved with IPv6-over-Ethernet - most 
other IPv6-over-foo documents are more or less mirroring it.

Moreover, I would oppose discarding IPv6-over-foo documents.

The automaticity offered by an IPv6-over-foo tool in 
address-autoconfiguration is a very useful feature in IPv6 - it's great 
to have an IPv6 address there (LL) in the computer to start with, before 
thinking what address to manually configure, or what prefix to put in 
the RA.

It seems that if we used a random number in the IID (rather than a IEEE 
MAC address) then the privacy concern would be eased a bit.

But still the automaticity in address auto-configuration would be thus 
offered.

Additionally, there are other IDs shared between IPv6 addresses (see 
address mapping sections in IPv6-over-foo), which dont have privacy 
concerns.  I am thinking for example of the IDs in the multicast addresses.

As such, my thought is that updating RFC2464 to address the privacy 
concern in the IID can be a good idea.

Alex

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


From nobody Thu May 26 15:18:42 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 52EC212DB81 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:18:41 -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=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 6c1n8bqGJbpm for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:18:40 -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 20B8312DB82 for <ipv6@ietf.org>; Thu, 26 May 2016 15:18:40 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 8357680651; Fri, 27 May 2016 00:18:30 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5747751E.7030302@si6networks.com>
Date: Thu, 26 May 2016 18:13:50 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mKVdtSzXMt1KuXix17owsVslhhE>
Cc: draft-ietf-6man-default-iids@tools.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: Thu, 26 May 2016 22:18:41 -0000

Hi, Ole,

On 05/26/2016 04:23 AM, otroan@employees.org wrote:
>> 
>> Since there *are* scenarios where stable addresses are required
>> and/or desirable (whether -only or in addition to temp addresses),
>> the work in this document is of value, and orthogonal to any
>> further advice regarding of when/where you do stable addresses
>> and/or temp addresses.
> 
> RFC7217 covers that.
> 
> Given the recent discussions on RFC4941, random MACs and on this
> document, I'm more and more leaning towards the opinion that we (as
> in the IETF) shouldn't have gotten into the business of trying to
> declare what people should put in the lower 64 bits. :-)

I disagree. For two different reasons:

1) We have already done so, recommending a, say, not so nice approach.
Hence we need to fix that.

2) At the end of the day, the folk implementing IPv6 has to make a
decision. And if we don't provide good advice, we have to plan for the
worst.



> We cannot all IPv6 implementations non-compliant by removing section
> 4 of RFC2464 as this document proposes.

We're changing the default to something that is sec&privacy better.

We cannot really claim that mass survelliance and the like is a threat,
and then keep this in "'cause we don't want to update the code of
existing implementations".



> Thought experiment. What if we abandon this document, and instead
> start work on updates to the IPv6 over foo documents? 2464bis
> specifically.

default-iids already does this, for RFC2464 and other documents.

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





From nobody Thu May 26 15:35: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 3C00312D760 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:35:24 -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 JOUuMvI4IAkO for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:35: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 887B212D1BE for <6man@ietf.org>; Thu, 26 May 2016 15:35:18 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 8F98A806DC; Fri, 27 May 2016 00:35:11 +0200 (CEST)
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <57432678.7050901@si6networks.com> <CAKD1Yr0x9o5BzC3a-5ZH47g7i7ROkmsEYJc2UJyWdX6=Hcxcrg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <574779BC.5060607@si6networks.com>
Date: Thu, 26 May 2016 18:33:32 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0x9o5BzC3a-5ZH47g7i7ROkmsEYJc2UJyWdX6=Hcxcrg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/08MqUVmUQeYYIm41iWoleZ0KkFM>
Cc: "6man@ietf.org" <6man@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: Thu, 26 May 2016 22:35:24 -0000

On 05/26/2016 12:35 AM, Lorenzo Colitti wrote:
> On Tue, May 24, 2016 at 12:49 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     Say two autoconfiguration prefixes are advertised on the link.
> 
> 
> As I said in the part of my email that you did not quote, most networks
> only have one prefix that is used for off-network traffic. That is why I
> said it's a good engineering tradeoff, not a perfect solution.

FWIW, most networks don't configure global IPv6 addresses in the first
place. And regarding those networks where nodes do configure global
addresses, since you don't really know how many global prefixes there
will be there, you have to fail on the safe side.

It's not crazy to expect redundant connections in the future (IIRC, even
homenet expected that), even if that's not happening right now. And
whatever recommendations we provide have to accommodate such case
gracefully.



> You're right that it has flaws. Every scheme has correlation flaws
> unless it uses a different source address for every packet. The question
> is where do we make the tradeoff.
> 
> For example, your proposal to using different IIDs for different
> prefixes still has correlation opportunities if the host network stack
> uses both addresses to go to the same destination.

It doesn't. You cannot correlate the traffic by looking at the addresses
themselves. If you correlate traffic by looking elsewhere (say,
app-layer data), that's obviously out of the scope of this document, and
has to be fixed elsewhere.



>  OTOH, if the host
> stack only uses one of the addresses (like, say, Linux does), then using
> a different IID for each prefix has the same properties as using the
> same IID on every prefix since only one of the addresses will be used.

Which addresses will be used depend on a number of factors.

For example, in a stable-only scenario for server-like operations, the
addresses that get employed may depend on which addresses are posted on
the DNS. For client-side operations, it may depend on src addr selection.

OTOH, for a (client-like) stable-only scenario, if we have an IPv6
server that, say, has two different addresses in different prefixes, and
DNS round-robin is employed, it may be the case that one address (from
one prefix) is employed to connect to one of the server addresses, while
another is employed to connect to the other server address.

Again: fail on the safe side. We don't want to e.g. find that two-prefix
scenarios become quite common, and then have to update the specs again,
*late*, because we failed to be proactive.

We have to learn to be more OpenBSD-like in this respect.

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





From nobody Thu May 26 15:35:39 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 3414F12D68A for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15: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 IhR-a-fwXslV for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:35:28 -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 8377C12D1BE for <ipv6@ietf.org>; Thu, 26 May 2016 15:35:24 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 945CC806A6; Fri, 27 May 2016 00:35:20 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Lorenzo Colitti <lorenzo@google.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <57477A07.2010702@si6networks.com>
Date: Thu, 26 May 2016 18:34:47 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TQe-5mJEj6V36ww6R3Qiw1Y-6IE>
Cc: 6man <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, 26 May 2016 22:35:38 -0000

On 05/26/2016 12:45 AM, Lorenzo Colitti wrote:
> On Tue, May 24, 2016 at 7:38 AM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > P.S. My personal experiment in running my laptop for several days
>     > with no stable address has been completely successful. Including the
>     > fact that my prototype of the Anima signaling protocol crashed after
>     > a while, because the address it was relying on went away, which is of
>     > course the expected behaviour.
> 
>     So, the question is: can this be considered "acceptable" behavior?
> 
> Yes, because IPv6 address can expire and be replaced at any time in a
> renumbering event.

So... is, in your opinion, the likeliness of a renumbering event similar
to that of a node simply staying connected to the network for, say, one day?

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





From nobody Thu May 26 15:57:20 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 720E912D11B for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:57: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 5_jaiQKPza5U for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 15:57:17 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::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 249FB12D0A6 for <ipv6@ietf.org>; Thu, 26 May 2016 15:57:17 -0700 (PDT)
Received: by mail-pa0-x22a.google.com with SMTP id xk12so33646901pac.0 for <ipv6@ietf.org>; Thu, 26 May 2016 15:57:16 -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=SxXw+0hmhs+HFBHkTOP3cnbIyzN06sDVIh/CClLdUTU=; b=gaGAZ4/o+hDXta3J/fdk2KQHDVzXzBqfpjLyesTJWZsWhXNVoROruyaBlq4Lkrp09J l060H0dfqq6EbJqhiJdg9nRDvTwzUf4F5qNnJvHHl+TlNNzmmOJ6tbPIwG5Mw+nY8L+y h6l0xCoaAkS+BGvVWEkM+NDdQeNett3wmE5oFB50t/8dhqCKVUYSTyQfcSR23QT1JUjK ZfHp6cgaTU93TqEN+4u53k/VSk9Gn06ZQxDE8AmWyOlMqflU3StjhY6PNoQ7RgLAV21F li56xl6kk29iTjH4dmvr+mwd5Kv4ullUJmG45c8JvQ+J5DGW9w0KxJ6gMHjXWQw6lng8 hw6Q==
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=SxXw+0hmhs+HFBHkTOP3cnbIyzN06sDVIh/CClLdUTU=; b=H88ZyvL972Mb5Vlbvwt+U0gDJbuHGI50gmvLhPdO93ZAFdlyxLKdq/ji+0tiGTbWqP xGTjiFDT00+QB7El0EmHfRUwNkrt5wiX96zar9IFbEXyxL0eivtIwjRVgT2MXlR1So1g IvnhqwBGWZqqKogJNNDsKgMED8tv4hDjMy8Pg1QQt7xIf1mYHhStFTteFv7yNVWR4MTO V6mGtwTs36rwEhat5bHroolzYoCBPswa5fq/IeiWMiy4/2DzC8ZIKHz8iwPhrqfbqZq8 i37tmTD02o3H3pfHkdD/h/Vc7LuURu8fUpIrYS2TBGBakfRiZqFNe9dOy+iGINKUkvPu nFXw==
X-Gm-Message-State: ALyK8tK7bPMVce4eHKPgl/angf01hTNLi9nYoXqghCuBPktKabPESKwAnsurmlES2NroIA==
X-Received: by 10.67.7.71 with SMTP id da7mr17750547pad.136.1464303436547; Thu, 26 May 2016 15:57:16 -0700 (PDT)
Received: from ?IPv6:2406:e007:50f6:1:657d:4ed7:1b30:999? ([2406:e007:50f6:1:657d:4ed7:1b30:999]) by smtp.gmail.com with ESMTPSA id 66sm8466184pfb.64.2016.05.26.15.57.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 15:57:15 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Fernando Gont <fgont@si6networks.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com>
Date: Fri, 27 May 2016 10:57:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <57477A07.2010702@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZeEz1bkKDQ1UsDx_2Zw0BiqfuQA>
Cc: 6man <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, 26 May 2016 22:57:18 -0000

On 27/05/2016 10:34, Fernando Gont wrote:
> On 05/26/2016 12:45 AM, Lorenzo Colitti wrote:
>> On Tue, May 24, 2016 at 7:38 AM, Fernando Gont <fgont@si6networks.com
>> <mailto:fgont@si6networks.com>> wrote:
>>
>>     > P.S. My personal experiment in running my laptop for several days
>>     > with no stable address has been completely successful. Including the
>>     > fact that my prototype of the Anima signaling protocol crashed after
>>     > a while, because the address it was relying on went away, which is of
>>     > course the expected behaviour.
>>
>>     So, the question is: can this be considered "acceptable" behavior?
>>
>> Yes, because IPv6 address can expire and be replaced at any time in a
>> renumbering event.
> 
> So... is, in your opinion, the likeliness of a renumbering event similar
> to that of a node simply staying connected to the network for, say, one day?

Allegedly, with some ISPs in some countries (Germany was mentioned), yes,
that is the case. My ISP in NZ gives me a new prefix each time the ADSL
reconnects, which with a poor quality circuit could be a frequent
occurrence. We really need all layers of the protocol stack to cope
elegantly with unplanned renumbering.

    Brian


From nobody Thu May 26 16:00:36 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 DC5E312D515 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 prLFxxfzFN7M for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:00:34 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::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 6878B12D56E for <ipv6@ietf.org>; Thu, 26 May 2016 16:00:34 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id c127so90820665ywb.1 for <ipv6@ietf.org>; Thu, 26 May 2016 16:00:34 -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=n3fORL98dpvwcj6hig8/RwQLR1uYZ0j2fZBjoyju3qw=; b=TdnmJLZ+YtAMfsXlfWzzxRGaS5FBskou7bQGBJUeegzsbx67qkyTBQ+9n0/eXti4z2 0TmccddaP0j749XjOuD/dq9ZkBZY/v2BQsQtx11RLMzLJKqLEWPJDt1ONiDQZbn/xcST nd/F9D8GqgYfN7iCj0YCCsacqiv6P8SU5Ey/1XFZmd3z8azuUEpVwboKQxPGRQutIUa+ LliPpOTEZjFav5qwnDwagaU3vmdYk4BeqNEQUnKq0GR5GweEHIcV9DcxjQ5e7iCb1Kmz FPkiHwJVRIeAfMBjTOUqCqbrSZy6WL6ynKrR3G+WRFRx0W1ig/BQIPFl3Nf3i1SHp7oy V+sw==
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=n3fORL98dpvwcj6hig8/RwQLR1uYZ0j2fZBjoyju3qw=; b=EeUe/kKXrnuQcZqLaGS3zvE/H8z4b+ts4tSXJvkySgxiRe6OZnOkmGhIWuGg1J7ZSU 6kmJkrqQ9WyNJhe2/9WzBve+xb+zbGvMmclQQcTD3s8sbjjfAdCtZ0pUEQ6UVRnIDOAH w4mhflFs9HrbpB8vZG+OGh5e2dI0DdFEPXIol91kDvQZr/FSg7QOQ46U/4QWuL6pyFIp 6cvx4t6YK0IXdH44Zmk5anFf/4dDUKrWoI6zvHXAgwUGuX7HHJdcOsyIc3w7b40nmd2C Zg9MNLdeO+Wg4yZCqLHHHBQHfqqgh5mtEewmHFV7KSk6WhBjtLI4Wjbti+rmo9bbjQiO 7O+Q==
X-Gm-Message-State: ALyK8tIdW6xNH1C2oiB8o5muP9cbpCJk7BDvztsM4gGA7AyjvgutN527v2EzBZr2a3Clp8LXpi0YmFDaY/UQncY7
X-Received: by 10.129.80.139 with SMTP id e133mr7655670ywb.197.1464303633492;  Thu, 26 May 2016 16:00:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 16:00:14 -0700 (PDT)
In-Reply-To: <57477A07.2010702@si6networks.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 08:00:14 +0900
Message-ID: <CAKD1Yr0FwLvzY5sz4Gd9CDiL75AXtuXAKgN4KOGREw4wor9_wQ@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1147e532eb7a970533c6c1ef
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Db85jUHzgwa1Ehh3HziRarZzk-g>
Cc: 6man <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, 26 May 2016 23:00:36 -0000

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

On Fri, May 27, 2016 at 7:34 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> > Yes, because IPv6 address can expire and be replaced at any time in a
> > renumbering event.
>
> So... is, in your opinion, the likeliness of a renumbering event similar
> to that of a node simply staying connected to the network for, say, one
> day?


Given the default lifetimes used by implementations, s/one day/one week/ .

Most apps don't need to care about IP addresses, but for the ones that do:
sorry, yes, IPv6 is not IPv4, and addresses can and do change. Failure to
deal with that is a bug.

--001a1147e532eb7a970533c6c1ef
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 F=
ri, May 27, 2016 at 7:34 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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"">&gt; Y=
es, because IPv6 address can expire and be replaced at any time in a<br>
&gt; renumbering event.<br>
<br>
</span>So... is, in your opinion, the likeliness of a renumbering event sim=
ilar<br>
to that of a node simply staying connected to the network for, say, one day=
?</blockquote><div><br></div><div>Given the default lifetimes used by imple=
mentations, s/one day/one week/ .</div><div><br></div><div>Most apps don&#3=
9;t need to care about IP addresses, but for the ones that do: sorry, yes, =
IPv6 is not IPv4, and addresses can and do change. Failure to deal with tha=
t is a bug.</div></div></div></div>

--001a1147e532eb7a970533c6c1ef--


From nobody Thu May 26 16:22:26 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 CA42212D56E for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:22:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, 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 h9G-7XRDM1HU for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:22:22 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::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 A117612D557 for <6man@ietf.org>; Thu, 26 May 2016 16:22:22 -0700 (PDT)
Received: by mail-ig0-x234.google.com with SMTP id ct2so11479955igb.0 for <6man@ietf.org>; Thu, 26 May 2016 16:22:22 -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:date:message-id:subject :from:to:cc; bh=MIGlJtppKmQO2w7ogOK7xsn+/XYrhy2NfHIeXnAyU/s=; b=PstmOqh4C4PPkoZnQ2WqNDONTb8UhZ+mRPFV15S1sGlnN2jM7OCZTac70kqaEORnGx OSJ4qkRUM8nLfi5XzYmW89QXcOG2At/+BX6weIM08JWUwGontB6QCrnpCtjUjgYvUHWG W5PcOxJ2IZEeyhHqiZXeO5COShAPOF9v40v4LHIPNsPJ5XAYxlYOaV5REtDtMaR+sxRP XHF73TpoE8yI0kiRREkJEJTzE1KIohgSmZDatU1ObpxtCfUkNucmwW/8q1SV9afXoRCm xpPjD8hpsQs0iv/ACPf2qNvoZiV1F393KNQ8imSxh/jcEF9IOVLT2ptHQFltBnvU6fAU WQSw==
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:date :message-id:subject:from:to:cc; bh=MIGlJtppKmQO2w7ogOK7xsn+/XYrhy2NfHIeXnAyU/s=; b=XzNBlv5Dd5PCdPVJ7AjtfuOroBZ91RqWGsx+1AvY5mbjZiUrN1ZwTnvN4TdWF5VAzD PTaMJe//kkfBkcCOXs6GDQ/awwywnWHO/FPpKe8Z/BI8ilYMz7b8yy8B+tNGKhQ83fD4 Ul+b49cGtvP3X6OraJG07ll+bcLRmAX3iiXhJD80Ortl8aOm30JpkVukGFpK6/cuZ2+6 NmfS7hP8wkmFgZGkv2kyPJNwkqD6WM46sSpH9h4lOtfrKj3qndHk/wJrQD4VZrao/K+6 FkF5nOdLMalVUItmtUj7JrR0dF5+OtFNyBF4Qb25kcbNjQY5j5atmKco8XXW+V6b4InG s8CA==
X-Gm-Message-State: ALyK8tJ+mCX0RtSTQaK12Vz9V8/XXAYz3JcCd5KSSdGaBUnV2FKVLO/Ldzq4GIJ5v+k69h9IsNkmCR86e4x2WQ==
MIME-Version: 1.0
X-Received: by 10.50.55.194 with SMTP id u2mr5148956igp.41.1464304941949; Thu, 26 May 2016 16:22:21 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.159.148 with HTTP; Thu, 26 May 2016 16:22:21 -0700 (PDT)
In-Reply-To: <57438806.9010902@si6networks.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <57438806.9010902@si6networks.com>
Date: Thu, 26 May 2016 16:22:21 -0700
X-Google-Sender-Auth: sDzVdekYzL3k6ev-P1cmQ5EIQZE
Message-ID: <CAJE_bqe=W88raTaZq9N6wC8rXpiNQ5Mi1H8cQ9eRvX3xiRw3Lw@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yGZeTDOSXQgbhRDSkEhcf9x9Ybk>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 26 May 2016 23:22:25 -0000

At Mon, 23 May 2016 18:45:26 -0400,
Fernando Gont <fgont@si6networks.com> wrote:

> >>>    The recommendations in this document apply only in cases where
> >>>    implementations otherwise would have configured a stable IPv6 IID
> >>>    containing a link layer address. Configuring a stable IPv6 IID is
> >>>    OPTIONAL.
> >>
> >> Jinmei had some better text, IIRC. Jinmei?
> >
> > My suggested text was this:
> >
> >    The recommendations in this document apply only in cases where
> >    implementations otherwise would have configured a stable IPv6 IID
> >    containing a link layer address.  For example, this document does
> >    not change any existing recommendations concerning the use of
> >    temporary addresses as specified in [RFC4941], nor do the
> >    recommendations apply to cases where the link layer address is not
> >    stable (e.g., it is periodically randomized) in the first place,
> >    nor does it introduce any new requirements regarding when stable
> >    addresses are to be configured.
>
> DO you consider the scenario where a hsot configures an address for
> multiple prefixes, using the same IID?

Not really, partly because that's not my point in my response to the
WGLC.  I can answer that if you want to know what I think about it,
but I'll defer it to some different opportunity so we won't be
distracted about my main point.

> But that's one possible
> outcome if you allow link-layer identifiers in IPv6 addresses -- even if
> they are andomized.

[...]

> > And, basically, they didn't seem to be happy about it.  In the above
> > text I just tried to make the scope of this document super clear
> > (i.e., cases where the link-layer address is not stable are out of
> > scope of this document), but it looks like Fernando didn't even like
> > to mention it at all, or may even think we should explicitly recommend
> > against that:
> >
> >> The root of this problem is reusing a link-yaer ID at layer-3. THat's
> >> bad, and we have to recommend against that.
>
> Please see my comment above, besides Brian's example of two different
> layer-3 protocols embedding link-layer addresses....

As I already explained in the cited text, my suggestion was to attempt
of making this document less controversial and, really, only focus on
"cases where implementations otherwise would have configured a stable
IPv6 IID containing a link layer address", explicitly stating other
cases are out of scope.  Since randomized link-layer addresses
wouldn't be considered stable, they should be obviously out of scope
of the document, hence my suggestion.

But (to me at least) your response actually proposes expanding (or
changing) the scope of the document.  Instead of:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured a stable IPv6 IID
   containing a link layer address.

it should actually be stated:

   The recommendations in this document apply only in cases where
   implementations otherwise would have configured an IPv6 IID
   containing a link layer address.

(i.e, whether it's stable or not is not the point).

That's certainly one option, but I'd expect this will involve a lot
more discussions.  If you don't mind that, I'm not opposed to that; we
should simply conclude it doesn't pass the WGLC, clearly re-stating
the actual intent of the draft (i.e., it's not about stability but
about embedding link-layer address in IPv6 addresses) with rationale,
discuss the matter to death in the wg, then hopefully have another
WGLC.

--
JINMEI, Tatuya


From nobody Thu May 26 16:38:06 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 1062712D6D2 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:38:03 -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 VlwSj4BN_l_v for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 16:38:01 -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 432FC12D1D9 for <6man@ietf.org>; Thu, 26 May 2016 16:38:01 -0700 (PDT)
Received: from [192.168.3.104] (192-174-17-190.fibertel.com.ar [190.17.174.192]) (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 A2C95805E1; Fri, 27 May 2016 01:37:57 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <57438806.9010902@si6networks.com> <CAJE_bqe=W88raTaZq9N6wC8rXpiNQ5Mi1H8cQ9eRvX3xiRw3Lw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <574788B2.6070404@si6networks.com>
Date: Thu, 26 May 2016 19:37:22 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAJE_bqe=W88raTaZq9N6wC8rXpiNQ5Mi1H8cQ9eRvX3xiRw3Lw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1ckUF33sikDH9pcDiJj8lz0Tl-M>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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, 26 May 2016 23:38:03 -0000

Hi, Jinmei,

On 05/26/2016 07:22 PM, ç¥žæ˜Žé�”å“‰ wrote:
> At Mon, 23 May 2016 18:45:26 -0400,
> Fernando Gont <fgont@si6networks.com> wrote:
> 
>>>>>    The recommendations in this document apply only in cases where
>>>>>    implementations otherwise would have configured a stable IPv6 IID
>>>>>    containing a link layer address. Configuring a stable IPv6 IID is
>>>>>    OPTIONAL.
>>>>
>>>> Jinmei had some better text, IIRC. Jinmei?
>>>
>>> My suggested text was this:
>>>
>>>    The recommendations in this document apply only in cases where
>>>    implementations otherwise would have configured a stable IPv6 IID
>>>    containing a link layer address.  For example, this document does
>>>    not change any existing recommendations concerning the use of
>>>    temporary addresses as specified in [RFC4941], nor do the
>>>    recommendations apply to cases where the link layer address is not
>>>    stable (e.g., it is periodically randomized) in the first place,
>>>    nor does it introduce any new requirements regarding when stable
>>>    addresses are to be configured.
>>
>> DO you consider the scenario where a hsot configures an address for
>> multiple prefixes, using the same IID?
> 
> Not really, partly because that's not my point in my response to the
> WGLC.  I can answer that if you want to know what I think about it,
> but I'll defer it to some different opportunity so we won't be
> distracted about my main point.

You seem to be arguing against we saying that nodes must not embed
link-layer addresses in the IID (or at least asking us to explain
ourselves).

Would it help if we, say, explicitly include Brian's example of
multiple-layer-3 protocols and also note that if MAC addreses are
embedded, then addresses for multiple prefixes would employ the same
IID, and that that allows for traffic correlation?




>>> And, basically, they didn't seem to be happy about it.  In the above
>>> text I just tried to make the scope of this document super clear
>>> (i.e., cases where the link-layer address is not stable are out of
>>> scope of this document), but it looks like Fernando didn't even like
>>> to mention it at all, or may even think we should explicitly recommend
>>> against that:
>>>
>>>> The root of this problem is reusing a link-yaer ID at layer-3. THat's
>>>> bad, and we have to recommend against that.
>>
>> Please see my comment above, besides Brian's example of two different
>> layer-3 protocols embedding link-layer addresses....
> 
> As I already explained in the cited text, my suggestion was to attempt
> of making this document less controversial and, really, only focus on
> "cases where implementations otherwise would have configured a stable
> IPv6 IID containing a link layer address", explicitly stating other
> cases are out of scope.  Since randomized link-layer addresses
> wouldn't be considered stable, they should be obviously out of scope
> of the document, hence my suggestion.

Ok. Now I see where you were coming from. If anything, maybe we could
tweak your text and say that randomized MAC addresses would lead to
non-stable addresses, and hence their use is considered out of the scope
for this document? (I guess I could live with that)


> 
> But (to me at least) your response actually proposes expanding (or
> changing) the scope of the document.  Instead of:
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured a stable IPv6 IID
>    containing a link layer address.
> 
> it should actually be stated:
> 
>    The recommendations in this document apply only in cases where
>    implementations otherwise would have configured an IPv6 IID
>    containing a link layer address.
> 
> (i.e, whether it's stable or not is not the point).
> 
> That's certainly one option, but I'd expect this will involve a lot
> more discussions.

We certainly want to focus on stable addresses here, so yes I agree with
you. Please see my comment above -- I think we're starting to converge...

Thoughts?

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





From nobody Thu May 26 17:52:02 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 7941312DB72 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 17:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 kwqhHg5rWUhv for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 17:51:51 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 8767E12D9B0 for <ipv6@ietf.org>; Thu, 26 May 2016 17:51:50 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id c189so124259186vkb.1 for <ipv6@ietf.org>; Thu, 26 May 2016 17:51: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:date:message-id:subject:from:to :cc; bh=9R/6hoh6PHfygSyM86dtIyWf2iKv2Fqn1K0l+UfJTLE=; b=xgYBImawe/ht4+J0Nnc4HizIDZM5osV6W4AWL7MwC92XwGTs22bqmIuphE3CewXvYp ylBnt/GhNd2TOJkHJ2wSRJOft5gAbNy4WYYDQSr/4aNJweHvD+vJz2nt9biCSyI77LNP lIOxXIQG2O7BC/tO2ltjuHmrmjMtR6QLS2iBVD/Ae4aa61IC0ZC0Ibp69t72UmNPyhdo lRrdtoNiou1aU/ydDpbVJqAOHBTB8TkDh5CeO2oAT3Vrznz+Xt5qvfKIEBK1m1rMEgkB QGGdFnXJ43UyOcAK+da3jfrQakpRqqcVU8CxjghqHLs8MNBOb/qBYFk7hzLGEZRwc3HB xVSg==
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:date :message-id:subject:from:to:cc; bh=9R/6hoh6PHfygSyM86dtIyWf2iKv2Fqn1K0l+UfJTLE=; b=hHtFYdHvyjNKpkQRKJOH4ntkJHdjQSIgZTJRUq45Wv2Uo4REs2SEhn48y0g7ycPSQm f+QAKBwzBo1rlnRiKgU6Mi0zOb/ZrdgT+H5gIdE3fR6Ex6ApS8A2KpxAiR2PQtuRURI8 +PfeAFdILp8mDrSYBVH0ArbGlEPdT3M1pY+duM0/INEzYN8wk004371gtL48l9KTv3+9 WtfEPXc3Jr6hjOSMws7wXcxsyhMb82yqwCg1ytiZszJ4hM/8eyd7Zl4wWo1JSLSbgSNT VuqaYGrze/cDQ9mikwQpLVVI5bF/jrrN9la9o5V1jTNeXEDADkI4sVyYSKtO/9Pynf5H 9VaA==
X-Gm-Message-State: ALyK8tI8k7nertilr5mHLUrTNrh9fGOE4riPQHFvjEk2Tj6r+onpi3ZkJf5wG3iztddCTa8eahplKNyYMWvjvw==
MIME-Version: 1.0
X-Received: by 10.159.54.171 with SMTP id p40mr6188445uap.129.1464310309425; Thu, 26 May 2016 17:51:49 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 17:51:49 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 17:51:49 -0700 (PDT)
In-Reply-To: <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org>
Date: Fri, 27 May 2016 10:51:49 +1000
Message-ID: <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Mark Smith <markzzzsmith@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=94eb2c03fe2ad596520533c84f7f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ww1NVVFsbG9xpPe-Vvhiqc7Xy50>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Fri, 27 May 2016 00:51:54 -0000

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

Hi Ole,

On 26 May 2016 7:40 PM, <otroan@employees.org> wrote:
>
> Mark,
>
> > >>>> For a selected class of devices, I'm a huge fan of using EUI-64
based IIDs.
> > >>>> I agree that in general EUI-64 based IIDs are bad, but we can just
as
> > >>>> well write down when they make life easier.
> > >>>
> > >>> are you saying that you'd rather have seen a v6ops style document
giving recommendations for what type of IIDs should be used for an
enumerated set of scenarios?
> > >>
> > >> SUch a document, whether inv6ops or 6man would be useful. BUt
> > >> default-iids is orthogonal to that. It improves stable addresses
where
> > >> such addresses are to be used.
> > >>
> > >> Since there *are* scenarios where stable addresses are required
and/or
> > >> desirable (whether -only or in addition to temp addresses), the work
in
> > >> this document is of value, and orthogonal to any further advice
> > >> regarding of when/where you do stable addresses and/or temp
addresses.
> > >
> > > RFC7217 covers that.
> > >
> > > Given the recent discussions on RFC4941, random MACs and on this
document, I'm more and more leaning towards the opinion that we (as in the
IETF) shouldn't have gotten into the business of trying to declare what
people should put in the lower 64 bits. :-)
> > >
> >
> > I think we should. What shouldn't have happened is embedding forms of
layer 2 addresses in layer 3 IIDs.
>
> it was convenient at the time.

I completely understand the convenience of it, as I first operated IPX
before operating  IPv4. (From that experience, my view is that IPv6 has to
at least attain the operational convenience and usability that IPX and
AppleTalk were providing around 25 years ago.)

> it's still convenient in certain cases, but not as the default for _all_
devices.
>

Why not?

We should pick safe defaults. In terms of privacy, I think this is the
safest default for stable addresses. I also think it satisfies stable
address use cases that I can think of (mainly server and router interfaces).

I think it is better to avoid options, however an option to switch them off
or override them would not conflict with these being the out-of-the-box
default.

> > > We cannot all IPv6 implementations non-compliant by removing section
4 of RFC2464 as this document proposes.
> > >
> >
> > I think "deprecated" would be a better term for them.
>
> I'm not even sure we should do that.
> there are valid uses for the current scheme.
> it's implemented, deployed, understood and well tested.
> the company I work for have tens of IPv6 implementations and hundreds of
different products with IPv6 stacks in them. it's unlikely I'm going to
champion making a change from EUI-64 to 7217 in cases where it doesn't
provide value.
>

I'd be curious to know what those cases are, and how RFC7217s might reduce
value.

One specific case related to what your company builds is the criticism that
swapping a router interface module results in a different LL address. They
address that issue by using either static LLs or globals (tying all of
their internal next hop addresses to an external prefix, something I think
should be avoided).

RFC7217s can automate LL address generation on routers that doesn't have
this issue, as the Net_Iface parameter can be something that is stable
across router interface swaps e.g. stable Ifindex or stable
slot/module/interface location ID.

Some people would still do static router interface addressing if RFC7217s
were available, however it would now be more of a choice of wanting to
rather than having to to achieve router interface address stability.

> there are 2^64 ways to generate an IID, we can only provide general
advice.

I think we go a little further than that and always try to recommend good
general defaults that are safe. In the past it has probably was just
operationally safe.

More recently we've been making security safe recommendations (e.g.
security considerations section mandatory).

Now I think we have to consider whether it is necessary to make a privacy
safe default recommendation. I think in this case we do, because these
addresses can be exposed to parties who might seek to violate privacy -
even LLs on public access networks such as cafe Wifi networks.

> for mobile devices it is clearly not a good idea to embed L2 addresses in
L3 addresses.
> but for those devices a lot of other things aren't good ideas either. if
you really care about privacy I'm not quite sure if any of this would
really help you, but oh well.
>

I think of it this way - it doesn't have to be perfect, just as long as it
is usefully better.

For stable address use cases, I think these addresses are better for
privacy than embedded MAC address IIDs that don't change across networks or
prefixes. They of course don't solve all privacy issues that can occur at
the IPv6 and other layers of the stack.

> when we want to make recommendations that should apply to _all_ devices,
that's when we get into trouble. that's incredibly hard to do, because the
only answer we can agree on is: it depends.
>
> > > Thought experiment. What if we abandon this document, and instead
start work on updates to the IPv6 over foo documents? 2464bis specifically.
> > >
> >
> > Don't we try to decouple layer 2 and 3 as much as possible, so we can
slot in new layer 2s as they become available, and layer 3 hides those
changes?
> >
> > RFC6272, "Internet Protocols for the Smart Grid"
> >
> >
> > "2.  The Internet Protocol Suite"
> >
> > "2.1.3.1.  Internet Protocol"
> >
> >
> > [...]
> >
> > "The Internet layer provides a uniform network abstraction network
> >    that hides the differences between various network technologies.
> >    This is the layer that allows diverse networks such as Ethernet,
> >    802.15.4, etc. to be combined into a uniform IP network.  New network
> >    technologies can be introduced into the IP Protocol Suite by defining
> >    how IP is carried over those technologies, leaving the other layers
> >    of the IPS and applications that use those protocol unchanged."
> >
> >
> > RFC7217 creates that addressing abstraction for stable addresses, as
well as localising the IID meaning to a specific prefix, which is also the
scope of an IID for the purposes of sending or receiving packets. Doing it
once now means never having to do it again for IPv6-over-future-foo
documents.
>
> L2 and L3 are decoupled in the current model. an example of them being
coupled would have been if we had used the IID to determine the MAC address
instead of doing ND address resolution.
>

Agree - coming from a distant past IPX background, I actually found the use
of MAC addresses in IIDs and continued use of ND initially confusing. I
think that shows that the choice of MAC based IIDs was purely a choice of
convenience, as there was an optimisation opportunity that wasn't taken.
(For those reading who don't know, IPX doesn't do any form of address
resolution, it takes the destination node ID in the IPX packet and uses it
as the layer 2 destination address).

> This is not an argument against 7217. I think the default should be to
use 7217. If you want stable addresses. I don't want to make other schemes
non-compliant. And I think we have to remember that these are just
defaults. For SLAAC. People can and do configure IIDs any which way they
like.
>
> My point given that there is a level of uncomfortableness with this
document was to try to do the reverse. Can we find some updates to 2464
there is consensus on?
>

I suppose the trouble is that there are all the other Ipv6 over foo
documents. Does updating RFC2464 make it an unexplained special case, or
does it make all the other IPv6 over foo document ignored or forgotten
cases?

Regards,
Mark.

> Cheers,
> Ole
>

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

<p dir=3D"ltr"><br>
Hi Ole,</p>
<p dir=3D"ltr">On 26 May 2016 7:40 PM, &lt;<a href=3D"mailto:otroan@employe=
es.org">otroan@employees.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Mark,<br>
&gt;<br>
&gt; &gt; &gt;&gt;&gt;&gt; For a selected class of devices, I&#39;m a huge =
fan of using EUI-64 based IIDs.<br>
&gt; &gt; &gt;&gt;&gt;&gt; I agree that in general EUI-64 based IIDs are ba=
d, but we can just as<br>
&gt; &gt; &gt;&gt;&gt;&gt; well write down when they make life easier.<br>
&gt; &gt; &gt;&gt;&gt;<br>
&gt; &gt; &gt;&gt;&gt; are you saying that you&#39;d rather have seen a v6o=
ps style document giving recommendations for what type of IIDs should be us=
ed for an enumerated set of scenarios?<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; SUch a document, whether inv6ops or 6man would be useful=
. BUt<br>
&gt; &gt; &gt;&gt; default-iids is orthogonal to that. It improves stable a=
ddresses where<br>
&gt; &gt; &gt;&gt; such addresses are to be used.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Since there *are* scenarios where stable addresses are r=
equired and/or<br>
&gt; &gt; &gt;&gt; desirable (whether -only or in addition to temp addresse=
s), the work in<br>
&gt; &gt; &gt;&gt; this document is of value, and orthogonal to any further=
 advice<br>
&gt; &gt; &gt;&gt; regarding of when/where you do stable addresses and/or t=
emp addresses.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; RFC7217 covers that.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Given the recent discussions on RFC4941, random MACs and on =
this document, I&#39;m more and more leaning towards the opinion that we (a=
s in the IETF) shouldn&#39;t have gotten into the business of trying to dec=
lare what people should put in the lower 64 bits. :-)<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I think we should. What shouldn&#39;t have happened is embedding =
forms of layer 2 addresses in layer 3 IIDs.<br>
&gt;<br>
&gt; it was convenient at the time.</p>
<p dir=3D"ltr">I completely understand the convenience of it, as I first op=
erated IPX before operating=C2=A0 IPv4. (From that experience, my view is t=
hat IPv6 has to at least attain the operational convenience and usability t=
hat IPX and AppleTalk were providing around 25 years ago.)</p>
<p dir=3D"ltr">&gt; it&#39;s still convenient in certain cases, but not as =
the default for _all_ devices.<br>
&gt;</p>
<p dir=3D"ltr">Why not?</p>
<p dir=3D"ltr">We should pick safe defaults. In terms of privacy, I think t=
his is the safest default for stable addresses. I also think it satisfies s=
table address use cases that I can think of (mainly server and router inter=
faces).</p>
<p dir=3D"ltr">I think it is better to avoid options, however an option to =
switch them off or override them would not conflict with these being the ou=
t-of-the-box default.</p>
<p dir=3D"ltr">&gt; &gt; &gt; We cannot all IPv6 implementations non-compli=
ant by removing section 4 of RFC2464 as this document proposes.<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; I think &quot;deprecated&quot; would be a better term for them.<b=
r>
&gt;<br>
&gt; I&#39;m not even sure we should do that.<br>
&gt; there are valid uses for the current scheme.<br>
&gt; it&#39;s implemented, deployed, understood and well tested.<br>
&gt; the company I work for have tens of IPv6 implementations and hundreds =
of different products with IPv6 stacks in them. it&#39;s unlikely I&#39;m g=
oing to champion making a change from EUI-64 to 7217 in cases where it does=
n&#39;t provide value.<br>
&gt;</p>
<p dir=3D"ltr">I&#39;d be curious to know what those cases are, and how RFC=
7217s might reduce value.</p>
<p dir=3D"ltr">One specific case related to what your company builds is the=
 criticism that swapping a router interface module results in a different L=
L address. They address that issue by using either static LLs or globals (t=
ying all of their internal next hop addresses to an external prefix, someth=
ing I think should be avoided).</p>
<p dir=3D"ltr">RFC7217s can automate LL address generation on routers that =
doesn&#39;t have this issue, as the Net_Iface parameter can be something th=
at is stable across router interface swaps e.g. stable Ifindex or stable sl=
ot/module/interface location ID.</p>
<p dir=3D"ltr">Some people would still do static router interface addressin=
g if RFC7217s were available, however it would now be more of a choice of w=
anting to rather than having to to achieve router interface address stabili=
ty.</p>
<p dir=3D"ltr">&gt; there are 2^64 ways to generate an IID, we can only pro=
vide general advice.</p>
<p dir=3D"ltr">I think we go a little further than that and always try to r=
ecommend good general defaults that are safe. In the past it has probably w=
as just operationally safe.</p>
<p dir=3D"ltr">More recently we&#39;ve been making security safe recommenda=
tions (e.g. security considerations section mandatory). </p>
<p dir=3D"ltr">Now I think we have to consider whether it is necessary to m=
ake a privacy safe default recommendation. I think in this case we do, beca=
use these addresses can be exposed to parties who might seek to violate pri=
vacy - even LLs on public access networks such as cafe Wifi networks.<br></=
p>
<p dir=3D"ltr">&gt; for mobile devices it is clearly not a good idea to emb=
ed L2 addresses in L3 addresses.<br>
&gt; but for those devices a lot of other things aren&#39;t good ideas eith=
er. if you really care about privacy I&#39;m not quite sure if any of this =
would really help you, but oh well.<br>
&gt;</p>
<p dir=3D"ltr">I think of it this way - it doesn&#39;t have to be perfect, =
just as long as it is usefully better.</p>
<p dir=3D"ltr">For stable address use cases, I think these addresses are be=
tter for privacy than embedded MAC address IIDs that don&#39;t change acros=
s networks or prefixes. They of course don&#39;t solve all privacy issues t=
hat can occur at the IPv6 and other layers of the stack.<br></p>
<p dir=3D"ltr">&gt; when we want to make recommendations that should apply =
to _all_ devices, that&#39;s when we get into trouble. that&#39;s incredibl=
y hard to do, because the only answer we can agree on is: it depends.<br>
&gt;<br>
&gt; &gt; &gt; Thought experiment. What if we abandon this document, and in=
stead start work on updates to the IPv6 over foo documents? 2464bis specifi=
cally.<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Don&#39;t we try to decouple layer 2 and 3 as much as possible, s=
o we can slot in new layer 2s as they become available, and layer 3 hides t=
hose changes?<br>
&gt; &gt;<br>
&gt; &gt; RFC6272, &quot;Internet Protocols for the Smart Grid&quot;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &quot;2.=C2=A0 The Internet Protocol Suite&quot;<br>
&gt; &gt;<br>
&gt; &gt; &quot;2.1.3.1.=C2=A0 Internet Protocol&quot;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; [...]<br>
&gt; &gt;<br>
&gt; &gt; &quot;The Internet layer provides a uniform network abstraction n=
etwork<br>
&gt; &gt;=C2=A0 =C2=A0 that hides the differences between various network t=
echnologies.<br>
&gt; &gt;=C2=A0 =C2=A0 This is the layer that allows diverse networks such =
as Ethernet,<br>
&gt; &gt;=C2=A0 =C2=A0 802.15.4, etc. to be combined into a uniform IP netw=
ork.=C2=A0 New network<br>
&gt; &gt;=C2=A0 =C2=A0 technologies can be introduced into the IP Protocol =
Suite by defining<br>
&gt; &gt;=C2=A0 =C2=A0 how IP is carried over those technologies, leaving t=
he other layers<br>
&gt; &gt;=C2=A0 =C2=A0 of the IPS and applications that use those protocol =
unchanged.&quot;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; RFC7217 creates that addressing abstraction for stable addresses,=
 as well as localising the IID meaning to a specific prefix, which is also =
the scope of an IID for the purposes of sending or receiving packets. Doing=
 it once now means never having to do it again for IPv6-over-future-foo doc=
uments.<br>
&gt;<br>
&gt; L2 and L3 are decoupled in the current model. an example of them being=
 coupled would have been if we had used the IID to determine the MAC addres=
s instead of doing ND address resolution.<br>
&gt;</p>
<p dir=3D"ltr">Agree - coming from a distant past IPX background, I actuall=
y found the use of MAC addresses in IIDs and continued use of ND initially =
confusing. I think that shows that the choice of MAC based IIDs was purely =
a choice of convenience, as there was an optimisation opportunity that wasn=
&#39;t taken. (For those reading who don&#39;t know, IPX doesn&#39;t do any=
 form of address resolution, it takes the destination node ID in the IPX pa=
cket and uses it as the layer 2 destination address).</p>
<p dir=3D"ltr">&gt; This is not an argument against 7217. I think the defau=
lt should be to use 7217. If you want stable addresses. I don&#39;t want to=
 make other schemes non-compliant. And I think we have to remember that the=
se are just defaults. For SLAAC. People can and do configure IIDs any which=
 way they like.<br>
&gt;<br>
&gt; My point given that there is a level of uncomfortableness with this do=
cument was to try to do the reverse. Can we find some updates to 2464 there=
 is consensus on?<br>
&gt;</p>
<p dir=3D"ltr">I suppose the trouble is that there are all the other Ipv6 o=
ver foo documents. Does updating RFC2464 make it an unexplained special cas=
e, or does it make all the other IPv6 over foo document ignored or forgotte=
n cases?<br></p>
<p dir=3D"ltr">Regards,<br>
Mark.<br></p>
<p dir=3D"ltr">&gt; Cheers,<br>
&gt; Ole<br>
&gt;<br>
</p>

--94eb2c03fe2ad596520533c84f7f--


From nobody Thu May 26 18:27:40 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 1126712D095 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 18:27:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 WS5DYe9ifSxD for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 18:27:36 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 A41C812B062 for <ipv6@ietf.org>; Thu, 26 May 2016 18:27:36 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id k1so69840624vka.3 for <ipv6@ietf.org>; Thu, 26 May 2016 18:27:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=cTO7boVxMaCcIq7uc8unsStkiTZsOq0oitIX/xP8iXw=; b=yNxkM95fAgDG1uDBv6HUxVAstq3F+YcvGm/ClygaGs21ZtIwezgpiJKDWi2WyanwuX Mm4+dTsxgdoW344DPjqTWNyenPW5VL1g1v6W9p793HPlos85tha68XL+l4ANJwtPhvtI l//+/a3mEF6yscR/A/8ylsqdl1jEGXoAienYcfBjs4RwSK99AHUarm1SUeXy0iRONFEa EipVIFCkyxb2FmrOQWQunNcMlcJlSOSTM3b6d+L0+5xpUzKG0dP0NFDNWuzs3tkJshRm EbMBl8Dl4dR2XnudBHu78ZRd5joybXfICI/C32av8e0UBDFvS3bszTsQ6CEbN0rg0u63 su7Q==
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:date :message-id:subject:from:to:cc; bh=cTO7boVxMaCcIq7uc8unsStkiTZsOq0oitIX/xP8iXw=; b=W5n6dfjDJkXJz699EWGFVr+eOTBi+smyhYy5yUNpdTs/WY26iUXyIrG4E2hjq3fIA8 PbriFbuY6JZ1qxDBZKXFNXYzlsGJBAsY8Ovx6u/v/LguXCZqVrGdbJOdbHjiRWiKoRYA sOOuaBAaUoV7jJ8vrF0Kkf7mSEy1E9tOZz6YBApdm/MtDmICqwNZqAvgn3I7MxVccz4S A9Ufk5Maee+lJC4y+uq+Xbb596vyS2nk4hVnlfCFgyVbFJnbGogHHwDYbmnXGqkMjP5a M9n9tlhTbaB745vEl+nEiIrH65p44AZ8/kFbyVxJLx3qlhf6T6bN4tjOhD1ixzz0woia GxaA==
X-Gm-Message-State: ALyK8tLfViausL7UFqdiYFfcyzdDO5r5RMleDsEIjGI//olLPQGM+MPNZlMiR7/jPxS+ENVKegBdsEX4GY1azQ==
MIME-Version: 1.0
X-Received: by 10.31.167.10 with SMTP id q10mr6399023vke.44.1464312455683; Thu, 26 May 2016 18:27:35 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 18:27:35 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 18:27:35 -0700 (PDT)
In-Reply-To: <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com> <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com>
Date: Fri, 27 May 2016 11:27:35 +1000
Message-ID: <CAO42Z2yfRynbCtwcFpS2d__Si92=6jh3W4pqZHziVy7KLjSgSA@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
From: Mark Smith <markzzzsmith@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11426662c2e4cc0533c8cf27
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/49oGgIxdsogd6I8zJZMTTBVI5Sw>
Cc: Fernando Gont <fgont@si6networks.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, 27 May 2016 01:27:40 -0000

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

On 27 May 2016 8:57 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:
>
> On 27/05/2016 10:34, Fernando Gont wrote:
> > On 05/26/2016 12:45 AM, Lorenzo Colitti wrote:
> >> On Tue, May 24, 2016 at 7:38 AM, Fernando Gont <fgont@si6networks.com
> >> <mailto:fgont@si6networks.com>> wrote:
> >>
> >>     > P.S. My personal experiment in running my laptop for several days
> >>     > with no stable address has been completely successful. Including
the
> >>     > fact that my prototype of the Anima signaling protocol crashed
after
> >>     > a while, because the address it was relying on went away, which
is of
> >>     > course the expected behaviour.
> >>
> >>     So, the question is: can this be considered "acceptable" behavior?
> >>
> >> Yes, because IPv6 address can expire and be replaced at any time in a
> >> renumbering event.
> >
> > So... is, in your opinion, the likeliness of a renumbering event similar
> > to that of a node simply staying connected to the network for, say, one
day?
>
> Allegedly, with some ISPs in some countries (Germany was mentioned), yes,
> that is the case. My ISP in NZ gives me a new prefix each time the ADSL
> reconnects, which with a poor quality circuit could be a frequent
> occurrence.

A business decision might be behind that.

Here in AU, it is common to use a fixed verses dynamic IPv4 address as the
major technical difference between residential and higher priced SOHO
plans, so it wouldn't surprise me of that thinking followed though to IPv6
delegated prefixes.

That thinking will probably encourage NAT66 to gain back address stability
that was provided by NAT44 in a similar situation, which I think is
unfortunately a simpler solution than to incorporate into all apps code to
cope with unexpected addressing changes.

This wasn't the model for the production residential deployment I worked on
in 2010 - the /64 on the PPPoE session was dynamic, while the delegated /56
was fixed for the customer.

Regards,
Mark.

>We really need all layers of the protocol stack to cope
> elegantly with unplanned renumbering.
>
>     Brian
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 27 May 2016 8:57 AM, &quot;Brian E Carpenter&quot; &lt;<a href=3D"mailto=
:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt; wrote:<br=
>
&gt;<br>
&gt; On 27/05/2016 10:34, Fernando Gont wrote:<br>
&gt; &gt; On 05/26/2016 12:45 AM, Lorenzo Colitti wrote:<br>
&gt; &gt;&gt; On Tue, May 24, 2016 at 7:38 AM, Fernando Gont &lt;<a href=3D=
"mailto:fgont@si6networks.com">fgont@si6networks.com</a><br>
&gt; &gt;&gt; &lt;mailto:<a href=3D"mailto:fgont@si6networks.com">fgont@si6=
networks.com</a>&gt;&gt; wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0&gt; P.S. My personal experiment in runnin=
g my laptop for several days<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0&gt; with no stable address has been compl=
etely successful. Including the<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0&gt; fact that my prototype of the Anima s=
ignaling protocol crashed after<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0&gt; a while, because the address it was r=
elying on went away, which is of<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0&gt; course the expected behaviour.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;=C2=A0 =C2=A0 =C2=A0So, the question is: can this be considere=
d &quot;acceptable&quot; behavior?<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Yes, because IPv6 address can expire and be replaced at any t=
ime in a<br>
&gt; &gt;&gt; renumbering event.<br>
&gt; &gt;<br>
&gt; &gt; So... is, in your opinion, the likeliness of a renumbering event =
similar<br>
&gt; &gt; to that of a node simply staying connected to the network for, sa=
y, one day?<br>
&gt;<br>
&gt; Allegedly, with some ISPs in some countries (Germany was mentioned), y=
es,<br>
&gt; that is the case. My ISP in NZ gives me a new prefix each time the ADS=
L<br>
&gt; reconnects, which with a poor quality circuit could be a frequent<br>
&gt; occurrence. </p>
<p dir=3D"ltr">A business decision might be behind that.</p>
<p dir=3D"ltr">Here in AU, it is common to use a fixed verses dynamic IPv4 =
address as the major technical difference between residential and higher pr=
iced SOHO plans, so it wouldn&#39;t surprise me of that thinking followed t=
hough to IPv6 delegated prefixes.</p>
<p dir=3D"ltr">That thinking will probably encourage NAT66 to gain back add=
ress stability that was provided by NAT44 in a similar situation, which I t=
hink is unfortunately a simpler solution than to incorporate into all apps =
code to cope with unexpected addressing changes.</p>
<p dir=3D"ltr">This wasn&#39;t the model for the production residential dep=
loyment I worked on in 2010 - the /64 on the PPPoE session was dynamic, whi=
le the delegated /56 was fixed for the customer.<br></p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>
<p dir=3D"ltr">&gt;We really need all layers of the protocol stack to cope<=
br>
&gt; elegantly with unplanned renumbering.<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 Brian<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>

--001a11426662c2e4cc0533c8cf27--


From nobody Thu May 26 19:17:40 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 EC5F012D19E for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 CWILJykps8KP for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:17:36 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::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 6AF8D12D160 for <6man@ietf.org>; Thu, 26 May 2016 19:17:36 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id c127so94025970ywb.1 for <6man@ietf.org>; Thu, 26 May 2016 19:17:36 -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=Myi5UK5VWIerQANnoOr8aSFIWkSwPblaBe0YFzM/kSk=; b=c89bxzNuONZy5pnrzRy1TlmPNfxHCVnUc+o64Jyqd44/q9Uz4yWiDs5V1EdZzT9kwP xe2u/S3xEulHAfHOaC2CRGvNykvLOz2aNu/Zles0XjJbXy25UvCPwvM4X0IhU/Zmfh3/ Acgu2N3VR0jE6l3rxMKdX510xlQqbiWX4WERSDOrL8tyU41JlgYPo+wIWWtCtF1HdbFJ Rmk3Am6PgFjP/HRtC61A/OEZvIejwfbFnyww5q/HYtb9OfKUQeBjpp5b6Xj314YX8KaB ODB4MwCGwL3Lz6LQVqq28nZ4SDpefv34nM4yf/oUCO9dFnCLh42Byo7d2PorX40E9c/e I9Fw==
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=Myi5UK5VWIerQANnoOr8aSFIWkSwPblaBe0YFzM/kSk=; b=LOiKO42B+20niVwCkzkoNO1fhFpqYFhACi6cU3Y5EYXFO/jmcGXscysYK6kK4usdaJ 8W5IvwLvQ2penIslr9QIpKtkBAqzx1aPg/wmUEvvU1f+2YzUJAhGuoLyyLiTb4DsKxAp OadMmHQ7+ytGHaaqecrHZZdhQA3PETjvgp1DRw4zB7M2aD+QkR/1bCoC2KbvDgrH/MHB he0XF8NmT9t/t5QXMNF0OC+85SPOrzD5OFweBZ9sVE8izXJ2Tv25L+uBAt0iKgaxjAGX GtCUXhUyiIUNCfshSUwea2Tko4hIsC9Q8ObgRTv2iXBlx6NZ/rFMULU29J4whYU0dEJ0 xm0g==
X-Gm-Message-State: ALyK8tLFgPj2cBpuKx8yKE1bdES3Ys/QMh8WpeiFjQskm+nZY1UqzXuTznfv7R/5psuIzYh6D7cHqq6bMJ8WVPfT
X-Received: by 10.37.110.65 with SMTP id j62mr7261271ybc.155.1464315455353; Thu, 26 May 2016 19:17:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 19:17:15 -0700 (PDT)
In-Reply-To: <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 11:17:15 +0900
Message-ID: <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a1148acd28eb3fe0533c982e8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/utmHLI_h0tJgxKxyC7ueWs3SCHA>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Fri, 27 May 2016 02:17:38 -0000

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

On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
>
> So the problem is how to distinguish between attaching to a new link
> and re-attaching to the same link?
>

A simple algorithm would seem to be:

   1. If you don't support, or don't want to use, DNA, then every link is a
   new link and you start off with no IP addresses. So you form a link-local
   address, send an RS, etc. etc. starting from scratch.
   2. If you support and want to use DNA, then you use DNA with the same
   MAC address as you had before.

That requires that you decide in advance whether you think that the network
you are connecting to might be the same as a previously-visited network. In
many cases (e.g., you connect to an SSID that you have connected to
before), that is a decision that is possible to make.

--001a1148acd28eb3fe0533c982e8
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=
hu, May 26, 2016 at 3:15 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&g=
t;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
So the problem is how to distinguish between attaching to a new link<br>
and re-attaching to the same link?<br></blockquote><div><br></div><div>A si=
mple algorithm would seem to be:</div><div><ol><li>If you don&#39;t support=
, or don&#39;t want to use, DNA, then every link is a new link and you star=
t off with no IP addresses. So you form a link-local address, send an RS, e=
tc. etc. starting from scratch.</li><li>If you support and want to use DNA,=
 then you use DNA with the same MAC address as you had before.</li></ol></d=
iv><div>That requires that you decide in advance whether you think that the=
 network you are connecting to might be the same as a previously-visited ne=
twork. In many cases (e.g., you connect to an SSID that you have connected =
to before), that is a decision that is possible to make.</div></div></div><=
/div>

--001a1148acd28eb3fe0533c982e8--


From nobody Thu May 26 19:28:34 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 1049A12D144 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 dyLDbQ96Q9nI for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:28:31 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 322BB12B058 for <6man@ietf.org>; Thu, 26 May 2016 19:28:31 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id c127so94194293ywb.1 for <6man@ietf.org>; Thu, 26 May 2016 19:28:31 -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=UCAm1l4trXNhHeVmzZoSWfYOKnpeq497G1p9d3fSM50=; b=kP/MXo/FT/PcIhWjB/DrP9UHBV/BxZT2BEfHr4p4ZXUA2QoGuUPOfgYeT5dmUvSINm I7XPqlTaXb1s8EuuqaBdEbNOxOX/q+6RqBDO++gJST4O7GEjMw89K7NRfk7XFwcqDg49 kLxkef/xBj4CunZ93rAfDKvQMgjtyiReV7IwGQRgghi8cllpC293eUXxHhSh6xKznTkH 13mdxBG4RqaKRMfKx9Nl8dQL/nkSpRN8ajhx5JDABqrqVZscMvBP5F/urK3ulqZM5467 fSKLy6ByV4CAkVIKdec+yW6lnuE6phfkGr5L0tdj15lYvc8PE4tscStwSbzsfpFJcTju do2w==
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=UCAm1l4trXNhHeVmzZoSWfYOKnpeq497G1p9d3fSM50=; b=Yjbh9DcsO2V1QPAAdJvQXxf6aM5EHptYhuMN6Z5NyMtN1dLCdRNKyAFy5/jBs0kFNo cYxwmMsJLYqaEDdLRhAocyhro40EvPUujWtHlcYzKt9W7TQhuaV1hruHGyqP7EWnTD0C yYSTE+t1HN68BloSsDSlAWO01hJEONGwK57fckbmjrW66+ndXmM9Of+VBXX/V2cscg6k BtTThRP7ZfhN9FzMGHfb0NQcd/FRqtl8VbDdL9XOEKUBJ5N354bSkard3rae+5InCthB MyGhjowPy47llJn0onzr3kTusS6H3WIEe7SBg5Doj8vZUeohYOm/5ew68LssOYGDJNbo VRdA==
X-Gm-Message-State: ALyK8tK1jAxYMX64YK5z2WFEryXIVMr8YYYwVY8GO94+ohKcgof/LmrHBJJxdLLXhgMuEue4kr0kw0cF1RNnE7iN
X-Received: by 10.129.82.214 with SMTP id g205mr8139454ywb.66.1464316110130; Thu, 26 May 2016 19:28:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 19:28:10 -0700 (PDT)
In-Reply-To: <574779BC.5060607@si6networks.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <57432678.7050901@si6networks.com> <CAKD1Yr0x9o5BzC3a-5ZH47g7i7ROkmsEYJc2UJyWdX6=Hcxcrg@mail.gmail.com> <574779BC.5060607@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 11:28:10 +0900
Message-ID: <CAKD1Yr05XLmW53Ccm0kevEwtG=-C4Z+sL2nL0+0qKRmiOQZCCw@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a114dc69495e6c00533c9a9c8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wroN0vNw3H3YNGdq2kdpblNBq3U>
Cc: "6man@ietf.org" <6man@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: Fri, 27 May 2016 02:28:33 -0000

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

On Fri, May 27, 2016 at 7:33 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> FWIW, most networks don't configure global IPv6 addresses in the first
> place. And regarding those networks where nodes do configure global
> addresses, since you don't really know how many global prefixes there
> will be there, you have to fail on the safe side.
>

Saying that most networks don't have IPv6 is irrelevant because on those
networks it doesn't matter what the IPv6 stack does. What is relevant is
what happens on networks when IPv6 is present, and in the vast majority of
cases those networks have only one prefix.


> It's not crazy to expect redundant connections in the future (IIRC, even
> homenet expected that), even if that's not happening right now. And
> whatever recommendations we provide have to accommodate such case
> gracefully.
>

> For example, your proposal to using different IIDs for different
> > prefixes still has correlation opportunities if the host network stack
> > uses both addresses to go to the same destination.
>
> It doesn't. You cannot correlate the traffic by looking at the addresses
> themselves. If you correlate traffic by looking elsewhere (say,
> app-layer data), that's obviously out of the scope of this document, and
> has to be fixed elsewhere.
>

Declaring a problem out of scope doesn't mean that the problem goes away.

Again: fail on the safe side. We don't want to e.g. find that two-prefix
> scenarios become quite common, and then have to update the specs again,
> *late*, because we failed to be proactive.
>

Like I said, it's a tradeoff. Updating standards documents is one thing,
and writing an implementation is another. Given that our process involves
rough consensus AND running code, we should take into account
implementation complexity, and the people who write the implementations are
the ones that are best positioned to make statements on that. That goes
back to Ole's point about replacing all the implementations that currently
do SLAAC and his suggestion that perhaps it is better not to declare those
implementations noncompliant overnight.

--001a114dc69495e6c00533c9a9c8
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 F=
ri, May 27, 2016 at 7:33 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.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">FWIW, most networks don=
&#39;t configure global IPv6 addresses in the first<br>
place. And regarding those networks where nodes do configure global<br>
addresses, since you don&#39;t really know how many global prefixes there<b=
r>
will be there, you have to fail on the safe side.<br></blockquote><div><br>=
</div><div>Saying that most networks don&#39;t have IPv6 is irrelevant beca=
use on those networks it doesn&#39;t matter what the IPv6 stack does. What =
is relevant is what happens on networks when IPv6 is present, and in the va=
st majority of cases those networks have only one prefix.</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">It&#39;s not crazy to expect redundant =
connections in the future (IIRC, even<br>
homenet expected that), even if that&#39;s not happening right now. And<br>
whatever recommendations we provide have to accommodate such case<br>
gracefully.<br></blockquote><div><br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
span class=3D"">&gt; For example, your proposal to using different IIDs for=
 different<br>
&gt; prefixes still has correlation opportunities if the host network stack=
<br>
&gt; uses both addresses to go to the same destination.<br>
<br>
</span>It doesn&#39;t. You cannot correlate the traffic by looking at the a=
ddresses<br>
themselves. If you correlate traffic by looking elsewhere (say,<br>
app-layer data), that&#39;s obviously out of the scope of this document, an=
d<br>
has to be fixed elsewhere.<br></blockquote><div><br></div><div>Declaring a =
problem out of scope doesn&#39;t mean that the problem goes away.</div><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">Again: fail on the safe side. We =
don&#39;t want to e.g. find that two-prefix<br>
scenarios become quite common, and then have to update the specs again,<br>
*late*, because we failed to be proactive.<br></blockquote><div>=C2=A0<br><=
/div><div>Like I said, it&#39;s a tradeoff. Updating standards documents is=
 one thing, and writing an implementation is another. Given that our proces=
s involves rough consensus AND running code, we should take into account im=
plementation complexity, and the people who write the implementations are t=
he ones that are best positioned to make statements on that. That goes back=
 to Ole&#39;s point about replacing all the implementations that currently =
do SLAAC and his suggestion that perhaps it is better not to declare those =
implementations noncompliant overnight.</div></div></div></div>

--001a114dc69495e6c00533c9a9c8--


From nobody Thu May 26 19:31:26 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 020E712D144 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 TbclVkwL_sbP for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 19:31:23 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 82A3112D0ED for <ipv6@ietf.org>; Thu, 26 May 2016 19:31:23 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id x189so94226443ywe.3 for <ipv6@ietf.org>; Thu, 26 May 2016 19:31:23 -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=J27G2ouwZK9qoEwQhWe5N5NV4eMbNxjP8A6NAta7JRA=; b=IT67Rii5SvmGAAZFsf4K+kT1DTP4SQVSsYHNahqaYx2HjL+o4/BNBywr+bkVoymdh9 PZoToIR6SpdJQzKr7Z3a4YxSiVICVQ0VZAQnK+7Ztpa7cf95rOVbvfF4T+kZEXjm+y9X K9sC8IsOci7XZd2clWjQLygPV5b5LZfAyq9pjxKQ/UNgFh2zbpFAC3yQxGS6eWVr42Y8 7Q6MNXqmzW67b5lC2aRnODKdFQ7ik4BIWsovad7MxDV13EWlPKr2lPRZsbYx/Foyu//n C14QTk/jAwzGyzwlJOpxN/6TpfXiTjcmzDb0AuZH4ZtDta+MsCGimbsmJDa160Z1RL5G zVeg==
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=J27G2ouwZK9qoEwQhWe5N5NV4eMbNxjP8A6NAta7JRA=; b=a7Fm4/GI7I3N+NjSxEwZqOEh2wiBXRgcvTYE/fiscEo95GQqkc+8355otL/ZDPRRwZ GUdHH1mu89kmNvtUn9ScWXx3ZlBR6Qww/rr2OeBX48sTeJFkeGQMQZpJNxUlw0K2l2Lx UNxRLiGYF6R/NpG0KlVdOAU+lLpPLHmmg2NODScEp2g9h9ZsU+Z6OIW1tsActh6KE5IK cHr4SHSHWpGUvXRJSJ9UmXTphPxu2OMNJ5WDU2GmxsqiZnv2BXPWW/+5hKl4zkr2fhPc 2xE/SWQWRza2IF7PBtEQ3LIIjnHmkPAC7CqXjnFgU3BgG2Toli2f3Vr/kwXiYIEcI2r6 yEjw==
X-Gm-Message-State: ALyK8tKyTm9DQWTUw+K5tJW/Ugbga6nhN/YNke3EVPBKztpcNcsdJo92T5kAAJ27vnb8lEgDKje1+doaBz1otT3H
X-Received: by 10.129.146.87 with SMTP id j84mr8202188ywg.39.1464316282645; Thu, 26 May 2016 19:31:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 19:31:03 -0700 (PDT)
In-Reply-To: <CAO42Z2yfRynbCtwcFpS2d__Si92=6jh3W4pqZHziVy7KLjSgSA@mail.gmail.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com> <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com> <CAO42Z2yfRynbCtwcFpS2d__Si92=6jh3W4pqZHziVy7KLjSgSA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 11:31:03 +0900
Message-ID: <CAKD1Yr343MV4vdPLi1VoieinniX_hifqMxe+A3p-Juo-1284kA@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0921fede27890533c9b38f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nfv4TKn5sBQlqQ3mV3NlRurn9Os>
Cc: Fernando Gont <fgont@si6networks.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, 27 May 2016 02:31:25 -0000

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

On Fri, May 27, 2016 at 10:27 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> > Allegedly, with some ISPs in some countries (Germany was mentioned), yes,
> > that is the case. My ISP in NZ gives me a new prefix each time the ADSL
> > reconnects, which with a poor quality circuit could be a frequent
> > occurrence.
>
> A business decision might be behind that.
>
Actually reason I've heard given most often (definitely in Germany) is
privacy. Not sure if that is because it's easier to justify something by
saying "it's better for your privacy" than "it's better for our business
model" or because people do believe that this it's important to do it for
privacy reasons.

--94eb2c0921fede27890533c9b38f
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 F=
ri, May 27, 2016 at 10:27 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:markzzzsmith@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-left:1px #ccc solid;padding-left:1ex"><span><p dir=3D"ltr">&g=
t; Allegedly, with some ISPs in some countries (Germany was mentioned), yes=
,<br>
&gt; that is the case. My ISP in NZ gives me a new prefix each time the ADS=
L<br>
&gt; reconnects, which with a poor quality circuit could be a frequent<br>
&gt; occurrence. </p>
</span><p dir=3D"ltr">A business decision might be behind that.</p></blockq=
uote><div>Actually reason I&#39;ve heard given most often (definitely in Ge=
rmany) is privacy. Not sure if that is because it&#39;s easier to justify s=
omething by saying &quot;it&#39;s better for your privacy&quot; than &quot;=
it&#39;s better for our business model&quot; or because people do believe t=
hat this it&#39;s important to do it for privacy reasons.</div></div></div>=
</div>

--94eb2c0921fede27890533c9b38f--


From nobody Thu May 26 20:01:01 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 3989712D1D8 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 65yMft7lJkFh for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:00:58 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 0EF3E12D140 for <6man@ietf.org>; Thu, 26 May 2016 20:00:58 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id f66so127382866vkh.2 for <6man@ietf.org>; Thu, 26 May 2016 20:00: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=3vYX5lO3cr8nVnx0JaOSrPn2dtIN07rMKNpIPB7Xi6s=; b=TgNBBc3nhVJGpEvYkw0ZDf8BaYYdQJlQLYEyslJJgjf/gcJMiAidRU0XLoVWWVGdqP mCcdyt7J/815lt6/6P+E43SMVS3/SxZiEYMRSdCTlMCzVl+fVo5i+VKf9vKWx089B7wP jVQnZ6HQwS3bc5NblcgwJV3rYvrFDX5use45RfS7FhnLnYAAFY/nZTTD5G8YMGIsSu8l qiK9Rd1aWE/02uwSTyl17MddhdxFbBFjGf4x5zZabcHwVX7pO1o7rfO3zMHshjIZKia8 infV+cDHSn++g/v70w67FjP2bf5QbVoW3n7RR0kJGikVIV5UJr+Xxbu/Zvy/eVVp6ILY rV8Q==
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=3vYX5lO3cr8nVnx0JaOSrPn2dtIN07rMKNpIPB7Xi6s=; b=cGYgHaGts66IxAOUxw8fkVDKwEkAgQUz1Bj9+m1gyhHNDeJYALgP92s/P/EdsQe1oe SAE4K9KimFejXEBkAvml4fsJnTjxRYB/WEKc7JALzpMEgJJbqT5T40axJdqKvxXO5Zut 61zP+YqaUXFtuwZU+Uhy6DX7aSKAU99dRZRMoRK61ECE8b4jKpkLSFjslANzAq9ve103 /zIdHfHF91BW0E6oIUKplF1xKNrNNLIY+NPNuh2boLVsNyl5fhsfuWMiegjQB2dfqlV9 Eo11RcZZk0Ate8Xfqf9keUPB7tOEYJZhEHlvyew+tqm7s2xfXe50IA6C3ekgjjxBs+M4 CXVQ==
X-Gm-Message-State: ALyK8tJaBtBmFZuWZ/lLnby43lqWZSOaY9xDWCs7qP+0ZWCxjGhsMn+gR3VgUBRhc7XVyWw5lS813XCAqxsFvA==
X-Received: by 10.31.73.132 with SMTP id w126mr7360656vka.94.1464318057206; Thu, 26 May 2016 20:00:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 20:00:27 -0700 (PDT)
In-Reply-To: <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 27 May 2016 13:00:27 +1000
Message-ID: <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114dd5a0a358e10533ca1d57
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NhLrQ-MlauQPBBvTeDRDUMiotAs>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Fri, 27 May 2016 03:01:00 -0000

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

On 27 May 2016 at 12:17, Lorenzo Colitti <lorenzo@google.com> wrote:

> On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com>
> wrote:
>>
>> So the problem is how to distinguish between attaching to a new link
>> and re-attaching to the same link?
>>
>
> A simple algorithm would seem to be:
>
>    1. If you don't support, or don't want to use, DNA, then every link is
>    a new link and you start off with no IP addresses. So you form a link-local
>    address, send an RS, etc. etc. starting from scratch.
>
>
That is significantly reducing the robustness of e.g. TCP connections, as
they won't survive that event because their address will change.

Hosts are supposed to be tolerant of transient network events. In my
experience, that has included disconnection and reconnection of the host's
interface to the same link, which has included moving the host's patch
cable from one switch to another attached to the same LAN. I didn't rush
the patch cable move because at the time I didn't have any expectations
that my existing telnet sessions would survive.


>    1. If you support and want to use DNA, then you use DNA with the same
>    MAC address as you had before.
>
>
The issue with DNA is that it seems to be relying on the MAC address and
therefore the Link-Local address of the on-link routers being stable for as
the link remains operating. If routers were changing their MAC addresses
periodically too, then DNA will fail. It seems you've been arguing for no
stable L2 and/or L3 addresses on any device, so that would have to mean
that routers don't have them either.



> That requires that you decide in advance whether you think that the
> network you are connecting to might be the same as a previously-visited
> network. In many cases (e.g., you connect to an SSID that you have
> connected to before), that is a decision that is possible to make.
>

I can probably come up with more examples.

The point is that I don't think this whole problem/solution space has been
fully explored, and with the limited thinking I've done about it, I don't
think it is quite as simple as saying "use randomised MAC addresses" to
attain layer 2 and layer 3 privacy.

I can't seem to find the reference right now, however I think the DHCPv6
work you've pointed to only considered it in the context of the DHCPv6
protocol (RFC7824 now?), rather than implications to things like ND, upper
layer connections surviving, routers changing their LL addresses
periodically etc.

Regards,
Mark.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 27 May 2016 at 12:17, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.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"><div dir=3D"ltr"><div clas=
s=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, May 26, 2016 at 3:15 P=
M, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmith@gmail.co=
m" target=3D"_blank">markzzzsmith@gmail.com</a>&gt;</span> wrote:<blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
So the problem is how to distinguish between attaching to a new link<br>
and re-attaching to the same link?<br></blockquote><div><br></div><div>A si=
mple algorithm would seem to be:</div><div><ol><li>If you don&#39;t support=
, or don&#39;t want to use, DNA, then every link is a new link and you star=
t off with no IP addresses. So you form a link-local address, send an RS, e=
tc. etc. starting from scratch.</li></ol></div></div></div></div></blockquo=
te><div><br></div><div>That is significantly reducing the robustness of e.g=
. TCP connections, as they won&#39;t survive that event because their addre=
ss will change.</div><div><br></div><div>Hosts are supposed to be tolerant =
of transient network events. In my experience, that has included disconnect=
ion and reconnection of the host&#39;s interface to the same link, which ha=
s included moving the host&#39;s patch cable from one switch to another att=
ached to the same LAN. I didn&#39;t rush the patch cable move because at th=
e time I didn&#39;t have any expectations that my existing telnet sessions =
would survive.</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><ol><li=
>If you support and want to use DNA, then you use DNA with the same MAC add=
ress as you had before.</li></ol></div></div></div></div></blockquote><div>=
<br></div><div>The issue with DNA is that it seems to be relying on the MAC=
 address and therefore the Link-Local address of the on-link routers being =
stable for as the link remains operating. If routers were changing their MA=
C addresses periodically too, then DNA will fail. It seems you&#39;ve been =
arguing for no stable L2 and/or L3 addresses on any device, so that would h=
ave to mean that routers don&#39;t have them either.</div><div><br></div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div>That requires that you dec=
ide in advance whether you think that the network you are connecting to mig=
ht be the same as a previously-visited network. In many cases (e.g., you co=
nnect to an SSID that you have connected to before), that is a decision tha=
t is possible to make.</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">I can probably come=
 up with more examples.=C2=A0</div><div class=3D"gmail_extra"><br></div><di=
v class=3D"gmail_extra">The point is that I don&#39;t think this whole prob=
lem/solution space has been fully explored, and with the limited thinking I=
&#39;ve done about it, I don&#39;t think it is quite as simple as saying &q=
uot;use randomised MAC addresses&quot; to attain layer 2 and layer 3 privac=
y.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I c=
an&#39;t seem to find the reference right now, however I think the DHCPv6 w=
ork you&#39;ve pointed to only considered it in the context of the DHCPv6 p=
rotocol (RFC7824 now?), rather than implications to things like ND, upper l=
ayer connections surviving, routers changing their LL addresses periodicall=
y etc.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
>Regards,</div><div class=3D"gmail_extra">Mark.</div><div class=3D"gmail_ex=
tra"><br></div></div>

--001a114dd5a0a358e10533ca1d57--


From nobody Thu May 26 20:17:29 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 CD9B612D82A for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 uB_n87jtANrE for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:17:25 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::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 05B4C12D80F for <ipv6@ietf.org>; Thu, 26 May 2016 20:17:25 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id r140so127715716vkf.0 for <ipv6@ietf.org>; Thu, 26 May 2016 20:17: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=8eam/Q1Sj4xmh/vFdIWKZ2CRV4Kb38gvyeSp5OfvcUw=; b=xUJ7nDnB8aIsGsKa4JA452sPXz3lsPodeIqTJQXK1swDVLowWsUphTWppvydOc47W4 nsJV0k0ZXCJMyryOvap8DmFJDrlwEoN+t8a6pw0x++jddX/VQQ2YKT14C8W8qHKAQz11 pbG/M8rf7CzQE5ls9VeWDIv6IUjl/SLvQmS7DzCq7PIG5TcDl8mbY9ptYZWM6zEwiZVQ j4tZQ+8A/s5px7n1HSzmtqaGxAIHluwDJDN2h6ZGHrFR8NtP1wC/DqMiWovyP6Q4EdOJ 8WGgmRVmgTSB59/u/sOczoJoRfC77XH5Jzqf0sbA7jmfdguWiKW8H/ExV6dnZvHqXUlk gHPg==
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=8eam/Q1Sj4xmh/vFdIWKZ2CRV4Kb38gvyeSp5OfvcUw=; b=B7/XNzqFSwMgOsCHQUuR5ONtmUgfctt7poxAJG0Jic0tN9b0szRfs53L/HFOwswPbH jHYf5BjpS9b/1bhcpCf7if9CLJbM7IQk2Wur8LXK5WA561DHYY4V846ulU6m1GDckc0y nE8YQIE3ikNZLWg/lbBiwg3ePHi6wvr19i9+5DjVnb0Vn3GxteqU4n2W5+HzvYww+4Jd rqc2j2Jp4k0i8hVrgRvJbtBovfS6ROTs9NcOnfnT2jPmURGEA3pIadb7yHm+kOy6qLnU 90GvaHt2FfL5Gkd5fCrafTJpsXysW5MBvJu3lc5KKMcQsbJvAUjKkKa/oSELjkd7dXIP V67g==
X-Gm-Message-State: ALyK8tLk0h3UtQJt8UMg7zFr6TjovcaMPEZ7VEQGjg/ahraPJhCawPidr5vipvkaAMoAo3wd94PBHfWWRH2Vgg==
X-Received: by 10.31.216.70 with SMTP id p67mr6276062vkg.129.1464319044080; Thu, 26 May 2016 20:17:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Thu, 26 May 2016 20:16:54 -0700 (PDT)
In-Reply-To: <CAKD1Yr343MV4vdPLi1VoieinniX_hifqMxe+A3p-Juo-1284kA@mail.gmail.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com> <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com> <CAO42Z2yfRynbCtwcFpS2d__Si92=6jh3W4pqZHziVy7KLjSgSA@mail.gmail.com> <CAKD1Yr343MV4vdPLi1VoieinniX_hifqMxe+A3p-Juo-1284kA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 27 May 2016 13:16:54 +1000
Message-ID: <CAO42Z2yfa=5uvBjggHaPNErrqUEnFmzPkrD4myEBPGSLrCVwfQ@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114ef08675d94e0533ca5875
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/i8XMBCCrEJYFrjoga2-5qCWBqVg>
Cc: Fernando Gont <fgont@si6networks.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, 27 May 2016 03:17:27 -0000

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

On 27 May 2016 at 12:31, Lorenzo Colitti <lorenzo@google.com> wrote:

> On Fri, May 27, 2016 at 10:27 AM, Mark Smith <markzzzsmith@gmail.com>
> wrote:
>
>> > Allegedly, with some ISPs in some countries (Germany was mentioned),
>> yes,
>> > that is the case. My ISP in NZ gives me a new prefix each time the ADSL
>> > reconnects, which with a poor quality circuit could be a frequent
>> > occurrence.
>>
>> A business decision might be behind that.
>>
> Actually reason I've heard given most often (definitely in Germany) is
> privacy. Not sure if that is because it's easier to justify something by
> saying "it's better for your privacy" than "it's better for our business
> model" or because people do believe that this it's important to do it for
> privacy reasons.
>

I understand it for the privacy reasons. I think it would be reasonable for
an ISP to provide customers, perhaps as a default with an opt out, periodic
phased change of delegated prefix over a time period that also provides
address stability for most applications e.g., once a day or possibly once a
week which would align with the preferred or valid lifetimes of RFC4941
addresses. A customer could be given an option to either switch that
changing off completely, initiate it manually, or be able to change the
default time period.

The trouble with what Brian's ISP is doing is that a transient fault is
causing the prefixes to change abruptly and that is fatal to existing TCP
connections using addresses from those prefixes. The point of attachment to
the network hasn't changed, so the prefixes shouldn't change in response to
the transient fault. Persistent prefixes across these sort of faults
wouldn't be contrary to the phased and intended changing over time of
delegated prefixes as above.

Regards,
Mark.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 27 May 2016 at 12:31, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.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"><div dir=3D"ltr"><div clas=
s=3D"gmail_extra"><div class=3D"gmail_quote">On Fri, May 27, 2016 at 10:27 =
AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmith@gmail.c=
om" target=3D"_blank">markzzzsmith@gmail.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><span><p dir=3D"ltr">&gt; Allegedly, with some IS=
Ps in some countries (Germany was mentioned), yes,<br>
&gt; that is the case. My ISP in NZ gives me a new prefix each time the ADS=
L<br>
&gt; reconnects, which with a poor quality circuit could be a frequent<br>
&gt; occurrence. </p>
</span><p dir=3D"ltr">A business decision might be behind that.</p></blockq=
uote><div>Actually reason I&#39;ve heard given most often (definitely in Ge=
rmany) is privacy. Not sure if that is because it&#39;s easier to justify s=
omething by saying &quot;it&#39;s better for your privacy&quot; than &quot;=
it&#39;s better for our business model&quot; or because people do believe t=
hat this it&#39;s important to do it for privacy reasons.</div></div></div>=
</div>
</blockquote></div><br></div><div class=3D"gmail_extra">I understand it for=
 the privacy reasons. I think it would be reasonable for an ISP to provide =
customers, perhaps as a default with an opt out, periodic phased change of =
delegated prefix over a time period that also provides address stability fo=
r most applications e.g., once a day or possibly once a week which would al=
ign with the preferred or valid lifetimes of RFC4941 addresses. A customer =
could be given an option to either switch that changing off completely, ini=
tiate it manually, or be able to change the default time period.</div><div =
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The trouble with=
 what Brian&#39;s ISP is doing is that a transient fault is causing the pre=
fixes to change abruptly and that is fatal to existing TCP connections usin=
g addresses from those prefixes. The point of attachment to the network has=
n&#39;t changed, so the prefixes shouldn&#39;t change in response to the tr=
ansient fault. Persistent prefixes across these sort of faults wouldn&#39;t=
 be contrary to the phased and intended changing over time of delegated pre=
fixes as above.</div><div class=3D"gmail_extra"><br></div><div class=3D"gma=
il_extra">Regards,</div><div class=3D"gmail_extra">Mark.</div><div class=3D=
"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra"><br></div><div class=3D"gmail_extra"><br></div></div>

--001a114ef08675d94e0533ca5875--


From nobody Thu May 26 20:21:17 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 ED1D712D1C8 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 uHE2EkMhQ7cX for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:21:14 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 1FCFA12D116 for <6man@ietf.org>; Thu, 26 May 2016 20:21:14 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id c127so94991465ywb.1 for <6man@ietf.org>; Thu, 26 May 2016 20:21:14 -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=PXE6P1qXrOqyBBODGb7TP3xjuxaMOs0SnzbbqE/Dw2c=; b=AcfnF6a9CGpsL3PLZxTQrWtQbjhE/DxBhjYPXeh4xDWegUhPc+4tryW/oH/mbXWtV+ qiOI8A00Pj0qaLk5FmLnRbHJrPcL1MGKKpcKngijwPbLMHfFT86u4zmH8813hlO6m7rR gvQMlGl6lGcLLlKeUx8ReiwUlQC6mcCA8oSsN8RiYzqQ0sd8UF/hwVP7bxIyY2vp4j9c iEbU0FJfz37pGybZTmVkhtutkAT5Lx49uWcbAPdcCJy7otQNDcdj5RZor5FxdHixKmL8 /W4wST6tHijWGdYGD2py9uRsmiUDNYmoCVCy1uujL0zoFYEfAcjjzOoxzvO0mWT8Hcw3 DMqA==
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=PXE6P1qXrOqyBBODGb7TP3xjuxaMOs0SnzbbqE/Dw2c=; b=AT3W0TXjhIvpo6KPfexldjXDqGa8k0GeK1j0/uJaBQkWrMPliJ/G7tZNDm0TxUj9kf MNv0vJsxP/zz6V+/uxtkQ4aXmqtZG/xIKj3/1jGR2EWJ67ICn+x600rukLWjlIAQpCxI JmEy2eNaE5p71id9JpJBTyFnOl4MGCgTbX2e3vfRntwU1+fDDXUDmmC1Oo5e2NERuYK3 E/Ja51e6JsjTpMe83ztzmynspenNBjBvPQGECyncmNA606AWdV3FzrmyBcNWDeQSvAAj uJAMF/WNjGHAeEArswmZiu13KqAuHmYQFseTMnppGsjg8JqlKZwlOAfVpLoekLSUJwof Lisg==
X-Gm-Message-State: ALyK8tJpqRzCjRm4ocsDylmtcVeDIagvBnTyAwVvgMKojuLO5iYUo9umAEkJc9Wu1ZFGvw7GX8Cs6oiQGvEvWR24
X-Received: by 10.37.228.198 with SMTP id b189mr7584772ybh.25.1464319272923; Thu, 26 May 2016 20:21:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 20:20:53 -0700 (PDT)
In-Reply-To: <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 12:20:53 +0900
Message-ID: <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114bc1c61a3cf50533ca66ea
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NsjxtBEUKqKL_JNQGT-D6VlpuQw>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Fri, 27 May 2016 03:21:16 -0000

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

On Fri, May 27, 2016 at 12:00 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

> A simple algorithm would seem to be:
>>
>>    1. If you don't support, or don't want to use, DNA, then every link
>>    is a new link and you start off with no IP addresses. So you form a
>>    link-local address, send an RS, etc. etc. starting from scratch.
>>
>>
> That is significantly reducing the robustness of e.g. TCP connections, as
> they won't survive that event because their address will change.
>

Most mobile devices close all TCP connections every time a network
disconnects, anyway. The reason for this is that if the device switches to
a different network, the TCP connections are dead anyway (because the IP
address changes) and apps just get stuck. Keeping the connection alive is
only useful if you think that there's a very high chance of reconnecting to
the same network soon, and you either have no other network in the
meantime, or you think you're going to reconnect so soon that it doesn't
make sense to re-establish a connection on another network.


>
>>    1. If you support and want to use DNA, then you use DNA with the same
>>    MAC address as you had before.
>>
>>
> The issue with DNA is that it seems to be relying on the MAC address and
> therefore the Link-Local address of the on-link routers being stable for as
> the link remains operating. If routers were changing their MAC addresses
> periodically too, then DNA will fail. It seems you've been arguing for no
> stable L2 and/or L3 addresses on any device, so that would have to mean
> that routers don't have them either.
>

Actually, I don't expect that routers will need random MAC addresses.

--001a114bc1c61a3cf50533ca66ea
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 F=
ri, May 27, 2016 at 12:00 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><span class=3D"gmail-"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>A simple algorith=
m would seem to be:</div><div><ol><li>If you don&#39;t support, or don&#39;=
t want to use, DNA, then every link is a new link and you start off with no=
 IP addresses. So you form a link-local address, send an RS, etc. etc. star=
ting from scratch.</li></ol></div></div></div></div></blockquote><div><br><=
/div></span><div>That is significantly reducing the robustness of e.g. TCP =
connections, as they won&#39;t survive that event because their address wil=
l change.</div></div></div></div></blockquote><div><br></div><div>Most mobi=
le devices close all TCP connections every time a network disconnects, anyw=
ay. The reason for this is that if the device switches to a different netwo=
rk, the TCP connections are dead anyway (because the IP address changes) an=
d apps just get stuck. Keeping the connection alive is only useful if you t=
hink that there&#39;s a very high chance of reconnecting to the same networ=
k soon, and you either have no other network in the meantime, or you think =
you&#39;re going to reconnect so soon that it doesn&#39;t make sense to re-=
establish a connection on another network.</div><div>=C2=A0</div><blockquot=
e 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-lef=
t:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quot=
e"><span class=3D"gmail-"><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-lef=
t-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"g=
mail_extra"><div class=3D"gmail_quote"><div><ol><li>If you support and want=
 to use DNA, then you use DNA with the same MAC address as you had before.<=
/li></ol></div></div></div></div></blockquote><div><br></div></span><div>Th=
e issue with DNA is that it seems to be relying on the MAC address and ther=
efore the Link-Local address of the on-link routers being stable for as the=
 link remains operating. If routers were changing their MAC addresses perio=
dically too, then DNA will fail. It seems you&#39;ve been arguing for no st=
able L2 and/or L3 addresses on any device, so that would have to mean that =
routers don&#39;t have them either.</div></div></div></div></blockquote><di=
v><br></div><div>Actually, I don&#39;t expect that routers will need random=
 MAC addresses.</div></div></div></div>

--001a114bc1c61a3cf50533ca66ea--


From nobody Thu May 26 20:53:16 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 BD44412D50C for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:53:14 -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 rUvSKFwmXUPz for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 20:53:13 -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 130DE12D170 for <ipv6@ietf.org>; Thu, 26 May 2016 20:53:13 -0700 (PDT)
Received: by mail-pa0-x231.google.com with SMTP id xk12so35819467pac.0 for <ipv6@ietf.org>; Thu, 26 May 2016 20:53:13 -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=hjNJM6sQu0Y8nS43I5qAb7iyLoWGDLCdgakUr4NlWQc=; b=FhN7UmptWaUnh6lcMVnUXx85PIJJhIsM9IIzHi7aA2NMHZjhquZ/UnTI30fBlfe+Ux Ms95CN/8fE20zS8JKwUW8BjoyExw9iiRNR+k2hYGpX4RBoRm05xi0PhHiTMPfI/E8Bgi YAdzv7bUWjfRh0ECZ++Rlawt/nMFohMCWU3zEkKWGDdWfuuf4EB6ci4VB984mCHN9ioJ KRdvVU7KenZr51vkFbQ7cUrqKd90K0+D2ZLxhppBjWiQV7bN5RfRtxDy3oPNx4hb8SvW J0y7XvEZm8IpsahHT9DDRoAJaBumEEyYwGNKu5j+fPtbAxaixyGy6QQ72IY7pAbrq3VX NzpQ==
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=hjNJM6sQu0Y8nS43I5qAb7iyLoWGDLCdgakUr4NlWQc=; b=FJr52BAWIOjz3Nb4Yeg5Bn3/SNcgbC4Whmuwnu8bCeBE22pLn7/KlZ94r5UOnlW0qV yyo36PtwqoFPw1np9ih7WaM1iOkj7+ToL13FJZnNxe9Ebax9N3tx9hqZX0pjAaOSQNKQ FCBeWeqbYeHqMe+21fhunAPHIJn/vX0+7XoZtMW6BKg/4ej9A3zT9yVuVW9dl+0SQ/Ig HgjuO44WXsQ8Fz4jLdsqcfOYGYvqBVog79m4CbLFBslFkC0/ZnxFoAs4mGC8tZSeOkaO STW9ubrMg4/4/S+mqQzYG4neihPmHShR5RAASHOJdqUFXcrxeTIuRVnZJDvnlXRlXLO9 WBow==
X-Gm-Message-State: ALyK8tKhdD4VmXB0EJcddrK2c6teFeuR7UsgtCOLYxj6sajZEOVND/1quexNFkiIt1Z8jg==
X-Received: by 10.66.236.167 with SMTP id uv7mr19307105pac.75.1464321192610; Thu, 26 May 2016 20:53:12 -0700 (PDT)
Received: from ?IPv6:2406:e007:50f6:1:3956:4fea:bc3f:719f? ([2406:e007:50f6:1:3956:4fea:bc3f:719f]) by smtp.gmail.com with ESMTPSA id u78sm3987420pfi.78.2016.05.26.20.53.09 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 20:53:11 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Mark Smith <markzzzsmith@gmail.com>, Lorenzo Colitti <lorenzo@google.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <5743864F.2080705@si6networks.com> <CAKD1Yr0YNovq9-WE61AdRYcvgMsjRL=UiasqONSrL2DUNpjQAw@mail.gmail.com> <57477A07.2010702@si6networks.com> <29070f15-c239-8105-db72-f7cffbdd8466@gmail.com> <CAO42Z2yfRynbCtwcFpS2d__Si92=6jh3W4pqZHziVy7KLjSgSA@mail.gmail.com> <CAKD1Yr343MV4vdPLi1VoieinniX_hifqMxe+A3p-Juo-1284kA@mail.gmail.com> <CAO42Z2yfa=5uvBjggHaPNErrqUEnFmzPkrD4myEBPGSLrCVwfQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <07662a66-66b1-89fa-75c6-10a12d9bb912@gmail.com>
Date: Fri, 27 May 2016 15:53:20 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAO42Z2yfa=5uvBjggHaPNErrqUEnFmzPkrD4myEBPGSLrCVwfQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-Ho8uXuw5mvGZtQVMT6uCL4W-Cg>
Cc: Fernando Gont <fgont@si6networks.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, 27 May 2016 03:53:15 -0000

On 27/05/2016 15:16, Mark Smith wrote:
> On 27 May 2016 at 12:31, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
>> On Fri, May 27, 2016 at 10:27 AM, Mark Smith <markzzzsmith@gmail.com>
>> wrote:
>>
>>>> Allegedly, with some ISPs in some countries (Germany was mentioned),
>>> yes,
>>>> that is the case. My ISP in NZ gives me a new prefix each time the ADSL
>>>> reconnects, which with a poor quality circuit could be a frequent
>>>> occurrence.
>>>
>>> A business decision might be behind that.
>>>
>> Actually reason I've heard given most often (definitely in Germany) is
>> privacy. Not sure if that is because it's easier to justify something by
>> saying "it's better for your privacy" than "it's better for our business
>> model" or because people do believe that this it's important to do it for
>> privacy reasons.
>>
> 
> I understand it for the privacy reasons. I think it would be reasonable for
> an ISP to provide customers, perhaps as a default with an opt out, periodic
> phased change of delegated prefix over a time period that also provides
> address stability for most applications e.g., once a day or possibly once a
> week which would align with the preferred or valid lifetimes of RFC4941
> addresses. A customer could be given an option to either switch that
> changing off completely, initiate it manually, or be able to change the
> default time period.
> 
> The trouble with what Brian's ISP is doing is that a transient fault is
> causing the prefixes to change abruptly and that is fatal to existing TCP
> connections using addresses from those prefixes. The point of attachment to
> the network hasn't changed, so the prefixes shouldn't change in response to
> the transient fault. Persistent prefixes across these sort of faults
> wouldn't be contrary to the phased and intended changing over time of
> delegated prefixes as above.

Next time I'm the sole user in the apartment, I'll try a very brief
disconnection just to check if the prefix really changes on a transient.
Normally the ADSL service stays up nicely, unless we power down the FritzBox.

   Brian


From nobody Thu May 26 21:26:14 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 2EC5E12D524 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 21:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 f7WpSL7qSOop for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 21:26:10 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 A97BD12D1A6 for <ipv6@ietf.org>; Thu, 26 May 2016 21:26:10 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id h19so96076555ywc.0 for <ipv6@ietf.org>; Thu, 26 May 2016 21:26:10 -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=gs+qq7h0LrB+dCFIcauAcm5NahRBNwXe9XcEn/cgtq0=; b=TU8phaCJowcDDffATW7atLNZw41rpqxwz0ENvEv7pd5ZrhIA2362WFEQGwJNuzR3O8 QHe0XBjRN7VO05j5Ed8N0a7V27NPi0aKY9XNS4io65QliUiOhte7j0z7yDeDarc2d9fL oJDkn1koegrZN+DoL/9hfD5FRO39SRhTsdrsTAMs5t8PiTGiaQbD1lfl/nQQo3tyV8WN 7qm7nl/QN8D4gRys8zeqJMXBbfT5rB3p7I7So/p+O/9CN/wcrXLz0SY7EOQ5mJav670s Uqb3JsdqKY9jJAeOJ5hNcnluvlUJOsPP9W4W+gpdx2HnRy7dxlfqwgfQbFOVh9VxFesQ bUyw==
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=gs+qq7h0LrB+dCFIcauAcm5NahRBNwXe9XcEn/cgtq0=; b=WF7qZWbWLnOCBTF5ff0wqyyp6ccOvku/zH6KOJ5/5tBd2oHnHKQ/qmKSm6fpqqKb9o C2fCOwpeYbGff/C6J7bGc7gOsAQKwhXQXQxTZhEYhb0jFzrXMnVPGNGBZSa1KWc7QgZF UufN0gUxZdVIRvgQGmYIVZ/AWd5pxhqF5ml8HhwcbNbx5Nl4yGYqCm03kacvd3x+/2JL lKkkLvH0TI5LBhuifc89iq85Fvf+eecwKDl27bOuklsFW1yaYL/8vQqaxYBRfZJqgBV9 ufJTqwCEsERNoRaHnemVzgQoOS/EIdS4eiON//m0ZvQXCzR2gEaiyBqK830qAWpQESHN sodQ==
X-Gm-Message-State: ALyK8tI/gnpRXuKtRnAwEyfb5rwVFQaGY9Hh2bDWWXPgYjsTgzVu5dFV6boitSaj8h6cK88LCITJr3loceGuCWvP
X-Received: by 10.37.228.198 with SMTP id b189mr7687049ybh.25.1464323169588; Thu, 26 May 2016 21:26:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Thu, 26 May 2016 21:25:49 -0700 (PDT)
In-Reply-To: <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 27 May 2016 13:25:49 +0900
Message-ID: <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114bc1c65c89d20533cb4e18
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3hB2NzU8P2dK8orf3hkBMOaQt-s>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Fri, 27 May 2016 04:26:12 -0000

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

On Fri, May 27, 2016 at 9:51 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> I'd be curious to know what those cases are, and how RFC7217s might reduce
> value.
>
Here's a case where RFC7217 reduces value: an enterprise network that keeps
track of machines by MAC address and  hostname generates AAAA records
automatically for the EUI-64 address.

RFC7217 breaks that because you'd have to either predict the address -
which relies on knowing the implementation and ensuring that every machine
boots with the same secret key - or scrape the address once the machine has
booted, which introduces a bootstrapping problem. DHCPv6 could fix this -
assuming the implementations don't default to LL+T DUIDs, which can't be
predicted - but it involves provisioning and running new servers that might
not exist. Dynamic DNS updates could also fix that, but it also requires
building infrastructure that might not exist.

Privacy concerns can be almost completely mitigated by making all machines
run 4941 by default. I say "almost" because I'm sure Fernando can come up
with a contrived situation where the address will leak, but the enterprise
might have thought of those scenarios and decided to mitigate those
situations. One way to mitigate the impact of some of those situations
would be to drop all packets to/from EUI-64 addresses outside the
enterprise network.

--001a114bc1c65c89d20533cb4e18
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 F=
ri, May 27, 2016 at 9:51 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=3D"ltr">I&#39;d b=
e curious to know what those cases are, and how RFC7217s might reduce value=
.<br></p></blockquote><div>Here&#39;s a case where RFC7217 reduces value: a=
n enterprise network that keeps track of machines by MAC address and =C2=A0=
hostname generates AAAA records automatically for the EUI-64 address.</div>=
<div><br></div><div>RFC7217 breaks that because you&#39;d have to either pr=
edict the address - which relies on knowing the implementation and ensuring=
 that every machine boots with the same secret key - or scrape the address =
once the machine has booted, which introduces a bootstrapping problem. DHCP=
v6 could fix this - assuming the implementations don&#39;t default to LL+T =
DUIDs, which can&#39;t be predicted - but it involves provisioning and runn=
ing new servers that might not exist. Dynamic DNS updates could also fix th=
at, but it also requires building infrastructure that might not exist.</div=
><div><br></div><div>Privacy concerns can be almost completely mitigated by=
 making all machines run 4941 by default. I say &quot;almost&quot; because =
I&#39;m sure Fernando can come up with a contrived situation where the addr=
ess will leak, but the enterprise might have thought of those scenarios and=
 decided to mitigate those situations. One way to mitigate the impact of so=
me of those situations would be to drop all packets to/from EUI-64 addresse=
s outside the enterprise network.</div></div></div></div>

--001a114bc1c65c89d20533cb4e18--


From nobody Thu May 26 23:04:51 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 58FC312D5E9 for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 23:04:48 -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 CnTYwn5WvyGE for <ipv6@ietfa.amsl.com>; Thu, 26 May 2016 23:04:46 -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 6961112D5C3 for <ipv6@ietf.org>; Thu, 26 May 2016 23:04:46 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 May 2016 06:04:45 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 1359B9CC51; Thu, 26 May 2016 23:04:44 -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=BK8nNJZwQDVKHmrKv2Z2yMgelZg=; b= Xi9YO94EDcYMsYqENeAerbRf91D1xDNfcSqEwazyObodkZiUphzEdUBQlvnpUk4M Nr44H+eFIKgjIQ7vaizBT7F97cjGKWjX5QvJ49YDRW2Hlih1wRr0NjySXaJRk34S sA6QpYP3y5tcU7NjcXhDau8Iu8sEeryHXv4lqLr91/0=
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=TbX0kCHgwMGGT/eN4mb5+M3HQ2 uSPpV4Zm+y4yXh83YUV7pSTArWi6KdUeAPaPou8fGANIaowm4YuwfrN4HarQTVXr uLoR5ca5PAD7/M23FkTilonDgwb2zfSjG0QQ/ToAKsLf0f+lqww49QUCl2gt/4xD IMc9NE+50XTH1CMGY=
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 6FD1B9CC4E; Thu, 26 May 2016 23:04:43 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 677E5172C971; Fri, 27 May 2016 08:04:37 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3C3FFBD4-EA7B-49EB-B03D-A7561556D816"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
Date: Fri, 27 May 2016 08:04:34 +0200
Message-Id: <CA490024-2D1E-4F6B-A225-DD8A319BC399@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/30NzuyTgf1RDKyFKGjnE2J2JxEY>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Fri, 27 May 2016 06:04:49 -0000

--Apple-Mail=_3C3FFBD4-EA7B-49EB-B03D-A7561556D816
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mark,

[...]

> > it's still convenient in certain cases, but not as the default for =
_all_ devices.
> >
>=20
> Why not?
>=20
> We should pick safe defaults. In terms of privacy, I think this is the =
safest default for stable addresses. I also think it satisfies stable =
address use cases that I can think of (mainly server and router =
interfaces).

agree.

> I think it is better to avoid options, however an option to switch =
them off or override them would not conflict with these being the =
out-of-the-box default.

agree.

> > > > We cannot all IPv6 implementations non-compliant by removing =
section 4 of RFC2464 as this document proposes.
> > > >
> > >
> > > I think "deprecated" would be a better term for them.
> >
> > I'm not even sure we should do that.
> > there are valid uses for the current scheme.
> > it's implemented, deployed, understood and well tested.
> > the company I work for have tens of IPv6 implementations and =
hundreds of different products with IPv6 stacks in them. it's unlikely =
I'm going to champion making a change from EUI-64 to 7217 in cases where =
it doesn't provide value.
> >
>=20
> I'd be curious to know what those cases are, and how RFC7217s might =
reduce value.
>=20
> One specific case related to what your company builds is the criticism =
that swapping a router interface module results in a different LL =
address. They address that issue by using either static LLs or globals =
(tying all of their internal next hop addresses to an external prefix, =
something I think should be avoided).

for the implementations I'm aware of a block of MAC addresses (say about =
a 1000) is tied to the node itself, interfaces are assigned MAC =
addresses out of the block, so at least in theory changing an interface =
doesn't necessarily lead to a change in MAC address.

> RFC7217s can automate LL address generation on routers that doesn't =
have this issue, as the Net_Iface parameter can be something that is =
stable across router interface swaps e.g. stable Ifindex or stable =
slot/module/interface location ID.
>=20
> Some people would still do static router interface addressing if =
RFC7217s were available, however it would now be more of a choice of =
wanting to rather than having to to achieve router interface address =
stability.
>=20
> > there are 2^64 ways to generate an IID, we can only provide general =
advice.
>=20
> I think we go a little further than that and always try to recommend =
good general defaults that are safe. In the past it has probably was =
just operationally safe.

I agree 7217 should be the default.
I would have been a lot more comfortable if we had had experience with =
it.
My point was that removing the 2464 section 4 is problematic for =
existing implementations.
EUI-64 should be an available option if anyone wants that, just not the =
default.
It is too early to deprecate.

> More recently we've been making security safe recommendations (e.g. =
security considerations section mandatory).
>=20
> Now I think we have to consider whether it is necessary to make a =
privacy safe default recommendation. I think in this case we do, because =
these addresses can be exposed to parties who might seek to violate =
privacy - even LLs on public access networks such as cafe Wifi networks.

on cafe WIFI networks you must have a random MAC as well.


> > for mobile devices it is clearly not a good idea to embed L2 =
addresses in L3 addresses.
> > but for those devices a lot of other things aren't good ideas =
either. if you really care about privacy I'm not quite sure if any of =
this would really help you, but oh well.
> >
>=20
> I think of it this way - it doesn't have to be perfect, just as long =
as it is usefully better.
>=20
> For stable address use cases, I think these addresses are better for =
privacy than embedded MAC address IIDs that don't change across networks =
or prefixes. They of course don't solve all privacy issues that can =
occur at the IPv6 and other layers of the stack.

I'm not sure I agree with that.
What's the main use case for stable addresses? Typically because there =
is a service on the host that needs to be registered in DNS. Then =
instead of monitoring the address just monitor changes in the DNS.

[...]

> > This is not an argument against 7217. I think the default should be =
to use 7217. If you want stable addresses. I don't want to make other =
schemes non-compliant. And I think we have to remember that these are =
just defaults. For SLAAC. People can and do configure IIDs any which way =
they like.
> >
> > My point given that there is a level of uncomfortableness with this =
document was to try to do the reverse. Can we find some updates to 2464 =
there is consensus on?
> >
>=20
> I suppose the trouble is that there are all the other Ipv6 over foo =
documents. Does updating RFC2464 make it an unexplained special case, or =
does it make all the other IPv6 over foo document ignored or forgotten =
cases?

Sorry I was unclear.
My suggestion was to do a bottoms-up approach by changing all the IPv6 =
over foo documents. Those are on the list to advance anyway. But instead =
of trying to do all of them at once, start with 2464.

Cheers,
Ole

--Apple-Mail=_3C3FFBD4-EA7B-49EB-B03D-A7561556D816
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

iQEcBAEBCgAGBQJXR+N1AAoJED4aXnjSQuKWUw0IAIvqUJ0jF6Wrq5bXeBuu6WfA
CqDsUoiGmizO9hTfAQzEXTtaXVjpVVo+Vl2zYFud7aUue6wDc47B3ca4+ZsG1xNa
I5ArR5WkWsCL0jz8to9qbzZ178BC8PqC+xfEpmLu/6NHWnubsO3SENJDDkqLNmc+
Xxhz3uIWrJ6UXAtcHti71XiT/x/2cKu/J5nXdL7a/WLr+BD6kxsiuvIAup+Djy5A
oBGZAqHCis0wNnwh32iVy2XmxILFUzn4v0UZ6wl0f2gp97jQ8EDY43ubhemHfK1Q
SUxIQnBlE0uYHepBKgHvX5kqyMO2VEXefxcuWeUXsv0mVAqEpMXLYnWQCVPaNcs=
=U3Fa
-----END PGP SIGNATURE-----

--Apple-Mail=_3C3FFBD4-EA7B-49EB-B03D-A7561556D816--


From nobody Fri May 27 08:16:05 2016
Return-Path: <dwcarder@wisc.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 E0BFF12D67A for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 08:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level: 
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, 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 kbA0mF68WP6y for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 08:16:02 -0700 (PDT)
Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 913D412D621 for <6man@ietf.org>; Fri, 27 May 2016 08:16:02 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII
Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0O7U00900CHLS200@smtpauth3.wiscmail.wisc.edu> for 6man@ietf.org; Fri, 27 May 2016 10:16:01 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-3, Version=6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.5.27.150917, SenderIP=0.0.0.0
Received: from DOIT-2NW1MRFY-X.doit.wisc.edu (brie.doit.wisc.edu [144.92.67.198]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPSA id <0O7U005XVD2MOQ00@smtpauth3.wiscmail.wisc.edu>; Fri, 27 May 2016 10:15:59 -0500 (CDT)
Date: Fri, 27 May 2016 10:16:00 -0500
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
Message-id: <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
In-reply-to: <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aYCsIA-vige7uYC3ZO7e4BH_wdk>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Fri, 27 May 2016 15:16:04 -0000

Thus spake Mark Smith (markzzzsmith@gmail.com) on Fri, May 27, 2016 at 01:00:27PM +1000:
> On 27 May 2016 at 12:17, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> > On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com>
> > wrote:
> >>
> >> So the problem is how to distinguish between attaching to a new link
> >> and re-attaching to the same link?
> >>
> >
> > A simple algorithm would seem to be:
> >
> >    1. If you don't support, or don't want to use, DNA, then every link is
> >    a new link and you start off with no IP addresses. So you form a link-local
> >    address, send an RS, etc. etc. starting from scratch.
> >
> >
> That is significantly reducing the robustness of e.g. TCP connections, as
> they won't survive that event because their address will change.
> 
> Hosts are supposed to be tolerant of transient network events. In my
> experience, that has included disconnection and reconnection of the host's
> interface to the same link, which has included moving the host's patch
> cable from one switch to another attached to the same LAN. I didn't rush
> the patch cable move because at the time I didn't have any expectations
> that my existing telnet sessions would survive.
> 
> 
> >    1. If you support and want to use DNA, then you use DNA with the same
> >    MAC address as you had before.
> >
> >
> The issue with DNA is that it seems to be relying on the MAC address and
> therefore the Link-Local address of the on-link routers being stable for as
> the link remains operating. If routers were changing their MAC addresses
> periodically too, then DNA will fail. It seems you've been arguing for no
> stable L2 and/or L3 addresses on any device, so that would have to mean
> that routers don't have them either.

I can't imagine that routers would be periodically randomizing their MAC 
addresses in any practical deployment.  Though, I do have a few routers that 
changed mac addresses exactly once, when I turned off DECnet. :-)  Even
that one change was quite problematic due to high timeouts on some host 
stacks.

Dale


From nobody Fri May 27 09:09:21 2016
Return-Path: <joelja@bogus.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 DB6A712D6C2 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 09:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 Hvofl3lW004C for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 09:09:18 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 2361D12D0CD for <6man@ietf.org>; Fri, 27 May 2016 09:09:18 -0700 (PDT)
Received: from mb-2.local (host210-131-static.6-79-b.business.telecomitalia.it [79.6.131.210]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4RG9ASR065040 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 27 May 2016 16:09:13 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host host210-131-static.6-79-b.business.telecomitalia.it [79.6.131.210] claimed to be mb-2.local
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: "Dale W. Carder" <dwcarder@wisc.edu>, Mark Smith <markzzzsmith@gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <20bfbadb-2145-c266-43be-346755c92c81@bogus.com>
Date: Fri, 27 May 2016 18:09:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2
MIME-Version: 1.0
In-Reply-To: <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LG4U7qUFdhENXgLKvaiAhc1q4EEw7ldao"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/B_bZNG8QcytrecM9WQJxnkwTnY8>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Fri, 27 May 2016 16:09:20 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--LG4U7qUFdhENXgLKvaiAhc1q4EEw7ldao
Content-Type: multipart/mixed; boundary="8WehPTjGqhKPjtt7J8USEt5BeAG9XqpkH"
From: joel jaeggli <joelja@bogus.com>
To: "Dale W. Carder" <dwcarder@wisc.edu>, Mark Smith <markzzzsmith@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>,
 =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Message-ID: <20bfbadb-2145-c266-43be-346755c92c81@bogus.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for
 draft-gont-6man-non-stable-iids-00.txt)
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com>
 <57431E27.8090209@si6networks.com>
 <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com>
 <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com>
 <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com>
 <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com>
 <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com>
 <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com>
 <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu>
In-Reply-To: <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu>

--8WehPTjGqhKPjtt7J8USEt5BeAG9XqpkH
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/27/16 5:16 PM, Dale W. Carder wrote:
> Thus spake Mark Smith (markzzzsmith@gmail.com) on Fri, May 27, 2016 at =
01:00:27PM +1000:
>> On 27 May 2016 at 12:17, Lorenzo Colitti <lorenzo@google.com> wrote:
>>
>>> On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com>
>>> wrote:
>>>>
>>>> So the problem is how to distinguish between attaching to a new link=

>>>> and re-attaching to the same link?
>>>>
>>>
>>> A simple algorithm would seem to be:
>>>
>>>    1. If you don't support, or don't want to use, DNA, then every lin=
k is
>>>    a new link and you start off with no IP addresses. So you form a l=
ink-local
>>>    address, send an RS, etc. etc. starting from scratch.
>>>
>>>
>> That is significantly reducing the robustness of e.g. TCP connections,=
 as
>> they won't survive that event because their address will change.
>>
>> Hosts are supposed to be tolerant of transient network events. In my
>> experience, that has included disconnection and reconnection of the ho=
st's
>> interface to the same link, which has included moving the host's patch=

>> cable from one switch to another attached to the same LAN. I didn't ru=
sh
>> the patch cable move because at the time I didn't have any expectation=
s
>> that my existing telnet sessions would survive.
>>
>>
>>>    1. If you support and want to use DNA, then you use DNA with the s=
ame
>>>    MAC address as you had before.
>>>
>>>
>> The issue with DNA is that it seems to be relying on the MAC address a=
nd
>> therefore the Link-Local address of the on-link routers being stable f=
or as
>> the link remains operating. If routers were changing their MAC address=
es
>> periodically too, then DNA will fail. It seems you've been arguing for=
 no
>> stable L2 and/or L3 addresses on any device, so that would have to mea=
n
>> that routers don't have them either.
>=20
> I can't imagine that routers would be periodically randomizing their MA=
C=20
> addresses in any practical deployment.  Though, I do have a few routers=
 that=20
> changed mac addresses exactly once, when I turned off DECnet. :-)  Even=

> that one change was quite problematic due to high timeouts on some host=
=20
> stacks.

Randomizing interfaces macs would really be a pain in the ass when
dealing with Link aggregation group members. swapping linecards or
routers is bad enough, but people actually do use these link-layer clues
as part of port inventry /port security / configuration systems and so on=
=2E..

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



--8WehPTjGqhKPjtt7J8USEt5BeAG9XqpkH--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAldIcSEACgkQ8AA1q7Z/VrJIfgCeK1cR2jVlKaxIBYSi50mO+qwV
NPIAn2KItJHnXvX1acvQPYZuNz5bk90h
=OX5c
-----END PGP SIGNATURE-----

--LG4U7qUFdhENXgLKvaiAhc1q4EEw7ldao--


From nobody Fri May 27 10:37:20 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 8C2DB12DB22 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 10:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.701
X-Spam-Level: 
X-Spam-Status: No, score=-1.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 T6AeM56Ovi30 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 10:37:17 -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 2602512DB7E for <6man@ietf.org>; Fri, 27 May 2016 10:36:36 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id l63so776547ita.1 for <6man@ietf.org>; Fri, 27 May 2016 10:36:36 -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:date:message-id:subject :from:to:cc; bh=IdrvqiEX2cChMsJl+9R3q0ufVmWtuc9mR8at39lSPko=; b=JoctwAJGLkMWaMFgKEYnggiQqlL/NonHItl115K6+KpyHutb+do3DC/X83+kgwFwyD vafjfyj1zaLhlKQOxRGjo/+/cDBVJvlEybq3do+i+Q92+i21CVxaOWcaU0R/CNVuyYnq HhaHI6/PM/K4MSVJAizIMMcB74AJnCas4dyJ41RW6lktqHPEtGNq+hmVbFcBrCgGVRAg FwY7eWigsPDuNF8LAdRT+v5QQFJrTtf09IqKLl0xDnbwEFEsnvaS+1BcJ5tL2uipFmCM p9keosalMONcW9H8y9qAkp9YiiHG+2+tCBZ0BlecObCiSnYkwd4POxQKWLNI4mrBJWvh AdiQ==
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:date :message-id:subject:from:to:cc; bh=IdrvqiEX2cChMsJl+9R3q0ufVmWtuc9mR8at39lSPko=; b=Dz2Zz9ZtWy/YCNZKiySXD5F7f133Ux2OXrxymmU0jKh7/Cn4J9U+16z7Ukg/wSuUiG EnjN7yLMQ3OMy65wPc7rj6GjU90Ds9OdULIizkFDp4+Xk8FNgs+RK5yulrMYa241Bwhf SDh+RybchcGF5pEO9hb4XVkmNafQpQlxsp1BI1bf0DrFH/leelPBPtrU8UH8AsWQDNq3 YPaqQRTOU16tfULWqyA6B4SoGNmAfIEvpymoq1dua7CqPEm5IVwN+aLxGmzQx01sK9PU jz/uivuXkJqD/iuKeL+nHOWjbKV68kIo/iucCFzKo1VWeh0dEFMW2lc2K2m4nghLVr0B v2gQ==
X-Gm-Message-State: ALyK8tKWQssmenJVI9Q+3zne/6I+EykcdGl30RGjf20x50rZZDvjUWTKt5mmj2zRDrqDRkVzz2OtoUj9j8hd7A==
MIME-Version: 1.0
X-Received: by 10.36.13.76 with SMTP id 73mr8865824itx.79.1464370595409; Fri, 27 May 2016 10:36:35 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.159.148 with HTTP; Fri, 27 May 2016 10:36:35 -0700 (PDT)
In-Reply-To: <574788B2.6070404@si6networks.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <57438806.9010902@si6networks.com> <CAJE_bqe=W88raTaZq9N6wC8rXpiNQ5Mi1H8cQ9eRvX3xiRw3Lw@mail.gmail.com> <574788B2.6070404@si6networks.com>
Date: Fri, 27 May 2016 10:36:35 -0700
X-Google-Sender-Auth: ut2RlkJGHl2_j-R5nxn4zv4YuXY
Message-ID: <CAJE_bqfmM7xk1DXmfZzhaCau+_qyBzuPfvLmDUs=ajZCQjiheQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AmOMA21gzvjmvWnRJzGR-f-_4yY>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@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: Fri, 27 May 2016 17:37:18 -0000

At Thu, 26 May 2016 19:37:22 -0400,
Fernando Gont <fgont@si6networks.com> wrote:

> > As I already explained in the cited text, my suggestion was to attempt
> > of making this document less controversial and, really, only focus on
> > "cases where implementations otherwise would have configured a stable
> > IPv6 IID containing a link layer address", explicitly stating other
> > cases are out of scope.  Since randomized link-layer addresses
> > wouldn't be considered stable, they should be obviously out of scope
> > of the document, hence my suggestion.
>
> Ok. Now I see where you were coming from. If anything, maybe we could
> tweak your text and say that randomized MAC addresses would lead to
> non-stable addresses, and hence their use is considered out of the scope
> for this document? (I guess I could live with that)

That works for me.

> We certainly want to focus on stable addresses here, so yes I agree with
> you. Please see my comment above -- I think we're starting to converge...
>
> Thoughts?

Yes, this (and updating other part of the doc along with this sense)
will address my point perfectly: the resulting text would be much
clearer on the scope and more obviously consistent with what the
authors said about the scope.

> > Not really, partly because that's not my point in my response to the
> > WGLC.  I can answer that if you want to know what I think about it,
> > but I'll defer it to some different opportunity so we won't be
> > distracted about my main point.
>
> You seem to be arguing against we saying that nodes must not embed
> link-layer addresses in the IID (or at least asking us to explain
> ourselves).

Not necessarily, but I guess we are now on the same page, so I won't
explain more on this.

> Would it help if we, say, explicitly include Brian's example of
> multiple-layer-3 protocols and also note that if MAC addreses are
> embedded, then addresses for multiple prefixes would employ the same
> IID, and that that allows for traffic correlation?

Same here, but: this, and stating more clearly that this is not only
about stable addresses but rather mainly about embedding link-layer
addresses (stable or not), then this will be another way to address my
point.  But I thought this will be much more controversial and require
another round of WG discussions.  So, assuming the authors' intent was
really about stable cases, I suggested the less controversial
approach.

--
JINMEI, Tatuya


From nobody Fri May 27 14:10:33 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 15FCC12D816 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 14:10:33 -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 tUrhAD-zBAHr for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 14:10:31 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 4A2FA12D10E for <ipv6@ietf.org>; Fri, 27 May 2016 14:10:31 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id g64so45268652pfb.2 for <ipv6@ietf.org>; Fri, 27 May 2016 14:10:31 -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=fFA8QLv7YcKqImnuAZum+xYiHqHrXum5cP9DlkOsXAY=; b=qxjco9liRbebN75Ra9i0ty1NlU4/T7QpzXirMmYz2d4nd6/N67Gdt+V4nn8MohCEZq I83NJZ+H88mBpCxWr4BujAdHE6qNFaXGbfnPAdJnfEX3SjRgSZ4xnW6eBvRUtM5KdJTd 4AzSG+2NHXMGQHhpHJtlGm6nhUgDbGgc+11bdrlaDNRJU7IwRki+jGueDDG7v+uMCBET WNNY+l7UrBpN9RKq1ea4wA1oD9X0YnHStkcOLGSnYU8BJ3AbNsxxbFeujebc+Vc6k/9X EepAqJU5EuFb2gLdunHSS3t+cjzJWT12NRcMibXFOBH2sgDHp/awTa4thgiw5H8oB0FY p3ag==
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=fFA8QLv7YcKqImnuAZum+xYiHqHrXum5cP9DlkOsXAY=; b=SsF+7tuTEbNRD3+rojXaNioBqvQ7sogXIZVLlp+EAxKWXGSRsDKOSrbPTb8eoL9BCU UoGwaGH1xsA2eVQD2jdGi4JdrObP7LInOq/zI0naP7mfMhCed02G1VOjSkdHKIk3HHwO IZBH8EUxUwPhzfimi8qxs2c5gOL2NO5yCWGt145b/XsICEqLXj8IJDdwiE4kzTv82b43 CJtXKmCG5auV0A7n7JNwWiCfPqwPEJV08/NqoXcLWBJgRTkumUV05pPyhguRteACrc0z qdqfKGfllPhBhSjhziksrp1WxwD5qK9agF34MY32zD42vpGvVfrUduw8LonCk9/au57T 91tA==
X-Gm-Message-State: ALyK8tKX4feVMqsmWMLSkVObAknPzSv2cqRH/MksvPDw06eFcOe4Cmw43rM48YxtG7hVIA==
X-Received: by 10.98.47.4 with SMTP id v4mr2268155pfv.68.1464383430753; Fri, 27 May 2016 14:10:30 -0700 (PDT)
Received: from ?IPv6:2406:e007:457a:1:e0ca:c02d:4b9c:8ea7? ([2406:e007:457a:1:e0ca:c02d:4b9c:8ea7]) by smtp.gmail.com with ESMTPSA id h6sm30300918paf.23.2016.05.27.14.10.26 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2016 14:10:29 -0700 (PDT)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Lorenzo Colitti <lorenzo@google.com>, Mark Smith <markzzzsmith@gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com>
Date: Sat, 28 May 2016 09:10:38 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vKcbYFj-9ZqPAnFJyvSPAo-fuSc>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Fri, 27 May 2016 21:10:33 -0000

On 27/05/2016 16:25, Lorenzo Colitti wrote:
> On Fri, May 27, 2016 at 9:51 AM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
>> I'd be curious to know what those cases are, and how RFC7217s might reduce
>> value.
>>
> Here's a case where RFC7217 reduces value: an enterprise network that keeps
> track of machines by MAC address

Yes,standard practice on many sites (that will, I expect, forbid MAC address
randomization).

> and  hostname generates AAAA records
> automatically for the EUI-64 address.

Why? Clients don't need AAAA records. Servers have stable addresses anyway,
usually with a small-integer IID.

    Brian

> 
> RFC7217 breaks that because you'd have to either predict the address -
> which relies on knowing the implementation and ensuring that every machine
> boots with the same secret key - or scrape the address once the machine has
> booted, which introduces a bootstrapping problem. DHCPv6 could fix this -
> assuming the implementations don't default to LL+T DUIDs, which can't be
> predicted - but it involves provisioning and running new servers that might
> not exist. Dynamic DNS updates could also fix that, but it also requires
> building infrastructure that might not exist.
> 
> Privacy concerns can be almost completely mitigated by making all machines
> run 4941 by default. I say "almost" because I'm sure Fernando can come up
> with a contrived situation where the address will leak, but the enterprise
> might have thought of those scenarios and decided to mitigate those
> situations. One way to mitigate the impact of some of those situations
> would be to drop all packets to/from EUI-64 addresses outside the
> enterprise network.
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Fri May 27 19:15:45 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 4184C12B050 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 19:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 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.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 ddoOzvnrSqrd for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 19:15:41 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 C3D7912B008 for <6man@ietf.org>; Fri, 27 May 2016 19:15:40 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id r140so164929260vkf.0 for <6man@ietf.org>; Fri, 27 May 2016 19:15:40 -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=TBpukiK6LBhth9Kfb4YwSvgaDkhMSjIHXpBLFFI/ctg=; b=U4guNhLdZ0rF4MLHV4hIrqnGttLDeM4m3jfnIjw2mFILfmJSodeAZZVr9ugsICqElL 1rQA7SWDHa3bNmmzIJFQpcvzL9Hx5O7u2GgT4zh6zcCfsnwue2OKplXRsYqfCsEuPf6m knKos5oFTJnAb/Oep+71SCDTmG2mpH68n8HxSha3odbWs7EadchtJIOenLKjIRLxbal7 vmZhTMNYnynm/r6Ej2CL1Xfyk897sLEMPcYwplrZFRQhoXt+Tyad1YnYte/1xCrIW3QY klsGBnpIGi5P8m0VraZgcl4vfFete6z6BVOySdiY04FUT5TXBe0S5qMmU7/AzrelImFt A18w==
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=TBpukiK6LBhth9Kfb4YwSvgaDkhMSjIHXpBLFFI/ctg=; b=bjVyFMaMg4s6CjuU5jTfOVEnQsStYPf/7z/j0qRikBkoVBye0RTT0dAFcgDV75eyhI cQV/49TlX5BItm0u9+LcSdeBbHxrDw1/gG0SPKQLECdY7xgPSYomwwH8+zuOO6ouSQbt PFVyd2e2xhVAABlGFrPsRAjVHXWb3jDByYyR0QiQOv3cg4/gLjwUSS5MQhfW+0FljUrY vgSBV8AFCMn2CreFX8LopXaSmk63TD23B9ojw9gbc16Om2O9sN8XEc9xWonv/r7heAGv REYcjnsHFA8ViTcBX5peiE9B+mgfWn62fJo6+QKMloQEkxrcbrVUmx6kM+HUwyls3O51 C8gw==
X-Gm-Message-State: ALyK8tKYdrXHX5zixNI6gy1aZh+Q523C0BBcT4AlBKV32y0ZSUsruxFz9/yG0K4nBf0kJq9CQhkJTP0Z+TXy+g==
X-Received: by 10.159.32.131 with SMTP id 3mr10386170uaa.75.1464401739735; Fri, 27 May 2016 19:15:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.3.168 with HTTP; Fri, 27 May 2016 19:15:10 -0700 (PDT)
In-Reply-To: <20bfbadb-2145-c266-43be-346755c92c81@bogus.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu> <20bfbadb-2145-c266-43be-346755c92c81@bogus.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 28 May 2016 12:15:10 +1000
Message-ID: <CAO42Z2yVqWk7QohetKzisk7ZcrygOjCDfVRTf4Qbqo-884xoiQ@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_g2CuWr1lrwLohhLIdbiku1WMS0>
Cc: "6man@ietf.org" <6man@ietf.org>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, 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: Sat, 28 May 2016 02:15:43 -0000

On 28 May 2016 at 02:09, joel jaeggli <joelja@bogus.com> wrote:
> On 5/27/16 5:16 PM, Dale W. Carder wrote:
>> Thus spake Mark Smith (markzzzsmith@gmail.com) on Fri, May 27, 2016 at 01:00:27PM +1000:
>>> On 27 May 2016 at 12:17, Lorenzo Colitti <lorenzo@google.com> wrote:
>>>
>>>> On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com>
>>>> wrote:
>>>>>
>>>>> So the problem is how to distinguish between attaching to a new link
>>>>> and re-attaching to the same link?
>>>>>
>>>>
>>>> A simple algorithm would seem to be:
>>>>
>>>>    1. If you don't support, or don't want to use, DNA, then every link is
>>>>    a new link and you start off with no IP addresses. So you form a link-local
>>>>    address, send an RS, etc. etc. starting from scratch.
>>>>
>>>>
>>> That is significantly reducing the robustness of e.g. TCP connections, as
>>> they won't survive that event because their address will change.
>>>
>>> Hosts are supposed to be tolerant of transient network events. In my
>>> experience, that has included disconnection and reconnection of the host's
>>> interface to the same link, which has included moving the host's patch
>>> cable from one switch to another attached to the same LAN. I didn't rush
>>> the patch cable move because at the time I didn't have any expectations
>>> that my existing telnet sessions would survive.
>>>
>>>
>>>>    1. If you support and want to use DNA, then you use DNA with the same
>>>>    MAC address as you had before.
>>>>
>>>>
>>> The issue with DNA is that it seems to be relying on the MAC address and
>>> therefore the Link-Local address of the on-link routers being stable for as
>>> the link remains operating. If routers were changing their MAC addresses
>>> periodically too, then DNA will fail. It seems you've been arguing for no
>>> stable L2 and/or L3 addresses on any device, so that would have to mean
>>> that routers don't have them either.
>>
>> I can't imagine that routers would be periodically randomizing their MAC
>> addresses in any practical deployment.  Though, I do have a few routers that
>> changed mac addresses exactly once, when I turned off DECnet. :-)  Even
>> that one change was quite problematic due to high timeouts on some host
>> stacks.
>
> Randomizing interfaces macs would really be a pain in the ass when
> dealing with Link aggregation group members. swapping linecards or
> routers is bad enough, but people actually do use these link-layer clues
> as part of port inventry /port security / configuration systems and so on...
>

Router interfaces is the situation where I would leave the MAC address
as burnt in by the factory to assist with troubleshooting etc., and
then have RFC7217 generate stable per-prefix IIDs, including for the
router's interface LLs, using slot/module/interface number or
slot/module/interface stable ifIndex as the Net_Interface parameter.

In that situation, I think the physical security protecting link
access, or the limited geographical scope of Wifi would provide enough
privacy for the factory MAC addresses, and as they're not being used
directly in the layer 3 IIDs, knowing them wouldn't allow somebody to
then target the router over the Internet at layer 3 (assuming it is
reachable over the Internet).

It might be more useful to randomise residential router MAC addresses
periodically e.g. on boot, although that looks like it would break
DNA. if DNA was changed to only use the router's LL address as the
router ID, on the assumption that it was stable, and RFC7217 was used
to generate stable LLs independent of the MAC address, then
randomising the router's MAC address on boot or gracefully some other
time (e.g., announced via unsolicited NAs) should be possible without
impacting operation.

Regards,
Mark.


From nobody Fri May 27 21:03:26 2016
Return-Path: <dale.carder@wisc.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 5CAD812D154 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 21:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level: 
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, 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 gXQulFm2XTEb for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 21:03:23 -0700 (PDT)
Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3713B12D144 for <6man@ietf.org>; Fri, 27 May 2016 21:03:23 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII
Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0O7V00G00BWW8X00@smtpauth2.wiscmail.wisc.edu> for 6man@ietf.org; Fri, 27 May 2016 23:03:22 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-2, Version=6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.5.28.35716, SenderIP=0.0.0.0
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0185.outbound.protection.outlook.com [207.46.163.185]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPS id <0O7V0069ICLLOM30@smtpauth2.wiscmail.wisc.edu>; Fri, 27 May 2016 23:03:21 -0500 (CDT)
Authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=wisc.edu;
Received: from havarti.local (24.240.33.157) by SN1PR06MB2127.namprd06.prod.outlook.com (10.169.125.151) with Microsoft SMTP Server (TLS) id 15.1.497.12; Sat, 28 May 2016 04:03:20 +0000
Date: Fri, 27 May 2016 23:03:13 -0500
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
Message-id: <20160528040313.GA80036@havarti.local>
References: <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <20160527151600.GB18905@DOIT-2NW1MRFY-X.doit.wisc.edu> <20bfbadb-2145-c266-43be-346755c92c81@bogus.com> <CAO42Z2yVqWk7QohetKzisk7ZcrygOjCDfVRTf4Qbqo-884xoiQ@mail.gmail.com>
In-reply-to: <CAO42Z2yVqWk7QohetKzisk7ZcrygOjCDfVRTf4Qbqo-884xoiQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Originating-IP: [24.240.33.157]
X-ClientProxiedBy: BLUPR17CA0043.namprd17.prod.outlook.com (10.162.85.139) To SN1PR06MB2127.namprd06.prod.outlook.com (10.169.125.151)
X-MS-Office365-Filtering-Correlation-Id: bb885ff2-2416-466f-3d04-08d386ad01b3
X-Microsoft-Exchange-Diagnostics: 1; SN1PR06MB2127; 2:bSG894plq9w7aLTKQ9fukXgvK7HLHEk3505p88Dy9d6WZxp0nMDEQL3NvDBzTjuUu0abeteWDfKVJhEhsqMgeOD1lURI8ZF0aQf1Q1TAvkzjaHRYzgayGGqaKbOShmUIzROQbMEExGWO0A7hHcLQzK5SNchbYW0EXP9jVNe6NNIbNrQkgAcDUpggvnUV79lb; 3:20bqw4Km8rslMD0ZVPo5f54oXgBhACYyElShd5niddtqwjkppPCr8EeOKi8oQkuKwK2QG1V1jEFBfnoe6NFS4s3xfLFVmHjVUTWDg9cwr6PlJSaWSgJZbRkjkYdSFHM8; 25:SRrOwdgRqGhbQUMlUfBv7m2vP7/PILBXYkPLz/F612AQoCEdVYeXma+HwspTANiZlKliC6yO5SFRenJyy9DYK4QNbYj301zAAurCMh09MdBPlFhCpsYF8P+DwCKvYNzINCctraHTtUHcGN3xIn1tdSqLFu87EACxWDuqPBM87F9x68ai2yW87YIn1tRqyiKiGxO4YH4wQG0LObAoSIr4DjIrMa4UuDBfLQoKhnuRGcln0+dNfSWM7pG1ldSO3YagwOkK62RpGrBsuzfphW24FFjamI3ad01CFuGcjF9sgXshLSjUYuiNSwH1/URRAR1ud9NHrWUMFy7HaiGOR1dxX648tz7x4ud2iDjcu6oGqV4S/c0GI+7ayQVQwgUZolZ4m1RxSrAVBvtaiJAzmroo92nSclPC5Wa7dKh/0I9bWkw=
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR06MB2127;
X-Microsoft-Exchange-Diagnostics: 1; SN1PR06MB2127; 20:uRz/0Ovk41K4m79Xfpt0l/YqRMg8BT1krkJVpymLxAXI3Ymd42uPvXdVQbsuvaIKLLAIierQmPPEPkvQK1f8MRJV5Vf6XVHk40u2yGqdNYknqs2NU7+OoTTLnGjd7dIA/TeMWWjS0LJlgQzCLa05kvvPpU19qAJ+Jg+e4hQ0HNpmzlKURsI9gvAwMUMUQK8kquyLEvBAdYtIg0estzBwcMk2dRVCIvhHdnxcdIdp6ZwsljMu8WvIWiihpJ045GABYv1H/qtmqEOzqtTNLvc8Vx3oQT4dkVRVqC+q7lsjsUaP/cDNNLChxTQdcb1h1IhZR9JWGSGWkfwbNr71NnX7kASuBodb4dqxCdoPITyj1Bc=; 4:DPvLCYsnL7A88VVlItGGn+MOdrkCRlYCew5bk8G5lb+lnqV0qiSxdulXpxM/fPk0JIGLsDz6gL3/3giFMRibpdN96BN/YaGb+Fl3PLc5tN++quCwMVBiDIghXRF5Uh/YfaNTrp+X2D7KfJbZXe0Cv0o1rhm0VvS9eROJio+EECI+OFashiMBif23KkSAtLMcguxmZoKubnhq85taHQSZZoFYuUvELKxBEUa0ijx1k4mwu8ss73Zu30hNSPgOLVnUjxozgyUtAS4szjcnIXny8wJeVSreWx7sWQzTqOFcvr9TsEBRwDC6CamxVR97dDF4Gq4QjiKtNb6saboS+JPBVvUlay4etzFVcrVUWY+AYxacfOJtEuZwDgpcWUikhzQBZqNlPnf0AHkD/MRO2CVYvJ8pjOz8iuxW67fYVQweLAq/Su0hMF3ClLakQvIwB9mnEKc0Hg2Ai9GMLdb1mJ1gSA==
X-Microsoft-Antispam-PRVS: <SN1PR06MB2127C4CB10C51F0D49D8DC448F430@SN1PR06MB2127.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705)(211936372134217);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026);  SRVR:SN1PR06MB2127; BCL:0; PCL:0; RULEID:; SRVR:SN1PR06MB2127; 
X-Forefront-PRVS: 09565527D6
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(4630300001)(6009001)(24454002)(377454003)(2473001)(19580395003)(50466002)(4001350100001)(75432002)(98436002)(19580405001)(97756001)(4326007)(83506001)(42186005)(586003)(33656002)(3846002)(23726003)(5008740100001)(1076002)(6116002)(77096005)(46406003)(2906002)(5890100001)(8676002)(93886004)(90282001)(230783001)(81166006)(47776003)(92566002)(110136002)(2950100001)(89122001)(88552002)(66066001)(189998001)(15650500001)(5004730100002)(9686002)(76176999)(50986999)(54356999); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR06MB2127; H:havarti.local; FPR:; SPF:None;  MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR06MB2127; 23:xfUNfu69kSKwhrqXsoV1X9IbCWJJIxb5kpzjhVvwI?= =?us-ascii?Q?pl2IReFji9kOztheuXXfIIMQqQdnAXWxpTw94y3RztNpe2cennDSOL7RhgMF?= =?us-ascii?Q?AJ/1A6dcXpj1mNK5Uco1ssgSxTWN18HcUa2QMQyIFEHQharebfw729FC3HAv?= =?us-ascii?Q?CxJw5vaQduDE1/zgdwHYf9oeBn78kMJ89jh2mLKiepNAqwqln9II7cclfR/Z?= =?us-ascii?Q?bUNhCfjPYeSKSX2WTMzzE/j6SEFjS2e5OeuqZ86BdCH5mdSCZXlewCYRS2Rg?= =?us-ascii?Q?V6lQTXFGAL2NeiuYOCwpyKmRKF//vgwxCepv1/Ds1NDPPO/43cYIHNfFI1Jb?= =?us-ascii?Q?HZcNz6EcINhgCmK5qlteli2ofcPO+4jtc86zDW11q/DI43kavy9SziaJtM7m?= =?us-ascii?Q?5KJjX5Szl59EBDTNAo4Q6Bzck/jY0ZdBfIClVwmZeC7bqVg8CQ1Ws1kb+Op7?= =?us-ascii?Q?j0Ait7bG9qXek/CSkvh1r6e/u3kdVh6GIJ5kPjhJmm/fd+9Ru4tNLpUbnxo+?= =?us-ascii?Q?c7SAlfi/NfmBTJfuTlGlGRb3IRr1/L+yxcEWhplB5Jl+7iGgpu0H+q0HjiNs?= =?us-ascii?Q?AtImyp7u1nQ2sPM8pua4t4zBiFM0qr1YW/jyQV0HCDTzZAer4eJdKr/sltNm?= =?us-ascii?Q?P1XAfQa+74upnOTC1tuPNK3loEIWfJnPIYiud2vqpsa4K7UlfW2cSHEZpWk9?= =?us-ascii?Q?le/QGsVpyDXu4YDJBJJaIHcBdeKtHRH5AkOttUnqnaY1YMxFTpbjIw5AnekK?= =?us-ascii?Q?j2/0APpafAu9BDOOrqNV577AEhGpwNHOei0VYdOxKTHwkImDcIf/w0le87qv?= =?us-ascii?Q?9EpBnoBLMdbPLiA1BRDolS9AuEDtzodlpASldo9tg4O8ooEneENOPBF/lxEM?= =?us-ascii?Q?nwYmxNK1N/PS6VwOxQ7mPv+CnL5M4HFPNvid//Fq4rdxPaXEFwuQRedy4y9u?= =?us-ascii?Q?KI7wmsTIw59T6dp5WAB0H+KA6QqyDjz109IE2X+RhfjB1NDM6oLZAEKhS57d?= =?us-ascii?Q?OPPHDegEXKK1WbFKtfKPqNlhTMZ3bA+NcJDiP/X6l/lv+rflct0cmoV39dfA?= =?us-ascii?Q?nXGgdt5WU8dn+/Sf732xdUP1RJj+oDPZiqoXhuy88Be+vdHn0MbHfc5QVX8W?= =?us-ascii?Q?ma/wxXpL93rKoqylag3WpgyvJ9TrT4sKYaA8LtU48qqTZ8Vplkghcia1iDku?= =?us-ascii?Q?roS3SSwcUY8XfY=3D?=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR06MB2127; 5:GMQKTunB15ufU9G+gEVcL4ydw5vfStBc6h08EcU5Km8l0MjU1Oan3eVDaQ0KHH1IzGr51riGhoLmd4TBrmJRXKSHnlyaUlLy4Wy4UlmX2VOu0ZruUvhIFV8yUqDk7W6cBqasPYEDNCp+WLGYi9ZgBg==; 24:eu2j9OrQqlgfTsN++DeVCKdoket8WaTW/Mh27xHirFLEOfU4JDi4BtYTQRNXNkhUMXlaPJRUG2FN68KjdVT1gkGE3VmkQ1ndjeBNeOKO+DQ=; 7:SHjLvw4I5HRtPuywpKqNLtkMrC+Qsgm42mLMEy7WtfoE0/4LUscTHZ/xD3XTUvcCFXK3Zx/EPa6k5Gv+uFIbQiR/qM8FbcXSkWHFZtvp+EBP3HlMkYCPPqTRqua90wIP/ma8D9Z9DvfWRmVx4tqkx3+AU+PuBOX3PZdfpLwcWxfbajY+vKpBYiywYWNIEZGt
SpamDiagnosticOutput: 1:23
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: wisc.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 May 2016 04:03:20.0047 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR06MB2127
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tvxXlyF8aAIP1A8c9ZEcSRX76bs>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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, 28 May 2016 04:03:25 -0000

Thus spake Mark Smith (markzzzsmith@gmail.com) on Sat, May 28, 2016 at 12:15:10PM +1000:
> On 28 May 2016 at 02:09, joel jaeggli <joelja@bogus.com> wrote:
> > On 5/27/16 5:16 PM, Dale W. Carder wrote:
> >> Thus spake Mark Smith (markzzzsmith@gmail.com) on Fri, May 27, 2016 at 01:00:27PM +1000:
> >>> On 27 May 2016 at 12:17, Lorenzo Colitti <lorenzo@google.com> wrote:
> >>>
> >>>> On Thu, May 26, 2016 at 3:15 PM, Mark Smith <markzzzsmith@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> So the problem is how to distinguish between attaching to a new link
> >>>>> and re-attaching to the same link?
> >>>>>
> >>>>
> >>>> A simple algorithm would seem to be:
> >>>>
> >>>>    1. If you don't support, or don't want to use, DNA, then every link is
> >>>>    a new link and you start off with no IP addresses. So you form a link-local
> >>>>    address, send an RS, etc. etc. starting from scratch.
> >>>>
> >>>>
> >>> That is significantly reducing the robustness of e.g. TCP connections, as
> >>> they won't survive that event because their address will change.
> >>>
> >>> Hosts are supposed to be tolerant of transient network events. In my
> >>> experience, that has included disconnection and reconnection of the host's
> >>> interface to the same link, which has included moving the host's patch
> >>> cable from one switch to another attached to the same LAN. I didn't rush
> >>> the patch cable move because at the time I didn't have any expectations
> >>> that my existing telnet sessions would survive.
> >>>
> >>>
> >>>>    1. If you support and want to use DNA, then you use DNA with the same
> >>>>    MAC address as you had before.
> >>>>
> >>>>
> >>> The issue with DNA is that it seems to be relying on the MAC address and
> >>> therefore the Link-Local address of the on-link routers being stable for as
> >>> the link remains operating. If routers were changing their MAC addresses
> >>> periodically too, then DNA will fail. It seems you've been arguing for no
> >>> stable L2 and/or L3 addresses on any device, so that would have to mean
> >>> that routers don't have them either.
> >>
> >> I can't imagine that routers would be periodically randomizing their MAC
> >> addresses in any practical deployment.  Though, I do have a few routers that
> >> changed mac addresses exactly once, when I turned off DECnet. :-)  Even
> >> that one change was quite problematic due to high timeouts on some host
> >> stacks.
> >
> > Randomizing interfaces macs would really be a pain in the ass when
> > dealing with Link aggregation group members. swapping linecards or
> > routers is bad enough, but people actually do use these link-layer clues
> > as part of port inventry /port security / configuration systems and so on...
> >
> 
> Router interfaces is the situation where I would leave the MAC address
> as burnt in by the factory to assist with troubleshooting etc., and
> then have RFC7217 generate stable per-prefix IIDs, including for the
> router's interface LLs, using slot/module/interface number or
> slot/module/interface stable ifIndex as the Net_Interface parameter.

For many enterprise and some ISP deployments it's going to be way more 
common to see a VRRP or HSRP mac address (group specific).  At our site, 
we also then set the router LL addr on every interface on every router 
to fe80::1.  It's the one thing I point to and say, "see, ipv6 makes this 
easier."  :-)

Home deployments are probably another matter.  I'm not sure randomizing
my home router mac addr would make any real difference.  Or I guess with 
people's smart TV's now spying on them, there's bigger fish to fry than
creating a new set of interoperability problems.


Dale


From nobody Fri May 27 23:25:55 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 72DAB12D0F1 for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 23:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 wa5FM4cmWObK for <ipv6@ietfa.amsl.com>; Fri, 27 May 2016 23:25:52 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 ABAE0128B44 for <ipv6@ietf.org>; Fri, 27 May 2016 23:25:52 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id x189so124212219ywe.3 for <ipv6@ietf.org>; Fri, 27 May 2016 23:25:52 -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=BAxzFKvp6uzAwMUm4fH1caR5/sLO4cI780cWxfBF/xY=; b=WjncbWNHOxKP0hkwXMoQhyzUMYsXiR48vArm+vlgVOmiG3Rfu4lMJaohA8fzlvttAN ARsc+ju+cjWF2NwlIQxbdgUAaEZdMIhHOTI7tFW7fnwhqEZZS7DopsEL4VGJukdoG1z5 lmmo+AVqrMQ0j/pdwJqRh6t6RWdAyEwA1QY/3EZgIttTBXXtxh4kqYof8s6uuhrZCA5I 9mcL8ah8a0l0CpM//pqlWV/XiXG76m1tTY1fjHY4/v1XYD3Xn1N5JgCQ0I82mVVqKDkt MCxD9qTXrXlXGcCeZuDoo83WHDDuwQXhTrzUpcqBeBdXe2HlYIWKhsU1DJyy6gHxcw2v p+hg==
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=BAxzFKvp6uzAwMUm4fH1caR5/sLO4cI780cWxfBF/xY=; b=mHPGuYSPildl7AFbSiLTyz6NqZqifcWSFQXm1ZgN6P7NFei59zJ2ki+UjAnXP5dmjz EZSk2LKFb+bwuaPfbWZOuJFdFoSPWrhiz2CbeIBQTF0XrTBeO3s8MTtzuE6/Ne8QAVs5 TwoZKMRy0THgPi2ixf4JYlQyeY2DGuBbYJBSGWh5ZiTu/T8DQU3dgwyLgxdYQFMudvLo SDh4nMTjQeimH+Sq8xePFDrfn4SEdLwW/PtYogSB0Y5ed4hHxpb501saRp+L9uP+GtLu qJNjpiK1rHHX6Slt7RaerE1jgqWyYcuuC9MKIFWxiFQeZZPCHFLmG99CsmuOEbxb7EEh kxCQ==
X-Gm-Message-State: ALyK8tJ7zRm0MVaQ79+Na+xz2y4/CH7SHDb+fzxDK+eDmUfGfNd7I3+YcktRFetlz+1W3HAFKaT63gj7Ra0iBa09
X-Received: by 10.129.146.87 with SMTP id j84mr12020759ywg.39.1464416751728; Fri, 27 May 2016 23:25:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.42.20 with HTTP; Fri, 27 May 2016 23:25:32 -0700 (PDT)
In-Reply-To: <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 28 May 2016 15:25:32 +0900
Message-ID: <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0921fe4abe8e0533e11862
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aAeMfDOEHx874nXgaBVbyT_oD9M>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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, 28 May 2016 06:25:54 -0000

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

On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > and  hostname generates AAAA records
> > automatically for the EUI-64 address.
>
> Why? Clients don't need AAAA records. Servers have stable addresses
> anyway, usually with a small-integer IID.
>

DNS records for client machines can be useful if you want to manage them,
run development webservers on them, SSH into them, etc.

--94eb2c0921fe4abe8e0533e11862
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 S=
at, May 28, 2016 at 6:10 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color=
:rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">&gt; and=C2=A0 h=
ostname generates AAAA records<br>
&gt; automatically for the EUI-64 address.<br>
<br>
</span>Why? Clients don&#39;t need AAAA records. Servers have stable addres=
ses anyway,=C2=A0usually with a small-integer IID.<br></blockquote><div><br=
></div><div>DNS records for client machines can be useful if you want to ma=
nage them, run development webservers on them, SSH into them, etc.</div></d=
iv></div></div>

--94eb2c0921fe4abe8e0533e11862--


From nobody Sat May 28 16:41: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 63CB612D0EA; Sat, 28 May 2016 16:41:38 -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-rdnss-rfc6106bis-13.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160528234138.20177.68591.idtracker@ietfa.amsl.com>
Date: Sat, 28 May 2016 16:41:38 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/veoS2P6agrf0zB7HXhdoeDFeLj8>
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, 28 May 2016 23:41: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           : IPv6 Router Advertisement Options for DNS Configuration
        Authors         : Jaehoon Paul Jeong
                          Soohong Daniel Park
                          Luc Beloeil
                          Syam Madanapalli
	Filename        : draft-ietf-6man-rdnss-rfc6106bis-13.txt
	Pages           : 17
	Date            : 2016-05-28

Abstract:
   This document specifies IPv6 Router Advertisement (RA) options
   (called DNS RA options) to allow IPv6 routers to advertise a list of
   DNS recursive server addresses and a DNS Search List to IPv6 hosts.

   This document obsoletes RFC 6106 and allows a higher default value of
   the lifetime of the DNS RA options to avoid the frequent expiry of
   the options on links with a relatively high rate of packet loss.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-13

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


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 Sat May 28 19:30:51 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 6741D12D17C for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 19:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 hUOCAWY_xBIq for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 19:30:48 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::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 5EEA912B062 for <6man@ietf.org>; Sat, 28 May 2016 19:30:48 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id d127so26792086vkh.2 for <6man@ietf.org>; Sat, 28 May 2016 19:30:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=3OwlFZH7fu6oLL489tahe7jX6CjroJ5wV7GEnXLOW5Y=; b=rYkzk6EL5rdVAXJagSCU+H3Fe8F1iyQzEMvl73YPd5sjC+OjBXu+X0ErlXriwTtgzV ytQdDaCTSNgGzzdVRATFI+HNCUaP4WbCjm5pmtEp5PYBO8M2BiobyvFQqOGLiJH8OTS3 kvrv7wBkRVJPRBYt7ieUnDduigCUFAIBdbrDKTXJIhLzmr0yuulfLI6nIRSrnJhaHIf8 vaXwVni1w0mozv9k5oqYc05R9HFxIzZsswA0STb8QI3nUgR4I7ohg25SFurTykkTLwuW OeZtsqpcXRjRgvJLYX82uYlvIxoBfvK/iw4X49FgkSZTINFaVeHo9KQYTcYcwXxydlYC TkzA==
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:date :message-id:subject:from:to:cc; bh=3OwlFZH7fu6oLL489tahe7jX6CjroJ5wV7GEnXLOW5Y=; b=aEKs6/1+sbd6Ie5SVJKCy97+rF0PSrj3bZD+Ju/CjehaxtnVC7HqercC26eYy5vhER 4QNiZTJohonsH2GMEFWGgqoGHXxoPNZmtC87sOSg+oOkYTfKvsy+gy1Nb/RMzVQbP6Pa WfDbbrnUwBRxUBI+5Lrs//XnC2n/dbC5qacUJi/0ozfHfnKq8vq6v7O/qDRhaFg+myqd umF5IymOIYNVYPyUZzJrK8gFr5BF84Nwq3PGarYKn5DVDHQf+cP/dt31bJ8nayIsIqqy Zhclmk5aDR5GMBVyuMu917Gg0i+JCwwe+lQBLqHUVPU9IWNKVmNAH8RMBCITfFNiDbxH BRYw==
X-Gm-Message-State: ALyK8tJqbFVz45mOdJks/BJc0BDhlRGDgueof8T0R7bXmqWot9ibEXkFuigBzgCBb5tv5Hc8KxC4HAQjvmbryQ==
MIME-Version: 1.0
X-Received: by 10.31.72.66 with SMTP id v63mr7469256vka.29.1464489047366; Sat, 28 May 2016 19:30:47 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sat, 28 May 2016 19:30:47 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sat, 28 May 2016 19:30:47 -0700 (PDT)
In-Reply-To: <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com>
Date: Sun, 29 May 2016 12:30:47 +1000
Message-ID: <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114e005472381d0533f1ed77
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pWCOW9FprQjp4fLe25qJuk0B4ME>
Cc: Fernando Gont <fgont@si6networks.com>, 6man@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: Sun, 29 May 2016 02:30:50 -0000

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

On 27 May 2016 12:51 PM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Fri, May 27, 2016 at 12:00 PM, Mark Smith <markzzzsmith@gmail.com>
wrote:
>>>
>>> A simple algorithm would seem to be:
>>> If you don't support, or don't want to use, DNA, then every link is a
new link and you start off with no IP addresses. So you form a link-local
address, send an RS, etc. etc. starting from scratch.
>>
>>
>> That is significantly reducing the robustness of e.g. TCP connections,
as they won't survive that event because their address will change.
>
>
> Most mobile devices close all TCP connections every time a network
disconnects, anyway.

My laptop running general purpose Linux doesn't. Servers don't.

I think that is the insight. I don't think you're considering any other
types of device in this discussion, meaning you won't be seeing where
stable addresses that have increased privacy properties (compared to
EUI-64s, but not in comparison with RFC4941s - which don't meet the
stability requirement) are beneficial.

>The reason for this is that if the device switches to a different network,
the TCP connections are dead anyway (because the IP address changes) and
apps just get stuck. Keeping the connection alive is only useful if you
think that there's a very high chance of reconnecting to the same network
soon, and you either have no other network in the meantime, or you think
you're going to reconnect so soon that it doesn't make sense to
re-establish a connection on another network.
>

>>>
>>> If you support and want to use DNA, then you use DNA with the same MAC
address as you had before.
>>
>>
>> The issue with DNA is that it seems to be relying on the MAC address and
therefore the Link-Local address of the on-link routers being stable for as
the link remains operating. If routers were changing their MAC addresses
periodically too, then DNA will fail. It seems you've been arguing for no
stable L2 and/or L3 addresses on any device, so that would have to mean
that routers don't have them either.
>
>
> Actually, I don't expect that routers will need random MAC addresses.

I think it depends on the type of router. Service provider or
corporate/enterprise router I'd agree.

Residential router, I'd disagree, unless there are any significant
drawbacks.

First thought is new random MACs on boot. The privacy enhancement would be
both periodically changing MAC addresses in WiFi SSID announcements, and no
disclosure of the router NIC manufacturer.

I'll look to find time to do this on my residential router in the next few
weeks.

Regards,
Mark.

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

<p dir=3D"ltr"><br>
On 27 May 2016 12:51 PM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Fri, May 27, 2016 at 12:00 PM, Mark Smith &lt;<a href=3D"mailto:mar=
kzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; A simple algorithm would seem to be:<br>
&gt;&gt;&gt; If you don&#39;t support, or don&#39;t want to use, DNA, then =
every link is a new link and you start off with no IP addresses. So you for=
m a link-local address, send an RS, etc. etc. starting from scratch.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; That is significantly reducing the robustness of e.g. TCP connecti=
ons, as they won&#39;t survive that event because their address will change=
.<br>
&gt;<br>
&gt;<br>
&gt; Most mobile devices close all TCP connections every time a network dis=
connects, anyway.</p>
<p dir=3D"ltr">My laptop running general purpose Linux doesn&#39;t. Servers=
 don&#39;t.</p>
<p dir=3D"ltr">I think that is the insight. I don&#39;t think you&#39;re co=
nsidering any other types of device in this discussion, meaning you won&#39=
;t be seeing where stable addresses that have increased privacy properties =
(compared to EUI-64s, but not in comparison with RFC4941s - which don&#39;t=
 meet the stability requirement) are beneficial.<br></p>
<p dir=3D"ltr">&gt;The reason for this is that if the device switches to a =
different network, the TCP connections are dead anyway (because the IP addr=
ess changes) and apps just get stuck. Keeping the connection alive is only =
useful if you think that there&#39;s a very high chance of reconnecting to =
the same network soon, and you either have no other network in the meantime=
, or you think you&#39;re going to reconnect so soon that it doesn&#39;t ma=
ke sense to re-establish a connection on another network.<br>
&gt; =C2=A0</p>
<p dir=3D"ltr">&gt;&gt;&gt;<br>
&gt;&gt;&gt; If you support and want to use DNA, then you use DNA with the =
same MAC address as you had before.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The issue with DNA is that it seems to be relying on the MAC addre=
ss and therefore the Link-Local address of the on-link routers being stable=
 for as the link remains operating. If routers were changing their MAC addr=
esses periodically too, then DNA will fail. It seems you&#39;ve been arguin=
g for no stable L2 and/or L3 addresses on any device, so that would have to=
 mean that routers don&#39;t have them either.<br>
&gt;<br>
&gt;<br>
&gt; Actually, I don&#39;t expect that routers will need random MAC address=
es.</p>
<p dir=3D"ltr">I think it depends on the type of router. Service provider o=
r corporate/enterprise router I&#39;d agree.</p>
<p dir=3D"ltr">Residential router, I&#39;d disagree, unless there are any s=
ignificant drawbacks.</p>
<p dir=3D"ltr">First thought is new random MACs on boot. The privacy enhanc=
ement would be both periodically changing MAC addresses in WiFi SSID announ=
cements, and no disclosure of the router NIC manufacturer.</p>
<p dir=3D"ltr">I&#39;ll look to find time to do this on my residential rout=
er in the next few weeks.</p>
<p dir=3D"ltr">Regards,<br>
Mark.</p>

--001a114e005472381d0533f1ed77--


From nobody Sat May 28 21:18:37 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 271B412D1A8 for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 21:18:36 -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 iq7NQidyL-bm for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 21:18:34 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::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 9697312D140 for <ipv6@ietf.org>; Sat, 28 May 2016 21:18:34 -0700 (PDT)
Received: by mail-pa0-x22b.google.com with SMTP id xk12so51603188pac.0 for <ipv6@ietf.org>; Sat, 28 May 2016 21:18:34 -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=W4ZU5b5bPQFQMf6zzazKQWeutYiilZIdxMwh07zsYm4=; b=pIy/d8wME1L978ZbMqptMtFCFrPqikbCrWK5hePKvI3k9Tk1orFRRFPyc1lYHn9QXd VFYoCrZmOjl1T6SwzxvcsypHfGMcSKJoKPlvSAKHKzgQfJ4dnmCTyurY8h6hWL6EofVz dnNPEWVTb6yI3ZsvaHNUmzVwYsrMbLfjSBIveqMncDdgeblx+Ve4R2vlx2tMsSfX0hMD SPfOBstW7kFRGXWrnfwyjeYlqn9RmXPYNpBZ3hdjgcJeIq1aSXAApW03K6d4ll1Qrd7P qGTmNA3qDiL0oaf566S4XhW0cn2SY/YtlpW9V309akes83n7szuBGB5h71hvg4GQJUoK clzQ==
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=W4ZU5b5bPQFQMf6zzazKQWeutYiilZIdxMwh07zsYm4=; b=MdfPrXqTR4ug2IFZGHV3nPU5v36+7doiMLICIyeSBmGqpH+6Wbc0XAm+cyj9xwoi/c Sfk+XRzdfXzm0/U983gCKZMEMByPVukrdIqDfA9MAVv9lwoTe1/4ZZvXytrr8hpMDYpL HL8M1yuHysTCyExw8hjFqSIN2qX3SQHibhugvoeOamKfJWcbQsA4CF8DCzdMkv+qkqoQ apvT0D7MZHUHXMypLXUG6eBoqAOxzl6/7cu0/sB/nNNTL/XKnNpFcTKTzlACfO3ZpHXJ 07VItdYL0AY6Z5PYm8BowlWPAS4lqZzdLh4AW+YSyWutDI+0nm8n0lpXVYDJK2RNsvum 4xwg==
X-Gm-Message-State: ALyK8tJ41oQ6HIhG8JzNlDN8WBC7HOi07pFFl0lXeL/Doj7isxn+qNjHAFz22+OkjL7iOw==
X-Received: by 10.66.21.102 with SMTP id u6mr35365664pae.118.1464495514131; Sat, 28 May 2016 21:18:34 -0700 (PDT)
Received: from ?IPv6:2406:e007:5923:1:113c:42f3:b0e2:80e1? ([2406:e007:5923:1:113c:42f3:b0e2:80e1]) by smtp.gmail.com with ESMTPSA id 22sm23617046pfw.92.2016.05.28.21.18.30 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 28 May 2016 21:18:33 -0700 (PDT)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Lorenzo Colitti <lorenzo@google.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a5f060f5-44e5-c868-ffe8-2aa6cf7f0d41@gmail.com>
Date: Sun, 29 May 2016 16:18:29 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gF6zaQBBgB8KXnb0vY6pWDTo24I>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 04:18:36 -0000

On 28/05/2016 18:25, Lorenzo Colitti wrote:
> On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>>> and  hostname generates AAAA records
>>> automatically for the EUI-64 address.
>>
>> Why? Clients don't need AAAA records. Servers have stable addresses
>> anyway, usually with a small-integer IID.
>>
> 
> DNS records for client machines can be useful if you want to manage them,
> run development webservers on them, SSH into them, etc.

Fair enough, for campus deployments, but of course there's no need to bind
that requirement to EUI-64.

    Brian


From nobody Sat May 28 21:49: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 B78C212B028 for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 21:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 c_psLq3BZfQE for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 21:49:17 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::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 1448312B00D for <ipv6@ietf.org>; Sat, 28 May 2016 21:49:16 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id x189so138770482ywe.3 for <ipv6@ietf.org>; Sat, 28 May 2016 21:49: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:date:message-id:subject:from:to :cc; bh=0YbXJ9O4I7a/JpxxEvziX+jG/ZFgNjhP69Lwt9skTYE=; b=fKl2C++/MDk6n3FU4zHXFpzx6Pdn+3gQM7NxR9DV8suv8kFSwUg4R52NalhxBxC8et EAPuMLIZa1zvcasupjwk3US2FXE1NNpExWuWZsFGVJb0uK/br8Qu+KHruIpwfiuW+6IX CZrRhQK61qwaMaYi4doqLAriX3NWVk5985kdfYKgInZWBU8tkdm3b14ZrjvcFVqEHECK NFI/dDiu9Ub8nzbkXCrZpeWAQX6ughyZytA29t8cQoo/besI0JrXzx1zfOTI44JqMVyG uRWOrzkDggaWhAHJmbIYDyycuUaYhcM8zS4R1CBl3g3+G11raOToaZ86MEktOdbrXO/l ufVQ==
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:date :message-id:subject:from:to:cc; bh=0YbXJ9O4I7a/JpxxEvziX+jG/ZFgNjhP69Lwt9skTYE=; b=mNNSyV3n8c3GxrmocLUECfiwg7lg59ElRYrnbRVtn43kLT26/Sk8nHoYJ4e03ffNMD 0+fhBVKL0LcJuSMvlHFSiVeRirhfzuxKZOV3cOEXhwAKU2EmALrB92tS3zYVE4sPV2Vt 4LdAierjWCbzkcMOy/SKBgVbjMZkRC84GfGJg5vWAQQG3HS9NEEPX81LEOOeTv3ynggl 4UCklU5byDAMzdlmuoJTOM2HCYL6NwBCH0moAGD9Df7dq85nIcBpIi+5uRQbIOYQ/kqb 7hi2YvkQVYZjbE+n6agSvkuv4gnDezCtD1zMtsTg2ImOzqh7DsxBKiCBSyKWwO8dYRKF n+Cg==
X-Gm-Message-State: ALyK8tLwtkMCZc16m6w2fU9UnfaF1oYoOLl4rBg9FLVt9Ii5v/5Aao8GYdk50vnRI4zx2nNoIgJnmLGRp54yCUVp
MIME-Version: 1.0
X-Received: by 10.37.79.87 with SMTP id d84mr12795209ybb.49.1464497355971; Sat, 28 May 2016 21:49:15 -0700 (PDT)
Received: by 10.37.198.210 with HTTP; Sat, 28 May 2016 21:49:15 -0700 (PDT)
Received: by 10.37.198.210 with HTTP; Sat, 28 May 2016 21:49:15 -0700 (PDT)
In-Reply-To: <a5f060f5-44e5-c868-ffe8-2aa6cf7f0d41@gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <a5f060f5-44e5-c868-ffe8-2aa6cf7f0d41@gmail.com>
Date: Sun, 29 May 2016 13:49:15 +0900
Message-ID: <CAKD1Yr1CD9=ZxZmK1DcSW22Zvy_z4mzqfmtF53NCsUMeOfa4HQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Lorenzo Colitti <lorenzo@google.com>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113f5cd0adee540533f3dc45
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/kOAIVv7vX-JliYuDURxjD_gNq1o>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 04:49:18 -0000

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

Actually there is: the IPv6 addresses are predictable, so DNS records can
be generated without having to build any additional infrastructure. As I
said in the email you quoted:

=====
RFC7217 breaks that because you'd have to either predict the address -
which relies on knowing the implementation and ensuring that every machine
boots with the same secret key - or scrape the address once the machine has
booted, which introduces a bootstrapping problem. DHCPv6 could fix this -
assuming the implementations don't default to LL+T DUIDs, which can't be
predicted - but it involves provisioning and running new servers that might
not exist. Dynamic DNS updates could also fix that, but it also requires
building infrastructure that might not exist.
=====
On 29 May 2016 1:18 pm, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 28/05/2016 18:25, Lorenzo Colitti wrote:
> > On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter <
> > brian.e.carpenter@gmail.com> wrote:
> >
> >>> and  hostname generates AAAA records
> >>> automatically for the EUI-64 address.
> >>
> >> Why? Clients don't need AAAA records. Servers have stable addresses
> >> anyway, usually with a small-integer IID.
> >>
> >
> > DNS records for client machines can be useful if you want to manage them,
> > run development webservers on them, SSH into them, etc.
>
> Fair enough, for campus deployments, but of course there's no need to bind
> that requirement to EUI-64.
>
>     Brian
>

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

<p dir=3D"ltr">Actually there is: the IPv6 addresses are predictable, so DN=
S records can be generated without having to build any additional infrastru=
cture. As I said in the email you quoted:</p>
<p dir=3D"ltr">=3D=3D=3D=3D=3D<br>
RFC7217 breaks that because you&#39;d have to either predict the address - =
which relies on knowing the implementation and ensuring that every machine =
boots with the same secret key - or scrape the address once the machine has=
 booted, which introduces a bootstrapping problem. DHCPv6 could fix this - =
assuming the implementations don&#39;t default to LL+T DUIDs, which can&#39=
;t be predicted - but it involves provisioning and running new servers that=
 might not exist. Dynamic DNS updates could also fix that, but it also requ=
ires building infrastructure that might not exist.<br>
=3D=3D=3D=3D=3D</p>
<div class=3D"gmail_quote">On 29 May 2016 1:18 pm, &quot;Brian E Carpenter&=
quot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@=
gmail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">On 28/05/2016 18:25, Lorenzo Colitti wrote:<br>
&gt; On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter &lt;<br>
&gt; <a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail=
.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt;&gt; and=C2=A0 hostname generates AAAA records<br>
&gt;&gt;&gt; automatically for the EUI-64 address.<br>
&gt;&gt;<br>
&gt;&gt; Why? Clients don&#39;t need AAAA records. Servers have stable addr=
esses<br>
&gt;&gt; anyway, usually with a small-integer IID.<br>
&gt;&gt;<br>
&gt;<br>
&gt; DNS records for client machines can be useful if you want to manage th=
em,<br>
&gt; run development webservers on them, SSH into them, etc.<br>
<br>
Fair enough, for campus deployments, but of course there&#39;s no need to b=
ind<br>
that requirement to EUI-64.<br>
<br>
=C2=A0 =C2=A0 Brian<br>
</blockquote></div>

--001a113f5cd0adee540533f3dc45--


From nobody Sat May 28 22:24:41 2016
Return-Path: <joelja@bogus.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 6BD1F12D0FE for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 22:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level: 
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 5A92XSVSVwHX for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 22:24:38 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 9F27C12D0A5 for <ipv6@ietf.org>; Sat, 28 May 2016 22:24:38 -0700 (PDT)
Received: from mb-2.local (80-219-237-103.dclient.hispeed.ch [80.219.237.103]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4T5OTHA098775 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sun, 29 May 2016 05:24:31 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host 80-219-237-103.dclient.hispeed.ch [80.219.237.103] claimed to be mb-2.local
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com>
Date: Sun, 29 May 2016 07:24:21 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6CRTql8Stl5Q86Ubx8tGgD4gCSovS69bd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9RUaWFaTxnM3hRPLtm6o9u-m-6A>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 05:24:40 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6CRTql8Stl5Q86Ubx8tGgD4gCSovS69bd
Content-Type: multipart/mixed; boundary="3a40wkWIc6MOeSXdgCEXmQjtSqAdeQ6Rv"
From: joel jaeggli <joelja@bogus.com>
To: Lorenzo Colitti <lorenzo@google.com>,
 Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>,
 draft-ietf-6man-default-iids@tools.ietf.org, 6man WG <ipv6@ietf.org>,
 =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Message-ID: <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com>
Subject: Re: default-iids: Closing concern regarding stable address
 requirement
References: <5742118B.6020308@si6networks.com>
 <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com>
 <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com>
 <m1b57qM-0000HYC@stereo.hq.phicoh.net>
 <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org>
 <57461B9D.2080001@si6networks.com>
 <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org>
 <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com>
 <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org>
 <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com>
 <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com>
 <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com>
 <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com>

--3a40wkWIc6MOeSXdgCEXmQjtSqAdeQ6Rv
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 5/28/16 8:25 AM, Lorenzo Colitti wrote:
> On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrot=
e:
>=20
>     > and  hostname generates AAAA records
>     > automatically for the EUI-64 address.
>=20
>     Why? Clients don't need AAAA records. Servers have stable addresses=

>     anyway, usually with a small-integer IID.
>=20
>=20
> DNS records for client machines can be useful if you want to manage
> them, run development webservers on them, SSH into them, etc.

There's also this thing called dhcpv6 for applications where the users
or administrators prefer centrally managed address assignment,

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



--3a40wkWIc6MOeSXdgCEXmQjtSqAdeQ6Rv--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAldKfQYACgkQ8AA1q7Z/VrKO8wCfbo8bW4Hiy38rF0ERqLfSGLj/
DzoAn3tFV8g+NzAu5HXE/deshaiQskkN
=7Tz9
-----END PGP SIGNATURE-----

--6CRTql8Stl5Q86Ubx8tGgD4gCSovS69bd--


From nobody Sat May 28 23:02:01 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 8FD2F12B04F for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 23:01:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 ji27lkeF5jrQ for <ipv6@ietfa.amsl.com>; Sat, 28 May 2016 23:01:56 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 C893A12B03D for <ipv6@ietf.org>; Sat, 28 May 2016 23:01:52 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id o16so139554250ywd.2 for <ipv6@ietf.org>; Sat, 28 May 2016 23:01:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6GL4nCCmolVtBYIFvy2CjWvziWFArLWidgeaVTtUHD4=; b=Ui8We/0Ae/sLSDlZhSTkjR4yJv/+vWS/jAXmtQPqxNdqCzZHcgLhFUA49m0HIzSDQ3 hcGfnF4TqDkZBj9+es5eM71ysfossL0yJFKWrFagfbmaLOpFJ3pc01J5A6ZTB7d1Xk25 jhThKJX4an1jAJv7F9vwxOOaZCAoWOtJ8iWJLodwwr6IHjPeMUgAS/1vyamCiPRDd28b l+ifeLD8V2RjQiPRLCV/IqDf9mR4lOrvWscI2ISAAGoEAok0otEeRwSPeu3JKgfxI/Vr ngIqnPpIFre2sOG1ypDpVcv32GN5aE7/lBupUOt0AmrLUxmpm7UCuNM9FSSf8m+NOOa6 ajRQ==
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:date :message-id:subject:from:to:cc; bh=6GL4nCCmolVtBYIFvy2CjWvziWFArLWidgeaVTtUHD4=; b=Cy75JQZy7eATa7tsgc4wgbaulnWAg+b3VosMPaZ4oSzP5Y0VHNCaU1x3ebEy0CTxbI bCWyB4cwaEn/KuusyoLWets24oAuihaG5o6tUlTm8PTDtT9oQPSzii7xPCtIm5q307lF B+xYlf+WD2zsuqCMF1lLvZRKsss6/yFPHYhb3SE4YbnVsJWBae2vvR0Z246IML162lLV crGghHhhFrkrll/1LEKFUHF4pOKWVXmdyM8zC4uqPYLaxsm6cOdjaSVcIs50FHPmFXep ZOLC2u2lnjfNW5ny66TXxDcjvhZFVkkFpPZLNMJ5K4uenyOaOMvmCBuHBc+U/uY4gGY/ KRrg==
X-Gm-Message-State: ALyK8tJRqFdboPU+nRTTUw3zqTOj/pmL07587eMGIR1dr57RJX9srkNH99dxnbif5dKkhXMS2M0Thk6joPoaGNcG
MIME-Version: 1.0
X-Received: by 10.37.228.198 with SMTP id b189mr13624289ybh.25.1464501711852;  Sat, 28 May 2016 23:01:51 -0700 (PDT)
Received: by 10.37.198.210 with HTTP; Sat, 28 May 2016 23:01:51 -0700 (PDT)
Received: by 10.37.198.210 with HTTP; Sat, 28 May 2016 23:01:51 -0700 (PDT)
In-Reply-To: <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com>
Date: Sun, 29 May 2016 15:01:51 +0900
Message-ID: <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Lorenzo Colitti <lorenzo@google.com>
To: Joel Jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=001a114bc1c64f56c60533f4e04c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/T9OD8EfYtRKnK4FeCM2UzCMseMc>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 06:02:00 -0000

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

On 29 May 2016 2:24 pm, "joel jaeggli" <joelja@bogus.com> wrote:
>
> On 5/28/16 8:25 AM, Lorenzo Colitti wrote:
> > On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter
> > <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
wrote:
> >
> >     > and  hostname generates AAAA records
> >     > automatically for the EUI-64 address.
> >
> >     Why? Clients don't need AAAA records. Servers have stable addresses
> >     anyway, usually with a small-integer IID.
> >
> >
> > DNS records for client machines can be useful if you want to manage
> > them, run development webservers on them, SSH into them, etc.
>
> There's also this thing called dhcpv6 for applications where the users
> or administrators prefer centrally managed address assignment,

Yep. Like I said, that one requires building and maintaining infrastructure
that might not exist. Also, the addresses are not predictable unless the
clients default to using LL DUIDs instead of LL+T.

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

<p dir=3D"ltr"><br>
On 29 May 2016 2:24 pm, &quot;joel jaeggli&quot; &lt;<a href=3D"mailto:joel=
ja@bogus.com">joelja@bogus.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 5/28/16 8:25 AM, Lorenzo Colitti wrote:<br>
&gt; &gt; On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter<br>
&gt; &gt; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpen=
ter@gmail.com</a> &lt;mailto:<a href=3D"mailto:brian.e.carpenter@gmail.com"=
>brian.e.carpenter@gmail.com</a>&gt;&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0&gt; and=C2=A0 hostname generates AAAA records=
<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0&gt; automatically for the EUI-64 address.<br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0Why? Clients don&#39;t need AAAA records. Serv=
ers have stable addresses<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0anyway, usually with a small-integer IID.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; DNS records for client machines can be useful if you want to mana=
ge<br>
&gt; &gt; them, run development webservers on them, SSH into them, etc.<br>
&gt;<br>
&gt; There&#39;s also this thing called dhcpv6 for applications where the u=
sers<br>
&gt; or administrators prefer centrally managed address assignment,</p>
<p dir=3D"ltr">Yep. Like I said, that one requires building and maintaining=
 infrastructure that might not exist. Also, the addresses are not predictab=
le unless the clients default to using LL DUIDs instead of LL+T.</p>

--001a114bc1c64f56c60533f4e04c--


From nobody Sun May 29 00:14:02 2016
Return-Path: <joelja@bogus.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 B251612D15D for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 00:14:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.325
X-Spam-Level: 
X-Spam-Status: No, score=-8.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] 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 jMZx2aXbBv8J for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 00:13:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 6B7F312D0C6 for <ipv6@ietf.org>; Sun, 29 May 2016 00:13:59 -0700 (PDT)
Received: from [100.175.111.117] ([172.56.6.30]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u4T7DjDi099109 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 29 May 2016 07:13:53 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [172.56.6.30] claimed to be [100.175.111.117]
Content-Type: multipart/alternative; boundary=Apple-Mail-7DEE6D06-96B8-4E53-9CBB-3DEB7F1F33B7
Mime-Version: 1.0 (1.0)
Subject: Re: default-iids: Closing concern regarding stable address requirement
From: Joel Jaeggli <joelja@bogus.com>
X-Mailer: iPhone Mail (13F69)
In-Reply-To: <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com>
Date: Sun, 29 May 2016 09:13:38 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com> <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-7vo2jp8Y3kVxG9yT1Ddv7YoziM>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 07:14:02 -0000

--Apple-Mail-7DEE6D06-96B8-4E53-9CBB-3DEB7F1F33B7
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



Sent from my iPhone

> On May 29, 2016, at 08:01, Lorenzo Colitti <lorenzo@google.com> wrote:
>=20
>=20
> On 29 May 2016 2:24 pm, "joel jaeggli" <joelja@bogus.com> wrote:
> >
> > On 5/28/16 8:25 AM, Lorenzo Colitti wrote:
> > > On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter
> > > <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wro=
te:
> > >
> > >     > and  hostname generates AAAA records
> > >     > automatically for the EUI-64 address.
> > >
> > >     Why? Clients don't need AAAA records. Servers have stable addresse=
s
> > >     anyway, usually with a small-integer IID.
> > >
> > >
> > > DNS records for client machines can be useful if you want to manage
> > > them, run development webservers on them, SSH into them, etc.
> >
> > There's also this thing called dhcpv6 for applications where the users
> > or administrators prefer centrally managed address assignment,
>=20
> Yep. Like I said, that one requires building and maintaining infrastructur=
e that might not exist. Also, the addresses are not predictable unless the c=
lients default to using LL DUIDs instead of LL+T.
>=20
Or use hostid because devices may have multiple interfaces anyway=

--Apple-Mail-7DEE6D06-96B8-4E53-9CBB-3DEB7F1F33B7
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>On May 29, 2016, at 08:01, Lorenzo Colitti &lt;<a href="mailto:lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><p dir="ltr"><br>
On 29 May 2016 2:24 pm, "joel jaeggli" &lt;<a href="mailto:joelja@bogus.com">joelja@bogus.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 5/28/16 8:25 AM, Lorenzo Colitti wrote:<br>
&gt; &gt; On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter<br>
&gt; &gt; &lt;<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a> &lt;mailto:<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt;&nbsp; &nbsp; &nbsp;&gt; and&nbsp; hostname generates AAAA records<br>
&gt; &gt;&nbsp; &nbsp; &nbsp;&gt; automatically for the EUI-64 address.<br>
&gt; &gt;<br>
&gt; &gt;&nbsp; &nbsp; &nbsp;Why? Clients don't need AAAA records. Servers have stable addresses<br>
&gt; &gt;&nbsp; &nbsp; &nbsp;anyway, usually with a small-integer IID.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; DNS records for client machines can be useful if you want to manage<br>
&gt; &gt; them, run development webservers on them, SSH into them, etc.<br>
&gt;<br>
&gt; There's also this thing called dhcpv6 for applications where the users<br>
&gt; or administrators prefer centrally managed address assignment,</p>
<p dir="ltr">Yep. Like I said, that one requires building and maintaining infrastructure that might not exist. Also, the addresses are not predictable unless the clients default to using LL DUIDs instead of LL+T.</p>
</div></blockquote><div>Or use hostid because devices may have multiple interfaces anyway</div></body></html>
--Apple-Mail-7DEE6D06-96B8-4E53-9CBB-3DEB7F1F33B7--


From nobody Sun May 29 04:30:27 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 BFBE312D1D5 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 04:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 XcVTVTRNkiVC for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 04:30:25 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::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 E572F12D0ED for <6man@ietf.org>; Sun, 29 May 2016 04:30:24 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id o16so142429050ywd.2 for <6man@ietf.org>; Sun, 29 May 2016 04:30:24 -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=pjR//u2sUgIenNAdzw8gtdBVYadRaksaObHLEXUxbjM=; b=n+4IR2YQWiP2ERHt++1UEjHFYHqJWxao+ZifTt36WT8g25Qt8zVZ7rDpH7oLWn1euU NFoW4Pd7lNaeH4+3CtKgE1aRLO5rk+x0FO8R5wi+qG/Rt2wqGT+Lk6XzbAo6ZFciVSQD 2Hb/Vh6yrD65w1jrygDH2HCugaHTmX9JIm1n2Jv8U4DDkurB5Aq7d+84xvCHpWd3ezJj HLHOLo+Joo3A4DQDI6fofp9diNny2Z5nmvfaqvjKNB2ZcFjIvSark5k4qCgtSztu5DsK dseSXPN08boV+rvyzdayRbGsHIhYteLq2WXExawbeLCzOFJXBb7jHx4qf8TtzPoS7eU4 VtWg==
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=pjR//u2sUgIenNAdzw8gtdBVYadRaksaObHLEXUxbjM=; b=i0g9QtIioxTROYlamNzqPKMMUF7W+rOPWNYSLMLt5BJqPnpLzJsQpQXByW6a4U5CXH 9zdyZg8bzvYDj7n+OxvFe4wk/5JdM1LD8OwbdXX1zI8v0NVYXZ5I8j0V5wgcudXCOTSD PzoWa3w7PwgckhMOMWXYM25+WFQhToBjo8My+ysK8CsT/QG738IdLL8CS8BdAb9PTabq SZs/sYsvrySm2yrPbyG+E4vnazcLtMmQ7nhdXqGdOL3aT9bh1XfBpPsLyCNBPcMea2CR 22EsTwYvF2OrmkC5BaNKZdAMZk27VFfqDJkhf7h2rwsH04vgtlW9sx6gbwQl9cuRYGxY rv3Q==
X-Gm-Message-State: ALyK8tLyGaNox9s0tCPUwqj2hLksNw+0LkUHVstj1F2DJS88oSNAR90N1/zQqTg8D5AGXzpZsy8+I+L+O5puSibn
X-Received: by 10.37.193.4 with SMTP id r4mr12766948ybf.185.1464521423891; Sun, 29 May 2016 04:30:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Sun, 29 May 2016 04:30:04 -0700 (PDT)
In-Reply-To: <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 29 May 2016 20:30:04 +0900
Message-ID: <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c05529c3d21990533f977cb
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yooqKuWFMf7AucanRlA7s9-vpEo>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Sun, 29 May 2016 11:30:27 -0000

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

On Sun, May 29, 2016 at 11:30 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> > Most mobile devices close all TCP connections every time a network
> disconnects, anyway.
>
> My laptop running general purpose Linux doesn't. Servers don't.
>
Your laptop doesn't do that, but perhaps it should. The fact that it
doesn't means that applications are forced to do it. For example:

   - Chrome has code that listens to netlink events and closes all sockets
   when addresses change.
   - It becomes impossible to use SSH with port forwarding across network
   switches because the forwarded port is still mapped to a TCP connection
   that will never come back because your IP address has changed. So you have
   to configure TCP keepalives.
   - ... and so on.

You could argue that this should in fact be up to the application, but I
think it's reasonable for the system to do it. Many OSes do. For mobile
devices, it's a necessity.

As for servers, numbering them with EUI-64 or RFC7217 (which has the same
stability properties, i.e., the stable for the life of the network card)
seems silly compared to giving them static addresses.> Actually, I don't
expect that routers will need random MAC addresses.

> I think it depends on the type of router. Service provider or
> corporate/enterprise router I'd agree.
>
> Residential router, I'd disagree, unless there are any significant
> drawbacks.
>
> First thought is new random MACs on boot. The privacy enhancement would be
> both periodically changing MAC addresses in WiFi SSID announcements, and no
> disclosure of the router NIC manufacturer.
>
> I'll look to find time to do this on my residential router in the next few
> weeks.
>
Good luck getting an an IPv4 address after rebooting the router 3 times in
5 minutes. Many ISPs only allow 1 or 2 IPv4 addresses per connection.

--94eb2c05529c3d21990533f977cb
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 S=
un, May 29, 2016 at 11:30 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:markzzzsmith@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-left:1px #ccc solid;padding-left:1ex"><span class=3D""><p dir=
=3D"ltr">&gt; Most mobile devices close all TCP connections every time a ne=
twork disconnects, anyway.</p>
</span><p dir=3D"ltr">My laptop running general purpose Linux doesn&#39;t. =
Servers don&#39;t.</p></blockquote><div>Your laptop doesn&#39;t do that, bu=
t perhaps it should. The fact that it doesn&#39;t means that applications a=
re forced to do it. For example:</div><div><ul><li>Chrome has code that lis=
tens to netlink events and closes all sockets when addresses change.<br></l=
i><li>It becomes impossible to use SSH with port forwarding across network =
switches because the forwarded port is still mapped to a TCP connection tha=
t will never come back because your IP address has changed. So you have to =
configure TCP keepalives.<br></li><li>... and so on.</li></ul><div>You coul=
d argue that this should in fact be up to the application, but I think it&#=
39;s reasonable for the system to do it. Many OSes do. For mobile devices, =
it&#39;s a necessity.</div></div><div><br></div><div>As for servers, number=
ing them with EUI-64 or RFC7217 (which has the same stability properties, i=
.e., the stable for the life of the network card) seems silly compared to g=
iving them static addresses.&gt; Actually, I don&#39;t expect that routers =
will need random MAC addresses.</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir=
=3D"ltr">I think it depends on the type of router. Service provider or corp=
orate/enterprise router I&#39;d agree.</p>
<p dir=3D"ltr">Residential router, I&#39;d disagree, unless there are any s=
ignificant drawbacks.</p>
<p dir=3D"ltr">First thought is new random MACs on boot. The privacy enhanc=
ement would be both periodically changing MAC addresses in WiFi SSID announ=
cements, and no disclosure of the router NIC manufacturer.</p>
<p dir=3D"ltr">I&#39;ll look to find time to do this on my residential rout=
er in the next few weeks.</p></blockquote><div>Good luck getting an an IPv4=
 address after rebooting the router 3 times in 5 minutes. Many ISPs only al=
low 1 or 2 IPv4 addresses per connection.<br></div></div></div></div>

--94eb2c05529c3d21990533f977cb--


From nobody Sun May 29 13:18:20 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 277A112B04B for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 13:18: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 JqJDXeC-7Ho8 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 13:18:16 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::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 77B6112B004 for <ipv6@ietf.org>; Sun, 29 May 2016 13:18:16 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id g64so57961123pfb.2 for <ipv6@ietf.org>; Sun, 29 May 2016 13:18:16 -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=6rUtqysXYHf6NSBLw7uhhnWJYxJxVfLgPo+IRCOkoQQ=; b=WPzocwK4KGk8gOtJmP2pzeJ1wHDqf0dlijvQW9aOxESKb2rI1xU1L6uCbHInTjCXsa zLJMXaQtAHUt1YxhnDuRWag4zvMnkw+p9cM8F/8TAmzr7pXtYyifF0vnA78esSoRumsY IazlrIUzQJBfsmdMEvvT9/GcNUT4IvedqihGjAhTTJaQVq7yIsXbkN2IQun7Psmt2s3f UsrraYB26VAM7AVfzlJuLwXMIhEEiUrtThMFTiw0mxh8HIyzYdfO93ASDOZ4zxXKwvS8 Ft73JkhR/f/oBBgeK6PFJ85IkLVMOpRiVQQViLa4nL8BdYTo3IwiM46qVJH5wWdJWEqX CW3Q==
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=6rUtqysXYHf6NSBLw7uhhnWJYxJxVfLgPo+IRCOkoQQ=; b=kweqY6lkqhFwi6V7F4MFaEm6ARy4uzXzqeUUw/x0ZZTOGGNVqXi3pNQaeddkCxm2lr WafSwJUhYPHt2XzrKIjaeAcQAeCd1bwnb061sjSokELSfRCztDdTraSjlgJQX43Xy39d kKXvAnHlcPLEOi9QngBWSxqwO+zRrQHnPcfkf+9dufdj08wO5MDZpj9VrSxYLpESiRTS 4Td259EYd37cHmW9E6iAIj67yFzdNV9uuY/VVO03i7RBUbGbhFxyo4eJ42s0LxfQDUDp BzqZogIYC6uK/JNEFmyX+WD8X9KP7orWnUCp8NnwTAovRkUKbnMt/Tu0szd+s76s8Shp nfyw==
X-Gm-Message-State: ALyK8tJI6yVktcFZZF4313SAvgJTolToMTxWhqrv0GrBRv2wrEFhRMoy2nkW/e9O9N0Z5w==
X-Received: by 10.98.87.133 with SMTP id i5mr40549365pfj.55.1464553095712; Sun, 29 May 2016 13:18:15 -0700 (PDT)
Received: from ?IPv6:2406:e007:5cae:1:292d:ccde:784:1cc4? ([2406:e007:5cae:1:292d:ccde:784:1cc4]) by smtp.gmail.com with ESMTPSA id o1sm42107185pax.24.2016.05.29.13.18.12 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2016 13:18:14 -0700 (PDT)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Joel Jaeggli <joelja@bogus.com>, Lorenzo Colitti <lorenzo@google.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com> <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com> <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com>
Date: Mon, 30 May 2016 08:18:09 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/X80giphLXJitLq1ROUJRGAc591w>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Sun, 29 May 2016 20:18:18 -0000

On 29/05/2016 19:13, Joel Jaeggli wrote:
> 
> 
> Sent from my iPhone
> 
>> On May 29, 2016, at 08:01, Lorenzo Colitti <lorenzo@google.com> wrote:
>>
>>
>> On 29 May 2016 2:24 pm, "joel jaeggli" <joelja@bogus.com> wrote:
>>>
>>> On 5/28/16 8:25 AM, Lorenzo Colitti wrote:
>>>> On Sat, May 28, 2016 at 6:10 AM, Brian E Carpenter
>>>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>>>>
>>>>     > and  hostname generates AAAA records
>>>>     > automatically for the EUI-64 address.
>>>>
>>>>     Why? Clients don't need AAAA records. Servers have stable addresses
>>>>     anyway, usually with a small-integer IID.
>>>>
>>>>
>>>> DNS records for client machines can be useful if you want to manage
>>>> them, run development webservers on them, SSH into them, etc.
>>>
>>> There's also this thing called dhcpv6 for applications where the users
>>> or administrators prefer centrally managed address assignment,
>>
>> Yep. Like I said, that one requires building and maintaining infrastructure that might not exist. Also, the addresses are not predictable unless the clients default to using LL DUIDs instead of LL+T.
>>
> Or use hostid because devices may have multiple interfaces anyway

So, I just don't see how we can claim to dictate any kind of general default
or BCP in this area. But I don't seee that draft-ietf-6man-default-iids does
that. Maybe it should be toned down to a SHOULD level, e.g.

Abstract

   This document changes the recommended scheme for generating stable
   Interface Identifiers with SLAAC to that specified in RFC7217, and
   recommends against embedding 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 accordingly.

and similar changes in the body of the draft.

Again, the 'bug' in 4941 is a separate issue.

   Brian


From nobody Sun May 29 14:01:14 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 A7CBC12D0F8 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 14:01:13 -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 1avfd9GpuaIF for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 14:01:11 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::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 C5BE412D12E for <ipv6@ietf.org>; Sun, 29 May 2016 14:01:11 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id g64so58128982pfb.2 for <ipv6@ietf.org>; Sun, 29 May 2016 14:01:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:from:organization:to:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Li26HMpRHDlLacUhrgLnTCIh6RC5QV63L8iVLmbtCmo=; b=EOxO0Hvpe5vDMUF2C4vwkGzzwhtaXKv/2zYjK+g9og0YDcF8VYEY2C2mlYoDO/qqsd mJuSNNqrlbT9xoYxc0xtvFO6FHB/G3CY7dFMflZcFQG97JnH417m/qLwaA5+NPSuvA63 g/BCBYgZyHomFa4D9A+JcqHlHntoH825TAgOkZRGiI4j3hfa4p9AhFPF9H5EGueEDTXu TKkLF3hbTmODRQurHxShVL0uExFP+tg5+91za42T331EUwHiLpbOODueTdlwHLksET94 WmADlwf1REpaYIJvM60ShnuhTnHGNUDoaXmM/UHDkwEMDQe7FOPubISRbyCsTlQ43mwb MuRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:organization:to :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Li26HMpRHDlLacUhrgLnTCIh6RC5QV63L8iVLmbtCmo=; b=Bs+ZntATKhS8dgl/gB4VaJI6aEPrSuMvgixia1/whVj1CkBENOU8itVbnNl15nl0Kv B9CffOko51Ao7+pB6v50d+Ru6gwtV4Mj90Kd4pCnLzYTx2V6S2PZNpK0dBrKfup9vYVd SzeBLUkd9UZjxAyB01erTi8M2tnuCDwPpuHabpcI4eJpSWHJrMrzPBeF/BWosg2KB87E /0/JZDXDbDO7HOggitn7Pcks1MXfKFgtuLJUtKnQ8pzTfDGgEY+TPECwUbHvMrPdekNJ yZMudxLB8ZYIcvGKf/eX9gKwh1w1fMvXipYAnxMSHoVmAJ0gb1A7tzGuVWBMPZ8vJ4nK Fkag==
X-Gm-Message-State: ALyK8tJLC8ikb5c9rNdXaGzM8O3U+ISqWpg5zC2cl3V6Cirz4awBAps8ZBl6xK95f6rzAQ==
X-Received: by 10.98.42.206 with SMTP id q197mr29137169pfq.108.1464555671323;  Sun, 29 May 2016 14:01:11 -0700 (PDT)
Received: from ?IPv6:2406:e007:5cae:1:292d:ccde:784:1cc4? ([2406:e007:5cae:1:292d:ccde:784:1cc4]) by smtp.gmail.com with ESMTPSA id d6sm42194864paw.30.2016.05.29.14.01.09 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2016 14:01:10 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-address-usage-recommendations-00.txt
References: <20160527233307.11106.7797.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: 6man <ipv6@ietf.org>
Message-ID: <17696295-c5b3-b7f7-fb20-f07da2030df2@gmail.com>
Date: Mon, 30 May 2016 09:01:06 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <20160527233307.11106.7797.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/E8q2HmGQDfNzA0vY38WrwbE-Pxs>
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, 29 May 2016 21:01:14 -0000

Hi,

> 
> 4.  Address Stability Considerations
...
>    Enforcing a maximum lifetime on IPv6 addresses may cause long-lived
>    TCP connections to fail.

That is only one example. Any scenario where a peer expects an address to
remain valid will fail. For example, any p2p application where some kind
of rendezvous or discovery process has occurred, such that the peers know
each other's addresses. Unstable addresses require significant complications
in such applications. The only good news is that mobility generally creates
the same problem, so many applications have already been fixed. (Related
problems were explored in 6renum, of course.)

> 6.  Advice on IPv6 Address Configuration
> 
>    [TBD]
> 
> 7.  Advice on IPv6 Address Usage
> 
>    [TBD]

I think we need to delete those sections. Stating the problem is about all we
can do today. Best, or least-bad, practice will emerge over a number of years.

   Brian


From nobody Sun May 29 16:18:05 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 5C74B127058 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 16:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 aXn_YuIBUtPr for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 16:18:01 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 9EC2412B01A for <6man@ietf.org>; Sun, 29 May 2016 16:18:01 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id c189so203717613vkb.1 for <6man@ietf.org>; Sun, 29 May 2016 16:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=vzz4srdMz41DMy6GII3cKjC5CYVUeUYykiVlVmzN+eU=; b=wstVm3e6tlWnMWQEObgOZxq3eF/nAM5M+tMh1vdzHmA7LtIJwNMBcsXYJ7It2MV/tt SUKZtv8nuJaF0MDYCCwMv53JtbVt+SExnZL80g5tKDX2ZbRBOrt+otC2J9b0LkymGSgL cXvbR8J93ZaDnD9Bt89FFnLpxZ6ul3I2U9hYFTFfs9WwvoiecejGoYbyUP6+2a7YK/mc C6qqicXKotc31pxM4ZnJP8qPZY+NPk1HPnEHpxY1Ukcl6clRgvgdfCWiSVLZI/6/buFz VOBqqgXg1+EsZsJQlco7sQOwllNh/QKumq2MmlPjcj80VMIc4SJpwzZPydr28ez/wx4T 38sg==
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:date :message-id:subject:from:to:cc; bh=vzz4srdMz41DMy6GII3cKjC5CYVUeUYykiVlVmzN+eU=; b=UaehZC66IIHRZX1DILo/rcRS5Tqf5CCQHlkM/GHear790szD+qWCP99pngmNYYhTw6 EcQzFTKEo3cN6ktkgCRM2hQLFEwC1agmOe1FPqvZT2whGIz6GRdKnlcIrCpYFhGaFuKA nnhJDAZR4MH7OySTYibREepyjs9h7XVXsUK91MRQTrDcM6oOuDakEqSDA+MlOhLuvfNI 2Y0dhKfPvaPa+8NxjIW/qGXkU5pEP2ixsPUb5qjfmoqg0ANdT/BdjpLZO3RnRh9BX4Dr 8PKjpdE8gsYPCETGvo0LayciUTHXUziG7FNJsztQb9IQ0n0j8XWrfabEup7KTAWIWk4b XEGQ==
X-Gm-Message-State: ALyK8tIurSpEpmuKD99VmnHMhjmlyhWHZzRIBfu1EzTY34hgTnbDi6yEzxYsijJE7z78M8q5D5/sCog7sC8kPQ==
MIME-Version: 1.0
X-Received: by 10.159.35.85 with SMTP id 79mr13751933uae.118.1464563880583; Sun, 29 May 2016 16:18:00 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 29 May 2016 16:18:00 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Sun, 29 May 2016 16:18:00 -0700 (PDT)
In-Reply-To: <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com>
Date: Mon, 30 May 2016 09:18:00 +1000
Message-ID: <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a113ad498da694f0534035953
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jnfVDqeYxred19I0I_8LgzPgQPg>
Cc: Fernando Gont <fgont@si6networks.com>, 6man@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: Sun, 29 May 2016 23:18:03 -0000

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

On 29 May 2016 21:00, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Sun, May 29, 2016 at 11:30 AM, Mark Smith <markzzzsmith@gmail.com>
wrote:
>>
>> > Most mobile devices close all TCP connections every time a network
disconnects, anyway.
>> My laptop running general purpose Linux doesn't. Servers don't.
>
> Your laptop doesn't do that, but perhaps it should.

Which is contrary to the robustness principle.

It would be smarter to test if the device reconnected to the same network
or not rather than assuming it is always a different network and tearing
down TCP sessions that will recover.

> The fact that it doesn't means that applications are forced to do it. For
example:
> Chrome has code that listens to netlink events and closes all sockets
when addresses change.
> It becomes impossible to use SSH with port forwarding across network
switches because the forwarded port is still mapped to a TCP connection
that will never come back because your IP address has changed.

Port forwarding is very useful sometimes, but it isn't a common thing to do
in the context of all the of users of all of these devices.

My example was moving between switches attached to the same subnet. Not a
common thing to occur either however an example of how hosts are robust
against transient network faults, including of the cable directly attached.

> So you have to configure TCP keepalives.
> ... and so on.
> You could argue that this should in fact be up to the application, but I
think it's reasonable for the system to do it. Many OSes do. For mobile
devices, it's a necessity.
>

See above about only doing it if the network has changed.

> As for servers, numbering them with EUI-64 or RFC7217 (which has the same
stability properties, i.e., the stable for the life of the network card)

Incorrect. See appendix A. If you think they are, then I don't think you've
not fully understood the problem that RFC7217s solve. They specifically
have decoupled the IID always relying on the NIC MAC address.

> seems silly compared to giving them static addresses.

I'd much rather 100 000 servers generate their own stable addresses that
have to generate 100 000 random numbers and then go and configure each
device with them.

> Actually, I don't expect that routers will need random MAC addresses.
>>
>> I think it depends on the type of router. Service provider or
corporate/enterprise router I'd agree.
>>
>> Residential router, I'd disagree, unless there are any significant
drawbacks.
>>
>> First thought is new random MACs on boot. The privacy enhancement would
be both periodically changing MAC addresses in WiFi SSID announcements, and
no disclosure of the router NIC manufacturer.
>>
>> I'll look to find time to do this on my residential router in the next
few weeks.
>
> Good luck getting an an IPv4 address after rebooting the router 3 times
in 5 minutes. Many ISPs only allow 1 or 2 IPv4 addresses per connection.

So there is another gotcha with randomising MAC addresses. (Years ago I
used MAC address randomisation to over come these sorts of blockages...)

I'm confident it is going to work for me though, as I used to be one of the
people on the other end.

Regards,
Mark.

--001a113ad498da694f0534035953
Content-Type: text/html; charset=UTF-8

<p dir="ltr"><br>
On 29 May 2016 21:00, &quot;Lorenzo Colitti&quot; &lt;<a href="mailto:lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sun, May 29, 2016 at 11:30 AM, Mark Smith &lt;<a href="mailto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; &gt; Most mobile devices close all TCP connections every time a network disconnects, anyway.<br>
&gt;&gt; My laptop running general purpose Linux doesn&#39;t. Servers don&#39;t.<br>
&gt;<br>
&gt; Your laptop doesn&#39;t do that, but perhaps it should.</p>
<p dir="ltr">Which is contrary to the robustness principle.</p>
<p dir="ltr">It would be smarter to test if the device reconnected to the same network or not rather than assuming it is always a different network and tearing down TCP sessions that will recover.</p>
<p dir="ltr">&gt; The fact that it doesn&#39;t means that applications are forced to do it. For example:<br>
&gt; Chrome has code that listens to netlink events and closes all sockets when addresses change.<br>
&gt; It becomes impossible to use SSH with port forwarding across network switches because the forwarded port is still mapped to a TCP connection that will never come back because your IP address has changed.</p>
<p dir="ltr">Port forwarding is very useful sometimes, but it isn&#39;t a common thing to do in the context of all the of users of all of these devices.</p>
<p dir="ltr">My example was moving between switches attached to the same subnet. Not a common thing to occur either however an example of how hosts are robust against transient network faults, including of the cable directly attached.</p>
<p dir="ltr">&gt; So you have to configure TCP keepalives.<br>
&gt; ... and so on.<br>
&gt; You could argue that this should in fact be up to the application, but I think it&#39;s reasonable for the system to do it. Many OSes do. For mobile devices, it&#39;s a necessity.<br>
&gt;</p>
<p dir="ltr">See above about only doing it if the network has changed.<br></p>
<p dir="ltr">&gt; As for servers, numbering them with EUI-64 or RFC7217 (which has the same stability properties, i.e., the stable for the life of the network card)</p>
<p dir="ltr">Incorrect. See appendix A. If you think they are, then I don&#39;t think you&#39;ve not fully understood the problem that RFC7217s solve. They specifically have decoupled the IID always relying on the NIC MAC address.</p>
<p dir="ltr">&gt; seems silly compared to giving them static addresses.</p>
<p dir="ltr">I&#39;d much rather 100 000 servers generate their own stable addresses that have to generate 100 000 random numbers and then go and configure each device with them.<br></p>
<p dir="ltr">&gt; Actually, I don&#39;t expect that routers will need random MAC addresses.<br>
&gt;&gt;<br>
&gt;&gt; I think it depends on the type of router. Service provider or corporate/enterprise router I&#39;d agree.<br>
&gt;&gt;<br>
&gt;&gt; Residential router, I&#39;d disagree, unless there are any significant drawbacks.<br>
&gt;&gt;<br>
&gt;&gt; First thought is new random MACs on boot. The privacy enhancement would be both periodically changing MAC addresses in WiFi SSID announcements, and no disclosure of the router NIC manufacturer.<br>
&gt;&gt;<br>
&gt;&gt; I&#39;ll look to find time to do this on my residential router in the next few weeks.<br>
&gt;<br>
&gt; Good luck getting an an IPv4 address after rebooting the router 3 times in 5 minutes. Many ISPs only allow 1 or 2 IPv4 addresses per connection.</p>
<p dir="ltr">So there is another gotcha with randomising MAC addresses. (Years ago I used MAC address randomisation to over come these sorts of blockages...)</p>
<p dir="ltr">I&#39;m confident it is going to work for me though, as I used to be one of the people on the other end.</p>
<p dir="ltr">Regards,<br>
Mark.</p>

--001a113ad498da694f0534035953--


From nobody Sun May 29 19:10:58 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 EF6D212B041 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 19:10:56 -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 JzoVWcwLwuzj for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 19:10:54 -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 DE35512B013 for <ipv6@ietf.org>; Sun, 29 May 2016 19:10:47 -0700 (PDT)
Received: from [192.168.1.101] (93-35-131-247.ip55.fastwebnet.it [93.35.131.247]) (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 58284800B4; Mon, 30 May 2016 04:10:37 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-address-usage-recommendations-00.txt
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
References: <20160527233307.11106.7797.idtracker@ietfa.amsl.com> <17696295-c5b3-b7f7-fb20-f07da2030df2@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <574BA0E5.6030901@si6networks.com>
Date: Sun, 29 May 2016 23:09:41 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <17696295-c5b3-b7f7-fb20-f07da2030df2@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sK_KmW8XcLSO0HFmv778HgrWj5c>
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, 30 May 2016 02:10:57 -0000

Hi, Brian,

Thanks for your feedback. Comments in-line...

On 05/29/2016 06:01 PM, Brian E Carpenter wrote:
>> 4.  Address Stability Considerations
> ...
>>    Enforcing a maximum lifetime on IPv6 addresses may cause long-lived
>>    TCP connections to fail.
> 
> That is only one example.

Exactly.


> Any scenario where a peer expects an address to
> remain valid will fail. For example, any p2p application where some kind
> of rendezvous or discovery process has occurred, such that the peers know
> each other's addresses. Unstable addresses require significant complications
> in such applications. 

Yes, that's why I wonder to what extent one can say "yes, feel free to
go ahead with temp addr only".



> The only good news is that mobility generally creates
> the same problem, so many applications have already been fixed. (Related
> problems were explored in 6renum, of course.)

Really? If the app doesn't have some concept of session or the like, how
would that happen?


>> 6.  Advice on IPv6 Address Configuration
>>
>>    [TBD]
>>
>> 7.  Advice on IPv6 Address Usage
>>
>>    [TBD]
> 
> I think we need to delete those sections. Stating the problem is about all we
> can do today. Best, or least-bad, practice will emerge over a number of years.

Fair enough. But... at the end of the day, nodes need to do *something*
so... what'd be the advice for them?

P.S.: If we remove Sections 6 and 7, the track should be changed to
"info", I guess.

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





From nobody Sun May 29 19:48:30 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 EE96712B015 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 19:48: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, 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 G55K-gW2JbAG for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 19:48:27 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::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 4FD7E12B013 for <ipv6@ietf.org>; Sun, 29 May 2016 19:48:27 -0700 (PDT)
Received: by mail-pa0-x229.google.com with SMTP id um11so5117401pab.0 for <ipv6@ietf.org>; Sun, 29 May 2016 19:48:27 -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=SwvJ1jkcGTg4ZW4xHexE+vP5ZyvAJAIif2pAUr2+bzM=; b=btKtwhMgXYHCdu2+US4tJdv6FFMGLtcZv/EnCuYwiYUNchVvlkh9P/7MaXPSHHlP8+ GO4ylnxYvLcIPC8hyL3CJvN0dtScf1qAqVfJG41m2UZfCa1GJfHNGAIUVafikdESiyFt y+lIXTJZb4jyjIJMCdPJe42U1FP9o1XrvcJh4NiVvkWQ1clUxX1jfITAX2GyHFUkulAk f4xRuVtLcsRvLo76xmSzjBsgXX3jguuIgL21jqRIKYYE5v7YKA/u5WE+uZlAQ+PF7WGW KCWmG5sHSd4iIWcmJF65pCMDKt4HDELk/LJs8UHpiLe4tvYgl0ogi1s42+ASonUbIWXr CBFA==
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=SwvJ1jkcGTg4ZW4xHexE+vP5ZyvAJAIif2pAUr2+bzM=; b=YF0OXQioSYFFz+wJEPdbjtvlXmOdXIuR9KANfk7YcuvK6QUyzZeqmfd5wQysud8j+A 96yrjpFbABgZVsw3GJTmBPMP6ErgGGMD0k5RZn0n2xvGMvpIwtov2AzuUTPioEFUqrpP dupWU+kCKGd3vCablVgjzhIzzEuEQJAAD9nII1s92EPYiNhMRCXYJ8YpHugkZHbhyyKY Ucm8TzK4kjlWi3ZjQyfyiej1IbUahm5zMhyNgTSsMFCV1dpLiU4yJFPI6lWKX5DjygML 2dWUO2iav+6Wxpj7CquWV367JCQv6Y559XuWaQWBOrMKSTtAyeMIb32n56ZvuJxhTHS2 YnsQ==
X-Gm-Message-State: ALyK8tKeJmX3TMDHsqphRbmlzJnEZdSiLWzzhB2GcmtQl6ZNHSSGvu9YDssyRfolYLYNTg==
X-Received: by 10.66.127.10 with SMTP id nc10mr42159028pab.98.1464576506745; Sun, 29 May 2016 19:48:26 -0700 (PDT)
Received: from ?IPv6:2406:e007:5cae:1:2046:1755:e1a:9646? ([2406:e007:5cae:1:2046:1755:e1a:9646]) by smtp.gmail.com with ESMTPSA id s8sm42971776pav.39.2016.05.29.19.48.24 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 May 2016 19:48:25 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-address-usage-recommendations-00.txt
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
References: <20160527233307.11106.7797.idtracker@ietfa.amsl.com> <17696295-c5b3-b7f7-fb20-f07da2030df2@gmail.com> <574BA0E5.6030901@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1615c1df-3e39-ccbf-9406-a01eb18f9243@gmail.com>
Date: Mon, 30 May 2016 14:48:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <574BA0E5.6030901@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jZia4VWmXU_CtJOXNHRKnbJsoqU>
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, 30 May 2016 02:48:29 -0000

On 30/05/2016 14:09, Fernando Gont wrote:
> Hi, Brian,
> 
> Thanks for your feedback. Comments in-line...
> 
> On 05/29/2016 06:01 PM, Brian E Carpenter wrote:
>>> 4.  Address Stability Considerations
>> ...
>>>    Enforcing a maximum lifetime on IPv6 addresses may cause long-lived
>>>    TCP connections to fail.
>>
>> That is only one example.
> 
> Exactly.
> 
> 
>> Any scenario where a peer expects an address to
>> remain valid will fail. For example, any p2p application where some kind
>> of rendezvous or discovery process has occurred, such that the peers know
>> each other's addresses. Unstable addresses require significant complications
>> in such applications. 
> 
> Yes, that's why I wonder to what extent one can say "yes, feel free to
> go ahead with temp addr only".
> 
> 
> 
>> The only good news is that mobility generally creates
>> the same problem, so many applications have already been fixed. (Related
>> problems were explored in 6renum, of course.)
> 
> Really? If the app doesn't have some concept of session or the like, how
> would that happen?

Yes, either a session (think Skype, or RTP traffic) or some kind of
intrinsic keep-alive check. There is quite a lot of such traffic, I think.

    Brian

> 
> 
>>> 6.  Advice on IPv6 Address Configuration
>>>
>>>    [TBD]
>>>
>>> 7.  Advice on IPv6 Address Usage
>>>
>>>    [TBD]
>>
>> I think we need to delete those sections. Stating the problem is about all we
>> can do today. Best, or least-bad, practice will emerge over a number of years.
> 
> Fair enough. But... at the end of the day, nodes need to do *something*
> so... what'd be the advice for them?
> 
> P.S.: If we remove Sections 6 and 7, the track should be changed to
> "info", I guess.
> 
> THanks,
> 


From nobody Sun May 29 23:40: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 2C79912B02C for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 23:40: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 LCR7_xbM2KEc for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 23:40: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 0C0B012B009 for <ipv6@ietf.org>; Sun, 29 May 2016 23:40:12 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2016 06:40:11 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 616409CC51; Sun, 29 May 2016 23:40:10 -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=hCospkH/HfV2Yw/w+fx6cKA8Tzs=; b= cst9K4A7s7xfGYowwZgl1FgWf0cx7gF0u1uU6vZdm1M3A6FfI92UV/OQUol+5G1P SsLpgBSj4iiA/JKAV1vi2lHO4oX74ubMfpxUqMSoxseXKuHM0TFK/v+nl+ELde6C pyWGK2qN9DyTwFzDOB6qMNAIBMZXo3Y6zshossEFOVU=
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=Lz7caB567k2JG8ynJ/3WPQHcto iK7mXaEKj9cW1QyR4+DW0zpABn0osxZTWisdIjdsAPwGGQULlBNqBuzaJWZMcxdZ ilBjjYjBjntfNY1jGJAvuQ233q9ivwEFHip6Hy1N/WjQMD0hkcGQS2zVPqu37yQ/ 5XlUmegiJ/jEL4Sn4=
Received: from h.hanazo.no (2.150.35.187.tmi.telenormobil.no [2.150.35.187]) (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 1D4B99CC4F; Sun, 29 May 2016 23:40:10 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C5C1A174018A; Mon, 30 May 2016 08:40:00 +0200 (CEST)
Subject: Re: default-iids: Closing concern regarding stable address requirement
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_BB68487C-532A-4504-BC5B-C816A94C5595"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com>
Date: Mon, 30 May 2016 08:39:56 +0200
Message-Id: <DF433684-2F5C-4DB1-82CF-A99975A77F8C@employees.org>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com> <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com> <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com> <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/F_l0Q_Q0EAvBT5jpgJr1cvFeLsQ>
Cc: 6man WG <ipv6@ietf.org>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Mon, 30 May 2016 06:40:19 -0000

--Apple-Mail=_BB68487C-532A-4504-BC5B-C816A94C5595
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> Or use hostid because devices may have multiple interfaces anyway
>=20
> So, I just don't see how we can claim to dictate any kind of general =
default
> or BCP in this area. But I don't seee that =
draft-ietf-6man-default-iids does
> that. Maybe it should be toned down to a SHOULD level, e.g.
>=20
> Abstract
>=20
>   This document changes the recommended scheme for generating stable
>   Interface Identifiers with SLAAC to that specified in RFC7217, and
>   recommends against embedding 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 accordingly.
>=20
> and similar changes in the body of the draft.
>=20
> Again, the 'bug' in 4941 is a separate issue.

agree, I think there is agreement that the default generation mechanism =
for stable addresses should be 7217.

cheers,
Ole

--Apple-Mail=_BB68487C-532A-4504-BC5B-C816A94C5595
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

iQEcBAEBCgAGBQJXS+BAAAoJED4aXnjSQuKWGv8H/2GKoKAxLzp+B/nwkj7BoEly
ykqLaOCzZ6/WTtVe4hysbvXVWJHaDKhRDA0rk4NaSdVeBRjcKRloQYcTZb/ak4bc
YGGh6ChMbwtXwESBi95e5GeWuZggFACPv3KkZC4RnDNrbOPUA8ot/5P+oIwcGSqw
ttGy8wlrlD8BUz4BVvqRwaQoX1NMaIvT0F9gFbzmW5hDmttzYTS841L7rYcaTyCS
p4x4iGixme8hCfgQ77gvGl6kryOrknHQ7qU7kR69YsLJo4QhLRiovSP6oSj4D6AL
pGTkMN/f7X2psQahMTRcH5jwTJ4Qr4lYhZ5X9j/cEJ72kAqetQOrzyFYSXw19kc=
=CweI
-----END PGP SIGNATURE-----

--Apple-Mail=_BB68487C-532A-4504-BC5B-C816A94C5595--


From nobody Sun May 29 23:58:56 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 14D4212D0F2 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 23:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 SSuRQ6OfsPV0 for <ipv6@ietfa.amsl.com>; Sun, 29 May 2016 23:58:53 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::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 2D68312D0C2 for <ipv6@ietf.org>; Sun, 29 May 2016 23:58:52 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id x189so155590446ywe.3 for <ipv6@ietf.org>; Sun, 29 May 2016 23:58:52 -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=BIuRALD9r76KVmav4PF7wDKE72ofbPtDAblhIaf4b0M=; b=NEIeXyaZge8AaVvbMcQz2jcnrQCmtsSTPh//8/PLGR64W7r4+8Fl5dG66rlAbDIAF2 Sb8Jwbz10ILG91b1r28C2G7WZw9iM64abfxTEf6q+l51DrTWU54F7SBHoELpT/RX8YGv VkWe7GpRiJ5HQvQtBYVzBa8QkQVV2ThFYdNpFVXv3cZu0o/e2HkyDIZhRuFtHPGr6a+g sJ6/LJH3YHdlQjEr5A/RObQjWcfAhyzohlzNKlB4O+rgDk1YuyulqMSBahj5CrVFViAk Zt1r+FkjJDFuAo1eiS4qFl1gfoqxL1vKJVuWw1q1bWFC0p+YJzspqAI/ugCSX/hAztE9 sMgg==
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=BIuRALD9r76KVmav4PF7wDKE72ofbPtDAblhIaf4b0M=; b=UV++4CYxTXyna8LqN97Z/6QrRfY/6qIy/JfcjHqhPlEW7jxr+o/wN9IRXpllGQuYuj 3dsXISuJR4dlyOdQ+uz4BJ8F9GVm/WeM6o6ZK+CWjOvl6tU0kOJcRwYR4WSZ8sBwkU11 BxC2cvFItcEHRMrrNlswdwfozeMh+qRqF8t6JTKqSz85mkyEQd1AyEUIKduvSmRg1Vg9 G9gwF1omCagXUONX+3QxpnMvXkZ5YbFKJ4+SGxBoMcuqz9CvVqBW5aVK8V7wM5tKchxg VlYkztiFZCe4U/vz4pjw+mLjnFMVmXnIWE778jUcagWFpL8pr/2TsRy3aykEJ8C4ajw8 e+Ng==
X-Gm-Message-State: ALyK8tIsPo736b8SFa7e1wDfo9QwZ8ydgF6tqkfGtKIpx6tzUAxokooH1xPBETVQ/dEVqAy3hiD8Db6e4DRSEBkS
X-Received: by 10.13.220.69 with SMTP id f66mr18156315ywe.132.1464591532026; Sun, 29 May 2016 23:58:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Sun, 29 May 2016 23:58:31 -0700 (PDT)
In-Reply-To: <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com>
References: <5742118B.6020308@si6networks.com> <CAKD1Yr1LVf3j2UOZu=Jpu8tm+4wO=Pi2izqhuKWXHvrLj89RGA@mail.gmail.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com> <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com> <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com> <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 30 May 2016 15:58:31 +0900
Message-ID: <CAKD1Yr0BKNOj82FmNPF-fpoHhFBaidai9ZHPfZShwdJbQH41_Q@mail.gmail.com>
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0815c8026a09053409ca13
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qsOy5nEBb64lU6t3BOwmGJHBXU0>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Mon, 30 May 2016 06:58:55 -0000

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

On Mon, May 30, 2016 at 5:18 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> So, I just don't see how we can claim to dictate any kind of general
> default
> or BCP in this area. But I don't seee that draft-ietf-6man-default-iids
> does
> that. Maybe it should be toned down to a SHOULD level, e.g.
>
> Abstract
>
>    This document changes the recommended scheme for generating stable
>    Interface Identifiers with SLAAC to that specified in RFC7217, and
>    recommends against embedding link-layer addresses in IPv6 Interface
>    Identifiers.  It formally updates RFC2464, [...]


If this document makes RFC7217 IIDs a SHOULD, how should it formally update
the IPv6-over-foo RFCs? Currently it just blasts away any/all text in them
that talks about IIDs. If it's just a SHOULD, then it can't do that any
more.

--94eb2c0815c8026a09053409ca13
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 M=
on, May 30, 2016 at 5:18 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpente=
r@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><d=
iv><span style=3D"color:rgb(34,34,34)">So, I just don&#39;t see how we can =
claim to dictate any kind of general default</span><br></div></div>
or BCP in this area. But I don&#39;t seee that draft-ietf-6man-default-iids=
 does<br>
that. Maybe it should be toned down to a SHOULD level, e.g.<br>
<br>
Abstract<br>
<br>
=C2=A0 =C2=A0This document changes the recommended scheme for generating st=
able<br>
=C2=A0 =C2=A0Interface Identifiers with SLAAC to that specified in RFC7217,=
 and<br>
=C2=A0 =C2=A0recommends against embedding link-layer addresses in IPv6 Inte=
rface<br>
=C2=A0 =C2=A0Identifiers.=C2=A0 It formally updates RFC2464, [...]</blockqu=
ote><div><br></div><div>If this document makes RFC7217 IIDs a SHOULD, how s=
hould it formally update the IPv6-over-foo RFCs? Currently it just blasts a=
way any/all text in them that talks about IIDs. If it&#39;s just a SHOULD, =
then it can&#39;t do that any more.</div></div></div></div>

--94eb2c0815c8026a09053409ca13--


From nobody Mon May 30 00:00: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 B76A812D0D3 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:00: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 XrWHn1EdpdvA for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:00: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 6AF9712B04E for <ipv6@ietf.org>; Mon, 30 May 2016 00:00:45 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2016 07:00:44 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 611DF9CC4F; Mon, 30 May 2016 00:00:43 -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=/sMlpcBrEtP4hXkc/Kaka77iQME=; b= Sg7id8PutCSJEth962gc+o2g5N+QGL/eckCmU2oy/5SVJs/V30MwCgGadgnpVSkR DCLQ90e5toMQ2tF7e+1mPD/ER+qoX4cNjJ1LnUUBZkFdPS8u+PPV0BpwlxUfm+nh 5iw9gP/uL+vdf/GNzpGZKKg4ahabWszXeSFkDacrZZ4=
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=a8FzrjoUNR93ivg5omnpMVIz77 f9dqaJHmSuqtqTLGKI7Vsvf9HgvgpoCcUS7z2rA1BK/PE+QQ7uvbWwROs4yGbxUp SDKjeGrm1+iTa1e/lD5LPwwd0vfJyZMimTXpL826PontlmVzpoGd2E71MqmNAxtQ oNVbX76Kc1Y4ZTREU=
Received: from h.hanazo.no (2.150.35.187.tmi.telenormobil.no [2.150.35.187]) (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 150399CC4E; Mon, 30 May 2016 00:00:43 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id E08D61740656; Mon, 30 May 2016 09:00:39 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_82A77E2E-0FBD-4B12-8DA0-9341CFDC2BDE"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com>
Date: Mon, 30 May 2016 09:00:36 +0200
Message-Id: <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/IzHMj0rw5aHv8q7TSUEuM_7GNZE>
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, 30 May 2016 07:00:47 -0000

--Apple-Mail=_82A77E2E-0FBD-4B12-8DA0-9341CFDC2BDE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> 3. Update to RFC4941
>=20
>   The temporary addresses specified in [RFC4941] MAY be used alone,
>   without configuring any stable addresses. In particular the word
>   'additional' is deleted from bullet 2 in Section 3 of RFC 4941.

do we agree that the privacy of a given address is compromised as soon =
as it is used in a way that identifies the user?

that would imply that any address used to reach facebook, google, etc is =
tainted and cannot be used for any other connection.

pretty much all my devices have umbilical cords back to the "cloud" for =
applications, software updates, management, data dumping etc. those =
cords are also connected to an identity.

I'd argue that there are no deployed hosts / application combinations =
that can only use privacy addresses
(they might use privacy addresses as short lived stable addresses, but =
in that case they would be better off with stable addresses).

if the consequence of this is that a temporary address can only be used =
within a single connection, then I can guarantee you that there will be =
many networks that will not support that. bridges do not have unlimited =
space.

cheers,
Ole





--Apple-Mail=_82A77E2E-0FBD-4B12-8DA0-9341CFDC2BDE
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

iQEcBAEBCgAGBQJXS+UXAAoJED4aXnjSQuKWW2MH/0Y9LoHdvCw9NkWO5Zqz0ZLy
fGMoVexDJC13F1gINNY8fBTJX5QI6qDmPBcRx+CdaXfVcasp9Zn5RrqVwyrdWba9
X+rfVg3o8t5CuxTPJyaSI/uKjE0fA9nND2uJF9+dR6Ocm+CKtZhS3JHKz8xN2kPE
OVtrv7Bhn/PBExTM8H5g9DcfrbmWnrgtoffHoVw8OYJ6Uv4cfzIHBTc90pHBH+SA
T18wbgHaI7DH7rmaFn8f4/df5Vn4w5KC73UEf1+bFp99OEu1+ya6RRtT3wqfmK1v
M64hJidLhj2f19MmIMV1dhRaAs+QRSwVoBJrQtg+Q+Gi3OWD5X/BsLWxFXX0stI=
=ZlWm
-----END PGP SIGNATURE-----

--Apple-Mail=_82A77E2E-0FBD-4B12-8DA0-9341CFDC2BDE--


From nobody Mon May 30 00:13:22 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 6F26F12D165 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 nbtW6BIC2-yU for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:13:18 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 7F5A812D144 for <ipv6@ietf.org>; Mon, 30 May 2016 00:13:18 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id o16so155994406ywd.2 for <ipv6@ietf.org>; Mon, 30 May 2016 00:13: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=G54MKRGKMJ0A54HbKQqbrGOxY3YgSwSRWqtuqaFkYSo=; b=PhngxcDyympP5eBNdydnc6SDuLeEBN2JH2W67T2K63f0F4oCP51vKTHNofE2oRStw3 jcpPsSCJg6gZ5TBLP5/2I39lGXchQTUQzva0jwfa6IvgAflmm4ny2Qwa2TWkQtnhB4U4 AMbDg7BQTIIcAdxZPRQ7Ty17cYKvLqzFJOIfa6RQP7/9LNXpWHw41gC8i2z61pzirSJN UCuAEC+XProy79X4m/576AwNUrQ6JUL3ptRvheRhuuAwkuRm8+sPoi0LypXFxeCsNd8d YPp26YxbvKw+T/MT48VK40eoeViasn06DIyoqOU4GiWSe55MEdljmaQQSb9nEYMM8oc6 wgsg==
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=G54MKRGKMJ0A54HbKQqbrGOxY3YgSwSRWqtuqaFkYSo=; b=F4YXpyeiX12y5FdK23mXuUiIs2P72diC5F2QtAiJkyUsbeIkORMfh/Ay93uFQD+3VL 9LHQbjAk3pSOOfCX4X5I4/1zOd0i5sEWV56cXFwhR0AWdZwMXEFnyQbw4256g+7IKJe2 DVVBSseFuXlqvKXhzb1Oz1fRAQK87dqZzClQ3N8JX7i3nWsSNpsAnyzJPjYZ4LM1pTfp WRt0xrpoq4T0oZEscvv3QdsZgqmP09t/0chovtfTisglvPzBWH294v9MJFY+LRBwI3Zk v5X5qrCUs3nmIapOty/TtuV4z7t56NgTBP0oyT2Xdh/H0yMnq/dSPDfTPcZiE90Xiu2j 2wkg==
X-Gm-Message-State: ALyK8tJKsFawKDirpD3EI4tQehNl5Lq/34WHBAE5qtOUobmenYsRdtZrM6QpBHlLrNskDcNTQ69QQZYsxICqRn8o
X-Received: by 10.129.108.211 with SMTP id h202mr17247204ywc.229.1464592397566;  Mon, 30 May 2016 00:13:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Mon, 30 May 2016 00:12:57 -0700 (PDT)
In-Reply-To: <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 30 May 2016 16:12:57 +0900
Message-ID: <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114da746997c0b053409fd3a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/aeG6aN8w-W_YV6J_-imj-deBzVk>
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, 30 May 2016 07:13:20 -0000

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

On Mon, May 30, 2016 at 4:00 PM, <otroan@employees.org> wrote:

> >   The temporary addresses specified in [RFC4941] MAY be used alone,
> >   without configuring any stable addresses. In particular the word
> >   'additional' is deleted from bullet 2 in Section 3 of RFC 4941.
>
> do we agree that the privacy of a given address is compromised as soon as
> it is used in a way that identifies the user?
>

In some sense, maybe, but...


> that would imply that any address used to reach facebook, google, etc is
> tainted and cannot be used for any other connection.
>

... privacy is not binary. An identifier is valid for 1 day poses much less
risk than one that is permanent for the life of the device. A party that
has *realtime* access to $COMPANY's webserver logs can track visitors to
$COMPANY's webservers all the time. But if you uninstall the $COMPANY app
and don't use $COMPANY's website for 1 day, that party cannot track you any
more via those means.


> I'd argue that there are no deployed hosts / application combinations that
> can only use privacy addresses


Privacy addresses as defined by RFC4941? Perhaps not today, but it's not
hard to change that.


> if the consequence of this is that a temporary address can only be used
> within a single connection, then I can guarantee you that there will be
> many networks that will not support that. bridges do not have unlimited
> space.


But some can. 3GPP mobile networks and
draft-ietf-v6ops-unique-ipv6-prefix-per-host networks, need not be limited.
Residential networks aren't limited but they might have space for thousands
of ND cache entries, so thousands of addresses.

--001a114da746997c0b053409fd3a
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 M=
on, May 30, 2016 at 4:00 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otroa=
n@employees.org">otroan@employees.org</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex"><span class=3D"gmail-">&gt;=C2=A0 =C2=A0The temporary addresses specif=
ied in [RFC4941] MAY be used alone,<br>
&gt;=C2=A0 =C2=A0without configuring any stable addresses. In particular th=
e word<br>
&gt;=C2=A0 =C2=A0&#39;additional&#39; is deleted from bullet 2 in Section 3=
 of RFC 4941.<br>
<br>
</span>do we agree that the privacy of a given address is compromised as so=
on as it is used in a way that identifies the user?<br></blockquote><div><b=
r></div><div>In some sense, maybe, but...</div><div>=C2=A0</div><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">that would imply that any address used to reach facebook, google, etc=
 is tainted and cannot be used for any other connection.<br></blockquote><d=
iv><br></div><div>... privacy is not binary. An identifier is valid for 1 d=
ay poses much less risk than one that is permanent for the life of the devi=
ce. A party that has *realtime* access to $COMPANY&#39;s webserver logs can=
 track visitors to $COMPANY&#39;s webservers all the time. But if you unins=
tall the $COMPANY app and don&#39;t use $COMPANY&#39;s website for 1 day, t=
hat party cannot track you any more via those means.</div><div>=C2=A0</div>=
<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);p=
adding-left:1ex">I&#39;d argue that there are no deployed hosts / applicati=
on combinations that can only use privacy addresses</blockquote><div><br></=
div><div>Privacy addresses as defined by RFC4941? Perhaps not today, but it=
&#39;s not hard to change that.=C2=A0<br></div><div>=C2=A0</div><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">if the consequence of this is that a temporary address can only be us=
ed within a single connection, then I can guarantee you that there will be =
many networks that will not support that. bridges do not have unlimited spa=
ce.</blockquote><div><br></div><div>But some can. 3GPP mobile networks and =
draft-ietf-v6ops-unique-ipv6-prefix-per-host networks, need not be limited.=
 Residential networks aren&#39;t limited but they might have space for thou=
sands of ND cache entries, so thousands of addresses.</div></div></div></di=
v>

--001a114da746997c0b053409fd3a--


From nobody Mon May 30 00:32: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 90F4D12D144 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:32: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 JUyb0GdOMO-D for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 00:32:43 -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 8D0EF12D0CE for <ipv6@ietf.org>; Mon, 30 May 2016 00:32:42 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport02.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 May 2016 07:32:41 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B8CBB9CC4F; Mon, 30 May 2016 00:32:39 -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=biFYIdh2L2fCJc4GuW8hoqgrZv8=; b= pch3r37Os6u3a9DME+Ga48FNePeSuecK1k6QnZFQnaIWcGIZKpiYj9qoRaT4CS4n uEJEmo4JfxaXqbIX9vbTazYI2C7/a6uKkrjjlh4Z69VpZdqEJhTlbsEggJlVxNgQ hw+nT0r9WNrAhgOFwXa9j/b3mXy/6eWDSBfOU8KtZ+8=
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=oPqXzHxqi7WMGmo4bD7BtewvAc lHv5c+QLO+vHjfrKUAa1g8gg1mUCDsEvcu3hIVfUi+mSzcx60KrcZUUWnddFyRNG 9n+B93j8sQLJ74dvqYvNv1UyXS6EbOE8+nfo11ekOUY8AMxT6N6LSm1vKB0Zfg1h vKyJl8rAa8EAm1Da4=
Received: from h.hanazo.no (2.150.35.187.tmi.telenormobil.no [2.150.35.187]) (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 703369CC4E; Mon, 30 May 2016 00:32:39 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 934361740FFC; Mon, 30 May 2016 09:32:36 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C9488C1B-B625-4466-A644-63170BFD426E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com>
Date: Mon, 30 May 2016 09:32:33 +0200
Message-Id: <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LduwKF8CfOkmiYByA7bFu5hnovM>
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, 30 May 2016 07:32:45 -0000

--Apple-Mail=_C9488C1B-B625-4466-A644-63170BFD426E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lorenzo,

> that would imply that any address used to reach facebook, google, etc =
is tainted and cannot be used for any other connection.
>=20
> ... privacy is not binary. An identifier is valid for 1 day poses much =
less risk than one that is permanent for the life of the device. A party =
that has *realtime* access to $COMPANY's webserver logs can track =
visitors to $COMPANY's webservers all the time. But if you uninstall the =
$COMPANY app and don't use $COMPANY's website for 1 day, that party =
cannot track you any more via those means.
>=20
> I'd argue that there are no deployed hosts / application combinations =
that can only use privacy addresses
>=20
> Privacy addresses as defined by RFC4941? Perhaps not today, but it's =
not hard to change that.

give me a functioning host that has no umbilical cord somewhere that =
leaks identity...

> if the consequence of this is that a temporary address can only be =
used within a single connection, then I can guarantee you that there =
will be many networks that will not support that. bridges do not have =
unlimited space.
>=20
> But some can. 3GPP mobile networks and =
draft-ietf-v6ops-unique-ipv6-prefix-per-host networks, need not be =
limited. Residential networks aren't limited but they might have space =
for thousands of ND cache entries, so thousands of addresses.

in 3GPP networks the subscriber is identified by the first 64 bits =
anyway.
there is no standardised way for a host to know if it is getting a =
unique /64 is it?
we're currently lacking a mechanism for the network to inform hosts that =
they aren't getting any addresses.

and I'm sure we can argue over the privacy properties of unique /64 per =
host.

cheers,
Ole

--Apple-Mail=_C9488C1B-B625-4466-A644-63170BFD426E
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

iQEcBAEBCgAGBQJXS+yUAAoJED4aXnjSQuKWd/AIAIdE7EXXPdJm7pKtobh16kk0
VjETDfFdo/Cgtd6k+wq/0hAlM3qZ9CHEualPpVf33Mr76zhlO/OV1ZffLneczi3h
VKAosOxujJYgnLpeZiD414/0CFSzRr8JDB1KZJA3vODI+7iI8KLcdThf3qgzCh67
V9ZCN/GbaTNo+i7Z8nDmgAn0qbWGJ73ImBY+rL5Wfu4uvyzlccvGUQC9fDGpseul
uXGYbThH6RcM2oksqfBtrDsPShQ4bk8u1sK2Y0CkQTVDUojLbaNvcuw7HU3V602/
kA0Zvz25TUHpQpIeT0lZXTqIBmCJM5LvWDqsNQtw9LmyZW5OMX7Dh7Bn2JQxp3E=
=71uJ
-----END PGP SIGNATURE-----

--Apple-Mail=_C9488C1B-B625-4466-A644-63170BFD426E--


From nobody Mon May 30 01:15:38 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 54E6F12D191 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 01:15:37 -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 zK9MeC6tiZvd for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 01:15:35 -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 3B64112B027 for <ipv6@ietf.org>; Mon, 30 May 2016 01:15:35 -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; 30 May 2016 08:15:34 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 2BBB39CC51; Mon, 30 May 2016 01:15:33 -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=aEO+me47vs6SAIEcm1+bt1ECw+k=; b=qBL8uiITjEBcxK3CwD QRaBF/dYppAXW9UgnWOSiWNMwaZwm1eBaaD4CVRaPxf7byd5G2+6aXm7oKTG0M1J FqDiigSvQTWBWroClfwhvP0Anh4Ks49dZ3gfXQifIAPkbNsU05XLyCdoJY7tgUTK 22cH7wIdUDbVqpGcB6uFZeKwI=
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=lHtzZPBg6l9MOy2BHQR5Q5c7uwDmHQcaVe3oZlEI8GFeitbl ED04n1YDI/hjj//u7bHNmzLk9TP5YqjuNg2mqTiw+NLj0SAnXaWiBGRt4oNJhbi6 joHoVBsRrsBSPxjohGA9Qw3CRf3iVz9FPqiTMBHofvfgOnXP60O5PjiMsOk=
Received: from h.hanazo.no (2.150.35.187.tmi.telenormobil.no [2.150.35.187]) (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 585F89CC4E; Mon, 30 May 2016 01:15:32 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 6F1521742082; Mon, 30 May 2016 10:15:29 +0200 (CEST)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_40A517A8-DB26-46B7-91CE-76CB7F33D3DA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN: Working group last call on RFC2460bis, RFC1981bis and RFC4291bis
Date: Mon, 30 May 2016 10:15:26 +0200
Message-Id: <C03A16B7-7202-49CC-A944-9DE947BFB198@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: <http://mailarchive.ietf.org/arch/msg/ipv6/F9DeAe3pLh5vHIc6kxwTTkX5owo>
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: Mon, 30 May 2016 08:15:37 -0000

--Apple-Mail=_40A517A8-DB26-46B7-91CE-76CB7F33D3DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This message starts a two week 6MAN Working Group Last Call on =
advancing:


Name:	draft-ietf-6man-rfc2460bis
Title:	Internet Protocol, Version 6 (IPv6) Specification
Authors:     S. Deering, R. Hinden
Date:	     2016-03-21
Pages:	     37
Htmlized:    https://tools.ietf.org/html/draft-ietf-6man-rfc2460bis-04

Name:	draft-ietf-6man-rfc1981bis
Title:	Path MTU Discovery for IP version 6
Authors:     J. McCann, S. Deering, J. Mogul, R. Hinden
Date:	     2016-04-27
Pages:	17
Htmlized:    https://tools.ietf.org/html/draft-ietf-6man-rfc1981bis-02

Name        : draft-ietf-6man-rfc4291bis-02
Title       : IP Version 6 Addressing Architecture
Authors     : Robert M. Hinden, Stephen E. Deering
Pages       : 30
Date        : 2016-04-27
Htmlized:   https://tools.ietf.org/html/draft-ietf-6man-rfc4291bis-02

as Internet Standards. Substantive comments and statements of support
for publishing these document should be directed to the mailing
list. Editorial suggestions can be sent to the editor.

This document is part of the core set of IPv6 standards that will be
advanced to Internet Standard. As part of that work, thorough review
of all the changes from draft standard documents are required. It is
important to verify that these changes do not create inconsistencies
with the rest of the document. All changes should follow the
guidelines set out in RFC6410:

  (1) There are at least two independent interoperating implementations
      with widespread deployment and successful operational experience.
  (2) There are no errata against the specification that would cause a
      new implementation to fail to interoperate with deployed ones.
  (3) There are no unused features in the specification that greatly
      increase implementation complexity.
  (4) If the technology required to implement the specification
      requires patented or otherwise controlled technology, then the
      set of implementations must demonstrate at least two independent,
      separate and successful uses of the licensing process.

All changes are enumerated in appendixes. The complete change-sets are
available at:
=
https://www.ietf.org/rfcdiff?url1=3Ddraft-hinden-6man-rfc2460bis-00&url2=3D=
draft-ietf-6man-rfc2460bis-04
=
https://www.ietf.org/rfcdiff?url1=3Ddraft-hinden-6man-rfc4291bis-00&url2=3D=
draft-ietf-6man-rfc4291bis-02
=
https://www.ietf.org/rfcdiff?url1=3Ddraft-hinden-6man-rfc1981bis-00&url2=3D=
draft-ietf-6man-rfc1981bis-02

We will track open issues using the 6MAN issue tracker available at:
https://trac.tools.ietf.org/wg/6man/trac/report

The document shepherd for this document is Ole Tr=C3=B8an. We need at =
least
two volunteer document reviewers who can review every change in detail
in all three documents.

This last call will end on June 13th, 2016.

Best regards,
Ole


--Apple-Mail=_40A517A8-DB26-46B7-91CE-76CB7F33D3DA
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

iQEcBAEBCgAGBQJXS/ahAAoJED4aXnjSQuKWhd4H/2F4arnRQpfvg3VDwPVFaAL0
MlN2bX0RVFYGcHhck83FrTtdE8PLgLtm7A+SbGc0rUKaDD7EWEPO0wq7dvoe2i+s
cIhvWimDql6vP3d3XUVPLwmsypZazN4+SkojJz7mMlqytz0lHRSZpdFGWKff8P3o
QjtcEo2oSwu5uCp7+BpK48vFOUXzVLCag4nfBUmwXinoPfMe696jIkYt3ul1hOhk
9zPDyjpPa6KwWunyvRUZAcYO1TsmNLGm1es29OGzoGw3DDBzbxciWL7ezQVcGKej
kYsTD4Y44AzHNQ28JsZm9OSjN96mLQVsYGS9Ox8vA2TOUE9gVod4OeZ5Qx/8Mt8=
=6qcG
-----END PGP SIGNATURE-----

--Apple-Mail=_40A517A8-DB26-46B7-91CE-76CB7F33D3DA--


From nobody Mon May 30 16:55:53 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 482D212D6A4 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 16:55:52 -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 WeHBhHZl3r6y for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 16:55:50 -0700 (PDT)
Received: from mail-pf0-x22e.google.com (mail-pf0-x22e.google.com [IPv6:2607:f8b0:400e:c00::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 79F0412D55D for <ipv6@ietf.org>; Mon, 30 May 2016 16:55:50 -0700 (PDT)
Received: by mail-pf0-x22e.google.com with SMTP id f144so55400500pfa.3 for <ipv6@ietf.org>; Mon, 30 May 2016 16:55:50 -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=VBZCJN3+QKlDUBkcK/C4Onu4AO7x2DbRq/XDvbOdlqE=; b=DkbiYhMLzUw2ZH1EkqTK080uYeY35reW0/med0awjynnVeQeTF1mwRMCPAAcfPINxQ oN8kPIbqdPjs2ytYZ0Wh6EQTbXS0Sn/AJYadJGMjeY76lMK+OBgubsCghPRfAj2Pq7Bo TNPG9bIGKqdITFSno2Wwcdp5B514iUwIFNCGNdaXrHEnomwd0pQF+dwMH0xMXj3zcCu5 e6YbwS5iDTtxuWFIA0CeqBTju7016JTpv4OU+mxoEYyAWLqRoY0x/EPP3HpoSpQK2ezp nTCpX3YUp12iIr3OtWL6MCH7BabmHbsNfFKbcI1vvQQKpuuKL0OxyIqowKO6t8MV6Fy8 +ZSA==
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=VBZCJN3+QKlDUBkcK/C4Onu4AO7x2DbRq/XDvbOdlqE=; b=doWMkAPZK4KwKrQf/smXJANRwVWIQfL2sQc2T0m9MAnNHhYfwYbmpDe+DRRRWfddk/ rZhR/q32LaZn4s3QH28wuNbIK0ftBtbB4J9rMUG2LNayLWpLZGBqaOTEch+YqJ7cWxZN sDTK7wAfnHvLE3lscghOE7MCDWw3cyIwoLSSayWbd8pvxAzGxp4Zv6mhrNBpseh6Y221 TfLjg2h5ykKgk1julM0JRKfKpja4bn9I+tdO+PxQ9dJhejlvH/H+fUFH13+SC8njAGIW hKggC3SXPQYyJKMjCdVuaIrdRg0skAuYLjbWPHs2rWRkefIWLFnkhUxaDjdQLkVAB7Zj UwYQ==
X-Gm-Message-State: ALyK8tLItsocjXUahOcaDMBQ3GkP9Bu5dMtzPWzviaTfUrV/OOOmJcnDgFWXrhnGTOcCGw==
X-Received: by 10.98.100.132 with SMTP id y126mr50666678pfb.101.1464652549975;  Mon, 30 May 2016 16:55:49 -0700 (PDT)
Received: from ?IPv6:2406:e007:7211:1:17b:d6:8bb5:3e91? ([2406:e007:7211:1:17b:d6:8bb5:3e91]) by smtp.gmail.com with ESMTPSA id c82sm35366617pfd.42.2016.05.30.16.55.46 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2016 16:55:48 -0700 (PDT)
Subject: Re: default-iids: Closing concern regarding stable address requirement
To: Lorenzo Colitti <lorenzo@google.com>
References: <5742118B.6020308@si6networks.com> <CAJE_bqdw9OX37JbENEg5qfqSfZPhzsLOQ6j+YZmXRosikb_0pA@mail.gmail.com> <m1b57qM-0000HYC@stereo.hq.phicoh.net> <1053CA91-EE52-4EE0-A995-E9139AE3FB53@employees.org> <57461B9D.2080001@si6networks.com> <A59929B2-1141-41B8-A864-A27D81A23E06@employees.org> <CAO42Z2w8y0d6mpnzE9qMsvKaxZZpnxCzNqm5bDVN=BkRud1RzA@mail.gmail.com> <8C9F7AC0-E262-4A64-AB42-4430151C2C31@employees.org> <CAO42Z2xGW9=6eHPXspjDA0TOL4LK3=zYv3wtdM53MsZ+KEiFhQ@mail.gmail.com> <CAKD1Yr1COjK5v2wn1CcEV4_j_0XSg8xNNoWN9fME75pR+ZVdUQ@mail.gmail.com> <de7da0da-87c0-219d-45a3-f8cb1760a370@gmail.com> <CAKD1Yr3=W2gbsC9rvwVBaxZR-0TnTK+w72W-QPy-FJbfFBU_XQ@mail.gmail.com> <ea6121dd-71f0-bf97-0019-0bf5b0285515@bogus.com> <CAKD1Yr2u4e14VWJe6_fEXzxjdgbBqPv_Aupu1C6LezY-VD23SQ@mail.gmail.com> <AC814216-26B1-4912-A1C0-5E1A8C3AB66A@bogus.com> <b271671f-8222-b435-3ae7-d62f23fac105@gmail.com> <CAKD1Yr0BKNOj82FmNPF-fpoHhFBaidai9ZHPfZShwdJbQH41_Q@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <f86bd1ff-2147-5583-75c8-aec754b0f91d@gmail.com>
Date: Tue, 31 May 2016 11:55:46 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0BKNOj82FmNPF-fpoHhFBaidai9ZHPfZShwdJbQH41_Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KlOHy4THFvPmc9ugWLwpH1Yq-Gc>
Cc: Fernando Gont <fgont@si6networks.com>, draft-ietf-6man-default-iids@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: Mon, 30 May 2016 23:55:52 -0000

On 30/05/2016 18:58, Lorenzo Colitti wrote:
> On Mon, May 30, 2016 at 5:18 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> So, I just don't see how we can claim to dictate any kind of general
>> default
>> or BCP in this area. But I don't seee that draft-ietf-6man-default-iids
>> does
>> that. Maybe it should be toned down to a SHOULD level, e.g.
>>
>> Abstract
>>
>>    This document changes the recommended scheme for generating stable
>>    Interface Identifiers with SLAAC to that specified in RFC7217, and
>>    recommends against embedding link-layer addresses in IPv6 Interface
>>    Identifiers.  It formally updates RFC2464, [...]
> 
> 
> If this document makes RFC7217 IIDs a SHOULD, how should it formally update
> the IPv6-over-foo RFCs? Currently it just blasts away any/all text in them
> that talks about IIDs. If it's just a SHOULD, then it can't do that any
> more.

Yes, I'm suggesting a compromise which adds a SHOULD-level alternative to all
those over-foos, rather than making a MUST-level change. That would require
some wordsmithing in the body of the draft, as well as in the Abstract.

   Brian


From nobody Mon May 30 17:00:59 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 0E81812D69E for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 17:00:58 -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 LWUuDeR3mCCG for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 17:00:56 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 5DE4712D62E for <ipv6@ietf.org>; Mon, 30 May 2016 17:00:56 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id f144so55436748pfa.3 for <ipv6@ietf.org>; Mon, 30 May 2016 17:00: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=h0EOvAgP9SqsWw4bjbu3L92Yy4ngmT2+lqnqHPqdzdE=; b=UcNvR1Sk5XKB4M2YKYOHcWA6HeJ0QSpy02lsko4jzKRPkSJm+a1L7IXIfxWxb3iBrZ lNWRfN3x3EAI1BUO4swU5vH+o71anh9HKHHNcqse3O+9kWKHU/kPg0qNdtlKhooMSpkb rfSamwbCztYewLTxvD7Z1cswosDBCGtJ6t124FWUn6AgDDnWh2bpqdwDV1vId0aPq+Qm ig3VilXWu69ZOnPHtag4XRUe38PjIdgkC9u60/WHUiNOu99cBBwiPL5F93MGE0uAEuOG Xlg6NNS+HLe8ZWpZp+ychWIvJAqM27MM4YwWIYeAMjVWpeby3ezzUOaCuns+ELe+TQWP PsHg==
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=h0EOvAgP9SqsWw4bjbu3L92Yy4ngmT2+lqnqHPqdzdE=; b=f0IqN6U8KhiBgpEH2+vBHbmPlEzzoTlNc+M+Vr6srhPbeR8EVm/FMI2X7qnK5whpcp RQZ3mhqebvIlU8XGifPsxh9KNch2BRTLjdKlx3IoEkYUUG2CpRa1brsTHH4ulqqXSACK sGVAD67t4svwV3NI9dSkVS/PMe981sBvLngFx4UTRAB+b6hfMlutdWyeTR/qtn1V4jW0 CcjoYVaHhK3m3AZIhwaQKnxksYye1I8Z/lJgTsknsUBp0dx+M9c6QltIS6+komVX5q8p 3QtHg4PIQNBcX8gco5jtkSn0RSigJrriYubFad/oTyNREqcL/KQ0tzkQEBjxANXo9zhP 220Q==
X-Gm-Message-State: ALyK8tLNzOauiWSNS8cwLqfA4/+HpPzMP9lcto9qChnSdI3b/E2w3KB2rDuOibEz+XKMAw==
X-Received: by 10.98.72.27 with SMTP id v27mr49826167pfa.143.1464652855831; Mon, 30 May 2016 17:00:55 -0700 (PDT)
Received: from ?IPv6:2406:e007:7211:1:17b:d6:8bb5:3e91? ([2406:e007:7211:1:17b:d6:8bb5:3e91]) by smtp.gmail.com with ESMTPSA id o2sm35335005pfi.85.2016.05.30.17.00.53 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2016 17:00:55 -0700 (PDT)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: otroan@employees.org, Lorenzo Colitti <lorenzo@google.com>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9dc39318-5e68-33ab-f55b-398d7a0893c0@gmail.com>
Date: Tue, 31 May 2016 12:00:54 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zaj1Wk2ZyVz8x6ipWP1cvos5hEc>
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, 31 May 2016 00:00:58 -0000

On 30/05/2016 19:32, otroan@employees.org wrote:
> Lorenzo,
> 
>> that would imply that any address used to reach facebook, google, etc is tainted and cannot be used for any other connection.
>>
>> ... privacy is not binary. An identifier is valid for 1 day poses much less risk than one that is permanent for the life of the device. A party that has *realtime* access to $COMPANY's webserver logs can track visitors to $COMPANY's webservers all the time. But if you uninstall the $COMPANY app and don't use $COMPANY's website for 1 day, that party cannot track you any more via those means.
>>
>> I'd argue that there are no deployed hosts / application combinations that can only use privacy addresses
>>
>> Privacy addresses as defined by RFC4941? Perhaps not today, but it's not hard to change that.
> 
> give me a functioning host that has no umbilical cord somewhere that leaks identity...
> 
>> if the consequence of this is that a temporary address can only be used within a single connection, then I can guarantee you that there will be many networks that will not support that. bridges do not have unlimited space.
>>
>> But some can. 3GPP mobile networks and draft-ietf-v6ops-unique-ipv6-prefix-per-host networks, need not be limited. Residential networks aren't limited but they might have space for thousands of ND cache entries, so thousands of addresses.
> 
> in 3GPP networks the subscriber is identified by the first 64 bits anyway.
> there is no standardised way for a host to know if it is getting a unique /64 is it?
> we're currently lacking a mechanism for the network to inform hosts that they aren't getting any addresses.
> 
> and I'm sure we can argue over the privacy properties of unique /64 per host.

Yes. But all I suggested is to remove the assumption in 4941 that there is always
a stable address. That is not the same thing as making a rule that there is
no stable address. It simply leaves the door open for an implementation to
allow no stable address, which is tricky at the moment.

    Brian


From nobody Mon May 30 17:44:19 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 B43B412D586 for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 17:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 8y0h6XOn-qVG for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 17:44:15 -0700 (PDT)
Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::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 992ED12D581 for <ipv6@ietf.org>; Mon, 30 May 2016 17:44:15 -0700 (PDT)
Received: by mail-yw0-x22d.google.com with SMTP id o16so174503474ywd.2 for <ipv6@ietf.org>; Mon, 30 May 2016 17:44:15 -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=PSZS+E/yCyrlhhlsrYHrfTMACt7rY7bAQ8kFHfIZPiY=; b=fsIy6z8YbdKVL24ZIfehwjRMRXukEc+t7LsKhQqe6Q6pXrDQNxdMO0jOY+ppf+ZWdm GmpjRDVwVRV+OfCQSzhZ8peCfQ+3x4aYGiBPY9imPDvWxFgyUnlUWP4VvOks6HC3XVIh EzopvyEs2yfm69exZHZAfQa27FtW8VYpXHZNlhcns5gSEEkImO3s0N9xLAUCumpAqsg8 FYt5Luh5cQPqRI7WfC6UbZwiMwIfo7N0iV8Y2VbOGMpwq1GfYkUemffOhWRSFEMsCn9o NZi+n6PhrSRf0T9h/nXN+xnQ/btzW/YpBnkPIkhvp2TZLTUbx01DCXcHYxexVo/CuxKu ayLg==
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=PSZS+E/yCyrlhhlsrYHrfTMACt7rY7bAQ8kFHfIZPiY=; b=cNKfOTB3FM+9CJ5v8X0VEHD/nGGKFEuQXINXDGaUg7zmO6VZHzir/ehwq/62mfsdR/ Iy0vneXjTNVR9eY6I9hmwm64iYUgU0FaKtR0WPARWjLxlGQne3KohclKnFD0dJoklSid DPJdqdYo2nRTh0OJrsidcxce30Nei6FUa0oxKBLCjOW3vM7APPizdk+DpIsN8Et7PWlD I/Gd18922ek78MhpgMTKz2XwdCkKCqFl3I9CRhLM2EH4ohqhI36ahvNwMcsj3UXXbxoZ xAp22ImgY+ye4I7mausYJO61oI/XG1uc90oVReSR9IPZgYV7TLfnvjzA9HZo1Z3vgY52 1D6A==
X-Gm-Message-State: ALyK8tLqcWvPy9hsmm26bJRqQF+7RdC7dNXRirsJ1cxua7QCVYFMl3AXHPdIEn0MYLw+vznCWQ0T6syXUuENwZm/
X-Received: by 10.37.228.198 with SMTP id b189mr18969110ybh.25.1464655454726;  Mon, 30 May 2016 17:44:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Mon, 30 May 2016 17:43:55 -0700 (PDT)
In-Reply-To: <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2016 09:43:55 +0900
Message-ID: <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114bc1c619a082053418acf3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0lZ_XU5Gi_Y5noYM6KGVJH-t1wk>
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, 31 May 2016 00:44:18 -0000

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

On Mon, May 30, 2016 at 4:32 PM, <otroan@employees.org> wrote:

> > I'd argue that there are no deployed hosts / application combinations
> that can only use privacy addresses
> >
> > Privacy addresses as defined by RFC4941? Perhaps not today, but it's not
> hard to change that.
>
> give me a functioning host that has no umbilical cord somewhere that leaks
> identity...
>

What are you suggesting? That RFC4941 addresses don't provide any useful
privacy? Or that hosts can't use only RFC4941 addresses? Something else?

in 3GPP networks the subscriber is identified by the first 64 bits anyway.
>

But that usually changes across disconnects, which can be initiated by the
host.


> there is no standardised way for a host to know if it is getting a unique
> /64 is it?
>

No, and I think it would be useful to have one.

--001a114bc1c619a082053418acf3
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 M=
on, May 30, 2016 at 4:32 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"><span class=3D"">&gt; I&#39;d argue th=
at there are no deployed hosts / application combinations that can only use=
 privacy addresses<br>
&gt;<br>
&gt; Privacy addresses as defined by RFC4941? Perhaps not today, but it&#39=
;s not hard to change that.<br>
<br>
</span>give me a functioning host that has no umbilical cord somewhere that=
 leaks identity...<br></blockquote><div><br></div><div>What are you suggest=
ing? That RFC4941 addresses don&#39;t provide any useful privacy? Or that h=
osts can&#39;t use only RFC4941 addresses? Something else?</div><div><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">in 3GPP networks the subscriber is ident=
ified by the first 64 bits anyway.<br></blockquote><div><br></div><div>But =
that usually changes across disconnects, which can be initiated by the host=
.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
there is no standardised way for a host to know if it is getting a unique /=
64 is it?<br></blockquote><div><br></div><div>No, and I think it would be u=
seful to have one.</div></div></div></div>

--001a114bc1c619a082053418acf3--


From nobody Mon May 30 21:53:45 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 37B3F12D0DA for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 21:53:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 XEFCa8noU8lf for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 21:53:41 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::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 C37C712B008 for <6man@ietf.org>; Mon, 30 May 2016 21:53:41 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id o16so178032556ywd.2 for <6man@ietf.org>; Mon, 30 May 2016 21:53:41 -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=A8PiA11K91flDHFqkq7yvRRbC80w5HXV87Y2sbj//K4=; b=ZE3Th7QCVdhPRNQlafXjJfSpjXB9PZ+hX2TTS2FxNRkDEng0j1tMKNG7xSkuKprI1J 6XiiDEpGNAFtAnTfX48lgCuaLOYPPFILvxD6LtVVIcFDxzfSfw2+dpjC14jpUhaGNy3o 6/NMVlpgMTDG21TWIY+vCTGn2RfRXNbJve9igOuCiQ8Wu0Vh3eQsjGtRzRRNZJhMjkeE Lg97bVd34azPorzQwuOPokhLitLAqa47nKr2C/kaaIguYYhQxYd6TJJO3spBil56vzWh 0SHHmZr1zj9qVEwoAg4yCpMNQ62wzkxxlPXCPSrb5s2r115Yu/ahTbEe7qVqy5c+3gxN vaIg==
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=A8PiA11K91flDHFqkq7yvRRbC80w5HXV87Y2sbj//K4=; b=EfqXCwQcvqMBCgDxM2qliLEsHV0pPKm1t2x1ZN+hjSZ1xe9DbKSY1AjIjmQTy0VoZD gGvHOVGAjB0qev8kvTeq8mvyHKnuP4X1MpZ/AWk4f+n3hE9tkuUFVRnw6cYygyBcbSNQ H5pF7uRSU7sVh+J+9PR+UVvPu4QZUNxB1JMz+i6pPdrYARp3lupl9X2gqS2z9bHoS6he WHIOxLQFTRZFTVivRYpNDH4f9d8OetQNwaUNiNYK0fMKoI1iHk+0JMhxoKCo1DJK6kpV HRZQgsYNukNoe0xHQtTrT76/epujfdCotFujTOLktcAEu73liQfNVbMbbonoeQP2X00l XNTQ==
X-Gm-Message-State: ALyK8tJX6hQrlTyQp8UZOq/q3DAyr1myCXDy/64XLg4L1PXakktvtEyHLiqgozKUbAxmLbbCrQ8Gok/xldmbT//4
X-Received: by 10.129.108.211 with SMTP id h202mr20295229ywc.229.1464670420741;  Mon, 30 May 2016 21:53:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Mon, 30 May 2016 21:53:21 -0700 (PDT)
In-Reply-To: <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2016 13:53:21 +0900
Message-ID: <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114da74624a79705341c2824
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zh546UhsPV5RGDNQDPF0MaCbmpo>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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, 31 May 2016 04:53:44 -0000

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

On Mon, May 30, 2016 at 8:18 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> > Your laptop doesn't do that, but perhaps it should.
>
> Which is contrary to the robustness principle.
>
> It would be smarter to test if the device reconnected to the same network
> or not rather than assuming it is always a different network and tearing
> down TCP sessions that will recover.
>
What if the device is already connected to another network? For example,
what if a device switches from cellular data to wifi? Does that count as a
"reconnect"? If it doesn't, then the app might be blocked for minutes in
read(), faithfully waiting for cellular data to come back (with the same IP
address!), even though there's a perfectly valid wifi connection available
that can be used right now.

> > As for servers, numbering them with EUI-64 or RFC7217 (which has the
> same stability properties, i.e., the stable for the life of the network
> card)
>
> Incorrect. See appendix A. If you think they are, then I don't think
> you've not fully understood the problem that RFC7217s solve. They
> specifically have decoupled the IID always relying on the NIC MAC address.
>
But RFC 7217 plainly states that it's associated with the network interface:

       Net_Iface:
          An implementation-dependent stable identifier associated with
          the network interface for which the RID is being generated.

"associated with the network interface" implies that it changes if the
interface changes.

> So there is another gotcha with randomising MAC addresses. (Years ago I
> used MAC address randomisation to over come these sorts of blockages...)
>
There are definitely gotchas with randomizing MAC addresses in the presence
of other stable identifiers like circuit IDs or physical network port
location. If the MAC address is the only identifier, as it is in wifi, then
that failure mode does not apply.

--001a114da74624a79705341c2824
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 M=
on, May 30, 2016 at 8:18 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-"><p dir=3D"ltr">&gt; Your laptop d=
oesn&#39;t do that, but perhaps it should.</p>
</span><p dir=3D"ltr">Which is contrary to the robustness principle.</p>
<p dir=3D"ltr">It would be smarter to test if the device reconnected to the=
 same network or not rather than assuming it is always a different network =
and tearing down TCP sessions that will recover.</p></blockquote><div>What =
if the device is already connected to another network? For example, what if=
 a device switches from cellular data to wifi? Does that count as a &quot;r=
econnect&quot;? If it doesn&#39;t, then the app might be blocked for minute=
s in read(), faithfully waiting for cellular data to come back (with the sa=
me IP address!), even though there&#39;s a perfectly valid wifi connection =
available that can be used right now.</div><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"><span class=3D"=
gmail-"><p dir=3D"ltr">&gt; As for servers, numbering them with EUI-64 or R=
FC7217 (which has the same stability properties, i.e., the stable for the l=
ife of the network card)<br></p></span><p dir=3D"ltr">Incorrect. See append=
ix A. If you think they are, then I don&#39;t think you&#39;ve not fully un=
derstood the problem that RFC7217s solve. They specifically have decoupled =
the IID always relying on the NIC MAC address.</p></blockquote><div>But RFC=
 7217 plainly states that it&#39;s associated with the network interface:</=
div><div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0Net_Iface:</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An implementation-dependent stable ide=
ntifier associated with</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the ne=
twork interface for which the RID is being generated.</div></div><div><br><=
/div><div>&quot;associated with the network interface&quot; implies that it=
 changes if the interface changes.</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class=3D"gma=
il-"><p dir=3D"ltr">So there is another gotcha with randomising MAC address=
es. (Years ago I used MAC address randomisation to over come these sorts of=
 blockages...)<br></p></span></blockquote><div>There are definitely gotchas=
 with randomizing MAC addresses in the presence of other stable identifiers=
 like circuit IDs or physical network port location. If the MAC address is =
the only identifier, as it is in wifi, then that failure mode does not appl=
y.</div></div></div></div>

--001a114da74624a79705341c2824--


From nobody Mon May 30 23:56:18 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 0E6CD12B04A for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 23:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 9s9Tho-DkUnr for <ipv6@ietfa.amsl.com>; Mon, 30 May 2016 23:56:14 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 08A1312B029 for <6man@ietf.org>; Mon, 30 May 2016 23:56:14 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id c189so246853650vkb.1 for <6man@ietf.org>; Mon, 30 May 2016 23:56:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=hQVSPJOAyA/yyWu5c+ioc+eOXS4CfTkSEMhsGw29Hw4=; b=BmmdGB4XdxnHKer7vT3hRDK78NPafAm4IjA6mRnIAAcaj69YiAg45Hav8USQm8RpQ+ tkkNOjlm9VBK676Uza9o9un7v90PXJlWhSEr45SoZB/QGYLUBeLOvHYvnNlFDtjWIqOy KIHo2zp03B7FKwJdyuQ5nf8cvycYO6PWc5+b3nMww3BybQCveBOAk/G3cj9LK+K7B+5+ mTKzMKnR5PQUqgV5nyTuOEiZ+UXvqMqTrF+Ac5dn4BicUsP6XO7mAAqQVBnQfyg11xG2 OuPgEG3EAWKI4IOIVmYRcAxDJ7Vz/OuUr0fzhmCJaiI0aE8xBJFzJylcTVQDBINkjrJQ PRAQ==
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:date :message-id:subject:from:to:cc; bh=hQVSPJOAyA/yyWu5c+ioc+eOXS4CfTkSEMhsGw29Hw4=; b=aiKYXhnkWBM7q4qzzLeGxYNq83PHfISTvHROHxcdgFSrbag1RMbONqD8U7ZbO/lTYo EnhfDrVkLk4ZNq+Lm6p77NJATphvHpwQWcQTaGGwct765F8vpHDJ/BlTrjq/NN1sPlyQ JXgI9Iul6jlK7At+AJPE3B6mO9nCGIpTHHE5YCBqqWyJKcmOn/ZbgOZqJOzfWlcdJjh5 ytPNW8Xf/HjayMl3XySd/vIWSFOnG+1MJnPkADOwxPyMNw5KOEXEg8oV680/4X4nYdLC 5WpQ1YSIfjTKXyPpZENTNH87giyOUZkgBqQO/aGzSZRUopeDf5TQfaAQjM3VgV8ZCeTp weYw==
X-Gm-Message-State: ALyK8tIfHubttMnQ4s1myCh4NK4iOKOeOgwOu5dzs8NPPuCXm9nc+D5/U630P8yjTlHcY2SN1pfkN2RFYutIBg==
MIME-Version: 1.0
X-Received: by 10.31.51.11 with SMTP id z11mr16388702vkz.150.1464677773029; Mon, 30 May 2016 23:56:13 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Mon, 30 May 2016 23:56:12 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Mon, 30 May 2016 23:56:12 -0700 (PDT)
In-Reply-To: <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com> <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com>
Date: Tue, 31 May 2016 16:56:12 +1000
Message-ID: <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114475985f35a005341dde17
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mUbldOyK5aQVFYoj8lj0Ka6Rvbg>
Cc: Fernando Gont <fgont@si6networks.com>, 6man@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, 31 May 2016 06:56:16 -0000

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

On 31 May 2016 2:23 PM, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Mon, May 30, 2016 at 8:18 AM, Mark Smith <markzzzsmith@gmail.com>
wrote:
>>
>> > Your laptop doesn't do that, but perhaps it should.
>>
>> Which is contrary to the robustness principle.
>>
>> It would be smarter to test if the device reconnected to the same
network or not rather than assuming it is always a different network and
tearing down TCP sessions that will recover.
>
> What if the device is already connected to another network? For example,
what if a device switches from cellular data to wifi? Does that count as a
"reconnect"?

No. Clearly different networks, of more specifically, different link
(RFc2460)/subnets/default router(s)

If it doesn't, then the app might be blocked for minutes in read(),
faithfully waiting for cellular data to come back (with the same IP
address!), even though there's a perfectly valid wifi connection available
that can be used right now.
>>
>> > As for servers, numbering them with EUI-64 or RFC7217 (which has the
same stability properties, i.e., the stable for the life of the network
card)
>>
>> Incorrect. See appendix A. If you think they are, then I don't think
you've not fully understood the problem that RFC7217s solve. They
specifically have decoupled the IID always relying on the NIC MAC address.
>
> But RFC 7217 plainly states that it's associated with the network
interface:
>
>        Net_Iface:
>           An implementation-dependent stable identifier associated with
>           the network interface for which the RID is being generated.
>
> "associated with the network interface" implies that it changes if the
interface changes.
>>

Read the whole of RFC7217, or at least Appendix A, as I said before.

>> So there is another gotcha with randomising MAC addresses. (Years ago I
used MAC address randomisation to over come these sorts of blockages...)
>
> There are definitely gotchas with randomizing MAC addresses in the
presence of other stable identifiers like circuit IDs or physical network
port location. If the MAC address is the only identifier, as it is in wifi,
then that failure mode does not apply.

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

<p dir=3D"ltr"><br>
On 31 May 2016 2:23 PM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:l=
orenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Mon, May 30, 2016 at 8:18 AM, Mark Smith &lt;<a href=3D"mailto:mark=
zzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; &gt; Your laptop doesn&#39;t do that, but perhaps it should.<br>
&gt;&gt;<br>
&gt;&gt; Which is contrary to the robustness principle.<br>
&gt;&gt;<br>
&gt;&gt; It would be smarter to test if the device reconnected to the same =
network or not rather than assuming it is always a different network and te=
aring down TCP sessions that will recover.<br>
&gt;<br>
&gt; What if the device is already connected to another network? For exampl=
e, what if a device switches from cellular data to wifi? Does that count as=
 a &quot;reconnect&quot;?</p>
<p dir=3D"ltr">No. Clearly different networks, of more specifically, differ=
ent link (RFc2460)/subnets/default router(s)</p>
<p dir=3D"ltr"> If it doesn&#39;t, then the app might be blocked for minute=
s in read(), faithfully waiting for cellular data to come back (with the sa=
me IP address!), even though there&#39;s a perfectly valid wifi connection =
available that can be used right now.<br>
&gt;&gt;<br>
&gt;&gt; &gt; As for servers, numbering them with EUI-64 or RFC7217 (which =
has the same stability properties, i.e., the stable for the life of the net=
work card)<br>
&gt;&gt;<br>
&gt;&gt; Incorrect. See appendix A. If you think they are, then I don&#39;t=
 think you&#39;ve not fully understood the problem that RFC7217s solve. The=
y specifically have decoupled the IID always relying on the NIC MAC address=
.<br>
&gt;<br>
&gt; But RFC 7217 plainly states that it&#39;s associated with the network =
interface:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Net_Iface:<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An implementation-dependent stable =
identifier associated with<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the network interface for which the=
 RID is being generated.<br>
&gt;<br>
&gt; &quot;associated with the network interface&quot; implies that it chan=
ges if the interface changes.<br>
&gt;&gt;</p>
<p dir=3D"ltr">Read the whole of RFC7217, or at least Appendix A, as I said=
 before.<br></p>
<p dir=3D"ltr">&gt;&gt; So there is another gotcha with randomising MAC add=
resses. (Years ago I used MAC address randomisation to over come these sort=
s of blockages...)<br>
&gt;<br>
&gt; There are definitely gotchas with randomizing MAC addresses in the pre=
sence of other stable identifiers like circuit IDs or physical network port=
 location. If the MAC address is the only identifier, as it is in wifi, the=
n that failure mode does not apply.<br></p>

--001a114475985f35a005341dde17--


From nobody Tue May 31 00:23:43 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 8A7C612B04A for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 00:23: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 v1BrFIVvzWsX for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 00:23:35 -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 8FB1812B008 for <ipv6@ietf.org>; Tue, 31 May 2016 00:23:35 -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 May 2016 07:23:34 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 36D839CC4E; Tue, 31 May 2016 00:23:33 -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=p1A3OM3b0AETJyYaTTaGMbzrQFc=; b= Bkwr8Fm2BLnHS/mVjWtBqM2SxmHHO8RlgfJ0FDwh+x4RTYReYtG71x1xYHuZosLn sUBd0ffU7MvGAG3BUTlbBimopy6x7LZAdwrFnwzOaoq0P6AzPrsbVipM5XjMu3Wn Ca55t8JqV3r1JFlo4hN5EJYiMQTFVcJNbxPQzZItd88=
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=jX6lbOb4dmwotjHcOKPuaIcJh+ dMwZNwNM2uXKZK3YHR659+w649MeEE/lWEzmn+2kvltOIHNNw+8/6pkiq72gZDJi 2/5Jwc0aAew55Tslt34I9o/VEG5gyNqbh2mI7KCdPJGA7NIg3OGH+EvL0O6jhUJ2 e9Sm5uwPNi2YL9pF0=
Received: from h.hanazo.no (eduroam-0-91.enst.fr [137.194.56.91]) (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 F11B19CC51; Tue, 31 May 2016 00:23:32 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2E14417527CB; Tue, 31 May 2016 09:23:31 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_65BFE76E-8FFB-4E50-952A-D037051D9399"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com>
Date: Tue, 31 May 2016 09:23:28 +0200
Message-Id: <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org> <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nTUSKvorzaZyf710AOJOYL9YobI>
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, 31 May 2016 07:23:41 -0000

--Apple-Mail=_65BFE76E-8FFB-4E50-952A-D037051D9399
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lorenzo,

> > I'd argue that there are no deployed hosts / application =
combinations that can only use privacy addresses
> >
> > Privacy addresses as defined by RFC4941? Perhaps not today, but it's =
not hard to change that.
>=20
> give me a functioning host that has no umbilical cord somewhere that =
leaks identity...
>=20
> What are you suggesting? That RFC4941 addresses don't provide any =
useful privacy? Or that hosts can't use only RFC4941 addresses? =
Something else?

I'm making the observation that if you have a host with only RFC4941 =
addresses, you will end up using 4941 addresses as public addresses. and =
that you cannot reuse an address you have coupled identity with for any =
other connection.

4941 may improve privacy, but it clearly isn't sufficient in itself.

>=20
> in 3GPP networks the subscriber is identified by the first 64 bits =
anyway.
>=20
> But that usually changes across disconnects, which can be initiated by =
the host.
>=20
> there is no standardised way for a host to know if it is getting a =
unique /64 is it?
>=20
> No, and I think it would be useful to have one.

DHCP PD?
we also need a mechanism to inform hosts that the network is out of =
addresses.

cheers,
Ole

--Apple-Mail=_65BFE76E-8FFB-4E50-952A-D037051D9399
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

iQEcBAEBCgAGBQJXTTvzAAoJED4aXnjSQuKWLikH/0V25g6WyNHgCIgmc4YJlthd
Y8CfqMK6d6UwTkdYPY/nzao7ujUEjIyul2k4EO0Y2o7ONtn2+1q6MHy++8Ll5su5
4K510xgJ4fwh5Yt+UtzjVS9VG5FrTHBfyxj+/HKDWgcYSGovlNsVWIddsUDhGoY1
miack6ac0j9VWLiSk4FxYALLEDXzDxGbL3KESc/iSmtcp7WrGEZCMIBloTR+T1c8
UMZH5Xx9hv8JiwqZiySTomCeUu05mle+TF3kdzBfrjwwEvqkXREtDULSNQwkshLH
TzlrcUFjNmiV3TocfhhyYOdJTmYn9Ugwv5xXpRZ2el/Inf3d3c/RduS8V4dDU8Q=
=6pxE
-----END PGP SIGNATURE-----

--Apple-Mail=_65BFE76E-8FFB-4E50-952A-D037051D9399--


From nobody Tue May 31 01:04:34 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 D0D2512D153 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:04:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 hsLlkftYjA3s for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:04:31 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::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 E821C12D140 for <ipv6@ietf.org>; Tue, 31 May 2016 01:04:30 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id x189so180929460ywe.3 for <ipv6@ietf.org>; Tue, 31 May 2016 01:04:30 -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=MLh2RAuMIBX8fQ24QDwWrySR1TYsw713s0y2M7H46YM=; b=SaBRizuUXL0gX7NAewLBI3c9pgX3y8kSKfOonRCTcCdTZs94z3wUp9hai1+CyciGoJ jVsX4onMguYiEakBVi+TeeWTdvSkjsVvtl3OfZV8Kfi29jIv1IAApszT4e2kSohB4IO2 jl5qjhBmt3ixqNlrsienC9AdazoWsKP/SGzsCGewT/61lR1iY3FcvIDKGbSuxtJKwyun udp287AbptsQF8gtduVL27MGT/mGE8msF+2OogYW2muZcUa1hE6va4k9aiCqMSfLUUlh HqiBVoLW+Rf0Xh0inS8ZcWiBHuhsi8vFJxJJb7D5DjymiuZFP2IeG7YCGKHw/7g2gw2h i8Nw==
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=MLh2RAuMIBX8fQ24QDwWrySR1TYsw713s0y2M7H46YM=; b=R2k1A71zh3wA3IvQjS6DIbfVaAp0VGhbIPHMAD0q4ZE4+aecLFUef0oJFx5oQpd9zO jo5oRCcgubfwNQfTE2ybLMdXC7ED4+3BQQjbJSDU/BN7D05g6dGG2N0o6hzRHF96DY2v AVOGhh5WunbomCvyiLoqtLAm6fEM6Up3FEoyO4wv8AYcPl84irs02XD4/+b5akxaYPO+ BxQVvxCyFNK7ih50uu7sHrgncnl4vblUGDuWOz07lwRcxX3EA1TYht4xuuKslFHEbhi3 PJfTOiwVSvdGQKYziFQQ/s6czJDUOr1HnlNwYVFT2e3dnbqQdnR4u9N45fqnapSSZNmZ K2Lg==
X-Gm-Message-State: ALyK8tL2Su4zQFUjXZ2P+ATsbznXTh+/O1d7XV+VSRxlyv3x0TQssOd0dadO2qeFK8Lecb393f1hefXcsfQeN/bc
X-Received: by 10.13.220.69 with SMTP id f66mr21822622ywe.132.1464681870040; Tue, 31 May 2016 01:04:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Tue, 31 May 2016 01:04:10 -0700 (PDT)
In-Reply-To: <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org> <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com> <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2016 17:04:10 +0900
Message-ID: <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=94eb2c0815c893227105341ed245
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bYcZAu_xWqkt9luI_YcyBOTNpKg>
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, 31 May 2016 08:04:33 -0000

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

On Tue, May 31, 2016 at 4:23 PM, <otroan@employees.org> wrote:

> > What are you suggesting? That RFC4941 addresses don't provide any useful
> privacy? Or that hosts can't use only RFC4941 addresses? Something else?
>
> I'm making the observation that if you have a host with only RFC4941
> addresses, you will end up using 4941 addresses as public addresses.


Your statement does not mean much unless you define "public". The
difference between RFC 4941 addresses and other addresses is not are that
RFC 4941 addresses are not persistent.


> and that you cannot reuse an address you have coupled identity with for
> any other connection.
>

Can you explain the threat you're trying to counter? From what you say I
assume it has to involve some party with realtime access to part of your
communications that is able to correlate temporary addresses before they
change, but I'm not sure exactly what the threat model is. There is one
party that can always track 100% of what you do at the IP layer, and that
is the first-hop router. Is that what you're talking about?


> > there is no standardised way for a host to know if it is getting a
> unique /64 is it?
> >
> > No, and I think it would be useful to have one.
>
> DHCP PD?
>

PD works, but most "/64 per host" deployments today do not use DHCPv6 PD
because they are 3GPP networks that use RAs. I would expect /64 per host
deployments to continue to be mostly RA-based, as discussed
in draft-ietf-v6ops-unique-ipv6-prefix-per-host. I think a "this prefix is
dedicated to you" flag in the RA would be useful.

we also need a mechanism to inform hosts that the network is out of
> addresses.
>

That's NOT RECOMMENDED by draft-ietf-v6ops-host-addr-availability.

--94eb2c0815c893227105341ed245
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, May 31, 2016 at 4:23 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otroa=
n@employees.org">otroan@employees.org</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:=
1ex"><span class=3D"gmail-">&gt; What are you suggesting? That RFC4941 addr=
esses don&#39;t provide any useful privacy? Or that hosts can&#39;t use onl=
y RFC4941 addresses? Something else?<br>
<br>
</span>I&#39;m making the observation that if you have a host with only RFC=
4941 addresses, you will end up using 4941 addresses as public addresses.</=
blockquote><div><br></div><div>Your statement does not mean much unless you=
 define &quot;public&quot;. The difference between RFC 4941 addresses and o=
ther addresses is not are that RFC 4941 addresses are not persistent.</div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"> and that you cannot reuse an address you=
 have coupled identity with for any other connection.<br></blockquote><div>=
<br></div><div>Can you explain the threat you&#39;re trying to counter? Fro=
m what you say I assume it has to involve some party with realtime access t=
o part of your communications that is able to correlate temporary addresses=
 before they change, but I&#39;m not sure exactly what the threat model is.=
 There is one party that can always track 100% of what you do at the IP lay=
er, and that is the first-hop router. Is that what you&#39;re talking about=
?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-=
color:rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">&gt; there =
is no standardised way for a host to know if it is getting a unique /64 is =
it?<br>
&gt;<br>
&gt; No, and I think it would be useful to have one.<br>
<br>
</span>DHCP PD?<br></blockquote><div><br></div><div>PD works, but most &quo=
t;/64 per host&quot; deployments today do not use DHCPv6 PD because they ar=
e 3GPP networks that use RAs. I would expect /64 per host deployments to co=
ntinue to be mostly RA-based, as discussed in=C2=A0draft-ietf-v6ops-unique-=
ipv6-prefix-per-host. I think a &quot;this prefix is dedicated to you&quot;=
 flag in the RA would be useful.</div><div><br></div><blockquote class=3D"g=
mail_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">
we also need a mechanism to inform hosts that the network is out of address=
es.<br></blockquote><div><br></div><div>That&#39;s NOT RECOMMENDED by draft=
-ietf-v6ops-host-addr-availability.</div></div></div></div>

--94eb2c0815c893227105341ed245--


From nobody Tue May 31 01:22:18 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 8DD6412B04F for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 lwRWGqVqTcUO for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:22:14 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::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 A4DF712B008 for <6man@ietf.org>; Tue, 31 May 2016 01:22:14 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id o16so181416772ywd.2 for <6man@ietf.org>; Tue, 31 May 2016 01:22:14 -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=aswy0yKyfAJem4FZTKdRPrRiQCCpa3NFVcmbY4entks=; b=Gedoxg/Qch676x3xTjE0FEft/fjSTx8k8c83sNEgWjlkgNZnCPzZNaTF7ApCF7Pc/R BVFKE0FZwq6FIMtWTAU+Imoy8ZLjvJe9JdrEipt4DZYI+mQcQY7rO8IME9JuzTYoVFaK 7ZC5wggpgzwcZnququpLFIiiM1XVXHkVFrmxt3iffXYiEIOSBC4acps8BaIdGwU7Z+VJ Rf0hm7DgzVH3r+PbYziVInJgMcjW8PlfUktj8uFnoED1KusS8FQ5dnJOstrbnonN3Pgf 8qH2E52IiV2a/ND3FltI6+8pLTWGl/dFusfftlpK9LxhetjzNyhT9JxyVsDfv8sfuJG8 Vp/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=aswy0yKyfAJem4FZTKdRPrRiQCCpa3NFVcmbY4entks=; b=fIfSDTZuJb0UX0/a572oooKPJevCnuLLJIcauPvqA9wL+tvnV2IEVHHfuhcspMstEV Dm/+fmqaXT3tKqRS31SiNyLnAk+VfJn8zPtiMS0gzKdNqKjuuqjj7+z1eKYWC/1KUtXc S4SivDcr++mRZgK7Pgr6ZcFMe5m4pU0mm8HTOnBpcQ8Xto6iWeQIi6dbWXnuv0aYMlmA eRf9MsgQhgOLB7UfDCHSso1YMCYmOZte8hbnvTsah0dZV+dgt6qhJ2/lCbegphUCWvVB 2A8iFF8Y8qP0kSMHlEtVbl35kuOFl1RQ7O5xfrQYiKS0EcSCLnSkoiimH4H1l9PTxq6e 10QA==
X-Gm-Message-State: ALyK8tKBJv4famW6eIV6Ti2lh59xcc/4v8Z3dp/QO5/imWRKDM3/8d/BNI6ZsLPaG3UAO9mS91jmRGuQQgQX1LV+
X-Received: by 10.129.108.211 with SMTP id h202mr20716725ywc.229.1464682933779;  Tue, 31 May 2016 01:22:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Tue, 31 May 2016 01:21:54 -0700 (PDT)
In-Reply-To: <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com> <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com> <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2016 17:21:54 +0900
Message-ID: <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114da746fa933e05341f11eb
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AVDLoHza2StXHXOF1alAanxmF4A>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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, 31 May 2016 08:22:16 -0000

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

On Tue, May 31, 2016 at 3:56 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

> > What if the device is already connected to another network? For example,
> what if a device switches from cellular data to wifi? Does that count as a
> "reconnect"?
>
> No. Clearly different networks, of more specifically, different link
> (RFc2460)/subnets/default router(s)
>
Then all apps are sitting there waiting for read() calls that will never
complete unless the same network reconnects. That's pretty much always the
wrong thing to do for the majority of apps - most apps are better served by
making a new connection on another network than sitting there waiting for a
network that is gone and might not come back for a long time. Imagine how
irritating it would be if your browser hung every time you walk in and out
of range of a wifi network.


> > But RFC 7217 plainly states that it's associated with the network
> interface:
> >
> >        Net_Iface:
> >           An implementation-dependent stable identifier associated with
> >           the network interface for which the RID is being generated.
> >
> > "associated with the network interface" implies that it changes if the
> interface changes.
> >>
>
> Read the whole of RFC7217, or at least Appendix A, as I said before.
>
But I did. The way I read it, all the suggestions in Appendix A have equal
or less stability than the interface link-layer address. On client systems,
interface name and index are at best as persistent as the MAC address. At
worst, they depend unpredictably on device initialization order and
connect/disconnect sequence.

Logical network service identity is the only one that might have higher
stability, but it's hard to tell what properties "a conception of logical
network service identity, distinct from network interface identity or
index" means since it's rather vague. One thing that's for sure is that
logical network interface identity *must* be tightly coupled to the network
card it's used with, because if it isn't and the host connects to the same
network simultaneously with two interfaces, the algorithm will generate
duplicate addresses, and that's explicitly forbidden by the document.

--001a114da746fa933e05341f11eb
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, May 31, 2016 at 3:56 PM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204)=
;padding-left:1ex"><span class=3D"gmail-"><p dir=3D"ltr">&gt; What if the d=
evice is already connected to another network? For example, what if a devic=
e switches from cellular data to wifi? Does that count as a &quot;reconnect=
&quot;?</p>
</span><p dir=3D"ltr">No. Clearly different networks, of more specifically,=
 different link (RFc2460)/subnets/default router(s)</p></blockquote><div>Th=
en all apps are sitting there waiting for read() calls that will never comp=
lete unless the same network reconnects. That&#39;s pretty much always the =
wrong thing to do for the majority of apps - most apps are better served by=
 making a new connection on another network than sitting there waiting for =
a network that is gone and might not come back for a long time. Imagine how=
 irritating it would be if your browser hung every time you walk in and out=
 of range of a wifi network.<br></div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><sp=
an class=3D"gmail-">
<p dir=3D"ltr">&gt; But RFC 7217 plainly states that it&#39;s associated wi=
th the network interface:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Net_Iface:<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An implementation-dependent stable =
identifier associated with<br>
&gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the network interface for which the=
 RID is being generated.<br>
&gt;<br>
&gt; &quot;associated with the network interface&quot; implies that it chan=
ges if the interface changes.<br>
&gt;&gt;</p>
</span><p dir=3D"ltr">Read the whole of RFC7217, or at least Appendix A, as=
 I said before.</p></blockquote><div>But I did. The way I read it, all the =
suggestions in Appendix A have equal or less stability than the interface l=
ink-layer address. On client systems, interface name and index are at best =
as persistent as the MAC address. At worst, they depend unpredictably on de=
vice initialization order and connect/disconnect sequence.</div><div><br></=
div><div>Logical network service identity is the only one that might have h=
igher stability, but it&#39;s hard to tell what properties &quot;a concepti=
on of logical network service identity, distinct from network interface ide=
ntity or index&quot; means since it&#39;s rather vague. One thing that&#39;=
s for sure is that logical network interface identity *must* be tightly cou=
pled to the network card it&#39;s used with, because if it isn&#39;t and th=
e host connects to the same network simultaneously with two interfaces, the=
 algorithm will generate duplicate addresses, and that&#39;s explicitly for=
bidden by the document.</div></div></div></div>

--001a114da746fa933e05341f11eb--


From nobody Tue May 31 01:37:09 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 897A712D189 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:37:02 -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 vI0utzp5RYBP for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 01:37:00 -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 7FE5F12D186 for <ipv6@ietf.org>; Tue, 31 May 2016 01:36:59 -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 May 2016 08:36:58 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 512679CC51; Tue, 31 May 2016 01:36:57 -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=G4dgIyZyl6Wom8CcDT10nqUSEz8=; b= KXV432HOpxzgYpu80WILLZj06KI9Sv1eNtt9lUxoyGCDPQrYjwXb9ND7i49kPfcz d2PKERwnGiLNYfAkei0DBdw/v+X7zFJR8UfgOv7dbb8GG+gRxiM3QeGJEMmPfw4q rzUoQS6jv+ZPmyvc9Mji/3BPj8xDMa9Z9PknUUVqTWM=
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=ndjPD8nBQosyBqCtovTr/NYhwd m5e9jejyFxj4UNmiDS/mqc/pUq6dnx1vPqSzE/Cn453qNckIHXZVSzntm1SaNVKG fisomdP7Z8Wo1w0+hcqfOs9sDAX8YYeN4AHjxWYzWNWNfO0B1JYnRRmbO7RLUIx0 3DY1qtxC38FqDaWAg=
Received: from h.hanazo.no (eduroam-0-91.enst.fr [137.194.56.91]) (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 CD5CB9CC4E; Tue, 31 May 2016 01:36:56 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 0987D1753A2C; Tue, 31 May 2016 10:36:55 +0200 (CEST)
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E937F338-A303-4983-9A73-2F184547D380"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com>
Date: Tue, 31 May 2016 10:36:52 +0200
Message-Id: <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org> <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com> <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org> <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qkc-Py1jR_xT7lEZjrkjJGzC5q4>
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, 31 May 2016 08:37:02 -0000

--Apple-Mail=_E937F338-A303-4983-9A73-2F184547D380
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lorenzo,

> > What are you suggesting? That RFC4941 addresses don't provide any =
useful privacy? Or that hosts can't use only RFC4941 addresses? =
Something else?
>=20
> I'm making the observation that if you have a host with only RFC4941 =
addresses, you will end up using 4941 addresses as public addresses.
>=20
> Your statement does not mean much unless you define "public". The =
difference between RFC 4941 addresses and other addresses is not are =
that RFC 4941 addresses are not persistent.

IPv6 addresses are not persistent. they are all ephemeral. it is just a =
matter of the lifetime.

a public address is one registered in DNS or some other external =
registry.
I would argue that the address you use to reach facebook (and thereby =
couple address and identity) you have made that address a public =
address.

> and that you cannot reuse an address you have coupled identity with =
for any other connection.
>=20
> Can you explain the threat you're trying to counter? =46rom what you =
say I assume it has to involve some party with realtime access to part =
of your communications that is able to correlate temporary addresses =
before they change, but I'm not sure exactly what the threat model is. =
There is one party that can always track 100% of what you do at the IP =
layer, and that is the first-hop router. Is that what you're talking =
about?
>=20
> > there is no standardised way for a host to know if it is getting a =
unique /64 is it?
> >
> > No, and I think it would be useful to have one.
>=20
> DHCP PD?
>=20
> PD works, but most "/64 per host" deployments today do not use DHCPv6 =
PD because they are 3GPP networks that use RAs. I would expect /64 per =
host deployments to continue to be mostly RA-based, as discussed in =
draft-ietf-v6ops-unique-ipv6-prefix-per-host. I think a "this prefix is =
dedicated to you" flag in the RA would be useful.

that would likely require a change to the subnet model.

> we also need a mechanism to inform hosts that the network is out of =
addresses.
>=20
> That's NOT RECOMMENDED by draft-ietf-v6ops-host-addr-availability.

it doesn't really matter if that draft says that. in reality there is a =
limit. an address can either fail silently (possibly with an ICMP) or =
explicitly.

cheers,
Ole

--Apple-Mail=_E937F338-A303-4983-9A73-2F184547D380
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

iQEcBAEBCgAGBQJXTU0mAAoJED4aXnjSQuKWbxYH/Apbm2aIBG6VwVNakOlJXZ/Q
3u2h3Q1uoWcLdizMGhBz0CclhCK/YQiIhz9g32OfIvCMD5pn3a4DFIhGXpeFPH0+
FgS429hsau61e4pgeEBUxx2cRMzPxRC6CDBDnzmyF8svwgQoXpxa2WEOYTGYAdHF
mzjFAWuJ+b7J8cR+DxE8pAgGcHNjbdKIoWW/BTsnN5Ezj78ZtNThPHKN6UeQ194y
NNATUVSGaLo/FKRu+7zVtKz3Do5zrwnJsrYL5II7sH3Tv/OpdZ9n3VUgvGlcaemN
fpKIUAxnBXayg6NFNfu4g2L5eiQ/hsaGbwpaPsPSCqRPW2HMoH3hb4IRT1JMdww=
=qEYR
-----END PGP SIGNATURE-----

--Apple-Mail=_E937F338-A303-4983-9A73-2F184547D380--


From nobody Tue May 31 02:05:42 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 7686D12D0C6 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 02:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 ZjFRa4-Izrd8 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 02:05:38 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 424F212D096 for <ipv6@ietf.org>; Tue, 31 May 2016 02:05:38 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id o16so182232160ywd.2 for <ipv6@ietf.org>; Tue, 31 May 2016 02:05:38 -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=AldQywwjjgpx+db4vrbT+RdygmjZ45CPlGfIVyvpkGc=; b=A28ijneSOESfZpp8LvDEx5EWZ8Le6OOtE/VSNaZg99YtjA1n9nXSvuiJdEnRpVBJ+Q JkuBYZmyjS+g2f0IzoHfv7cw2tIVkat/p5cIqkz+OhN/2xMA6SfjSK5aUdRzDM+s1rgB 0O0wVx53mStu9At1l9zpMx34UQlk3AytBwZk2ydYl74OJWuZT3J1vo1Lib/0Jq0NAeJL aENKEjEesqA4Cd7WWl9A7+s22csS/+wvcJ4i6AwKtlxEPzlIWHDz3t8NJOnwzX86UxNc rELY4j62GFCmENi55zCvM2p+0kQGyCfILfHA3fnHQHq6SFJHj4T1izwnf7SD4jnrirUf aOog==
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=AldQywwjjgpx+db4vrbT+RdygmjZ45CPlGfIVyvpkGc=; b=Bosp3S2ZKsWSRLsGk0EWWd3Dmiyu/xJlHSyIU7r+RWavMbJlwqTfwu1W1qSSIjd/Nh VRAaWsKBhsExqLN9c7RmZUBaHG0tGRZ4YGmCJBHmqzZh9naf5aRzo52RbFfDgRLUgXtb LJUW1L81aXYSwo9fYk8IEzxUuC9I8H1/eo5ykOUwpwJBH/ekQbgW+yyR3c0eFhKgVuZC jj9kUWeo+hvbrdTHzOdorseFSZo/8SnskOzR8k8fVBRbMFIBemW+bS1Ezy6vcEywGEL+ R2ga55dGZUixPrtDyeiuI0hZRwfeD+6wxLgpfPpaHgK7kDP5V44Md7I8FoQpXwRAs4S5 nonA==
X-Gm-Message-State: ALyK8tKv+12gzzGThVpIC20XQDd7pmranjvojld7e9Gn6VrLciRQJD8YgR+mjSD1Nvt5h0E3OqJm5WbdZDoDA4A/
X-Received: by 10.129.82.214 with SMTP id g205mr21485985ywb.66.1464685537360;  Tue, 31 May 2016 02:05:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Tue, 31 May 2016 02:05:17 -0700 (PDT)
In-Reply-To: <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org>
References: <20160523150736.10739.19307.idtracker@ietfa.amsl.com> <de70bacb-40f2-0684-897f-8a5167b68c36@gmail.com> <85D7A11B-03B1-4570-8F4B-EA533FF2CAEA@employees.org> <CAKD1Yr0c0R3zO+ejcLKCqize8ncQVmV_Cgy1F_JO4UdoDi=_Ng@mail.gmail.com> <3F8CA752-D0B9-4516-9C93-C736BF9946CF@employees.org> <CAKD1Yr1OMWyksyt7m50AuVFQcAsa3xqfn4BytHUA0HjpuG8MNw@mail.gmail.com> <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org> <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com> <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 31 May 2016 18:05:17 +0900
Message-ID: <CAKD1Yr3dOwH8ESDOc59xnv6uqP50FXoX-OH4pXMCuSM0DMe8qg@mail.gmail.com>
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114dc69429f96705341fadd0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7YIZlUDKtmAsDaNrKbV-YanRRrw>
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, 31 May 2016 09:05:41 -0000

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

On Tue, May 31, 2016 at 5:36 PM, <otroan@employees.org> wrote:

> > Your statement does not mean much unless you define "public". The
> difference between RFC 4941 addresses and other addresses is not are that
> RFC 4941 addresses are not persistent.
>
> IPv6 addresses are not persistent. they are all ephemeral. it is just a
> matter of the lifetime.
>

Right, but there are many orders of magnitude differences between EUI-64
(~= life of the device) and RFC4941 (1 day).


> a public address is one registered in DNS or some other external registry.
> I would argue that the address you use to reach facebook (and thereby
> couple address and identity) you have made that address a public address.
>

I don't think it's the same. The DNS comes with no expectation of privacy.
If you use an address to talk to Facebook, it's not public in that people
cannot look it up. Facebook knows it, just like everyone else whom you
choose to talk to knows the address you used to talk to them. Your ISP
might know it. The NSA might know it. But again, what's the threat model?
Facebook telling someone else what address you used? For what purpose, and
what would happen if it did?


> I think a "this prefix is dedicated to you" flag in the RA would be useful.
>
> that would likely require a change to the subnet model.
>

Really? How is it different from, say, 127.0.0.0/8, or the delegated subnet
on a CPE router?


> > That's NOT RECOMMENDED by draft-ietf-v6ops-host-addr-availability.
>
> it doesn't really matter if that draft says that. in reality there is a
> limit. an address can either fail silently (possibly with an ICMP) or
> explicitly.
>

I think failing silently is better.

--001a114dc69429f96705341fadd0
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, May 31, 2016 at 5:36 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"><span>&gt; Your statement does not mea=
n much unless you define &quot;public&quot;. The difference between RFC 494=
1 addresses and other addresses is not are that RFC 4941 addresses are not =
persistent.<br>
<br>
</span>IPv6 addresses are not persistent. they are all ephemeral. it is jus=
t a matter of the lifetime.<br></blockquote><div><br></div><div>Right, but =
there are many orders of magnitude differences between EUI-64 (~=3D life of=
 the device) and RFC4941 (1 day).</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">a public address is one registered in DNS or some other exter=
nal registry.<br>
I would argue that the address you use to reach facebook (and thereby coupl=
e address and identity) you have made that address a public address.<br></b=
lockquote><div><br></div><div>I don&#39;t think it&#39;s the same. The DNS =
comes with no expectation of privacy. If you use an address to talk to Face=
book, it&#39;s not public in that people cannot look it up. Facebook knows =
it, just like everyone else whom you choose to talk to knows the address yo=
u used to talk to them. Your ISP might know it. The NSA might know it. But =
again, what&#39;s the threat model? Facebook telling someone else what addr=
ess you used? For what purpose, and what would happen if it did?<br></div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span>I think a &quot;this p=
refix is dedicated to you&quot; flag in the RA would be useful.<br>
<br>
</span>that would likely require a change to the subnet model.<br></blockqu=
ote><div><br></div><div>Really? How is it different from, say, <a href=3D"h=
ttp://127.0.0.0/8" target=3D"_blank">127.0.0.0/8</a>, or the delegated subn=
et on a CPE router?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><s=
pan>&gt; That&#39;s NOT RECOMMENDED by draft-ietf-v6ops-host-addr-availabil=
ity.<br>
<br>
</span>it doesn&#39;t really matter if that draft says that. in reality the=
re is a limit. an address can either fail silently (possibly with an ICMP) =
or explicitly.<br></blockquote><div><br></div><div>I think failing silently=
 is better.</div></div></div></div>

--001a114dc69429f96705341fadd0--


From nobody Tue May 31 02:19:29 2016
Return-Path: <sthaug@nethelp.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 8328712D195 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 02:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level: 
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, 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 hKVU2hl8Uk6R for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 02:19:26 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with SMTP id D70B212D15D for <ipv6@ietf.org>; Tue, 31 May 2016 02:19:25 -0700 (PDT)
Received: (qmail 46605 invoked from network); 31 May 2016 09:19:23 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 31 May 2016 09:19:23 -0000
Date: Tue, 31 May 2016 11:19:23 +0200 (CEST)
Message-Id: <20160531.111923.74710755.sthaug@nethelp.no>
To: otroan@employees.org
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
From: sthaug@nethelp.no
In-Reply-To: <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org>
References: <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org> <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com> <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Y-j340X0JiyVHeMpAFP-KX7bL90>
Cc: 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, 31 May 2016 09:19:28 -0000

Minor comment:

> > Your statement does not mean much unless you define "public". The difference between RFC 4941 addresses and other addresses is not are that RFC 4941 addresses are not persistent.
> 
> IPv6 addresses are not persistent. they are all ephemeral. it is just a matter of the lifetime.

While that may be technically true, it certainly goes against the way
a lot of people *think* about IPv6 addresses, and could easily lead to
misunderstanding.

For example, I have a fixed /64 for the link to my home server, and
another fixed /64 (out of a /56) for my home LAN. The server has these
two /64 addresses statically configured on separate Ethernet interfaces.
To me it's not particularly useful to think of these addresses as
ephemeral.

Steinar Haug, AS2116


From nobody Tue May 31 06:23:49 2016
Return-Path: <alexandre.petrescu@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 4DCC712D7BB for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 06:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 XBYSEXwD0XAJ for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 06:23:44 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01DCE12D527 for <ipv6@ietf.org>; Tue, 31 May 2016 06:23:43 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u4VDNfwC013297 for <ipv6@ietf.org>; Tue, 31 May 2016 15:23:41 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5ED0920CF63 for <ipv6@ietf.org>; Tue, 31 May 2016 15:24:01 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4EE9E201C89 for <ipv6@ietf.org>; Tue, 31 May 2016 15:24:01 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u4VDNfnd021026 for <ipv6@ietf.org>; Tue, 31 May 2016 15:23:41 +0200
Subject: Re: I-D Action: draft-gont-6man-non-stable-iids-00.txt
To: ipv6@ietf.org
References: <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org> <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com> <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org> <20160531.111923.74710755.sthaug@nethelp.no>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <9b5cf44d-412f-8948-370c-fa0512259f9b@gmail.com>
Date: Tue, 31 May 2016 15:23:41 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <20160531.111923.74710755.sthaug@nethelp.no>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vkUwVkz3Ad26HPOG9sZM5pC0DSc>
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, 31 May 2016 13:23:47 -0000

Le 31/05/2016 à 11:19, sthaug@nethelp.no a écrit :
> Minor comment:
>
>>> Your statement does not mean much unless you define "public". The difference between RFC 4941 addresses and other addresses is not are that RFC 4941 addresses are not persistent.
>>
>> IPv6 addresses are not persistent. they are all ephemeral. it is just a matter of the lifetime.
>
> While that may be technically true, it certainly goes against the way
> a lot of people *think* about IPv6 addresses, and could easily lead to
> misunderstanding.
>
> For example, I have a fixed /64 for the link to my home server, and
> another fixed /64 (out of a /56) for my home LAN. The server has these
> two /64 addresses statically configured on separate Ethernet interfaces.
> To me it's not particularly useful to think of these addresses as
> ephemeral.

I think I agree.

Here too I have multiple addresses very persistent.

In the past there could have been some tendency to believe that in IPv6 
- contrary to IPv4 (nuance) - each address had a lifetime attached to 
it; because many IPv6 addresses in the initial deployments were 
auto-configured statelessly; that was a new - convenient at that time 
(nuance) - feature of IPv6, an argument persuading to migrate; it was 
better than having to install a DHCP server.  And these IPv6 addresses 
depend on the lifetime of the prefix in the RA.

But, since then, many IPv6 addresses are configured without receiving a 
prefix in an RA.  The manually configured addresses on linux last 
forever; there is no need to even type an argument to tell the lifetime 
is infinity.  Just type ifconfig eth0 1::1/64 and it's there forever.

(I dont know in cisco ios or bsd).

Alex

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


From nobody Tue May 31 08:55:10 2016
Return-Path: <talmi@marvell.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 EDF7F12B03F; Tue, 31 May 2016 08:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 LeYVwcYQP--w; Tue, 31 May 2016 08:54:58 -0700 (PDT)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (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 32ABC12B053; Tue, 31 May 2016 08:54:58 -0700 (PDT)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id u4VFpQiS028005; Tue, 31 May 2016 08:54:56 -0700
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0b-0016f401.pphosted.com with ESMTP id 237aumsvq1-6 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 31 May 2016 08:54:55 -0700
Received: from IL-EXCH02.marvell.com (10.4.102.221) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 31 May 2016 18:54:53 +0300
Received: from IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f]) by IL-EXCH02.marvell.com ([fe80::7dee:c960:1ac6:8c1f%20]) with mapi id 15.00.1104.000; Tue, 31 May 2016 18:54:53 +0300
From: Tal Mizrahi <talmi@marvell.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>
Subject: RE: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMThJCvw5mf6XUe954CmH3IV2Z/GIJVA///SB4CAADJs4P//1B0AgADL+gCAAAnXgIAMbgIA
Date: Tue, 31 May 2016 15:54:52 +0000
Message-ID: <d5f75f2fc2dd4e72a0de3e581667b9f6@IL-EXCH02.marvell.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com> <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com> <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com> <36D9FCF0-382C-4669-85A5-C782636A85BB@vmware.com> <D368BC04.19BA29%kreeger@cisco.com>
In-Reply-To: <D368BC04.19BA29%kreeger@cisco.com>
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: [10.4.102.210]
Content-Type: multipart/alternative; boundary="_000_d5f75f2fc2dd4e72a0de3e581667b9f6ILEXCH02marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-05-31_09:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1605310181
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/RpxC571-vccYyQ-Qsx5Z41hPow4>
Cc: "spring@ietf.org" <spring@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, 31 May 2016 15:55:07 -0000

--_000_d5f75f2fc2dd4e72a0de3e581667b9f6ILEXCH02marvellcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Stefano,

Going back to our original discussion, I believe we can conclude that the L=
4 Checksum may be interesting in two possible scenarios:


1.       The SRH is generated by the host. In this case the L4 Checksum is =
computed by the host based on the IP address of the last hop.

2.       The SRH is generated by the ingress node of the SR domain using an=
 IP tunnel. Specifically, if the tunnel encapsulation includes an L4 header=
 (e.g., VXLAN, VXLAN-GPE, Geneve, GUE), then (again) the ingress node compu=
tes the L4 Checksum based on the IP address of the last hop.

In both cases intermediate routers in the SR domain do not need to update t=
he Checksum, even though they update the destination IP address.

It would be great if some text would be added to the draft to clarify these=
 observations.

Cheers,
Tal.



From: Larry Kreeger (kreeger) [mailto:kreeger@cisco.com]
Sent: Monday, May 23, 2016 11:55 PM
To: Tal Mizrahi
Cc: draft-ietf-nvo3-geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe@tools.=
ietf.org; spring@ietf.org; 6man WG; nvo3@ietf.org; draft-ietf-6man-segment-=
routing-header@tools.ietf.org; Stefano Previdi (sprevidi)
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header

I agree with Robert and Jesse. - Larry

From: Jesse Gross <jgross@vmware.com<mailto:jgross@vmware.com>>
Date: Monday, May 23, 2016 at 1:19 PM
To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>, Tal Mizrah=
i <talmi@marvell.com<mailto:talmi@marvell.com>>
Cc: "draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@to=
ols.ietf.org>" <draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo=
3-geneve@tools.ietf.org>>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org<mailto=
:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>" <draft-ietf-nvo3-vxlan-gpe@tool=
s.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>>, "spring@ietf.=
org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, 6ma=
n WG <ipv6@ietf.org<mailto:ipv6@ietf.org>>, "nvo3@ietf.org<mailto:nvo3@ietf=
.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>>, "draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org<mailto:draft-ietf-6man-segment-routing-header@too=
ls.ietf.org>" <draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto=
:draft-ietf-6man-segment-routing-header@tools.ietf.org>>, "Stefano Previdi =
(sprevidi)" <sprevidi@cisco.com<mailto:sprevidi@cisco.com>>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>, <jgro=
ss@vmware.com<mailto:jgross@vmware.com>>
Resent-To: Larry Kreeger <kreeger@cisco.com<mailto:kreeger@cisco.com>>, <ur=
i.elzur@intel.com<mailto:uri.elzur@intel.com>>, <draft-ietf-6man-segment-ro=
uting-header@ietf.org<mailto:draft-ietf-6man-segment-routing-header@ietf.or=
g>>
Resent-Date: Monday, May 23, 2016 at 1:20 PM

I agree that I don't believe that there is anything in these drafts that pr=
ecludes the use of extension headers or segment routing - IP is simply the =
layer underneath that these protocols are building on. The figures are defi=
nitely just examples - they also show outer Ethernet headers, which is not =
a requirement.

I wouldn't want to add text specifically stating that extension headers are=
 permissible. It seems like that could lead to similar questions in the fut=
ure where one might wonder if other features of IP are allowed because one =
is explicitly listed and others are not, etc. In my opinion, the drafts are=
 about as clear as they can be on this point.

Jesse

On 5/23/16, 1:09 AM, "rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf=
 of Robert Raszuk" <rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf o=
f robert@raszuk.net<mailto:robert@raszuk.net>> wrote:

Hi Tal,

> In order to avoid ambiguity, it would be great if the
> authors could explicitly mention that IPv6 extension
> headers are permitted.

Well the drafts are complaint to RFC2119 (normative reference) so unless th=
e text excludes elements with MUST/MUST NOT - everything else defined in th=
e building blocks they (re)use is permitted.

However as you say perhaps for clarity what could be added to those drafts =
is a normative reference to IPv4 and IPv6 base RFCs.

Best,
R.


On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Robert,

That makes sense.
However, in this case the figures may be a bit confusing WRT the possible e=
xistence of extension headers. This confusion is what led to the discussion=
 in this thread about whether segment routing is possible with VXLAN/VXLAN-=
GPE/Geneve encapsulations.

In order to avoid ambiguity, it would be great if the authors could explici=
tly mention that IPv6 extension headers are permitted.

Regards,
Tal.

From:rraszuk@gmail.com<mailto:rraszuk@gmail.com> [mailto:rraszuk@gmail.com<=
mailto:rraszuk@gmail.com>] On Behalf Of Robert Raszuk
Sent: Monday, May 23, 2016 10:47 AM

To: Tal Mizrahi
Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo3@=
ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@tool=
s.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>; d=
raft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.ie=
tf.org>; Stefano Previdi (sprevidi)
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header

Hi Tal,

Indeed .. I saw the figures, but figures are non normative in any draft/rfc=
 unless text below specifically spells it out.

For example from vxlan-gpe:

"When the outer IP header is IPv4, VTEPs MUST set the DF bit."

Besides it is pretty challenging to add animation to the current draft form=
ats to illustrate all possibly allowed field values/combinations in any fig=
ure :)  Figures just illustrate one use example.

To me the current specs permit any value of IPv6 NxtHdr field as permitted =
in both encapsulations.

Best,
Robert.


On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Hi Robert,


>Where say in draft draft-quinn-vxlan-gpe do you see such statement that wo=
uld imply
> that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer to any=
 other type
> of extension header further followed by UDP ?


The following text is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:

      Outer IPv6 Header:
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Version| Traffic Class |           Flow Label                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Payload Length        | NxtHdr=3D17(UDP)|   Hop Limit   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |


There is a similar figure in draft-ietf-nvo3-geneve.

Best regards,
Tal.

From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] On =
Behalf Of Robert Raszuk
Sent: Monday, May 23, 2016 10:29 AM
To: Tal Mizrahi
Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo3@=
ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@tool=
s.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>; d=
raft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.ie=
tf.org>; Stefano Previdi (sprevidi)

Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routin=
g-header

Hi Tal,

> drafts seem to imply

Where say in draft draft-quinn-vxlan-gpe do you see such statement that wou=
ld imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer=
 to any other type of extension header further followed by UDP ?

Thx,
R.


On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com<mailto:talm=
i@marvell.com>> wrote:
Dear Authors of VXLAN-GPE / Geneve,

I am reiterating on this question, as I haven't seen a response yet:

Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.

Thanks,
Tal.



>-----Original Message-----
>From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] On=
 Behalf Of Tal Mizrahi
>Sent: Tuesday, May 17, 2016 12:09 PM
>To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
>geneve@tools.ietf.org<mailto:geneve@tools.ietf.org>; draft-ietf-nvo3-vxlan=
-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>
>Cc: spring@ietf.org<mailto:spring@ietf.org>; nvo3@ietf.org<mailto:nvo3@iet=
f.org>; 6man WG; draft-ietf-6man-segment-
>routing-header@tools.ietf.org<mailto:routing-header@tools.ietf.org>
>Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
>routing-header
>
>Stefano,
>
>If I understand your point correctly:
>IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, since
>these encapsulations do not currently allow the use of IPv6 extension
>headers.
>
>I wonder if the authors of VXLAN-GPE and Geneve have considered the use of
>segment routing.
>
>Thanks,
>Tal.
>
>
>
>>-----Original Message-----
>>From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:sprevi=
di@cisco.com>]
>>Sent: Tuesday, May 17, 2016 10:41 AM
>>To: Tom Herbert
>>Cc: Tal Mizrahi; 6man WG; spring@ietf.org<mailto:spring@ietf.org>;
>>draft-ietf-6man-segment-routing- header@tools.ietf.org<mailto:header@tool=
s.ietf.org>
>>Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
>>header
>>
>>
>>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com<mailto:to=
m@herbertland.com>>
>wrote:
>>>
>>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com<mailto:=
talmi@marvell.com>>
>>wrote:
>>>>> it's all about IP, not layer-2.
>>>>>
>>>>> s.
>>>>
>>>> Right. However, it appears that at least in some cases a VXLAN VTEP
>>>> will
>>use SR. It certainly may be the case in SFC use cases (see Section 2.3
>>in draft- ietf-spring-ipv6-use-cases).
>>>>
>>>
>>> draft-ietf-6man-segment-routing-header mentions that the packet is
>>> encapsulated
>>
>>
>>into an outer ipv6 header which makes it a layer-3 encap.
>>
>>
>>> , but I don't think it is explicit as to exact encapsulation format
>>> (I suppose simple ip6ip6 is implied).
>>
>>
>>see section 2.2
>>
>>
>>> But, it
>>> seems like any of several encapsulation techniques could work (VXLAN,
>>
>>
>>I have some problems to understand where to fit an extension header
>>into a vxlan encap...
>>
>>
>>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
>>> to do SR is already doing tunneling it seems reasonable to me to only
>>> have one layer of encapsulation. Maybe this should be clarified in
>>> the draft?
>>
>>
>>the draft is about IPv6 extension header and more precisely a new type
>>of the routing extension header defined in rfc2460. That's the context.
>>
>>
>>s.
>>
>>
>>
>>
>>>
>>> Tom
>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:sp=
revidi@cisco.com>]
>>>>> Sent: Monday, May 16, 2016 2:24 PM
>>>>> To: Tal Mizrahi
>>>>> Cc: Ole Tr=F8an;
>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft-ie=
tf-6man-segment-routing-header@tools.ietf.org>;
>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>> Subject: Re: [spring] L4 Checksum and
>>>>> draft-ietf-6man-segment-routing- header
>>>>>
>>>>>
>>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com<mailto:t=
almi@marvell.com>> wrote:
>>>>>>
>>>>>> Hi Stefano,
>>>>>>
>>>>>> Thanks again for the prompt response.
>>>>>>
>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>> is removed and the packet continues  its journey like nothing
>happened.
>>>>>>
>>>>>> So VXLAN is off the table?
>>>>>
>>>>>
>>>>> it's all about IP, not layer-2.
>>>>>
>>>>> s.
>>>>>
>>>>>
>>>>>> It would be worthwhile to clarify this in the draft. If you have a
>>>>>> specific
>>>>> encapsulation in mind, it would be great if the draft would specify i=
t.
>>>>>>
>>>>>> Thanks,
>>>>>> Tal.
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:=
sprevidi@cisco.com>]
>>>>>>> Sent: Monday, May 16, 2016 2:13 PM
>>>>>>> To: Tal Mizrahi
>>>>>>> Cc: Ole Tr=F8an;
>>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft-=
ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com<mailto=
:talmi@marvell.com>>
>>wrote:
>>>>>>>>
>>>>>>>> Hi Stefano,
>>>>>>>>
>>>>>>>> Thanks for the responses.
>>>>>>>>
>>>>>>>>> exactly.
>>>>>>>>>
>>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>>>>> encapsulation so clearly there's no L4 involved here.
>>>>>>>>>
>>>>>>>>> s.
>>>>>>>>
>>>>>>>> Two questions:
>>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
>>>>>>>> involved,
>>right?
>>>>>>>
>>>>>>>
>>>>>>> See below.
>>>>>>>
>>>>>>>
>>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
>>>>>>>> host cannot
>>>>>>> send an IPv6 packet with an SRH? The current draft says:
>>>>>>>>
>>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
>>>>>>>> its
>>>>>>>> IPv6 and Segment Routing Headers.  This include either:
>>>>>>>>
>>>>>>>>    A host originating an IPv6 packet.
>>>>>>>>
>>>>>>>>    An SR domain ingress router encapsulating a received IPv6 packe=
t
>>>>>>>>    into an outer IPv6 header followed by an SRH.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Will appreciate if you can clarify that.
>>>>>>>
>>>>>>>
>>>>>>> ok, two cases:
>>>>>>>
>>>>>>> 1. the SRH is inserted at the source.
>>>>>>> the source originates the packet, the ipv6 header and  the SRH.
>>>>>>> The source computes L4 checksum taking into  account the whole
>>IPv6+SRH.
>>>>>>> Here, theres' nothing new  compared to rfc2460.
>>>>>>>
>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>> is removed and the packet continues  its journey like nothing
>happened.
>>>>>>>
>>>>>>> s.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Tal.
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailt=
o:sprevidi@cisco.com>]
>>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
>>>>>>>>> To: Ole Tr=F8an; Tal Mizrahi
>>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:=
draft-ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org<mailto:otroan@=
employees.org> wrote:
>>>>>>>>>>
>>>>>>>>>> Tal,
>>>>>>>>>>
>>>>>>>>>>> [Apologies if this issue has been discussed before.]
>>>>>>>>>>>
>>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an 'SR
>>>>>>>>>>> Segment
>>>>>>>>> Endpoint Node' updates the Destination IP address.
>>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>>>>>>>>
>>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
>>>>>>>>>>> Otherwise, the
>>>>>>>>> L4 Checksum may be located in a pretty deep location.
>>>>>>>>>>> Speaking from a chip vendor's perspective this may be a problem=
.
>>>>>>>>>>
>>>>>>>>>> From RFC2460, RH0:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>   o  If the IPv6 packet contains a Routing header, the Destinati=
on
>>>>>>>>>>      Address used in the pseudo-header is that of the final
>>>>>>>>>>      destination.  At the originating node, that address will be=
 in
>>>>>>>>>>      the last element of the Routing header; at the recipient(s)=
,
>>>>>>>>>>      that address will be in the Destination Address field of th=
e
>>>>>>>>>>      IPv6 header.
>>>>>>>>>>
>>>>>>>>>> I would expect SR would work the same.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> exactly.
>>>>>>>>>
>>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>>>>> encapsulation so clearly there's no L4 involved here.
>>>>>>>>>
>>>>>>>>> s.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>> Ole
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list ipv6@ietf.org<mailto:ipv6@ietf.or=
g> Administrative
>>>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>
>_______________________________________________
>nvo3 mailing list
>nvo3@ietf.org<mailto:nvo3@ietf.org>
>https://www.ietf.org/mailman/listinfo/nvo3
_______________________________________________
spring mailing list
spring@ietf.org<mailto:spring@ietf.org>
https://www.ietf.org/mailman/listinfo/spring




--_000_d5f75f2fc2dd4e72a0de3e581667b9f6ILEXCH02marvellcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1316488622;
	mso-list-type:hybrid;
	mso-list-template-ids:2048576200 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi Stefano,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Going back to our origina=
l discussion, I believe we can conclude that the L4 Checksum may be interes=
ting in two possible scenarios:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso=
-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D">The SRH is generated by the host. In this case the L4 Checksum is c=
omputed by the host based on the IP address of the last
 hop.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso=
-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"font=
-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D">The SRH is generated by the ingress node of the SR domain using an =
IP tunnel. Specifically, if the tunnel encapsulation includes
 an L4 header (e.g., VXLAN, VXLAN-GPE, Geneve, GUE), then (again) the ingre=
ss node computes the L4 Checksum based on the IP address of the last hop.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">In both cases intermediat=
e routers in the SR domain do not need to update the Checksum, even though =
they update the destination IP address.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It would be great if some=
 text would be added to the draft to clarify these observations.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Cheers,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Tal.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Larry Kr=
eeger (kreeger) [mailto:kreeger@cisco.com]
<br>
<b>Sent:</b> Monday, May 23, 2016 11:55 PM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> draft-ietf-nvo3-geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe=
@tools.ietf.org; spring@ietf.org; 6man WG; nvo3@ietf.org; draft-ietf-6man-s=
egment-routing-header@tools.ietf.org; Stefano Previdi (sprevidi)<br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I agree with Robert and Jes=
se. - Larry<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:
</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;;color:black">Jesse Gross &lt;<a href=3D"mailto:jgros=
s@vmware.com">jgross@vmware.com</a>&gt;<br>
<b>Date: </b>Monday, May 23, 2016 at 1:19 PM<br>
<b>To: </b>Robert Raszuk &lt;<a href=3D"mailto:robert@raszuk.net">robert@ra=
szuk.net</a>&gt;, Tal Mizrahi &lt;<a href=3D"mailto:talmi@marvell.com">talm=
i@marvell.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:draft-ietf-nvo3-geneve@tools.ietf.org">d=
raft-ietf-nvo3-geneve@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-=
ietf-nvo3-geneve@tools.ietf.org">draft-ietf-nvo3-geneve@tools.ietf.org</a>&=
gt;, &quot;<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org">draf=
t-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org">draft-ietf=
-nvo3-vxlan-gpe@tools.ietf.org</a>&gt;, &quot;<a href=3D"mailto:spring@ietf=
.org">spring@ietf.org</a>&quot; &lt;<a href=3D"mailto:spring@ietf.org">spri=
ng@ietf.org</a>&gt;, 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf=
.org</a>&gt;,
 &quot;<a href=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:nvo3@ietf.org">nvo3@ietf.org</a>&gt;, &quot;<a href=3D"mailto:dr=
aft-ietf-6man-segment-routing-header@tools.ietf.org">draft-ietf-6man-segmen=
t-routing-header@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-=
6man-segment-routing-header@tools.ietf.org">draft-ietf-6man-segment-routing=
-header@tools.ietf.org</a>&gt;,
 &quot;Stefano Previdi (sprevidi)&quot; &lt;<a href=3D"mailto:sprevidi@cisc=
o.com">sprevidi@cisco.com</a>&gt;<br>
<b>Subject: </b>Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<br>
<b>Resent-From: </b>&lt;<a href=3D"mailto:alias-bounces@ietf.org">alias-bou=
nces@ietf.org</a>&gt;, &lt;<a href=3D"mailto:jgross@vmware.com">jgross@vmwa=
re.com</a>&gt;<br>
<b>Resent-To: </b>Larry Kreeger &lt;<a href=3D"mailto:kreeger@cisco.com">kr=
eeger@cisco.com</a>&gt;, &lt;<a href=3D"mailto:uri.elzur@intel.com">uri.elz=
ur@intel.com</a>&gt;, &lt;<a href=3D"mailto:draft-ietf-6man-segment-routing=
-header@ietf.org">draft-ietf-6man-segment-routing-header@ietf.org</a>&gt;<b=
r>
<b>Resent-Date: </b>Monday, May 23, 2016 at 1:20 PM<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I agree that I don&#8217;t =
believe that there is anything in these drafts that precludes the use of ex=
tension headers or segment routing &#8211; IP is simply the layer underneat=
h
 that these protocols are building on. The figures are definitely just exam=
ples &#8211; they also show outer Ethernet headers, which is not a requirem=
ent.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I wouldn&#8217;t want to ad=
d text specifically stating that extension headers are permissible. It seem=
s like that could lead to similar questions in the future where
 one might wonder if other features of IP are allowed because one is explic=
itly listed and others are not, etc. In my opinion, the drafts are about as=
 clear as they can be on this point.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Jesse<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">On 5/23/16, 1:09 AM, &quot;=
<a href=3D"mailto:rraszuk@gmail.com">rraszuk@gmail.com</a> on behalf of Rob=
ert Raszuk&quot; &lt;<a href=3D"mailto:rraszuk@gmail.com">rraszuk@gmail.com=
</a>
 on behalf of <a href=3D"mailto:robert@raszuk.net">robert@raszuk.net</a>&gt=
; wrote:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<blockquote style=3D"border:none;border-left:solid #B5C4DF 4.5pt;padding:0c=
m 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id=3D"MAC_OUTLOOK_ATTR=
IBUTION_BLOCKQUOTE">
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black">Hi Tal,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt; In order to avoid am=
biguity, it would be great if the&nbsp;</span><span style=3D"font-family:&q=
uot;Arial&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt; authors could explic=
itly mention that IPv6 extension&nbsp;</span><span style=3D"font-family:&qu=
ot;Arial&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt; headers are permitte=
d.</span><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black">Well the drafts are complaint to RFC2119 (norm=
ative reference) so unless the text excludes elements with MUST/MUST NOT - =
everything else defined in the building blocks they (re)use
 is permitted.&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black">However as you say perhaps for clarity what co=
uld be added to those drafts is a normative reference to IPv4 and IPv6 base=
 RFCs.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black">Best,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black">R.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,&quot;s=
ans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">On Mon, May 23, 2016 at 9:5=
4 AM, Tal Mizrahi &lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank=
">talmi@marvell.com</a>&gt; wrote:<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Hi Robert,</span><span style=3D"color:b=
lack"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">That makes sense.</span><span style=3D"=
color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">However, in this case the figures may b=
e a bit confusing WRT the possible existence of extension
 headers. This confusion is what led to the discussion in this thread about=
 whether segment routing is possible with VXLAN/VXLAN-GPE/Geneve encapsulat=
ions.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">In order to avoid ambiguity, it would b=
e great if the authors could explicitly mention that IPv6
 extension headers are permitted.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regards,</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Tal.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
><a href=3D"mailto:rraszuk@gmail.com" target=3D"_blank">rraszuk@gmail.com</=
a>
 [mailto:<a href=3D"mailto:rraszuk@gmail.com" target=3D"_blank">rraszuk@gma=
il.com</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:47 AM</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>;
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a hr=
ef=3D"mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=
=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">
draft-ietf-nvo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)<br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Hi Tal,</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Indeed .. I saw the figures, but figures are non normative i=
n any draft/rfc unless text below specifically spells it out.&nbsp;</span><=
span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">For example from vxlan-gpe:&nbsp;</span><span style=3D"color=
:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&quot;When the outer IP header is IPv4, VTEPs MUST set the D=
F bit.&quot;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Besides it is pretty challenging to add animation to the cur=
rent draft formats to illustrate all possibly allowed field
 values/combinations in any figure :) &nbsp;Figures just illustrate one use=
 example.&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">To me the current specs permit any value of IPv6 NxtHdr fiel=
d as permitted in both encapsulations.</span><span style=3D"color:black"><o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Best,</span><span style=3D"color:black"><o:p></o:p></span></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Robert.</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">On Mon, May 23, 2016 at 9:35 AM, Tal M=
izrahi &lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@mar=
vell.com</a>&gt; wrote:<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Hi Robert,</span><span style=3D"color:b=
lack"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&gt;Where say in draft draft-quinn-vxla=
n-gpe do you see such statement that would imply
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&gt; that v6 NxtHdr must be only equal =
to 17 (UDP) and not be a pointer to any other type
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&gt; of extension header further follow=
ed by UDP ?</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">The following text is from Figure 4 in =
draft-ietf-nvo3-vxlan-gpe:</span><span style=3D"color:black"><o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Outer IPv6 Header:</span><s=
pan style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Version| Traffic Class |&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Flow Label&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; |</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Payload Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; | NxtHdr=3D17(UDP)|&nbsp;&nbsp; Hop Limit&nbsp;&nbsp; |</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-=
&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#43;-&#4=
3;-&#43;-&#43;-&#43;</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;|</span><span style=3D"color=
:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">There is a similar figure in draft-ietf=
-nvo3-geneve.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Best regards,</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Tal.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> nvo3
 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_blank">nvo3-bo=
unces@ietf.org</a>]
<b>On Behalf Of </b>Robert Raszuk<br>
<b>Sent:</b> Monday, May 23, 2016 10:29 AM<br>
<b>To:</b> Tal Mizrahi<br>
<b>Cc:</b> <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf=
.org</a>; 6man WG;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a>;
<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a>; <a hr=
ef=3D"mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org" target=
=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>; <a href=3D"mailt=
o:draft-ietf-nvo3-geneve@tools.ietf.org" target=3D"_blank">
draft-ietf-nvo3-geneve@tools.ietf.org</a>; Stefano Previdi (sprevidi)</span=
><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><br>
<b>Subject:</b> Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment=
-routing-header<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Hi Tal,</span><span style=3D"color:black"><o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&gt;&nbsp;</span><span style=3D"font-size:9.5pt;font-family:=
&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">drafts seem to imply<=
/span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Where say in draft&nbsp;draft-quinn-vxlan-gpe do you see suc=
h statement that would imply that v6 NxtHdr must be only equal
 to 17 (UDP) and not be a pointer to any other type of extension header fur=
ther followed by UDP ?&nbsp;</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">Thx,<br>
R.</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Arial&quot;,&quot;sans-serif&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">On Mon, May 23, 2016 at 7:50 AM, Tal M=
izrahi &lt;<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@mar=
vell.com</a>&gt; wrote:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">Dear Authors of VXLAN-GPE / Geneve,<br=
>
<br>
I am reiterating on this question, as I haven't seen a response yet:<br>
<br>
Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? The=
 current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension header=
s are currently not supported.<br>
<br>
Thanks,<br>
Tal.<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><br>
<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: nvo3 [mailto:<a href=3D"mailto:nvo3-bounces@ietf.org" target=3D"_=
blank">nvo3-bounces@ietf.org</a>] On Behalf Of Tal Mizrahi<br>
&gt;Sent: Tuesday, May 17, 2016 12:09 PM<br>
&gt;To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-<br>
&gt;<a href=3D"mailto:geneve@tools.ietf.org" target=3D"_blank">geneve@tools=
.ietf.org</a>;
<a href=3D"mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org" target=3D"_blan=
k">draft-ietf-nvo3-vxlan-gpe@tools.ietf.org</a><br>
&gt;Cc: <a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.or=
g</a>; <a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">
nvo3@ietf.org</a>; 6man WG; draft-ietf-6man-segment-<br>
&gt;<a href=3D"mailto:routing-header@tools.ietf.org" target=3D"_blank">rout=
ing-header@tools.ietf.org</a><br>
&gt;Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-<b=
r>
&gt;routing-header<br>
&gt;<br>
&gt;Stefano,<br>
&gt;<br>
&gt;If I understand your point correctly:<br>
&gt;IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sin=
ce<br>
&gt;these encapsulations do not currently allow the use of IPv6 extension<b=
r>
&gt;headers.<br>
&gt;<br>
&gt;I wonder if the authors of VXLAN-GPE and Geneve have considered the use=
 of<br>
&gt;segment routing.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;Tal.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;-----Original Message-----<br>
&gt;&gt;From: Stefano Previdi (sprevidi) [mailto:<a href=3D"mailto:sprevidi=
@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;Sent: Tuesday, May 17, 2016 10:41 AM<br>
&gt;&gt;To: Tom Herbert<br>
&gt;&gt;Cc: Tal Mizrahi; 6man WG; <a href=3D"mailto:spring@ietf.org" target=
=3D"_blank">spring@ietf.org</a>;<br>
&gt;&gt;draft-ietf-6man-segment-routing- <a href=3D"mailto:header@tools.iet=
f.org" target=3D"_blank">
header@tools.ietf.org</a><br>
&gt;&gt;Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routi=
ng-<br>
&gt;&gt;header<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On May 16, 2016, at 7:10 PM, Tom Herbert &lt;<a href=3D"mailto=
:tom@herbertland.com" target=3D"_blank">tom@herbertland.com</a>&gt;<br>
&gt;wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi &lt;<a href=3D"ma=
ilto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt; it&#8217;s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Right. However, it appears that at least in some cases a V=
XLAN VTEP<br>
&gt;&gt;&gt;&gt; will<br>
&gt;&gt;use SR. It certainly may be the case in SFC use cases (see Section =
2.3<br>
&gt;&gt;in draft- ietf-spring-ipv6-use-cases).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; draft-ietf-6man-segment-routing-header mentions that the packe=
t is<br>
&gt;&gt;&gt; encapsulated<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;into an outer ipv6 header which makes it a layer-3 encap.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; , but I don't think it is explicit as to exact encapsulation f=
ormat<br>
&gt;&gt;&gt; (I suppose simple ip6ip6 is implied).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;see section 2.2<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; But, it<br>
&gt;&gt;&gt; seems like any of several encapsulation techniques could work =
(VXLAN,<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;I have some problems to understand where to fit an extension header=
<br>
&gt;&gt;into a vxlan encap&#8230;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that =
wants<br>
&gt;&gt;&gt; to do SR is already doing tunneling it seems reasonable to me =
to only<br>
&gt;&gt;&gt; have one layer of encapsulation. Maybe this should be clarifie=
d in<br>
&gt;&gt;&gt; the draft?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;the draft is about IPv6 extension header and more precisely a new t=
ype<br>
&gt;&gt;of the routing extension header defined in rfc2460. That&#8217;s th=
e context.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Tom<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a href=3D"ma=
ilto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<br>
&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:24 PM<br>
&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=F8an;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-routing-head=
er@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_blank">s=
pring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 1:19 PM, Tal Mizrahi &lt;<a hr=
ef=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a>&gt;=
 wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks again for the prompt response.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the&nbsp; packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation&n=
bsp; (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues&nbsp; its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; So VXLAN is off the table?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; it&#8217;s all about IP, not layer-2.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; It would be worthwhile to clarify this in the draf=
t. If you have a<br>
&gt;&gt;&gt;&gt;&gt;&gt; specific<br>
&gt;&gt;&gt;&gt;&gt; encapsulation in mind, it would be great if the draft =
would specify it.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mailto:<a hr=
ef=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.com</a>]<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 2:13 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: Ole Tr=F8an;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:draft-ietf-6man-segment-rout=
ing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" target=3D"_=
blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- header<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 16, 2016, at 11:04 AM, Tal Mizrahi &lt;=
<a href=3D"mailto:talmi@marvell.com" target=3D"_blank">talmi@marvell.com</a=
>&gt;<br>
&gt;&gt;wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Stefano,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the responses.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there&#8217;s=
 no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Two questions:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. What if the encapsulation is VXLAN? L4 =
would still be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; involved,<br>
&gt;&gt;right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; See below.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. When you say 'assumes encapsulation', d=
oes it mean that a<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; host cannot<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; send an IPv6 packet with an SRH? The current d=
raft says:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; A Source SR Node can be any node originati=
ng an IPv6 packet with<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; its<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; IPv6 and Segment Routing Headers.&nbsp; Th=
is include either:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; A host originating an IPv6 pa=
cket.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; An SR domain ingress router e=
ncapsulating a received IPv6 packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; into an outer IPv6 header fol=
lowed by an SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Will appreciate if you can clarify that.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ok, two cases:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 1. the SRH is inserted at the source.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the source originates the packet, the ipv6 hea=
der and&nbsp; the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The source computes L4 checksum taking into&nb=
sp; account the whole<br>
&gt;&gt;IPv6&#43;SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Here, theres&#8217; nothing new&nbsp; compared=
 to rfc2460.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 2. the SRH is originated by the ingress node o=
f the SR domain.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; This is done by encapsulating the packet into =
a outer<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; (additional) ipv6 header followed by an SRH. T=
his is L3<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation and no L4 checksum is involved. =
When the&nbsp; packet<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; leaves the SR tunnel the outer encapsulation&n=
bsp; (including the SRH)<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is removed and the packet continues&nbsp; its =
journey like nothing<br>
&gt;happened.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: Stefano Previdi (sprevidi) [mail=
to:<a href=3D"mailto:sprevidi@cisco.com" target=3D"_blank">sprevidi@cisco.c=
om</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Monday, May 16, 2016 11:59 AM<br=
>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Ole Tr=F8an; Tal Mizrahi<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:draft-ietf-6man-=
segment-routing-header@tools.ietf.org" target=3D"_blank">
draft-ietf-6man-segment-routing-header@tools.ietf.org</a>;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:spring@ietf.org" tar=
get=3D"_blank">spring@ietf.org</a>; 6man WG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [spring] L4 Checksum and<=
br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; draft-ietf-6man-segment-routing- heade=
r<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On May 15, 2016, at 8:06 PM, <a hr=
ef=3D"mailto:otroan@employees.org" target=3D"_blank">
otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Tal,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; [Apologies if this issue has b=
een discussed before.]<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; According to draft-ietf-6man-s=
egment-routing-header, an &#8216;SR<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Segment<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Endpoint Node&#8217; updates the Desti=
nation IP address.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Therefore, it must also update=
 the Layer 4 Checksum, right?<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I wonder if there is an upper =
bound on the size of the SRH.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Otherwise, the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; L4 Checksum may be located in a pretty=
 deep location.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Speaking from a chip vendor&#8=
217;s perspective this may be a problem.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; From RFC2460, RH0:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;o&nbsp; If the IPv6 pa=
cket contains a Routing header, the Destination<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; Address used i=
n the pseudo-header is that of the final<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; destination.&n=
bsp; At the originating node, that address will be in<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; the last eleme=
nt of the Routing header; at the recipient(s),<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; that address w=
ill be in the Destination Address field of the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; IPv6 header.<b=
r>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I would expect SR would work the s=
ame.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; exactly.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Moreover, draft-ietf-6man-segment-rout=
ing-header assumes<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; encapsulation so clearly there&#8217;s=
 no L4 involved here.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; s.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Ole<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;&gt;&gt;&gt; IETF IPv6 working group mailing list <a href=3D"mailto:ipv=
6@ietf.org" target=3D"_blank">
ipv6@ietf.org</a> Administrative<br>
&gt;&gt;&gt;&gt; Requests: <a href=3D"https://www.ietf.org/mailman/listinfo=
/ipv6" target=3D"_blank">
https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt;&gt;&gt;&gt; ----------------------------------------------------------=
----------<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;nvo3 mailing list<br>
&gt;<a href=3D"mailto:nvo3@ietf.org" target=3D"_blank">nvo3@ietf.org</a><br=
>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/nvo3" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/nvo3</a><o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">______________________________________=
_________<br>
spring mailing list<br>
<a href=3D"mailto:spring@ietf.org" target=3D"_blank">spring@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/spring" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/spring</a><o:p></o:p></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_d5f75f2fc2dd4e72a0de3e581667b9f6ILEXCH02marvellcom_--


From nobody Tue May 31 09:02:48 2016
Return-Path: <sprevidi@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 474D712D7FE; Tue, 31 May 2016 09:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 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.426, 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 bq2kzmSywLVr; Tue, 31 May 2016 09:02:42 -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 1713412D610; Tue, 31 May 2016 09:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18065; q=dns/txt; s=iport; t=1464710561; x=1465920161; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QfQPj7a+Zde9BvekMbL0revFNBqgy5slxPLuRdoysYg=; b=G6tY9hoE+U2o8cLrouwAeVYKdS+NuW8Ak1Yd9mzfoWEXGT2gvs/y00Qd +oKLutoIDtV9hEU/Tb4ZBHmHpdu0+4nEOnEe0VP0dPjx6mtOVYpQONo2J z5Vi/ngb8wKezk9xv9eb4oz2f5UvAarMvvAWZaH/8A/w5c3VDoQF16uxo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D3AQBftE1X/4oNJK1bgzyBUwauFYtvA?= =?us-ascii?q?Q2BeoYRAoE+OBQBAQEBAQEBZSeERQEBAQMBeQUHBAIBCBEDAQEBARUSByERFAk?= =?us-ascii?q?IAgQOBYgVAw8IuXMNhB8BAQEBAQEBAQEBAQEBAQEBAQEBAQEchieBdwiBS4EDg?= =?us-ascii?q?kOBWiM/gnWCLgWOHYlnMwGId4MvgXmBaY0zhjOBMYdnAR4BAUKDbW6IcwEGIB9?= =?us-ascii?q?/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,396,1459814400"; d="scan'208";a="279981446"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 May 2016 16:02:39 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u4VG2dDo020533 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 31 May 2016 16:02:39 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 31 May 2016 12:02:38 -0400
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.009; Tue, 31 May 2016 12:02:38 -0400
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Tal Mizrahi <talmi@marvell.com>
Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Topic: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Thread-Index: AQHRtMWkQ84SBd4Z00OPA2d5Y/ic9p/GZ/OAgAACKoCAAARfAIAAy/oAgAAJ14CADD6+AIAAAh4A
Date: Tue, 31 May 2016 16:02:38 +0000
Message-ID: <5A098FFC-5D34-4E4C-9231-4783077B7D05@cisco.com>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com> <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org> <ECB16B90-392C-4C98-B3EA-86050AE2BEBA@cisco.com> <5dc56935eba94c2390120244564f9b21@IL-EXCH02.marvell.com> <A5EFDE4C-BE25-4F5C-B176-E63740E94F4B@cisco.com> <ed76a19f5995465e8f4eddcba5d0c95c@IL-EXCH02.marvell.com> <0551686F-F1D2-4C34-81C8-530F1BEE1BDF@cisco.com> <5d889e7013b44b27ae1e75cf7ea2dd22@IL-EXCH02.marvell.com> <CALx6S35iChUWbF_Qp6Sf2s5ipPDqkNfVB1k0i=45Nq5q4OnS_w@mail.gmail.com> <3549ABBE-9828-42D2-A056-851432487E2E@cisco.com> <1e13d2e32b2448af94bf23d5acf17740@IL-EXCH02.marvell.com> <569a4067fd1f45dd85d60e983be69b90@IL-EXCH02.marvell.com> <CA+b+ER=zQbceetmYE-ehVczCVTcx0tawEZb1bdRB9ZktdfW7ZA@mail.gmail.com> <bb99730deb8348bcac4f5c433e88d435@IL-EXCH02.marvell.com> <CA+b+ERkQf5ezEZdP=+U0MBHHSX7cKVnxudVKCrJ0BX+5HBq1oQ@mail.gmail.com> <1c27bb3513bc48889ec310e8d143784c@IL-EXCH02.marvell.com> <CA+b+ERmsCQbjcGLK4sNo+B51pZyXTqFW6On_CeTbYq4gSjHwRw@mail.gmail.com> <36D9FCF0-382C-4669-85A5-C782636A85BB@vmware.com> <D368BC04.19BA29%kreeger@cisco.com> <d5f75f2fc2dd4e72a0de3e581667b9f6@IL-EXCH02.marvell.com>
In-Reply-To: <d5f75f2fc2dd4e72a0de3e581667b9f6@IL-EXCH02.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.201.156]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <764A43FFFC5A82498A4729D56E40B12D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/llDCu_ZoiImH8bcCdFwy17wdUys>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@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, 31 May 2016 16:02:46 -0000

> On May 31, 2016, at 5:54 PM, Tal Mizrahi <talmi@marvell.com> wrote:
>=20
> Hi Stefano,
>=20
> Going back to our original discussion, I believe we can conclude that the=
 L4 Checksum may be interesting in two possible scenarios:
>=20
>=20
> 1.       The SRH is generated by the host. In this case the L4 Checksum i=
s computed by the host based on the IP address of the last hop.
>=20
> 2.       The SRH is generated by the ingress node of the SR domain using =
an IP tunnel. Specifically, if the tunnel encapsulation includes an L4 head=
er (e.g., VXLAN, VXLAN-GPE, Geneve, GUE), then (again) the ingress node com=
putes the L4 Checksum based on the IP address of the last hop.
>=20
> In both cases intermediate routers in the SR domain do not need to update=
 the Checksum, even though they update the destination IP address.


it can be simplified by stating that any SRH that is inserted in transit MU=
ST be removed prior to deliver the packet to the final destination.

All other cases implies that the source is inserting the SRH, in which case=
 the checksum is consistent.


s.



>=20
> It would be great if some text would be added to the draft to clarify the=
se observations.
>=20
> Cheers,
> Tal.
>=20
>=20
>=20
> From: Larry Kreeger (kreeger) [mailto:kreeger@cisco.com]
> Sent: Monday, May 23, 2016 11:55 PM
> To: Tal Mizrahi
> Cc: draft-ietf-nvo3-geneve@tools.ietf.org; draft-ietf-nvo3-vxlan-gpe@tool=
s.ietf.org; spring@ietf.org; 6man WG; nvo3@ietf.org; draft-ietf-6man-segmen=
t-routing-header@tools.ietf.org; Stefano Previdi (sprevidi)
> Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-rout=
ing-header
>=20
> I agree with Robert and Jesse. - Larry
>=20
> From: Jesse Gross <jgross@vmware.com<mailto:jgross@vmware.com>>
> Date: Monday, May 23, 2016 at 1:19 PM
> To: Robert Raszuk <robert@raszuk.net<mailto:robert@raszuk.net>>, Tal Mizr=
ahi <talmi@marvell.com<mailto:talmi@marvell.com>>
> Cc: "draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@=
tools.ietf.org>" <draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-n=
vo3-geneve@tools.ietf.org>>, "draft-ietf-nvo3-vxlan-gpe@tools.ietf.org<mail=
to:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>" <draft-ietf-nvo3-vxlan-gpe@to=
ols.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>>, "spring@iet=
f.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:spring@ietf.org>>, 6=
man WG <ipv6@ietf.org<mailto:ipv6@ietf.org>>, "nvo3@ietf.org<mailto:nvo3@ie=
tf.org>" <nvo3@ietf.org<mailto:nvo3@ietf.org>>, "draft-ietf-6man-segment-ro=
uting-header@tools.ietf.org<mailto:draft-ietf-6man-segment-routing-header@t=
ools.ietf.org>" <draft-ietf-6man-segment-routing-header@tools.ietf.org<mail=
to:draft-ietf-6man-segment-routing-header@tools.ietf.org>>, "Stefano Previd=
i (sprevidi)" <sprevidi@cisco.com<mailto:sprevidi@cisco.com>>
> Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-rout=
ing-header
> Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>, <jg=
ross@vmware.com<mailto:jgross@vmware.com>>
> Resent-To: Larry Kreeger <kreeger@cisco.com<mailto:kreeger@cisco.com>>, <=
uri.elzur@intel.com<mailto:uri.elzur@intel.com>>, <draft-ietf-6man-segment-=
routing-header@ietf.org<mailto:draft-ietf-6man-segment-routing-header@ietf.=
org>>
> Resent-Date: Monday, May 23, 2016 at 1:20 PM
>=20
> I agree that I don't believe that there is anything in these drafts that =
precludes the use of extension headers or segment routing - IP is simply th=
e layer underneath that these protocols are building on. The figures are de=
finitely just examples - they also show outer Ethernet headers, which is no=
t a requirement.
>=20
> I wouldn't want to add text specifically stating that extension headers a=
re permissible. It seems like that could lead to similar questions in the f=
uture where one might wonder if other features of IP are allowed because on=
e is explicitly listed and others are not, etc. In my opinion, the drafts a=
re about as clear as they can be on this point.
>=20
> Jesse
>=20
> On 5/23/16, 1:09 AM, "rraszuk@gmail.com<mailto:rraszuk@gmail.com> on beha=
lf of Robert Raszuk" <rraszuk@gmail.com<mailto:rraszuk@gmail.com> on behalf=
 of robert@raszuk.net<mailto:robert@raszuk.net>> wrote:
>=20
> Hi Tal,
>=20
>> In order to avoid ambiguity, it would be great if the
>> authors could explicitly mention that IPv6 extension
>> headers are permitted.
>=20
> Well the drafts are complaint to RFC2119 (normative reference) so unless =
the text excludes elements with MUST/MUST NOT - everything else defined in =
the building blocks they (re)use is permitted.
>=20
> However as you say perhaps for clarity what could be added to those draft=
s is a normative reference to IPv4 and IPv6 base RFCs.
>=20
> Best,
> R.
>=20
>=20
> On Mon, May 23, 2016 at 9:54 AM, Tal Mizrahi <talmi@marvell.com<mailto:ta=
lmi@marvell.com>> wrote:
> Hi Robert,
>=20
> That makes sense.
> However, in this case the figures may be a bit confusing WRT the possible=
 existence of extension headers. This confusion is what led to the discussi=
on in this thread about whether segment routing is possible with VXLAN/VXLA=
N-GPE/Geneve encapsulations.
>=20
> In order to avoid ambiguity, it would be great if the authors could expli=
citly mention that IPv6 extension headers are permitted.
>=20
> Regards,
> Tal.
>=20
> From:rraszuk@gmail.com<mailto:rraszuk@gmail.com> [mailto:rraszuk@gmail.co=
m<mailto:rraszuk@gmail.com>] On Behalf Of Robert Raszuk
> Sent: Monday, May 23, 2016 10:47 AM
>=20
> To: Tal Mizrahi
> Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxl=
an-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo=
3@ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@to=
ols.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>;=
 draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.=
ietf.org>; Stefano Previdi (sprevidi)
> Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-rout=
ing-header
>=20
> Hi Tal,
>=20
> Indeed .. I saw the figures, but figures are non normative in any draft/r=
fc unless text below specifically spells it out.
>=20
> For example from vxlan-gpe:
>=20
> "When the outer IP header is IPv4, VTEPs MUST set the DF bit."
>=20
> Besides it is pretty challenging to add animation to the current draft fo=
rmats to illustrate all possibly allowed field values/combinations in any f=
igure :)  Figures just illustrate one use example.
>=20
> To me the current specs permit any value of IPv6 NxtHdr field as permitte=
d in both encapsulations.
>=20
> Best,
> Robert.
>=20
>=20
> On Mon, May 23, 2016 at 9:35 AM, Tal Mizrahi <talmi@marvell.com<mailto:ta=
lmi@marvell.com>> wrote:
> Hi Robert,
>=20
>=20
>> Where say in draft draft-quinn-vxlan-gpe do you see such statement that =
would imply
>> that v6 NxtHdr must be only equal to 17 (UDP) and not be a pointer to an=
y other type
>> of extension header further followed by UDP ?
>=20
>=20
> The following text is from Figure 4 in draft-ietf-nvo3-vxlan-gpe:
>=20
>      Outer IPv6 Header:
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |Version| Traffic Class |           Flow Label                  |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |         Payload Length        | NxtHdr=3D17(UDP)|   Hop Limit   |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>=20
>=20
> There is a similar figure in draft-ietf-nvo3-geneve.
>=20
> Best regards,
> Tal.
>=20
> From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] O=
n Behalf Of Robert Raszuk
> Sent: Monday, May 23, 2016 10:29 AM
> To: Tal Mizrahi
> Cc: spring@ietf.org<mailto:spring@ietf.org>; 6man WG; draft-ietf-nvo3-vxl=
an-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>; nvo=
3@ietf.org<mailto:nvo3@ietf.org>; draft-ietf-6man-segment-routing-header@to=
ols.ietf.org<mailto:draft-ietf-6man-segment-routing-header@tools.ietf.org>;=
 draft-ietf-nvo3-geneve@tools.ietf.org<mailto:draft-ietf-nvo3-geneve@tools.=
ietf.org>; Stefano Previdi (sprevidi)
>=20
> Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-rout=
ing-header
>=20
> Hi Tal,
>=20
>> drafts seem to imply
>=20
> Where say in draft draft-quinn-vxlan-gpe do you see such statement that w=
ould imply that v6 NxtHdr must be only equal to 17 (UDP) and not be a point=
er to any other type of extension header further followed by UDP ?
>=20
> Thx,
> R.
>=20
>=20
> On Mon, May 23, 2016 at 7:50 AM, Tal Mizrahi <talmi@marvell.com<mailto:ta=
lmi@marvell.com>> wrote:
> Dear Authors of VXLAN-GPE / Geneve,
>=20
> I am reiterating on this question, as I haven't seen a response yet:
>=20
> Have you considered the use of Segment Routing with VXLAN-GPE / Geneve? T=
he current VXLAN-GPE / Geneve drafts seem to imply that IPv6 extension head=
ers are currently not supported.
>=20
> Thanks,
> Tal.
>=20
>=20
>=20
>> -----Original Message-----
>> From: nvo3 [mailto:nvo3-bounces@ietf.org<mailto:nvo3-bounces@ietf.org>] =
On Behalf Of Tal Mizrahi
>> Sent: Tuesday, May 17, 2016 12:09 PM
>> To: Stefano Previdi (sprevidi); Tom Herbert; draft-ietf-nvo3-
>> geneve@tools.ietf.org<mailto:geneve@tools.ietf.org>; draft-ietf-nvo3-vxl=
an-gpe@tools.ietf.org<mailto:draft-ietf-nvo3-vxlan-gpe@tools.ietf.org>
>> Cc: spring@ietf.org<mailto:spring@ietf.org>; nvo3@ietf.org<mailto:nvo3@i=
etf.org>; 6man WG; draft-ietf-6man-segment-
>> routing-header@tools.ietf.org<mailto:routing-header@tools.ietf.org>
>> Subject: Re: [nvo3] [spring] L4 Checksum and draft-ietf-6man-segment-
>> routing-header
>>=20
>> Stefano,
>>=20
>> If I understand your point correctly:
>> IPv6 segment routing does not work with VXLAN / VXLAN-GPE / Geneve, sinc=
e
>> these encapsulations do not currently allow the use of IPv6 extension
>> headers.
>>=20
>> I wonder if the authors of VXLAN-GPE and Geneve have considered the use =
of
>> segment routing.
>>=20
>> Thanks,
>> Tal.
>>=20
>>=20
>>=20
>>> -----Original Message-----
>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:spre=
vidi@cisco.com>]
>>> Sent: Tuesday, May 17, 2016 10:41 AM
>>> To: Tom Herbert
>>> Cc: Tal Mizrahi; 6man WG; spring@ietf.org<mailto:spring@ietf.org>;
>>> draft-ietf-6man-segment-routing- header@tools.ietf.org<mailto:header@to=
ols.ietf.org>
>>> Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-
>>> header
>>>=20
>>>=20
>>>> On May 16, 2016, at 7:10 PM, Tom Herbert <tom@herbertland.com<mailto:t=
om@herbertland.com>>
>> wrote:
>>>>=20
>>>> On Mon, May 16, 2016 at 4:32 AM, Tal Mizrahi <talmi@marvell.com<mailto=
:talmi@marvell.com>>
>>> wrote:
>>>>>> it's all about IP, not layer-2.
>>>>>>=20
>>>>>> s.
>>>>>=20
>>>>> Right. However, it appears that at least in some cases a VXLAN VTEP
>>>>> will
>>> use SR. It certainly may be the case in SFC use cases (see Section 2.3
>>> in draft- ietf-spring-ipv6-use-cases).
>>>>>=20
>>>>=20
>>>> draft-ietf-6man-segment-routing-header mentions that the packet is
>>>> encapsulated
>>>=20
>>>=20
>>> into an outer ipv6 header which makes it a layer-3 encap.
>>>=20
>>>=20
>>>> , but I don't think it is explicit as to exact encapsulation format
>>>> (I suppose simple ip6ip6 is implied).
>>>=20
>>>=20
>>> see section 2.2
>>>=20
>>>=20
>>>> But, it
>>>> seems like any of several encapsulation techniques could work (VXLAN,
>>>=20
>>>=20
>>> I have some problems to understand where to fit an extension header
>>> into a vxlan encap...
>>>=20
>>>=20
>>>> GRE/IP, ESP/IP, GUE, foo over UDP, etc.) and if a device that wants
>>>> to do SR is already doing tunneling it seems reasonable to me to only
>>>> have one layer of encapsulation. Maybe this should be clarified in
>>>> the draft?
>>>=20
>>>=20
>>> the draft is about IPv6 extension header and more precisely a new type
>>> of the routing extension header defined in rfc2460. That's the context.
>>>=20
>>>=20
>>> s.
>>>=20
>>>=20
>>>=20
>>>=20
>>>>=20
>>>> Tom
>>>>=20
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto:s=
previdi@cisco.com>]
>>>>>> Sent: Monday, May 16, 2016 2:24 PM
>>>>>> To: Tal Mizrahi
>>>>>> Cc: Ole Tr=F8an;
>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft-i=
etf-6man-segment-routing-header@tools.ietf.org>;
>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>=20
>>>>>>=20
>>>>>>> On May 16, 2016, at 1:19 PM, Tal Mizrahi <talmi@marvell.com<mailto:=
talmi@marvell.com>> wrote:
>>>>>>>=20
>>>>>>> Hi Stefano,
>>>>>>>=20
>>>>>>> Thanks again for the prompt response.
>>>>>>>=20
>>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>>> is removed and the packet continues  its journey like nothing
>> happened.
>>>>>>>=20
>>>>>>> So VXLAN is off the table?
>>>>>>=20
>>>>>>=20
>>>>>> it's all about IP, not layer-2.
>>>>>>=20
>>>>>> s.
>>>>>>=20
>>>>>>=20
>>>>>>> It would be worthwhile to clarify this in the draft. If you have a
>>>>>>> specific
>>>>>> encapsulation in mind, it would be great if the draft would specify =
it.
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Tal.
>>>>>>>=20
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mailto=
:sprevidi@cisco.com>]
>>>>>>>> Sent: Monday, May 16, 2016 2:13 PM
>>>>>>>> To: Tal Mizrahi
>>>>>>>> Cc: Ole Tr=F8an;
>>>>>>>> draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto:draft=
-ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>>=20
>>>>>>>> Hi,
>>>>>>>>=20
>>>>>>>> On May 16, 2016, at 11:04 AM, Tal Mizrahi <talmi@marvell.com<mailt=
o:talmi@marvell.com>>
>>> wrote:
>>>>>>>>>=20
>>>>>>>>> Hi Stefano,
>>>>>>>>>=20
>>>>>>>>> Thanks for the responses.
>>>>>>>>>=20
>>>>>>>>>> exactly.
>>>>>>>>>>=20
>>>>>>>>>> Moreover, draft-ietf-6man-segment-routing-header assumes
>>>>>>>>>> encapsulation so clearly there's no L4 involved here.
>>>>>>>>>>=20
>>>>>>>>>> s.
>>>>>>>>>=20
>>>>>>>>> Two questions:
>>>>>>>>> 1. What if the encapsulation is VXLAN? L4 would still be
>>>>>>>>> involved,
>>> right?
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> See below.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>> 2. When you say 'assumes encapsulation', does it mean that a
>>>>>>>>> host cannot
>>>>>>>> send an IPv6 packet with an SRH? The current draft says:
>>>>>>>>>=20
>>>>>>>>> A Source SR Node can be any node originating an IPv6 packet with
>>>>>>>>> its
>>>>>>>>> IPv6 and Segment Routing Headers.  This include either:
>>>>>>>>>=20
>>>>>>>>>   A host originating an IPv6 packet.
>>>>>>>>>=20
>>>>>>>>>   An SR domain ingress router encapsulating a received IPv6 packe=
t
>>>>>>>>>   into an outer IPv6 header followed by an SRH.
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Will appreciate if you can clarify that.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> ok, two cases:
>>>>>>>>=20
>>>>>>>> 1. the SRH is inserted at the source.
>>>>>>>> the source originates the packet, the ipv6 header and  the SRH.
>>>>>>>> The source computes L4 checksum taking into  account the whole
>>> IPv6+SRH.
>>>>>>>> Here, theres' nothing new  compared to rfc2460.
>>>>>>>>=20
>>>>>>>> 2. the SRH is originated by the ingress node of the SR domain.
>>>>>>>> This is done by encapsulating the packet into a outer
>>>>>>>> (additional) ipv6 header followed by an SRH. This is L3
>>>>>>>> encapsulation and no L4 checksum is involved. When the  packet
>>>>>>>> leaves the SR tunnel the outer encapsulation  (including the SRH)
>>>>>>>> is removed and the packet continues  its journey like nothing
>> happened.
>>>>>>>>=20
>>>>>>>> s.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Thanks,
>>>>>>>>> Tal.
>>>>>>>>>=20
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Stefano Previdi (sprevidi) [mailto:sprevidi@cisco.com<mail=
to:sprevidi@cisco.com>]
>>>>>>>>>> Sent: Monday, May 16, 2016 11:59 AM
>>>>>>>>>> To: Ole Tr=F8an; Tal Mizrahi
>>>>>>>>>> Cc: draft-ietf-6man-segment-routing-header@tools.ietf.org<mailto=
:draft-ietf-6man-segment-routing-header@tools.ietf.org>;
>>>>>>>>>> spring@ietf.org<mailto:spring@ietf.org>; 6man WG
>>>>>>>>>> Subject: Re: [spring] L4 Checksum and
>>>>>>>>>> draft-ietf-6man-segment-routing- header
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>> On May 15, 2016, at 8:06 PM, otroan@employees.org<mailto:otroan=
@employees.org> wrote:
>>>>>>>>>>>=20
>>>>>>>>>>> Tal,
>>>>>>>>>>>=20
>>>>>>>>>>>> [Apologies if this issue has been discussed before.]
>>>>>>>>>>>>=20
>>>>>>>>>>>> According to draft-ietf-6man-segment-routing-header, an 'SR
>>>>>>>>>>>> Segment
>>>>>>>>>> Endpoint Node' updates the Destination IP address.
>>>>>>>>>>>> Therefore, it must also update the Layer 4 Checksum, right?
>>>>>>>>>>>>=20
>>>>>>>>>>>> I wonder if there is an upper bound on the size of the SRH.
>>>>>>>>>>>> Otherwise, the
>>>>>>>>>> L4 Checksum may be located in a pretty deep location.
>>>>>>>>>>>> Speaking from a chip vendor's perspective this may be a proble=
m


From nobody Tue May 31 11:34:06 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 620DF12D17B for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 11:33:56 -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 oGUElkJXCQKZ for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 11:33:54 -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 7C58512D14B for <ipv6@ietf.org>; Tue, 31 May 2016 11:33:54 -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 u4VIXr7n021899; Tue, 31 May 2016 11:33:54 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com [137.136.239.172]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u4VIXmts021843 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 31 May 2016 11:33:48 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 31 May 2016 11:33:47 -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; Tue, 31 May 2016 11:33:47 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "sthaug@nethelp.no" <sthaug@nethelp.no>, "otroan@employees.org" <otroan@employees.org>
Subject: RE: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Thread-Topic: I-D Action: draft-gont-6man-non-stable-iids-00.txt
Thread-Index: AQHRukEPAVThhZzzR0iFhASXuVaEI5/RhjiAgAAFeoCAASApgIAAb6IAgAALXwCAAAkjAIAAC+GAgAAjEZA=
Date: Tue, 31 May 2016 18:33:47 +0000
Message-ID: <1a4f519ef43c4d64a61643ab21d83401@XCH15-06-11.nw.nos.boeing.com>
References: <02BC17C8-35B8-4BC4-9A3B-D7DF61C84CAA@employees.org> <CAKD1Yr3trrLEziadqxSKC2QzFOSS6=45b4j4b1Zc-53Q-kQsJw@mail.gmail.com> <90628A01-A7C0-4D2C-83ED-74F3F9963E00@employees.org> <20160531.111923.74710755.sthaug@nethelp.no>
In-Reply-To: <20160531.111923.74710755.sthaug@nethelp.no>
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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Fx9Lu8Yxt6TZe_YMlRFEnZlbBQo>
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: Tue, 31 May 2016 18:33:56 -0000

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of sthaug@nethelp.no

> > IPv6 addresses are not persistent. they are all ephemeral. it is just a
> matter of the lifetime.
>=20
> While that may be technically true, it certainly goes against the way
> a lot of people *think* about IPv6 addresses, and could easily lead to
> misunderstanding.
>=20
> For example, I have a fixed /64 for the link to my home server, and
> another fixed /64 (out of a /56) for my home LAN. The server has these
> two /64 addresses statically configured on separate Ethernet interfaces.
> To me it's not particularly useful to think of these addresses as
> ephemeral.

+1. I think that all IP addresses have trended to ephemeral, but only in pa=
rt. The original model was stable addresses exclusively, and then things ev=
olved. But the existence of stable addresses continues to be a fact of life=
. For instance, my home modem's IPv4 address changes (a) every time I reboo=
t it, and (b) at some seemingly random interval, with no action required on=
 my part.

At the same time, DHCPv6 certainly presumes address stability. That's the w=
hole point. Equally, the client identifier option of DHCPv4 and v6 also pre=
sumes a known and stable IP address, based on the client's identity (functi=
on).

So I think it's problematic to assume that there's something fundamentally =
about IPv6 addresses, on this stability aspect.

Bert



From nobody Tue May 31 13:12:33 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 C30C412D8B5 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 13:12:32 -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 njT2ZJT-lGJC for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 13:12:30 -0700 (PDT)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::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 BEE9912D651 for <6man@ietf.org>; Tue, 31 May 2016 13:12:30 -0700 (PDT)
Received: by mail-pf0-x22b.google.com with SMTP id b124so77719416pfb.0 for <6man@ietf.org>; Tue, 31 May 2016 13:12:30 -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=dRskd4GFROEQQIAUOHOTfCgeR+WGnR69/pI25SIghDI=; b=fwkEP5p7p5u7lb9pblDxYrL4LIdr97koa6bwd2XXF8PLRUYyi2+3b82IPc7HbwDUZK yvsehCOxJW0CDOJW/1MgeNY8ES73DhONYlqjfShinkNxSUjcK0S42VfjhLNnXOxwP+C9 Coj9LgCrtyCRaruRf1a/Vo3G0D3YDTwPl8QXWuoHBhrsDoaRFeltqVlu8uRX8IyD3En/ /+Ad5cbGP+PktaoV3LAyI3Wbd7raObU7IFJed1set1TvzMPbBHcU8oKIXNbHwKxD0W/W 6968ml5sDeEMUboCoRlN1xVbrsAVTxbFgeP5rZbHNAArVN3oL7hC1O2/v/vHNZmoFYVS n0rw==
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=dRskd4GFROEQQIAUOHOTfCgeR+WGnR69/pI25SIghDI=; b=eQTJeH9txg8+flIcMKo7kqNdYY5+ryhBx2HaGSbzT94fY6NwUogZLn7RovOJx2qfOt AMICQLNV2ZtbdkliIHMyQAHBX918bDky5Jx1GiTCGFEhh5toFVkzS+LNl56lOr2dfVSr RBIP8h07QTDsBceLGsI0f4hliG/IR50ifvLpNEkHHrwUKzyp/ra0PLiAh1ZT1oI/PULW tPyZKLOAbn/Yfook17U2fQlHChQNG/cBs10zCl1CP01qhxr1Z3GAEzIU+Ewlpy2zqhHl pkcFHWKgB7rpRvnaDnXLPitEB7t42B40ZWkEf/nGsnh9EwkzQ39tyw5GYlMWBSJ8XMeG ANNQ==
X-Gm-Message-State: ALyK8tKjwqJidmRcq8A3YAaO+YtYHLe07rkBkfbTg/WD8eY5qn06ZdKu7Fuvn+Cdlh1q8A==
X-Received: by 10.98.30.133 with SMTP id e127mr18535420pfe.112.1464725550272;  Tue, 31 May 2016 13:12:30 -0700 (PDT)
Received: from [192.168.178.22] ([118.148.66.3]) by smtp.gmail.com with ESMTPSA id ff10sm23557603pac.13.2016.05.31.13.12.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 31 May 2016 13:12:29 -0700 (PDT)
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Lorenzo Colitti <lorenzo@google.com>, Mark Smith <markzzzsmith@gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com> <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com> <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com> <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <35661fe9-8839-1bdf-db3a-c4648a3733b7@gmail.com>
Date: Wed, 1 Jun 2016 08:12:29 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mI93S631Pimac2rR4x7Bq26JxL0>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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, 31 May 2016 20:12:33 -0000

Lorenzo,
On 31/05/2016 20:21, Lorenzo Colitti wrote:
> On Tue, May 31, 2016 at 3:56 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
>>> What if the device is already connected to another network? For example,
>> what if a device switches from cellular data to wifi? Does that count as a
>> "reconnect"?
>>
>> No. Clearly different networks, of more specifically, different link
>> (RFc2460)/subnets/default router(s)
>>
> Then all apps are sitting there waiting for read() calls that will never
> complete unless the same network reconnects. 

That's an important point. read() timeouts in clients are tricky. Quoting
a comment found on stackoverflow.com, "The only safe approach to handle TCP
timeout is to run the connection code in a different thread and interrupt the
thread when it takes too long." Or you can wait in select() instead of read().
But I bet that many applications do neither.

   Brian

> That's pretty much always the
> wrong thing to do for the majority of apps - most apps are better served by
> making a new connection on another network than sitting there waiting for a
> network that is gone and might not come back for a long time. Imagine how
> irritating it would be if your browser hung every time you walk in and out
> of range of a wifi network.
> 
> 
>>> But RFC 7217 plainly states that it's associated with the network
>> interface:
>>>
>>>        Net_Iface:
>>>           An implementation-dependent stable identifier associated with
>>>           the network interface for which the RID is being generated.
>>>
>>> "associated with the network interface" implies that it changes if the
>> interface changes.
>>>>
>>
>> Read the whole of RFC7217, or at least Appendix A, as I said before.
>>
> But I did. The way I read it, all the suggestions in Appendix A have equal
> or less stability than the interface link-layer address. On client systems,
> interface name and index are at best as persistent as the MAC address. At
> worst, they depend unpredictably on device initialization order and
> connect/disconnect sequence.
> 
> Logical network service identity is the only one that might have higher
> stability, but it's hard to tell what properties "a conception of logical
> network service identity, distinct from network interface identity or
> index" means since it's rather vague. One thing that's for sure is that
> logical network interface identity *must* be tightly coupled to the network
> card it's used with, because if it isn't and the host connects to the same
> network simultaneously with two interfaces, the algorithm will generate
> duplicate addresses, and that's explicitly forbidden by the document.
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Tue May 31 16:24:10 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 DD42112D8F8 for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 16:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.197
X-Spam-Level: 
X-Spam-Status: No, score=-2.197 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.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 Vk6yrorvhx9K for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 16:23:52 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::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 BAABC12D690 for <6man@ietf.org>; Tue, 31 May 2016 16:23:51 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id d127so3834218vkh.2 for <6man@ietf.org>; Tue, 31 May 2016 16:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=kOw0Ptm7CdFxH86i1GfCHacqeX2D7gkuPSz3ZigiS44=; b=s3F4Z2gwOTyAOv08Fel7JQAoUrJYKTsEqR5Ku1s4Aprm/rBK5fYcoYYLPzjwufFtDI L7HfvwQK21qM+s3hdJ8FjxeHtaX2Pf/oDhDnxW5bg2yS/IhrTNOsVaeOTgsCG/NMhwng MW8R07lQLJdfFcnIMoXbilhsGVp/c076rrzV9s+XTTpVliqy3aluDPHsn2O3qfzRbnbY ry1Irh0cHjhs3pfWBF5m2Xs0nw6CmLoqNMkYqf22jnYAQDctFy7dhEAJUHhGaQe6thgA BINQsOQEcxMZSAotkR7v6JQ0teuMMszt9bU5gbqSsq4lJyeiACYQj3Ri16LpGfLY1/zb Q//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:date :message-id:subject:from:to:cc; bh=kOw0Ptm7CdFxH86i1GfCHacqeX2D7gkuPSz3ZigiS44=; b=DYyq7V7sPdBA/Xu37bryqvbTccX7yuivamL/F0bR5U1qYdQI7JbhqkaHiwhpVfn3rO dDoBuhi5p2F5HzcAk8eN1V+6+stxDSuY7wGQgDHzbnWTx8RcwzwvDX1MKtsRz+bAnEld 6dKEDsMTo2e/n08L8N6gVvy74zUx2k788ELoaOLpjAIQP//xJzR9UlicVkz84RTxdBXC p6HQ8A6fU7PWzsXSbmbwp8uPc7aifeclsf4yN5t7Vgt1juCHd8kldkE5YXD+CVWktt8o dHdKjb47zYMBxnjjwv7HWraHttQ9ij3e0asr5EGWxCuzdJRmcK7ca5Lo1Yrk3744UbAQ LFuQ==
X-Gm-Message-State: ALyK8tJk7pjnfI8D8cutqEra/yj3S1Azlb9fJ0dZA9imLMTCy+9wdiCOyN08Z0+IZ7DxwFSp/jshTscLWfoX5A==
MIME-Version: 1.0
X-Received: by 10.176.67.227 with SMTP id l90mr388968ual.133.1464737030649; Tue, 31 May 2016 16:23:50 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 31 May 2016 16:23:50 -0700 (PDT)
Received: by 10.176.3.168 with HTTP; Tue, 31 May 2016 16:23:50 -0700 (PDT)
In-Reply-To: <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com> <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com> <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com> <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com>
Date: Wed, 1 Jun 2016 09:23:50 +1000
Message-ID: <CAO42Z2wJe8VgrqbqytqhXxms+LN_j9v_VGOUuhnZqC5-fR_07Q@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
From: Mark Smith <markzzzsmith@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114a5e6666bab305342baa2a
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bbuehy8uE66V2mf0FUw5cazkQM0>
Cc: Fernando Gont <fgont@si6networks.com>, 6man@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, 31 May 2016 23:24:00 -0000

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

On 31 May 2016 17:52, "Lorenzo Colitti" <lorenzo@google.com> wrote:
>
> On Tue, May 31, 2016 at 3:56 PM, Mark Smith <markzzzsmith@gmail.com>
wrote:
>>
>> > What if the device is already connected to another network? For
example, what if a device switches from cellular data to wifi? Does that
count as a "reconnect"?
>>
>> No. Clearly different networks, of more specifically, different link
(RFc2460)/subnets/default router(s)
>
> Then all apps are sitting there waiting for read() calls that will never
complete unless the same network reconnects. That's pretty much always the
wrong thing to do for the majority of apps - most apps are better served by
making a new connection on another network than sitting there waiting for a
network that is gone and might not come back for a long time. Imagine how
irritating it would be if your browser hung every time you walk in and out
of range of a wifi network.
>
>>

The answer is MPTCP.

This discussion has got way past whether link-layer address randomisation
is an adequate substitute for RFC7217 addresses.

As someone who is using random MAC addresses in most places I can, they're
not.

>> > But RFC 7217 plainly states that it's associated with the network
interface:
>> >
>> >        Net_Iface:
>> >           An implementation-dependent stable identifier associated with
>> >           the network interface for which the RID is being generated.
>> >
>> > "associated with the network interface" implies that it changes if the
interface changes.
>> >>
>>
>> Read the whole of RFC7217, or at least Appendix A, as I said before.
>
> But I did. The way I read it,

You're reading it incorrectly.

>all the suggestions in Appendix A have equal or less stability than the
interface link-layer address. On client systems, interface name and index
are at best as persistent
as the MAC address.

If I recall, Fedora assigns interface names based on PCI slot.

>At worst, they depend unpredictably on device initialization order and
connect/disconnect sequence.
>

Get some time on a commercial router and you'll find out that none of what
you're saying occurs. Their interface names are persistent, and will
commonly use slot/module/interface to refer to the interface. Swapping an
interface module changes nothing but the MAC address. People object to
router interface LL and other addresses changing because the MAC address
has changed. Another example of why it has been a mistake to use MAC
addresses as L3 IIDs.

(Static addresses should be a choice. Making static addresses mandatory to
decouple an interface address from a MAC address is IPv4 thinking. The
ANIMA people won't like making static addressing on routers mandatory.)

Regarding ifIndex to interface persistence:

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/ifindx.html


> Logical network service identity is the only one that might have higher
stability, but it's hard to tell what properties "a conception of logical
network service identity, distinct from network interface identity or
index" means since it's rather vague. One thing that's for sure is that
logical network interface identity *must* be tightly coupled to the network
card it's used with, because if it isn't and the host connects to the same
network simultaneously with two interfaces, the algorithm will generate
duplicate addresses, and that's explicitly forbidden by the document.

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

<p dir=3D"ltr"><br>
On 31 May 2016 17:52, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:lor=
enzo@google.com">lorenzo@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On Tue, May 31, 2016 at 3:56 PM, Mark Smith &lt;<a href=3D"mailto:mark=
zzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; &gt; What if the device is already connected to another network? F=
or example, what if a device switches from cellular data to wifi? Does that=
 count as a &quot;reconnect&quot;?<br>
&gt;&gt;<br>
&gt;&gt; No. Clearly different networks, of more specifically, different li=
nk (RFc2460)/subnets/default router(s)<br>
&gt;<br>
&gt; Then all apps are sitting there waiting for read() calls that will nev=
er complete unless the same network reconnects. That&#39;s pretty much alwa=
ys the wrong thing to do for the majority of apps - most apps are better se=
rved by making a new connection on another network than sitting there waiti=
ng for a network that is gone and might not come back for a long time. Imag=
ine how irritating it would be if your browser hung every time you walk in =
and out of range of a wifi network.<br>
&gt; =C2=A0<br>
&gt;&gt;</p>
<p dir=3D"ltr">The answer is MPTCP.</p>
<p dir=3D"ltr">This discussion has got way past whether link-layer address =
randomisation is an adequate substitute for RFC7217 addresses.</p>
<p dir=3D"ltr">As someone who is using random MAC addresses in most places =
I can, they&#39;re not.</p>
<p dir=3D"ltr">&gt;&gt; &gt; But RFC 7217 plainly states that it&#39;s asso=
ciated with the network interface:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0Net_Iface:<br>
&gt;&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 An implementation-dependen=
t stable identifier associated with<br>
&gt;&gt; &gt; =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 the network interface for =
which the RID is being generated.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &quot;associated with the network interface&quot; implies tha=
t it changes if the interface changes.<br>
&gt;&gt; &gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Read the whole of RFC7217, or at least Appendix A, as I said befor=
e.<br>
&gt;<br>
&gt; But I did. The way I read it,</p>
<p dir=3D"ltr">You&#39;re reading it incorrectly.</p>
<p dir=3D"ltr">&gt;all the suggestions in Appendix A have equal or less sta=
bility than the interface link-layer address. On client systems, interface =
name and index are at best as persistent <br>
as the MAC address.</p>
<p dir=3D"ltr">If I recall, Fedora assigns interface names based on PCI slo=
t.</p>
<p dir=3D"ltr">&gt;At worst, they depend unpredictably on device initializa=
tion order and connect/disconnect sequence.<br>
&gt;</p>
<p dir=3D"ltr">Get some time on a commercial router and you&#39;ll find out=
 that none of what you&#39;re saying occurs. Their interface names are pers=
istent, and will commonly use slot/module/interface to refer to the interfa=
ce. Swapping an interface module changes nothing but the MAC address. Peopl=
e object to router interface LL and other addresses changing because the MA=
C address has changed. Another example of why it has been a mistake to use =
MAC addresses as L3 IIDs.</p>
<p dir=3D"ltr">(Static addresses should be a choice. Making static addresse=
s mandatory to decouple an interface address from a MAC address is IPv4 thi=
nking. The ANIMA people won&#39;t like making static addressing on routers =
mandatory.)</p>
<p dir=3D"ltr">Regarding ifIndex to interface persistence:</p>
<p dir=3D"ltr"><a href=3D"http://www.cisco.com/c/en/us/td/docs/switches/lan=
/catalyst6500/ios/12-2SX/configuration/guide/book/ifindx.html">http://www.c=
isco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration=
/guide/book/ifindx.html</a><br><br><br></p>
<p dir=3D"ltr">&gt; Logical network service identity is the only one that m=
ight have higher stability, but it&#39;s hard to tell what properties &quot=
;a conception of logical network service identity, distinct from network in=
terface identity or index&quot; means since it&#39;s rather vague. One thin=
g that&#39;s for sure is that logical network interface identity *must* be =
tightly coupled to the network card it&#39;s used with, because if it isn&#=
39;t and the host connects to the same network simultaneously with two inte=
rfaces, the algorithm will generate duplicate addresses, and that&#39;s exp=
licitly forbidden by the document.</p>

--001a114a5e6666bab305342baa2a--


From nobody Tue May 31 17:58:56 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 538CB12D93C for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 17:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level: 
X-Spam-Status: No, score=-4.126 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.426, 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 m0DwuNylHSLY for <ipv6@ietfa.amsl.com>; Tue, 31 May 2016 17:58:52 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 6D28212D935 for <6man@ietf.org>; Tue, 31 May 2016 17:58:49 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id o16so4424694ywd.2 for <6man@ietf.org>; Tue, 31 May 2016 17:58:49 -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=fi4Hf5krK/vLDA+0KOGQTv9St/43uVq8SAsTr9MTsyY=; b=kMI/EWWQntte28knn99Kc/lynp29x46Fuz4Bb5tqb1RqSfYEtd+aJ7LU7Wb2m7QrwZ Ico59wHFNnWRkFe3AK6i3YRlhvbalyydURRIG65jIf0+MplgudGghb65baoPVt+tp6CN t6Q9w8kOb0hrLYAHokm/PmM6yWN/qd3WERzZ5hUT5kedl4VidU6dG7iZOzdIK7IRnfX5 GMUWHqdb/5b5vV46ayUnlq1RQszfxbgWWRbbd4pXOwMy1rzezqqRRpj5ErXqixqEguRb rB69xQGcacSOOgoV3t8/ThiU+vXCJKPqROZrFai8NklbuC+czN7JvEP1/jP5SEP5sf/i 6fkg==
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=fi4Hf5krK/vLDA+0KOGQTv9St/43uVq8SAsTr9MTsyY=; b=Ce+Z2xG56eRokt2GTQImPp1b3p+0cZD41Cg2HetaQrI3HtM3s6uNaFIZpqWoxBvreq 7sekFt9DAiUcxNVHpg47M1gRzd/ihtX8SQT/gN1FEHhYNlwkehExpcN+6R2eDdi43mPh ESa/vCetyvMgCua6O9wkCWzySXddouWtDNTISuvIriFisxLOSgy9Lc8J7mZ0e/I63u9x qGtiYT4c9eBGDT8L2m7U3Tmd3FzfcAukGEmry93zoXbl7FGeFXyclths4BGl2R0uPld6 c2rA92pYTaIoZT1eW8pmkMMnVm215qOp+aZOcpcHhEFEXO5BrTz4a1/uaOJ7aSj6EZRP D9Nw==
X-Gm-Message-State: ALyK8tLZKIZgaTEVcTF4OknBkjhBcw+jsR5w+znuHLvSG7F+Ie7F3A4Mp244fFpToRI1oDQFPyvkM4pJuKwh0Awb
X-Received: by 10.129.108.211 with SMTP id h202mr630346ywc.229.1464742728463;  Tue, 31 May 2016 17:58:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.210 with HTTP; Tue, 31 May 2016 17:58:28 -0700 (PDT)
In-Reply-To: <CAO42Z2wJe8VgrqbqytqhXxms+LN_j9v_VGOUuhnZqC5-fR_07Q@mail.gmail.com>
References: <20160523150736.10739.56619.idtracker@ietfa.amsl.com> <57431E27.8090209@si6networks.com> <CAKD1Yr37A61zBeqQ4TDbHTwyVbnm35OC4ez-LGC7zvOuHt9iVg@mail.gmail.com> <CAO42Z2xFRN9khnvhP7Rd=rrrPexF=t841J8HbzRkYn1XqbfewQ@mail.gmail.com> <CAKD1Yr1AiQVdEt4V=stCfWO2Ayn+q2ztZwOp5s3YDpPpUQU7xA@mail.gmail.com> <CAO42Z2xVx66ayPmKTQ=guYjAcudkfCnSOm5p4XQh_dYoBRCHdg@mail.gmail.com> <CAKD1Yr1qpQXMS=Ep2RK_Aj+RuNB8OxxMxSepu7TZ+Boqvh4w=g@mail.gmail.com> <CAO42Z2z1L4+HiSAw8eoL9pS2bY5DJDLA7YvkhSxm9GRYpVBbFw@mail.gmail.com> <CAKD1Yr3gR6rdV=d7NpqzF-K+f=DCOTU0RccJPiMZoLh80yOt-w@mail.gmail.com> <CAO42Z2zEX1vRLeM5HknL3bjW4svvAeiSRWqWumO_zg6xDXmb=A@mail.gmail.com> <CAKD1Yr1Le+7h1OYN5Ug2WfyOGSuw9JVUdP04uSBsRcj3pikSLQ@mail.gmail.com> <CAO42Z2wb-D4USoNnH4fezmcRMNa22sfjYOx20T_HueE_htxWJA@mail.gmail.com> <CAKD1Yr2d8ska1Y27Lzy+997MqBZqdLnhD3sgGtQVc94dMQ3FtA@mail.gmail.com> <CAO42Z2ww2wvMi5MQsFUvGysDpX9Dgx_eBvwhU8=5yOJqJf0DEw@mail.gmail.com> <CAKD1Yr3sZ0aHHmgk-TCaZjn9yRjbGrJuJVBwL120P0Y0XdRiKQ@mail.gmail.com> <CAO42Z2wJe8VgrqbqytqhXxms+LN_j9v_VGOUuhnZqC5-fR_07Q@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 1 Jun 2016 09:58:28 +0900
Message-ID: <CAKD1Yr0xuu66_bQA_EMAfR3=MUonrno0gkh42iONY9bHt4a02g@mail.gmail.com>
Subject: Re: RFC4941, temp-addr only, etc. (Fwd: New Version Notification for draft-gont-6man-non-stable-iids-00.txt)
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114da746051d3605342cfe91
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bw0u62NCIqN8TFBDvELD0hPCSPo>
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@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: Wed, 01 Jun 2016 00:58:54 -0000

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

On Wed, Jun 1, 2016 at 8:23 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> The answer is MPTCP.
>
If you ask me, a protocol that cannot be deployed is never the answer to
anything. But MPTCP is not the only way to do multipath, and it's true that
that's OT for this thread.

> >all the suggestions in Appendix A have equal or less stability than the
> interface link-layer address. On client systems, interface name and index
> are at best as persistent
>
> as the MAC address.
>
> If I recall, Fedora assigns interface names based on PCI slot.
>
On ubuntu they come from udev rules:

# PCI device 0x8086:0x0085 (iwlwifi)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="84:3a:4b:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
...
# USB device 0x:0x (r8152)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:e0:4c:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth5"

PCI slot (or USB bus location) really isn't going to work well for the USB
ethernet adapter which I use every day.

> Get some time on a commercial router and you'll find out that none of what
> you're saying occurs.
>
Of course it doesn't. What I'm saying applies to hosts, but it does apply
to most hosts, and hosts are the things that have the greater privacy
requirements. You want to make RFC7217 a MUST for commercial routers, sure:
Ole is the one you have to fight on that one, not me :-)

Cheers,
Lorenzo

--001a114da746051d3605342cfe91
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 W=
ed, Jun 1, 2016 at 8:23 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:markzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt;</span> wrote:<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"><span class=3D"gmail-"><p dir=3D"ltr">The answer is MPTCP=
.<br></p></span></blockquote><div>If you ask me, a protocol that cannot be =
deployed is never the answer to anything. But MPTCP is not the only way to =
do multipath, and it&#39;s true that that&#39;s OT for this thread.</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pad=
ding-left:1ex"><span class=3D"gmail-"><p dir=3D"ltr"></p></span>
<p dir=3D"ltr">&gt;all the suggestions in Appendix A have equal or less sta=
bility than the interface link-layer address. On client systems, interface =
name and index are at best as persistent=C2=A0<br></p><span class=3D"gmail-=
"><p dir=3D"ltr">
as the MAC address.</p>
</span><p dir=3D"ltr">If I recall, Fedora assigns interface names based on =
PCI slot.</p></blockquote><div>On ubuntu they come from udev rules:</div><d=
iv><br></div><div><div># PCI device 0x8086:0x0085 (iwlwifi)</div><div>SUBSY=
STEM=3D=3D&quot;net&quot;, ACTION=3D=3D&quot;add&quot;, DRIVERS=3D=3D&quot;=
?*&quot;, ATTR{address}=3D=3D&quot;84:3a:4b:xx:xx:xx&quot;, ATTR{dev_id}=3D=
=3D&quot;0x0&quot;, ATTR{type}=3D=3D&quot;1&quot;, KERNEL=3D=3D&quot;wlan*&=
quot;, NAME=3D&quot;wlan0&quot;</div></div><div>...</div><div><div># USB de=
vice 0x:0x (r8152)</div><div>SUBSYSTEM=3D=3D&quot;net&quot;, ACTION=3D=3D&q=
uot;add&quot;, DRIVERS=3D=3D&quot;?*&quot;, ATTR{address}=3D=3D&quot;00:e0:=
4c:xx:xx:xx&quot;, ATTR{dev_id}=3D=3D&quot;0x0&quot;, ATTR{type}=3D=3D&quot=
;1&quot;, KERNEL=3D=3D&quot;eth*&quot;, NAME=3D&quot;eth5&quot;</div></div>=
<div><br></div><div>PCI slot (or USB bus location) really isn&#39;t going t=
o work well for the USB ethernet adapter which I use every day.</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding=
-left:1ex"><span class=3D"gmail-">
<p dir=3D"ltr">Get some time on a commercial router and you&#39;ll find out=
 that none of what you&#39;re saying occurs.</p></span></blockquote><div>Of=
 course it doesn&#39;t. What I&#39;m saying applies to hosts, but it does a=
pply to most hosts, and hosts are the things that have the greater privacy =
requirements. You want to make RFC7217 a MUST for commercial routers, sure:=
 Ole is the one you have to fight on that one, not me :-)</div><div><br></d=
iv><div>Cheers,</div><div>Lorenzo</div></div></div></div>

--001a114da746051d3605342cfe91--

