
From kauer@biplane.com.au  Tue Mar  1 03:54:06 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03B933A67B0 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 03:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGXdW7cqjg4N for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 03:54:05 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id B10773A67AE for <ipv6@ietf.org>; Tue,  1 Mar 2011 03:54:01 -0800 (PST)
Received: from [203.63.43.162] (helo=[172.17.0.178]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PuOAQ-0006MK-6N for ipv6@ietf.org; Tue, 01 Mar 2011 06:55:02 -0500
Subject: question about solicited node multicast addresses
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-aYdyLnamF4RtdTO5KAl1"
Date: Tue, 01 Mar 2011 22:28:55 +1030
Message-ID: <1298980735.14724.18.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 11:54:06 -0000

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

How come solicited node multicast addresses use only 24 bits of the
host's IPv6 address? It looks like there is space for many more; 64 more
at a pinch. Using more bits from the host address would decrease even
further the likelihood of two nodes sharing the same SNM address.

See RFC 4291, section 2.7.1, page 16.

I can see why at least one bit is needed to discriminate between
all-nodes and SNM addresses[1], but why use so many bits (8)?

The only plausible theory I have is that after 8 bits of "ff" and 16
bits of ethernet multicast prefix (0x3333) are factored in, there is
only room at layer 2 for 24 more bits, so there is no point having more
bits in layer 3. This is not a satisfying theory because it appears to
tie layer 3 multicast to a specific layer 2 technology (ethernet, with
its 48-bit MAC addresses).

Regards, K.

[1] All-nodes L2 multicast                   33:33:00:00:00:01
    SNM L2 multicast of 2001:db8:100:200::1  33:33:ff:00:00:01
    SNM L2 with 32 bits instead of 24 bits   33:33:00:00:00:01

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-aYdyLnamF4RtdTO5KAl1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1s334ACgkQMAcU7Vc29ofbZwCfQEwiVldGSEeAN2Q9jmDpEB/v
QuEAoLD9g9Oll5qWzRQVp/t9pMIa98h2
=/369
-----END PGP SIGNATURE-----

--=-aYdyLnamF4RtdTO5KAl1--


From trejrco@gmail.com  Tue Mar  1 05:21:09 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0EBA3A682C for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 05:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.714
X-Spam-Level: 
X-Spam-Status: No, score=-2.714 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YUd1yfyb57J for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 05:21:00 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 4729B3A689A for <ipv6@ietf.org>; Tue,  1 Mar 2011 05:20:01 -0800 (PST)
Received: by iyj8 with SMTP id 8so4378655iyj.31 for <ipv6@ietf.org>; Tue, 01 Mar 2011 05:21:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vnyTkhjiROluTEEzOqIlJxF9fUhRMpcoIPec3FPPkXA=; b=j+yhz0e1f46C2OHIVKfvlcWIAqUSNpQQe3nJmCkUE2aB/IWx4Maitn+sGEu05dC0Nh qHoGHXIqXXrp4gKl3fKWp0MBsajoTKzSQVq1AHIqxvvW7D29nKNEYe3rBRKJdh2LIxqe GMcUmn/KI6evWP1G+qzhDZrVc944JUufkNh7I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=ZsTZz2aLbodlznkNPmuYSGqBdO/2+EynZbXM5jwJ4HvzQCIqNUkEsZqjj5T0bgS4ZF jS1PjFvSBELRgrccaxt/cTwre9PtxlpgeGnyopSI1hw4Fi7pdQHUwZGKMUmOgNVtNk/C dhpCMPIhVSFOQZ5hrMnokyG7w+nO2cJkv8L/w=
MIME-Version: 1.0
Received: by 10.42.170.132 with SMTP id f4mr6653796icz.255.1298985663053; Tue, 01 Mar 2011 05:21:03 -0800 (PST)
Received: by 10.231.148.143 with HTTP; Tue, 1 Mar 2011 05:21:02 -0800 (PST)
In-Reply-To: <1298980735.14724.18.camel@karl>
References: <1298980735.14724.18.camel@karl>
Date: Tue, 1 Mar 2011 08:21:02 -0500
Message-ID: <AANLkTikmoCvepH0EYh2rS1dPC6OQK-GPWaAXFxsrg5xN@mail.gmail.com>
Subject: Re: question about solicited node multicast addresses
From: TJ <trejrco@gmail.com>
To: IETF IPv6 <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=90e6ba61366403bf56049d6bab74
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 13:21:09 -0000

--90e6ba61366403bf56049d6bab74
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 1, 2011 at 06:58, Karl Auer <kauer@biplane.com.au> wrote:
>
> The only plausible theory I have is that after 8 bits of "ff" and 16
> bits of ethernet multicast prefix (0x3333) are factored in, there is
> only room at layer 2 for 24 more bits, so there is no point having more
> bits in layer 3. This is not a satisfying theory because it appears to
> tie layer 3 multicast to a specific layer 2 technology (Ethernet, with
> its 48-bit MAC addresses).
>

"This is not a satisfying theory because it appears to tie layer 3 multicast
to a specific layer 2 technology (Ethernet, with its 48-bit MAC addresses)."

Factoring reality in to any decision typically yields better results, yes?
More importantly - what problem are you really trying to solve?  Do you
expect to have lots of collisions in this 24 bit space on a given link?


/TJ

--90e6ba61366403bf56049d6bab74
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Tue, Mar 1, 2011 at 06:58, Karl Auer <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:kauer@biplane.com.au">kauer@biplane.com=
.au</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

The only plausible theory I have is that after 8 bits of &quot;ff&quot; and=
 16<br>
bits of ethernet multicast prefix (0x3333) are factored in, there is<br>
only room at layer 2 for 24 more bits, so there is no point having more<br>
bits in layer 3. This is not a satisfying theory because it appears to<br>
tie layer 3 multicast to a specific layer 2 technology (Ethernet, with<br>
its 48-bit MAC addresses).<br></blockquote><div><br></div><div>&quot;<font =
class=3D"Apple-style-span" color=3D"#202020" face=3D"&#39;Droid Sans&#39;, =
arial, sans-serif"><span class=3D"Apple-style-span" style=3D"border-collaps=
e: collapse;">This is not a satisfying theory because it appears to=A0tie l=
ayer 3 multicast to a specific layer 2 technology (Ethernet, with=A0its 48-=
bit MAC addresses).</span></font>&quot;</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Factoring r=
eality in to any decision typically yields better results, yes?</div><div c=
lass=3D"gmail_quote">More importantly - what problem are you really trying =
to solve? =A0Do you expect to have lots of collisions in this 24 bit space =
on a given link?</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><br></div>/=
TJ<br><div><br></div></div>

--90e6ba61366403bf56049d6bab74--

From suresh.krishnan@ericsson.com  Tue Mar  1 07:58:37 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4F583A6940 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 07:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.366
X-Spam-Level: 
X-Spam-Status: No, score=-102.366 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSd2Uj5k+1Di for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 07:58:36 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 81A523A6985 for <ipv6@ietf.org>; Tue,  1 Mar 2011 07:58:28 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p21Glo3V032265; Tue, 1 Mar 2011 10:47:51 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 1 Mar 2011 10:59:16 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Karl Auer <kauer@biplane.com.au>, IETF IPv6 <ipv6@ietf.org>
Date: Tue, 1 Mar 2011 10:59:15 -0500
Subject: RE: question about solicited node multicast addresses
Thread-Topic: question about solicited node multicast addresses
Thread-Index: AcvYB5X2oXfNkrp7TIWAX7ZDWoZa7gAIVvrQ
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150EBF2F95D@EUSAACMS0703.eamcs.ericsson.se>
References: <1298980735.14724.18.camel@karl>
In-Reply-To: <1298980735.14724.18.camel@karl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 15:58:37 -0000

Hi Karl,
  The solicited node multicast address is just a pre-filter. Any collision =
that will be detected with your proposed 32 bit solicited node multicast ad=
dress will also be detected with a 24 bit solicited node multicast address.=
 How many nodes do you expect to have on your link?

Cheers
Suresh

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
> Behalf Of Karl Auer
> Sent: Tuesday, March 01, 2011 3:59 AM
> To: IETF IPv6
> Subject: question about solicited node multicast addresses
>=20
> How come solicited node multicast addresses use only 24 bits=20
> of the host's IPv6 address? It looks like there is space for=20
> many more; 64 more at a pinch. Using more bits from the host=20
> address would decrease even further the likelihood of two=20
> nodes sharing the same SNM address.
>=20
> See RFC 4291, section 2.7.1, page 16.
>=20
> I can see why at least one bit is needed to discriminate=20
> between all-nodes and SNM addresses[1], but why use so many bits (8)?
>=20
> The only plausible theory I have is that after 8 bits of "ff"=20
> and 16 bits of ethernet multicast prefix (0x3333) are=20
> factored in, there is only room at layer 2 for 24 more bits,=20
> so there is no point having more bits in layer 3. This is not=20
> a satisfying theory because it appears to tie layer 3=20
> multicast to a specific layer 2 technology (ethernet, with=20
> its 48-bit MAC addresses).
>=20
> Regards, K.
>=20
> [1] All-nodes L2 multicast                   33:33:00:00:00:01
>     SNM L2 multicast of 2001:db8:100:200::1  33:33:ff:00:00:01
>     SNM L2 with 32 bits instead of 24 bits   33:33:00:00:00:01
>=20
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~~~~~~~~
> Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
> http://www.biplane.com.au/kauer/                  =20
> +61-428-957160 (mob)
>=20
> GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736=20
> F687 Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B=20
> CD97 0156
> =

From pch-b6B5344D9@u-1.phicoh.com  Tue Mar  1 08:13:39 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E59413A67B3 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 08:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGYDtR0Ix6SA for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 08:13:39 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id A6D473A67A8 for <ipv6@ietf.org>; Tue,  1 Mar 2011 08:13:37 -0800 (PST)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1PuSDg-0001dRC; Tue, 1 Mar 2011 17:14 +0100
Message-Id: <m1PuSDg-0001dRC@stereo.hq.phicoh.net>
To: IETF IPv6 <ipv6@ietf.org>
Subject: Re: question about solicited node multicast addresses 
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
In-reply-to: Your message of "Tue, 01 Mar 2011 22:28:55 +1030 ." <1298980735.14724.18.camel@karl> 
Date: Tue, 01 Mar 2011 17:14:33 +0100
X-Mailman-Approved-At: Tue, 01 Mar 2011 09:27:25 -0800
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 16:13:40 -0000

In your letter dated Tue, 01 Mar 2011 22:28:55 +1030 you wrote:
>How come solicited node multicast addresses use only 24 bits of the
>host's IPv6 address? It looks like there is space for many more; 64 more
>at a pinch. Using more bits from the host address would decrease even
>further the likelihood of two nodes sharing the same SNM address.

Assuming that the lower part of the IPv6 address is random, the birthday
paradox suggests that you can expect a collision when there are about 
2048 hosts in a single broadcast domain. And that is just a single collision,
two hosts that happen to have the same SNM.

On average, the amount of traffic a hosts sees due to collisions is one
16 millionth of the total ND traffic.

I don't think allocating more bits will have any kind of impact.

Of course, if addresses are not chosen randomly, all bets are off. But that
doesn't change if you use more bits.



From narten@us.ibm.com  Tue Mar  1 11:20:46 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13FBE3A6A74 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 11:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZK2OxgO82x3 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 11:20:44 -0800 (PST)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by core3.amsl.com (Postfix) with ESMTP id 0EAA73A6A4A for <ipv6@ietf.org>; Tue,  1 Mar 2011 11:20:43 -0800 (PST)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e37.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p21JJ4LC000467 for <ipv6@ietf.org>; Tue, 1 Mar 2011 12:19:04 -0700
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p21JLchr120736 for <ipv6@ietf.org>; Tue, 1 Mar 2011 12:21:38 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p21JJEPl010152 for <ipv6@ietf.org>; Tue, 1 Mar 2011 12:19:14 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-48-47-119.mts.ibm.com [9.48.47.119]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p21JJDWT010029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Mar 2011 12:19:13 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p21JLZpZ022099; Tue, 1 Mar 2011 14:21:35 -0500
Message-Id: <201103011921.p21JLZpZ022099@cichlid.raleigh.ibm.com>
To: John Leslie <john@jlc.net>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-node-req-bis-07.txt>
In-reply-to: <20110218144244.GA15397@verdi>
References: <7B63F7B6-D788-4A05-9722-C1CAAA42B754@gmail.com> <201101171932.p0HJWU58003756@cichlid.raleigh.ibm.com> <alpine.LRH.2.02.1102181052020.3891@netcore.fi> <20110218144244.GA15397@verdi>
Comments: In-reply-to John Leslie <john@jlc.net> message dated "Fri, 18 Feb 2011 09:42:44 -0500."
Date: Tue, 01 Mar 2011 14:21:35 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 19:20:46 -0000

John Leslie <john@jlc.net> writes:

> Pekka Savola <pekkas@netcore.fi> wrote:
> > On Mon, 17 Jan 2011, Thomas Narten wrote:
> >>>This message starts a 6MAN Working Group Last Call on advancing:
> >> 
> >>>	Title           : IPv6 Node Requirements RFC 4294-bis
> >>>	Author(s)       : E. Jankiewicz, et al.
> >>>	Filename        : draft-ietf-6man-node-req-bis-07.txt
> >
> > I have reviewed this document.
> > 
> > The most important omission is that RFC4294 changelog is not up-to-date.
> > This gives a good overview on what has changed and it needs to convey
> > accurate information.

>    Comparing bis-07 to RFC 4294, the number of changes begins to boggle...

>    I strongly concur with Pekka that this document needs a single
> "changes from 4294" section.

In the works.. :-)

>    And, seeing as 4294 will be five years old by the time 4294-bis is
> published, I'd suggest adding to that section a note on where to look
> for "pending" changes over the next five years. ;^)

:-( ...

>    (BTW, I remain confused on what happened to 5.2.1 of 4294 "Managed
> Address Configuration". Hopefully that will become clearer with a
> single "changes since 4294" section.)

It got yanked. We do not have consensus on what to do with these
flags. I think that is broken, but I believe the proper way to fix
this is via a standalone document that updates the relevant specs.

It is not appropriate to fix that in node requirements.

I've added the following to the changes section:

    16. Removed discussion of "Managed" and "Other" flags in
    RAs. There is no consensus at present on how to process these
    flags and discussion of their semantics was removed in the most
    recent update of Stateless Address Autoconfiguration (RFC 4862).


>    (I suppose this means I volunteer to help draft such a section, but
> to tell truth I'm not sure where to start!)

heh!

Thomas

From kauer@biplane.com.au  Tue Mar  1 14:09:38 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E19B53A69FE for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 14:09:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ad40QUZXAJSV for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 14:09:31 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id D43023A6AF4 for <ipv6@ietf.org>; Tue,  1 Mar 2011 14:09:28 -0800 (PST)
Received: from vpn.cliftons.com ([203.94.133.81] helo=[10.5.104.186]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PuXm3-0004Eh-Dk for ipv6@ietf.org; Tue, 01 Mar 2011 17:10:31 -0500
Subject: Re: question about solicited node multicast addresses
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <AANLkTikmoCvepH0EYh2rS1dPC6OQK-GPWaAXFxsrg5xN@mail.gmail.com>
References: <1298980735.14724.18.camel@karl> <AANLkTikmoCvepH0EYh2rS1dPC6OQK-GPWaAXFxsrg5xN@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Ec/cw2iaHmySjqebhPrK"
Date: Wed, 02 Mar 2011 08:19:57 +1030
Message-ID: <1299016197.14724.31.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Mar 2011 22:09:39 -0000

--=-Ec/cw2iaHmySjqebhPrK
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2011-03-01 at 08:21 -0500, TJ wrote:
> On Tue, Mar 1, 2011 at 06:58, Karl Auer <kauer@biplane.com.au> wrote:
> This is not a satisfying theory because it appears to tie layer 3
> multicast to a specific layer 2 technology (Ethernet, with its 48-bit
> MAC addresses).
>=20
> Factoring reality in to any decision typically yields better results,
> yes?

Sure.

> More importantly - what problem are you really trying to solve?  Do
> you expect to have lots of collisions in this 24 bit space on a given
> link?

I'm not trying to solve a problem. I'm seeking to understand why a thing
is the way it is.

At this stage I have received as answers only rhetorical questions and
the statement that 24 is enough bits. 24 certainly is enough bits - I'm
just wondering why 24 was chosen, as any greater number up to about 100
would also be "enough", and would cost no more to paste into the SNM
address. There is space for more (up to 31) of those bits in the
underlying layer 2 multicast address (for ethernet at least), which
would be "better" than 24 in some senses, though I can see that returns
are starting to diminish.

So from anyone who actually knows - why 24 bits? And why spend 8 bits of
the ethernet multicast address on what appears to be a simple
discrimination between the all-nodes multicast address and SNM
addresses? For example, it might be easier and faster to check for "all
ones" in a whole octet than to test a single bit - that would explain
why ff was used as the discriminator instead of just one bit, and the
need for that octet would explain why 24 instead of 31 bits were used
from the SNM address. But again, that's just a theory, I have no clue as
to whether this is actually the case.

I repeat - this is not a criticism, it is a simply desire to know. To
me, it's an interesting question.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-Ec/cw2iaHmySjqebhPrK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1taf4ACgkQMAcU7Vc29oeBZgCfZYswWZIZrFDz3xZ3YCRAHpzo
uPIAoK3Ualb76sXFJddYYCIvK7Sp7S8m
=/bOh
-----END PGP SIGNATURE-----

--=-Ec/cw2iaHmySjqebhPrK--


From yhb810501@gmail.com  Tue Mar  1 17:20:30 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91F353A6AC3 for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 17:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.102
X-Spam-Level: *
X-Spam-Status: No, score=1.102 tagged_above=-999 required=5 tests=[AWL=3.700,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7aG6QHVkOdiN for <ipv6@core3.amsl.com>; Tue,  1 Mar 2011 17:20:29 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 9C8513A6A21 for <ipv6@ietf.org>; Tue,  1 Mar 2011 17:20:29 -0800 (PST)
Received: by vxg33 with SMTP id 33so5333445vxg.31 for <ipv6@ietf.org>; Tue, 01 Mar 2011 17:21:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=SCm4PAGy8gbbw/9f5fbvCU+NlEp79DuocLGaWA22u3A=; b=Cw8HR/5NOOrSc7B20FgKz1zgN9TXV2iS4W3WANuQWpkFNJPco6H/HTO87crDQkB2cB g+Nbq5w0cazoH21eHawbg8NOA3JNJXxdZGtsZ/VUXn68E5Qv83oqJogPi6Ku1HzU43VU rBPQmm2YEL9wWvN7vQTrl5Io52WsCWuX8i8Kg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=WeNLt/YVo/ysDhSxfWMO0WtydwAhrpMYOY/bp+Rc1GUPHN/Zh12F4IeHUzW8yC6jKH m3yKAnQCRJy956fLUYxPNBnx6X31x3TeUkZp3DbcGQo3cN8QZK5JeBR9czrUph5axKwi P2wsTyWSt/EKnk8nuLKBbqfrtNZ6p6VMG85sc=
MIME-Version: 1.0
Received: by 10.52.179.99 with SMTP id df3mr8198748vdc.195.1299028893710; Tue, 01 Mar 2011 17:21:33 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Tue, 1 Mar 2011 17:21:33 -0800 (PST)
Date: Wed, 2 Mar 2011 09:21:33 +0800
Message-ID: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>
Subject: draft-yhb-6man-slaac-improvement-00
From: huabing yu <yhb810501@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=bcaec5014c51c3379a049d75bb43
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 01:20:30 -0000

--bcaec5014c51c3379a049d75bb43
Content-Type: text/plain; charset=ISO-8859-1

Hi.
This is my draft, the link is

http://datatracker.ietf.org/doc/draft-yhb-6man-slaac-improvement/?include_text=1

Please give some advice.Thank you.

Abstract
IPv6 stateless address autoconfiguration described by RFC4862 only supports
64-bit prefixes. This approach can't be deployed in the sites with prefixes
longer than 64. We have no right to require that the sites MUST use 64-bit
prefixes. This document tries to implement stateless address
autoconfiguration with prefixes longer than 64.

Yu Hua bing

--bcaec5014c51c3379a049d75bb43
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi.</div><div>This is my draft, the link is=A0</div><div><br></div><a =
href=3D"http://datatracker.ietf.org/doc/draft-yhb-6man-slaac-improvement/?i=
nclude_text=3D1" target=3D"_blank">http://datatracker.ietf.org/doc/draft-yh=
b-6man-slaac-improvement/?include_text=3D1</a><div>
<br></div><div><span>Please give some advice.Thank you.</span></div><div><s=
pan><br></span></div><div>
<span>Abstract</span></div><div><span></span>
   IPv6 stateless address autoconfiguration described by RFC4862 only=20
   supports 64-bit prefixes. This approach can&#39;t be deployed in the=20
   sites with prefixes longer than 64. We have no right to require that=20
   the sites MUST use 64-bit prefixes. This document tries to implement
   stateless address autoconfiguration with prefixes longer than 64.</div><=
div><br></div><div>Yu Hua bing</div>

--bcaec5014c51c3379a049d75bb43--

From yhb810501@gmail.com  Wed Mar  2 05:23:53 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1D5A3A67D3 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 05:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.734
X-Spam-Level: 
X-Spam-Status: No, score=-2.734 tagged_above=-999 required=5 tests=[AWL=-0.136, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u++m-yBabXTC for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 05:23:52 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 98DA93A67AD for <ipv6@ietf.org>; Wed,  2 Mar 2011 05:23:52 -0800 (PST)
Received: by vxg33 with SMTP id 33so5784033vxg.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 05:24:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:references:in-reply-to :subject:date:mime-version:content-type:x-priority:x-msmail-priority :importance:x-mailer:x-mimeole; bh=Oiw/9f+vmH9M6ryqjUy05EdDCXymkxx7UyrAD81tY6M=; b=jECLrh6/tTHTuZuPpstn59Os2mtxp832F8C1kSepe8HMmemZ1JCzc83OkZvjjOiT1G piNdjRajjvN8WFNGEbKVPfo474l+5SP8VJJVCLfuZkwwW07JYGMOS+8b4yk6wzk5nRST PSq83XFM5g+Z3Vxokuo3QHLTtn6V9KW2S8C4c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:references:in-reply-to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; b=BClwDYPNFWKVfC+Z7qMKJE0oy9muzeuZckLikXqsUPNjsEMikqL1ebOr2Dwc97Bcyz XiSZdy2/dITHKyhJfq5U2Nr+LJpj5ct2yst3k6h7weO7oh0vZg9Upn4Phd9KdVxVnQEO Xm/GXGiNPLelYr4vt7HkfXUo2b2qp9qzYCiS4=
Received: by 10.52.89.103 with SMTP id bn7mr7292769vdb.289.1299072297833; Wed, 02 Mar 2011 05:24:57 -0800 (PST)
Received: from yhbPC ([220.200.0.167]) by mx.google.com with ESMTPS id i7sm1182218vdu.45.2011.03.02.05.24.54 (version=SSLv3 cipher=OTHER); Wed, 02 Mar 2011 05:24:56 -0800 (PST)
Message-ID: <A7BE2CABE2FE4699BEBB2E2B7CE19A71@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <trejrco@gmail.com>, <ipv6@ietf.org>
References: <AANLkTikpe2bTeSJMcFpWVQeRJPD4bLN=WzLZanWgkZ4q@mail.gmail.com>
In-Reply-To: <AANLkTikpe2bTeSJMcFpWVQeRJPD4bLN=WzLZanWgkZ4q@mail.gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Date: Wed, 2 Mar 2011 21:24:45 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01CBD920.40B5ACA0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 13:23:53 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_0009_01CBD920.40B5ACA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

If the prefix of the site is longer than 64, the stateless address =
autoconfiguration cannot be used and the=20
convenience it will bring cannot be shared.

I hope that SLAAC can be deployed in the sites which use the prefixes =
longer than 64. Not all sites use=20
the 64-bit prefixes.





From: TJ=20
Sent: Wednesday, March 02, 2011 9:50 AM
To: huabing yu=20
Subject: Re: draft-yhb-6man-slaac-improvement-00


Let me play devil's advocate:

What problem are you really trying to solve?  Have you balanced the =
perceived value of the fix with the impact of implementing such =
(especially vendor responsibilities and user expectations!)?

Why would a site receive such a short prefix/block? (Aside from gross =
failure in planning, that is.)

Regarding "no right" - is that like saying we have "no right" to require =
49 bit MACs?  Also, as you say it atleast twice - are you sure the IETF =
doesn't actually have the right?


Also, /s/detect/defect ... And note that this is a perceived defect, =
which most implementations don't see as a real problem.  Oh, and =
"scream" - really?


Thanks, TJ's Droid2 ... Pls excuse the top-posting.

On Mar 1, 2011 8:21 PM, "huabing yu" <yhb810501@gmail.com> wrote:

------=_NextPart_000_0009_01CBD920.40B5ACA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri>If the prefix of the site is longer than 64,=20
the&nbsp;stateless address autoconfiguration cannot be used and the=20
<BR>convenience it will bring cannot be shared.</FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>I hope that SLAAC can be deployed in the sites =
which use=20
the prefixes longer than 64. Not all sites use </FONT></DIV>
<DIV><FONT face=3DCalibri>the 64-bit prefixes.</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp;</DIV>
<DIV><BR></DIV></FONT>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dtrejrco@gmail.com=20
href=3D"mailto:trejrco@gmail.com">TJ</A> </DIV>
<DIV><B>Sent:</B> Wednesday, March 02, 2011 9:50 AM</DIV>
<DIV><B>To:</B> <A title=3D"mailto:yhb810501@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:yhb810501@gmail.com">huabing yu</A> </DIV>
<DIV><B>Subject:</B> Re: =
draft-yhb-6man-slaac-improvement-00</DIV></DIV></DIV>
<DIV><BR></DIV>
<P>Let me play devil's advocate:</P>
<P>What problem are you really trying to solve?&nbsp; Have you balanced =
the=20
perceived value of the fix with the impact of implementing such =
(especially=20
vendor responsibilities and user expectations!)?</P>
<P>Why would a site receive such a short prefix/block? (Aside from gross =
failure=20
in planning, that is.)</P>
<P>Regarding "no right" - is that like saying we have "no right" to =
require 49=20
bit MACs?&nbsp; Also, as you say it atleast twice - are you sure the =
IETF=20
doesn't actually have the right?<BR></P>
<P>Also, /s/detect/defect ... And note that this is a perceived defect, =
which=20
most implementations don't see as a real problem.&nbsp; Oh, and "scream" =
-=20
really?<BR></P>
<P>Thanks, TJ's Droid2 ... Pls excuse the top-posting.</P>
<DIV class=3Dgmail_quote>On Mar 1, 2011 8:21 PM, "huabing yu" &lt;<A=20
title=3D"mailto:yhb810501@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:yhb810501@gmail.com">yhb810501@gmail.com</A>&gt; =
wrote:<BR=20
type=3D"attribution"></DIV></BODY></HTML>

------=_NextPart_000_0009_01CBD920.40B5ACA0--


From Francis.Dupont@fdupont.fr  Wed Mar  2 05:28:18 2011
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EFA63A67D8 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 05:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUA3nPz5XNbe for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 05:28:16 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [91.121.26.85]) by core3.amsl.com (Postfix) with ESMTP id BB4123A67F1 for <ipv6@ietf.org>; Wed,  2 Mar 2011 05:28:15 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p22DTJ1r039775; Wed, 2 Mar 2011 14:29:20 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201103021329.p22DTJ1r039775@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: question about solicited node multicast addresses 
In-reply-to: Your message of Wed, 02 Mar 2011 08:19:57 +1030. <1299016197.14724.31.camel@karl> 
Date: Wed, 02 Mar 2011 14:29:19 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 13:28:19 -0000

 In your previous mail you wrote:

   I'm not trying to solve a problem. I'm seeking to understand why a thing
   is the way it is.
   
=> there are two parts:
 - why was it accepted? As I was involved in IPv6 design at that stage
  I can answer:
   * the proposal looked sane (i.e., it did what we wanted)
   * collisions were rare and not annoying (needs 4096 (2^(24/2)) nodes
    to get .5 probability)
   * fits well to Ethernet (which was the far most common shared link at
    this time, and perhaps even more common today :-)
   * 8 bit boundary, i.e., clearly straightforward to implement
   * no other proposal (IMHO the main point! :-)
  so nobody raised a concern and it reached rough consensus in one step.

 - what is exactly the idea behind the design?
 You should try to find the author of the initial I-D, wish (s)he is not
 dead or retired, or perhaps switch to the ih (Internet History) mailing
 list (perhaps too soon for IPv6 but BTW your question is not really
 technical, is it?).

Thanks

Francis.Dupont@fdupont.fr

From brian.e.carpenter@gmail.com  Wed Mar  2 12:57:05 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B61123A686E for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 12:57:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.467
X-Spam-Level: 
X-Spam-Status: No, score=-103.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Qol+BeSe4G2 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 12:57:04 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 848363A6864 for <ipv6@ietf.org>; Wed,  2 Mar 2011 12:57:04 -0800 (PST)
Received: by fxm15 with SMTP id 15so445158fxm.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 12:58:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=M8LDnHbnmjgHNMZn4CwOVjg6dhqxE83G1/g1sct+az8=; b=VBnYpUe17yraGEghLp/KJIbR6OKBJ8XfPWoqO5nihY8QSOuMPaYjTP8P+BJ/uGUgao 4T3Jaa5P3K5WDhE+5RnHwJK2IkaGfLzlPfplKHBW0paWZ9kZsgwd3HP7T6hukrtHEl7A veFoTueL+AgGx08gFqJkZ9jx2LJVKIZ2LwxDk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=UnQfUCuOvrWmGb9voV5P1Cj5KoBvfTuqAjaAumRmLtFgX04Ycm8EJap9s/B9Q2bsah nPgjILQqbsNoXDfojzuLABC8prH4li3j4rdNvhPU41AgvJHMhLE1n2kWO1fGN/oqqRdr trkebVAMfq+GfuU+PLF9l6Yi3RmTGn6eOwMes=
Received: by 10.223.83.201 with SMTP id g9mr411868fal.140.1299099489523; Wed, 02 Mar 2011 12:58:09 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id o12sm226824fav.30.2011.03.02.12.58.06 (version=SSLv3 cipher=OTHER); Wed, 02 Mar 2011 12:58:08 -0800 (PST)
Message-ID: <4D6EAF57.8050606@gmail.com>
Date: Thu, 03 Mar 2011 09:57:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: huabing yu <yhb810501@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>
In-Reply-To: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 20:57:05 -0000

Hi

> We have no right to require that the sites MUST use 64-bit prefixes.

Actually, we do have that right. Since the IETF sets Internet standards,
we can write exactly what we want to. IETF standards are voluntary,
so sites have the right to ignore them too. However, if they do that,
they will not be able to interoperate with the Internet.

An accurate sentence for the draft would therefore be

[RFC4862] requires that subnets operating stateless address
autoconfiguration use 64 bit prefixes, and [RFC4291] requires
that interface identifiers conform to modified EUI-64 format.

However, the draft does not explain why this is a problem.
Since the Internet has only just run out of 24 bit prefixes,
why is there a risk of running out of 64 bit prefixes?

By the way, the proposed solution will not work with FireWire.

Regards
   Brian Carpenter




On 2011-03-02 14:21, huabing yu wrote:
> Hi.
> This is my draft, the link is
> 
> http://datatracker.ietf.org/doc/draft-yhb-6man-slaac-improvement/?include_text=1
> 
> Please give some advice.Thank you.
> 
> Abstract
> IPv6 stateless address autoconfiguration described by RFC4862 only supports
> 64-bit prefixes. This approach can't be deployed in the sites with prefixes
> longer than 64. We have no right to require that the sites MUST use 64-bit
> prefixes. This document tries to implement stateless address
> autoconfiguration with prefixes longer than 64.
> 
> Yu Hua bing
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From narten@us.ibm.com  Wed Mar  2 13:25:05 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA4523A6850 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 13:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-2.500, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oi6ZTBp7mB0f for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 13:25:04 -0800 (PST)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by core3.amsl.com (Postfix) with ESMTP id 95EA33A6816 for <ipv6@ietf.org>; Wed,  2 Mar 2011 13:25:04 -0800 (PST)
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e35.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p22LBDbc015537 for <ipv6@ietf.org>; Wed, 2 Mar 2011 14:11:13 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id p22LQ0Qo113984 for <ipv6@ietf.org>; Wed, 2 Mar 2011 14:26:00 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p22LPx2s012017 for <ipv6@ietf.org>; Wed, 2 Mar 2011 14:25:59 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-76-132-232.mts.ibm.com [9.76.132.232]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p22LPwMB011942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Mar 2011 14:25:59 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p22LPljL020592; Wed, 2 Mar 2011 16:25:47 -0500
Message-Id: <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-reply-to: <4D6EAF57.8050606@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Thu, 03 Mar 2011 09:57:59 +1300."
Date: Wed, 02 Mar 2011 16:25:47 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: ipv6@ietf.org, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 21:25:06 -0000

> [RFC4862] requires that subnets operating stateless address
> autoconfiguration use 64 bit prefixes,

Actually, not true! Stateless address autoconfiguration supports
different prefix lengths just fine. That was a deliberate design
decision, even after we switched to 64-bit Interface IDs. E.g (from
4862):

   A link-local address is formed by combining the well-known link-local
   prefix FE80::0 [RFC4291] (of appropriate length) with an interface
   identifier as follows:

   1.  The left-most 'prefix length' bits of the address are those of
       the link-local prefix.

   2.  The bits in the address to the right of the link-local prefix are
       set to all zeroes.

   3.  If the length of the interface identifier is N bits, the right-
       most N bits of the address are replaced by the interface
       identifier.

   If the sum of the link-local prefix length and N is larger than 128,
   autoconfiguration fails and manual configuration is required.  The
   length of the interface identifier is defined in a separate link-
   type-specific document, which should also be consistent with the
   address architecture [RFC4291] (see Section 2).  These documents will
   carefully define the length so that link-local addresses can be
   autoconfigured on the link.

and so on.

> and [RFC4291] requires that interface identifiers conform to
> modified EUI-64 format.

That is where the effective requirement is hard coded in. 

Thomas

From brian.e.carpenter@gmail.com  Wed Mar  2 14:09:07 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3FD53A67D9 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.971
X-Spam-Level: 
X-Spam-Status: No, score=-100.971 tagged_above=-999 required=5 tests=[AWL=-2.372, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6sDOMcLq3Jz for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:09:07 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id C02B93A67B5 for <ipv6@ietf.org>; Wed,  2 Mar 2011 14:09:06 -0800 (PST)
Received: by fxm15 with SMTP id 15so519534fxm.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 14:10:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9I+sd/8vHcwW8yJiNJDIr7DxNgJemiPJW6llsDgsMsM=; b=lvpn10/wW//a/KMYdGLFJpT2taZ0wol6g4vbPEhzhCypVMYQFIwX+ObLS9DrmaJx8c e4IABkBNeu/tQFQAt/PflfCEtqwtM5awtIu2fiyW1MBkvxgbLzS3vF4iKDDZ3TmDDz2t SCYwWdI+Nspqxf8zoGTka+xMPtCaD7hZriNkY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=ExnMruEk6CJjQEdwjE573v3crBStt0oPeVzUAO6V62sbtnO1NTjb/IMET4AIsXjyiP eDBpLJzDS4JYqQIbNI0Cv1eJJv5fJ+u+bqi8AKqH6S0Cn/qQbb+JlaQw80C7csBl6lco JCezvwv7fhe7tkTshNlsNNxAWtQbubieM3UBg=
Received: by 10.223.83.16 with SMTP id d16mr486286fal.148.1299103812431; Wed, 02 Mar 2011 14:10:12 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id n15sm267831fam.36.2011.03.02.14.10.09 (version=SSLv3 cipher=OTHER); Wed, 02 Mar 2011 14:10:11 -0800 (PST)
Message-ID: <4D6EC041.4070304@gmail.com>
Date: Thu, 03 Mar 2011 11:10:09 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com>
In-Reply-To: <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 22:09:07 -0000

I stand corrected.

BTW there is also the issue of interaction with ILNP, which
has been recommended to the IETF by the RRG chairs.

   Brian

On 2011-03-03 10:25, Thomas Narten wrote:
>> [RFC4862] requires that subnets operating stateless address
>> autoconfiguration use 64 bit prefixes,
> 
> Actually, not true! Stateless address autoconfiguration supports
> different prefix lengths just fine. That was a deliberate design
> decision, even after we switched to 64-bit Interface IDs. E.g (from
> 4862):
> 
>    A link-local address is formed by combining the well-known link-local
>    prefix FE80::0 [RFC4291] (of appropriate length) with an interface
>    identifier as follows:
> 
>    1.  The left-most 'prefix length' bits of the address are those of
>        the link-local prefix.
> 
>    2.  The bits in the address to the right of the link-local prefix are
>        set to all zeroes.
> 
>    3.  If the length of the interface identifier is N bits, the right-
>        most N bits of the address are replaced by the interface
>        identifier.
> 
>    If the sum of the link-local prefix length and N is larger than 128,
>    autoconfiguration fails and manual configuration is required.  The
>    length of the interface identifier is defined in a separate link-
>    type-specific document, which should also be consistent with the
>    address architecture [RFC4291] (see Section 2).  These documents will
>    carefully define the length so that link-local addresses can be
>    autoconfigured on the link.
> 
> and so on.
> 
>> and [RFC4291] requires that interface identifiers conform to
>> modified EUI-64 format.
> 
> That is where the effective requirement is hard coded in. 
> 
> Thomas
> 

From scott.brim@gmail.com  Wed Mar  2 14:22:52 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EF373A68BD for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6k3zOUcRbjLM for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:22:51 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 258233A68B5 for <ipv6@ietf.org>; Wed,  2 Mar 2011 14:22:51 -0800 (PST)
Received: by gxk5 with SMTP id 5so174724gxk.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 14:23:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=t7mxkOVLwp1r3iAbmP8YYXZ4PEdU6v/Z6UtX9XnLf+k=; b=N27BZOAEy1q2O76hS6xIx+qL4NfdFUyDjk4XCx0nEccgUUz0Kt9vwVMxBUFTuSTozq u8SWo5UvRMrkInb3X1Ob4WbgOKB6LX2f8y4JJAwIHtPU+X0KAw9HJRwx/JRgfZcmBxIt 2rpqrB9VePKfg2ankG1KE10i31WH40KkLrtLw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=r0AY6DpSK7S8OlrMNa7FEulC7G7/4QySJJ7/sMvo58iByM+t7hwWoLNO4NY6FU05tS wZ5UsF8jK5qIIUOZ468qintw1gDwC/YiWcooAxuRQWjJiXC12LkklrqxtzuBGOGTjaoF G3IID4DG1+ZoT7/Gwkm2PCL5fTpQ2Rp7d2Si4=
MIME-Version: 1.0
Received: by 10.91.27.31 with SMTP id e31mr943153agj.79.1299104637585; Wed, 02 Mar 2011 14:23:57 -0800 (PST)
Received: by 10.90.40.25 with HTTP; Wed, 2 Mar 2011 14:23:57 -0800 (PST)
In-Reply-To: <4D6EC041.4070304@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com>
Date: Wed, 2 Mar 2011 17:23:57 -0500
Message-ID: <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
From: Scott W Brim <scott.brim@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001485f913c6730b9e049d875e29
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 22:22:52 -0000

--001485f913c6730b9e049d875e29
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Mar 2, 2011 at 17:10, Brian E Carpenter <brian.e.carpenter@gmail.com
> wrote:

> BTW there is also the issue of interaction with ILNP, which
> has been recommended to the IETF by the RRG chairs.
>

ILNP is barely experimental, its probability of being widely deployed is
totally unknown, and in any case sites that want to run ILNP MAY adhere to a
64-bit minimum themselves without making that even a SHOULD for everyone.

Scott

--001485f913c6730b9e049d875e29
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 2, 2011 at 17:10, 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><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1p=
x solid rgb(204, 204, 204); padding-left: 1ex;">

BTW there is also the issue of interaction with ILNP, which<br>
has been recommended to the IETF by the RRG chairs.<br></blockquote><div><b=
r>ILNP is barely experimental, its probability of being widely deployed is =
totally unknown, and in any case sites that want to run ILNP MAY adhere to =
a 64-bit minimum themselves without making that even a SHOULD for everyone.=
<br>
<br>Scott<br>
</div><div><br>=A0</div></div>

--001485f913c6730b9e049d875e29--

From brian.e.carpenter@gmail.com  Wed Mar  2 14:31:39 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31A7F3A68BD for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:31:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.437
X-Spam-Level: 
X-Spam-Status: No, score=-103.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HlNLuC9PgOhX for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:31:38 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 1B1A43A68B5 for <ipv6@ietf.org>; Wed,  2 Mar 2011 14:31:37 -0800 (PST)
Received: by wwb22 with SMTP id 22so476761wwb.13 for <ipv6@ietf.org>; Wed, 02 Mar 2011 14:32:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ukzqn4hVI/WjoVm7XOqTkNAmNkAPK1OWrnpGWCqz6jA=; b=N7fx7SAsmnNIoyHid+BhOzdQrfxv7jWX3J8RvIX0MyLJqp3d//CBafzIWMHWpql0Og H77X96Jb6feyAf6TxqqsYqTOFOUPCl64GTd6u7u5GWREswApLzf+IS86EgdCYwvizb0X 0CroqcwIq6UP9pRb6PNSeh+IWPw4TFimdzX00=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=tL2ILz69seBPNYOqjTLjH3kAqHr74C9GJHW5E9WgEW3R8PkWi387vxbr4v8j/oexoy 8Lwf9CNAX1LE9XDmkuJ6SAwlL6tg0pe9BueRGUKcWK2flBRM8rhvpKJOCFe/mNd2kcEA EM7msoTRlU3xp4KTaku5Fefs8QTDKV3GooMX0=
Received: by 10.227.138.147 with SMTP id a19mr252816wbu.68.1299105163388; Wed, 02 Mar 2011 14:32:43 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id x1sm135514wbh.8.2011.03.02.14.32.39 (version=SSLv3 cipher=OTHER); Wed, 02 Mar 2011 14:32:42 -0800 (PST)
Message-ID: <4D6EC58A.6050404@gmail.com>
Date: Thu, 03 Mar 2011 11:32:42 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott W Brim <scott.brim@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>	<4D6EAF57.8050606@gmail.com>	<201103022125.p22LPljL020592@cichlid.raleigh.ibm.com>	<4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com>
In-Reply-To: <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 22:31:39 -0000

On 2011-03-03 11:23, Scott W Brim wrote:
> On Wed, Mar 2, 2011 at 17:10, Brian E Carpenter <brian.e.carpenter@gmail.com
>> wrote:
> 
>> BTW there is also the issue of interaction with ILNP, which
>> has been recommended to the IETF by the RRG chairs.
>>
> 
> ILNP is barely experimental, its probability of being widely deployed is
> totally unknown, and in any case sites that want to run ILNP MAY adhere to a
> 64-bit minimum themselves without making that even a SHOULD for everyone.

That's all certainly true. However, the idea that we might have one set of
sites running ILNP and another set of sites running >64 bit prefixes seems
like Balkanization to me, even though it may not strictly speaking cause
interoperability failures. In any case my point is that it should be mentioned
in the draft, like the Firewire issue.

I'd rather get IPv6 deployed in a uniform way first.

   Brian

From trejrco@gmail.com  Wed Mar  2 14:57:31 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B97CB3A6892 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.156
X-Spam-Level: 
X-Spam-Status: No, score=-3.156 tagged_above=-999 required=5 tests=[AWL=0.442,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mt9etyOwfGP6 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 14:57:30 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id AC2BF3A6816 for <ipv6@ietf.org>; Wed,  2 Mar 2011 14:57:30 -0800 (PST)
Received: by iyj8 with SMTP id 8so462989iyj.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 14:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=dYEAeIQVuGgi6fPZfPvSnX5m0UJ/3FtJ3MI2oZCnwHs=; b=wjT5kjcK65R4D8DvM6xajl9ItN7qKVAyVu5oqU+A3a0+pU6W4gCjMc4uMBvZVPEywj dtFdot6XT8LDrnSz/hmWtX8GxqdZnI5T/pvEqI9D63/OFibVBDnuWwDc+4F5jGk0Of4M uxo1ZqJNm5esSmNeDlpoowfFPPvHebMCp0MC8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=lYuAiLUpt/pHeejX+9m7nkednAnksBmioMagDMNU3lh+wFyBLM80ZW6bgDds3PhhLq 5GTyuKZtfqFJGsCK/DGoiCzP3Abg3B2kklBraxW3c9kX0zFQQTYYDlyDP55TghDPCN3b YCl5GhSggn59I5qsInud7tpLSNyOBqEpSETJo=
MIME-Version: 1.0
Received: by 10.231.19.68 with SMTP id z4mr369243iba.65.1299106717328; Wed, 02 Mar 2011 14:58:37 -0800 (PST)
Received: by 10.231.148.143 with HTTP; Wed, 2 Mar 2011 14:58:37 -0800 (PST)
In-Reply-To: <4D6EC58A.6050404@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com>
Date: Wed, 2 Mar 2011 17:58:37 -0500
Message-ID: <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
From: TJ <trejrco@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=00221532cd00696757049d87dae9
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 Mar 2011 22:57:31 -0000

--00221532cd00696757049d87dae9
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter <brian.e.carpenter@gmail.com
> wrote:

<snip>

I'd rather get IPv6 deployed in a uniform way first.
>

I'd take that sentence a step or two further:

"I'd rather get IPv6 deployed in a uniform way."

or even simpler:

"I'd rather get IPv6 deployed."


To be (perhaps overly) blunt: IMHO the changes proposed in this draft create
unneeded confusion, solve a problem that is either non-existent or is
readily solved in other ways and can create functional problems / detriments
to actual deployment.

Note: I am ready, willing and (often!) able to be proven wrong ... (and
welcome the conversation!)



/TJ

--00221532cd00696757049d87dae9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div><div class=3D"gmail_quote">On Wed, Mar 2, 2011 at 17:32, Brian E Carpe=
nter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">b=
rian.e.carpenter@gmail.com</a>&gt;</span> wrote:</div><div class=3D"gmail_q=
uote">
<br></div><div class=3D"gmail_quote">&lt;snip&gt;</div><div class=3D"gmail_=
quote"><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex;">I&#39;d rather get IPv6 deployed=
 in a uniform way first.<br>
</blockquote><div><br></div><div>I&#39;d take that sentence a step or two f=
urther:</div></div></div><blockquote class=3D"webkit-indent-blockquote" sty=
le=3D"margin: 0 0 0 40px; border: none; padding: 0px;"><div><div class=3D"g=
mail_quote">
<div>&quot;<span class=3D"Apple-style-span" style=3D"border-collapse: colla=
pse; color: rgb(32, 32, 32); font-family: &#39;Droid Sans&#39;, arial, sans=
-serif; font-size: 13px; ">I&#39;d rather get IPv6 deployed in a uniform wa=
y.</span>&quot;=A0</div>
</div></div></blockquote>or even simpler:<blockquote class=3D"webkit-indent=
-blockquote" style=3D"margin: 0 0 0 40px; border: none; padding: 0px;"><div=
>&quot;<span class=3D"Apple-style-span" style=3D"border-collapse: collapse;=
 color: rgb(32, 32, 32); font-family: &#39;Droid Sans&#39;, arial, sans-ser=
if; font-size: 13px; ">I&#39;d rather get IPv6 deployed.</span>&quot;</div>
<div><br></div></blockquote><div><br></div>To be (perhaps overly) blunt: IM=
HO the changes proposed in this draft create unneeded confusion, solve a pr=
oblem that is either non-existent or is readily solved in other ways and ca=
n create functional problems / detriments to actual deployment. =A0<div>
<br></div><div>Note:=A0I am ready, willing and (often!) able to be proven w=
rong ... (and welcome the conversation!)<div><br></div><div><br></div><div>=
<br></div><div>/TJ</div></div>

--00221532cd00696757049d87dae9--

From randy@psg.com  Wed Mar  2 16:37:16 2011
Return-Path: <randy@psg.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AFC93A68AE for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 16:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.58
X-Spam-Level: 
X-Spam-Status: No, score=-4.58 tagged_above=-999 required=5 tests=[AWL=2.019,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZ8BrY84lskF for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 16:36:56 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [147.28.0.36]) by core3.amsl.com (Postfix) with ESMTP id 162F93A67F5 for <ipv6@ietf.org>; Wed,  2 Mar 2011 16:36:56 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PuwX3-0006Rr-8q; Thu, 03 Mar 2011 00:36:41 +0000
Date: Thu, 03 Mar 2011 09:36:39 +0900
Message-ID: <m262s1ox9k.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <4D6EC58A.6050404@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 00:37:16 -0000

> I'd rather get IPv6 deployed in a uniform way first.

try cidr

From yhb810501@gmail.com  Wed Mar  2 17:34:16 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABB213A65A6 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 17:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.631
X-Spam-Level: 
X-Spam-Status: No, score=-0.631 tagged_above=-999 required=5 tests=[AWL=2.967,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZpK1Xjose-6g for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 17:34:15 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id C75593A6359 for <ipv6@ietf.org>; Wed,  2 Mar 2011 17:34:15 -0800 (PST)
Received: by vws6 with SMTP id 6so604377vws.31 for <ipv6@ietf.org>; Wed, 02 Mar 2011 17:35:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=uYa5jFYttw90Bzo3TvxN0WOc8n94uIRZssnySk7wKL4=; b=oeNFvgEk5zS2Sb6j7sAOPen17FMgEvoyeRxU2u9a/dOaEEUgCoCsXkSRjjP6ssz9o7 ExsXvLWa+S/cEi0OEiVlXMMBDCfbHPKitpfA9sCZk0Akm5ilxu67tyd3kbAMBh6YvhV8 9iPHgKE/M3grSSJkjMEXMfk8x45G8D51YRjRE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mEVqD9V3/InaJ71V2eJ1eL7zA+fQq7PR7/VSx3+HtcIWVH5PKxBC5yxxrU8kaDJoBV rbR7PcU6oEXlYWL3gNmGhSyY37Cv+Bunm/vdGBtfnEEc9rfkBBFO+ygBmzZe8ReDwvGM 5C7uyryUZqAi0+LC+i9Fdhcvk1Vz59dVv+qcs=
MIME-Version: 1.0
Received: by 10.52.157.4 with SMTP id wi4mr901106vdb.75.1299116122276; Wed, 02 Mar 2011 17:35:22 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Wed, 2 Mar 2011 17:35:22 -0800 (PST)
Date: Thu, 3 Mar 2011 09:35:22 +0800
Message-ID: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com>
Subject: draft-yhb-6man-ra-privacy-flag-01
From: huabing yu <yhb810501@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=bcaec53f91adfd8452049d8a0add
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 01:34:16 -0000

--bcaec53f91adfd8452049d8a0add
Content-Type: text/plain; charset=ISO-8859-1

Hi

I updated the draft "DisablePrivacy Flag of Prefix-information Option in the
Router Advertisement". The flag's name changed from
Privacy to DisablePrivacy.The link is
http://datatracker.ietf.org/doc/draft-yhb-6man-ra-privacy-flag/?include_text=1
.

Do you have some advice?

Yu Hua bing

--bcaec53f91adfd8452049d8a0add
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi<div><br></div><div>I updated the draft &quot;<span class=3D"Apple-style-=
span" style=3D"font-family: monospace; font-size: 13px; line-height: 15px; =
white-space: pre; -webkit-border-horizontal-spacing: 2px; -webkit-border-ve=
rtical-spacing: 2px; ">DisablePrivacy Flag of Prefix-information Option </s=
pan><span class=3D"Apple-style-span" style=3D"font-family: monospace; font-=
size: 13px; line-height: 15px; white-space: pre; -webkit-border-horizontal-=
spacing: 2px; -webkit-border-vertical-spacing: 2px; ">in the Router Adverti=
sement</span>&quot;.=A0<span class=3D"Apple-style-span" style=3D"font-famil=
y: monospace; font-size: 13px; line-height: 15px; white-space: pre; -webkit=
-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Th=
e flag&#39;s name changed from </span></div>
<div><span class=3D"Apple-style-span" style=3D"font-family: monospace; font=
-size: 13px; line-height: 15px; white-space: pre; -webkit-border-horizontal=
-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">Privacy to DisablePr=
ivacy.T</span>he link is=A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-yhb-6man-ra-privacy-flag/?include_text=3D1">http://datatracker.ietf.org/do=
c/draft-yhb-6man-ra-privacy-flag/?include_text=3D1</a>.</div>
<div><br></div><div>Do you have some advice?</div><div><br></div><div>Yu Hu=
a bing</div><div><br></div><div><br></div>

--bcaec53f91adfd8452049d8a0add--

From jhw@apple.com  Wed Mar  2 18:38:02 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E6BC3A6927 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 18:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22VyHLSi49vx for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 18:38:01 -0800 (PST)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 7D85E3A6936 for <ipv6@ietf.org>; Wed,  2 Mar 2011 18:38:01 -0800 (PST)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 508D1D3A79A8 for <ipv6@ietf.org>; Wed,  2 Mar 2011 18:39:08 -0800 (PST)
X-AuditID: 1180711d-b7b1cae000002701-b0-4d6eff4cc383
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay13.apple.com (Apple SCV relay) with SMTP id 79.71.09985.C4FFE6D4; Wed,  2 Mar 2011 18:39:08 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHG00KS8ND7RH10@elliott.apple.com> for ipv6@ietf.org; Wed, 02 Mar 2011 18:39:08 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: james woodyatt <jhw@apple.com>
In-reply-to: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com>
Date: Wed, 02 Mar 2011 18:39:07 -0800
Message-id: <054EBE54-D54C-4154-8C72-0F413F462BB0@apple.com>
References: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com>
To: 6MAN <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1203)
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 02:38:02 -0000

On Mar 2, 2011, at 5:35 PM, huabing yu wrote:
> 
> Do you have some advice?

The current revision of the draft contains a normative reference to RFC 4941 but it doesn't seem to have any language in section 2.3 specifying host behavior that would prevent it from using any other sort of statelessly autoconfigured addresses that would pose the same problem for network administrators that privacy addresses do, i.e. make it difficult to identify authoritatively which host is the originator of any particular traffic given only the source addresses in the captured IPv6 headers.  It just says, hosts MUST have a conceptual variable that controls whether they generate temporary addresses.  That doesn't prevent them from generating persistent ones that pose the same problem for network administrators as RFC 4941 privacy addresses.

I think some wordsmithing is still required here.  I have no useful advice for how to do that because I'm not entirely sure I understand what this draft is hoping to accomplish, much less how it hopes to do it.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From swmike@swm.pp.se  Wed Mar  2 18:57:33 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AA653A6939 for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 18:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.424
X-Spam-Level: 
X-Spam-Status: No, score=-4.424 tagged_above=-999 required=5 tests=[AWL=1.825,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pesdyVL112nP for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 18:57:17 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id BE3793A6403 for <ipv6@ietf.org>; Wed,  2 Mar 2011 18:57:17 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 75C229C; Thu,  3 Mar 2011 03:57:53 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 753CA9A; Thu,  3 Mar 2011 03:57:53 +0100 (CET)
Date: Thu, 3 Mar 2011 03:57:53 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: james woodyatt <jhw@apple.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <054EBE54-D54C-4154-8C72-0F413F462BB0@apple.com>
Message-ID: <alpine.DEB.1.10.1103030352210.7942@uplift.swm.pp.se>
References: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com> <054EBE54-D54C-4154-8C72-0F413F462BB0@apple.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: 6MAN <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 02:57:33 -0000

On Wed, 2 Mar 2011, james woodyatt wrote:

> The current revision of the draft contains a normative reference to RFC 
> 4941 but it doesn't seem to have any language in section 2.3 specifying 
> host behavior that would prevent it from using any other sort of 
> statelessly autoconfigured addresses that would pose the same problem 
> for network administrators that privacy addresses do, i.e. make it 
> difficult to identify authoritatively which host is the originator of 
> any particular traffic given only the source addresses in the captured 
> IPv6 headers.  It just says, hosts MUST have a conceptual variable that 
> controls whether they generate temporary addresses.  That doesn't 
> prevent them from generating persistent ones that pose the same problem 
> for network administrators as RFC 4941 privacy addresses.

In our testing, the only way we found to achieve this was to not announce 
any on-net prefix and using the M-flag to make the client ask for DHCPv6 
address.

I've asked this before in different fora because I have not been able to 
find any RFC text.

Wen an on-link prefix is present and the M-flag is set, RFC4861 says:

M              1-bit "Managed address configuration" flag.  When
                      set, it indicates that addresses are available via
                      Dynamic Host Configuration Protocol [DHCPv6].

It doesn't say "don't do SLAAC and only get addresses from IPv6". So my 
interpretation is that as soon as there is an on-link prefix, hosts will 
do SLAAC regardless of M flag 0 or 1.

So let's say I want to disallow SLAAC, I want to hand out addresses using 
DHCPv6, but I still want the hosts to be able to talk L2 directly to each 
other within the subnet.

How should I configure things when it comes to information in RA and 
DHCPv6? If this isn't possible, was this intentional behaviour from the 
beginning, that DHCPv6 hosts without SLAAC can't get an on-link prefix but 
they must go through the router to talk to each other?

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

From swmike@swm.pp.se  Wed Mar  2 20:06:52 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 930E23A694D for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 20:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.652
X-Spam-Level: 
X-Spam-Status: No, score=-4.652 tagged_above=-999 required=5 tests=[AWL=1.597,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zshG988ccNif for <ipv6@core3.amsl.com>; Wed,  2 Mar 2011 20:06:51 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by core3.amsl.com (Postfix) with ESMTP id BBE0D3A6947 for <ipv6@ietf.org>; Wed,  2 Mar 2011 20:06:51 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id ECA349C; Thu,  3 Mar 2011 05:07:27 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EB2C89A; Thu,  3 Mar 2011 05:07:27 +0100 (CET)
Date: Thu, 3 Mar 2011 05:07:27 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: james woodyatt <jhw@apple.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <alpine.DEB.1.10.1103030352210.7942@uplift.swm.pp.se>
Message-ID: <alpine.DEB.1.10.1103030506190.7942@uplift.swm.pp.se>
References: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com> <054EBE54-D54C-4154-8C72-0F413F462BB0@apple.com> <alpine.DEB.1.10.1103030352210.7942@uplift.swm.pp.se>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: 6MAN <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 04:06:52 -0000

On Thu, 3 Mar 2011, Mikael Abrahamsson wrote:

> How should I configure things when it comes to information in RA and 
> DHCPv6? If this isn't possible, was this intentional behaviour from the 
> beginning, that DHCPv6 hosts without SLAAC can't get an on-link prefix 
> but they must go through the router to talk to each other?

I have received help off-list for this, evidently there is a Cisco option 
called "no-autoconf" that sets the A bit to 0 on the on-link prefix 
announcement, that does what I was asking for.

Thanks!

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

From bob.hinden@gmail.com  Thu Mar  3 02:02:10 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E0853A6827 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 02:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.504
X-Spam-Level: 
X-Spam-Status: No, score=-103.504 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8ob6dft6Qsf for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 02:02:09 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 186AE3A6809 for <ipv6@ietf.org>; Thu,  3 Mar 2011 02:02:08 -0800 (PST)
Received: by bwz13 with SMTP id 13so1169805bwz.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 02:03:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=QyM0tpXgihOe5u3Mcw6RBwwypwb25dbDZwzw8Rhkn9I=; b=rmy/OU6Lf9+xScODKiKQSymMmgSF3SWU7gxx1S2vp5R3e1On7floVgTG23lZss9408 EkLqALUV7/axhP1pvM/14Nx/MXCCE0qESrtWXlRDQcLdkysbFH9L2lz/Xj6hshJXmCxA a0itMawC6sDijc05DOzPEodBVtJ/j5dAw3Wt0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=cfbZm3FAL9/g4SH9wxTrJUAH8sanRBtlxhGZOQt2pJQZ2miItTe335wnzl1Z/ZwU/x GaAx53vKm5LEUTEbOdrkNZzTgGNpj1SiF5YntM+urZJAi1kmbioAF+ydKjm4ERvQdEgN 3U5WzgVtZvevwPjTcg4g1d6pWSOBZF79MCwQg=
Received: by 10.204.76.65 with SMTP id b1mr1194867bkk.29.1299146595955; Thu, 03 Mar 2011 02:03:15 -0800 (PST)
Received: from [172.24.249.63] (dyn32-131.checkpoint.com [194.29.32.131]) by mx.google.com with ESMTPS id w3sm613781bkt.17.2011.03.03.02.03.13 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 Mar 2011 02:03:14 -0800 (PST)
Subject: Re: draft-yhb-6man-slaac-improvement-00
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>
Date: Thu, 3 Mar 2011 12:03:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA43223D-9EA2-4A75-8972-E7DFE27B01DC@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com> <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>
To: trejrco@gmail.com
X-Mailer: Apple Mail (2.1082)
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Scott W Brim <scott.brim@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 10:02:10 -0000

On Mar 3, 2011, at 12:58 AM, TJ wrote:

> On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> <snip>
>=20
> I'd rather get IPv6 deployed in a uniform way first.
>=20
> I'd take that sentence a step or two further:
> "I'd rather get IPv6 deployed in a uniform way."=20
> or even simpler:
> "I'd rather get IPv6 deployed."
>=20
>=20
> To be (perhaps overly) blunt: IMHO the changes proposed in this draft =
create unneeded confusion, solve a problem that is either non-existent =
or is readily solved in other ways and can create functional problems / =
detriments to actual deployment. =20

+1

Bob



From yhb810501@gmail.com  Thu Mar  3 06:49:33 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ABD43A67E7 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 06:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.221
X-Spam-Level: 
X-Spam-Status: No, score=-3.221 tagged_above=-999 required=5 tests=[AWL=0.377,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfjUktOqCL5S for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 06:49:32 -0800 (PST)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 7D5763A67B2 for <ipv6@ietf.org>; Thu,  3 Mar 2011 06:49:32 -0800 (PST)
Received: by pxi6 with SMTP id 6so236746pxi.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 06:50:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:x-priority:x-msmail-priority :importance:x-mailer:x-mimeole; bh=xlY87t78lK9d2WjE4i6HruZ1sOlE1jjwjIuPdyMMPaw=; b=pE520Xu/0LOW28NeULZ9o/HLzMJfI1jBYpZ3BWU5sr9VWsZupGM29lHA5eEbzD4Myk Ruk+M5Oa1EZ/arxm64uubD8/iw+Ejol5Wlcbdexk8raj7DorwpnoCrYi1bPHCWS2Zhjo ykE/vRrKjSo0fJaEmuqLubKEMUot4dyLjPDow=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; b=WHAjK5HRagQtIic+OVxP/kkE4tohIUF1+rQCJEF/4KGct2tnDkWSYRL8rnfXrbe4oy G7kmYGuE7jn0sQ1gQpc2VtoUNyWSkyxjZBfGFs2FI8GLtdm3gQ8U30ndaWWpUmpJ9Qci kvNTM6Kjic2l6R2B7fwULwz0Lg+qArs5W29us=
Received: by 10.142.245.1 with SMTP id s1mr898632wfh.135.1299163840148; Thu, 03 Mar 2011 06:50:40 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id w32sm1534773wfh.19.2011.03.03.06.50.35 (version=SSLv3 cipher=OTHER); Thu, 03 Mar 2011 06:50:38 -0800 (PST)
Message-ID: <FFBA5A9A337141739D05B7F35096787F@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <trejrco@gmail.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4D6EAF57.8050606@gmail.com><201103022125.p22LPljL020592@cichlid.raleigh.ibm.com><4D6EC041.4070304@gmail.com><AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com><4D6EC58A.6050404@gmail.com> <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>
In-Reply-To: <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Date: Thu, 3 Mar 2011 22:50:26 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CB_01CBD9F5.636CF110"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 14:49:33 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_00CB_01CBD9F5.636CF110
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

I think that SLAAC should be deployed in the sites which use the =
prefixes longer than 64.=20
Don't put a limit on the prefix length.
DHCPv6 can be deployed in the sites which use the prefixes longer than =
64.Why can't SLAAC?
It is not reasonable.


From: TJ=20
Sent: Thursday, March 03, 2011 6:58 AM
To: Brian E Carpenter=20
Cc: Scott W Brim ; Thomas Narten ; ipv6 ; huabing yu=20
Subject: Re: draft-yhb-6man-slaac-improvement-00


On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:


<snip>


  I'd rather get IPv6 deployed in a uniform way first.



I'd take that sentence a step or two further:
  "I'd rather get IPv6 deployed in a uniform way."=20
or even simpler:=20
  "I'd rather get IPv6 deployed."




To be (perhaps overly) blunt: IMHO the changes proposed in this draft =
create unneeded confusion, solve a problem that is either non-existent =
or is readily solved in other ways and can create functional problems / =
detriments to actual deployment.  =20


Note: I am ready, willing and (often!) able to be proven wrong ... (and =
welcome the conversation!)=20






/TJ
------=_NextPart_000_00CB_01CBD9F5.636CF110
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV>I&nbsp;think that SLAAC&nbsp;should be deployed in the sites which =
use the=20
prefixes longer than 64. </DIV>
<DIV>Don't put a limit on the prefix length.</DIV>
<DIV>DHCPv6 can be deployed in the sites which use the prefixes longer =
than=20
64.Why can't SLAAC?</DIV>
<DIV>It is not reasonable.</DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dtrejrco@gmail.com=20
href=3D"mailto:trejrco@gmail.com">TJ</A> </DIV>
<DIV><B>Sent:</B> Thursday, March 03, 2011 6:58 AM</DIV>
<DIV><B>To:</B> <A title=3Dbrian.e.carpenter@gmail.com=20
href=3D"mailto:brian.e.carpenter@gmail.com">Brian E Carpenter</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dscott.brim@gmail.com=20
href=3D"mailto:scott.brim@gmail.com">Scott W Brim</A> ; <A =
title=3Dnarten@us.ibm.com=20
href=3D"mailto:narten@us.ibm.com">Thomas Narten</A> ; <A =
title=3Dipv6@ietf.org=20
href=3D"mailto:ipv6@ietf.org">ipv6</A> ; <A title=3Dyhb810501@gmail.com=20
href=3D"mailto:yhb810501@gmail.com">huabing yu</A> </DIV>
<DIV><B>Subject:</B> Re: =
draft-yhb-6man-slaac-improvement-00</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV>
<DIV class=3Dgmail_quote>On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter =
<SPAN=20
dir=3Dltr>&lt;<A title=3D"mailto:brian.e.carpenter@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</=
A>&gt;</SPAN>=20
wrote:</DIV>
<DIV class=3Dgmail_quote><BR></DIV>
<DIV class=3Dgmail_quote>&lt;snip&gt;</DIV>
<DIV class=3Dgmail_quote><BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; =
PADDING-LEFT: 1ex"=20
class=3Dgmail_quote>I'd rather get IPv6 deployed in a uniform way=20
first.<BR></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>I'd take that sentence a step or two further:</DIV></DIV></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; =
PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; =
PADDING-TOP: 0px"=20
class=3Dwebkit-indent-blockquote>
  <DIV>
  <DIV class=3Dgmail_quote>
  <DIV>"<SPAN=20
  style=3D"BORDER-COLLAPSE: collapse; FONT-FAMILY: 'Droid Sans', arial, =
sans-serif; COLOR: rgb(32,32,32); FONT-SIZE: 13px"=20
  class=3DApple-style-span>I'd rather get IPv6 deployed in a uniform=20
  way.</SPAN>"&nbsp;</DIV></DIV></DIV></BLOCKQUOTE>or even simpler:=20
<BLOCKQUOTE=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; =
PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 40px; PADDING-LEFT: 0px; =
PADDING-RIGHT: 0px; BORDER-TOP: medium none; BORDER-RIGHT: medium none; =
PADDING-TOP: 0px"=20
class=3Dwebkit-indent-blockquote>
  <DIV>"<SPAN=20
  style=3D"BORDER-COLLAPSE: collapse; FONT-FAMILY: 'Droid Sans', arial, =
sans-serif; COLOR: rgb(32,32,32); FONT-SIZE: 13px"=20
  class=3DApple-style-span>I'd rather get IPv6 deployed.</SPAN>"</DIV>
  <DIV><BR></DIV></BLOCKQUOTE>
<DIV><BR></DIV>To be (perhaps overly) blunt: IMHO the changes proposed =
in this=20
draft create unneeded confusion, solve a problem that is either =
non-existent or=20
is readily solved in other ways and can create functional problems / =
detriments=20
to actual deployment. &nbsp;=20
<DIV><BR></DIV>
<DIV>Note:&nbsp;I am ready, willing and (often!) able to be proven wrong =
...=20
(and welcome the conversation!)=20
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>/TJ</DIV></DIV></BODY></HTML>

------=_NextPart_000_00CB_01CBD9F5.636CF110--


From btv1==04354ea924a==Richard.Duncan_contractor@dtra.mil  Thu Mar  3 06:53:00 2011
Return-Path: <btv1==04354ea924a==Richard.Duncan_contractor@dtra.mil>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 333773A67E7 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 06:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.594
X-Spam-Level: **
X-Spam-Status: No, score=2.594 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FR_TEST_BASE64_BAD=3.189, HTML_MESSAGE=0.001, TRACKER_ID=2.003]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qp6SmeBoAyQ6 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 06:52:55 -0800 (PST)
Received: from U348.dtra.mil (u348.dtra.mil [214.3.36.172]) by core3.amsl.com (Postfix) with ESMTP id 5570E3A68AD for <ipv6@ietf.org>; Thu,  3 Mar 2011 06:52:53 -0800 (PST)
X-ASG-Debug-ID: 1299164038-697d00a30001-WbpaHM
Received: from OWA101.unet1.ad.dtra.mil (ufncr1.dtra.mil [214.3.40.3]) by U348.dtra.mil with SMTP id HXe3BGjVS3nKn7QV; Thu, 03 Mar 2011 09:53:58 -0500 (EST)
X-Barracuda-Envelope-From: Richard.Duncan_contractor@DTRA.MIL
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-Barracuda-RBL-Trusted-Forwarder: 214.3.40.3
X-ASG-Whitelist: Client
Received: from NNDD01S1.unet1.ad.dtra.mil ([10.8.5.13]) by OWA101.unet1.ad.dtra.mil with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Mar 2011 09:56:22 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-ASG-Orig-Subj: RE: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Subject: RE: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Date: Thu, 3 Mar 2011 09:56:22 -0500
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_004B_01CBD989.3DEC3BB0"
Message-ID: <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>
In-Reply-To: <FFBA5A9A337141739D05B7F35096787F@yhbPC>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Thread-Index: AcvZssFJECsTsYi0RjW0QxndUzQwIwAAB0Zg
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4D6EAF57.8050606@gmail.com><201103022125.p22LPljL020592@cichlid.raleigh.ibm.com><4D6EC041.4070304@gmail.com><AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com><4D6EC58A.6050404@gmail.com><AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@yhbPC>
From: "Duncan, Richard J. (Jeremy)  CONTRACTOR" <Richard.Duncan_contractor@DTRA.MIL>
To: "Yu Hua bing" <yhb810501@gmail.com>, <trejrco@gmail.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 03 Mar 2011 14:56:22.0765 (UTC) FILETIME=[296E29D0:01CBD9B3]
X-Barracuda-Connect: ufncr1.dtra.mil[214.3.40.3]
X-Barracuda-Start-Time: 1299164038
X-Barracuda-URL: http://214.3.36.172:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at dtra.mil
X-Mailman-Approved-At: Thu, 03 Mar 2011 06:58:10 -0800
Cc: Thomas Narten <narten@us.ibm.com>, Scott W Brim <scott.brim@gmail.com>, ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 14:53:41 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_004B_01CBD989.3DEC3BB0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_004C_01CBD989.3DEC3BB0"


------=_NextPart_001_004C_01CBD989.3DEC3BB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I think that SLAAC should be deployed in the sites which use the prefixes
longer than 64. 

Don't put a limit on the prefix length.

DHCPv6 can be deployed in the sites which use the prefixes longer than
64.Why can't SLAAC?

It is not reasonable.

 

No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How would
you plan to squeeze blood out of the proverbial turnip?

 

 

010100110110010101101101011100000110010101110010001000000100011001101001

Jeremy Duncan

Defense Threat Reduction Agency (DTRA)
BE-BI INFOCON 3, IPv6 Architect
Command Information
Google Voice:  (540) 440-1193

  _____  

From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Yu
Hua bing
Sent: Thursday, March 03, 2011 9:50 AM
To: trejrco@gmail.com; Brian E Carpenter
Cc: Thomas Narten; ipv6; Scott W Brim
Subject: [BULK] Re: draft-yhb-6man-slaac-improvement-00
Importance: Low

 

I think that SLAAC should be deployed in the sites which use the prefixes
longer than 64. 

Don't put a limit on the prefix length.

DHCPv6 can be deployed in the sites which use the prefixes longer than
64.Why can't SLAAC?

It is not reasonable.

 

From: TJ <mailto:trejrco@gmail.com>  

Sent: Thursday, March 03, 2011 6:58 AM

To: Brian <mailto:brian.e.carpenter@gmail.com>  E Carpenter 

Cc: Scott W Brim <mailto:scott.brim@gmail.com>  ; Thomas Narten
<mailto:narten@us.ibm.com>  ; ipv6 <mailto:ipv6@ietf.org>  ; huabing yu
<mailto:yhb810501@gmail.com>  

Subject: Re: draft-yhb-6man-slaac-improvement-00

 

On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

 

<snip>

 

I'd rather get IPv6 deployed in a uniform way first.

 

I'd take that sentence a step or two further:

"I'd rather get IPv6 deployed in a uniform way." 

or even simpler: 

"I'd rather get IPv6 deployed."

 

 

To be (perhaps overly) blunt: IMHO the changes proposed in this draft create
unneeded confusion, solve a problem that is either non-existent or is
readily solved in other ways and can create functional problems / detriments
to actual deployment.   

 

Note: I am ready, willing and (often!) able to be proven wrong ... (and
welcome the conversation!) 

 

 

 

/TJ


------=_NextPart_001_004C_01CBD989.3DEC3BB0
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
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=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue id=3DMailContainerBody =
leftmargin=3D0
topmargin=3D0 CanvasTabStop=3Dtrue name=3D"Compose message area">

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I&nbsp;think that SLAAC&nbsp;should be deployed in the sites =
which use
the prefixes longer than 64. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Don't put a limit on the prefix =
length.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>DHCPv6 can be deployed in the sites which use the prefixes =
longer than
64.Why can't SLAAC?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>It is not reasonable.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>No&#8230; EUI-64 requires 64 bit =
host id&#8217;s.
&nbsp;48 bits is from the MAC. &nbsp;How would you plan to squeeze blood =
out of the proverbial
turnip?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:10.0pt;color:navy'>01010011011001010110110101110000011=
0010101110010001000000100011001101001<br>
<br>
Jeremy Duncan<br>
<br>
Defense Threat Reduction Agency (DTRA)<br>
BE-BI INFOCON 3, IPv6 Architect<br>
Command Information<br>
Google Voice:&nbsp; (540) 440-1193</span></font><o:p></o:p></p>

</div>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Yu Hua bing<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, March 03, =
2011
9:50 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> trejrco@gmail.com; =
Brian E
Carpenter<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> Thomas Narten; ipv6; =
Scott W
Brim<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [BULK] Re:
draft-yhb-6man-slaac-improvement-00<br>
<b><span style=3D'font-weight:bold'>Importance:</span></b> =
Low</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I&nbsp;think that SLAAC&nbsp;should be deployed in the sites =
which use
the prefixes longer than 64. <o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Don't put a limit on the prefix =
length.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>DHCPv6 can be deployed in the sites which use the prefixes =
longer than
64.Why can't SLAAC?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>It is not reasonable.<o:p></o:p></span></font></p>

</div>

<div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<div style=3D'font-color:black'>

<p class=3DMsoNormal style=3D'background:whitesmoke'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> <a
href=3D"mailto:trejrco@gmail.com" title=3D"trejrco@gmail.com">TJ</a> =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'background:whitesmoke'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>Sent:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Thursday,
March 03, 2011 6:58 AM<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'background:whitesmoke'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>To:</span>=
</font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> <a
href=3D"mailto:brian.e.carpenter@gmail.com" =
title=3D"brian.e.carpenter@gmail.com">Brian
E Carpenter</a> <o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'background:whitesmoke'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>Cc:</span>=
</font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> <a
href=3D"mailto:scott.brim@gmail.com" =
title=3D"scott.brim@gmail.com">Scott W Brim</a>
; <a href=3D"mailto:narten@us.ibm.com" =
title=3D"narten@us.ibm.com">Thomas Narten</a>
; <a href=3D"mailto:ipv6@ietf.org" title=3D"ipv6@ietf.org">ipv6</a> ; <a
href=3D"mailto:yhb810501@gmail.com" =
title=3D"yhb810501@gmail.com">huabing yu</a> =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal style=3D'background:whitesmoke'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>Subject:</=
span></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Re:
draft-yhb-6man-slaac-improvement-00<o:p></o:p></span></font></p>

</div>

</div>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter &lt;<a
href=3D"mailto:brian.e.carpenter@gmail.com"
title=3D"mailto:brian.e.carpenter@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;">brian.e.carpenter@gmail=
.com</a>&gt;
wrote:<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&lt;snip&gt;<o:p></o:p></span></font></p>

</div>

<div>

<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I'd rather get IPv6 deployed in a uniform way =
first.<o:p></o:p></span></font></p>

</blockquote>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>I'd take that sentence a step or two =
further:<o:p></o:p></span></font></p>

</div>

</div>

</div>

<blockquote style=3D'margin-left:30.0pt;margin-right:0in'>

<div>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&quot;</span></font><span class=3Dapple-style-span><font =
size=3D2
color=3D"#202020" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:#202020'>I'd rather get IPv6 deployed in a uniform =
way.</span></font></span>&quot;&nbsp;<o:p></o:p></p>

</div>

</div>

</div>

</blockquote>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>or even simpler: <o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&quot;</span></font><span class=3Dapple-style-span><font =
size=3D2
color=3D"#202020" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:#202020'>I'd rather get IPv6 =
deployed.</span></font></span>&quot;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>To be (perhaps overly) blunt: IMHO the changes proposed in this =
draft
create unneeded confusion, solve a problem that is either non-existent =
or is
readily solved in other ways and can create functional problems / =
detriments to
actual deployment. &nbsp; <o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Note:&nbsp;I am ready, willing and (often!) able to be proven =
wrong ...
(and welcome the conversation!) <o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>/TJ<o:p></o:p></span></font></p>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_001_004C_01CBD989.3DEC3BB0--

------=_NextPart_000_004B_01CBD989.3DEC3BB0
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIS5DCCA3Aw
ggJYoAMCAQICAQUwDQYJKoZIhvcNAQEFBQAwWzELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxFjAUBgNVBAMTDURvRCBSb290
IENBIDIwHhcNMDQxMjEzMTUwMDEwWhcNMjkxMjA1MTUwMDEwWjBbMQswCQYDVQQGEwJVUzEYMBYG
A1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEWMBQGA1UE
AxMNRG9EIFJvb3QgQ0EgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMAswfaNO6z/
PzzWcb64dCIH7HBBFfyrQOMHqsHD2J/+2kw6vz/I2Ch7SzYBwKxFJcPSDgqPhRhkED0aE3Aqb47X
3I2Ts0EPOCHNravCPSoF01cRNw3NjFH5k+PMRkkhjhS0zcsUPjjNcjHuqxLyZeo0LlZd/+5jdctt
upE0/J7z9C0cvlDEQt9ZiP9qs/qobD3LVnFxBZa7n4DlgEVZZ0Gw68OtYKSAdQYXnA70Q+CZDhv7
f/WzzLKBgrH9MsG4vkGkZLVgOlpRMIzO3kEsGUdcSRBkuXSph0GvfW66wbihv2UxOgRn+bW7jpKK
AGO4seaMOF+D/1DVO6Jda7IQzGMCAwEAAaM/MD0wHQYDVR0OBBYEFEl0uwxeunr+AlTve6DGlcYJ
gHCWMAsGA1UdDwQEAwIBhjAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBBQUAA4IBAQCYkY0/
ici79cBpcyk7Nay6swh2PXAJkumERCEBfRR2G+5RbB2NFTctezFp9JpEuK9GzDT6I8sDJxnSgyF1
K+fgG5km3IRAleio0sz2WFxm7z9KlxCCHboKot1bBiudp2RO6y4BNaS0PxOtVeTVc6hpmxHxmPIx
Hm9A1Ph4n46RoG9wBJBmqgYrzuF6krV94eDRluehOi3MsZ0fBUTth5nTTRpwOcEEDOV+2fGv1yAO
8SJ6JaRzmcw/pAcnlqiile2CuRbTnguHwsHyiPVi32jfx7xpUe2xXNxUVCkPCTmarAPB2wxNrm8K
ehZJ8b+R0jiU0/aVLLdsyUK2jcqQjYXZMIIExTCCA62gAwIBAgIDB0hEMA0GCSqGSIb3DQEBBQUA
MF0xCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0RvRDEM
MAoGA1UECxMDUEtJMRgwFgYDVQQDEw9ET0QgRU1BSUwgQ0EtMjYwHhcNMTAwOTE1MDAwMDAwWhcN
MTIwOTE2MjM1OTU5WjB+MQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQww
CgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTETMBEGA1UECxMKQ09OVFJBQ1RPUjEkMCIGA1UEAxMb
RFVOQ0FOLlJJQ0hBUkQuSi4xMDQxODMyNDQwMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
AQEAhP6yC8vEQsiL5O5awiAmhpbX6E8hNtrtnuOPRFqBiLnImOrtqrMuVvjFl/UY+2oMPtFTsG0s
ydHb0rOAyfVBik8iPq6RDkGfOeziBQA4J84QzYE7g9eAZEOANGRfdMj4k78i/bDzxEx3oDwe1dYA
MaYR5D2o1Kfzb6tAuKcuzEdiB11ojoTcUk2Fo1NrQe65t4Oikl+dgul6BjSDW8wucbhx79DblKFJ
AivkMv7D0rZr9UdsZlwPeFh9lGzyRuCnq181aif0Zvto6gdmQUliM3Zt4UOQ8KMVoYDqLxAJncoJ
JOgy2dFq3TmA4ykQ42aXyn1IfzZutH2z6KKgzWnmoQIDAQABo4IBazCCAWcwHwYDVR0jBBgwFoAU
Mt/IbfP/Pin96QyXKVDwohAsbi8wOgYDVR0fBDMwMTAvoC2gK4YpaHR0cDovL2NybC5kaXNhLm1p
bC9jcmwvRE9ERU1BSUxDQV8yNi5jcmwwDgYDVR0PAQH/BAQDAgUgMCMGA1UdIAQcMBowCwYJYIZI
AWUCAQsJMAsGCWCGSAFlAgELEzAdBgNVHQ4EFgQUt1CzRFWsJs3mW5qQfsSCye5i7A0waAYIKwYB
BQUHAQEEXDBaMDYGCCsGAQUFBzAChipodHRwOi8vY3JsLmRpc2EubWlsL3NpZ24vRE9ERU1BSUxD
QV8yNi5jZXIwIAYIKwYBBQUHMAGGFGh0dHA6Ly9vY3NwLmRpc2EubWlsMC0GA1UdEQQmMCSBIlJp
Y2hhcmQuRHVuY2FuX0NPTlRSQUNUT1JAZHRyYS5taWwwGwYDVR0JBBQwEjAQBggrBgEFBQcJBDEE
EwJVUzANBgkqhkiG9w0BAQUFAAOCAQEAHpTKLV38BsHKzfT1GDlFm9GeiQsgIR4Jf5zdTACdhYpZ
+h2jv/i55BRfAmULeP2t45ISx2BMrV88Q0k6YjPNCjuFGIjPpJ6Y4LsPIX7IBB4V5u3aLU9YMWMt
ZDD1/8kgaAFxz1ct+kOMy5C7lBHklfkhit+F4LolvNS4Xfaot365fF+2zap1JB8QYcq7DrZygmfq
k1LCVvTWRCDma/Ol4nukCRSn8ynjQs9qdDfPkp25DBNnv1sdcHA9bmi8qJdnBxnMjcCUHMUl+M9d
WQomAdPgB7wgnx7nmHtaHCDzGUGrgp8ERSJBL08ghserEIedmJO/sG+xD5H4IR1fzhnjizCCBRAw
ggP4oAMCAQICAwdIQDANBgkqhkiG9w0BAQUFADBdMQswCQYDVQQGEwJVUzEYMBYGA1UEChMPVS5T
LiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsTA1BLSTEYMBYGA1UEAxMPRE9EIEVN
QUlMIENBLTI2MB4XDTEwMDkxNTAwMDAwMFoXDTEyMDkxNjIzNTk1OVowfjELMAkGA1UEBhMCVVMx
GDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxEzAR
BgNVBAsTCkNPTlRSQUNUT1IxJDAiBgNVBAMTG0RVTkNBTi5SSUNIQVJELkouMTA0MTgzMjQ0MDCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOaTYMLhSI8XLZSVYhyzs3540PZpKNej/Y8T
MvtUq1uM3DQGFuK+g3rE9l7phXjFarQauefLyHtMgkFSU1WALhU2BEbcgy4xToLioN1zwHsaqyce
yYejcJQ2t5875Au/yUK+A2JRKeXBchbuKKx8LXa5To8imXHjK66qLoBn1Wfykauz78067qboHONE
2gB6DN4FMawuhkMs6R8ZLAMIqthnYpfxSyi8IeB1iNRhQq28VYxY37KpMBgpg4Gn9uapRy2pAN6Q
8L660BWVBCAz6q36Thos47mpwVRr/wK6vfR496kIz28c3XrCcGwhXSI/YnDLzZi46Q4pPwyAsVwB
cLMCAwEAAaOCAbYwggGyMB8GA1UdIwQYMBaAFDLfyG3z/z4p/ekMlylQ8KIQLG4vMDoGA1UdHwQz
MDEwL6AtoCuGKWh0dHA6Ly9jcmwuZGlzYS5taWwvY3JsL0RPREVNQUlMQ0FfMjYuY3JsMA4GA1Ud
DwEB/wQEAwIGwDAjBgNVHSAEHDAaMAsGCWCGSAFlAgELCTALBglghkgBZQIBCxMwHQYDVR0OBBYE
FNNzL60bX1s3xsMvvqdkISmao4/OMGgGCCsGAQUFBwEBBFwwWjA2BggrBgEFBQcwAoYqaHR0cDov
L2NybC5kaXNhLm1pbC9zaWduL0RPREVNQUlMQ0FfMjYuY2VyMCAGCCsGAQUFBzABhhRodHRwOi8v
b2NzcC5kaXNhLm1pbDBNBgNVHREERjBEgSJSaWNoYXJkLkR1bmNhbl9DT05UUkFDVE9SQGR0cmEu
bWlsoB4GCisGAQQBgjcUAgOgEAwOMTA0MTgzMjQ0MEBtaWwwGwYDVR0JBBQwEjAQBggrBgEFBQcJ
BDEEEwJVUzApBgNVHSUEIjAgBgorBgEEAYI3FAICBggrBgEFBQcDAgYIKwYBBQUHAwQwDQYJKoZI
hvcNAQEFBQADggEBAAu2kntsKAJVciJ2ot9IDDIgN5InqwL5Gn+j355KgpXHZVlR0aBjuY3hQZXr
jPoZvuwZqBGKeGMwaPEun3xUXeSxeWDc9vvSjfD8+BnOCxwWmg/s1zs1SaeHrL/xtoDw28GoZGEa
O+Kt+il5FEjeepAE88aTvZrcLClY/sjL1dR87PonHR/l/Fy0DLufjQKBQ7qWW5q+870sDHJOL9bq
2TMkXre2G16tIQzsVQgbriZjfAGV3/2JsEbHHo6SFi60X/zD56ODfym/Uf9volaQhltjtAj0F8DB
27Qx+Hvt02rkV8CEiyhUJJ+16sbp+BuGWodR1fucTkfi39Mb//MOcPcwggWPMIIEd6ADAgECAgFR
MA0GCSqGSIb3DQEBBQUAMFsxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQx
DDAKBgNVBAsTA0RvRDEMMAoGA1UECxMDUEtJMRYwFAYDVQQDEw1Eb0QgUm9vdCBDQSAyMB4XDTEw
MDExNDE3MzkyN1oXDTE2MDExNDE3MzkyN1owXTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kxGDAWBgNVBAMTD0RPRCBFTUFJ
TCBDQS0yNjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKxfEFs9Kgf97s9OxrBOPVqg
AGBQecICRWZPODSBXBy/J2BqecymlwvWiebY25V8VzoH7kblZCoTF48dMPwt+jZ/N2Ek5RSi/SJX
HGGuTS4DUGZVRt1qJ/ipeatcKuUlXVwb+3EPtbgVj1+UewPP7quSCArkvaOhXYPXPcef1EQQOqJf
X+SGlG8DoDXzg9jhuBmferp1zwAF0NsjpGol12lwRcZdeIsHX0WsndajS10Yz49MChGh2RHb+Zyl
1Y+c6g9HvSWClPlgkkoU+LqbqWzfyhURoYs5vvoZTby7FG/dYH2ynJAHfIBHuYWMuD6jdbmuXneR
c8F1iVW6TYbkrbsCAwEAAaOCAlowggJWMA4GA1UdDwEB/wQEAwIBhjAfBgNVHSMEGDAWgBRJdLsM
Xrp6/gJU73ugxpXGCYBwljAdBgNVHQ4EFgQUMt/IbfP/Pin96QyXKVDwohAsbi8wDAYDVR0kBAUw
A4ABADASBgNVHRMBAf8ECDAGAQH/AgEAMIGfBgNVHSAEgZcwgZQwCwYJYIZIAWUCAQsFMAsGCWCG
SAFlAgELCTALBglghkgBZQIBCwowCwYJYIZIAWUCAQsSMAsGCWCGSAFlAgELEzALBglghkgBZQIB
CxQwDAYKYIZIAWUDAgEDBjAMBgpghkgBZQMCAQMHMAwGCmCGSAFlAwIBAwgwDAYKYIZIAWUDAgED
DTAMBgpghkgBZQMCAQMRMD8GA1UdHwQ4MDYwNKAyoDCGLmh0dHA6Ly9jcmwuZGlzYS5taWwvZ2V0
Y3JsP0RvRCUyMFJvb3QlMjBDQSUyMDIwgf4GCCsGAQUFBwEBBIHxMIHuMD8GCCsGAQUFBzAChjNo
dHRwOi8vY3JsLmRpc2EubWlsL2dldElzc3VlZFRvP0RvRCUyMFJvb3QlMjBDQSUyMDIwIAYIKwYB
BQUHMAGGFGh0dHA6Ly9vY3NwLmRpc2EubWlsMIGIBggrBgEFBQcwAoZ8bGRhcDovL2NybC5nZHMu
ZGlzYS5taWwvY24lM2REb0QlMjBSb290JTIwQ0ElMjAyJTJjb3UlM2RQS0klMmNvdSUzZERvRCUy
Y28lM2RVLlMuJTIwR292ZXJubWVudCUyY2MlM2RVUz9jQUNlcnRpZmljYXRlO2JpbmFyeTANBgkq
hkiG9w0BAQUFAAOCAQEAasBQKYT43GcTsZbuulzU5ZL5zWRlM4UoC6Aaq1MdjEAXkbpm2mtrvKyO
YQHDZzURWVKFcF2hhud6wRzD2F7Ld7vMXNwa3QRf+ojts261tETLOjWdoE4cwEW19tTNBnnSGjns
JSZxnNm4b5Ns1js0O2eZql+luG1MxwnqycB0mdlZiymJkCuBldmH/VX4WHVSpn8iaG2F1n2uig0v
NL/XKGzGW628/xs6xmSFpJx9hJWfqANl5H9NzAx1ekoFRFiAizk0TzM/K0Tx1nTv73ya2NwLGD3y
5Z1QOyMp5fTPYOpgTxxgwRqynFoCBLB8wckVatsqrwsIuz5xeqY85R1EIjGCA0EwggM9AgEBMGQw
XTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQww
CgYDVQQLEwNQS0kxGDAWBgNVBAMTD0RPRCBFTUFJTCBDQS0yNgIDB0hAMAkGBSsOAwIaBQCgggGy
MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDMwMzE0NTYxOFow
IwYJKoZIhvcNAQkEMRYEFIwhYGE+gX/pLGDP4sUZ3o/iQXE8MGcGCSqGSIb3DQEJDzFaMFgwCgYI
KoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3
DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3DQIFMHMGCSsGAQQBgjcQBDFmMGQwXTELMAkGA1UEBhMC
VVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRG9EMQwwCgYDVQQLEwNQS0kx
GDAWBgNVBAMTD0RPRCBFTUFJTCBDQS0yNgIDB0hEMHUGCyqGSIb3DQEJEAILMWagZDBdMQswCQYD
VQQGEwJVUzEYMBYGA1UEChMPVS5TLiBHb3Zlcm5tZW50MQwwCgYDVQQLEwNEb0QxDDAKBgNVBAsT
A1BLSTEYMBYGA1UEAxMPRE9EIEVNQUlMIENBLTI2AgMHSEQwDQYJKoZIhvcNAQEBBQAEggEAzAx+
X/qedUNkQqxfFBYN9Fz4PHsLTZzyuld/qd1AjZetdj5+zvye7Hstf92iOAJUfMu4xjb43yzagHai
uOMb5d2H5dH0JHmf9UOFSzERKD5WQ4FqAZXervMuww5cXzS8fDbexCq3pDuGAI/MTaz4WH8RhMPx
bvRTUOiTFlM4O+eLGol4RQWwOqGp5tDBkJ7zSX+m5z9Epe0Yk1AorVzcFLbi4flOMj3ulhE1FPc+
IahKS6iUnOiu4tIsAA07lijnWN46tPZ+uQgKziv1ebVTqXuKVIK9Gqa8ZoXqe4WC/791Jior1f9I
aF/bB/0/CUsN/vJA1G8o1ztaFYQIIdjjbwAAAAAAAA==

------=_NextPart_000_004B_01CBD989.3DEC3BB0--

From yhb810501@gmail.com  Thu Mar  3 07:01:31 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DDB33A67B1 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 07:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.659
X-Spam-Level: 
X-Spam-Status: No, score=-0.659 tagged_above=-999 required=5 tests=[AWL=-2.253, BAYES_00=-2.599, FR_TEST_BASE64_BAD=3.189, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vDO79WAZ0Fm for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 07:01:27 -0800 (PST)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 998FF3A69ED for <ipv6@ietf.org>; Thu,  3 Mar 2011 07:01:27 -0800 (PST)
Received: by pxi6 with SMTP id 6so239025pxi.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 07:02:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:x-priority:x-msmail-priority :importance:x-mailer:x-mimeole; bh=LC1r23X9GIXOdMKDPsfM88xN1axJZLKeI4CQLAQHItY=; b=l2WEhhcArDjZM8nonR/IoM/nXI6YcsbCo9B9jBWyJseAuyw2wZigy7QpY9aqEbnvSm mA4vlq73QsSwnIQ8ouLYZKt1qmv4L9Nk4Ra3GzXFxsQw2PFMz4gCbgaHTfi2tt8sZEvo v3AghZ2fmdJ5ugqvMLhfhyFGvm+xRq1q9pdGA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; b=FSgfTlPA7DMcukrwRnAlv/HzxBHx18W8hrKxiDuOHZOw+WFyxm4L38DUuyZNwkx0ls XompzOT1RTK/BWX4yA67WuByHwy95KigMGIg7JucYep+nLTAJZ51AAVCXZghi+T0T2Od IGD+WrzptK2p7Fx5XSWriQqJAR7o5uQrNEbUs=
Received: by 10.142.239.11 with SMTP id m11mr907579wfh.120.1299164555278; Thu, 03 Mar 2011 07:02:35 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id z8sm1562811wfj.1.2011.03.03.07.02.30 (version=SSLv3 cipher=OTHER); Thu, 03 Mar 2011 07:02:34 -0800 (PST)
Message-ID: <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: "Duncan, Richard J. \(Jeremy\)  CONTRACTOR" <Richard.Duncan_contractor@DTRA.MIL>, <trejrco@gmail.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4D6EAF57.8050606@gmail.com><201103022125.p22LPljL020592@cichlid.raleigh.ibm.com><4D6EC041.4070304@gmail.com><AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com><4D6EC58A.6050404@gmail.com><AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@yhbPC> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>
In-Reply-To: <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>
Subject: Re: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Date: Thu, 3 Mar 2011 23:02:22 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F6_01CBD9F7.0E351360"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: Thomas Narten <narten@us.ibm.com>, Scott W Brim <scott.brim@gmail.com>, ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 15:01:31 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_00F6_01CBD9F7.0E351360
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

      If the prefix is longer than 64, don't use EUI-64 interface ID.

   (7.2)If the prefix length is greater than 64 and is not greater than
   80, an address is formed by combining the advertised prefix with=20
   the MAC address of the interface as follows:

      |            N bits            | (80 - N) bits |     48 bits     |
      +------------------------------+---------------+-----------------+
      |            link prefix       |   reserved    |   MAC address   |
      +----------------------------------------------------------------+
   (7.3) If the prefix length is greater than 80, a random number=20
   between 0 and 2 ^ (128 - prefix length) is generated, and an address
   is formed by combining the advertised prefix with the random number
   as follows:
           =20
      |                N bits                 |       128 - N bits     |
      +---------------------------------------+------------------------+
      |            link prefix                |     random number      |
      +----------------------------------------------------------------+ =
                  =20



From: Duncan, Richard J. (Jeremy) CONTRACTOR=20
Sent: Thursday, March 03, 2011 10:56 PM
To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter=20
Cc: Thomas Narten ; ipv6 ; Scott W Brim=20
Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00


I think that SLAAC should be deployed in the sites which use the =
prefixes longer than 64.=20

Don't put a limit on the prefix length.

DHCPv6 can be deployed in the sites which use the prefixes longer than =
64.Why can't SLAAC?

It is not reasonable.

=20

No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How =
would you plan to squeeze blood out of the proverbial turnip?

=20

=20

010100110110010101101101011100000110010101110010001000000100011001101001

Jeremy Duncan

Defense Threat Reduction Agency (DTRA)
BE-BI INFOCON 3, IPv6 Architect
Command Information
Google Voice:  (540) 440-1193


-------------------------------------------------------------------------=
-------

------=_NextPart_000_00F6_01CBD9F7.0E351360
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:v =3D "urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722">
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>

<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 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:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody lang=3DEN-US leftMargin=3D0 link=3Dblue =
topMargin=3D0 vLink=3Dblue=20
CanvasTabStop=3D"true" name=3D"Compose message area">
<DIV><FONT face=3DCalibri>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If the prefix =
is longer=20
than 64, don't use EUI-64 interface ID.</FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; (7.2)If the prefix length is greater than 64 and is =
not=20
greater than<BR>&nbsp;&nbsp; 80, an address is formed by combining the=20
advertised prefix with <BR>&nbsp;&nbsp; the MAC address of the interface =
as=20
follows:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N=20
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =
(80 -=20
N) bits |&nbsp;&nbsp;&nbsp;&nbsp; 48 bits&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+------------------------------+---------------+-----------------+<BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link =

prefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;=20
reserved&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; MAC address&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+----------------------------------------------------------------+<BR>&nb=
sp;&nbsp;=20
(7.3) If the prefix length is greater than 80, a random number =
<BR>&nbsp;&nbsp;=20
between 0 and 2 ^ (128 - prefix length) is generated, and an=20
address<BR>&nbsp;&nbsp; is formed by combining the advertised prefix =
with the=20
random number<BR>&nbsp;&nbsp; as=20
follows:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=20
N=20
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 128 - N =
bits&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+---------------------------------------+------------------------+<BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; link =

prefix&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp; random number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
+----------------------------------------------------------------+&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR></DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A=20
title=3D"mailto:Richard.Duncan_contractor@DTRA.MIL&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:Richard.Duncan_contractor@DTRA.MIL">Duncan, Richard J. =
(Jeremy)=20
CONTRACTOR</A> </DIV>
<DIV><B>Sent:</B> Thursday, March 03, 2011 10:56 PM</DIV>
<DIV><B>To:</B> <A title=3Dyhb810501@gmail.com=20
href=3D"mailto:yhb810501@gmail.com">Yu Hua bing</A> ; <A=20
title=3D"mailto:trejrco@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:trejrco@gmail.com">trejrco@gmail.com</A> ; <A=20
title=3D"mailto:brian.e.carpenter@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:brian.e.carpenter@gmail.com">Brian E Carpenter</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dnarten@us.ibm.com=20
href=3D"mailto:narten@us.ibm.com">Thomas Narten</A> ; <A=20
title=3D"mailto:ipv6@ietf.org&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:ipv6@ietf.org">ipv6</A> ; <A=20
title=3D"mailto:scott.brim@gmail.com&#10;CTRL + =
&#21333;&#20987;&#20197;&#19979;&#38142;&#25509;"=20
href=3D"mailto:scott.brim@gmail.com">Scott W Brim</A> </DIV>
<DIV><B>Subject:</B> RE: [BULK] Re:=20
draft-yhb-6man-slaac-improvement-00</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT size=3D3 face=3D"Times New Roman"><SPAN=20
style=3D"FONT-SIZE: 12pt">I&nbsp;think that SLAAC&nbsp;should be =
deployed in the=20
sites which use the prefixes longer than 64. =
<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT size=3D3 face=3D"Times New Roman"><SPAN=20
style=3D"FONT-SIZE: 12pt">Don't put a limit on the prefix=20
length.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT size=3D3 face=3D"Times New Roman"><SPAN=20
style=3D"FONT-SIZE: 12pt">DHCPv6 can be deployed in the sites which use =
the=20
prefixes longer than 64.Why can't SLAAC?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT size=3D3 face=3D"Times New Roman"><SPAN=20
style=3D"FONT-SIZE: 12pt">It is not =
reasonable.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: 10pt">No=85 EUI-64 =
requires 64=20
bit host id=92s. &nbsp;48 bits is from the MAC. &nbsp;How would you plan =
to=20
squeeze blood out of the proverbial turnip?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3DArial><SPAN=20
style=3D"FONT-FAMILY: Arial; COLOR: navy; FONT-SIZE: =
10pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<P class=3DMsoNormal><FONT color=3Dnavy size=3D2 face=3D"Times New =
Roman"><SPAN=20
style=3D"COLOR: navy; FONT-SIZE: =
10pt">0101001101100101011011010111000001100101011100100010000001000110011=
01001<BR><BR>Jeremy=20
Duncan<BR><BR>Defense Threat Reduction Agency (DTRA)<BR>BE-BI INFOCON 3, =
IPv6=20
Architect<BR>Command Information<BR>Google Voice:&nbsp; (540)=20
440-1193</SPAN></FONT><o:p></o:p></P></DIV>
<DIV>
<DIV style=3D"TEXT-ALIGN: center" class=3DMsoNormal align=3Dcenter><FONT =
size=3D3=20
face=3D"Times New Roman"><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter SIZE=3D2 width=3D"100%">
</SPAN></FONT></DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_00F6_01CBD9F7.0E351360--


From suresh.krishnan@ericsson.com  Thu Mar  3 10:27:19 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7431028C0F1 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 10:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MjYIB0Qcdiap for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 10:27:18 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by core3.amsl.com (Postfix) with ESMTP id 4043B3A682C for <ipv6@ietf.org>; Thu,  3 Mar 2011 10:27:18 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id p23ISN0R025806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Mar 2011 12:28:24 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Thu, 3 Mar 2011 13:28:23 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, james woodyatt <jhw@apple.com>
Date: Thu, 3 Mar 2011 13:28:21 -0500
Subject: RE: draft-yhb-6man-ra-privacy-flag-01
Thread-Topic: draft-yhb-6man-ra-privacy-flag-01
Thread-Index: AcvZTu3mhUIn8lt2QUCkhCN3p8i8wgAgAkkg
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150EBF3060D@EUSAACMS0703.eamcs.ericsson.se>
References: <AANLkTin7oZR2Y=PO_k_24VQ115bbA_ehomgtZxDJzEE7@mail.gmail.com> <054EBE54-D54C-4154-8C72-0F413F462BB0@apple.com> <alpine.DEB.1.10.1103030352210.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103030352210.7942@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6MAN <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 18:27:19 -0000

Hi Mike,
=20

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
> Behalf Of Mikael Abrahamsson
> Sent: Wednesday, March 02, 2011 6:58 PM
> To: james woodyatt
> Cc: 6MAN
> Subject: Re: draft-yhb-6man-ra-privacy-flag-01
>=20
> On Wed, 2 Mar 2011, james woodyatt wrote:
>=20
> > The current revision of the draft contains a normative reference to=20
> > RFC
> > 4941 but it doesn't seem to have any language in section 2.3=20
> > specifying host behavior that would prevent it from using any other=20
> > sort of statelessly autoconfigured addresses that would=20
> pose the same=20
> > problem for network administrators that privacy addresses do, i.e.=20
> > make it difficult to identify authoritatively which host is the=20
> > originator of any particular traffic given only the source=20
> addresses=20
> > in the captured
> > IPv6 headers.  It just says, hosts MUST have a conceptual variable=20
> > that controls whether they generate temporary addresses. =20
> That doesn't=20
> > prevent them from generating persistent ones that pose the same=20
> > problem for network administrators as RFC 4941 privacy addresses.
>=20
> In our testing, the only way we found to achieve this was to=20
> not announce any on-net prefix and using the M-flag to make=20
> the client ask for DHCPv6 address.
>=20
> I've asked this before in different fora because I have not=20
> been able to find any RFC text.
>=20
> Wen an on-link prefix is present and the M-flag is set, RFC4861 says:
>=20
> M              1-bit "Managed address configuration" flag.  When
>                       set, it indicates that addresses are=20
> available via
>                       Dynamic Host Configuration Protocol [DHCPv6].
>=20
> It doesn't say "don't do SLAAC and only get addresses from=20
> IPv6". So my interpretation is that as soon as there is an=20
> on-link prefix, hosts will do SLAAC regardless of M flag 0 or 1.

No. This is not the case. We can have on-link prefixes that are not used fo=
r SLAAC. All you have to do is set the L flag to 1 and the A flag to 0 in t=
he PIO. This means that the host will not use this prefix to do SLAAC.

>=20
> So let's say I want to disallow SLAAC, I want to hand out=20
> addresses using DHCPv6, but I still want the hosts to be able=20
> to talk L2 directly to each other within the subnet.

This is possible using the link-local addresses.

>=20
> How should I configure things when it comes to information in=20
> RA and DHCPv6? If this isn't possible, was this intentional=20
> behaviour from the beginning, that DHCPv6 hosts without SLAAC=20
> can't get an on-link prefix but they must go through the=20
> router to talk to each other?

This is perfectly doable within the current specs. This is what I would adv=
ise.=20

Let's say the DHCPv6 addresses are formed using the prefix P1::/64. All you=
 need to do is to advertise the prefix P1 in a PIO of an RA with L=3D1 and =
A=3D0. This will let hosts communicate directly without going through the r=
outer and it will also disable SLAAC.

Thanks
Suresh

From ipng@69706e6720323030352d30312d31340a.nosense.org  Thu Mar  3 13:00:07 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA3D73A6A20 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:00:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akLi+yCiorzm for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:00:04 -0800 (PST)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id BC8913A6823 for <ipv6@ietf.org>; Thu,  3 Mar 2011 13:00:03 -0800 (PST)
Received: from 114-30-108-110.ip.adam.com.au ([114.30.108.110] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PvFdr-00030a-7p; Fri, 04 Mar 2011 07:30:59 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 91BB15355A; Fri,  4 Mar 2011 07:30:58 +1030 (CST)
Date: Fri, 4 Mar 2011 07:30:58 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Yu Hua bing" <yhb810501@gmail.com>
Subject: Re: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110304073058.7b8bc56d@opy.nosense.org>
In-Reply-To: <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com> <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@yhbPC> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>, "Duncan, Richard J. \(Jeremy\) CONTRACTOR" <Richard.Duncan_contractor@DTRA.MIL>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 21:00:08 -0000

Hi,

I think your fundamental premise is flawed. You're saying that as an
upstream provider is precious about address space, and only going to
give out a /64, that it should be possible to subnet that /64 further. 
Unfortunately all I think that will do is also facilitate the upstream
provider pushing the initial allocation boundary even further to the
right. A really "precious" upstream provider will start handing
out /127s, /126s etc. because they now can - only as many as they
perceive you to "need" right now. You'll have to justify the
exact amount of address space you want, you'll have to deal with
them again to get more, and they'll have to manage their IPv6 address
space at an address rather than subnet level. All these costs are
necessary ones in IPv4, but don't need to exist in IPv6. There are no
useful benefits to be gained from paying them.

One thing I'm noticing is that when people find out that a /64 is the
basic minimum size for a subnet, and that it's all about numbers of
subnets, rather than numbers of addresses, they start to slowly stop
applying their IPv4 conserve addresses addresses mentality to IPv6. I
think moving away from a single and fixed size interface id will start
to encourage people to become more conservative again, unnecessarily.

Oh, and "waste" only occurs if you get no value when you use something -

" In fact,
   any LAN can't run out of so many IPv6 addresses, and only a very
   small part of IPv6 addresses are used, so it is a serious waste."

The value you get out of IPv6's (and also in fact Ethernet's) large
address space is convenience. If you have a car with an automatic
transmission, or electric windows, or central locking, or even an
electric start (i.e. you're not hand winding it to start it), you've
already placed value on having convenience. If the costs are low enough
(e.g. cheap addressing bits), data networking protocols should be
convenient to use too.

Regards,
Mark.

On Thu, 3 Mar 2011 23:02:22 +0800
"Yu Hua bing" <yhb810501@gmail.com> wrote:

>       If the prefix is longer than 64, don't use EUI-64 interface ID.
> 
>    (7.2)If the prefix length is greater than 64 and is not greater than
>    80, an address is formed by combining the advertised prefix with 
>    the MAC address of the interface as follows:
> 
>       |            N bits            | (80 - N) bits |     48 bits     |
>       +------------------------------+---------------+-----------------+
>       |            link prefix       |   reserved    |   MAC address   |
>       +----------------------------------------------------------------+
>    (7.3) If the prefix length is greater than 80, a random number 
>    between 0 and 2 ^ (128 - prefix length) is generated, and an address
>    is formed by combining the advertised prefix with the random number
>    as follows:
>             
>       |                N bits                 |       128 - N bits     |
>       +---------------------------------------+------------------------+
>       |            link prefix                |     random number      |
>       +----------------------------------------------------------------+                    
> 
> 
> 
> From: Duncan, Richard J. (Jeremy) CONTRACTOR 
> Sent: Thursday, March 03, 2011 10:56 PM
> To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter 
> Cc: Thomas Narten ; ipv6 ; Scott W Brim 
> Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00
> 
> 
> I think that SLAAC should be deployed in the sites which use the prefixes longer than 64. 
> 
> Don't put a limit on the prefix length.
> 
> DHCPv6 can be deployed in the sites which use the prefixes longer than 64.Why can't SLAAC?
> 
> It is not reasonable.
> 
>  
> 
> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How would you plan to squeeze blood out of the proverbial turnip?
> 
>  
> 
>  
> 
> 010100110110010101101101011100000110010101110010001000000100011001101001
> 
> Jeremy Duncan
> 
> Defense Threat Reduction Agency (DTRA)
> BE-BI INFOCON 3, IPv6 Architect
> Command Information
> Google Voice:  (540) 440-1193
> 
> 
> --------------------------------------------------------------------------------

From brian.e.carpenter@gmail.com  Thu Mar  3 13:40:35 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE3A728C0DF for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.49
X-Spam-Level: 
X-Spam-Status: No, score=-103.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aDJ6UA2d0VOn for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:40:32 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 10A9D3A6835 for <ipv6@ietf.org>; Thu,  3 Mar 2011 13:40:31 -0800 (PST)
Received: by fxm15 with SMTP id 15so1669311fxm.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 13:41:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DVGZiNo/1E8Jr0g3t/WQZZX0HjXc7H+2ikGS6gKP6Q0=; b=Nyq20sb7uEUxEuI+tPVhjdW5nL4ubXFxCZ2ILk5v7u6t/jDlwIkfwPh9EgDRlvV/PR EnhDGcyoSU7xW5WxyNeuEZkHRGfOH4um8KY0NzZuoCo6RnnojJTDh7Iqm8t9CzMOHYM3 toMsw5GesvidfwNRheGaj0xPTqWF8GeMxMKfI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=ub8s3z85V+2NA5jE/Xy5U9AkeRHd9d5ycHoVwfW0tZMZ/luwLHGDHa7NWxDNNoeSo1 np1ONkmFF2GhLgHT91Fr5/Rb1iG7gFBPdeUq4BAMBnZTstHo1G+laGSLP4pLoYRsaU5h JWvCOzeOtG/pfsk/BJZPE2m05nuN09obJfdrg=
Received: by 10.223.71.195 with SMTP id i3mr2090896faj.149.1299188497645; Thu, 03 Mar 2011 13:41:37 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id n26sm857346fam.37.2011.03.03.13.41.30 (version=SSLv3 cipher=OTHER); Thu, 03 Mar 2011 13:41:36 -0800 (PST)
Message-ID: <4D700B06.9040802@gmail.com>
Date: Fri, 04 Mar 2011 10:41:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>	<4D6EAF57.8050606@gmail.com>	<201103022125.p22LPljL020592@cichlid.raleigh.ibm.com>	<4D6EC041.4070304@gmail.com>	<AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com>	<4D6EC58A.6050404@gmail.com>	<AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>	<FFBA5A9A337141739D05B7F35096787F@yhbPC>	<9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>	<7B548E69939543EFA27A8AA66A2AAD1A@yhbPC> <20110304073058.7b8bc56d@opy.nosense.org>
In-Reply-To: <20110304073058.7b8bc56d@opy.nosense.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>, "Duncan, Richard J. \(Jeremy\) CONTRACTOR" <Richard.Duncan_contractor@DTRA.MIL>, Yu Hua bing <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 21:40:35 -0000

Yes, and in fact draft-ietf-v6ops-3177bis-end-sites deals
with this and will be an RFC soon:

https://datatracker.ietf.org/doc/search/?name=draft-ietf-v6ops-3177bis-end-sites&rfcs=on&activeDrafts=on

Regards
   Brian Carpenter

On 2011-03-04 10:00, Mark Smith wrote:
> Hi,
> 
> I think your fundamental premise is flawed. You're saying that as an
> upstream provider is precious about address space, and only going to
> give out a /64, that it should be possible to subnet that /64 further. 
> Unfortunately all I think that will do is also facilitate the upstream
> provider pushing the initial allocation boundary even further to the
> right. A really "precious" upstream provider will start handing
> out /127s, /126s etc. because they now can - only as many as they
> perceive you to "need" right now. You'll have to justify the
> exact amount of address space you want, you'll have to deal with
> them again to get more, and they'll have to manage their IPv6 address
> space at an address rather than subnet level. All these costs are
> necessary ones in IPv4, but don't need to exist in IPv6. There are no
> useful benefits to be gained from paying them.
> 
> One thing I'm noticing is that when people find out that a /64 is the
> basic minimum size for a subnet, and that it's all about numbers of
> subnets, rather than numbers of addresses, they start to slowly stop
> applying their IPv4 conserve addresses addresses mentality to IPv6. I
> think moving away from a single and fixed size interface id will start
> to encourage people to become more conservative again, unnecessarily.
> 
> Oh, and "waste" only occurs if you get no value when you use something -
> 
> " In fact,
>    any LAN can't run out of so many IPv6 addresses, and only a very
>    small part of IPv6 addresses are used, so it is a serious waste."
> 
> The value you get out of IPv6's (and also in fact Ethernet's) large
> address space is convenience. If you have a car with an automatic
> transmission, or electric windows, or central locking, or even an
> electric start (i.e. you're not hand winding it to start it), you've
> already placed value on having convenience. If the costs are low enough
> (e.g. cheap addressing bits), data networking protocols should be
> convenient to use too.
> 
> Regards,
> Mark.
> 
> On Thu, 3 Mar 2011 23:02:22 +0800
> "Yu Hua bing" <yhb810501@gmail.com> wrote:
> 
>>       If the prefix is longer than 64, don't use EUI-64 interface ID.
>>
>>    (7.2)If the prefix length is greater than 64 and is not greater than
>>    80, an address is formed by combining the advertised prefix with 
>>    the MAC address of the interface as follows:
>>
>>       |            N bits            | (80 - N) bits |     48 bits     |
>>       +------------------------------+---------------+-----------------+
>>       |            link prefix       |   reserved    |   MAC address   |
>>       +----------------------------------------------------------------+
>>    (7.3) If the prefix length is greater than 80, a random number 
>>    between 0 and 2 ^ (128 - prefix length) is generated, and an address
>>    is formed by combining the advertised prefix with the random number
>>    as follows:
>>             
>>       |                N bits                 |       128 - N bits     |
>>       +---------------------------------------+------------------------+
>>       |            link prefix                |     random number      |
>>       +----------------------------------------------------------------+                    
>>
>>
>>
>> From: Duncan, Richard J. (Jeremy) CONTRACTOR 
>> Sent: Thursday, March 03, 2011 10:56 PM
>> To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter 
>> Cc: Thomas Narten ; ipv6 ; Scott W Brim 
>> Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00
>>
>>
>> I think that SLAAC should be deployed in the sites which use the prefixes longer than 64. 
>>
>> Don't put a limit on the prefix length.
>>
>> DHCPv6 can be deployed in the sites which use the prefixes longer than 64.Why can't SLAAC?
>>
>> It is not reasonable.
>>
>>  
>>
>> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How would you plan to squeeze blood out of the proverbial turnip?
>>
>>  
>>
>>  
>>
>> 010100110110010101101101011100000110010101110010001000000100011001101001
>>
>> Jeremy Duncan
>>
>> Defense Threat Reduction Agency (DTRA)
>> BE-BI INFOCON 3, IPv6 Architect
>> Command Information
>> Google Voice:  (540) 440-1193
>>
>>
>> --------------------------------------------------------------------------------
> 

From albert.e.manfredi@boeing.com  Thu Mar  3 13:58:23 2011
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86C4C3A6A05 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvaPFPT1+-G7 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 13:58:22 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 6EC333A68B0 for <ipv6@ietf.org>; Thu,  3 Mar 2011 13:58:22 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p23LxSkP025196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 3 Mar 2011 13:59:29 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p23LxSPt006217; Thu, 3 Mar 2011 15:59:28 -0600 (CST)
Received: from XCH-MWHT-02.mw.nos.boeing.com (xch-mwht-02.mw.nos.boeing.com [134.57.113.20]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p23LxSpv006214 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 3 Mar 2011 15:59:28 -0600 (CST)
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-02.mw.nos.boeing.com ([134.57.113.20]) with mapi; Thu, 3 Mar 2011 15:59:28 -0600
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Thu, 3 Mar 2011 15:59:25 -0600
Subject: RE: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Thread-Topic: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
Thread-Index: AcvZ69VdF2FuCyoaSUSdzqxVSeZhAwAAK7kg
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>	< 4D6EAF57.8050606@gmail.com>	<201103022125.p22LPljL020592@cichlid.raleigh.ib m.com>	<4D6EC041.4070304@gmail.com>	<AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0Vz S7pfZk4@mail.gmail.com>	<4D6EC58A.6050404@gmail.com>	<AANLkTim95MdX+EXCk06j bE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>	<FFBA5A9A337141739D05B7F35096787F@ yhbPC>	<9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC><20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com>
In-Reply-To: <4D700B06.9040802@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 21:58:23 -0000

I guess I'm missing what the solution is.

As 3177-bis says, the IETF has no control over how service providers hand o=
ut IPv6 address space. From what I've been reading in the past few years, i=
t looks like at least some providers are planning to give /64s to customers=
.

The way I see it, unless we permit SLAAC to use more than 64-bit prefixes, =
either of two things will happen.

1. SLAAC will not work inside home networks, except for the simplest one-co=
mputer case, or

2. Someone will have the brilliant idea to invent an IPv6 NAT.

As Mark points out, this may encourage providers to hand out /127s. So, roc=
k and hard place. What's the answer, if no one can force providers to hand =
out AT LEAST /56s? NAT?

Bert

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Thursday, March 03, 2011 4:41 PM
> To: Mark Smith
> Cc: Thomas Narten; ipv6; Scott W Brim; Duncan,Richard J. (Jeremy)
> CONTRACTOR; Yu Hua bing
> Subject: Re: [BULK] Re: draft-yhb-6man-slaac-improvement-00
>=20
> Yes, and in fact draft-ietf-v6ops-3177bis-end-sites deals
> with this and will be an RFC soon:
>=20
> https://datatracker.ietf.org/doc/search/?name=3Ddraft-ietf-v6ops-3177bis-
> end-sites&rfcs=3Don&activeDrafts=3Don
>=20
> Regards
>    Brian Carpenter
>=20
> On 2011-03-04 10:00, Mark Smith wrote:
> > Hi,
> >
> > I think your fundamental premise is flawed. You're saying that as an
> > upstream provider is precious about address space, and only going to
> > give out a /64, that it should be possible to subnet that /64
> further.
> > Unfortunately all I think that will do is also facilitate the
> upstream
> > provider pushing the initial allocation boundary even further to the
> > right. A really "precious" upstream provider will start handing
> > out /127s, /126s etc. because they now can - only as many as they
> > perceive you to "need" right now. You'll have to justify the
> > exact amount of address space you want, you'll have to deal with
> > them again to get more, and they'll have to manage their IPv6 address
> > space at an address rather than subnet level. All these costs are
> > necessary ones in IPv4, but don't need to exist in IPv6. There are no
> > useful benefits to be gained from paying them.
> >
> > One thing I'm noticing is that when people find out that a /64 is the
> > basic minimum size for a subnet, and that it's all about numbers of
> > subnets, rather than numbers of addresses, they start to slowly stop
> > applying their IPv4 conserve addresses addresses mentality to IPv6. I
> > think moving away from a single and fixed size interface id will
> start
> > to encourage people to become more conservative again, unnecessarily.
> >
> > Oh, and "waste" only occurs if you get no value when you use
> something -
> >
> > " In fact,
> >    any LAN can't run out of so many IPv6 addresses, and only a very
> >    small part of IPv6 addresses are used, so it is a serious waste."
> >
> > The value you get out of IPv6's (and also in fact Ethernet's) large
> > address space is convenience. If you have a car with an automatic
> > transmission, or electric windows, or central locking, or even an
> > electric start (i.e. you're not hand winding it to start it), you've
> > already placed value on having convenience. If the costs are low
> enough
> > (e.g. cheap addressing bits), data networking protocols should be
> > convenient to use too.
> >
> > Regards,
> > Mark.
> >
> > On Thu, 3 Mar 2011 23:02:22 +0800
> > "Yu Hua bing" <yhb810501@gmail.com> wrote:
> >
> >>       If the prefix is longer than 64, don't use EUI-64 interface
> ID.
> >>
> >>    (7.2)If the prefix length is greater than 64 and is not greater
> than
> >>    80, an address is formed by combining the advertised prefix with
> >>    the MAC address of the interface as follows:
> >>
> >>       |            N bits            | (80 - N) bits |     48 bits
> |
> >>       +------------------------------+---------------+--------------
> ---+
> >>       |            link prefix       |   reserved    |   MAC address
> |
> >>       +-------------------------------------------------------------
> ---+
> >>    (7.3) If the prefix length is greater than 80, a random number
> >>    between 0 and 2 ^ (128 - prefix length) is generated, and an
> address
> >>    is formed by combining the advertised prefix with the random
> number
> >>    as follows:
> >>
> >>       |                N bits                 |       128 - N bits
> |
> >>       +---------------------------------------+---------------------
> ---+
> >>       |            link prefix                |     random number
> |
> >>       +-------------------------------------------------------------
> ---+
> >>
> >>
> >>
> >> From: Duncan, Richard J. (Jeremy) CONTRACTOR
> >> Sent: Thursday, March 03, 2011 10:56 PM
> >> To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter
> >> Cc: Thomas Narten ; ipv6 ; Scott W Brim
> >> Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00
> >>
> >>
> >> I think that SLAAC should be deployed in the sites which use the
> prefixes longer than 64.
> >>
> >> Don't put a limit on the prefix length.
> >>
> >> DHCPv6 can be deployed in the sites which use the prefixes longer
> than 64.Why can't SLAAC?
> >>
> >> It is not reasonable.
> >>
> >>
> >>
> >> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How
> would you plan to squeeze blood out of the proverbial turnip?
> >>
> >>
> >>
> >>
> >>
> >>
> 01010011011001010110110101110000011001010111001000100000010001100110100
> 1
> >>
> >> Jeremy Duncan
> >>
> >> Defense Threat Reduction Agency (DTRA)
> >> BE-BI INFOCON 3, IPv6 Architect
> >> Command Information
> >> Google Voice:  (540) 440-1193
> >>
> >>
> >> --------------------------------------------------------------------
> ------------
> >
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From tena@huawei.com  Thu Mar  3 14:01:00 2011
Return-Path: <tena@huawei.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C29B28C0DF for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.452
X-Spam-Level: 
X-Spam-Status: No, score=-106.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXWnMiJwTrm6 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:00:58 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 97CA93A6A46 for <ipv6@ietf.org>; Thu,  3 Mar 2011 14:00:58 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHI005O357IB3@usaga04-in.huawei.com> for ipv6@ietf.org; Thu, 03 Mar 2011 16:02:06 -0600 (CST)
Received: from TingZousc1 ([10.212.246.186]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LHI00IWJ57G2I@usaga04-in.huawei.com> for ipv6@ietf.org; Thu, 03 Mar 2011 16:02:06 -0600 (CST)
Date: Thu, 03 Mar 2011 14:02:06 -0800
From: Tina Tsou <tena@huawei.com>
Subject: RE: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
In-reply-to: <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
To: "'Manfredi, Albert E'" <albert.e.manfredi@boeing.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
Message-id: <02e101cbd9ee$a40620e0$ec1262a0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvZ69VdF2FuCyoaSUSdzqxVSeZhAwAAK7kgAACA4hA=
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <4D6EC041.4070304@gmail.com> <"AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0Vz S7pfZk4"@mail.gmail.com> <4D6EC58A.6050404@gmail.com> <"AANLkTim95MdX+EXCk06j bE0ofXZz3ivxVYo4V+hpGNbL"@mail.gmail.com> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC> <20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com> <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
Cc: 'ipv6' <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 22:01:00 -0000

Hi Bert,
Comments in line.


We keep our promises with one another - no matter what!

Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html


-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Manfredi, Albert E
Sent: Thursday, March 03, 2011 1:59 PM
To: Brian E Carpenter
Cc: ipv6
Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00

I guess I'm missing what the solution is.

As 3177-bis says, the IETF has no control over how service providers hand
out IPv6 address space. From what I've been reading in the past few years,
it looks like at least some providers are planning to give /64s to
customers.

The way I see it, unless we permit SLAAC to use more than 64-bit prefixes,
either of two things will happen.

1. SLAAC will not work inside home networks, except for the simplest
one-computer case, or

2. Someone will have the brilliant idea to invent an IPv6 NAT.
[Tina: do you mean NAT66?]

As Mark points out, this may encourage providers to hand out /127s. So, rock
and hard place. What's the answer, if no one can force providers to hand out
AT LEAST /56s? NAT?

Bert

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Thursday, March 03, 2011 4:41 PM
> To: Mark Smith
> Cc: Thomas Narten; ipv6; Scott W Brim; Duncan,Richard J. (Jeremy)
> CONTRACTOR; Yu Hua bing
> Subject: Re: [BULK] Re: draft-yhb-6man-slaac-improvement-00
> 
> Yes, and in fact draft-ietf-v6ops-3177bis-end-sites deals
> with this and will be an RFC soon:
> 
> https://datatracker.ietf.org/doc/search/?name=draft-ietf-v6ops-3177bis-
> end-sites&rfcs=on&activeDrafts=on
> 
> Regards
>    Brian Carpenter
> 
> On 2011-03-04 10:00, Mark Smith wrote:
> > Hi,
> >
> > I think your fundamental premise is flawed. You're saying that as an
> > upstream provider is precious about address space, and only going to
> > give out a /64, that it should be possible to subnet that /64
> further.
> > Unfortunately all I think that will do is also facilitate the
> upstream
> > provider pushing the initial allocation boundary even further to the
> > right. A really "precious" upstream provider will start handing
> > out /127s, /126s etc. because they now can - only as many as they
> > perceive you to "need" right now. You'll have to justify the
> > exact amount of address space you want, you'll have to deal with
> > them again to get more, and they'll have to manage their IPv6 address
> > space at an address rather than subnet level. All these costs are
> > necessary ones in IPv4, but don't need to exist in IPv6. There are no
> > useful benefits to be gained from paying them.
> >
> > One thing I'm noticing is that when people find out that a /64 is the
> > basic minimum size for a subnet, and that it's all about numbers of
> > subnets, rather than numbers of addresses, they start to slowly stop
> > applying their IPv4 conserve addresses addresses mentality to IPv6. I
> > think moving away from a single and fixed size interface id will
> start
> > to encourage people to become more conservative again, unnecessarily.
> >
> > Oh, and "waste" only occurs if you get no value when you use
> something -
> >
> > " In fact,
> >    any LAN can't run out of so many IPv6 addresses, and only a very
> >    small part of IPv6 addresses are used, so it is a serious waste."
> >
> > The value you get out of IPv6's (and also in fact Ethernet's) large
> > address space is convenience. If you have a car with an automatic
> > transmission, or electric windows, or central locking, or even an
> > electric start (i.e. you're not hand winding it to start it), you've
> > already placed value on having convenience. If the costs are low
> enough
> > (e.g. cheap addressing bits), data networking protocols should be
> > convenient to use too.
> >
> > Regards,
> > Mark.
> >
> > On Thu, 3 Mar 2011 23:02:22 +0800
> > "Yu Hua bing" <yhb810501@gmail.com> wrote:
> >
> >>       If the prefix is longer than 64, don't use EUI-64 interface
> ID.
> >>
> >>    (7.2)If the prefix length is greater than 64 and is not greater
> than
> >>    80, an address is formed by combining the advertised prefix with
> >>    the MAC address of the interface as follows:
> >>
> >>       |            N bits            | (80 - N) bits |     48 bits
> |
> >>       +------------------------------+---------------+--------------
> ---+
> >>       |            link prefix       |   reserved    |   MAC address
> |
> >>       +-------------------------------------------------------------
> ---+
> >>    (7.3) If the prefix length is greater than 80, a random number
> >>    between 0 and 2 ^ (128 - prefix length) is generated, and an
> address
> >>    is formed by combining the advertised prefix with the random
> number
> >>    as follows:
> >>
> >>       |                N bits                 |       128 - N bits
> |
> >>       +---------------------------------------+---------------------
> ---+
> >>       |            link prefix                |     random number
> |
> >>       +-------------------------------------------------------------
> ---+
> >>
> >>
> >>
> >> From: Duncan, Richard J. (Jeremy) CONTRACTOR
> >> Sent: Thursday, March 03, 2011 10:56 PM
> >> To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter
> >> Cc: Thomas Narten ; ipv6 ; Scott W Brim
> >> Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00
> >>
> >>
> >> I think that SLAAC should be deployed in the sites which use the
> prefixes longer than 64.
> >>
> >> Don't put a limit on the prefix length.
> >>
> >> DHCPv6 can be deployed in the sites which use the prefixes longer
> than 64.Why can't SLAAC?
> >>
> >> It is not reasonable.
> >>
> >>
> >>
> >> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How
> would you plan to squeeze blood out of the proverbial turnip?
> >>
> >>
> >>
> >>
> >>
> >>
> 01010011011001010110110101110000011001010111001000100000010001100110100
> 1
> >>
> >> Jeremy Duncan
> >>
> >> Defense Threat Reduction Agency (DTRA)
> >> BE-BI INFOCON 3, IPv6 Architect
> >> Command Information
> >> Google Voice:  (540) 440-1193
> >>
> >>
> >> --------------------------------------------------------------------
> ------------
> >
> --------------------------------------------------------------------
> 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 brian.e.carpenter@gmail.com  Thu Mar  3 14:07:13 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B4D33A687C for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.493
X-Spam-Level: 
X-Spam-Status: No, score=-103.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7UE5fliBHCR for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:07:12 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id DEB943A6850 for <ipv6@ietf.org>; Thu,  3 Mar 2011 14:07:11 -0800 (PST)
Received: by fxm15 with SMTP id 15so1692555fxm.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 14:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SHfu3cYdyPDSXcd97aBIdvYc8NuAgdSaF1IJcNyr9Ms=; b=rZp4DDq5pFVq0pgOZsQVfKJDxhWQMCGO9b3ZUOsNX0GzGdNvpbkRMXbF/6relIoMg3 7mZQ2xoAiQlKx074clxvkpqJf8Hrcgjm0GIzFjM3DqN2x3jX6RrPrl+6OJSqyK2Hmbje Ze33A4Etesl/jQ6SjAByDrGL+5G4hz/ZmNV74=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=ryB8nIxNxGBx5ENsYoDFsmJzVU93P8DqHuVhRQpsxs920Iisnjq2X9P2MMX0cR6hXA rLUSZ4nN8py8pJ6TaLFpKXAlzHWlp5Av7Cg/nGnlDVqI2cPXiqotQYHBKvQabPosPpJv U+fQ+xCdw1JMANpGGvAkHdRJGVAel0/dpo8Xk=
Received: by 10.223.96.67 with SMTP id g3mr2198030fan.114.1299190099457; Thu, 03 Mar 2011 14:08:19 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id e17sm61455fak.10.2011.03.03.14.08.14 (version=SSLv3 cipher=OTHER); Thu, 03 Mar 2011 14:08:17 -0800 (PST)
Message-ID: <4D701149.6020600@gmail.com>
Date: Fri, 04 Mar 2011 11:08:09 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Subject: Re: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com>	<	4D6EAF57.8050606@gmail.com>	<201103022125.p22LPljL020592@cichlid.raleigh.ib	m.com>	<4D6EC041.4070304@gmail.com>	<AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0Vz	S7pfZk4@mail.gmail.com>	<4D6EC58A.6050404@gmail.com>	<AANLkTim95MdX+EXCk06j	bE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com>	<FFBA5A9A337141739D05B7F35096787F@	yhbPC>	<9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>		<7B548E69939543EFA27A8AA66A2AAD1A@yhbPC><20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com> <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 22:07:13 -0000

On 2011-03-04 10:59, Manfredi, Albert E wrote:
> I guess I'm missing what the solution is.
> 
> As 3177-bis says, the IETF has no control over how service providers hand out IPv6 address space. From what I've been reading in the past few years, it looks like at least some providers are planning to give /64s to customers.

Then their customers will discover that they need to switch to
another ISP, won't they?

   Brian

> 
> The way I see it, unless we permit SLAAC to use more than 64-bit prefixes, either of two things will happen.
> 
> 1. SLAAC will not work inside home networks, except for the simplest one-computer case, or
> 
> 2. Someone will have the brilliant idea to invent an IPv6 NAT.
> 
> As Mark points out, this may encourage providers to hand out /127s. So, rock and hard place. What's the answer, if no one can force providers to hand out AT LEAST /56s? NAT?
> 
> Bert
> 
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
>> Brian E Carpenter
>> Sent: Thursday, March 03, 2011 4:41 PM
>> To: Mark Smith
>> Cc: Thomas Narten; ipv6; Scott W Brim; Duncan,Richard J. (Jeremy)
>> CONTRACTOR; Yu Hua bing
>> Subject: Re: [BULK] Re: draft-yhb-6man-slaac-improvement-00
>>
>> Yes, and in fact draft-ietf-v6ops-3177bis-end-sites deals
>> with this and will be an RFC soon:
>>
>> https://datatracker.ietf.org/doc/search/?name=draft-ietf-v6ops-3177bis-
>> end-sites&rfcs=on&activeDrafts=on
>>
>> Regards
>>    Brian Carpenter
>>
>> On 2011-03-04 10:00, Mark Smith wrote:
>>> Hi,
>>>
>>> I think your fundamental premise is flawed. You're saying that as an
>>> upstream provider is precious about address space, and only going to
>>> give out a /64, that it should be possible to subnet that /64
>> further.
>>> Unfortunately all I think that will do is also facilitate the
>> upstream
>>> provider pushing the initial allocation boundary even further to the
>>> right. A really "precious" upstream provider will start handing
>>> out /127s, /126s etc. because they now can - only as many as they
>>> perceive you to "need" right now. You'll have to justify the
>>> exact amount of address space you want, you'll have to deal with
>>> them again to get more, and they'll have to manage their IPv6 address
>>> space at an address rather than subnet level. All these costs are
>>> necessary ones in IPv4, but don't need to exist in IPv6. There are no
>>> useful benefits to be gained from paying them.
>>>
>>> One thing I'm noticing is that when people find out that a /64 is the
>>> basic minimum size for a subnet, and that it's all about numbers of
>>> subnets, rather than numbers of addresses, they start to slowly stop
>>> applying their IPv4 conserve addresses addresses mentality to IPv6. I
>>> think moving away from a single and fixed size interface id will
>> start
>>> to encourage people to become more conservative again, unnecessarily.
>>>
>>> Oh, and "waste" only occurs if you get no value when you use
>> something -
>>> " In fact,
>>>    any LAN can't run out of so many IPv6 addresses, and only a very
>>>    small part of IPv6 addresses are used, so it is a serious waste."
>>>
>>> The value you get out of IPv6's (and also in fact Ethernet's) large
>>> address space is convenience. If you have a car with an automatic
>>> transmission, or electric windows, or central locking, or even an
>>> electric start (i.e. you're not hand winding it to start it), you've
>>> already placed value on having convenience. If the costs are low
>> enough
>>> (e.g. cheap addressing bits), data networking protocols should be
>>> convenient to use too.
>>>
>>> Regards,
>>> Mark.
>>>
>>> On Thu, 3 Mar 2011 23:02:22 +0800
>>> "Yu Hua bing" <yhb810501@gmail.com> wrote:
>>>
>>>>       If the prefix is longer than 64, don't use EUI-64 interface
>> ID.
>>>>    (7.2)If the prefix length is greater than 64 and is not greater
>> than
>>>>    80, an address is formed by combining the advertised prefix with
>>>>    the MAC address of the interface as follows:
>>>>
>>>>       |            N bits            | (80 - N) bits |     48 bits
>> |
>>>>       +------------------------------+---------------+--------------
>> ---+
>>>>       |            link prefix       |   reserved    |   MAC address
>> |
>>>>       +-------------------------------------------------------------
>> ---+
>>>>    (7.3) If the prefix length is greater than 80, a random number
>>>>    between 0 and 2 ^ (128 - prefix length) is generated, and an
>> address
>>>>    is formed by combining the advertised prefix with the random
>> number
>>>>    as follows:
>>>>
>>>>       |                N bits                 |       128 - N bits
>> |
>>>>       +---------------------------------------+---------------------
>> ---+
>>>>       |            link prefix                |     random number
>> |
>>>>       +-------------------------------------------------------------
>> ---+
>>>>
>>>>
>>>> From: Duncan, Richard J. (Jeremy) CONTRACTOR
>>>> Sent: Thursday, March 03, 2011 10:56 PM
>>>> To: Yu Hua bing ; trejrco@gmail.com ; Brian E Carpenter
>>>> Cc: Thomas Narten ; ipv6 ; Scott W Brim
>>>> Subject: RE: [BULK] Re: draft-yhb-6man-slaac-improvement-00
>>>>
>>>>
>>>> I think that SLAAC should be deployed in the sites which use the
>> prefixes longer than 64.
>>>> Don't put a limit on the prefix length.
>>>>
>>>> DHCPv6 can be deployed in the sites which use the prefixes longer
>> than 64.Why can't SLAAC?
>>>> It is not reasonable.
>>>>
>>>>
>>>>
>>>> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How
>> would you plan to squeeze blood out of the proverbial turnip?
>>>>
>>>>
>>>>
>>>>
>>>>
>> 01010011011001010110110101110000011001010111001000100000010001100110100
>> 1
>>>> Jeremy Duncan
>>>>
>>>> Defense Threat Reduction Agency (DTRA)
>>>> BE-BI INFOCON 3, IPv6 Architect
>>>> Command Information
>>>> Google Voice:  (540) 440-1193
>>>>
>>>>
>>>> --------------------------------------------------------------------
>> ------------
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 

From trejrco@gmail.com  Thu Mar  3 14:09:20 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3513F3A68A9 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.377
X-Spam-Level: 
X-Spam-Status: No, score=-3.377 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V19cu19Eyyud for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 14:09:19 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 548AC3A687C for <ipv6@ietf.org>; Thu,  3 Mar 2011 14:09:19 -0800 (PST)
Received: by iwl42 with SMTP id 42so1612675iwl.31 for <ipv6@ietf.org>; Thu, 03 Mar 2011 14:10:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=U84HM7Kbxsu9ieQ4rxdwWV+5kaMi4Ub9R5bHpY/+faw=; b=Tk0pe8bn0vqGHcNCpj53+DjaTh9YkFDzlb5gq44UWNaltB7uuzajQ7kYSYMYlLorq2 NMWJdfiSr0VNbLRp7IMeNulRMgMRJ5CT6Fe+QpAz2EHq9HT1/AT2Azmh4igxbUr0OS7h p5MaDpkpzgvXklFBBenatpuQSzgagcgFgdRtI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=FVf/Pz6BIkUW+jH4EnqWd17c41wpuwYh72eTRSvkMEtM3za05lLlPQzUTXaC0vDYNJ qQm9s+m1yIhGt8yro+IZ40/vKcDCJEa2E2Vr/Qde+GMncimLcqutRj2EMzBdf2Zbdibk LebvfkMDWMd7/FkO6C8EIez7lPvlMhppjGvBI=
MIME-Version: 1.0
Received: by 10.231.206.197 with SMTP id fv5mr1389347ibb.84.1299190227465; Thu, 03 Mar 2011 14:10:27 -0800 (PST)
Received: by 10.231.148.143 with HTTP; Thu, 3 Mar 2011 14:10:27 -0800 (PST)
In-Reply-To: <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EC041.4070304@gmail.com> <4D6EC58A.6050404@gmail.com> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC> <20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com> <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
Date: Thu, 3 Mar 2011 17:10:27 -0500
Message-ID: <AANLkTimCBsb0Uutx2USh3_ZB323nSDwAnEEnQTAma_LF@mail.gmail.com>
Subject: Re: [BULK] Re: draft-yhb-6man-slaac-improvement-00
From: TJ <trejrco@gmail.com>
To: ipv6 <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=90e6ba4fc24800f870049d9b4c24
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 22:09:20 -0000

--90e6ba4fc24800f870049d9b4c24
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Mar 3, 2011 at 16:59, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> I guess I'm missing what the solution is.
>
The solution is for providers to not give out just /64s :).


>
> As 3177-bis says, the IETF has no control over how service providers hand
> out IPv6 address space. From what I've been reading in the past few years,
> it looks like at least some providers are planning to give /64s to
> customers.
>

Really?  None of the ISPs I have spoken with, and certainly none of the ones
I have worked with, are following a /64 per client plan.  I have discussed
/48s vs /56s vs /60s ... but never a /64.  If you know of any /64ers, please
name-and-shame them - or atleast push them to start thinking more clearly!


/TJ

--90e6ba4fc24800f870049d9b4c24
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Thu, Mar 3, 2011 at 16:59, Manfredi, Albe=
rt E <span dir=3D"ltr">&lt;<a href=3D"mailto:albert.e.manfredi@boeing.com">=
albert.e.manfredi@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;">
I guess I&#39;m missing what the solution is.<br></blockquote><div>The solu=
tion is for providers to not give out just /64s :).</div><div>=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex;">

<br>
As 3177-bis says, the IETF has no control over how service providers hand o=
ut IPv6 address space. From what I&#39;ve been reading in the past few year=
s, it looks like at least some providers are planning to give /64s to custo=
mers.<br>
</blockquote><div><br></div><div>Really? =A0None of the ISPs I have spoken =
with, and certainly none of the ones I have worked with, are following a /6=
4 per client plan. =A0I have discussed /48s vs /56s vs /60s ... but never a=
 /64. =A0If you know of any /64ers, please name-and-shame them - or atleast=
 push them to start thinking more clearly!</div>
<div><br></div><div><br></div><div>/TJ</div></div>

--90e6ba4fc24800f870049d9b4c24--

From jhw@apple.com  Thu Mar  3 15:29:40 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 760623A68BD for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 15:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.566
X-Spam-Level: 
X-Spam-Status: No, score=-106.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmpR-kSIRuE2 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 15:29:39 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 1E8B73A6872 for <ipv6@ietf.org>; Thu,  3 Mar 2011 15:29:39 -0800 (PST)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id 7B135D64AC08 for <ipv6@ietf.org>; Thu,  3 Mar 2011 15:30:40 -0800 (PST)
X-AuditID: 1180711d-b7c70ae00000719a-0a-4d7024a020f9
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay13.apple.com (Apple SCV relay) with SMTP id 13.F4.29082.0A4207D4; Thu,  3 Mar 2011 15:30:40 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHI00LDH9B4W710@gertie.apple.com> for ipv6@ietf.org; Thu, 03 Mar 2011 15:30:40 -0800 (PST)
Subject: Re: [BULK] draft-yhb-6man-slaac-improvement-00
From: james woodyatt <jhw@apple.com>
In-reply-to: <AANLkTimCBsb0Uutx2USh3_ZB323nSDwAnEEnQTAma_LF@mail.gmail.com>
Date: Thu, 03 Mar 2011 15:30:39 -0800
Message-id: <E06A3861-D916-4105-AF8A-2A918180E19F@apple.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EC041.4070304@gmail.com> <4D6EC58A.6050404@gmail.com> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC> <20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com> <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com> <AANLkTimCBsb0Uutx2USh3_ZB323nSDwAnEEnQTAma_LF@mail.gmail.com>
To: trejrco@gmail.com
X-Mailer: Apple Mail (2.1203)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 Mar 2011 23:29:40 -0000

On Mar 3, 2011, at 2:10 PM, TJ wrote:
> 
> As 3177-bis says, the IETF has no control over how service providers hand out IPv6 address space. From what I've been reading in the past few years, it looks like at least some providers are planning to give /64s to customers.
> 
> Really?  None of the ISPs I have spoken with, and certainly none of the ones I have worked with, are following a /64 per client plan.  I have discussed /48s vs /56s vs /60s ... but never a /64.  If you know of any /64ers, please name-and-shame them - or atleast push them to start thinking more clearly!

Here is a Reddit commenter from Canada who claims to have been delegated a native /64 prefix by some unnamed service provider:

  <http://www.reddit.com/r/ipv6/comments/fvvh9/i_am_a_verizon_fios_customerwhen_can_i_get_on_ipv6/c1j10sy>

Not sure how credible that claim can be regarded, but it's a claim that can be checked.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From dougb@dougbarton.us  Thu Mar  3 16:13:21 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEC063A68CB for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSUBR1Z5NgIO for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:13:20 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id 7C5DF3A68B7 for <ipv6@ietf.org>; Thu,  3 Mar 2011 16:13:20 -0800 (PST)
Received: (qmail 27165 invoked by uid 399); 4 Mar 2011 00:14:25 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 4 Mar 2011 00:14:25 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D702EDF.6000503@dougbarton.us>
Date: Thu, 03 Mar 2011 16:14:23 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.14) Gecko/20110301 Thunderbird/3.1.8
MIME-Version: 1.0
To: Yu Hua bing <yhb810501@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4D6EAF57.8050606@gmail.com><201103022125.p22LPljL020592@cichlid.raleigh.ibm.com><4D6EC041.4070304@gmail.com><AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com><4D6EC58A.6050404@gmail.com>	<AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@yhbPC>
In-Reply-To: <FFBA5A9A337141739D05B7F35096787F@yhbPC>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Scott W Brim <scott.brim@gmail.com>, ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 00:13:21 -0000

On 03/03/2011 06:50, Yu Hua bing wrote:
> DHCPv6 can be deployed in the sites which use the prefixes longer than
> 64.Why can't SLAAC?

Because SLAAC was not designed as a general-purpose mechanism, and 
should not be modified (further) to be so.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From albert.e.manfredi@boeing.com  Thu Mar  3 16:37:00 2011
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB8223A68B5 for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWv4tvVDf4MQ for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:36:58 -0800 (PST)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id A81733A6859 for <ipv6@ietf.org>; Thu,  3 Mar 2011 16:36:58 -0800 (PST)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id p240c3hM024058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 3 Mar 2011 16:38:04 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id p240c3IR010238; Thu, 3 Mar 2011 18:38:03 -0600 (CST)
Received: from XCH-MWHT-02.mw.nos.boeing.com (xch-mwht-02.mw.nos.boeing.com [134.57.113.20]) by stl-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id p240c3iO010235 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Thu, 3 Mar 2011 18:38:03 -0600 (CST)
Received: from XCH-MW-08V.mw.nos.boeing.com ([134.57.119.191]) by XCH-MWHT-02.mw.nos.boeing.com ([134.57.113.20]) with mapi; Thu, 3 Mar 2011 18:38:03 -0600
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: james woodyatt <jhw@apple.com>
Date: Thu, 3 Mar 2011 18:37:59 -0600
Subject: RE: [BULK] draft-yhb-6man-slaac-improvement-00
Thread-Topic: [BULK] draft-yhb-6man-slaac-improvement-00
Thread-Index: AcvZ+w3Ll6msRYbaThiBOjOtatHP8QAB3NiQ
Message-ID: <B0147C3DD45E42478038FC347CCB65FE02A76431CB@XCH-MW-08V.mw.nos.boeing.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4 D6EC041.4070304@gmail.com> <4D6EC58A.6050404@gmail.com><9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S 1.unet1.ad.dtra.mil><7B548E69939543EFA27A8AA66A2AAD1A@yhbPC><20110304073058 .7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com><B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH -MW-08V.mw.nos.boeing.com><AANLkTimCBsb0Uutx2USh3_ZB323nSDwAnEEnQTAma_LF@mail.gmail.com> <E06A3861-D916-4105-AF8A-2A918180E19F@apple.com>
In-Reply-To: <E06A3861-D916-4105-AF8A-2A918180E19F@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 00:37:01 -0000

> On Mar 3, 2011, at 2:10 PM, TJ wrote:

>> Really?  None of the ISPs I have spoken with, and certainly none of
>> the ones I have worked with, are following a /64 per client plan.  I
>> have discussed /48s vs /56s vs /60s ... but never a /64.

James Woodyatt wrote:

> Here is a Reddit commenter from Canada who claims to have been
> delegated a native /64 prefix by some unnamed service provider:
>=20
> <http://www.reddit.com/r/ipv6/comments/fvvh9/i_am_a_verizon_fios_custom
> erwhen_can_i_get_on_ipv6/c1j10sy>
>=20
> Not sure how credible that claim can be regarded, but it's a claim that
> can be checked.

I've certainly seen ISPs suggesting that they would do this. But a quick se=
arch turned up this, dated 2/8/2011:

http://www.ripe.net/ripe/docs/ripe-512#end_site

   5.4.1. Assignment address space size

   End Users are assigned an End Site assignment from their LIR or
   ISP. The size of the assignment is a local decision for the LIR
   or ISP to make, using a minimum value of a /64 (only one subnet
   is anticipated for the End Site).

So, is anyone willing to bet that ISPs won't use /64s?

Bert


From marka@isc.org  Thu Mar  3 16:42:25 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DB023A68CF for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.304
X-Spam-Level: 
X-Spam-Status: No, score=-5.304 tagged_above=-999 required=5 tests=[AWL=2.995,  BAYES_00=-2.599, MANGLED_LOOK=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIb+hn5l47bW for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 16:42:24 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) by core3.amsl.com (Postfix) with ESMTP id 7845A3A68CB for <ipv6@ietf.org>; Thu,  3 Mar 2011 16:42:24 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id D86A5C9422; Fri,  4 Mar 2011 00:42:09 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:ea06:88ff:fef3:4f9c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 53B52216C1E; Fri,  4 Mar 2011 00:42:09 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 285EDBA1AB3; Fri,  4 Mar 2011 11:42:07 +1100 (EST)
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
From: Mark Andrews <marka@isc.org>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> < 4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ib m.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0Vz S7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com> <AANLkTim95MdX+EXCk06j bE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@ yhbPC> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil> <7B548E69939543EFA27A8AA66A2AAD1A@yhbPC><20110304073058.7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com> <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
Subject: Re: [BULK] Re: draft-yhb-6man-slaac-improvement-00
In-reply-to: Your message of "Thu, 03 Mar 2011 15:59:25 MDT." <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing.com>
Date: Fri, 04 Mar 2011 11:42:07 +1100
Message-Id: <20110304004207.285EDBA1AB3@drugs.dv.isc.org>
Cc: ipv6 <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 00:42:25 -0000

In message <B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH-MW-08V.mw.nos.boeing
.com>, "Manfredi, Albert E" writes:
> I guess I'm missing what the solution is.
> 
> As 3177-bis says, the IETF has no control over how service providers hand out
> IPv6 address space. From what I've been reading in the past few years, it lo
> oks like at least some providers are planning to give /64s to customers.

Every ISP I've seen make that claim has also thought they need to
fit into a /32.  Once they were informed that that was not the case
they changed their plans.  Additionally the *nog lists see /56 as
being standard these days (changed from about 6 months ago).  There
are still arguments about /48 but the /56 vs /64 has gone to /56.

> The way I see it, unless we permit SLAAC to use more than 64-bit prefixes, ei
> ther of two things will happen.
> 
> 1. SLAAC will not work inside home networks, except for the simplest one-comp
> uter case, or
>
> 2. Someone will have the brilliant idea to invent an IPv6 NAT.
> 
> As Mark points out, this may encourage providers to hand out /127s. So, rock 
> and hard place. What's the answer, if no one can force providers to hand out 
> AT LEAST /56s? NAT?

Competition will.  CPE device manufactures will.  Prefix delegation
is being delivered today as part of the basic IPv6 functionality
set in CPE devices.

Remember HE hands out /48's for free to anyone in the world today.
6to4 delivers /48.  Current 6rd (RFC 5969) supports just about an
sized prefix.

I don't think this is something that needs to be solved as it is a
non problem.

> Bert
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Thu Mar  3 17:31:04 2011
Return-Path: <marka@isc.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB9C23A67FC for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 17:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILFxOWhSD9wq for <ipv6@core3.amsl.com>; Thu,  3 Mar 2011 17:31:02 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 016BE3A684B for <ipv6@ietf.org>; Thu,  3 Mar 2011 17:31:02 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 3DC585F9891; Fri,  4 Mar 2011 01:31:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:ea06:88ff:fef3:4f9c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1244D216C1E; Fri,  4 Mar 2011 01:31:52 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id F0B70BA21EB; Fri,  4 Mar 2011 12:31:49 +1100 (EST)
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
From: Mark Andrews <marka@isc.org>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com><4 D6EC041.4070304@gmail.com> <4D6EC58A.6050404@gmail.com><9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S 1.unet1.ad.dtra.mil><7B548E69939543EFA27A8AA66A2AAD1A@yhbPC><20110304073058 .7b8bc56d@opy.nosense.org> <4D700B06.9040802@gmail.com><B0147C3DD45E42478038FC347CCB65FE02A76431A2@XCH -MW-08V.mw.nos.boeing.com><AANLkTimCBsb0Uutx2USh3_ZB323nSDwAnEEnQTAma_LF@mail.gmail.com> <E06A3861-D916-4105-AF8A-2A918180E19F@apple.com> <B0147C3DD45E42478038FC347CCB65FE02A76431CB@XCH-MW-08V.mw.nos.boeing.com>
Subject: Re: [BULK] draft-yhb-6man-slaac-improvement-00
In-reply-to: Your message of "Thu, 03 Mar 2011 18:37:59 MDT." <B0147C3DD45E42478038FC347CCB65FE02A76431CB@XCH-MW-08V.mw.nos.boeing.com>
Date: Fri, 04 Mar 2011 12:31:49 +1100
Message-Id: <20110304013149.F0B70BA21EB@drugs.dv.isc.org>
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 01:31:04 -0000

In message <B0147C3DD45E42478038FC347CCB65FE02A76431CB@XCH-MW-08V.mw.nos.boeing
.com>, "Manfredi, Albert E" writes:
> > On Mar 3, 2011, at 2:10 PM, TJ wrote:
> 
> >> Really?  None of the ISPs I have spoken with, and certainly none of
> >> the ones I have worked with, are following a /64 per client plan.  I
> >> have discussed /48s vs /56s vs /60s ... but never a /64.
> 
> James Woodyatt wrote:
> 
> > Here is a Reddit commenter from Canada who claims to have been
> > delegated a native /64 prefix by some unnamed service provider:
> > 
> > <http://www.reddit.com/r/ipv6/comments/fvvh9/i_am_a_verizon_fios_custom
> > erwhen_can_i_get_on_ipv6/c1j10sy>
> > 
> > Not sure how credible that claim can be regarded, but it's a claim that
> > can be checked.
> 
> I've certainly seen ISPs suggesting that they would do this. But a quick sear
> ch turned up this, dated 2/8/2011:
> 
> http://www.ripe.net/ripe/docs/ripe-512#end_site
> 
>    5.4.1. Assignment address space size
> 
>    End Users are assigned an End Site assignment from their LIR or
>    ISP. The size of the assignment is a local decision for the LIR
>    or ISP to make, using a minimum value of a /64 (only one subnet
>    is anticipated for the End Site).
> 
> So, is anyone willing to bet that ISPs won't use /64s?

And it use /56 for the HD-Ratio.

5.2.1. Subsequent allocation criteria

Subsequent allocation will be provided when an organisation (i.e.
ISP/LIR) satisfies the evaluation threshold of past address utilisation
in terms of the number of sites in units of /56 assignments. The
HD-Ratio [RFC 3194] is used to determine the utilisation thresholds
that justify the allocation of additional address as described
below.

The customer just needs to say "you are allocated space assuming
that you will be handing out up to /56's, please give me a /56".

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From randy@psg.com  Fri Mar  4 01:09:14 2011
Return-Path: <randy@psg.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B5083A6971 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 01:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TpLn0HAQIocc for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 01:09:13 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 94BE23A693B for <ipv6@ietf.org>; Fri,  4 Mar 2011 01:09:13 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PvR1a-000HTO-8S; Fri, 04 Mar 2011 09:10:14 +0000
Date: Fri, 04 Mar 2011 18:10:12 +0900
Message-ID: <m27hcfz1xn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Duncan, Richard J. (Jeremy)  CONTRACTOR" <Richard.Duncan_contractor@DTRA.MIL>
Subject: Re: [BULK]  Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <AANLkTimpEqnwkKYzk51SG58JNeJ9tsnc+n0VzS7pfZk4@mail.gmail.com> <4D6EC58A.6050404@gmail.com> <AANLkTim95MdX+EXCk06jbE0ofXZz3ivxVYo4V+hpGNbL@mail.gmail.com> <FFBA5A9A337141739D05B7F35096787F@yhbPC> <9CDF28D4DC180243907E2B4791654E75D3353F@NNDD01S1.unet1.ad.dtra.mil>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: Thomas Narten <narten@us.ibm.com>, ipv6 <ipv6@ietf.org>, Scott W Brim <scott.brim@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Yu Hua bing <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 09:09:14 -0000

> No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How
> would you plan to squeeze blood out of the proverbial turnip?

perhaps going back and reading thomas's message would help dispel this
odd religion.

http://www.ietf.org/mail-archive/web/ipv6/current/msg13461.html

randy

From yhb810501@gmail.com  Fri Mar  4 05:24:54 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 482723A67C2 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 05:24:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.067
X-Spam-Level: 
X-Spam-Status: No, score=-3.067 tagged_above=-999 required=5 tests=[AWL=0.531,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eV8BUin6FFzI for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 05:24:53 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 565653A699C for <ipv6@ietf.org>; Fri,  4 Mar 2011 05:24:53 -0800 (PST)
Received: by vws6 with SMTP id 6so2244503vws.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 05:26:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:x-priority:x-msmail-priority :importance:x-mailer:x-mimeole; bh=NKXWA/+Eo+TthzJ/0dhS2ImZZg9Aqn1uuGsU5SbIekM=; b=m4lk7ouGb+Cqhl+X4Jo81IUELALijV/BxErlCiFRZgIojRihnYyECSxVSqIn1DZ1wl 4L5BidaDRPWa4frfoLcHMjbXKZrn75cZHLIJcprE5oKrHhFsu12lRiB+j73FtXGg6p/2 Bbqxms6dR1vXlG8Bhl1o1Dd5kT/7ft+b6jmTo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; b=Yw22RpDVdEQ7vRsAjy6r8JSu/EuPxcUo6CtzhaoMLvJzeZSgT0LxmrBTPHvBhX17TO aRT5pK2sYPfg9bPgncIla/zmKVwJN0UrdhEUL8ZZDUynehaJvVWwXKz15cp6FtJsYd6E bUBI46ZFQBPYaLXxF1i4Dt1WbarPDNr7M+Wuo=
Received: by 10.220.85.203 with SMTP id p11mr156977vcl.274.1299245162022; Fri, 04 Mar 2011 05:26:02 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id h21sm923286vcr.8.2011.03.04.05.25.59 (version=SSLv3 cipher=OTHER); Fri, 04 Mar 2011 05:26:01 -0800 (PST)
Message-ID: <CB3AECBBB94A4ECFA2CF9A89C2E26D62@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <trejrco@gmail.com>
References: <AANLkTinuhtXfj1enR9m0U56qCUgRi3c6DiUowoDY-yjF@mail.gmail.com>
In-Reply-To: <AANLkTinuhtXfj1enR9m0U56qCUgRi3c6DiUowoDY-yjF@mail.gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Date: Fri, 4 Mar 2011 21:25:50 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01CBDAB2.BC08FA90"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 13:24:54 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_0025_01CBDAB2.BC08FA90
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

From: TJ=20
Sent: Thursday, March 03, 2011 9:59 AM
To: huabing yu=20
Subject: Re: draft-yhb-6man-ra-privacy-flag-01


Questions:
* 2.3(3.1) - Concern over an attacker "forcing" a host to drop it's =
active privacy addresses?

Reply: It is possible, but the threat is not so serious, so don't worry =
about it. If the privacy address is deprecated, the host can use=20

the other IPv6 addresses, for example, the EUI-64 IPv6 address.


* What about OSes that only do randomized IIDs by default ... Should =
they switch to EUI64 if this bit is set?=20

Reply: No. This flag is only valid to the privacy addresses.


* What if this flag disagrees with  manual configuration / GPO?

Reply: Is your meaning the flag deprecated manually configured IPv6 =
addresses? I don't understand your meaning.

Please describe it in detail.





------=_NextPart_000_0025_01CBDAB2.BC08FA90
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><B>From:</B> <A title=3Dtrejrco@gmail.com=20
href=3D"mailto:trejrco@gmail.com">TJ</A> </DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV><B>Sent:</B> Thursday, March 03, 2011 9:59 AM</DIV>
<DIV><B>To:</B> <A title=3Dyhb810501@gmail.com=20
href=3D"mailto:yhb810501@gmail.com">huabing yu</A> </DIV>
<DIV><B>Subject:</B> Re: =
draft-yhb-6man-ra-privacy-flag-01</DIV></DIV></DIV>
<DIV><BR></DIV>
<P>Questions:<BR>* 2.3(3.1) - Concern over an attacker "forcing" a host =
to drop=20
it's active privacy addresses?</P>
<P><FONT face=3DCalibri>Reply: It is possible, but the threat is not so =
serious,=20
so don't worry about it. If the privacy address is deprecated, the host =
can use=20
</FONT></P>
<P><FONT face=3DCalibri>the other IPv6 addresses, for example, the =
EUI-64 IPv6=20
address.</FONT></P>
<P><FONT face=3DCalibri></FONT><FONT face=3DCalibri></FONT><BR>* What =
about OSes=20
that only do randomized IIDs by default ... Should they switch to EUI64 =
if this=20
bit is set? </P>
<P><FONT face=3DCalibri>Reply: No.&nbsp;This flag is only valid to the =
privacy=20
addresses.</FONT></P>
<P><FONT face=3DCalibri></FONT><BR>* What if this flag disagrees =
with&nbsp; manual=20
configuration / GPO?</P>
<P>Reply: Is your meaning the flag deprecated manually configured IPv6=20
addresses? I don't understand your meaning.</P>
<P>Please describe it in detail.</P>
<P>&nbsp;</P>
<P><FONT face=3DCalibri></FONT>&nbsp;</P></BODY></HTML>

------=_NextPart_000_0025_01CBDAB2.BC08FA90--


From rja.lists@gmail.com  Fri Mar  4 07:32:33 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8C5A3A6906 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:32:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.966
X-Spam-Level: 
X-Spam-Status: No, score=-2.966 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzKLA9FQ10Kh for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:32:32 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id A07753A6893 for <ipv6@ietf.org>; Fri,  4 Mar 2011 07:32:32 -0800 (PST)
Received: by vxg33 with SMTP id 33so2420497vxg.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 07:33:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=LmRchumLzd9pCBw8JvOeE+0oYeINTRfMiJFHZ1ehJ88=; b=XHxZdxx4iopslVeK1FVYM3o27zuRT96Pu5pk+zt2szpI7UxdVNu0SJhqbEojez9Du7 C8DEAxNGkCaGWufZfG/8mrwN4U0Cz36+u74zRAt0RYU9EUNApPDdQHAcndfH0DQsTCXH zqmkPnrDnx1/ljAr6KkFi7J00quyuvMudQTPw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=R4oa+QVphENeSN2EvUqtU40GH7n0HhjjnTByag2owZi4mnRkpS+oeHFnS0Qa6RuuBz ddyRNTBg4i+c4K2wYnPkrEhZbfsTRSLgseCi3fM73RFFZFbXTt+zqbBmrC21USsPs9nI zLNlgqa5sBjwO47W6iEw8rrFil5rgjC+7i8vs=
Received: by 10.52.93.19 with SMTP id cq19mr1072899vdb.294.1299252778996; Fri, 04 Mar 2011 07:32:58 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id v7sm663981vch.11.2011.03.04.07.32.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2011 07:32:58 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: RE: draft-yhb-6man-ra-privacy-flag-01
Date: Fri, 4 Mar 2011 10:32:56 -0500
Message-Id: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 15:32:33 -0000

Some of my clients operate pretty large enterprise networks.
Within those networks, they want to avoid using the so-called
"privacy IPv6 addresses" because of requirements (e.g. the US
HIPAA law) to be able to audit their network, including 
auditing precisely which devices are present.

IPv6 SLAAC works fine for this, provided that the so-called
IPv6 privacy addresses are not used.  DHCPv6 also could work, 
but has substantial deployment costs, including recurring 
operational costs, making it a visibly more expensive
deployment approach than SLAAC.

So at least some of my enterprise network clients would be
very interested in seeing a SLAAC flag be created to inform
end systems that the so-called IPv6 privacy addresses 
are NOT to be used with a given routing-prefix advertised
via IPv6 RA messages.

So I think it would be valuable for the WG to explore 
the ideas of this I-D.  The document itself is clearly
not yet mature, however.

1) The "Introduction" of this I-D needs additional editorial 
   work to clarify the broader range of reasons (some examples
   are provided above) why this flag might be useful within
   some IPv6 deployments.  

2A) The "Security Considerations" needs to include a thorough 
   and serious discussion of the differences in user privacy 
   expectations between corporate/enterprise network deployments 
   and home/residential network deployments.  

2B) Within home/residential deployments, use of privacy 
   addressing ought NOT be disabled operationally because there 
   is a reasonable expectation of privacy when a user is on 
   his/her home/residential network.  This advice needs to be 
   clearly documented within this I-D in the Security Considerations 
   section.

One last thing.  A number of my clients have a very crisp perception
that the ongoing IETF IPv6 WG activity to add/change specifications 
means that "IPv6 is NOT yet ready to deploy operationally".   

I think this perception is pretty widespread.  Reducing the rate
of change/addition to the IPv6 specification set generally would be
helpful to encouraging IPv6 deployment.  I'm not suggesting zero
changes/additions, but instead suggesting that the WG carefully
consider whether a proposed change/addition is really useful and
whether it needs to be undertaken now/soon as part of considering 
each proposed change/addition to the IPv6 specifications.  
A lower rate of change/addition will tend to speed IPv6 deployment,
in my estimation.

Yours,

Ran



From rja.lists@gmail.com  Fri Mar  4 07:40:55 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3D9E3A6893 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.441
X-Spam-Level: 
X-Spam-Status: No, score=-3.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Y1ocDYYjpP5 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:40:55 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D2B4D3A6906 for <ipv6@ietf.org>; Fri,  4 Mar 2011 07:40:54 -0800 (PST)
Received: by vws6 with SMTP id 6so2390522vws.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 07:42:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=Ifayds6xsA/b/OMkJG+fA5Lw3qvilSyLthVKuwq2ySE=; b=iL6tZ7U6rYvQCU6+r0WPLHE3XcQrGkgaCQCLcH3co7TrtaJhXOBMgKE//046NWEMzD FegcQKq4lrNfyw+pRMAS4UiSCmy+XkUmRW2RmeAAzZuUud3sVrNceXttlnU5S7lN4DGZ 3UW+wZQY1KOK1Lss7G3bVLH4lcw5IqagcmGUs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=HVIj/fG8Y1gGm5ilCMj4eOCqgdHHkQIjNEAZc18pNNa9Ri8vb13sVBe/B7n/UQA9lb zS+trpuH82tS7MPgjRG0z56UvK/eSAo1yv2AiFM7sLsBLdJBhg67Z2h/cQN7mx76LSFJ 89KTVoFwY6gWljn7P6IiAQ/DK+qmxT/qyMVv8=
Received: by 10.52.72.67 with SMTP id b3mr1150126vdv.116.1299253323893; Fri, 04 Mar 2011 07:42:03 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id bc20sm500313vdb.33.2011.03.04.07.42.02 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2011 07:42:03 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: draft-yhb-6man-slaac-improvement-00
Date: Fri, 4 Mar 2011 10:42:01 -0500
Message-Id: <B5FDFFF0-4AAD-4F70-BF06-B6C8FF28BCA0@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 15:40:56 -0000

Much much Earlier, TJ wrote:
> To be (perhaps overly) blunt: IMHO the changes proposed 
> in this draft create unneeded confusion, solve a problem 
> that is either non-existent or is readily solved in other 
> ways and can create functional problems / detriments to 
> actual deployment.  

+1


Much Earlier, Brian Carpenter wrote:
> Since the IETF sets Internet standards, we can write exactly 
> what we want to. IETF standards are voluntary, so sites have 
> the right to ignore them too. However, if they do that,
> they will not be able to interoperate with the Internet.

+1


Earlier, Doug Barton wrote:
> SLAAC was not designed as a general-purpose mechanism, 
> and should not be modified (further) to be so.

+1


More recently, Mark Andrews wrote:
> I don't think this is something that needs to be solved
> as it is a non problem.

+1


There seems to be pretty broad agreement on this list that
this I-D is not an improvement, is not solving an actual problem, 
and that pursuing this draft is likely to create significant
new operational problems that are best avoided.

Yours,

Ran



From jhw@apple.com  Fri Mar  4 07:54:15 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C014C3A6946 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-fNXQ267osh for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 07:54:15 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id F3AF13A69C0 for <ipv6@ietf.org>; Fri,  4 Mar 2011 07:54:14 -0800 (PST)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id 03286D678EC5 for <ipv6@ietf.org>; Fri,  4 Mar 2011 07:55:24 -0800 (PST)
X-AuditID: 11807136-b7c6bae000004a34-0a-4d710b6b23aa
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay15.apple.com (Apple SCV relay) with SMTP id 46.23.18996.B6B017D4; Fri,  4 Mar 2011 07:55:23 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.20] ([75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHJ009CEIWBVV00@elliott.apple.com> for ipv6@ietf.org; Fri, 04 Mar 2011 07:55:23 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: james woodyatt <jhw@apple.com>
In-reply-to: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com>
Date: Fri, 04 Mar 2011 07:55:23 -0800
Message-id: <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com>
To: 6MAN <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1204)
X-Brightmail-Tracker: AAAAAA==
Cc: RJ Atkinson <rja.lists@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 15:54:15 -0000

On Mar 4, 2011, at 7:32 AM, RJ Atkinson wrote:
> 
> [...] but instead suggesting that the WG carefully consider whether a proposed change/addition is really useful and whether it needs to be undertaken now/soon as part of considering each proposed change/addition to the IPv6 specifications. [...]


And on that note, let me hereby register my opposition to the adoption of this draft as a working group item on the grounds that this change is not sufficiently useful to justify such a late change to the core protocol specification.  Enterprise networks should expect to pay for the proper costs of auditing, and if that includes the cost of requiring every host to use DHCPv6 to obtain both temporary and persistent addresses, then that's an adequate solution to the auditing problem without requiring any change to the core specifications.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From sander@steffann.nl  Fri Mar  4 08:01:12 2011
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 922E63A6802 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 08:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.071
X-Spam-Level: 
X-Spam-Status: No, score=0.071 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0WF3LZq+xC1 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 08:01:12 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by core3.amsl.com (Postfix) with ESMTP id 852ED3A68EE for <ipv6@ietf.org>; Fri,  4 Mar 2011 08:01:11 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id DBF922012; Fri,  4 Mar 2011 17:02:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O+f9jlxNhTmn; Fri,  4 Mar 2011 17:02:06 +0100 (CET)
Received: from [172.16.1.92] (unknown [46.144.134.200]) by mail.sintact.nl (Postfix) with ESMTP id 418B02047; Fri,  4 Mar 2011 17:01:16 +0100 (CET)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com>
Date: Fri, 4 Mar 2011 17:01:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com> <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
Cc: RJ Atkinson <rja.lists@gmail.com>, 6MAN <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 16:01:12 -0000

Hi,

> And on that note, let me hereby register my opposition to the adoption =
of this draft as a working group item on the grounds that this change is =
not sufficiently useful to justify such a late change to the core =
protocol specification.  Enterprise networks should expect to pay for =
the proper costs of auditing, and if that includes the cost of requiring =
every host to use DHCPv6 to obtain both temporary and persistent =
addresses, then that's an adequate solution to the auditing problem =
without requiring any change to the core specifications.

+1

And existing hosts/implementations will ignore the new flag anyway, so =
how can an enterprise 'guarantee' that privacy extensions will not be =
used? My feeling is that this I-D will only cause confusion without =
solving the problem.

- Sander


From swmike@swm.pp.se  Fri Mar  4 08:22:55 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E00B3A67B1 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 08:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7HnoTu6PN4LN for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 08:22:52 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 24D713A67A1 for <ipv6@ietf.org>; Fri,  4 Mar 2011 08:22:50 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 17B2B9E; Fri,  4 Mar 2011 17:23:57 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 1565F9A for <ipv6@ietf.org>; Fri,  4 Mar 2011 17:23:57 +0100 (CET)
Date: Fri, 4 Mar 2011 17:23:57 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: 6MAN <ipv6@ietf.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl>
Message-ID: <alpine.DEB.1.10.1103041722150.7942@uplift.swm.pp.se>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com> <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com> <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 16:22:55 -0000

On Fri, 4 Mar 2011, Sander Steffann wrote:

> Hi,
>
>> And on that note, let me hereby register my opposition to the adoption of this draft as a working group item on the grounds that this change is not sufficiently useful to justify such a late change to the core protocol specification.  Enterprise networks should expect to pay for the proper costs of auditing, and if that includes the cost of requiring every host to use DHCPv6 to obtain both temporary and persistent addresses, then that's an adequate solution to the auditing problem without requiring any change to the core specifications.
>
> +1
>
> And existing hosts/implementations will ignore the new flag anyway, so how can an enterprise 'guarantee' that privacy extensions will not be used? My feeling is that this I-D will only cause confusion without solving the problem.

I also agree. Let's not change RA more than is absolutely needed. The 
problem description sounds exactly like what DHCPv6 was designed to solve. 
If you need to track what IPs are used at a given time and by whom, SLAAC 
is not the way to go.

The proposed solution doesn't solve the problem described.

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

From rja.lists@gmail.com  Fri Mar  4 09:20:52 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5E2DE3A6841 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 09:20:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.451
X-Spam-Level: 
X-Spam-Status: No, score=-3.451 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TgDqTpRgyx7q for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 09:20:51 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 603773A683C for <ipv6@ietf.org>; Fri,  4 Mar 2011 09:20:51 -0800 (PST)
Received: by qyk29 with SMTP id 29so337927qyk.10 for <ipv6@ietf.org>; Fri, 04 Mar 2011 09:22:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=xBQhZPkps7TA0RPJ9RY3lZAWl+V2/I9aq19SqCCLi/Y=; b=MxH3VGFYYRQweNyMo46EG/gaHWxUjaNhJieXnlzIfLc71cMFkBrwXYPusGUwBj3q5M 77lTbZRMxekzfJ2/XWN4kqWxLN1uMkF96gJhD+4GaEjXDf+dP8UN3T2Hc9cUArFIDOxc XA3M80F44cLTJYJkA99W1I3KXoOqxllhvVhjo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=igZOshTBvSOIs4vzTIpWHMRSpRrpG3asxTIxYP2sBKZ6R/LyHX4ty3MGyhc31fyoXw KqZqMula/Agu7b8XiNyVQSGx40T/apUoedLIMw1vF2Wfw9NfCyuv2BxvDvv2zroN65Sg /p1R9pnqxkBtCt8FsxmkfzojWP7viAGxDmkFk=
Received: by 10.224.127.35 with SMTP id e35mr771053qas.389.1299259320189; Fri, 04 Mar 2011 09:22:00 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id g32sm1826915qck.22.2011.03.04.09.21.58 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2011 09:21:59 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl>
Date: Fri, 4 Mar 2011 12:21:57 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <72C2685B-ABAE-46E9-80C5-0A08B7957C62@gmail.com>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com> <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com> <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 17:20:52 -0000

On 04  Mar 2011, at 11:01 , Sander Steffann wrote:
> And existing hosts/implementations will ignore the new flag anyway,
> so how can an enterprise 'guarantee' that privacy extensions
> will not be used?

As with any proposed change/addition to existing IPv6 specs,
implementation support appears over time.  

While any proposed change/addition is not available universally 
on Day 1, it is also likely that an adopted change/addition
will appear in various products over time.

> My feeling is that this I-D will only cause confusion
> without solving the problem.

Noted. 

Of course, that argument (i.e. not all implementations 
will support feature X on day 1) equally can be applied 
to all proposed IPv6 specification additions/changes.

So my takeaway from your note (and jhw's note :-) is that 
you all are among the folks who would like to see IPv6 specs 
freeze more than they have so far.

:-)

Cheers,

Ran


From rja.lists@gmail.com  Fri Mar  4 09:40:39 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C0453A6946 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 09:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.46
X-Spam-Level: 
X-Spam-Status: No, score=-3.46 tagged_above=-999 required=5 tests=[AWL=0.139,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXEC13ge-4SJ for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 09:40:38 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 062523A67F1 for <ipv6@ietf.org>; Fri,  4 Mar 2011 09:40:37 -0800 (PST)
Received: by yic13 with SMTP id 13so1015168yic.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 09:41:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=LCJJBxbCAD9Qxzj4y2Q0PNATsoX2vOu6vfnokf+hBsw=; b=Bjnt6NUg9NwHJVD4ZyIshhs3T/NyPS4y5nvFQlfNopP6/Re/Jok0NeZJ+i2y1yjMKc tS7MZJRAVJ+WXEEYwX81Hnz2qxUebG7cC/a/UewHBFp6KOcUMGaZ+cYhV5FRo21mLEkn I5f+ERPZ6BISZprRiitKc0KN5sH1osKthldA0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=mxy/P24VF0QYPiMrQv0uwexcxb+0lJU3nnfN5u8mPRTBKY9H+nmyJI13Z3zwSVhewf dytTHpKuQV3/StrM7gbCytUm8tyWG26+/Qmg0njtLjq1vp5f+Buc3iEd0GgYE3HnEvmO ukocgzQkDOtBHSrkQ5Jz7NK9j5Vx8LK7b6vqM=
Received: by 10.90.147.18 with SMTP id u18mr1236472agd.95.1299260507075; Fri, 04 Mar 2011 09:41:47 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id c39sm3187422anc.7.2011.03.04.09.41.45 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2011 09:41:46 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Date: Fri, 4 Mar 2011 12:41:44 -0500
Message-Id: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 17:40:39 -0000

Mikael Abrahamsson wrote:
% The proposed solution doesn't solve the problem described.

Hmm.

IPv6 addresses formed using any MAC address belonging to a given 
node (i.e. in modified EUI-64 form per the RFCs) does entirely 
meet the user audit needs for the users I am aware of (and 
previously summarised).  

One might or might not like the proposal, but the above quote 
from Mikael is NOT accurate, at least for the user deployment
audit needs that I am aware of.

Yours,

Ran





From swmike@swm.pp.se  Fri Mar  4 10:09:29 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E77213A6A06 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlOiJi5+Rrca for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:09:29 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id D96FA3A6946 for <ipv6@ietf.org>; Fri,  4 Mar 2011 10:09:28 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 01FEA9C; Fri,  4 Mar 2011 19:10:36 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id F3BE29A; Fri,  4 Mar 2011 19:10:36 +0100 (CET)
Date: Fri, 4 Mar 2011 19:10:36 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com>
Message-ID: <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 18:09:30 -0000

On Fri, 4 Mar 2011, RJ Atkinson wrote:

> IPv6 addresses formed using any MAC address belonging to a given node 
> (i.e. in modified EUI-64 form per the RFCs) does entirely meet the user 
> audit needs for the users I am aware of (and previously summarised).

And how do you know the host didn't make up a new address because it 
needed to for some reason? It doesn't have to be privacy extension. SLAAC 
leaves it up to the host to do what it want, it can take any address not 
currently in use by someone else.

> One might or might not like the proposal, but the above quote
> from Mikael is NOT accurate, at least for the user deployment
> audit needs that I am aware of.

SLAAC is by definion host-controlled. You use the term "audit" in a way I 
don't really understand (though I am not a native english speaker so I 
could very well be wrong).

If you want to be sure who did what when, you need centrally controlled 
IPv6 address hand-out (DHCPv6 is the only one I am aware of for IPv6) plus 
something that makes sure user can't source any other traffic, such as the 
SAVI-WG functionality IP/MAC address verification schemes.

Please do not put more functionality into RA than what is absolutely 
needed. If you need to know what host had what IP address at what time, 
disallow SLAAC and run DHCPv6.

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

From ietfc@btconnect.com  Fri Mar  4 10:15:03 2011
Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 599CF3A6982 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:15:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUmrAJ3D2xcb for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:15:02 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id 258033A6838 for <ipv6@ietf.org>; Fri,  4 Mar 2011 10:15:01 -0800 (PST)
Received: from host217-44-145-106.range217-44.btcentralplus.com (HELO pc6) ([217.44.145.106]) by c2beaomr07.btconnect.com with SMTP id BZN05202; Fri, 04 Mar 2011 18:16:07 +0000 (GMT)
Message-ID: <001d01cbda8f$37cf44a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>, "6MAN" <ipv6@ietf.org>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com><C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com><B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl> <alpine.DEB.1.10.1103041722150.7942@uplift.swm.pp.se>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Date: Fri, 4 Mar 2011 18:11:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D712C66.01C5, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4D712C68.0036,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 18:15:03 -0000

----- Original Message -----
From: "Mikael Abrahamsson" <swmike@swm.pp.se>
To: "6MAN" <ipv6@ietf.org>
Sent: Friday, March 04, 2011 5:23 PM

> On Fri, 4 Mar 2011, Sander Steffann wrote:
>
> > Hi,
> >
> >> And on that note, let me hereby register my opposition to the adoption of
this draft as a working group item on the grounds that this change is not
sufficiently useful to justify such a late change to the core protocol
specification.  Enterprise networks should expect to pay for the proper costs of
auditing, and if that includes the cost of requiring every host to use DHCPv6 to
obtain both temporary and persistent addresses, then that's an adequate solution
to the auditing problem without requiring any change to the core specifications.
> >
> > +1
> >
> > And existing hosts/implementations will ignore the new flag anyway, so how
can an enterprise 'guarantee' that privacy extensions will not be used? My
feeling is that this I-D will only cause confusion without solving the problem.
>
> I also agree. Let's not change RA more than is absolutely needed. The
> problem description sounds exactly like what DHCPv6 was designed to solve.
> If you need to track what IPs are used at a given time and by whom, SLAAC
> is not the way to go.

I agree.

After how ever many years it is, we really ought to be rolling something out
be it ever so slightly imperfect.

Who knows, we might need to use it in anger in a large scale deployment:-)

Tom Petch

>
> The proposed solution doesn't solve the problem described.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From rja.lists@gmail.com  Fri Mar  4 10:54:44 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB5C63A69EC for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:54:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.968
X-Spam-Level: 
X-Spam-Status: No, score=-2.968 tagged_above=-999 required=5 tests=[AWL=-0.369, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bamxOZNaL11x for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 10:54:43 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id B2CE93A687E for <ipv6@ietf.org>; Fri,  4 Mar 2011 10:54:43 -0800 (PST)
Received: by vxg33 with SMTP id 33so2627917vxg.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 10:55:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=c4NvrLapwBIfS86mCu4K0k5RmWLFRUGk9QjpXUf7GV0=; b=IN7JXMPqfM2PTdNSNtGZBweeB8/yfbdXoYGZKuvFnknqCkAV3AcK202OkrZO6DFS2H ddMCOR0TylNXC2Cw2TdfIwTTqD3p5eA66BKq7f2X/A58XE2Xnfxrg/HgNHkUtRwemMnt rEDcBhRepOYF92xKghKtoWJg5vt1uDtvuTkso=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=YxfDhGRA98L3wjow6hKajaIYPf5YyUukZu4bTijhcHk92XISc7aUUlCI5jnit3bgaa GSy0VMjbhPGY5oM/aT9biBmN7Efjx3c935+apQcbqzcX2D/zNENgNZI4u4ust6RIN+TF O8UZ3D9KHrseBtnI9vmruU2g+1WR7EcBHkDMY=
Received: by 10.52.0.74 with SMTP id 10mr1530029vdc.18.1299264950772; Fri, 04 Mar 2011 10:55:50 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id cj13sm548753vdb.12.2011.03.04.10.55.49 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2011 10:55:50 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se>
Date: Fri, 4 Mar 2011 13:55:48 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 18:54:44 -0000

On 04  Mar 2011, at 13:10 , Mikael Abrahamsson wrote:
> SLAAC is by definion host-controlled.  

Existing RA flags control whether SLAAC is allowed
or DHCP is required, so this proposal is not a significant 
architectural change either to IPv6 or to RA flag use.

Any proposal to the WG might or might not meet one's 
personal definition of "sufficient need to justify 
changing/adding specs" -- I gather you think it does not 
meet your definition of sufficient need (jhw and some others 
seem to have a similar view :-).

> You use the term "audit" in a way I don't really understand 

At least for these users, "audit" has a meaning quite similar
to the ordinary business usage (e.g. when a CPA or Chartered Accountant 
audits a public firm's financial records).  

In many countries, public firms aren't required to have 
flawless financial records, merely "good enough" (reportedly
this is often expressed as a sufficient "confidence interval").

> If you want to be sure who did what when, you need centrally
> controlled IPv6 address hand-out plus something that makes sure
> user can't source any other traffic, such as the SAVI-WG
> functionality IP/MAC address verification schemes.

My apologies if I was unclear.  
This is NOT access-control, but instead merely audit.  

As with audits of financial records, perfection is not required,
but a certain confidence interval IS desired/required/needed.

As near as I can  tell, different user organisations target 
different confidence intervals.  

If a significant number of systems use the "privacy-mode" addressing, 
that confidence interval is not achievable.  If a tiny number use 
that mode, a large deployment reportedly can meet the required 
confidence interval.

Again, this is audit, not access control, and absolute perfection
is not a requirement.

> If you need to know what host had what IP address at what time,
> disallow SLAAC and run DHCPv6.


I'm told that some users already are using implementation-specific
configuration mechanisms (e.g. apparently a MS-Windows "Registry"
setting) that allow SLAAC, but disallow the privacy extension.

I'm further told that when configured to disable "privacy-mode",
such hosts then create the EUI-64 based on some MAC address 
in the host.  

I'm told that outcome is quite sufficient for audit purposes, 
but is expensive and tedious to deploy -- primarily because
the configuration is platform-dependent.

This proposal would provide an platform-independent way 
to configure that sort of knob, which knob apparently exists 
now within an interesting number of deployed end systems. 

I hope the situation is more clear now.  Thanks for your
follow-up questions and comments.

Cheers,

Ran


From swmike@swm.pp.se  Fri Mar  4 11:14:16 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E601A3A69EC for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 11:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4VpKWltuzlw for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 11:14:11 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 0B7D23A6878 for <ipv6@ietf.org>; Fri,  4 Mar 2011 11:14:09 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D826D9E; Fri,  4 Mar 2011 20:15:17 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D762B9A; Fri,  4 Mar 2011 20:15:17 +0100 (CET)
Date: Fri, 4 Mar 2011 20:15:17 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
Message-ID: <alpine.DEB.1.10.1103042009000.7942@uplift.swm.pp.se>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 19:14:17 -0000

On Fri, 4 Mar 2011, RJ Atkinson wrote:

> I hope the situation is more clear now.  Thanks for your follow-up 
> questions and comments.

Well, I still oppose it. Either we have SLAAC and then the host is allowed 
to choose any address it sees fit, or we don't.

If an organisation wants to disallow privacy extensions and still use 
SLAAC (and trust the host to just allocate one tracable IPv6 address and 
nothing else), then I hope they have sufficient control over the host and 
thus can afford to do the registry setting to disallow privacy extensions.

I would have more understanding of your case if the proposal was to 
implement a flag which said "only use a single EUI64 based IPv6-address 
and nothing else when doing SLAAC" which by definition would do what you 
want, but I still don't like this.

I'd much rather make sure vendors implement proper support for DHCPv6 
(stateless and stateful) than to fiddle with RAs where the router vendor 
also has to implement this functionality. Let's try to change RA as few 
times as possible, please. Let the routers do forwarding of 
policy-required queries and handle these in a server that is not on the 
local subnet.

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

From kauer@biplane.com.au  Fri Mar  4 14:30:35 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 522C43A691F for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:30:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94wNidhedinS for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:30:32 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 5638F3A6A42 for <ipv6@ietf.org>; Fri,  4 Mar 2011 14:30:31 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PvdX9-0002vA-3g for ipv6@ietf.org; Fri, 04 Mar 2011 17:31:39 -0500
Subject: RE: draft-yhb-6man-ra-privacy-flag-01
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-WidlE4bCFZIbMXjt6Bde"
Date: Sat, 05 Mar 2011 09:35:44 +1100
Message-ID: <1299278144.27837.239.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 22:30:35 -0000

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

On Fri, 2011-03-04 at 10:32 -0500, RJ Atkinson wrote:
> So at least some of my enterprise network clients would be
> very interested in seeing a SLAAC flag be created to inform
> end systems that the so-called IPv6 privacy addresses=20
> are NOT to be used with a given routing-prefix advertised
> via IPv6 RA messages.

Even if the router issued such a flag, any host would still be at
liberty to use any address it liked. The router flags, as I read the
RFCs anyway, are more in the nature of hints. Short of not issuing RAs
at all.

For example, nothing stops me configuring a static address, even though
my router is issuing prefix information - in fact, even if it doesn't
issue any prefix information at all (which is pretty much where IPv4 is
at). And I can still issue a DHCP SOLICIT, even if the router didn't
tell me to (though how far it would get is another story).

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-WidlE4bCFZIbMXjt6Bde
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1xaTkACgkQMAcU7Vc29ocxTwCgldKTnes4hPNip68j48LLxxbz
MDsAn0nlaO1W0eK7asvBml5PTsE1WiN9
=T1s3
-----END PGP SIGNATURE-----

--=-WidlE4bCFZIbMXjt6Bde--


From kauer@biplane.com.au  Fri Mar  4 14:33:39 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D410D3A692D for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tvb+7nFRGDfs for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:33:38 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 9A8613A68AB for <ipv6@ietf.org>; Fri,  4 Mar 2011 14:33:38 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PvdaA-0003GP-ST for ipv6@ietf.org; Fri, 04 Mar 2011 17:34:47 -0500
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <alpine.DEB.1.10.1103041722150.7942@uplift.swm.pp.se>
References: <D34E4E85-87EB-4A0E-A98F-11E252E54C28@gmail.com> <C4AC6E6A-72B2-4354-BD54-FC9B74795A37@apple.com> <B29751BB-DA5D-45D4-86B4-EEAB38DAA8D3@steffann.nl> <alpine.DEB.1.10.1103041722150.7942@uplift.swm.pp.se>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-SfitdverK3pqM5A/WAJJ"
Date: Sat, 05 Mar 2011 09:38:49 +1100
Message-ID: <1299278329.27837.243.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 22:33:40 -0000

--=-SfitdverK3pqM5A/WAJJ
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2011-03-04 at 17:23 +0100, Mikael Abrahamsson wrote:
> I also agree. Let's not change RA more than is absolutely needed. The=20
> problem description sounds exactly like what DHCPv6 was designed to solve=
.=20
> If you need to track what IPs are used at a given time and by whom, SLAAC=
=20
> is not the way to go.

Well, if SLAAC is using the MAC addresses, it's pretty useful. But
neither SLAAC nor DHCP *really* solve it. Any host can take any address
in the right prefix and (modulo snooping and other switch/router
features) be active in the network. That is, both SLAAC and DHCP really
only allow "tracking" of well-behaved hosts.

> The proposed solution doesn't solve the problem described.

No, it doesn't.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-SfitdverK3pqM5A/WAJJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1xafkACgkQMAcU7Vc29oeppQCeOxQ3nEWrNzhQph25InTn8KP9
kk0AoMs0ZleKaORdJo1olCsAbiVXkzUe
=IxYV
-----END PGP SIGNATURE-----

--=-SfitdverK3pqM5A/WAJJ--


From kauer@biplane.com.au  Fri Mar  4 14:44:34 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB9D93A68A9 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AgrD5QLBgoar for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 14:44:33 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 73FDB3A6812 for <ipv6@ietf.org>; Fri,  4 Mar 2011 14:44:33 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1Pvdkk-0004sf-0z for ipv6@ietf.org; Fri, 04 Mar 2011 17:45:42 -0500
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>
In-Reply-To: <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-QIG8B/oE164bSsMZzDGY"
Date: Sat, 05 Mar 2011 09:49:47 +1100
Message-ID: <1299278987.27837.255.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 22:44:35 -0000

--=-QIG8B/oE164bSsMZzDGY
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2011-03-04 at 13:55 -0500, RJ Atkinson wrote:
> Existing RA flags control whether SLAAC is allowed
> or DHCP is required

I don't think they do. They inform the host about whether SLAAC *should*
be done, or whether DHCP *could* be done, but do not *control* the host
in any way.

> If a significant number of systems use the "privacy-mode" addressing,=20
> that confidence interval is not achievable.

In my ignorance I may be being over-confident, but it seems to me that
some very basic NDP snooping in routers would enable logging of every
active address - when it became active and the last time it was seen,
along with layer-2 info for the address. Such features don't exist yet,
of course... er, do they?

> I'm told that some users already are using implementation-specific
> configuration mechanisms (e.g. apparently a MS-Windows "Registry"
> setting) that allow SLAAC, but disallow the privacy extension.

If that setting is on the host, it's toast in the hands of a Bad Guy.
But using your sense of "audit" I guess that's not too bad.

> This proposal would provide an platform-independent way=20
> to configure that sort of knob, which knob apparently exists=20
> now within an interesting number of deployed end systems.=20

Again - a knob only useful for well-behaved systems hosts.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-QIG8B/oE164bSsMZzDGY
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1xbIoACgkQMAcU7Vc29oegAgCfQfZstFI8b/WTA9i2LR4vhFIR
87UAoJeAv2eOiEWNZjxpDdyFrzdUZ12+
=oj/3
-----END PGP SIGNATURE-----

--=-QIG8B/oE164bSsMZzDGY--


From jhw@apple.com  Fri Mar  4 15:02:00 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA0203A68AC for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 15:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.572
X-Spam-Level: 
X-Spam-Status: No, score=-106.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxoL-mN5q5HM for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 15:02:00 -0800 (PST)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 35E6D3A6812 for <ipv6@ietf.org>; Fri,  4 Mar 2011 15:02:00 -0800 (PST)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 19BC0D435640 for <ipv6@ietf.org>; Fri,  4 Mar 2011 15:03:10 -0800 (PST)
X-AuditID: 11807134-b7c8cae000005108-2b-4d716fade487
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay14.apple.com (Apple SCV relay) with SMTP id 75.9E.20744.DAF617D4; Fri,  4 Mar 2011 15:03:10 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHK003JY2P9JI80@et.apple.com> for ipv6@ietf.org; Fri, 04 Mar 2011 15:03:09 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: james woodyatt <jhw@apple.com>
In-reply-to: <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
Date: Fri, 04 Mar 2011 15:03:09 -0800
Message-id: <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1203)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 23:02:01 -0000

On Mar 4, 2011, at 10:55 AM, RJ Atkinson wrote:
> 
> As with audits of financial records, perfection is not required,
> but a certain confidence interval IS desired/required/needed.


It seems to me that proper accounting of which hosts are using what IPv6 addresses is probably better achieved by enhancing routers with the capability to journal their neighbor discovery cache insertions to a secure repository for offline review.  That combined with authorization logs from EAPOL ought to provide sufficient confidence for most civilian audits.  Am I missing something?


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From james.cutler@consultant.com  Fri Mar  4 15:13:50 2011
Return-Path: <james.cutler@consultant.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 395233A6921 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 15:13:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level: 
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FAKE_HELO_MAIL_COM_DOM=3.199]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKog3BrdL0CE for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 15:13:49 -0800 (PST)
Received: from mailout-us.mail.com (mailout-us.mail.com [74.208.122.35]) by core3.amsl.com (Postfix) with SMTP id 4538C3A6850 for <ipv6@ietf.org>; Fri,  4 Mar 2011 15:13:49 -0800 (PST)
Received: (qmail invoked by alias); 04 Mar 2011 23:14:55 -0000
Received: from adsl-99-131-3-236.dsl.sfldmi.sbcglobal.net (EHLO minijim.local) [99.131.3.236] by mail.gmx.com (mp-us009) with SMTP; 04 Mar 2011 18:14:55 -0500
X-Authenticated: #76096295
X-Provags-ID: V01U2FsdGVkX1924FkwWpR2GMBYuN9mUUPXFAmAu9T5F07+9/fcve /Tn+4VRU3y9NW9
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cutler James R <james.cutler@consultant.com>
In-Reply-To: <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com>
Date: Fri, 4 Mar 2011 18:14:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <77FCDA0D-6AC2-482D-9F38-2267333BC147@consultant.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com> <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 Mar 2011 23:13:50 -0000

On Mar 4, 2011, at 6:03 PM, james woodyatt wrote:

> On Mar 4, 2011, at 10:55 AM, RJ Atkinson wrote:
>>=20
>> As with audits of financial records, perfection is not required,
>> but a certain confidence interval IS desired/required/needed.
>=20
>=20
> It seems to me that proper accounting of which hosts are using what =
IPv6 addresses is probably better achieved by enhancing routers with the =
capability to journal their neighbor discovery cache insertions to a =
secure repository for offline review.  That combined with authorization =
logs from EAPOL ought to provide sufficient confidence for most civilian =
audits.  Am I missing something?
>=20
>=20
> --james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

Playing my favorite refrain regarding separation of functions and =
powers:

James, you are missing the need for routers to tend to the business of =
routing. =20

Placing the configuration and accounting and audit mechanisms elsewhere =
greatly benefits network performance and separates router software and =
configuration from the non-trivial end system management functions.

If I were responsible for transporting IP packets, I would insist on =
distancing my self from attempts to complicate my life beyond trying to =
keep up with software updates from A, C, HP, J, HP and etc. while =
keeping the network running well.  Tuning BGP should be enough.  No mas!

James R. Cutler
james.cutler@consultant.com





From narten@us.ibm.com  Fri Mar  4 17:29:44 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B167F3A68D4 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 17:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.974
X-Spam-Level: 
X-Spam-Status: No, score=-105.974 tagged_above=-999 required=5 tests=[AWL=0.625, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wg3WqGM6macq for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 17:29:43 -0800 (PST)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by core3.amsl.com (Postfix) with ESMTP id CC3AD3A6875 for <ipv6@ietf.org>; Fri,  4 Mar 2011 17:29:43 -0800 (PST)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e33.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p251OHo2022483 for <ipv6@ietf.org>; Fri, 4 Mar 2011 18:24:17 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p251UiLa118624 for <ipv6@ietf.org>; Fri, 4 Mar 2011 18:30:44 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p251UhrO013627 for <ipv6@ietf.org>; Fri, 4 Mar 2011 18:30:44 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-76-152-128.mts.ibm.com [9.76.152.128]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p251UgNn013567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Mar 2011 18:30:43 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p251UeNE025668; Fri, 4 Mar 2011 18:30:41 -0700
Message-Id: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-reply-to: <4D6EC041.4070304@gmail.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com>
Comments: In-reply-to Brian E Carpenter <brian.e.carpenter@gmail.com> message dated "Thu, 03 Mar 2011 11:10:09 +1300."
Date: Fri, 04 Mar 2011 18:30:40 -0700
From: Thomas Narten <narten@us.ibm.com>
Cc: ipv6@ietf.org, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 01:29:44 -0000

> I stand corrected.

That said, updating the specs to allow a site to use stateless address
autoconfiguration with prefix lengths other than /64 would almost
certainly require updating both specs.

The stateless autoconfig spec would need to be tweaked to convert the
IID produced by the specific link-layer into something that is either
extended (or shrunk) to match the advertised prefix in an RA. And we'd
then have to recover from address collision (duplicate addresses),
which the current spec does not, and generate (and try) new addresses,
sort of like the temporary addresses spec defines.

This could probably all be defined in a way that is an optional
extension to stateless address autoconfig. So it wouldn't necessarily
cause "confusion" or delay getting IPv6 deployed. 

However, I wonder what incentive device implementors would have to
actually implement it. They seem (these days) to only implement the
bare minimal functionality needed to get by. Extensions that might be
useful in only some deployments, don't seem to be high priority.

And, if you have a network in which 80% of the devices implement the
new spec, but 20% do not, how useable would such a feature be in
practice?

And, keep in mind, one can use abitrary prefixes by turning off
stateless address autoconfiguration  and using DHCPv6.

Thomas

From yhb810501@gmail.com  Fri Mar  4 18:05:13 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FB163A68D4 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.108
X-Spam-Level: 
X-Spam-Status: No, score=-3.108 tagged_above=-999 required=5 tests=[AWL=0.490,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJgAMEE2+YIQ for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:05:12 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 510723A68AE for <ipv6@ietf.org>; Fri,  4 Mar 2011 18:05:12 -0800 (PST)
Received: by gyc15 with SMTP id 15so1224109gyc.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 18:06:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:content-transfer-encoding :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; bh=oImI1I3JZRgoJ4zsPHB2UuWnJ1WFSoRT7JiTCWXZX4Q=; b=vQYJvxCR6Eo4m3l9F7T/SsXSyS/TqWZiWcrnl4r/lYwei16x2/KBAJLPu7YMZoWV0C 5XS7BPXUMKhRraasigZTda5lKWZrIyAlB1ANIEHb3mZK0U3XRWMlITT+pNnbSAlLMOBR eL2gq3q1jc4B/P7zxa4ucDN1pjGXECDyuL2EY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:importance:x-mailer:x-mimeole; b=tW6bQyTQkxTaAJ+lgRtxY7Lj4IqluEyqcFKHx7Kf+wWJlhoPoj6hAGHhPEaQLvHy1b OzoIQWrEZ2A6AzpQB1x9C2wMRanOI+6rd/Ok1At+wkAq+DbidruupdDlWo0S4uqIkqCh hxGIac/YOki8aCfSW7ENoODdc2fWw5xp0LMG0=
Received: by 10.101.25.20 with SMTP id c20mr66332anj.179.1299290781920; Fri, 04 Mar 2011 18:06:21 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id u13sm67169ank.3.2011.03.04.18.06.19 (version=SSLv3 cipher=OTHER); Fri, 04 Mar 2011 18:06:21 -0800 (PST)
Message-ID: <213CA4B2061F403C87009985DFE3C63F@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Thomas Narten" <narten@us.ibm.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com>
In-Reply-To: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Date: Sat, 5 Mar 2011 10:06:09 +0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="gb2312"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 02:05:13 -0000

> This could probably all be defined in a way that is an optional
> extension to stateless address autoconfig. So it wouldn't necessarily
> cause "confusion" or delay getting IPv6 deployed. 

I agree.

Yu Hua bing 

From yhb810501@gmail.com  Fri Mar  4 18:32:27 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E84E43A69E7 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:32:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.143
X-Spam-Level: 
X-Spam-Status: No, score=-3.143 tagged_above=-999 required=5 tests=[AWL=0.455,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brIwNPbSyk4p for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:32:27 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id CF59C3A68EA for <ipv6@ietf.org>; Fri,  4 Mar 2011 18:32:26 -0800 (PST)
Received: by gxk5 with SMTP id 5so1200662gxk.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 18:33:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=PGERbKvwuDrxlPc1KNjw4bUu4JTPgGTKegVdIhLy0bM=; b=J+9WbnWTA/+qlF4DGwYAnZT+UNhjq3OhkKYyBQ8+eByBVKBL/cP4YbnP85j+Z7ZzC4 ECe7F7qJhYhyjhsHtEpHIm/DBd9PejhrhfSao9NUmhYV3aXPVZTBsQAs2Dd2eTZT1osd sAPBFMhY6EMdGOgGU3mvcAf3Fse7ft2v+mhTo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=dJNMgpFxKqHoeFbS5hwm4SfedvvcvWy8jdHjmFB/bXBetTI7w3j32L78NW7QaDs5kG D0y+WY+JiLAY+WHkNQkxC26fWswYeIa5CuqncpdT6KMpcC0t4U3gKf/1ZLRKxhEbETcs syN+wTZOqSaK02bB2zoqJYpoZ9mpiNbnLxMOo=
Received: by 10.150.215.7 with SMTP id n7mr1610641ybg.104.1299292416466; Fri, 04 Mar 2011 18:33:36 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id u4sm20711ybe.21.2011.03.04.18.33.34 (version=SSLv3 cipher=OTHER); Fri, 04 Mar 2011 18:33:35 -0800 (PST)
Message-ID: <71337E6093E44BB7A540E31C851695BE@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <ipv6@ietf.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Date: Sat, 5 Mar 2011 10:33:25 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_002B_01CBDB20.C2056140"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 02:32:28 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_002B_01CBDB20.C2056140
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

>RJ Atkinson wrote:
>I'm told that some users already are using implementation-specific
>configuration mechanisms (e.g. apparently a MS-Windows "Registry"
>setting) that allow SLAAC, but disallow the privacy extension.

>I'm further told that when configured to disable "privacy-mode",
>such hosts then create the EUI-64 based on some MAC address=20
>in the host. =20

>I'm told that outcome is quite sufficient for audit purposes,=20
>but is expensive and tedious to deploy -- primarily because
>the configuration is platform-dependent.

>This proposal would provide an platform-independent way=20
>to configure that sort of knob, which knob apparently exists=20
>now within an interesting number of deployed end systems.

I agree.

Yu Hua bing
------=_NextPart_000_002B_01CBDB20.C2056140
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV>&gt;RJ Atkinson wrote:</DIV>
<DIV>&gt;I'm told that some users already are using=20
implementation-specific<BR>&gt;configuration mechanisms (e.g. apparently =
a=20
MS-Windows "Registry"<BR>&gt;setting) that allow SLAAC, but disallow the =
privacy=20
extension.<BR><BR>&gt;I'm further told that when configured to disable=20
"privacy-mode",<BR>&gt;such hosts then create the EUI-64 based on some =
MAC=20
address <BR>&gt;in the host.&nbsp; <BR><BR>&gt;I'm told that outcome is =
quite=20
sufficient for audit purposes, <BR>&gt;but is expensive and tedious to =
deploy --=20
primarily because<BR>&gt;the configuration is=20
platform-dependent.<BR><BR>&gt;This proposal would provide an=20
platform-independent way <BR>&gt;to configure that sort of knob, which =
knob=20
apparently exists <BR>&gt;now within an interesting number of deployed =
end=20
systems.</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>I agree.</FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>Yu Hua bing</FONT></DIV></BODY></HTML>

------=_NextPart_000_002B_01CBDB20.C2056140--


From yhb810501@gmail.com  Fri Mar  4 18:58:28 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D2843A69FC for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.173
X-Spam-Level: 
X-Spam-Status: No, score=-3.173 tagged_above=-999 required=5 tests=[AWL=0.425,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZ0OILqVRW6P for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 18:58:27 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 6C1EA3A69E7 for <ipv6@ietf.org>; Fri,  4 Mar 2011 18:58:27 -0800 (PST)
Received: by gxk5 with SMTP id 5so1206284gxk.31 for <ipv6@ietf.org>; Fri, 04 Mar 2011 18:59:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=kGbfBVQ7KGV5W2AOHbX5oO364L7ApeZtUCGo53kxVz0=; b=Uy6QCnan5BiIucW0+cF2HCoq94hI79jncDwq6eyGp+AQmtQZjk4z46a0i72AhmqqPi Q0syosXDiwyDSgX/ORV2AnKEFk1ejyU9VryNnHSabM9PRJ68LEMVQw1eaXohyH3QNuvI klHDxBmYLh5WOW4xCGo70ugYDbuQ36ElltDK8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=CEKqKz9skwfHvUMIEXQ1bmqT6Fj0MIphMEL13HSVXzL+YR17BAZGVYZXp+JsSKsyq0 FIiOn/iCDGwGo8RVtcZFYfgn7YEToJQ6VZbEVNleeO6oMpM03D2kJBA7wCEKQ3GXqkkJ kR1y9EsPNvurh52ZTrFCJSugHne5jlIcGlxzw=
Received: by 10.151.158.18 with SMTP id k18mr1537259ybo.299.1299293977119; Fri, 04 Mar 2011 18:59:37 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id f2sm95687ybh.7.2011.03.04.18.59.34 (version=SSLv3 cipher=OTHER); Fri, 04 Mar 2011 18:59:36 -0800 (PST)
Message-ID: <F71A62696B354E2D8A892FCAAE467886@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <ipv6@ietf.org>
Subject: Question about the link-local addresses
Date: Sat, 5 Mar 2011 10:59:25 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0045_01CBDB24.6432D670"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 02:58:28 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_0045_01CBDB24.6432D670
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

   >RFC4291
  > Link-Local addresses are for use on a single link.  Link-Local
  > addresses have the following format:

   |   10     |
   |  bits    |         54 bits         |          64 bits           |
   +----------+-------------------------+----------------------------+
   |1111111010|           0             |       interface ID         |
   +----------+-------------------------+----------------------------+

I have a question: If the front 10 bits of one IPv6 address is FE80 and =
the middle 54 bits is not zero, is it link-local address?




------=_NextPart_000_0045_01CBDB24.6432D670
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; &gt;RFC4291</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp;&gt; Link-Local addresses are for =
use on a=20
single link.&nbsp; Link-Local<BR>&nbsp;&nbsp;&gt; addresses have the =
following=20
format:<BR><BR>&nbsp;&nbsp; |&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp; |&nbsp; bits&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 54=20
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 64=20
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;&nbsp;=20
+----------+-------------------------+----------------------------+<BR>&n=
bsp;&nbsp;=20
|1111111010|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface=20
ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;&nbsp;=20
+----------+-------------------------+----------------------------+</FONT=
></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>I have a question: If the front 10 bits of one =
IPv6=20
address is FE80 and the middle 54 bits is not zero, is it link-local=20
address?</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp;</DIV>
<DIV><BR><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_0045_01CBDB24.6432D670--


From yhb810501@gmail.com  Fri Mar  4 19:26:41 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 653593A6916 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 19:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.758
X-Spam-Level: 
X-Spam-Status: No, score=-2.758 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLbSdktDVNnb for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 19:26:40 -0800 (PST)
Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by core3.amsl.com (Postfix) with ESMTP id 70DAA3A6902 for <ipv6@ietf.org>; Fri,  4 Mar 2011 19:26:40 -0800 (PST)
Received: by gwj22 with SMTP id 22so1352122gwj.27 for <ipv6@ietf.org>; Fri, 04 Mar 2011 19:27:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=c61SSmCEVP5B2gvDPAoE5/yMHFFoncX7/AuIhnYlRm0=; b=fddu2M+E3fYpf5q7iLH60wx7vUzDEzoXFko9Gu+a1ocva6wBA7GHiLhE5mPqEczfxF y2FKQu9q5mcQ08UC5yQ+R5YE9Z1bqwGRRnIslb3DBBTDOgDgvzKusYDBuTI8Wbee8rM6 VkjBDxPivocZPL50YxnqB5d+HCpdd1xjRLKY4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=jUNHbfdskH+ZNI7NvrZECuPtpvef/gpl/Eg8nHbAMNXodE1/rim6P/XnZ/ajkVgZjz 0XSa5On8E1taUlrhCxQVBhexZbV198CVI1/YkewNLp/32j4wAFFtt1r5ckn2YsIW5Gh8 gMW/1L0CNOaBHsy3xKcNvDjcj2Am01Y8BD/kQ=
Received: by 10.236.76.194 with SMTP id b42mr2130563yhe.14.1299295670200; Fri, 04 Mar 2011 19:27:50 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id n10sm72318yhb.38.2011.03.04.19.27.47 (version=SSLv3 cipher=OTHER); Fri, 04 Mar 2011 19:27:49 -0800 (PST)
Message-ID: <C9189B001B774CB7ADE879E6BB5C2A92@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <swmike@swm.pp.se>
Subject: RE: draft-yhb-6man-ra-privacy-flag-01
Date: Sat, 5 Mar 2011 11:27:38 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_006E_01CBDB28.553DA830"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 03:26:41 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_006E_01CBDB28.553DA830
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

>Date: Fri, 4 Mar 2011 19:10:36 +0100 (CET)
>From: Mikael Abrahamsson <swmike@swm.pp.se>
>SLAAC is by definion host-controlled. You use the term "audit" in a way =
I=20
>don't really understand (though I am not a native english speaker so I=20
>could very well be wrong).

>If you want to be sure who did what when, you need centrally controlled =

>IPv6 address hand-out (DHCPv6 is the only one I am aware of for IPv6) =
plus=20
>something that makes sure user can't source any other traffic, such as =
the=20
>SAVI-WG functionality IP/MAC address verification schemes.

>Please do not put more functionality into RA than what is absolutely=20
>needed. If you need to know what host had what IP address at what time, =

>disallow SLAAC and run DHCPv6.

No, DHCPv6 can't stop the user configuring a static address.



------=_NextPart_000_006E_01CBDB28.553DA830
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri><FONT face=3D=CB=CE=CC=E5>&gt;Date: Fri, 4 Mar =
2011 19:10:36 +0100=20
(CET)<BR>&gt;From: Mikael Abrahamsson &lt;</FONT><A href=3D""><FONT=20
face=3D=CB=CE=CC=E5>swmike@swm.pp.se</FONT></A><FONT =
face=3D=CB=CE=CC=E5>&gt;</FONT><BR><FONT=20
face=3D=CB=CE=CC=E5>&gt;SLAAC is by definion host-controlled. You use =
the term "audit" in a=20
way I <BR>&gt;don't really understand (though I am not a native english =
speaker=20
so I <BR>&gt;could very well be wrong).<BR><BR>&gt;If you want to be =
sure who=20
did what when, you need centrally controlled <BR>&gt;IPv6 address =
hand-out=20
(DHCPv6 is the only one I am aware of for IPv6) plus <BR>&gt;something =
that=20
makes sure user can't source any other traffic, such as the =
<BR>&gt;SAVI-WG=20
functionality IP/MAC address verification schemes.<BR><BR>&gt;Please do =
not put=20
more functionality into RA than what is absolutely <BR>&gt;needed. If =
you need=20
to know what host had what IP address at what time, <BR>&gt;disallow =
SLAAC and=20
run DHCPv6.</FONT></FONT></DIV>
<DIV><FONT face=3DCalibri><FONT =
face=3D=CB=CE=CC=E5></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri><FONT face=3D=CB=CE=CC=E5>No, DHCPv6 can't =
stop the user configuring=20
a static address.</FONT></DIV>
<DIV><BR><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_006E_01CBDB28.553DA830--


From swmike@swm.pp.se  Fri Mar  4 19:41:56 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEE723A6919 for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 19:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDT5kfOKUuKH for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 19:41:55 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id A2F9A3A68F3 for <ipv6@ietf.org>; Fri,  4 Mar 2011 19:41:54 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BAF239C; Sat,  5 Mar 2011 04:43:02 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BA0CF9A; Sat,  5 Mar 2011 04:43:02 +0100 (CET)
Date: Sat, 5 Mar 2011 04:43:02 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Yu Hua bing <yhb810501@gmail.com>
Subject: RE: draft-yhb-6man-ra-privacy-flag-01
In-Reply-To: <C9189B001B774CB7ADE879E6BB5C2A92@yhbPC>
Message-ID: <alpine.DEB.1.10.1103050441020.7942@uplift.swm.pp.se>
References: <C9189B001B774CB7ADE879E6BB5C2A92@yhbPC>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 03:41:56 -0000

On Sat, 5 Mar 2011, Yu Hua bing wrote:

>> IPv6 address hand-out (DHCPv6 is the only one I am aware of for IPv6) plus
>> something that makes sure user can't source any other traffic, such as the
>> SAVI-WG functionality IP/MAC address verification schemes.
    ---------------------------------------------------------

> No, DHCPv6 can't stop the user configuring a static address.

Together with SAVI functionality it can. Well, they can configure it, but 
they won't be allowed to send packets to the network with it.

<http://tools.ietf.org/wg/savi/>

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

From fred@cisco.com  Fri Mar  4 21:41:18 2011
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 987333A6A4A for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 21:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.42
X-Spam-Level: 
X-Spam-Status: No, score=-110.42 tagged_above=-999 required=5 tests=[AWL=0.178, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68muJ0DX1vyC for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 21:41:17 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 73CF63A6935 for <ipv6@ietf.org>; Fri,  4 Mar 2011 21:41:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3706; q=dns/txt; s=iport; t=1299303747; x=1300513347; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=IrdAQA37WWZfJu3z378zYfBV2uv+G3l8E6KZK9NbeUA=; b=XG2O1nnP6iYCG05cwU4AhOC4PSNKcp1qU7D5FeSUqiSM8y3nns6sxa1c oXUtk8g8MdQmJtGt4wST99CDoCorQ25yczcgBRBi6NfnjMkKyPfc3py25 x/8sNlH8aLaYkJdDFIsERXT86jWy2m81ur1rPm9zhmXpiySigTG+2d0om Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAG9ccU2rR7Ht/2dsb2JhbACebgGHdnSiJZsyhWEEhRyHEw
X-IronPort-AV: E=Sophos;i="4.62,268,1297036800";  d="scan'208,217";a="269954970"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 05 Mar 2011 05:42:13 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p255gDhP024059; Sat, 5 Mar 2011 05:42:13 GMT
Subject: Re: Question about the link-local addresses
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-514-1021469758
From: Fred Baker <fred@cisco.com>
X-Priority: 3
In-Reply-To: <F71A62696B354E2D8A892FCAAE467886@yhbPC>
Date: Fri, 4 Mar 2011 21:42:13 -0800
Message-Id: <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC>
To: Yu Hua bing <yhb810501@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 05:41:18 -0000

--Apple-Mail-514-1021469758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 4, 2011, at 6:59 PM, Yu Hua bing wrote:

>    >RFC4291
>   > Link-Local addresses are for use on a single link.  Link-Local
>   > addresses have the following format:
>=20
>    |   10     |
>    |  bits    |         54 bits         |          64 bits           |
>    +----------+-------------------------+----------------------------+
>    |1111111010|           0             |       interface ID         |
>    +----------+-------------------------+----------------------------+
> =20
> I have a question: If the front 10 bits of one IPv6 address is FE80 =
and the middle 54 bits is not zero, is it link-local address?

http://tools.ietf.org/html/rfc4291#section-2.5.6

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


--Apple-Mail-514-1021469758
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 4, 2011, at 6:59 PM, Yu Hua bing wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px" id="MailContainerBody" leftmargin="0" topmargin="0" canvastabstop="true" name="Compose message area">
<div><font face="Calibri">&nbsp;&nbsp; &gt;RFC4291</font></div>
<div><font face="Calibri">&nbsp;&nbsp;&gt; Link-Local addresses are for use on a 
single link.&nbsp; Link-Local<br>&nbsp;&nbsp;&gt; addresses have the following 
format:<br><br>&nbsp;&nbsp; |&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp; 
|<br>&nbsp;&nbsp; |&nbsp; bits&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 54 
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 64 
bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|<br>&nbsp;&nbsp; 
+----------+-------------------------+----------------------------+<br>&nbsp;&nbsp; 
|1111111010|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface 
ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>&nbsp;&nbsp; 
+----------+-------------------------+----------------------------+</font></div>
<div><font face="Calibri"></font>&nbsp;</div>
<div><font face="Calibri">I have a question: If the front 10 bits of one IPv6 
address is FE80 and the middle 54 bits is not zero, is it link-local 
address?</font></div></div></blockquote><div><br></div><a href="http://tools.ietf.org/html/rfc4291#section-2.5.6">http://tools.ietf.org/html/rfc4291#section-2.5.6</a></div><div><br><blockquote type="cite"><div style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px" id="MailContainerBody" leftmargin="0" topmargin="0" canvastabstop="true" name="Compose message area"><font face="Calibri">
<div><br><br></div></font></div>
--------------------------------------------------------------------<br>IETF IPv6 working group mailing list<br><a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<br>--------------------------------------------------------------------<br></blockquote></div><br></body></html>
--Apple-Mail-514-1021469758--

From kauer@biplane.com.au  Fri Mar  4 22:09:11 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F7F33A695F for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 22:09:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ys4PIYTRjaNr for <ipv6@core3.amsl.com>; Fri,  4 Mar 2011 22:09:10 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 260B13A684D for <ipv6@ietf.org>; Fri,  4 Mar 2011 22:09:09 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1Pvkh0-0006iH-O4 for ipv6@ietf.org; Sat, 05 Mar 2011 01:10:18 -0500
Subject: Re: Question about the link-local addresses
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-6+32rnX+N+CgSjlRc4T9"
Date: Sat, 05 Mar 2011 17:14:22 +1100
Message-ID: <1299305662.27837.368.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 06:09:12 -0000

--=-6+32rnX+N+CgSjlRc4T9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2011-03-04 at 21:42 -0800, Fred Baker wrote:
> > I have a question: If the front 10 bits of one
> > IPv6 address is FE80 and the middle 54 bits is
> > not zero, is it link-local address?
>=20
> http://tools.ietf.org/html/rfc4291#section-2.5.6

That section contains the exact text that Yu Hua bing quoted from the
RFC. I'm not sure that it answers his question. Does it?

My guess is that having any bits set in that 54-bit region makes an
address technically "not a link-local address". On the other hand, I
wonder how many implementations do more than check the first ten bits...

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-6+32rnX+N+CgSjlRc4T9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1x1LgACgkQMAcU7Vc29ocRDwCeOAbBQvhMOvW/RsRvkAkrobHE
M3AAoJn8SoHl+oDN7+cpcRHXEU3dvPsv
=4tbY
-----END PGP SIGNATURE-----

--=-6+32rnX+N+CgSjlRc4T9--


From yhb810501@gmail.com  Sat Mar  5 04:11:19 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E38D3A6778 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 04:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.197
X-Spam-Level: 
X-Spam-Status: No, score=-3.197 tagged_above=-999 required=5 tests=[AWL=0.401,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+KQ1jsW-53U for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 04:11:09 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id ED9E03A69EE for <ipv6@ietf.org>; Sat,  5 Mar 2011 04:11:03 -0800 (PST)
Received: by gxk5 with SMTP id 5so1315975gxk.31 for <ipv6@ietf.org>; Sat, 05 Mar 2011 04:12:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:x-priority:x-msmail-priority :importance:x-mailer:x-mimeole; bh=MzSmsWCMDUUhXmFzLgyoXXAuI8mfuJfQshFtseCjsoc=; b=l2NtUKSewB3ddnvOhJA8Ongwoj+IPDPCc6JNKG1s87u31T+K+xKOupyxJg4PwEcScR pQo+1rfyhGKwsPLgDkLvQuIR+WcqBIyMCg4jusgawCPuSarc8JdyNq++EoYcPPjCP8gg rVXs6zdzYJorqp+dewPQ8TK7Hpa/PlwnlutCw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole; b=WS6ASZ7/c/dTkhpaS1uoFnHvQJeFVZVyKqN4qYbnvqXf0kWsdgqmK3YNvV00zTbngs N8G9wvdkOYnHPrw1wCFTGTaQQtNO5R5EF0HmSrVNJ3uPtEKhOiFgFGnk3po2WJFG12oR wf7rlzpodBHCMMttToneEGs/CxyonRpNpzupg=
Received: by 10.236.192.228 with SMTP id i64mr2636540yhn.83.1299327125663; Sat, 05 Mar 2011 04:12:05 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id u75sm279432yhn.30.2011.03.05.04.12.02 (version=SSLv3 cipher=OTHER); Sat, 05 Mar 2011 04:12:05 -0800 (PST)
Message-ID: <938E496EA9E44055A322AFC8FAAE83F4@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: "Fred Baker" <fred@cisco.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>
In-Reply-To: <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>
Subject: Re: Question about the link-local addresses
Date: Sat, 5 Mar 2011 20:11:51 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01CBDB71.907168D0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 12:11:21 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_0011_01CBDB71.907168D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

According to RFC4291, it is not link-local address, but cisco and BSD =
think of it as link-local address.


From: Fred Baker=20
Sent: Saturday, March 05, 2011 1:42 PM
To: Yu Hua bing=20
Cc: ipv6@ietf.org=20
Subject: Re: Question about the link-local addresses




On Mar 4, 2011, at 6:59 PM, Yu Hua bing wrote:


     >RFC4291
    > Link-Local addresses are for use on a single link.  Link-Local
    > addresses have the following format:

     |   10     |
     |  bits    |         54 bits         |          64 bits           |
     +----------+-------------------------+----------------------------+
     |1111111010|           0             |       interface ID         |
     +----------+-------------------------+----------------------------+

  I have a question: If the front 10 bits of one IPv6 address is FE80 =
and the middle 54 bits is not zero, is it link-local address?


http://tools.ietf.org/html/rfc4291#section-2.5.6





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


------=_NextPart_000_0011_01CBDB71.907168D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY=20
style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; WORD-WRAP: break-word; =
PADDING-TOP: 15px; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri>According to RFC4291, it is not link-local =
address,=20
b</FONT><FONT face=3DCalibri>ut cisco and BSD think of it as link-local=20
address.</FONT></DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A title=3Dfred@cisco.com=20
href=3D"mailto:fred@cisco.com">Fred Baker</A> </DIV>
<DIV><B>Sent:</B> Saturday, March 05, 2011 1:42 PM</DIV>
<DIV><B>To:</B> <A title=3Dyhb810501@gmail.com=20
href=3D"mailto:yhb810501@gmail.com">Yu Hua bing</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dipv6@ietf.org=20
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</A> </DIV>
<DIV><B>Subject:</B> Re: Question about the link-local=20
addresses</DIV></DIV></DIV>
<DIV><BR></DIV><BR>
<DIV>
<DIV>On Mar 4, 2011, at 6:59 PM, Yu Hua bing wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
  id=3DMailContainerBody name=3D"Compose message area" leftmargin=3D"0" =
topmargin=3D"0"=20
  canvastabstop=3D"true">
  <DIV><FONT face=3DCalibri>&nbsp;&nbsp; &gt;RFC4291</FONT></DIV>
  <DIV><FONT face=3DCalibri>&nbsp;&nbsp;&gt; Link-Local addresses are =
for use on a=20
  single link.&nbsp; Link-Local<BR>&nbsp;&nbsp;&gt; addresses have the =
following=20
  format:<BR><BR>&nbsp;&nbsp; |&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&nbsp;&nbsp; |&nbsp; bits&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 54=20
  bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 64=20
  bits&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&nbsp;&nbsp;=20
  =
+----------+-------------------------+----------------------------+<BR>&n=
bsp;&nbsp;=20
  =
|1111111010|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface=20
  ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;&nbsp;=20
  =
+----------+-------------------------+----------------------------+</FONT=
></DIV>
  <DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DCalibri>I have a question: If the front 10 bits of =
one IPv6=20
  address is FE80 and the middle 54 bits is not zero, is it link-local=20
  address?</FONT></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV><A=20
href=3D"http://tools.ietf.org/html/rfc4291#section-2.5.6">http://tools.ie=
tf.org/html/rfc4291#section-2.5.6</A></DIV>
<DIV><BR>
<BLOCKQUOTE type=3D"cite">
  <DIV style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
  id=3DMailContainerBody name=3D"Compose message area" leftmargin=3D"0" =
topmargin=3D"0"=20
  canvastabstop=3D"true"><FONT face=3DCalibri>
  =
<DIV><BR><BR></DIV></FONT></DIV>-----------------------------------------=
---------------------------<BR>IETF=20
  IPv6 working group mailing list<BR><A=20
  href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</A><BR>Administrative =
Requests:=20
  =
https://www.ietf.org/mailman/listinfo/ipv6<BR>---------------------------=
-----------------------------------------<BR></BLOCKQUOTE></DIV><BR></BOD=
Y></HTML>

------=_NextPart_000_0011_01CBDB71.907168D0--


From i.grok@comcast.net  Sat Mar  5 06:48:52 2011
Return-Path: <i.grok@comcast.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D68913A6A74 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 06:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level: 
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=0.482, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Fm7TyN52Tu1 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 06:48:51 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id B995B3A6857 for <ipv6@ietf.org>; Sat,  5 Mar 2011 06:48:51 -0800 (PST)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta09.westchester.pa.mail.comcast.net with comcast id FSbB1g00527AodY59Sq38G; Sat, 05 Mar 2011 14:50:03 +0000
Received: from olympia.mars.sol ([68.33.77.0]) by omta19.westchester.pa.mail.comcast.net with comcast id FSpw1g01i00PQ6U3fSpxYy; Sat, 05 Mar 2011 14:49:58 +0000
Received: from olympia.mars.sol (localhost [127.0.0.1]) by olympia.mars.sol (8.14.4/8.14.3) with ESMTP id p25EnsYO023457 for <ipv6@ietf.org>; Sat, 5 Mar 2011 09:49:54 -0500
Received: (from draco@localhost) by olympia.mars.sol (8.14.4/8.14.4/Submit) id p25EnsOw023455 for ipv6@ietf.org; Sat, 5 Mar 2011 09:49:54 -0500
Date: Sat, 5 Mar 2011 09:49:54 -0500
From: Scott Schmit <i.grok@comcast.net>
To: ipv6@ietf.org
Subject: Re: Question about the link-local addresses
Message-ID: <20110305144954.GB2782@odin.mars.sol>
Mail-Followup-To: ipv6@ietf.org
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F71A62696B354E2D8A892FCAAE467886@yhbPC>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 14:48:52 -0000

On Sat, Mar 05, 2011 at 10:59:25AM +0800, Yu Hua bing wrote ipv6:
>    >RFC4291
>   > Link-Local addresses are for use on a single link.  Link-Local
>   > addresses have the following format:
> 
>    |   10     |
>    |  bits    |         54 bits         |          64 bits           |
>    +----------+-------------------------+----------------------------+
>    |1111111010|           0             |       interface ID         |
>    +----------+-------------------------+----------------------------+
> 
> I have a question: If the front 10 bits of one IPv6 address is FE80 and the middle 54 bits is not zero, is it link-local address?

Increasing the puzzle, while the text above would imply that if the
middle 54 bits are not zero, it's not link-local, but if you look at
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml,
you will see that IANA has allocated fe80::/10 to "Link Local Unicast".
This lends weight to the interpretation that it's the 10 bits that makes
it a link-local address. Otherwise, they should only have allocated
fe80::/64 for that purpose.

I'm leaning toward the interpretation being "if you're in fe80::/10,
you're link local, but addresses outside fe80::/64 are reserved."

-- 
Scott Schmit

From shemant@cisco.com  Sat Mar  5 07:26:45 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40BC33A6A78 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 07:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.649
X-Spam-Level: 
X-Spam-Status: No, score=-10.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGqcDDmzPoqr for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 07:26:44 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 00F2A3A69DD for <ipv6@ietf.org>; Sat,  5 Mar 2011 07:26:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2069; q=dns/txt; s=iport; t=1299338875; x=1300548475; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=ufdk3WFY0a/zexpG0DM1GDPpSfALrCV4NBMzM1mDmFM=; b=ZgVmmv+7AEXOdYs91p2vRdKXSO6JeMjHHPQFIsAgzPW7F+nQf03BLjeH vsX6bAW4wMjgv6mlAAtTZVNu10mNf/bsjkC2bNPGVH2rMdtoYRTKVCzce vzZDAIvXTvH0QyJXgPrKkVQJhNwFS3NwOGP0XPSH8hH1/E0GCK41SNaju s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgABAIrlcU2tJV2Y/2dsb2JhbACYLo47dKFYmyOFYgSFHIpd
X-IronPort-AV: E=Sophos;i="4.62,269,1297036800"; d="scan'208";a="222508072"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-1.cisco.com with ESMTP; 05 Mar 2011 15:27:52 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p25FRpPJ025661;  Sat, 5 Mar 2011 15:27:51 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 5 Mar 2011 09:27:52 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Question about the link-local addresses
Date: Sat, 5 Mar 2011 09:27:50 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3E2A4B5@XMB-RCD-109.cisco.com>
In-Reply-To: <20110305144954.GB2782@odin.mars.sol>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question about the link-local addresses
Thread-Index: AcvbRKijY8Uv0yThTLeJrmjF2RKFCQABOtAQ
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <20110305144954.GB2782@odin.mars.sol>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Scott Schmit" <i.grok@comcast.net>, <ipv6@ietf.org>
X-OriginalArrivalTime: 05 Mar 2011 15:27:52.0300 (UTC) FILETIME=[E481D2C0:01CBDB49]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 15:26:45 -0000

Scott,

You are correct.  Note IANA assigns address blocks defined in some RFC
and indeed for the IPv6 link-local address RFC 4291 is referenced by
IANA.  See section 2.4 of RFC 4291 that includes this line.

[Link-Local unicast   1111111010           FE80::/10       2.5.6]

Hemant

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Scott Schmit
Sent: Saturday, March 05, 2011 9:50 AM
To: ipv6@ietf.org
Subject: Re: Question about the link-local addresses

On Sat, Mar 05, 2011 at 10:59:25AM +0800, Yu Hua bing wrote ipv6:
>    >RFC4291
>   > Link-Local addresses are for use on a single link.  Link-Local
>   > addresses have the following format:
>=20
>    |   10     |
>    |  bits    |         54 bits         |          64 bits           |
>    +----------+-------------------------+----------------------------+
>    |1111111010|           0             |       interface ID         |
>    +----------+-------------------------+----------------------------+
>=20
> I have a question: If the front 10 bits of one IPv6 address is FE80
and the middle 54 bits is not zero, is it link-local address?

Increasing the puzzle, while the text above would imply that if the
middle 54 bits are not zero, it's not link-local, but if you look at
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xm
l,
you will see that IANA has allocated fe80::/10 to "Link Local Unicast".
This lends weight to the interpretation that it's the 10 bits that makes
it a link-local address. Otherwise, they should only have allocated
fe80::/64 for that purpose.

I'm leaning toward the interpretation being "if you're in fe80::/10,
you're link local, but addresses outside fe80::/64 are reserved."

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

From trejrco@gmail.com  Sat Mar  5 07:30:42 2011
Return-Path: <trejrco@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6A283A67F4 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 07:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.451
X-Spam-Level: 
X-Spam-Status: No, score=-3.451 tagged_above=-999 required=5 tests=[AWL=0.147,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SDwGi2cnzVLt for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 07:30:41 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id D16033A6826 for <ipv6@ietf.org>; Sat,  5 Mar 2011 07:30:41 -0800 (PST)
Received: by iyj8 with SMTP id 8so3179473iyj.31 for <ipv6@ietf.org>; Sat, 05 Mar 2011 07:31:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=DmSTRlGjLlSoRFSlxa/Rq7lUA6cEsoYXpc0xKuvvc6g=; b=wJP296NyPeRuS7YH+gvdaBXS5c0M5oY38M8ePPDt45EIr4ryP8+vVSmk6LvwI67+yf jX3jrbtpHG9oB4Iy1aWe2HLTJbwRZlBM3Nr+KN4dwtuWUsBgjYFv+EPPjWqmDH0wdMpA oMioX1IyFe9m4+fPMYpw0WN/Z0EDcbIntsp6o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=EABk+4y/6BR5MS6b0gp6NtNIMt4Z4t9LiIyYI4ZWBXbbCtKmMVIM6aPE9jR2KUIBTN yCKuXhLnRq2IQdq8Ml0C6/nUoPA1O8qfAYRDpaqC4omnlVI2L8mq271XAZP5iC6G4nCW 4LDQj5xTwJUoGALx3a+1wZ2zsyIatk0RWyjEw=
MIME-Version: 1.0
Received: by 10.231.3.142 with SMTP id 14mr1394730ibn.84.1299339112415; Sat, 05 Mar 2011 07:31:52 -0800 (PST)
Received: by 10.231.148.143 with HTTP; Sat, 5 Mar 2011 07:31:52 -0800 (PST)
Received: by 10.231.148.143 with HTTP; Sat, 5 Mar 2011 07:31:52 -0800 (PST)
In-Reply-To: <20110305144954.GB2782@odin.mars.sol>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <20110305144954.GB2782@odin.mars.sol>
Date: Sat, 5 Mar 2011 10:31:52 -0500
Message-ID: <AANLkTimdfF3ZvV9h+PU7Mn51s02XnMMggKYaBt50=j5d@mail.gmail.com>
Subject: Re: Question about the link-local addresses
From: TJ <trejrco@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=002215045bdb3d07c8049dbdf677
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: trejrco@gmail.com
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 15:30:43 -0000

--002215045bdb3d07c8049dbdf677
Content-Type: text/plain; charset=ISO-8859-1

On Mar 5, 2011 9:50 AM, "Scott Schmit" <i.grok@comcast.net> wrote:
>
> On Sat, Mar 05, 2011 at 10:59:25AM +0800, Yu Hua bing wrote ipv6:
> >    >RFC4291
> >   > Link-Local addresses are for use on a single link.  Link-Local
> >   > addresses have the following format:
> >
> >    |   10     |
> >    |  bits    |         54 bits         |          64 bits           |
> >    +----------+-------------------------+----------------------------+
> >    |1111111010|           0             |       interface ID         |
> >    +----------+-------------------------+----------------------------+
> >
> > I have a question: If the front 10 bits of one IPv6 address is FE80 and
the middle 54 bits is not zero, is it link-local address?
>
> Increasing the puzzle, while the text above would imply that if the
> middle 54 bits are not zero, it's not link-local, but if you look at
> http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xml,
> you will see that IANA has allocated fe80::/10 to "Link Local Unicast".
> This lends weight to the interpretation that it's the 10 bits that makes
> it a link-local address. Otherwise, they should only have allocated
> fe80::/64 for that purpose.
>
> I'm leaning toward the interpretation being "if you're in fe80::/10,
> you're link local, but addresses outside fe80::/64 are reserved."

Exactly right, IMHO.  Link local unicast (generic, that is - any link-scoped
uni) vs link local addresses (specific, the ones required* to be on an
interface)
/TJ

--002215045bdb3d07c8049dbdf677
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p><br>
On Mar 5, 2011 9:50 AM, &quot;Scott Schmit&quot; &lt;<a href=3D"mailto:i.gr=
ok@comcast.net">i.grok@comcast.net</a>&gt; wrote:<br>
&gt;<br>
&gt; On Sat, Mar 05, 2011 at 10:59:25AM +0800, Yu Hua bing wrote ipv6:<br>
&gt; &gt; =A0 =A0&gt;RFC4291<br>
&gt; &gt; =A0 &gt; Link-Local addresses are for use on a single link. =A0Li=
nk-Local<br>
&gt; &gt; =A0 &gt; addresses have the following format:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0| =A0 10 =A0 =A0 |<br>
&gt; &gt; =A0 =A0| =A0bits =A0 =A0| =A0 =A0 =A0 =A0 54 bits =A0 =A0 =A0 =A0=
 | =A0 =A0 =A0 =A0 =A064 bits =A0 =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 =A0+----------+-------------------------+--------------------=
--------+<br>
&gt; &gt; =A0 =A0|1111111010| =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0=
 | =A0 =A0 =A0 interface ID =A0 =A0 =A0 =A0 |<br>
&gt; &gt; =A0 =A0+----------+-------------------------+--------------------=
--------+<br>
&gt; &gt;<br>
&gt; &gt; I have a question: If the front 10 bits of one IPv6 address is FE=
80 and the middle 54 bits is not zero, is it link-local address?<br>
&gt;<br>
&gt; Increasing the puzzle, while the text above would imply that if the<br=
>
&gt; middle 54 bits are not zero, it&#39;s not link-local, but if you look =
at<br>
&gt; <a href=3D"http://www.iana.org/assignments/ipv6-address-space/ipv6-add=
ress-space.xml">http://www.iana.org/assignments/ipv6-address-space/ipv6-add=
ress-space.xml</a>,<br>
&gt; you will see that IANA has allocated fe80::/10 to &quot;Link Local Uni=
cast&quot;.<br>
&gt; This lends weight to the interpretation that it&#39;s the 10 bits that=
 makes<br>
&gt; it a link-local address. Otherwise, they should only have allocated<br=
>
&gt; fe80::/64 for that purpose.<br>
&gt;<br>
&gt; I&#39;m leaning toward the interpretation being &quot;if you&#39;re in=
 fe80::/10,<br>
&gt; you&#39;re link local, but addresses outside fe80::/64 are reserved.&q=
uot;</p>
<p>Exactly right, IMHO.=A0 Link local unicast (generic, that is - any link-=
scoped uni) vs link local addresses (specific, the ones required* to be on =
an interface)<br>
/TJ<br>
</p>

--002215045bdb3d07c8049dbdf677--

From brian.e.carpenter@gmail.com  Sat Mar  5 11:39:44 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344573A69EC for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 11:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.5
X-Spam-Level: 
X-Spam-Status: No, score=-103.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9RDwFuYG3myD for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 11:39:42 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 8DA563A687E for <ipv6@ietf.org>; Sat,  5 Mar 2011 11:39:42 -0800 (PST)
Received: by yic13 with SMTP id 13so1415585yic.31 for <ipv6@ietf.org>; Sat, 05 Mar 2011 11:40:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ERlF4jx+xJn+5dF//zLC8Gm4efyMAqaXVSNGlTh1330=; b=sW4nb/MAq792RmGvP7hZgCotoAy575HTDGV9T2PHYX+LFG7uhGgE7xDJp0XEBkVOev RHPLNs7o1JUbMnmv3+OLZgRnXM3xLXN+Gzi3KnRs1g56oujQSmyLe97yqJanbfWMnCl8 GPCsvJe/DuOYpV3ZWdlUp/Fu123QvJjEO0dMQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=a6ELBui7VaKDLMLTwciriLmISHYPA1SO9p7d3Q78H9iYGsI4JdD+sMto4cbgOiyLqy 3iD0c3Ct63lxUDtCdR2y3ToG20GytLqymJDYpLSkVVrtyA5O3VS/15Bn1YhetShSD73R Zcoo02w/E11AcZ1zfrSvPgpY2maXT+LUnRon4=
Received: by 10.90.199.19 with SMTP id w19mr2886719agf.19.1299354053146; Sat, 05 Mar 2011 11:40:53 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id 35sm1139280ano.31.2011.03.05.11.40.50 (version=SSLv3 cipher=OTHER); Sat, 05 Mar 2011 11:40:52 -0800 (PST)
Message-ID: <4D7291B8.60508@gmail.com>
Date: Sun, 06 Mar 2011 08:40:40 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Yu Hua bing <yhb810501@gmail.com>
Subject: Re: Question about the link-local addresses
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC>	<C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com> <938E496EA9E44055A322AFC8FAAE83F4@yhbPC>
In-Reply-To: <938E496EA9E44055A322AFC8FAAE83F4@yhbPC>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Fred Baker <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 19:39:44 -0000

Any router that forwards fe80::/10 would be pretty stupid I think,
since the whole prefix is IANA-reserved. The RFC apears to
only reserve fe80::/64.

Maybe this should be logged as a "held" erratum for RFC 4291,
to be made 100% clear if it is updated.

Regards
   Brian Carpenter

From brian@innovationslab.net  Sat Mar  5 12:10:47 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A80353A6AB1 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 12:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bttIGxY2SUhN for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 12:10:46 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 8C2FB3A6AB4 for <ipv6@ietf.org>; Sat,  5 Mar 2011 12:10:45 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 09DD688261 for <ipv6@ietf.org>; Sat,  5 Mar 2011 12:11:52 -0800 (PST)
Received: from Littlejohn.local (c-76-100-105-215.hsd1.md.comcast.net [76.100.105.215]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id A170213682B4 for <ipv6@ietf.org>; Sat,  5 Mar 2011 12:11:47 -0800 (PST)
Message-ID: <4D7298FD.3000205@innovationslab.net>
Date: Sat, 05 Mar 2011 15:11:41 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Question about the link-local addresses
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC>	<C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com>	<938E496EA9E44055A322AFC8FAAE83F4@yhbPC> <4D7291B8.60508@gmail.com>
In-Reply-To: <4D7291B8.60508@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 20:10:48 -0000

On 3/5/11 2:40 PM, Brian E Carpenter wrote:
> Any router that forwards fe80::/10 would be pretty stupid I think,
> since the whole prefix is IANA-reserved. The RFC apears to
> only reserve fe80::/64.

Actually, the IANA Considerations section of 4291 doesn't reserve 
anything.  But, 3513 does reserve FE80::/10 (as well as a bunch of other 
ranges).

>
> Maybe this should be logged as a "held" erratum for RFC 4291,
> to be made 100% clear if it is updated.

There is a discrepancy between what is actually in 4291 and what is 
listed in the IANA table...

Regards,
Brian

From kauer@biplane.com.au  Sat Mar  5 14:22:53 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1DA53A6A2F for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_54=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id naiLpLN7V3dr for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:22:52 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 05DA23A69F0 for <ipv6@ietf.org>; Sat,  5 Mar 2011 14:22:50 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PvztI-00040T-DN for ipv6@ietf.org; Sat, 05 Mar 2011 17:24:00 -0500
Subject: Re: Question about the link-local addresses
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <20110305144954.GB2782@odin.mars.sol>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <20110305144954.GB2782@odin.mars.sol>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-HLdezwShxcwLvYpPXyH7"
Date: Sun, 06 Mar 2011 09:28:06 +1100
Message-ID: <1299364086.16769.34.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 22:22:54 -0000

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

On Sat, 2011-03-05 at 09:49 -0500, Scott Schmit wrote:
> I'm leaning toward the interpretation being "if you're in fe80::/10,
> you're link local, but addresses outside fe80::/64 are reserved."

Linux treats link local addresses as being in a /64:

wlan0     [...]
          inet6 addr: fe80::222:fbff:fe54:9b80/64 Scope:Link
          [...]

While it may be that having bits set in that 54-bit region makes the
address technically not a link local address, I think in practice you
will see all addresses in fe80::/10 regarded as link local.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-HLdezwShxcwLvYpPXyH7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk1yuO8ACgkQMAcU7Vc29oekJgCgnIr7gxOD+Chep8PzRbLl92W4
Zk0An0dfrFFnybbrsBbKrUgV1Zjg8K5b
=AVBl
-----END PGP SIGNATURE-----

--=-HLdezwShxcwLvYpPXyH7--


From hagen@jauu.net  Sat Mar  5 14:48:13 2011
Return-Path: <hagen@jauu.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9DEAD3A682E for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_54=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKSUrtW+DIU0 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:48:13 -0800 (PST)
Received: from geheimer.internetendpunkt.de (alternativer.internetendpunkt.de [88.198.24.89]) by core3.amsl.com (Postfix) with ESMTP id E31163A6784 for <ipv6@ietf.org>; Sat,  5 Mar 2011 14:48:12 -0800 (PST)
Received: by geheimer.internetendpunkt.de (Postfix, from userid 1000) id DB12538001; Sat,  5 Mar 2011 23:49:22 +0100 (CET)
Date: Sat, 5 Mar 2011 23:49:22 +0100
From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: Question about the link-local addresses
Message-ID: <20110305224922.GC9163@nuttenaction>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <20110305144954.GB2782@odin.mars.sol> <1299364086.16769.34.camel@karl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <1299364086.16769.34.camel@karl>
X-Key-Id: 98350C22
X-Key-Fingerprint: 490F 557B 6C48 6D7E 5706 2EA2 4A22 8D45 9835 0C22
X-GPG-Key: gpg --recv-keys --keyserver wwwkeys.eu.pgp.net 98350C22
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 22:48:13 -0000

* Karl Auer | 2011-03-06 09:28:06 [+1100]:

>Linux treats link local addresses as being in a /64:
>
>wlan0     [...]
>          inet6 addr: fe80::222:fbff:fe54:9b80/64 Scope:Link
>          [...]

Yes (Linux):

if ((st & htonl(0xFFC00000)) =3D=3D htonl(0xFE800000))
        return (IPV6_ADDR_LINKLOCAL | IPV6_ADDR_UNICAST |
                IPV6_ADDR_SCOPE_TYPE(IPV6_ADDR_SCOPE_LINKLOCAL));=20

as well as *BSD:

#define IN6_IS_ADDR_LINKLOCAL(a)        \
        (((a)->s6_addr[0] =3D=3D 0xfe) && (((a)->s6_addr[1] & 0xc0) =3D=3D =
0x80))


Best regards, Hagen

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Mar  5 14:55:53 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5404D3A68BC for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:55:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iT5A3hYViG2e for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 14:55:52 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 857713A67ED for <ipv6@ietf.org>; Sat,  5 Mar 2011 14:55:52 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pw0P8-0004hR-GD; Sun, 06 Mar 2011 09:26:54 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id B9E8B5355C; Sun,  6 Mar 2011 09:26:53 +1030 (CST)
Date: Sun, 6 Mar 2011 09:26:53 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Question about the link-local addresses
Message-ID: <20110306092653.791d4ab3@opy.nosense.org>
In-Reply-To: <4D7291B8.60508@gmail.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com> <938E496EA9E44055A322AFC8FAAE83F4@yhbPC> <4D7291B8.60508@gmail.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Fred Baker <fred@cisco.com>, Yu Hua bing <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 22:55:53 -0000

On Sun, 06 Mar 2011 08:40:40 +1300
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> Any router that forwards fe80::/10 would be pretty stupid I think,
> since the whole prefix is IANA-reserved. The RFC apears to
> only reserve fe80::/64.
> 
> Maybe this should be logged as a "held" erratum for RFC 4291,
> to be made 100% clear if it is updated.
> 

I've been a bit interested in this area fairly recently, in the context
of making things like RA guard a bit easier. If some of those 54 bits
were used to encode a device or function type, then RA guard could
be more simply achieved by filtering on link local source address
types e.g. if bits 11 through 16 in the link local prefix were used to
encode a type, then -

fe80::/16 - end-hosts
fe81::/16 - routers
fe82::/16 - dhcpv6 servers
etc.

This isn't a new idea, IIRC Appletalk used the lower 1-127 node
ids in a cable number for end-nodes, and the upper 128 to 253
for servers.

To see of non-fe80::/64 link locals would work with existing
implementations, I've run up a quick test with a couple of linux boxes,
with one running as a router (radvd, fe81::1/64, autoconf'd fe80::/64
deleted) and the other with a conventional kernel configured fe80::/64
link local address. Everything appears to be working, so it could be
possible to move to a link-local encoded type model without too much
trouble if other implementations handle non-fe80::/64 in the same way
(i.e. apparently as fe80::/10).

Regards,
Mark.

From fred@cisco.com  Sat Mar  5 15:57:56 2011
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C45973A6A3E for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 15:57:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.425
X-Spam-Level: 
X-Spam-Status: No, score=-110.425 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUgToveNOhuO for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 15:57:55 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id B6AA83A6A32 for <ipv6@ietf.org>; Sat,  5 Mar 2011 15:57:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2087; q=dns/txt; s=iport; t=1299369547; x=1300579147; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=bFzcIhzpFz6wnBn+STCznJtSX6wVgpRVOoWGAB9HhTM=; b=YEZX0SKBVEx/1coDktF6uxv2T9h0iJLM2791t8jhEK89OyZ9VEywmrKL 9ths3iMykD8mgkw8dfA6QqIMYLkXpVq65hNWE+t7zpFyTKl32TCXYoYoT xBrNtoDjkd+ah3ufnrauAqtwJHXl1Zgf3/PEn9B7Uf9wuLRpODQYTynK5 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABNdck2rR7Hu/2dsb2JhbACmaXSjBpprgn6CZASFHIcUhl0
X-IronPort-AV: E=Sophos;i="4.62,270,1297036800"; d="scan'208";a="270225991"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 05 Mar 2011 23:59:06 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p25Nx6jZ014026; Sat, 5 Mar 2011 23:59:06 GMT
Subject: Re: Question about the link-local addresses
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20110306092653.791d4ab3@opy.nosense.org>
Date: Sat, 5 Mar 2011 15:59:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A33336F-8326-44FE-AD5E-A780C0FABAD2@cisco.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com> <938E496EA9E44055A322AFC8FAAE83F4@yhbPC> <4D7291B8.60508@gmail.com> <20110306092653.791d4ab3@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, Yu Hua bing <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 Mar 2011 23:57:56 -0000

Dumb question. Is there an attack in your proposal? For example, if I =
were to mis-identify my RA as coming from an end-host, could I now =
bypass RA-Guard?

On Mar 5, 2011, at 2:56 PM, Mark Smith wrote:

> On Sun, 06 Mar 2011 08:40:40 +1300
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>=20
>> Any router that forwards fe80::/10 would be pretty stupid I think,
>> since the whole prefix is IANA-reserved. The RFC apears to
>> only reserve fe80::/64.
>>=20
>> Maybe this should be logged as a "held" erratum for RFC 4291,
>> to be made 100% clear if it is updated.
>>=20
>=20
> I've been a bit interested in this area fairly recently, in the =
context
> of making things like RA guard a bit easier. If some of those 54 bits
> were used to encode a device or function type, then RA guard could
> be more simply achieved by filtering on link local source address
> types e.g. if bits 11 through 16 in the link local prefix were used to
> encode a type, then -
>=20
> fe80::/16 - end-hosts
> fe81::/16 - routers
> fe82::/16 - dhcpv6 servers
> etc.
>=20
> This isn't a new idea, IIRC Appletalk used the lower 1-127 node
> ids in a cable number for end-nodes, and the upper 128 to 253
> for servers.
>=20
> To see of non-fe80::/64 link locals would work with existing
> implementations, I've run up a quick test with a couple of linux =
boxes,
> with one running as a router (radvd, fe81::1/64, autoconf'd fe80::/64
> deleted) and the other with a conventional kernel configured fe80::/64
> link local address. Everything appears to be working, so it could be
> possible to move to a link-local encoded type model without too much
> trouble if other implementations handle non-fe80::/64 in the same way
> (i.e. apparently as fe80::/10).
>=20
> Regards,
> Mark.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Mar  5 17:04:38 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB4573A6A43 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 17:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysFF7msMmH5T for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 17:04:37 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 878C53A68A9 for <ipv6@ietf.org>; Sat,  5 Mar 2011 17:04:37 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pw2Po-0002Qt-J6; Sun, 06 Mar 2011 11:35:44 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 33AF15355C; Sun,  6 Mar 2011 11:35:44 +1030 (CST)
Date: Sun, 6 Mar 2011 11:35:43 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fred Baker <fred@cisco.com>
Subject: Re: Question about the link-local addresses
Message-ID: <20110306113543.0eec5d2e@opy.nosense.org>
In-Reply-To: <9A33336F-8326-44FE-AD5E-A780C0FABAD2@cisco.com>
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC> <C100F400-3F7F-48DF-ABC3-7B0204C73726@cisco.com> <938E496EA9E44055A322AFC8FAAE83F4@yhbPC> <4D7291B8.60508@gmail.com> <20110306092653.791d4ab3@opy.nosense.org> <9A33336F-8326-44FE-AD5E-A780C0FABAD2@cisco.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Yu, ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, bing <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 01:04:38 -0000

Hi Fred,

On Sat, 5 Mar 2011 15:59:06 -0800
Fred Baker <fred@cisco.com> wrote:

> Dumb question. Is there an attack in your proposal? For example, if I were to mis-identify my RA as coming from an end-host, could I now bypass RA-Guard?
> 

I'm not sure I fully understand your question, although I think you're
asking if end-nodes would also have to enforce this source
address/device function policy. That would be the case. My thoughts
around this area have mainly been related to the sort of effort layer 2
devices have to go to to inspect existing format RAs - encoding device
type/function in the source link local IPv6 address would seem to me
to be simpler, as the permit/deny decision it would be an exact match
on the first 10 bits of the source IPv6 address, almost directly after
the link-layer destination address in the frame, and that avoids these
layer 2 devices having to have knowledge of e.g. ICMPv6 formats, (maybe)
possibilities of extension headers etc. Possibly some devices which
can't implement RA guard as it is today might be able to perform a
simpler link-local source address based version. 

My interest in compatibility with existing link-local implementations
where RAs come from a non-fe80::/64 source was about how to easy a
transition to this sort of addressing model would be during an interim
period.

I haven't fully thought through my idea, including whether the cost of
this sort of change would be worth benefit, I mentioned it mainly
because it was relevant to the fe80::/10 vs fe80::/64 discussion.
Possibly there may be other benefits in encoding a device or function
type in a link-local address even if a simpler RA guard is not one of
them.

Regards,
Mark.


> On Mar 5, 2011, at 2:56 PM, Mark Smith wrote:
> 
> > On Sun, 06 Mar 2011 08:40:40 +1300
> > Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> > 
> >> Any router that forwards fe80::/10 would be pretty stupid I think,
> >> since the whole prefix is IANA-reserved. The RFC apears to
> >> only reserve fe80::/64.
> >> 
> >> Maybe this should be logged as a "held" erratum for RFC 4291,
> >> to be made 100% clear if it is updated.
> >> 
> > 
> > I've been a bit interested in this area fairly recently, in the context
> > of making things like RA guard a bit easier. If some of those 54 bits
> > were used to encode a device or function type, then RA guard could
> > be more simply achieved by filtering on link local source address
> > types e.g. if bits 11 through 16 in the link local prefix were used to
> > encode a type, then -
> > 
> > fe80::/16 - end-hosts
> > fe81::/16 - routers
> > fe82::/16 - dhcpv6 servers
> > etc.
> > 
> > This isn't a new idea, IIRC Appletalk used the lower 1-127 node
> > ids in a cable number for end-nodes, and the upper 128 to 253
> > for servers.
> > 
> > To see of non-fe80::/64 link locals would work with existing
> > implementations, I've run up a quick test with a couple of linux boxes,
> > with one running as a router (radvd, fe81::1/64, autoconf'd fe80::/64
> > deleted) and the other with a conventional kernel configured fe80::/64
> > link local address. Everything appears to be working, so it could be
> > possible to move to a link-local encoded type model without too much
> > trouble if other implementations handle non-fe80::/64 in the same way
> > (i.e. apparently as fe80::/10).
> > 
> > Regards,
> > Mark.
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> 

From randy@psg.com  Sat Mar  5 20:19:40 2011
Return-Path: <randy@psg.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB97B3A6A01 for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 20:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OoekTj+XUuEB for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 20:19:38 -0800 (PST)
Received: from ran.psg.com (ssh.psg.com [IPv6:2001:418:1::40]) by core3.amsl.com (Postfix) with ESMTP id 3933A3A69FC for <ipv6@ietf.org>; Sat,  5 Mar 2011 20:19:37 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Pw5ST-000JBk-Gf; Sun, 06 Mar 2011 04:20:42 +0000
Date: Sun, 06 Mar 2011 13:20:40 +0900
Message-ID: <m2aah8x4kn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 04:19:40 -0000

> And, keep in mind, one can use abitrary prefixes by turning off
> stateless address autoconfiguration  and using DHCPv6.

we wish.  there is still the exciting mess of ra.

randy

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Mar  5 23:39:36 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 079A13A692A for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 23:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaBImGLKd2Um for <ipv6@core3.amsl.com>; Sat,  5 Mar 2011 23:39:35 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 095A33A689F for <ipv6@ietf.org>; Sat,  5 Mar 2011 23:39:34 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pw8Zz-0002RC-RH; Sun, 06 Mar 2011 18:10:39 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 5C3B35355C; Sun,  6 Mar 2011 18:10:39 +1030 (CST)
Date: Sun, 6 Mar 2011 18:10:39 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Randy Bush <randy@psg.com>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110306181039.7728b3f4@opy.nosense.org>
In-Reply-To: <m2aah8x4kn.wl%randy@psg.com>
References: <AANLkTingK90GD4W-z4LXQ-dUvVv6b=ZUwTokddwXAM=u@mail.gmail.com> <4D6EAF57.8050606@gmail.com> <201103022125.p22LPljL020592@cichlid.raleigh.ibm.com> <4D6EC041.4070304@gmail.com> <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, huabing yu <yhb810501@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 07:39:36 -0000

On Sun, 06 Mar 2011 13:20:40 +0900
Randy Bush <randy@psg.com> wrote:

> > And, keep in mind, one can use abitrary prefixes by turning off
> > stateless address autoconfiguration  and using DHCPv6.
> 
> we wish.  there is still the exciting mess of ra.
> 

Your wishes are already true. You switch off the autonomous
address-configuration flag (A bit) for the prefix -

      A              1-bit autonomous address-configuration flag.  When
                     set indicates that this prefix can be used for
                     stateless address configuration as specified in
                     [ADDRCONF].

So in summary -

RA with M and O bits set
PIO in RA with prefix(es) with L bit on and A bit off

will force DHCPv6.


From sthaug@nethelp.no  Sun Mar  6 00:01:11 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A39CE3A6A5A for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPH7rZx6MFE0 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:01:10 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 9AF423A6A4F for <ipv6@ietf.org>; Sun,  6 Mar 2011 00:01:09 -0800 (PST)
Received: (qmail 53021 invoked from network); 6 Mar 2011 08:02:18 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 6 Mar 2011 08:02:18 -0000
Date: Sun, 06 Mar 2011 09:02:18 +0100 (CET)
Message-Id: <20110306.090218.74700598.sthaug@nethelp.no>
To: ipng@69706e6720323030352d30312d31340a.nosense.org
Subject: Re: draft-yhb-6man-slaac-improvement-00
From: sthaug@nethelp.no
In-Reply-To: <20110306181039.7728b3f4@opy.nosense.org>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.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
Cc: narten@us.ibm.com, ipv6@ietf.org, brian.e.carpenter@gmail.com, yhb810501@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 08:01:12 -0000

> So in summary -
> 
> RA with M and O bits set
> PIO in RA with prefix(es) with L bit on and A bit off
> 
> will force DHCPv6.

Or, alternatively, RA with M and O bits set and no prefix at all.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Mar  6 00:32:02 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B0E83A68B8 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPELoaDbHUfM for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:32:01 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id C0B8C3A67AE for <ipv6@ietf.org>; Sun,  6 Mar 2011 00:32:01 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pw9On-0004WN-QT; Sun, 06 Mar 2011 19:03:09 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 6B7AA5355C; Sun,  6 Mar 2011 19:03:09 +1030 (CST)
Date: Sun, 6 Mar 2011 19:03:09 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: sthaug@nethelp.no
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110306190309.04e96116@opy.nosense.org>
In-Reply-To: <20110306.090218.74700598.sthaug@nethelp.no>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, ipv6@ietf.org, brian.e.carpenter@gmail.com, yhb810501@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 08:32:02 -0000

On Sun, 06 Mar 2011 09:02:18 +0100 (CET)
sthaug@nethelp.no wrote:

> > So in summary -
> > 
> > RA with M and O bits set
> > PIO in RA with prefix(es) with L bit on and A bit off
> > 
> > will force DHCPv6.
> 
> Or, alternatively, RA with M and O bits set and no prefix at all.
> 

I don't think that will always work. The PIO is needed to indicate to
end-nodes what the onlink prefix(es) are, as per RFC5942. 


> Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From sthaug@nethelp.no  Sun Mar  6 00:48:02 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CD1228C0F5 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4YqM0B-RmuA for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:48:01 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 242773A6916 for <ipv6@ietf.org>; Sun,  6 Mar 2011 00:48:00 -0800 (PST)
Received: (qmail 61997 invoked from network); 6 Mar 2011 08:49:11 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 6 Mar 2011 08:49:11 -0000
Date: Sun, 06 Mar 2011 09:49:11 +0100 (CET)
Message-Id: <20110306.094911.41682473.sthaug@nethelp.no>
To: ipng@69706e6720323030352d30312d31340a.nosense.org
Subject: Re: draft-yhb-6man-slaac-improvement-00
From: sthaug@nethelp.no
In-Reply-To: <20110306190309.04e96116@opy.nosense.org>
References: <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.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
Cc: narten@us.ibm.com, ipv6@ietf.org, brian.e.carpenter@gmail.com, yhb810501@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 08:48:02 -0000

> > > So in summary -
> > > 
> > > RA with M and O bits set
> > > PIO in RA with prefix(es) with L bit on and A bit off
> > > 
> > > will force DHCPv6.
> > 
> > Or, alternatively, RA with M and O bits set and no prefix at all.
> > 
> 
> I don't think that will always work. The PIO is needed to indicate to
> end-nodes what the onlink prefix(es) are, as per RFC5942. 

Agreed, it won't always work. But it *can* work, if your deployment
model is DHCPv6 with IA_PD using the link-local address of the router
as next-hop.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no



From swmike@swm.pp.se  Sun Mar  6 00:53:33 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF9B628C0D8 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:53:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycHniwI7NoyB for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 00:53:33 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 1CE8828C0CF for <ipv6@ietf.org>; Sun,  6 Mar 2011 00:53:31 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9E0E79C; Sun,  6 Mar 2011 09:54:42 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 9BF0A9A; Sun,  6 Mar 2011 09:54:42 +0100 (CET)
Date: Sun, 6 Mar 2011 09:54:42 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <20110306190309.04e96116@opy.nosense.org>
Message-ID: <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 08:53:34 -0000

On Sun, 6 Mar 2011, Mark Smith wrote:

> I don't think that will always work. The PIO is needed to indicate to 
> end-nodes what the onlink prefix(es) are, as per RFC5942.

Why do they need to know that?

In our testing at least under Linux did just fine by knowing how to reach 
the router and that it needed to use (and actually used) DHCPv6 to get its 
IPv6 address. No on-link prefix was needed (or even desireable in some 
deployment scenarios).

Does RFC5942 says this is mandatory? I interpret 4.1 as this is definitely 
not mandatory, rather the opposite?

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

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Mar  6 01:04:14 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A84BF3A688C for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQFE8Y1Hw8cb for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:04:14 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id E09703A67AE for <ipv6@ietf.org>; Sun,  6 Mar 2011 01:04:13 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pw9tz-0005ra-UU; Sun, 06 Mar 2011 19:35:24 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id B055E5355C; Sun,  6 Mar 2011 19:35:23 +1030 (CST)
Date: Sun, 6 Mar 2011 19:35:23 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: sthaug@nethelp.no
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110306193523.2082967c@opy.nosense.org>
In-Reply-To: <20110306.094911.41682473.sthaug@nethelp.no>
References: <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <20110306.094911.41682473.sthaug@nethelp.no>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 09:04:14 -0000

On Sun, 06 Mar 2011 09:49:11 +0100 (CET)
sthaug@nethelp.no wrote:

> > > > So in summary -
> > > > 
> > > > RA with M and O bits set
> > > > PIO in RA with prefix(es) with L bit on and A bit off
> > > > 
> > > > will force DHCPv6.
> > > 
> > > Or, alternatively, RA with M and O bits set and no prefix at all.
> > > 
> > 
> > I don't think that will always work. The PIO is needed to indicate to
> > end-nodes what the onlink prefix(es) are, as per RFC5942. 
> 
> Agreed, it won't always work. But it *can* work, if your deployment
> model is DHCPv6 with IA_PD using the link-local address of the router
> as next-hop.
> 

i.e. an unnumbered link where there is no assigned prefix, and every
destination, other than link local ones, are considered to be off-link.
If you want a prefix to be considered on link, such as a group of
end-nodes LAN scenario, you need to announce it in a PIO (with A off if
you don't want SLAAC).

> Steinar Haug, Nethelp consulting, sthaug@nethelp.no
> 
> 

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Mar  6 01:22:53 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 259433A6842 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xq0+wAvtOrOg for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:22:52 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 0BF013A67AE for <ipv6@ietf.org>; Sun,  6 Mar 2011 01:22:51 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PwABz-0006qk-1r; Sun, 06 Mar 2011 19:53:59 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id A48345355C; Sun,  6 Mar 2011 19:53:58 +1030 (CST)
Date: Sun, 6 Mar 2011 19:53:58 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110306195358.1d47b424@opy.nosense.org>
In-Reply-To: <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 09:22:53 -0000

On Sun, 6 Mar 2011 09:54:42 +0100 (CET)
Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Sun, 6 Mar 2011, Mark Smith wrote:
> 
> > I don't think that will always work. The PIO is needed to indicate to 
> > end-nodes what the onlink prefix(es) are, as per RFC5942.
> 
> Why do they need to know that?
> 
> In our testing at least under Linux did just fine by knowing how to reach 
> the router and that it needed to use (and actually used) DHCPv6 to get its 
> IPv6 address. No on-link prefix was needed (or even desireable in some 
> deployment scenarios).
> 

The PIO isn't to make DHCPv6 work, it is to inform the end-host of what
destinations are onlink. Here is what RFC5942 says -


   The behavior of IPv6 as specified in Neighbor Discovery (ND)
   [RFC4861] is quite different.  The on-link determination is separate
   from the address assignment.  A host can have IPv6 addresses without



Singh, et al.                Standards Track                    [Page 2]
^L
RFC 5942                    IPv6 Subnet Model                  July 2010


   any related on-link prefixes or can have on-link prefixes that are
   not related to any IPv6 addresses that are assigned to the host.  Any
   assigned address on an interface should initially be considered as
   having no internal structure as shown in [RFC4291].

   In IPv6, by default, a host treats only the link-local prefix as
   on-link.

   The reception of a Prefix Information Option (PIO) with the L-bit set
   [RFC4861] and a non-zero valid lifetime creates (or updates) an entry
   in the Prefix List.  All prefixes on a host's Prefix List (i.e.,
   those prefixes that have not yet timed out) are considered to be
   on-link by that host.


> Does RFC5942 says this is mandatory?

It updates 4861.

> I interpret 4.1 as this is definitely 
> not mandatory, rather the opposite?
> 

I'm not quite sure which 4.1 you're referring to. Point 1. of section 4
of RFC5942?




From swmike@swm.pp.se  Sun Mar  6 01:45:57 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B60F3A6934 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:45:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id clpoQ9cmf+ea for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 01:45:56 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 7B7753A688C for <ipv6@ietf.org>; Sun,  6 Mar 2011 01:45:56 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A9D409C; Sun,  6 Mar 2011 10:47:06 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A69219A; Sun,  6 Mar 2011 10:47:06 +0100 (CET)
Date: Sun, 6 Mar 2011 10:47:06 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <20110306195358.1d47b424@opy.nosense.org>
Message-ID: <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se> <20110306195358.1d47b424@opy.nosense.org>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 09:45:57 -0000

On Sun, 6 Mar 2011, Mark Smith wrote:

> The PIO isn't to make DHCPv6 work, it is to inform the end-host of what
> destinations are onlink. Here is what RFC5942 says -

Why does it need destinations on-link? It only needs to know it's IPv6 
address and how to reach the router, nothing more. I don't see any 
theoretical or practical MUST requirement for an on-link prefix.

> I'm not quite sure which 4.1 you're referring to. Point 1. of section 4 
> of RFC5942?

Yes.

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

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Mar  6 02:08:25 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E7153A6968 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 02:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TDodfUwJbMTx for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 02:08:24 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id B21BA3A691C for <ipv6@ietf.org>; Sun,  6 Mar 2011 02:08:24 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PwAtz-0000fP-8c; Sun, 06 Mar 2011 20:39:27 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 642975355C; Sun,  6 Mar 2011 20:39:26 +1030 (CST)
Date: Sun, 6 Mar 2011 20:39:26 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110306203926.365cfb9b@opy.nosense.org>
In-Reply-To: <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se> <20110306195358.1d47b424@opy.nosense.org> <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 10:08:25 -0000

On Sun, 6 Mar 2011 10:47:06 +0100 (CET)
Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Sun, 6 Mar 2011, Mark Smith wrote:
> 
> > The PIO isn't to make DHCPv6 work, it is to inform the end-host of what
> > destinations are onlink. Here is what RFC5942 says -
> 
> Why does it need destinations on-link? It only needs to know it's IPv6 
> address and how to reach the router, nothing more. I don't see any 
> theoretical or practical MUST requirement for an on-link prefix.
> 

I don't think I said an on-link prefix was required. All I have ever
said is that, as per the RFC5942, if you want to have an on-link
prefix, you must announce it in a PIO (without the A bit if you don't
want it to be used for SLAAC). Steinar gave an example which could
imply that wasn't the case, but his example was actually one where an
on-link prefix wasn't required. IOW, his example didn't disprove my
statement, it only showed that there are some situations where no PIO
announced prefix has a use case - where all destinations are required
to be considered off-link. 


> > I'm not quite sure which 4.1 you're referring to. Point 1. of section 4 
> > of RFC5942?
> 
> Yes.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

From swmike@swm.pp.se  Sun Mar  6 02:39:03 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBDFB3A6AD7 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 02:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x25Kx6iZjlMp for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 02:39:03 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id B984B3A6A5B for <ipv6@ietf.org>; Sun,  6 Mar 2011 02:39:02 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 832769C; Sun,  6 Mar 2011 11:40:12 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8263B9A; Sun,  6 Mar 2011 11:40:12 +0100 (CET)
Date: Sun, 6 Mar 2011 11:40:12 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <20110306203926.365cfb9b@opy.nosense.org>
Message-ID: <alpine.DEB.1.10.1103061135420.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se> <20110306195358.1d47b424@opy.nosense.org> <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se> <20110306203926.365cfb9b@opy.nosense.org>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 10:39:03 -0000

On Sun, 6 Mar 2011, Mark Smith wrote:

> I don't think I said an on-link prefix was required. All I have ever
> said is that, as per the RFC5942, if you want to have an on-link
> prefix, you must announce it in a PIO (without the A bit if you don't
> want it to be used for SLAAC).

You said:

> I don't think that will always work. The PIO is needed to indicate to
> end-nodes what the onlink prefix(es) are, as per RFC5942.

I interpreted your use of "needed" as "required".

> Steinar gave an example which could imply that wasn't the case, but his 
> example was actually one where an on-link prefix wasn't required. IOW, 
> his example didn't disprove my statement, it only showed that there are 
> some situations where no PIO announced prefix has a use case - where all 
> destinations are required to be considered off-link.

Well, I interpreted your "I don't think that will always work" as saying 
that you thought what he said wouldn't work in all sitations. What 
situations were you thinking of that won't work?

As far as I can see, not having an on-link prefix means all traffic will 
be passing via the router, but that's not the same as "not working", it 
might just be suboptimal in some deployment scenarios and highly desired 
in others.

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

From sthaug@nethelp.no  Sun Mar  6 05:33:22 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE4043A67B5 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:33:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.932
X-Spam-Level: 
X-Spam-Status: No, score=-5.932 tagged_above=-999 required=5 tests=[AWL=0.667,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxK51BR06fNQ for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:33:21 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 40C3E3A67C1 for <ipv6@ietf.org>; Sun,  6 Mar 2011 05:33:20 -0800 (PST)
Received: (qmail 19523 invoked from network); 6 Mar 2011 13:34:31 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 6 Mar 2011 13:34:31 -0000
Date: Sun, 06 Mar 2011 14:34:31 +0100 (CET)
Message-Id: <20110306.143431.71134115.sthaug@nethelp.no>
To: ipng@69706e6720323030352d30312d31340a.nosense.org
Subject: Re: draft-yhb-6man-slaac-improvement-00
From: sthaug@nethelp.no
In-Reply-To: <20110306203926.365cfb9b@opy.nosense.org>
References: <20110306195358.1d47b424@opy.nosense.org> <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se> <20110306203926.365cfb9b@opy.nosense.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
Cc: narten@us.ibm.com, ipv6@ietf.org, brian.e.carpenter@gmail.com, yhb810501@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 13:33:22 -0000

> I don't think I said an on-link prefix was required. All I have ever
> said is that, as per the RFC5942, if you want to have an on-link
> prefix, you must announce it in a PIO (without the A bit if you don't
> want it to be used for SLAAC). Steinar gave an example which could
> imply that wasn't the case, but his example was actually one where an
> on-link prefix wasn't required. IOW, his example didn't disprove my
> statement, it only showed that there are some situations where no PIO
> announced prefix has a use case - where all destinations are required
> to be considered off-link. 

I have a similar use case where some information seems to be missing
in the RFCs. Or maybe I haven't read them in sufficient detail.

Assume I want to assign addresses to clients using DHCPv6, using only
a link-local next-hop. So my router is sending RA with M and O bits
set and no PIO. However, my client requests IA_NA, not IA_PD. The
question is:

*What netmask should the client use for the received address* in this
case?

The only obvious alternatives I can think of are /64 and /128, since
the IA_NA address doesn't include a prefix length. Can anybody point
me to RFCs which describe this?

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From swmike@swm.pp.se  Sun Mar  6 05:36:48 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DF1E3A67C3 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:36:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AH8jURwFRbDp for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:36:47 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 627333A67B5 for <ipv6@ietf.org>; Sun,  6 Mar 2011 05:36:46 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 482B29C; Sun,  6 Mar 2011 14:37:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 45DCE9A; Sun,  6 Mar 2011 14:37:56 +0100 (CET)
Date: Sun, 6 Mar 2011 14:37:56 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: sthaug@nethelp.no
Subject: Re: draft-yhb-6man-slaac-improvement-00
In-Reply-To: <20110306.143431.71134115.sthaug@nethelp.no>
Message-ID: <alpine.DEB.1.10.1103061435260.7942@uplift.swm.pp.se>
References: <20110306195358.1d47b424@opy.nosense.org> <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se> <20110306203926.365cfb9b@opy.nosense.org> <20110306.143431.71134115.sthaug@nethelp.no>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: narten@us.ibm.com, ipv6@ietf.org, brian.e.carpenter@gmail.com, yhb810501@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 13:36:48 -0000

On Sun, 6 Mar 2011, sthaug@nethelp.no wrote:

> *What netmask should the client use for the received address* in this
> case?

When we tested this, it used /128 which is the only sane behaviour I can 
see.

> The only obvious alternatives I can think of are /64 and /128, since
> the IA_NA address doesn't include a prefix length. Can anybody point
> me to RFCs which describe this?

I think the RFC I quoted already says this, if you don't get an on-link 
prefix, you're not allowed to make up an on-link prefix. If you get an 
address, you get that single address, nothing else.

Thus the behaviour I've seen is correct, you end up with a /128 pointing 
to yourself and a default route pointing to the router LL address, nothing 
else.

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

From brian@innovationslab.net  Sun Mar  6 05:55:51 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 673443A67C3 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skOrvY4mxL8b for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 05:55:50 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 2A62D3A67CF for <ipv6@ietf.org>; Sun,  6 Mar 2011 05:55:49 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 216988823E for <ipv6@ietf.org>; Sun,  6 Mar 2011 05:56:47 -0800 (PST)
Received: from clemson.local (c-76-100-105-215.hsd1.md.comcast.net [76.100.105.215]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id B4F00130002 for <ipv6@ietf.org>; Sun,  6 Mar 2011 05:56:56 -0800 (PST)
Message-ID: <4D7392A1.9080008@innovationslab.net>
Date: Sun, 06 Mar 2011 08:56:49 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Question about the link-local addresses
References: <F71A62696B354E2D8A892FCAAE467886@yhbPC>	<20110305144954.GB2782@odin.mars.sol> <1299364086.16769.34.camel@karl>
In-Reply-To: <1299364086.16769.34.camel@karl>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 13:55:51 -0000

On 3/5/11 5:28 PM, Karl Auer wrote:
> On Sat, 2011-03-05 at 09:49 -0500, Scott Schmit wrote:
>> I'm leaning toward the interpretation being "if you're in fe80::/10,
>> you're link local, but addresses outside fe80::/64 are reserved."
> 
> Linux treats link local addresses as being in a /64:
> 
> wlan0     [...]
>           inet6 addr: fe80::222:fbff:fe54:9b80/64 Scope:Link
>           [...]
> 
> While it may be that having bits set in that 54-bit region makes the
> address technically not a link local address, I think in practice you
> will see all addresses in fe80::/10 regarded as link local.

It is the FE80::/10 prefix that makes it link-local.  The FE80::/64 is
the currently documented formulation of a link-local unicast address
(and IANA properly reserves the FE80::/10 range).

Regards,
Brian

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sun Mar  6 13:13:33 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 623373A6889 for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 13:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4uerILdvxS-g for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 13:13:32 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 452603A6886 for <ipv6@ietf.org>; Sun,  6 Mar 2011 13:13:32 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PwLHf-0002lS-Vy; Mon, 07 Mar 2011 07:44:36 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 766EA5355C; Mon,  7 Mar 2011 07:44:35 +1030 (CST)
Date: Mon, 7 Mar 2011 07:44:35 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-yhb-6man-slaac-improvement-00
Message-ID: <20110307074435.37e121eb@opy.nosense.org>
In-Reply-To: <alpine.DEB.1.10.1103061135420.7942@uplift.swm.pp.se>
References: <201103050130.p251UeNE025668@cichlid.raleigh.ibm.com> <m2aah8x4kn.wl%randy@psg.com> <20110306181039.7728b3f4@opy.nosense.org> <20110306.090218.74700598.sthaug@nethelp.no> <20110306190309.04e96116@opy.nosense.org> <alpine.DEB.1.10.1103060950410.7942@uplift.swm.pp.se> <20110306195358.1d47b424@opy.nosense.org> <alpine.DEB.1.10.1103061045470.7942@uplift.swm.pp.se> <20110306203926.365cfb9b@opy.nosense.org> <alpine.DEB.1.10.1103061135420.7942@uplift.swm.pp.se>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, yhb810501@gmail.com, ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 Mar 2011 21:13:33 -0000

On Sun, 6 Mar 2011 11:40:12 +0100 (CET)
Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Sun, 6 Mar 2011, Mark Smith wrote:
> 
> > I don't think I said an on-link prefix was required. All I have ever
> > said is that, as per the RFC5942, if you want to have an on-link
> > prefix, you must announce it in a PIO (without the A bit if you don't
> > want it to be used for SLAAC).
> 
> You said:
> 
> > I don't think that will always work. The PIO is needed to indicate to
> > end-nodes what the onlink prefix(es) are, as per RFC5942.
> 
> I interpreted your use of "needed" as "required".
> 

As always context matters.

I was stating it in the common and usually unstated conext of the most
common case. Usually people want optimal traffic forwarding paths,
which on a multi-access, peer-to-peer layer 2 segment (e.g. an
Ethernet), means traffic is sent directly between attached nodes,
rather than "hair-pinned" or "trumbonned" through a default router. In
this common case, you'll need a PIO option with the L bit switched on,
to indicate the on-link prefix(es), regardless of the addressing
information and address prefix length that DHCPv6 supplies.

In the less common cases of "non-link-local prefix-free" unnumbered
links, you don't need a PIO. In the less common case of DHCPv6 only
(M+O in RA) with hair-pinned traffic paths via a router on a
multi-access, peer-to-peer layer 2 segent, you don't need a PIO. In the
less common case of SLAAC only (-M -O in RA), with hair-pinned traffic
paths via a router on a multi-access, peer-to-peer layer 2 segment,
you'll need a PIO, with the A bit on, and the L bit switched off.

> > Steinar gave an example which could imply that wasn't the case, but his 
> > example was actually one where an on-link prefix wasn't required. IOW, 
> > his example didn't disprove my statement, it only showed that there are 
> > some situations where no PIO announced prefix has a use case - where all 
> > destinations are required to be considered off-link.
> 
> Well, I interpreted your "I don't think that will always work" as saying 
> that you thought what he said wouldn't work in all sitations. What 
> situations were you thinking of that won't work?
> 
> As far as I can see, not having an on-link prefix means all traffic will 
> be passing via the router, but that's not the same as "not working", it 
> might just be suboptimal in some deployment scenarios and highly desired 
> in others.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

From brian.e.carpenter@gmail.com  Sun Mar  6 19:39:40 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D60793A68CF for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 19:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.442
X-Spam-Level: 
X-Spam-Status: No, score=-103.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEtzMhSXKiIo for <ipv6@core3.amsl.com>; Sun,  6 Mar 2011 19:39:40 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id E49853A68C7 for <ipv6@ietf.org>; Sun,  6 Mar 2011 19:39:39 -0800 (PST)
Received: by vws6 with SMTP id 6so3971362vws.31 for <ipv6@ietf.org>; Sun, 06 Mar 2011 19:40:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m+TepKv2w0qHFoIS0NQe9Cx94M1X8woD2rTLvptg/PM=; b=mODWE2/CfGkOtEdoMYkGt1XoOfYRURPeLgAhWndymsOd1g67SWUDzOMRFdzmtxhM6z mCopPGRmsIjTd2sBh/XsuHLjq58gyyo/4NlOLRFn9fRvTkdfOqguVpVSBiedHDI3IkZf EB4HLF16+pqv7tyRIinjoM8kTNRQDtQN2ZyBg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Z9dm4NGMan248M8i0IbNtUc4fY14JA2Acl8CmZcUsmiMFpw8IUKlkDp0uWd0jJ1PtU RjsHkOTFB7y6vB6IEYweffF8Bv2ZLI4KWI7r3DTWcut5wBRVe8zrJNVKV8k9drEwhr0Y aMaLPrveaWoxff8OznnpaC5gLIgCp6sA+O/FI=
Received: by 10.52.89.226 with SMTP id br2mr4593112vdb.265.1299469250546; Sun, 06 Mar 2011 19:40:50 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id n13sm414901vcr.41.2011.03.06.19.40.48 (version=SSLv3 cipher=OTHER); Sun, 06 Mar 2011 19:40:49 -0800 (PST)
Message-ID: <4D7453BE.1040606@gmail.com>
Date: Mon, 07 Mar 2011 16:40:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: Flow label drafts - updates, main open issue
References: <4D682228.7020304@gmail.com>
In-Reply-To: <4D682228.7020304@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 03:39:40 -0000

Hi,

I'm not hearing much in response to the open issue:

  Should we delete most of the text concerning stateful methods
  of handling the flow label?

In fact I'm not hearing much at all. Should I ask the WG Chairs
to conclude that everybody is OK with these drafts? That would
save us some time in Prague...

Regards
   Brian

On 2011-02-26 10:42, Brian E Carpenter wrote:
> Hi,
> 
> There are three updated flow label drafts:
> 
> 1. http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-3697bis-01.txt
> 
> This is the draft of the updated proposed standard for the flow label.
> The open issues discussed for the previous draft have been closed
> according to comments received - see the attached file for details.
> The authors believe that there is one big issue remaining:
> 
>   Should we delete most of the text concerning stateful methods
>   of handling the flow label? Basically that would mean deleting
>   Section 4 (and corresponding parts of the Security Considerations)
>   and making minor text adjustments elsewhere.
> 
> This would not mean that stateful methods are excluded for ever - it
> would just recognise that we are only sure of the stateless approach
> today.
> 
> 2. http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-update-03.txt
> 
> This draft is background rationale for the previous one, with minor
> updates to keep it in synch.
> 
> 3. http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-ecmp-01.txt
> 
> This is the ECMP/LAG draft updated according to WG Last Call comments.
> 
>    Brian + co-authors
> 
> 

From yhb810501@gmail.com  Mon Mar  7 03:06:28 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E748D3A6961 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 03:06:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.573
X-Spam-Level: 
X-Spam-Status: No, score=-0.573 tagged_above=-999 required=5 tests=[AWL=1.425,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_54=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x799icQDh8YQ for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 03:06:28 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 136CC3A6944 for <ipv6@ietf.org>; Mon,  7 Mar 2011 03:06:26 -0800 (PST)
Received: by vxg33 with SMTP id 33so4247999vxg.31 for <ipv6@ietf.org>; Mon, 07 Mar 2011 03:07:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=RBmEVEsxEHsfRLWA1OnCfGpluS3+3i5NIODNdQ70PPg=; b=l/u/KUK3ToOTfZrBJItq1ISVG+Yu8Yzgid5Gdzvv+Qka4CVeY1+59c5MmPoCcsVdXb JSB26CQIrbDL/4snytAdp9orDEtDKUYDsyE4TqJR3pPDLtXVV3XnZSD54Zom/sAbkage T+YapmeReWDkxNen1DkmlNKYv2jzdAua7ygOk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=EpQUB6Addn2OtJgFLhy1UTMBXgx7d9Ys4LXQ/dPV0bwr/EuKe5AmuIR8jiiGcmeHJ4 r2cbpUNRopt6sKG4vMwbixHgLPJaRSP9WQECAiJSnXHTkM81DpNVjn7zfQYPY9BZ+xtm 2/OD5dfQGW4MAp97+qgITazmd6eIGxiMp38/A=
MIME-Version: 1.0
Received: by 10.52.175.100 with SMTP id bz4mr1158103vdc.44.1299496059837; Mon, 07 Mar 2011 03:07:39 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Mon, 7 Mar 2011 03:07:39 -0800 (PST)
Date: Mon, 7 Mar 2011 19:07:39 +0800
Message-ID: <AANLkTikq5U==gCUvaHz4U+0GNyBGp0kHt=+evPMUF3Ou@mail.gmail.com>
Subject: draft-yhb-6man-ra-privacy-flag-01
From: huabing yu <yhb810501@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=bcaec5171e7f089e57049de2810e
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 11:06:29 -0000

--bcaec5171e7f089e57049de2810e
Content-Type: text/plain; charset=ISO-8859-1

Hi, every member of the 6man working group,good day!

I want to describe clearly what this draft is hoping to accomplish.
Please give me a chance.

In some sites, the network administrators want to deploy SLAAC, and just
permit the EUI-64 addresses to communicate with the Internet.They will
do as follows:

(1)Bind the MAC address and the EUI-64 address for each host on the access
switches.
Because the privacy addresses are varying, it is impossible to bind the MAC
address
and the privacy address.

(2)Disable the privacy addresses on each host.Why?Because the privacy
addresses
is preferred as the source of the outbound IPv6 traffic.Now it is difficult
to disable the privacy
addresses on all the hosts in the site,because:

(2.1)The network administrator has to notify every one to disable the
privacy
adrresses.In the enterprise with thousands of employees, it is very
difficult to
ensure that every one will see the notice.

(2.2)Many people are not familier with the host operation system, they don't
know
how to disable the privacy addresses.

So I advise to add the DisablePrivacy flag to the prefix-information
option.It is
helpful in the above scenario.

Thank you!

Yu Hua bing

--bcaec5171e7f089e57049de2810e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi, every member of the 6man working group,good day!</div><div><br></d=
iv><div>I want to describe clearly what this draft is hoping to accomplish.=
</div><div>Please give me a chance.</div><div><br></div><div>In some sites,=
 the network administrators want to deploy SLAAC, and just=A0</div>
<div>permit the EUI-64 addresses to communicate with the Internet.They will=
=A0</div><div>do as follows:</div><div><br></div><div>(1)Bind the MAC addre=
ss and the EUI-64 address for each host on the access switches.</div><div>
Because the privacy addresses are varying, it is impossible to bind the MAC=
 address=A0</div><div>and the privacy address.</div><div><br></div><div>(2)=
Disable the privacy addresses on each host.Why?Because the privacy addresse=
s=A0</div>
<div>is preferred as=A0the source of the outbound IPv6 traffic.Now it is di=
fficult to disable the privacy=A0</div><div>addresses on all the hosts in t=
he site,because:</div><div><br></div><div>(2.1)The network administrator ha=
s to notify every one to disable the privacy=A0</div>
<div>adrresses.In the enterprise with thousands of employees, it is very di=
fficult to=A0</div><div>ensure that every one will see the notice.</div><di=
v><br></div><div>(2.2)Many people are not familier with the host operation =
system, they don&#39;t know=A0</div>
<div>how to disable the privacy addresses.</div><div><br></div><div>So I ad=
vise to add the DisablePrivacy flag to the prefix-information option.It is=
=A0</div><div>helpful in the above scenario.</div><div><br></div><div>Thank=
 you!</div>
<div><br></div><div>Yu Hua bing</div>

--bcaec5171e7f089e57049de2810e--

From kauer@biplane.com.au  Mon Mar  7 03:35:30 2011
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 367923A6998 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 03:35:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ks5bGd0hUhCp for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 03:35:28 -0800 (PST)
Received: from syd-srv03.ezyreg.com (syd-srv03.ezyreg.com [117.58.251.4]) by core3.amsl.com (Postfix) with ESMTP id 6E2323A699C for <ipv6@ietf.org>; Mon,  7 Mar 2011 03:35:28 -0800 (PST)
Received: from igw.biplane.com.au ([203.26.128.2] helo=[192.168.1.202]) by syd-srv03.ezyreg.com with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from <kauer@biplane.com.au>) id 1PwYjw-0003m0-DM for ipv6@ietf.org; Mon, 07 Mar 2011 06:36:40 -0500
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
In-Reply-To: <AANLkTikq5U==gCUvaHz4U+0GNyBGp0kHt=+evPMUF3Ou@mail.gmail.com>
References: <AANLkTikq5U==gCUvaHz4U+0GNyBGp0kHt=+evPMUF3Ou@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-/aW7hftwqLUSeaErAhhf"
Date: Mon, 07 Mar 2011 22:40:45 +1100
Message-ID: <1299498045.16769.307.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - syd-srv03.ezyreg.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - biplane.com.au
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 11:35:30 -0000

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

On Mon, 2011-03-07 at 19:07 +0800, huabing yu wrote:
> (2)Disable the privacy addresses on each host.Why?Because the privacy
> addresses is preferred as the source of the outbound IPv6 traffic.

My reading of RFC3484 is that privacy addresses are NOT preferred, but
that it should be possible on a host to change that preference. See
"Rule 7" in Section 5 (on page 11):

   "Rule 7:  Prefer public addresses.
    If SA is a public address and SB is a temporary address, then
    prefer SA. Similarly, if SB is a public address and SA is a
    temporary address, then prefer SB.
    [...]
    Implementations MUST provide a mechanism allowing an
    application to reverse the sense of this preference and prefer
    temporary addresses over public addresses[...]"

Your idea may still be good, just possibly not for that reason.

Regards, K.

--=20
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (h)
http://www.biplane.com.au/kauer/                   +61-428-957160 (mob)

GPG fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687
Old fingerprint: B386 7819 B227 2961 8301 C5A9 2EBC 754B CD97 0156

--=-/aW7hftwqLUSeaErAhhf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEABECAAYFAk10xDUACgkQMAcU7Vc29ocmNwCguuk/60YVc4mwiXXzAofegCsJ
jDcAnjsK+HHkyJwFC2Y5cqWHFwsI5ad1
=9l4P
-----END PGP SIGNATURE-----

--=-/aW7hftwqLUSeaErAhhf--


From yhb810501@gmail.com  Mon Mar  7 04:12:01 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAE923A63EB for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 04:12:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level: 
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[AWL=1.940,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68a3qdYiQCvC for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 04:12:00 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id D16ED3A63D3 for <ipv6@ietf.org>; Mon,  7 Mar 2011 04:11:59 -0800 (PST)
Received: by vws6 with SMTP id 6so4250910vws.31 for <ipv6@ietf.org>; Mon, 07 Mar 2011 04:13:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=rtsrlVlTAmEABPspLpadaCZuR1rUmNRpgGwQrgkr9GI=; b=sclJ7QrVlVZGiqERnQtI6QATNiBxA38pgKr7FVwa9tWvLrEQZrU96PSoLnNw9M9w1H acG0dT06Dq89mZMKU5EHwLs3OFSvV7X39ZfMDoPGIbt9/R3fob2/k5X36IJG+bA7udFo 84mJLaCnUjs2tMX3c3OTevE/Q8gkzvtHjkviM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=DRxcDby6r2idxnSWoxM12jsZ9u/+mt0teHvzoaUlHo0JRH8IArl+Y34alHBypyMgR/ gVOl/0kElN96ens30VuIymyZbTb4B655u4GYbtAMVi2qqYYWVAVT0X+VckDF8pcwL4xM qfYtHzSCOXqZw5weg56rGKUFjER26Dl1UcJpU=
MIME-Version: 1.0
Received: by 10.52.88.98 with SMTP id bf2mr1467772vdb.284.1299499992834; Mon, 07 Mar 2011 04:13:12 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Mon, 7 Mar 2011 04:13:12 -0800 (PST)
Date: Mon, 7 Mar 2011 20:13:12 +0800
Message-ID: <AANLkTimusEb6GqaQJvpfx2woJZmv=q7mDdt0agL4rGJz@mail.gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: huabing yu <yhb810501@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=20cf307d03c47560c5049de36be6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 12:12:01 -0000

--20cf307d03c47560c5049de36be6
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

On Mon, 07 Mar 2011 22:40:45 +1100, Karl Auer wrote=A3=BA
> My reading of RFC3484 is that privacy addresses are NOT preferred, but
that it should be possible on a host to change that preference. See "Rule 7=
"
in Section 5 (on page 11):
>"Rule 7: Prefer public addresses. If SA is a public address and SB is a
temporary address, then prefer SA. Similarly, if SB is a public address and
SA is a temporary address, then
>prefer SB. [...] Implementations MUST provide a mechanism allowing an
application to reverse the sense of this preference and prefer temporary
addresses over public
>addresses[...]"

RFC3484 page 11, the last sentense:
Implementations for which privacy considerations outweigh these application
compatibility concerns MAY reverse the sense of this rule and by default
prefer temporary addresses over public addresses.
Windows OS prefers temporary addresses over public addresses by default.

Yu Hua bing

--20cf307d03c47560c5049de36be6
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<div>On Mon, 07 Mar 2011 22:40:45 +1100, Karl Auer wrote=A3=BA</div><div>&g=
t; My reading of RFC3484 is that privacy addresses are NOT preferred, but
that it should be possible on a host to change that preference. See
&quot;Rule 7&quot; in Section 5 (on page 11):&nbsp;</div><div>&gt;&quot;Rul=
e 7:  Prefer public addresses.
    If SA is a public address and SB is a temporary address, then
    prefer SA. Similarly, if SB is a public address and SA is a
    temporary address, then</div><div>&gt;prefer SB.
    [...]
    Implementations MUST provide a mechanism allowing an
    application to reverse the sense of this preference and prefer
    temporary addresses over public&nbsp;</div><div>&gt;addresses[...]&quot=
;</div><div><br></div><div>RFC3484 page 11, the last sentense:</div>Impleme=
ntations for which
   privacy considerations outweigh these application compatibility
   concerns MAY reverse the sense of this rule and by default prefer
   temporary addresses over public addresses.<div>Windows OS prefers&nbsp;t=
emporary addresses over public addresses by default.</div><div><br></div><d=
iv>Yu Hua bing</div><div><br></div>

--20cf307d03c47560c5049de36be6--

From ipng@69706e6720323030352d30312d31340a.nosense.org  Mon Mar  7 05:17:38 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DD8CE3A692C for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 05:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id INTJqpb+Tzi0 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 05:17:38 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 1ECEE3A67B4 for <ipv6@ietf.org>; Mon,  7 Mar 2011 05:17:38 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PwaKk-00080r-Us; Mon, 07 Mar 2011 23:48:46 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 777025355C; Mon,  7 Mar 2011 23:48:46 +1030 (CST)
Date: Mon, 7 Mar 2011 23:48:46 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: james woodyatt <jhw@apple.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Message-ID: <20110307234846.484650a4@opy.nosense.org>
In-Reply-To: <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com> <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, RJ Atkinson <rja.lists@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 13:17:38 -0000

On Fri, 04 Mar 2011 15:03:09 -0800
james woodyatt <jhw@apple.com> wrote:

> On Mar 4, 2011, at 10:55 AM, RJ Atkinson wrote:
> > 
> > As with audits of financial records, perfection is not required,
> > but a certain confidence interval IS desired/required/needed.
> 
> 
> It seems to me that proper accounting of which hosts are using what IPv6 addresses is probably better achieved by enhancing routers with the capability to journal their neighbor discovery cache insertions to a secure repository for offline review.  That combined with authorization logs from EAPOL ought to provide sufficient confidence for most civilian audits.  Am I missing something?
> 

+1

I think a router (or some other appropriate device) could be enhanced to
specifically listen for DAD attempts, insert the preliminary info
sourced from the DAD attempt(s) into it's neighbor cache, and then let
NUD determine if the address passes DAD. Once that occurs, it could
generate e.g. an SNMP trap towards an auditing device. When NUD detects
that the device has disappeared, another SNMP trap would occur.

Influencing behaviour via e.g. forcing DHCPv6 or trying to switch
off privacy addresses is a reasonable method to try to use to address
this issue, but ultimately you're trusting the device to behave as
specified. You really also need to be trying to detect when devices
don't behave. Financial accounting and auditing follows this model -
defined accounting procedures, and audits to detect when they haven't
been complied with.


Regards,
Mark.



From kawashimam@necat.nec.co.jp  Mon Mar  7 05:58:10 2011
Return-Path: <kawashimam@necat.nec.co.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99C353A69A5 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 05:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hFxJkJt9bZsH for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 05:58:09 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id 2D4453A6955 for <ipv6@ietf.org>; Mon,  7 Mar 2011 05:58:08 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.160]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p27DxMdD003128 for <ipv6@ietf.org>; Mon, 7 Mar 2011 22:59:22 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p27DxMI17643 for ipv6@ietf.org; Mon, 7 Mar 2011 22:59:22 +0900 (JST)
Received: from s254008.necat.nec.co.jp (s254008.necat.nec.co.jp [10.24.144.53]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id p27DxLGR021881 for <ipv6@ietf.org>; Mon, 7 Mar 2011 22:59:21 +0900 (JST)
Received: (from root@localhost) by s254008.necat.nec.co.jp (8.12.8/8.12.8) id p27DxBLZ006439 for ipv6@ietf.org; Mon, 7 Mar 2011 22:59:11 +0900
Received: from mail.necat.nec.co.jp [10.24.144.32]  by s254008.necat.nec.co.jp with ESMTP id YAD06384; Mon, 7 Mar 2011 22:59:11 +0900
Received: from siznecatg159185.trd.necat.nec.co.jp (EHLO siznecatg159185) ([10.3.159.185]) by mail.necat.nec.co.jp (MOS 3.10.4-GA FastPath queued) with ESMTP id BVA64216 (AUTH kawashimam); Mon, 07 Mar 2011 22:59:20 +0900 (JST)
To: ipv6@ietf.org
Subject: Question about IPv6 Address State
Message-Id: <20110307225920kawashimam@mail.necat.nec.co.jp>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@necat.nec.co.jp>
Date: Mon, 7 Mar 2011 22:59:20 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 13:58:10 -0000

Hi All,

I'd like to ask simple question. :-)
Can IPv6 address restore to Preferred State from Deprecated state?
I think it's possible to do. However, there is no clear description
 in RFC4861/4862. Is it written in other RFCs?

I know that one of the weird behavior. Please see the following links.

issue with SLAAC and deprecated IPv6 addresses on recent windows versions
http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html

Windows 7 does not restore autoconfigured IPv6 addresses to Preferred
 from Deprecated state (bug?) [originally from windows7 forum]
http://social.technet.microsoft.com/Forums/en-US/ipv6/thread/2e97220e-af61-48da-b2d4-f1d4ba321b1a/

In addtion, a address can become valid address such as a preferred address
 even if its valid lifetime expires during above situation.

If CPE implemented a requirement that is described L-13 in
 draft-ietf-v6ops-ipv6-cpe-router-09, it could happen.
If the prefix is changed to such as "prefix A --> prefix B --> prefix A",
 CPE can't recognize as a same prefix. Therefore, IPv6 address should
 restore to Preferred State from Deprecated state.

> L-13:  If the delegated prefix changes, i.e. the current prefix is
>        replaced with a new prefix without any overlapping time
>        period, then the IPv6 CE router MUST immediately advertise the
>        old prefix with a preferred lifetime of 0 and a valid lifetime
>        of 2 hours (which must be decremented in real time) in a
>        Router Advertisement message.

Sincerely,
Masanobu

$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Access Networks Engineering Department 
 Masanobu Kawashima                     
========================================


From jhw@apple.com  Mon Mar  7 07:47:38 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DFE423A67EE for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 07:47:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9CRrn2ElJbm for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 07:47:38 -0800 (PST)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 48F4E3A67E1 for <ipv6@ietf.org>; Mon,  7 Mar 2011 07:47:36 -0800 (PST)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 25D80D4A518D for <ipv6@ietf.org>; Mon,  7 Mar 2011 07:48:50 -0800 (PST)
X-AuditID: 11807134-b7c8cae000005108-91-4d74fe616938
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id C4.D3.20744.16EF47D4; Mon,  7 Mar 2011 07:48:50 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.20] ([75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHP002SP2LDIY60@elliott.apple.com> for ipv6@ietf.org; Mon, 07 Mar 2011 07:48:49 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: james woodyatt <jhw@apple.com>
In-reply-to: <D33AD322-77E3-43BC-8835-EA89B030E118@gmail.com>
Date: Mon, 07 Mar 2011 07:48:49 -0800
Message-id: <89483F06-C3E4-454F-9743-36CD5B26CC79@apple.com>
References: <ECE33859-92B0-4104-BB61-AD071166CC39@gmail.com> <alpine.DEB.1.10.1103041905120.7942@uplift.swm.pp.se> <18BACF96-F9DF-497F-979A-0DD1A44C502B@gmail.com> <DA26F5E7-793E-4660-A6BF-12115A266C23@apple.com> <20110307234846.484650a4@opy.nosense.org> <D33AD322-77E3-43BC-8835-EA89B030E118@gmail.com>
To: RJ Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: 6MAN <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 15:47:39 -0000

On Mar 7, 2011, at 6:08 AM, RJ Atkinson wrote:
> 
> Again, it is only audit, not full blown accounting or access control
> or what not.  Perfection is not a requirement here.
> 
> On Fri, 04 Mar 2011 15:03:09 -0800, james woodyatt <jhw@apple.com> wrote:
>> is probably better achieved by enhancing routers with the capability
>> to journal their neighbor discovery cache insertions to a secure
>> repository for offline review.  
> 
> That is tremendously complicated, and there is no requirement for
> a "secure" anything.  We're only talking about audit and confidence
> intervals, not malicious users or malicious hosts.

Then it's much simpler.  Just deploy the routers that have the capability I propose, but forget about SAVI and/or EAPOL and don't sweat the security of the journal logs so much.  There is no need to rev the specs to support the network audit you're talking about.  Just buy routers that support journaling.  Done.

Later, when the security of your audits are something you have to take more seriously, then you add the EAPOL and you secure the journal repository better.  It's incremental.  The "DisablePrivacy" flag adds nothing but additional complexity and transition friction.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From jhw@apple.com  Mon Mar  7 08:43:22 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A36D93A6908 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 08:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1EfDp1cVqN4 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 08:43:22 -0800 (PST)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 08A1A3A67F2 for <ipv6@ietf.org>; Mon,  7 Mar 2011 08:43:22 -0800 (PST)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id EC57AD4A82A1 for <ipv6@ietf.org>; Mon,  7 Mar 2011 08:44:35 -0800 (PST)
X-AuditID: 11807134-b7c8cae000005108-24-4d750b733d05
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id 9D.72.20744.37B057D4; Mon,  7 Mar 2011 08:44:35 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from 67-218-106-202.cust.layer42.net ([67.218.106.202]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHP0078N569NM00@elliott.apple.com> for ipv6@ietf.org; Mon, 07 Mar 2011 08:44:35 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
From: james woodyatt <jhw@apple.com>
In-reply-to: <AANLkTimusEb6GqaQJvpfx2woJZmv=q7mDdt0agL4rGJz@mail.gmail.com>
Date: Mon, 07 Mar 2011 08:44:29 -0800
Message-id: <CACAB40C-4E27-4B91-9236-D84416A746CC@apple.com>
References: <AANLkTimusEb6GqaQJvpfx2woJZmv=q7mDdt0agL4rGJz@mail.gmail.com>
To: huabing yu <yhb810501@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 16:43:22 -0000

On Mar 7, 2011, at 4:13 AM, huabing yu wrote:
> 
> Implementations for which privacy considerations outweigh these application compatibility concerns MAY reverse the sense of this rule and by default prefer temporary addresses over public addresses.

This.  Application compatibility concerns almost never trump privacy concerns.  And when they do, it's usually a source of shame.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From moore@network-heretics.com  Mon Mar  7 11:07:25 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083033A67F9 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 11:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jM5UmFQAEAbp for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 11:07:24 -0800 (PST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 052D53A67E2 for <ipv6@ietf.org>; Mon,  7 Mar 2011 11:07:24 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4DA462090E; Mon,  7 Mar 2011 14:08:37 -0500 (EST)
Received: from frontend1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 07 Mar 2011 14:08:37 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Ij/TOWY23qNT81tBeAfCIGCWRXY=; b=MoaJl0MQcfdPoLiRunew5uhlczVtusBKA6qhe7xWB+Qrdmx+l6pTpPwGfPuHhq6J79QJR7o1dJ59xd/pEYkfoHQb924suk8jAfDhEmKp18A7z9mmSP0BYcUq8Glix59dyht0CkTaqb9uToa7hP/CZuqy7uJXt0TM4IoMWxiXTKw=
X-Sasl-enc: Bt+THtKuV48MXFbKSJpoxr+07Lns347fjdkmz4rRxJZx 1299524916
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9D163400451; Mon,  7 Mar 2011 14:08:36 -0500 (EST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-01
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-32--904831192
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <CACAB40C-4E27-4B91-9236-D84416A746CC@apple.com>
Date: Mon, 7 Mar 2011 14:08:35 -0500
Message-Id: <9D959F11-039D-4B56-B8FA-5D72E9358311@network-heretics.com>
References: <AANLkTimusEb6GqaQJvpfx2woJZmv=q7mDdt0agL4rGJz@mail.gmail.com> <CACAB40C-4E27-4B91-9236-D84416A746CC@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 19:07:25 -0000

--Apple-Mail-32--904831192
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Mar 7, 2011, at 11:44 AM, james woodyatt wrote:

> On Mar 7, 2011, at 4:13 AM, huabing yu wrote:
>>=20
>> Implementations for which privacy considerations outweigh these =
application compatibility concerns MAY reverse the sense of this rule =
and by default prefer temporary addresses over public addresses.
>=20
> This.  Application compatibility concerns almost never trump privacy =
concerns.  And when they do, it's usually a source of shame.

It really depends on the nature of the application.  Some applications =
need relatively stable addresses; others don't.  There's nothing =
shameful about needing relatively stable addresses.

Keith


--Apple-Mail-32--904831192
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Mar 7, 2011, at 11:44 AM, james woodyatt wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
Mar 7, 2011, at 4:13 AM, huabing yu wrote:<br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Implementations =
for which privacy considerations outweigh these application =
compatibility concerns MAY reverse the sense of this rule and by default =
prefer temporary addresses over public =
addresses.<br></blockquote><br>This. &nbsp;Application compatibility =
concerns almost never trump privacy concerns. &nbsp;And when they do, =
it's usually a source of shame.<font class=3D"Apple-style-span" =
color=3D"#000000"><font class=3D"Apple-style-span" =
color=3D"#144FAE"><br></font></font></div></blockquote><br></div><div>It =
really depends on the nature of the application. &nbsp;Some applications =
need relatively stable addresses; others don't. &nbsp;There's nothing =
shameful about needing relatively stable =
addresses.</div><div><br></div><div>Keith</div><div><br></div></body></htm=
l>=

--Apple-Mail-32--904831192--

From shemant@cisco.com  Mon Mar  7 11:59:00 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A56C13A6407 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 11:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.643
X-Spam-Level: 
X-Spam-Status: No, score=-10.643 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbO+bewcXgAZ for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 11:58:59 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 1EDD73A63D3 for <ipv6@ietf.org>; Mon,  7 Mar 2011 11:58:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=4502; q=dns/txt; s=iport; t=1299528013; x=1300737613; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=tLM9bZxJtedp4t7SZWAzfG/RXkdEDTzePEi+dYkti+M=; b=F4UPDSaprwnJkoniuOdYZx9kusDS94S61mbPgRurwCeZxH9isKkQmTsq mVzRkIKFKtISRELXrh6+RSkxmP3KP7z7g2mntaQJyL69ShbzBmYFWzV/Q JhoRI3c901mYuKiDmatVnz2tI3vPObQqLzKore7F+v0uolu15KAJ8KP9K g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvoAAE3IdE2tJV2Z/2dsb2JhbACEK5Ngjkd0oi2LBwGQboEkgV+CXwSFHIpd
X-IronPort-AV: E=Sophos;i="4.62,278,1297036800"; d="scan'208";a="341756663"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-5.cisco.com with ESMTP; 07 Mar 2011 19:58:16 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p27JwGN1014721;  Mon, 7 Mar 2011 19:58:16 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 7 Mar 2011 13:58:16 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
x-cr-hashedpuzzle: AIxq CTrA FmvO GuMO Kjub KkRI LuEl PEkD PF3w PxCP QGGq QYqy QqEh SGFV UG7I UOnT; 2; aQBwAHYANgBAAGkAZQB0AGYALgBvAHIAZwA7AGsAYQB3AGEAcwBoAGkAbQBhAG0AQABuAGUAYwBhAHQALgBuAGUAYwAuAGMAbwAuAGoAcAA=; Sosha1_v1; 7; {CCEE77E5-9E83-4656-BBC6-6C11E7262C70}; cwBoAGUAbQBhAG4AdABAAGMAaQBzAGMAbwAuAGMAbwBtAA==; Mon, 07 Mar 2011 19:58:13 GMT; UgBFADoAIABRAHUAZQBzAHQAaQBvAG4AIABhAGIAbwB1AHQAIABJAFAAdgA2ACAAQQBkAGQAcgBlAHMAcwAgAFMAdABhAHQAZQA=
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
x-cr-puzzleid: {CCEE77E5-9E83-4656-BBC6-6C11E7262C70}
Content-class: urn:content-classes:message
Subject: RE: Question about IPv6 Address State
Date: Mon, 7 Mar 2011 13:58:13 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3EDA141@XMB-RCD-109.cisco.com>
In-Reply-To: <20110307225920kawashimam@mail.necat.nec.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question about IPv6 Address State
Thread-Index: Acvcz+MmCU9hbYmFTRa3cnrx2Ub61AAMSSgw
References: <20110307225920kawashimam@mail.necat.nec.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masanobu Kawashima" <kawashimam@necat.nec.co.jp>, <ipv6@ietf.org>
X-OriginalArrivalTime: 07 Mar 2011 19:58:16.0967 (UTC) FILETIME=[FFFD0970:01CBDD01]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 19:59:00 -0000

Masanobu,

I have snipped the following text from your test details at http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html between squared brackets.


[I deprecated an formerly (by RA) announced IPv6 prefix (let's say
2001:db8:1:2::/64) by  sending some RAs with PreferredLifetime=0 and
ValidLifetime=7200 and thereafter stopped sending RAs.
All windows machines behaved correctly and deprecated the addresses derived from
that prefix. Outgoing connections no longer used it as source address, but
incoming packets (like icmpv6 echo request) where answered due to the valid
"ValidLifetime" value. ;)

Then in the second step (after some minutes of testing) I tried to re-activate
the _same_ prefix (2001:db8:1:2::/64) by sending periodic RAs with
PreferredLifetime=86400 and ValidLifetime=43200. And here the weird things
began. On Vista and 7 the values for the "Lifetimes" where updated to the new
ones derived from the RA, but the prefix status didn't change. It still was
stuck in status "deprecated". Hence the still valid IPv6 addresses from that
prefix (2001:db8:1:2::/64) wasn't used as source addresses for new connections,
only old connections used it and incoming packets where answered.]

There is one problem with your test and that is why I suspect you see the behavior.  In the 2nd step your Preferred Lifetime value of 86400 is greater than Valid Lifetime of 43200 and thus a host can get confused.  Note from the following text from section 4.6.2 of RFC 4861 that the Preferred Lifetime cannot exceed the Valid Lifetime.

[Preferred Lifetime
                     32-bit unsigned integer.  The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred [ADDRCONF].  A value of all one bits (0xffffffff) represents infinity.  See [ADDRCONF]. Note that the value of this field MUST NOT exceed the Valid Lifetime field to avoid preferring addresses that are no longer valid.]

Also, a host is totally legal to use just the Valid Lifetime and thus I'd repeat your test with changing of Valid Lifetime and see what you see for behavior by the host.

Hemant

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Masanobu Kawashima
Sent: Monday, March 07, 2011 8:59 AM
To: ipv6@ietf.org
Subject: Question about IPv6 Address State


Hi All,

I'd like to ask simple question. :-)
Can IPv6 address restore to Preferred State from Deprecated state?
I think it's possible to do. However, there is no clear description
 in RFC4861/4862. Is it written in other RFCs?

I know that one of the weird behavior. Please see the following links.

issue with SLAAC and deprecated IPv6 addresses on recent windows versions
http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html

Windows 7 does not restore autoconfigured IPv6 addresses to Preferred
 from Deprecated state (bug?) [originally from windows7 forum]
http://social.technet.microsoft.com/Forums/en-US/ipv6/thread/2e97220e-af61-48da-b2d4-f1d4ba321b1a/

In addtion, a address can become valid address such as a preferred address
 even if its valid lifetime expires during above situation.

If CPE implemented a requirement that is described L-13 in
 draft-ietf-v6ops-ipv6-cpe-router-09, it could happen.
If the prefix is changed to such as "prefix A --> prefix B --> prefix A",
 CPE can't recognize as a same prefix. Therefore, IPv6 address should
 restore to Preferred State from Deprecated state.

> L-13:  If the delegated prefix changes, i.e. the current prefix is
>        replaced with a new prefix without any overlapping time
>        period, then the IPv6 CE router MUST immediately advertise the
>        old prefix with a preferred lifetime of 0 and a valid lifetime
>        of 2 hours (which must be decremented in real time) in a
>        Router Advertisement message.

Sincerely,
Masanobu

$B!q(J(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Access Networks Engineering Department 
 Masanobu Kawashima                     
========================================

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

From suresh.krishnan@ericsson.com  Mon Mar  7 12:03:20 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E864C3A635F for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 12:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.412
X-Spam-Level: 
X-Spam-Status: No, score=-102.412 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzM3Fz3I0-O8 for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 12:03:20 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 847B33A677E for <ipv6@ietf.org>; Mon,  7 Mar 2011 12:03:08 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p27K2pYi008565; Mon, 7 Mar 2011 14:04:21 -0600
Received: from [142.133.10.107] (147.117.20.213) by eusaamw0712.eamcs.ericsson.se (147.117.20.182) with Microsoft SMTP Server id 8.2.234.1; Mon, 7 Mar 2011 15:04:08 -0500
Message-ID: <4D7539D2.4090102@ericsson.com>
Date: Mon, 7 Mar 2011 15:02:26 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Masanobu Kawashima <kawashimam@necat.nec.co.jp>
Subject: Re: Question about IPv6 Address State
References: <20110307225920kawashimam@mail.necat.nec.co.jp>
In-Reply-To: <20110307225920kawashimam@mail.necat.nec.co.jp>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 20:03:21 -0000

Hi Kawashima-san,

On 11-03-07 08:59 AM, Masanobu Kawashima wrote:
> Hi All,
> 
> I'd like to ask simple question. :-)
> Can IPv6 address restore to Preferred State from Deprecated state?
> I think it's possible to do. However, there is no clear description
>  in RFC4861/4862. Is it written in other RFCs?

Yes. It is possible. Please refer to bullet e) in Section 5.5.3 of
RFC4862 on RA processing which states

"If the advertised prefix is equal to the prefix of an address
 configured by stateless autoconfiguration in the list, the
 preferred lifetime of the address is reset to the Preferred
 Lifetime in the received advertisement."

This should give you the effect you are looking for.

Thanks
Suresh

From Internet-Drafts@ietf.org  Mon Mar  7 15:15:04 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82C663A6809; Mon,  7 Mar 2011 15:15:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-4f+8ziLXik; Mon,  7 Mar 2011 15:15:03 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CB1928C0FB; Mon,  7 Mar 2011 15:15:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-udpchecksums-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110307231502.3672.1019.idtracker@localhost>
Date: Mon, 07 Mar 2011 15:15:02 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 Mar 2011 23:15:04 -0000

--NextPart

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


	Title           : UDP Checksums for Tunneled Packets
	Author(s)       : M. Eubanks
	Filename        : draft-ietf-6man-udpchecksums-00.txt
	Pages           : 11
	Date            : 2011-03-07

We address the problem of computing the UDP checksum on tunneling
IPv6 packets when using lightweight tunneling protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-udpchecksums-00.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-udpchecksums-00.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-07150945.I-D@ietf.org>


--NextPart--

From kawashimam@necat.nec.co.jp  Mon Mar  7 16:55:31 2011
Return-Path: <kawashimam@necat.nec.co.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 297043A69CC for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 16:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i9Zx91sUApWS for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 16:55:29 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id 9D91E3A69D0 for <ipv6@ietf.org>; Mon,  7 Mar 2011 16:55:29 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.197]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p280uhG5018866 for <ipv6@ietf.org>; Tue, 8 Mar 2011 09:56:43 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p280uhl23863 for ipv6@ietf.org; Tue, 8 Mar 2011 09:56:43 +0900 (JST)
Received: from s254008.necat.nec.co.jp (s254008.necat.nec.co.jp [10.24.144.53]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id p280ugph018246 for <ipv6@ietf.org>; Tue, 8 Mar 2011 09:56:43 +0900 (JST)
Received: (from root@localhost) by s254008.necat.nec.co.jp (8.12.8/8.12.8) id p280uU2t015560 for ipv6@ietf.org; Tue, 8 Mar 2011 09:56:30 +0900
Received: from mail.necat.nec.co.jp [10.24.144.32]  by s254008.necat.nec.co.jp with ESMTP id KAF14927; Tue, 8 Mar 2011 09:56:30 +0900
Received: from siznecatg159185.trd.necat.nec.co.jp (EHLO siznecatg159185) ([10.3.159.185]) by mail.necat.nec.co.jp (MOS 3.10.4-GA FastPath queued) with ESMTP id BVA84229 (AUTH kawashimam); Tue, 08 Mar 2011 09:56:42 +0900 (JST)
To: ipv6@ietf.org
Subject: RE: Question about IPv6 Address State
In-reply-to: <5B6B2B64C9FE2A489045EEEADDAFF2C3EDA141@XMB-RCD-109.cisco.com>
References: <5B6B2B64C9FE2A489045EEEADDAFF2C3EDA141@XMB-RCD-109.cisco.com>
Message-Id: <20110308095642kawashimam@mail.necat.nec.co.jp>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@necat.nec.co.jp>
Date: Tue, 8 Mar 2011 09:56:42 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 00:55:31 -0000

Hi Hemant,

Thank you for your comment. I agree with you.

But I should have added following link.
http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002732.html

I am sorry for the confusion.

Sincerely,
Masanobu


>Masanobu,
>
>I have snipped the following text from your test details at http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html between squared brackets.
>
>
>[I deprecated an formerly (by RA) announced IPv6 prefix (let's say
>2001:db8:1:2::/64) by  sending some RAs with PreferredLifetime=0 and
>ValidLifetime=7200 and thereafter stopped sending RAs.
>All windows machines behaved correctly and deprecated the addresses derived from
>that prefix. Outgoing connections no longer used it as source address, but
>incoming packets (like icmpv6 echo request) where answered due to the valid
>"ValidLifetime" value. ;)
>
>Then in the second step (after some minutes of testing) I tried to re-activate
>the _same_ prefix (2001:db8:1:2::/64) by sending periodic RAs with
>PreferredLifetime=86400 and ValidLifetime=43200. And here the weird things
>began. On Vista and 7 the values for the "Lifetimes" where updated to the new
>ones derived from the RA, but the prefix status didn't change. It still was
>stuck in status "deprecated". Hence the still valid IPv6 addresses from that
>prefix (2001:db8:1:2::/64) wasn't used as source addresses for new connections,
>only old connections used it and incoming packets where answered.]
>
>There is one problem with your test and that is why I suspect you see the behavior.  In the 2nd step your Preferred Lifetime value of 86400 is greater than Valid Lifetime of 43200 and thus a host can get confused.  Note from the following text from section 4.6.2 of RFC 4861 that the Preferred Lifetime cannot exceed the Valid Lifetime.
>
>[Preferred Lifetime
>                     32-bit unsigned integer.  The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred [ADDRCONF].  A value of all one bits (0xffffffff) represents infinity.  See [ADDRCONF]. Note that the value of this field MUST NOT exceed the Valid Lifetime field to avoid preferring addresses that are no longer valid.]
>
>Also, a host is totally legal to use just the Valid Lifetime and thus I'd repeat your test with changing of Valid Lifetime and see what you see for behavior by the host.
>
>Hemant
>
>-----Original Message-----
>From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Masanobu Kawashima
>Sent: Monday, March 07, 2011 8:59 AM
>To: ipv6@ietf.org
>Subject: Question about IPv6 Address State
>
>
>Hi All,
>
>I'd like to ask simple question. :-)
>Can IPv6 address restore to Preferred State from Deprecated state?
>I think it's possible to do. However, there is no clear description
> in RFC4861/4862. Is it written in other RFCs?
>
>I know that one of the weird behavior. Please see the following links.
>
>issue with SLAAC and deprecated IPv6 addresses on recent windows versions
>http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html
>
>Windows 7 does not restore autoconfigured IPv6 addresses to Preferred
> from Deprecated state (bug?) [originally from windows7 forum]
>http://social.technet.microsoft.com/Forums/en-US/ipv6/thread/2e97220e-af61-48da-b2d4-f1d4ba321b1a/
>
>In addtion, a address can become valid address such as a preferred address
> even if its valid lifetime expires during above situation.
>
>If CPE implemented a requirement that is described L-13 in
> draft-ietf-v6ops-ipv6-cpe-router-09, it could happen.
>If the prefix is changed to such as "prefix A --> prefix B --> prefix A",
> CPE can't recognize as a same prefix. Therefore, IPv6 address should
> restore to Preferred State from Deprecated state.
>
>> L-13:  If the delegated prefix changes, i.e. the current prefix is
>>        replaced with a new prefix without any overlapping time
>>        period, then the IPv6 CE router MUST immediately advertise the
>>        old prefix with a preferred lifetime of 0 and a valid lifetime
>>        of 2 hours (which must be decremented in real time) in a
>>        Router Advertisement message.
>
>Sincerely,
>Masanobu
>
>$B!q(B(._.)
>========================================
> NEC AccessTechnica, Ltd.               
> Access Networks Engineering Department 
> Masanobu Kawashima                     
>========================================
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------

$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Access Networks Engineering Department 
 Masanobu Kawashima                     
========================================


From kawashimam@necat.nec.co.jp  Mon Mar  7 16:56:50 2011
Return-Path: <kawashimam@necat.nec.co.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 296683A67EE for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 16:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMorwbLUty4m for <ipv6@core3.amsl.com>; Mon,  7 Mar 2011 16:56:49 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id 3CA4B3A685B for <ipv6@ietf.org>; Mon,  7 Mar 2011 16:56:49 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.195]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p280w3RV020108 for <ipv6@ietf.org>; Tue, 8 Mar 2011 09:58:03 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p280w3I28235 for ipv6@ietf.org; Tue, 8 Mar 2011 09:58:03 +0900 (JST)
Received: from s254008.necat.nec.co.jp (s254008.necat.nec.co.jp [10.24.144.53]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id p280w2ED019270 for <ipv6@ietf.org>; Tue, 8 Mar 2011 09:58:02 +0900 (JST)
Received: (from root@localhost) by s254008.necat.nec.co.jp (8.12.8/8.12.8) id p280vovw016365 for ipv6@ietf.org; Tue, 8 Mar 2011 09:57:50 +0900
Received: from mail.necat.nec.co.jp [10.24.144.32]  by s254008.necat.nec.co.jp with ESMTP id KAB16359; Tue, 8 Mar 2011 09:57:50 +0900
Received: from siznecatg159185.trd.necat.nec.co.jp (EHLO siznecatg159185) ([10.3.159.185]) by mail.necat.nec.co.jp (MOS 3.10.4-GA FastPath queued) with ESMTP id BVA84369 (AUTH kawashimam); Tue, 08 Mar 2011 09:58:02 +0900 (JST)
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: Question about IPv6 Address State
In-reply-to: <4D7539D2.4090102@ericsson.com>
Message-Id: <20110308095802kawashimam@mail.necat.nec.co.jp>
References: <4D7539D2.4090102@ericsson.com>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@necat.nec.co.jp>
Date: Tue, 8 Mar 2011 09:58:02 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 00:56:50 -0000

Hi Suresh,

Thank you for your comment.

But Windows Vista and 7 are correctly updating preferred lifetime. :-)
(i.e. It conforms to Section 5.5.3 of RFC4862.)

The problem is that Windows Vista and 7 don't restore to "Preferred"
 from "Deprecated".

Please see my question.

>Can IPv6 address restore to Preferred State from Deprecated state?
>I think it's possible to do. However, there is no clear description
> in RFC4861/4862. Is it written in other RFCs?

We have to define clearly in RFC?

Sincerely,
Masanobu


>Hi Kawashima-san,
>
>On 11-03-07 08:59 AM, Masanobu Kawashima wrote:
>> Hi All,
>> 
>> I'd like to ask simple question. :-)
>> Can IPv6 address restore to Preferred State from Deprecated state?
>> I think it's possible to do. However, there is no clear description
>>  in RFC4861/4862. Is it written in other RFCs?
>
>Yes. It is possible. Please refer to bullet e) in Section 5.5.3 of
>RFC4862 on RA processing which states
>
>"If the advertised prefix is equal to the prefix of an address
> configured by stateless autoconfiguration in the list, the
> preferred lifetime of the address is reset to the Preferred
> Lifetime in the received advertisement."
>
>This should give you the effect you are looking for.
>
>Thanks
>Suresh

$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Access Networks Engineering Department 
 Masanobu Kawashima                     
========================================


From HahnC@t-systems.com  Tue Mar  8 00:29:07 2011
Return-Path: <HahnC@t-systems.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A8873A6912 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 00:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEkaYeLvLWe8 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 00:29:02 -0800 (PST)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 0A8383A6904 for <ipv6@ietf.org>; Tue,  8 Mar 2011 00:29:01 -0800 (PST)
From: <HahnC@t-systems.com>
Received: from he101251.emea1.cds.t-internal.com ([10.125.92.154]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 08 Mar 2011 09:30:09 +0100
Received: from HE101453.emea1.cds.t-internal.com ([169.254.3.169]) by HE101251.emea1.cds.t-internal.com ([fe80::e428:2144:dcc5:bcce%15]) with mapi; Tue, 8 Mar 2011 09:29:57 +0100
To: <shemant@cisco.com>, <kawashimam@necat.nec.co.jp>
Date: Tue, 8 Mar 2011 09:29:54 +0100
Subject: RE: Question about IPv6 Address State
Thread-Topic: Question about IPv6 Address State
Thread-Index: Acvcz+MmCU9hbYmFTRa3cnrx2Ub61AAMSSgwABnmGoA=
Message-ID: <901586CA8F92D543BFFFD6E1122F5A36026B9EBCA8ED@HE101453.emea1.cds.t-internal.com>
References: <20110307225920kawashimam@mail.necat.nec.co.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C3EDA141@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3EDA141@XMB-RCD-109.cisco.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Mar 2011 00:38:17 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 08:29:07 -0000

Hello Hemant, Masanobu,

may I jump since the cited text was from a discussion I opened on ipv6-ops@=
cluenet.=20
Please see my comments inline.

>Masanobu,
>
>I have snipped the following text from your test details at=20
>http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718
>.html between squared brackets.
>
>
>[I deprecated an formerly (by RA) announced IPv6 prefix (let's say
>2001:db8:1:2::/64) by  sending some RAs with=20
>PreferredLifetime=3D0 and ValidLifetime=3D7200 and thereafter=20
>stopped sending RAs.
>All windows machines behaved correctly and deprecated the=20
>addresses derived from that prefix. Outgoing connections no=20
>longer used it as source address, but incoming packets (like=20
>icmpv6 echo request) where answered due to the valid=20
>"ValidLifetime" value. ;)
>
>Then in the second step (after some minutes of testing) I=20
>tried to re-activate the _same_ prefix (2001:db8:1:2::/64) by=20
>sending periodic RAs with PreferredLifetime=3D86400 and=20
>ValidLifetime=3D43200. And here the weird things began. On Vista=20
>and 7 the values for the "Lifetimes" where updated to the new=20
>ones derived from the RA, but the prefix status didn't change.=20
>It still was stuck in status "deprecated". Hence the still=20
>valid IPv6 addresses from that prefix (2001:db8:1:2::/64)=20
>wasn't used as source addresses for new connections, only old=20
>connections used it and incoming packets where answered.]
>
>There is one problem with your test and that is why I suspect=20
>you see the behavior.  In the 2nd step your Preferred Lifetime=20
>value of 86400 is greater than Valid Lifetime of 43200 and=20
>thus a host can get confused.  Note from the following text=20
>from section 4.6.2 of RFC 4861 that the Preferred Lifetime=20
>cannot exceed the Valid Lifetime.

In another message http://lists.cluenet.de/pipermail/ipv6-ops/2009-December=
/002732.html=20
I corrected myself since I confused the values of PreferredLT and ValidLT *=
only in the email* not in the tests.

I can confirm the decribed behaviour of Win7 since I repeated the tests in =
autumn 2010 with the same results.

cheers,
Christian

>
>[Preferred Lifetime
>                     32-bit unsigned integer.  The length of=20
>time in seconds (relative to the time the packet is sent) that=20
>addresses generated from the prefix via stateless address=20
>autoconfiguration remain preferred [ADDRCONF].  A value of all=20
>one bits (0xffffffff) represents infinity.  See [ADDRCONF].=20
>Note that the value of this field MUST NOT exceed the Valid=20
>Lifetime field to avoid preferring addresses that are no longer valid.]
>
>Also, a host is totally legal to use just the Valid Lifetime=20
>and thus I'd repeat your test with changing of Valid Lifetime=20
>and see what you see for behavior by the host.
>
>Hemant
>
>-----Original Message-----
>From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On=20
>Behalf Of Masanobu Kawashima
>Sent: Monday, March 07, 2011 8:59 AM
>To: ipv6@ietf.org
>Subject: Question about IPv6 Address State
>
>
>Hi All,
>
>I'd like to ask simple question. :-)
>Can IPv6 address restore to Preferred State from Deprecated state?
>I think it's possible to do. However, there is no clear=20
>description  in RFC4861/4862. Is it written in other RFCs?
>
>I know that one of the weird behavior. Please see the following links.
>
>issue with SLAAC and deprecated IPv6 addresses on recent=20
>windows versions=20
>http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html
>
>Windows 7 does not restore autoconfigured IPv6 addresses to=20
>Preferred  from Deprecated state (bug?) [originally from=20
>windows7 forum]=20
>http://social.technet.microsoft.com/Forums/en-US/ipv6/thread/2e
>97220e-af61-48da-b2d4-f1d4ba321b1a/
>
>In addtion, a address can become valid address such as a=20
>preferred address  even if its valid lifetime expires during=20
>above situation.
>
>If CPE implemented a requirement that is described L-13 in =20
>draft-ietf-v6ops-ipv6-cpe-router-09, it could happen.
>If the prefix is changed to such as "prefix A --> prefix B -->=20
>prefix A",  CPE can't recognize as a same prefix. Therefore,=20
>IPv6 address should  restore to Preferred State from Deprecated state.
>
>> L-13:  If the delegated prefix changes, i.e. the current prefix is
>>        replaced with a new prefix without any overlapping time
>>        period, then the IPv6 CE router MUST immediately advertise the
>>        old prefix with a preferred lifetime of 0 and a valid lifetime
>>        of 2 hours (which must be decremented in real time) in a
>>        Router Advertisement message.
>
>Sincerely,
>Masanobu
>
>=1B$B!q=1B(B(._.)
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> NEC AccessTechnica, Ltd.              =20
> Access Networks Engineering Department=20
> Masanobu Kawashima                    =20
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>--------------------------------------------------------------------
>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 kawashimam@necat.nec.co.jp  Tue Mar  8 02:26:38 2011
Return-Path: <kawashimam@necat.nec.co.jp>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95F8D3A6842 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 02:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.09
X-Spam-Level: 
X-Spam-Status: No, score=-100.09 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ADlmq+3OwJ2s for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 02:26:26 -0800 (PST)
Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.193]) by core3.amsl.com (Postfix) with ESMTP id D833F3A6835 for <ipv6@ietf.org>; Tue,  8 Mar 2011 02:26:19 -0800 (PST)
Received: from mailgate3.nec.co.jp ([10.7.69.193]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id p28ARYPr002247 for <ipv6@ietf.org>; Tue, 8 Mar 2011 19:27:34 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id p28ARY023331 for ipv6@ietf.org; Tue, 8 Mar 2011 19:27:34 +0900 (JST)
Received: from s254008.necat.nec.co.jp (s254008.necat.nec.co.jp [10.24.144.53]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id p28ARXGF008197 for <ipv6@ietf.org>; Tue, 8 Mar 2011 19:27:33 +0900 (JST)
Received: (from root@localhost) by s254008.necat.nec.co.jp (8.12.8/8.12.8) id p28ARJZL010533 for ipv6@ietf.org; Tue, 8 Mar 2011 19:27:19 +0900
Received: from mail.necat.nec.co.jp [10.24.144.32]  by s254008.necat.nec.co.jp with ESMTP id VAA10532; Tue, 8 Mar 2011 19:27:19 +0900
Received: from siznecatg159185.trd.necat.nec.co.jp (EHLO siznecatg159185) ([10.3.159.185]) by mail.necat.nec.co.jp (MOS 3.10.4-GA FastPath queued) with ESMTP id BVB39892 (AUTH kawashimam); Tue, 08 Mar 2011 19:27:33 +0900 (JST)
To: ipv6@ietf.org
Subject: RE: Question about IPv6 Address State
In-reply-to: <901586CA8F92D543BFFFD6E1122F5A36026B9EBCA8ED@HE101453.emea1.cds.t-internal.com>
Message-Id: <20110308192733kawashimam@mail.necat.nec.co.jp>
References: <901586CA8F92D543BFFFD6E1122F5A36026B9EBCA8ED@HE101453.emea1.cds.t-internal.com>
Mime-Version: 1.0
X-Mailer: StarOffice21/MailClient[4.65 Step9]
From: Masanobu Kawashima <kawashimam@necat.nec.co.jp>
Date: Tue, 8 Mar 2011 19:27:33 +0900
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 10:26:40 -0000
X-List-Received-Date: Tue, 08 Mar 2011 10:26:40 -0000

Hi Christian,

Thank you for your information.
I also got the same results last week.

>In another message http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002732.html 
>I corrected myself since I confused the values of PreferredLT and ValidLT *only in the email* not in the tests.
>
>I can confirm the decribed behaviour of Win7 since I repeated the tests in autumn 2010 with the same results.

Sincerely,
Masanobu


>Hello Hemant, Masanobu,
>
>may I jump since the cited text was from a discussion I opened on ipv6-ops@cluenet. 
>Please see my comments inline.
>
>>Masanobu,
>>
>>I have snipped the following text from your test details at 
>>http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718
>>.html between squared brackets.
>>
>>
>>[I deprecated an formerly (by RA) announced IPv6 prefix (let's say
>>2001:db8:1:2::/64) by  sending some RAs with 
>>PreferredLifetime=0 and ValidLifetime=7200 and thereafter 
>>stopped sending RAs.
>>All windows machines behaved correctly and deprecated the 
>>addresses derived from that prefix. Outgoing connections no 
>>longer used it as source address, but incoming packets (like 
>>icmpv6 echo request) where answered due to the valid 
>>"ValidLifetime" value. ;)
>>
>>Then in the second step (after some minutes of testing) I 
>>tried to re-activate the _same_ prefix (2001:db8:1:2::/64) by 
>>sending periodic RAs with PreferredLifetime=86400 and 
>>ValidLifetime=43200. And here the weird things began. On Vista 
>>and 7 the values for the "Lifetimes" where updated to the new 
>>ones derived from the RA, but the prefix status didn't change. 
>>It still was stuck in status "deprecated". Hence the still 
>>valid IPv6 addresses from that prefix (2001:db8:1:2::/64) 
>>wasn't used as source addresses for new connections, only old 
>>connections used it and incoming packets where answered.]
>>
>>There is one problem with your test and that is why I suspect 
>>you see the behavior.  In the 2nd step your Preferred Lifetime 
>>value of 86400 is greater than Valid Lifetime of 43200 and 
>>thus a host can get confused.  Note from the following text 
>>from section 4.6.2 of RFC 4861 that the Preferred Lifetime 
>>cannot exceed the Valid Lifetime.
>
>In another message http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002732.html 
>I corrected myself since I confused the values of PreferredLT and ValidLT *only in the email* not in the tests.
>
>I can confirm the decribed behaviour of Win7 since I repeated the tests in autumn 2010 with the same results.
>
>cheers,
>Christian
>
>>
>>[Preferred Lifetime
>>                     32-bit unsigned integer.  The length of 
>>time in seconds (relative to the time the packet is sent) that 
>>addresses generated from the prefix via stateless address 
>>autoconfiguration remain preferred [ADDRCONF].  A value of all 
>>one bits (0xffffffff) represents infinity.  See [ADDRCONF]. 
>>Note that the value of this field MUST NOT exceed the Valid 
>>Lifetime field to avoid preferring addresses that are no longer valid.]
>>
>>Also, a host is totally legal to use just the Valid Lifetime 
>>and thus I'd repeat your test with changing of Valid Lifetime 
>>and see what you see for behavior by the host.
>>
>>Hemant
>>
>>-----Original Message-----
>>From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On 
>>Behalf Of Masanobu Kawashima
>>Sent: Monday, March 07, 2011 8:59 AM
>>To: ipv6@ietf.org
>>Subject: Question about IPv6 Address State
>>
>>
>>Hi All,
>>
>>I'd like to ask simple question. :-)
>>Can IPv6 address restore to Preferred State from Deprecated state?
>>I think it's possible to do. However, there is no clear 
>>description  in RFC4861/4862. Is it written in other RFCs?
>>
>>I know that one of the weird behavior. Please see the following links.
>>
>>issue with SLAAC and deprecated IPv6 addresses on recent 
>>windows versions 
>>http://lists.cluenet.de/pipermail/ipv6-ops/2009-December/002718.html
>>
>>Windows 7 does not restore autoconfigured IPv6 addresses to 
>>Preferred  from Deprecated state (bug?) [originally from 
>>windows7 forum] 
>>http://social.technet.microsoft.com/Forums/en-US/ipv6/thread/2e
>>97220e-af61-48da-b2d4-f1d4ba321b1a/
>>
>>In addtion, a address can become valid address such as a 
>>preferred address  even if its valid lifetime expires during 
>>above situation.
>>
>>If CPE implemented a requirement that is described L-13 in  
>>draft-ietf-v6ops-ipv6-cpe-router-09, it could happen.
>>If the prefix is changed to such as "prefix A --> prefix B --> 
>>prefix A",  CPE can't recognize as a same prefix. Therefore, 
>>IPv6 address should  restore to Preferred State from Deprecated state.
>>
>>> L-13:  If the delegated prefix changes, i.e. the current prefix is
>>>        replaced with a new prefix without any overlapping time
>>>        period, then the IPv6 CE router MUST immediately advertise the
>>>        old prefix with a preferred lifetime of 0 and a valid lifetime
>>>        of 2 hours (which must be decremented in real time) in a
>>>        Router Advertisement message.
>>
>>Sincerely,
>>Masanobu
>>
>>$B!q(B(._.)
>>========================================
>> NEC AccessTechnica, Ltd.               
>> Access Networks Engineering Department 
>> Masanobu Kawashima                     
>>========================================
>>
>>--------------------------------------------------------------------
>>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
>>--------------------------------------------------------------------
>>

$B!q(B(._.)
========================================
 NEC AccessTechnica, Ltd.               
 Access Networks Engineering Department 
 Masanobu Kawashima                     
========================================


From yhb810501@gmail.com  Tue Mar  8 07:10:17 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77EA83A68A6 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 07:10:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukaFSj792Nq3 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 07:10:12 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 109593A67B7 for <ipv6@ietf.org>; Tue,  8 Mar 2011 07:10:11 -0800 (PST)
Received: by fxm15 with SMTP id 15so5637494fxm.31 for <ipv6@ietf.org>; Tue, 08 Mar 2011 07:11:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=iBwH1/HlRwokQCJuy6GFLcoCGgi8lcFoF+NFYk7CP88=; b=ebPLCalVoJDEZ3KbRU10Fob2l7tMJ9E8ffWcpAT6kz2w+1v8xkNZE55McYe29lxFX0 0Cw00eajBcf/vvtZ33YpdNLXCKlG5gUD0RYlBqhVdOVfyRcdOT4YicvdLqzpgX+znHvi jMMUUNKXPqEjsN+qNF1eaigG6EoJiIItaFKVw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=S1A7RTFX/azCLiWXRIvII7VIsEQ7kHQVE0KWG+p+mnW1giJISchLrvo4CwMmQNcxxf GOr7R3qk0RDtPxb12+vFJPCb+ch/4FPFwc6ngAKv/MxDHGUtEodRP7PLxQrmgranOXp8 hSkGUbOmYDgn75SNWUNU/PdI8wlVTv5WJYC4w=
Received: by 10.223.57.206 with SMTP id d14mr4212563fah.143.1299597081934; Tue, 08 Mar 2011 07:11:21 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id n1sm365140fam.40.2011.03.08.07.10.47 (version=SSLv3 cipher=OTHER); Tue, 08 Mar 2011 07:11:19 -0800 (PST)
Message-ID: <C7F01288723C414C99A2D999E63341C7@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <ipv6@ietf.org>
Subject: draft-yhb-6man-ra-privacy-flag-02
Date: Tue, 8 Mar 2011 23:09:46 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_009A_01CBDDE5.EA998510"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 15:10:17 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_009A_01CBDDE5.EA998510
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

   Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to=20
   be solved is as follows:

   In some sites, the network administrators want to deploy stateless=20
   address autoconfiguration, and just permit the hardware-derived=20
   addresses to communicate with the Internet.They will do as follows:

   (1)Bind the MAC address and the hardware-derived address for each=20
   host on the access switches.Because the temporary addresses are=20
   variable, it is impossible to bind the MAC address and the temporary=20
   address.

   (2)Disable the temporary addresses on each host.Why?Because the=20
   temporary addresses may be preferred as the source of the outbound=20
   IPv6 traffic.Now it is difficult to disable the temporary addresses=20
   on all the hosts in the site,because:

   (2.1)The network administrator has to notify every one to disable the =

   temporary adrresses.In the enterprise with thousands of employees, it
   is very difficult to ensure that every one will see the notice.

   (2.2)Many people are not familier with the host operation system,=20
   they don't know how to disable the temporary addresses.   =20
  =20
   This document tries to provide a solution to these network=20
   administrators,and they can specify whether the prefixes can be used
   to generate the temporary addresses.

  Now we can provide two solutions to the network administrators:
  (1) SLAAC + bind the MAC address and the  hardware-derived address on =
the access switch + disable the temporary addresses
  (2) DHCPv6 + DHCPv6 snooping
  The first solution is cheaper, and is easier to deploy.
------=_NextPart_000_009A_01CBDDE5.EA998510
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; Hi,&nbsp;I have submit=20
draft-yhb-6man-ra-privacy-flag-02. The problem to </FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; be solved is as =
follows:</FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp; &nbsp;In some sites, the network =
administrators=20
want to deploy stateless <BR>&nbsp;&nbsp; address autoconfiguration, and =
just=20
permit the hardware-derived <BR>&nbsp;&nbsp; addresses to communicate =
with the=20
Internet.They will do as follows:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; (1)Bind the MAC address and the=20
hardware-derived address for each <BR>&nbsp;&nbsp; host on the access=20
switches.Because the temporary addresses are <BR>&nbsp;&nbsp; variable, =
it is=20
impossible to bind the MAC address and the temporary <BR>&nbsp;&nbsp;=20
address.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; (2)Disable the temporary =
addresses on each=20
host.Why?Because the <BR>&nbsp;&nbsp; temporary addresses may be =
preferred as=20
the source of the outbound <BR>&nbsp;&nbsp; IPv6 traffic.Now it is =
difficult to=20
disable the temporary addresses <BR>&nbsp;&nbsp; on all the hosts in the =

site,because:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; (2.1)The network administrator =
has to=20
notify every one to disable the <BR>&nbsp;&nbsp; temporary adrresses.In =
the=20
enterprise with thousands of employees, it<BR>&nbsp;&nbsp; is very =
difficult to=20
ensure that every one will see the notice.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp;&nbsp; (2.2)Many people are not familier =
with the=20
host operation system, <BR>&nbsp;&nbsp; they don't know how to disable =
the=20
temporary addresses.&nbsp;&nbsp;&nbsp; <BR>&nbsp;&nbsp; <BR>&nbsp;&nbsp; =
This=20
document tries to provide a solution to these network <BR>&nbsp;&nbsp;=20
administrators,and they can specify whether the prefixes can be=20
used<BR>&nbsp;&nbsp; to generate the temporary addresses.</FONT></DIV>
<DIV><FONT face=3DCalibri></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri>&nbsp; Now we can provide two solutions to the =
network=20
administrators:</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp; (1) SLAAC + bind the MAC address and =
the&nbsp;=20
hardware-derived address on the access switch + disable the temporary=20
addresses</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp; (2) DHCPv6 + DHCPv6 =
snooping</FONT></DIV>
<DIV><FONT face=3DCalibri>&nbsp; The first solution is cheaper, and is =
easier to=20
deploy.</FONT></DIV></BODY></HTML>

------=_NextPart_000_009A_01CBDDE5.EA998510--


From brian@innovationslab.net  Tue Mar  8 07:34:41 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EB5F3A68F1 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 07:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1KY1zGCUcRg8 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 07:34:40 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id C33423A68EC for <ipv6@ietf.org>; Tue,  8 Mar 2011 07:34:39 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1C4A5882BD for <ipv6@ietf.org>; Tue,  8 Mar 2011 07:35:52 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 8524F130002 for <ipv6@ietf.org>; Tue,  8 Mar 2011 07:35:48 -0800 (PST)
Message-ID: <4D764CC8.6010805@innovationslab.net>
Date: Tue, 08 Mar 2011 10:35:36 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
References: <C7F01288723C414C99A2D999E63341C7@yhbPC>
In-Reply-To: <C7F01288723C414C99A2D999E63341C7@yhbPC>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 15:34:41 -0000

On 3/8/11 10:09 AM, Yu Hua bing wrote:
>    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to 
>    be solved is as follows:
> 
>    In some sites, the network administrators want to deploy stateless 
>    address autoconfiguration, and just permit the hardware-derived 
>    addresses to communicate with the Internet.They will do as follows:
> 
>    (1)Bind the MAC address and the hardware-derived address for each 
>    host on the access switches.Because the temporary addresses are 
>    variable, it is impossible to bind the MAC address and the temporary 
>    address.
> 
>    (2)Disable the temporary addresses on each host.Why?Because the 
>    temporary addresses may be preferred as the source of the outbound 
>    IPv6 traffic.Now it is difficult to disable the temporary addresses 
>    on all the hosts in the site,because:
> 
>    (2.1)The network administrator has to notify every one to disable the 
>    temporary adrresses.In the enterprise with thousands of employees, it
>    is very difficult to ensure that every one will see the notice.
> 
>    (2.2)Many people are not familier with the host operation system, 
>    they don't know how to disable the temporary addresses.    
>    
>    This document tries to provide a solution to these network 
>    administrators,and they can specify whether the prefixes can be used
>    to generate the temporary addresses.
> 
>   Now we can provide two solutions to the network administrators:
>   (1) SLAAC + bind the MAC address and the  hardware-derived address on the access switch + disable the temporary addresses
>   (2) DHCPv6 + DHCPv6 snooping
>   The first solution is cheaper, and is easier to deploy.

How is option 1 cheaper if you need all your hosts to be updated (at
some point) to recognize this new flag?  I understand the desire to
offer a SLAAC-based approach that mimics the type of control one would
have with DHCP-based address assignment, but the cost argument in this
case does not seem like a valid argument.

Another possible approach is to increase the preference of
public/permanent addresses in the address selection policy table (RFC
3484 and its update 3484bis). That would effectively preclude hosts from
using privacy addresses.  Of course, there is still the issue as to
*how* the network operator disseminates the policy table...

Regards,
Brian

From ipng@69706e6720323030352d30312d31340a.nosense.org  Tue Mar  8 12:47:49 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63DA73A635F for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 12:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPmGD38TaMo7 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 12:47:48 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 480933A6359 for <ipv6@ietf.org>; Tue,  8 Mar 2011 12:47:47 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Px3q1-0007vP-5U; Wed, 09 Mar 2011 07:19:01 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 777175355C; Wed,  9 Mar 2011 07:19:00 +1030 (CST)
Date: Wed, 9 Mar 2011 07:19:00 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Yu Hua bing" <yhb810501@gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Message-ID: <20110309071900.239a9585@opy.nosense.org>
In-Reply-To: <C7F01288723C414C99A2D999E63341C7@yhbPC>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 Mar 2011 20:47:49 -0000

On Tue, 8 Mar 2011 23:09:46 +0800
"Yu Hua bing" <yhb810501@gmail.com> wrote:

>    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to 
>    be solved is as follows:
> 
>    In some sites, the network administrators want to deploy stateless 
>    address autoconfiguration, and just permit the hardware-derived 
>    addresses to communicate with the Internet.They will do as follows:
> 
<snip>
> 
>   Now we can provide two solutions to the network administrators:
>   (1) SLAAC + bind the MAC address and the  hardware-derived address on the access switch + disable the temporary addresses
>   (2) DHCPv6 + DHCPv6 snooping
>   The first solution is cheaper, and is easier to deploy.

You'd be better off focusing on address usage and recording
mechanisms, which will not require changes to end-nodes, would be
compatible with all current addressing methods (i.e. SLAAC, DHCPv6,
static), and would also inherently accommodate any future
addressing methods (how ever unlikely that may be of occuring). That
will be the cheapest and most effective solution to your problem.

Neighbor caches, Duplicate Address Detection and Neighbor
Unreachability Detection create enough externally visible information
and maintain enough state to track appearance, continued existence and
the disappearance of nodes using IPv6. Develop a mechanism that
externally records the state transitions you're interested in, and I
think you'd have an adequate solution to your problem without having
develop additional IPv6 related addressing mechanisms and then having
to deploy them to end-nodes on a wide scale.
 
http://ndpmon.sourceforge.net/ is an example of the sorts of things
people are already using external observance of ND transactions for. It
can already record new station, new IPv6 Global Address and new
Link Local Address. It probably wouldn't be too hard to make it also
record when stations disappear. Ideally it'd be best to utilise the
underlying operating system's existing NUD mechanism to do this
tracking.

Regards,
Mark.

From yhb810501@gmail.com  Tue Mar  8 17:23:50 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D47283A67E6 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 17:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.712
X-Spam-Level: 
X-Spam-Status: No, score=-1.712 tagged_above=-999 required=5 tests=[AWL=1.886,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AXGZvRPlFCq for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 17:23:43 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 850603A67CC for <ipv6@ietf.org>; Tue,  8 Mar 2011 17:23:42 -0800 (PST)
Received: by vws6 with SMTP id 6so54612vws.31 for <ipv6@ietf.org>; Tue, 08 Mar 2011 17:24:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NWd0nj2cSa821l98vK5tp48rZiJxt6IyKGawfgRqdnc=; b=BBk+xUZo8FwBQk93goIW4rF1zOZp0S/Pa5XKtgRkzQ4VOyi3Hlyu3Q58z3vDYhrcwm Uyxo+MyICUtgkY6pcOXVbb1cXbubrsJOegKHsueGZAcWhsotVUaQn3U0ThXDMeleSZPN FMPnADDDfKYSwidUlNBZuaI7mtcUJ2NLKYnmE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZBqkG8SJXlGRQKJUiJN5hQVy7rnkzYjCXczHYREffqW/IaWdOJYwko9j54CBPztmp8 amSiFFVq6dZZwfT/PHFQ1Gvy36Y0PY5/KN3MyFP10W/E0eCMjw6siqYO1VS+jyPk7Xl2 dksisoON1kr3CSIxPSi+ywjgkjvszDBY8n8ZI=
MIME-Version: 1.0
Received: by 10.52.76.193 with SMTP id m1mr8510105vdw.204.1299633897836; Tue, 08 Mar 2011 17:24:57 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Tue, 8 Mar 2011 17:24:57 -0800 (PST)
In-Reply-To: <4D764CC8.6010805@innovationslab.net>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC> <4D764CC8.6010805@innovationslab.net>
Date: Wed, 9 Mar 2011 09:24:57 +0800
Message-ID: <AANLkTinuQHK-6cGB6JNYCaC=M5o3EJbMw5VTd39kLS+K@mail.gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
From: huabing yu <yhb810501@gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Content-Type: multipart/alternative; boundary=bcaec501603bd18f3e049e029898
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 01:23:50 -0000

--bcaec501603bd18f3e049e029898
Content-Type: text/plain; charset=ISO-8859-1

2011/3/8 Brian Haberman <brian@innovationslab.net>

> On 3/8/11 10:09 AM, Yu Hua bing wrote:
> >    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to
> >    be solved is as follows:
> >
> >    In some sites, the network administrators want to deploy stateless
> >    address autoconfiguration, and just permit the hardware-derived
> >    addresses to communicate with the Internet.They will do as follows:
> >
> >    (1)Bind the MAC address and the hardware-derived address for each
> >    host on the access switches.Because the temporary addresses are
> >    variable, it is impossible to bind the MAC address and the temporary
> >    address.
> >
> >    (2)Disable the temporary addresses on each host.Why?Because the
> >    temporary addresses may be preferred as the source of the outbound
> >    IPv6 traffic.Now it is difficult to disable the temporary addresses
> >    on all the hosts in the site,because:
> >
> >    (2.1)The network administrator has to notify every one to disable the
> >    temporary adrresses.In the enterprise with thousands of employees, it
> >    is very difficult to ensure that every one will see the notice.
> >
> >    (2.2)Many people are not familier with the host operation system,
> >    they don't know how to disable the temporary addresses.
> >
> >    This document tries to provide a solution to these network
> >    administrators,and they can specify whether the prefixes can be used
> >    to generate the temporary addresses.
> >
> >   Now we can provide two solutions to the network administrators:
> >   (1) SLAAC + bind the MAC address and the  hardware-derived address on
> the access switch + disable the temporary addresses
> >   (2) DHCPv6 + DHCPv6 snooping
> >   The first solution is cheaper, and is easier to deploy.
>
> How is option 1 cheaper if you need all your hosts to be updated (at
> some point) to recognize this new flag?  I understand the desire to
> offer a SLAAC-based approach that mimics the type of control one would
> have with DHCP-based address assignment, but the cost argument in this
> case does not seem like a valid argument.
>
> Another possible approach is to increase the preference of
> public/permanent addresses in the address selection policy table (RFC
> 3484 and its update 3484bis). That would effectively preclude hosts from
> using privacy addresses.  Of course, there is still the issue as to
> *how* the network operator disseminates the policy table...
>
> Regards,
> Brian
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

 We can't only think about now. We should think about the future.For IPv6,
the path is long.
  I think an idea should be adopted if it is helpful in the future.

 Your proposed approach has a flaw: if the application explicitely specifies
the privacy address
  as the source, the address selection policy table will not work. It is
best that the host disables
  the privacy addresses.

--bcaec501603bd18f3e049e029898
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/3/8 Brian Haberman <span dir=3D"ltr=
">&lt;<a href=3D"mailto:brian@innovationslab.net">brian@innovationslab.net<=
/a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class=3D"h5">On 3/8/11 10:09 AM, Yu Hua bing wrote:<br=
>
&gt; =A0 =A0Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The proble=
m to<br>
&gt; =A0 =A0be solved is as follows:<br>
&gt;<br>
&gt; =A0 =A0In some sites, the network administrators want to deploy statel=
ess<br>
&gt; =A0 =A0address autoconfiguration, and just permit the hardware-derived=
<br>
&gt; =A0 =A0addresses to communicate with the Internet.They will do as foll=
ows:<br>
&gt;<br>
&gt; =A0 =A0(1)Bind the MAC address and the hardware-derived address for ea=
ch<br>
&gt; =A0 =A0host on the access switches.Because the temporary addresses are=
<br>
&gt; =A0 =A0variable, it is impossible to bind the MAC address and the temp=
orary<br>
&gt; =A0 =A0address.<br>
&gt;<br>
&gt; =A0 =A0(2)Disable the temporary addresses on each host.Why?Because the=
<br>
&gt; =A0 =A0temporary addresses may be preferred as the source of the outbo=
und<br>
&gt; =A0 =A0IPv6 traffic.Now it is difficult to disable the temporary addre=
sses<br>
&gt; =A0 =A0on all the hosts in the site,because:<br>
&gt;<br>
&gt; =A0 =A0(2.1)The network administrator has to notify every one to disab=
le the<br>
&gt; =A0 =A0temporary adrresses.In the enterprise with thousands of employe=
es, it<br>
&gt; =A0 =A0is very difficult to ensure that every one will see the notice.=
<br>
&gt;<br>
&gt; =A0 =A0(2.2)Many people are not familier with the host operation syste=
m,<br>
&gt; =A0 =A0they don&#39;t know how to disable the temporary addresses.<br>
&gt;<br>
&gt; =A0 =A0This document tries to provide a solution to these network<br>
&gt; =A0 =A0administrators,and they can specify whether the prefixes can be=
 used<br>
&gt; =A0 =A0to generate the temporary addresses.<br>
&gt;<br>
&gt; =A0 Now we can provide two solutions to the network administrators:<br=
>
&gt; =A0 (1) SLAAC + bind the MAC address and the =A0hardware-derived addre=
ss on the access switch + disable the temporary addresses<br>
&gt; =A0 (2) DHCPv6 + DHCPv6 snooping<br>
&gt; =A0 The first solution is cheaper, and is easier to deploy.<br>
<br>
</div></div>How is option 1 cheaper if you need all your hosts to be update=
d (at<br>
some point) to recognize this new flag? =A0I understand the desire to<br>
offer a SLAAC-based approach that mimics the type of control one would<br>
have with DHCP-based address assignment, but the cost argument in this<br>
case does not seem like a valid argument.<br>
<br>
Another possible approach is to increase the preference of<br>
public/permanent addresses in the address selection policy table (RFC<br>
3484 and its update 3484bis). That would effectively preclude hosts from<br=
>
using privacy addresses. =A0Of course, there is still the issue as to<br>
*how* the network operator disseminates the policy table...<br>
<br>
Regards,<br>
Brian<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" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br></b=
lockquote><div><br></div><div>=A0We can&#39;t only think about now. We shou=
ld think about the future.For IPv6, the path is long.=A0</div><div>=A0=A0I =
think an idea should be adopted if it is helpful in the future.</div>
<div><br></div><div>=A0Your proposed approach has a flaw: if the applicatio=
n explicitely specifies the privacy address=A0</div><div>=A0=A0as the sourc=
e,=A0the address selection policy table will not work. It is best that the =
host disables=A0</div>
<div>=A0=A0the privacy addresses.</div></div><br>

--bcaec501603bd18f3e049e029898--

From yhb810501@gmail.com  Tue Mar  8 17:28:42 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1DED3A67E6 for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 17:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.448
X-Spam-Level: 
X-Spam-Status: No, score=-1.448 tagged_above=-999 required=5 tests=[AWL=1.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndrW51TM3WHU for <ipv6@core3.amsl.com>; Tue,  8 Mar 2011 17:28:41 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id B7C5B3A67CF for <ipv6@ietf.org>; Tue,  8 Mar 2011 17:28:40 -0800 (PST)
Received: by vxg33 with SMTP id 33so59275vxg.31 for <ipv6@ietf.org>; Tue, 08 Mar 2011 17:29:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=y1MiL8FSgcl1PQVZvTx5W9M2qO9B+b4fEDprZ2azimA=; b=sV1KXWhtPc1UXp9B0vOxBe3FPPNnJIFKPTim/tMvU4TEhmov3XX5A9+seQc80vysr2 uyGwNAbCp45cj9MsKpCBY+7OvXrD6Byn7opvgtZJ3TmU7+e+csdqfT8kOSzeNwEgjdnH jCe5cLxMRdNwZvazm/xJTOsV5xU8HQtL3OJCg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=AZmtLrSipAOHZAMlEej3aEGOL3jNDR5WGz+prZewaqj6jeq8Bdo7gJ2Dizl8Jw/wDL nWK+3O+qJnpkDrg3S/Vci0Oidn0uapAV1UlTh5E4hw/3B8SQgDNX25TyxtRoET03OP5D nYnSF2+Ekumdmp6Icect90Y/ccCyMsJjREiy0=
MIME-Version: 1.0
Received: by 10.52.0.226 with SMTP id 2mr5726643vdh.4.1299634194219; Tue, 08 Mar 2011 17:29:54 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Tue, 8 Mar 2011 17:29:54 -0800 (PST)
In-Reply-To: <20110309071900.239a9585@opy.nosense.org>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC> <20110309071900.239a9585@opy.nosense.org>
Date: Wed, 9 Mar 2011 09:29:54 +0800
Message-ID: <AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
From: huabing yu <yhb810501@gmail.com>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Content-Type: multipart/alternative; boundary=20cf3054abf77c0628049e02aa15
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 01:28:42 -0000

--20cf3054abf77c0628049e02aa15
Content-Type: text/plain; charset=ISO-8859-1

2011/3/9 Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>

> On Tue, 8 Mar 2011 23:09:46 +0800
> "Yu Hua bing" <yhb810501@gmail.com> wrote:
>
> >    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to
> >    be solved is as follows:
> >
> >    In some sites, the network administrators want to deploy stateless
> >    address autoconfiguration, and just permit the hardware-derived
> >    addresses to communicate with the Internet.They will do as follows:
> >
> <snip>
> >
> >   Now we can provide two solutions to the network administrators:
> >   (1) SLAAC + bind the MAC address and the  hardware-derived address on
> the access switch + disable the temporary addresses
> >   (2) DHCPv6 + DHCPv6 snooping
> >   The first solution is cheaper, and is easier to deploy.
>
> You'd be better off focusing on address usage and recording
> mechanisms, which will not require changes to end-nodes, would be
> compatible with all current addressing methods (i.e. SLAAC, DHCPv6,
> static), and would also inherently accommodate any future
> addressing methods (how ever unlikely that may be of occuring). That
> will be the cheapest and most effective solution to your problem.
>
> Neighbor caches, Duplicate Address Detection and Neighbor
> Unreachability Detection create enough externally visible information
> and maintain enough state to track appearance, continued existence and
> the disappearance of nodes using IPv6. Develop a mechanism that
> externally records the state transitions you're interested in, and I
> think you'd have an adequate solution to your problem without having
> develop additional IPv6 related addressing mechanisms and then having
> to deploy them to end-nodes on a wide scale.
>
> http://ndpmon.sourceforge.net/ is an example of the sorts of things
> people are already using external observance of ND transactions for. It
> can already record new station, new IPv6 Global Address and new
> Link Local Address. It probably wouldn't be too hard to make it also
> record when stations disappear. Ideally it'd be best to utilise the
> underlying operating system's existing NUD mechanism to do this
> tracking.
>
> Regards,
> Mark.
>

  In some sites, the network administrators want to prevent the host from
using any IPv6 address,
  like DHCPv6 plus DHCPv6 snooping. Your method can't.

--20cf3054abf77c0628049e02aa15
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/3/9 Mark Smith <span dir=3D"ltr">&l=
t;<a href=3D"mailto:ipng@69706e6720323030352d30312d31340a.nosense.org">ipng=
@69706e6720323030352d30312d31340a.nosense.org</a>&gt;</span><br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex;">
<div class=3D"im">On Tue, 8 Mar 2011 23:09:46 +0800<br>
&quot;Yu Hua bing&quot; &lt;<a href=3D"mailto:yhb810501@gmail.com">yhb81050=
1@gmail.com</a>&gt; wrote:<br>
<br>
&gt; =A0 =A0Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The proble=
m to<br>
&gt; =A0 =A0be solved is as follows:<br>
&gt;<br>
&gt; =A0 =A0In some sites, the network administrators want to deploy statel=
ess<br>
&gt; =A0 =A0address autoconfiguration, and just permit the hardware-derived=
<br>
&gt; =A0 =A0addresses to communicate with the Internet.They will do as foll=
ows:<br>
&gt;<br>
</div>&lt;snip&gt;<br>
<div class=3D"im">&gt;<br>
&gt; =A0 Now we can provide two solutions to the network administrators:<br=
>
&gt; =A0 (1) SLAAC + bind the MAC address and the =A0hardware-derived addre=
ss on the access switch + disable the temporary addresses<br>
&gt; =A0 (2) DHCPv6 + DHCPv6 snooping<br>
&gt; =A0 The first solution is cheaper, and is easier to deploy.<br>
<br>
</div>You&#39;d be better off focusing on address usage and recording<br>
mechanisms, which will not require changes to end-nodes, would be<br>
compatible with all current addressing methods (i.e. SLAAC, DHCPv6,<br>
static), and would also inherently accommodate any future<br>
addressing methods (how ever unlikely that may be of occuring). That<br>
will be the cheapest and most effective solution to your problem.<br>
<br>
Neighbor caches, Duplicate Address Detection and Neighbor<br>
Unreachability Detection create enough externally visible information<br>
and maintain enough state to track appearance, continued existence and<br>
the disappearance of nodes using IPv6. Develop a mechanism that<br>
externally records the state transitions you&#39;re interested in, and I<br=
>
think you&#39;d have an adequate solution to your problem without having<br=
>
develop additional IPv6 related addressing mechanisms and then having<br>
to deploy them to end-nodes on a wide scale.<br>
<br>
<a href=3D"http://ndpmon.sourceforge.net/" target=3D"_blank">http://ndpmon.=
sourceforge.net/</a> is an example of the sorts of things<br>
people are already using external observance of ND transactions for. It<br>
can already record new station, new IPv6 Global Address and new<br>
Link Local Address. It probably wouldn&#39;t be too hard to make it also<br=
>
record when stations disappear. Ideally it&#39;d be best to utilise the<br>
underlying operating system&#39;s existing NUD mechanism to do this<br>
tracking.<br>
<br>
Regards,<br>
<font color=3D"#888888">Mark.<br></font></blockquote><div><br></div><div>=
=A0=A0In some sites, the network administrators want to prevent the host fr=
om using any IPv6 address,=A0</div><div>=A0=A0like DHCPv6 plus DHCPv6 snoop=
ing.=A0Your method can&#39;t.</div>
</div><br>

--20cf3054abf77c0628049e02aa15--

From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Mar  9 01:17:20 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E68783A68D7 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 01:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.595
X-Spam-Level: 
X-Spam-Status: No, score=-1.595 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_72=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PwSEj5cLI5-m for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 01:17:20 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 1FC1E3A68D5 for <ipv6@ietf.org>; Wed,  9 Mar 2011 01:17:19 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxFXN-0001Zp-J5; Wed, 09 Mar 2011 19:48:33 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 1A18A5355C; Wed,  9 Mar 2011 19:48:33 +1030 (CST)
Date: Wed, 9 Mar 2011 19:48:32 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: huabing yu <yhb810501@gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Message-ID: <20110309194832.06bc1f6b@opy.nosense.org>
In-Reply-To: <AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC> <20110309071900.239a9585@opy.nosense.org> <AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 09:17:21 -0000

On Wed, 9 Mar 2011 09:29:54 +0800
huabing yu <yhb810501@gmail.com> wrote:

> 2011/3/9 Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
> 
> > On Tue, 8 Mar 2011 23:09:46 +0800
> > "Yu Hua bing" <yhb810501@gmail.com> wrote:
> >
> > >    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem to
> > >    be solved is as follows:
> > >
> > >    In some sites, the network administrators want to deploy stateless
> > >    address autoconfiguration, and just permit the hardware-derived
> > >    addresses to communicate with the Internet.They will do as follows:
> > >
> > <snip>
> > >
> > >   Now we can provide two solutions to the network administrators:
> > >   (1) SLAAC + bind the MAC address and the  hardware-derived address on
> > the access switch + disable the temporary addresses
> > >   (2) DHCPv6 + DHCPv6 snooping
> > >   The first solution is cheaper, and is easier to deploy.
> >
<snip>

> > Regards,
> > Mark.
> >
> 
>   In some sites, the network administrators want to prevent the host from
> using any IPv6 address,
>   like DHCPv6 plus DHCPv6 snooping. Your method can't.

So, looking at the text at the top of the draft (although this is from
the -01 version, as I can't seem to find the -02 one), where you
present your use case -


"when the network is in trouble,it is difficult to find out
which host is attacking the other hosts."

it seems your real and fundamental goal is to be able to track the
mappings between MAC addresses and corresponding IPv6 addresses. Since
privacy addresses naturally makes that harder, and the decision to use
that is in the control of the end-host, you think the way to achieve
that auditability is to provide a mechanism to suppress privacy them.

I think you should sit back and think about the problem some more. The
people who are likely to execute these attacks will have also have
a motive to (a) choose an operating system where the tools to execute
these attacks are more commonly available and (b) as that operating
system is likely to be an open source one, modify the kernel, or
install somebody else's kernel patch that ignores any "disable privacy"
addresses mechanisms you manage to get deployed. You can't completely
trust the end-host to follow mechanisms that aren't in its owner's
interests.

I think you'll be more successful at achieving your fundamental goal by
observing and recording their IPv6 address use rather than trying to
control it with mechanisms they have the ability to disable.

Regards,
Mark.









From ran.atkinson@gmail.com  Wed Mar  9 02:00:27 2011
Return-Path: <ran.atkinson@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAB7A3A68D9 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 02:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.2
X-Spam-Level: 
X-Spam-Status: No, score=-3.2 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWhtPjO5ZQAp for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 02:00:27 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 1C8B53A67F1 for <ipv6@ietf.org>; Wed,  9 Mar 2011 02:00:27 -0800 (PST)
Received: by vws6 with SMTP id 6so379615vws.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 02:01:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=I9AzFYVTYRO9AbyCYqiqeUADCmV2V8J7Zh0PigWRLLU=; b=luLSZdeil5GjNFpyivZ2LjuuEem2yAPs6SxYPYCtujOp3rKOuezpcRaBIqfjwcqqJv lLpdG1UnnHe5ghSNr/BDZzlI9biiqLvsHu8aeiw0glagXA3rj0OCDo9PCqXyQZ5jDu+S 9Wo8mQHIJpF0tF9zhh61r6qxJSNVVw7Owoafs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=QrwUJJZSBggw+oY/lcWTr9tH8v727nohhMQSW4887kx+ghk3FWnIZRauwbZp3fE8Mc ry1kRCVYsEuU4aWdabF0ynI4aOTSuiTvZuoPpFTZCPY/LI+weKqecFNo89ulNStlz37/ i3vzwohIcPRkGSB0OsUt5aWVEcf7WgHgZMvS8=
Received: by 10.52.90.109 with SMTP id bv13mr3592026vdb.237.1299664901076; Wed, 09 Mar 2011 02:01:41 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id q13sm336052vdu.5.2011.03.09.02.01.39 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2011 02:01:40 -0800 (PST)
From: Ran Atkinson <ran.atkinson@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-gont-6man-managing-privacy-extensions-00.txt
Date: Wed, 9 Mar 2011 05:01:39 -0500
Message-Id: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 10:00:28 -0000

=
<http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-exte=
nsions-00.txt>

I recommend that folks read the above draft.  I haven't seen the
I-D announcement get cross-posted to the IPv6 WG, perhaps due to
the volume of recent I-D postings, and the topic seems relevant.

Cheers !



From swmike@swm.pp.se  Wed Mar  9 03:15:53 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E3193A693A for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 03:15:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dN5vH0kwQ6+8 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 03:15:52 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 225F03A6936 for <ipv6@ietf.org>; Wed,  9 Mar 2011 03:15:51 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 30E019E; Wed,  9 Mar 2011 12:17:05 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 2DFC29C; Wed,  9 Mar 2011 12:17:05 +0100 (CET)
Date: Wed, 9 Mar 2011 12:17:05 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ran Atkinson <ran.atkinson@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
In-Reply-To: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>
Message-ID: <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 11:15:53 -0000

On Wed, 9 Mar 2011, Ran Atkinson wrote:

>
> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt>
>
> I recommend that folks read the above draft.  I haven't seen the
> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
> the volume of recent I-D postings, and the topic seems relevant.

I don't think it solves what it thinks it solves, but if this REALLY 
should be implemented, it's my initial thinking that the H flag should be 
a MUST demand to only have ONE and only one MAC-based IPv6 address 
according to EUI64. I would appreciate some reasoning in the draft why 
this was chosen as a SHOULD option.

I do not like the "disable Privacy"-flag thinking at all and I really 
oppose going with that solution.

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

From yhb810501@gmail.com  Wed Mar  9 04:18:15 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 563CD3A6993 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 04:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.576
X-Spam-Level: 
X-Spam-Status: No, score=-1.576 tagged_above=-999 required=5 tests=[AWL=1.022,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbMrOlnq6hKp for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 04:18:14 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 362143A696D for <ipv6@ietf.org>; Wed,  9 Mar 2011 04:18:14 -0800 (PST)
Received: by vxg33 with SMTP id 33so490620vxg.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 04:19:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=EThI6eLWqWR/VocZE5uq1JMgq+XkQ4O3gAaE9DrGV7Y=; b=QzuYnkfZaL1IJXOaEEcfS7/0XQnHGHs1ZrX9jkcCZNU1JCbEO33VkTDQmAnn4JobnB A0iyM7A0oCROc1u1q54vo3OVbEoCooPSxdgbKfVilVXrS7orC0CGbeywR9W5VV70gs4M 3N6WAqfa5SzYcp3AGJ7V/73rzD4BI5LzkMFaA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EV6CSv8yJ30uWIp7bKmxDdAd6EVguJ3elGyyBjPUAekdPdaENKqQL/wP58s4Xcxof8 rhgCIUz3dmS/MkYf2wKKGVnML6uhh6qGQfA1rMUjo5eTe0rP3M3qYPR42mqRkUkKB42x h75BPVyMgPILod9GAIvUdSDuDWxN3vUKiHXE0=
MIME-Version: 1.0
Received: by 10.52.70.200 with SMTP id o8mr2696306vdu.84.1299673168079; Wed, 09 Mar 2011 04:19:28 -0800 (PST)
Received: by 10.52.161.134 with HTTP; Wed, 9 Mar 2011 04:19:28 -0800 (PST)
In-Reply-To: <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
Date: Wed, 9 Mar 2011 20:19:28 +0800
Message-ID: <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: huabing yu <yhb810501@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=20cf3071c96081ecb4049e0bbdf0
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 12:18:15 -0000

--20cf3071c96081ecb4049e0bbdf0
Content-Type: text/plain; charset=ISO-8859-1

2011/3/9 Mikael Abrahamsson <swmike@swm.pp.se>

> On Wed, 9 Mar 2011, Ran Atkinson wrote:
>
>
>> <
>> http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt
>> >
>>
>> I recommend that folks read the above draft.  I haven't seen the
>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>> the volume of recent I-D postings, and the topic seems relevant.
>>
>
> I don't think it solves what it thinks it solves, but if this REALLY should
> be implemented, it's my initial thinking that the H flag should be a MUST
> demand to only have ONE and only one MAC-based IPv6 address according to
> EUI64. I would appreciate some reasoning in the draft why this was chosen as
> a SHOULD option.
>
> I do not like the "disable Privacy"-flag thinking at all and I really
> oppose going with that solution.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


(1)If "H" ("Hardware-derived addresses") flag is 1, it indicates that
the host SHOULD generate hardware-derived addresses, and doesn't
generate privacy addresses.
(2)If "H" ("Hardware-derived addresses") flag is 0, the author say that
this bit indicates that Privacy Extensions SHOULD be enabled
when configuring IPv6 addresses as a result of Stateless Address
Autoconfiguration,
*but many people will think that it indicates that the host doesn't
generate *
*hardware-derived addresses, and SHOULD generate privacy addresses. It may *
*result in a misunderstanding.*
*I think "DisablePrivacy" proposed by "draft-yhb-6man-ra-privacy-flag-01"*
*is better than "H",although some people don't like the problem to be
solved.*
*
*
*Yu Hua bing*

--20cf3071c96081ecb4049e0bbdf0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/3/9 Mikael Abrahamsson <span dir=3D=
"ltr">&lt;<a href=3D"mailto:swmike@swm.pp.se">swmike@swm.pp.se</a>&gt;</spa=
n><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Wed, 9 Mar 2011, Ran Atkinson wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&lt;<a href=3D"http://www.ietf.org/internet-drafts/draft-gont-6man-managing=
-privacy-extensions-00.txt" target=3D"_blank">http://www.ietf.org/internet-=
drafts/draft-gont-6man-managing-privacy-extensions-00.txt</a>&gt;<br>
<br>
I recommend that folks read the above draft. =A0I haven&#39;t seen the<br>
I-D announcement get cross-posted to the IPv6 WG, perhaps due to<br>
the volume of recent I-D postings, and the topic seems relevant.<br>
</blockquote>
<br></div>
I don&#39;t think it solves what it thinks it solves, but if this REALLY sh=
ould be implemented, it&#39;s my initial thinking that the H flag should be=
 a MUST demand to only have ONE and only one MAC-based IPv6 address accordi=
ng to EUI64. I would appreciate some reasoning in the draft why this was ch=
osen as a SHOULD option.<br>

<br>
I do not like the &quot;disable Privacy&quot;-flag thinking at all and I re=
ally oppose going with that solution.<br><font color=3D"#888888">
<br>
-- <br>
Mikael Abrahamsson =A0 =A0email: <a href=3D"mailto:swmike@swm.pp.se" target=
=3D"_blank">swmike@swm.pp.se</a></font><div><div></div><div class=3D"h5"><b=
r>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</div></div></blockquote></div><br><div><br></div><div><div>(1)If &quot;H&q=
uot; (&quot;Hardware-derived addresses&quot;) flag is 1, it indicates that<=
/div><div>the host SHOULD generate hardware-derived addresses, and doesn&#3=
9;t=A0</div>
<div>generate privacy addresses.</div><div>(2)If &quot;H&quot; (&quot;Hardw=
are-derived addresses&quot;) flag is 0, the author say that=A0</div><div>th=
is bit indicates that Privacy Extensions SHOULD be enabled=A0</div><div>whe=
n configuring IPv6 addresses as a result of Stateless Address Autoconfigura=
tion,</div>
<div><b>but many people will think that it indicates that the host doesn&#3=
9;t generate=A0</b></div><div><b>hardware-derived addresses, and SHOULD gen=
erate privacy addresses. It may=A0</b></div><div><b>result in a misundersta=
nding.</b></div>
<div><b>I think &quot;DisablePrivacy&quot; proposed by &quot;draft-yhb-6man=
-ra-privacy-flag-01&quot;</b></div><div><b>is better than &quot;H&quot;,alt=
hough some people don&#39;t like the problem to be solved.</b></div></div>
<div><b><br></b></div><div><b>Yu Hua bing</b></div>

--20cf3071c96081ecb4049e0bbdf0--

From yhb810501@gmail.com  Wed Mar  9 05:42:51 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E46773A69A2 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 05:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=-0.442,  BAYES_00=-2.599, J_CHICKENPOX_72=0.6, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ysf3UWTqF1pe for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 05:42:51 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id F3DC73A684D for <ipv6@ietf.org>; Wed,  9 Mar 2011 05:42:50 -0800 (PST)
Received: by vxg33 with SMTP id 33so570797vxg.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 05:44:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:content-transfer-encoding :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; bh=lZEQznmlkMQCYty2rgkDx1/v3oT2InDoYwuPv7CBuhI=; b=FpMKgsv7rFwFa6KlTRQezIDobDdxIV4hCeXDJcmzDw6kflBXhDDnwzCaTE2RchB8A1 XtKfJPhRiWCqkLjcCkjw1LRK1g8z3SCj3qze8rRpy17BIAQ1FqjzTjPYRTXc5qNEV5A1 0cH1yPlmlRSmcjdFKLjwRfY3eeB0B8qVGY+jM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:importance:x-mailer:x-mimeole; b=LZGeQ04Qa+Xa1GmGxl+7qJIBcDHFRPdZerkw4hwk4lngTsokSRkYIX/N7huAGa8U6A dBBK1JzrnXd2kft1kJGx7Vq8EJdJ/rYzMOHhOsNUnih40+DqaTZ1nORy9jJCd/dRFEWR AGaj+b4ycJk/j/2tquax0hRIHgiNUe6jGPt90=
Received: by 10.52.72.232 with SMTP id g8mr5038649vdv.108.1299678246840; Wed, 09 Mar 2011 05:44:06 -0800 (PST)
Received: from yhbPC ([220.200.26.60]) by mx.google.com with ESMTPS id f17sm1375576vbv.16.2011.03.09.05.44.03 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 05:44:06 -0800 (PST)
Message-ID: <CC9B14C9695649E3BB56369789394424@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: "Mark Smith" <ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC><20110309071900.239a9585@opy.nosense.org><AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com> <20110309194832.06bc1f6b@opy.nosense.org>
In-Reply-To: <20110309194832.06bc1f6b@opy.nosense.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Date: Wed, 9 Mar 2011 21:43:54 +0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 13:42:52 -0000

--------------------------------------------------
From: "Mark Smith" <ipng@69706e6720323030352d30312d31340a.nosense.org>
Sent: Wednesday, March 09, 2011 5:18 PM
To: "huabing yu" <yhb810501@gmail.com>
Cc: <ipv6@ietf.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02

> On Wed, 9 Mar 2011 09:29:54 +0800
> huabing yu <yhb810501@gmail.com> wrote:
>
>> 2011/3/9 Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
>>
>> > On Tue, 8 Mar 2011 23:09:46 +0800
>> > "Yu Hua bing" <yhb810501@gmail.com> wrote:
>> >
>> > >    Hi, I have submit draft-yhb-6man-ra-privacy-flag-02. The problem 
>> > > to
>> > >    be solved is as follows:
>> > >
>> > >    In some sites, the network administrators want to deploy stateless
>> > >    address autoconfiguration, and just permit the hardware-derived
>> > >    addresses to communicate with the Internet.They will do as 
>> > > follows:
>> > >
>> > <snip>
>> > >
>> > >   Now we can provide two solutions to the network administrators:
>> > >   (1) SLAAC + bind the MAC address and the  hardware-derived address 
>> > > on
>> > the access switch + disable the temporary addresses
>> > >   (2) DHCPv6 + DHCPv6 snooping
>> > >   The first solution is cheaper, and is easier to deploy.
>> >
> <snip>
>
>> > Regards,
>> > Mark.
>> >
>>
>>   In some sites, the network administrators want to prevent the host from
>> using any IPv6 address,
>>   like DHCPv6 plus DHCPv6 snooping. Your method can't.
>
> So, looking at the text at the top of the draft (although this is from
> the -01 version, as I can't seem to find the -02 one), where you
> present your use case -
>
>
> "when the network is in trouble,it is difficult to find out
> which host is attacking the other hosts."
>
> it seems your real and fundamental goal is to be able to track the
> mappings between MAC addresses and corresponding IPv6 addresses. Since
> privacy addresses naturally makes that harder, and the decision to use
> that is in the control of the end-host, you think the way to achieve
> that auditability is to provide a mechanism to suppress privacy them.
>
> I think you should sit back and think about the problem some more. The
> people who are likely to execute these attacks will have also have
> a motive to (a) choose an operating system where the tools to execute
> these attacks are more commonly available and (b) as that operating
> system is likely to be an open source one, modify the kernel, or
> install somebody else's kernel patch that ignores any "disable privacy"
> addresses mechanisms you manage to get deployed. You can't completely
> trust the end-host to follow mechanisms that aren't in its owner's
> interests.
>
> I think you'll be more successful at achieving your fundamental goal by
> observing and recording their IPv6 address use rather than trying to
> control it with mechanisms they have the ability to disable.
>
> Regards,
> Mark.


I have submit draft-yhb-6man-ra-privacy-flag-02 by email to 
internet-drafts@ietf.org.
IETF didn't publish it. Please wait.

I described the problem to be solved in the email 
"draft-yhb-6man-ra-privacy-flag-02".
I just want to cite an example to let you realize the value of the flag.Some 
people may
 not like it, but the other people may like it.

Yu Hua bing 


From swmike@swm.pp.se  Wed Mar  9 06:55:58 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B429D3A6874 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 06:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRNVLae-iDcG for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 06:55:56 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 24A723A6821 for <ipv6@ietf.org>; Wed,  9 Mar 2011 06:55:55 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0DA8D9C; Wed,  9 Mar 2011 15:57:11 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0AA969A; Wed,  9 Mar 2011 15:57:11 +0100 (CET)
Date: Wed, 9 Mar 2011 15:57:11 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: huabing yu <yhb810501@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
In-Reply-To: <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>
Message-ID: <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 14:55:58 -0000

On Wed, 9 Mar 2011, huabing yu wrote:

> (1)If "H" ("Hardware-derived addresses") flag is 1, it indicates that
> the host SHOULD generate hardware-derived addresses, and doesn't
> generate privacy addresses.

I think it should indicate that ONLY hw-derived address should be created, 
which by defintion is only ONE, and not more, and this is the ONLY one.

> *I think "DisablePrivacy" proposed by "draft-yhb-6man-ra-privacy-flag-01"*
> *is better than "H",although some people don't like the problem to be
> solved.*

Well, I don't think the problem is solved by these proposals, but if the 
RA standard should be changed, then I want the solution to be what I wrote 
before.

SLAAC means the host can take any address it wants as long as it's not 
already in use. Privacy Extensions is not the only mechanisms that might 
create an address to be used, thus I think the "disable privacy" flag is 
meaningless.

If you want to know the mac address of the computer who used an IP address 
at a certain time, then you need to tell the host to only use EUI64 based 
address and nothing else, you don't tell it to disable privacy extensions. 
Just because privacy extensions is the only address widely seen today as 
being non-EUI64, doesn't mean that if you disable privacy, you get only 
single EUI64.

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

From john@jlc.net  Wed Mar  9 07:47:21 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6E1C3A6866 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 07:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.572
X-Spam-Level: 
X-Spam-Status: No, score=-106.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUgsIk-F+cUv for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 07:47:21 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id D9EC83A6859 for <ipv6@ietf.org>; Wed,  9 Mar 2011 07:47:20 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 2EFE133C6C; Wed,  9 Mar 2011 10:48:37 -0500 (EST)
Date: Wed, 9 Mar 2011 10:48:37 -0500
From: John Leslie <john@jlc.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Flow label drafts - updates, main open issue
Message-ID: <20110309154837.GN89966@verdi>
References: <4D682228.7020304@gmail.com> <4D7453BE.1040606@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D7453BE.1040606@gmail.com>
User-Agent: Mutt/1.4.1i
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 15:47:22 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> I'm not hearing much in response to the open issue:
> 
>   Should we delete most of the text concerning stateful methods
>   of handling the flow label?

   I don't really have a horse in that race, but at first blush I'd say
the I-D goes into too much detail about stateful handling.

   IMHO, most handling (assuming it happens at all) will be stateless,
and will greatly resemble "damage" (as in what we route-around).

> In fact I'm not hearing much at all. Should I ask the WG Chairs
> to conclude that everybody is OK with these drafts? That would
> save us some time in Prague...

   I won't be in Prague... :^(

   But while this I-D is a step in the right direction, where I think
we ought to get should allow much more leeway in setting -- even
changing -- Flow Labels _by_prior_arrangement_.

   The basic assumption that Flow Labels will be set by the sender and
passed unchanged is certainly correct in the absence of arrangements
that specify particular processing.

   I am a bit nervous about _always_ allowing a zero Flow Label to be
changed without sender consent...

   But clearly, there _can_ be no protection against such changes --
or any changes, for that matter.

   My intuition is that any time the Traffic Class is changed during
forwarding, rules about Flow Label particular to that Traffic Class
should apply.

   Further, there probably need to be _various_ largely out-of-band
mechanisms to validate a contractual basis for special handling of
packets based upon Flow Labels. There could be one or more in-band
mechanisms if we had what I'll call a "Middlebox Options" extension
header (between Hop-by-Hop and Destination Options) to store validation
information.

   Fundamentally, I don't believe the completely-insecure Flow Label
can serve by itself as sufficient justification for special handling;
and I don't believe that the sender alone can justify special handling
by _all_ the different service-providers along the forwarding path.
I think more infrastructure will need to evolve.

   Legislating what we can't specify any means to enforce isn't wise...

====

   Disclaimer: I in some sense "represent" the ConEx WG, where several
folks want to reserve one bit from the Flow Label for ConEx use. I am
_not_ the right person to put the case for that, because frankly I
don't agree with the idea. Nonetheless, it seems reasonable to me to
allow things like that on an Experimental basis if clearly labeled
by setting an Experimental Traffic Class.

--
John Leslie <john@jlc.net>

From rja.lists@gmail.com  Wed Mar  9 07:50:46 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D490B3A6A2E for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 07:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.939
X-Spam-Level: 
X-Spam-Status: No, score=-2.939 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Em5xvNWQefwh for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 07:50:46 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id CDA1B3A6859 for <ipv6@ietf.org>; Wed,  9 Mar 2011 07:50:45 -0800 (PST)
Received: by vxg33 with SMTP id 33so718306vxg.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 07:52:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=IrodK8VP2ItRkhQO6j+bzyi9xhzSeWuhbB7ffb95HDE=; b=CkI+hK60pWGNGl/hAIUZyKZCB1FcO5LDl1MqEKIygaYugQORU2rzLlqJK4GaI82LgV 4x1GLrTRjltnCv6i/LxuF8nfhdyDo/8WXigEHpFkAPiq5d7rFKeO/gy7CnJ2N0DRU/qB Xm7UosOdjbJUIzwzXN1j80xYTllUVeFMogeko=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=o84kAW0zsCU236DKUbvJMUctycZHWbwXefTMpxPYuqgrFKQKUDTNc7byTbECMR5tPx qq5OByACaPuUmmDnXVYzChkBolyfouBaxbvvetpBgLD0mYzc4niIF+vH3z0VBNCGiuji u5meYZm2Y1K/evX1h3phKAVoQDw+0iyCJfDks=
Received: by 10.52.18.47 with SMTP id t15mr4746044vdd.48.1299685921511; Wed, 09 Mar 2011 07:52:01 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id bm19sm381914vdb.10.2011.03.09.07.52.00 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2011 07:52:00 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
Date: Wed, 9 Mar 2011 10:51:59 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <BD1A42A7-CCD4-4625-94C6-037FD8C3CF2C@gmail.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com> <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 15:50:46 -0000

On 09  Mar 2011, at 09:57 , Mikael Abrahamsson wrote:
> Privacy Extensions is not the only mechanisms that might create an
> address to be used, thus I think the "disable privacy" flag is meaningless.
> 
> If you want to know the mac address of the computer who used an
> IP address at a certain time, then you need to tell the host
> to only use EUI64 based address and nothing else, you don't tell it
> to disable privacy extensions.
> 
> Just because privacy extensions is the only address widely seen
> today as being non-EUI64, doesn't mean that if you disable privacy,
> you get only single EUI64.

The above is a very helpful clarification.  

Based on that, I agree with Mikael that the correct semantic 
to the flag should be to require direct/embedded use of a 
hardware MAC value for the IPv6 IID.  That would disallow 
not only the (pseudo-)Privacy addresses, but any other kind 
of addressing that would not embed a hardware address in the IID.



REQUEST for Fernando G/Ron B:
	Separately, keeping the quoted comments above in mind, the I-D
	draft-gont-6man-managing-privacy-extensions needs clarification 
	edits to avoid using the phrase "hardware-derived" anywhere.

REASON:
	Any (pseudo-) Privacy address is derived ("computed") using the 
	MAC address as a seed (at least originally). [RFC-3041, Seection 3.2]

	So it is confusing and not clear to say "hardware-derived",
	when one means that the system ought to only use IIDs that
	are embedded IEEE MAC addresses (whether 802, Firewire, or BlueTooth)
	or some other embedded hardware address type.


Cheers,

Ran



From brian.e.carpenter@gmail.com  Wed Mar  9 10:40:53 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D2323A6A0B for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level: 
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gb68F1oAJxpD for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:40:52 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 2F1113A692A for <ipv6@ietf.org>; Wed,  9 Mar 2011 10:40:52 -0800 (PST)
Received: by fxm15 with SMTP id 15so857304fxm.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 10:42:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G6wRPDqHo3+QG0dEw0soqp93lBtGMf9Zx8Ju+StlpUc=; b=PmIM7DCVs3nxGmIKeczPb9Fvh5ES1G2FG8iTEL9A0eWm0X6scZynKIRxko2McFNB7Q 5OKZGR9zfDmta1eboG7GczuIUzi15rHvEWeEq5Tc6dto5zPa0KhsySDitsV0MwZBrER0 mM3CSz0xIBPy3j1j5C7U/76uvheHlqNkPyr0A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=lm4GqXn0HzVmfBQM/iy8W46t6cbhjSY5HUTbNxnJYTLiCoYAEK3MHaraaLy3IFvB// 5SYjCUe2X70WOwh9PsqqtBdo6WELznA1HLwT4xcuOH18iHicRdx63HYk0d8cn0YYWI3D YlAay2XQIIC8RxWsJ49jafu3xKLRxJdV1IgCc=
Received: by 10.223.61.18 with SMTP id r18mr461820fah.140.1299696118937; Wed, 09 Mar 2011 10:41:58 -0800 (PST)
Received: from [192.168.2.167] (202-180-96-58.callplus.net.nz [202.180.96.58]) by mx.google.com with ESMTPS id n3sm1069291fax.31.2011.03.09.10.41.55 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 10:41:58 -0800 (PST)
Message-ID: <4D77C9EC.7060704@gmail.com>
Date: Thu, 10 Mar 2011 07:41:48 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
References: <C7F01288723C414C99A2D999E63341C7@yhbPC>	<20110309071900.239a9585@opy.nosense.org>	<AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com> <20110309194832.06bc1f6b@opy.nosense.org>
In-Reply-To: <20110309194832.06bc1f6b@opy.nosense.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 18:40:53 -0000

On 2011-03-09 22:18, Mark Smith wrote:
...
> I think you'll be more successful at achieving your fundamental goal by
> observing and recording their IPv6 address use rather than trying to
> control it with mechanisms they have the ability to disable.

Since we defined privacy addresses specifically so that individual
hosts could reduce their traceability, it seems very controversial
to do anything that harms that ability.

We did this, people will recall, as a direct result of public concern
about traceability based on CPU serial numbers and/or MAC addresses.

That refers to traceability on the open Internet, not traceability
on the LAN. So indeed, as Mark says, this can be solved locally
by MAC logging (from DHCP or ND). That will not remove the ability
to use privacy addresses beyond the LAN.

   Brian

From brian.e.carpenter@gmail.com  Wed Mar  9 10:48:24 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA38A3A692A for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZNKTfiMBvzF for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:48:24 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B8A1A3A6928 for <ipv6@ietf.org>; Wed,  9 Mar 2011 10:48:23 -0800 (PST)
Received: by fxm15 with SMTP id 15so864984fxm.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 10:49:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jDKPwQWTqHB5Ebz1xSlG0AVsliRgQkR6QPpRUn5juuk=; b=cqS408hqsHYRVS6h0rlp1bR73DLtDZKSM1wV3R3/EL+WmbeA7+n4zPucu0TSq0BWvT r0pcjx5zQXU3Da43SiNWCIRNoBIx+8raDAntIP83GJPMFV+ImCENFyXzDg/EDZbAYEsk K98YkbulJfjxEzEocO5g3NvrWqgzFg+30pPNo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=V64d8/mc125TVfkxmBNPdX46cFeb7jMTd9Dg7E5STWFCMgeHKhIEgaE5KkZGkIV9pv Y5E3uINdwaspSc/3RTa/ykJJ6zLYH9s0B4UvbDrn/eNOwevn6HcBzQKtzEBi+fPldsBf GSw6FgGWRTcxbqA00WrX+2kMVuVT6GH+7f168=
Received: by 10.223.91.79 with SMTP id l15mr5916782fam.53.1299696579929; Wed, 09 Mar 2011 10:49:39 -0800 (PST)
Received: from [192.168.2.167] (202-180-96-58.callplus.net.nz [202.180.96.58]) by mx.google.com with ESMTPS id n3sm1077971fax.7.2011.03.09.10.49.36 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 10:49:39 -0800 (PST)
Message-ID: <4D77CBB9.1080702@gmail.com>
Date: Thu, 10 Mar 2011 07:49:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 18:48:24 -0000

On 2011-03-10 00:17, Mikael Abrahamsson wrote:
> On Wed, 9 Mar 2011, Ran Atkinson wrote:
> 
>>
>> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt>
>>
>>
>> I recommend that folks read the above draft.  I haven't seen the
>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>> the volume of recent I-D postings, and the topic seems relevant.
> 
> I don't think it solves what it thinks it solves, but if this REALLY
> should be implemented, it's my initial thinking that the H flag should
> be a MUST demand to only have ONE and only one MAC-based IPv6 address
> according to EUI64. I would appreciate some reasoning in the draft why
> this was chosen as a SHOULD option.

For the reason I just gave against the disable-private flag: this
violates the host's right to use an untraceable address.

It may be that in corporate deployments, that right can be removed.
But removing it for public subscribers would be a political blunder.

    Brian

> 
> I do not like the "disable Privacy"-flag thinking at all and I really
> oppose going with that solution.
> 

From brian.e.carpenter@gmail.com  Wed Mar  9 10:57:34 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC6493A67D3 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:57:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.479
X-Spam-Level: 
X-Spam-Status: No, score=-103.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7Miccs9N2li for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:57:34 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 9AE883A680F for <ipv6@ietf.org>; Wed,  9 Mar 2011 10:57:33 -0800 (PST)
Received: by bwz13 with SMTP id 13so1071901bwz.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 10:58:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PHCgv8Ulj2PvFHsDlPvADEjLb5IMUAovoDVl8+WyGVY=; b=JFnzxWfl20A+nWfXIzbzlDHzPRZDp1q2k+b0TM+YaX4ftprllbPPyvn/OCCtfa/PY/ kM4bUi3JsRzLUHbxPDRVNA5T6MOUFc9PfA9rJ8BPGsuULkkY/xGkH1jOlvz1sRpYPLqM 2oSNqE4wD1E1WAO3jvRlufFregwyL2O4omDKI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Rk5gz8Fuc3nOT7cLZlHxx94hlBqv+vwsgB1lm1NFp8QluC7X8A58tmfMU84qZrRsb6 X8gwjK0xBUmWqNA/pflu2yxP/oP76RTtxxsR8o48B0bIZ3qVfgr73Y3Q3+LrQk7/fGvK KNGEykOS+UDWg9ZjEEp5MVUPCagab+BFxoVsI=
Received: by 10.204.3.146 with SMTP id 18mr3775581bkn.1.1299697116716; Wed, 09 Mar 2011 10:58:36 -0800 (PST)
Received: from [192.168.2.167] (202-180-96-58.callplus.net.nz [202.180.96.58]) by mx.google.com with ESMTPS id l3sm1946293fan.0.2011.03.09.10.58.33 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 10:58:35 -0800 (PST)
Message-ID: <4D77CDD1.3060005@gmail.com>
Date: Thu, 10 Mar 2011 07:58:25 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: Flow label drafts - updates, main open issue
References: <4D682228.7020304@gmail.com> <4D7453BE.1040606@gmail.com> <20110309154837.GN89966@verdi>
In-Reply-To: <20110309154837.GN89966@verdi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 18:57:35 -0000

John,

In line comments...

On 2011-03-10 04:48, John Leslie wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> I'm not hearing much in response to the open issue:
>>
>>   Should we delete most of the text concerning stateful methods
>>   of handling the flow label?
> 
>    I don't really have a horse in that race, but at first blush I'd say
> the I-D goes into too much detail about stateful handling.
> 
>    IMHO, most handling (assuming it happens at all) will be stateless,
> and will greatly resemble "damage" (as in what we route-around).
> 
>> In fact I'm not hearing much at all. Should I ask the WG Chairs
>> to conclude that everybody is OK with these drafts? That would
>> save us some time in Prague...
> 
>    I won't be in Prague... :^(
> 
>    But while this I-D is a step in the right direction, where I think
> we ought to get should allow much more leeway in setting -- even
> changing -- Flow Labels _by_prior_arrangement_.

The draft creates that leeway - apart from the Section 4 text about
stateful methods.
> 
>    The basic assumption that Flow Labels will be set by the sender and
> passed unchanged is certainly correct in the absence of arrangements
> that specify particular processing.
> 
>    I am a bit nervous about _always_ allowing a zero Flow Label to be
> changed without sender consent...
> 
>    But clearly, there _can_ be no protection against such changes --
> or any changes, for that matter.
> 
>    My intuition is that any time the Traffic Class is changed during
> forwarding, rules about Flow Label particular to that Traffic Class
> should apply.

There was considerable pushback in the WG to adding the concept
of local domains to the flow label definition.

> 
>    Further, there probably need to be _various_ largely out-of-band
> mechanisms to validate a contractual basis for special handling of
> packets based upon Flow Labels. There could be one or more in-band
> mechanisms if we had what I'll call a "Middlebox Options" extension
> header (between Hop-by-Hop and Destination Options) to store validation
> information.

Yes, but that's in the stateful part that you're arguing above
should be replaced by "more leeway".

> 
>    Fundamentally, I don't believe the completely-insecure Flow Label
> can serve by itself as sufficient justification for special handling;
> and I don't believe that the sender alone can justify special handling
> by _all_ the different service-providers along the forwarding path.
> I think more infrastructure will need to evolve.

Ditto.

> 
>    Legislating what we can't specify any means to enforce isn't wise...
> 
> ====
> 
>    Disclaimer: I in some sense "represent" the ConEx WG, where several
> folks want to reserve one bit from the Flow Label for ConEx use. I am
> _not_ the right person to put the case for that, because frankly I
> don't agree with the idea. Nonetheless, it seems reasonable to me to
> allow things like that on an Experimental basis if clearly labeled
> by setting an Experimental Traffic Class.

Ditto. What the draft is talking about is default behaviour, absent
anything requiring prior agreement or signalling.

I take your whole comment as a recommendation to remove section 4.

     Brian

From bob.hinden@gmail.com  Wed Mar  9 10:59:22 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E94DB3A6A37 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:59:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.345
X-Spam-Level: 
X-Spam-Status: No, score=-103.345 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ok9dh13GxrMc for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 10:59:22 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 168B53A680F for <ipv6@ietf.org>; Wed,  9 Mar 2011 10:59:22 -0800 (PST)
Received: by iwl42 with SMTP id 42so1017278iwl.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 11:00:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=pxkK1kJbYNZt3SUXfPKlFJ2dY8M+eya/r4dHBkqn12g=; b=Pfgx83ZWm26CdzfTywx9Rem2gG6d03i+0OvXlFFhIWb2plJicHAb4qLVgqHvX24ivB +qvtpGQaRqIA8MdS3xueSHBgIPWt91zfB6ZRepNGKp5cUiM2GBw9i+dyt5UrQGpPVfll 7F89lF/UUf0OxiacFSDMpSTV8TIV6otZ6ze9o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=pJKnbQbwQMN/FRjlnOGLACm7lxKd17uN7hbwxh6IusKogVNbGCyt8pRzql3Ui9A5zG i94njClHLxsd9YLUz/0yxdAYtB7NYvEZeAqdY+I5KnylxeeplO+O+K0zAygM/i40W93c ObcWVS9PbpE4Txv/TlpNhjYhpbr0Hxohsrwng=
Received: by 10.43.51.135 with SMTP id vi7mr742134icb.336.1299697238630; Wed, 09 Mar 2011 11:00:38 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id xa8sm1587451icb.22.2011.03.09.11.00.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2011 11:00:37 -0800 (PST)
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4D77C9EC.7060704@gmail.com>
Date: Wed, 9 Mar 2011 11:00:35 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <8C539C1E-9C03-4692-8FF7-9B7CD2DA1B94@gmail.com>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC>	<20110309071900.239a9585@opy.nosense.org>	<AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com> <20110309194832.06bc1f6b@opy.nosense.org> <4D77C9EC.7060704@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 18:59:23 -0000

On Mar 9, 2011, at 10:41 AM, Brian E Carpenter wrote:

> On 2011-03-09 22:18, Mark Smith wrote:
> ...
>> I think you'll be more successful at achieving your fundamental goal by
>> observing and recording their IPv6 address use rather than trying to
>> control it with mechanisms they have the ability to disable.
> 
> Since we defined privacy addresses specifically so that individual
> hosts could reduce their traceability, it seems very controversial
> to do anything that harms that ability.
> 
> We did this, people will recall, as a direct result of public concern
> about traceability based on CPU serial numbers and/or MAC addresses.
> 
> That refers to traceability on the open Internet, not traceability
> on the LAN. So indeed, as Mark says, this can be solved locally
> by MAC logging (from DHCP or ND). That will not remove the ability
> to use privacy addresses beyond the LAN.

+1

Bob



From jhw@apple.com  Wed Mar  9 11:06:50 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B5313A6965 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nb2EteoGhdpy for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:06:49 -0800 (PST)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 0FD2E3A68AF for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:06:49 -0800 (PST)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 3D92BD54F9C7 for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:08:05 -0800 (PST)
X-AuditID: 11807134-b7c8cae000005108-df-4d77d015c168
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id B6.68.20744.510D77D4; Wed,  9 Mar 2011 11:08:05 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHT00DO015GVU60@elliott.apple.com> for ipv6@ietf.org; Wed, 09 Mar 2011 11:08:05 -0800 (PST)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: james woodyatt <jhw@apple.com>
In-reply-to: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>
Date: Wed, 09 Mar 2011 11:08:04 -0800
Message-id: <26FA7472-2BD6-4D68-B3EC-F465B92EAC9E@apple.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>
To: ipv6 <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1203)
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 19:06:50 -0000

On Mar 9, 2011, at 2:01 AM, Ran Atkinson wrote:
> 
> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt>
> 
> I recommend that folks read the above draft.  I haven't seen the
> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
> the volume of recent I-D postings, and the topic seems relevant.


About the H-bit in the PIO it proposes, the draft says this:

   When set, this bit indicates that
   hardware-derived addresses SHOULD be used when configuring IPv6
   addresses as a result of Stateless Address Autoconfiguration.  When
   not set, this bit indicates that Privacy Extensions SHOULD be enabled
   when configuring IPv6 addresses as a result of Stateless Address
   Autoconfiguration

Which makes the bit worse than useless.  If the PIO contains A=1, then both EUI-64 and privacy IID are eligible under the current regime, but this draft says only that one or the other SLAAC alternative SHOULD be used depending on the state of the bit, without explicitly saying whether the complementary alternative SHOULD NOT be used.

I'm not sure if the intent is to make a signal for hosts that network administration regards any particular SLAAC alternative as NOT RECOMMENDED, but if it is, then the draft should explicitly say so.  Of course, if the draft were to changed to do that, then I would lodge the same complaints that I lodged previously against I-D.yhb-6man-ra-privacy-flag... for the same reasons.

This draft has a long struggle ahead of it, if you ask me.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From rja.lists@gmail.com  Wed Mar  9 11:16:06 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 145DC3A680F for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.923
X-Spam-Level: 
X-Spam-Status: No, score=-2.923 tagged_above=-999 required=5 tests=[AWL=-0.324, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Kkd6pwDuyNc for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:16:05 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id F33923A6A61 for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:15:58 -0800 (PST)
Received: by vxg33 with SMTP id 33so949379vxg.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 11:17:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=11EgYu/i9khFOrMHcgFrQ2lHCDWBzfszqUxReir23D4=; b=v8AEOkcOwF9X4zBWKGkPwgWU407pKyQxA4NDJBgLGtJFmRuUuG9k6wh6fuiuONP/Gd ZyjqcGv9JbXSveQrPBHma1nHMgEhy6fH6PJQ1H5/1/swx4uSPRg5aflTaY5ULntcQvhj Tp2TciR6GHjVv0wEH7eVgBmJFsMruqxj/Vutw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=Dvf9k+WVzHrYvLVHmRsK3+RTaZtPsc27RSXqxLRdcOqqEFxLzGIs+/Xa5qgfzEmbtl AVYNF6kAYhDdQiZHZhkDbmzt5w/ymD6EzlfGJ6U0LPev0ZXK0mimdScqWx2Ie4oKogsl JfpAXFtIjLWxAFbAvOvTfN9jpeFi9NQ30GHFA=
Received: by 10.52.178.164 with SMTP id cz4mr4066763vdc.42.1299698234214; Wed, 09 Mar 2011 11:17:14 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id e10sm848360vch.43.2011.03.09.11.17.12 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2011 11:17:13 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <4D77CBB9.1080702@gmail.com>
Date: Wed, 9 Mar 2011 14:17:12 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <A8E3ED1C-D74F-4B16-8CBE-049CA30B7D29@gmail.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 19:16:06 -0000

On 09  Mar 2011, at 13:49 , Brian E Carpenter wrote:
> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
>> 
>> I don't think it solves what it thinks it solves, but if this REALLY
>> should be implemented, it's my initial thinking that the H flag should
>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>> according to EUI64. I would appreciate some reasoning in the draft why
>> this was chosen as a SHOULD option.
> 
> For the reason I just gave against the disable-private flag: this
> violates the host's right to use an untraceable address.

(Hardware I am familiar with is not sentient.  So I don't know 
what it means to talk about the rights of a host, as above ---
I'll assume the meaning is that human users have privacy rights. :-)

> It may be that in corporate deployments, that right can be removed.

At least within the US, I am told that multiple courts have ruled 
that when an employee is using employer-owned equipment attached 
to an employer-owned network, then a reasonable expectation of 
privacy does not exist.  My examples and discussion have solely
focused on this "corporate deployment" scenario.

[ASIDE:  I am also told that the courts have ruled differently with 
respect to people accessing the Internet from their own home when 
using their own equipment.]

[ASIDE: Of course the IETF is global; legal systems vary from one place
to another.  So the above is intended narrowly as a practical example. :-]  

> But removing it for public subscribers would be a political blunder.


Earlier, I specifically noted that the privacy issue ought to be 
discussed in the Security Considerations section of (any) I-D on 
this topic, in (2A) and (2B) of this previous list email:

	<http://www.ietf.org/mail-archive/web/ipv6/current/msg13489.html>

Cheers !



From jmh@joelhalpern.com  Wed Mar  9 11:31:31 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 851EF3A6A48 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHzz1Mye-WrO for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 11:31:30 -0800 (PST)
Received: from hgblob.out.tigertech.net (hgblob.out.tigertech.net [74.114.88.71]) by core3.amsl.com (Postfix) with ESMTP id 3E7D73A69D1 for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:31:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 3E133325B2CD for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:32:47 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.154.181.170] (unknown [129.192.147.67]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id E3D3332280B3 for <ipv6@ietf.org>; Wed,  9 Mar 2011 11:32:46 -0800 (PST)
Message-ID: <4D77D5DD.40100@joelhalpern.com>
Date: Wed, 09 Mar 2011 14:32:45 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <A8E3ED1C-D74F-4B16-8CBE-049CA30B7D29@gmail.com>
In-Reply-To: <A8E3ED1C-D74F-4B16-8CBE-049CA30B7D29@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 19:31:31 -0000

I would observe that we have multiple documents which note the 
importance of traceability for "problem" resolution.  Treating privacy 
as an all-or-nothing thing is probably a misleading perspective.
It is extremely likely that privacy addresses, and their bindings to 
homes or office desktops, will be logged.  I would hope that said logs 
will be handled in a manner that preserves privacy in the normal course 
of events.

Pretending that such things will not happen strikes me as even sillier 
than assuming that a malicious host will cooperate with some unenforced 
flags.

Yours,
Joel

On 3/9/2011 2:17 PM, RJ Atkinson wrote:
>
> On 09  Mar 2011, at 13:49 , Brian E Carpenter wrote:
>> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
>>>
>>> I don't think it solves what it thinks it solves, but if this REALLY
>>> should be implemented, it's my initial thinking that the H flag should
>>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>>> according to EUI64. I would appreciate some reasoning in the draft why
>>> this was chosen as a SHOULD option.
>>
>> For the reason I just gave against the disable-private flag: this
>> violates the host's right to use an untraceable address.
>
> (Hardware I am familiar with is not sentient.  So I don't know
> what it means to talk about the rights of a host, as above ---
> I'll assume the meaning is that human users have privacy rights. :-)
>
>> It may be that in corporate deployments, that right can be removed.
>
> At least within the US, I am told that multiple courts have ruled
> that when an employee is using employer-owned equipment attached
> to an employer-owned network, then a reasonable expectation of
> privacy does not exist.  My examples and discussion have solely
> focused on this "corporate deployment" scenario.
>
> [ASIDE:  I am also told that the courts have ruled differently with
> respect to people accessing the Internet from their own home when
> using their own equipment.]
>
> [ASIDE: Of course the IETF is global; legal systems vary from one place
> to another.  So the above is intended narrowly as a practical example. :-]
>
>> But removing it for public subscribers would be a political blunder.
>
>
> Earlier, I specifically noted that the privacy issue ought to be
> discussed in the Security Considerations section of (any) I-D on
> this topic, in (2A) and (2B) of this previous list email:
>
> 	<http://www.ietf.org/mail-archive/web/ipv6/current/msg13489.html>
>
> Cheers !
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Mar  9 12:12:16 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 913533A6A89 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:12:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.87
X-Spam-Level: 
X-Spam-Status: No, score=-1.87 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7ERtVuApve5 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:12:15 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 6A02D3A6A87 for <ipv6@ietf.org>; Wed,  9 Mar 2011 12:12:15 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxPlB-0007vS-38; Thu, 10 Mar 2011 06:43:29 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id AD6685355C; Thu, 10 Mar 2011 06:43:28 +1030 (CST)
Date: Thu, 10 Mar 2011 06:43:28 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Message-ID: <20110310064328.3388ce88@opy.nosense.org>
In-Reply-To: <4D77D5DD.40100@joelhalpern.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <A8E3ED1C-D74F-4B16-8CBE-049CA30B7D29@gmail.com> <4D77D5DD.40100@joelhalpern.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 20:12:16 -0000

On Wed, 09 Mar 2011 14:32:45 -0500
"Joel M. Halpern" <jmh@joelhalpern.com> wrote:

> I would observe that we have multiple documents which note the 
> importance of traceability for "problem" resolution.  Treating privacy 
> as an all-or-nothing thing is probably a misleading perspective.
> It is extremely likely that privacy addresses, and their bindings to 
> homes or office desktops, will be logged.  I would hope that said logs 
> will be handled in a manner that preserves privacy in the normal course 
> of events.
> 
> Pretending that such things will not happen strikes me as even sillier 
> than assuming that a malicious host will cooperate with some unenforced 
> flags.
> 

I also think there is a fundamentally incorrect assumption is being
made - that IPv6 addresses and humans are tightly coupled. An IPv6
address identifies an end-node, and the traffic to or from it, but does
not always identify the human that caused that traffic to occur. If you
truly need auditable access/traffic logs, you need to identify the
human at the time via "human-facing" authentication methods e.g.
802.1x.

IOW, machines (and their IPv6 addresses) aren't really the security
threat, it's the people behind them.

Regards,
Mark.



> Yours,
> Joel
> 
> On 3/9/2011 2:17 PM, RJ Atkinson wrote:
> >
> > On 09  Mar 2011, at 13:49 , Brian E Carpenter wrote:
> >> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
> >>>
> >>> I don't think it solves what it thinks it solves, but if this REALLY
> >>> should be implemented, it's my initial thinking that the H flag should
> >>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
> >>> according to EUI64. I would appreciate some reasoning in the draft why
> >>> this was chosen as a SHOULD option.
> >>
> >> For the reason I just gave against the disable-private flag: this
> >> violates the host's right to use an untraceable address.
> >
> > (Hardware I am familiar with is not sentient.  So I don't know
> > what it means to talk about the rights of a host, as above ---
> > I'll assume the meaning is that human users have privacy rights. :-)
> >
> >> It may be that in corporate deployments, that right can be removed.
> >
> > At least within the US, I am told that multiple courts have ruled
> > that when an employee is using employer-owned equipment attached
> > to an employer-owned network, then a reasonable expectation of
> > privacy does not exist.  My examples and discussion have solely
> > focused on this "corporate deployment" scenario.
> >
> > [ASIDE:  I am also told that the courts have ruled differently with
> > respect to people accessing the Internet from their own home when
> > using their own equipment.]
> >
> > [ASIDE: Of course the IETF is global; legal systems vary from one place
> > to another.  So the above is intended narrowly as a practical example. :-]
> >
> >> But removing it for public subscribers would be a political blunder.
> >
> >
> > Earlier, I specifically noted that the privacy issue ought to be
> > discussed in the Security Considerations section of (any) I-D on
> > this topic, in (2A) and (2B) of this previous list email:
> >
> > 	<http://www.ietf.org/mail-archive/web/ipv6/current/msg13489.html>
> >
> > Cheers !
> >
> >
> > --------------------------------------------------------------------
> > 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 ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Mar  9 12:43:44 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10B623A6AB1 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.572
X-Spam-Level: 
X-Spam-Status: No, score=-1.572 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CyA9EZ4prhWH for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:43:43 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id E038E3A6A9C for <ipv6@ietf.org>; Wed,  9 Mar 2011 12:43:42 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxQFe-0000YK-Mb; Thu, 10 Mar 2011 07:14:58 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 439215355C; Thu, 10 Mar 2011 07:14:58 +1030 (CST)
Date: Thu, 10 Mar 2011 07:14:58 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Message-ID: <20110310071458.76d75e9e@opy.nosense.org>
In-Reply-To: <BD1A42A7-CCD4-4625-94C6-037FD8C3CF2C@gmail.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com> <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se> <BD1A42A7-CCD4-4625-94C6-037FD8C3CF2C@gmail.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 20:43:44 -0000

Hi Ran,

On Wed, 9 Mar 2011 10:51:59 -0500
RJ Atkinson <rja.lists@gmail.com> wrote:

> 
> On 09  Mar 2011, at 09:57 , Mikael Abrahamsson wrote:
> > Privacy Extensions is not the only mechanisms that might create an
> > address to be used, thus I think the "disable privacy" flag is meaningless.
> > 
> > If you want to know the mac address of the computer who used an
> > IP address at a certain time, then you need to tell the host
> > to only use EUI64 based address and nothing else, you don't tell it
> > to disable privacy extensions.
> > 
> > Just because privacy extensions is the only address widely seen
> > today as being non-EUI64, doesn't mean that if you disable privacy,
> > you get only single EUI64.
> 
> The above is a very helpful clarification.  
> 
> Based on that, I agree with Mikael that the correct semantic 
> to the flag should be to require direct/embedded use of a 
> hardware MAC value for the IPv6 IID.  That would disallow 
> not only the (pseudo-)Privacy addresses, but any other kind 
> of addressing that would not embed a hardware address in the IID.
> 

That may have unintended consequences. If a hardware address isn't
available, IIDs can be generated randomly, so if this flag was
properly obeyed, these random IID end-nodes should not acquire
addresses.

An example of where this might matter is on a large scale PPP
deployment. If an ISP switched this flag on in the RAs it sends over PPP
sessions on the BRAS, and the CPE PPP implementations did not use
hardware derived IIDs (i.e. sourced from another interfaces), the PPP
session may not come up. Another property of IPV6CP is to negotiate
IIDs, to overcome collisions if they occur. On a BRAS, the scope of the
collision detection may not only be within a single PPP session, but
across all of them, which may number in the 10s of 1000s.

Taking a step back, I'm wondering what the actual problem with privacy
addresses is - neither of the drafts have specifically said. Is it that
they're a random, non-hardware derived IID, or is it that they're
random, non-hardware derived IID and that they change over time?

If hardware derived IIDs are enforced, there aren't any guarantees that
the underlying hardware address isn't random either, or won't be made
so intentionally by somebody who wants to preserve their network layer
anonimity. Temporarily changing MAC addresses on Ethernet cards is easy
if you've got admin access to an OS (or at least, on Windows and Linux
it is, not sure about Mac OS X).

Regards,
Mark.



From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Mar  9 12:48:12 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 904773A6AC3 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.852
X-Spam-Level: 
X-Spam-Status: No, score=-1.852 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dXJq+-VV0PJ for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 12:48:11 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 4069A3A6ABF for <ipv6@ietf.org>; Wed,  9 Mar 2011 12:48:11 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxQJx-0000hK-M7; Thu, 10 Mar 2011 07:19:25 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 54E3E5355C; Thu, 10 Mar 2011 07:19:25 +1030 (CST)
Date: Thu, 10 Mar 2011 07:19:25 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Message-ID: <20110310071925.309d467b@opy.nosense.org>
In-Reply-To: <4D77CBB9.1080702@gmail.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 20:48:12 -0000

On Thu, 10 Mar 2011 07:49:29 +1300
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
> > On Wed, 9 Mar 2011, Ran Atkinson wrote:
> > 
> >>
> >> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt>
> >>
> >>
> >> I recommend that folks read the above draft.  I haven't seen the
> >> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
> >> the volume of recent I-D postings, and the topic seems relevant.
> > 
> > I don't think it solves what it thinks it solves, but if this REALLY
> > should be implemented, it's my initial thinking that the H flag should
> > be a MUST demand to only have ONE and only one MAC-based IPv6 address
> > according to EUI64. I would appreciate some reasoning in the draft why
> > this was chosen as a SHOULD option.
> 
> For the reason I just gave against the disable-private flag: this
> violates the host's right to use an untraceable address.
> 
> It may be that in corporate deployments, that right can be removed.
> But removing it for public subscribers would be a political blunder.
> 

I agree. I sort of accept that an ISP can know my addresses in use, in
part because they gave them to me. However, for an ISP to not let me
choose if I want to use privacy addresses on the Internet would
be completely unacceptable.

Regards,
Mark.

>     Brian
> 
> > 
> > I do not like the "disable Privacy"-flag thinking at all and I really
> > oppose going with that solution.
> > 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Mar  9 13:10:18 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 729AA3A6AB7 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 13:10:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CP1NDkuU4XHv for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 13:10:17 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 343BB3A6AB0 for <ipv6@ietf.org>; Wed,  9 Mar 2011 13:10:17 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxQfN-0001R9-Bd; Thu, 10 Mar 2011 07:41:33 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 0E51D5355C; Thu, 10 Mar 2011 07:41:33 +1030 (CST)
Date: Thu, 10 Mar 2011 07:41:32 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Message-ID: <20110310074132.463bf972@opy.nosense.org>
In-Reply-To: <4D77C9EC.7060704@gmail.com>
References: <C7F01288723C414C99A2D999E63341C7@yhbPC> <20110309071900.239a9585@opy.nosense.org> <AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com> <20110309194832.06bc1f6b@opy.nosense.org> <4D77C9EC.7060704@gmail.com>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 09 Mar 2011 21:10:18 -0000

On Thu, 10 Mar 2011 07:41:48 +1300
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> On 2011-03-09 22:18, Mark Smith wrote:
> ...
> > I think you'll be more successful at achieving your fundamental goal by
> > observing and recording their IPv6 address use rather than trying to
> > control it with mechanisms they have the ability to disable.
> 
> Since we defined privacy addresses specifically so that individual
> hosts could reduce their traceability, it seems very controversial
> to do anything that harms that ability.
> 
> We did this, people will recall, as a direct result of public concern
> about traceability based on CPU serial numbers and/or MAC addresses.
> 
> That refers to traceability on the open Internet, not traceability
> on the LAN. So indeed, as Mark says, this can be solved locally
> by MAC logging (from DHCP or ND). That will not remove the ability
> to use privacy addresses beyond the LAN.
> 

Actually, one of the reasons I've been thinking about this "ND logging"
recently, before these privacy proposals came up, is because of the
criticisms about both stateless and stateful addressing methods
existing in IPv6.

The common argument from the "stateful-only crowd" seems to be that
they need to have a log of IPv6 address/MAC addresses for audit
purposes, and therefore think they need to have stateful, database
driven addressing to do that, probably because that is how it has
been done in IPv4. I've thought that SLAAC with more detailed ND state
logging, triggered by NUD state changes, would provide them with what
they need, without requiring the additional software infrastructure and
state maintenance that stateful DHCPv6 addressing involves. Although
stateful DHCPv6 clients are becoming far more widely available, all
IPv6 end-nodes are at minimum going to support SLAAC.

Regards,
Mark.

From brian.e.carpenter@gmail.com  Wed Mar  9 18:04:48 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 472F03A6814 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 18:04:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.008
X-Spam-Level: 
X-Spam-Status: No, score=-103.008 tagged_above=-999 required=5 tests=[AWL=-0.409, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BuNvAYbyusU7 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 18:04:47 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 4FE4A3A680D for <ipv6@ietf.org>; Wed,  9 Mar 2011 18:04:47 -0800 (PST)
Received: by vxg33 with SMTP id 33so1342539vxg.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 18:06:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=f60JRd++2xIDoGeAU23fNRI5NlrpmCHRlWZ4DX3uDUE=; b=G3Nx6kjBM5NIMQ1AABb3kmCx4R7p93NzH09Gx7+p12Br2ST9lWWqnZ7tEZKDVw49em Q/p6hSCMY+9XMz3uWIHQEJwvoWjbfbLRdNRimH1qAzg8yxsWbYsAO+T+JEoe5r2CFzDc UEIeqzDKTDC17vOXWLyLkGIuCwbOh4bXejbD8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=bX457Ye8oHRomjiv3gog+V4O72i/eVLnfM9PLvqKvTv0WMwAdHiD4Dpmv90W1MOGsg 7num+Zv7XgkitR9xMTeTY0q1nmR/mC5sezBAU4s3//yayRk5LXATyoKm9wTUgBTZdcGy U0KRiyNMhJI8fu2/HluoWU+rEKw07Xov/37fA=
Received: by 10.52.97.41 with SMTP id dx9mr736527vdb.97.1299722763898; Wed, 09 Mar 2011 18:06:03 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id r5sm1034439vch.16.2011.03.09.18.06.01 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 18:06:03 -0800 (PST)
Message-ID: <4D7831FB.6030701@gmail.com>
Date: Thu, 10 Mar 2011 15:05:47 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
References: <C7F01288723C414C99A2D999E63341C7@yhbPC>	<20110309071900.239a9585@opy.nosense.org>	<AANLkTimJV_CgVTdGY50ZNUxLU-RZP1nRvY4jpwn7yw=B@mail.gmail.com>	<20110309194832.06bc1f6b@opy.nosense.org>	<4D77C9EC.7060704@gmail.com> <20110310074132.463bf972@opy.nosense.org>
In-Reply-To: <20110310074132.463bf972@opy.nosense.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 02:04:48 -0000

On 2011-03-10 10:11, Mark Smith wrote:
> On Thu, 10 Mar 2011 07:41:48 +1300
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2011-03-09 22:18, Mark Smith wrote:
>> ...
>>> I think you'll be more successful at achieving your fundamental goal by
>>> observing and recording their IPv6 address use rather than trying to
>>> control it with mechanisms they have the ability to disable.
>> Since we defined privacy addresses specifically so that individual
>> hosts could reduce their traceability, it seems very controversial
>> to do anything that harms that ability.
>>
>> We did this, people will recall, as a direct result of public concern
>> about traceability based on CPU serial numbers and/or MAC addresses.
>>
>> That refers to traceability on the open Internet, not traceability
>> on the LAN. So indeed, as Mark says, this can be solved locally
>> by MAC logging (from DHCP or ND). That will not remove the ability
>> to use privacy addresses beyond the LAN.
>>
> 
> Actually, one of the reasons I've been thinking about this "ND logging"
> recently, before these privacy proposals came up, is because of the
> criticisms about both stateless and stateful addressing methods
> existing in IPv6.
> 
> The common argument from the "stateful-only crowd" seems to be that
> they need to have a log of IPv6 address/MAC addresses for audit
> purposes, and therefore think they need to have stateful, database
> driven addressing to do that, probably because that is how it has
> been done in IPv4. I've thought that SLAAC with more detailed ND state
> logging, triggered by NUD state changes, would provide them with what
> they need, without requiring the additional software infrastructure and
> state maintenance that stateful DHCPv6 addressing involves. Although
> stateful DHCPv6 clients are becoming far more widely available, all
> IPv6 end-nodes are at minimum going to support SLAAC.

Not to mention that such a logging mechanism will detect any hosts that
are misbehaving by simply giving themselves arbitrary addresses, which as
far as I can see can't be prevented in the general case.

     Brian

From brian.e.carpenter@gmail.com  Wed Mar  9 18:14:07 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2E273A6814 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 18:14:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.342
X-Spam-Level: 
X-Spam-Status: No, score=-103.342 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yieovQkgd8a7 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 18:14:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id DAE063A680D for <ipv6@ietf.org>; Wed,  9 Mar 2011 18:14:05 -0800 (PST)
Received: by eye13 with SMTP id 13so415926eye.31 for <ipv6@ietf.org>; Wed, 09 Mar 2011 18:15:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=z+1vY8qXqqoC3n6EhOUOCX8UaTXASZGoAdrBr2+uW6Q=; b=ACZXFIrk7qt4pr81KFwHnSOJXmA3NduuaTUWSG2Mve8t6JUiZ4kdx3OnjP43vWQdFW I+1fUDdSTzAQnQQmHu90m5vyWcSyYsQmNiboDTjkU8oF5nVFl4WJ7ma8iaXbLrs12A5o kkTFPsTCQK9NM1rPxAVsU/2Zor61LGirZclCk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=VML8v5B49elE26fgYMmHmUBPBuL4RI1WI5ymHqcx9Av8GL6q6084AL4MUvImDqBphG Y7n9bnPrI+R6O36pIgo/f+9hzBTB7PHIRhe03BiraMg0bxAc0OV75ZWv3ta7ssf/Y164 hx6H3nj6ldVe6K6i/O9qdvwaSTLZKl+EzeQFs=
Received: by 10.14.53.1 with SMTP id f1mr5122655eec.29.1299723321792; Wed, 09 Mar 2011 18:15:21 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id t5sm2072103eeh.14.2011.03.09.18.15.17 (version=SSLv3 cipher=OTHER); Wed, 09 Mar 2011 18:15:20 -0800 (PST)
Message-ID: <4D78342C.2060207@gmail.com>
Date: Thu, 10 Mar 2011 15:15:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org>
In-Reply-To: <20110310071925.309d467b@opy.nosense.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 02:14:07 -0000

On 2011-03-10 09:49, Mark Smith wrote:
> On Thu, 10 Mar 2011 07:49:29 +1300
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
>>> On Wed, 9 Mar 2011, Ran Atkinson wrote:
>>>
>>>> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-privacy-extensions-00.txt>
>>>>
>>>>
>>>> I recommend that folks read the above draft.  I haven't seen the
>>>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>>>> the volume of recent I-D postings, and the topic seems relevant.
>>> I don't think it solves what it thinks it solves, but if this REALLY
>>> should be implemented, it's my initial thinking that the H flag should
>>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>>> according to EUI64. I would appreciate some reasoning in the draft why
>>> this was chosen as a SHOULD option.
>> For the reason I just gave against the disable-private flag: this
>> violates the host's right to use an untraceable address.
>>
>> It may be that in corporate deployments, that right can be removed.
>> But removing it for public subscribers would be a political blunder.
>>
> 
> I agree. I sort of accept that an ISP can know my addresses in use, in
> part because they gave them to me. However, for an ISP to not let me
> choose if I want to use privacy addresses on the Internet would
> be completely unacceptable.

Right, and since that sentiment is shared by the human hosts of
millions of Internet hosts, we have to make sure that our standards
allow for it. Of course, there will be situations where local laws
don't grant a right to privacy, but we need to be sure that IETF standards
allow for the preservation of privacy. That has been established as a
pretty strong consensus in the IETF a number of times.

   Brian

From dwing@cisco.com  Wed Mar  9 23:32:57 2011
Return-Path: <dwing@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5E093A68C6 for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 23:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.567
X-Spam-Level: 
X-Spam-Status: No, score=-110.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAoBFM2LDfyJ for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 23:32:57 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 1B8CB3A67EF for <ipv6@ietf.org>; Wed,  9 Mar 2011 23:32:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2744; q=dns/txt; s=iport; t=1299742454; x=1300952054; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=l05YFpQacsERsw/XF/Pg8MQi5mnx/5RnUR499r2ZMwk=; b=jb1yEPxm/f/P6h/aSmNhpLl3g4mH5q73XWV1FMG3Q+lNKVfEY0PZJ/ez 9GdoqVeE10Uy4GMiA1bVfvI68vmWdw4ulyNenRp4M9IwDzf1jmvFuO1Kt SxGhkgaVf01YEcVuchc19yabwnRbv/Lfw0zsS2crtts+kubx2dN90ZLtX 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAHwNeE2rR7Hu/2dsb2JhbACYVIFkjEl3pR2cFoViBIUk
X-IronPort-AV: E=Sophos;i="4.62,295,1297036800"; d="scan'208";a="276323958"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 10 Mar 2011 07:34:14 +0000
Received: from dwingWS ([10.32.240.195]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p2A7YEVL014858; Thu, 10 Mar 2011 07:34:14 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Mikael Abrahamsson'" <swmike@swm.pp.se>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>
In-Reply-To: <4D77CBB9.1080702@gmail.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Date: Wed, 9 Mar 2011 23:34:13 -0800
Message-ID: <233b01cbdef5$8e214550$aa63cff0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcveitPFUMG1lOt6T3KjDCXZ7rdhMQAacyBg
Content-Language: en-us
Cc: ipv6@ietf.org, 'Ran Atkinson' <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 07:32:58 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Wednesday, March 09, 2011 10:49 AM
> To: Mikael Abrahamsson
> Cc: ipv6@ietf.org; Ran Atkinson
> Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
> 
> On 2011-03-10 00:17, Mikael Abrahamsson wrote:
> > On Wed, 9 Mar 2011, Ran Atkinson wrote:
> >
> >>
> >> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-
> privacy-extensions-00.txt>
> >>
> >>
> >> I recommend that folks read the above draft.  I haven't seen the
> >> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
> >> the volume of recent I-D postings, and the topic seems relevant.
> >
> > I don't think it solves what it thinks it solves, but if this REALLY
> > should be implemented, it's my initial thinking that the H flag
> should
> > be a MUST demand to only have ONE and only one MAC-based IPv6 address
> > according to EUI64. I would appreciate some reasoning in the draft
> why
> > this was chosen as a SHOULD option.
> 
> For the reason I just gave against the disable-private flag: this
> violates the host's right to use an untraceable address.
> 
> It may be that in corporate deployments, that right can be removed.

Nobody wants it removed in corporate deployments, either.  Consider
for a moment an IPv6-enabled telephone, on the desk of a Very 
Important Person at a company, who is calling the CEO of some
Itty Bitty Company.  And then the CEO calls.  Then someone on
the acquisition team calls.  It hardly matters what they're talking 
about -- just seeing that traffic with those IPv6 addresses is
sufficient to decide to buy (or sell) stock in Itty Bitty 
Company.  

We should, instead, look at how a host's privacy address can
be reported and recorded, so the network administrator has all
the necessary ability to determine which host is using which
address now or in the past.  This is easily done -- without 
changing RA.

If we don't have IPv6 privacy addresses, we will also soon
see NAPT66 (with UDP and TCP port rewriting) in order to 
achieve the same result as privacy addresses:  trying to 
obfuscate which host is communicating.

-d


> But removing it for public subscribers would be a political blunder.
> 
>     Brian
> 
> >
> > I do not like the "disable Privacy"-flag thinking at all and I really
> > oppose going with that solution.
> >
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From sthaug@nethelp.no  Wed Mar  9 23:44:40 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8CB43A67FF for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 23:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPSebpu-2ZBV for <ipv6@core3.amsl.com>; Wed,  9 Mar 2011 23:44:40 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 7500B3A67EF for <ipv6@ietf.org>; Wed,  9 Mar 2011 23:44:39 -0800 (PST)
Received: (qmail 13485 invoked from network); 10 Mar 2011 07:45:54 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 10 Mar 2011 07:45:54 -0000
Date: Thu, 10 Mar 2011 08:45:54 +0100 (CET)
Message-Id: <20110310.084554.41634571.sthaug@nethelp.no>
To: ipng@69706e6720323030352d30312d31340a.nosense.org
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
From: sthaug@nethelp.no
In-Reply-To: <20110310074132.463bf972@opy.nosense.org>
References: <20110309194832.06bc1f6b@opy.nosense.org> <4D77C9EC.7060704@gmail.com> <20110310074132.463bf972@opy.nosense.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
Cc: ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 07:44:40 -0000

> The common argument from the "stateful-only crowd" seems to be that
> they need to have a log of IPv6 address/MAC addresses for audit
> purposes, and therefore think they need to have stateful, database
> driven addressing to do that, probably because that is how it has
> been done in IPv4.

In our (service provider) case the basic requirement is to be able to
associate a dynamic IPv6 address with a specific *customer*.

We're not really interested in the MAC address other than the fact
that customer support sometimes finds it useful to look at the OUI and
tell the customer "you need to restart your XX wireless router because
..."

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From ipng@69706e6720323030352d30312d31340a.nosense.org  Thu Mar 10 04:05:11 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F5443A691D for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.558
X-Spam-Level: 
X-Spam-Status: No, score=-1.558 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCjY7gU-qAoc for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:05:10 -0800 (PST)
Received: from smtp3.adam.net.au (smtp3.adam.net.au [202.136.110.249]) by core3.amsl.com (Postfix) with ESMTP id 97C9A3A6941 for <ipv6@ietf.org>; Thu, 10 Mar 2011 04:05:10 -0800 (PST)
Received: from 114-30-116-21.ip.adam.com.au ([114.30.116.21] helo=opy.nosense.org) by smtp3.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PxedN-0000A0-Gb; Thu, 10 Mar 2011 22:36:25 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 232D65355C; Thu, 10 Mar 2011 22:36:25 +1030 (CST)
Date: Thu, 10 Mar 2011 22:36:23 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: sthaug@nethelp.no
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Message-ID: <20110310223623.5221b994@opy.nosense.org>
In-Reply-To: <20110310.084554.41634571.sthaug@nethelp.no>
References: <20110309194832.06bc1f6b@opy.nosense.org> <4D77C9EC.7060704@gmail.com> <20110310074132.463bf972@opy.nosense.org> <20110310.084554.41634571.sthaug@nethelp.no>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 12:05:11 -0000

On Thu, 10 Mar 2011 08:45:54 +0100 (CET)
sthaug@nethelp.no wrote:

> > The common argument from the "stateful-only crowd" seems to be that
> > they need to have a log of IPv6 address/MAC addresses for audit
> > purposes, and therefore think they need to have stateful, database
> > driven addressing to do that, probably because that is how it has
> > been done in IPv4.
> 
> In our (service provider) case the basic requirement is to be able to
> associate a dynamic IPv6 address with a specific *customer*.
> 

Can't you use RADIUS for that? I'm working in a SLAAC
environment for SP customers over PPP/PPPoE or L2TP, and RADIUS is
reporting everything we're interested in knowing, including username,
PPP IPV6CP IIDs, chosen dynamic prefixes for the PPP session and dynamic
delegated prefixes if they're requested and the customer falls in that
service type.

> We're not really interested in the MAC address other than the fact
> that customer support sometimes finds it useful to look at the OUI and
> tell the customer "you need to restart your XX wireless router because
> ..."
> 
> Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From ran.atkinson@gmail.com  Thu Mar 10 04:08:51 2011
Return-Path: <ran.atkinson@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9034C3A695B for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wP-SanWt4wrS for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:08:50 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id A9ECD3A6A45 for <ipv6@ietf.org>; Thu, 10 Mar 2011 04:08:50 -0800 (PST)
Received: by vxg33 with SMTP id 33so1730505vxg.31 for <ipv6@ietf.org>; Thu, 10 Mar 2011 04:10:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=UdSIdhuHAXJqh0TNszKWMxncyL0uOiwH9eF0cEF1j2s=; b=Z/+lZgTsSV/F3vyEblXuuh3pKv0mVBByu3TiCUEWNX7POrEB7furmftzAQGLWt+8iO uD/f4BhFzwcaLH6+Vb9i7w48Vsqv1ahZJ+XooDxdSijwIu+z1PnGw7Bzs/9BITpcRRnw TKZ8Gye1d32PoUayh8ajAIf81rgajpacNvn+E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=PsEeDfCHE1Fv8ZeTZ0Scx+jeZtOJJo7BnZkdtK8Sx3AM0cGrlT95Hq5T6utq7DIeli m8y/ZPPau/lw+M8f4hweuXS0z7FmmZjXJufqhnQgzBMkSqgTOrtDn4PHkTVQn7JIH/1I JWCXfsETYYnK+ztBSHN7wvVGSagTSVYdgrPfA=
Received: by 10.52.90.109 with SMTP id bv13mr5920732vdb.237.1299759007837; Thu, 10 Mar 2011 04:10:07 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id bl17sm570489vdb.0.2011.03.10.04.10.06 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 10 Mar 2011 04:10:06 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: Ran Atkinson <ran.atkinson@gmail.com>
In-Reply-To: <233b01cbdef5$8e214550$aa63cff0$@com>
Date: Thu, 10 Mar 2011 07:10:05 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 12:08:51 -0000

On 10  Mar 2011, at 02:34 , Dan Wing wrote:
> Nobody wants it removed in corporate deployments, either.  

That statement is far too strong; it simply is not true.

> Consider for a moment an IPv6-enabled telephone,
> on the desk of a Very Important Person at a company, ...

(Laugh.  I don't believe in that untrue example for a second,
but thanks for the humorous start to my morning.  :-)

Oh, and consider that Caller-ID, usually including a full name,
is already widely deployed in many countries.  It is so
much simpler just to read the Caller-ID string off of the
telephone handset.  

If one wants to intercept traffic, it is MUCH simpler to intercept 
the SIP traffic -- which is never encrypted in real-world corporate 
deployments because that would make VoIP too hard to debug.

> If we don't have IPv6 privacy addresses, we will also soon
> see NAPT66 (with UDP and TCP port rewriting) in order to 
> achieve the same result as privacy addresses:  trying to 
> obfuscate which host is communicating.

It seems pretty clear that Fred's NPTv6 is going to be
deployed in at least some locations, albeit for entirely 
different reasons.  I'm not sure if that meets your 
definition of NAPT66 or not.

Cheers,

Ran



From sthaug@nethelp.no  Thu Mar 10 04:30:49 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C27CB3A696F for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.899
X-Spam-Level: 
X-Spam-Status: No, score=-5.899 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eoGiZZa+hlo6 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 04:30:44 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 015103A6924 for <ipv6@ietf.org>; Thu, 10 Mar 2011 04:30:43 -0800 (PST)
Received: (qmail 83149 invoked from network); 10 Mar 2011 12:31:59 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 10 Mar 2011 12:31:59 -0000
Date: Thu, 10 Mar 2011 13:31:58 +0100 (CET)
Message-Id: <20110310.133158.74670479.sthaug@nethelp.no>
To: ipng@69706e6720323030352d30312d31340a.nosense.org
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
From: sthaug@nethelp.no
In-Reply-To: <20110310223623.5221b994@opy.nosense.org>
References: <20110310074132.463bf972@opy.nosense.org> <20110310.084554.41634571.sthaug@nethelp.no> <20110310223623.5221b994@opy.nosense.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
Cc: ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 12:30:49 -0000

> > > The common argument from the "stateful-only crowd" seems to be that
> > > they need to have a log of IPv6 address/MAC addresses for audit
> > > purposes, and therefore think they need to have stateful, database
> > > driven addressing to do that, probably because that is how it has
> > > been done in IPv4.
> > 
> > In our (service provider) case the basic requirement is to be able to
> > associate a dynamic IPv6 address with a specific *customer*.
> 
> Can't you use RADIUS for that? I'm working in a SLAAC
> environment for SP customers over PPP/PPPoE or L2TP, and RADIUS is
> reporting everything we're interested in knowing, including username,
> PPP IPV6CP IIDs, chosen dynamic prefixes for the PPP session and dynamic
> delegated prefixes if they're requested and the customer falls in that
> service type.

Sure we can. If we redo our DHCP infrastructure to use Radius instead.
It is a major change, and we don't really want to do it unless we
absolutely have to.

There are plenty of *other* bumps in the road on our way to IPv6. I
see no need to introduce more of these than necessary.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From cb.list6@gmail.com  Thu Mar 10 07:34:55 2011
Return-Path: <cb.list6@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A01C3A6A11 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 07:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.514
X-Spam-Level: 
X-Spam-Status: No, score=-3.514 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97orABcU7deS for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 07:34:54 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id D52863A69EE for <ipv6@ietf.org>; Thu, 10 Mar 2011 07:34:53 -0800 (PST)
Received: by iwl42 with SMTP id 42so2085476iwl.31 for <ipv6@ietf.org>; Thu, 10 Mar 2011 07:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tajL6MKHOKpcOK2IY7c6+mvqURQnXEwzTDhSOrNKu7I=; b=ilo4mVSy0KUTrnKwlNAGwfwOcPYoYvh4wmewl/rzHRFzf/l0hfo+vWpP83T13rIJVG e3bANbtDsruq/OU5JmtFAvpl4OS0vtFuwnJ0vnlkzDL+7YjMmX2Xab0fW8fPnv6YtcBB mwEU7DtkB3QW4oq0TaBcxcC2cxQ/ewOpodOqg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=r1KSBnqOFUk/WkXt6dRYAJee6wvi7YLk/+aIwZfcY0MFQVm+2OrTCOggVfknoz1mo4 GeT2xqrKPmI+BoLD209yYUPg6Nc+yPqELyCNzKDN769tUZyAwPhJBhpQjNsKNpmu9wfL 68G7RZkvkvoGRwUprqz6pGcqpshgefEwAwPhk=
MIME-Version: 1.0
Received: by 10.42.168.129 with SMTP id w1mr662812icy.373.1299771371718; Thu, 10 Mar 2011 07:36:11 -0800 (PST)
Received: by 10.42.172.137 with HTTP; Thu, 10 Mar 2011 07:36:11 -0800 (PST)
Received: by 10.42.172.137 with HTTP; Thu, 10 Mar 2011 07:36:11 -0800 (PST)
In-Reply-To: <233b01cbdef5$8e214550$aa63cff0$@com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com>
Date: Thu, 10 Mar 2011 07:36:11 -0800
Message-ID: <AANLkTikAb7Y4mYPjQDnvJUcHbD3mybAaszn2_ehXFeCy@mail.gmail.com>
Subject: Re: RE: draft-gont-6man-managing-privacy-extensions-00.txt
From: Cameron Byrne <cb.list6@gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8d42e6875a049e229a25
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 15:34:55 -0000

--90e6ba6e8d42e6875a049e229a25
Content-Type: text/plain; charset=ISO-8859-1

On Mar 9, 2011 11:34 PM, "Dan Wing" <dwing@cisco.com> wrote:
>
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> > Brian E Carpenter
> > Sent: Wednesday, March 09, 2011 10:49 AM
> > To: Mikael Abrahamsson
> > Cc: ipv6@ietf.org; Ran Atkinson
> > Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
> >
> > On 2011-03-10 00:17, Mikael Abrahamsson wrote:
> > > On Wed, 9 Mar 2011, Ran Atkinson wrote:
> > >
> > >>
> > >> <http://www.ietf.org/internet-drafts/draft-gont-6man-managing-
> > privacy-extensions-00.txt>
> > >>
> > >>
> > >> I recommend that folks read the above draft.  I haven't seen the
> > >> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
> > >> the volume of recent I-D postings, and the topic seems relevant.
> > >
> > > I don't think it solves what it thinks it solves, but if this REALLY
> > > should be implemented, it's my initial thinking that the H flag
> > should
> > > be a MUST demand to only have ONE and only one MAC-based IPv6 address
> > > according to EUI64. I would appreciate some reasoning in the draft
> > why
> > > this was chosen as a SHOULD option.
> >
> > For the reason I just gave against the disable-private flag: this
> > violates the host's right to use an untraceable address.
> >
> > It may be that in corporate deployments, that right can be removed.
>
> Nobody wants it removed in corporate deployments, either.  Consider
> for a moment an IPv6-enabled telephone, on the desk of a Very
> Important Person at a company, who is calling the CEO of some
> Itty Bitty Company.  And then the CEO calls.  Then someone on
> the acquisition team calls.  It hardly matters what they're talking
> about -- just seeing that traffic with those IPv6 addresses is
> sufficient to decide to buy (or sell) stock in Itty Bitty
> Company.
>
> We should, instead, look at how a host's privacy address can
> be reported and recorded, so the network administrator has all
> the necessary ability to determine which host is using which
> address now or in the past.  This is easily done -- without
> changing RA.
>
> If we don't have IPv6 privacy addresses, we will also soon
> see NAPT66 (with UDP and TCP port rewriting) in order to
> achieve the same result as privacy addresses:  trying to
> obfuscate which host is communicating.
>

+1.  Assume media and signalling are encrypted, node to node communication
can still reveal a lot.

Cb

> -d
>
>
> > But removing it for public subscribers would be a political blunder.
> >
> >     Brian
> >
> > >
> > > I do not like the "disable Privacy"-flag thinking at all and I really
> > > oppose going with that solution.
> > >
> > --------------------------------------------------------------------
> > 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
> --------------------------------------------------------------------

--90e6ba6e8d42e6875a049e229a25
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p><br>
On Mar 9, 2011 11:34 PM, &quot;Dan Wing&quot; &lt;<a href=3D"mailto:dwing@c=
isco.com">dwing@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.=
org</a> [mailto:<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.=
org</a>] On Behalf Of<br>
&gt; &gt; Brian E Carpenter<br>
&gt; &gt; Sent: Wednesday, March 09, 2011 10:49 AM<br>
&gt; &gt; To: Mikael Abrahamsson<br>
&gt; &gt; Cc: <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>; Ran Atkin=
son<br>
&gt; &gt; Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt<b=
r>
&gt; &gt;<br>
&gt; &gt; On 2011-03-10 00:17, Mikael Abrahamsson wrote:<br>
&gt; &gt; &gt; On Wed, 9 Mar 2011, Ran Atkinson wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; &lt;<a href=3D"http://www.ietf.org/internet-drafts/draft=
-gont-6man-managing-">http://www.ietf.org/internet-drafts/draft-gont-6man-m=
anaging-</a><br>
&gt; &gt; privacy-extensions-00.txt&gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; I recommend that folks read the above draft. =A0I haven&=
#39;t seen the<br>
&gt; &gt; &gt;&gt; I-D announcement get cross-posted to the IPv6 WG, perhap=
s due to<br>
&gt; &gt; &gt;&gt; the volume of recent I-D postings, and the topic seems r=
elevant.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don&#39;t think it solves what it thinks it solves, but if=
 this REALLY<br>
&gt; &gt; &gt; should be implemented, it&#39;s my initial thinking that the=
 H flag<br>
&gt; &gt; should<br>
&gt; &gt; &gt; be a MUST demand to only have ONE and only one MAC-based IPv=
6 address<br>
&gt; &gt; &gt; according to EUI64. I would appreciate some reasoning in the=
 draft<br>
&gt; &gt; why<br>
&gt; &gt; &gt; this was chosen as a SHOULD option.<br>
&gt; &gt;<br>
&gt; &gt; For the reason I just gave against the disable-private flag: this=
<br>
&gt; &gt; violates the host&#39;s right to use an untraceable address.<br>
&gt; &gt;<br>
&gt; &gt; It may be that in corporate deployments, that right can be remove=
d.<br>
&gt;<br>
&gt; Nobody wants it removed in corporate deployments, either. =A0Consider<=
br>
&gt; for a moment an IPv6-enabled telephone, on the desk of a Very<br>
&gt; Important Person at a company, who is calling the CEO of some<br>
&gt; Itty Bitty Company. =A0And then the CEO calls. =A0Then someone on<br>
&gt; the acquisition team calls. =A0It hardly matters what they&#39;re talk=
ing<br>
&gt; about -- just seeing that traffic with those IPv6 addresses is<br>
&gt; sufficient to decide to buy (or sell) stock in Itty Bitty<br>
&gt; Company.<br>
&gt;<br>
&gt; We should, instead, look at how a host&#39;s privacy address can<br>
&gt; be reported and recorded, so the network administrator has all<br>
&gt; the necessary ability to determine which host is using which<br>
&gt; address now or in the past. =A0This is easily done -- without<br>
&gt; changing RA.<br>
&gt;<br>
&gt; If we don&#39;t have IPv6 privacy addresses, we will also soon<br>
&gt; see NAPT66 (with UDP and TCP port rewriting) in order to<br>
&gt; achieve the same result as privacy addresses: =A0trying to<br>
&gt; obfuscate which host is communicating.<br>
&gt;</p>
<p>+1.=A0 Assume media and signalling are encrypted, node to node communica=
tion can still reveal a lot.</p>
<p>Cb<br></p>
<p>&gt; -d<br>
&gt;<br>
&gt;<br>
&gt; &gt; But removing it for public subscribers would be a political blund=
er.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Brian<br>
&gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I do not like the &quot;disable Privacy&quot;-flag thinking =
at all and I really<br>
&gt; &gt; &gt; oppose going with that solution.<br>
&gt; &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>

--90e6ba6e8d42e6875a049e229a25--

From jhw@apple.com  Thu Mar 10 08:00:50 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75F643A6B2F for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 08:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmiEyCkblvKn for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 08:00:49 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id BE17F3A68A9 for <ipv6@ietf.org>; Thu, 10 Mar 2011 08:00:49 -0800 (PST)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id D2007D7DF97E for <ipv6@ietf.org>; Thu, 10 Mar 2011 08:02:07 -0800 (PST)
X-AuditID: 11807136-b7c6bae000004a34-e1-4d78f5ffd243
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay15.apple.com (Apple SCV relay) with SMTP id F0.0A.18996.FF5F87D4; Thu, 10 Mar 2011 08:02:07 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.20] ([75.101.54.88]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LHU001HON7J2060@gertie.apple.com> for ipv6@ietf.org; Thu, 10 Mar 2011 08:02:07 -0800 (PST)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: james woodyatt <jhw@apple.com>
In-reply-to: <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>
Date: Thu, 10 Mar 2011 08:02:06 -0800
Message-id: <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>
To: Ran Atkinson <ran.atkinson@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 16:00:50 -0000

On Mar 10, 2011, at 4:10 AM, Ran Atkinson wrote:
> 
> It seems pretty clear that Fred's NPTv6 is going to be deployed in at least some locations, albeit for entirely  different reasons.  I'm not sure if that meets your definition of NAPT66 or not.

It does not.  NPTv6 only translates the network prefix; it therefore doesn't prevent global tracking of hosts that use EUI-64 interface identifiers.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From paul.chilton@nxp.com  Thu Mar 10 10:17:01 2011
Return-Path: <paul.chilton@nxp.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26A093A68F1 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 10:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YgxuaGKztC43 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 10:17:00 -0800 (PST)
Received: from be1ssnxpe1.nxp.com (be1ssnxpe1.nxp.com [57.67.164.69]) by core3.amsl.com (Postfix) with ESMTP id 1F4D63A68CB for <ipv6@ietf.org>; Thu, 10 Mar 2011 10:16:59 -0800 (PST)
Received: from EU1RDCRDC1VW024.exi.nxp.com ([134.27.176.169]) by be1ssnxpe1.nxp.com (8.14.3/8.14.3) with ESMTP id p2AIIEDA028771 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 10 Mar 2011 19:18:14 +0100
Received: from eu1rdcrdc1wx032.exi.nxp.com ([134.27.179.186]) by EU1RDCRDC1VW024.exi.nxp.com ([134.27.176.169]) with mapi; Thu, 10 Mar 2011 19:18:14 +0100
From: Paul Chilton <paul.chilton@nxp.com>
To: james woodyatt <jhw@apple.com>
Date: Thu, 10 Mar 2011 19:18:12 +0100
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AcvfPImkSrHUQZ1RTwmX5CUIKMyXDQAEhMlg
Message-ID: <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>
In-Reply-To: <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.2.15, 1.0.148, 0.0.0000 definitions=2011-03-10_08:2011-03-10, 2011-03-10, 1970-01-01 signatures=0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 18:17:01 -0000

Doesn't a combination of RFC4941 and NPTv6 produce the necessary privacy ov=
er both parts of the IPv6 address?=20
(BTW thats a question from an interested observer new to this topic, not a =
statement - I started following this thread and ended up digging around in =
the RFCs and drafts the thread uncovered)


Paul Chilton
Low Power RF Solutions (formerly Jennic)
NXP Semiconductors


-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of jam=
es woodyatt
Sent: 10 March 2011 16:02
To: Ran Atkinson
Cc: ipv6@ietf.org
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt

On Mar 10, 2011, at 4:10 AM, Ran Atkinson wrote:
>=20
> It seems pretty clear that Fred's NPTv6 is going to be deployed in at lea=
st some locations, albeit for entirely  different reasons.  I'm not sure if=
 that meets your definition of NAPT66 or not.

It does not.  NPTv6 only translates the network prefix; it therefore doesn'=
t prevent global tracking of hosts that use EUI-64 interface identifiers.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking



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

From dwing@cisco.com  Thu Mar 10 11:52:01 2011
Return-Path: <dwing@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B29953A67FF for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 11:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.57
X-Spam-Level: 
X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YPD+mDvKzChT for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 11:51:58 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 6C5A93A696F for <ipv6@ietf.org>; Thu, 10 Mar 2011 11:51:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2375; q=dns/txt; s=iport; t=1299786795; x=1300996395; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=F8o/LbH6HX5kU1hsw38kcjKMDs8OZu25Ud2LDTKUhS0=; b=Wc4sdC51vXAWUq5n2ELWiyTGyxcSJ34phn2eDlonKy4/zf7bnlmhXkSu zmv3oSkDGPHw5u1S1o1SCfY0svxWmk2pVunzRCTusyU0zptvhmoiCRJjc wDigDagBCjllrtlcbSJI40R8YGbd9B8OH+7bTaHR3MAQmZAeiPV/TIHqL c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBAOu6eE2rR7H+/2dsb2JhbACYX4Fki253pUicMYViBIUk
X-IronPort-AV: E=Sophos;i="4.62,297,1297036800"; d="scan'208";a="276847016"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 10 Mar 2011 19:53:13 +0000
Received: from dwingWS ([10.32.240.195]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p2AJrDXq023512; Thu, 10 Mar 2011 19:53:13 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Ran Atkinson'" <ran.atkinson@gmail.com>, <ipv6@ietf.org>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>
In-Reply-To: <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Date: Thu, 10 Mar 2011 11:53:12 -0800
Message-ID: <262e01cbdf5c$ca372cf0$5ea586d0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvfHCE+bOTkuaBZQTi1E8M4VbAJ/gAP5kmg
Content-Language: en-us
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 19:52:02 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Ran Atkinson
> Sent: Thursday, March 10, 2011 4:10 AM
> To: ipv6@ietf.org
> Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
> 
> 
> On 10  Mar 2011, at 02:34 , Dan Wing wrote:
> > Nobody wants it removed in corporate deployments, either.
> 
> That statement is far too strong; it simply is not true.
> 
> > Consider for a moment an IPv6-enabled telephone,
> > on the desk of a Very Important Person at a company, ...
> 
> (Laugh.  I don't believe in that untrue example for a second,
> but thanks for the humorous start to my morning.  :-)

Laughing at IPv6, or an IP telephone on someone's desk, or
the combination of the two?

> Oh, and consider that Caller-ID, usually including a full name,
> is already widely deployed in many countries.  It is so
> much simpler just to read the Caller-ID string off of the
> telephone handset.
>
> If one wants to intercept traffic, it is MUCH simpler to intercept
> the SIP traffic -- which is never encrypted in real-world corporate
> deployments because that would make VoIP too hard to debug.

Ergo, we should let it all hang out?

We have many customers which enable encryption on their IP PBXs.
All of our telepresence systems ship with encryption enabled 
by default (both signaling and media).

If you didn't like the SIP example, is SIP the one and only case 
where an IPv6 privacy address is useful?

> > If we don't have IPv6 privacy addresses, we will also soon
> > see NAPT66 (with UDP and TCP port rewriting) in order to
> > achieve the same result as privacy addresses:  trying to
> > obfuscate which host is communicating.
> 
> It seems pretty clear that Fred's NPTv6 is going to be
> deployed in at least some locations, albeit for entirely
> different reasons.  I'm not sure if that meets your
> definition of NAPT66 or not.

It doesn't; NPTv6 does not provide obfuscation of the endpoint,
because it only rewrites the IPv6 prefix.

-d


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


From dwing@cisco.com  Thu Mar 10 11:56:08 2011
Return-Path: <dwing@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D2713A6962 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 11:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.57
X-Spam-Level: 
X-Spam-Status: No, score=-110.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkrqNRskFwSx for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 11:56:07 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id D32DE3A67FF for <ipv6@ietf.org>; Thu, 10 Mar 2011 11:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2683; q=dns/txt; s=iport; t=1299787046; x=1300996646; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=OPXKaIv+SAAPWEk7leN0ZCOXt7+Cy23GHKBLzxg/1aw=; b=LAj94si0xPwJ77H8A0/sozoj6yIEmkgqewT5SinxWsu9BX/Qv4WpgP7L iev+bNbdq5bKtWQva4FrqAZART+k1xujr4HRVLmFX1HP5tH6KQ1DQzIZv ggXJsUL3wPHZCEfuCeQAPNZUF9PZ6GVNWvR6d7QnzlWxF0/zBgvlzHUtH w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggBAJ67eE2rR7H+/2dsb2JhbACYX4Fki253pTScMYViBIUk
X-IronPort-AV: E=Sophos;i="4.62,297,1297036800"; d="scan'208";a="319288080"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 10 Mar 2011 19:57:26 +0000
Received: from dwingWS ([10.32.240.195]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p2AJvPXc028366; Thu, 10 Mar 2011 19:57:25 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Paul Chilton'" <paul.chilton@nxp.com>, "'james woodyatt'" <jhw@apple.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>
In-Reply-To: <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Date: Thu, 10 Mar 2011 11:57:25 -0800
Message-ID: <262f01cbdf5d$607c69f0$21753dd0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvfPImkSrHUQZ1RTwmX5CUIKMyXDQAEhMlgAAOQCYA=
Content-Language: en-us
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 10 Mar 2011 19:56:08 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Paul Chilton
> Sent: Thursday, March 10, 2011 10:18 AM
> To: james woodyatt
> Cc: ipv6@ietf.org
> Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
> 
> Doesn't a combination of RFC4941 and NPTv6 produce the necessary
> privacy over both parts of the IPv6 address?
> (BTW thats a question from an interested observer new to this topic,
> not a statement - I started following this thread and ended up digging
> around in the RFCs and drafts the thread uncovered)

RFC4941 by itself does the trick.

But draft-gont-6man-managing-privacy-extensions (the subject of
this thread) says "you can't use RFC4941".

I'm saying the reasons people are tempted to disable RFC4941 are
misplaced.  Really, they want the same tracking of 
which-host-is-using-which-address that they have, today, with
DHCPv4 (by examining the DHCP server's logs) and have, today,
with DHCPv6 (by examining the DHCPv6 server's logs).  Thus the
desire to simply throw away RFC4941 (sorry, "disable on this 
network") is misplaced.  We should devote our energies 
elsewhere and provide the means to log use of a SLAAC address.

-d


> 
> Paul Chilton
> Low Power RF Solutions (formerly Jennic)
> NXP Semiconductors
> 
> 
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> james woodyatt
> Sent: 10 March 2011 16:02
> To: Ran Atkinson
> Cc: ipv6@ietf.org
> Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
> 
> On Mar 10, 2011, at 4:10 AM, Ran Atkinson wrote:
> >
> > It seems pretty clear that Fred's NPTv6 is going to be deployed in at
> least some locations, albeit for entirely  different reasons.  I'm not
> sure if that meets your definition of NAPT66 or not.
> 
> It does not.  NPTv6 only translates the network prefix; it therefore
> doesn't prevent global tracking of hosts that use EUI-64 interface
> identifiers.
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, core os networking
> 
> 
> 
> --------------------------------------------------------------------
> 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 huitema@microsoft.com  Thu Mar 10 18:31:20 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 569573A6AC2 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.566
X-Spam-Level: 
X-Spam-Status: No, score=-10.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HLZe71Ji8KO for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:31:16 -0800 (PST)
Received: from smtp.microsoft.com (mail3.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 350B33A69B6 for <ipv6@ietf.org>; Thu, 10 Mar 2011 18:31:16 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Thu, 10 Mar 2011 18:32:34 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.270.2; Thu, 10 Mar 2011 18:32:34 -0800
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.56]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0270.002; Thu, 10 Mar 2011 18:32:34 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Dan Wing <dwing@cisco.com>, 'Paul Chilton' <paul.chilton@nxp.com>, "'james woodyatt'" <jhw@apple.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AQHL3kEKAbTYw5EzSU+RGMZ29OXheJQlYKSAgAB+ZoCAANWqgIAATRSAgABA0wCAACYHAIAAG7iA///mPyA=
Date: Fri, 11 Mar 2011 02:32:32 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com>
In-Reply-To: <262f01cbdf5d$607c69f0$21753dd0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.90]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 02:31:20 -0000

> I'm saying the reasons people are tempted to disable RFC4941 are misplace=
d. =20

+1

Consider that if I want privacy and you won't let me use RFC4941, I might j=
ust make up a new MAC address each time I connect.

Consider also the effect of unique identifiers on tracking. The MAC address=
 follows you when you roam. By embedding it in the IPv6 address, we are eff=
ectively offering a "super cookie" to all web services. Is it really what w=
e want? In addition to privacy issues, displaying the MAC address allows th=
ird parties to track hardware purchase, and enables other attacks by provid=
ing the data necessary for MAC spoofing. In short, it looked like a great i=
dea at the time... but wasn't.

-- Christian Huitema





From dougb@dougbarton.us  Thu Mar 10 18:52:16 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 078E73A67F2 for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xjmekyT3nPI for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 18:52:15 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id CD02D3A6819 for <ipv6@ietf.org>; Thu, 10 Mar 2011 18:52:14 -0800 (PST)
Received: (qmail 15681 invoked by uid 399); 11 Mar 2011 02:53:31 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 11 Mar 2011 02:53:31 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D798EA9.2070402@dougbarton.us>
Date: Thu, 10 Mar 2011 18:53:29 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110304 Thunderbird/3.1.9
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com> <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 02:52:16 -0000

On 03/09/2011 06:57, Mikael Abrahamsson wrote:
> If you want to know the mac address of the computer who used an IP
> address at a certain time, then you need to tell the host to only use
> EUI64 based address and nothing else, you don't tell it to disable
> privacy extensions. Just because privacy extensions is the only address
> widely seen today as being non-EUI64, doesn't mean that if you disable
> privacy, you get only single EUI64.

Right. When I was at Yahoo! we had a db of mac addresses of authorized 
hosts, and used that to drive configuration of the switches, dhcp, dns, 
etc. that way we could be sure that only authorized hosts had access to 
the network. If you don't manage access at the switch level, you can't 
guarantee what the client is going to do, regardless of what flags are 
sent in SLAAC.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From narten@us.ibm.com  Thu Mar 10 20:03:43 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 423FD3A680D for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 20:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0E3JLIi3uqD for <ipv6@core3.amsl.com>; Thu, 10 Mar 2011 20:03:41 -0800 (PST)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by core3.amsl.com (Postfix) with ESMTP id B9D643A6B72 for <ipv6@ietf.org>; Thu, 10 Mar 2011 20:03:41 -0800 (PST)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e35.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p2B3nt0i027611 for <ipv6@ietf.org>; Thu, 10 Mar 2011 20:49:55 -0700
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p2B44vxB117302 for <ipv6@ietf.org>; Thu, 10 Mar 2011 21:04:57 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p2B44uTb009551 for <ipv6@ietf.org>; Thu, 10 Mar 2011 21:04:56 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-48-45-217.mts.ibm.com [9.48.45.217]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p2B44t65008821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Mar 2011 21:04:56 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p2B44sD4021062; Thu, 10 Mar 2011 23:04:54 -0500
Message-Id: <201103110404.p2B44sD4021062@cichlid.raleigh.ibm.com>
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-node-req-bis-07.txt>
In-reply-to: <alpine.LRH.2.02.1102181052020.3891@netcore.fi>
References: <7B63F7B6-D788-4A05-9722-C1CAAA42B754@gmail.com> <201101171932.p0HJWU58003756@cichlid.raleigh.ibm.com> <alpine.LRH.2.02.1102181052020.3891@netcore.fi>
Comments: In-reply-to Pekka Savola <pekkas@netcore.fi> message dated "Fri, 18 Feb 2011 10:55:18 +0200."
Date: Thu, 10 Mar 2011 23:04:54 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 04:03:43 -0000

Pekka Savola <pekkas@netcore.fi> writes:

> I have reviewed this document.

Thanks agin!

> The most important omission is that RFC4294 changelog is not up-to-date.
> This gives a good overview on what has changed and it needs to convey
> accurate information.

ACK.

I've just posted a new version. Have a look to see the changes.

> At the same time, I'd also add (or check from WG) if some of the RFCs
> not listed should be included.

We've done multiple passes on trying to include all relevant
RFCs. Seems to be a never-ending task...

> Some requirement levels have also changed, and explicit support from
> WG would be good on these.  With an updated RFC4294 changelog, rough
> consensus on the result could be evaluated.

OK. But to be clear, the changes in this document have been discussed
on the list and IMO do have consensus. I.e., they are not "surprises".

> I think a brief WGLC should be warranted after document update.

OK (if we can get more reviewers!)

> The document should be IETF last called.

No objection.

> WG should explicitly request feedback from at least IPSECME WG.

IPsecME has seen and reviewed text. Indeed, some IPsecME members
helped with getting the text right. I also presented the text at the
saag meeting in Maastricht

> substantial
> -----------

> General:

> Section 21 describes Changes from RFC 4294.  This is not up-to-date. 
> Specifically, at least S 17-20 describe changes between draft versions that
> are not incorporated in S 21.  As "changes between drafts" sections are
> removed upon publication, it is important that the changes from the previous
> RFC are complete.  The updated RFC references are of medium importance
> (there are significant changes e.g. in the requirements imposed by ICMP
> specification versons), but changes in requirement level seem like a high
> importance issue. As such the former could be addressed with a short
> list.

I took a stab at this, but I'm not sure I got all the major
changes. In particular, there were a couple of revs of the ID before
we started adding changes between versions.

> This is a very important section for a document like this as just by
> looking at it you should be able to see the major new requirements
> or changes in requirements.  Therefore, updating this should be the
> first priority.  Then I would suggest another Last Call, just to
> make sure there's rough consensus on these higher level bits.

fine with me.

> Specific not in text:
> ---------------------

> I think this document should also discuss APIs we have defined and that
> relate to the protocols described in the document.  A separate section
> should be added on this.

I added a section on APIs. I made them all FYIs. I agree with the
comments others have made on the list that we can't mandate them.

> RFC4191 (Default Router Preferences and More-Specific Routes) should
> be discussed.  Is this a MAY?  Quite a few host implementations
> already support it.

I added it as a MAY. I don't think its widely enough implmented or
used (?) to say this is even a SHOULD.

> In the context of autoconfiguration, RFC5453 (Reserved IPv6
> Interface Identifiers) should probably be discussed. My quick
> (re-)read of it seems to say that every host should avoid the
> designated IIDs. Is host support needed for this?

I added a reference to 5453 to the section on temporary addresses.

> Should Node Information Queries be mentioned (RFC4620)?  It would be
> a MAY.  I'm fine with leaving it out.

I think not. AFAIK, its not widely used.

> S 5.8.2 could refer to RFC4429 (Optimistic DAD) with a MAY support.

I added a paragraph on this, but made it clear this is not something
that general purpose nodes need to do at this time.

> The document is silent on Flow Label (as Brian mentioned).  Rather than
> silence, I might be tempted to say something at least from the current
> perspective.  The key point here is, "are hosts expected to randomize or
> otherwise by default set a flow label"?

I'll defer to the list for guidance. That said, the general position
being taken for this document is not to update other specs, but to
refer to them. Given the Flow Label spec is under review, I don't
think we should say much. 

> Specific on text:
> -----------------

> S 5.2 no longer requires support for DAD but this is actually done 
> in S 5.8.2.  A pointer might be helpful (though not necessary).

I think what I did was consolidate text that was (previously) in two
sections in RFC 4294.

> Text on redirects is also new, but probably not very controversial.

It was taken from the mailing list...

> S 5.5.1 does not make any (uppercase) recommendation on PMTUD like the
> previous version did, just quoting RFC2460.

That was intentional.  I don't see why we need to say you MUST do
2460, and then go and say you MUST/SHOULD do things that are required
in 2460 already. That seems redudent to me, and raises the question of
why we do that for some, but not other pieces. AFAICT, most everyone
implements PMTUD. So I don't think we need to call out any part of RFC
1981 specifically.

> line with: "Path MTU Discovery [RFC1981] SHOULD be Supported. From
> [RFC2460]:"

done


> S 5.8.3 has watered down the privacy addresses text:

>     In such situations, RFC4941 SHOULD be implemented.  In other cases,
>     such as with dedicated servers in a data center, RFC4941 provides
>     limited or no benefit.

> .. this is not acceptable.  Per previous RFC, we should say:

>     RFC4941 SHOULD be supported.

I strongly disagree, and there was a thread about this. I have seen
cases where people just assume that 4941 should be supported by all
nodes, including servers (not clients) in data centers. There is no
need to implement 4941 on server-only systems.

Please review the thread at
http://www.ietf.org/mail-archive/web/ipv6/current/msg10468.html and if
you have further comments, speak up. But it was an explicit goal to
not just say "SHOULD" with not context/direction, as RFC 4294 does.

> We could also add (or make specific recommendations):
>     This document does not make a generic recommendation on the default
>     behaviour.

> I note that previous version of the doc also suggested privacy be configurable
> on per-connection basis, etc. -- this text has been removed now. (I did not
> dig deeper whether it has been incorporated in RFC4941 revisions
> etc.)

Discussed on list (a very long while back). The suggestion to do
per-connection overrides and all was deemed as going too far.

> In S 5.9,
>     A reference should be added (MAY support) to RFC 5790, 
> "Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and
> Multicast Listener Discovery Version 2 (MLDv2) Protocols"

Actually, I may need some help with this.

If 5790 is enough, and omits functionality that most nodes don't need,
we should recommend its usage.

We should provide clear guidance on when it makes sense to recommend
one over the other.

> In S 7.3:
>     Implementations SHOULD implement the DNS RA option [RFC6106].

> .. is this too strong?  DHCP is (only) a conditional SHOULD. I'm OK with
> this as it is, but I would also be fine with a MAY.

This was discussed on the list (a little). I could go either way.
Curent text is a SHOULD (see Section 7.3 of the draft).

> In S 10, Certain Mobile IP-specific SHOULDs have been downgraded to
> a general MAY.  I'm fine with this but I would have been OK with
> retaining those specific SHOULDs.

Long list discussion. I think the feeling about MIPv6 has changed. It
has clearly not been deployed and there may be better alternatives
now.  Hence, a MAY.

> In S 11, IPsec and IKE have been downgraded to a SHOULD. I'm fine with this.
> (None of the changes I've mentioned are listed in the changelog.)

Added to changelog. And discussed in all the right places, (6man,
saag, ipsecme).

> editorial:
> ----------
>     -  Transmission of IPv6 over IPv4 Domains without Explicit Tunnels
>        [RFC2529]

> ... even as an example, this is a bad one. It is not used and there exists
> probably about one implementation.  I suggest replacing this with RFC4213
> (an existing reference).

Done.

> 5.9. Multicast Listener Discovery (MLD) for IPv6 - RFC 2710

> .. take out the RFC number from the title as you're actually addressing two
> different MLD versions in this subsection.

Done.

>     The following two MIBs SHOULD be supported by nodes that support an
>     SNMP agent.

> .. s/MIBs/MIB modules/ :P

Done.

Thomas

From Internet-Drafts@ietf.org  Thu Mar 10 20:15:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2FBE83A6A60; Thu, 10 Mar 2011 20:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmcBVVpq4qQ7; Thu, 10 Mar 2011 20:15:01 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77AAE3A6860; Thu, 10 Mar 2011 20:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-node-req-bis-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110311041501.15290.60634.idtracker@localhost>
Date: Thu, 10 Mar 2011 20:15:01 -0800
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 04:15:02 -0000

--NextPart

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


	Title           : IPv6 Node Requirements RFC 4294-bis
	Author(s)       : E. Jankiewicz, et al.
	Filename        : draft-ietf-6man-node-req-bis-08.txt
	Pages           : 29
	Date            : 2011-03-10

This document defines requirements for IPv6 nodes.  It is expected
that IPv6 will be deployed in a wide range of devices and situations.
Specifying the requirements for IPv6 nodes allows IPv6 to function
well and interoperate in a large number of situations and
deployments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-node-req-bis-08.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-node-req-bis-08.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-10200317.I-D@ietf.org>


--NextPart--

From narten@us.ibm.com  Fri Mar 11 04:50:31 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 479CD3A6BA8 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 04:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StCrHnRNF35V for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 04:50:27 -0800 (PST)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by core3.amsl.com (Postfix) with ESMTP id ED5FC3A6A17 for <ipv6@ietf.org>; Fri, 11 Mar 2011 04:50:26 -0800 (PST)
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e31.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p2BCaUoi005414 for <ipv6@ietf.org>; Fri, 11 Mar 2011 05:36:30 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p2BCpbI5100522 for <ipv6@ietf.org>; Fri, 11 Mar 2011 05:51:37 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p2BCpaYF011889 for <ipv6@ietf.org>; Fri, 11 Mar 2011 05:51:37 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-154-135.mts.ibm.com [9.49.154.135]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p2BCpZOY011841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Mar 2011 05:51:36 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p2BCpTO6024851; Fri, 11 Mar 2011 07:51:34 -0500
Message-Id: <201103111251.p2BCpTO6024851@cichlid.raleigh.ibm.com>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
In-reply-to: <20110310064328.3388ce88@opy.nosense.org>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <A8E3ED1C-D74F-4B16-8CBE-049CA30B7D29@gmail.com> <4D77D5DD.40100@joelhalpern.com> <20110310064328.3388ce88@opy.nosense.org>
Comments: In-reply-to Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org> message dated "Thu, 10 Mar 2011 06:43:28 +1030."
Date: Fri, 11 Mar 2011 07:51:29 -0500
From: Thomas Narten <narten@us.ibm.com>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 12:50:31 -0000

Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org> writes:

> I also think there is a fundamentally incorrect assumption is being
> made - that IPv6 addresses and humans are tightly coupled.

Actually, if you look at trends, they are increasingly tightly
coupled.

Internet access by humans is increasingly through single-owner devices
(recently laptops, but increasingly smart phones and the like, which
are typically single-owner). Indeed, I've seen projections that assert
that sometime this year more people will access the Internet though
Mobile Wireless devices than through traditional computers. The
primary method of Internet access is changing...

> An IPv6 address identifies an end-node, and the traffic to or from
> it, but does not always identify the human that caused that traffic
> to occur.

True, but if it correctly identifies the human in 70, 80, or 90% of
the cases, that's likely good enough for "innovation" to move in and
exploit such characteristics.

Up levelling, this draft simply reopens a discussion that was had back
when stateless addrconf was first defined. Today, there is no easy way
for the network adminstrator to "configure" clients. When stateless
addrconf is used, there are pretty much no mechanisms for
communicating network preferences or policy.

Allowing/disallowing temporary addresses is one instance of a broader
problem. Another example of policy that would be useful to commnicate
is address selection preferences. Hence, if we are going to define
something like an "H bit", we should really look at the more general
problem.

And, even if there was a mechanism for the network to communicate its
preferences/policies, we'd still have the problem that end hosts could
simply ignore or override those preferences. 

There is no good/easy/simple answer here folks.

Thomas

From mark@townsley.net  Fri Mar 11 04:52:44 2011
Return-Path: <mark@townsley.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 681993A6987 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 04:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vJX3O7MENl3p for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 04:52:43 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 42AD93A6985 for <ipv6@ietf.org>; Fri, 11 Mar 2011 04:52:43 -0800 (PST)
Received: by fxm15 with SMTP id 15so1032872fxm.31 for <ipv6@ietf.org>; Fri, 11 Mar 2011 04:54:01 -0800 (PST)
Received: by 10.223.58.80 with SMTP id f16mr1244197fah.148.1299848041502; Fri, 11 Mar 2011 04:54:01 -0800 (PST)
Received: from saturn.livebox.home (AMontsouris-159-1-12-106.w83-202.abo.wanadoo.fr [83.202.167.106]) by mx.google.com with ESMTPS id n26sm1881378fam.37.2011.03.11.04.53.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2011 04:53:58 -0800 (PST)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <262f01cbdf5d$607c69f0$21753dd0$@com>
Date: Fri, 11 Mar 2011 13:53:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7BA465C-35FF-4D13-98FC-6DA91F13C02D@townsley.net>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 12:52:44 -0000

On Mar 10, 2011, at 8:57 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
>> Paul Chilton
>> Sent: Thursday, March 10, 2011 10:18 AM
>> To: james woodyatt
>> Cc: ipv6@ietf.org
>> Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
>>=20
>> Doesn't a combination of RFC4941 and NPTv6 produce the necessary
>> privacy over both parts of the IPv6 address?
>> (BTW thats a question from an interested observer new to this topic,
>> not a statement - I started following this thread and ended up =
digging
>> around in the RFCs and drafts the thread uncovered)
>=20
> RFC4941 by itself does the trick.
>=20
> But draft-gont-6man-managing-privacy-extensions (the subject of
> this thread) says "you can't use RFC4941".
>=20
> I'm saying the reasons people are tempted to disable RFC4941 are
> misplaced.  Really, they want the same tracking of=20
> which-host-is-using-which-address that they have, today, with
> DHCPv4 (by examining the DHCP server's logs) and have, today,
> with DHCPv6 (by examining the DHCPv6 server's logs).  Thus the
> desire to simply throw away RFC4941 (sorry, "disable on this=20
> network") is misplaced.  We should devote our energies=20
> elsewhere and provide the means to log use of a SLAAC address.

In addition to the logging, don't forget the MAC-IP mappings in switches =
(SAVI) and wi-fi access points (AP roaming). Talking with our friends at =
Microsoft, their recommendation was to plan for accommodating 9 IPv6 =
addresses per interface for hosts with privacy addressing (vs. one of =
course for IPv4). None of that is rocket science, nor beyond our ability =
to build hardware for, but it certainly doesn't help the IPv4 vs. IPv6 =
cost equation at these points in the network :-/

- Mark


>=20
> -d
>=20
>=20
>>=20
>> Paul Chilton
>> Low Power RF Solutions (formerly Jennic)
>> NXP Semiconductors
>>=20
>>=20
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf =
Of
>> james woodyatt
>> Sent: 10 March 2011 16:02
>> To: Ran Atkinson
>> Cc: ipv6@ietf.org
>> Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
>>=20
>> On Mar 10, 2011, at 4:10 AM, Ran Atkinson wrote:
>>>=20
>>> It seems pretty clear that Fred's NPTv6 is going to be deployed in =
at
>> least some locations, albeit for entirely  different reasons.  I'm =
not
>> sure if that meets your definition of NAPT66 or not.
>>=20
>> It does not.  NPTv6 only translates the network prefix; it therefore
>> doesn't prevent global tracking of hosts that use EUI-64 interface
>> identifiers.
>>=20
>>=20
>> --
>> james woodyatt <jhw@apple.com>
>> member of technical staff, core os networking
>>=20
>>=20
>>=20
>> --------------------------------------------------------------------
>> 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
>> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From mark@townsley.net  Fri Mar 11 05:01:55 2011
Return-Path: <mark@townsley.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73B103A6BE4 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 05:01:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9YXffMMmzZHB for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 05:01:54 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 004293A6BD6 for <ipv6@ietf.org>; Fri, 11 Mar 2011 05:01:53 -0800 (PST)
Received: by fxm15 with SMTP id 15so1041038fxm.31 for <ipv6@ietf.org>; Fri, 11 Mar 2011 05:03:12 -0800 (PST)
Received: by 10.223.65.196 with SMTP id k4mr1011298fai.9.1299848519259; Fri, 11 Mar 2011 05:01:59 -0800 (PST)
Received: from saturn.livebox.home (AMontsouris-159-1-12-106.w83-202.abo.wanadoo.fr [83.202.167.106]) by mx.google.com with ESMTPS id l3sm2624393fan.2.2011.03.11.05.01.57 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2011 05:01:57 -0800 (PST)
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-9--581229240
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Fri, 11 Mar 2011 14:01:57 +0100
Message-Id: <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com> <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1082)
Cc: draft-brim-mobility-and-privacy@tools.ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 13:01:55 -0000

--Apple-Mail-9--581229240
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Mar 11, 2011, at 3:32 AM, Christian Huitema wrote:

>> I'm saying the reasons people are tempted to disable RFC4941 are =
misplaced. =20
>=20
> +1
>=20
> Consider that if I want privacy and you won't let me use RFC4941, I =
might just make up a new MAC address each time I connect.
>=20
> Consider also the effect of unique identifiers on tracking. The MAC =
address follows you when you roam. By embedding it in the IPv6 address, =
we are effectively offering a "super cookie" to all web services. Is it =
really what we want? In addition to privacy issues, displaying the MAC =
address allows third parties to track hardware purchase, and enables =
other attacks by providing the data necessary for MAC spoofing. In =
short, it looked like a great idea at the time... but wasn't.

One person's attack is another's targeted ad business case ;-)

That aside, the considerations proposed in this document may be relevant =
to this discussion:

http://tools.ietf.org/html/draft-brim-mobility-and-privacy-00

- Mark



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


--Apple-Mail-9--581229240
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 11, 2011, at 3:32 AM, Christian Huitema =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><blockquote type=3D"cite">I'm saying the reasons =
people are tempted to disable RFC4941 are misplaced. =
&nbsp;<br></blockquote><br>+1<br><br>Consider that if I want privacy and =
you won't let me use RFC4941, I might just make up a new MAC address =
each time I connect.<br><br>Consider also the effect of unique =
identifiers on tracking. The MAC address follows you when you roam. By =
embedding it in the IPv6 address, we are effectively offering a "super =
cookie" to all web services. Is it really what we want? In addition to =
privacy issues, displaying the MAC address allows third parties to track =
hardware purchase, and enables other attacks by providing the data =
necessary for MAC spoofing. In short, it looked like a great idea at the =
time... but wasn't.<br></div></blockquote><div><br></div><div>One =
person's attack is another's targeted ad business case =
;-)</div><div><br></div><div>That aside, the considerations proposed in =
this document may be relevant to this =
discussion:</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-brim-mobility-and-privacy-00">htt=
p://tools.ietf.org/html/draft-brim-mobility-and-privacy-00</a></div><div><=
br></div><div>- Mark</div><div><br></div><div><br></div><br><blockquote =
type=3D"cite"><div><br>-- Christian =
Huitema<br><br><br><br><br>-----------------------------------------------=
---------------------<br>IETF IPv6 working group mailing list<br><a =
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Administrative =
Requests: =
https://www.ietf.org/mailman/listinfo/ipv6<br>----------------------------=
----------------------------------------<br></div></blockquote></div><br><=
/body></html>=

--Apple-Mail-9--581229240--

From bob.hinden@gmail.com  Fri Mar 11 06:55:25 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 173613A6C38 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 06:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.509
X-Spam-Level: 
X-Spam-Status: No, score=-103.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id frXe4CnkJMJw for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 06:55:24 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 553EB3A6BFF for <ipv6@ietf.org>; Fri, 11 Mar 2011 06:55:24 -0800 (PST)
Received: by iwl42 with SMTP id 42so3362785iwl.31 for <ipv6@ietf.org>; Fri, 11 Mar 2011 06:56:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=8+kUzATK85DMfRfqMDqO/lvmiksvhCFpXRbz4nqn8bc=; b=aixwHs7JkmVDU/eWYFriMQw0YhwUfqQLRxPA6y6Pqtv8cDxjwBfALz+9GmDwt53okL Q5OXrvHBMFk7eTyTRTrjyLqPFlaqEvb0JLlPwu6i97u94hozIQHIlWW8Qiz/lButLP6t KJV4+vbvKeDbHeW1yy23i3FpyHFe1wSlVAPkY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=vjoMrNLSSjwdKvgeCHgwLGL3DgsmDp78aUWjAFpTDnDT65ofwlGCVVLoXM6/b4PF81 5fXV0tDPMMgLLhDWuluy/UkzEjX55sf4Ey6ef32Qy1Pwts+N3FESly7TbOm+5AIQ7MGl 6Wa056dN5ckbch5uow/G59fohPo8aqENYndJI=
Received: by 10.42.18.197 with SMTP id y5mr4021033ica.317.1299855403468; Fri, 11 Mar 2011 06:56:43 -0800 (PST)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id xa8sm3175329icb.22.2011.03.11.06.56.42 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2011 06:56:42 -0800 (PST)
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-node-req-bis-07.txt>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <201103110404.p2B44sD4021062@cichlid.raleigh.ibm.com>
Date: Fri, 11 Mar 2011 06:56:41 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7D450B3-E1EC-49B5-B542-DC1AD686A5D9@gmail.com>
References: <7B63F7B6-D788-4A05-9722-C1CAAA42B754@gmail.com> <201101171932.p0HJWU58003756@cichlid.raleigh.ibm.com> <alpine.LRH.2.02.1102181052020.3891@netcore.fi> <201103110404.p2B44sD4021062@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1082)
Cc: 6man Mailing List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 14:55:25 -0000

One small clarification from the chairs to avoid any confusion.

>=20
>> The document should be IETF last called.
>=20
> No objection.

All documents the 6man w.g. advances to the IESG are IETF last called.  =
It's not an optional step.

Bob & Brian





From d.sturek@att.net  Fri Mar 11 08:01:58 2011
Return-Path: <d.sturek@att.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E28F43A69F7 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.451
X-Spam-Level: 
X-Spam-Status: No, score=0.451 tagged_above=-999 required=5 tests=[AWL=-1.000,  BAYES_50=0.001, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7REvxUApgr9 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:01:55 -0800 (PST)
Received: from nm15-vm0.bullet.mail.ne1.yahoo.com (nm15-vm0.bullet.mail.ne1.yahoo.com [98.138.91.70]) by core3.amsl.com (Postfix) with SMTP id 2921C3A69D6 for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:01:55 -0800 (PST)
Received: from [98.138.90.56] by nm15.bullet.mail.ne1.yahoo.com with NNFMP; 11 Mar 2011 16:03:08 -0000
Received: from [98.138.89.174] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 11 Mar 2011 16:03:08 -0000
Received: from [127.0.0.1] by omp1030.mail.ne1.yahoo.com with NNFMP; 11 Mar 2011 16:03:08 -0000
X-Yahoo-Newman-Id: 805338.32881.bm@omp1030.mail.ne1.yahoo.com
Received: (qmail 87487 invoked from network); 11 Mar 2011 16:03:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1299859388; bh=b6OpjaVa+9c2EonM6WO+nLS4JkumRRWYOxbNoLnFHeg=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Reply-To:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language; b=wtKjkn42xA545p3PY0qySAvogtRDcSz4u6k6TmNLE8jU6SKs+1ko4zK9L+iT0H0OvXoV4poNImjYGJhmAQ/tPS5Hq4XNhUl6lLFtABbAia/JtK3ZxHb9M9+KkFALbQDLpm1pEqWVvdxlxMpgSnWmqNkzy+X4ddu6x6dJY8GtEyQ=
Received: from Studio (d.sturek@69.105.138.3 with login) by smtp101.sbc.mail.ne1.yahoo.com with SMTP; 11 Mar 2011 08:03:08 -0800 PST
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
X-YMail-OSG: C25BEIQVM1npUh28UP.cHv5CcrpzV5phzGrGI.fZGaXxQVN 5YBQg0.EWIN1N.oBhfP32TlV2YqfHoexgrtrZM5mAQ6vt5EGlZupXqOdl6PY kF4VWbd.Mer3vwh3pr5b9NUNZgP5P7EBGmQK2R_1vw0_SK_3sioCkqBpH9TZ CWLQwqlr0FtMHP9To8vw4ScYyE4VIByzq2T4iAXC4yE17eYY_9WG4rv8hFf0 61t3mDVDaP7fz__bu6q2cqPBMJJugKpFOAuEkQ34fuvI9cZ5CuDHwMwk036. I4IftAxBl3B1jEx5QSIY2gXKiOlM-
X-Yahoo-Newman-Property: ymail-3
From: "Don Sturek" <d.sturek@att.net>
To: <ipv6@ietf.org>
Subject: Status of ROLL RPL related drafts in 6man
Date: Fri, 11 Mar 2011 08:03:05 -0800
Message-ID: <016c01cbe005$cf8c0730$6ea41590$@sturek@att.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_016D_01CBDFC2.C168C730"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvgBXZ8O6PAm0AwTEW4KQOKhlAfYg==
Content-Language: en-us
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: d.sturek@att.net
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 16:01:59 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_016D_01CBDFC2.C168C730
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Can I ask about the current WG status of the following drafts:

http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-header/

http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-option/

 

Also, the following draft has not been adopted by WG (can it?):

http://datatracker.ietf.org/doc/draft-hui-6man-trickle-mcast/

 

Before the holidays, there was a thread around lack of responses on last
call for the first two drafts.  Did Last Call ever complete (does not appear
so from the WG page)

 

We would also like to see the trickle multicast draft adopted by the group.

 

I am affiliated with the ZigBee Alliance working on the Smart Energy 2
project.  We plan to deploy with these drafts next year with a very large
(many million devices) deployment.  We would like to see these drafts moved
along in the process.  We have been doing interoperability testing (with 10
vendors) for the past several months with these drafts so have data to share
on our experience.

 

Thanks,

 

Don Sturek

Chair, ZigBee Core Stack Working Group (responsible for "ZigBee IP"
application profile targeting Smart Energy 2)

 

 


------=_NextPart_000_016D_01CBDFC2.C168C730
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-microsoft-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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color: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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Can I ask =
about the current WG status of the following drafts:<o:p></o:p></p><p =
class=3DMsoNormal><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-heade=
r/">http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-header/</=
a><o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-option/">http=
://datatracker.ietf.org/doc/draft-ietf-6man-rpl-option/</a><o:p></o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Also, =
the following draft has not been adopted by WG (can =
it?):<o:p></o:p></p><p class=3DMsoNormal><a =
href=3D"http://datatracker.ietf.org/doc/draft-hui-6man-trickle-mcast/">ht=
tp://datatracker.ietf.org/doc/draft-hui-6man-trickle-mcast/</a><o:p></o:p=
></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Before the holidays, there was a thread around lack of =
responses on last call for the first two drafts.&nbsp; Did Last Call =
ever complete (does not appear so from the WG page)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We would =
also like to see the trickle multicast draft adopted by the =
group.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>I am affiliated with the ZigBee Alliance working on =
the Smart Energy 2 project.&nbsp; We plan to deploy with these drafts =
next year with a very large (many million devices) deployment.&nbsp; We =
would like to see these drafts moved along in the process.&nbsp; We have =
been doing interoperability testing (with 10 vendors) for the past =
several months with these drafts so have data to share on our =
experience.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Don =
Sturek<o:p></o:p></p><p class=3DMsoNormal>Chair, ZigBee Core Stack =
Working Group (responsible for &#8220;ZigBee IP&#8221; application =
profile targeting Smart Energy 2)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_016D_01CBDFC2.C168C730--


From brian@innovationslab.net  Fri Mar 11 08:16:42 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C7FD3A6AC7 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cf9BhVArqiKp for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:16:41 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 763863A6A98 for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:16:41 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 3055B88289 for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:17:59 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id B7306130002 for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:17:56 -0800 (PST)
Message-ID: <4D7A4B2E.3090206@innovationslab.net>
Date: Fri, 11 Mar 2011 11:17:50 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Status of ROLL RPL related drafts in 6man
References: <016c01cbe005$cf8c0730$6ea41590$@sturek@att.net>
In-Reply-To: <016c01cbe005$cf8c0730$6ea41590$@sturek@att.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 16:16:42 -0000

On 3/11/11 11:03 AM, Don Sturek wrote:
> Can I ask about the current WG status of the following drafts:
> 
> http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-routing-header/
> 
> http://datatracker.ietf.org/doc/draft-ietf-6man-rpl-option/
> 

The WG Last Call completed for these documents.  There were some
comments that, according to the authors, have been resolved but not
incorporated into the document(s).

>  
> 
> Also, the following draft has not been adopted by WG (can it?):
> 
> http://datatracker.ietf.org/doc/draft-hui-6man-trickle-mcast/
> 

No one has made a request for the WG to adopt it.

> 
> We would also like to see the trickle multicast draft adopted by the group.
> 

>From my brief read of the draft, I am not sure it belongs in 6MAN.  It
describes a multicast forwarding paradigm specific to low-power
networks. It would seem like ROLL is a better fit for this draft.

Regards,
Brian

From brian@innovationslab.net  Fri Mar 11 08:21:53 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 149383A6C20 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtgAqHsapra9 for <ipv6@core3.amsl.com>; Fri, 11 Mar 2011 08:21:52 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 4231A3A6C1D for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:21:52 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0CC258829E for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:23:09 -0800 (PST)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 6A2C3130002 for <ipv6@ietf.org>; Fri, 11 Mar 2011 08:23:05 -0800 (PST)
Message-ID: <4D7A4C5D.8030400@innovationslab.net>
Date: Fri, 11 Mar 2011 11:22:53 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Flow label drafts - updates, main open issue
References: <4D682228.7020304@gmail.com> <4D7453BE.1040606@gmail.com>	<20110309154837.GN89966@verdi> <4D77CDD1.3060005@gmail.com>
In-Reply-To: <4D77CDD1.3060005@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 11 Mar 2011 16:21:53 -0000

On 3/9/11 1:58 PM, Brian E Carpenter wrote:
> 
> Ditto. What the draft is talking about is default behaviour, absent
> anything requiring prior agreement or signalling.
> 
> I take your whole comment as a recommendation to remove section 4.

I would agree with removing section 4.  Without a defined stateful
mechanism anywhere on the horizon, it is reasonable to move forward
without that baggage.

Regards,
Brian

From fernando.gont.netbook.win@gmail.com  Sat Mar 12 02:55:25 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40F503A687D for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 02:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTf3G1fKN42p for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 02:55:24 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 170913A67E2 for <ipv6@ietf.org>; Sat, 12 Mar 2011 02:55:23 -0800 (PST)
Received: by bwz13 with SMTP id 13so3692159bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 02:56:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=AJugqv+X/O8UWvG+izdNznEwrDIMtGTrCIf3yRxV0Hs=; b=mNyvHZF76XAHSO/7UWS3V1BCmzji8pSd8L/1IoM0qxtQaZr+h0ukg0F2uRaerVh9Sx 2PQcUIM6uCjQKC6MNw3Y86TNzUmXYWfNSNSTwf4hflPHevupGBI9+CSC2sZaTh3gWnnG SiefKLddGPEDCnNz/3uYn0km/UOTp3aLIqbvo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=UGqvOvdPsLH97JO6rUbqk3/R1EGN8wENcEdodIbIXPNAe0a6+gZ+Q8/owmJO9KmC/S /VLb/7u4EXIA2UfLMDeZsACRzQa5CgfH/jto+7FilJoFeT7HCWcJm8b/+hiD/WUrqW34 c0KCyzvaix/8BrQFUdIiBcTB3tRhx9OmQNIeA=
Received: by 10.204.20.81 with SMTP id e17mr3036413bkb.151.1299927403684; Sat, 12 Mar 2011 02:56:43 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id u23sm3596915bkw.21.2011.03.12.02.56.38 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 02:56:41 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B5164.1030306@gont.com.ar>
Date: Sat, 12 Mar 2011 07:56:36 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 10:55:25 -0000

Hi, Mikael,

On 09/03/2011 08:17 a.m., Mikael Abrahamsson wrote:
>> I recommend that folks read the above draft.  I haven't seen the
>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>> the volume of recent I-D postings, and the topic seems relevant.
> 
> I don't think it solves what it thinks it solves, but if this REALLY
> should be implemented, it's my initial thinking that the H flag should
> be a MUST demand to only have ONE and only one MAC-based IPv6 address
> according to EUI64. 

Not sure what you mean... If H is set, why should we prevent generation
of MAC-based addresses of different scopes?


> I would appreciate some reasoning in the draft why
> this was chosen as a SHOULD option.

Because a "SHOULD" allows the host to override this policy if it has
good reasons to do so.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 02:59:46 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2B3F3A687D for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 02:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+Aw6QQElpFZ for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 02:59:45 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 86A2F3A67B0 for <ipv6@ietf.org>; Sat, 12 Mar 2011 02:59:45 -0800 (PST)
Received: by bwz13 with SMTP id 13so3693827bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:01:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:x-enigmail-version:openpgp:content-type :content-transfer-encoding; bh=iostW2gPqoIIrJs2n0Oy+X73RLfLSzebAeVLVpdWCUg=; b=PEvdwloPUyrfp1ViJcmPtfrtMTwDZzkdbNZlreJ9BJBk1DoIIlZbZVsIQblsHP/so0 mwTsSoNIIjBL8o5QpNcc59zMiiZ8NZPfnG00fxN9wq/6RGmSmnl6x+QXnzGyjkBDpA/w ZPzrnI508U5RtkoU4sDPCic2mimcOlzueE+RQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=RtK5GnLZIXmM+AxmOrREHNC+dvCI7OLk50qqbKBUttaQl5sTQrB/UIzyc3P5+QNV1W tbF9EXdfE4djmM+r9wYMyNaEBXA0x9KGx1fhXpG57S5cSYs1rEoIkaKlK06QZHq+obr6 I7xpVKhbkeeFzvLmsGbm3kXIrSyK28SRq0zuM=
Received: by 10.204.25.194 with SMTP id a2mr7506306bkc.197.1299927665347; Sat, 12 Mar 2011 03:01:05 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id z18sm1963893bkf.20.2011.03.12.03.01.02 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:01:05 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B5268.4040905@gont.com.ar>
Date: Sat, 12 Mar 2011 08:00:56 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Fwd: New Version Notification for draft-gont-6man-managing-privacy-extensions-01
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 10:59:46 -0000

Folks,

I've just realized that I had submitted an old version of the I-D. So
I've rev'ed the document and resubmitted it. -- The change log in the
appendix describes the changes since version -00.

Any comments will be more than welcome.

P.S.: There's still quite a bit of text that we need to include in the
I-D (e.g., regarding the motivation of this proposal, etc.) -- we simply
have not yet crafted the corresponding text (and wanted to meet the
deadline for version -00 documents), but plan to do it soon.

Thanks!
Fernando



-------- Original Message --------
Subject: New Version Notification for
draft-gont-6man-managing-privacy-extensions-01
Date: Sat, 12 Mar 2011 02:57:54 -0800 (PST)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: fernando@gont.com.ar
CC: ron@spawar.navy.mil


A new version of I-D, draft-gont-6man-managing-privacy-extensions-01.txt
has been successfully submitted by Fernando Gont and posted to the IETF
repository.

Filename:	 draft-gont-6man-managing-privacy-extensions
Revision:	 01
Title:		 Managing the Use of Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
Creation_date:	 2011-03-12
WG ID:		 Independent Submission
Number_of_pages: 15

Abstract:
This document describes an operational problem that arises due to the
impossibility of managing the use of "Privacy Extensions" for IPv6
Stateless Address Autoconfiguration (SLAAC) in network scenarios that
employ SLAAC.  Additionally, this document specifies new flag in the
Prefix Information option of Router Advertisement messages, such that
routers can advertise, for each network prefix to be used for SLAAC,
whether the aforementioned "Privacy Extensions" should be used.




The IETF Secretariat.


Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fernando.gont.netbook.win@gmail.com  Sat Mar 12 03:03:27 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 639553A687D for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BcOHc0KvfwCC for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:03:26 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 2DF2D3A686A for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:03:26 -0800 (PST)
Received: by bwz13 with SMTP id 13so3695362bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:04:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=5IMH99Gs4so3brOgm8+2JkniiBn3xtDf+Fr6bQTOTr4=; b=Dh7Mz+34p/rbDwE0znCfYrup2INqJ3q1vrWjrY34T+hNY4j/1KhTiZrbkRvtcBoTww X9DiChTR3W9UA6MMDva3Sd8Wa/a3bf1dWeUQjuVCuCOc5xmkTh/RyU5PS4s0ogS/Knoy w5P1ky5B9j0TbqGgTtvNRUawNzv+cJrLjn0PA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=lbS13XMZb2yEDGHcyna0ArZD/5P9XyMNJbHi/7xIx21k+EQmO5dDRx/ZIUSfv2Cox5 izxom1TnuaAYhgFR6eM5GTyKur5BG0IgB+ttGOsoHGMOZvUDkNcd2kFeY1c+exuC0r8c XkBXpgSrV+YLqoR+sT1SPnSx304z0y44n5M/4=
Received: by 10.204.127.88 with SMTP id f24mr4455383bks.54.1299927886069; Sat, 12 Mar 2011 03:04:46 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id c11sm2101646bkc.14.2011.03.12.03.04.42 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:04:45 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B5347.7070900@gont.com.ar>
Date: Sat, 12 Mar 2011 08:04:39 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: huabing yu <yhb810501@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>
In-Reply-To: <AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 11:03:27 -0000

On 09/03/2011 09:19 a.m., huabing yu wrote:

> (1)If "H" ("Hardware-derived addresses") flag is 1, it indicates that
> the host SHOULD generate hardware-derived addresses, and doesn't 
> generate privacy addresses.
> (2)If "H" ("Hardware-derived addresses") flag is 0, the author say that 
> this bit indicates that Privacy Extensions SHOULD be enabled 
> when configuring IPv6 addresses as a result of Stateless Address
> Autoconfiguration,
> *but many people will think that it indicates that the host doesn't
> generate *
> *hardware-derived addresses, and SHOULD generate privacy addresses. It may *
> *result in a misunderstanding.*

I don't really follow the potential misunderstanding. Anyway see version
-01 of the document (that I've just posted).

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 03:05:26 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFF9A3A6B1D for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R2bbJ7486c0R for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:05:25 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id D7E043A67B0 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:05:24 -0800 (PST)
Received: by bwz13 with SMTP id 13so3696166bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:06:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=1KZB+w+O77XOIjY5bup9BU4zYEuXB7ecuVb8DrHi9SI=; b=dR4juXFfAfC27NGA221B9t2vVb729DrurcIGva/ZNWZexEv0ysBv5czBD7aFsnveSU Akl1iTUBoaR6QXJeL2JB9WKSi8Bprp7QzPXG2MMd/8UwjXufKO5VXGqlJB+MUDGs0Lfg Gv34sCuy6vDZOg+oHsNIgJa74iA3c/SYbY73c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=YGzFVqjslJs9I3yQQWyCOt0zK56atYSBKqjfdXCy8Hx0m34Leu+sxyWzkaZkNDpWoD sHSbdqPjjRXDJCKgfU+7Mmg1BC2rt5cxAs0eweyWivLiwc10BchIMs1l31HaemQjVXkS np9wFyBKvlbdw6ZdIBHLVAEE0FQCCQlvaUXvU=
Received: by 10.204.81.27 with SMTP id v27mr5031049bkk.115.1299928004759; Sat, 12 Mar 2011 03:06:44 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id b7sm3606564bkb.6.2011.03.12.03.06.41 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:06:44 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B53BF.5070104@gont.com.ar>
Date: Sat, 12 Mar 2011 08:06:39 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com> <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 11:05:26 -0000

On 09/03/2011 11:57 a.m., Mikael Abrahamsson wrote:

> If you want to know the mac address of the computer who used an IP
> address at a certain time, then you need to tell the host to only use
> EUI64 based address and nothing else, you don't tell it to disable
> privacy extensions. 

This was exactly the rationale for the "H" bit in version -00 of the
document. And the current version (-01) follows the same principle.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 03:07:46 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC04C3A68B7 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJPhRhw72tFG for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:07:46 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id AE1913A686A for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:07:45 -0800 (PST)
Received: by bwz13 with SMTP id 13so3697150bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:09:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=Es5wrsVuuGigP00YujZ9E5XoecnU+H1P46Oam2eb6sU=; b=YcXba9IYEYkbiOQR6Jqa+WvnBzTxhO1v7/V1vS22sdUdVnBon8RiTJxibAsrvqNBPj LrjMIt7e0uzyAEXTG8xRPK8BMjHTCnRxIPhquf2SyHIjnYIgxrRvF1cvVVyYazHrU/dz p7+Od0/VtdFfZe6TVzMy92haEd9PKln+CAGBM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=EQrZKjLVTSQOslTVJpB/giGLrnX3kIj0qzCltwVJSVHGBkCq3QWFmoM3A/9g79cQQL MaZhIfPYewG/FEtlJ1jEgJb0TkK+5nU8/44yiP22PNtLunqhAaG+nEIvzRt/P9pgNQ3e O6/n197JzpAmIZliTHPgfB7dxlqLyU9c5cySQ=
Received: by 10.204.233.11 with SMTP id jw11mr1967084bkb.32.1299928145704; Sat, 12 Mar 2011 03:09:05 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id b7sm3608056bkb.6.2011.03.12.03.09.02 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:09:05 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B544C.3070607@gont.com.ar>
Date: Sat, 12 Mar 2011 08:09:00 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<AANLkTim7W3BCCgW_Hpvr3p+SdYobpk-yoZYTtbWxL14r@mail.gmail.com>	<alpine.DEB.1.10.1103091552560.7942@uplift.swm.pp.se> <BD1A42A7-CCD4-4625-94C6-037FD8C3CF2C@gmail.com>
In-Reply-To: <BD1A42A7-CCD4-4625-94C6-037FD8C3CF2C@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 11:07:46 -0000

Hi, Ran,

On 09/03/2011 12:51 p.m., RJ Atkinson wrote:
>> Just because privacy extensions is the only address widely seen
>> today as being non-EUI64, doesn't mean that if you disable privacy,
>> you get only single EUI64.
> 
> The above is a very helpful clarification.  
> 
> Based on that, I agree with Mikael that the correct semantic 
> to the flag should be to require direct/embedded use of a 
> hardware MAC value for the IPv6 IID.  That would disallow 
> not only the (pseudo-)Privacy addresses, but any other kind 
> of addressing that would not embed a hardware address in the IID.

Will clarify this in the next rev of the document.



> REQUEST for Fernando G/Ron B:
> 	Separately, keeping the quoted comments above in mind, the I-D
> 	draft-gont-6man-managing-privacy-extensions needs clarification 
> 	edits to avoid using the phrase "hardware-derived" anywhere.

Will do.



> REASON:
> 	Any (pseudo-) Privacy address is derived ("computed") using the 
> 	MAC address as a seed (at least originally). [RFC-3041, Seection 3.2]
> 
> 	So it is confusing and not clear to say "hardware-derived",
> 	when one means that the system ought to only use IIDs that
> 	are embedded IEEE MAC addresses (whether 802, Firewire, or BlueTooth)
> 	or some other embedded hardware address type.

Will do. And will reference the corresponding RFCs (EUI-64 stuff).

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 03:10:48 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7865A3A6B15 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XalIJWyMFZYr for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:10:47 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 63BE63A6AE4 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:10:47 -0800 (PST)
Received: by bwz13 with SMTP id 13so3698395bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:12:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=De5MdgR37tz9xnkJrcFU8KRgKKdm2eu9MxycbNjK6gc=; b=EBqwecTVioMNrN6Ex+y6TSph3k3hpfrjyuE7FY9p1rU/YCZkNZ8ZtRJ4nPrTtwbPkZ CxRzsf2SY1CgtPgDW1sFtAfnSf0ZVdnZA0r46k669Hw93VF94Iz8hReS9jY0N+e9/myp fpefvfWFPsQ6zSO8ndfMZQFXrcImSIs/LjY/8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=vjQJyOdDFY1Od9GMuUr7y9wgZqRc+pTssr2Snl1902Q0WkvsSauWY7Bk4IzmXmg4d9 sDrfLCRiXy54R20RH5mzL4NXzwpZ83GIfdOJeRrOPuro7KJYHXR9cD/O6dDy6tE9QIK6 Gg+Kl4tF3SMSTLxgcvrM+zT1uRi0J6MawxVrs=
Received: by 10.204.151.205 with SMTP id d13mr3822847bkw.117.1299928322967; Sat, 12 Mar 2011 03:12:02 -0800 (PST)
Received: from [192.168.200.28] ([194.2.150.133]) by mx.google.com with ESMTPS id q18sm3606922bka.15.2011.03.12.03.11.59 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:12:02 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B54FC.8090800@gont.com.ar>
Date: Sat, 12 Mar 2011 08:11:56 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>
In-Reply-To: <4D77CBB9.1080702@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 11:10:48 -0000

On 09/03/2011 03:49 p.m., Brian E Carpenter wrote:
>> I don't think it solves what it thinks it solves, but if this REALLY
>> should be implemented, it's my initial thinking that the H flag should
>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>> according to EUI64. I would appreciate some reasoning in the draft why
>> this was chosen as a SHOULD option.
> 
> For the reason I just gave against the disable-private flag: this
> violates the host's right to use an untraceable address.
> 
> It may be that in corporate deployments, that right can be removed.
> But removing it for public subscribers would be a political blunder.

The requirements in draft-gont-6man-managing-privacy-extensions are
SHOULDs, for this very reason.

How about including some text that explicitly states that a host can
always override the desired policy (with a system toggle) if it desires
to do so?

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 03:38:04 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF5093A69AA for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:38:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q6NlH6amhIoX for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 03:38:04 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 997D73A686A for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:38:03 -0800 (PST)
Received: by bwz13 with SMTP id 13so3709111bwz.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 03:39:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=KOnVn5wIDZO4e89q3zgzoeyT5AZsrPMO86TWDcQ2oW0=; b=QL2qH85kqK5f2WhI3v+ExMxkb5aT9UnIiRHBsHYoryYTsVVZq+enAwa+xISTbJAK/Q zDoisln8BV6UNGOi7E9S1eoT+04gfJPERjTVeF1HaqTTz5lDfik6S9+QSyACnGzx1oVb 8ywHyuoFaHeYJb5hIRLjf+guQT2N6CEaNofD8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=eIFGnfSmnqjFrD75b1P2oGp0lYWYzsesUA4fSsOVMFW0UOfVdixg64rye3YroM33HQ 5cjHXLoCrrSHqX/Wym92CtS1cCqGHU3V32PIFQiwmEd3Ih3AfhT1JRBvshdRpsIZlvhv orxPrDTZLs8k35KkT7fAfeJFoLPiT4z3F68Xw=
Received: by 10.204.164.2 with SMTP id c2mr1027059bky.85.1299929963518; Sat, 12 Mar 2011 03:39:23 -0800 (PST)
Received: from [192.168.200.22] ([194.2.150.133]) by mx.google.com with ESMTPS id q18sm3627718bka.3.2011.03.12.03.39.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 03:39:22 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7B5914.6090000@gont.com.ar>
Date: Sat, 12 Mar 2011 08:29:24 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 11:38:04 -0000

On 09/03/2011 08:17 a.m., Mikael Abrahamsson wrote:

>> I recommend that folks read the above draft.  I haven't seen the
>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>> the volume of recent I-D postings, and the topic seems relevant.
> 
> I don't think it solves what it thinks it solves, but if this REALLY
> should be implemented, it's my initial thinking that the H flag should
> be a MUST demand to only have ONE and only one MAC-based IPv6 address
> according to EUI64. I would appreciate some reasoning in the draft why
> this was chosen as a SHOULD option.

I realize I misunderstood your comment.

The intention of the I-D is/was that if the "H" bit is set, you SHOULD
generate your addresses corresponding to this prefix ONLY with according
to EUI64.

The above requirement is a "SHOULD" (rather than a MUST), since a hosts
that has good reasons to do so (e.g., privacy concerns) is allowed to
override the policy specified by the router.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From scott.brim@gmail.com  Sat Mar 12 07:13:26 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B74F3A69DB for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 07:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.574
X-Spam-Level: 
X-Spam-Status: No, score=-103.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8D7-Vf3R0AS for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 07:13:25 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 291A73A69BA for <ipv6@ietf.org>; Sat, 12 Mar 2011 07:13:25 -0800 (PST)
Received: by iyi12 with SMTP id 12so490615iyi.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 07:14:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9jwHQoLg/evtXTrUZD5ySTFjFO6kjyiJEVu1bByPQjQ=; b=nZ9v2MrxGUNLiqABxcEAsNA2su2rVcZ62APX1RxMg7EJM02pBgDrOZ8/v/ymLvkaYZ 1S6ixK5k/oeyIoX4mj/stjxQr0icJQ+GmiHd49euj4Igb7MuVtYnIIOJteD66Nb+C/xZ 5tukzb7o/dO+iI2+A3n5gtWwZKwrxOfr0nGzA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=qe/M87//dlCFmTYYHcVO4zQHoJO+QApfi+PauWKNFoHHrFzaahpVfmhtshjWcLt+HA bc0nUmD4bMdPXmna6hh3dODcJEno7IoyR7h44YjHYzk9btmFhvBrAKlu28MHNezhEnKk nADP7RMa1i92aiqvkjq+vdGdpisWQQkyk1QdI=
Received: by 10.43.51.65 with SMTP id vh1mr3115668icb.435.1299942885530; Sat, 12 Mar 2011 07:14:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.42.114.81 with HTTP; Sat, 12 Mar 2011 07:14:25 -0800 (PST)
In-Reply-To: <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com> <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net>
From: Scott W Brim <scott.brim@gmail.com>
Date: Sat, 12 Mar 2011 10:14:25 -0500
Message-ID: <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
To: Mark Townsley <mark@townsley.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ipv6@ietf.org, draft-brim-mobility-and-privacy@tools.ietf.org, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 15:13:26 -0000

On Fri, Mar 11, 2011 at 08:01, Mark Townsley <mark@townsley.net>
wrote:
>> On Mar 11, 2011, at 3:32 AM, Christian Huitema wrote:
>>
>> I'm saying the reasons people are tempted to disable RFC4941 are
>> misplaced.
>>
>> +1
>>
>> Consider that if I want privacy and you won't let me use RFC4941, I
>> might just make up a new MAC address each time I connect.
>>
>> Consider also the effect of unique identifiers on tracking. The MAC
>> address follows you when you roam. By embedding it in the IPv6
>> address, we are effectively offering a "super cookie" to all web
>> services. Is it really what we want? In addition to privacy issues,
>> displaying the MAC address allows third parties to track hardware
>> purchase, and enables other attacks by providing the data necessary
>> for MAC spoofing. In short, it looked like a great idea at the
>> time... but wasn't.
>
> One person's attack is another's targeted ad business case ;-)
>
> That aside, the considerations proposed in this document may be
> relevant to this discussion:
>
> http://tools.ietf.org/html/draft-brim-mobility-and-privacy-00 - Mark

Since you called it out :-) ... I think less in terms of privacy than
confidentiality scopes.  Privacy is the right to withhold information.
Confidentiality is an agreement that a second party will honor your
wish for privacy from others, i.e. that information you give them will
not be given to others.  We give others information all the time,
including hardware addresses.  Confidentiality issues are at least as
important as privacy.

Forcing people to reveal information to a larger scope than they wish,
i.e. forcing loss of privacy, is a significant issue that must be
taken into account by everyone doing protocol work.  If we design our
systems so that non-privacy addresses used locally must be also be
used globally, we are designing away the possibility of both privacy
and confidentiality.  Requiring an end user to use a MAC or any
persistent identifier for all communications with everything else on
the Internet is probably illegal in an increasing number of countries
around the world.  (On the other hand, in some countries it is
probably illegal to NOT require it.)
However, it's perfectly legitimate to require an identifier within an
enterprise -- there is a confidentiality agreement.

How can the enterprise get the information it needs without requiring
users to give away privacy for other communications?  An algorithmic
mapping from a hardware identifier to a different one at the
enterprise boundary does not solve the problem, because (1) all those
problems around non-globalness of addresses/locators/identifiers, and
(2) that mapped identifier is also persistent, and usage can be
tracked.

Blue sky: Could the SP allow privacy addresses, at least for global
use, and log its own mappings between privacy addressses and MACs or
other persistent identifiers?  Then it can always trace back to
determine who did what if necessary.

Scott

From sthaug@nethelp.no  Sat Mar 12 08:07:14 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DC2C3A6A8B for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:07:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.216
X-Spam-Level: 
X-Spam-Status: No, score=-6.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qf1BiYukrKaP for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:07:13 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 4473A3A69F6 for <ipv6@ietf.org>; Sat, 12 Mar 2011 08:07:12 -0800 (PST)
Received: (qmail 29152 invoked from network); 12 Mar 2011 16:08:31 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 12 Mar 2011 16:08:31 -0000
Date: Sat, 12 Mar 2011 17:08:31 +0100 (CET)
Message-Id: <20110312.170831.74726157.sthaug@nethelp.no>
To: scott.brim@gmail.com
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: sthaug@nethelp.no
In-Reply-To: <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
References: <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net> <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
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
Cc: draft-brim-mobility-and-privacy@tools.ietf.org, ipv6@ietf.org, huitema@microsoft.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 16:07:14 -0000

> Blue sky: Could the SP allow privacy addresses, at least for global
> use, and log its own mappings between privacy addressses and MACs or
> other persistent identifiers?  Then it can always trace back to
> determine who did what if necessary.

I'm sure service providers *could* do this. But it's probably not
significantly simpler than just assigning an address using DHCPv6
or Radius - so where's the incentive for the service provider to do
such logging?

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From huitema@microsoft.com  Sat Mar 12 08:39:40 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 58D143A6945 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.569
X-Spam-Level: 
X-Spam-Status: No, score=-10.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cXY0miLBiuyo for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 08:39:38 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id B4BAB3A68F1 for <ipv6@ietf.org>; Sat, 12 Mar 2011 08:39:38 -0800 (PST)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 12 Mar 2011 08:40:59 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.1.270.2; Sat, 12 Mar 2011 08:40:59 -0800
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.56]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0270.002; Sat, 12 Mar 2011 08:40:58 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Scott W Brim <scott.brim@gmail.com>, Mark Townsley <mark@townsley.net>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AQHL3kEKAbTYw5EzSU+RGMZ29OXheJQlYKSAgAB+ZoCAANWqgIAATRSAgABA0wCAACYHAIAAG7iA///mPyCAATgCgIABt1eA//+QKvA=
Date: Sat, 12 Mar 2011 16:40:58 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C22F4@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com> <22F6318E46E26B498ABC828879B08D4F0C15B1@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <EF3F736B-777F-4F03-8AB5-62D46452B942@townsley.net> <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
In-Reply-To: <AANLkTik4FEfjUjwH4EsVHA6kQRQ+6PcMNEX6=4e6FqM_@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "draft-brim-mobility-and-privacy@tools.ietf.org" <draft-brim-mobility-and-privacy@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 16:39:40 -0000

> Blue sky: Could the SP allow privacy addresses, at least for global use, =
and log its own mappings between privacy=20
> addressses and MACs or other persistent identifiers?  Then it can always =
trace back to determine who did what if necessary.

That's more or less what Windows does by default. The persistent address is=
 not derived from the MAC, but from a hash of the prefix and the MAC id. Li=
ke a privacy address, it does not expose the MAC. Unlike a privacy address,=
 its lifetime is as long as the routers will allow. This means nodes have a=
 stable address in the corporate network, and can be easily traced within t=
hat network. But they get different addresses when they move around, and ca=
nnot be easily traced by third parties.

-- Christian Huitema




From brian.e.carpenter@gmail.com  Sat Mar 12 11:01:11 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 010743A6946 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 11:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhEiriyrs6Cg for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 11:01:09 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id B91093A6930 for <ipv6@ietf.org>; Sat, 12 Mar 2011 11:01:09 -0800 (PST)
Received: by ywi6 with SMTP id 6so2059476ywi.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 11:02:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WWgr2AbYw9DZBrtCNLpO9NepM9gV/M21pfEc5s0duVM=; b=Ph3BNX1sykL9L3Ne0iFxEtERQqSAw7A+Nqyr4bT4APnrGABvriXoEvdSaZD0H19Sa1 4awWcBrmuzWhdFn9b4QElLrUMkcx6rHNaqooiI3XnwnAyiBdqN4LXsjOVH/hR40+052V EuISNK1oyypXbCP7lVy3i9QPRabJmbOwwD64c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=lcYKYVArffIpS1cfwbDEgf/xnId6s7JY85yNygEpQXMzwKLdNfetmKE6QnKHb5rWHR RyuXUsMatFe4Yiu0N+qWCCdCY9HB8wAfYqbdLN2l+92CqG+cG0FmPRQdKTf2Y8fv02MN aFPkoGRiqOSIsHcnDNkoSEAVnsFSPUsAqdIk8=
Received: by 10.151.78.4 with SMTP id f4mr4121688ybl.240.1299956550597; Sat, 12 Mar 2011 11:02:30 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id q29sm4031974ybk.22.2011.03.12.11.02.26 (version=SSLv3 cipher=OTHER); Sat, 12 Mar 2011 11:02:29 -0800 (PST)
Message-ID: <4D7BC339.3000001@gmail.com>
Date: Sun, 13 Mar 2011 08:02:17 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <4D7B54FC.8090800@gont.com.ar>
In-Reply-To: <4D7B54FC.8090800@gont.com.ar>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 12 Mar 2011 19:01:11 -0000

On 2011-03-13 00:11, Fernando Gont wrote:
> On 09/03/2011 03:49 p.m., Brian E Carpenter wrote:
>>> I don't think it solves what it thinks it solves, but if this REALLY
>>> should be implemented, it's my initial thinking that the H flag should
>>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>>> according to EUI64. I would appreciate some reasoning in the draft why
>>> this was chosen as a SHOULD option.
>> For the reason I just gave against the disable-private flag: this
>> violates the host's right to use an untraceable address.
>>
>> It may be that in corporate deployments, that right can be removed.
>> But removing it for public subscribers would be a political blunder.
> 
> The requirements in draft-gont-6man-managing-privacy-extensions are
> SHOULDs, for this very reason.
> 
> How about including some text that explicitly states that a host can
> always override the desired policy (with a system toggle) if it desires
> to do so?

Yes, I think so, clearly labelled as "Privacy Considerations".

Otherwise we'll just have a re-run of the Jasmine thread right here.

   Brian

From fernando.gont.netbook.win@gmail.com  Sat Mar 12 16:23:51 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7B2D3A6A82 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qlMo-6noPJnc for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:23:51 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id C16923A6A75 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:23:50 -0800 (PST)
Received: by wyb42 with SMTP id 42so3848622wyb.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:25:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=HmfClRCO5GE42U6LQQWMaIVifRVCgmE+fWWEK6ty/wA=; b=eie0OHa5NY0Et4oJvtpk0jewVnik5Cmzh3SmIB+OHpfDfERKNZbLJI8PxxYUjBlT1i 2+q2AvQIAnG2C/j6boxcv1ASlzOABE6jv5jYxlaCyfKM7VLCR3H4Y9wL7O70uTSDxBKD HHNoetBvtHxa2UezfPJbCS7DY0rBspbVJOQSc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=ciYYa8521hsHdlDReDWHLCzTcAZtHe3kNzZQ7xbu1zNNXepb7fTkRzT9Qsp3Jtltpu ktDyhzCXDP4BewZz67B5m7z0XLbfLppMbwPYBd1ZwWFP2Lwh0a57HdEOHUW3zFKj0RwP LlU7ZkW0dFZOlofsxb0TfBmqtn4uLv6e1YNKc=
Received: by 10.216.9.141 with SMTP id 13mr899549wet.73.1299975911404; Sat, 12 Mar 2011 16:25:11 -0800 (PST)
Received: from [192.168.200.18] ([194.2.150.133]) by mx.google.com with ESMTPS id m2sm3007833wer.13.2011.03.12.16.25.08 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 16:25:10 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7C0EE5.2080405@gont.com.ar>
Date: Sat, 12 Mar 2011 21:25:09 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>	<78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com>
In-Reply-To: <262f01cbdf5d$607c69f0$21753dd0$@com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 00:23:51 -0000

Hi, Dan,

On 10/03/2011 04:57 p.m., Dan Wing wrote:
>> Doesn't a combination of RFC4941 and NPTv6 produce the necessary
>> privacy over both parts of the IPv6 address?
>> (BTW thats a question from an interested observer new to this topic,
>> not a statement - I started following this thread and ended up digging
>> around in the RFCs and drafts the thread uncovered)
> 
> RFC4941 by itself does the trick.
> 
> But draft-gont-6man-managing-privacy-extensions (the subject of
> this thread) says "you can't use RFC4941".

It doesn't. The I-D aims at allowing routers specify which policy they
want hosts to employ when generating their IPv6 addresses.

Version -01 of the document probably makes this even more clear: the
router can actually advice nodes to use privacy addresses. -- As an
example, please note that while some stacks implement "privacy
extensions", they do not enable them by default. Thus, use of the
mechanism specified in this document could result in those boxes
*enabling*╬rivacy addresses (if desired).

This document aims to improve the ability of the network administrator
of managing the generation of IPv6 addresses. It is not mean, per se, to
disable privacy addresses.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From huitema@microsoft.com  Sat Mar 12 16:43:15 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50F123A6A75 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L00PnvYdbqtT for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:43:14 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 8FAB33A6A4D for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:43:14 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sat, 12 Mar 2011 16:44:35 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.270.2; Sat, 12 Mar 2011 16:44:35 -0800
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.56]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi id 14.01.0270.002; Sat, 12 Mar 2011 16:44:35 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fernando@gont.com.ar>, Dan Wing <dwing@cisco.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AQHL3kEKAbTYw5EzSU+RGMZ29OXheJQlYKSAgAB+ZoCAANWqgIAATRSAgABA0wCAACYHAIAAG7iAgANveID//32XAA==
Date: Sun, 13 Mar 2011 00:44:34 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com> <4D7C0EE5.2080405@gont.com.ar>
In-Reply-To: <4D7C0EE5.2080405@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 00:43:15 -0000

> It doesn't. The I-D aims at allowing routers specify which policy they wa=
nt hosts to employ when generating their IPv6 addresses.

Uh? I definitely don't want to give the router at Starbucks the means to sp=
ecify the privacy configuration of my laptop.

I understand that corporation want to enforce policies so PC and routers ar=
e easier to manage, but we have to be careful. If we define that policy as =
part of the address configuration standard, then it will apply everywhere, =
not just in the corporate network where the laptop is managed. That seems a=
 terrible idea.=20

If we want policy options to be applied safely, they have to be propagated =
by trusted mechanism, where the host can verify the authority of the policy=
 source. Anything else is abuse waiting to happen.

-- Christian Huitema


=20

From dougb@dougbarton.us  Sat Mar 12 16:49:03 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 938183A6A9D for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:49:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbMQO2U2bmv1 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:49:02 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id B3B8C3A6A84 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:49:01 -0800 (PST)
Received: (qmail 24320 invoked by uid 399); 13 Mar 2011 00:50:17 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 13 Mar 2011 00:50:17 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D7C14C7.4020508@dougbarton.us>
Date: Sat, 12 Mar 2011 16:50:15 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110304 Thunderbird/3.1.9
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>	<78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>	<262f01cbdf5d$607c69f0$21753dd0$@com> <4D7C0EE5.2080405@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 00:49:03 -0000

On 03/12/2011 16:44, Christian Huitema wrote:
>> It doesn't. The I-D aims at allowing routers specify which policy they want hosts to employ when generating their IPv6 addresses.
>
> Uh? I definitely don't want to give the router at Starbucks the means to specify the privacy configuration of my laptop.
>
> I understand that corporation want to enforce policies so PC and routers are easier to manage, but we have to be careful. If we define that policy as part of the address configuration standard, then it will apply everywhere, not just in the corporate network where the laptop is managed. That seems a terrible idea.
>
> If we want policy options to be applied safely, they have to be propagated by trusted mechanism, where the host can verify the authority of the policy source. Anything else is abuse waiting to happen.

Please consider this my periodic repetition of support for what 
Christian is saying here, along with my periodic repetition of 
opposition to (further) modifying RA/SLAAC to do things that DHCP 
can/does do, or should be doing.

And to state publicly something that I discussed in private, I'm 
completely unsympathetic to the viewpoint that "we need to show to the 
auditors that we tried to prevent hosts from doing bad things" in the 
absence of rigorous security steps to _actually_ prevent them.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From fernando.gont.netbook.win@gmail.com  Sat Mar 12 16:55:58 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4DA113A6AAA for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exM5loB0UgkV for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 16:55:55 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 610BB3A6A84 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:55:55 -0800 (PST)
Received: by wyb42 with SMTP id 42so3858660wyb.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 16:57:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=E4gqvfl7ewZoumS5EuXq1TjV56jDgqgTj9lLXG2aln4=; b=o4WNG0L5XhhjLXIPARYVS1CtPPSVRDbaC7jqGsZVFaL1QbBvTzyVqnfyV2pFPoTyPm edGg099eewtGj3/RNwOuc//5Q1v5uV7rUlr63s2iC95VbmZ+2gmO0eaB3YqjjD64HnX7 09+Gd8uwGV6oTv0Lxxcx0LTM/CeU2t+wZ35mo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=VRJWTAWg6D7Jb2jJ8KVP7QCqNOUkPC4Lsrw14RnARuzZOgNP3llHWwjuHWnQt6WFgf tvWyrht0CD+MGQ1nse5ulxjcznRIDAqJLvMDEP6Vu1OtHYJmg2IhnP2+T+v328PM88Ut NbGWwdICP/gyEfwk1CFrCwy5TWnUSiu3ln2Ag=
Received: by 10.216.87.8 with SMTP id x8mr9706724wee.46.1299977835923; Sat, 12 Mar 2011 16:57:15 -0800 (PST)
Received: from [192.168.200.18] ([194.2.150.133]) by mx.google.com with ESMTPS id l5sm3018247wej.32.2011.03.12.16.57.14 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 16:57:15 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7C166A.9060608@gont.com.ar>
Date: Sat, 12 Mar 2011 21:57:14 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>	<78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>	<262f01cbdf5d$607c69f0$21753dd0$@com> <4D7C0EE5.2080405@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 00:55:58 -0000

On 12/03/2011 09:44 p.m., Christian Huitema wrote:

>> It doesn't. The I-D aims at allowing routers specify which policy
>> they want hosts to employ when generating their IPv6 addresses.
> 
> Uh? I definitely don't want to give the router at Starbucks the means
> to specify the privacy configuration of my laptop.

Override the advice provided by the router at Starbucks, and you're done
(e.g., I guess this could even be automatically done by the OS depending
on how you tag the network you're connecting to (e.g., Public, Home,
whatever)).



> If we want policy options to be applied safely, they have to be
> propagated by trusted mechanism, where the host can verify the
> authority of the policy source. Anything else is abuse waiting to
> happen.

The threat model for this case is no different to that for ND in general...

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Sat Mar 12 17:22:04 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C77283A6AA2 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 17:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1czbGr51vMer for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 17:22:03 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 8522C3A67B6 for <ipv6@ietf.org>; Sat, 12 Mar 2011 17:22:03 -0800 (PST)
Received: by wwa36 with SMTP id 36so3129724wwa.13 for <ipv6@ietf.org>; Sat, 12 Mar 2011 17:23:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=CDIZoHSsh6AcmyJalKmx5GlSA6XUnOytaHKQ9ITlvNQ=; b=UohRn7lLWJXHg0sYzacIcJI+1AzcdwS7XEUdSyWubIoHlHZ8pv1kmce7WdwsGmCDsK DVSr8FzS5rnkgBkmV7BI4I1xI1HFx0rRx7h8MQJJfO3yrbcYccFXNtySejj6eCSqNfFV BfA4ejWP0w/RPN7tCWGC5p8wDJ1VqiIGLR+QY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=Bl+X/OXagZ2b4kEl9fN+29e4NREBB3gvoFwjFZWzn0xqCqekQ5CULloNLuXBZMFsRu yy1GgFD4drent+F+7Oa5vASCqu00l8I2O1go3fRAB7XG6YPIN1vn6Ei7XKYLquJPQq02 yMMbwd615QLCMhpJmWQVildmmRljNjaKjlA+E=
Received: by 10.216.192.82 with SMTP id h60mr401841wen.54.1299979404290; Sat, 12 Mar 2011 17:23:24 -0800 (PST)
Received: from [192.168.200.18] ([194.2.150.133]) by mx.google.com with ESMTPS id l5sm3025798wej.32.2011.03.12.17.23.22 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 17:23:23 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7C1C8A.9070509@gont.com.ar>
Date: Sat, 12 Mar 2011 22:23:22 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <26FA7472-2BD6-4D68-B3EC-F465B92EAC9E@apple.com>
In-Reply-To: <26FA7472-2BD6-4D68-B3EC-F465B92EAC9E@apple.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6 <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 01:22:04 -0000

Hi, James,

On 09/03/2011 04:08 p.m., james woodyatt wrote:
> About the H-bit in the PIO it proposes, the draft says this:
> 
> When set, this bit indicates that hardware-derived addresses SHOULD
> be used when configuring IPv6 addresses as a result of Stateless
> Address Autoconfiguration.  When not set, this bit indicates that
> Privacy Extensions SHOULD be enabled when configuring IPv6 addresses
> as a result of Stateless Address Autoconfiguration
> 
> Which makes the bit worse than useless.  If the PIO contains A=1,
> then both EUI-64 and privacy IID are eligible under the current
> regime, but this draft says only that one or the other SLAAC
> alternative SHOULD be used depending on the state of the bit, without
> explicitly saying whether the complementary alternative SHOULD NOT be
> used.
> 
> I'm not sure if the intent is to make a signal for hosts that network
> administration regards any particular SLAAC alternative as NOT
> RECOMMENDED, but if it is, then the draft should explicitly say so.

Will do. The idea is that there's a policy that SHOULD be used, with the
others being "NOT RECOMMENDED".


> Of course, if the draft were to changed to do that, then I would
> lodge the same complaints that I lodged previously against
> I-D.yhb-6man-ra-privacy-flag... for the same reasons.

I will dig the archives. :-)  However, as noted in other posts, this is
not about "disabling privacy addresses", but about allowing admins to
communicate policies to hosts. i.e., this mechanism might be used for
*enabling* privacy addresses (rather than disabling them), too.



> This draft has a long struggle ahead of it, if you ask me.

Comments on specific issues would be very welcome, such that we can work
on fixing/improving them. ;-)

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Mar 12 17:29:43 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8914C3A6AB3 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 17:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.542
X-Spam-Level: 
X-Spam-Status: No, score=-1.542 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3hFALeqG3bC for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 17:29:42 -0800 (PST)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by core3.amsl.com (Postfix) with ESMTP id 654FF3A6A7A for <ipv6@ietf.org>; Sat, 12 Mar 2011 17:29:41 -0800 (PST)
Received: from 114-30-119-224.ip.adam.com.au ([114.30.119.224] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Pya96-00082z-5o; Sun, 13 Mar 2011 12:01:00 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id A83075355B; Sun, 13 Mar 2011 12:00:59 +1030 (CST)
Date: Sun, 13 Mar 2011 12:00:59 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: sthaug@nethelp.no
Subject: Re: draft-yhb-6man-ra-privacy-flag-02
Message-ID: <20110313120059.647854b4@opy.nosense.org>
In-Reply-To: <20110310.133158.74670479.sthaug@nethelp.no>
References: <20110310074132.463bf972@opy.nosense.org> <20110310.084554.41634571.sthaug@nethelp.no> <20110310223623.5221b994@opy.nosense.org> <20110310.133158.74670479.sthaug@nethelp.no>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, brian.e.carpenter@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 01:29:43 -0000

On Thu, 10 Mar 2011 13:31:58 +0100 (CET)
sthaug@nethelp.no wrote:

> > > > The common argument from the "stateful-only crowd" seems to be that
> > > > they need to have a log of IPv6 address/MAC addresses for audit
> > > > purposes, and therefore think they need to have stateful, database
> > > > driven addressing to do that, probably because that is how it has
> > > > been done in IPv4.
> > > 
> > > In our (service provider) case the basic requirement is to be able to
> > > associate a dynamic IPv6 address with a specific *customer*.
> > 
> > Can't you use RADIUS for that? I'm working in a SLAAC
> > environment for SP customers over PPP/PPPoE or L2TP, and RADIUS is
> > reporting everything we're interested in knowing, including username,
> > PPP IPV6CP IIDs, chosen dynamic prefixes for the PPP session and dynamic
> > delegated prefixes if they're requested and the customer falls in that
> > service type.
> 
> Sure we can. If we redo our DHCP infrastructure to use Radius instead.
> It is a major change, and we don't really want to do it unless we
> absolutely have to.

Where did I say you had to change what you already had and were
satisfied with? All I've said is that I think SLAAC plus more
detailed ND state logging would be functionality equivalent to
what those who advocate stateful DHCPv6 addressing usually
state they require, and that is generally in the (unstated) common case
of a LAN environment, although it may also be applicable in an SP/CPE
scenario. I think if the choice between SLAAC + more detailed router ND
state recording verses stateful DHCPv6 was commonly available, the SLAAC
option would be the most likely choice, due to more (and most likely
all) IPv6 end-nodes supporting SLAAC (in the common case context of a
LAN environment).

> 
> There are plenty of *other* bumps in the road on our way to IPv6. I
> see no need to introduce more of these than necessary.
> 

Maintaining state costs CPU, RAM, and potentially disk space and
network traffic. Reducing the amount of state and/or gaining more value
out of existing essential state seems to me to be a worthy goal. In
practical terms, I think reducing the end-node requirement for stateful
DHCPv6, and leveraging the existing and essential NUD state to achieve
the same functional results for most use cases of stateful DHCPv6 would
be something worth aiming for.

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Mar 12 18:03:13 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 830753A6ACD for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 18:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.828
X-Spam-Level: 
X-Spam-Status: No, score=-1.828 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ovhb97GptnH0 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 18:03:12 -0800 (PST)
Received: from smtp4.adam.net.au (smtp4.adam.net.au [202.136.110.247]) by core3.amsl.com (Postfix) with ESMTP id 3011A3A6AB4 for <ipv6@ietf.org>; Sat, 12 Mar 2011 18:03:12 -0800 (PST)
Received: from 114-30-119-224.ip.adam.com.au ([114.30.119.224] helo=opy.nosense.org) by smtp4.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PyafQ-0000wk-7v; Sun, 13 Mar 2011 12:34:24 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id A135D5355B; Sun, 13 Mar 2011 12:34:21 +1030 (CST)
Date: Sun, 13 Mar 2011 12:34:21 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Message-ID: <20110313123421.5a5c8ea1@opy.nosense.org>
In-Reply-To: <4D7C166A.9060608@gont.com.ar>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <233b01cbdef5$8e214550$aa63cff0$@com> <25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com> <091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com> <78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com> <262f01cbdf5d$607c69f0$21753dd0$@com> <4D7C0EE5.2080405@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D7C166A.9060608@gont.com.ar>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 02:03:13 -0000

On Sat, 12 Mar 2011 21:57:14 -0300
Fernando Gont <fernando@gont.com.ar> wrote:

> On 12/03/2011 09:44 p.m., Christian Huitema wrote:
> 
> >> It doesn't. The I-D aims at allowing routers specify which policy
> >> they want hosts to employ when generating their IPv6 addresses.
> > 
> > Uh? I definitely don't want to give the router at Starbucks the means
> > to specify the privacy configuration of my laptop.
> 
> Override the advice provided by the router at Starbucks, and you're done
> (e.g., I guess this could even be automatically done by the OS depending
> on how you tag the network you're connecting to (e.g., Public, Home,
> whatever)).
> 
> 

I doubt typical end-users will be capable of getting this right often
enough for them to accept the possible privacy compromise when they
don't.

So what is wrong with the record and observe model, avoiding modifying
existing protocols and end-nodes to achieve your goal?

I don't understand why proactively putting an entry in a
neighbor cache when an end-node performs DAD, on a designated audit
device, and then letting NUD observe and report state changes for that
neighbor cache entry won't achieve the goal. There may need to be some
minor changes to ND state mechanisms to achieve this (e.g. ignore the
DAD if there is already an entry for the DAD tentative IPv6 address,
as DAD will fail, and maybe report it), however those changes
would only be required to be deployed to the audit device.

> 
> > If we want policy options to be applied safely, they have to be
> > propagated by trusted mechanism, where the host can verify the
> > authority of the policy source. Anything else is abuse waiting to
> > happen.
> 
> The threat model for this case is no different to that for ND in general...
> 

Existing addressing mechanisms in ND only have a goal of advising
end-nodes what method they should use to acquire their IPv6 addresses.
The end-node has a vested interest in following that advice, as it
will provide connectivity to other peer nodes as well as off-link
connectivity. However, end-nodes can ignore it, and e.g. use static
addressing or link-local addressing to still achieve useful
connectivity, albeit more limited than if they followed the advice in
an RA.

If you want to place far more trust in the end-nodes' address
selection choice, for audit purposes, I think you're going to have to
build much more complicated mechanisms that the one proposed, that allow
you to be assured that they've followed your advice.

Regards,
Mark.

From ichiroumakino@gmail.com  Sat Mar 12 23:37:36 2011
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EFD63A68C0 for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 23:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zVJwMKSDab0i for <ipv6@core3.amsl.com>; Sat, 12 Mar 2011 23:37:35 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 444B83A6805 for <ipv6@ietf.org>; Sat, 12 Mar 2011 23:37:35 -0800 (PST)
Received: by eye13 with SMTP id 13so1582270eye.31 for <ipv6@ietf.org>; Sat, 12 Mar 2011 23:38:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=YZjA1we1SstDTt36A0RV/SkE6PjIl2rtjla5Wd/PANg=; b=nOL8qJHCjfAgeHTp7j4B9/wLPr6B8/I0hdKzcdOVj5Xx9TvOx2MMj6ONc9V86cL4VZ AAAqE6PhPmL9bsAmI0uIW3SnaU9Ruy5NfdyzDWbqEl4MIdF9kOgDx64UbZeQbYGtyCJE L/3fhMnXzAODnHXpxhknk64DSO+Dqmmw7wu/w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=oLYKnelgDz5FLsMmUnEcb1bP0Gq2vWoJkQ4lUuBbY0Ka+ik/XhfHZVqbmsaeZBhLh2 qGhW4vadsyORTGv1hxQ+1NqPJ3buIHyDOPt/lSouET/Q5D1aglvRm7pH0+JBNiWFJqQB /0CCnBsMJ+6Cqmhep7A+WjbUVMjxxvfLBcwM0=
Received: by 10.213.25.79 with SMTP id y15mr2299513ebb.41.1300001936319; Sat, 12 Mar 2011 23:38:56 -0800 (PST)
Received: from gomlefisk.cisco.com (152.84-48-210.nextgentel.com [84.48.210.152]) by mx.google.com with ESMTPS id q53sm4879625eeh.10.2011.03.12.23.38.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 12 Mar 2011 23:38:53 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <4D7C14C7.4020508@dougbarton.us>
Date: Sun, 13 Mar 2011 08:37:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C8BD88A-2E20-4485-B22C-09F1B56B2D09@employees.org>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<233b01cbdef5$8e214550$aa63cff0$@com>	<25B3D469-F3DA-4A1D-A462-FEB71FA69485@gmail.com>	<091D1284-99E4-450E-8AFF-7D4C6310D760@apple.com>	<78B923726E7D59429936580CF127E943A13E758C27@eu1rdcrdc1wx032.exi.nxp.com>	<262f01cbdf5d$607c69f0$21753dd0$@com> <4D7C0EE5.2080405@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C2420@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D7C14C7.4020508@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1082)
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 07:37:36 -0000

>>> It doesn't. The I-D aims at allowing routers specify which policy =
they want hosts to employ when generating their IPv6 addresses.
>>=20
>> Uh? I definitely don't want to give the router at Starbucks the means =
to specify the privacy configuration of my laptop.
>>=20
>> I understand that corporation want to enforce policies so PC and =
routers are easier to manage, but we have to be careful. If we define =
that policy as part of the address configuration standard, then it will =
apply everywhere, not just in the corporate network where the laptop is =
managed. That seems a terrible idea.
>>=20
>> If we want policy options to be applied safely, they have to be =
propagated by trusted mechanism, where the host can verify the authority =
of the policy source. Anything else is abuse waiting to happen.
>=20
> Please consider this my periodic repetition of support for what =
Christian is saying here, along with my periodic repetition of =
opposition to (further) modifying RA/SLAAC to do things that DHCP =
can/does do, or should be doing.

+1

> And to state publicly something that I discussed in private, I'm =
completely unsympathetic to the viewpoint that "we need to show to the =
auditors that we tried to prevent hosts from doing bad things" in the =
absence of rigorous security steps to _actually_ prevent them.

+1

Ole


From Internet-Drafts@ietf.org  Sun Mar 13 08:30:04 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 171FA3A6989; Sun, 13 Mar 2011 08:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4MzM1jExUn7; Sun, 13 Mar 2011 08:30:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41C173A6933; Sun, 13 Mar 2011 08:30:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-rpl-routing-header-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110313153002.13737.12413.idtracker@localhost>
Date: Sun, 13 Mar 2011 08:30:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 15:30:04 -0000

--NextPart

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


	Title           : An IPv6 Routing Header for Source Routes with RPL
	Author(s)       : J. Hui, et al.
	Filename        : draft-ietf-6man-rpl-routing-header-02.txt
	Pages           : 19
	Date            : 2011-03-13

In Low power and Lossy Networks (LLNs), memory constraints on routers
may limit them to maintaining at most a few routes.  In some
configurations, it is necessary to use these memory constrained
routers to deliver datagrams to nodes within the LLN.  The Routing
for Low Power and Lossy Networks (RPL) protocol can be used in some
deployments to store most, if not all, routes on one (e.g. the
Directed Acyclic Graph (DAG) root) or few routers and forward the
IPv6 datagram using a source routing technique to avoid large routing
tables on memory constrained routers.  This document specifies a new
IPv6 Routing header type for delivering datagrams within a RPL
domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-routing-header-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-rpl-routing-header-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-13082236.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Sun Mar 13 14:00:03 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90E6F3A6BAB; Sun, 13 Mar 2011 14:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0DMMchKe8wU; Sun, 13 Mar 2011 14:00:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D98D3A6A02; Sun, 13 Mar 2011 14:00:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-flow-3697bis-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110313210002.27627.10446.idtracker@localhost>
Date: Sun, 13 Mar 2011 14:00:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 21:00:03 -0000

--NextPart

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


	Title           : IPv6 Flow Label Specification
	Author(s)       : S. Amante, et al.
	Filename        : draft-ietf-6man-flow-3697bis-02.txt
	Pages           : 13
	Date            : 2011-03-13

This document specifies the IPv6 Flow Label field and the minimum
requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
labeled packets, and flow state establishment methods.  Even when
mentioned as examples of possible uses of the flow labeling, more
detailed requirements for specific use cases are out of scope for
this document.

The usage of the Flow Label field enables efficient IPv6 flow
classification based only on IPv6 main header fields in fixed
positions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-3697bis-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-flow-3697bis-02.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-13134822.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Sun Mar 13 14:00:04 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6793A6A02; Sun, 13 Mar 2011 14:00:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7O0j8bzC6R6t; Sun, 13 Mar 2011 14:00:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85F303A6B91; Sun, 13 Mar 2011 14:00:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-flow-update-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110313210002.27627.62846.idtracker@localhost>
Date: Sun, 13 Mar 2011 14:00:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 21:00:04 -0000

--NextPart

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


	Title           : Rationale for update to the IPv6 flow label specification
	Author(s)       : S. Amante, et al.
	Filename        : draft-ietf-6man-flow-update-04.txt
	Pages           : 12
	Date            : 2011-03-13

Various published proposals for use of the IPv6 flow label are
incompatible with its original specification in RFC 3697.
Furthermore, very little practical use is made of the flow label,
partly due to some uncertainties about the correct interpretation of
the specification.  This document discusses and motivates changes to
the specification in order to clarify it, and to introduce some
additional flexibility.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-update-04.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-6man-flow-update-04.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-13134834.I-D@ietf.org>


--NextPart--

From brian.e.carpenter@gmail.com  Sun Mar 13 14:26:05 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9CEA3A6B80 for <ipv6@core3.amsl.com>; Sun, 13 Mar 2011 14:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUuxsvrul-F5 for <ipv6@core3.amsl.com>; Sun, 13 Mar 2011 14:26:05 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id DC55A3A680F for <ipv6@ietf.org>; Sun, 13 Mar 2011 14:26:04 -0700 (PDT)
Received: by gyf3 with SMTP id 3so893173gyf.31 for <ipv6@ietf.org>; Sun, 13 Mar 2011 14:27:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=ETs9hhKLP1qzyjlL2RRCKk1fY7Y1LUbeTJeXK6bFfeA=; b=EMmlsaAm+Qie/Ob2pXDkDzjUgSg4vCK3mL313qfX+n5xCLo9rHFNzTRhPCMNiC4sCE 5XNsQKgBJ+o36WxGNSd1kLIm/RKOuONKdaMNzWR4MBB98XnWZbaFaxDe58n0cwYGaHX7 /mj8GHf7bcC1LwdP6Qs5IHT8LcX/G0I9V3bqw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; b=BGN+TIQt0qKPdoiFBNMGhohc4PtdKzEY1vrJE3z5RhdTkgkXcC6qfMnlXpS3fLtSFb 6dX7Z1uln2ps8xMlkYDBgj/4DjK8+3LgggFWka1337HCdtfgTTtlO77kjrDHqP0Imowb MOqvgTsHfAOWZADWR7JQlWysBE5MHkKpvMgSI=
Received: by 10.151.3.3 with SMTP id f3mr5193993ybi.96.1300051646103; Sun, 13 Mar 2011 14:27:26 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q18sm1398752ybk.11.2011.03.13.14.27.24 (version=SSLv3 cipher=OTHER); Sun, 13 Mar 2011 14:27:25 -0700 (PDT)
Message-ID: <4D7D36BA.3040301@gmail.com>
Date: Mon, 14 Mar 2011 10:27:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: [Fwd: I-D Action:draft-ietf-6man-flow-3697bis-02.txt]
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 13 Mar 2011 21:26:06 -0000

Hi,

This update resolves the open issue by deleting most of the text
concerning the stateful model for the flow label, which is what the
comments received on and off the list indicated we should do.

There is also a trivial update to the rationale update to
match this change (draft-ietf-6man-flow-update-04.txt).

As noted previously, draft-ietf-6man-flow-ecmp-01.txt
was updated after WGLC.

   Brian

-------- Original Message --------
Subject: I-D Action:draft-ietf-6man-flow-3697bis-02.txt
Date: Sun, 13 Mar 2011 14:00:02 -0700
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
CC: ipv6@ietf.org

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


	Title           : IPv6 Flow Label Specification
	Author(s)       : S. Amante, et al.
	Filename        : draft-ietf-6man-flow-3697bis-02.txt
	Pages           : 13
	Date            : 2011-03-13

This document specifies the IPv6 Flow Label field and the minimum
requirements for IPv6 nodes labeling flows, IPv6 nodes forwarding
labeled packets, and flow state establishment methods.  Even when
mentioned as examples of possible uses of the flow labeling, more
detailed requirements for specific use cases are out of scope for
this document.

The usage of the Flow Label field enables efficient IPv6 flow
classification based only on IPv6 main header fields in fixed
positions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-flow-3697bis-02.txt


From Internet-Drafts@ietf.org  Mon Mar 14 03:00:05 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF8A93A6C62; Mon, 14 Mar 2011 03:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9sfj8IMiHe2u; Mon, 14 Mar 2011 03:00:04 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3240F3A6C58; Mon, 14 Mar 2011 03:00:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-rfc3484-revise-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314100003.5501.5607.idtracker@localhost>
Date: Mon, 14 Mar 2011 03:00:03 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 Mar 2011 10:00:06 -0000

--NextPart

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


	Title           : Update to RFC 3484 Default Address Selection for IPv6
	Author(s)       : A. Matsumoto, et al.
	Filename        : draft-ietf-6man-rfc3484-revise-02.txt
	Pages           : 11
	Date            : 2011-03-14

RFC 3484 describes algorithms for source address selection and for
destination address selection.  The algorithms specify default
behavior for all Internet Protocol version 6 (IPv6) implementations.
This document specifies a set of updates that modify the algorithms
and provide fixes for the identified issues.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rfc3484-revise-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-rfc3484-revise-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14025716.I-D@ietf.org>


--NextPart--

From pekkas@netcore.fi  Mon Mar 14 06:49:51 2011
Return-Path: <pekkas@netcore.fi>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BF9D3A6D6B for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 06:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7JR7uHRa-Df for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 06:49:50 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id E43563A6D18 for <ipv6@ietf.org>; Mon, 14 Mar 2011 06:49:49 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id p2EDp58d011215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Mar 2011 15:51:05 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id p2EDp3eu011211; Mon, 14 Mar 2011 15:51:04 +0200
Date: Mon, 14 Mar 2011 15:51:03 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: 6MAN WG Last Call: <draft-ietf-6man-node-req-bis-07.txt>
In-Reply-To: <201103110404.p2B44sD4021062@cichlid.raleigh.ibm.com>
Message-ID: <alpine.LRH.2.02.1103141537080.10683@netcore.fi>
References: <7B63F7B6-D788-4A05-9722-C1CAAA42B754@gmail.com> <201101171932.p0HJWU58003756@cichlid.raleigh.ibm.com> <alpine.LRH.2.02.1102181052020.3891@netcore.fi> <201103110404.p2B44sD4021062@cichlid.raleigh.ibm.com>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Virus-Scanned: clamav-milter 0.97 at otso.netcore.fi
X-Virus-Status: Clean
Cc: 6man Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 Mar 2011 13:49:51 -0000

On Thu, 10 Mar 2011, Thomas Narten wrote:
>> Some requirement levels have also changed, and explicit support from
>> WG would be good on these.  With an updated RFC4294 changelog, rough
>> consensus on the result could be evaluated.
>
> OK. But to be clear, the changes in this document have been discussed
> on the list and IMO do have consensus. I.e., they are not "surprises".

Yes, I don't doubt they've been mentioned, but given the long time 
cycle and that a lot of participants do not have time to read all 
the mails very closely, strong consensus can be best built by 
iteration. (But it can also lead to iteration cycles and hashing the 
same issues over and over again, of course)

>> The document should be IETF last called.
>
> No objection.

Wrt. to Bob's comment, I was just pointing out that Informational 
documents do not (by IETF procedures) require an IETF Last Call. It's 
good that 6MAN documents have set a higher bar :-)

>> WG should explicitly request feedback from at least IPSECME WG.
>
> IPsecME has seen and reviewed text. Indeed, some IPsecME members
> helped with getting the text right. I also presented the text at the
> saag meeting in Maastricht

Great to hear, maybe this is a non-issue then!

>> I think this document should also discuss APIs we have defined and that
>> relate to the protocols described in the document.  A separate section
>> should be added on this.
>
> I added a section on APIs. I made them all FYIs. I agree with the
> comments others have made on the list that we can't mandate them.

Works for me.

>> S 5.8.3 has watered down the privacy addresses text:
>
>>     In such situations, RFC4941 SHOULD be implemented.  In other cases,
>>     such as with dedicated servers in a data center, RFC4941 provides
>>     limited or no benefit.
>
>> .. this is not acceptable.  Per previous RFC, we should say:
>
>>     RFC4941 SHOULD be supported.
>
> I strongly disagree, and there was a thread about this. I have seen
> cases where people just assume that 4941 should be supported by all
> nodes, including servers (not clients) in data centers. There is no
> need to implement 4941 on server-only systems.
>
> Please review the thread at
> http://www.ietf.org/mail-archive/web/ipv6/current/msg10468.html and if
> you have further comments, speak up. But it was an explicit goal to
> not just say "SHOULD" with not context/direction, as RFC 4294 does.

I should have articulated my objection more clearly. The issue stems 
from the word "implemented".  I totally agree that it's a bad idea to 
turn on 4941 on server nodes.  But because it's usually difficult to 
distinguish purely client and server implementations, in most cases 
4941 should be implemented -- the big question is really whether to 
turn it on or off.

>
>> In S 5.9,
>>     A reference should be added (MAY support) to RFC 5790,
>> "Lightweight Internet Group Management Protocol Version 3 (IGMPv3) and
>> Multicast Listener Discovery Version 2 (MLDv2) Protocols"
>
> Actually, I may need some help with this.
>
> If 5790 is enough, and omits functionality that most nodes don't need,
> we should recommend its usage.
>
> We should provide clear guidance on when it makes sense to recommend
> one over the other.

Hitoshi Aseada (author) made some suggestions on this on the list on 
Feb 21-22.  IMHO, 5790 seems enough and only omits functionality that 
the most nodes don't need (but I also don't see a pressing need for 
existing implementations to take out these bits).

....

A few editorial bugs in the latest version:

- the added text on more-specific routes (S 5.3) mistakenly points to
   rfc5942.

- running " in the added rfc4941 text in S 5.9.3

- there's some overlap in the changelog section, at least rfc5952 and
   rfc5722 are mentioned twice. (strange to see both numbered and
   non-numbered entries there as well.)


-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

From Internet-Drafts@ietf.org  Mon Mar 14 09:30:19 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0988E3A6D75; Mon, 14 Mar 2011 09:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6G3dUsB66HJA; Mon, 14 Mar 2011 09:30:05 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C8223A6A06; Mon, 14 Mar 2011 09:30:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-addr-select-considerations-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314163004.26365.91477.idtracker@localhost>
Date: Mon, 14 Mar 2011 09:30:04 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 Mar 2011 16:30:19 -0000

--NextPart

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


	Title           : Considerations for IPv6 Address Selection Policy Changes
	Author(s)       : T. Chown
	Filename        : draft-ietf-6man-addr-select-considerations-03.txt
	Pages           : 19
	Date            : 2011-03-14

Where the source and/or destination node of an IPv6 communication is
multi-addressed, a mechanism is required for the initiating node to
select the most appropriate address pair for the communication.  RFC
3484 (IPv6 Default Address Selection) [RFC3484] defines such a
mechanism for nodes to perform source and destination address
selection.  While RFC3484 recognised the need for implementations to
be able to change the policy table, it did not define how this could
be achieved.  Requirements have now emerged for administrators to be
able to configure and potentially dynamically change RFC 3484 policy
from a central control point, and for (nomadic) hosts to be able to
obtain the policy for the network that they are currently attached to
without manual user intervention.  This text discusses considerations
for such policy changes, including examples of cases where a change
of policy is required, and the likely frequency of such policy
changes.  This text also includes some discussion on the need to also
update RFC 3484, where default policies are currently defined.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-addr-select-considerations-03.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-addr-select-considerations-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14092341.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Mon Mar 14 15:30:10 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2E693A6DB9; Mon, 14 Mar 2011 15:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHxbbYNC-dGn; Mon, 14 Mar 2011 15:30:08 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34A113A691F; Mon, 14 Mar 2011 15:30:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-exthdr-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110314223006.15936.74266.idtracker@localhost>
Date: Mon, 14 Mar 2011 15:30:06 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 Mar 2011 22:30:10 -0000

--NextPart

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


	Title           : An uniform format for IPv6 extension headers
	Author(s)       : S. Krishnan, et al.
	Filename        : draft-ietf-6man-exthdr-02.txt
	Pages           : 6
	Date            : 2011-03-14

In IPv6, optional internet-layer information is encoded in separate
headers that may be placed between the IPv6 header and the transport
layer header.  There are a small number of such extension headers
currently defined.  This document defines a format for defining new
IPv6 extension headers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-exthdr-02.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-6man-exthdr-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14152048.I-D@ietf.org>


--NextPart--

From john@jlc.net  Mon Mar 14 15:54:04 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C2413A6D34 for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 15:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fs9aYxJ6LHH for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 15:54:02 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id A69353A6BCB for <ipv6@ietf.org>; Mon, 14 Mar 2011 15:54:02 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 6857333C29; Mon, 14 Mar 2011 18:55:26 -0400 (EDT)
Date: Mon, 14 Mar 2011 18:55:26 -0400
From: John Leslie <john@jlc.net>
To: ipv6@ietf.org
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
Message-ID: <20110314225526.GB52874@verdi>
References: <20110314223006.15936.74266.idtracker@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110314223006.15936.74266.idtracker@localhost>
User-Agent: Mutt/1.4.1i
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 Mar 2011 22:54:04 -0000

Internet-Drafts@ietf.org <Internet-Drafts@ietf.org> wrote:
> 
> 	Title           : An uniform format for IPv6 extension headers
> 	Author(s)       : S. Krishnan, et al.
> 	Filename        : draft-ietf-6man-exthdr-02.txt
> 	Pages           : 6
> 	Date            : 2011-03-14
> 
> In IPv6, optional internet-layer information is encoded in separate
> headers that may be placed between the IPv6 header and the transport
> layer header.  There are a small number of such extension headers
> currently defined.  This document defines a format for defining new
> IPv6 extension headers.

   I notice that Section 4 calls for TLV:
] 
] 4. Proposed IPv6 Extension Header format
] 
]  This document proposes that all IPv6 extension headers be encoded in
]  a consistent TLV format so that it is possible for nodes to skip over
]  unknown extension headers and continue to further process the header
]  chain.

   But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
the TLV format.

   What am I missing?

--
John Leslie <john@jlc.net>

From Internet-Drafts@ietf.org  Mon Mar 14 17:00:02 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E26AA3A6977; Mon, 14 Mar 2011 17:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BlUiBOQTXxpy; Mon, 14 Mar 2011 17:00:02 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F4DB3A6B8B; Mon, 14 Mar 2011 17:00:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-lineid-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.12
Message-ID: <20110315000002.23483.55819.idtracker@localhost>
Date: Mon, 14 Mar 2011 17:00:02 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 00:00:03 -0000

--NextPart

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


	Title           : The Line Identification Destination Option
	Author(s)       : S. Krishnan, et al.
	Filename        : draft-ietf-6man-lineid-01.txt
	Pages           : 13
	Date            : 2011-03-14

In Ethernet based aggregation networks, several subscriber premises
may be logically connected to the same interface of an edge router.
This document proposes a method for the edge router to identify the
subscriber premises using the contents of the received Router
Solicitation messages.  The applicability is limited to broadband
network deployment scenarios where multiple user ports are mapped to
the same virtual interface on the Edge Router.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-lineid-01.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-6man-lineid-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-14164834.I-D@ietf.org>


--NextPart--

From suresh.krishnan@ericsson.com  Mon Mar 14 17:16:06 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 341993A6BFB for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 17:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81OkoaYjCnd7 for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 17:16:05 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id D46063A6EAC for <ipv6@ietf.org>; Mon, 14 Mar 2011 17:16:02 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2F0HPIA005313; Mon, 14 Mar 2011 19:17:26 -0500
Received: from [142.133.10.107] (147.117.20.213) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.2.234.1; Mon, 14 Mar 2011 20:17:19 -0400
Message-ID: <4D7EAF77.3080504@ericsson.com>
Date: Mon, 14 Mar 2011 20:14:47 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
References: <20110314223006.15936.74266.idtracker@localhost> <20110314225526.GB52874@verdi>
In-Reply-To: <20110314225526.GB52874@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 00:16:06 -0000

Hi John,

On 11-03-14 06:55 PM, John Leslie wrote:
> Internet-Drafts@ietf.org <Internet-Drafts@ietf.org> wrote:
>> 	Title           : An uniform format for IPv6 extension headers
>> 	Author(s)       : S. Krishnan, et al.
>> 	Filename        : draft-ietf-6man-exthdr-02.txt
>> 	Pages           : 6
>> 	Date            : 2011-03-14
>>
>> In IPv6, optional internet-layer information is encoded in separate
>> headers that may be placed between the IPv6 header and the transport
>> layer header.  There are a small number of such extension headers
>> currently defined.  This document defines a format for defining new
>> IPv6 extension headers.
> 
>    I notice that Section 4 calls for TLV:
> ] 
> ] 4. Proposed IPv6 Extension Header format
> ] 
> ]  This document proposes that all IPv6 extension headers be encoded in
> ]  a consistent TLV format so that it is possible for nodes to skip over
> ]  unknown extension headers and continue to further process the header
> ]  chain.
> 
>    But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
> the TLV format.

The T is the "Next Header", the L is the "Hdr Ext Len" and V is the 
"Header Specific Data" as specified in the figure in Section 4 of the draft.

Thanks
Suresh


From fernando.gont.netbook.win@gmail.com  Tue Mar 15 04:54:05 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B5693A6C96 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 04:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3X+2h0ufAeql for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 04:54:04 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 123DA3A6C65 for <ipv6@ietf.org>; Tue, 15 Mar 2011 04:54:03 -0700 (PDT)
Received: by bwz13 with SMTP id 13so508696bwz.31 for <ipv6@ietf.org>; Tue, 15 Mar 2011 04:55:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=OiCktJgF6X12ssKD2RV80cRUE3wzXM5zH6qU04zjvX8=; b=p7b+a6ZzIIA7Mk906O6PThJcwn63PaMeCh6LRQYoIq30ylStqgC6l2xTXZvtaEeG5R +dCVjvGT05AV/0mqRauoJpuzdJIYK6fQp2rW8c+0b7QhFg4gW87eSIwFGWNFXafYm7PJ 3JgP1P6f6euX79f5LnJ8d6+Ka/C7g2a4xhGKQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=LnUAqJsY2M15/I3VQUqGLPSSYVxZ4wM+qbqVDRPWuEs7+2gBK9W2WOtjGooZHGntXK Cjy1Z1cY0BWQ5WfKDWynuOs29lGBP/oiKDUB6iNyWtjHtrPeCZ2OUsue+62dhtC6YMC0 fZfQokGbMzD4nOke587EeUS8XgdYuHpcax4tk=
Received: by 10.204.16.216 with SMTP id p24mr1463821bka.5.1300190116924; Tue, 15 Mar 2011 04:55:16 -0700 (PDT)
Received: from [192.168.200.58] ([194.2.150.133]) by mx.google.com with ESMTPS id c11sm4406135bkc.2.2011.03.15.04.55.12 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Mar 2011 04:55:13 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D7F539E.7030308@gont.com.ar>
Date: Tue, 15 Mar 2011 08:55:10 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org>
In-Reply-To: <20110310071925.309d467b@opy.nosense.org>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 11:54:05 -0000

On 09/03/2011 05:49 p.m., Mark Smith wrote:
> I agree. I sort of accept that an ISP can know my addresses in use, in
> part because they gave them to me. However, for an ISP to not let me
> choose if I want to use privacy addresses on the Internet would
> be completely unacceptable.

Why would you find it acceptable to have the ISP assign you the complete
address e.g. with DHCP, then?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From john@jlc.net  Tue Mar 15 06:24:15 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 691D63A6B5A for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 06:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yt++gs4ZUixn for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 06:24:14 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id 753EE3A694E for <ipv6@ietf.org>; Tue, 15 Mar 2011 06:24:14 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8E5BA33C2D; Tue, 15 Mar 2011 09:25:39 -0400 (EDT)
Date: Tue, 15 Mar 2011 09:25:39 -0400
From: John Leslie <john@jlc.net>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
Message-ID: <20110315132539.GD52874@verdi>
References: <20110314223006.15936.74266.idtracker@localhost> <20110314225526.GB52874@verdi> <4D7EAF77.3080504@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D7EAF77.3080504@ericsson.com>
User-Agent: Mutt/1.4.1i
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 13:24:15 -0000

Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> On 11-03-14 06:55 PM, John Leslie wrote:
>>
>>   I notice that Section 4 calls for TLV:
>>] 
>>] 4. Proposed IPv6 Extension Header format
>>] 
>>]  This document proposes that all IPv6 extension headers be encoded in
>>]  a consistent TLV format so that it is possible for nodes to skip over
>>]  unknown extension headers and continue to further process the header
>>]  chain.
>>
>> But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
>> the TLV format.
> 
> The T is the "Next Header", the L is the "Hdr Ext Len" and V is the 
> "Header Specific Data" as specified in the figure in Section 4 of the
> draft.

   Well, of course "Next Header" _isn't_ the Type of this option (rather
it's the Type of the next option).

   And the "Hdr Ext Len" isn't a particularly intuitive coding of Length
either...

   IMHO, referring to this format as "TLV" is unnecessarily confusing.

   Also IMHO, if we do define another Extension Header, it's likely we'll
want to make it expandable using the TLV format we _are_ familiar with.

--
John Leslie <john@jlc.net>

From suresh.krishnan@ericsson.com  Tue Mar 15 06:59:35 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 661463A6D4B for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 06:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ipqoakg2kd2k for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 06:59:34 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 8D1683A6D4A for <ipv6@ietf.org>; Tue, 15 Mar 2011 06:59:34 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2FE0Qhh009126; Tue, 15 Mar 2011 09:00:59 -0500
Received: from [142.133.10.107] (147.117.20.213) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 10:00:48 -0400
Message-ID: <4D7F7073.3050009@ericsson.com>
Date: Tue, 15 Mar 2011 09:58:11 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
References: <20110314223006.15936.74266.idtracker@localhost> <20110314225526.GB52874@verdi> <4D7EAF77.3080504@ericsson.com> <20110315132539.GD52874@verdi>
In-Reply-To: <20110315132539.GD52874@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 13:59:35 -0000

Hi John,

On 11-03-15 09:25 AM, John Leslie wrote:
> Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
>> On 11-03-14 06:55 PM, John Leslie wrote:
>>>   I notice that Section 4 calls for TLV:
>>> ] 
>>> ] 4. Proposed IPv6 Extension Header format
>>> ] 
>>> ]  This document proposes that all IPv6 extension headers be encoded in
>>> ]  a consistent TLV format so that it is possible for nodes to skip over
>>> ]  unknown extension headers and continue to further process the header
>>> ]  chain.
>>>
>>> But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
>>> the TLV format.
>> The T is the "Next Header", the L is the "Hdr Ext Len" and V is the 
>> "Header Specific Data" as specified in the figure in Section 4 of the
>> draft.
> 
>    Well, of course "Next Header" _isn't_ the Type of this option (rather
> it's the Type of the next option).
> 
>    And the "Hdr Ext Len" isn't a particularly intuitive coding of Length
> either...

Yep. You are right on both counts, but I am not sure how we can change 
this. We cannot chain the headers without the T being in the *previous* 
header. I think the best we can do is to refrain from calling this TLV 
like you said.

> 
>    IMHO, referring to this format as "TLV" is unnecessarily confusing.

OK.

> 
>    Also IMHO, if we do define another Extension Header, it's likely we'll
> want to make it expandable using the TLV format we _are_ familiar with.

Do you mean inside the Header Specific data? If so, yes, that makes 
perfect sense.

Thanks
Suresh


From hanauska@equinux.de  Mon Mar 14 04:59:20 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980403A68E4 for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 04:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTV6Qyg7NUxz for <ipv6@core3.amsl.com>; Mon, 14 Mar 2011 04:59:19 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id C4AB93A68C7 for <ipv6@ietf.org>; Mon, 14 Mar 2011 04:59:18 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hfnosa0171ss for <ipv6@ietf.org>; Mon, 14 Mar 2011 11:44:54 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Mon, 14 Mar 2011 11:44:54 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 23F9520F4DD6 for <ipv6@ietf.org>; Mon, 14 Mar 2011 13:00:11 +0100 (CET)
From: Markus Hanauska <hanauska@equinux.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Date: Mon, 14 Mar 2011 13:00:11 +0100
Message-Id: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>
To: ipv6@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103141044540078654
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 14:12:42 -0000

Since IPv6 plays an increasingly prominent role in planing network =
environments, I spent most of the weekend to think about IPv6 =
distribution strategies for our company and my home Internet connection, =
re-reading most of the important RFCs and I came across a serious =
address deployment issue that seems to not be addressed by any of them. =
I searched the Internet, since I could not believe nobody every came =
across that issue, but after reading over 100 web pages and over 50 =
papers regarding IPv6 address deployment, this issue either has not been =
discovered up to now or has been intentionally ignored. I must admit, =
the issue is highly unlikely to ever cause a problem in real life =
scenarios, but as a programmer there is a huge difference between =
"impossible" and "highly unlikely", and I definitely prefer =
"impossible".

I assume you are all familiar with all those RFCs in question, thus I =
don't want to bore you more than necessary, but I have to go into =
greater detail to make sure my concern is correctly understood. Assuming =
that you plan address distribution according to the 64/64 rule of RFC =
4291, using 64 bit network ID and 64 bit host ID, there are 4 major ways =
how to distribute the addresses:

A) Manually - definitely necessary for routers and most likely a good =
idea for permanent services (DNS-, mail-, file-servers, etc.)

B) DHCPv6 according to RFC 3315 - either randomly distribute addresses =
from available pools or possibly even reserve certain addresses for =
certain hosts by MAC address.

C) Stateless Address Autoconfiguration according to RFC 4862 - currently =
the auto configuration scheme supported by most operating systems and =
devices. This major case has four important major sub-cases that people =
tend to ignore in general (there are some more minor sub-cases, but I'd =
like to ignore those here as well):

	C1) Device has a globally unique EU-/MAC-48 identifier
	C2) Device has NO globally unique EU-/MAC-48 identifier, but one =
manually assigned by a network admin
	C3) Device has a globally unique EU-64 identifier
	C4) Device has no globally unique EU-64 identifier, but one =
manually assigned by a network admin

D) Stateless Address Autoconfiguration with Privacy Extension according =
to RFC 4941

You can pick either scheme above or you can pick multiple at the same =
time. The second case implies that all these four schemes must =
peacefully coexist within the same network at the same time, and exactly =
this is *NOT* the case. Let me explain my concerns to you:

Mixing (A) and (B) shouldn't be a problem, just like in case of IPv4 =
admins only have to make sure that the manual addresses never overlap =
any DHCP address pool; this should be easily enforceable. E.g. reserve =
<prefix>::1 to <prefix>::FF (sorry for using upper case hex, it just =
reads better on my screen) for manual assignment (254 addresses) and =
<prefix>::100 to <prefix>::FF:FFFF as DHCP pool (over 16 mio DHCP =
addresses).

Adding (C) to the mix is no problem either, but only if you are aware of =
some border cases that are to be avoided. In most cases (C) means (C1) =
or (C3) and that means no conflicts are to be expected, since (C1)+(C3) =
have addresses which have the "u"-bit set to indicate global uniqueness, =
while this bit is never set in cases (A) and (B) - this is the original =
intention behind "inverting" the bit according to the RFC.=20

What most people tend to ignore are the cases (C2) and (C4), where the =
"u" bit will not be set after inverting it and those cases are not plain =
hypothetical, I have seen them in real-life more than once. There exists =
still no problem in case of (C2), since FFFE will be added to the =
address and network admins are thus advised to not choose manual and =
DHCP address ranges in such a way, that they might ever have FFFE at the =
same position. This leaves only (C4) addresses that might potentially =
conflict with cases (A) and (B) and this is easily to be avoided by =
making sure network admins never manually assign local hardware =
identifiers where the vendor ID (the first three bytes of the =
identifier) are all zero. Not that it would be forbidden to do so, but =
considering the case of potential conflicts, it is just not advisable =
and also avoidable.

So far all these standards peacefully coexist with each other... =
however, case (D) does not. Case (D) can conflict with all other cases, =
except the cases (C1) and (C3). And that even though a tiny modification =
of RFC 4941 could entirely avoid this issue. A modification that would =
lead to maybe four lines of code in most IPv6 implementations out there. =
All that was necessary was adding the rule, that those random addresses =
must never start with three zero bytes and the address generation =
process must be repeated if such an address is generated on the first =
attempt. I must admit, an MD5 hash where the first three byte are all =
zero is rather unlikely but it is not impossible; unless someone can =
prove to me mathematically, that given the possible input data, such an =
outcome is absolutely impossible. However, bear in mind that the RFC =
does not require the usage of MD5, it only suggests it and even if it is =
impossible for MD5, who can guarantee it will be impossible for all =
other existing hash functions in the world that will ever be used for =
IPv6 address generation? I don't think I have to explain here how case =
(D) can conflict with all the other cases, since the address is =
unpredictable, any result is possible. And bear in mind, that other RFCs =
even mention cases where a device might create its 64 bit host ID =
entirely "random"; which is even worse than using a hash function.

I know what people will probably reply up to this point: No conflict can =
ever arise, duplicate address detection (DAD) is going to prevent that. =
And here is my reply: How is DAD preventing this problem if the device =
with the conflicting address in question is not connected to the network =
the moment DAD is performed? E.g. the address of type (D) conflicts with =
a DHCP address (very unlikely, but possible), a DHCP address that has =
been reserved for a certain mobile device, which currently is not =
connected to the network. DAD will not see any conflict and assign the =
IP to some other device. If now the mobile device is added to the =
network, it cannot obtain its reserved DHCP address. Of course the same =
is true for server with an manually assigned IP address that is only =
turned on at certain times of the day for example. And the same problem =
arises for a mobile device with a manual assigned interface ID as in =
cases (C2) or (C4).

I think we can safely ignore any security aspects here, since an =
attacker can always manually assign any address to any interface he =
likes, possibly using a manipulated IPv6 implementation that will simply =
never perform DAD. If someone wants to create address collisions by =
intention, there is no easy way to stop him and there are other =
standards that deal with host authentication. I'm only concerned about =
the fact that a couple of address deployment schemes that were designed =
to be simple and to ease the life of all network admins and home users, =
were not designed to always peacefully coexist within a single network, =
where hosts might come and go any time. Has this issue really been =
intentionally ignored, because given 2^64 addresses, the likeliness of a =
collision was seen as too unlikely to ever take place in real-life?

Regards,
Markus Hanauska=

From hingkam16@gmail.com  Tue Mar 15 07:36:19 2011
Return-Path: <hingkam16@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F09A3A6D85 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 07:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soh4bIk50TQ9 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 07:36:18 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 7F45F3A6D20 for <ipv6@ietf.org>; Tue, 15 Mar 2011 07:36:18 -0700 (PDT)
Received: by gxk19 with SMTP id 19so314202gxk.31 for <ipv6@ietf.org>; Tue, 15 Mar 2011 07:37:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=4VyseUztwGyEkihBVCc5H4tjz/jAvluC47/H9WTku2s=; b=GZYDAoDzs9xuuk+Bfp8zckQF9g2JBMZ72pKP2609CAPBeeR3lzhOBEE8TlTzyUe9zT QvrlXQjyMHRrcyt4cs2FsMz+Ibc8YCr6raNVHQtygGxTRH7BJNnT6NJ5xZJ9b9KNAGCs qLCkE0AJn/sea7ghGKHbF7Q3wpBMFgzuzZabM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=cq9XAhyvXvKOmP441oNDGrco1Z91AT+RlLpvavBhxD9xkspzCCgb2gKr0Orw1ld12p nb8fz4csVOc3jwZfuywFiYQLc/7PcGFjbnEJ7Ur0SmjVbXDzhUAzbbPCWQjowMQnDdUD Sv4/f1ZrkLxlMOqg/+/t4B+fiuXMxERuWfPj4=
MIME-Version: 1.0
Received: by 10.42.138.129 with SMTP id c1mr6012152icu.492.1300199863224; Tue, 15 Mar 2011 07:37:43 -0700 (PDT)
Received: by 10.231.37.13 with HTTP; Tue, 15 Mar 2011 07:37:43 -0700 (PDT)
In-Reply-To: <20110314223006.15936.74266.idtracker@localhost>
References: <20110314223006.15936.74266.idtracker@localhost>
Date: Tue, 15 Mar 2011 20:07:43 +0530
Message-ID: <AANLkTinW5DbxJvXB6i0iVDKG56CS3w=wHS+wBpR==8UO@mail.gmail.com>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
From: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
To: ipv6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 14:36:19 -0000

I am forgetting what the resolution was on the Hdr Options that were
defined in the -01 version. I find those missing here, so i assume
that they have been intentionally dropped out. I was personally in
favor of those and didnt see too much harm in keeping them.

Other than the small nit above, the current version looks good.

Kam

On Tue, Mar 15, 2011 at 4:00 AM,  <Internet-Drafts@ietf.org> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the IPv6 Maintenance Working Group of the IE=
TF.
>
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : An uniform format for IPv6 ext=
ension headers
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : S. Krishnan, et al.
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-6man-exthdr-02.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 6
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-03-14
>
> In IPv6, optional internet-layer information is encoded in separate
> headers that may be placed between the IPv6 header and the transport
> layer header. =A0There are a small number of such extension headers
> currently defined. =A0This document defines a format for defining new
> IPv6 extension headers.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-6man-exthdr-02.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

From pch-b6B5344D9@u-1.phicoh.com  Tue Mar 15 08:56:53 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 464E63A6D2A for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 08:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F1sBEN9wcsxM for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 08:56:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id 2B6643A6C5B for <ipv6@ietf.org>; Tue, 15 Mar 2011 08:56:51 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1PzWdR-0001h0C; Tue, 15 Mar 2011 16:58 +0100
Message-Id: <m1PzWdR-0001h0C@stereo.hq.phicoh.net>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
In-reply-to: Your message of "Mon, 14 Mar 2011 13:00:11 +0100 ." <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> 
Date: Tue, 15 Mar 2011 16:58:04 +0100
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 15:56:53 -0000

In your letter dated Mon, 14 Mar 2011 13:00:11 +0100 you wrote:
>And bear in mind, that other RFCs even mention cases where a device might 
>create its 64 bit host ID entirely "random"; which is even worse than using a 
>hash function.

I think the answer is that is statistically very unlikely that on a single
subnet, a 64-bit random number will ever be equal to any address manually
configured in DHCP.

Is is far more likely that by accident to ethernet cards have the same MAC
address than that a true 64-bit random number will collide with another number
out of a relatively small set.



From jhw@apple.com  Tue Mar 15 10:26:44 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B1013A6D28 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 10:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RL9hFBxXkn1p for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 10:26:43 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 603253A69F9 for <ipv6@ietf.org>; Tue, 15 Mar 2011 10:26:43 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 7D016D927791 for <ipv6@ietf.org>; Tue, 15 Mar 2011 10:28:08 -0700 (PDT)
X-AuditID: 11807137-b7c3cae0000010f5-4b-4d7fa1a89b21
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay16.apple.com (Apple SCV relay) with SMTP id BB.34.04341.8A1AF7D4; Tue, 15 Mar 2011 10:28:08 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LI400C4O0IWSH20@gertie.apple.com> for ipv6@ietf.org; Tue, 15 Mar 2011 10:28:08 -0700 (PDT)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
From: james woodyatt <jhw@apple.com>
In-reply-to: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>
Date: Tue, 15 Mar 2011 10:28:07 -0700
Message-id: <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>
To: Markus Hanauska <hanauska@equinux.de>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 17:26:44 -0000

On Mar 14, 2011, at 05:00 , Markus Hanauska wrote:
> 
> [...] And here is my reply: How is DAD preventing this problem if the device with the conflicting address in question is not connected to the network the moment DAD is performed? [...]

Were RFC 4429 and I-D.ietf-6man-dad-proxy among the documents you read over the weekend?

In general, you cannot prevent address conflict simply by reserving interface identifier patterns according to a strict plan.  No plan ever survives its initial encounter with the enemy.  Address conflicts MUST be dynamically resolved by protocol action, and protocols can fail when packets are lost.  Retransmits help reduce failure rates, but failure cannot ever be made logically impossible.  (There is math for that claim.)

Duplicate Address Detection (DAD) is the mechanism by which address conflicts are resolved in IPv6.  If you set DupAddrDetectTransmits to zero on an interface where DAD is required to prevent address conflicts, then the network isn't required to work properly when you do that.  If the subscriber aggregation network by which you're connecting a mobile node to the Internet requires a DAD proxy to prevent address conflicts, and the DAD proxy is malfunctional, then you can expect damaged network service as a result.  There is nothing special about RFC 4941 temporary addresses or RFC 3972 cryptographic addresses in this regard.

Plan accordingly and stay calm.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From hanauska@equinux.de  Tue Mar 15 11:04:09 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCB393A6DD4 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 11:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=0.620,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhnfwIe22T7E for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 11:04:09 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id DE07D3A6971 for <ipv6@ietf.org>; Tue, 15 Mar 2011 11:04:08 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hfucbg0171sc for <ipv6@ietf.org>; Tue, 15 Mar 2011 17:49:15 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Tue, 15 Mar 2011 17:49:14 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id ED9F320F7F47; Tue, 15 Mar 2011 19:04:48 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <m1PzWdR-0001h0C@stereo.hq.phicoh.net>
Date: Tue, 15 Mar 2011 19:04:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B79EE39-3033-4120-AB28-6C023C089F70@equinux.de>
References: <m1PzWdR-0001h0C@stereo.hq.phicoh.net>
To: Philip Homburg <pch-6man@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103151649140089972
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 18:04:09 -0000

On 2011-03-15, at 16:58 , Philip Homburg wrote:

> I think the answer is that is statistically very unlikely that on a =
single
> subnet, a 64-bit random number will ever be equal to any address =
manually
> configured in DHCP.

I'd say this entirely depends on how the (usually pseudo-) random number =
has been created. No RFC says it is forbidden to choose a random IPv6 =
address by simply picking a number between 1-255 and pad all the bits to =
the left with zeros. It may not be very advisable to do that, but it is =
not disallowed either. If there was a rule like I suggested ("the first =
three bytes must not be zero"), such an address would be forbidden, of =
course.

> Is is far more likely that by accident to ethernet cards have the same =
MAC
> address than that a true 64-bit random number will collide with =
another number
> out of a relatively small set.

See above, choosing a "very poor" random number makes this scenario very =
likely and no RFC demands that "good" random numbers must be chosen, nor =
does any of them define what "good" means in this context. A random =
number with 3 zero bytes in a row is probably "not good", but can =
nonetheless be considered random.

How would two ethernet cards have the same MAC address, unless it has =
been manually configured? Doesn't globally unique mean "globally unique" =
anymore?

Regards,
Markus



From pch-b6B5344D9@u-1.phicoh.com  Tue Mar 15 11:26:37 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 493703A6E44 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 11:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XA-XXKqVFlfx for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 11:26:36 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id AC55A3A6D78 for <ipv6@ietf.org>; Tue, 15 Mar 2011 11:26:34 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1PzYyK-0001NyC; Tue, 15 Mar 2011 19:27 +0100
Message-Id: <m1PzYyK-0001NyC@stereo.hq.phicoh.net>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <m1PzWdR-0001h0C@stereo.hq.phicoh.net> <8B79EE39-3033-4120-AB28-6C023C089F70@equinux.de> 
In-reply-to: Your message of "Tue, 15 Mar 2011 19:04:48 +0100 ." <8B79EE39-3033-4120-AB28-6C023C089F70@equinux.de> 
Date: Tue, 15 Mar 2011 19:27:44 +0100
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 18:26:37 -0000

In your letter dated Tue, 15 Mar 2011 19:04:48 +0100 you wrote:
>On 2011-03-15, at 16:58 , Philip Homburg wrote:
>
>> I think the answer is that is statistically very unlikely that on a =
>single
>> subnet, a 64-bit random number will ever be equal to any address =
>manually
>> configured in DHCP.
>
>I'd say this entirely depends on how the (usually pseudo-) random number =
>has been created. No RFC says it is forbidden to choose a random IPv6 =
>address by simply picking a number between 1-255 and pad all the bits to =
>the left with zeros. It may not be very advisable to do that, but it is =
>not disallowed either. 

Yes, it is possible that some junior programmer doesn't know how to generate
a 64-bit random number. Hopefully people will figure out that some device is
broken in that regard and get the manufacturer to fix it.

But there is an easy fix for you. What if you put something in those
bytes? If you come up with a number that relates to just your
organisation, then it is very unlikely that a broken random number generator
will generate exactly that pattern.

If you just need stable addresses, then you can also put your own random
numbers in DHCP. 

>How would two ethernet cards have the same MAC address, unless it has =
>been manually configured? Doesn't globally unique mean "globally unique" =
>anymore?

No, it never did. That's the problem. From manufacturing defects (a batch
of cards all with the same ethernet address), small mistakes (a manufacturer
reusing a range) to companies that doen't know how it works and just use
some random vendor id, to cards that can just be jumpered to look some
other vendor's cards because that is what the software expects.


From hanauska@equinux.de  Tue Mar 15 12:11:25 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6162D3A6E53 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.186
X-Spam-Level: 
X-Spam-Status: No, score=-2.186 tagged_above=-999 required=5 tests=[AWL=0.413,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KkyR0-rt17-6 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:11:18 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id 37BFB3A6ACD for <ipv6@ietf.org>; Tue, 15 Mar 2011 12:11:16 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hfuk760171se for <ipv6@ietf.org>; Tue, 15 Mar 2011 18:56:20 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Tue, 15 Mar 2011 18:56:19 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 9866920F80F0; Tue, 15 Mar 2011 20:11:54 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>
Date: Tue, 15 Mar 2011 20:11:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103151756190090413
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 19:11:26 -0000

On 2011-03-15, at 18:28 , james woodyatt wrote:

> Were RFC 4429 and I-D.ietf-6man-dad-proxy among the documents you read =
over the weekend?

I only read the introduction and problem statement of RFC 4429 and =
neither seemed to address my concerns, thus I skipped the rest. I just =
browsed through it a bit and I still fail to see that it addresses my =
concern; the fact that it mentions that the likeliness of a collision is =
tiny in practice is certainly good, but making a tiny change to existing =
RFCs to make it impossible will always be better IMHO.

I have not heard of I-D.ietf-6man-dad-proxy so far, so I just browsed =
over this one as well, however despite the fact that it is a draft, may =
never leave draft status, may not be implemented for years even if it =
will ever leave draft status, it does not seem to address my concerns =
either, but rather a problem related to the limited propagation of DAD =
traffic (this is for sure also a problem, but not in my scenario).

Maybe I was not able to express my concerns appropriately, after all I =
tried to express them as abstract as possible. Maybe I can explain them =
better if I try to explain them by example. Let's take the LAN network =
of a tiny company, for simplicity we assume that the WLAN network and =
the LAN network are bridged to make automatic device discovery work out =
of the box. This may not be a wise setup from a security perspective but =
I have seen such a setup far too often in my life to call it =
unrealistic. In such a network we will have four kind of hosts:

1) Static servers (e.g. a DNS server, a file server, a mail server, ...) =
and comparable devices (e.g. network printers). Those devices will =
usually have a static manual assigned IP address, since this simplifies =
hardware replacement and DNS management, as you usually want to have DNS =
entries for all of these hosts.

2) Static workstations, desktop computers that are permanently connected =
to the network and never leave the building. However those hosts are not =
turned on 24 hours a day, they are only running when they are in use, so =
from a network perspective they might come and go several times a day. =
Those hosts are "well known" and thus usually shall have a well known IP =
address and a DNS entry. To simplify administration they will receive =
their addresses via DHCP, that means a specific IP address has been =
reserved for each of them within the available address pools and they =
will always receive the same IP address each time they are turned back =
on and have to renew their previous lease. This way all management =
happens within central places: the DHCP and the DNS server.

3) Mobile workstations, notebooks that can also leave the building. =
Those are exactly like hosts of type (2), they might just join and leave =
the network more often, but anything I wrote for type (2) applies to =
them as well. They are also well known and thus their addresses are =
managed via DHCP.

4) Mobile devices, e.g. mobile phones or tablet devices. These devices =
are not necessarily well known and since they usually won't offer any =
important services to other hosts, it is not necessary that they have a =
static IP address or a DNS entry. For those devices it is sufficient and =
acceptable to create addresses via stateless address configuration. Some =
of these devices may not even support DHCPv6, since DHCPv6 is not widely =
supported at the moment (so far I have not seen DHCPv6 support in any =
MacOS X version for example), while any device with IPv6 support seems =
to also support stateless auto configuration.

If we ignore the existence of the privacy extension, I claim that the =
scheme above will be collision free. Devices of type (4) can only =
collide if global unique MAC addresses are manually overwritten or a =
vendor makes a mistake and accidentally reuses MAC addresses. DHCP and =
manual addresses will be selected appropriately to avoid collisions by =
network administrators and I fail to see how stateless addresses of =
devices of type (4) should ever collide with DHCP or manual addresses, =
if those will have up to 6 zero bytes in front, which is usually what =
admins want in the first place.

However, there is no way you can prevent devices of type (4) to use the =
privacy extension for stateless configuration, which would be no concert =
in general, if those addresses could never conflict with any other =
addresses mentioned above... but they can. The address might match =
exactly one of the reserved DHCP addresses and since the device of type =
(2) or (3) - lets name it DevX - might either be turned off or otherwise =
currently not connected to the network, DAD will not show any conflict. =
When DevX comes back while the temporary address is still in use, it =
will not be able to take the address that it is supposed to have and =
that will be offered to it by DHCP (if it even will be offered at all).

If you suggest that this is no problem, after all DevX will detect the =
conflict via DAD and can simply pick another address by any other means, =
you are not solving the problem. DevX is supposed to have its reserved =
DHCP address and the DNS entry for it is supposed to point to exactly =
this device. The offending device should have never been allowed to pick =
the conflicting address in the first place. This whole situation would =
have easily been avoidable by tightening the constrains of what =
qualifies as a legal temporary IPv6 address and what not.

Further when reading your mail, I got the impression that you are trying =
to add in security aspects to the mix, but I'm really not talking about =
security aspects. That a malicious attacker might intentionally =
configure one of the DHCP addresses manually to "take the place" of a =
workstation while this workstation is being away of the network was =
never part of my concern. This is a different scenario. My mail was =
never about protecting against an attack scenario where a host "steals" =
an IP  address of another host, but only about the fact that an device =
may "accidentally" steal it, without the device or its owner ever =
intending to do so.

Regards,
Markus=

From hanauska@equinux.de  Tue Mar 15 12:26:10 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E43E63A6B25 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:26:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKoo+4AbPgdM for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:26:10 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id 872933A6C99 for <ipv6@ietf.org>; Tue, 15 Mar 2011 12:26:07 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hfulv00171sh for <ipv6@ietf.org>; Tue, 15 Mar 2011 19:11:57 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Tue, 15 Mar 2011 19:11:57 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 1D88720F8196; Tue, 15 Mar 2011 20:27:32 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <m1PzYyK-0001NyC@stereo.hq.phicoh.net>
Date: Tue, 15 Mar 2011 20:27:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <759E8F04-5899-451E-B838-F2FF35D5FB96@equinux.de>
References: <m1PzWdR-0001h0C@stereo.hq.phicoh.net> <8B79EE39-3033-4120-AB28-6C023C089F70@equinux.de> <m1PzYyK-0001NyC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-6man@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103151811570090519
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 19:26:11 -0000

On 2011-03-15, at 19:27 , Philip Homburg wrote:

> If you just need stable addresses, then you can also put your own =
random
> numbers in DHCP.=20

Of course everything will be fine if you exclusively use DHCPv6. You can =
have a pool with addresses for well known devices, so the same device =
always gets the same address from the pool, while all other devices get =
addresses from another pool that are more or less random.

However, there are devices that support IPv6 and stateless =
auto-configuration, possibly even the privacy extension, but not DHCPv6. =
And if a device supports both, there is no way to force the device to =
use DHCP; if it is "nice" it may listen to the RA managed flag, but does =
the RFC say that it must listen to this flag and that users may not =
override this flag, by configuration their device to always generate =
stateless addresses? Not as far as I can see and the meaning of this =
flag is not exactly defined (this flag does not imply DHCP, it could =
also imply a different protocol or manual configuration only) and I saw =
that even deprecation of the flag has been discussed publicly.

I just thought it would be nice if DHCP, manual configuration and =
stateless auto-configuration can always play together nicely within the =
same network, even when privacy extension is being used. Without privacy =
extension this is pretty much the case, except for MAC address conflicts =
like you mentioned previously, but when privacy extension enters the =
game (and don't get me wrong, I think privacy extension is a good thing =
and it is important that such an extension exists) this is not =
guaranteed any longer.

Regards,
Markus=

From suresh.krishnan@ericsson.com  Tue Mar 15 12:28:15 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8ACC43A6B25 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level: 
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rsU1OaRASeET for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 12:28:14 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id B313F3A6B49 for <ipv6@ietf.org>; Tue, 15 Mar 2011 12:28:14 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2FJTalT013144; Tue, 15 Mar 2011 14:29:38 -0500
Received: from [142.133.10.107] (147.117.20.213) by eusaamw0711.eamcs.ericsson.se (147.117.20.179) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 15:29:32 -0400
Message-ID: <4D7FBD7E.7010405@ericsson.com>
Date: Tue, 15 Mar 2011 15:26:54 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "Hing-Kam (Kam) Lam" <hingkam16@gmail.com>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
References: <20110314223006.15936.74266.idtracker@localhost> <AANLkTinW5DbxJvXB6i0iVDKG56CS3w=wHS+wBpR==8UO@mail.gmail.com>
In-Reply-To: <AANLkTinW5DbxJvXB6i0iVDKG56CS3w=wHS+wBpR==8UO@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 19:28:15 -0000

Hi Kam,

On 11-03-15 10:37 AM, Hing-Kam (Kam) Lam wrote:
> I am forgetting what the resolution was on the Hdr Options that were
> defined in the -01 version. I find those missing here, so i assume
> that they have been intentionally dropped out. I was personally in
> favor of those and didnt see too much harm in keeping them.

Correct. They were intentionally dropped since there was no consensus to 
keep them. I will try to summarize the current status at the Prague 
meeting and see how to proceed further.

Thanks
Suresh


From john@jlc.net  Tue Mar 15 13:14:14 2011
Return-Path: <john@jlc.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8E793A6C01 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.575
X-Spam-Level: 
X-Spam-Status: No, score=-106.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-mtTPx9reOH for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:14:14 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id D43AD3A6B77 for <ipv6@ietf.org>; Tue, 15 Mar 2011 13:14:13 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 1807733C21; Tue, 15 Mar 2011 16:15:39 -0400 (EDT)
Date: Tue, 15 Mar 2011 16:15:39 -0400
From: John Leslie <john@jlc.net>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
Message-ID: <20110315201539.GF52874@verdi>
References: <20110314223006.15936.74266.idtracker@localhost> <20110314225526.GB52874@verdi> <4D7EAF77.3080504@ericsson.com> <20110315132539.GD52874@verdi> <4D7F7073.3050009@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D7F7073.3050009@ericsson.com>
User-Agent: Mutt/1.4.1i
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 20:14:14 -0000

Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
> On 11-03-15 09:25 AM, John Leslie wrote:
>>>>
>>>> But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
>>>> the TLV format.
>>> 
>>> The T is the "Next Header", the L is the "Hdr Ext Len" and V is the 
>>> "Header Specific Data" as specified in the figure in Section 4 of the
>>> draft.
>>
>> Well, of course "Next Header" _isn't_ the Type of this option (rather
>> it's the Type of the next option).
>>
>> And the "Hdr Ext Len" isn't a particularly intuitive coding of Length
>> either...
> 
> Yep. You are right on both counts, but I am not sure how we can change 
> this. We cannot chain the headers without the T being in the *previous* 
> header. I think the best we can do is to refrain from calling this TLV 
> like you said.

   That would satisfy me...

   But, the 2460 section 4.2 TLV also defines four actions when a Type
isn't recognized (skip and three cases of discard). exthdr-02 gives
us no way of defining skip-vs-discard.

   I think some mention of this issue would be wise. It appears, at
first blush, that you intend for a middlebox to skip over these
prospective extension headers, whereas 2460 calls for dropping the
packet.

   I'm not prepared to say what the resolution may be; I just think
it deserves some text (even if only to say, "Beware!").

--
John Leslie <john@jlc.net>

From suresh.krishnan@ericsson.com  Tue Mar 15 13:24:29 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BC343A6B64 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6yh6a11u5uL0 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:24:28 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id E6DD23A6A8B for <ipv6@ietf.org>; Tue, 15 Mar 2011 13:24:27 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2FKPpPD024146; Tue, 15 Mar 2011 15:25:53 -0500
Received: from [142.133.10.107] (147.117.20.213) by eusaamw0707.eamcs.ericsson.se (147.117.20.92) with Microsoft SMTP Server id 8.2.234.1; Tue, 15 Mar 2011 16:25:45 -0400
Message-ID: <4D7FCAAB.7070608@ericsson.com>
Date: Tue, 15 Mar 2011 16:23:07 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: I-D Action:draft-ietf-6man-exthdr-02.txt
References: <20110314223006.15936.74266.idtracker@localhost> <20110314225526.GB52874@verdi> <4D7EAF77.3080504@ericsson.com> <20110315132539.GD52874@verdi> <4D7F7073.3050009@ericsson.com> <20110315201539.GF52874@verdi>
In-Reply-To: <20110315201539.GF52874@verdi>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 20:24:29 -0000

Hi John,

On 11-03-15 04:15 PM, John Leslie wrote:
> Suresh Krishnan <suresh.krishnan@ericsson.com> wrote:
>> On 11-03-15 09:25 AM, John Leslie wrote:
>>>>> But I don't see the equivalent of Section 4.2 of RFC 2460, specifying
>>>>> the TLV format.
>>>> The T is the "Next Header", the L is the "Hdr Ext Len" and V is the 
>>>> "Header Specific Data" as specified in the figure in Section 4 of the
>>>> draft.
>>> Well, of course "Next Header" _isn't_ the Type of this option (rather
>>> it's the Type of the next option).
>>>
>>> And the "Hdr Ext Len" isn't a particularly intuitive coding of Length
>>> either...
>> Yep. You are right on both counts, but I am not sure how we can change 
>> this. We cannot chain the headers without the T being in the *previous* 
>> header. I think the best we can do is to refrain from calling this TLV 
>> like you said.
> 
>    That would satisfy me...
> 
>    But, the 2460 section 4.2 TLV also defines four actions when a Type
> isn't recognized (skip and three cases of discard). exthdr-02 gives
> us no way of defining skip-vs-discard.
> 
>    I think some mention of this issue would be wise. It appears, at
> first blush, that you intend for a middlebox to skip over these
> prospective extension headers, whereas 2460 calls for dropping the
> packet.

Right. These behavior flags were added in version -01 of the draft (the 
previous version) due to a apparent consensus at the physical wg meeting 
but this change has been rolled back in version -02 due to lack of 
consensus in the mailing list.

> 
>    I'm not prepared to say what the resolution may be; I just think
> it deserves some text (even if only to say, "Beware!").

Let's see if we can make some progress at the next meeting.

Thanks
Suresh


From jhw@apple.com  Tue Mar 15 13:34:30 2011
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30A123A6976 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.552
X-Spam-Level: 
X-Spam-Status: No, score=-106.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yR72Q6LsB0-a for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 13:34:29 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 6FE0E3A6808 for <ipv6@ietf.org>; Tue, 15 Mar 2011 13:34:29 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out3.apple.com (Postfix) with ESMTP id 22F66D6FC28C for <ipv6@ietf.org>; Tue, 15 Mar 2011 13:35:55 -0700 (PDT)
X-AuditID: 11807136-b7c6bae000004a34-c1-4d7fcdaaa493
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay15.apple.com (Apple SCV relay) with SMTP id 68.75.18996.AADCF7D4; Tue, 15 Mar 2011 13:35:55 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.193.13.64] by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LI4009W397UMI50@elliott.apple.com> for ipv6@ietf.org; Tue, 15 Mar 2011 13:35:54 -0700 (PDT)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
From: james woodyatt <jhw@apple.com>
In-reply-to: <E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de>
Date: Tue, 15 Mar 2011 13:35:54 -0700
Message-id: <35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com> <E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de>
To: Markus Hanauska <hanauska@equinux.de>
X-Mailer: Apple Mail (2.1084)
X-Brightmail-Tracker: AAAAAA==
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 20:34:30 -0000

On Mar 15, 2011, at 12:11 , Markus Hanauska wrote:
> 
> [...] but making a tiny change to existing RFCs to make it impossible will always be better IMHO

Let me try again... there is no "tiny change" to existing RFCs that can make it *impossible* for address conflicts to arise.  The best we can do is to reduce the probability of address conflicts from arising inadvertently under normal usage scenarios.

You seem to think that by reserving certain IID patterns for use with different address configuration schemes, we could have more than *optimism* that DAD will succeed, c.f. RFC 4429, that we could be *certain*.  No such determinism is possible.  EUI-48 and EUI-64 addresses with global uniqueness flags are not always globally unique because factories make errors.  Cryptographic and privacy addresses can collide in rare circumstances.  Most importantly, because it's the most frequent cause of error, manual configuration procedures are-- sing it with me-- prone to manual error, including but not limited to humans inappropriately loading addresses that conflict with otherwise automatically configured addresses on the network.

No certainty is possible.  Duplicate Address Detection (DAD) is your last best hope for civilization.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From brian.e.carpenter@gmail.com  Tue Mar 15 15:15:42 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF9B83A6BD3 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.457
X-Spam-Level: 
X-Spam-Status: No, score=-103.457 tagged_above=-999 required=5 tests=[AWL=0.142, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0JtjApSjU3D for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:15:42 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B50763A6BC6 for <ipv6@ietf.org>; Tue, 15 Mar 2011 15:15:41 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1150945fxm.31 for <ipv6@ietf.org>; Tue, 15 Mar 2011 15:17:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UpjBIqvd9uDwtUnIb7Cshso1U8xcSjsqziOZ9VLrQsI=; b=u5/uffwKb2lGzLruKSNWfixBlaH4FVQsW6Twk0JSn3ot1dFk2VqKDhVZELsuBjqC0D s29Lf9VLZ55YDq+D/32f7fubnnRHNt7LLwp8W1LuOuArii5dWWarxCRDGi3MNONJW8Bt Tu/kxk4dGan4DdDVOrOZms68+ZO14ALy53yXA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=XvVOaN8DZzdZvBo9VDxGg/Jr9VKm3/D7lSSLQoM29fZHYsWLxZoMkU9xnd1LdsUYUH o1j4q0H1r+zEXgupbTqj5Jo71rz9Cbc22Nydf3xG2+cslXI7b0lyvwL9yyf6vvRYSM8y 7QXiZU0OZykG0bKsV70OF+TkqdkXhunPlJ41s=
Received: by 10.223.15.141 with SMTP id k13mr77041faa.30.1300227426462; Tue, 15 Mar 2011 15:17:06 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id 17sm162578far.19.2011.03.15.15.17.02 (version=SSLv3 cipher=OTHER); Tue, 15 Mar 2011 15:17:05 -0700 (PDT)
Message-ID: <4D7FE55B.7050207@gmail.com>
Date: Wed, 16 Mar 2011 11:16:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar>
In-Reply-To: <4D7F539E.7030308@gont.com.ar>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 22:15:42 -0000

Fernando,

On 2011-03-16 00:55, Fernando Gont wrote:
> On 09/03/2011 05:49 p.m., Mark Smith wrote:
>> I agree. I sort of accept that an ISP can know my addresses in use, in
>> part because they gave them to me. However, for an ISP to not let me
>> choose if I want to use privacy addresses on the Internet would
>> be completely unacceptable.
> 
> Why would you find it acceptable to have the ISP assign you the complete
> address e.g. with DHCP, then?

In the context of a user requiring privacy protection, it isn't acceptable.
As far as I know, what the ISP will assign is a prefix; the individual
host addresses are locally assigned by the CPE.

Thus, in an Internet cafe, a user using privacy addresses can be traced
to the cafe but no further, even if the cafe is also using DHCP to
assign addresses.

This is also why we accept the negligible risk of address collisions
referred to in another thread.

   Brian

From brian.e.carpenter@gmail.com  Tue Mar 15 15:53:13 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C38413A6BD8 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.458
X-Spam-Level: 
X-Spam-Status: No, score=-103.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8V-5ZBkjK+B for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:53:12 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 621D33A6A4B for <ipv6@ietf.org>; Tue, 15 Mar 2011 15:53:12 -0700 (PDT)
Received: by vws12 with SMTP id 12so1268706vws.31 for <ipv6@ietf.org>; Tue, 15 Mar 2011 15:54:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KcX43lnuAiVDD1ti5nxW4BZG4IopxLhUFRHXxoYeipI=; b=lBCQvps/25WI3M6KDm5NLtAT2z20imM/OLNdGtuI5fbVQiIgJ6K9OL/yUgCBpV+9x/ ByxX9Lmevu7HgbSFocoRSttFaWzF75fgGs7jVfiMejzadTBWh2qS9g+QnEe0BE0qqdAN wym7Sld1jxKqEdK1PuqBEkwfSlICUySdFryTY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=dDMI3Ns23lShUDnkNfNdZDgPlDxXmwQD+iyZBCkBeDQ+gA+FRNEbU3ZFAKixiL1hT/ 1CK9INZvPQvnKmDtCj5dHRhSQ0X9ZQJtE0heJMPqgsuwFnN5hkj/zxb6vkPxL/ijM3aE 55HBqWInL+j8zJGcNGAdIO07iTybExnr4bXTI=
Received: by 10.52.97.228 with SMTP id ed4mr13475vdb.180.1300229677554; Tue, 15 Mar 2011 15:54:37 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id dm14sm142366vdb.17.2011.03.15.15.54.33 (version=SSLv3 cipher=OTHER); Tue, 15 Mar 2011 15:54:37 -0700 (PDT)
Message-ID: <4D7FEE26.9060502@gmail.com>
Date: Wed, 16 Mar 2011 11:54:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de> <35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com>
In-Reply-To: <35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 22:53:13 -0000

On 2011-03-16 09:35, james woodyatt wrote:
...
> No certainty is possible.  Duplicate Address Detection (DAD) is your last best hope for civilization.

If you'll excuse an anecdote, while I was living in Geneva I was regularly
amused when the shiny new information screens in the shiny new buses
would display the Windows IPv4 duplicate address warning instead of
the next bus stop. Even so, the Geneva bus service hasn't come to an end.

My point? The probability of a duplicate address in an IPv6 subnet is
many orders of magnitude less than it is in IPv4. Like 1 in 2^63
instead of 1 in 2^8.

This is just too remote a probability to worry about.

   Brian

From pch-b6B5344D9@u-1.phicoh.com  Tue Mar 15 15:59:40 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 545C43A6EF8 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OeoI0WZM3sd for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 15:59:38 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id C2B6C3A6EFA for <ipv6@ietf.org>; Tue, 15 Mar 2011 15:59:36 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1PzdEY-0001NyC; Wed, 16 Mar 2011 00:00 +0100
Message-Id: <m1PzdEY-0001NyC@stereo.hq.phicoh.net>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <m1PzWdR-0001h0C@stereo.hq.phicoh.net> <8B79EE39-3033-4120-AB28-6C023C089F70@equinux.de> <m1PzYyK-0001NyC@stereo.hq.phicoh.net> <759E8F04-5899-451E-B838-F2FF35D5FB96@equinux.de> 
In-reply-to: Your message of "Tue, 15 Mar 2011 20:27:32 +0100 ." <759E8F04-5899-451E-B838-F2FF35D5FB96@equinux.de> 
Date: Wed, 16 Mar 2011 00:00:53 +0100
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 15 Mar 2011 22:59:40 -0000

In your letter dated Tue, 15 Mar 2011 20:27:32 +0100 you wrote:
>
>On 2011-03-15, at 19:27 , Philip Homburg wrote:
>
>> If you just need stable addresses, then you can also put your own =
>random
>> numbers in DHCP.=20
>
>I just thought it would be nice if DHCP, manual configuration and =
>stateless auto-configuration can always play together nicely within the =
>same network, even when privacy extension is being used. Without privacy =
>extension this is pretty much the case, except for MAC address conflicts =
>like you mentioned previously, but when privacy extension enters the =
>game (and don't get me wrong, I think privacy extension is a good thing =
>and it is important that such an extension exists) this is not =
>guaranteed any longer.

What I was trying to say in the above quote is this: if you assign an
interface identifier to a host like this: ::0CB5:C04C:F5FD:DCCA then
there is no way that broken random number generator in a host will ever 
come up with that same value.
 
So just put those random numbers in DHCPv6, forward and reverse DNS, etc.

It doesn't really matter if a host uses both automatic configuration and
DHCP. It just means that it has more IPv6 addresses, which no problem. And
that reverse DNS may not work. Which may or may not be a problem.



From fernando.gont.netbook.win@gmail.com  Tue Mar 15 18:44:56 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B5413A6B1F for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 18:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOdmPXoVEZhe for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 18:44:55 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 0F4923A6A7E for <ipv6@ietf.org>; Tue, 15 Mar 2011 18:44:54 -0700 (PDT)
Received: by wwk4 with SMTP id 4so3596420wwk.1 for <ipv6@ietf.org>; Tue, 15 Mar 2011 18:46:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=d9vUMuJDEil5MkOzOPsjQa7QPYnxQW0Fj6BqHvel3Ec=; b=NLu+QVqVKoWl4F2mUBUDxTCyMbc7ASJlAyGawQA0g7BWDLKey2DfZ2jGPFEB6/jK9L qQ4wOR9QIB/CnUSgooDL0A9SqKkB7D4qBRdETR+lHnulGVzzDG0yhO0Su5cF5oGnrAUM KU2YoBxpCNvoxlIW693LqzbW2x53Fl9EjyRU0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=TNas70pab6M8tSBEVpsqSLe/vycNC3JKRLnqJqYh4x4mWvh8tLJZikej7pxggZ7p+n 8YgEOxIkR/gtcVig3fA8e1l9TeVtLNxWkkrmsqX9gwVgwjJ3qULRPkUH84rDIZQpDg1M AmRPjym3ezHZ7LyM01/24AWcPplgjuXoUk8Zo=
Received: by 10.216.254.39 with SMTP id g39mr138969wes.108.1300239980175; Tue, 15 Mar 2011 18:46:20 -0700 (PDT)
Received: from [192.168.200.34] ([194.2.150.133]) by mx.google.com with ESMTPS id g32sm267545wej.3.2011.03.15.18.46.18 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Mar 2011 18:46:19 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D80166A.9060502@gont.com.ar>
Date: Tue, 15 Mar 2011 22:46:18 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com>
In-Reply-To: <4D7FE55B.7050207@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 01:44:56 -0000

Hi, Brian,

On 15/03/2011 07:16 p.m., Brian E Carpenter wrote:
>>> I agree. I sort of accept that an ISP can know my addresses in use, in
>>> part because they gave them to me. However, for an ISP to not let me
>>> choose if I want to use privacy addresses on the Internet would
>>> be completely unacceptable.
>>
>> Why would you find it acceptable to have the ISP assign you the complete
>> address e.g. with DHCP, then?
> 
> In the context of a user requiring privacy protection, it isn't acceptable.

Then what's all this controversy with
draft-gont-6man-managing-privacy-extensions? :-) -- That aside, there
have been quite a few publications asessing the real "privacy" provided
with the so-called privacy-extensions....


> As far as I know, what the ISP will assign is a prefix; the individual
> host addresses are locally assigned by the CPE.

Yep, sorry. I meant "CPE", not "ISP".


> Thus, in an Internet cafe, a user using privacy addresses can be traced
> to the cafe but no further, even if the cafe is also using DHCP to
> assign addresses.

If your threat model is that the CPE is maliciously recommending hosts
not to use privacy addresses, the CPE might as well claim that DHCP is
needed, and assign to each host an IPv6 address that is based on the
EUI-64 of that host...

P.S.: Bottom-line is: This is about improving the manageability of the
address generation policy. Thus, even if different systems have
different defaults, a router can provide advice such that they all
employ the same address generation policy (whether EUI-64, privacy
addresses, or whatever).

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From huitema@microsoft.com  Tue Mar 15 23:29:23 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E99203A67DB for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 23:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.574
X-Spam-Level: 
X-Spam-Status: No, score=-10.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 93kcjrmwupg7 for <ipv6@core3.amsl.com>; Tue, 15 Mar 2011 23:29:23 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 1AD1F3A67E5 for <ipv6@ietf.org>; Tue, 15 Mar 2011 23:29:23 -0700 (PDT)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 15 Mar 2011 23:30:47 -0700
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server (TLS) id 14.1.270.2; Tue, 15 Mar 2011 23:30:47 -0700
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.56]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi id 14.01.0270.002; Tue, 15 Mar 2011 23:30:47 -0700
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fernando@gont.com.ar>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Topic: draft-gont-6man-managing-privacy-extensions-00.txt
Thread-Index: AQHL3kEKAbTYw5EzSU+RGMZ29OXheJQlYKSAgAB+ZoCAACGDgIAIx/UAgACtu4CAADp8AP//2TmQ
Date: Wed, 16 Mar 2011 06:30:46 +0000
Message-ID: <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>	<20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar>
In-Reply-To: <4D80166A.9060502@gont.com.ar>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.123.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 06:29:24 -0000

> Then what's all this controversy with draft-gont-6man-managing-privacy-ex=
tensions? :-) -- That aside, there have been quite a few publications asess=
ing the real "privacy" provided with the so-called privacy-extensions....

Using randomized host identifiers is way more private than sticking a MAC a=
ddress in the IPv6 address. In fact, rather than your draft proposing to no=
t use privacy addresses, we should pursue the deprecation of using EUI-64 i=
n addresses.

The worst part of your draft is that , if we published it, it would give th=
e impression that for the IETF, EUI-64 addresses are more secure than priva=
cy addresses. This is obviously false.

-- Christian Huitema




From sthaug@nethelp.no  Wed Mar 16 00:33:26 2011
Return-Path: <sthaug@nethelp.no>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D930E3A6822 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 00:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.312
X-Spam-Level: 
X-Spam-Status: No, score=-6.312 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqUhcKqIn2bL for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 00:33:25 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 6C62E3A6820 for <ipv6@ietf.org>; Wed, 16 Mar 2011 00:33:24 -0700 (PDT)
Received: (qmail 14514 invoked from network); 16 Mar 2011 07:34:47 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 16 Mar 2011 07:34:47 -0000
Date: Wed, 16 Mar 2011 08:34:47 +0100 (CET)
Message-Id: <20110316.083447.74736630.sthaug@nethelp.no>
To: brian.e.carpenter@gmail.com
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
From: sthaug@nethelp.no
In-Reply-To: <4D7FE55B.7050207@gmail.com>
References: <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com>
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
Cc: ipv6@ietf.org, ran.atkinson@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 07:33:27 -0000

> > Why would you find it acceptable to have the ISP assign you the complete
> > address e.g. with DHCP, then?
> 
> In the context of a user requiring privacy protection, it isn't acceptable.
> As far as I know, what the ISP will assign is a prefix; the individual
> host addresses are locally assigned by the CPE.

Or the host could be connected to a bridge, and assigned a /128 using
DHCPv6 IA_NA (RFC 3315).

As an ISP: I would *prefer* to require each customer to have a router,
and assign a /56 using DHCPv6 IA_PD. However, the reality is that many
customers today are using a PC behind a bridge, and such customers
would then be assigned a /128.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From mohacsi@niif.hu  Wed Mar 16 02:07:07 2011
Return-Path: <mohacsi@niif.hu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5FFA3A68B3 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 02:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.052
X-Spam-Level: 
X-Spam-Status: No, score=0.052 tagged_above=-999 required=5 tests=[AWL=0.056,  BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fWqonZODLzEk for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 02:07:06 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by core3.amsl.com (Postfix) with ESMTP id 160C63A68BE for <ipv6@ietf.org>; Wed, 16 Mar 2011 02:07:06 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id 0887B86D75; Wed, 16 Mar 2011 10:08:31 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id eQ2vaLt65RSh; Wed, 16 Mar 2011 10:08:15 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id AB4F186D60; Wed, 16 Mar 2011 10:08:09 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id A751686D55; Wed, 16 Mar 2011 10:08:09 +0100 (CET)
Date: Wed, 16 Mar 2011 10:08:09 +0100 (CET)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way,	that it might cause address conflicts?
In-Reply-To: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>
Message-ID: <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 09:07:07 -0000

On Mon, 14 Mar 2011, Markus Hanauska wrote:

> Since IPv6 plays an increasingly prominent role in planing network environments, I spent most of the weekend to think about IPv6 distribution strategies for our company and my home Internet connection, re-reading most of the important RFCs and I came across a serious address deployment issue that seems to not be addressed by any of them. I searched the Internet, since I could not believe nobody every came across that issue, but after reading over 100 web pages and over 50 papers regarding IPv6 address deployment, this issue either has not been discovered up to now or has been intentionally ignored. I must admit, the issue is highly unlikely to ever cause a problem in real life scenarios, but as a programmer there is a huge difference between "impossible" and "highly unlikely", and I definitely prefer "impossible".
>
> B) DHCPv6 according to RFC 3315 - either randomly distribute addresses from available pools or possibly even reserve certain addresses for certain hosts by MAC address.
>
> C) Stateless Address Autoconfiguration according to RFC 4862 - currently the auto configuration scheme supported by most operating systems and devices. This major case has four important major sub-cases that people tend to ignore in general (there are some more minor sub-cases, but I'd like to ignore those here as well):
>
> 	C1) Device has a globally unique EU-/MAC-48 identifier
> 	C2) Device has NO globally unique EU-/MAC-48 identifier, but one manually assigned by a network admin
> 	C3) Device has a globally unique EU-64 identifier
> 	C4) Device has no globally unique EU-64 identifier, but one manually assigned by a network admin
>
> D) Stateless Address Autoconfiguration with Privacy Extension according to RFC 4941

I think D) is still C) but IID is generated randomly.

>
> Mixing (A) and (B) shouldn't be a problem, just like in case of IPv4 
> admins only have to make sure that the manual addresses never overlap 
> any DHCP address pool; this should be easily enforceable. E.g. reserve 
> <prefix>::1 to <prefix>::FF (sorry for using upper case hex, it just 
> reads better on my screen) for manual assignment (254 addresses) and 
> <prefix>::100 to <prefix>::FF:FFFF as DHCP pool (over 16 mio DHCP 
> addresses).

This assignment is overly restictive.

>
> What most people tend to ignore are the cases (C2) and (C4), where the 
> "u" bit will not be set after inverting it and those cases are not plain 
> hypothetical, I have seen them in real-life more than once.

Can you desctibe the environment you encountered such a setup?

> There exists 
> still no problem in case of (C2), since FFFE will be added to the 
> address and network admins are thus advised to not choose manual and 
> DHCP address ranges in such a way, that they might ever have FFFE at the 
> same position.

In DHCP address assignment you should not use range with u bit 1.

>
> So far all these standards peacefully coexist with each other... 
> however, case (D) does not. Case (D) can conflict with all other cases, 
> except the cases (C1) and (C3). And that even though a tiny modification 
> of RFC 4941 could entirely avoid this issue. A modification that would 
> lead to maybe four lines of code in most IPv6 implementations out there. 
> All that was necessary was adding the rule, that those random addresses 
> must never start with three zero bytes and the address generation 
> process must be repeated if such an address is generated on the first 
> attempt. I must admit, an MD5 hash where the first three byte are all 
> zero is rather unlikely but it is not impossible; unless someone can 
> prove to me mathematically, that given the possible input data, such an 
> outcome is absolutely impossible. However, bear in mind that the RFC 
> does not require the usage of MD5, it only suggests it and even if it is 
> impossible for MD5, who can guarantee it will be impossible for all 
> other e xisting hash functions in the world that will ever be used for 
> IPv6 address generation? I don't think I have to explain here how case 
> (D) can conflict with all the other cases, since the address is 
> unpredictable, any result is possible. And bear in mind, that other RFCs 
> even mention cases where a device might create its 64 bit host ID 
> entirely "random"; which is even worse than using a hash function.

You ususally add privacy enhanced addresses next to other addresses. The 
other addresses still exist in case of Duplicate Addrees scenario.

>
> I know what people will probably reply up to this point: No conflict can 
> ever arise, duplicate address detection (DAD) is going to prevent that. 
> And here is my reply: How is DAD preventing this problem if the device 
> with the conflicting address in question is not connected to the network 
> the moment DAD is performed? E.g. the address of type (D) conflicts with 
> a DHCP address (very unlikely, but possible), a DHCP address that has 
> been reserved for a certain mobile device, which currently is not 
> connected to the network. DAD will not see any conflict and assign the 
> IP to some other device. If now the mobile device is added to the 
> network, it cannot obtain its reserved DHCP address. Of course the same 
> is true for server with an manually assigned IP address that is only 
> turned on at certain times of the day for example. And the same problem 
> arises for a mobile device with a manual assigned interface ID as in 
> cases (C2) or (C4).



Yes. DAD can fail, and you system log you will see.

Best Regards,
 		Janos Mohacsi

From hanauska@equinux.de  Wed Mar 16 02:46:51 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B1473A68F3 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 02:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXo1xYA831Tx for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 02:46:50 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id 6A9A93A68F7 for <ipv6@ietf.org>; Wed, 16 Mar 2011 02:46:50 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hg1qq20171sp for <ipv6@ietf.org>; Wed, 16 Mar 2011 09:32:02 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Wed, 16 Mar 2011 09:32:02 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 831E220F93A3; Wed, 16 Mar 2011 10:47:45 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu>
Date: Wed, 16 Mar 2011 10:47:45 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu>
To: Mohacsi Janos <mohacsi@niif.hu>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103160832020094427
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 09:46:51 -0000

On 2011-03-16, at 10:08 , Mohacsi Janos wrote:

> Yes. DAD can fail, and you system log you will see.


How will this help a network admin, when the system log says, that a =
server that is supposed to have a certain fixed IP or a DHCP client, =
that is also supposed to have a certain fixed IP (however, one assigned =
by DHCP) cannot obtain this IP, because some other host with privacy =
extension enabled is currently using this IP by plain coincident? How =
can you resolve that problem? Running around the building and asking all =
people with non-DHCP devices to please temporarily disconnect of the =
network? Assigning a different IP to the server or the DHCP device does =
not resolve the problem at all, because those are supposed to have a =
certain IP and not any IP. Assigning a different IP to the stateless =
device would work, but how can you know which of the maybe 100 stateless =
devices on the network is the device that captured the IP?

Best regards,
Markus

From sander@steffann.nl  Wed Mar 16 03:04:17 2011
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86FE93A68E8 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:04: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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8taVSZRwa4Zd for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:04:16 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by core3.amsl.com (Postfix) with ESMTP id 706DD3A68E0 for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:04:16 -0700 (PDT)
Received: from macpro.10ww.steffann.nl (unknown [IPv6:2001:610:6ce:1:224:36ff:feef:1d89]) by mail.sintact.nl (Postfix) with ESMTP id 28B2C2034; Wed, 16 Mar 2011 11:05:40 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>
Date: Wed, 16 Mar 2011 11:05:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FBAEF08B-2E46-47BD-A432-31A584E72786@steffann.nl>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>
To: Markus Hanauska <hanauska@equinux.de>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Mohacsi Janos <mohacsi@niif.hu>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:04:17 -0000

Hi,

> How will this help a network admin, when the system log says, that a =
server that is supposed to have a certain fixed IP or a DHCP client, =
that is also supposed to have a certain fixed IP (however, one assigned =
by DHCP) cannot obtain this IP, because some other host with privacy =
extension enabled is currently using this IP by plain coincident?

The chance of this happening is *very* *very* small. I would worry more =
about people choosing such an IP address intentionally to cause =
trouble...
Sander


From pch-b6B5344D9@u-1.phicoh.com  Wed Mar 16 03:26:26 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39CFE3A6917 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i34s-XmG3HqW for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:26:25 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id 6AA5D3A6912 for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:26:23 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1PznxD-0001dSC; Wed, 16 Mar 2011 11:27 +0100
Message-Id: <m1PznxD-0001dSC@stereo.hq.phicoh.net>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de> 
In-reply-to: Your message of "Wed, 16 Mar 2011 10:47:45 +0100 ." <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de> 
Date: Wed, 16 Mar 2011 11:27:29 +0100
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:26:26 -0000

In your letter dated Wed, 16 Mar 2011 10:47:45 +0100 you wrote:
>On 2011-03-16, at 10:08 , Mohacsi Janos wrote:
>
>> Yes. DAD can fail, and you system log you will see.
>
>How will this help a network admin, when the system log says, that a server th
>at is supposed to have a certain fixed IP or a DHCP client, that is also suppo
>sed to have a certain fixed IP (however, one assigned by DHCP) cannot obtain t
>his IP, because some other host with privacy extension enabled is currently us
>ing this IP by plain coincident? How can you resolve that problem? Running aro
>und the building and asking all people with non-DHCP devices to please tempora
>rily disconnect of the network? 

You look up the MAC address for that IPv6 address and then block the MAC
address on your switches. Problem solved.

You can slightly better than that. For wired connections, you can look up
to which port the offending system is connected, and with an up-to-date cable
plan you can also find it.

For wireless, you want EAP anyhow, so you can just look up which user account
was used and then contact that user.



From hanauska@equinux.de  Wed Mar 16 03:37:02 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B1213A6935 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.393
X-Spam-Level: 
X-Spam-Status: No, score=-2.393 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbiK6C-WwJhN for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:37:01 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id F20A03A690E for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:37:00 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hg20m80171s6 for <ipv6@ietf.org>; Wed, 16 Mar 2011 10:21:51 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Wed, 16 Mar 2011 10:21:51 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 7FDDE20F9535; Wed, 16 Mar 2011 11:37:35 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <FBAEF08B-2E46-47BD-A432-31A584E72786@steffann.nl>
Date: Wed, 16 Mar 2011 11:37:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E78895C-8CFC-4B4B-9882-B20C29D25E01@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de> <FBAEF08B-2E46-47BD-A432-31A584E72786@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103160921510094670
Cc: ipv6@ietf.org, Mohacsi Janos <mohacsi@niif.hu>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:37:02 -0000

On 2011-03-16, at 11:05 , Sander Steffann wrote:

> The chance of this happening is *very* *very* small.

The chances that a MD5 hash of any data will ever be exactly zero (all =
octets are zero) is ridiculous tiny. It is probably so extremely =
unlikely that the world would rather be destroyed by a meteor tomorrow =
than this is ever going to happen. Still IPv6 implementations verify =
that the output of the MD5 hash function is not exactly zero when =
creating a temporary address as suggested by RFC 4941 (I verified this =
by source code). The scenario that I described is much more likely than =
a MD5 of zero, but here no code exists to prevent it.

> I would worry more about people choosing such an IP address =
intentionally to cause trouble...

That would rather be security issue, since why would anyone do that, =
unless he's doing it by intention? And if someone does that by =
intention, he's probably planing to do something evil.

Best regards,
Markus


From mohacsi@niif.hu  Wed Mar 16 03:44:12 2011
Return-Path: <mohacsi@niif.hu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 93DAA3A693D for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.046
X-Spam-Level: 
X-Spam-Status: No, score=0.046 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gt9R4+i39sbt for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:44:12 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by core3.amsl.com (Postfix) with ESMTP id B6E3E3A693A for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:44:11 -0700 (PDT)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id 4F45A86D4B; Wed, 16 Mar 2011 11:45:37 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id fd-cycH3IYqI; Wed, 16 Mar 2011 11:45:21 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id BCEAF86D6D; Wed, 16 Mar 2011 11:45:21 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id BAA2B86D64; Wed, 16 Mar 2011 11:45:21 +0100 (CET)
Date: Wed, 16 Mar 2011 11:45:21 +0100 (CET)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way,	that it might cause address conflicts?
In-Reply-To: <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>
Message-ID: <alpine.BSF.2.00.1103161143220.87087@mignon.ki.iif.hu>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:44:12 -0000

On Wed, 16 Mar 2011, Markus Hanauska wrote:

>
> On 2011-03-16, at 10:08 , Mohacsi Janos wrote:
>
>> Yes. DAD can fail, and you system log you will see.
>
>
> How will this help a network admin, when the system log says, that a 
> server that is supposed to have a certain fixed IP or a DHCP client, 
> that is also supposed to have a certain fixed IP (however, one assigned 
> by DHCP) cannot obtain this IP, because some other host with privacy 
> extension enabled is currently using this IP by plain coincident? How 
> can you resolve that problem? Running around the building and asking all 
> people with non-DHCP devices to please temporarily disconnect of the 
> network? Assigning a different IP to the server or the DHCP device does 
> not resolve the problem at all, because those are supposed to have a 
> certain IP and not any IP. Assigning a different IP to the stateless 
> device would work, but how can you know which of the maybe 100 stateless 
> devices on the network is the device that captured the IP?

The servers are "always" working. Newcomers cannot hijack their addresses 
since DAD will fail for them....

Best Regards,
 		Janos Mohacsi


From hanauska@equinux.de  Wed Mar 16 03:47:31 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2EBAA3A68C2 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level: 
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBl2pGhFnzgf for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:47:30 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id B9F6F3A690B for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:47:29 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hg21tg0171sk for <ipv6@ietf.org>; Wed, 16 Mar 2011 10:33:11 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Wed, 16 Mar 2011 10:33:11 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 9E0EE20F9590; Wed, 16 Mar 2011 11:48:55 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com>
Date: Wed, 16 Mar 2011 11:48:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <61640AE3-C0A9-4693-B3A6-4E675E15123C@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com> <E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de> <35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103160933110094729
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:47:31 -0000

On 2011-03-15, at 21:35 , james woodyatt wrote:

> Let me try again... there is no "tiny change" to existing RFCs that =
can make it *impossible* for address conflicts to arise.

This seems an rather odd reasoning to me; it's like saying "An =
algorithm, that solves only one specific problem, is bad because the =
world is full of so many other problems it doesn't solve". I'm not in =
particular worried about conflicts between two devices that use both =
some kind of stateless address configuration (by interface ID, privacy =
extension, or both), since those devices will only create stateless =
addresses while they are connected to the network and thus DAD will work =
to detect those conflicts and devices are able to do whatever they wish =
to resolve them; e.g. just picking another random address. Since it =
doesn't really matter for stateless devices which IP they'll have, =
picking one IP seems as good as picking any other IP IMO. My main =
concern always has been that stateless devices might conflict with IP =
ranges that are reserved by the network admin for DHCP clients and =
manually configured servers. And to avoid this scenario, a single =
sentence and at most 4 lines of code in implementations would be enough =
already. I cannot understand what would be so bad about limiting the =
address range of the privacy extension in such a way, that a *tiny* =
fraction of it is reserved to create a "safety-zone" which admins can =
use for static or DHCP pool addresses. After all RFC 4941 already does =
that:

"Compare the generated identifier against a list of reserved interface =
identifiers [...]"
	- RFC 4941 - 3.2.1

And as an example the reserved anycast addresses of RFC 2526 are =
explicitly mentioned. All that I was asking was why such a reserved =
address range has not been created for admins that need static addresses =
on the network (manually assigned or assigned by DHCPv6), however, the =
devices that will use them are not permanently connected to the network =
and thus DAD will simply *not work*. DAD can only prevent that there =
will ever be an address conflict, but it does not prevent a device from =
*accidentally* picking an address (and that is important, I'm not =
worried about intentionally picking one) that has been reserved for =
another device currently not connected to the network. It's great that I =
will get informed when such a conflict arises, but how should I resolve =
it? Assigning a different static IP to the device (again, manually or by =
DHCP) resolves the IP address conflict, but may still prevent proper =
operation of the network, since now the server or other device in =
question won't have the IP it is supposed to have and other devices may =
rely on that IP.

For EUI/MAC-48 such a safety zone exists implicitly, for EUI-64 =
addresses it only exists if the u bit is set (and is not set for the =
static or DHCP addresses), but that should almost always be the case; =
despite that this won't be an issue on most networks as long as network =
ethernet network adapters have 48-bit addresses and in networks where =
EUI-64 is already in use today neither DHCP nor manual assigned =
addresses are in use.

> EUI-48 and EUI-64 addresses with global uniqueness flags are not =
always globally unique because factories make errors.

Yes, I got that point, but this is nothing I'm worried about. These are =
conflicts that will prevent one device joining the network because =
another device with the same EUI is already on the network; an in that =
case assigning a different IP also won't resolve the conflict, since the =
devices would still conflict on layer 2, which is probably even worse =
than a conflict on layer 3. The tiny change I suggested would not solve =
this problem, well, but it will still solve the problem I'm worried =
about.

> manual configuration procedures are-- sing it with me-- prone to =
manual error

Yes, it certainly is. If I mess up the manual configuration, it's my =
fault and there is nobody to blame but myself. And it will also be me =
who has to fix the mess. However, if standards, that are supposed to =
cooperate and automatically work on my behalf, mess up the =
configuration, who can I blame then and who is going to fix it? Further =
saying "Don't do something that can go wrong if you make a mistake" =
seems another odd reasoning, since pretty much everything you do can go =
wrong if you make mistakes and by that reasoning I better stop touching =
my computer right away.

Best regards,
Markus=

From hanauska@equinux.de  Wed Mar 16 03:50:33 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE1B73A6951 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V+Lm08oL-k9L for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 03:50:33 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id 122DB3A6952 for <ipv6@ietf.org>; Wed, 16 Mar 2011 03:50:33 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hg228u0171sc for <ipv6@ietf.org>; Wed, 16 Mar 2011 10:36:15 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Wed, 16 Mar 2011 10:36:15 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id 00F7520F95AC; Wed, 16 Mar 2011 11:51:59 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <alpine.BSF.2.00.1103161143220.87087@mignon.ki.iif.hu>
Date: Wed, 16 Mar 2011 11:51:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0F71DA0-7295-4EF7-B577-313FA1EC9C58@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de> <alpine.BSF.2.00.1103161143220.87087@mignon.ki.iif.hu>
To: Mohacsi Janos <mohacsi@niif.hu>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103160936150094752
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 10:50:34 -0000

On 2011-03-16, at 11:45 , Mohacsi Janos wrote:

> The servers are "always" working. Newcomers cannot hijack their =
addresses since DAD will fail for them....


Maybe on your network, but on our network some servers are only working =
at certain office times or when they are needed. Some "servers" are no =
servers in the classical sense, they are servers by "software" (they =
offer a certain service via a well know protocol at a well known port), =
not by "hardware" (they might not even be computers in the classical =
sense).

Best regards,
Markus=

From hanauska@equinux.de  Wed Mar 16 04:05:11 2011
Return-Path: <hanauska@equinux.de>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFB3A3A6959 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 04:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level: 
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nfu4vbQCUQ7u for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 04:05:11 -0700 (PDT)
Received: from mail.equinux.net (mail.equinux.net [194.145.236.10]) by core3.amsl.com (Postfix) with ESMTP id D55EA3A6949 for <ipv6@ietf.org>; Wed, 16 Mar 2011 04:05:10 -0700 (PDT)
Received: from mail.equinux.net (127.0.0.1) by mail.equinux.net (MlfMTA v3.2r9) id hg23vq0171su for <ipv6@ietf.org>; Wed, 16 Mar 2011 10:50:52 +0100 (envelope-from <hanauska@equinux.de>)
Received: from mail.muc.equinux.net ([192.168.40.207]) by mail.equinux.net (equinux Secure Mail Relay) with ESMTP; Wed, 16 Mar 2011 10:50:52 +0100
Received: from anaheim.muc.equinux.net (anaheim.muc.equinux.net [192.168.40.40]) by mail.muc.equinux.net (Postfix) with ESMTPS id C4D1F20F960B; Wed, 16 Mar 2011 12:06:36 +0100 (CET)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Markus Hanauska <hanauska@equinux.de>
In-Reply-To: <m1PznxD-0001dSC@stereo.hq.phicoh.net>
Date: Wed, 16 Mar 2011 12:06:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F83685EF-959F-488B-B4E8-FD41712F9BA6@equinux.de>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu> <3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de> <m1PznxD-0001dSC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-6man@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1082)
X-Mlf-Version: 7.2.1.2841
X-Mlf-UniqueId: o201103160950520094819
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 11:05:12 -0000

On 2011-03-16, at 11:27 , Philip Homburg wrote:

> You look up the MAC address for that IPv6 address and then block the =
MAC
> address on your switches. Problem solved.

Sure, that will work. However, that means I have to invest time and work =
to solve a problem, that would have easily been avoidable by a tiny =
standard change and that did not arise because anyone made a mistake, it =
just has been recklessly accepted by the standard creators, because it =
seemed unlikely. And this is a lot of work, since I cannot block it =
globally, but I have to work my way through all our managed switches and =
I will get a problem on some parts of the network, where unmanaged =
switches are used, which I might have to reboot after blocking to flush =
their address cache.

> You can slightly better than that. For wired connections, you can look =
up
> to which port the offending system is connected, and with an =
up-to-date cable
> plan you can also find it.

Still I have to work my way through all managed switches and if =
connected to an unmanaged switch, I can only take down the switch at a =
whole.

At the moment, I'm rather considering to choose a smaller address prefix =
than /64 for the network, which will disable stateless addresses =
entirely (even on devices that don't listen to the A flag in RA =
messages) and only use DHCPv6 which solves all my worries. Of course =
that means only Windows and Linux hosts can be added to the network for =
the time being since MacOS X has no DHCPv6 support, so bad luck for =
those. If all DHCPv6 clients support obtaining two IPs via DHCP, one =
"normal" IP and one temporary, to avoid that they are traceable from =
outside is questionable, but I'm investigating to solve this issue by =
having the border router perform random IPv6 NATing for the LAN, where =
for every internal address a random external address is being created =
and used whenever packets leave our network.

Best regards,
Markus=

From fernando.gont.netbook.win@gmail.com  Wed Mar 16 05:31:10 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E81B93A691A for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcNGy-dugacU for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:30:59 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id D39153A68EA for <ipv6@ietf.org>; Wed, 16 Mar 2011 05:30:56 -0700 (PDT)
Received: by bwz13 with SMTP id 13so1611366bwz.31 for <ipv6@ietf.org>; Wed, 16 Mar 2011 05:32:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=RWJVtbzv+gPZhy51ffbH+NVgaH3xbtvV90TBjweB/Nw=; b=plMpDOBIy6hchPzCV2fCL4PlR6Yb9lyjc9syEDqiH6iXTotPz8QadXsQm+FOtZc2D1 3IPFpJNSlkiEV5MowQjb0iM6vFqnRRhPeoIfie9CjyWgtUP03jyX2u7kH6ENOdNL34GA VR1vawLUJZXX55jPiLZoRswkE8BAKc3WTGlcE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hvcmpDty9AyS20NNYKqQj6pKKfjLVHp2TtCxtCVIVgnv6U8bjh36uhIopCG7etDArs Ek6zRAHwgHBxrQBqF0GbrCV95vXhQ5J2Cb01lDoyoQ7JFiLA85v4l+P5Wjc/t/A3aBFi bNDkLh1xUPJVtHorfWLHlWxDm7/qJ53lo6WSw=
Received: by 10.204.82.143 with SMTP id b15mr687845bkl.118.1300278741953; Wed, 16 Mar 2011 05:32:21 -0700 (PDT)
Received: from [192.168.200.34] ([194.2.150.133]) by mx.google.com with ESMTPS id l3sm1630555fan.2.2011.03.16.05.32.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Mar 2011 05:32:17 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D80ADCF.7060409@gont.com.ar>
Date: Wed, 16 Mar 2011 09:32:15 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<20110310071925.309d467b@opy.nosense.org>	<4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 12:31:10 -0000

On 16/03/2011 03:30 a.m., Christian Huitema wrote:
>> Then what's all this controversy with
>> draft-gont-6man-managing-privacy-extensions? :-) -- That aside,
>> there have been quite a few publications asessing the real
>> "privacy" provided with the so-called privacy-extensions....
> 
> Using randomized host identifiers is way more private than sticking a
> MAC address in the IPv6 address. 

Agreed. Also in some scenarios privacy extensions may give a false sense
of privacy (see e.g. some of the pointers in our I-D).


> In fact, rather than your draft
> proposing to not use privacy addresses, we should pursue the
> deprecation of using EUI-64 in addresses.

Our draft is not meant to propose "not to use privacy addresses" -- as
noted a few times, already, the proposed mechanism could be used to turn
"privacy addresses" on for some systems that have decided not to enable
them by default (e.g., FreeBSD).

I realize that the case is made only for those scenarios in which an
admin might want to disable privacy addresses, though.


> The worst part of your draft is that , if we published it, it would
> give the impression that for the IETF, EUI-64 addresses are more
> secure than privacy addresses. This is obviously false.

We didn't argue that "privacy addresses" should be off by default.
Actually, I'd probably argue the opposite: for the general case they
should probably be "on"... but the admins should have the means to
manage how address are selected (whether privacy addresses, EUI-64, or
anything else).

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From mohacsi@niif.hu  Wed Mar 16 05:46:57 2011
Return-Path: <mohacsi@niif.hu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77A6B3A6911 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.041
X-Spam-Level: 
X-Spam-Status: No, score=0.041 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNkHluShReut for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 05:46:56 -0700 (PDT)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by core3.amsl.com (Postfix) with ESMTP id 780023A67FA for <ipv6@ietf.org>; Wed, 16 Mar 2011 05:46:56 -0700 (PDT)
Received: from cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [193.225.14.182]) by mail.ki.iif.hu (Postfix) with ESMTP id 90CF186D3A; Wed, 16 Mar 2011 13:48:21 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at cirkusz.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id ZUeglxSpRG+G; Wed, 16 Mar 2011 13:48:06 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 0A5F586D25; Wed, 16 Mar 2011 13:48:06 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 0645386BED; Wed, 16 Mar 2011 13:48:05 +0100 (CET)
Date: Wed, 16 Mar 2011 13:48:05 +0100 (CET)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
In-Reply-To: <4D80ADCF.7060409@gont.com.ar>
Message-ID: <alpine.BSF.2.00.1103161337140.87087@mignon.ki.iif.hu>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D80ADCF.7060409@gont.com.ar>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 12:46:57 -0000

On Wed, 16 Mar 2011, Fernando Gont wrote:

> On 16/03/2011 03:30 a.m., Christian Huitema wrote:
>>> Then what's all this controversy with
>>> draft-gont-6man-managing-privacy-extensions? :-) -- That aside,
>>> there have been quite a few publications asessing the real
>>> "privacy" provided with the so-called privacy-extensions....
>>
>> Using randomized host identifiers is way more private than sticking a
>> MAC address in the IPv6 address.
>
> Agreed. Also in some scenarios privacy extensions may give a false sense
> of privacy (see e.g. some of the pointers in our I-D).
>
>
>> In fact, rather than your draft
>> proposing to not use privacy addresses, we should pursue the
>> deprecation of using EUI-64 in addresses.
>
> Our draft is not meant to propose "not to use privacy addresses" -- as
> noted a few times, already, the proposed mechanism could be used to turn
> "privacy addresses" on for some systems that have decided not to enable
> them by default (e.g., FreeBSD).
>

As RFC 4941 says:

Changed the default setting for usage of temporary addresses to be 
disabled.

and also:
"
Additionally, sites might wish to selectively enable or disable the
    use of temporary addresses for some prefixes.  For example, a site
    might wish to disable temporary address generation for "Unique local"
    [ULA] prefixes while still generating temporary addresses for all
    other global prefixes.  Another site might wish to enable temporary
    address generation only for the prefixes 2001::/16 and 2002::/16,
    while disabling it for all other prefixes.  To support this behavior,
    implementations SHOULD provide a way to enable and disable generation
    of temporary addresses for specific prefix subranges.  This per-
    prefix setting SHOULD override the global settings on the node with
    respect to the specified prefix subranges.  Note that the pre-prefix
    setting can be applied at any granularity, and not necessarily on a
    per-subnet basis.
"

Best Regards,
 		Jans Mohacsi

From yhb810501@gmail.com  Wed Mar 16 06:47:04 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97D323A6999 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 06:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.717
X-Spam-Level: 
X-Spam-Status: No, score=-2.717 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FefeRXetBQTW for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 06:47:03 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 52D503A698F for <ipv6@ietf.org>; Wed, 16 Mar 2011 06:47:03 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1929135vxg.31 for <ipv6@ietf.org>; Wed, 16 Mar 2011 06:48:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:importance:x-mailer :x-mimeole; bh=nxvmSor3obFgFUPU0375kC5BUy4S+1DIYXqQX1l9VLQ=; b=OdrFBV/KEXQOTZwdgAfluP/mxwIUQYg8I3My63xnsD8PutezyMgQN4KO0p9q9Fnz/X C9srAdyVKT7FMlWjqXv6gPG6ZrdTKyGy1TJDVJHZzHLHHKPKyE8JmcT5JZ6uzeY+EiY0 L0qseDvh9p3E9wION9rkfTBvJ/23x/HEyBn/8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; b=LbWDSBCQN5+pCfzbQtpwOF3fbXAghEfy23ZQ9y6EGYTJCMa9nBk7V9DTzeAxd8Il6F kNn6cX/HcDgXcltn/0RjTL4mL8vGemiGUEPUcbIjQqwqt/OEP4y13YBiGjcOooucwco0 1jFN/coCreXRRNcywrAFEjAQiaN8Q4QVgWepQ=
Received: by 10.220.186.131 with SMTP id cs3mr6895vcb.38.1300283309177; Wed, 16 Mar 2011 06:48:29 -0700 (PDT)
Received: from yhbPC ([220.200.24.149]) by mx.google.com with ESMTPS id n13sm343386vcr.41.2011.03.16.06.48.25 (version=SSLv3 cipher=OTHER); Wed, 16 Mar 2011 06:48:28 -0700 (PDT)
Message-ID: <42CE6F8FB47047BC917B7A168B33ED86@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: <ipv6@ietf.org>
Subject: draft-yhb-6man-ra-privacy-flag-02 
Date: Wed, 16 Mar 2011 21:48:11 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01CBE423.D822D1E0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 13:47:04 -0000

这是一封 MIME 格式的多方邮件。

------=_NextPart_000_000E_01CBE423.D822D1E0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi, please read the following words.After you read the words, you may =
agree that the DisablePrivacy flag is helpful.

RFC 4941

3.6.  Deployment Considerations

   Devices implementing this specification MUST provide a way for the
   end user to explicitly enable or disable the use of temporary
   addresses.  In addition, a site might wish to disable the use of
   temporary addresses in order to simplify network debugging and
   operations.  Consequently, implementations SHOULD provide a way for
   trusted system administrators to enable or disable the use of
   temporary addresses.

   Additionally, sites might wish to selectively enable or disable the
   use of temporary addresses for some prefixes.  For example, a site
   might wish to disable temporary address generation for "Unique local"
   [ULA] prefixes while still generating temporary addresses for all
   other global prefixes.  Another site might wish to enable temporary
   address generation only for the prefixes 2001::/16 and 2002::/16,
   while disabling it for all other prefixes.  To support this behavior,
   implementations SHOULD provide a way to enable and disable generation
   of temporary addresses for specific prefix subranges.  This per-
   prefix setting SHOULD override the global settings on the node with
   respect to the specified prefix subranges.  Note that the pre-prefix
   setting can be applied at any granularity, and not necessarily on a
   per-subnet basis.

   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.  Individual
   applications, which have specific knowledge about the normal duration
   of connections, MAY override this as appropriate.


------=_NextPart_000_000E_01CBE423.D822D1E0
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3Dtext/html;charset=3Dgb2312 http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.7600.16722"></HEAD>
<BODY style=3D"PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: =
15px"=20
id=3DMailContainerBody leftMargin=3D0 topMargin=3D0 =
CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DCalibri><SPAN class=3Dm_h><STRONG><FONT =
face=3DArial>Hi, please read=20
the following words.After you read the words, you may agree that the=20
DisablePrivacy flag is helpful.</FONT></STRONG></SPAN></FONT></DIV>
<DIV><FONT face=3DArial><SPAN=20
class=3Dm_h><STRONG></STRONG></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri><SPAN class=3Dm_h></SPAN></FONT><FONT =
face=3DCalibri><SPAN=20
class=3Dm_h><STRONG><FONT face=3DArial>RFC =
4941</FONT></STRONG></SPAN></FONT></DIV>
<DIV><FONT face=3DCalibri><SPAN class=3Dm_h><STRONG><FONT=20
face=3DArial></FONT></STRONG></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DCalibri><SPAN class=3Dm_h><STRONG><FONT =
face=3DArial>3.6.&nbsp;=20
Deployment Considerations</FONT></STRONG></SPAN><BR><BR>&nbsp;&nbsp; =
Devices=20
implementing this specification MUST provide a way for =
the<BR>&nbsp;&nbsp; end=20
user to explicitly enable or disable the use of =
temporary<BR>&nbsp;&nbsp;=20
addresses.&nbsp; In addition, a site might wish to disable the use=20
of<BR>&nbsp;&nbsp; temporary addresses in order to simplify network =
debugging=20
and<BR>&nbsp;&nbsp; operations.&nbsp; Consequently, implementations =
SHOULD=20
provide a way for<BR>&nbsp;&nbsp; trusted system administrators to =
enable or=20
disable the use of<BR>&nbsp;&nbsp; temporary =
addresses.<BR><BR>&nbsp;&nbsp;=20
Additionally, sites might wish to selectively enable or disable=20
the<BR>&nbsp;&nbsp; use of temporary addresses for some prefixes.&nbsp; =
For=20
example, a site<BR>&nbsp;&nbsp; might wish to disable temporary address=20
generation for "Unique local"<BR>&nbsp;&nbsp; [ULA] prefixes while still =

generating temporary addresses for all<BR>&nbsp;&nbsp; other global=20
prefixes.&nbsp; Another site might wish to enable =
temporary<BR>&nbsp;&nbsp;=20
address generation only for the prefixes 2001::/16 and=20
2002::/16,<BR>&nbsp;&nbsp; while disabling it for all other =
prefixes.&nbsp; To=20
support this behavior,<BR>&nbsp;&nbsp; implementations SHOULD provide a =
way to=20
enable and disable generation<BR>&nbsp;&nbsp; of temporary addresses for =

specific prefix subranges.&nbsp; This per-<BR>&nbsp;&nbsp; prefix =
setting SHOULD=20
override the global settings on the node with<BR>&nbsp;&nbsp; respect to =
the=20
specified prefix subranges.&nbsp; Note that the =
pre-prefix<BR>&nbsp;&nbsp;=20
setting can be applied at any granularity, and not necessarily on=20
a<BR>&nbsp;&nbsp; per-subnet basis.<BR><BR>&nbsp;&nbsp; The use of =
temporary=20
addresses may cause unexpected difficulties with<BR>&nbsp;&nbsp; some=20
applications.&nbsp; As described below, some servers refuse to=20
accept<BR>&nbsp;&nbsp; communications from clients for which they cannot =
map the=20
IP address<BR>&nbsp;&nbsp; into a DNS name.&nbsp; In addition, some =
applications=20
may not behave<BR>&nbsp;&nbsp; robustly if temporary addresses are used =
and an=20
address expires<BR>&nbsp;&nbsp; before the application has terminated, =
or if it=20
opens multiple<BR>&nbsp;&nbsp; sessions, but expects them to all use the =
same=20
addresses.<BR>&nbsp;&nbsp; Consequently, the use of temporary addresses =
SHOULD=20
be disabled by<BR>&nbsp;&nbsp; default in order to minimize potential=20
disruptions.&nbsp; Individual<BR>&nbsp;&nbsp; applications, which have =
specific=20
knowledge about the normal duration<BR>&nbsp;&nbsp; of connections, MAY =
override=20
this as appropriate.<BR><BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_000E_01CBE423.D822D1E0--


From yhb810501@gmail.com  Wed Mar 16 07:13:07 2011
Return-Path: <yhb810501@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3BAE3A69B6 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 07:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.712
X-Spam-Level: 
X-Spam-Status: No, score=-2.712 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2V8rwGLyFo1 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 07:13:06 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id AE77F3A69B2 for <ipv6@ietf.org>; Wed, 16 Mar 2011 07:13:06 -0700 (PDT)
Received: by vxg33 with SMTP id 33so1958920vxg.31 for <ipv6@ietf.org>; Wed, 16 Mar 2011 07:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:cc:references:in-reply-to :subject:date:mime-version:content-type:content-transfer-encoding :x-priority:x-msmail-priority:importance:x-mailer:x-mimeole; bh=L8BhaDzltr0vocYquqHQcpmsNJNJtFFfAcz3fhcedjE=; b=ih48pnVA0PejuSQtQDajTKp2gR6/3Ypk03NLxm7ypZvVEZLFP5/p5gkpwTnkZqcZEx 16vWxTyukBmj+YtkhKWmI8/RremHPGET5DQvu1pQ3Ml/h47dPimAbCcWCR34XQfzcbJe g6HDs4WoU+J+ckZC/8SacI18gAL0DFad7BAwY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:cc:references:in-reply-to:subject:date :mime-version:content-type:content-transfer-encoding:x-priority :x-msmail-priority:importance:x-mailer:x-mimeole; b=Z+AzziewnXQ2JCnz3vArLbS9oukzNmObqPs9tJsGIQjQh/asAzZeQKqh/s7tsFICn6 9il6YKEAQCGs9jVr7tDWjQEVxzfv3QuUM2/VejqmMS8XaEyuljKIIf9ImbuhS4AXtnLo EhGWDe04egRSOq0dA/3yB2wPzmexK5vuIJbIM=
Received: by 10.52.175.100 with SMTP id bz4mr8653vdc.261.1300284872910; Wed, 16 Mar 2011 07:14:32 -0700 (PDT)
Received: from yhbPC ([220.200.24.149]) by mx.google.com with ESMTPS id bc20sm359589vdb.9.2011.03.16.07.14.29 (version=SSLv3 cipher=OTHER); Wed, 16 Mar 2011 07:14:31 -0700 (PDT)
Message-ID: <AAB2A33432A6460490005A0EF60D3A9E@yhbPC>
From: "Yu Hua bing" <yhb810501@gmail.com>
To: "Fernando Gont" <fernando@gont.com.ar>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<20110310071925.309d467b@opy.nosense.org>	<4D7F539E.7030308@gont.com.ar><4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar><22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D80ADCF.7060409@gont.com.ar>
In-Reply-To: <4D80ADCF.7060409@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Date: Wed, 16 Mar 2011 22:14:19 +0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 14:13:07 -0000

>Our draft is not meant to propose "not to use privacy addresses" -- as
>noted a few times, already, the proposed mechanism could be used to turn
>"privacy addresses" on for some systems that have decided not to enable
>them by default (e.g., FreeBSD).

Windows provides the command line to turn on or off the privacy extension.
Is your meaning is that if the user turn off the privacy extension, the RAG
flag in the router advertisement can turn on the privacy extension?
 


From Francis.Dupont@fdupont.fr  Wed Mar 16 08:14:15 2011
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30E8C3A69B5 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 08:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.227
X-Spam-Level: 
X-Spam-Status: No, score=-3.227 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id raFTc3yVCn32 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 08:14:14 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [91.121.26.85]) by core3.amsl.com (Postfix) with ESMTP id 3A91D3A6957 for <ipv6@ietf.org>; Wed, 16 Mar 2011 08:14:14 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p2GFFeFD082005; Wed, 16 Mar 2011 16:15:40 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201103161515.p2GFFeFD082005@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts? 
In-reply-to: Your message of Wed, 16 Mar 2011 11:37:35 +0100. <6E78895C-8CFC-4B4B-9882-B20C29D25E01@equinux.de> 
Date: Wed, 16 Mar 2011 16:15:40 +0100
Sender: Francis.Dupont@fdupont.fr
Cc: ipv6@ietf.org, Mohacsi Janos <mohacsi@niif.hu>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 15:14:15 -0000

 In your previous mail you wrote:

   The chances that a MD5 hash of any data will ever be exactly zero
   (all octets are zero) is ridiculous tiny.

=> yes, I offer a free beer to you if you find one for the next
IETF meeting.

Regards

Francis.Dupont@fdupont.fr

From brian.haley@hp.com  Wed Mar 16 09:50:37 2011
Return-Path: <brian.haley@hp.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B8843A69E8 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 09:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y4cXS8E1V7o5 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 09:50:36 -0700 (PDT)
Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by core3.amsl.com (Postfix) with ESMTP id 7B2233A69E1 for <ipv6@ietf.org>; Wed, 16 Mar 2011 09:50:36 -0700 (PDT)
Received: from g1t0038.austin.hp.com (g1t0038.austin.hp.com [16.236.32.44]) by g1t0027.austin.hp.com (Postfix) with ESMTP id 81C4F38BFC; Wed, 16 Mar 2011 16:52:02 +0000 (UTC)
Received: from [16.1.1.20] (squirrel.fc.hp.com [15.11.146.57]) by g1t0038.austin.hp.com (Postfix) with ESMTP id EEEA630192; Wed, 16 Mar 2011 16:52:00 +0000 (UTC)
Message-ID: <4D80EAAF.6010509@hp.com>
Date: Wed, 16 Mar 2011 12:51:59 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D7B5914.6090000@gont.com.ar>
In-Reply-To: <4D7B5914.6090000@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 16:50:37 -0000

On 03/12/2011 06:29 AM, Fernando Gont wrote:
> On 09/03/2011 08:17 a.m., Mikael Abrahamsson wrote:
> 
>>> I recommend that folks read the above draft.  I haven't seen the
>>> I-D announcement get cross-posted to the IPv6 WG, perhaps due to
>>> the volume of recent I-D postings, and the topic seems relevant.
>>
>> I don't think it solves what it thinks it solves, but if this REALLY
>> should be implemented, it's my initial thinking that the H flag should
>> be a MUST demand to only have ONE and only one MAC-based IPv6 address
>> according to EUI64. I would appreciate some reasoning in the draft why
>> this was chosen as a SHOULD option.
> 
> I realize I misunderstood your comment.
> 
> The intention of the I-D is/was that if the "H" bit is set, you SHOULD
> generate your addresses corresponding to this prefix ONLY with according
> to EUI64.
> 
> The above requirement is a "SHOULD" (rather than a MUST), since a hosts
> that has good reasons to do so (e.g., privacy concerns) is allowed to
> override the policy specified by the router.

I have an almost off-topic comment, but since I've seen no mention of it
in any of these privacy threads...

You have to assume in a large data center that almost every MAC address you
encounter is going to be randomly generated.  This is because there are
*lots* of virtual machines out there, and the density of them is increasing
exponentially.  Their MACs could change daily as they are deployed and
decommissioned, but from their perspective their MAC is hardware-based.
I know you have this as a "SHOULD" requirement, but figured I should mention
it since it's one of those places where this bit will be completely ignored.

-Brian

From brian.haley@hp.com  Wed Mar 16 09:50:40 2011
Return-Path: <brian.haley@hp.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 991453A69EE for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 09:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsRKl3EzEt5v for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 09:50:39 -0700 (PDT)
Received: from g1t0027.austin.hp.com (g1t0027.austin.hp.com [15.216.28.34]) by core3.amsl.com (Postfix) with ESMTP id A4EA53A69E8 for <ipv6@ietf.org>; Wed, 16 Mar 2011 09:50:39 -0700 (PDT)
Received: from g1t0038.austin.hp.com (g1t0038.austin.hp.com [16.236.32.44]) by g1t0027.austin.hp.com (Postfix) with ESMTP id 6B67A38A6D; Wed, 16 Mar 2011 16:52:05 +0000 (UTC)
Received: from [16.1.1.20] (squirrel.fc.hp.com [15.11.146.57]) by g1t0038.austin.hp.com (Postfix) with ESMTP id AD23530249; Wed, 16 Mar 2011 16:52:01 +0000 (UTC)
Message-ID: <4D80EAB0.2050701@hp.com>
Date: Wed, 16 Mar 2011 12:52:00 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: Markus Hanauska <hanauska@equinux.de>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<alpine.BSF.2.00.1103160951100.87087@mignon.ki.iif.hu>	<3833B29B-1475-4BD7-B94D-7BD70AE4CB3B@equinux.de>	<m1PznxD-0001dSC@stereo.hq.phicoh.net> <F83685EF-959F-488B-B4E8-FD41712F9BA6@equinux.de>
In-Reply-To: <F83685EF-959F-488B-B4E8-FD41712F9BA6@equinux.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 16:50:40 -0000

On 03/16/2011 07:06 AM, Markus Hanauska wrote:
> 
> On 2011-03-16, at 11:27 , Philip Homburg wrote:
> 
>> You look up the MAC address for that IPv6 address and then block the MAC
>> address on your switches. Problem solved.
> 
> Sure, that will work. However, that means I have to invest time and work to solve a problem, that would have easily been avoidable by a tiny standard change and that did not arise because anyone made a mistake, it just has been recklessly accepted by the standard creators, because it seemed unlikely. And this is a lot of work, since I cannot block it globally, but I have to work my way through all our managed switches and I will get a problem on some parts of the network, where unmanaged switches are used, which I might have to reboot after blocking to flush their address cache.

But you have to be able to do this anyways, because someone *is* going to
configure a system wrong and cause big problems, you can't assume an RFC
will protect you.  It's even extremely easy to disable DAD and manually
configure an address on a lot of systems - what will you do then?  If you
can't secure the configuration on a host, and you can't typically, you
have to do it in the infrastructure where you *do* control everything.

If I had $1 for every time I had to track-down a system configured as
a default IPv6 router and sending bogus advertisements out, well, I'd have
about $10 :)  That's what happens when people google 'ipv6 configuration'
and blindly cut/paste commands...

-Brian

From remi.despres@free.fr  Wed Mar 16 10:01:44 2011
Return-Path: <remi.despres@free.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7C8D3A69D9 for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 10:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.315
X-Spam-Level: 
X-Spam-Status: No, score=-0.315 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_20=-0.74, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAT4klQvJMOR for <ipv6@core3.amsl.com>; Wed, 16 Mar 2011 10:01:44 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.4]) by core3.amsl.com (Postfix) with ESMTP id 178343A6941 for <ipv6@ietf.org>; Wed, 16 Mar 2011 10:01:44 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id 77F8E700008C; Wed, 16 Mar 2011 18:03:10 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2114.sfr.fr (SMTP Server) with ESMTP id 114F97000096; Wed, 16 Mar 2011 18:03:09 +0100 (CET)
X-SFR-UUID: 20110316170310709.114F97000096@msfrf2114.sfr.fr
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
Date: Wed, 16 Mar 2011 18:03:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CB96844-B467-4EDC-B872-8000F9ED62CF@free.fr>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com>	<20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1082)
Cc: Ran Atkinson <ran.atkinson@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 16 Mar 2011 17:01:44 -0000

Le 16 mars 2011 =E0 07:30, Christian Huitema a =E9crit :
...

> In fact, rather than your draft proposing to not use privacy =
addresses, we should pursue the deprecation of using EUI-64 in =
addresses.

-1

> The worst part of your draft is that , if we published it, it would =
give the impression that for the IETF, EUI-64 addresses are more secure =
than privacy addresses. This is obviously false.

But they are more stable by default, a feature that can be useful where =
privacy isn't a must.

RD

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



From bob.hinden@gmail.com  Thu Mar 17 09:31:32 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4EC0E3A6A98 for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 09:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.528
X-Spam-Level: 
X-Spam-Status: No, score=-103.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2e8WYZZUanm for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 09:31:31 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 946393A69FD for <ipv6@ietf.org>; Thu, 17 Mar 2011 09:31:31 -0700 (PDT)
Received: by iyi12 with SMTP id 12so3517805iyi.31 for <ipv6@ietf.org>; Thu, 17 Mar 2011 09:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=srvTcGVSzPLXJvX9WFFgrJwMLiz2EClhK4p6KRyZyHM=; b=AK36clKZfbNWOrXDCMztZv8/SjjrnKsojsoPPaYx7v37EirY1BqidAO/g2kZqKGhrT k/EYPefdHNXkjx05qyGYMHbrOQjfLTOsop63yGqyXYlG0FfShPyTUfWM4B23ubakMCXc +jU/blDvJQyYHo/ZeLc2lEmbRVs8ETrQg6uLU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=qEITiokUY7/eIq5YqzX/BAiyyxViC6WsWSTQgVuWEwh/wiI6YIoFdn2yHVmxjAmsJx xccprFh+vawG57IzOCVwne/SuuO10ZZZhjEwXL5jmVvqtgXmfh6aKxU6HTIHxuXpe4ny baeTbJ3Yi60+yfw/aCAp1AowcYeOt+YAbf7x4=
Received: by 10.42.74.3 with SMTP id u3mr2127054icj.512.1300379579752; Thu, 17 Mar 2011 09:32:59 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id g4sm1293175ick.23.2011.03.17.09.32.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Mar 2011 09:32:59 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: 6man IETF Agenda
Date: Thu, 17 Mar 2011 09:32:57 -0700
Message-Id: <BC2100F7-F542-4E1A-A4B6-FC379F686E1E@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 17 Mar 2011 16:31:32 -0000

The current agenda can be found at:

   http://www.ietf.org/proceedings/80/agenda/6man.html

Thanks,
Bob & Brian


From jpv@cisco.com  Thu Mar 17 11:07:09 2011
Return-Path: <jpv@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6A2E3A6ADD for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 11:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.511
X-Spam-Level: 
X-Spam-Status: No, score=-110.511 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rZ8pY6GHaV9 for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 11:07:08 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id B6FD33A6A04 for <ipv6@ietf.org>; Thu, 17 Mar 2011 11:07:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jpv@cisco.com; l=9761; q=dns/txt; s=iport; t=1300385317; x=1301594917; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=wMkCkT+u2D6rI5ZPCp32TRgSMcHkoBjFsH/0JlW1GnQ=; b=MY1Iv3ftRdvv/XuWywW1UbSQpwaPgPRCDSlGKcEIJr6A6OSJH0cdxqd6 TI67ZVZ6u9g5a6Z4S4CKbrp93yzbsStETY5cGLqZ7I6RIUOfORsf3SWU/ 7p2W1sT8Sg60juEwcfvsmBzZ4vCYSqGNlELngEH9hQBWFB9prEyPrL3O1 Y=;
X-IronPort-AV: E=Sophos;i="4.63,200,1299456000";  d="scan'208,217";a="415495150"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-1.cisco.com with ESMTP; 17 Mar 2011 18:08:35 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2HI88Gb014367;  Thu, 17 Mar 2011 18:08:35 GMT
Received: from xfe-sjc-232.amer.cisco.com ([128.107.191.79]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 17 Mar 2011 11:08:33 -0700
Received: from [10.2.59.95] ([10.21.76.250]) by xfe-sjc-232.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 17 Mar 2011 11:08:32 -0700
Subject: Re: Lack of responses on WG Last Calls
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-134--44434350
From: JP Vasseur <jpv@cisco.com>
In-Reply-To: <80CC860A-8625-4B27-89F8-3C5DB1FAF538@cisco.com>
Date: Thu, 17 Mar 2011 11:08:32 -0700
Message-Id: <93C139AA-66C1-437A-A5D0-1B7EAAA686BB@cisco.com>
References: <4D0AA2CE.8000604@gmail.com> <80CC860A-8625-4B27-89F8-3C5DB1FAF538@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-OriginalArrivalTime: 17 Mar 2011 18:08:32.0839 (UTC) FILETIME=[53AC5570:01CBE4CE]
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 17 Mar 2011 18:07:10 -0000

--Apple-Mail-134--44434350
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear Brian,

Many thanks for your review. We addressed your comment in the new =
revision, just posted.

Kind Regards.

JP.
> > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> > Date: December 16, 2010 3:37:50 PM PST
> > To: Brian Haberman <brian@innovationslab.net>
> > Cc: IPv6 WG Mailing List <ipv6@ietf.org>
> > Subject: Re: Lack of responses on WG Last Calls
> >
> > For my sins, I was the Gen-ART reviewer for the main RPL spec,
> > so I was able to have a quick glance at these without being
> > completely mystified.
> >
> > On 2010-12-17 02:53, Brian Haberman wrote:
> >> All,
> >>    Working group last calls ended 10 days ago for the two =
RPL-related
> >> drafts (draft-ietf-6man-rpl-option
> >
> > This looks basically OK to me. However:
> >
> >> 9.  IANA Considerations
> >>
> >>   The RPL option requires an IPv6 Option Number.
> >
> > Shouldn't we have a "TBD" here, as used in the main text?
> > And an instruction to the RFC Editor to resolve the TBD
> > after IANA performs the assignment.
> >
> >>
> >>   HEX         act  chg  rest
> >>   ---         ---  ---  -----
> >>     1          01    1  01011
> >>
> >>
> >>   The first two bits indicate that the IPv6 node MUST discard the
> >>   packet if it doesn't recognize the option type, and the third bit
> >>   indicates that the Option Data may change en-route.
> >>
> >>   This document also creates a new IANA registry for the sub-TLVs.  =
No
> >>   sub-TLVs are defined in this specification.  The policy for this
> >>   registry [RFC5226] is IETF Review.
> >
> > I think the IANA will ask for a bit more guidance about the format
> > and name of this registry.
> >
> > and
> >> draft-ietf-6man-rpl-routing-header).
> >
> > This defines a new routing header called RH4 (subject to
> > IANA confirming the "4"). One question that comes to mind
> > is whether this is going to cause more or fewer operational
> > difficulties than an instantiation of draft-ietf-6man-exthdr
> > would. Will legacy nodes treat RH4 as they should (discard the
> > packet), treat it like RH0 due to sloppy coding (which
> > amounts to the same thing under RFC5095) or what? Anyway,
> > it seems clear that RH4 will not successfully cross any
> > non-RPL-aware routers.
> >
> > Now this may be deemed irrelevant because RH4 is "for use
> > strictly within a RPL domain." But it seems highly likely that
> > in practice, the odd non-RPL router will see one of these
> > headers. So at the least, I think the draft should discuss
> > what will happen in that case, even if only to point out that
> > the rules of RFC 2460 mean that the packet (not just the header)
> > will be dropped unless Segments Left is zero.
> >
> > Then:
> >
> >> 6.1.  Source Routing Attacks
> >>
> >>   [RFC5095] deprecates the Type 0 Routing header due to a number of
> >>   significant attacks that are referenced in that document.  Such
> >>   attacks include network discovery, bypassing filtering devices,
> >>   denial-of-service, and defeating anycast.
> >>
> >>   Because this document specifies that Type 4 Routing headers are =
only
> >>   for use within a RPL domain, such attacks cannot be mounted from
> >>   outside the RPL domain.  As described in Section 5, RPL Border
> >>   Routers MUST drop datagrams entering or exiting the RPL domain =
that
> >>   contain a Type 4 Routing header in the IPv6 Extension headers.
> >
> > OK, but that implies that such attacks can still be mounted inside =
the
> > RPL domain. How is that OK, given that ROLL may be deployed in =
highly
> > dynamic scenarios where roaming nodes drop into a network at will?
> >
> >   Brian
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>=20
>=20


--Apple-Mail-134--44434350
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Brian,<div><br></div><div>Many thanks for your review. We addressed your comment in the new revision, just posted.</div><div><br></div><div>Kind Regards.</div><div><br></div><div>JP.<br><div><blockquote type="cite"><div><p><font size="2">&gt; From: Brian E Carpenter &lt;<a href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
&gt; Date: December 16, 2010 3:37:50 PM PST<br>
&gt; To: Brian Haberman &lt;<a href="mailto:brian@innovationslab.net">brian@innovationslab.net</a>&gt;<br>
&gt; Cc: IPv6 WG Mailing List &lt;<a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;<br>
&gt; Subject: Re: Lack of responses on WG Last Calls<br>
&gt;<br>
&gt; For my sins, I was the Gen-ART reviewer for the main RPL spec,<br>
&gt; so I was able to have a quick glance at these without being<br>
&gt; completely mystified.<br>
&gt;<br>
&gt; On 2010-12-17 02:53, Brian Haberman wrote:<br>
&gt;&gt; All,<br>
&gt;&gt;&nbsp;&nbsp;&nbsp; Working group last calls ended 10 days ago for the two RPL-related<br>
&gt;&gt; drafts (draft-ietf-6man-rpl-option<br>
&gt;<br>
&gt; This looks basically OK to me. However:<br>
&gt;<br>
&gt;&gt; 9.&nbsp; IANA Considerations<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; The RPL option requires an IPv6 Option Number.<br>
&gt;<br>
&gt; Shouldn't we have a "TBD" here, as used in the main text?<br>
&gt; And an instruction to the RFC Editor to resolve the TBD<br>
&gt; after IANA performs the assignment.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; HEX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; act&nbsp; chg&nbsp; rest<br>
&gt;&gt;&nbsp;&nbsp; ---&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ---&nbsp; ---&nbsp; -----<br>
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 01&nbsp;&nbsp;&nbsp; 1&nbsp; 01011<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; The first two bits indicate that the IPv6 node MUST discard the<br>
&gt;&gt;&nbsp;&nbsp; packet if it doesn't recognize the option type, and the third bit<br>
&gt;&gt;&nbsp;&nbsp; indicates that the Option Data may change en-route.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; This document also creates a new IANA registry for the sub-TLVs.&nbsp; No<br>
&gt;&gt;&nbsp;&nbsp; sub-TLVs are defined in this specification.&nbsp; The policy for this<br>
&gt;&gt;&nbsp;&nbsp; registry [RFC5226] is IETF Review.<br>
&gt;<br>
&gt; I think the IANA will ask for a bit more guidance about the format<br>
&gt; and name of this registry.<br>
&gt;<br>
&gt; and<br>
&gt;&gt; draft-ietf-6man-rpl-routing-header).<br>
&gt;<br>
&gt; This defines a new routing header called RH4 (subject to<br>
&gt; IANA confirming the "4"). One question that comes to mind<br>
&gt; is whether this is going to cause more or fewer operational<br>
&gt; difficulties than an instantiation of draft-ietf-6man-exthdr<br>
&gt; would. Will legacy nodes treat RH4 as they should (discard the<br>
&gt; packet), treat it like RH0 due to sloppy coding (which<br>
&gt; amounts to the same thing under RFC5095) or what? Anyway,<br>
&gt; it seems clear that RH4 will not successfully cross any<br>
&gt; non-RPL-aware routers.<br>
&gt;<br>
&gt; Now this may be deemed irrelevant because RH4 is "for use<br>
&gt; strictly within a RPL domain." But it seems highly likely that<br>
&gt; in practice, the odd non-RPL router will see one of these<br>
&gt; headers. So at the least, I think the draft should discuss<br>
&gt; what will happen in that case, even if only to point out that<br>
&gt; the rules of RFC 2460 mean that the packet (not just the header)<br>
&gt; will be dropped unless Segments Left is zero.<br>
&gt;<br>
&gt; Then:<br>
&gt;<br>
&gt;&gt; 6.1.&nbsp; Source Routing Attacks<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; [RFC5095] deprecates the Type 0 Routing header due to a number of<br>
&gt;&gt;&nbsp;&nbsp; significant attacks that are referenced in that document.&nbsp; Such<br>
&gt;&gt;&nbsp;&nbsp; attacks include network discovery, bypassing filtering devices,<br>
&gt;&gt;&nbsp;&nbsp; denial-of-service, and defeating anycast.<br>
&gt;&gt;<br>
&gt;&gt;&nbsp;&nbsp; Because this document specifies that Type 4 Routing headers are only<br>
&gt;&gt;&nbsp;&nbsp; for use within a RPL domain, such attacks cannot be mounted from<br>
&gt;&gt;&nbsp;&nbsp; outside the RPL domain.&nbsp; As described in Section 5, RPL Border<br>
&gt;&gt;&nbsp;&nbsp; Routers MUST drop datagrams entering or exiting the RPL domain that<br>
&gt;&gt;&nbsp;&nbsp; contain a Type 4 Routing header in the IPv6 Extension headers.<br>
&gt;<br>
&gt; OK, but that implies that such attacks can still be mounted inside the<br>
&gt; RPL domain. How is that OK, given that ROLL may be deployed in highly<br>
&gt; dynamic scenarios where roaming nodes drop into a network at will?<br>
&gt;<br>
&gt;&nbsp;&nbsp; Brian<br>
&gt;<br>
&gt; --------------------------------------------------------------------<br>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href="mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<br>
<br>
</font>
</p>

</div>
</blockquote></div><br></div>
</body></html>
--Apple-Mail-134--44434350--

From fernando.gont.netbook.win@gmail.com  Thu Mar 17 18:09:21 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 029843A6B03 for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 18:09:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfVaZpQrXJ9g for <ipv6@core3.amsl.com>; Thu, 17 Mar 2011 18:09:20 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id EBBBB3A6AB0 for <ipv6@ietf.org>; Thu, 17 Mar 2011 18:09:19 -0700 (PDT)
Received: by wyb42 with SMTP id 42so3680706wyb.31 for <ipv6@ietf.org>; Thu, 17 Mar 2011 18:10:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=zWWJGVzYWFJnbOQaQWEqgfmT78+clx2EIkXJej/jIS4=; b=EfUOv8uFEidgmda4StOo6OVCUyaHIaNlXe6Z3+OakH+ilRwpKMUKT/zKygVA9hzM55 NLI+L3j7H4CmukZ8KlsKx73Qk9CBXC9O8dv9KGRu/FEMVJ0BeeCuYwWqm/liGquVDRGH NUBXZbfxIqz6GGZJtdVtFuhbqxIcWL0rbRpoI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=r0ufEnJFpSu3+a2JtL4RX+ug4XblcxgtcvkAkY6pIJs7gRTqbcVTmyjaFYFQClbgv9 1K18i3kgKEkoR4HRgppCcAuXE41c6T4z3AggrYWiAKlll7WHlSgoAH8TF44GT8e5qcv6 /6Dvs9jYF3XpSBbjKWT/lsuPmDQVqwCg37S6Y=
Received: by 10.216.170.213 with SMTP id p63mr1648880wel.37.1300410647711; Thu, 17 Mar 2011 18:10:47 -0700 (PDT)
Received: from [192.168.200.34] ([194.2.150.133]) by mx.google.com with ESMTPS id h11sm1004735wbc.60.2011.03.17.18.10.44 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Mar 2011 18:10:45 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D82B116.40305@gont.com.ar>
Date: Thu, 17 Mar 2011 22:10:46 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Yu Hua bing <yhb810501@gmail.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se>	<4D77CBB9.1080702@gmail.com>	<20110310071925.309d467b@opy.nosense.org>	<4D7F539E.7030308@gont.com.ar><4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar><22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D80ADCF.7060409@gont.com.ar> <AAB2A33432A6460490005A0EF60D3A9E@yhbPC>
In-Reply-To: <AAB2A33432A6460490005A0EF60D3A9E@yhbPC>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 18 Mar 2011 01:09:21 -0000

On 16/03/2011 11:14 a.m., Yu Hua bing wrote:
>> Our draft is not meant to propose "not to use privacy addresses" -- as
>> noted a few times, already, the proposed mechanism could be used to turn
>> "privacy addresses" on for some systems that have decided not to enable
>> them by default (e.g., FreeBSD).
> 
> Windows provides the command line to turn on or off the privacy extension.
> Is your meaning is that if the user turn off the privacy extension, the RAG
> flag in the router advertisement can turn on the privacy extension?

No.

A host could have two knobs, e.g.:
DefaultAddressPolicy = PrivacyExtensions/EUI64
EnableAddressPolicyConfiguration = Enabled/Disabled

If EnableAddressPolicyConfiguration is Enabled, then the host will
employ whatever address policy is advised by the router (or, if no
specific advice is provided, it would use DefaultAddressPolicy).

If EnableAddressPolicyConfiguration is Disabled, then the host would
employ DefaultAddressPolicy regardless of what the router is advising.

The aforementioned knobs might be configured with different
granularities. For example, on a "per wireless network" basis, or whatever.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Fri Mar 18 14:07:59 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE1553A6A2D for <ipv6@core3.amsl.com>; Fri, 18 Mar 2011 14:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.103
X-Spam-Level: 
X-Spam-Status: No, score=-3.103 tagged_above=-999 required=5 tests=[AWL=-0.496, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPhUjpxPKdh7 for <ipv6@core3.amsl.com>; Fri, 18 Mar 2011 14:07:59 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id CCCD03A6A19 for <ipv6@ietf.org>; Fri, 18 Mar 2011 14:07:58 -0700 (PDT)
Received: by bwz13 with SMTP id 13so4041004bwz.31 for <ipv6@ietf.org>; Fri, 18 Mar 2011 14:09:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=IQq/4/RkJsIRu57cpC5Wpz1bqCV0pndUHC7wbtceA/8=; b=p12suF26Hd8gQyC0H0iWU8xYNru4XgO2SxyRiYqTNakdaWHezhV8mZp7iePIqjwKom 2Rnkk5qVBKpfsW8/tYTc4YwIYUcwW1q6zt1mBVTul4u+ZGffRR1uLYp8xPzg9naz6eNu krHD80fErtsuAQmQZiUjCRq2bG7Gip/A0qbbA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=wWvdNnt6wXMH4BXxIJV7YK2zrhbd0YLpRdm/meF6stGB7B0e52kw2zmrD0x68ZEDFS 5aPbr5e5rj+DefyxPfGoEDbs3DytRMxVoq+LkpV/7Q+ob9g9ccXDR8nX6yMpOV65OiNJ 9iFnipLlBspJeaBEOeteHoa0vs91/Ynye4Y/I=
Received: by 10.204.136.217 with SMTP id s25mr1404412bkt.13.1300482568026; Fri, 18 Mar 2011 14:09:28 -0700 (PDT)
Received: from [192.168.200.80] ([194.2.150.133]) by mx.google.com with ESMTPS id w3sm2445725bkt.17.2011.03.18.14.09.04 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Mar 2011 14:09:24 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D82AE78.20808@gont.com.ar>
Date: Thu, 17 Mar 2011 21:59:36 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Mohacsi Janos <mohacsi@niif.hu>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D77CBB9.1080702@gmail.com> <20110310071925.309d467b@opy.nosense.org> <4D7F539E.7030308@gont.com.ar> <4D7FE55B.7050207@gmail.com> <4D80166A.9060502@gont.com.ar> <22F6318E46E26B498ABC828879B08D4F0C40AA@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <4D80ADCF.7060409@gont.com.ar> <alpine.BSF.2.00.1103161337140.87087@mignon.ki.iif.hu>
In-Reply-To: <alpine.BSF.2.00.1103161337140.87087@mignon.ki.iif.hu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 18 Mar 2011 21:07:59 -0000

On 16/03/2011 09:48 a.m., Mohacsi Janos wrote:

> As RFC 4941 says:
> 
> Changed the default setting for usage of temporary addresses to be
> disabled.
> 
> and also:
> "
> Additionally, sites might wish to selectively enable or disable the
>    use of temporary addresses for some prefixes.  For example, a site
>    might wish to disable temporary address generation for "Unique local"
>    [ULA] prefixes while still generating temporary addresses for all
>    other global prefixes.  Another site might wish to enable temporary
>    address generation only for the prefixes 2001::/16 and 2002::/16,
>    while disabling it for all other prefixes.  To support this behavior,
>    implementations SHOULD provide a way to enable and disable generation
>    of temporary addresses for specific prefix subranges.  This per-
>    prefix setting SHOULD override the global settings on the node with
>    respect to the specified prefix subranges.  Note that the pre-prefix
>    setting can be applied at any granularity, and not necessarily on a
>    per-subnet basis.
> "

The proposed modification to the Prefix Information option would enable
administrators to avoid the pain of having to do this manually on each
node attached to their site -- which in some cases could be impossible.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From bob.hinden@gmail.com  Fri Mar 18 15:52:54 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F7E13A6A6D for <ipv6@core3.amsl.com>; Fri, 18 Mar 2011 15:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.456
X-Spam-Level: 
X-Spam-Status: No, score=-103.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qz0sE9mcUMtX for <ipv6@core3.amsl.com>; Fri, 18 Mar 2011 15:52:53 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 771553A6A53 for <ipv6@ietf.org>; Fri, 18 Mar 2011 15:52:53 -0700 (PDT)
Received: by iyi12 with SMTP id 12so5212052iyi.31 for <ipv6@ietf.org>; Fri, 18 Mar 2011 15:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=bc9XYpzdXN4QWjwsgGB+0yST8VlrjEEBQs048ru1gxc=; b=TFAVeG7+MH+P9oGVR56zoqVMQdjvB0kOMXq/4OJsinnsUkfugnVkxCdsXs9uGCiwUk TksFhee28XbNHoB1pQOzlDEXToVl6tXbn2+MvikeAk08p0poUEkcDEQWd5aNTL05+qn/ b+2uEdSwaChtV9IVfTBGx1c8Ebs+ct7Xz0o4s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=AKOHjoq1BNCpkBjUggCJpl7SLu/EtDVS7KssfZApRic45iESc9LiBIIF8k2H6FDSw+ j+V3GrgJKvmJIKZB+1Y2VGyQMXOBHW7GJjAbop37wmzxLKuP0DU4B91/fTrqTnpY7+3m lEHRHZkaEjfuc7nSyhFoCeNzKP7jCj4OQ83Ks=
Received: by 10.43.52.195 with SMTP id vn3mr2342279icb.272.1300488863362; Fri, 18 Mar 2011 15:54:23 -0700 (PDT)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id y10sm1780832iba.11.2011.03.18.15.54.22 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Mar 2011 15:54:23 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6MAN WG Last Call: <draft-ietf-6man-flow-3697bis-02.txt>
Date: Fri, 18 Mar 2011 15:54:22 -0700
Message-Id: <E6B0E090-0FC1-482F-A7D3-E47A747539A8@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 18 Mar 2011 22:52:54 -0000

All,

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

	Title           : IPv6 Flow Label Specification
	Author(s)       : S. Amante, et al.
	Filename        : draft-ietf-6man-flow-3697bis-02.txt
	Pages           : 13
	Date            : 2011-03-13
=09
       http://tools.ietf.org/html/draft-ietf-6man-flow-3697bis-02

as an Proposed Standard.  Substantive comments and statements of support =
for advancing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 1 April 2011.

Regards,
Bob Hinden & Brian Haberman
6MAN Chairs


From shemant@cisco.com  Sun Mar 20 07:25:45 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 017F53A6BC7 for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 07:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.452
X-Spam-Level: 
X-Spam-Status: No, score=-10.452 tagged_above=-999 required=5 tests=[AWL=-0.453, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xk2dW5MmemRu for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 07:25:44 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 001353A6A03 for <ipv6@ietf.org>; Sun, 20 Mar 2011 07:25:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1349; q=dns/txt; s=iport; t=1300631236; x=1301840836; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=1yZuPM7XYYKui+ve3c5ZUd/YMNMBoJr6oyefK73sdpI=; b=Rl37B9w44pD/Vmo86fiZiYfvwH1angH7Ga0xlu3WniHBsfDKRnYjaQv1 1uYiHfDC5Agwih86GlOZnYx7S0ipyMG7DUbKkZXIKEbnwNx+pgZ8eDYmj 7O8wMbP9i9+95JgXHOaUZMrxLRSvFaGNMTD9OHuy2UALjGn+uL2x7D/Uy E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuIAAAushU2tJV2Z/2dsb2JhbACYPY06d6RGmxOFYwSFM4sL
X-IronPort-AV: E=Sophos;i="4.63,214,1299456000"; d="scan'208";a="668906887"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-6.cisco.com with ESMTP; 20 Mar 2011 14:27:14 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2KEREac027225;  Sun, 20 Mar 2011 14:27:14 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 20 Mar 2011 09:27:14 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Date: Sun, 20 Mar 2011 09:27:09 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2AF1@XMB-RCD-109.cisco.com>
In-Reply-To: <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why has RFC 4941 been designed in such a way, that it might cause address conflicts?
Thread-Index: AcvjNmB7FvdLEHp1QVem+kmr/t2g/gD0SwYA
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de> <E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "james woodyatt" <jhw@apple.com>, "Markus Hanauska" <hanauska@equinux.de>
X-OriginalArrivalTime: 20 Mar 2011 14:27:14.0581 (UTC) FILETIME=[E8743450:01CBE70A]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 Mar 2011 14:25:45 -0000

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
james woodyatt
Sent: Tuesday, March 15, 2011 1:28 PM
To: Markus Hanauska
Cc: ipv6@ietf.org
Subject: Re: Why has RFC 4941 been designed in such a way,that it might
cause address conflicts?


>Duplicate Address Detection (DAD) is the mechanism by which address
conflicts are resolved in IPv6. =20

DAD as per RFC 4862 does not resolve conflicts but detects the
conflicts.  See section 5.4.5 which punts a duplicate detected event to
the admin of the network to deal with.

>If you set DupAddrDetectTransmits to zero on an interface where DAD is
required to prevent address conflicts, then the network isn't required
to work properly when you do that.  If the subscriber >aggregation
network by which you're connecting a mobile node to the Internet
requires a DAD proxy to prevent address conflicts, and the DAD proxy is
malfunctional, then you can expect damaged network >service as a result.


Speaking of a mobile network (cellular) where it does make sense to set
DupAddrDetectTransmits to zero since the hosts use p2p and hosts use the
Modified EUI-64 format for Interface Identifier (IID) - see RFC 2472.
Modified EUI-64 uses a global token to generate the IID and thus the IID
is likely to be unique.=20

Hemant

From shemant@cisco.com  Sun Mar 20 14:59:03 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3DC753A6BEA for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 14:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.739
X-Spam-Level: 
X-Spam-Status: No, score=-10.739 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tP8j0pDXuLyg for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 14:59:02 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 11A753A69B6 for <ipv6@ietf.org>; Sun, 20 Mar 2011 14:59:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2036; q=dns/txt; s=iport; t=1300658434; x=1301868034; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=lgM8S+q7ivfdrIqjhZiLWtAEUKfbxk4gJxvkHyDWdQc=; b=Zyt1rqtZDarqBrf4IdAtJuvu9R1xSj8UBulRWs6wExI+YGQgqq6xD8Jl KAdQNJNXQaUUmNp9q/nPvkB7iAUKd4tJoWF/vCQJSjtYtLCMeX50WBEjD ymZQq624EK4PjCiB4g3uoAgvw17xt8P/c3HDo3JSbhOwHlpW9z/HXT5UE M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAI0Vhk2tJV2a/2dsb2JhbACYNI06d6Nrji6MYYVjBIUziws
X-IronPort-AV: E=Sophos;i="4.63,216,1299456000"; d="scan'208";a="227291409"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 20 Mar 2011 22:00:31 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2KM0V27000351;  Sun, 20 Mar 2011 22:00:31 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 20 Mar 2011 17:00:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Date: Sun, 20 Mar 2011 17:00:29 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com>
In-Reply-To: <4D7FEE26.9060502@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Thread-Index: AcvjY/zRy0liUrQMQnmfkCWb3QB2mgD4wjmA
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de><35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com> <4D7FEE26.9060502@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "james woodyatt" <jhw@apple.com>
X-OriginalArrivalTime: 20 Mar 2011 22:00:32.0086 (UTC) FILETIME=[3B6E1F60:01CBE74A]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 Mar 2011 21:59:03 -0000

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Brian E Carpenter
Sent: Tuesday, March 15, 2011 6:55 PM
To: james woodyatt
Cc: ipv6@ietf.org
Subject: Re: Why has RFC 4941 been designed in such a way, that it might
causeaddress conflicts?


>If you'll excuse an anecdote, while I was living in Geneva I was
regularly
>amused when the shiny new information screens in the shiny new buses
>would display the Windows IPv4 duplicate address warning instead of
>the next bus stop. Even so, the Geneva bus service hasn't come to an
end.

>My point? The probability of a duplicate address in an IPv6 subnet is
>many orders of magnitude less than it is in IPv4. Like 1 in 2^63
>instead of 1 in 2^8.

>This is just too remote a probability to worry about.

In a recent IPv6 CE Router Interop in the U.S. during mid-February 2011
where such home routers were tested in a cable broadband network IPv6
link-local addresses were found to be duplicate.  My guess is that the
Interop network had 2-30 IPv6 nodes.  Two different CE routers with
different mac-addresses created the same IPv6 link-local address.  I
don't have logs from the problem but the problem can only be one of two
things.  Either the CE did not generate its IPv6 link-local address
using EUI-64 or the CE did but the CE has a bug in the code to generate
an IPv6 link-local address using the EUI-64 format that uses the
mac-address of the CE.  The CE routers are consumer devices that will
deploy with no console.  So what admin of the network will see the CE
reporting to the CE console a DAD failure for the IPv6 link-local
address?   The SP serving this home is also clueless as to what
happened! =20

Stuff happens.  Others on this thread have reported they want to secure
their IPv6 networks.  We should collect a list of all issues operators
of networks and other folks are reporting and see if the existing
protocols are not able to help, let's see what else we can do.

Hemant

From brian.e.carpenter@gmail.com  Sun Mar 20 15:47:28 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56BA928C0FD for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 15:47:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.451
X-Spam-Level: 
X-Spam-Status: No, score=-103.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUJAXWj1NvD8 for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 15:47:27 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 657D528B23E for <ipv6@ietf.org>; Sun, 20 Mar 2011 15:47:27 -0700 (PDT)
Received: by yxk30 with SMTP id 30so2603265yxk.31 for <ipv6@ietf.org>; Sun, 20 Mar 2011 15:48:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8a/NuPb1m3JMptgbqHLtUwSwTLyYvyNLJ4tkUbdecAk=; b=D8QVOQCMRSQBPWSp0UBPv0xe3j/qshzqOU8p6Xnb/9Aeet4rJKdHrjMUu21MaRBVuG aDEwxCXstCZYii3s/vOsIaerHESQBZ72wz+f5OfpqWT0xBSzx2jsfZusXtcyHXePvUxQ T8ZHHoqZpMMy8zb6JQ7REJpDyu7MtlUnd0dgM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=O5Ysg2qhB2fvoRqzxroca8o5jA+YWPVT+6npvBhGQ/z7q3boCiYrB/XHYJARxuXnzn CSb3cC4uH3fJI5HcIdsi++kyg7fy778hgDjZ7MGoJHWgDgedJsquvlTVuvXHgBlPgNYX LMQAXp8/esdmED8Bi1lmb/4QgqAPERnq2lx3E=
Received: by 10.91.84.7 with SMTP id m7mr3195078agl.125.1300661339202; Sun, 20 Mar 2011 15:48:59 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id c4sm371121ana.23.2011.03.20.15.48.57 (version=SSLv3 cipher=OTHER); Sun, 20 Mar 2011 15:48:58 -0700 (PDT)
Message-ID: <4D868457.5060504@gmail.com>
Date: Mon, 21 Mar 2011 11:48:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de><35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com> <4D7FEE26.9060502@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 Mar 2011 22:47:28 -0000

On 2011-03-21 11:00, Hemant Singh (shemant) wrote:
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Brian E Carpenter
> Sent: Tuesday, March 15, 2011 6:55 PM
> To: james woodyatt
> Cc: ipv6@ietf.org
> Subject: Re: Why has RFC 4941 been designed in such a way, that it might
> causeaddress conflicts?
> 
> 
>> If you'll excuse an anecdote, while I was living in Geneva I was
> regularly
>> amused when the shiny new information screens in the shiny new buses
>> would display the Windows IPv4 duplicate address warning instead of
>> the next bus stop. Even so, the Geneva bus service hasn't come to an
> end.
> 
>> My point? The probability of a duplicate address in an IPv6 subnet is
>> many orders of magnitude less than it is in IPv4. Like 1 in 2^63
>> instead of 1 in 2^8.
> 
>> This is just too remote a probability to worry about.
> 
> In a recent IPv6 CE Router Interop in the U.S. during mid-February 2011
> where such home routers were tested in a cable broadband network IPv6
> link-local addresses were found to be duplicate.  My guess is that the
> Interop network had 2-30 IPv6 nodes.  Two different CE routers with
> different mac-addresses created the same IPv6 link-local address.  I
> don't have logs from the problem but the problem can only be one of two
> things.  Either the CE did not generate its IPv6 link-local address
> using EUI-64 or the CE did but the CE has a bug in the code to generate
> an IPv6 link-local address using the EUI-64 format that uses the
> mac-address of the CE.  The CE routers are consumer devices that will
> deploy with no console.  So what admin of the network will see the CE
> reporting to the CE console a DAD failure for the IPv6 link-local
> address?   The SP serving this home is also clueless as to what
> happened!  
> 
> Stuff happens.  

Yes, and paradoxically this illustrates my point. Passing a law that
addresses shall not conflict, or shall only conflict with a probability
of 1 in 2^63, is beside the point.

Others on this thread have reported they want to secure
> their IPv6 networks.  We should collect a list of all issues operators
> of networks and other folks are reporting and see if the existing
> protocols are not able to help, let's see what else we can do.

Good idea, where's the wiki?

    Brian

From shemant@cisco.com  Sun Mar 20 15:48:33 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B59E43A69CD for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 15:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.435
X-Spam-Level: 
X-Spam-Status: No, score=-10.435 tagged_above=-999 required=5 tests=[AWL=-0.436, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LcNoKOla8HtJ for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 15:48:33 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A9D4E3A69C7 for <ipv6@ietf.org>; Sun, 20 Mar 2011 15:48:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=474; q=dns/txt; s=iport; t=1300661405; x=1301871005; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=MZrv3w2jNcNpq/3R6mu1d4sFfEC26HwcbfCaGvhWPso=; b=K5Tm39vfBbwrD7zr4v8wvntAuopi46d2Jo0GRQELjx0YZRsfYGg3EN5r PV/EzxsDakG3fQMfktI8EeFe1ie10XhI2dn4nEwJvRivxZhuFgNSv/FzJ 4QQe/WySucZmTL6LByyEsnCJLjTW4HZDjfZE4VTDAopmwZFxUcQrPXBCW E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuMAAEUhhk2Q/khMgWdsb2JhbACYNI07FAEBFiYlpASbEoVjBIUziws
X-IronPort-AV: E=Sophos;i="4.63,216,1299456000"; d="scan'208";a="79974859"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 20 Mar 2011 22:50:04 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2KMo3Ge023679; Sun, 20 Mar 2011 22:50:03 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 20 Mar 2011 17:50:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Date: Sun, 20 Mar 2011 17:50:02 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B37@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Thread-Index: AcvjY/zRy0liUrQMQnmfkCWb3QB2mgD4wjmAAAKADqA=
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de><35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com><4D7FEE26.9060502@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "james woodyatt" <jhw@apple.com>
X-OriginalArrivalTime: 20 Mar 2011 22:50:03.0211 (UTC) FILETIME=[265BD1B0:01CBE751]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 Mar 2011 22:48:33 -0000

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Hemant Singh (shemant)
Sent: Sunday, March 20, 2011 6:00 PM
To: Brian E Carpenter; james woodyatt
Cc: ipv6@ietf.org
Subject: RE: Why has RFC 4941 been designed in such a way,that it might
causeaddress conflicts?

>My guess is that the Interop network had 2-30 IPv6 nodes. =20

Sorry for the typo.  Replace "2-30 IPv6 nodes" with "20-30 IPv6 nodes".

Hemant


From shemant@cisco.com  Sun Mar 20 16:08:01 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E8BD3A6A07 for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 16:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.423
X-Spam-Level: 
X-Spam-Status: No, score=-10.423 tagged_above=-999 required=5 tests=[AWL=-0.424, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kc7+zqoU5Ld for <ipv6@core3.amsl.com>; Sun, 20 Mar 2011 16:08:00 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 54A5D3A69CD for <ipv6@ietf.org>; Sun, 20 Mar 2011 16:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2382; q=dns/txt; s=iport; t=1300662570; x=1301872170; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=JEkeVUek1J1cmjzqD64ONs+DOWD7A5RJaaGYEcppLVY=; b=WVa7Jo/3diTKEa7H0EgGLEJeI12mTfRjRs6vBxDwaJf7g3+EpL7nuwJz XokXtGNE3Zma3iTBTDR0rw+NnyLewLjEEb9c3iU4n23FXnX2CeKhxIqvv YPA0yj66N98mQeHGYsvokS5t6p9Uv9tJyrC3pQ8iyXP3F713O0mDdOZq7 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvQAAHIlhk2tJXG8/2dsb2JhbACERZNvjF1ed6N/iyiDBoxmgSeDRXcEhTOLC4Mg
X-IronPort-AV: E=Sophos;i="4.63,216,1299456000"; d="scan'208";a="416312436"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by sj-iport-1.cisco.com with ESMTP; 20 Mar 2011 23:09:30 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id p2KN9UQP029144;  Sun, 20 Mar 2011 23:09:30 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 20 Mar 2011 18:09:30 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Subject: RE: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Date: Sun, 20 Mar 2011 18:09:27 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B39@XMB-RCD-109.cisco.com>
In-Reply-To: <4D868457.5060504@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Thread-Index: AcvnUQGk0zeH7K9jSN6Ye4GDL53qGQAAENGg
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de><35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com> <4D7FEE26.9060502@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com> <4D868457.5060504@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 20 Mar 2011 23:09:30.0054 (UTC) FILETIME=[DDD9EE60:01CBE753]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 Mar 2011 23:08:01 -0000

LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEJyaWFuIEUgQ2FycGVudGVyIFttYWls
dG86YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tXSANClNlbnQ6IFN1bmRheSwgTWFyY2ggMjAs
IDIwMTEgNjo0OSBQTQ0KVG86IEhlbWFudCBTaW5naCAoc2hlbWFudCkNCkNjOiBqYW1lcyB3b29k
eWF0dDsgaXB2NkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFdoeSBoYXMgUkZDIDQ5NDEgYmVlbiBk
ZXNpZ25lZCBpbiBzdWNoIGEgd2F5LCB0aGF0IGl0IG1pZ2h0IGNhdXNlYWRkcmVzcyBjb25mbGlj
dHM/DQoNCg0KPkdvb2QgaWRlYSwgd2hlcmUncyB0aGUgd2lraT8NCg0KQWgsIG5vbmUgdGhhdCBJ
IGtub3cgb2YuICBBbHNvLCBJIGFtIG9ubHkgY2F0Y2hpbmcgdXAgdG8gNm1hbiBlbWFpbCB0aGlz
IHdlZWtlbmQgYmVpbmcgYnVzeSBpbiB0aGUgd2VlayB3aXRoIHY2b3BzIGVtYWlscy4gIElmIGEg
d2lraSBkb2VzIG5vdCBleGlzdCBmb3Igc3VjaCBpc3N1ZXMsIHdlIGNvdWxkIHN0YXJ0IG9uZS4g
IFNpbmNlIG91ciBjYWJsZSBJUHY2IGhvbWUgZGV2aWNlcyBzdWNoIGFzIGNhYmxlIG1vZGVtcyBh
bmQgSVB2NiBDRSBSb3V0ZXJzIChzdGFuZGFsb25lIG9yIGNvbWJpbmVkIGluc2lkZSBhIG1vZGVt
KSBhcmUgYXNzdW1lZCB0byBwcm92aWRlIG5vIGNvbnNvbGUsIHdlIGhhdmUgc3BlY2lmaWVkIHVz
ZSBvZiBhIERBRCBQcm94eSBhdCB0aGUgZmlyc3QtaG9wIElQdjYgcm91dGVyLiAgVGhpcyBmaXJz
dC1ob3Agcm91dGVyIGlzIGFsc28gdGhlIGFjY2VzcyBjb25jZW50cmF0b3IgKGEgQ01UUyAtIENh
YmxlIE1vZGVtIFRlcm1pbmF0aW9uIFN5c3RlbSkgZm9yIGNhYmxlIGJyb2FkYmFuZC4gIE5vdGUg
c2luY2UgdGhlIGNhYmxlIG5ldHdvcmsgaXMgYW4gZW5kLXRvLWVuZCBJUCBuZXR3b3JrLCBpdCBp
cyBlYXNpZXIgZm9yIGNhYmxlIHRvIHNwZWNpZnkgc3VwcG9ydCBmb3IgREFEIFByb3h5IGF0IHRo
ZSBDTVRTLiAgRFNMIHdoaWNoIGlzIG5vdCBlbmQtdG8tZW5kIGF0IHRoZSBJUCBsYXllciBoYXMg
bW9yZSBpc3N1ZXMgdG8gZGVhbCB3aXRoLiAgVGhlIHJlYXNvbiBpcyB0aGF0IGEgU1AgaGFzIGNv
bnNvbGUgYWNjZXNzIHRvIHRoZSBDTVRTIGFuZCBpZiB0aGUgQ01UUyBzdXBwb3J0cyBhIERBRCBQ
cm94eSwgdGhlIFNQIGF0IGxlYXN0IGtub3dzIHdoaWNoIGhvbWUgdGhlIGZhaWx1cmUgaGFzIG9j
Y3VycmVkIGluIGFuZCB0YWtlIHNvbWUgYWN0aW9uLiAgV2l0aG91dCB0aGUgQ01UUyBzdXBwb3J0
aW5nIERBRCBwcm94eSwgdGhlIERBRCBmYWlsdXJlIGZvciBhIG1vZGVtIG9yIENFIGZlc3RlcnMg
Zm9yIGFuIGVycm9yIHdpdGggdGhlIG1vZGVtIG9yIENFIGRlYWQgaW4gdGhlIHdhdGVyLiAgIE9m
IGNvdXJzZSwgdGhlIGhvbWUgY3VzdG9tZXIgd291bGQgY2FsbCB0aGUgU1AgaW4gc3VjaCBhIHNp
dHVhdGlvbiBidXQgaXQncyBiZXR0ZXIgZm9yIHRoZSBTUCB0byBiZSBwcm9hY3RpdmUgdG8gY2F0
Y2ggdGhlIGVycm9yIGJlZm9yZSBhbnkgaG9tZSB1c2VyIGNhbGxzLiAgDQoNCkl0J3MgYWxzbyBp
bnRlcmVzdGluZyB0aGF0IGV2ZW4gd2hlbiB0aGUgU1AgaGFzIGRldGVjdGVkIGEgREFEIER1cGxp
Y2F0ZSwgd2hhdCBkb2VzIHRoZSBTUCBkbyBiZXNpZGVzIHNodXR0aW5nIGRvd24gb25lIG9mIHRo
ZSB0d28gbm9kZXMgdGhhdCBjbGFzaGVkIGZvciB0aGUgc2FtZSBJUHY2IGxpbmstbG9jYWwgYWRk
cmVzcy4gIA0KDQpUaGFua3MsDQoNCkhlbWFudA0K

From twinters@iol.unh.edu  Mon Mar 21 08:17:44 2011
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40DE28C14F for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 08:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.298
X-Spam-Level: 
X-Spam-Status: No, score=-6.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gQZyVqKSwSe9 for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 08:17:43 -0700 (PDT)
Received: from exprod5og113.obsmtp.com (exprod5og113.obsmtp.com [64.18.0.26]) by core3.amsl.com (Postfix) with SMTP id 77A873A6881 for <ipv6@ietf.org>; Mon, 21 Mar 2011 08:17:43 -0700 (PDT)
Received: from source ([132.177.123.84]) by exprod5ob113.postini.com ([64.18.4.12]) with SMTP ID DSNKTYdsVCixw1dRNg1e5HjhmiFbWrnlmyDZ@postini.com; Mon, 21 Mar 2011 08:19:16 PDT
Received: from optimus.iol.unh.edu (optimus.iol.unh.edu [132.177.118.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by postal.iol.unh.edu (Postfix) with ESMTPSA id 15FB521F056; Mon, 21 Mar 2011 11:18:44 -0400 (EDT)
Subject: Re: Why has RFC 4941 been designed in such a way, that it might causeaddress conflicts?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-5-290977250
From: Timothy Winters <twinters@iol.unh.edu>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B39@XMB-RCD-109.cisco.com>
Date: Mon, 21 Mar 2011 11:18:44 -0400
Message-Id: <6D0CE79E-9651-45A9-B094-057D5ED6EFCE@iol.unh.edu>
References: <C744C51B-F2B0-4137-B39F-54B8D62F1C97@equinux.de>	<E7CFEDBC-5048-413E-93C9-DBF79B4FC238@apple.com>	<E8CD61BF-827E-4A83-AA63-275D0CCB0B53@equinux.de><35A891E0-9BA1-4694-AFA3-C6C46C8F3625@apple.com> <4D7FEE26.9060502@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B1F@XMB-RCD-109.cisco.com> <4D868457.5060504@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3010D2B39@XMB-RCD-109.cisco.com>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1082)
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 Mar 2011 15:17:45 -0000

--Apple-Mail-5-290977250
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello,
	The UNH-IOL has made a white paper from the event available on =
the IPv6 homepage.  As Hemant stated there were issues discovered around =
DAD and the need for it.

Regards,
Tim

On Mar 20, 2011, at 7:09 PM, Hemant Singh (shemant) wrote:

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
> Sent: Sunday, March 20, 2011 6:49 PM
> To: Hemant Singh (shemant)
> Cc: james woodyatt; ipv6@ietf.org
> Subject: Re: Why has RFC 4941 been designed in such a way, that it =
might causeaddress conflicts?
>=20
>=20
>> Good idea, where's the wiki?
>=20
> Ah, none that I know of.  Also, I am only catching up to 6man email =
this weekend being busy in the week with v6ops emails.  If a wiki does =
not exist for such issues, we could start one.  Since our cable IPv6 =
home devices such as cable modems and IPv6 CE Routers (standalone or =
combined inside a modem) are assumed to provide no console, we have =
specified use of a DAD Proxy at the first-hop IPv6 router.  This =
first-hop router is also the access concentrator (a CMTS - Cable Modem =
Termination System) for cable broadband.  Note since the cable network =
is an end-to-end IP network, it is easier for cable to specify support =
for DAD Proxy at the CMTS.  DSL which is not end-to-end at the IP layer =
has more issues to deal with.  The reason is that a SP has console =
access to the CMTS and if the CMTS supports a DAD Proxy, the SP at least =
knows which home the failure has occurred in and take some action.  =
Without the CMTS supporting DAD proxy, the DAD failure for a modem or CE =
festers for an
>  error with the modem or CE dead in the water.   Of course, the home =
customer would call the SP in such a situation but it's better for the =
SP to be proactive to catch the error before any home user calls. =20
>=20
> It's also interesting that even when the SP has detected a DAD =
Duplicate, what does the SP do besides shutting down one of the two =
nodes that clashed for the same IPv6 link-local address. =20
>=20
> Thanks,
>=20
> Hemant
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail-5-290977250
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hello,<div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>The UNH-IOL has made a&nbsp;white paper from the =
event&nbsp;available on the IPv6&nbsp;<a =
href=3D"http://www.iol.unh.edu/services/testing/ipv6/">homepage</a>. =
&nbsp;As Hemant stated there were issues discovered around DAD and the =
need for =
it.</div><div><br></div><div>Regards,</div><div>Tim</div><div><div>
</div>
<br><div><div>On Mar 20, 2011, at 7:09 PM, Hemant Singh (shemant) =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>-----Original Message-----<br>From: Brian E Carpenter =
[mailto:brian.e.carpenter@gmail.com] <br>Sent: Sunday, March 20, 2011 =
6:49 PM<br>To: Hemant Singh (shemant)<br>Cc: james woodyatt; <a =
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Subject: Re: Why has =
RFC 4941 been designed in such a way, that it might causeaddress =
conflicts?<br><br><br><blockquote type=3D"cite">Good idea, where's the =
wiki?<br></blockquote><br>Ah, none that I know of. &nbsp;Also, I am only =
catching up to 6man email this weekend being busy in the week with v6ops =
emails. &nbsp;If a wiki does not exist for such issues, we could start =
one. &nbsp;Since our cable IPv6 home devices such as cable modems and =
IPv6 CE Routers (standalone or combined inside a modem) are assumed to =
provide no console, we have specified use of a DAD Proxy at the =
first-hop IPv6 router. &nbsp;This first-hop router is also the access =
concentrator (a CMTS - Cable Modem Termination System) for cable =
broadband. &nbsp;Note since the cable network is an end-to-end IP =
network, it is easier for cable to specify support for DAD Proxy at the =
CMTS. &nbsp;DSL which is not end-to-end at the IP layer has more issues =
to deal with. &nbsp;The reason is that a SP has console access to the =
CMTS and if the CMTS supports a DAD Proxy, the SP at least knows which =
home the failure has occurred in and take some action. &nbsp;Without the =
CMTS supporting DAD proxy, the DAD failure for a modem or CE festers for =
an<br> &nbsp;error with the modem or CE dead in the water. =
&nbsp;&nbsp;Of course, the home customer would call the SP in such a =
situation but it's better for the SP to be proactive to catch the error =
before any home user calls. &nbsp;<br><br>It's also interesting that =
even when the SP has detected a DAD Duplicate, what does the SP do =
besides shutting down one of the two nodes that clashed for the same =
IPv6 link-local address. =
&nbsp;<br><br>Thanks,<br><br>Hemant<br>-----------------------------------=
---------------------------------<br>IETF IPv6 working group mailing =
list<br><a =
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Administrative =
Requests: =
https://www.ietf.org/mailman/listinfo/ipv6<br>----------------------------=
----------------------------------------<br></div></blockquote></div><br><=
/div></body></html>=

--Apple-Mail-5-290977250--

From bob.hinden@gmail.com  Mon Mar 21 10:16:01 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E7013A68C6 for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 10:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.537
X-Spam-Level: 
X-Spam-Status: No, score=-103.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6mRxwZq9LYg for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 10:16:00 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 7818F3A68B3 for <ipv6@ietf.org>; Mon, 21 Mar 2011 10:16:00 -0700 (PDT)
Received: by ywi6 with SMTP id 6so2995828ywi.31 for <ipv6@ietf.org>; Mon, 21 Mar 2011 10:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=BTFIRIikanANDhCdU4ZLQiWVR/DYAKp8M+LEh1QC+Bw=; b=g45A75eZwaG67uomVxOQDVWavjWbAyCh5DX4TUdZqhfRz3Tvce3JRcUcHXbI3F0d87 sK4kro7/+g0bjkt2bdN8Jp4Asnn4bPnB5+BClmI2SU1AIyDcSeNWv7pKLue/EgbECPuG RZDiYVyux4vMJLRiyKcvscNtgbxaMW15hV0yA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=O4zDRpx1bzDDycpuHbtM/VYQaVr0XLF3eOhRSUJsBiu8eEfS7cBIcGpz2pauwXfZxp Dh5cQGz+SRs41LtPryKxuI6n3MA6+PODxE6R62zON7W3R4agwyrv8AmwpN9xyBRl54Gr 325fkwgtJ8OEaOlvck6bY5+zGXNvpEFxBPZ04=
Received: by 10.43.59.80 with SMTP id wn16mr7677720icb.67.1300727750503; Mon, 21 Mar 2011 10:15:50 -0700 (PDT)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id i20sm3815550iby.14.2011.03.21.10.15.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Mar 2011 10:15:46 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6MAN WG Last Call: <draft-ietf-6man-flow-update-04.txt>
Date: Mon, 21 Mar 2011 10:15:42 -0700
Message-Id: <2F8FF78F-24CF-4895-A5BC-EA4167D92C6D@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 Mar 2011 17:16:01 -0000

All,

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

	Title           : Rationale for update to the IPv6 flow label =
specification
	Author(s)       : S. Amante, et al.
	Filename        : draft-ietf-6man-flow-update-04.txt
	Pages           : 12
	Date            : 2011-03-13
=09
      http://tools.ietf.org/html/draft-ietf-6man-flow-update-04

as an Informational RFC.  Substantive comments and statements of support =
for advancing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 4 April 2011.

Regards,
Bob Hinden & Brian Haberman
6MAN Chairs


From brian.e.carpenter@gmail.com  Mon Mar 21 13:09:55 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 77A7028C15D for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 13:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.454
X-Spam-Level: 
X-Spam-Status: No, score=-103.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbhgnnJ7M2I4 for <ipv6@core3.amsl.com>; Mon, 21 Mar 2011 13:09:48 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 58F5D28C156 for <ipv6@ietf.org>; Mon, 21 Mar 2011 13:09:48 -0700 (PDT)
Received: by wwa36 with SMTP id 36so5287815wwa.13 for <ipv6@ietf.org>; Mon, 21 Mar 2011 13:11:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=vvcMP5x/lIA93pxU1L+12AoTLV86tZdf9KwCyI4P38w=; b=H/IFcLBpG5yriQqrgWAcbBwQe53eMpTBpzKyzinHSuhTDbd8qzaPM1QcXkd4yFVBEt hkQiVhZj+o4xtLq52f+DRtygJ04wVTfk/4C9LH+st44+9e0A9uvHurmAaNjzISaJfZte zQLd+duOA9RQeZVVNgzOivH3o0tCLeFX36z8Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; b=ugfGy89R7/kpGxQUxnLk+DN1MBrb1+Pd8DADPx7/Y8ezdt5weVztfXoSyfljYxgzEU vKwYdrPSW4ECSQJ/htboRDOnbk11pwrz6O2/MGTsN5IB7tW2wFTMM/DhXP7bvRUeJScU dGWS2/ioqphU2IVptGUFza2mDsX9NJmRiY+zQ=
Received: by 10.227.100.219 with SMTP id z27mr4460604wbn.45.1300738280489; Mon, 21 Mar 2011 13:11:20 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id ed10sm2911781wbb.49.2011.03.21.13.11.18 (version=SSLv3 cipher=OTHER); Mon, 21 Mar 2011 13:11:19 -0700 (PDT)
Message-ID: <4D87B0E3.5080005@gmail.com>
Date: Tue, 22 Mar 2011 09:11:15 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: [Fwd: Re: Informational RFC to be: <draft-hu-flow-label-cases-03.txt>]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 Mar 2011 20:09:55 -0000

FYI - this was an Independent Submission to the RFc Editor.

   Brian

-------- Original Message --------
Subject: Re: Informational RFC to be: <draft-hu-flow-label-cases-03.txt>
Date: Mon, 21 Mar 2011 11:02:27 -0700
From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>
CC: iana@iana.org, The IESG <iesg@ietf.org>, ietf-announce@ietf.org

The IESG has no problem with the publication of 'Survey of proposed use
cases for the IPv6 flow label' <draft-hu-flow-label-cases-03.txt> as an
Informational RFC.

The IESG would also like the RFC-Editor to review the comments in
the datatracker
(http://datatracker.ietf.org/doc/draft-hu-flow-label-cases/) related to
this document and determine whether or not they merit incorporation into
the document. Comments may exist in both the ballot and the comment log.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-hu-flow-label-cases/

The process for such documents is described at
http://www.rfc-editor.org/indsubs.html

Thank you,

The IESG Secretary




Technical Summary

   This document describes the current limitations of the flow label field
   in IPv6, and explains known proposals with respect to those limitations.

Working Group Summary

   This topic has been discussed in the 6MAN working group, but this
   document is an independent submission, not a WG product.

Document Quality

   Not applicable. The responsible Area Director believes that the
   document is useful to publish.

Personnel

   The responsible Area Director is Jari Arkko.

IESG Note

  The IESG believes that this document is related to the work done in the
  6MAN working group, but this does not prevent publishing.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From bob.hinden@gmail.com  Tue Mar 22 11:31:21 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5513528C0F9 for <ipv6@core3.amsl.com>; Tue, 22 Mar 2011 11:31:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOAvKhG5O3JA for <ipv6@core3.amsl.com>; Tue, 22 Mar 2011 11:31:20 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by core3.amsl.com (Postfix) with ESMTP id 9D02D28C143 for <ipv6@ietf.org>; Tue, 22 Mar 2011 11:31:20 -0700 (PDT)
Received: by pxi20 with SMTP id 20so1230907pxi.27 for <ipv6@ietf.org>; Tue, 22 Mar 2011 11:32:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=vYquXyl0fqFqeYa4ZsMf0KsXHO2fSsGd6c6txAdDPb0=; b=VaimjuE25jK6EhMqhnSDA1cpt5ah6UD5QZsMPe7GuUcPc4lJvl8si6ueRHMt/+Zf83 Et8DdH3w/DeE5+g9ZacOwYrSw8Bcf4amUp3nHCXNX0h406eGQO6GIXlCiL2f0s8FW+LO O+LKevpzCBE6iCl2lzL1a3HXq5C5zwe9C1ywA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=mhUhEZyr0IRUs2d585sKg1suni94yMvYk5DUfastdRAQlqZuf7IRvUZIKPhXFWMZSO sgzbt90g1F6k6QzFM6JGE2+6vfQ7/oh3ZNdl5dT1f+gHNI8UJ4SMjY3w5IfkpyEWMWlt cSZ9k2gCGrSiDJgZpXGC4NTV4NA0BhoNVbLHw=
Received: by 10.143.137.4 with SMTP id p4mr4124442wfn.79.1300818774009; Tue, 22 Mar 2011 11:32:54 -0700 (PDT)
Received: from [10.242.58.206] (m170436d0.tmodns.net [208.54.4.23]) by mx.google.com with ESMTPS id o11sm8973025wfa.0.2011.03.22.11.32.49 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Mar 2011 11:32:50 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Need minute taker and jabber scribe(s)
Date: Tue, 22 Mar 2011 11:32:47 -0700
Message-Id: <A4ED6B87-1BA6-4812-A9DB-B85B096BF65D@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 Mar 2011 18:31:21 -0000

We are looking for volunteers to take minutes and jabber scribe for the =
6man session on Monday morning in Prague.

It a great service to the working group and the IETF!

Thanks,
Bob & Brian



From fernando.gont.netbook.win@gmail.com  Thu Mar 24 21:29:26 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BD893A6943 for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 21:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KuhhmJPhP6ZG for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 21:29:25 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id EC6153A6946 for <ipv6@ietf.org>; Thu, 24 Mar 2011 21:29:24 -0700 (PDT)
Received: by yxk30 with SMTP id 30so356149yxk.31 for <ipv6@ietf.org>; Thu, 24 Mar 2011 21:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=XR5n4m0L8e6dye2xxexx7Em9tvAvYHMhAhxYAcF0UGs=; b=MJkcSmdVQuD20Vie4+lSuAUgJMj9L54eqbJYfNsylzqQmGdy4GHmb6C4JMFMS98tgy iUvavguiQuiocqEpm7875OJ6LpX9eCsXmc0WY0MrJmqcaIsjvBaPW5NZjxFvR5L1wl3Y +OnVRNXNtCnLJFHmv/zJBqemdgHVImAVO867I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=PaYT4LVfzFGTkQnWE9LiVoyR/7K8oGMSj7Uayqy+PFLR0QyYHHeT74GJnKQUrcd3tp I6cU7T5uLp90VoI4U8O45aQFHmcbw2w0p4CE4prhim0zud0N4EKn11bB4gYREkE1EjPt zzgabFeLIXoOmgtijhhR2UTMizywmyqAN7Yjg=
Received: by 10.101.55.11 with SMTP id h11mr254154ank.52.1301027459696; Thu, 24 Mar 2011 21:30:59 -0700 (PDT)
Received: from [192.168.123.101] ([190.48.254.9]) by mx.google.com with ESMTPS id b28sm654597anb.22.2011.03.24.21.30.53 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Mar 2011 21:30:56 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D8C1A78.4010505@gont.com.ar>
Date: Fri, 25 Mar 2011 01:30:48 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com>	<alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D7B5914.6090000@gont.com.ar> <4D80EAAF.6010509@hp.com>
In-Reply-To: <4D80EAAF.6010509@hp.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ran Atkinson <ran.atkinson@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 Mar 2011 04:29:26 -0000

On 16/03/2011 01:51 p.m., Brian Haley wrote:

> I have an almost off-topic comment, but since I've seen no mention of it
> in any of these privacy threads...
> 
> You have to assume in a large data center that almost every MAC address you
> encounter is going to be randomly generated.  

Are they actually random? i.e., I'm curious about the algorithm used for
generating the Interface IDs.


> This is because there are
> *lots* of virtual machines out there, and the density of them is increasing
> exponentially.  Their MACs could change daily as they are deployed and
> decommissioned, but from their perspective their MAC is hardware-based.
> I know you have this as a "SHOULD" requirement, but figured I should mention
> it since it's one of those places where this bit will be completely ignored.

>From the point of view of the VMs, they would still be using Modified
EUI-64 Interface Identifiers. This is not that different from the case
in which the admin sets the MAC address of an interface to some value
that he wants (other than the *real* address of the interface). IMHO,
this is out-of-scope for this document.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From fernando.gont.netbook.win@gmail.com  Thu Mar 24 23:55:19 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DDE03A6964 for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 23:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0WRLbd6dSSQ for <ipv6@core3.amsl.com>; Thu, 24 Mar 2011 23:55:18 -0700 (PDT)
Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by core3.amsl.com (Postfix) with ESMTP id 2666E3A6811 for <ipv6@ietf.org>; Thu, 24 Mar 2011 23:55:18 -0700 (PDT)
Received: by gwb15 with SMTP id 15so479021gwb.27 for <ipv6@ietf.org>; Thu, 24 Mar 2011 23:56:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:x-enigmail-version:openpgp:content-type :content-transfer-encoding; bh=W+Sjej0kwV5Z6SFBl8iMFhcGrpCF1iBPsx3eyPInjS8=; b=FLLpGqf2Mb5ARMhd5wwL2aonrUtyZDJoMx4xgSWHSiXLPKNKuQio+3aYApbmCZDs6V bMQ594eD4cklCaWWPZKqqu+CQXb/FIz8EG90zO3LuIHC99qxt6BQN9HS9jN8GXKv4psD lSoiDBgdTixQnLcvIfoDOv51ZCFPsBgEXx32Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=J2FTZw1qGnTkhE7m7jo9yoes4dRY42ce8xyfbTu8YFSqWqLiMHWFnvDyGkoTHh2+qs Zr6fDlHxbbHdIILtBileKjxRoV0zGLY9pZOtPcQlvq0WWB9g1HNzFMPzlhLZXUwJFVHD 9xSPgMGVZS8fwibJ7UryxSKXx7qk0qaali+Zg=
Received: by 10.236.185.138 with SMTP id u10mr562374yhm.248.1301036213049; Thu, 24 Mar 2011 23:56:53 -0700 (PDT)
Received: from [192.168.123.100] ([190.48.254.192]) by mx.google.com with ESMTPS id g2sm383511yhc.76.2011.03.24.23.56.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Mar 2011 23:56:52 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D8C3CAD.8010509@gont.com.ar>
Date: Fri, 25 Mar 2011 03:56:45 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Upcoming revision of draft-gont-6man-managing-privacy-extensions
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 Mar 2011 06:55:19 -0000

Folks,

I have been working on a revision of the aforementioned I-D. It
incorporates the changes and clarifications suggested on-list during the
recent discussions of this I-D on the mailing-list.

The upcoming revision is available at:

* TXT format:
<http://www.gont.com.ar/drafts/address-generation/draft-gont-6man-managing-privacy-extensions-02b.txt>
* PDF format:
<http://www.gont.com.ar/drafts/address-generation/draft-gont-6man-managing-privacy-extensions-02b.pdf>

For your convenience, the diff between this upcoming rev and the last
posted version (-01) is available here:
<http://www.gont.com.ar/drafts/address-generation/diff-from-version-01.html>

Any comments will be more than welcome.

In particular, I'd like to hear if folks who have made suggestions for
improvements think this upcoming rev has successfully incorporated them
(and, if they feel it has not, please provide advice on how to do it).

Thanks!

P.S.: If you're using wget to get any of the aforementioned files,
please use the "user-agent" option to "forge" a different "User-agent"
tag. e.g.,

wget --user-agent='Mozilla/4.0 (compatible; MSIE 5.5; OMG MB; Windows
98)'
http://www.gont.com.ar/drafts/address-generation/draft-gont-6man-managing-privacy-extensions-02b.txt

as my web-hosting provider is currently blocking "wget" access (not that
I agree with their policy).

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From ipng@69706e6720323030352d30312d31340a.nosense.org  Fri Mar 25 00:20:02 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 236973A696C for <ipv6@core3.amsl.com>; Fri, 25 Mar 2011 00:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.575
X-Spam-Level: 
X-Spam-Status: No, score=-1.575 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckUBvOeRWxdE for <ipv6@core3.amsl.com>; Fri, 25 Mar 2011 00:20:01 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id B84863A696A for <ipv6@ietf.org>; Fri, 25 Mar 2011 00:20:00 -0700 (PDT)
Received: from 182-239-157-177.ip.adam.com.au ([182.239.157.177] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1Q31Ke-00043l-IB; Fri, 25 Mar 2011 17:51:16 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id E990E530DB; Fri, 25 Mar 2011 17:51:15 +1030 (CST)
Date: Fri, 25 Mar 2011 17:51:15 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: draft-gont-6man-managing-privacy-extensions-00.txt
Message-ID: <20110325175115.67f6e91e@opy.nosense.org>
In-Reply-To: <4D8C1A78.4010505@gont.com.ar>
References: <7111FC5F-BC3F-4242-9C3F-037E79894749@gmail.com> <alpine.DEB.1.10.1103091212570.7942@uplift.swm.pp.se> <4D7B5914.6090000@gont.com.ar> <4D80EAAF.6010509@hp.com> <4D8C1A78.4010505@gont.com.ar>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Brian Haley <brian.haley@hp.com>, ipv6@ietf.org, Ran Atkinson <ran.atkinson@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 Mar 2011 07:20:02 -0000

On Fri, 25 Mar 2011 01:30:48 -0300
Fernando Gont <fernando@gont.com.ar> wrote:

> On 16/03/2011 01:51 p.m., Brian Haley wrote:
> 
> > I have an almost off-topic comment, but since I've seen no mention of it
> > in any of these privacy threads...
> > 
> > You have to assume in a large data center that almost every MAC address you
> > encounter is going to be randomly generated.  
> 
> Are they actually random? i.e., I'm curious about the algorithm used for
> generating the Interface IDs.
> 

Here's the routine typically used under Linux to generate these types
of addresses -

include/linux/etherdevice.h

/**
 * random_ether_addr - Generate software assigned random Ethernet
address
 * @addr: Pointer to a six-byte array containing the Ethernet address
 *
 * Generate a random Ethernet address (MAC) that is not multicast
 * and has the local assigned bit set.
 */
static inline void random_ether_addr(u8 *addr)
{
        get_random_bytes (addr, ETH_ALEN);
        addr [0] &= 0xfe;       /* clear multicast bit */
        addr [0] |= 0x02;       /* set local assignment bit (IEEE802) */
}



> 
> > This is because there are
> > *lots* of virtual machines out there, and the density of them is increasing
> > exponentially.  Their MACs could change daily as they are deployed and
> > decommissioned, but from their perspective their MAC is hardware-based.
> > I know you have this as a "SHOULD" requirement, but figured I should mention
> > it since it's one of those places where this bit will be completely ignored.
> 
> From the point of view of the VMs, they would still be using Modified
> EUI-64 Interface Identifiers. This is not that different from the case
> in which the admin sets the MAC address of an interface to some value
> that he wants (other than the *real* address of the interface). IMHO,
> this is out-of-scope for this document.
> 
> Thanks!
> 
> Best regards,
> -- 
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> 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
> --------------------------------------------------------------------

From bob.hinden@gmail.com  Fri Mar 25 13:43:10 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A371C28C0EB for <ipv6@core3.amsl.com>; Fri, 25 Mar 2011 13:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id alcG+02ARC4Z for <ipv6@core3.amsl.com>; Fri, 25 Mar 2011 13:43:09 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id C5D5828C0E9 for <ipv6@ietf.org>; Fri, 25 Mar 2011 13:43:09 -0700 (PDT)
Received: by iye19 with SMTP id 19so1046862iye.31 for <ipv6@ietf.org>; Fri, 25 Mar 2011 13:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=4c0X0XCwgv9I9oJxQwuTixRNYvDWGUDvyKoES9WUGM8=; b=XRKYT0WkPyWD0n6R++nIL4AbsdETaCulAzWE1wVpBufYU5TwaT7jQk6FfJhLBK2jXm Ct4mt27bkVmibHOwLO17Ir/xJJogIEHv+lGGx1Bq57lzKYntBZQ2tsGxQIweZJOMMxsi jOXODaYwDmWRScx7mOge/LIEQ0Tg5OCCNaKt4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=KkaiLNbcT2qJSIltCkbZcSaNaPmYGTU/f4lfbadXzshvjgOM406lpgAC2x7iApCVyj Dck3qGZTTMil1RIDVCymzYs4S7KbBptNRnzcDPg43Zu4s48XqQGutVorqzv/h3bBNaB3 m7wMzzfq6MD550Eiyr0iDXGLv+7giuv2MtwN0=
Received: by 10.231.193.233 with SMTP id dv41mr1193176ibb.186.1301085885323; Fri, 25 Mar 2011 13:44:45 -0700 (PDT)
Received: from [10.12.209.126] ([217.194.73.178]) by mx.google.com with ESMTPS id d10sm870258ibb.51.2011.03.25.13.44.41 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 25 Mar 2011 13:44:42 -0700 (PDT)
Subject: Re: Need minute taker and jabber scribe(s)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <A4ED6B87-1BA6-4812-A9DB-B85B096BF65D@gmail.com>
Date: Fri, 25 Mar 2011 21:44:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A499E9A-FAF5-450E-8F35-6EB30424D981@gmail.com>
References: <A4ED6B87-1BA6-4812-A9DB-B85B096BF65D@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 Mar 2011 20:43:10 -0000

We still need a jabber scribe.=20

Thanks to Suresh for volunteering to take minutes.

Thanks,
Bob


On Mar 22, 2011, at 7:32 PM, Bob Hinden wrote:

> We are looking for volunteers to take minutes and jabber scribe for =
the 6man session on Monday morning in Prague.
>=20
> It a great service to the working group and the IETF!
>=20
> Thanks,
> Bob & Brian
>=20
>=20


From arifumi@nttv6.net  Sat Mar 26 23:58:35 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20EEB3A69A0 for <ipv6@core3.amsl.com>; Sat, 26 Mar 2011 23:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.987
X-Spam-Level: 
X-Spam-Status: No, score=-101.987 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIX2PMSH5PTS for <ipv6@core3.amsl.com>; Sat, 26 Mar 2011 23:58:32 -0700 (PDT)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by core3.amsl.com (Postfix) with ESMTP id 2D6993A699A for <ipv6@ietf.org>; Sat, 26 Mar 2011 23:58:32 -0700 (PDT)
Received: from [IPv6:::1] (localhost.nttv6.net [IPv6:::1]) by leo.nttv6.net (8.14.4/8.14.3) with ESMTP id p2R6wgKX076142; Sun, 27 Mar 2011 15:58:42 +0900 (JST) (envelope-from arifumi@nttv6.net)
References: <alpine.LRH.2.02.1101031151250.23654@netcore.fi>	<20110103204031.0c3589b7@opy.nosense.org> <alpine.LRH.2.02.1101031213060.23654@netcore.fi> <4D2223DB.1000708@gmail.com>
In-Reply-To: <4D2223DB.1000708@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
Message-Id: <49BBE77F-7339-4916-A005-EC3FE0227709@nttv6.net>
Content-Transfer-Encoding: 7bit
From: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: addrsel: privacy addresses within/out of a site
Date: Sun, 27 Mar 2011 15:58:42 +0900
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 06:58:35 -0000

Hi,

Sorry for replying to an oooold thread.

A privacy address will also be generated for a ULA prefix,
because it is treated just like a global prefix, right ?

On 2011/01/04, at 4:30, Brian E Carpenter wrote:

> Pekka,
> 
> Wouldn't the rule "Use ULA prefix inside the site and PA prefix (with
> privacy addresses if desired) otherwise" be simpler? And, by default,
> it would prevent the "inside" address being exported by mistake.
> 
> Regards
>   Brian
> 
> 
> On 2011-01-03 23:21, Pekka Savola wrote:
>> On Mon, 3 Jan 2011, Mark Smith wrote:
>>>> "do not use privacy addresses when communicating inside the site [a
>>>> set of
>>>> designated destination prefixes], use it by default otherwise"
>>>> 
>>> 
>>> I'd be curious what the benefits are.
>>> 
>>> The only reason I could think of as to why to do this is to be able to
>>> associate internal application access logs with internal hosts. At face
>>> value that sounds useful, however if you really care about auditing
>>> application access and use, it isn't the hosts you need to worry about,
>>> but the people behind them - and they can usually easily change hosts.
>>> So I think those applications should be using proper AAA to identify the
>>> user, rather than using IPv6 host identifiers as very poor substitutes
>>> for user identities.
>> 
>> One use case is administrators running ssh, vnc or some such remote
>> management to the client OS.  The conclusion from looking at various
>> similar cases was that systems need to have a well-known (non-privacy)
>> IP where they can be reached and run TCP services at, or the privacy IP
>> needs to be stored in DNS (not much point in that..).
>> 
>> Also, many site-internal access control mechanisms (for example,
>> hosts.allow for ssh, some others for e.g. web browsing) use
>> host-specific IPs in addition to other checks.  In some cases these
>> could be substituted with stronger upper-layer identities e.g with
>> certificates.
>> 
>> On the other hand, user identification due to static EU64 is a little
>> bit of concern e.g. with web surfing, but this also applies to other
>> applications so the issue does not go away with application-specific
>> tuning.
>> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From bob.hinden@gmail.com  Sun Mar 27 00:11:00 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25A723A69AC for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 00:11:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjqqF5RDT4SS for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 00:10:59 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id AC3253A69A7 for <ipv6@ietf.org>; Sun, 27 Mar 2011 00:10:58 -0700 (PDT)
Received: by wyb29 with SMTP id 29so1765795wyb.31 for <ipv6@ietf.org>; Sun, 27 Mar 2011 00:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=s4TkYnz/Z/lxrKa0anFo1S0/vrNllt44cYiS4GRtqkY=; b=GTEEMDf3THPXXF2E3EKJZFALX9Lkmmb/UjuwAf1PIXPApnPAqISpcVB68nmfTHffQV L0xLz+u+hB2/7CB9qnDmw8ME3KecrbMGG0IuPPDEEWBNKdFbNL9ahTBqJeSsGwEx0pDA pSu2JEm0++Mr4v3PNv6vI2aOualLjX7FAO0Lo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=bybMO5E4RG/H0IOi50qhAClP+2I9pDTkLMcr7aVouEwYeeItjYDWwVHwmkcA40aZrJ p4OXpfCxKabHMCYxOJxjZMOJDZvK9xjZvF/KPuqugEzAuQkxWR2n1X8Q7TRC7jEbfW8m Wc+IJ5fcGDAra9IPE5egIYcC0HZgSGIxqaWgo=
Received: by 10.216.82.68 with SMTP id n46mr2556256wee.57.1301209954696; Sun, 27 Mar 2011 00:12:34 -0700 (PDT)
Received: from dhcp-47af.meeting.ietf.org (dhcp-47af.meeting.ietf.org [130.129.71.175]) by mx.google.com with ESMTPS id b54sm983335wer.45.2011.03.27.00.12.32 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Mar 2011 00:12:33 -0700 (PDT)
Subject: Re: addrsel: privacy addresses within/out of a site
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <49BBE77F-7339-4916-A005-EC3FE0227709@nttv6.net>
Date: Sun, 27 Mar 2011 09:12:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F74C01F-4A6D-4AB5-8DF8-D6C2D6694455@gmail.com>
References: <alpine.LRH.2.02.1101031151250.23654@netcore.fi>	<20110103204031.0c3589b7@opy.nosense.org> <alpine.LRH.2.02.1101031213060.23654@netcore.fi> <4D2223DB.1000708@gmail.com> <49BBE77F-7339-4916-A005-EC3FE0227709@nttv6.net>
To: Arifumi Matsumoto <arifumi@nttv6.net>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 07:11:00 -0000

On Mar 27, 2011, at 8:58 AM, Arifumi Matsumoto wrote:

> Hi,
>=20
> Sorry for replying to an oooold thread.
>=20
> A privacy address will also be generated for a ULA prefix,
> because it is treated just like a global prefix, right ?

I would think so, but there might be less need for this kind of privacy =
in a local environment.

Bob


>=20
> On 2011/01/04, at 4:30, Brian E Carpenter wrote:
>=20
>> Pekka,
>>=20
>> Wouldn't the rule "Use ULA prefix inside the site and PA prefix (with
>> privacy addresses if desired) otherwise" be simpler? And, by default,
>> it would prevent the "inside" address being exported by mistake.
>>=20
>> Regards
>>  Brian
>>=20
>>=20
>> On 2011-01-03 23:21, Pekka Savola wrote:
>>> On Mon, 3 Jan 2011, Mark Smith wrote:
>>>>> "do not use privacy addresses when communicating inside the site =
[a
>>>>> set of
>>>>> designated destination prefixes], use it by default otherwise"
>>>>>=20
>>>>=20
>>>> I'd be curious what the benefits are.
>>>>=20
>>>> The only reason I could think of as to why to do this is to be able =
to
>>>> associate internal application access logs with internal hosts. At =
face
>>>> value that sounds useful, however if you really care about auditing
>>>> application access and use, it isn't the hosts you need to worry =
about,
>>>> but the people behind them - and they can usually easily change =
hosts.
>>>> So I think those applications should be using proper AAA to =
identify the
>>>> user, rather than using IPv6 host identifiers as very poor =
substitutes
>>>> for user identities.
>>>=20
>>> One use case is administrators running ssh, vnc or some such remote
>>> management to the client OS.  The conclusion from looking at various
>>> similar cases was that systems need to have a well-known =
(non-privacy)
>>> IP where they can be reached and run TCP services at, or the privacy =
IP
>>> needs to be stored in DNS (not much point in that..).
>>>=20
>>> Also, many site-internal access control mechanisms (for example,
>>> hosts.allow for ssh, some others for e.g. web browsing) use
>>> host-specific IPs in addition to other checks.  In some cases these
>>> could be substituted with stronger upper-layer identities e.g with
>>> certificates.
>>>=20
>>> On the other hand, user identification due to static EU64 is a =
little
>>> bit of concern e.g. with web surfing, but this also applies to other
>>> applications so the issue does not go away with application-specific
>>> tuning.
>>>=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 brian@innovationslab.net  Sun Mar 27 05:35:53 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F7353A681C for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 05:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atfmX3st8Lvv for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 05:35:52 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id EF8D23A6819 for <ipv6@ietf.org>; Sun, 27 Mar 2011 05:35:51 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id BB407881AE; Sun, 27 Mar 2011 05:37:28 -0700 (PDT)
Received: from clemson.local (c-76-100-105-215.hsd1.md.comcast.net [76.100.105.215]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 1CB3E130002; Sun, 27 Mar 2011 05:37:27 -0700 (PDT)
Message-ID: <4D8F2F84.10204@innovationslab.net>
Date: Sun, 27 Mar 2011 08:37:24 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: IPv6 WG Mailing List <ipv6@ietf.org>
Subject: Re: 6MAN WG Last Call:draft-ietf-6man-rpl-option
References: <4CE1ABB5.2050809@innovationslab.net>
In-Reply-To: <4CE1ABB5.2050809@innovationslab.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 12:35:53 -0000

All,
     The chairs have determined that there is consensus to advance
draft-ietf-6man-rpl-option as a Proposed Standard to the IESG.

Regards,
Brian & Bob

On 11/15/10 4:52 PM, Brian Haberman wrote:
> All,
>      This starts a 6MAN WG Last Call on advancing:
> 
> Title     : RPL Option for Carrying RPL Information in
>             Data-Plane Datagrams
> Author(s) : J. Hui, J. Vasseur
> Filename  : draft-ietf-6man-rpl-option-01.txt
> Pages     : 16
> Date      : 2010-10-22
> 
> as a Proposed Standard.  Substantive comments should be sent to the
> mailing list and/or the WG co-chairs.  Editorial comments can be
> directed to the document authors.  This last call will end on December
> 6, 2010.
> 
> Regards,
> Brian & Bob
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From brian@innovationslab.net  Sun Mar 27 05:36:01 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7FB628C114 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 05:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yernT4BwrDZL for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 05:36:00 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id BF26A28C113 for <ipv6@ietf.org>; Sun, 27 Mar 2011 05:36:00 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id D1887881AE; Sun, 27 Mar 2011 05:37:37 -0700 (PDT)
Received: from clemson.local (c-76-100-105-215.hsd1.md.comcast.net [76.100.105.215]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0E33A130002; Sun, 27 Mar 2011 05:37:36 -0700 (PDT)
Message-ID: <4D8F2F8E.9030305@innovationslab.net>
Date: Sun, 27 Mar 2011 08:37:34 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6MAN WG Last Call:draft-ietf-6man-rpl-routing-header
References: <4CE1ABAE.9070400@innovationslab.net>
In-Reply-To: <4CE1ABAE.9070400@innovationslab.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 12:36:01 -0000

All,
     The chairs have determined that there is consensus to advance
draft-ietf-6man-rpl-routing-header as a Proposed Standard to the IESG.

Regards,
Brian & Bob

On 11/15/10 4:52 PM, Brian Haberman wrote:
> All,
>      This starts a 6MAN WG Last Call on advancing:
> 
>      Title     : An IPv6 Routing Header for Source Routes with RPL
>      Author(s) : J. Hui, et al.
>      Filename  : draft-ietf-6man-rpl-routing-header-01.txt
>      Pages     : 18
>      Date      : 2010-10-23
> 
> as a Proposed Standard.  Substantive comments should be sent to the
> mailing list and/or the WG co-chairs.  Editorial comments can be
> directed to the document authors.  This last call will end on December
> 6, 2010.
> 
> Regards,
> Brian & Bob
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From teemu.savolainen@nokia.com  Sun Mar 27 06:19:11 2011
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25CAD3A67E3; Sun, 27 Mar 2011 06:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level: 
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSA049oXW9Gw; Sun, 27 Mar 2011 06:19:10 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 5070428C100; Sun, 27 Mar 2011 06:19:10 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p2RDKjqP012355; Sun, 27 Mar 2011 16:20:46 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 27 Mar 2011 16:20:35 +0300
Received: from 008-AM1MMR1-001.mgdnok.nokia.com (65.54.30.56) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Sun, 27 Mar 2011 15:20:35 +0200
Received: from 008-AM1MPN1-036.mgdnok.nokia.com ([169.254.6.195]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.01.0270.002; Sun, 27 Mar 2011 15:20:34 +0200
From: <teemu.savolainen@nokia.com>
To: <ipv6@ietf.org>, <behave@ietf.org>
Subject: RFC3484-revise and NAT64 Well-Known Prefix
Thread-Topic: RFC3484-revise and NAT64 Well-Known Prefix
Thread-Index: AcvsgcCRXbnjiKSUSuKTwnQkrPt+Hw==
Date: Sun, 27 Mar 2011 13:20:34 +0000
Message-ID: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.162.93.108]
Content-Type: multipart/alternative; boundary="_000_916CE6CF87173740BC8A2CE443096962014C5D008AM1MPN1036mgdn_"
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Mar 2011 13:20:35.0901 (UTC) FILETIME=[C1F24ED0:01CBEC81]
X-Nokia-AV: Clean
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 13:19:11 -0000

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

Hi,

I discussed shortly with Arifumi about RFC3484 default policy table updates=
 and NAT64 WKP, i.e. whether the default policy table should take a stand o=
n 64:ff9b::/96 preference.

It seemed to us that default policy table does not necessarily have to, as =
it could be ok to handle addresses with WKP similarly to global IPv6 addres=
ses. Furthermore, the default policy table anyway cannot cover Network-Spec=
ific Prefixes.

Hence prefixes used for protocol translation would be handled like global I=
Pv6 addresses unless something different is configured via policy distribut=
ion mechanism? And this should perhaps be documented into the RFC3484-revis=
ed.

Best regards,

                Teemu

--_000_916CE6CF87173740BC8A2CE443096962014C5D008AM1MPN1036mgdn_
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 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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"><span lang=3D"FI">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"FI"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">I discussed shortly with Arifumi about RFC3484 defau=
lt policy table updates and NAT64 WKP, i.e. whether the default policy tabl=
e should take a stand on 64:ff9b::/96 preference.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It seemed to us that default policy table does not n=
ecessarily have to, as it could be ok to handle addresses with WKP similarl=
y to global IPv6 addresses. Furthermore, the default policy table anyway ca=
nnot cover Network-Specific Prefixes.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hence prefixes used for protocol translation would b=
e handled like global IPv6 addresses unless something different is configur=
ed via policy distribution mechanism? And this should perhaps be documented=
 into the RFC3484-revised.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Teemu <o:p></o:p></p>
</div>
</body>
</html>

--_000_916CE6CF87173740BC8A2CE443096962014C5D008AM1MPN1036mgdn_--

From cb.list6@gmail.com  Sun Mar 27 08:13:51 2011
Return-Path: <cb.list6@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9C3D3A686C; Sun, 27 Mar 2011 08:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level: 
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9WMYH7Fj+GOJ; Sun, 27 Mar 2011 08:13:50 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 5797C3A6868; Sun, 27 Mar 2011 08:13:50 -0700 (PDT)
Received: by eye13 with SMTP id 13so1044326eye.31 for <multiple recipients>; Sun, 27 Mar 2011 08:15:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9z/wuR7qkmkwfrggqaywkG9U9hd1Ioj7/2K9urTRSHA=; b=wv5cG4YtB3PemGAgauDX3Ts5MuNGKfyPwKK5oqCWlAQgN/8G/fMM00aZyECjQGIzLR r/4sGD2GhB+gjn0rJmXYJtHj2qab55q5IWlUdN1XjkHspLygZECn45AlVtZ36Cab/8q/ GWC+CSEjc4UQDfDmZiGA2SD4l+lnYTjDhFDsU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IZ5ulS/QALZouewNDH6Sj3ijWYFTIQW+4vdBnJEayH2KsaEl+k0ILsLvUEp7Q9j5af NWzYxNSukS+GoHMIE2yxw4TyaL+t5d2shTROtu5pCBRVrqHTw4QT7i4FFo+9qmL4qchP QqFs3k0F1BFDqe9JIqT2emiavKZAx9NXsJy7o=
MIME-Version: 1.0
Received: by 10.213.104.103 with SMTP id n39mr1298333ebo.144.1301238924068; Sun, 27 Mar 2011 08:15:24 -0700 (PDT)
Received: by 10.213.104.141 with HTTP; Sun, 27 Mar 2011 08:15:24 -0700 (PDT)
In-Reply-To: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com>
References: <AcvsgcCRXbnjiKSUSuKTwnQkrPt+Hw==> <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com>
Date: Sun, 27 Mar 2011 08:15:24 -0700
Message-ID: <AANLkTikeL7Q1cN1h2n3GBtiGvDbNQ5EPKa3f0n_v=kPb@mail.gmail.com>
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
From: Cameron Byrne <cb.list6@gmail.com>
To: teemu.savolainen@nokia.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: behave@ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 15:13:51 -0000

On Sun, Mar 27, 2011 at 6:20 AM,  <teemu.savolainen@nokia.com> wrote:
> Hi,
>
>
>
> I discussed shortly with Arifumi about RFC3484 default policy table updat=
es
> and NAT64 WKP, i.e. whether the default policy table should take a stand =
on
> 64:ff9b::/96 preference.
>
>
>
> It seemed to us that default policy table does not necessarily have to, a=
s
> it could be ok to handle addresses with WKP similarly to global IPv6
> addresses. Furthermore, the default policy table anyway cannot cover
> Network-Specific Prefixes.
>
>
>
> Hence prefixes used for protocol translation would be handled like global
> IPv6 addresses unless something different is configured via policy
> distribution mechanism? And this should perhaps be documented into the
> RFC3484-revised.
>

I agree that prefixes used for protocol translation should be treated
as normal IPv6.  I do not believe the policy table needs to be updated
.... seems like the policy table has been the target of trying to fix
various things (or the table was implemented wrong ...), but relying
on that static host level logic is very difficult in the real world to
solve dynamic problems.

Cameron
>
>
> Best regards,
>
>
>
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 Teemu
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

From alexandru.petrescu@gmail.com  Sun Mar 27 10:57:19 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62FD33A68C1 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 10:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mHmGvBgXP-r2 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 10:57:17 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id A319D3A68C0 for <ipv6@ietf.org>; Sun, 27 Mar 2011 10:57:17 -0700 (PDT)
Received: by pzk30 with SMTP id 30so551799pzk.31 for <ipv6@ietf.org>; Sun, 27 Mar 2011 10:58:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=0JygvjxRHLN8NhQzi0y1p2j56FtNbW+VdKokVEhiO40=; b=ErcCE2/t3tsjlJUGrE53YoQG4uDwf3LOdub/QXJdNRo5EUd4hWlbuBubisEzDJLvsQ 8ZIChhdIMuS2pgHlOKROWqofFysWtDWls8VnLtbt+X+QlTGyi9YUk+3c81L6TebQRlfq LPiG0xFNZJZaBUct6VZtGqNvAeCeSgRh5hkug=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=Kia1xODzh9BSqK7OWZ2Xu2RphHDtmFLq5xNbneI9a5gn5/DKuVcutySkLRr5Elcf32 Xbr7WuxwafTtGxr49hPCizICZYp6xK99EsvqEtdpgsWCSGzFCh8AFfjVuXs+jRo+dAoj 7ZBCa8pw0tYUx0IqAQ+BVVKX94Trp58opw0Dg=
Received: by 10.142.178.17 with SMTP id a17mr2743062wff.64.1301248734435; Sun, 27 Mar 2011 10:58:54 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id m10sm4702605wfl.23.2011.03.27.10.58.52 (version=SSLv3 cipher=OTHER); Sun, 27 Mar 2011 10:58:53 -0700 (PDT)
Message-ID: <4D8F7ADA.4090103@gmail.com>
Date: Sun, 27 Mar 2011 19:58:50 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Small comment on draft-ietf-6man-rpl-routing-header-02
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 17:57:19 -0000

Hello 6man,

I know this is late about the draft-ietf-6man-rpl-routing-header-02, but
allow me a small comment, thank you.


>> Third, to avoid some attacks that lead to the deprecation of RH0,
                                       led(?)

>> The Routing for Low Power and Lossy Networks (RPL) protocol can be
>> used in some deployments to store most, if not all, routes on one
>> (e.g. the Directed Acyclic Graph (DAG) root) or few routers and
>> forward the IPv6 datagram using a source routing technique to
>> avoid large routing tables on memory constrained routers.

If I understand correctly, the advice is to use a form of routing header
in order to avoid maintaining large routing tables in the routers.  But
I think that sometimes the routing table is larger if using routing
header; in these cases the rt table is smaller when using a prefixed dst
entry rather than a set of addresses (RH contents) per non-prefixed dst.

Besides, I believe the smallest routing tables are realized when only a
default route is used.  Or, this is already the case with RPL, i.e. a
leaf router only sends packest "up" to "parent" until it reaches the
Border Router.

This border router seems to be a very capable device, memory-rich, thus
not needing to reduce its tables.  Fortunately, this seems to
accommodate the use of Routing Headers, because it can accommodate
larger routing tables.

For the nodes which are memory-constrained, it is better to use default
routes if need to reduce the storage requirements, rather than RH.  In
some cases.

If you are comparing host-based routes vs prefixed routes - then yes:
using host-based routes implies there's going to be more entries in the
routing tables, hence larger.

In order to use prefix-based routes instead of host-based routes it is
sufficient to have a link layer having link multicast capabilities.
802.15.4 is one of them, when reading the spec.

Just some thought,

Alex


From alexandru.petrescu@gmail.com  Sun Mar 27 11:06:43 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED2C03A68D1 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 11:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Fq+xlA9156G for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 11:06:43 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 420873A68CF for <ipv6@ietf.org>; Sun, 27 Mar 2011 11:06:43 -0700 (PDT)
Received: by pve39 with SMTP id 39so551223pve.31 for <ipv6@ietf.org>; Sun, 27 Mar 2011 11:08:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Cpd1rFFvHhnCrBxwdMMOMxXvCIskYBQkr0KFTwlrB9o=; b=gjCeDv/4RD9vr6mkFcTTVrKSd+GdP5vaXJAlmzrM25E3gZJENUcGgrdPot9T66lw5C A3nZMc22pR5esXgFhV0Ihio+aGN1oMo8caO37C3PudVDMPoL2u3PtzDBxQdlmQRUg/Ee s3rCUYHHBWk3JrHyA29aXR8+Zx4GutD6Ft/7o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=jiKMN0E6L0nf8WX+bgMxzmf/5Cr3LxIUbMIeHzOOgp7wxDGpZIGb2k6yTnuyN7n9Ds VoksCwO83pnFU7FJFcNYLP+JIOEUEzRIp66nhj+KxPddc48mKQ9zbfR279ZCwWZoyX6y WUg2X20FBI1Fs5+nVFXlHhihHMAWcPVbzlAfc=
Received: by 10.142.222.17 with SMTP id u17mr2719349wfg.423.1301249300254; Sun, 27 Mar 2011 11:08:20 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id w27sm4716481wfd.4.2011.03.27.11.08.18 (version=SSLv3 cipher=OTHER); Sun, 27 Mar 2011 11:08:19 -0700 (PDT)
Message-ID: <4D8F7D0F.7030507@gmail.com>
Date: Sun, 27 Mar 2011 20:08:15 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Comment on  draft-ietf-6man-node-req-bis-08.txt
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 18:06:44 -0000

Hello 6man,

Comment on draft-ietf-6man-node-req-bis-08.txt.

In section 10 "Mobility" cite RFC3963 ""NEMO" Basic Support", as a MAY
for network mobility.  It is at least as much implemented as other
cited RFCs in the mobility section.

In section 7.2 DHCPv6 - explicitely cite RFC3633 "IPv6 Prefix Options
for Dynamic Host Configuration Protocol (DHCP) version 6".  I think this
is currently available in some widely available DHCP implementation.
This wouldn't be "other non-address information".

Alex

From Teemu.Kiviniemi@csc.fi  Sun Mar 27 12:51:40 2011
Return-Path: <Teemu.Kiviniemi@csc.fi>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3582B3A6926; Sun, 27 Mar 2011 12:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48h+f4fo80dI; Sun, 27 Mar 2011 12:51:38 -0700 (PDT)
Received: from smtp3.csc.fi (smtp3.csc.fi [193.166.7.53]) by core3.amsl.com (Postfix) with ESMTP id 249DA3A691B; Sun, 27 Mar 2011 12:51:37 -0700 (PDT)
Received: from kusti.csc.fi (kusti.csc.fi [193.166.0.100]) by smtp3.csc.fi (8.14.3/8.14.3/CSC) with ESMTP id p2RJrDvI030512; Sun, 27 Mar 2011 22:53:13 +0300
Received: from sampo3.csc.fi (193.166.1.170) by kusti.csc.fi (192.168.120.3) with Microsoft SMTP Server (TLS) id 8.2.254.0; Sun, 27 Mar 2011 22:54:00 +0300
Date: Sun, 27 Mar 2011 22:53:13 +0300
From: Teemu Kiviniemi <tekivini@csc.fi>
To: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
In-Reply-To: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com>
Message-ID: <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format=flowed
X-CanIt-Geo: ip=193.166.0.100; country=FI; latitude=64.0000; longitude=26.0000; http://maps.google.com/maps?q=64.0000,26.0000&z=6
X-CanItPRO-Stream: 00_Opt_Out (inherits from default)
X-Scanned-By: CanIt (www . roaringpenguin . com) on 193.166.7.53
Cc: "behave@ietf.org" <behave@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 19:51:40 -0000

On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:

> I discussed shortly with Arifumi about RFC3484 default policy table 
> updates and NAT64 WKP, i.e. whether the default policy table should take 
> a stand on 64:ff9b::/96 preference.
>
> It seemed to us that default policy table does not necessarily have to, 
> as it could be ok to handle addresses with WKP similarly to global IPv6 
> addresses. Furthermore, the default policy table anyway cannot cover 
> Network-Specific Prefixes.
>
> Hence prefixes used for protocol translation would be handled like 
> global IPv6 addresses unless something different is configured via 
> policy distribution mechanism? And this should perhaps be documented 
> into the RFC3484-revised.

I believe native IPv4 should always be preferred over NAT64. Even if 
native IPv4 was using NAT, it is likely to work better with current 
applications than NAT64.

Preferring IPv4 over the NAT64 well-known prefix does not fix the problem 
for network-specific NAT64 prefixes. However, I see no reasons why the 
NAT64 WKP should not be given a lower preference than IPv4 by default.

-- 
Teemu

From cb.list6@gmail.com  Sun Mar 27 14:15:36 2011
Return-Path: <cb.list6@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CE3E3A6950; Sun, 27 Mar 2011 14:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.547
X-Spam-Level: 
X-Spam-Status: No, score=-3.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uxi1tgTRkTY5; Sun, 27 Mar 2011 14:15:35 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id CEEA43A6955; Sun, 27 Mar 2011 14:15:34 -0700 (PDT)
Received: by eye13 with SMTP id 13so1106434eye.31 for <multiple recipients>; Sun, 27 Mar 2011 14:17:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+g7/FZNB3bMFTbhfiT09vzmK6bSQuMKo5GaRF8/kuYI=; b=uir+9+pZPfw/k+ODENgAWife4Opqi4V2u3wvJ8EqqFxgSTMcd17qHLwc6N74J9yuYH bNTwSJN0vqEhURQM+5NBxHN4oyhTc92WgKltWcspFYwHtVcslE7t7Va7g4Ueu55H1iIr UnPx4yesQqNJigandQIYrJUJi/dfB+8+65InI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xeZxERPDKif76xfmSb7NrfeM+D28CBalXyH+WT/hXpX6rqLqFPerLUEad0o9Y0dQEC IJh9uJqBwkSP8JZ0VB6SpfL1lgzAXqI2dmjK0ZvAHQZcABcdn251RJWqFSOqo/vOgatc jF4aZlYVBhatBCQHFTc/0YWebQO8fjRA0usNE=
MIME-Version: 1.0
Received: by 10.213.25.212 with SMTP id a20mr1365590ebc.106.1301260630983; Sun, 27 Mar 2011 14:17:10 -0700 (PDT)
Received: by 10.213.104.141 with HTTP; Sun, 27 Mar 2011 14:17:10 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
Date: Sun, 27 Mar 2011 14:17:10 -0700
Message-ID: <AANLkTikBBFkiRpTizwdnCp3TFd9Mwh8zi1M8NFEZnE8B@mail.gmail.com>
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
From: Cameron Byrne <cb.list6@gmail.com>
To: Teemu Kiviniemi <tekivini@csc.fi>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "behave@ietf.org" <behave@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 21:15:36 -0000

On Sun, Mar 27, 2011 at 12:53 PM, Teemu Kiviniemi <tekivini@csc.fi> wrote:
> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
>
>> I discussed shortly with Arifumi about RFC3484 default policy table
>> updates and NAT64 WKP, i.e. whether the default policy table should take a
>> stand on 64:ff9b::/96 preference.
>>
>> It seemed to us that default policy table does not necessarily have to, as
>> it could be ok to handle addresses with WKP similarly to global IPv6
>> addresses. Furthermore, the default policy table anyway cannot cover
>> Network-Specific Prefixes.
>>
>> Hence prefixes used for protocol translation would be handled like global
>> IPv6 addresses unless something different is configured via policy
>> distribution mechanism? And this should perhaps be documented into the
>> RFC3484-revised.
>
> I believe native IPv4 should always be preferred over NAT64. Even if native
> IPv4 was using NAT, it is likely to work better with current applications
> than NAT64.
>

I strongly disagree.

Let's not keep changing things, and please leave well enough alone.
We can't keep changing the rules of the game, we just end up with
inconsistent implementations that cannot be changed easily once
deployed.

What data do you have to show that NAT44 experience is better than
NAT64?  As someone who has deployed and operated NAT44 at very large
scale and NAT64 (small scale, for over a year, but the largest i know
of) there is not a service difference that i am aware of between NAT64
and NAT44.

I see this, like happy eyeballs, as a threat to growing IPv6 traffic
volumes.  If we cannot grow traffic volumes on IPv6, the relevant
planning people (google's now famous graph ... and others) will not
put resources to growing IPv6.  IPv6 remains a second class half-way
implemented / RFP checkbox protocol that is not fit for production....
and over time looses the ground it has gained like ... Symbian^3 now
not working with IPv6.

T-Mobile USA just launched the Nokia C7, and it less IPv6
functionality than last year's Nokia phones ...

Network planners see the CGN NAT44 growing, so they put time and money
on that ... Yet CGN NAT44 is a dead end.  CGN NAT64 is not a dead end,
it gets the protocol right and ENABLES one end of the connection to
have the opportunity to have native IPv6 and that pressures the other
end to support IPv6 to avoid CGN issues....

What you are suggesting just ensures the status quo while injecting
additional entropy across the install base.  With IPv6 preferred and
going via NAT64, network planners and application folks can see the
latent IPv6 opportunity that would be available if both ends of the
connection were IPv6.

> Preferring IPv4 over the NAT64 well-known prefix does not fix the problem

Please make your cogent case for that there is a problem first.

> for network-specific NAT64 prefixes. However, I see no reasons why the NAT64
> WKP should not be given a lower preference than IPv4 by default.
>

No reason to not do it != reason to do it.

Let's not keep changing the rules of the game.

Cameron

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

From fernando.gont.netbook.win@gmail.com  Sun Mar 27 15:55:37 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E961C28C0E2 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 15:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZG7w8YMTrTk for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 15:55:36 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id C59E13A67AB for <ipv6@ietf.org>; Sun, 27 Mar 2011 15:55:36 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2857697iwn.31 for <ipv6@ietf.org>; Sun, 27 Mar 2011 15:57:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=z9rHDm/5+6MsvF52PuLbHlrW36yVdqdnCVLNnZ/90xg=; b=BYiI3Szwb8O7Hf+/Cm6Wn1Yr8FHK/zJ0ok1qDp/Z8DME4fnuV9qel+RKdxlWU8j9nV HqCT2kcJOpXfBJsVapjtGf5i+8E+xrlznXhcrELuezqGQfVo+nyJxYNXS3oZuvjuVDPC RJgHCVwUAR8EjyZUERlLZlPsjbtgRgFvqImTI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=jgk8b/6v3iC3tR3snXKwTOD04ItlmRNgPeJlLBy041fWAFcayerkbI9zpjyiLaA0vv RPi128ANDASmq9Rlx/DNaDxLM40GcgGsF9IzCHpyk3VOTjhNir1RobteXNv2HKR7gyWm m4JpyArNtQu9suCjdpr68yocgGx6lYypuVf08=
Received: by 10.43.60.133 with SMTP id ws5mr5557634icb.89.1301266633861; Sun, 27 Mar 2011 15:57:13 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id he40sm2506073ibb.67.2011.03.27.15.57.09 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Mar 2011 15:57:12 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D8FC0BD.20206@gont.com.ar>
Date: Sun, 27 Mar 2011 19:57:01 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: addrsel: privacy addresses within/out of a site
References: <alpine.LRH.2.02.1101031151250.23654@netcore.fi>	<20110103204031.0c3589b7@opy.nosense.org>	<alpine.LRH.2.02.1101031213060.23654@netcore.fi>	<4D2223DB.1000708@gmail.com> <49BBE77F-7339-4916-A005-EC3FE0227709@nttv6.net>
In-Reply-To: <49BBE77F-7339-4916-A005-EC3FE0227709@nttv6.net>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 Mar 2011 22:55:38 -0000

Hi, Arifumi,

On 27/03/2011 03:58 a.m., Arifumi Matsumoto wrote:
> A privacy address will also be generated for a ULA prefix,
> because it is treated just like a global prefix, right ?

Yes. This would be another scenario in which
draft-gont-6man-managing-privacy-extensions would be of help. You'd
advertise the ULA prefix recommending Modified EUI-64 Identifiers, and
that's it.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From brian.e.carpenter@gmail.com  Sun Mar 27 22:53:33 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA1CE3A6814; Sun, 27 Mar 2011 22:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kOv2ki7Im5Et; Sun, 27 Mar 2011 22:53:32 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 6E32C3A6813; Sun, 27 Mar 2011 22:53:32 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1205979gxk.31 for <multiple recipients>; Sun, 27 Mar 2011 22:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jYtL6IVUJZaQX84Xta0ttpY+UzIWhH5JFrShYjyCMn0=; b=LRiRp1raVwbc4WZapVk5218YN+V2lF/1a68VfgeVUHVAneO7iDaeLhcZae5KW09Llv 6e/vQa2Wa7zIXKZFOC9wi/XdynZGmrcqIcvGWszlYC9qeFE91iGyVqJxOtXquISTvNIN mjsUnn9njjxnjs/zO/qx7fPefBDpvdAmolGH0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=wt/PMvcFbAxhaQFLMu40rroouwQdLfQBfnlTCRht+yf95dXUPpzxrqh34YiDCJ0a6j tMKzb8h4gVwNkbugxOSOQY6ZRqhcDBegtCkwICG3jKudxZc6MLv2F2dytiXGE2ZKoW7f 5pWg3g3biJ7D6fJ4z0iV3NstYX6/5rY9+P7qI=
Received: by 10.150.31.16 with SMTP id e16mr3683633ybe.227.1301291709299; Sun, 27 Mar 2011 22:55:09 -0700 (PDT)
Received: from [130.129.71.154] (dhcp-479a.meeting.ietf.org [130.129.71.154]) by mx.google.com with ESMTPS id b4sm48878ybn.8.2011.03.27.22.55.06 (version=SSLv3 cipher=OTHER); Sun, 27 Mar 2011 22:55:08 -0700 (PDT)
Message-ID: <4D9022B6.8020105@gmail.com>
Date: Mon, 28 Mar 2011 18:55:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Teemu Kiviniemi <tekivini@csc.fi>
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
In-Reply-To: <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "behave@ietf.org" <behave@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 05:53:33 -0000

On 2011-03-28 08:53, Teemu Kiviniemi wrote:
> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
...
> I believe native IPv4 should always be preferred over NAT64. 

That is just irrelevant and of no importance, since the only hosts
that use DNS64 and NAT64 in normal life are IPv6-only hosts.

There is a side issue of what happens if a synthetic IPv6 address
is referred to a non-IPv6-only host, but that is a whole other
problem that cannot be solved at the RFC3484bis level.

See draft-carpenter-referral-ps-02.txt...

    Brian

From bob.hinden@gmail.com  Sun Mar 27 23:50:44 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1AF83A6866 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 23:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.537
X-Spam-Level: 
X-Spam-Status: No, score=-103.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dre3qDLIJSz1 for <ipv6@core3.amsl.com>; Sun, 27 Mar 2011 23:50:43 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id A4ED63A6876 for <ipv6@ietf.org>; Sun, 27 Mar 2011 23:50:42 -0700 (PDT)
Received: by iye19 with SMTP id 19so3147171iye.31 for <ipv6@ietf.org>; Sun, 27 Mar 2011 23:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=zxKcNVwlXDutP1MkR3AXDUuQwtRXFMytxOrYK111dMg=; b=WIEK4Lrrmw1UgfDFzvOFsv7cyyz+dq0TbbqBndB2rNeArP87BMg0dabVxVI1sxqAGN WaEZDunSCshALZW0yVKhen65oCcR4DwlFPCOxjf9y8aQ43zlwujWiIOQaXpft9HuQXk3 sKDKdC9JXeSFEnj9V02zaX6UK1ZH23gTuUxA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=IE7oQvTNKZnUziDJIfs+jYgGT0mfFWk376tXHiiHSIjFq+c9IXtIk8729vVAQzOwXs qJWbL30mPCBEi8rwfVY7ZVEajG9/cOSw1fqhmUkO0g7QiUmKND2q5J7THejxQcJUFc1/ X2w3EN+NWt4aMlwN33dXY+U7wBsv/mYgYNEDs=
Received: by 10.231.117.36 with SMTP id o36mr3781436ibq.64.1301295139868; Sun, 27 Mar 2011 23:52:19 -0700 (PDT)
Received: from dhcp-57ed.meeting.ietf.org (dhcp-57ed.meeting.ietf.org [130.129.87.237]) by mx.google.com with ESMTPS id 8sm2746343iba.55.2011.03.27.23.52.17 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Mar 2011 23:52:18 -0700 (PDT)
Subject: Re: Need minute taker and jabber scribe(s)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <6A499E9A-FAF5-450E-8F35-6EB30424D981@gmail.com>
Date: Mon, 28 Mar 2011 08:52:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D64AB84F-1977-491F-8A2D-01BC49F09A5A@gmail.com>
References: <A4ED6B87-1BA6-4812-A9DB-B85B096BF65D@gmail.com> <6A499E9A-FAF5-450E-8F35-6EB30424D981@gmail.com>
To: 6man Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 06:50:44 -0000

Still looking for a jabber scribe.

Bob

On Mar 25, 2011, at 9:44 PM, Bob Hinden wrote:

> We still need a jabber scribe.=20
>=20
> Thanks to Suresh for volunteering to take minutes.
>=20
> Thanks,
> Bob
>=20
>=20
> On Mar 22, 2011, at 7:32 PM, Bob Hinden wrote:
>=20
>> We are looking for volunteers to take minutes and jabber scribe for =
the 6man session on Monday morning in Prague.
>>=20
>> It a great service to the working group and the IETF!
>>=20
>> Thanks,
>> Bob & Brian
>>=20
>>=20
>=20


From teemu.savolainen@nokia.com  Mon Mar 28 00:18:03 2011
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1167A3A6876; Mon, 28 Mar 2011 00:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wd60IUNReIvK; Mon, 28 Mar 2011 00:18:02 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by core3.amsl.com (Postfix) with ESMTP id 866BD3A68B0; Mon, 28 Mar 2011 00:17:46 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-sa01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p2S7JJkR008207; Mon, 28 Mar 2011 10:19:21 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 10:19:08 +0300
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Mon, 28 Mar 2011 09:19:00 +0200
Received: from 008-AM1MPN1-036.mgdnok.nokia.com ([169.254.6.195]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0270.002; Mon, 28 Mar 2011 09:19:00 +0200
From: <teemu.savolainen@nokia.com>
To: <brian.e.carpenter@gmail.com>, <tekivini@csc.fi>
Subject: RE: RFC3484-revise and NAT64 Well-Known Prefix
Thread-Topic: RFC3484-revise and NAT64 Well-Known Prefix
Thread-Index: AcvsgcCRXbnjiKSUSuKTwnQkrPt+HwAivlGZAALORlA=
Date: Mon, 28 Mar 2011 07:19:00 +0000
Message-ID: <916CE6CF87173740BC8A2CE443096962015109@008-AM1MPN1-036.mgdnok.nokia.com>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <4D9022B6.8020105@gmail.com>
In-Reply-To: <4D9022B6.8020105@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.99.11]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Mar 2011 07:19:08.0803 (UTC) FILETIME=[6DD78530:01CBED18]
X-Nokia-AV: Clean
Cc: ipv6@ietf.org, behave@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 07:18:03 -0000

TXVsdGktaW50ZXJmYWNlZCBob3N0IG1pZ2h0IGhhdmUgb25lIG5ldHdvcmsgaW50ZXJmYWNlIElQ
djYtb25seSB3aXRoIE5BVDY0IChlLmcuIGNlbGx1bGFyKSBhbmQgYW5vdGhlciBuZXR3b3JrIGlu
dGVyZmFjZSBJUHY0LW9ubHkgKGUuZy4gV0xBTikuDQoNClRlZW11DQoNCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogZXh0IEJyaWFuIEUgQ2FycGVudGVyIFttYWlsdG86YnJp
YW4uZS5jYXJwZW50ZXJAZ21haWwuY29tXQ0KPiBTZW50OiAyOC4gbWFhbGlza3V1dGEgMjAxMSAw
Nzo1NQ0KPiBUbzogVGVlbXUgS2l2aW5pZW1pDQo+IENjOiBTYXZvbGFpbmVuIFRlZW11IChOb2tp
YS1NUy9UYW1wZXJlKTsgYmVoYXZlQGlldGYub3JnOyBpcHY2QGlldGYub3JnDQo+IFN1YmplY3Q6
IFJlOiBSRkMzNDg0LXJldmlzZSBhbmQgTkFUNjQgV2VsbC1Lbm93biBQcmVmaXgNCj4gDQo+IE9u
IDIwMTEtMDMtMjggMDg6NTMsIFRlZW11IEtpdmluaWVtaSB3cm90ZToNCj4gPiBPbiBTdW4sIDI3
IE1hciAyMDExLCB0ZWVtdS5zYXZvbGFpbmVuQG5va2lhLmNvbSB3cm90ZToNCj4gLi4uDQo+ID4g
SSBiZWxpZXZlIG5hdGl2ZSBJUHY0IHNob3VsZCBhbHdheXMgYmUgcHJlZmVycmVkIG92ZXIgTkFU
NjQuDQo+IA0KPiBUaGF0IGlzIGp1c3QgaXJyZWxldmFudCBhbmQgb2Ygbm8gaW1wb3J0YW5jZSwg
c2luY2UgdGhlIG9ubHkgaG9zdHMNCj4gdGhhdCB1c2UgRE5TNjQgYW5kIE5BVDY0IGluIG5vcm1h
bCBsaWZlIGFyZSBJUHY2LW9ubHkgaG9zdHMuDQo+IA0KPiBUaGVyZSBpcyBhIHNpZGUgaXNzdWUg
b2Ygd2hhdCBoYXBwZW5zIGlmIGEgc3ludGhldGljIElQdjYgYWRkcmVzcw0KPiBpcyByZWZlcnJl
ZCB0byBhIG5vbi1JUHY2LW9ubHkgaG9zdCwgYnV0IHRoYXQgaXMgYSB3aG9sZSBvdGhlcg0KPiBw
cm9ibGVtIHRoYXQgY2Fubm90IGJlIHNvbHZlZCBhdCB0aGUgUkZDMzQ4NGJpcyBsZXZlbC4NCj4g
DQo+IFNlZSBkcmFmdC1jYXJwZW50ZXItcmVmZXJyYWwtcHMtMDIudHh0Li4uDQo+IA0KPiAgICAg
QnJpYW4NCg==

From brian.e.carpenter@gmail.com  Mon Mar 28 00:52:00 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F16783A68EB; Mon, 28 Mar 2011 00:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFCd46-MXQIo; Mon, 28 Mar 2011 00:52:00 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id F1FBF3A68EE; Mon, 28 Mar 2011 00:51:59 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1248319yxk.31 for <multiple recipients>; Mon, 28 Mar 2011 00:53:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UEPuUjYgd1+SCkGJ6XcHyOZRAwpBsukauLzK65mbflM=; b=lsVedPprAEsTEzAml1v/nZhw2Ze/s3zAMSHParILLwOPZdQtLLxS90hcx63DF76dA9 HaX08NRQkOT3t2vGJ1oNKlv76mRCia37Mu42fuqG9nmNBHP6cJQrhcn8HxH2zJtloWdO XTMFTAZIZC3JyFsg3jwyo2GeSxQwopEJpph1E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=q2dEXeRfqV8lHv/4mskDLoKqlL6BjNEpiVFNErEw2ED9ZbKPd6bf98OrxhsMtXF/3k sgqCKyWx20C2oE1xhJfVUVoKZ3RfWTAx/eiX6uudYEayUPQp1Diqwk2GLmRPhyX/RLlW ZwoDy+asOqJEAVceaIYIpDcm89l3GS51YVzN4=
Received: by 10.236.197.7 with SMTP id s7mr1099535yhn.188.1301298817069; Mon, 28 Mar 2011 00:53:37 -0700 (PDT)
Received: from [130.129.22.150] (dhcp-1696.meeting.ietf.org [130.129.22.150]) by mx.google.com with ESMTPS id x76sm1823631yhn.94.2011.03.28.00.53.00 (version=SSLv3 cipher=OTHER); Mon, 28 Mar 2011 00:53:06 -0700 (PDT)
Message-ID: <4D903E55.1010807@gmail.com>
Date: Mon, 28 Mar 2011 20:52:53 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: teemu.savolainen@nokia.com
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <4D9022B6.8020105@gmail.com> <916CE6CF87173740BC8A2CE443096962015109@008-AM1MPN1-036.mgdnok.nokia.com>
In-Reply-To: <916CE6CF87173740BC8A2CE443096962015109@008-AM1MPN1-036.mgdnok.nokia.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, tekivini@csc.fi, behave@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 07:52:01 -0000

Yes. The MIF model seems to me to be fairly broken
from an architectural point of view. Maybe you have to
forbid exporting certain information from one stack to another
on a MIF host.

   Brian

On 2011-03-28 20:19, teemu.savolainen@nokia.com wrote:
> Multi-interfaced host might have one network interface IPv6-only with NAT64 (e.g. cellular) and another network interface IPv4-only (e.g. WLAN).
> 
> Teemu
> 
>> -----Original Message-----
>> From: ext Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: 28. maaliskuuta 2011 07:55
>> To: Teemu Kiviniemi
>> Cc: Savolainen Teemu (Nokia-MS/Tampere); behave@ietf.org; ipv6@ietf.org
>> Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
>>
>> On 2011-03-28 08:53, Teemu Kiviniemi wrote:
>>> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
>> ...
>>> I believe native IPv4 should always be preferred over NAT64.
>> That is just irrelevant and of no importance, since the only hosts
>> that use DNS64 and NAT64 in normal life are IPv6-only hosts.
>>
>> There is a side issue of what happens if a synthetic IPv6 address
>> is referred to a non-IPv6-only host, but that is a whole other
>> problem that cannot be solved at the RFC3484bis level.
>>
>> See draft-carpenter-referral-ps-02.txt...
>>
>>     Brian

From magnus.westerlund@ericsson.com  Mon Mar 28 00:58:28 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AF4B3A6808 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 00:58:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.396
X-Spam-Level: 
X-Spam-Status: No, score=-106.396 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NM+z-WSomxr8 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 00:58:27 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 37E103A68BC for <ipv6@ietf.org>; Mon, 28 Mar 2011 00:58:27 -0700 (PDT)
X-AuditID: c1b4fb3d-b7bbbae000005311-44-4d904003528f
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B6.D0.21265.300409D4; Mon, 28 Mar 2011 10:00:03 +0200 (CEST)
Received: from [153.88.17.31] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Mon, 28 Mar 2011 10:00:02 +0200
Message-ID: <4D904002.1070206@ericsson.com>
Date: Mon, 28 Mar 2011 10:00:02 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: "6man WG" <ipv6@ietf.org>
Subject: Update on draft-ietf-6man-udpzero-02
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 07:58:28 -0000

Hi,

We authors plan an editorial update of the draft. We think it is in
fairly good state. However, as the intention is to be a consideration
for the update of the IPv6 specs UDP checksuming rules, I think we
should not go forward to WG last call until also
https://datatracker.ietf.org/doc/draft-ietf-6man-udpchecksums/ has been
WG last called.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
F鋜鰃atan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From shemant@cisco.com  Mon Mar 28 01:04:42 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEBF73A68EB for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 01:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.381
X-Spam-Level: 
X-Spam-Status: No, score=-10.381 tagged_above=-999 required=5 tests=[AWL=-0.383, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id igE38ttfrhBc for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 01:04:42 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 114BA3A68DE for <ipv6@ietf.org>; Mon, 28 Mar 2011 01:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=3981; q=dns/txt; s=iport; t=1301299579; x=1302509179; h=mime-version:subject:date:message-id:from:to; bh=es6LCLXO0t4l5Si6rT+zJmSK/JPiQoChgoI2BYPUqm8=; b=TgEsHEqUln52LdvcROSZlEUpKPc7B70MQOySAuM9XUBmUE7osujrk7Du WmDpnfbRgjBUP9TiMYcpZOEC6Ugzfi3g5D4JW0Uu2CjUMFOzLJ+e/AsK/ kJM8oFZCM5WMMxeKHMVLXm2wdhCV99UZVzCfJWO9mwqv4VTLt3UDnmNtX k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AngBACJAkE2tJXG//2dsb2JhbACCX5UuP4x+d6VFmyGFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,253,1299456000";  d="scan'208,217";a="419264480"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by sj-iport-1.cisco.com with ESMTP; 28 Mar 2011 08:06:19 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2S86JnL023696 for <ipv6@ietf.org>; Mon, 28 Mar 2011 08:06:19 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 03:06:19 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBED1F.04755F92"
Subject: FW: comment on draft-gont-6man-managing-privacy-extensions-01
Date: Mon, 28 Mar 2011 03:06:18 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E587@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: comment on draft-gont-6man-managing-privacy-extensions-01
Thread-Index: AcvtHlwCe4W7gAIUS5SdwNJOgbFgSAAAF2HA
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 08:06:19.0431 (UTC) FILETIME=[05071370:01CBED1F]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 08:04:42 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBED1F.04755F92
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Humble apologies that I meant to send this email to 6man but instead
sent it to v6ops.

=20

Hemant

=20

From: Hemant Singh (shemant)=20
Sent: Monday, March 28, 2011 10:02 AM
To: IPv6 Ops WG
Subject: comment on draft-gont-6man-managing-privacy-extensions-01

=20

In some certain large-scale broadband networks, an RA does not even
include any PIO, so how will this document signal new bits? =20

=20

Hemant

=20


------_=_NextPart_001_01CBED1F.04755F92
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-microsoft-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=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'color:#1F497D'>Humble apologies that =
I meant to
send this email to 6man but instead sent it to =
v6ops.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hemant<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Hemant =
Singh (shemant)
<br>
<b>Sent:</b> Monday, March 28, 2011 10:02 AM<br>
<b>To:</b> IPv6 Ops WG<br>
<b>Subject:</b> comment on =
draft-gont-6man-managing-privacy-extensions-01<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>In some certain large-scale broadband networks, an =
RA does
not even include any PIO, so how will this document signal new =
bits?&nbsp; <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Hemant<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01CBED1F.04755F92--

From swmike@swm.pp.se  Mon Mar 28 01:23:34 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E0F33A68F3 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 01:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level: 
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=-0.270, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SUrupeoGE+h for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 01:23:32 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id A2D9D3A683C for <ipv6@ietf.org>; Mon, 28 Mar 2011 01:23:32 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7BC4A9C; Mon, 28 Mar 2011 10:25:08 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7A5F39A for <ipv6@ietf.org>; Mon, 28 Mar 2011 10:25:08 +0200 (CEST)
Date: Mon, 28 Mar 2011 10:25:08 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ipv6@ietf.org
Subject: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Message-ID: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 08:23:34 -0000

Hello.

I read through 2.3 of the draft, and I am a bit unclear as to how the 
next-hop should be selected.

In the case of my SLAAC machine, I see the next-hop for my default-route 
as a LL address. How would the SA and the default router LL be tied 
together?

In the case of getting address using DHCPv6, there is also no direct 
connection between the default route and the SA, as the DHCPv6 server 
might be different from the default-route gw?

There is a use of "destination D" in several places, for a default-route 
this seems misplaced and has caused misunderstandings recent discussions 
in v6ops, perhaps there would be benefit in using different terminology 
here?

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

From brian@innovationslab.net  Mon Mar 28 05:20:42 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25F003A688B for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wcoYSMU7DebW for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:20:41 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 6A85D3A67F0 for <ipv6@ietf.org>; Mon, 28 Mar 2011 05:20:41 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 3486F8816E for <ipv6@ietf.org>; Mon, 28 Mar 2011 05:22:19 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 3C444130002 for <ipv6@ietf.org>; Mon, 28 Mar 2011 05:22:18 -0700 (PDT)
Message-ID: <4D907D77.1030904@innovationslab.net>
Date: Mon, 28 Mar 2011 08:22:15 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 12:20:42 -0000

Hi Mikael,

On 3/28/11 4:25 AM, Mikael Abrahamsson wrote:
> 
> Hello.
> 
> I read through 2.3 of the draft, and I am a bit unclear as to how the
> next-hop should be selected.
> 
> In the case of my SLAAC machine, I see the next-hop for my default-route
> as a LL address. How would the SA and the default router LL be tied
> together?

One way would be for the stack to keep track of which router's LL
address was the source of the PIO containing the prefix used to generate
the address.

> 
> In the case of getting address using DHCPv6, there is also no direct
> connection between the default route and the SA, as the DHCPv6 server
> might be different from the default-route gw?

Does the DHCPv6 response contain any information about the DHCP-relay used?

Regards,
Brian

From shemant@cisco.com  Mon Mar 28 05:34:41 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08ACF3A68D5 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.673
X-Spam-Level: 
X-Spam-Status: No, score=-10.673 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RASlZFKsAm5M for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:34:40 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 0F2313A67E4 for <ipv6@ietf.org>; Mon, 28 Mar 2011 05:34:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1075; q=dns/txt; s=iport; t=1301315777; x=1302525377; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=GYiwjh3a1eY9tMiMVeA9rswzuWZX9h6g54hZbaKUVlY=; b=B0Zr16IyC+e9TVNhIiAtWJOPnOtzWeEmX6ddtgleqVRFmwpHM0wbcqmP N7O+IDImRAAKEvOCHUjY2m0fBB4L5eLLKmGRMSQO9A3DSbsEPbOX0SIur TELLDHai9GRAPNImyzVHZxjlku/UE0HYRZ3NRLDUfqvlf7gXrX5XAvHqU s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAJeAkE2tJV2c/2dsb2JhbACYAI0/d6cEm2CFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="281579386"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by sj-iport-4.cisco.com with ESMTP; 28 Mar 2011 12:36:17 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p2SCaHRa006246;  Mon, 28 Mar 2011 12:36:17 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 07:36:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Mon, 28 Mar 2011 07:36:16 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com>
In-Reply-To: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Thread-Index: AcvtIbvCmfPUTJ7IQcmFCZdLN21r7gAIl4KA
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>, <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 12:36:17.0151 (UTC) FILETIME=[BB9F00F0:01CBED44]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 12:34:41 -0000

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Mikael Abrahamsson
Sent: Monday, March 28, 2011 10:25 AM
To: ipv6@ietf.org
Subject: question regarding draft-ietf-6man-rfc3484-revise-02 section
2.3

Mikael,

>In the case of getting address using DHCPv6, there is also no direct=20
>connection between the default route and the SA, as the DHCPv6 server=20
>might be different from the default-route gw?

It's the IPv6 default router for the DHCPv6 client that sends a RA with
the M-bit set and seeing such an RA the client initiates DHCPv6.  Or the
client could initiate DHCPv6 even on receiving an RA with the M-bit
cleared.  But the fact still remains that the DHCPv6 client did receive
an RA from the IPv6 first-hop router to the client.  The client is
supposed to perform router discovery and send RS.  The RA lets the
client know what the default router is.  If I missed anything, perhaps
if you could please draw a diagram and let us know what specific use
case I missed.

Thanks,

Hemant

From swmike@swm.pp.se  Mon Mar 28 05:35:16 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03A213A680A for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.263
X-Spam-Level: 
X-Spam-Status: No, score=-2.263 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3weCAkTt0Ho for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 05:35:15 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id F06D83A67E4 for <ipv6@ietf.org>; Mon, 28 Mar 2011 05:35:14 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D78EE9C; Mon, 28 Mar 2011 14:36:51 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D53899A for <ipv6@ietf.org>; Mon, 28 Mar 2011 14:36:51 +0200 (CEST)
Date: Mon, 28 Mar 2011 14:36:51 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ipv6@ietf.org
Subject: Re: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
In-Reply-To: <4D907D77.1030904@innovationslab.net>
Message-ID: <alpine.DEB.2.00.1103281431180.4842@uplift.swm.pp.se>
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <4D907D77.1030904@innovationslab.net>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 12:35:16 -0000

On Mon, 28 Mar 2011, Brian Haberman wrote:

> Hi Mikael,
>
> On 3/28/11 4:25 AM, Mikael Abrahamsson wrote:
>>
>> Hello.
>>
>> I read through 2.3 of the draft, and I am a bit unclear as to how the
>> next-hop should be selected.
>>
>> In the case of my SLAAC machine, I see the next-hop for my default-route
>> as a LL address. How would the SA and the default router LL be tied
>> together?
>
> One way would be for the stack to keep track of which router's LL
> address was the source of the PIO containing the prefix used to generate
> the address.

I realise this is a possibility, but shouldn't there be a mention in the 
draft of recommended mechanisms to achieve this goal?

>> In the case of getting address using DHCPv6, there is also no direct
>> connection between the default route and the SA, as the DHCPv6 server
>> might be different from the default-route gw?
>
> Does the DHCPv6 response contain any information about the DHCP-relay used?

If the DHCPv6 server is just local to the network and doesn't use a relay?

Afaik there has been a deliberate decoupling of stateful DHCPv6 and SLAAC 
so as to make DHCPv6 not able to hand out a default routes, so I don't 
really see how this coupling can be done again with the basic mechanisms 
available today?

In v6ops I was pointed to BRDP 
<http://tools.ietf.org/html/draft-boot-brdp-based-routing-00> which is an 
expired draft, I believe a mechanism like this is needed to properly 
achieve the goal of correct default route for certain SA. I don't really 
see how it can be done otherwise.

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

From dwing@cisco.com  Mon Mar 28 05:46:58 2011
Return-Path: <dwing@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 475203A6A61; Mon, 28 Mar 2011 05:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.488
X-Spam-Level: 
X-Spam-Status: No, score=-110.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uPJyJEybA4YE; Mon, 28 Mar 2011 05:46:57 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 0D72A3A6A56; Mon, 28 Mar 2011 05:46:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2635; q=dns/txt; s=iport; t=1301316514; x=1302526114; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=v7nyfG2aYOT9HpbHi7Bs9lhzL88CRzBZZnCo8LoxTi4=; b=GJGoFuWI8INcP3sk/GbalAcqsq6zlG39ZGD0ezfI5ZjErdBi+n7R33ex 9zK01ektzPn+C/kA4Bvb730Fzuz+esjBSmtHMtWHlczAH7RLi//PM841X P1el7mPwaMDFprkCA+zRQQvv/XGxihHT3WX1oHYcAUzPHXQmTGe1xTcTk g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAKCCkE2rRDoJ/2dsb2JhbACYAYFki1t3pw+bZIVpBA
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="284021027"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 28 Mar 2011 12:48:21 +0000
Received: from dwingWS (sjc-vpn6-310.cisco.com [10.21.121.54]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2SCmJ44023036; Mon, 28 Mar 2011 12:48:20 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Teemu Kiviniemi'" <tekivini@csc.fi>, <teemu.savolainen@nokia.com>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
In-Reply-To: <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi>
Subject: RE: RFC3484-revise and NAT64 Well-Known Prefix
Date: Mon, 28 Mar 2011 14:48:18 +0200
Message-ID: <040201cbed46$6b4c5790$41e506b0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvsuKZl117vMpmdSv2qMkR5SwORbAAjTprw
Content-Language: en-us
Cc: ipv6@ietf.org, behave@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 12:46:58 -0000

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Teemu Kiviniemi
> Sent: Sunday, March 27, 2011 9:53 PM
> To: teemu.savolainen@nokia.com
> Cc: behave@ietf.org; ipv6@ietf.org
> Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
> 
> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
> 
> > I discussed shortly with Arifumi about RFC3484 default policy table
> > updates and NAT64 WKP, i.e. whether the default policy table should
> take
> > a stand on 64:ff9b::/96 preference.
> >
> > It seemed to us that default policy table does not necessarily have
> to,
> > as it could be ok to handle addresses with WKP similarly to global
> IPv6
> > addresses. Furthermore, the default policy table anyway cannot cover
> > Network-Specific Prefixes.
> >
> > Hence prefixes used for protocol translation would be handled like
> > global IPv6 addresses unless something different is configured via
> > policy distribution mechanism? And this should perhaps be documented
> > into the RFC3484-revised.
> 
> I believe native IPv4 should always be preferred over NAT64. Even if
> native IPv4 was using NAT, it is likely to work better with current
> applications than NAT64.
> 
> Preferring IPv4 over the NAT64 well-known prefix does not fix the
> problem
> for network-specific NAT64 prefixes. However, I see no reasons why the
> NAT64 WKP should not be given a lower preference than IPv4 by default.

One reason is that it changes behavior for a network using the well-known
NAT64 prefix versus using their own network's NAT64 prefix.  Not to 
mention they won't know if/when their IPv6 devices are using the new
RFC3484 default table, and will thus start shifting their preference
away from IPv6 (and a NAT64) and towards IPv4 (and a NAPT44, because 
let's be real, everyone will have a NAPT44 if we're talking about an
RFC3484 change).

Personally, I don't see any benefit to changing RFC3484 table to 
accomodate NAT64, assuming there is a way for the host to learn
its NAT64 prefix (draft-korhonen-behave-nat64-learn-analysis).  
Assuming there is no standard way to learn the prefix by the time
we would want to standardize rfc3484bis, I see harm in adding 
the NAT64 well known prefix 64:ff9b::/96 to the default policy 
table.

-d


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


From swmike@swm.pp.se  Mon Mar 28 06:02:26 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 194EA3A6978 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level: 
X-Spam-Status: No, score=-2.258 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRvyjfCA3YIq for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:02:25 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 3185C3A67DA for <ipv6@ietf.org>; Mon, 28 Mar 2011 06:02:25 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 155BF9E; Mon, 28 Mar 2011 15:04:02 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0FF489C; Mon, 28 Mar 2011 15:04:02 +0200 (CEST)
Date: Mon, 28 Mar 2011 15:04:02 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com>
Message-ID: <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se>
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 13:02:26 -0000

On Mon, 28 Mar 2011, Hemant Singh (shemant) wrote:

> It's the IPv6 default router for the DHCPv6 client that sends a RA with 
> the M-bit set and seeing such an RA the client initiates DHCPv6.  Or the 
> client could initiate DHCPv6 even on receiving an RA with the M-bit 
> cleared.  But the fact still remains that the DHCPv6 client did receive 
> an RA from the IPv6 first-hop router to the client.  The client is 
> supposed to perform router discovery and send RS.  The RA lets the 
> client know what the default router is.  If I missed anything, perhaps 
> if you could please draw a diagram and let us know what specific use 
> case I missed.

I'm thinking in the terms of multiple routers on the same LAN but with 
multiple subnets, the multihoming scenario we're discussing in v6ops.

Your above description makes perfect sense for single homing, and if text 
like this (how to tie them together) was present in the draft (or a 
referral to other text describing it), I'd be fine.

Right now I couldn't help reading the text in section 2.3 and wondering 
how it was supposed to achieve what was described.

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

From shemant@cisco.com  Mon Mar 28 06:06:53 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 224FD3A6828 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.672
X-Spam-Level: 
X-Spam-Status: No, score=-10.672 tagged_above=-999 required=5 tests=[AWL=-0.073, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIr5vg5Xf-DR for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:06:52 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 242FA3A680A for <ipv6@ietf.org>; Mon, 28 Mar 2011 06:06:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1297; q=dns/txt; s=iport; t=1301317709; x=1302527309; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=R4pCEQs1rLPMqZPmdnyGO44zX4JwVhhBIFUFDn1nc5o=; b=i+mE3QnTLiFsi2fXARZyiLy82GwJaMN4pv3fajTqKTuYzbC7BtM8qc4+ eVWS3NA4iYV5dZLzjQUCwrDgMxG5sf+FmLoEYU7yR/U4Q4+DkgdLDQWBu bYVltvNYMDaCCyt5jyyPQE2tQYTit2g+Dx7dVnz1KI1RcBX7VbjU/uyvU w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBAFGHkE2tJXG+/2dsb2JhbACYAI0/d6cKm2aFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="284036592"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-3.cisco.com with ESMTP; 28 Mar 2011 13:08:28 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2SD8TEt024969;  Mon, 28 Mar 2011 13:08:29 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 08:08:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Mon, 28 Mar 2011 08:08:26 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5D8@XMB-RCD-109.cisco.com>
In-Reply-To: <4D907D77.1030904@innovationslab.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Thread-Index: AcvtQs4F1EIN0QOVSZeRPLpNha8CjQABBPew
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <4D907D77.1030904@innovationslab.net>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Brian Haberman" <brian@innovationslab.net>, <ipv6@ietf.org>
X-OriginalArrivalTime: 28 Mar 2011 13:08:29.0271 (UTC) FILETIME=[3B411E70:01CBED49]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 13:06:53 -0000

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
Brian Haberman
Sent: Monday, March 28, 2011 2:22 PM
To: ipv6@ietf.org
Subject: Re: question regarding draft-ietf-6man-rfc3484-revise-02
section 2.3


>Does the DHCPv6 response contain any information about the DHCP-relay
used?

No - the reason is because the relay strips the relay-reply from the
server and then sends the response to the client's IPv6 link-local
address.  I am assuming the goal of this discussion is to find out how
does the client gets its default route?  The first-hop router also
happens to be a DHCPv6 relay agent. The email that I just sent will be
able to let the client know what the mac-address of the default router
is.  Thus when the client sends a globally destined packet upstream
towards the default router, the packet has a global destination and
global source (the source global address was acquired from DHCPv6).  The
packet is shipped to the default router using the mac-address of the
first-hop default router.=20

My humble apologies if I did not understand the question being asked.
If that is the case, please articulate which node or policy table needs
to decide what for a SA and then we can discuss more.

Thanks,

Hemant

From shemant@cisco.com  Mon Mar 28 06:12:07 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 410E73A680A for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.37
X-Spam-Level: 
X-Spam-Status: No, score=-10.37 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N30-ILEzbjAR for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:12:04 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 159B23A6803 for <ipv6@ietf.org>; Mon, 28 Mar 2011 06:12:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=662; q=dns/txt; s=iport; t=1301318022; x=1302527622; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=lRWlV/RAxV55TiQU2ipzjkn7zRClWqXsGTdSBnyeyCM=; b=R4KUyRi8sQsLcyWvGQnW7zIbKT6HhrjOK5H8meonxdLis+GBmwvQM2Yo PeC2wic+Rd9TkHgxRWG8oScnFo1aHjmqnq/bTOAhw232ynjXaxlsnkSlB 4Nb1RHdIbNB1KuIJP8+3GYcm3xCLJ/u9LPt/E2nNNofWnrg2V17DOFekf M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBADGJkE2tJV2b/2dsb2JhbACYAI0/d6Z8m2aFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="671721377"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by sj-iport-6.cisco.com with ESMTP; 28 Mar 2011 13:13:40 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2SDDerL011414;  Mon, 28 Mar 2011 13:13:40 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 08:13:40 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Mon, 28 Mar 2011 08:13:38 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5DD@XMB-RCD-109.cisco.com>
In-Reply-To: <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Thread-Index: AcvtSMa4kdS9EW+xSS6zbTrYWGnohAAAN6Lg
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>
X-OriginalArrivalTime: 28 Mar 2011 13:13:40.0576 (UTC) FILETIME=[F4CE7E00:01CBED49]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 13:12:07 -0000

-----Original Message-----
From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
Sent: Monday, March 28, 2011 3:04 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02
section 2.3


>I'm thinking in the terms of multiple routers on the same LAN but with=20
>multiple subnets, the multihoming scenario we're discussing in v6ops.

Ah, thanks for this clarification.  No I understand the problem at hand.
Sorry, I haven't read the document being discussed here.  Let me started
from the section 2.3 of this document and then also mull over the
multihoming issue.

Thanks,

Hemant

From fernando.gont.netbook.win@gmail.com  Mon Mar 28 06:17:35 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 097433A67EA for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:17:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FwpPr77TWcT6 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 06:17:34 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 3D9F83A67E4 for <ipv6@ietf.org>; Mon, 28 Mar 2011 06:17:34 -0700 (PDT)
Received: by iye19 with SMTP id 19so3546477iye.31 for <ipv6@ietf.org>; Mon, 28 Mar 2011 06:19:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=U89aR3XuZ+0j6J4UqlzGE7ZWdtIBcTkA1X1FB91BYU0=; b=b6742DKVE8UreyYaq5wyNPDxUBLCJWzrnW0OAvUs6ffhXX+UrUabHMzb9AsTvcuUVn k8vnzHPsCudhf45AOJyRpRv3+aVKjs118z9CTaHZLMl7+4JLO9xNChkZxgTJmX/oZZTF 8lEyEQxEsHnK7XtSE17n0z9FqQNFZT5GnwahE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=KPmzCFYHGCYYufDTapqKmQdiw0QxEYCGP+FnlqxrUTdgwcju/Mxgbt5CjluK88RMT2 vUnd7WGY89Le+8Z2U+iF9T7/3F6nSNib6aqJjovHelClFyein8Sin3MsmwOs2Z9UHbSC o6dFoLC3YpcpU2+fiqMTy66532Ck89iCBZQ2w=
Received: by 10.43.48.130 with SMTP id uw2mr6276131icb.312.1301318351679; Mon, 28 Mar 2011 06:19:11 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id gy41sm2951760ibb.39.2011.03.28.06.19.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Mar 2011 06:19:10 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D908AC9.9080708@gont.com.ar>
Date: Mon, 28 Mar 2011 10:19:05 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: FW: comment on draft-gont-6man-managing-privacy-extensions-01
References: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E587@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E587@XMB-RCD-109.cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 13:17:35 -0000

On 28/03/2011 05:06 a.m., Hemant Singh (shemant) wrote:

> In some certain large-scale broadband networks, an RA does not even
> include any PIO, so how will this document signal new bits? 

I guess that those networks employ something else for host
configuration? (e.g., DHCP) -- If that's the case, such deployments are
out of scope, as this proposal is only meant from addressesconfigured as
a result of SLAAC.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From shemant@cisco.com  Mon Mar 28 07:27:22 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 203BD3A684D for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 07:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.664
X-Spam-Level: 
X-Spam-Status: No, score=-10.664 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlRtMwgy4egl for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 07:27:20 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id E485F3A6805 for <ipv6@ietf.org>; Mon, 28 Mar 2011 07:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1781; q=dns/txt; s=iport; t=1301322538; x=1302532138; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=JEr2sm1nZXoA0rHjPOT5qb/fFZkvMt1o0a0ELH7T6oU=; b=aFSftpoydEv8qllDR7vh5FMFaoRVc+4wTEJkY72zwRdONKSKG8PN0BGv 7KavoMm7CPuI14oUpWFh17vETnUjSfRj8R7EMIAsYBIDjigwDev0Gj/F3 cH9LZ2zmeJ/yyakLBvR53nG12QigrGiD3bSOXIUq/qOTlWv1GXUnsvuOl g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBABiakE2tJXG//2dsb2JhbACYAI0/d6ZXm22FaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,255,1299456000"; d="scan'208";a="325877184"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by sj-iport-2.cisco.com with ESMTP; 28 Mar 2011 14:28:58 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2SESwVV005468;  Mon, 28 Mar 2011 14:28:58 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 09:28:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Mon, 28 Mar 2011 09:28:55 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E663@XMB-RCD-109.cisco.com>
In-Reply-To: <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Thread-Index: AcvtSMa4kdS9EW+xSS6zbTrYWGnohAAB1jVQ
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>
X-OriginalArrivalTime: 28 Mar 2011 14:28:58.0264 (UTC) FILETIME=[798EF980:01CBED54]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 14:27:22 -0000

=20
-----Original Message-----
From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
Sent: Monday, March 28, 2011 3:04 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02
section 2.3

Mikael,

>Right now I couldn't help reading the text in section 2.3 and wondering

>how it was supposed to achieve what was described.

[If SA is assigned by the selected next-hop that will be used to send to
D and SB is assigned by a different next-hop, then prefer SA.
Similarly, if SB is assigned by the next-hop that will be used to send
to D and SA is assigned by a different next-hop, then prefer SB.]

Here is an attempt to explain the text above from section 2.3 of the
document that I have included between squared brackets above.  SA was
acquired using DHCPv6 where the DHCPv6 response did arrive to the client
on the IPv6 link-local address of the first-hop.  The client already
knows this link-local address matches a mac-address of, say,
mac-address1 obtained from the RA from the same first-hop router.  Thus
SA is associated with Router 1 (from Figure 1 of section 2.1.1 of RFC
5220).  Likewise SB is associated with Router 2 with mac-addr of say,
mac-address2.  Thus far we established that SA is used when sending to
the default router of Router 1 and likewise for SB with Router 2.  An
orthogonal question is how does the host know for a destination D which
default router to go to - should such a question be addressed by this
document?  If yes, then an out of band mechanism is needed to let the
host know what default router to use for a destination D.  One out of
band mechanism is use an MSR to signal a specific route to the host.

Did I miss anything?

Thanks,

Hemant

From swmike@swm.pp.se  Mon Mar 28 08:59:53 2011
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DDF428C0DC for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 08:59:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTTj5SsWCKWZ for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 08:59:52 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 6452E28C0D9 for <ipv6@ietf.org>; Mon, 28 Mar 2011 08:59:52 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9814E9C; Mon, 28 Mar 2011 18:01:28 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 95CA19A; Mon, 28 Mar 2011 18:01:28 +0200 (CEST)
Date: Mon, 28 Mar 2011 18:01:28 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E663@XMB-RCD-109.cisco.com>
Message-ID: <alpine.DEB.2.00.1103281755550.4842@uplift.swm.pp.se>
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E663@XMB-RCD-109.cisco.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 15:59:53 -0000

On Mon, 28 Mar 2011, Hemant Singh (shemant) wrote:

> Here is an attempt to explain the text above from section 2.3 of the 
> document that I have included between squared brackets above.  SA was 
> acquired using DHCPv6 where the DHCPv6 response did arrive to the client 
> on the IPv6 link-local address of the first-hop.  The client already 
> knows this link-local address matches a mac-address of, say, 
> mac-address1 obtained from the RA from the same first-hop router.  Thus 
> SA is associated with Router 1 (from Figure 1 of section 2.1.1 of RFC 
> 5220).  Likewise SB is associated with Router 2 with mac-addr of say, 
> mac-address2.  Thus far we established that SA is used when sending to 
> the default router of Router 1 and likewise for SB with Router 2.  An 
> orthogonal question is how does the host know for a destination D which 
> default router to go to - should such a question be addressed by this 
> document?  If yes, then an out of band mechanism is needed to let the 
> host know what default router to use for a destination D.  One out of 
> band mechanism is use an MSR to signal a specific route to the host.
>
> Did I miss anything?

I am not at all worried about "destination D". Destination based routing 
we know how to do already, we can always add an IGP.

Source based routing is more magic.

Your above text is approximately what I envisioned how things could work, 
and I do think there needs to be text somewhere that describes this. I am 
though worried that it would require quite a lot of work to implement this 
because of the decoupling between DHCPv6 and routing as I mentioned 
before, since for instance on Linux the kernel handles RA and DHCP client 
runs in userspace. They will need to invent new APIs or move things around 
to handle what we're requiring here.

Anyhow, the above text seems fine to me from a technical point of view, 
nothing pops up as weird or wrong anyway. I think it needs a second look 
over before it's ready for publishing?

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

From shemant@cisco.com  Mon Mar 28 09:38:23 2011
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 923DC28C106 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 09:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.663
X-Spam-Level: 
X-Spam-Status: No, score=-10.663 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tq6+9rnkr8R8 for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 09:38:22 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 2235D28C107 for <ipv6@ietf.org>; Mon, 28 Mar 2011 09:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=872; q=dns/txt; s=iport; t=1301330400; x=1302540000; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=Do0LIGYZDeYL8datTDx10PbdgJe1Kt//7xWFw9NAJl4=; b=Md5MNFJtHBdoq0EvgI2QK0OEbtQ73pDRnCZNv6ST9GhJwvV+yiZVUhl9 y87EWd8hyVv5rdXt1BdS8mLV47ioWrBa0kBMOlXJveK88WQefALjoJRZk WD5F90Psk85yi5VGEBaIIQwf/7hN7Z+CmVst06461f5XYlZRZZPfhVVGG U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYBALS5kE2tJXG9/2dsb2JhbACYBY1Ad6cDnAeFaQSFOosX
X-IronPort-AV: E=Sophos;i="4.63,256,1299456000"; d="scan'208";a="284193183"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-3.cisco.com with ESMTP; 28 Mar 2011 16:39:52 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2SGdq4i020704;  Mon, 28 Mar 2011 16:39:52 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 28 Mar 2011 11:39:52 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Mon, 28 Mar 2011 11:39:53 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30121E76C@XMB-RCD-109.cisco.com>
In-Reply-To: <alpine.DEB.2.00.1103281755550.4842@uplift.swm.pp.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Thread-Index: AcvtYXb4nI2FoMMUTcmhYEU3dQCrtAABChtg
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E5C1@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103281501150.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C30121E663@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103281755550.4842@uplift.swm.pp.se>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Mikael Abrahamsson" <swmike@swm.pp.se>
X-OriginalArrivalTime: 28 Mar 2011 16:39:52.0642 (UTC) FILETIME=[C321F220:01CBED66]
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 Mar 2011 16:38:23 -0000

-----Original Message-----
From: Mikael Abrahamsson [mailto:swmike@swm.pp.se]=20
Sent: Monday, March 28, 2011 6:01 PM
To: Hemant Singh (shemant)
Cc: ipv6@ietf.org
Subject: RE: question regarding draft-ietf-6man-rfc3484-revise-02
section 2.3


>Anyhow, the above text seems fine to me from a technical point of view,

>nothing pops up as weird or wrong anyway. I think it needs a second
look=20
>over before it's ready for publishing?

Ah, the text I wrote is in conversational language and I don't deem the
text for use in an RFC.  However, if the WG thinks such text needs
addition to this document, I'd be happy to provide more tighter text.
For example, change mac-addr to link-layer address and the fact that if
the link layer supports addresses, it is the IPv6 ND Source Link-Layer
Address option that carries the link-layer address.

Hemant

From jjamil@earthlink.net  Mon Mar 28 18:30:50 2011
Return-Path: <jjamil@earthlink.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3DEB28C0DF for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 18:30:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qipl5tEk9jaT for <ipv6@core3.amsl.com>; Mon, 28 Mar 2011 18:30:49 -0700 (PDT)
Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by core3.amsl.com (Postfix) with ESMTP id 158B23A6833 for <ipv6@ietf.org>; Mon, 28 Mar 2011 18:30:49 -0700 (PDT)
Received: from [192.168.1.2] ([unknown] [108.23.140.158]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LIS007KOPLR7LU3@vms173005.mailsrvcs.net> for ipv6@ietf.org; Mon, 28 Mar 2011 20:32:16 -0500 (CDT)
Message-id: <4D91369C.1070301@earthlink.net>
Date: Mon, 28 Mar 2011 18:32:12 -0700
From: Jaffer <jjamil@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-version: 1.0
To: D64AB84F-1977-491F-8A2D-01BC49F09A5A@gmail.com, bob.hinden@gmail.com, ipv6@ietf.org
Subject: Re: Need minute taker and jabber scribe(s)
Content-type: multipart/alternative; boundary=------------010606020707090904020101
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 01:30:50 -0000

This is a multi-part message in MIME format.
--------------010606020707090904020101
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bob,

What are the times involved and how often? Please feel free to email me directly. I may need some info about whether to use one of your existing Jabber accounts/IDs or create one for this purpose.

Thanks,

Jaffer Jamil


------------------------------

Message: 5
Date: Mon, 28 Mar 2011 08:52:13 +0200
From: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Need minute taker and jabber scribe(s)
To: 6man Mailing List <ipv6@ietf.org>
Cc: Bob Hinden <bob.hinden@gmail.com>
Message-ID: <D64AB84F-1977-491F-8A2D-01BC49F09A5A@gmail.com>
Content-Type: text/plain; charset=us-ascii

Still looking for a jabber scribe.

Bob

On Mar 25, 2011, at 9:44 PM, Bob Hinden wrote:

>> We still need a jabber scribe. 
>> 
>> Thanks to Suresh for volunteering to take minutes.
>> 
>> Thanks,
>> Bob
>> 
>> 
>> On Mar 22, 2011, at 7:32 PM, Bob Hinden wrote:
>> 
>  
>
>>>> We are looking for volunteers to take minutes and jabber scribe for the 6man session on Monday morning in Prague.
>>>> 
>>>> It a great service to the working group and the IETF!
>>>> 
>>>> Thanks,
>>>> Bob & Brian
>>>> 
>>>> 
>>    
>>
>> 
>  
>



------------------------------


--------------010606020707090904020101
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<pre wrap=""><big><font face="Arial">Bob,</font>

<font face="Arial">What are the times involved and how often? Please feel free to email me directly. I may need some info about whether to use one of your existing Jabber accounts/IDs or create one for this purpose.</font>

<font face="Arial">Thanks,</font>

<font face="Arial">Jaffer Jamil</font></big>
</pre>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 28 Mar 2011 08:52:13 +0200<br>
From: Bob Hinden <a class="moz-txt-link-rfc2396E"
 href="mailto:bob.hinden@gmail.com">&lt;bob.hinden@gmail.com&gt;</a><br>
Subject: Re: Need minute taker and jabber scribe(s)<br>
To: 6man Mailing List <a class="moz-txt-link-rfc2396E"
 href="mailto:ipv6@ietf.org">&lt;ipv6@ietf.org&gt;</a><br>
Cc: Bob Hinden <a class="moz-txt-link-rfc2396E"
 href="mailto:bob.hinden@gmail.com">&lt;bob.hinden@gmail.com&gt;</a><br>
Message-ID: <a class="moz-txt-link-rfc2396E"
 href="mailto:D64AB84F-1977-491F-8A2D-01BC49F09A5A@gmail.com">&lt;D64AB84F-1977-491F-8A2D-01BC49F09A5A@gmail.com&gt;</a><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Still looking for a jabber scribe.<br>
<br>
Bob<br>
<br>
On Mar 25, 2011, at 9:44 PM, Bob Hinden wrote:<br>
<br>
<blockquote type="cite">
  <pre wrap=""><span class="moz-txt-citetags">&gt; </span>We still need a jabber scribe. 
<span class="moz-txt-citetags">&gt; </span>
<span class="moz-txt-citetags">&gt; </span>Thanks to Suresh for volunteering to take minutes.
<span class="moz-txt-citetags">&gt; </span>
<span class="moz-txt-citetags">&gt; </span>Thanks,
<span class="moz-txt-citetags">&gt; </span>Bob
<span class="moz-txt-citetags">&gt; </span>
<span class="moz-txt-citetags">&gt; </span>
<span class="moz-txt-citetags">&gt; </span>On Mar 22, 2011, at 7:32 PM, Bob Hinden wrote:
<span class="moz-txt-citetags">&gt; </span>
  </pre>
  <blockquote type="cite">
    <pre wrap=""><span class="moz-txt-citetags">&gt;&gt; </span>We are looking for volunteers to take minutes and jabber scribe for the 6man session on Monday morning in Prague.
<span class="moz-txt-citetags">&gt;&gt; </span>
<span class="moz-txt-citetags">&gt;&gt; </span>It a great service to the working group and the IETF!
<span class="moz-txt-citetags">&gt;&gt; </span>
<span class="moz-txt-citetags">&gt;&gt; </span>Thanks,
<span class="moz-txt-citetags">&gt;&gt; </span>Bob &amp; Brian
<span class="moz-txt-citetags">&gt;&gt; </span>
<span class="moz-txt-citetags">&gt;&gt; </span>
    </pre>
  </blockquote>
  <pre wrap=""><span class="moz-txt-citetags">&gt; </span>
  </pre>
</blockquote>
<pre wrap=""><!---->


------------------------------</pre>
</body>
</html>

--------------010606020707090904020101--

From Internet-Drafts@ietf.org  Tue Mar 29 01:45:04 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F72F3A692D; Tue, 29 Mar 2011 01:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ak+N2obwuTCo; Tue, 29 Mar 2011 01:45:03 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADAD03A68CE; Tue, 29 Mar 2011 01:45:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-rpl-option-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.14
Message-ID: <20110329084503.15983.86800.idtracker@localhost>
Date: Tue, 29 Mar 2011 01:45:03 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 08:45:04 -0000

--NextPart

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


	Title           : RPL Option for Carrying RPL Information in Data-Plane Datagrams
	Author(s)       : J. Hui, J. Vasseur
	Filename        : draft-ietf-6man-rpl-option-03.txt
	Pages           : 14
	Date            : 2011-03-29

The RPL protocol requires data-plane datagrams to carry RPL routing
information that is processed by RPL routers when forwarding those
datagrams.  This document describes the RPL option for use within a
RPL domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-option-03.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-6man-rpl-option-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-29013041.I-D@ietf.org>


--NextPart--

From Internet-Drafts@ietf.org  Tue Mar 29 01:45:04 2011
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 777503A6917; Tue, 29 Mar 2011 01:45:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X92Kc38to6Wa; Tue, 29 Mar 2011 01:45:03 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C21403A6918; Tue, 29 Mar 2011 01:45:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-ietf-6man-rpl-routing-header-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.14
Message-ID: <20110329084503.15983.17057.idtracker@localhost>
Date: Tue, 29 Mar 2011 01:45:03 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 08:45:04 -0000

--NextPart

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


	Title           : An IPv6 Routing Header for Source Routes with RPL
	Author(s)       : J. Hui, et al.
	Filename        : draft-ietf-6man-rpl-routing-header-03.txt
	Pages           : 19
	Date            : 2011-03-29

In Low power and Lossy Networks (LLNs), memory constraints on routers
may limit them to maintaining at most a few routes.  In some
configurations, it is necessary to use these memory constrained
routers to deliver datagrams to nodes within the LLN.  The Routing
for Low Power and Lossy Networks (RPL) protocol can be used in some
deployments to store most, if not all, routes on one (e.g. the
Directed Acyclic Graph (DAG) root) or few routers and forward the
IPv6 datagram using a source routing technique to avoid large routing
tables on memory constrained routers.  This document specifies a new
IPv6 Routing header type for delivering datagrams within a RPL
domain.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-6man-rpl-routing-header-03.txt

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-6man-rpl-routing-header-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-03-29013125.I-D@ietf.org>


--NextPart--

From suresh.krishnan@ericsson.com  Tue Mar 29 03:45:49 2011
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D63813A6952; Tue, 29 Mar 2011 03:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.906
X-Spam-Level: 
X-Spam-Status: No, score=-104.906 tagged_above=-999 required=5 tests=[AWL=1.693, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pE9wlVwmrE9S; Tue, 29 Mar 2011 03:45:49 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id CDC343A68D4; Tue, 29 Mar 2011 03:45:48 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p2TAlMES029914; Tue, 29 Mar 2011 05:47:23 -0500
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.203]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 29 Mar 2011 06:47:16 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Dan Wing <dwing@cisco.com>, "'Teemu Kiviniemi'" <tekivini@csc.fi>, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
Date: Tue, 29 Mar 2011 06:47:15 -0400
Subject: RE: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
Thread-Topic: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
Thread-Index: AcvsuKZl117vMpmdSv2qMkR5SwORbAAjTprwAC3irhA=
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150F161274E@EUSAACMS0703.eamcs.ericsson.se>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <040201cbed46$6b4c5790$41e506b0$@com>
In-Reply-To: <040201cbed46$6b4c5790$41e506b0$@com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "behave@ietf.org" <behave@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 10:45:49 -0000

Hi Dan/Teemu(s)/Cameron,
  I am afraid there is no single right answer here. There will be networks =
that will prefer NAT44 over NAT64 and those that prefer NAT64 over NAT44. F=
or this reason, I think this is better left as a site-specific policy decis=
ion for distribution using a mechanism such as draft-ietf-6man-addr-select-=
opt. So, I agree with Dan and Cameron that we should not add an entry to th=
e default table for the NAT64 prefix.

Cheers
Suresh=20

> -----Original Message-----
> From: behave-bounces@ietf.org=20
> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> Sent: Monday, March 28, 2011 2:48 PM
> To: 'Teemu Kiviniemi'; teemu.savolainen@nokia.com
> Cc: ipv6@ietf.org; behave@ietf.org
> Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]=20
> On Behalf=20
> > Of Teemu Kiviniemi
> > Sent: Sunday, March 27, 2011 9:53 PM
> > To: teemu.savolainen@nokia.com
> > Cc: behave@ietf.org; ipv6@ietf.org
> > Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
> >=20
> > On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
> >=20
> > > I discussed shortly with Arifumi about RFC3484 default=20
> policy table=20
> > > updates and NAT64 WKP, i.e. whether the default policy=20
> table should
> > take
> > > a stand on 64:ff9b::/96 preference.
> > >
> > > It seemed to us that default policy table does not=20
> necessarily have
> > to,
> > > as it could be ok to handle addresses with WKP similarly to global
> > IPv6
> > > addresses. Furthermore, the default policy table anyway=20
> cannot cover=20
> > > Network-Specific Prefixes.
> > >
> > > Hence prefixes used for protocol translation would be=20
> handled like=20
> > > global IPv6 addresses unless something different is=20
> configured via=20
> > > policy distribution mechanism? And this should perhaps be=20
> documented=20
> > > into the RFC3484-revised.
> >=20
> > I believe native IPv4 should always be preferred over=20
> NAT64. Even if=20
> > native IPv4 was using NAT, it is likely to work better with current=20
> > applications than NAT64.
> >=20
> > Preferring IPv4 over the NAT64 well-known prefix does not fix the=20
> > problem for network-specific NAT64 prefixes. However, I see=20
> no reasons=20
> > why the
> > NAT64 WKP should not be given a lower preference than IPv4=20
> by default.
>=20
> One reason is that it changes behavior for a network using=20
> the well-known
> NAT64 prefix versus using their own network's NAT64 prefix. =20
> Not to mention they won't know if/when their IPv6 devices are=20
> using the new
> RFC3484 default table, and will thus start shifting their=20
> preference away from IPv6 (and a NAT64) and towards IPv4 (and=20
> a NAPT44, because let's be real, everyone will have a NAPT44=20
> if we're talking about an
> RFC3484 change).
>=20
> Personally, I don't see any benefit to changing RFC3484 table=20
> to accomodate NAT64, assuming there is a way for the host to=20
> learn its NAT64 prefix (draft-korhonen-behave-nat64-learn-analysis). =20
> Assuming there is no standard way to learn the prefix by the=20
> time we would want to standardize rfc3484bis, I see harm in=20
> adding the NAT64 well known prefix 64:ff9b::/96 to the=20
> default policy table.
>=20
> -d
>=20
>=20
> > --
> > Teemu
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>=20
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
> =

From arifumi@nttv6.net  Tue Mar 29 08:14:46 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB4E23A6824 for <ipv6@core3.amsl.com>; Tue, 29 Mar 2011 08:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.013
X-Spam-Level: 
X-Spam-Status: No, score=-102.013 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Spikqi6Pg59k for <ipv6@core3.amsl.com>; Tue, 29 Mar 2011 08:14:46 -0700 (PDT)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by core3.amsl.com (Postfix) with ESMTP id EE1B73A6984 for <ipv6@ietf.org>; Tue, 29 Mar 2011 08:14:45 -0700 (PDT)
Received: from [IPv6:::1] (localhost.nttv6.net [IPv6:::1]) by leo.nttv6.net (8.14.4/8.14.3) with ESMTP id p2TFF3S7014302; Wed, 30 Mar 2011 00:15:04 +0900 (JST) (envelope-from arifumi@nttv6.net)
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <4D907D77.1030904@innovationslab.net> <alpine.DEB.2.00.1103281431180.4842@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1103281431180.4842@uplift.swm.pp.se>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <A19FA9C8-ED0E-4F5F-A5D0-702653392B5E@nttv6.net>
Content-Transfer-Encoding: quoted-printable
From: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3
Date: Wed, 30 Mar 2011 00:15:03 +0900
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1084)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 15:14:47 -0000

Hi, Mikael, Hemant,

I think Mikael's concern is fair and it should be addressed clearer in =
this document.

I agree that this rule is applicable when
- SLAAC is used for address assignment.
, or
- DHCPv6 server/relay is used for address assignment and it's on the =
router sending RA.

Also, I understand DHCPv6 client is often in userland, so it's not =
trivial to implement it.

So, the description of this rule should be like:

If the implementation can know and manage the coupling of a next-hop and =
a prefix
delegated from it, then the corresponding prefix should be chosen as the =
source address.
For example, in SLAAC case, ... (the description of how the coupling is =
acquired and used)

Regarding whether this new rule should be included in 3484bis,
I know some rules in RFC 3484 is implementation dependent.=20
For example,  the destination address selection rule 1: "avoid unusable =
destinations"
is implemented in several ways.
So, I do not think implementation dependent rule is always bad.
The point should be how much benefits we see in this proposed rule.

Best regards,

On 2011/03/28, at 21:36, Mikael Abrahamsson wrote:

> On Mon, 28 Mar 2011, Brian Haberman wrote:
>=20
>> Hi Mikael,
>>=20
>> On 3/28/11 4:25 AM, Mikael Abrahamsson wrote:
>>>=20
>>> Hello.
>>>=20
>>> I read through 2.3 of the draft, and I am a bit unclear as to how =
the
>>> next-hop should be selected.
>>>=20
>>> In the case of my SLAAC machine, I see the next-hop for my =
default-route
>>> as a LL address. How would the SA and the default router LL be tied
>>> together?
>>=20
>> One way would be for the stack to keep track of which router's LL
>> address was the source of the PIO containing the prefix used to =
generate
>> the address.
>=20
> I realise this is a possibility, but shouldn't there be a mention in =
the draft of recommended mechanisms to achieve this goal?
>=20
>>> In the case of getting address using DHCPv6, there is also no direct
>>> connection between the default route and the SA, as the DHCPv6 =
server
>>> might be different from the default-route gw?
>>=20
>> Does the DHCPv6 response contain any information about the DHCP-relay =
used?
>=20
> If the DHCPv6 server is just local to the network and doesn't use a =
relay?
>=20
> Afaik there has been a deliberate decoupling of stateful DHCPv6 and =
SLAAC so as to make DHCPv6 not able to hand out a default routes, so I =
don't really see how this coupling can be done again with the basic =
mechanisms available today?
>=20
> In v6ops I was pointed to BRDP =
<http://tools.ietf.org/html/draft-boot-brdp-based-routing-00> which is =
an expired draft, I believe a mechanism like this is needed to properly =
achieve the goal of correct default route for certain SA. I don't really =
see how it can be done otherwise.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From arifumi@nttv6.net  Tue Mar 29 08:24:26 2011
Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34CA73A682B; Tue, 29 Mar 2011 08:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.312
X-Spam-Level: 
X-Spam-Status: No, score=-102.312 tagged_above=-999 required=5 tests=[AWL=0.287, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9L972GluD7b; Tue, 29 Mar 2011 08:24:25 -0700 (PDT)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by core3.amsl.com (Postfix) with ESMTP id DB7403A6824; Tue, 29 Mar 2011 08:24:24 -0700 (PDT)
Received: from [IPv6:::1] (localhost.nttv6.net [IPv6:::1]) by leo.nttv6.net (8.14.4/8.14.3) with ESMTP id p2TFOXgm014360; Wed, 30 Mar 2011 00:24:34 +0900 (JST) (envelope-from arifumi@nttv6.net)
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <040201cbed46$6b4c5790$41e506b0$@com> <4FD1E7CD248BF84F86BD4814EDDDBCC150F161274E@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC150F161274E@EUSAACMS0703.eamcs.ericsson.se>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <8B54EB8B-F0A6-4FAD-A364-1524EA08600E@nttv6.net>
Content-Transfer-Encoding: quoted-printable
From: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
Date: Wed, 30 Mar 2011 00:24:33 +0900
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, 'Teemu Kiviniemi' <tekivini@csc.fi>, "behave@ietf.org" <behave@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 15:24:26 -0000

Hi,

thank you for insightful comments on this issue, all.
I'll put some texts in the next version to note discussions about it.

Best regards,

On 2011/03/29, at 19:47, Suresh Krishnan wrote:

> Hi Dan/Teemu(s)/Cameron,
>  I am afraid there is no single right answer here. There will be =
networks that will prefer NAT44 over NAT64 and those that prefer NAT64 =
over NAT44. For this reason, I think this is better left as a =
site-specific policy decision for distribution using a mechanism such as =
draft-ietf-6man-addr-select-opt. So, I agree with Dan and Cameron that =
we should not add an entry to the default table for the NAT64 prefix.
>=20
> Cheers
> Suresh=20
>=20
>> -----Original Message-----
>> From: behave-bounces@ietf.org=20
>> [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
>> Sent: Monday, March 28, 2011 2:48 PM
>> To: 'Teemu Kiviniemi'; teemu.savolainen@nokia.com
>> Cc: ipv6@ietf.org; behave@ietf.org
>> Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
>>=20
>>> -----Original Message-----
>>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]=20
>> On Behalf=20
>>> Of Teemu Kiviniemi
>>> Sent: Sunday, March 27, 2011 9:53 PM
>>> To: teemu.savolainen@nokia.com
>>> Cc: behave@ietf.org; ipv6@ietf.org
>>> Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
>>>=20
>>> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
>>>=20
>>>> I discussed shortly with Arifumi about RFC3484 default=20
>> policy table=20
>>>> updates and NAT64 WKP, i.e. whether the default policy=20
>> table should
>>> take
>>>> a stand on 64:ff9b::/96 preference.
>>>>=20
>>>> It seemed to us that default policy table does not=20
>> necessarily have
>>> to,
>>>> as it could be ok to handle addresses with WKP similarly to global
>>> IPv6
>>>> addresses. Furthermore, the default policy table anyway=20
>> cannot cover=20
>>>> Network-Specific Prefixes.
>>>>=20
>>>> Hence prefixes used for protocol translation would be=20
>> handled like=20
>>>> global IPv6 addresses unless something different is=20
>> configured via=20
>>>> policy distribution mechanism? And this should perhaps be=20
>> documented=20
>>>> into the RFC3484-revised.
>>>=20
>>> I believe native IPv4 should always be preferred over=20
>> NAT64. Even if=20
>>> native IPv4 was using NAT, it is likely to work better with current=20=

>>> applications than NAT64.
>>>=20
>>> Preferring IPv4 over the NAT64 well-known prefix does not fix the=20
>>> problem for network-specific NAT64 prefixes. However, I see=20
>> no reasons=20
>>> why the
>>> NAT64 WKP should not be given a lower preference than IPv4=20
>> by default.
>>=20
>> One reason is that it changes behavior for a network using=20
>> the well-known
>> NAT64 prefix versus using their own network's NAT64 prefix. =20
>> Not to mention they won't know if/when their IPv6 devices are=20
>> using the new
>> RFC3484 default table, and will thus start shifting their=20
>> preference away from IPv6 (and a NAT64) and towards IPv4 (and=20
>> a NAPT44, because let's be real, everyone will have a NAPT44=20
>> if we're talking about an
>> RFC3484 change).
>>=20
>> Personally, I don't see any benefit to changing RFC3484 table=20
>> to accomodate NAT64, assuming there is a way for the host to=20
>> learn its NAT64 prefix (draft-korhonen-behave-nat64-learn-analysis). =20=

>> Assuming there is no standard way to learn the prefix by the=20
>> time we would want to standardize rfc3484bis, I see harm in=20
>> adding the NAT64 well known prefix 64:ff9b::/96 to the=20
>> default policy table.
>>=20
>> -d
>>=20
>>=20
>>> --
>>> Teemu
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>> _______________________________________________
>> Behave mailing list
>> Behave@ietf.org
>> https://www.ietf.org/mailman/listinfo/behave
>>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From brian@innovationslab.net  Wed Mar 30 08:10:22 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0E843A6847; Wed, 30 Mar 2011 08:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxPlXuC8F1JD; Wed, 30 Mar 2011 08:10:21 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 51DD53A6821; Wed, 30 Mar 2011 08:10:18 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id EA932882A8; Wed, 30 Mar 2011 08:11:57 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2AA50130002; Wed, 30 Mar 2011 08:11:55 -0700 (PDT)
Message-ID: <4D934836.10801@innovationslab.net>
Date: Wed, 30 Mar 2011 11:11:50 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: iesg-secretary@ietf.org, 6man-ads@tools.ietf.org
Subject: Request To Advance: <draft-ietf-6man-rpl-option-03.txt>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 WG Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 15:10:22 -0000

Jari & Ralph,
     On behalf of the 6MAN WG, the chairs request the advancement of:

     Title     : RPL Option for Carrying RPL Information in
                 Data-Plane Datagrams
     Author(s) : J. Hui, J. Vasseur
     Filename  : draft-ietf-6man-rpl-option-03.txt
     Pages     : 14
     Date      : 2011-03-29

as a Proposed Standard.  A 6MAN WG Last Call ended on December 6, 2010
and this version addresses all comments raised.

Regards,
Brian & Bob

From brian@innovationslab.net  Wed Mar 30 08:10:28 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A933E3A6B70; Wed, 30 Mar 2011 08:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XuzhAHX1DAna; Wed, 30 Mar 2011 08:10:28 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id 05D9B3A6B69; Wed, 30 Mar 2011 08:10:28 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 4965D882AA; Wed, 30 Mar 2011 08:12:07 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 55EE9130003; Wed, 30 Mar 2011 08:12:06 -0700 (PDT)
Message-ID: <4D934844.1090106@innovationslab.net>
Date: Wed, 30 Mar 2011 11:12:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: iesg-secretary@ietf.org, 6man-ads@tools.ietf.org
Subject: Request To Advance: <draft-ietf-6man-rpl-routing-header-03.txt>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, IPv6 WG Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 15:10:28 -0000

Jari & Ralph,
     On behalf of the 6MAN WG, the chairs request the advancement of:

     Title     : An IPv6 Routing Header for Source Routes with RPL
     Author(s) : J. Hui, et al.
     Filename  : draft-ietf-6man-rpl-routing-header-03.txt
     Pages     : 19
     Date      : 2011-03-29

as a Proposed Standard.  A 6MAN WG Last Call ended on December 6, 2010
and this version addresses all comments raised.

Regards,
Brian & Bob

From jari.arkko@piuha.net  Wed Mar 30 08:21:26 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A4C03A6A20 for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zson5ePx6wrH for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:21:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 48AA83A690D for <ipv6@ietf.org>; Wed, 30 Mar 2011 08:21:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6B5322CC3B; Wed, 30 Mar 2011 18:23:02 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DGyd5FSyXja; Wed, 30 Mar 2011 18:23:01 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 2D2D12CC2F; Wed, 30 Mar 2011 18:23:01 +0300 (EEST)
Message-ID: <4D934AD4.2030701@piuha.net>
Date: Wed, 30 Mar 2011 17:23:00 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: Request To Advance: <draft-ietf-6man-rpl-option-03.txt>
References: <4D934836.10801@innovationslab.net>
In-Reply-To: <4D934836.10801@innovationslab.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man-ads@tools.ietf.org, IPv6 WG Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 15:21:26 -0000

Got it. Thanks.

jari

Brian Haberman kirjoitti:
> Jari & Ralph,
>      On behalf of the 6MAN WG, the chairs request the advancement of:
>
>      Title     : RPL Option for Carrying RPL Information in
>                  Data-Plane Datagrams
>      Author(s) : J. Hui, J. Vasseur
>      Filename  : draft-ietf-6man-rpl-option-03.txt
>      Pages     : 14
>      Date      : 2011-03-29
>
> as a Proposed Standard.  A 6MAN WG Last Call ended on December 6, 2010
> and this version addresses all comments raised.
>
> Regards,
> Brian & Bob
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>   


From pch-b6B5344D9@u-1.phicoh.com  Wed Mar 30 08:47:44 2011
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 091A53A6B71 for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:47:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0HRhYVZ2a-n for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:47:43 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id AB2D13A6A48 for <ipv6@ietf.org>; Wed, 30 Mar 2011 08:47:41 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1Q4xe2-0001VHC; Wed, 30 Mar 2011 17:49 +0200
Message-Id: <m1Q4xe2-0001VHC@stereo.hq.phicoh.net>
To: Arifumi Matsumoto <arifumi@nttv6.net>
Subject: Re: question regarding draft-ietf-6man-rfc3484-revise-02 section 2.3 
From: Philip Homburg <pch-6man@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <alpine.DEB.2.00.1103281015240.4842@uplift.swm.pp.se> <4D907D77.1030904@innovationslab.net> <alpine.DEB.2.00.1103281431180.4842@uplift.swm.pp.se> <A19FA9C8-ED0E-4F5F-A5D0-702653392B5E@nttv6.net> 
In-reply-to: Your message of "Wed, 30 Mar 2011 00:15:03 +0900 ." <A19FA9C8-ED0E-4F5F-A5D0-702653392B5E@nttv6.net> 
Date: Wed, 30 Mar 2011 17:49:05 +0200
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 15:47:44 -0000

In your letter dated Wed, 30 Mar 2011 00:15:03 +0900 you wrote:
>So, the description of this rule should be like:
>
>If the implementation can know and manage the coupling of a next-hop and a pre
>fix
>delegated from it, then the corresponding prefix should be chosen as the sourc
>e address.
>For example, in SLAAC case, ... (the description of how the coupling is acquir
>ed and used)

I think this is fine as an optimization, but do we really want to force hosts
to be involved in routing packets?

So far, the model is that a host can just dump a packet at a default router
and the router will figure it out.

In more complex setups, i.e. where there are multiple CPEs providing access
to different ISPs but also multiple internal LANs at the site, routers will
have to know the right exit for a packet anyhow.

So I would propose to focus on (and put emphasis on) getting routers to 
send packets to the right ISP and only add changes to the hosts as an
optimization.



From fernando.gont.netbook.win@gmail.com  Wed Mar 30 10:13:55 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABF593A6BA2 for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 10:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level: 
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id peC1lbvoIusx for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 10:13:54 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 6221528C12E for <ipv6@ietf.org>; Wed, 30 Mar 2011 10:13:54 -0700 (PDT)
Received: by bwz13 with SMTP id 13so1224976bwz.31 for <ipv6@ietf.org>; Wed, 30 Mar 2011 10:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:subject:x-enigmail-version:openpgp:content-type :content-transfer-encoding; bh=/XX+XoJZWDS3gHaImKGPv+Lo8UkqfpCa2sCaZBImuPI=; b=EHYTpYw9E/T92fbqfDOYwowGWVATCPlKMYbgTvmXYdtDPYI3XlAMpwBXhKKcsc+/79 wdANi1fgnufADNtzY3S8UCupfN6ziVXqKjcWZm1QWXoQwgU88iq4IUZt9L1ndu6s5HcS TvIQJgLeQ8VA5frZ7xSJvEkNaIYkhS0z+eZPQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=ePSS33SAQ8K9u2TbIv3JsdDmer9b31pNBT7qqMRcp0Jd+8x/7D7sbyXhdyTOi28Riv KIExPYqgvcxui1vomXpFGqyqgWRzs1iPpn1BerRKQxuVD/E2JsL/EPz6OKL2LrhSHfBZ 0fJwI1HIGcnG4Oyj5ZdL0+N+2ht8w91eYaaGM=
Received: by 10.204.165.193 with SMTP id j1mr1469308bky.11.1301505332840; Wed, 30 Mar 2011 10:15:32 -0700 (PDT)
Received: from [130.129.16.243] (dhcp-10f3.meeting.ietf.org [130.129.16.243]) by mx.google.com with ESMTPS id c11sm213047bkc.14.2011.03.30.10.15.31 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Mar 2011 10:15:31 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D9361F8.60203@gont.com.ar>
Date: Wed, 30 Mar 2011 14:01:44 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: draft-gont-6man-managing-privacy-extensions
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 17:13:55 -0000

Folks,

At the 6man wg meeting, the aforementioned I-D was deemed "as a very bad
idea", because of its privacy implications.

My question is: what's the trust model that leads to that conclusion?

I mean, a host doing SLAAC trusts the router about the prefix to be
configured, default route, various network parameters (Hop Count, MTU,
etc.), recursive DNS resolver, etc.

Why do folks consider that for some of this information, the router is
to be trusted, while for other (the SAG bits that our I-D specifies)
shouldn't?

That aside, if a router is deemed as possibly malicious, even without
the SAG bits it could claim that DHCPv6 is needed, and then have the
DHCP server lease an address that embeds the source link-layer address
of the DHCPv6 request...

*And*, as noted in the upcoming version that I had posted, the final
decision on which policy to apply is on de hands of the host (and not
the router).

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1





From denghui02@gmail.com  Tue Mar 29 04:37:36 2011
Return-Path: <denghui02@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2017E28C156; Tue, 29 Mar 2011 04:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWy5xDbsmWaE; Tue, 29 Mar 2011 04:37:34 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 399513A67CC; Tue, 29 Mar 2011 04:37:34 -0700 (PDT)
Received: by iye19 with SMTP id 19so94243iye.31 for <multiple recipients>; Tue, 29 Mar 2011 04:39:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=qLRnAU/oRQeRQzLpnQWtqg91lgRR81Ua4+bXSXadW6g=; b=OEDyEvzIs40MQDvNpI2F+9B1fjPxn61owGBbmQZtX7StzDlALP7aOj8gENuJbkLe45 Q84UpDx7j3ywWTdJd5RjNRMbGtKzIWVc0aYxr9QM3X+M0DHl3n1tvIW9ZHmqvCvXYAKJ Be5zyuFfSWR+jZWfSrUEx0o8JfEOaZ/28Bs2o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NFunJczumTEgZwCc/TD+PWwUXSseaCjcyFfKmUcpN8L9sBNDWWrF7Jg9m9i3sruBDz nknmJc8y+2wlzp/XKMCGSG7F9Rbg+6bUDWdxll4oRLzKXzejq8aU5SjdLr1aRKVPRhKi /qJvMe+1/xXsCc/nEiMfbunNQMmkjtncubDAY=
MIME-Version: 1.0
Received: by 10.42.66.147 with SMTP id p19mr9120535ici.7.1301398752304; Tue, 29 Mar 2011 04:39:12 -0700 (PDT)
Received: by 10.42.224.71 with HTTP; Tue, 29 Mar 2011 04:39:12 -0700 (PDT)
In-Reply-To: <4FD1E7CD248BF84F86BD4814EDDDBCC150F161274E@EUSAACMS0703.eamcs.ericsson.se>
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <040201cbed46$6b4c5790$41e506b0$@com> <4FD1E7CD248BF84F86BD4814EDDDBCC150F161274E@EUSAACMS0703.eamcs.ericsson.se>
Date: Tue, 29 Mar 2011 13:39:12 +0200
Message-ID: <AANLkTin1mv55bZoiRiV0mCJzQOT7D3O0TiqxDKgBOcyB@mail.gmail.com>
Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
From: Hui Deng <denghui02@gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/alternative; boundary=90e6ba614eec579df1049f9d8243
X-Mailman-Approved-At: Wed, 30 Mar 2011 11:37:35 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Teemu Kiviniemi <tekivini@csc.fi>, "behave@ietf.org" <behave@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 Mar 2011 11:37:36 -0000

--90e6ba614eec579df1049f9d8243
Content-Type: text/plain; charset=ISO-8859-1

make sense

-Hui

2011/3/29 Suresh Krishnan <suresh.krishnan@ericsson.com>

> Hi Dan/Teemu(s)/Cameron,
>  I am afraid there is no single right answer here. There will be networks
> that will prefer NAT44 over NAT64 and those that prefer NAT64 over NAT44.
> For this reason, I think this is better left as a site-specific policy
> decision for distribution using a mechanism such as
> draft-ietf-6man-addr-select-opt. So, I agree with Dan and Cameron that we
> should not add an entry to the default table for the NAT64 prefix.
>
> Cheers
> Suresh
>
> > -----Original Message-----
> > From: behave-bounces@ietf.org
> > [mailto:behave-bounces@ietf.org] On Behalf Of Dan Wing
> > Sent: Monday, March 28, 2011 2:48 PM
> > To: 'Teemu Kiviniemi'; teemu.savolainen@nokia.com
> > Cc: ipv6@ietf.org; behave@ietf.org
> > Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix
> >
> > > -----Original Message-----
> > > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org]
> > On Behalf
> > > Of Teemu Kiviniemi
> > > Sent: Sunday, March 27, 2011 9:53 PM
> > > To: teemu.savolainen@nokia.com
> > > Cc: behave@ietf.org; ipv6@ietf.org
> > > Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
> > >
> > > On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
> > >
> > > > I discussed shortly with Arifumi about RFC3484 default
> > policy table
> > > > updates and NAT64 WKP, i.e. whether the default policy
> > table should
> > > take
> > > > a stand on 64:ff9b::/96 preference.
> > > >
> > > > It seemed to us that default policy table does not
> > necessarily have
> > > to,
> > > > as it could be ok to handle addresses with WKP similarly to global
> > > IPv6
> > > > addresses. Furthermore, the default policy table anyway
> > cannot cover
> > > > Network-Specific Prefixes.
> > > >
> > > > Hence prefixes used for protocol translation would be
> > handled like
> > > > global IPv6 addresses unless something different is
> > configured via
> > > > policy distribution mechanism? And this should perhaps be
> > documented
> > > > into the RFC3484-revised.
> > >
> > > I believe native IPv4 should always be preferred over
> > NAT64. Even if
> > > native IPv4 was using NAT, it is likely to work better with current
> > > applications than NAT64.
> > >
> > > Preferring IPv4 over the NAT64 well-known prefix does not fix the
> > > problem for network-specific NAT64 prefixes. However, I see
> > no reasons
> > > why the
> > > NAT64 WKP should not be given a lower preference than IPv4
> > by default.
> >
> > One reason is that it changes behavior for a network using
> > the well-known
> > NAT64 prefix versus using their own network's NAT64 prefix.
> > Not to mention they won't know if/when their IPv6 devices are
> > using the new
> > RFC3484 default table, and will thus start shifting their
> > preference away from IPv6 (and a NAT64) and towards IPv4 (and
> > a NAPT44, because let's be real, everyone will have a NAPT44
> > if we're talking about an
> > RFC3484 change).
> >
> > Personally, I don't see any benefit to changing RFC3484 table
> > to accomodate NAT64, assuming there is a way for the host to
> > learn its NAT64 prefix (draft-korhonen-behave-nat64-learn-analysis).
> > Assuming there is no standard way to learn the prefix by the
> > time we would want to standardize rfc3484bis, I see harm in
> > adding the NAT64 well known prefix 64:ff9b::/96 to the
> > default policy table.
> >
> > -d
> >
> >
> > > --
> > > Teemu
> > > --------------------------------------------------------------------
> > > IETF IPv6 working group mailing list
> > > ipv6@ietf.org
> > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > --------------------------------------------------------------------
> >
> > _______________________________________________
> > Behave mailing list
> > Behave@ietf.org
> > https://www.ietf.org/mailman/listinfo/behave
> >
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>

--90e6ba614eec579df1049f9d8243
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>make sense</div>
<div>=A0</div>
<div>-Hui<br><br></div>
<div class=3D"gmail_quote">2011/3/29 Suresh Krishnan <span dir=3D"ltr">&lt;=
<a href=3D"mailto:suresh.krishnan@ericsson.com">suresh.krishnan@ericsson.co=
m</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">Hi Dan/Teemu(s)/Cameron,<br>=A0I=
 am afraid there is no single right answer here. There will be networks tha=
t will prefer NAT44 over NAT64 and those that prefer NAT64 over NAT44. For =
this reason, I think this is better left as a site-specific policy decision=
 for distribution using a mechanism such as draft-ietf-6man-addr-select-opt=
. So, I agree with Dan and Cameron that we should not add an entry to the d=
efault table for the NAT64 prefix.<br>
<br>Cheers<br><font color=3D"#888888">Suresh<br></font>
<div>
<div></div>
<div class=3D"h5"><br>&gt; -----Original Message-----<br>&gt; From: <a href=
=3D"mailto:behave-bounces@ietf.org">behave-bounces@ietf.org</a><br>&gt; [ma=
ilto:<a href=3D"mailto:behave-bounces@ietf.org">behave-bounces@ietf.org</a>=
] On Behalf Of Dan Wing<br>
&gt; Sent: Monday, March 28, 2011 2:48 PM<br>&gt; To: &#39;Teemu Kiviniemi&=
#39;; <a href=3D"mailto:teemu.savolainen@nokia.com">teemu.savolainen@nokia.=
com</a><br>&gt; Cc: <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>; <a =
href=3D"mailto:behave@ietf.org">behave@ietf.org</a><br>
&gt; Subject: Re: [BEHAVE] RFC3484-revise and NAT64 Well-Known Prefix<br>&g=
t;<br>&gt; &gt; -----Original Message-----<br>&gt; &gt; From: <a href=3D"ma=
ilto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.org</a> [mailto:<a href=3D"ma=
ilto:ipv6-bounces@ietf.org">ipv6-bounces@ietf.org</a>]<br>
&gt; On Behalf<br>&gt; &gt; Of Teemu Kiviniemi<br>&gt; &gt; Sent: Sunday, M=
arch 27, 2011 9:53 PM<br>&gt; &gt; To: <a href=3D"mailto:teemu.savolainen@n=
okia.com">teemu.savolainen@nokia.com</a><br>&gt; &gt; Cc: <a href=3D"mailto=
:behave@ietf.org">behave@ietf.org</a>; <a href=3D"mailto:ipv6@ietf.org">ipv=
6@ietf.org</a><br>
&gt; &gt; Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix<br>&gt; &=
gt;<br>&gt; &gt; On Sun, 27 Mar 2011, <a href=3D"mailto:teemu.savolainen@no=
kia.com">teemu.savolainen@nokia.com</a> wrote:<br>&gt; &gt;<br>&gt; &gt; &g=
t; I discussed shortly with Arifumi about RFC3484 default<br>
&gt; policy table<br>&gt; &gt; &gt; updates and NAT64 WKP, i.e. whether the=
 default policy<br>&gt; table should<br>&gt; &gt; take<br>&gt; &gt; &gt; a =
stand on 64:ff9b::/96 preference.<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; It se=
emed to us that default policy table does not<br>
&gt; necessarily have<br>&gt; &gt; to,<br>&gt; &gt; &gt; as it could be ok =
to handle addresses with WKP similarly to global<br>&gt; &gt; IPv6<br>&gt; =
&gt; &gt; addresses. Furthermore, the default policy table anyway<br>&gt; c=
annot cover<br>
&gt; &gt; &gt; Network-Specific Prefixes.<br>&gt; &gt; &gt;<br>&gt; &gt; &g=
t; Hence prefixes used for protocol translation would be<br>&gt; handled li=
ke<br>&gt; &gt; &gt; global IPv6 addresses unless something different is<br=
>
&gt; configured via<br>&gt; &gt; &gt; policy distribution mechanism? And th=
is should perhaps be<br>&gt; documented<br>&gt; &gt; &gt; into the RFC3484-=
revised.<br>&gt; &gt;<br>&gt; &gt; I believe native IPv4 should always be p=
referred over<br>
&gt; NAT64. Even if<br>&gt; &gt; native IPv4 was using NAT, it is likely to=
 work better with current<br>&gt; &gt; applications than NAT64.<br>&gt; &gt=
;<br>&gt; &gt; Preferring IPv4 over the NAT64 well-known prefix does not fi=
x the<br>
&gt; &gt; problem for network-specific NAT64 prefixes. However, I see<br>&g=
t; no reasons<br>&gt; &gt; why the<br>&gt; &gt; NAT64 WKP should not be giv=
en a lower preference than IPv4<br>&gt; by default.<br>&gt;<br>&gt; One rea=
son is that it changes behavior for a network using<br>
&gt; the well-known<br>&gt; NAT64 prefix versus using their own network&#39=
;s NAT64 prefix.<br>&gt; Not to mention they won&#39;t know if/when their I=
Pv6 devices are<br>&gt; using the new<br>&gt; RFC3484 default table, and wi=
ll thus start shifting their<br>
&gt; preference away from IPv6 (and a NAT64) and towards IPv4 (and<br>&gt; =
a NAPT44, because let&#39;s be real, everyone will have a NAPT44<br>&gt; if=
 we&#39;re talking about an<br>&gt; RFC3484 change).<br>&gt;<br>&gt; Person=
ally, I don&#39;t see any benefit to changing RFC3484 table<br>
&gt; to accomodate NAT64, assuming there is a way for the host to<br>&gt; l=
earn its NAT64 prefix (draft-korhonen-behave-nat64-learn-analysis).<br>&gt;=
 Assuming there is no standard way to learn the prefix by the<br>&gt; time =
we would want to standardize rfc3484bis, I see harm in<br>
&gt; adding the NAT64 well known prefix 64:ff9b::/96 to the<br>&gt; default=
 policy table.<br>&gt;<br>&gt; -d<br>&gt;<br>&gt;<br>&gt; &gt; --<br>&gt; &=
gt; Teemu<br>&gt; &gt; ----------------------------------------------------=
----------------<br>
&gt; &gt; IETF IPv6 working group mailing list<br>&gt; &gt; <a href=3D"mail=
to:ipv6@ietf.org">ipv6@ietf.org</a><br>&gt; &gt; Administrative Requests: <=
a href=3D"https://www.ietf.org/mailman/listinfo/ipv6" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; &gt; -----------------------------------------------------------------=
---<br>&gt;<br>&gt; _______________________________________________<br>&gt;=
 Behave mailing list<br>&gt; <a href=3D"mailto:Behave@ietf.org">Behave@ietf=
.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/behave</a><br>&gt;<br>__________=
_____________________________________<br>Behave mailing list<br><a href=3D"=
mailto:Behave@ietf.org">Behave@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/behave" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/behave</a><br></div></div></blockquot=
e></div><br>

--90e6ba614eec579df1049f9d8243--

From radoslaw.wrobel@pwr.wroc.pl  Wed Mar 30 08:30:36 2011
Return-Path: <radoslaw.wrobel@pwr.wroc.pl>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CCBB3A6B6C for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.387
X-Spam-Level: 
X-Spam-Status: No, score=0.387 tagged_above=-999 required=5 tests=[BAYES_50=0.001, GB_I_LETTER=-2, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHztlIGZhjvG for <ipv6@core3.amsl.com>; Wed, 30 Mar 2011 08:30:35 -0700 (PDT)
Received: from sun1000.pwr.wroc.pl (sun1000.pwr.wroc.pl [156.17.1.33]) by core3.amsl.com (Postfix) with ESMTP id CC2173A6B72 for <ipv6@ietf.org>; Wed, 30 Mar 2011 08:30:34 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_LJBiQLKkpCrfk6wzqxlOBA)"
Received: from sparrow ([156.17.28.130]) by sun1000.pwr.wroc.pl (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPSA id <0LIV00JNRN5BLU40@sun1000.pwr.wroc.pl> for ipv6@ietf.org; Wed, 30 Mar 2011 17:31:59 +0200 (CEST)
X-autoryzacja: Submit
Sender: radoslaw.wrobel@pwr.wroc.pl
Message-id: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
From: =?iso-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
To: ipv6@ietf.org
Subject: Vehicle's VIN in IPv6.
Date: Wed, 30 Mar 2011 17:31:56 +0200
X-Priority: 3
X-MSMail-priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
X-Antivirus: avast! (VPS 110330-0, 2011-03-30), Outbound message
X-Antivirus-Status: Clean
X-Mailman-Approved-At: Wed, 30 Mar 2011 11:37:35 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 Mar 2011 15:43:25 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_LJBiQLKkpCrfk6wzqxlOBA)
Content-type: text/plain; charset=iso-8859-2
Content-transfer-encoding: 7BIT

Dear 6man!
My name is Radek Wrobel, I'm writing from Poland (I'm working in Wroclaw University of Technology, Division of Car Vehicles and Combustion Engines). With this idea I wrote to IANA and Leo Vegoda redirected me to you. 
Vehicle / mechanic engineers are working on a new On Board Diagnosis standard for vehicles (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 can diagnose (quasi online) 849 failures. One of most important advantage of EOBDv2 (but not only it) will be constant, real time communication with service. The best way of them will be indyvidual number for every car vehicles in the world. This number ought to cooporate with global networking - TCP/IP (IPv6). All cars have indyvidual number - VIN (17 characters which indicates on a country of production  and mark of the car: digits and letters A-X). Maybe there is time when someone must think about conversion VIN to IPv6 (like it's in local IPv4)? I've a few ideas about it and of course I can share them if you will be intersting in. 
Also we cooperate with VW and Toyota. I think they will be interesting about it too.
Best regards, Radek Wrobel.
+48660406004

--Boundary_(ID_LJBiQLKkpCrfk6wzqxlOBA)
Content-type: text/html; charset=iso-8859-2
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-2" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19019">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>Dear 6man!</DIV>
<DIV>My name is Radek Wrobel, I'm writing from Poland (I'm working in Wroclaw 
University of Technology, Division of Car Vehicles and Combustion 
Engines).&nbsp;With this idea I wrote to IANA and Leo Vegoda redirected&nbsp;me 
to you. </DIV>
<DIV>Vehicle / mechanic&nbsp;engineers&nbsp;are working on a new On Board 
Diagnosis standard for vehicles (<A 
href="http://en.wikipedia.org/wiki/On-board_diagnostics">http://en.wikipedia.org/wiki/On-board_diagnostics</A>). 
Today EOBDv1 can diagnose (quasi online) 849 failures.&nbsp;One of most 
important advantage of EOBDv2 (but not only it) will be constant, real time 
communication with service.&nbsp;The best way of them will be indyvidual number 
for every car vehicles in the world. This number ought to cooporate with global 
networking - TCP/IP (IPv6). All cars have indyvidual number - VIN 
(17&nbsp;characters which indicates on a country of production&nbsp; and mark of 
the car: digits and letters A-X).&nbsp;Maybe there is time when someone must 
think about conversion VIN to IPv6 (like it's in local IPv4)? I've a few ideas 
about it and of course I can share them if you will be intersting in. </DIV>
<DIV>Also we cooperate with VW and Toyota. I think they will be interesting 
about it too.</DIV>
<DIV>Best regards, Radek Wrobel.</DIV>
<DIV>+48660406004</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_LJBiQLKkpCrfk6wzqxlOBA)--

From scott.brim@gmail.com  Thu Mar 31 01:38:53 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD0AF3A6B14 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 01:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.434
X-Spam-Level: 
X-Spam-Status: No, score=-104.434 tagged_above=-999 required=5 tests=[AWL=0.865, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P33hKX0OQB4z for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 01:38:52 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id A3E383A6AFA for <ipv6@ietf.org>; Thu, 31 Mar 2011 01:38:52 -0700 (PDT)
Received: by iye19 with SMTP id 19so2474533iye.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 01:40:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=oWlvoHD3L8NNL7KOKazHo66xrJnT8HnUt/DehYwsONE=; b=mGaZBqBTOGg2Twri1/HSVavg4GmH7/HKeMbcbfSDuSXWmwpk7pXrGcKQFnGcX43nQ+ TFFruvX3Nh95FnNyoq1EVc4JpDqjj4iDoGDesSck37RUW0dJBilUiD8iFQxje3xQyOle RgmM7KDpi2iga2HJXmsTn+ELJC3oqZ8lplEfw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=tQaR05JP0Dnlf0FjSLo7EcNvIF97kxvn+unmFRC0sjadQi9yHWXD9V2MRdeJ1LoLVc tRPlo8IXiZTHpO14opazHXXKcEYJS6Z3sPQF2Pv2tXduPZI5RK5DTAy6JCQzrPzBHoPk I5cEVC05NZOfCpeS+D+vbuoXIT6feyoQtIxtw=
Received: by 10.42.131.200 with SMTP id a8mr2670303ict.415.1301560832103; Thu, 31 Mar 2011 01:40:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.225.133 with HTTP; Thu, 31 Mar 2011 01:40:12 -0700 (PDT)
In-Reply-To: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 Mar 2011 10:40:12 +0200
Message-ID: <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
To: =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 08:38:53 -0000

Hello Radek.

I have privacy concerns, because the VIN is permanent for the vehicle.
 I suspect there is a good chance that the vehicle's IP address will
not be used just for diagnostics, but also for general purpose
connections to the Internet (for example fetching a movie for the
children).  If an IP address is based on VIN, then it will never
change, ever.  It will be possible for observers to build up
information about what the vehicle's users like to connect to.

Also, if you are a diagnostic center and you receive packets from an
IP address claiming to have a particular VIN number, how do you
authenticate it?  How do you know that is really the vehicle it claims
to be?  You will need application layer authentication in any case.

I believe it would be much better to decouple "vehicle identification"
from "IP layer location" (the IP address).  These tokens have
different purposes.  The vehicle identification is for use with
database applications and diagnostic applications, while the IP
address is for IP forwarding to know how to reach the vehicle.  You
could possibly allow the vehicle to connect to the network and get any
IP address -- any address at all -- and then connect to the diagnostic
center and tell you its VIN and authenticate, all in a higher layer
protocol.

2011/3/30 Radek Wr=F3bel <radoslaw.wrobel@pwr.wroc.pl>:
> Dear 6man!
> My name is Radek Wrobel, I'm writing from Poland (I'm working in Wroclaw
> University of Technology, Division of Car Vehicles and Combustion
> Engines).=A0With this idea I wrote to IANA and Leo Vegoda redirected=A0me=
 to
> you.
> Vehicle / mechanic=A0engineers=A0are working on a new On Board Diagnosis
> standard for vehicles (http://en.wikipedia.org/wiki/On-board_diagnostics)=
.
> Today EOBDv1 can diagnose (quasi online) 849 failures.=A0One of most impo=
rtant
> advantage of EOBDv2 (but not only it) will be constant, real time
> communication with service.=A0The best way of them will be indyvidual num=
ber
> for every car vehicles in the world. This number ought to cooporate with
> global networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
> (17=A0characters which indicates on a country of production=A0 and mark o=
f the
> car: digits and letters A-X).=A0Maybe there is time when someone must thi=
nk
> about conversion VIN to IPv6 (like it's in local IPv4)? I've a few ideas
> about it and of course I can share them if you will be intersting in.
> Also we cooperate with VW and Toyota. I think they will be interesting ab=
out
> it too.
> Best regards, Radek Wrobel.
> +48660406004
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

From ggm+ietf@apnic.net  Thu Mar 31 01:44:20 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FE613A6AFA for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 01:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7UIXbi74Lzw for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 01:44:19 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by core3.amsl.com (Postfix) with ESMTP id 4AE2D3A6AFD for <ipv6@ietf.org>; Thu, 31 Mar 2011 01:44:09 -0700 (PDT)
Received: from dhcp-54ae.meeting.ietf.org (dhcp-54ae.meeting.ietf.org [130.129.84.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id CB627B681F for <ipv6@ietf.org>; Thu, 31 Mar 2011 18:45:44 +1000 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Vehicle's VIN in IPv6.
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
Date: Thu, 31 Mar 2011 10:45:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 08:44:20 -0000

There is a general model here which will re-occur many many times.

manufacturers have context-specific serial numbers which behave in =
context like EUI164.

It is reasonable (from their perspective) to ask if there is an address =
management function which can suit their context, to exploit IPv6. =
Perhaps a private overlay network for IPSEC trusted remote upload and =
download. re-blow your SONY TV on any Internet via a trust path homed =
inside the manufacturer. 'ET call home' models of device management.

I believe we have to have this discussion, but can I point out that =
global address policy lies in many places, only some of which are held =
in IETF Mailing lists.

So, a decision to establish a registry which spans outside of the =
private domain, and touches into global-unicast behaviours really has to =
be far, far wider than 'here'

It has to encompass the RIR process, basically. Or, clarify why its not =
in that model/space.

128 bits is a higher trust. we have to run this in the wider public =
interest. We currently hold ourselves to a tiny footprint for a reason, =
but that reason doesn't EXCLUDE this discussion, it certainly informs =
it.

-George (personal capacity)

On 31/03/2011, at 10:40 AM, Scott Brim wrote:

> Hello Radek.
>=20
> I have privacy concerns, because the VIN is permanent for the vehicle.
> I suspect there is a good chance that the vehicle's IP address will
> not be used just for diagnostics, but also for general purpose
> connections to the Internet (for example fetching a movie for the
> children).  If an IP address is based on VIN, then it will never
> change, ever.  It will be possible for observers to build up
> information about what the vehicle's users like to connect to.
>=20
> Also, if you are a diagnostic center and you receive packets from an
> IP address claiming to have a particular VIN number, how do you
> authenticate it?  How do you know that is really the vehicle it claims
> to be?  You will need application layer authentication in any case.
>=20
> I believe it would be much better to decouple "vehicle identification"
> from "IP layer location" (the IP address).  These tokens have
> different purposes.  The vehicle identification is for use with
> database applications and diagnostic applications, while the IP
> address is for IP forwarding to know how to reach the vehicle.  You
> could possibly allow the vehicle to connect to the network and get any
> IP address -- any address at all -- and then connect to the diagnostic
> center and tell you its VIN and authenticate, all in a higher layer
> protocol.
>=20
> 2011/3/30 Radek Wr=F3bel <radoslaw.wrobel@pwr.wroc.pl>:
>> Dear 6man!
>> My name is Radek Wrobel, I'm writing from Poland (I'm working in =
Wroclaw
>> University of Technology, Division of Car Vehicles and Combustion
>> Engines). With this idea I wrote to IANA and Leo Vegoda redirected me =
to
>> you.
>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>> standard for vehicles =
(http://en.wikipedia.org/wiki/On-board_diagnostics).
>> Today EOBDv1 can diagnose (quasi online) 849 failures. One of most =
important
>> advantage of EOBDv2 (but not only it) will be constant, real time
>> communication with service. The best way of them will be indyvidual =
number
>> for every car vehicles in the world. This number ought to cooporate =
with
>> global networking - TCP/IP (IPv6). All cars have indyvidual number - =
VIN
>> (17 characters which indicates on a country of production  and mark =
of the
>> car: digits and letters A-X). Maybe there is time when someone must =
think
>> about conversion VIN to IPv6 (like it's in local IPv4)? I've a few =
ideas
>> about it and of course I can share them if you will be intersting in.
>> Also we cooperate with VW and Toyota. I think they will be =
interesting about
>> it too.
>> Best regards, Radek Wrobel.
>> +48660406004
>>=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 roland.bless@kit.edu  Thu Mar 31 02:02:05 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1331E28C181 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.066
X-Spam-Level: 
X-Spam-Status: No, score=-7.066 tagged_above=-999 required=5 tests=[AWL=0.883,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNJ6qWsCh58b for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:02:04 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id C152828C188 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:02:03 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5Dmw-0002u2-3E; Thu, 31 Mar 2011 11:03:42 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 4A6AA2C6; Thu, 31 Mar 2011 11:06:28 +0200 (CEST)
Message-ID: <4D944365.4020809@kit.edu>
Date: Thu, 31 Mar 2011 11:03:33 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
In-Reply-To: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: quoted-printable
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301562222.752788000
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:02:05 -0000

Hi Radek,

On 30.03.2011 17:31, Radek Wr=F3bel wrote:
> Vehicle / mechanic engineers are working on a new On Board Diagnosis
> standard for vehicles
> (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 can
> diagnose (quasi online) 849 failures. One of most important advantage o=
f
> EOBDv2 (but not only it) will be constant, real time communication with
> service. The best way of them will be indyvidual number for every car
> vehicles in the world. This number ought to cooporate with global
> networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
> (17 characters which indicates on a country of production  and mark of
> the car: digits and letters A-X). Maybe there is time when someone must
> think about conversion VIN to IPv6 (like it's in local IPv4)? I've a fe=
w
> ideas about it and of course I can share them if you will be intersting=
 in.

There is already related work for this.
You should be aware of a US Patent of 2005 "Method for Setting an
Internet Protocol Address using a vehicle identification number".
US 2005/0273505 A1, first hit
http://www.google.com/patents?q=3DVIN+IPv6&btnG=3DSearch+Patents
(no comment on its usefulness here...)
BMW has also recently filed a patent application with a VIN7 to IPv6
address mapping.
It's not totally clear to me what _problem_ you want to solve.
Depending on that several options exist.
However, I share the concerns that Scott Brim already expressed in his
mail.

Regards,
 Roland

From thierry.ernst@inria.fr  Thu Mar 31 02:06:21 2011
Return-Path: <thierry.ernst@inria.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A858828C1B6 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.249
X-Spam-Level: 
X-Spam-Status: No, score=-11.249 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qaZuXw4sqFN for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:06:16 -0700 (PDT)
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by core3.amsl.com (Postfix) with ESMTP id 21FEB28C186 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:06:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.63,274,1299452400";  d="vcf'?scan'208";a="95447081"
Received: from dhcp-rocq-243.inria.fr ([128.93.62.243]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 31 Mar 2011 11:07:54 +0200
Message-ID: <4D94446C.40008@inria.fr>
Date: Thu, 31 Mar 2011 11:07:56 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
Organization: INRIA
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
In-Reply-To: <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------070100010206040201080606"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:06:21 -0000

This is a multi-part message in MIME format.
--------------070100010206040201080606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Dear all,

I fail to see why a VIN would be mapped to an IPv6 address as much as I 
fail to see why a passport number would be mapped to an IPv6 number. As 
said by Scott, the purpose of the IP address is to forward packets to 
the destination.

Such an idea is going against location privacy. To address the location 
privacy issue related to the ID of the vehicle used at the networking 
layer, the Car-to-Car Communication Consortium propose to use 
pseudonyms; when it goes to IPv6 communications (all communications are 
not IP-based) this pseudonym is used to configure an IPv6 address, i.e. 
a transient address (you can check the work of the SeVeCom project). In 
the meantime, the vehicle also has a permanent address (indeed, prefix) 
as which the vehicle is reachable (using NEMO). Up to now, there is no 
one in any of the standardisation or consortium I know (ETSI TC ITS, ISO 
TC204, ISO TC22, CEN TC278, Car2Car Communication Consortium) who is 
thinking about mapping a vehicle ID to the IPv6 address.

So, I'm afraid this idea is going nowhere.

Regards,
Thierry Ernst.

On 31/03/11 10:40, Scott Brim wrote:
> Hello Radek.
>
> I have privacy concerns, because the VIN is permanent for the vehicle.
>   I suspect there is a good chance that the vehicle's IP address will
> not be used just for diagnostics, but also for general purpose
> connections to the Internet (for example fetching a movie for the
> children).  If an IP address is based on VIN, then it will never
> change, ever.  It will be possible for observers to build up
> information about what the vehicle's users like to connect to.
>
> Also, if you are a diagnostic center and you receive packets from an
> IP address claiming to have a particular VIN number, how do you
> authenticate it?  How do you know that is really the vehicle it claims
> to be?  You will need application layer authentication in any case.
>
> I believe it would be much better to decouple "vehicle identification"
> from "IP layer location" (the IP address).  These tokens have
> different purposes.  The vehicle identification is for use with
> database applications and diagnostic applications, while the IP
> address is for IP forwarding to know how to reach the vehicle.  You
> could possibly allow the vehicle to connect to the network and get any
> IP address -- any address at all -- and then connect to the diagnostic
> center and tell you its VIN and authenticate, all in a higher layer
> protocol.
>
> 2011/3/30 Radek Wr骲el<radoslaw.wrobel@pwr.wroc.pl>:
>> Dear 6man!
>> My name is Radek Wrobel, I'm writing from Poland (I'm working in Wroclaw
>> University of Technology, Division of Car Vehicles and Combustion
>> Engines). With this idea I wrote to IANA and Leo Vegoda redirected me to
>> you.
>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>> standard for vehicles (http://en.wikipedia.org/wiki/On-board_diagnostics).
>> Today EOBDv1 can diagnose (quasi online) 849 failures. One of most important
>> advantage of EOBDv2 (but not only it) will be constant, real time
>> communication with service. The best way of them will be indyvidual number
>> for every car vehicles in the world. This number ought to cooporate with
>> global networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
>> (17 characters which indicates on a country of production  and mark of the
>> car: digits and letters A-X). Maybe there is time when someone must think
>> about conversion VIN to IPv6 (like it's in local IPv4)? I've a few ideas
>> about it and of course I can share them if you will be intersting in.
>> Also we cooperate with VW and Toyota. I think they will be interesting about
>> it too.
>> Best regards, Radek Wrobel.
>> +48660406004
>>
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------


--------------070100010206040201080606
Content-Type: text/x-vcard; charset=utf-8;
 name="thierry_ernst.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="thierry_ernst.vcf"

begin:vcard
fn:Thierry  Ernst
n:Ernst;Thierry 
org:INRIA - Project Team IMARA - LaRA JRU
tel;work:+33 1 3963 59 30
tel;fax:+33 1 39 63 54 91
tel;cell:+33 6 76 56 25 96
url:http://www.lara.prd.fr
version:2.1
end:vcard


--------------070100010206040201080606--

From brian.e.carpenter@gmail.com  Thu Mar 31 02:09:11 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0F6B28C1FF for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CzKrY8tfdEE2 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:09:10 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 3F98D28C201 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:08:57 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2045737wyb.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:10:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b5lrXRdVtJ2naLwG7P2h0preA+5wMLJHZtsAfoaDaUY=; b=R7YUQekWBDdCjCWo7181kOrFvu31/yoAqQyAACVA01Z0WhkWrxXl97Fzjj3Sy+FHxI bHtxAqmHWPsJHALTg+ox+2slZNr/VpjgS3g920Uradkc4MgLOf6yCvvKje26Zqj3D1lc IImZzEA61dARlDxz8DpMRxm8loaEZL74E91jU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=JTebxj/iGjVGYbTC82YA/3QrUQ9DhxDs6o3waDc8CAEj7aC3GeOFN9aSV1kXp5kvVX 2sAH6ut5so95kPvEujMFFWJMddQqHHLVfdkFNsJCg4KwVgcwAORZgCQR9nikf5GyXsxg QY1Ff1ySz9Nibb//UF+QzPsN0x+cRJOk8WEJY=
Received: by 10.216.255.201 with SMTP id j51mr165779wes.94.1301562635616; Thu, 31 Mar 2011 02:10:35 -0700 (PDT)
Received: from [130.129.22.150] (dhcp-1696.meeting.ietf.org [130.129.22.150]) by mx.google.com with ESMTPS id d59sm107386wed.21.2011.03.31.02.10.34 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 02:10:34 -0700 (PDT)
Message-ID: <4D944505.3060407@gmail.com>
Date: Thu, 31 Mar 2011 22:10:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Roland Bless <roland.bless@kit.edu>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu>
In-Reply-To: <4D944365.4020809@kit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, =?UTF-8?B?UmFkZWsgV3LDs2JlbA==?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:09:11 -0000

I rather like the thought that each BMW will need its own BGP4
advertisement. Boeing tried that for a while with airplanes, and
it didn't work out too well.

    Brian


On 2011-03-31 22:03, Roland Bless wrote:
> Hi Radek,
>=20
> On 30.03.2011 17:31, Radek Wr=C3=B3bel wrote:
>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>> standard for vehicles
>> (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 can
>> diagnose (quasi online) 849 failures. One of most important advantage =
of
>> EOBDv2 (but not only it) will be constant, real time communication wit=
h
>> service. The best way of them will be indyvidual number for every car
>> vehicles in the world. This number ought to cooporate with global
>> networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
>> (17 characters which indicates on a country of production  and mark of=

>> the car: digits and letters A-X). Maybe there is time when someone mus=
t
>> think about conversion VIN to IPv6 (like it's in local IPv4)? I've a f=
ew
>> ideas about it and of course I can share them if you will be interstin=
g in.
>=20
> There is already related work for this.
> You should be aware of a US Patent of 2005 "Method for Setting an
> Internet Protocol Address using a vehicle identification number".
> US 2005/0273505 A1, first hit
> http://www.google.com/patents?q=3DVIN+IPv6&btnG=3DSearch+Patents
> (no comment on its usefulness here...)
> BMW has also recently filed a patent application with a VIN7 to IPv6
> address mapping.
> It's not totally clear to me what _problem_ you want to solve.
> Depending on that several options exist.
> However, I share the concerns that Scott Brim already expressed in his
> mail.
>=20
> Regards,
>  Roland
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From scott.brim@gmail.com  Thu Mar 31 02:10:56 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFFD428C186 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qlNKZvtmiYg for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:10:56 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 90EF53A6B00 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:10:55 -0700 (PDT)
Received: by iye19 with SMTP id 19so2508378iye.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:12:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=5D0d/MSllTBo5AhOt0B+fSvXtGWHMT3KtkGw96DznXo=; b=wELiNB/Wf+Eql8ha24uHTeKV3D77GSmRn4x+1blIGiaCSYXCBUaX0dqQmNpRqjUvgM j4ZR+8g9zl8T43tde8CnhEJGg95wACCXK03hahsejaUEuPzB5HUtsZfP/qfBGCtWQqlr 93G7qOznkT8Ygrzoot00lzERO0La/E855Gl8Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=f//a+Qp8Px5W/7P8NUixoooOGOF4dRH51XendMaiwkpae44i8ypke9evcMSUrzFcev b0X44BKiLXsX0D9cBgN3c4492MPAnM9rg0rN9mg7S7lYFaBoqWb0c56q0IbdJ3MdjOq0 v01ZP24im0oNQjmHHDQOs12W2K1rMOlKu9Fow=
Received: by 10.42.131.200 with SMTP id a8mr2716004ict.415.1301562755014; Thu, 31 Mar 2011 02:12:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.225.133 with HTTP; Thu, 31 Mar 2011 02:12:14 -0700 (PDT)
In-Reply-To: <C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 Mar 2011 11:12:14 +0200
Message-ID: <AANLkTimV9HG5rb0p3rjb7+dguq+CnxB452tQMn-YnMkQ@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
To: George Michaelson <ggm+ietf@apnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:10:56 -0000

On Thu, Mar 31, 2011 at 10:45, George Michaelson <ggm+ietf@apnic.net> wrote=
:
> There is a general model here which will re-occur many many times.
>
> manufacturers have context-specific serial numbers which behave in contex=
t like EUI164.
>
> It is reasonable (from their perspective) to ask if there is an address m=
anagement function which can suit their context, to exploit IPv6. Perhaps a=
 private overlay network for IPSEC trusted remote upload and download. re-b=
low your SONY TV on any Internet via a trust path homed inside the manufact=
urer. 'ET call home' models of device management.

An overlay sure.  One could use IPv6 addresses the way back-to-my-Mac
does.  But I would like it to be clear that

  Internet location

and

  Endpoint identification for use by applications

are totally different functions and in the long run everything is
easier if they are kept separate.  It's taken us 20 years to get to
the point where we might be able to separate them.  Let's help others
not go through the same learning experience.

From ggm+ietf@apnic.net  Thu Mar 31 02:14:28 2011
Return-Path: <ggm+ietf@apnic.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4E9728C107 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.949
X-Spam-Level: 
X-Spam-Status: No, score=-102.949 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3vW-cbbL38J for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:14:27 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by core3.amsl.com (Postfix) with ESMTP id F1E463A699C for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:14:26 -0700 (PDT)
Received: from dhcp-54ae.meeting.ietf.org (dhcp-54ae.meeting.ietf.org [130.129.84.174]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 00139B681F; Thu, 31 Mar 2011 19:16:03 +1000 (EST)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: George Michaelson <ggm+ietf@apnic.net>
In-Reply-To: <AANLkTimV9HG5rb0p3rjb7+dguq+CnxB452tQMn-YnMkQ@mail.gmail.com>
Date: Thu, 31 Mar 2011 11:16:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net> <AANLkTimV9HG5rb0p3rjb7+dguq+CnxB452tQMn-YnMkQ@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:14:28 -0000

On 31/03/2011, at 11:12 AM, Scott Brim wrote:

> On Thu, Mar 31, 2011 at 10:45, George Michaelson <ggm+ietf@apnic.net> =
wrote:
>> There is a general model here which will re-occur many many times.
>>=20
>> manufacturers have context-specific serial numbers which behave in =
context like EUI164.
>>=20
>> It is reasonable (from their perspective) to ask if there is an =
address management function which can suit their context, to exploit =
IPv6. Perhaps a private overlay network for IPSEC trusted remote upload =
and download. re-blow your SONY TV on any Internet via a trust path =
homed inside the manufacturer. 'ET call home' models of device =
management.
>=20
> An overlay sure.  One could use IPv6 addresses the way back-to-my-Mac
> does.  But I would like it to be clear that
>=20
>  Internet location
>=20
> and
>=20
>  Endpoint identification for use by applications
>=20
> are totally different functions and in the long run everything is
> easier if they are kept separate.

I *think* I'd do a 'no disagree +1' on that, but maybe thats another =
conversation.

>  It's taken us 20 years to get to
> the point where we might be able to separate them.  Let's help others
> not go through the same learning experience.

Like I said, the conversation is going to happen, and we have to face =
their expectations. I think its being done individually, industrial =
sector by sector. My first introduction was the smart whitegoods sector, =
washing machines and the like. I had no exposure to the car segment but =
its clear high-value goods attract 'smart' solutions labels like flies =
to honey.

I don't think "go away" is the right answer. I think "your model has =
flaws" is closer.

The key message is that if they apply for patents in it (BMW) they =
clearly see dollar-signs and its very hard to trump money.


-G=

From bob.hinden@gmail.com  Thu Mar 31 02:31:26 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 92F1328C204 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.57
X-Spam-Level: 
X-Spam-Status: No, score=-104.57 tagged_above=-999 required=5 tests=[AWL=1.029, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8H2O8pMfgMqI for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:31:16 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 5A0DD28C1FA for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:30:34 -0700 (PDT)
Received: by pzk30 with SMTP id 30so465585pzk.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=5MzS/GPV8PqFpC765TXUUtJLHXGgOqzZkYUnljESQyc=; b=LgU/w24dSj7nkb0RycBTK5CvGaU2vG/EPXEcKssrCVlYFDykcwO8nXvHt0iNDd8tlW YSlBtfeHBA9naMWnjxXoTSvxZWI44Vp5nN7cs/N3fYL1CvXjuWTaVpUxfAxVToU1ve+x Prk1B3dmrn9AjrGald7LL7ALKPofWK6XssU5k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=ULKplD0IrL2sk7xSmXV1jJXHSgu2+lGSLKzyeo2hE0BI+XrbQDKa29RveKt+DEpq+i yXfL889+JbQzLgWFrQoX0X9VUll5Rj9gly+lQQjAFoTsfAjxB3jr2xMrBhipb8K1ZCXs U+xT3Rg8iqGjQzJwieNY7cgoIHMYRyCl/6KzA=
Received: by 10.142.187.16 with SMTP id k16mr1796614wff.130.1301563933807; Thu, 31 Mar 2011 02:32:13 -0700 (PDT)
Received: from dhcp-6337.meeting.ietf.org (dhcp-6337.meeting.ietf.org [130.129.99.55]) by mx.google.com with ESMTPS id w32sm1268453wfh.19.2011.03.31.02.32.11 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 02:32:13 -0700 (PDT)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4D944505.3060407@gmail.com>
Date: Thu, 31 Mar 2011 11:32:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, =?iso-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:31:26 -0000

Brian,

On Mar 31, 2011, at 11:10 AM, Brian E Carpenter wrote:

> I rather like the thought that each BMW will need its own BGP4
> advertisement. Boeing tried that for a while with airplanes, and
> it didn't work out too well.

BGP is overkill :-)  I thought the problem with the Boeing service was =
largely financial, their BGP based technical solution did work.  At =
least the number of commercial airplanes isn't too large a number.

They could use a fixed car address and use mobile IPv6 with a provider =
based address. =20

Bob


>=20
>    Brian
>=20
>=20
> On 2011-03-31 22:03, Roland Bless wrote:
>> Hi Radek,
>>=20
>> On 30.03.2011 17:31, Radek Wr=F3bel wrote:
>>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>>> standard for vehicles
>>> (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 =
can
>>> diagnose (quasi online) 849 failures. One of most important =
advantage of
>>> EOBDv2 (but not only it) will be constant, real time communication =
with
>>> service. The best way of them will be indyvidual number for every =
car
>>> vehicles in the world. This number ought to cooporate with global
>>> networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
>>> (17 characters which indicates on a country of production  and mark =
of
>>> the car: digits and letters A-X). Maybe there is time when someone =
must
>>> think about conversion VIN to IPv6 (like it's in local IPv4)? I've a =
few
>>> ideas about it and of course I can share them if you will be =
intersting in.
>>=20
>> There is already related work for this.
>> You should be aware of a US Patent of 2005 "Method for Setting an
>> Internet Protocol Address using a vehicle identification number".
>> US 2005/0273505 A1, first hit
>> http://www.google.com/patents?q=3DVIN+IPv6&btnG=3DSearch+Patents
>> (no comment on its usefulness here...)
>> BMW has also recently filed a patent application with a VIN7 to IPv6
>> address mapping.
>> It's not totally clear to me what _problem_ you want to solve.
>> Depending on that several options exist.
>> However, I share the concerns that Scott Brim already expressed in =
his
>> mail.
>>=20
>> Regards,
>> Roland
>> --------------------------------------------------------------------
>> 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 scott.brim@gmail.com  Thu Mar 31 02:32:41 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AEAB28C1FE for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Se73LNo2Q8xN for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:32:35 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 8EFD828C1B1 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:32:17 -0700 (PDT)
Received: by iwn39 with SMTP id 39so2529271iwn.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:33:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=JKKHeqwFPgBMqRqwvg/la9Jcg7uIUhuUIMwHT1aFoBU=; b=PlPBmEIRR0/vV7A47zvzMozkPE6WXcIdj6hzksrERFNtEeSx6WgSuX6XxvoaIcRcE9 kGHv1f91AYQlRg7+6+MAMVIt4PuBamgsGnBBzthkROYm/32F8WfRJJfWf5lscAcP5k4v qZ0hWM0RbGKGUI6OhxqvvCAQIgjXrK1+jCIoM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=bd5Yqm7+burE6Do+JrHWYU2oY8V4EkB5usJ4299yHxlftVb+GBpt5+Ryb2Su9LdxJg 3HOSXMOlTdMs979kDEFlUClUItD7wDAOrWIJ+JkSuP4oIFcjBe7GA+mfuWCI/XFJl7m5 ANceww3Ir4XRfrwPITsCiKwvQ1MJMUbUo+AtY=
Received: by 10.42.170.8 with SMTP id d8mr2762933icz.281.1301564037053; Thu, 31 Mar 2011 02:33:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.225.133 with HTTP; Thu, 31 Mar 2011 02:33:37 -0700 (PDT)
In-Reply-To: <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net> <AANLkTimV9HG5rb0p3rjb7+dguq+CnxB452tQMn-YnMkQ@mail.gmail.com> <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 Mar 2011 11:33:37 +0200
Message-ID: <AANLkTinWGKoB5u7RhFOZXtOOqGDp93r=_VdB9GdSS72N@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
To: George Michaelson <ggm+ietf@apnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:32:41 -0000

On Thu, Mar 31, 2011 at 11:16, George Michaelson <ggm+ietf@apnic.net> wrote=
:
>> =A0Internet location
>>
>> and
>>
>> =A0Endpoint identification for use by applications
>>
>> are totally different functions and in the long run everything is
>> easier if they are kept separate.
>
> I *think* I'd do a 'no disagree +1' on that, but maybe thats another conv=
ersation.
>
>> =A0It's taken us 20 years to get to
>> the point where we might be able to separate them. =A0Let's help others
>> not go through the same learning experience.
>
> Like I said, the conversation is going to happen, and we have to face the=
ir expectations. I think its being done individually, industrial sector by =
sector. My first introduction was the smart whitegoods sector, washing mach=
ines and the like. I had no exposure to the car segment but its clear high-=
value goods attract 'smart' solutions labels like flies to honey.
>
> I don't think "go away" is the right answer. I think "your model has flaw=
s" is closer.

Someone (IAB? ISOC?) needs to publish something to the world about
separation of functions, and the perils of mixing locators and
identifiers.  We can help write it.

> The key message is that if they apply for patents in it (BMW) they clearl=
y see dollar-signs and its very hard to trump money.

Hadn't thought of that.  Hm.

Scott

From roland.bless@kit.edu  Thu Mar 31 02:37:27 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E64E3A6AFA for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.272
X-Spam-Level: 
X-Spam-Status: No, score=-6.272 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5u5j-nXL17G for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:37:26 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 0376D3A6949 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:37:23 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5ELB-0000qq-79; Thu, 31 Mar 2011 11:39:02 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 829102C6; Thu, 31 Mar 2011 11:41:51 +0200 (CEST)
Message-ID: <4D944BB0.5080900@kit.edu>
Date: Thu, 31 Mar 2011 11:38:56 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr>
In-Reply-To: <4D94446C.40008@inria.fr>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301564342.802590000
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:37:27 -0000

Hi Thierry,

On 31.03.2011 11:07, Thierry Ernst wrote:
> I fail to see why a VIN would be mapped to an IPv6 address as much as I
> fail to see why a passport number would be mapped to an IPv6 number. As

There may be scenarios where it may be useful to uniquely address
a particular car, e.g., for (remote) diagnosis, remote unlocking
services etc. However, doing this by statically mapping the VIN to an
IPv6 address (either into the IID part or the network prefix part)
is for several reasons not a great idea.

> Such an idea is going against location privacy. To address the location

Yep.

Regards,
 Roland

From thierry.ernst@inria.fr  Thu Mar 31 02:38:54 2011
Return-Path: <thierry.ernst@inria.fr>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DBB7D28C0FA for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.749
X-Spam-Level: 
X-Spam-Status: No, score=-11.749 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHpLPXqnIE0a for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 02:38:52 -0700 (PDT)
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by core3.amsl.com (Postfix) with ESMTP id C14E428C203 for <ipv6@ietf.org>; Thu, 31 Mar 2011 02:38:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.63,274,1299452400";  d="vcf'?scan'208";a="104116796"
Received: from dhcp-rocq-243.inria.fr ([128.93.62.243]) by mail1-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-CAMELLIA256-SHA; 31 Mar 2011 11:40:01 +0200
Message-ID: <4D944BF1.205@inria.fr>
Date: Thu, 31 Mar 2011 11:40:01 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
Organization: INRIA
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
In-Reply-To: <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
Content-Type: multipart/mixed; boundary="------------050308080503070507090303"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 09:38:55 -0000

This is a multi-part message in MIME format.
--------------050308080503070507090303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


>> I rather like the thought that each BMW will need its own BGP4
>> advertisement. Boeing tried that for a while with airplanes, and
>> it didn't work out too well.
> BGP is overkill :-)  I thought the problem with the Boeing service was largely financial, their BGP based technical solution did work.  At least the number of commercial airplanes isn't too large a number.
>
> They could use a fixed car address and use mobile IPv6 with a provider based address.
This is what the intend to do:

  Slides presented at the ITU Fully Networked Car Workshop may be of 
interest to you.

  Convergence of car connectivity

Bernadette Villeforceix (Orange) and St閜hane Petti (Orange)

http://www.itu.int/dms_pub/itu-t/oth/06/41/T06410000700002PDFE.pdf

Regards,
Thierry Ernst.
> Bob
>
>
>>     Brian
>>
>>
>> On 2011-03-31 22:03, Roland Bless wrote:
>>> Hi Radek,
>>>
>>> On 30.03.2011 17:31, Radek Wr骲el wrote:
>>>> Vehicle / mechanic engineers are working on a new On Board Diagnosis
>>>> standard for vehicles
>>>> (http://en.wikipedia.org/wiki/On-board_diagnostics). Today EOBDv1 can
>>>> diagnose (quasi online) 849 failures. One of most important advantage of
>>>> EOBDv2 (but not only it) will be constant, real time communication with
>>>> service. The best way of them will be indyvidual number for every car
>>>> vehicles in the world. This number ought to cooporate with global
>>>> networking - TCP/IP (IPv6). All cars have indyvidual number - VIN
>>>> (17 characters which indicates on a country of production  and mark of
>>>> the car: digits and letters A-X). Maybe there is time when someone must
>>>> think about conversion VIN to IPv6 (like it's in local IPv4)? I've a few
>>>> ideas about it and of course I can share them if you will be intersting in.
>>> There is already related work for this.
>>> You should be aware of a US Patent of 2005 "Method for Setting an
>>> Internet Protocol Address using a vehicle identification number".
>>> US 2005/0273505 A1, first hit
>>> http://www.google.com/patents?q=VIN+IPv6&btnG=Search+Patents
>>> (no comment on its usefulness here...)
>>> BMW has also recently filed a patent application with a VIN7 to IPv6
>>> address mapping.
>>> It's not totally clear to me what _problem_ you want to solve.
>>> Depending on that several options exist.
>>> However, I share the concerns that Scott Brim already expressed in his
>>> mail.
>>>
>>> Regards,
>>> Roland
>>> --------------------------------------------------------------------
>>> 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
> --------------------------------------------------------------------


--------------050308080503070507090303
Content-Type: text/x-vcard; charset=utf-8;
 name="thierry_ernst.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="thierry_ernst.vcf"

begin:vcard
fn:Thierry  Ernst
n:Ernst;Thierry 
org:INRIA - Project Team IMARA - LaRA JRU
tel;work:+33 1 3963 59 30
tel;fax:+33 1 39 63 54 91
tel;cell:+33 6 76 56 25 96
url:http://www.lara.prd.fr
version:2.1
end:vcard


--------------050308080503070507090303--

From roland.bless@kit.edu  Thu Mar 31 03:01:53 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34DA83A6919 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.268
X-Spam-Level: 
X-Spam-Status: No, score=-6.268 tagged_above=-999 required=5 tests=[AWL=-0.019, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3GlXuGcc1GOa for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:01:52 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 5F7643A6A63 for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:01:52 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5Eiq-0005Oq-5H; Thu, 31 Mar 2011 12:03:30 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 7D07E2C6; Thu, 31 Mar 2011 12:06:18 +0200 (CEST)
Message-ID: <4D94516B.6010805@kit.edu>
Date: Thu, 31 Mar 2011 12:03:23 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: George Michaelson <ggm+ietf@apnic.net>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>	<C53621C2-41A0-4818-8E01-377A5468DD8D@apnic.net>	<AANLkTimV9HG5rb0p3rjb7+dguq+CnxB452tQMn-YnMkQ@mail.gmail.com> <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
In-Reply-To: <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301565810.889982000
Cc: ipv6@ietf.org, Scott Brim <scott.brim@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 10:01:53 -0000

Hi George,

On 31.03.2011 11:16, George Michaelson wrote:
> I don't think "go away" is the right answer. I think "your model has
> flaws" is closer.

Yep. Given the huge IPv6 address space, some manufacturers are tempted
to use the IPv6 address as identifier.

> The key message is that if they apply for patents in it (BMW) they
> clearly see dollar-signs and its very hard to trump money.

I'm not speaking for BMW nor defending them,
but maybe it's not the $$$ directly rather than the
usual patent competition between vendors:
they probably wanted to have filed something before any
other vendor, so that they can have a royalty free
negotiation later on...

Regards,
 Roland

From alexandru.petrescu@gmail.com  Thu Mar 31 03:07:17 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B74F63A69AC for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.449
X-Spam-Level: 
X-Spam-Status: No, score=-4.449 tagged_above=-999 required=5 tests=[AWL=0.850,  BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9iQAZGnud8u for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:07:16 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 5A9D43A697A for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:07:16 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1822787wwa.13 for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nvP6g5jZiFHUCuCxk/2rOjK61CX3tdieEN3Fwhvfgwo=; b=sfIuvVd0bLvlWtUuZVuiu1vLKiM699t2LehRGPVAWB7WR+STIZItRbR7XAzMWd6O3V iIg95y0j/QT+YjaLT9c0Rzt/d04htMakLB/elc/UkeEXKNCqRCTH5JFlvVxBEynvkSRa KiPycUlMDjTRoKRExztieDNohA5zThW2CXvEQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=O+iVmsAkNknJHy9Mdkkd9Wp+NV1oKnAqp2W0og/hsHUC9fXPGTjSR1VyBpJ2VXYn/B 5dG+DEiKvzABSCaGkfIoO6iNU1xgGR53z4FY7jU+ZuF1Eq4J4kze8fLb2p4YkWS+/0Df A8b36MtO5wv/g5ZHZw9nb3GXfEbZAATFEbGnA=
Received: by 10.216.205.17 with SMTP id i17mr1877479weo.71.1301566135277; Thu, 31 Mar 2011 03:08:55 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id e13sm552215wbi.40.2011.03.31.03.08.53 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 03:08:54 -0700 (PDT)
Message-ID: <4D9452B3.2010504@gmail.com>
Date: Thu, 31 Mar 2011 12:08:51 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
In-Reply-To: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 10:07:17 -0000

Le 30/03/2011 17:31, Radek Wr骲el a 閏rit :
> Dear 6man! My name is Radek Wrobel, I'm writing from Poland (I'm
> working in Wroclaw University of Technology, Division of Car
> Vehicles and Combustion Engines). With this idea I wrote to IANA and
> Leo Vegoda redirected me to you. Vehicle / mechanic engineers are
> working on a new On Board Diagnosis standard for vehicles
> (http://en.wikipedia.org/wiki/On-board_diagnostics).

Thanks for the pointer, I am discovering OBD.  We are also interested in
wireless usage of IP within the vehicle, with off-the-shelf links (i.e.
consumer electronics market wifi, bluetooth, ant) together with OBD if
needed.

> Today EOBDv1 can diagnose (quasi online) 849 failures. One of most
> important advantage of EOBDv2 (but not only it) will be constant,
> real time communication with service. The best way of them will be
> indyvidual number for every car vehicles in the world.

Excellent requirement to IP.

> This number ought to cooporate with global networking - TCP/IP
> (IPv6). All cars have indyvidual number - VIN (17 characters which
> indicates on a country of production and mark of the car: digits and
>  letters A-X). Maybe there is time when someone must think about
> conversion VIN to IPv6

Hmm... sounds as good idea.  But there may be several IP addresses
within a vehicle, one for the obu, one for map device, etc.

In case one would like to map VIN to an IPv6 address one would consider
first an Interface Identifier of the IPv6 address. (rightmost 64 bits).

Interface Identifier is about an Interface, and I am not sure VIN is
about an interface, or is it. (like Interface is the Ethernet interface
of this pc).

> (like it's in local IPv4)?

Hmm..?  What do you mean?  Has VIN been mapped to some reserved IPv4
address?

> I've a few ideas about it and of course I can share them if you will
> be intersting in.

Well definitely I am interested to hear what the idea is about and what
the mapping could look like.

I am interested on everything about how to connect vehicles (cars,
buses, trains) to the Internet with IPv6.

FYI, the MEXT working group has discussed several times about vehicles
ans Internet, with protocol Mobile IPv6 and various extensions.  A
number of people are actively involved.  A specific "vehicular reqs"
draft exists expired in MEXT, as well as some solution individual drafts
(non wg item) for v2v communications.

Alex

> Also we cooperate with VW and Toyota. I think they will be
> interesting about it too. Best regards, Radek Wrobel. +48660406004
>
>
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From roland.bless@kit.edu  Thu Mar 31 03:25:15 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12F7F3A6B1E for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.267
X-Spam-Level: 
X-Spam-Status: No, score=-7.267 tagged_above=-999 required=5 tests=[AWL=0.982,  BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMqKw9Tt+KGU for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:25:14 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id C538B3A6AF3 for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:25:13 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5F5T-0001HO-34; Thu, 31 Mar 2011 12:26:52 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 81C042C6; Thu, 31 Mar 2011 12:29:41 +0200 (CEST)
Message-ID: <4D9456E6.90608@kit.edu>
Date: Thu, 31 Mar 2011 12:26:46 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D9452B3.2010504@gmail.com>
In-Reply-To: <4D9452B3.2010504@gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301567213.037497000
Cc: ipv6@ietf.org, =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 10:25:15 -0000

Hi Alexandru,

On 31.03.2011 12:08, Alexandru Petrescu wrote:
> Thanks for the pointer, I am discovering OBD.  We are also interested in
> wireless usage of IP within the vehicle, with off-the-shelf links (i.e.
> consumer electronics market wifi, bluetooth, ant) together with OBD if
> needed.

See below.

>> Today EOBDv1 can diagnose (quasi online) 849 failures. One of most
>> important advantage of EOBDv2 (but not only it) will be constant,
>> real time communication with service. The best way of them will be
>> indyvidual number for every car vehicles in the world.
> 
> Excellent requirement to IP.

Maybe to some mapping system, but not directly to IPv6
(ID/Loc split).

>> This number ought to cooporate with global networking - TCP/IP
>> (IPv6). All cars have indyvidual number - VIN (17 characters which
>> indicates on a country of production and mark of the car: digits and
>>  letters A-X). Maybe there is time when someone must think about
>> conversion VIN to IPv6
> 
> Hmm... sounds as good idea.  But there may be several IP addresses
> within a vehicle, one for the obu, one for map device, etc.

> In case one would like to map VIN to an IPv6 address one would consider
> first an Interface Identifier of the IPv6 address. (rightmost 64 bits).
> Interface Identifier is about an Interface, and I am not sure VIN is
> about an interface, or is it. (like Interface is the Ethernet interface
> of this pc).

Yes, but from a security point of view, it would be a nightmare
if some hacker could directly send IP packets to the ECU controlling
your airbag or other safety relevant ECUs etc. So a strong
security architecture is a MUST. I'm not sure that there is a need
to _directly_ address any internal car devices. A security gateway
as policy enforcement point seems to be required at least.

Regards,
 Roland

From ietf-ipv6@daork.net  Thu Mar 31 03:41:59 2011
Return-Path: <ietf-ipv6@daork.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EDE23A6B2A for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGhSnPbekN1l for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 03:41:58 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id AD9213A6B0C for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:41:58 -0700 (PDT)
Received: by pzk30 with SMTP id 30so480900pzk.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 03:43:38 -0700 (PDT)
Received: by 10.142.144.7 with SMTP id r7mr1883603wfd.412.1301568218288; Thu, 31 Mar 2011 03:43:38 -0700 (PDT)
Received: from [192.168.0.4] ([121.98.191.176]) by mx.google.com with ESMTPS id n4sm1353379wfl.2.2011.03.31.03.43.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 03:43:36 -0700 (PDT)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Nathan Ward <ietf-ipv6@daork.net>
In-Reply-To: <4D944505.3060407@gmail.com>
Date: Thu, 31 Mar 2011 23:43:31 +1300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7EF89C89-675C-446E-9B00-AE06820988B6@daork.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, =?iso-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 10:41:59 -0000

On 31/03/2011, at 10:10 PM, Brian E Carpenter wrote:

> I rather like the thought that each BMW will need its own BGP4
> advertisement. Boeing tried that for a while with airplanes, and
> it didn't work out too well.

My laptop has an address based on the physical network interface's MAC =
address, which is used over a tunnel to Apple for Back to my Mac. It =
doesn't do BGP4, obviously, and I assume it works well.
utun0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
        inet6 fe80::217:f2ff:fed5:a13%utun0 prefixlen 64 scopeid 0x8=20
        inet6 fd00:6587:52d7:20:217:f2ff:fed5:a13 prefixlen 64=20

Perhaps something a bit more relevant to IETF is generating a ULA prefix =
from a VIN?=

From scott.brim@gmail.com  Thu Mar 31 04:14:45 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2693728C115 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 04:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6k2I0ulWDyb for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 04:14:28 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 806A93A6B35 for <ipv6@ietf.org>; Thu, 31 Mar 2011 04:14:28 -0700 (PDT)
Received: by iye19 with SMTP id 19so2641562iye.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 04:16:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=uEs2kioUu+HrGOjzJoRGdmFBOUoVed4gvHHtB1E8rhI=; b=lJcYybuLExH0GFenWz+7D/MS9SWMYH0xyfV5GcNQzx1TkvblOZl+qAfMYvjLIWk08+ Jmpf0UnPHgaKoOds1/2q/tWfq1KCxejr2hfrXWBiXJtyIsOblLxm78msDMyBcKigdrM3 rV5Baj1SbpzE5Fd0sRYF85YTERz6haU3PlZvw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=LPO/VYXMMNFp2GvLxz+ag2GKvT1YDHgOIbw2i0kEdZXNXUC7DuMUz6s/Iy0KbpOsld Z6DRviF1yrg1R5qYijQtA0ZYOEcSoLr+5LMv8mmdPymTFmX246OyaurxRGFc+vVuI8sj VzOFzMxfxojYIxQXgvn+UZl7on4UA9lKeLsbc=
Received: by 10.42.131.200 with SMTP id a8mr2891542ict.415.1301570168063; Thu, 31 Mar 2011 04:16:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.225.133 with HTTP; Thu, 31 Mar 2011 04:15:48 -0700 (PDT)
In-Reply-To: <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 Mar 2011 13:15:48 +0200
Message-ID: <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 11:14:45 -0000

On Thu, Mar 31, 2011 at 11:32, Bob Hinden <bob.hinden@gmail.com> wrote:
> They could use a fixed car address and use mobile IPv6 with a provider based address.

That would help.  A rendezvous point (e.g. home agent) always helps to
protect confidentiality. Plus a firewall to protect the
always-out-of-date vehicle software.   They can work out how to do
path optimization later.

From scott.brim@gmail.com  Thu Mar 31 04:17:08 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C55C93A6930 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 04:17:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lX5Q1AU60abl for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 04:17:08 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id F3B053A68B1 for <ipv6@ietf.org>; Thu, 31 Mar 2011 04:17:07 -0700 (PDT)
Received: by iye19 with SMTP id 19so2644232iye.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 04:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=jHXvsetiRYkrO8+cioRu4nPyeBGyj8gLTSmA9uedZF0=; b=p7adtZgTXB3gqsChgbFqFFtVOfVeBTFHfDirreYjplBSeDorGVbEFn9NxndDJO0IEq hllTC779ar15OIITOQqyF/jB9qy1fohf0V78xI1iJ4r3aov1EL0y55ABkXJbrlpLmR/w cy5dcTwdmchmS1q3y9TnvSe02/YQ4M1MuWhn0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=ImIjGD85+Ck3RBbqydcrtUPPzoFacZILGEL+Y+kkVuVS9OmeeAj/55sn5egZBcGEKZ 38SUqkdH6i+mDs5MbAuimsBpXBpedNNjB4LQ5kOk3x3JaHW/HF0v5nEL3pcCoBj6Nlz4 3LWHg5VhOoblHifkXDjbXcdPz7heJ0OkEQHJM=
Received: by 10.42.170.8 with SMTP id d8mr2910509icz.281.1301570327362; Thu, 31 Mar 2011 04:18:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.42.225.133 with HTTP; Thu, 31 Mar 2011 04:18:27 -0700 (PDT)
In-Reply-To: <7EF89C89-675C-446E-9B00-AE06820988B6@daork.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <7EF89C89-675C-446E-9B00-AE06820988B6@daork.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 31 Mar 2011 13:18:27 +0200
Message-ID: <AANLkTikAA1WfeKgc8_L0Z-JYFGAUuGzvXyUQPZmvyJvD@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
To: Nathan Ward <ietf-ipv6@daork.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 11:17:08 -0000

On Thu, Mar 31, 2011 at 12:43, Nathan Ward <ietf-ipv6@daork.net> wrote:
> My laptop has an address based on the physical network interface's MAC ad=
dress, which is used over a tunnel to Apple for Back to my Mac. It doesn't =
do BGP4, obviously, and I assume it works well.
> utun0: flags=3D8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
> =A0 =A0 =A0 =A0inet6 fe80::217:f2ff:fed5:a13%utun0 prefixlen 64 scopeid 0=
x8
> =A0 =A0 =A0 =A0inet6 fd00:6587:52d7:20:217:f2ff:fed5:a13 prefixlen 64
>
> Perhaps something a bit more relevant to IETF is generating a ULA prefix =
from a VIN?

If these addresses will never be used for anything except diagnostics
and internal communications, then okay, but this looks like a classic
case of a net that is going to start out with just local use, and soon
move to needing global addresses.  Hey, I know, NAT.

From tjc@ecs.soton.ac.uk  Thu Mar 31 04:52:48 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0F0E3A6B48; Thu, 31 Mar 2011 04:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.359
X-Spam-Level: 
X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JgWK35ePOEAo; Thu, 31 Mar 2011 04:52:47 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by core3.amsl.com (Postfix) with ESMTP id E870B28C145; Thu, 31 Mar 2011 04:52:46 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p2VBsJqp025619; Thu, 31 Mar 2011 12:54:19 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk p2VBsJqp025619
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1301572460; bh=OuPD3oyBZURGsWesJQHZcmAmIp8=; h=From:Subject:Date:Cc:To:Mime-Version:References; b=IpWDRC1KOOoAwZjI3qVU6ZgxBIAJQYG2mDuhsNWBZbpvTWZ7lXzWYOS0IgxtlQp2c Ydo4jVTG76UNyA38JY6vVh42WIh1cv0xvdanoNqJScc8OjBrrMTRqxneaOGvBpNBR1 e9MD5hCIxA5qarWA+UaYQZcLne49B2p/7EOdxy4A=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id n2UCsJ0035620040Zj ret-id none; Thu, 31 Mar 2011 12:54:19 +0100
Received: from dhcp-13bc.meeting.ietf.org (dhcp-13bc.meeting.ietf.org [130.129.19.188]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id p2VBr0hL006649 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 Mar 2011 12:53:01 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF renum BoF today at 3.20pm
Date: Thu, 31 Mar 2011 13:53:00 +0200
Message-ID: <EMEW3|948c082ab016e1be575b28030e5b9145n2UCsJ03tjc|ecs.soton.ac.uk|28B42591-35B7-455E-8C6A-05ABF3D1000F@ecs.soton.ac.uk>
To: IPv6 Ops WG <v6ops@ietf.org>, 6man <ipv6@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=n2UCsJ003562004000; tid=n2UCsJ0035620040Zj; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
References: <28B42591-35B7-455E-8C6A-05ABF3D1000F@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: p2VBsJqp025619
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 11:52:48 -0000

Hi,

Just a heads-up or reminder that there is a Site Renumbering (renum) BoF =
being held today (Thursday) at 15:20 in Congress Hall II.

The description and agenda are listed here:
http://www.ietf.org/proceedings/80/agenda/renum.txt

Remote participation information (audio, Jabber, etc) is listed here:
http://www.ietf.org/meeting/80/remote-participation.html

Tim


From behcetsarikaya@yahoo.com  Thu Mar 31 05:27:04 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B8F428C108 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.088
X-Spam-Level: 
X-Spam-Status: No, score=-3.088 tagged_above=-999 required=5 tests=[AWL=1.511,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elbaVfPHhnuv for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:27:03 -0700 (PDT)
Received: from nm19.bullet.mail.sp2.yahoo.com (nm19.bullet.mail.sp2.yahoo.com [98.139.91.89]) by core3.amsl.com (Postfix) with SMTP id 5167D3A6AFA for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:27:03 -0700 (PDT)
Received: from [98.139.91.64] by nm19.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:43 -0000
Received: from [98.139.91.21] by tm4.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:43 -0000
Received: from [127.0.0.1] by omp1021.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 12:28:42 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 993316.38435.bm@omp1021.mail.sp2.yahoo.com
Received: (qmail 93817 invoked by uid 60001); 31 Mar 2011 12:28:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1301574522; bh=/qef+yeFEjw0iwPbHa+F/nuiePsXHrCwOAVLFwPls4A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ZAVqfz56TaWiLQsgwpsXqbqB7kugt9FLDn+gC++10FAi2+VtkjkOoI5gR9n2lmsrnAtXCxbGvRYYJe3G13n8dGca29XkG7QcvW1l4DbzNT6U1+11rl8cI7f3Gge4crZeZ/hyi3VqTl464Jp4OdWEGAw2yaCWhfuZpoqF6SLaKZ0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=a+od5vZfstVo9x68Bf2fINF7BO2FN2jRHBQowf41PFzHLG6oykMwcuQfiKRD0cmajQmdstptxRCwIEEM+MsmKVrMywiVHmfc/CXXIRDvpyC6Whg5K9V8tmYpSnUtoEQvJsMFIDTlqG1vJaE1STW5VeOUcbsKf09cOmk9oqLk8LA=;
Message-ID: <575406.83799.qm@web111414.mail.gq1.yahoo.com>
X-YMail-OSG: 8A8Ufk8VM1k7q34dhaoDWffFxdwy3eeBbmzXTKFvcLXfvfe QAppw0e_mJPTyez4QhgJn6EvAAmr.slA.JgHH76bhxlbAVxC7t3.WrD1jtyM qfQiCm5tqWi7bdlrpa9tE0M7ce2MLBQC5euhVUBbsk_zlISPN9PtJU6VfLO6 aZP2xzRfciD3A_hjVkMYEIByks3UhWO5zwj4fmetqnV.i7pGgUhHesn_hklR ELfjUqVErX7pusFUFQ5bADnjHq0M8cEf8R3t92NYkNPuSqkhcNLRmiZOqQBZ RkeWhYn0qPJ6.cMtAdVPYEIYM1ooZxn6iHG5e08p81dWMxwIXDOdSZ_I3Eqx Y2h27b28v0tKMsTaE8LsO7Ga50zhwH378odYyC42Ll0WTSmjk9GbHfmKanMB hTNkgKjOoKL8-
Received: from [130.129.68.193] by web111414.mail.gq1.yahoo.com via HTTP; Thu, 31 Mar 2011 05:28:42 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.109.295617
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr>
Date: Thu, 31 Mar 2011 05:28:42 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Vehicle's VIN in IPv6.
To: Thierry Ernst <thierry.ernst@inria.fr>, ipv6@ietf.org
In-Reply-To: <4D94446C.40008@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 12:27:04 -0000

I think the idea here is to use VIN as link layer id when assigning an =0Aa=
ddress/prefix to a host in the car. The host can provide such an id in DHCP=
 =0Arequest message.=0A=0ARegards,=0A=0ABehcet=0A=0A> Dear all,=0A> =0A> I =
fail to see why a VIN would be mapped to an IPv6 address as  much as I fail=
 =0A>to see why a passport number would be mapped to an IPv6 number.  As sa=
id by =0A>Scott, the purpose of the IP address is to forward packets to the=
  destination.=0A> =0A> Such an idea is going against location privacy. To =
address  the location =0A>privacy issue related to the ID of the vehicle us=
ed at the  networking layer, =0A>the Car-to-Car Communication Consortium pr=
opose to use  pseudonyms; when it goes =0A>to IPv6 communications (all comm=
unications are not  IP-based) this pseudonym is =0A>used to configure an IP=
v6 address, i.e. a transient  address (you can check the =0A>work of the Se=
VeCom project). In the meantime, the  vehicle also has a permanent =0A>addr=
ess (indeed, prefix) as which the vehicle is  reachable (using NEMO). Up to=
 =0A>now, there is no one in any of the standardisation  or consortium I kn=
ow (ETSI =0A>TC ITS, ISO TC204, ISO TC22, CEN TC278, Car2Car  Communication=
 Consortium) who =0A>is thinking about mapping a vehicle ID to the IPv6  ad=
dress.=0A> =0A> So, I'm afraid this idea is going  nowhere.=0A> =0A> Regard=
s,=0A> Thierry Ernst.=0A> =0A> On 31/03/11 10:40, Scott Brim  wrote:=0A> > =
Hello Radek.=0A> > =0A> > I have privacy concerns, because  the VIN is perm=
anent for the vehicle.=0A> >   I suspect there is a good  chance that the v=
ehicle's IP address will=0A> > not be used just for  diagnostics, but also =
for general purpose=0A> > connections to the Internet  (for example fetchin=
g a movie for the=0A> > children).  If an IP address  is based on VIN, then=
 it will never=0A> > change, ever.  It will be  possible for observers to b=
uild up=0A> > information about what the vehicle's  users like to connect t=
o.=0A> > =0A> > Also, if you are a diagnostic center  and you receive packe=
ts from an=0A> > IP address claiming to have a particular  VIN number, how =
do you=0A> > authenticate it?  How do you know that is  really the vehicle =
it claims=0A> > to be?  You will need application  layer authentication in =
any case.=0A> > =0A> > I believe it would be much  better to decouple "vehi=
cle identification"=0A> > from "IP layer location"  (the IP address).  Thes=
e tokens have=0A> > different purposes.  The  vehicle identification is for=
 use with=0A> > database applications and  diagnostic applications, while t=
he IP=0A> > address is for IP forwarding to  know how to reach the vehicle.=
  You=0A> > could possibly allow the  vehicle to connect to the network and=
 get any=0A> > IP address -- any address  at all -- and then connect to the=
 diagnostic=0A> > center and tell you its VIN  and authenticate, all in a h=
igher layer=0A> > protocol.=0A> > =0A> >  2011/3/30 Radek Wr=F3bel<radoslaw=
.wrobel@pwr.wroc.pl>:=0A> >>  Dear 6man!=0A> >> My name is Radek Wrobel, I'=
m writing from Poland (I'm  working in Wroclaw=0A> >> University of Technol=
ogy, Division of Car  Vehicles and Combustion=0A> >> Engines). With this id=
ea I wrote to IANA and  Leo Vegoda redirected me to=0A> >> you.=0A> >> Vehi=
cle / mechanic  engineers are working on a new On Board Diagnosis=0A> >> st=
andard for  vehicles (http://en.wikipedia.org/wiki/On-board_diagnostics).=
=0A> >> Today  EOBDv1 can diagnose (quasi online) 849 failures. One of most=
  =0A>important=0A> >> advantage of EOBDv2 (but not only it) will be consta=
nt,  real time=0A> >> communication with service. The best way of them will=
 be  indyvidual number=0A> >> for every car vehicles in the world. This num=
ber  ought to cooporate with=0A> >> global networking - TCP/IP (IPv6). All =
cars  have indyvidual number - VIN=0A> >> (17 characters which indicates on=
 a  country of production  and mark of the=0A> >> car: digits and letters  =
A-X). Maybe there is time when someone must think=0A> >> about conversion  =
VIN to IPv6 (like it's in local IPv4)? I've a few ideas=0A> >> about it and=
  of course I can share them if you will be intersting in.=0A> >> Also we  =
cooperate with VW and Toyota. I think they will be interesting =0A>about=0A=
> >>  it too.=0A> >> Best regards, Radek Wrobel.=0A> >>  +48660406004=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> >  ---------------------------------------------------=
-----------------=0A> >  IETF IPv6 working group mailing list=0A> > ipv6@ie=
tf.org=0A> > Administrative Requests: https://www.ietf.org/mailman/listinfo=
/ipv6=0A> >  --------------------------------------------------------------=
------=0A> =0A> 

From alexandru.petrescu@gmail.com  Thu Mar 31 05:51:15 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F6A33A6B3C for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.72
X-Spam-Level: 
X-Spam-Status: No, score=-4.72 tagged_above=-999 required=5 tests=[AWL=0.879,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9S6t61V9q+u for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:51:13 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 964E33A6B12 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:51:12 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1936531wwa.13 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:52:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NE9p0r8MKbIbg/QT5V9YOdfOXo7f5f2vFMInjTbcsZk=; b=jngYOpnXI1XTBZk4WiQQpLkuJV/HTKK5UORo1u+rkQ/IAsa6sjyFOWfkxEMqv25RF5 xDa+3c7GZSVfrBPP3SKLhS0R7hBt1eBTs3rly4qavq9oIq7vUMWbyWEJLAiWMTo907/Y IL32RqrqTC8EeTtOaNkLuLBgg0CBpuVsRISb8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=QzC5mJgpecfOY2ODSQObhkSQVqvEq2Q7+DN87Ske14mYofRU3+LL0/dH3Y4CAmZsZ6 GBbgYW/dNsONkjXWjACXlR48IT+F3alFZNjDOR9NVLTqt27BSiyiHPH/eb58KNHzJaxI CmMGMwHzdARKIcB67GOompTerAb5axPxgEkqU=
Received: by 10.216.143.74 with SMTP id k52mr2087295wej.8.1301575971676; Thu, 31 Mar 2011 05:52:51 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id ed10sm636372wbb.15.2011.03.31.05.52.49 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 05:52:50 -0700 (PDT)
Message-ID: <4D94791F.1010709@gmail.com>
Date: Thu, 31 Mar 2011 14:52:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>	<4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com>
In-Reply-To: <575406.83799.qm@web111414.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 12:51:15 -0000

hmm... sounds as there would be a VIN-specific link layer? (not ieee 
ethernet, not usb, not bluetooth)?  Which is that?

Alex


Le 31/03/2011 14:28, Behcet Sarikaya a 閏rit :
> I think the idea here is to use VIN as link layer id when assigning an
> address/prefix to a host in the car. The host can provide such an id in DHCP
> request message.
>
> Regards,
>
> Behcet
>
>> Dear all,
>>
>> I fail to see why a VIN would be mapped to an IPv6 address as  much as I fail
>> to see why a passport number would be mapped to an IPv6 number.  As said by
>> Scott, the purpose of the IP address is to forward packets to the  destination.
>>
>> Such an idea is going against location privacy. To address  the location
>> privacy issue related to the ID of the vehicle used at the  networking layer,
>> the Car-to-Car Communication Consortium propose to use  pseudonyms; when it goes
>> to IPv6 communications (all communications are not  IP-based) this pseudonym is
>> used to configure an IPv6 address, i.e. a transient  address (you can check the
>> work of the SeVeCom project). In the meantime, the  vehicle also has a permanent
>> address (indeed, prefix) as which the vehicle is  reachable (using NEMO). Up to
>> now, there is no one in any of the standardisation  or consortium I know (ETSI
>> TC ITS, ISO TC204, ISO TC22, CEN TC278, Car2Car  Communication Consortium) who
>> is thinking about mapping a vehicle ID to the IPv6  address.
>>
>> So, I'm afraid this idea is going  nowhere.
>>
>> Regards,
>> Thierry Ernst.
>>
>> On 31/03/11 10:40, Scott Brim  wrote:
>>> Hello Radek.
>>>
>>> I have privacy concerns, because  the VIN is permanent for the vehicle.
>>>    I suspect there is a good  chance that the vehicle's IP address will
>>> not be used just for  diagnostics, but also for general purpose
>>> connections to the Internet  (for example fetching a movie for the
>>> children).  If an IP address  is based on VIN, then it will never
>>> change, ever.  It will be  possible for observers to build up
>>> information about what the vehicle's  users like to connect to.
>>>
>>> Also, if you are a diagnostic center  and you receive packets from an
>>> IP address claiming to have a particular  VIN number, how do you
>>> authenticate it?  How do you know that is  really the vehicle it claims
>>> to be?  You will need application  layer authentication in any case.
>>>
>>> I believe it would be much  better to decouple "vehicle identification"
>>> from "IP layer location"  (the IP address).  These tokens have
>>> different purposes.  The  vehicle identification is for use with
>>> database applications and  diagnostic applications, while the IP
>>> address is for IP forwarding to  know how to reach the vehicle.  You
>>> could possibly allow the  vehicle to connect to the network and get any
>>> IP address -- any address  at all -- and then connect to the diagnostic
>>> center and tell you its VIN  and authenticate, all in a higher layer
>>> protocol.
>>>
>>>   2011/3/30 Radek Wr骲el<radoslaw.wrobel@pwr.wroc.pl>:
>>>>   Dear 6man!
>>>> My name is Radek Wrobel, I'm writing from Poland (I'm  working in Wroclaw
>>>> University of Technology, Division of Car  Vehicles and Combustion
>>>> Engines). With this idea I wrote to IANA and  Leo Vegoda redirected me to
>>>> you.
>>>> Vehicle / mechanic  engineers are working on a new On Board Diagnosis
>>>> standard for  vehicles (http://en.wikipedia.org/wiki/On-board_diagnostics).
>>>> Today  EOBDv1 can diagnose (quasi online) 849 failures. One of most
>> important
>>>> advantage of EOBDv2 (but not only it) will be constant,  real time
>>>> communication with service. The best way of them will be  indyvidual number
>>>> for every car vehicles in the world. This number  ought to cooporate with
>>>> global networking - TCP/IP (IPv6). All cars  have indyvidual number - VIN
>>>> (17 characters which indicates on a  country of production  and mark of the
>>>> car: digits and letters  A-X). Maybe there is time when someone must think
>>>> about conversion  VIN to IPv6 (like it's in local IPv4)? I've a few ideas
>>>> about it and  of course I can share them if you will be intersting in.
>>>> Also we  cooperate with VW and Toyota. I think they will be interesting
>> about
>>>>   it too.
>>>> Best regards, Radek Wrobel.
>>>>   +48660406004
>>>>
>>>>   --------------------------------------------------------------------
>>>>   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 brian@innovationslab.net  Thu Mar 31 05:58:00 2011
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A2953A6952 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gocKZWzhord9 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 05:57:59 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id ABDA33A6914 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:57:59 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 9A2FF8826A for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:59:39 -0700 (PDT)
Received: from clemson.jhuapl.edu (unknown [128.244.243.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C1524130002 for <ipv6@ietf.org>; Thu, 31 Mar 2011 05:59:38 -0700 (PDT)
Message-ID: <4D947AB9.8000502@innovationslab.net>
Date: Thu, 31 Mar 2011 08:59:37 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
In-Reply-To: <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 12:58:00 -0000

On 3/31/11 4:40 AM, Scott Brim wrote:
> Hello Radek.
> 
> I have privacy concerns, because the VIN is permanent for the vehicle.
>  I suspect there is a good chance that the vehicle's IP address will
> not be used just for diagnostics, but also for general purpose
> connections to the Internet (for example fetching a movie for the
> children).  If an IP address is based on VIN, then it will never
> change, ever.  It will be possible for observers to build up
> information about what the vehicle's users like to connect to.
> 
> Also, if you are a diagnostic center and you receive packets from an
> IP address claiming to have a particular VIN number, how do you
> authenticate it?  How do you know that is really the vehicle it claims
> to be?  You will need application layer authentication in any case.
> 
> I believe it would be much better to decouple "vehicle identification"
> from "IP layer location" (the IP address).  These tokens have

This made me immediately think of HIP with the VIN being used as the
Host Identifier.

> different purposes.  The vehicle identification is for use with
> database applications and diagnostic applications, while the IP
> address is for IP forwarding to know how to reach the vehicle.  You
> could possibly allow the vehicle to connect to the network and get any
> IP address -- any address at all -- and then connect to the diagnostic
> center and tell you its VIN and authenticate, all in a higher layer
> protocol.

From jonghyouk@gmail.com  Thu Mar 31 06:00:36 2011
Return-Path: <jonghyouk@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91AF73A6B12 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:00:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7EBBiVgqT1o for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:00:34 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 3E3F13A6B4F for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:00:30 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2241511wyb.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:02:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cVUrc2nzcNdDG7+45xNN70WYhDjlrzJS/tBOjAixmoE=; b=fckTvQSRVO+2dg8Xfzmn+30WmiD9c6MLW4ViN46Ja01peITvQ91ALWs04q1bXwrm2G Ekwvd+h6E4MnIxe6jpNPznDsJgJYWzmM3JAAMjgLl52pJiT9EllwXmBu3ND8k+m16qaD jkAcMGwNQAVKJKATKc/RM/T6Bir+3plivd83w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=blkrj2LxSsOJLbKfxLfXmI5Mjf1svCAxJnGaNORZ0nFsLrQGIRfYjUFZzCxWz8IZOT 1RtPnkHYYgPPUkUSn1oMO2o8Egigg9aeA8d49sH95VRr9168xSf3egcdaOGTdkfs2GWE Nr0UIlm2fNZ201unPAudcbQhnsAesy2obNl+4=
MIME-Version: 1.0
Received: by 10.227.139.149 with SMTP id e21mr2592779wbu.147.1301576529078; Thu, 31 Mar 2011 06:02:09 -0700 (PDT)
Received: by 10.227.152.201 with HTTP; Thu, 31 Mar 2011 06:02:08 -0700 (PDT)
In-Reply-To: <575406.83799.qm@web111414.mail.gq1.yahoo.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com>
Date: Thu, 31 Mar 2011 15:02:08 +0200
Message-ID: <AANLkTimOP1bd=W9ETy5nzE3Q=2nfgoFLLk=gaLD_bqQq@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
From: Jong-Hyouk Lee <jonghyouk@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>, radoslaw.wrobel@pwr.wroc.pl
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 13:00:36 -0000

Dear all.

For Internet connectivity of vehicles, the use of IPv6 (with mobility
support, NEMO) is being fully considered at some standardization
organizations such as ISO and ETSI. But, I totally disagree with the
use of IPv6 as a permanent ID of a vehicle, i.e., VIN, because

1) This breaks the layered architecture concept.
2) This causes security issues, especially location privacy.

For, the comments from Behcet, plz see inline.

On Thu, Mar 31, 2011 at 2:28 PM, Behcet Sarikaya
<behcetsarikaya@yahoo.com> wrote:
> I think the idea here is to use VIN as link layer id when assigning an
> address/prefix to a host in the car.

The ITS station architecture being considered at ISO and ETSI defines
that a vehicle ITS station must implement at least three entities such
as the gateway, router, and host. The mobility support for Internet
connectivity, i.e., NEMO, is in the router forming the in-vehicle
network where hosts of the vehicle ITS station are attached.

So, the use of link layer ID as the VIN does not make sense.

In addition, the link layer ID for the router of vehicle is changed
frequently, e.g., randomly generated ID is used for preventing
location tracking. Even the security mechanism developed for securing
the vehicle ITS station adopts an approach of pseudonym, i.e.,
certificate not including any identical information of vehicle and
vehicle's owner and use in a given short time.

Cheers.

The host can provide such an id in DHCP
> request message.
>
> Regards,
>
> Behcet
>
>> Dear all,
>>
>> I fail to see why a VIN would be mapped to an IPv6 address as =A0much as=
 I fail
>>to see why a passport number would be mapped to an IPv6 number. =A0As sai=
d by
>>Scott, the purpose of the IP address is to forward packets to the =A0dest=
ination.
>>
>> Such an idea is going against location privacy. To address =A0the locati=
on
>>privacy issue related to the ID of the vehicle used at the =A0networking =
layer,
>>the Car-to-Car Communication Consortium propose to use =A0pseudonyms; whe=
n it goes
>>to IPv6 communications (all communications are not =A0IP-based) this pseu=
donym is
>>used to configure an IPv6 address, i.e. a transient =A0address (you can c=
heck the
>>work of the SeVeCom project). In the meantime, the =A0vehicle also has a =
permanent
>>address (indeed, prefix) as which the vehicle is =A0reachable (using NEMO=
). Up to
>>now, there is no one in any of the standardisation =A0or consortium I kno=
w (ETSI
>>TC ITS, ISO TC204, ISO TC22, CEN TC278, Car2Car =A0Communication Consorti=
um) who
>>is thinking about mapping a vehicle ID to the IPv6 =A0address.
>>
>> So, I'm afraid this idea is going =A0nowhere.
>>
>> Regards,
>> Thierry Ernst.
>>
>> On 31/03/11 10:40, Scott Brim =A0wrote:
>> > Hello Radek.
>> >
>> > I have privacy concerns, because =A0the VIN is permanent for the vehic=
le.
>> > =A0 I suspect there is a good =A0chance that the vehicle's IP address =
will
>> > not be used just for =A0diagnostics, but also for general purpose
>> > connections to the Internet =A0(for example fetching a movie for the
>> > children). =A0If an IP address =A0is based on VIN, then it will never
>> > change, ever. =A0It will be =A0possible for observers to build up
>> > information about what the vehicle's =A0users like to connect to.
>> >
>> > Also, if you are a diagnostic center =A0and you receive packets from a=
n
>> > IP address claiming to have a particular =A0VIN number, how do you
>> > authenticate it? =A0How do you know that is =A0really the vehicle it c=
laims
>> > to be? =A0You will need application =A0layer authentication in any cas=
e.
>> >
>> > I believe it would be much =A0better to decouple "vehicle identificati=
on"
>> > from "IP layer location" =A0(the IP address). =A0These tokens have
>> > different purposes. =A0The =A0vehicle identification is for use with
>> > database applications and =A0diagnostic applications, while the IP
>> > address is for IP forwarding to =A0know how to reach the vehicle. =A0Y=
ou
>> > could possibly allow the =A0vehicle to connect to the network and get =
any
>> > IP address -- any address =A0at all -- and then connect to the diagnos=
tic
>> > center and tell you its VIN =A0and authenticate, all in a higher layer
>> > protocol.
>> >
>> > =A02011/3/30 Radek Wr=F3bel<radoslaw.wrobel@pwr.wroc.pl>:
>> >> =A0Dear 6man!
>> >> My name is Radek Wrobel, I'm writing from Poland (I'm =A0working in W=
roclaw
>> >> University of Technology, Division of Car =A0Vehicles and Combustion
>> >> Engines). With this idea I wrote to IANA and =A0Leo Vegoda redirected=
 me to
>> >> you.
>> >> Vehicle / mechanic =A0engineers are working on a new On Board Diagnos=
is
>> >> standard for =A0vehicles (http://en.wikipedia.org/wiki/On-board_diagn=
ostics).
>> >> Today =A0EOBDv1 can diagnose (quasi online) 849 failures. One of most
>>important
>> >> advantage of EOBDv2 (but not only it) will be constant, =A0real time
>> >> communication with service. The best way of them will be =A0indyvidua=
l number
>> >> for every car vehicles in the world. This number =A0ought to cooporat=
e with
>> >> global networking - TCP/IP (IPv6). All cars =A0have indyvidual number=
 - VIN
>> >> (17 characters which indicates on a =A0country of production =A0and m=
ark of the
>> >> car: digits and letters =A0A-X). Maybe there is time when someone mus=
t think
>> >> about conversion =A0VIN to IPv6 (like it's in local IPv4)? I've a few=
 ideas
>> >> about it and =A0of course I can share them if you will be intersting =
in.
>> >> Also we =A0cooperate with VW and Toyota. I think they will be interes=
ting
>>about
>> >> =A0it too.
>> >> Best regards, Radek Wrobel.
>> >> =A0+48660406004
>> >>
>> >> =A0------------------------------------------------------------------=
--
>> >> =A0IETF IPv6 working group mailing list
>> >> ipv6@ietf.org
>> >> Administrative =A0Requests: https://www.ietf.org/mailman/listinfo/ipv=
6
>> >> =A0------------------------------------------------------------------=
--
>> >>
>> >>
>> > =A0-------------------------------------------------------------------=
-
>> > =A0IETF IPv6 working group mailing list
>> > ipv6@ietf.org
>> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> > =A0-------------------------------------------------------------------=
-
>>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



--=20
IMARA Team, INRIA, France.
Jong-Hyouk Lee.

#email: jonghyouk (at) gmail (dot) com || jong-hyouk.lee (at) inria (dot) f=
r
#webpage: https://sites.google.com/site/hurryon/

From roland.bless@kit.edu  Thu Mar 31 06:01:13 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE46728C14A for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.332
X-Spam-Level: 
X-Spam-Status: No, score=-6.332 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WIyyTfP8u4or for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:01:13 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 13D8E28C0F9 for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:01:13 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5HWM-0004HH-K9; Thu, 31 Mar 2011 15:02:49 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 748BF2C6; Thu, 31 Mar 2011 15:05:37 +0200 (CEST)
Message-ID: <4D947B71.5010002@kit.edu>
Date: Thu, 31 Mar 2011 15:02:41 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Nathan Ward <ietf-ipv6@daork.net>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <7EF89C89-675C-446E-9B00-AE06820988B6@daork.net>
In-Reply-To: <7EF89C89-675C-446E-9B00-AE06820988B6@daork.net>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301576569.898610000
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 13:01:14 -0000

Hi,

On 31.03.2011 12:43, Nathan Ward wrote:
> Perhaps something a bit more relevant to IETF is generating a ULA prefix from a VIN?

That could indeed be useful.
In the German SEIS project we are considering to use IPv6
internally for communication between ECUs in cars. For such internal
use this may help indeed a lot. It's a different story for external
connectivity.

Regards,
 Roland

From roland.bless@kit.edu  Thu Mar 31 06:08:46 2011
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AFEB3A6A1B for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.327
X-Spam-Level: 
X-Spam-Status: No, score=-6.327 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2J-5C-9XouYX for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:08:45 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 4F0A63A67E9 for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:08:44 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1Q5Hdh-0005hN-At; Thu, 31 Mar 2011 15:10:23 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 2CC4D2C6; Thu, 31 Mar 2011 15:13:12 +0200 (CEST)
Message-ID: <4D947D38.6070901@kit.edu>
Date: Thu, 31 Mar 2011 15:10:16 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com>	<7EF89C89-675C-446E-9B00-AE06820988B6@daork.net> <AANLkTikAA1WfeKgc8_L0Z-JYFGAUuGzvXyUQPZmvyJvD@mail.gmail.com>
In-Reply-To: <AANLkTikAA1WfeKgc8_L0Z-JYFGAUuGzvXyUQPZmvyJvD@mail.gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1301577023.845563000
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 13:08:46 -0000

Hi Scott,

On 31.03.2011 13:18, Scott Brim wrote:
>> Perhaps something a bit more relevant to IETF is generating a ULA prefix from a VIN?
> 
> If these addresses will never be used for anything except diagnostics
> and internal communications, then okay, but this looks like a classic
> case of a net that is going to start out with just local use, and soon
> move to needing global addresses.  Hey, I know, NAT.

We are currently designing a security architecture for cars
that use IPv6 for their internal communications. For this
internal communication, you may use this ULA-like prefix.
If external connectivity is required (which will be the case),
this may happen by dedicated ALGs or proxies, making sure
that the safety-critical internal communications is not
affected adversely. Filtering traffic would be easier
using something like ULAs. Direct, unauthorized access to the ECUs
is therefore unwanted and unlikely.

Regards,
 Roland

From alexandru.petrescu@gmail.com  Thu Mar 31 06:50:26 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70E6128C168 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.83
X-Spam-Level: 
X-Spam-Status: No, score=-4.83 tagged_above=-999 required=5 tests=[AWL=0.769,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZkYb1dxZhuMl for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 06:50:25 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 3E26228C141 for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:50:25 -0700 (PDT)
Received: by wwa36 with SMTP id 36so1986264wwa.13 for <ipv6@ietf.org>; Thu, 31 Mar 2011 06:52:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Wdc2e43vekdvSZJy8jn3+bxArjcAdsZbqlbA55CIPEg=; b=gLrvXbIZfe1zNMDmbhrcBHeQeEOs3RL6XmUw8wHGeKjxgeZR7YWpukhc4Ltih7idum T4T9T3jQWnke1P/VeXSWx3ZpJsh0WYfKcsROVXyldI2hP4c+g4j9y1w3KTsjgvWBnQ2O N7bn11OexkwOWWB4xUqKrIFoAAestPwm256dA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=K3ePrCokbiu+Vv8WBBC8k7RcBF3qMtucM5VdD/v/LlxOsxuQ5kJ/mRU+0VsI2gNlSV RRyZTSSFudR5pNSP3YVXhREKxFm9elTtplG7EhYftDqz6J9e0SJxJpUDd+CP8TpPbeqm CV8+KFzw0Gruql4ihll5aab6lINywtbesTg6k=
Received: by 10.227.174.14 with SMTP id r14mr520387wbz.30.1301579524350; Thu, 31 Mar 2011 06:52:04 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id x1sm665699wbh.19.2011.03.31.06.52.02 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 06:52:03 -0700 (PDT)
Message-ID: <4D948700.5070807@gmail.com>
Date: Thu, 31 Mar 2011 15:52:00 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Roland Bless <roland.bless@kit.edu>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D9452B3.2010504@gmail.com> <4D9456E6.90608@kit.edu>
In-Reply-To: <4D9456E6.90608@kit.edu>
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org, =?ISO-8859-2?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 13:50:26 -0000

Le 31/03/2011 12:26, Roland Bless a 閏rit :
> Hi Alexandru,
>
> On 31.03.2011 12:08, Alexandru Petrescu wrote:
>> Thanks for the pointer, I am discovering OBD.  We are also
>> interested in wireless usage of IP within the vehicle, with
>> off-the-shelf links (i.e. consumer electronics market wifi,
>> bluetooth, ant) together with OBD if needed.
>
> See below.
>
>>> Today EOBDv1 can diagnose (quasi online) 849 failures. One of
>>> most important advantage of EOBDv2 (but not only it) will be
>>> constant, real time communication with service. The best way of
>>> them will be indyvidual number for every car vehicles in the
>>> world.
>>
>> Excellent requirement to IP.
>
> Maybe to some mapping system, but not directly to IPv6 (ID/Loc
> split).

I quickly get confused on id/loc split discussions.  I meant to say that
it is wonderful to request Internet to let a vehicle connect to it
anywhere in the world and, moreover, solution should not be exclusively 
satellite.

>>> This number ought to cooporate with global networking - TCP/IP
>>> (IPv6). All cars have indyvidual number - VIN (17 characters
>>> which indicates on a country of production and mark of the car:
>>> digits and letters A-X). Maybe there is time when someone must
>>> think about conversion VIN to IPv6
>>
>> Hmm... sounds as good idea.  But there may be several IP addresses
>> within a vehicle, one for the obu, one for map device, etc.
>
>> In case one would like to map VIN to an IPv6 address one would
>> consider first an Interface Identifier of the IPv6 address.
>> (rightmost 64 bits). Interface Identifier is about an Interface,
>> and I am not sure VIN is about an interface, or is it. (like
>> Interface is the Ethernet interface of this pc).
>
> Yes, but from a security point of view, it would be a nightmare if
> some hacker could directly send IP packets to the ECU controlling
> your airbag or other safety relevant ECUs etc. So a strong security
> architecture is a MUST.

I agree, appropriate security is useful.  What's ECU? (other than the
currency).

> I'm not sure that there is a need to _directly_ address any internal
> car devices. A security gateway as policy enforcement point seems to
> be required at least.

For entertainment, passengers may like to youtube without policy
enforcement, i.e. all laptops in the vehicle be each IP-addressable.

In other cases, only the OBU would be IP-addressable and it would be
connect on its ingress interface to rs232/can devices (but it would
still need a 2nd IP address on that interface).

Alex

> Regards, Roland


From bob.hinden@gmail.com  Thu Mar 31 07:18:09 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D61673A6AD7 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pToYnmuhxS2X for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:18:09 -0700 (PDT)
Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by core3.amsl.com (Postfix) with ESMTP id 2DAAF3A6A92 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:18:09 -0700 (PDT)
Received: by pxi20 with SMTP id 20so634197pxi.27 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:19:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=j954oZ3J5wimVeCPMp2OwxbnW1L5pcB9QFBRZETMI7M=; b=b50Q3vFtqM6ESGS2zcv7JpSPUpgXar3CGmS2ccUuS9KBrT69pTaLICipf/Fr7tbI2J s8h9IjRssP9LG67sf+tabZMNl7e5HUXVAB93vMzFFbcMi77Ssn6Pj1inu356gQxbedtT 8nFsZk3uLeVBOHgzKg94q/R8G3y4tpDjtjISU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=OCpuaxt7pNxWSoQMo9+/MObW1qe75qXro6LIpCmiWqJJuMDZsGrTU2lTqfb4P6R4cT nRa1FfIl1c6VcyMNTqQE4lyTkWlt6gCSrlNEb65iCdx6Ie3fZfPSBsVZ2x1UamULingv EmcP7gEpbKjAEtuZ4AZMGyrDXr2Sff2Qz375s=
Received: by 10.142.199.9 with SMTP id w9mr1927395wff.366.1301581188756; Thu, 31 Mar 2011 07:19:48 -0700 (PDT)
Received: from dhcp-6337.meeting.ietf.org (dhcp-6337.meeting.ietf.org [130.129.99.55]) by mx.google.com with ESMTPS id y2sm1567185wfd.8.2011.03.31.07.19.44 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 31 Mar 2011 07:19:46 -0700 (PDT)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com>
Date: Thu, 31 Mar 2011 16:19:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com> <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com>
To: Scott Brim <Scott.Brim@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?iso-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 14:18:09 -0000

On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:

> On Thu, Mar 31, 2011 at 11:32, Bob Hinden <bob.hinden@gmail.com> =
wrote:
>> They could use a fixed car address and use mobile IPv6 with a =
provider based address.
>=20
> That would help.  A rendezvous point (e.g. home agent) always helps to
> protect confidentiality. Plus a firewall to protect the
> always-out-of-date vehicle software.   They can work out how to do
> path optimization later.

I agree.  If you put the "home agent" in the middle of the internet (for =
some value of middle), then path optimization probably isn't that =
important.

Bob


From behcetsarikaya@yahoo.com  Thu Mar 31 07:32:36 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D4B928C0F7 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:32:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.39
X-Spam-Level: 
X-Spam-Status: No, score=-3.39 tagged_above=-999 required=5 tests=[AWL=1.209,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0jy7B2kQWc6 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:32:35 -0700 (PDT)
Received: from nm6-vm1.bullet.mail.sp2.yahoo.com (nm6-vm1.bullet.mail.sp2.yahoo.com [98.139.91.207]) by core3.amsl.com (Postfix) with SMTP id 1E02C28C102 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:32:35 -0700 (PDT)
Received: from [98.139.91.68] by nm6.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 14:34:10 -0000
Received: from [98.139.91.15] by tm8.bullet.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 14:34:10 -0000
Received: from [127.0.0.1] by omp1015.mail.sp2.yahoo.com with NNFMP; 31 Mar 2011 14:34:10 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 222956.1721.bm@omp1015.mail.sp2.yahoo.com
Received: (qmail 58503 invoked by uid 60001); 31 Mar 2011 14:34:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1301582049; bh=ts52gmGCeAfvKQmQEMEveTgMe1417yEKuAYZf9F+O1g=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DUGPzw4qh/6UQBoOLqIW/aj5Q/WcTIN5a8C3vzfEsOpS+wIUu1xIu0xM+CnMzIudoCM3CL21222PQw4RKPRh1gEXQU9ScV/6M0E7QLYM6zdMGADb7/7tuNedAuVXmHNcvxuB8DloERcRZ8bbnetZGNTBlEMdlsmfq4Y1CY64NhM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ApnTGtNy/TWQFjmtQDQ8s88tLIrbB9MS9QTUx3cxAElJV3H8UUe/jhHTEIKIOGjwx+11DEdYZCuoba2BDChlw5JOhtc9cjYwoX+p5Y0fF3ZzoYlNuOwHP+/zB0q4aLZ6BLUFP/gxHySHkTktyjMBxhEJYJk19ZCUZq8aRPNvNY0=;
Message-ID: <867407.58179.qm@web111412.mail.gq1.yahoo.com>
X-YMail-OSG: esKV3Y8VM1nkJSimncyVfkVeP0I5tHy38kk.gP36vvhWQC3 eeXdXYn.7cDT2nePz9wtoomOuFFG5Ilh_l6IIPKyE2tLem4ppyrzFxZ3l2sh tunsClT8GkgZlxunFmUrqBzvpbWrc2cJ8XXAawPvozNNW5RjARa86V6rqxG. VpIENUcmm920heXKAcKpFonZLIG.HjMA3fgg7kLz9bNBGsEnbCOtrDQ66ApD 105uJQ_Dvpxl22yu9CrpLTVRoLjyKyeiWL3tEr_MEzRNAhv71KJlH.wD3Rwk 3cJPCzoF3A_Gcfh9GxubL54SKoNAh63RHuWGOjqpVoQ.ixvfvJOTSe08CSwY 6KQwUgIFHechsWCIJdsgdHS56duRIGZF2wZ5xjl65vGtBYXGie2vB9OLrrgD B7Gjnu0qw0vODiQ--
Received: from [130.129.18.76] by web111412.mail.gq1.yahoo.com via HTTP; Thu, 31 Mar 2011 07:34:09 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.109.295617
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com> <4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com> <AANLkTimOP1bd=W9ETy5nzE3Q=2nfgoFLLk=gaLD_bqQq@mail.gmail.com>
Date: Thu, 31 Mar 2011 07:34:09 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: Vehicle's VIN in IPv6.
To: Jong-Hyouk Lee <jonghyouk@gmail.com>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <AANLkTimOP1bd=W9ETy5nzE3Q=2nfgoFLLk=gaLD_bqQq@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 14:32:36 -0000

I meant something like DUID.=0A=0A--b=0A=0A=0A=0A> Dear all.=0A> =0A> For I=
nternet connectivity of vehicles, the use of IPv6 (with  mobility=0A> suppo=
rt, NEMO) is being fully considered at some  standardization=0A> organizati=
ons such as ISO and ETSI. But, I totally disagree  with the=0A> use of IPv6=
 as a permanent ID of a vehicle, i.e., VIN,  because=0A> =0A> 1) This break=
s the layered architecture concept.=0A> 2) This  causes security issues, es=
pecially location privacy.=0A> =0A> For, the comments  from Behcet, plz see=
 inline.=0A> =0A> On Thu, Mar 31, 2011 at 2:28 PM, Behcet  Sarikaya=0A> <be=
hcetsarikaya@yahoo.com>  wrote:=0A> > I think the idea here is to use VIN a=
s link layer id when  assigning an=0A> > address/prefix to a host in the ca=
r.=0A> =0A> The ITS station  architecture being considered at ISO and ETSI =
defines=0A> that a vehicle ITS  station must implement at least three entit=
ies such=0A> as the gateway, router,  and host. The mobility support for In=
ternet=0A> connectivity, i.e., NEMO, is in  the router forming the in-vehic=
le=0A> network where hosts of the vehicle ITS  station are attached.=0A> =
=0A> So, the use of link layer ID as the VIN does not  make sense.=0A> =0A>=
 In addition, the link layer ID for the router of vehicle is  changed=0A> f=
requently, e.g., randomly generated ID is used for  preventing=0A> location=
 tracking. Even the security mechanism developed for  securing=0A> the vehi=
cle ITS station adopts an approach of pseudonym,  i.e.,=0A> certificate not=
 including any identical information of vehicle  and=0A> vehicle's owner an=
d use in a given short time.=0A> =0A> Cheers.=0A> =0A> The  host can provid=
e such an id in DHCP=0A> > request message.=0A> >=0A> >  Regards,=0A> >=0A>=
 > Behcet=0A> >=0A> >> Dear  all,=0A> >>=0A> >> I fail to see why a VIN wou=
ld be mapped to an IPv6  address as  much as I =0A>fail=0A> >>to see why a =
passport number would be  mapped to an IPv6 number.  As said by=0A> >>Scott=
, the purpose of the IP  address is to forward packets to the =0A> destinat=
ion.=0A> >>=0A> >> Such  an idea is going against location privacy. To addr=
ess  the  location=0A> >>privacy issue related to the ID of the vehicle use=
d at the   networking =0A>layer,=0A> >>the Car-to-Car Communication Consort=
ium propose to  use  pseudonyms; when it =0A>goes=0A> >>to IPv6 communicati=
ons (all  communications are not  IP-based) this pseudonym =0A>is=0A> >>use=
d to configure  an IPv6 address, i.e. a transient  address (you can check =
=0A>the=0A> >>work of  the SeVeCom project). In the meantime, the  vehicle =
also has a  =0A>permanent=0A> >>address (indeed, prefix) as which the vehic=
le is  reachable  (using NEMO). Up =0A>to=0A> >>now, there is no one in any=
 of the  standardisation  or consortium I know =0A>(ETSI=0A> >>TC ITS, ISO =
TC204, ISO  TC22, CEN TC278, Car2Car  Communication Consortium) =0A>who=0A>=
 >>is thinking  about mapping a vehicle ID to the IPv6  address.=0A> >>=0A>=
 >> So, I'm  afraid this idea is going  nowhere.=0A> >>=0A> >> Regards,=0A>=
 >>  Thierry Ernst.=0A> >>=0A> >> On 31/03/11 10:40, Scott Brim   wrote:=0A=
> >> > Hello Radek.=0A> >> >=0A> >> > I have  privacy concerns, because  th=
e VIN is permanent for the vehicle.=0A> >>  >   I suspect there is a good  =
chance that the vehicle's IP address  will=0A> >> > not be used just for  d=
iagnostics, but also for general  purpose=0A> >> > connections to the Inter=
net  (for example fetching a  movie for the=0A> >> > children).  If an IP a=
ddress  is based on VIN,  then it will never=0A> >> > change, ever.  It wil=
l be  possible for  observers to build up=0A> >> > information about what t=
he vehicle's   users like to connect to.=0A> >> >=0A> >> > Also, if you are=
 a  diagnostic center  and you receive packets from an=0A> >> > IP address =
 claiming to have a particular  VIN number, how do you=0A> >> >  authentica=
te it?  How do you know that is  really the vehicle it  claims=0A> >> > to =
be?  You will need application  layer authentication  in any case.=0A> >> >=
=0A> >> > I believe it would be much   better to decouple "vehicle identifi=
cation"=0A> >> > from "IP layer  location"  (the IP address).  These tokens=
 have=0A> >> > different  purposes.  The  vehicle identification is for use=
 with=0A> >> > database  applications and  diagnostic applications, while t=
he IP=0A> >> > address  is for IP forwarding to  know how to reach the vehi=
cle.  You=0A> >> >  could possibly allow the  vehicle to connect to the net=
work and get  any=0A> >> > IP address -- any address  at all -- and then co=
nnect to  the diagnostic=0A> >> > center and tell you its VIN  and authenti=
cate,  all in a higher layer=0A> >> > protocol.=0A> >> >=0A> >>  >  2011/3/=
30 Radek Wr=F3bel<radoslaw.wrobel@pwr.wroc.pl>:=0A> >>  >>  Dear 6man!=0A> =
>> >> My name is Radek Wrobel, I'm writing  from Poland (I'm  working in =
=0A>Wroclaw=0A> >> >> University of  Technology, Division of Car  Vehicles =
and Combustion=0A> >> >>  Engines). With this idea I wrote to IANA and  Leo=
 Vegoda redirected me  =0A>to=0A> >> >> you.=0A> >> >> Vehicle / mechanic  =
engineers  are working on a new On Board Diagnosis=0A> >> >> standard for  =
 vehicles =0A>(http://en.wikipedia.org/wiki/On-board_diagnostics).=0A> >>  =
>> Today  EOBDv1 can diagnose (quasi online) 849 failures. One of  most=0A>=
 >>important=0A> >> >> advantage of EOBDv2 (but not only  it) will be const=
ant,  real time=0A> >> >> communication with  service. The best way of them=
 will be  indyvidual =0A>number=0A> >> >>  for every car vehicles in the wo=
rld. This number  ought to cooporate  =0A>with=0A> >> >> global networking =
- TCP/IP (IPv6). All cars  have  indyvidual number - =0A>VIN=0A> >> >> (17 =
characters which indicates on a   country of production  and mark of =0A>th=
e=0A> >> >> car: digits and  letters  A-X). Maybe there is time when someon=
e must =0A>think=0A> >> >>  about conversion  VIN to IPv6 (like it's in loc=
al IPv4)? I've a few  =0A>ideas=0A> >> >> about it and  of course I can sha=
re them if you will  be intersting in.=0A> >> >> Also we  cooperate with VW=
 and Toyota. I  think they will be interesting=0A> >>about=0A> >> >>  it  t=
oo.=0A> >> >> Best regards, Radek Wrobel.=0A> >> >>   +48660406004=0A> >> >=
>=0A> >> >>   -------------------------------------------------------------=
-------=0A> >>  >>  IETF IPv6 working group mailing list=0A> >> >> ipv6@iet=
f.org=0A> >> >>  Administrative  Requests: https://www.ietf.org/mailman/lis=
tinfo/ipv6=0A> >>  >>   ---------------------------------------------------=
-----------------=0A> >>  >>=0A> >> >>=0A> >> >   -------------------------=
-------------------------------------------=0A> >>  >  IETF IPv6 working gr=
oup mailing list=0A> >> > ipv6@ietf.org=0A> >> > Administrative  Requests: =
https://www.ietf.org/mailman/listinfo/ipv6=0A> >> >   ---------------------=
-----------------------------------------------=0A> >>=0A> >>=0A> >  ------=
--------------------------------------------------------------=0A> >  IETF =
IPv6 working group mailing list=0A> > ipv6@ietf.org=0A> > Administrative Re=
quests: https://www.ietf.org/mailman/listinfo/ipv6=0A> >  -----------------=
---------------------------------------------------=0A> >=0A> =0A> =0A> =0A=
> -- =0A> IMARA Team, INRIA, France.=0A> Jong-Hyouk Lee.=0A> =0A> #email: j=
onghyouk (at)  gmail (dot) com || jong-hyouk.lee (at) inria (dot) fr=0A> #w=
ebpage: https://sites.google.com/site/hurryon/=0A> 

From jonghyouk@gmail.com  Thu Mar 31 07:32:42 2011
Return-Path: <jonghyouk@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D118D28C139 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:32:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0zKp3CWbDnl for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:32:42 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id AAFB428C137 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:32:41 -0700 (PDT)
Received: by wwa36 with SMTP id 36so2026237wwa.13 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:34:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=orBKeBDb4BSLakoohk54jDE7SY7oQkoNfwEkF1aHwgQ=; b=vtKy3VIjyYsaDQ46QGoXa9vuqRpMOgNET30KYHulbhqMfzn9zMlfS5MNHP+gL50apU TBAldyEIKLtnZ7LH64M28BXHqewIzkUpxg4H4z+xmxVCQjYJHed93OHCzMv0/XMB7/Z9 Pyu/wt9LdMGYoHgdeuzZ/CIYRhSOJotd1lPEc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=k5rvSbvKn4mK3AN+GkP9v2UmxeOCxXqlvXH9/qWbHV67mVjzPOL0YELyy12dHth3Gr /wFEjd7Eo6a9dhv3P0QKKhqC8h0CZ3QCNpf9x4fqwnZ8PY0QdxPpAyAixA4KWqjZQe1S uy5JX2VJdrH40qrFNSJYSgnffejVU+dBImQds=
MIME-Version: 1.0
Received: by 10.227.172.7 with SMTP id j7mr2782184wbz.60.1301582060777; Thu, 31 Mar 2011 07:34:20 -0700 (PDT)
Received: by 10.227.152.201 with HTTP; Thu, 31 Mar 2011 07:34:20 -0700 (PDT)
In-Reply-To: <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com> <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com> <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>
Date: Thu, 31 Mar 2011 16:34:20 +0200
Message-ID: <AANLkTikyThYbMwAiB=47beqTCwR70=zsskBVAc37kokW@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
From: Jong-Hyouk Lee <jonghyouk@gmail.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 14:32:42 -0000

Dear all.

Plz, see inline.

On Thu, Mar 31, 2011 at 4:19 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>
> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>
>> On Thu, Mar 31, 2011 at 11:32, Bob Hinden <bob.hinden@gmail.com> wrote:
>>> They could use a fixed car address and use mobile IPv6 with a provider =
based address.

Clearly, not Mobile IPv6, the correct one is NEMO able to form the
in-vehicle network wherein hosts, e.g., electronic control units, can
attach through IPv6 addresses.

>>
>> That would help. =A0A rendezvous point (e.g. home agent) always helps to
>> protect confidentiality. Plus a firewall to protect the
>> always-out-of-date vehicle software. =A0 They can work out how to do
>> path optimization later.
>
> I agree. =A0If you put the "home agent" in the middle of the internet (fo=
r some value of middle), then path optimization probably isn't that importa=
nt.

No. The routing performance in terms of NEMO, i.e., IPv6 data packets
destined to hosts attached to a vehicle, should not be solved by
locating the home agent in a proper location at the Internet. It
should be approached by thinking of how network prefix being used in
the in-vehicle network, i.e., mobile network prefix in terms of NEMO,
is provisioned.

Cheers.

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



--=20
IMARA Team, INRIA, France.
Jong-Hyouk Lee.

#email: jonghyouk (at) gmail (dot) com || jong-hyouk.lee (at) inria (dot) f=
r
#webpage: https://sites.google.com/site/hurryon/

From alexandru.petrescu@gmail.com  Thu Mar 31 07:51:43 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 713DB28B56A for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.884
X-Spam-Level: 
X-Spam-Status: No, score=-3.884 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hwurh0soK6K5 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 07:51:42 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 10D8C3A6B38 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:51:41 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2357545wyb.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 07:53:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ldmw4+cdNt5Wx7xxJBx+bsEm39xbhiPs2h1ssRM63+M=; b=A9lNEY1LeTBNZ8Zq8oB3vq67zvmcVgaqfiOPo0Plb11CQUrblzY+Qj80hfc+Fd9nKn qz1nt/HLheGmaS0GzGp+fOSk0pxPH2OvzCwp/j9NeQ3RAMTPj0SZkDMJH0EctWEcp+EN CNSOtM5pf2Ah6s9daOx9QKucK5erlyVomOpE0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=aU03JOOaE7YT1rqnJP8wfYYz3PlHtB+lUO1zEBu99K69Jv0M86I2UyWC36sHcF6FN0 L/t3Wg8e6ZkO9QiUuUKkdMNK5cNM9dXtXOOaD2Z8I/NhBrNlXgqlrfjb5yqoOi3zDdbc uQi/kRvOGcyZWcg9eftJqDmGKE1vqhNXzoAzg=
Received: by 10.227.12.17 with SMTP id v17mr2786780wbv.157.1301583200406; Thu, 31 Mar 2011 07:53:20 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id o23sm700150wbc.10.2011.03.31.07.53.15 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 07:53:16 -0700 (PDT)
Message-ID: <4D949559.3090509@gmail.com>
Date: Thu, 31 Mar 2011 16:53:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com>	<E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>	<AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com> <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>
In-Reply-To: <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 14:51:43 -0000

Le 31/03/2011 16:19, Bob Hinden a 閏rit :
>
> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>
>> On Thu, Mar 31, 2011 at 11:32, Bob Hinden<bob.hinden@gmail.com>
>> wrote:
>>> They could use a fixed car address and use mobile IPv6 with a
>>> provider based address.
>>
>> That would help.  A rendezvous point (e.g. home agent) always
>> helps to protect confidentiality. Plus a firewall to protect the
>> always-out-of-date vehicle software.   They can work out how to do
>>  path optimization later.
>
> I agree.  If you put the "home agent" in the middle of the internet
> (for some value of middle), then path optimization probably isn't
> that important.

Makes some sense.  This "middle" depends on latency; and core network
has an order of magnitude (sometimes 2) less than even the first hop to
vehicle.

That means that it may suffice to put the HA on wired link, anywhere in
the Internet, and relatively close (in terms of hopcount) to where the
handover is about to take place.  And not necessarily put it where eg
akamai stuff sits.

Alex

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


From jonghyouk@gmail.com  Thu Mar 31 08:00:48 2011
Return-Path: <jonghyouk@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1029528C140 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Etuan3fwG9Zx for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:00:47 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id E442E3A6B10 for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:00:46 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2366937wyb.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Zj/lG5VQAEOX8XyP4t9q4N+1lgZZVvpCeze91fNlf+A=; b=sNTlkBB+pAyM8ex5ixvns8b14CAyI0sDoYl4kCzLaaotqWDdEZqCdKtXHWSJJFq8V/ 2zPjFKcCRahUVEFlY2Evl6U5uFZUts0uaJg9rTBe7Olx3mkuZBrN48AeBSx84U5zRPll SrUpLhDz+XSrbb+7gLAfTocwAajBBx0VOuRxA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=IK0DGfcRQP3rLiuKkjZ3uwBa9TIEYTOjiVhdZanzvnDMfgr0ePUYcI+loLuYd6FyTm nMSbe9WFcu6yiljkNyOZWTvWY9dmeyrRwuALOERmlsStM6P2ucsVPERdzpwG80Elkjvh QPxro6Xe+SR+hpC6qb/pD644pyHerVf+3L+Rc=
MIME-Version: 1.0
Received: by 10.227.172.7 with SMTP id j7mr2815820wbz.60.1301583745824; Thu, 31 Mar 2011 08:02:25 -0700 (PDT)
Received: by 10.227.152.201 with HTTP; Thu, 31 Mar 2011 08:02:25 -0700 (PDT)
In-Reply-To: <4D949559.3090509@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com> <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com> <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com> <4D949559.3090509@gmail.com>
Date: Thu, 31 Mar 2011 17:02:25 +0200
Message-ID: <AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
From: Jong-Hyouk Lee <jonghyouk@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 15:00:48 -0000

Hi, Alex.

Plz, see inline. I fully failed to understand your words.

On Thu, Mar 31, 2011 at 4:53 PM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> Le 31/03/2011 16:19, Bob Hinden a =E9crit :
>>
>> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>>
>>> On Thu, Mar 31, 2011 at 11:32, Bob Hinden<bob.hinden@gmail.com>
>>> wrote:
>>>>
>>>> They could use a fixed car address and use mobile IPv6 with a
>>>> provider based address.
>>>
>>> That would help. =A0A rendezvous point (e.g. home agent) always
>>> helps to protect confidentiality. Plus a firewall to protect the
>>> always-out-of-date vehicle software. =A0 They can work out how to do
>>> =A0path optimization later.
>>
>> I agree. =A0If you put the "home agent" in the middle of the internet
>> (for some value of middle), then path optimization probably isn't
>> that important.
>
> Makes some sense. =A0This "middle" depends on latency; and core network
> has an order of magnitude (sometimes 2) less than even the first hop to
> vehicle.

In the context of ITS communication, how do you expect the movement of
vehicles? Then, how do you decide the location of home agent for
reducing the routing performance for user data packets destined to
hosts attached to the router of a vehicle?

>
> That means that it may suffice to put the HA on wired link, anywhere in
> the Internet, and relatively close (in terms of hopcount) to where the
> handover is about to take place.

In the context of this thread, Bob mentioned about the routing
performance, exactly saying user data packets' routing performance,
not saying handover latency mainly consisted of 1) movement detection
at IP level; 2) address configuration; and 3) location update (BU/BA)
to the home agent.

Cheers.

And not necessarily put it where eg
> akamai stuff sits.
>
> Alex
>
>> Bob
>>
>> --------------------------------------------------------------------
>> =A0IETF 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
> --------------------------------------------------------------------
>



--=20
IMARA Team, INRIA, France.
Jong-Hyouk Lee.

#email: jonghyouk (at) gmail (dot) com || jong-hyouk.lee (at) inria (dot) f=
r
#webpage: https://sites.google.com/site/hurryon/

From jared@puck.nether.net  Thu Mar 31 08:13:18 2011
Return-Path: <jared@puck.nether.net>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 220C83A69BE for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WdxBtSYkDgpo for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:13:17 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by core3.amsl.com (Postfix) with ESMTP id 257113A680E for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:13:16 -0700 (PDT)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.12.9) with ESMTP id p2VFEnTA067914 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 31 Mar 2011 11:14:50 -0400 (EDT) (envelope-from jared@puck.nether.net)
Subject: Re: Vehicle's VIN in IPv6.
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <4D94791F.1010709@gmail.com>
Date: Thu, 31 Mar 2011 11:14:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <584CBCD9-DDB5-46EE-ABB2-51B6BFDC9D04@puck.nether.net>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<AANLkTintFks2OmnfcnUKah8omAEHgiY8BzVhCxL=bD99@mail.gmail.com>	<4D94446C.40008@inria.fr> <575406.83799.qm@web111414.mail.gq1.yahoo.com> <4D94791F.1010709@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 31 Mar 2011 11:14:51 -0400 (EDT)
Cc: Behcet Sarikaya <behcetsarikaya@yahoo.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 15:13:18 -0000

On Mar 31, 2011, at 8:52 AM, Alexandru Petrescu wrote:

> hmm... sounds as there would be a VIN-specific link layer? (not ieee =
ethernet, not usb, not bluetooth)?  Which is that?

This is the same question I have.  What is the communications phy that =
will interface with the outside world?  I'm sure it's going to be =
something where there is an existing bit of hardware that requires a =
ieee ethernet/mac or other addressable interface.  seems like the VIN =
would be best put in a datagram transmitted over that phy.

- Jared=

From alexandru.petrescu@gmail.com  Thu Mar 31 08:35:34 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78FD83A694C for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.858
X-Spam-Level: 
X-Spam-Status: No, score=-3.858 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Nzf+USB3Hfw for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:35:33 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id DA4E63A6B33 for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:35:32 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2019403bwz.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:37:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xZ7A1wIsA6I3e3GJBYn5n2Ly7H3Oour7XhiHZf/A3vg=; b=F4hZdX4ir0yj2O2/u0v87jcp4KJ32M+P6cJsntp7BUX1isD5B5sYlEEeSlNeMD7XRW wdgAgooTjyZpO9eF0/JkCu6xnq1gXaEEuSNF6+FePgVa8kvvZpk865zdo06ozjFQbS0R IiA6dujUrpKrAI8eW4OYYPX7ahdGgRCNxNkwk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=fVERo5C/t0GB5mthOL+/eXd6ZkfHR6i0HogznuzdI3weA+pTK8xIL/RyP5DxbRY/dN a6zgSSnf5gNAZdo+OWAiKBjXBuDYrPSeqfoJPX+raJGEgbNE9kcA18BQbh8uF5gdYf4N dzWy6OIBKoTl0O1f2fH1MVeX0W8Hggh29KQUE=
Received: by 10.204.26.132 with SMTP id e4mr2571003bkc.142.1301585831806; Thu, 31 Mar 2011 08:37:11 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id w3sm839544bkt.5.2011.03.31.08.37.09 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 08:37:10 -0700 (PDT)
Message-ID: <4D949FA2.5070901@gmail.com>
Date: Thu, 31 Mar 2011 17:37:06 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Jong-Hyouk Lee <jonghyouk@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<4D944365.4020809@kit.edu>	<4D944505.3060407@gmail.com>	<E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>	<AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com>	<6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>	<4D949559.3090509@gmail.com> <AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com>
In-Reply-To: <AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 15:35:34 -0000

Le 31/03/2011 17:02, Jong-Hyouk Lee a 閏rit :
> Hi, Alex.
>
> Plz, see inline. I fully failed to understand your words.
>
> On Thu, Mar 31, 2011 at 4:53 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com>  wrote:
>> Le 31/03/2011 16:19, Bob Hinden a 閏rit :
>>>
>>> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>>>
>>>> On Thu, Mar 31, 2011 at 11:32, Bob
>>>> Hinden<bob.hinden@gmail.com> wrote:
>>>>>
>>>>> They could use a fixed car address and use mobile IPv6 with
>>>>> a provider based address.
>>>>
>>>> That would help.  A rendezvous point (e.g. home agent) always
>>>> helps to protect confidentiality. Plus a firewall to protect
>>>> the always-out-of-date vehicle software.   They can work out
>>>> how to do path optimization later.
>>>
>>> I agree.  If you put the "home agent" in the middle of the
>>> internet (for some value of middle), then path optimization
>>> probably isn't that important.
>>
>> Makes some sense.  This "middle" depends on latency; and core
>> network has an order of magnitude (sometimes 2) less than even the
>>  first hop to vehicle.
>
> In the context of ITS communication, how do you expect the movement
> of vehicles?

Right, mouvement of private vehicles is unpredictable.  Some common
sense may reduce the space to, say, mostly a continent.  And even some
vehicles like trains have very highly predictable trajectories.

Not only ITS should be considered, but also operators of public
transportation networks (if they're not already part of it).

> Then, how do you decide the location of home agent for reducing the
> routing performance for user data packets destined to hosts attached
>  to the router of a vehicle?

The direct seller of vehicle (concessionnaire, garage) may decide to
host HA relativley close (geo terms) to where the vehicle is owned,
suffices HA to be on wire instead of wireless, which is rather natural.
  The parts manufacturer too.  The transportation operator, etc.

The common wisdom of needing to host a webcache closer in order to
deliver data quicker to http clients assumes the http clients use wire
too (as the servers do).  The latency difference between pc's wire and
server's wire is much smaller than between server's wire and wireless.

>> That means that it may suffice to put the HA on wired link,
>> anywhere in the Internet, and relatively close (in terms of
>> hopcount) to where the handover is about to take place.
>
> In the context of this thread, Bob mentioned about the routing
> performance, exactly saying user data packets' routing performance,
> not saying handover latency mainly consisted of 1) movement
> detection at IP level; 2) address configuration; and 3) location
> update (BU/BA) to the home agent.

Right, I didn't mean handover performance.

Routing performance... hmm... I believe there is not much routing
performance gain when trying to bring HA as close as possible to the
handover place.

Alex
>
> Cheers.
>
> And not necessarily put it where eg
>> akamai stuff sits.
>>
>> Alex
>>
>>> Bob
>>>
>>> --------------------------------------------------------------------
>>>
>>>
>>>
>>>
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 jonghyouk@gmail.com  Thu Mar 31 08:59:20 2011
Return-Path: <jonghyouk@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 350FE3A6B10 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdBrjDiixsFY for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 08:59:19 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id C3A3F28C0DF for <ipv6@ietf.org>; Thu, 31 Mar 2011 08:59:18 -0700 (PDT)
Received: by wyb29 with SMTP id 29so2427500wyb.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 09:00:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=k08N8+eVvducaV5ldBq9ptgVXUyYTc9BL70qL2ZnaYk=; b=IGdvIQiMf3wNyUYwhU3PGsbbbF8nAKDxfCDlVdPAVofOJXbUebJ+o/Lu8+u5BKmME1 vTg7vPZrkhmB2k5BuJ8yUqVjMB1h+eaPdcHm4PAVLCeH3Es4uFjXhlkaudNxGzcfNFfm 2OTVADPTbF/AxmQ9kHTYBLEyGkGjdIn0odZ8c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=lhD/heE5LSNW3sAzMIP/ZymZ82PFmRbFAt5ZwiVqbDN0Mw4TVZktqyCoAToQYa9AMe OY3d1dYFv4tB4zcY9eubifiJWtmQUL89DxCHEgxyh+EFu8AbuWgu1E5h8v6zUKvyad2r t+Ciy7jaOgXUA09mdbo/4ZbYUWYykTwv5PUQI=
MIME-Version: 1.0
Received: by 10.227.39.66 with SMTP id f2mr2897606wbe.2.1301587257805; Thu, 31 Mar 2011 09:00:57 -0700 (PDT)
Received: by 10.227.152.201 with HTTP; Thu, 31 Mar 2011 09:00:57 -0700 (PDT)
In-Reply-To: <4D949FA2.5070901@gmail.com>
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow> <4D944365.4020809@kit.edu> <4D944505.3060407@gmail.com> <E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com> <AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com> <6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com> <4D949559.3090509@gmail.com> <AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com> <4D949FA2.5070901@gmail.com>
Date: Thu, 31 Mar 2011 18:00:57 +0200
Message-ID: <AANLkTikviCSzupW0L+fj6Zxh6gBVEiC6ZthJRShybfLX@mail.gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
From: Jong-Hyouk Lee <jonghyouk@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 15:59:20 -0000

Hi, Alex.

Please, come back to a person who I know. See inline.

On Thu, Mar 31, 2011 at 5:37 PM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
>
> Le 31/03/2011 17:02, Jong-Hyouk Lee a =E9crit :
>>
>> Hi, Alex.
>>
>> Plz, see inline. I fully failed to understand your words.
>>
>> On Thu, Mar 31, 2011 at 4:53 PM, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> =A0wrote:
>>>
>>> Le 31/03/2011 16:19, Bob Hinden a =E9crit :
>>>>
>>>> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>>>>
>>>>> On Thu, Mar 31, 2011 at 11:32, Bob
>>>>> Hinden<bob.hinden@gmail.com> wrote:
>>>>>>
>>>>>> They could use a fixed car address and use mobile IPv6 with
>>>>>> a provider based address.
>>>>>
>>>>> That would help. =A0A rendezvous point (e.g. home agent) always
>>>>> helps to protect confidentiality. Plus a firewall to protect
>>>>> the always-out-of-date vehicle software. =A0 They can work out
>>>>> how to do path optimization later.
>>>>
>>>> I agree. =A0If you put the "home agent" in the middle of the
>>>> internet (for some value of middle), then path optimization
>>>> probably isn't that important.
>>>
>>> Makes some sense. =A0This "middle" depends on latency; and core
>>> network has an order of magnitude (sometimes 2) less than even the
>>> =A0first hop to vehicle.
>>
>> In the context of ITS communication, how do you expect the movement
>> of vehicles?
>
> Right, mouvement of private vehicles is unpredictable. =A0Some common
> sense may reduce the space to, say, mostly a continent. =A0And even some
> vehicles like trains have very highly predictable trajectories.
>
> Not only ITS should be considered, but also operators of public
> transportation networks (if they're not already part of it).
>
>> Then, how do you decide the location of home agent for reducing the
>> routing performance for user data packets destined to hosts attached
>> =A0to the router of a vehicle?
>
> The direct seller of vehicle (concessionnaire, garage) may decide to
> host HA relativley close (geo terms) to where the vehicle is owned,
> suffices HA to be on wire instead of wireless, which is rather natural.
> =A0The parts manufacturer too. =A0The transportation operator, etc.

Ummm...let me explain a little thing about the use of home agent (HA)
in the context of ISO and ETSI. The HA is located at the central ITS
station that must be maintained by authorized organization, i.e.,
belonging to the government. Such private companies will not have
permissions to install the HA; might be possible for only private
company's client, but this is not the case we're talking here.

>
> The common wisdom of needing to host a webcache closer in order to
> deliver data quicker to http clients assumes the http clients use wire
> too (as the servers do). =A0The latency difference between pc's wire and
> server's wire is much smaller than between server's wire and wireless.

Come on. I don't really know why you bring this text here.

>
>>> That means that it may suffice to put the HA on wired link,
>>> anywhere in the Internet, and relatively close (in terms of
>>> hopcount) to where the handover is about to take place.
>>
>> In the context of this thread, Bob mentioned about the routing
>> performance, exactly saying user data packets' routing performance,
>> not saying handover latency mainly consisted of 1) movement
>> detection at IP level; 2) address configuration; and 3) location
>> update (BU/BA) to the home agent.
>
> Right, I didn't mean handover performance.
>
> Routing performance... hmm... I believe there is not much routing
> performance gain when trying to bring HA as close as possible to the
> handover place.
>
> Alex
>>
>> Cheers.
>>
>> And not necessarily put it where eg
>>>
>>> akamai stuff sits.
>>>
>>> Alex
>>>
>>>> Bob
>>>>
>>>> --------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
> 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
>>> --------------------------------------------------------------------
>>>
>>
>>>
>>>
>>>
>>
>>
>
>



--=20
IMARA Team, INRIA, France.
Jong-Hyouk Lee.

#email: jonghyouk (at) gmail (dot) com || jong-hyouk.lee (at) inria (dot) f=
r
#webpage: https://sites.google.com/site/hurryon/

From alexandru.petrescu@gmail.com  Thu Mar 31 13:13:32 2011
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E6C528C12B for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 13:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.818
X-Spam-Level: 
X-Spam-Status: No, score=-3.818 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76b54mupJ+FQ for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 13:13:31 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id CD38A28C12A for <ipv6@ietf.org>; Thu, 31 Mar 2011 13:13:30 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2222788bwz.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 13:15:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+4JeY0CRM0ve3VueJExknzi0jCuaLkRCoSTtgqDYJUY=; b=rDnaRPSWKnPzYxiccQKCEtdRqYwUYujEQqlHOFluGfMJmJuhAWjyowYkB/JIfi01bL /FUoAMTPgxuhH5Jiz1se3V+CMMp8Kr/roSNZok4s6U4fgPV/KPUF3YG6OWD6Ct6VSKe7 KmNDKQFWsINd3YR5oAJI1xOF1KoHhrp5h7xp4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=TN/ysR2pWvdSde0fcPJW+aqzba8hFp8+Uv7ArlJsu0FaX1HS+vR9s42qB0HumX6VKD xJi5kXPS2FrQvYhUG7ZXzLu+m1AOdciHDQMdI6kB6ykTM9ajPLSRxHdC2JpEdkWAgsNT qimMd6NBN1DyUXEbN/z4wyIREvF9LVxIzdLAs=
Received: by 10.204.74.7 with SMTP id s7mr409835bkj.57.1301602509800; Thu, 31 Mar 2011 13:15:09 -0700 (PDT)
Received: from [127.0.0.1] (dhcp-150a.meeting.ietf.org [130.129.21.10]) by mx.google.com with ESMTPS id l1sm969950bkl.13.2011.03.31.13.15.04 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 13:15:08 -0700 (PDT)
Message-ID: <4D94E0C3.9030400@gmail.com>
Date: Thu, 31 Mar 2011 22:14:59 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fr; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Jong-Hyouk Lee <jonghyouk@gmail.com>
Subject: Re: Vehicle's VIN in IPv6.
References: <5C4A2B87ED124653A9BDEDAC14D6F2C8@sparrow>	<4D944365.4020809@kit.edu>	<4D944505.3060407@gmail.com>	<E9DE74CB-03B0-4529-B6D1-BD875332C20F@gmail.com>	<AANLkTimmqkddMrTAzn0yZYKJ1mnSGAoOTqiiir92beE2@mail.gmail.com>	<6CEB6E26-AE20-450B-AD61-BE7B7029EFCF@gmail.com>	<4D949559.3090509@gmail.com>	<AANLkTinVqhU97_kvPJ4EUtNog-oKoehGdW9jqFHfCjdk@mail.gmail.com>	<4D949FA2.5070901@gmail.com> <AANLkTikviCSzupW0L+fj6Zxh6gBVEiC6ZthJRShybfLX@mail.gmail.com>
In-Reply-To: <AANLkTikviCSzupW0L+fj6Zxh6gBVEiC6ZthJRShybfLX@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, =?ISO-8859-1?Q?Radek_Wr=F3bel?= <radoslaw.wrobel@pwr.wroc.pl>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 20:13:32 -0000

Le 31/03/2011 18:00, Jong-Hyouk Lee a 閏rit :
> Hi, Alex.
>
> Please, come back to a person who I know. See inline.
>
> On Thu, Mar 31, 2011 at 5:37 PM, Alexandru Petrescu
> <alexandru.petrescu@gmail.com>  wrote:
>>
>> Le 31/03/2011 17:02, Jong-Hyouk Lee a 閏rit :
>>>
>>> Hi, Alex.
>>>
>>> Plz, see inline. I fully failed to understand your words.
>>>
>>> On Thu, Mar 31, 2011 at 4:53 PM, Alexandru Petrescu
>>> <alexandru.petrescu@gmail.com>    wrote:
>>>>
>>>> Le 31/03/2011 16:19, Bob Hinden a 閏rit :
>>>>>
>>>>> On Mar 31, 2011, at 1:15 PM, Scott Brim wrote:
>>>>>
>>>>>> On Thu, Mar 31, 2011 at 11:32, Bob
>>>>>> Hinden<bob.hinden@gmail.com>  wrote:
>>>>>>>
>>>>>>> They could use a fixed car address and use mobile IPv6
>>>>>>> with a provider based address.
>>>>>>
>>>>>> That would help.  A rendezvous point (e.g. home agent)
>>>>>> always helps to protect confidentiality. Plus a firewall to
>>>>>> protect the always-out-of-date vehicle software.   They can
>>>>>> work out how to do path optimization later.
>>>>>
>>>>> I agree.  If you put the "home agent" in the middle of the
>>>>> internet (for some value of middle), then path optimization
>>>>> probably isn't that important.
>>>>
>>>> Makes some sense.  This "middle" depends on latency; and core
>>>> network has an order of magnitude (sometimes 2) less than even
>>>>  the first hop to vehicle.
>>>
>>> In the context of ITS communication, how do you expect the
>>> movement of vehicles?
>>
>> Right, mouvement of private vehicles is unpredictable.  Some
>> common sense may reduce the space to, say, mostly a continent.  And
>> even some vehicles like trains have very highly predictable
>> trajectories.
>>
>> Not only ITS should be considered, but also operators of public
>> transportation networks (if they're not already part of it).
>>
>>> Then, how do you decide the location of home agent for reducing
>>> the routing performance for user data packets destined to hosts
>>> attached to the router of a vehicle?
>>
>> The direct seller of vehicle (concessionnaire, garage) may decide
>> to host HA relativley close (geo terms) to where the vehicle is
>> owned, suffices HA to be on wire instead of wireless, which is
>> rather natural. The parts manufacturer too.  The transportation
>> operator, etc.
>
> Ummm...let me explain a little thing about the use of home agent
> (HA) in the context of ISO and ETSI. The HA is located at the central
> ITS station that must be maintained by authorized organization,
> i.e., belonging to the government.

Hmm... yes that can be done.  Some governments are even Cert Auth, but
that does not prevent other private organizations to be CA.

> Such private companies will not have permissions to install the HA;
> might be possible for only private company's client, but this is not
>  the case we're talking here.

Ah I see, I agree.

But I am still curious to understand the lines of VIN-v6 proposal
before discarding it. In the process maybe I (or someone else) get a
chance to suggest some alternative... to satisfy some requirement,
some problem statement.

Alex

>> The common wisdom of needing to host a webcache closer in order to
>> deliver data quicker to http clients assumes the http clients use
>> wire too (as the servers do).  The latency difference between pc's
>>  wire and server's wire is much smaller than between server's wire
>>  and wireless.
>
> Come on. I don't really know why you bring this text here.
>
>>
>>>> That means that it may suffice to put the HA on wired link,
>>>> anywhere in the Internet, and relatively close (in terms of
>>>> hopcount) to where the handover is about to take place.
>>>
>>> In the context of this thread, Bob mentioned about the routing
>>> performance, exactly saying user data packets' routing
>>> performance, not saying handover latency mainly consisted of 1)
>>> movement detection at IP level; 2) address configuration; and 3)
>>>  location update (BU/BA) to the home agent.
>>
>> Right, I didn't mean handover performance.
>>
>> Routing performance... hmm... I believe there is not much routing
>> performance gain when trying to bring HA as close as possible to
>> the handover place.
>>
>> Alex
>>>
>>> Cheers.
>>>
>>> And not necessarily put it where eg
>>>>
>>>> akamai stuff sits.
>>>>
>>>> Alex
>>>>
>>>>> Bob
>>>>>
>>>>> --------------------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>
>>>>>
>>>>>
>>>>>
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 hesham@elevatemobile.com  Thu Mar 31 16:28:04 2011
Return-Path: <hesham@elevatemobile.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7423C28C141 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 16:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFkVIwEhB7dV for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 16:28:00 -0700 (PDT)
Received: from smtp-1.servers.netregistry.net (smtp.netregistry.net [202.124.241.204]) by core3.amsl.com (Postfix) with ESMTP id 0AFA828C10D for <ipv6@ietf.org>; Thu, 31 Mar 2011 16:27:59 -0700 (PDT)
Received: from [121.219.0.84] (helo=[10.0.0.11]) by smtp-1.servers.netregistry.net protocol: esmtpa (Exim 4.69 #1 (Debian)) id 1Q5RIn-0006bz-AA; Fri, 01 Apr 2011 10:29:22 +1100
User-Agent: Microsoft-MacOutlook/14.2.0.101115
Date: Fri, 01 Apr 2011 10:29:14 +1100
Subject: Re: Vehicle's VIN in IPv6.
From: Hesham Soliman <hesham@elevatemobile.com>
To: George Michaelson <ggm+ietf@apnic.net>, Scott Brim <scott.brim@gmail.com>
Message-ID: <C9BB58E5.1072E%hesham@elevatemobile.com>
Thread-Topic: Vehicle's VIN in IPv6.
In-Reply-To: <7BAD13E9-6D29-4422-8361-7D3461D0BA91@apnic.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-User: hesham@elevatemobile.com
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 Mar 2011 23:28:04 -0000

>
>
>
>I don't think "go away" is the right answer. I think "your model has
>flaws" is closer.
>
>The key message is that if they apply for patents in it (BMW) they
>clearly see dollar-signs and its very hard to trump money.

=> I don't think it's as organised as you might think. People apply for
patents all the time for a wide range of reasons and they don't
necessarily reflect dollar signs.

We've seen people from ITU suggest we embed IPv6 addresses in phone
numbers ....etc before. The same type of education about
locator/application identifier separation is needed here.

Hesham

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



From brian.e.carpenter@gmail.com  Thu Mar 31 22:37:41 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4D283A69B9 for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 22:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.629
X-Spam-Level: 
X-Spam-Status: No, score=-103.629 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXlm8oMqSDXX for <ipv6@core3.amsl.com>; Thu, 31 Mar 2011 22:37:39 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 6AB0C3A67F1 for <ipv6@ietf.org>; Thu, 31 Mar 2011 22:37:39 -0700 (PDT)
Received: by bwz13 with SMTP id 13so2462572bwz.31 for <ipv6@ietf.org>; Thu, 31 Mar 2011 22:39:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type:content-transfer-encoding; bh=OMT8S3eHlmzjDChx6/whSmTeNTr0BjopEA+Xi1/ccNE=; b=SDf8Rj9FRBhn3HaRTuFQw8tBx5Ly4r+w76iNeVLz6wiU3WJW58NPc2kKoh+h2x/N7k IGAIlFrPGdEd3rGHoiODcInlt4P0o05zgCKUBpyzS3tg8FQnt8amRa6NDw2p4omGXcRf y71xeSynRCRnaER3EAIMqCEKYfs0V6suH1WH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; b=PRadHoYUxkj2o3HKha+MOVDofeAvwMDgeOddIVhg/dWDRszY/x2rFm1OpxYXUuEHyO cTFfpoIbo8XYJBZ2Ir0v8Z7lgXsjE3jU4/w2buFkzTJGcR7IGG/j+D5SJI0f/gKv8cIJ LUF6Uw0CUnu0MbBUyXm/nkft6kpwpk0ymH8cw=
Received: by 10.204.25.20 with SMTP id x20mr3265428bkb.112.1301636358324; Thu, 31 Mar 2011 22:39:18 -0700 (PDT)
Received: from [130.129.69.166] (dhcp-45a6.meeting.ietf.org [130.129.69.166]) by mx.google.com with ESMTPS id w3sm1143674bkt.5.2011.03.31.22.39.17 (version=SSLv3 cipher=OTHER); Thu, 31 Mar 2011 22:39:17 -0700 (PDT)
Message-ID: <4D956500.3060001@gmail.com>
Date: Fri, 01 Apr 2011 18:39:12 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Process violation apology
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Apr 2011 05:37:42 -0000

I do apologise. The attached was inadvertently published without
WG Last Call or IETF Last Call. There was some urgency to ensure
that it can be deployed before World IPv6 Day.

    Brian

-------- Original Message --------
Subject: RFC 6214 on Adaptation of RFC 1149 for IPv6
Date: Thu, 31 Mar 2011 15:56:56 -0700 (PDT)
From: rfc-editor@rfc-editor.org
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
CC: rfc-editor@rfc-editor.org


A new Request for Comments is now available in online RFC libraries.


        RFC 6214

        Title:      Adaptation of RFC 1149 for
                    IPv6
        Author:     B. Carpenter, R. Hinden
        Status:     Informational
        Stream:     Independent
        Date:       1 April 2011
        Mailbox:    brian.e.carpenter@gmail.com,
                    bob.hinden@gmail.com
        Pages:      7
        Characters: 15073
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-carpenter-6man-adapt-rfc1149-00.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6214.txt

This document specifies a method for transmission of IPv6 datagrams
over the same medium as specified for IPv4 datagrams in RFC 1149.
This document is not an Internet Standards Track specification; it is
published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce


