
From iesg-secretary@ietf.org  Wed May  1 09:20:13 2013
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D0A21F9A64; Wed,  1 May 2013 09:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HY7CeeJgMB54; Wed,  1 May 2013 09:20:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 70ACA21F9A51; Wed,  1 May 2013 09:20:12 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-addr-select-opt-10.txt> (Distributing Address Selection Policy using DHCPv6) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p4
Sender: <iesg-secretary@ietf.org>
Message-ID: <20130501162012.574.45050.idtracker@ietfa.amsl.com>
Date: Wed, 01 May 2013 09:20:12 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 16:20:13 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'Distributing Address Selection Policy using DHCPv6'
  <draft-ietf-6man-addr-select-opt-10.txt> as Proposed Standard

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

Abstract


   RFC 6724 defines default address selection mechanisms for IPv6 that
   allow nodes to select an appropriate address when faced with multiple
   source and/or destination addresses to choose between.  The RFC 6724
   allowed for the future definition of methods to administratively
   configure the address selection policy information.  This document
   defines a new DHCPv6 option for such configuration, allowing a site
   administrator to distribute address selection policy overriding the
   default address selection parameters and policy table, and thus
   control the address selection behavior of nodes in their site.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt/ballot/


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



From zhou.sujing@zte.com.cn  Thu May  2 00:54:48 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9CF21F992E; Thu,  2 May 2013 00:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.245
X-Spam-Level: 
X-Spam-Status: No, score=-100.245 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, MIME_BASE64_TEXT=1.753, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpb-AA3usz4W; Thu,  2 May 2013 00:54:44 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 268C521F991F; Thu,  2 May 2013 00:54:43 -0700 (PDT)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 28C39129216D; Thu,  2 May 2013 15:54:16 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r427s9AT033241; Thu, 2 May 2013 15:54:11 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <517C9B07.8080807@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFBDABAACC.4BD49D72-ON48257B5F.002A705A-48257B5F.002B7DBA@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Thu, 2 May 2013 15:54:00 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-02 15:53:54, Serialize complete at 2013-05-02 15:53:54
Content-Type: multipart/alternative; boundary="=_alternative 002B7DB848257B5F_="
X-MAIL: mse02.zte.com.cn r427s9AT033241
Cc: ipv6-bounces@ietf.org, Christian Huitema <huitema@microsoft.com>, Alissa Cooper <acooper@cdt.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 07:54:48 -0000

This is a multipart message in MIME format.
--=_alternative 002B7DB848257B5F_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

PiANCj4gDQo+ID4gSG93ZXZlciwgaW4gdGhlIGNhc2Ugb2YNCj4gPiByb2FtaW5nIHRoZSBmZWF0
dXJlIGlzIGhpZ2hseSBkZWJhdGFibGUuIElmIGEgaG9zdCB2aXNpdHMgdGhlIHNhbWUNCj4gPiBu
ZXR3b3JrIG11bHRpcGxlIHRpbWVzLCBzaG91bGQgaXQgYWx3YXlzIHJldXNlIHRoZSBzYW1lIElE
LCBvciBzaG91bGQNCj4gPiBpdCBnZXQgYSBuZXcgaWRlbnRpZmllciBlYWNoIHRpbWU/IEl0IGlz
IHZlcnkgZWFzeSB0byBhcmd1ZSB0aGF0DQo+ID4gImRpZmZlcmVudCBlYWNoIHRpbWUiIGhhcyBi
ZXR0ZXIgcHJpdmFjeSBwcm9wZXJ0aWVzLg0KPiANCj4gQWdyZWVkLiBGb3IgaW5zdGFuY2UsIGRy
YWZ0LWlldGYtNm1hbi1zdGFibGUtcHJpdmFjeS1hZGRyZXNzZXMtMDYudHh0IGlzDQo+IG5vdCBh
IHJlcGxhY2VtZW50IGZvciBSRkM0OTQxLiBJZiB5b3UncmUgYSByb2FtaW5nIG5vZGUsIHlvdSBw
cm9iYWJseQ0KPiB3YW50IFJGQzQ5NDEgZW5hYmxlZCAoaW4gYWRkaXRpb24gdG8gaGF2aW5nDQo+
IGRyYWZ0LWlldGYtNm1hbi1zdGFibGUtcHJpdmFjeS1hZGRyZXNzZXMtMDYudHh0IGVuYWJsZWQp
Lg0KDQpIYXZlIHlvdSBjb25zaWRlcmVkIGFkZGluZyBhIGRhdGUvdGltZSBwYXJhbWV0ZXIgaW4g
Z2VuZXJhdGluZyB0aGUgbmV3IA0KUklEPw0KZS5nLiBSSUQgoa89IEYoUHJlZml4LCBJbnRlcmZh
Y2VfSW5kZXgsIE5ldHdvcmtfSUQsIERBRF9Db3VudGVyLERhdGUvdGltZSwNCiAgICAgICBzZWNy
ZXRfa2V5KQ0KVGhhdCB3aWxsIHJlc3VsdCBpbiBkaWZmZXJlbnQgSUlEcyBmcm9tIHRpbWUgdG8g
dGltZSwgYW5kIHRoZSB0aW1lIGNvdWxkIA0KYmUgY2hvc2VuIA0KYSB3aWRlIHJhbmdlLCBlLmcu
LCB0aGUgeWVhciwgdGhlIG1vbnRoLCBzbyB0aGF0IHdoZW4gYSBub2RlIG1vdmUgd2l0aGluIGEg
DQpjZXJ0YWluIHRpbWUsIA0KdGhlIHJ1bm5pbmcgc2Vzc2lvbnMgd2lsbCBub3QgYnJlYWsgYmVj
YXVzZSBvZiB0aW1lIGNoYW5nZS4gDQpGb3IgY29udmVuaWVuY3ksIHRoZSB0aW1lIHBhcmFtZXRl
ciBjb3VsZCBiZSBkZWNpZGVkIG9wdGlvbmFsLg0KDQpPZiBjb3Vyc2UsIGNoYW5naW5nIHNlY3Jl
dCBrZXkgd2lsbCBhbHNvIGhhdmUgYSBzaW1pbGFyIGVmZmVjdCwgYXQgdGhlIA0Kb3duZXIncyB3
aWxsLA0KYnV0IGFkZGluZyBhIG9wdGlvbmFsIHRpbWUgcGFyYW1ldGVyIHdpbGwgYWRkIG1vcmUg
ZmxleGliaWxpdHkuDQoNCg0KDQo+IA0KPiBDaGVlcnMsDQo+IC0tIA0KPiBGZXJuYW5kbyBHb250
DQo+IFNJNiBOZXR3b3Jrcw0KPiBlLW1haWw6IGZnb250QHNpNm5ldHdvcmtzLmNvbQ0KPiBQR1Ag
RmluZ2VycHJpbnQ6IDY2NjYgMzFDNiBENDg0IDYzQjIgOEZCMSBFM0M0IEFFMjUgMEQ1NSAxRDRF
IDc0OTINCj4gDQo+IA0KPiANCj4gDQo+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IElFVEYgSVB2NiB3b3JraW5n
IGdyb3VwIG1haWxpbmcgbGlzdA0KPiBpcHY2QGlldGYub3JnDQo+IEFkbWluaXN0cmF0aXZlIFJl
cXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYNCj4gLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCg0K
--=_alternative 002B7DB848257B5F_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj48YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0K
Jmd0OyAmZ3Q7IEhvd2V2ZXIsIGluIHRoZSBjYXNlIG9mPGJyPg0KJmd0OyAmZ3Q7IHJvYW1pbmcg
dGhlIGZlYXR1cmUgaXMgaGlnaGx5IGRlYmF0YWJsZS4gSWYgYSBob3N0IHZpc2l0cyB0aGUNCnNh
bWU8YnI+DQomZ3Q7ICZndDsgbmV0d29yayBtdWx0aXBsZSB0aW1lcywgc2hvdWxkIGl0IGFsd2F5
cyByZXVzZSB0aGUgc2FtZSBJRCwgb3INCnNob3VsZDxicj4NCiZndDsgJmd0OyBpdCBnZXQgYSBu
ZXcgaWRlbnRpZmllciBlYWNoIHRpbWU/IEl0IGlzIHZlcnkgZWFzeSB0byBhcmd1ZSB0aGF0PGJy
Pg0KJmd0OyAmZ3Q7ICZxdW90O2RpZmZlcmVudCBlYWNoIHRpbWUmcXVvdDsgaGFzIGJldHRlciBw
cml2YWN5IHByb3BlcnRpZXMuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEFncmVlZC4gRm9yIGluc3Rh
bmNlLCBkcmFmdC1pZXRmLTZtYW4tc3RhYmxlLXByaXZhY3ktYWRkcmVzc2VzLTA2LnR4dA0KaXM8
YnI+DQomZ3Q7IG5vdCBhIHJlcGxhY2VtZW50IGZvciBSRkM0OTQxLiBJZiB5b3UncmUgYSByb2Ft
aW5nIG5vZGUsIHlvdSBwcm9iYWJseTxicj4NCiZndDsgd2FudCBSRkM0OTQxIGVuYWJsZWQgKGlu
IGFkZGl0aW9uIHRvIGhhdmluZzxicj4NCiZndDsgZHJhZnQtaWV0Zi02bWFuLXN0YWJsZS1wcml2
YWN5LWFkZHJlc3Nlcy0wNi50eHQgZW5hYmxlZCkuPGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+PHR0
Pjxmb250IHNpemU9Mj5IYXZlIHlvdSBjb25zaWRlcmVkIGFkZGluZyBhIGRhdGUvdGltZSBwYXJh
bWV0ZXIgaW4NCmdlbmVyYXRpbmcgdGhlIG5ldyBSSUQ/PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxm
b250IHNpemU9Mz5lLmcuIFJJRCChrz0gRihQcmVmaXgsIEludGVyZmFjZV9JbmRleCwgTmV0d29y
a19JRCwNCkRBRF9Db3VudGVyLERhdGUvdGltZSw8YnI+DQogJm5ic3A7ICZuYnNwOyAmbmJzcDsg
c2VjcmV0X2tleSk8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0zPlRoYXQgd2lsbCBy
ZXN1bHQgaW4gZGlmZmVyZW50IElJRHMgZnJvbSB0aW1lIHRvIHRpbWUsDQphbmQgdGhlIHRpbWUg
Y291bGQgYmUgY2hvc2VuIDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTM+YSB3aWRl
IHJhbmdlLCBlLmcuLCB0aGUgeWVhciwgdGhlIG1vbnRoLCBzbyB0aGF0IHdoZW4NCmEgbm9kZSBt
b3ZlIHdpdGhpbiBhIGNlcnRhaW4gdGltZSwgPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNp
emU9Mz50aGUgcnVubmluZyBzZXNzaW9ucyB3aWxsIG5vdCBicmVhayBiZWNhdXNlIG9mIHRpbWUN
CmNoYW5nZS4gPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mz5Gb3IgY29udmVuaWVu
Y3ksIHRoZSB0aW1lIHBhcmFtZXRlciBjb3VsZCBiZSBkZWNpZGVkDQpvcHRpb25hbC48L2ZvbnQ+
PC90dD4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0zPk9mIGNvdXJzZSwgY2hhbmdpbmcgc2Vj
cmV0IGtleSB3aWxsIGFsc28gaGF2ZSBhIHNpbWlsYXINCmVmZmVjdCwgYXQgdGhlIG93bmVyJ3Mg
d2lsbCw8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0zPmJ1dCBhZGRpbmcgYSBvcHRp
b25hbCB0aW1lIHBhcmFtZXRlciB3aWxsIGFkZCBtb3JlDQpmbGV4aWJpbGl0eS48YnI+DQo8YnI+
DQo8L2ZvbnQ+PC90dD4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0
OyBDaGVlcnMsPGJyPg0KJmd0OyAtLSA8YnI+DQomZ3Q7IEZlcm5hbmRvIEdvbnQ8YnI+DQomZ3Q7
IFNJNiBOZXR3b3Jrczxicj4NCiZndDsgZS1tYWlsOiBmZ29udEBzaTZuZXR3b3Jrcy5jb208YnI+
DQomZ3Q7IFBHUCBGaW5nZXJwcmludDogNjY2NiAzMUM2IEQ0ODQgNjNCMiA4RkIxIEUzQzQgQUUy
NSAwRDU1IDFENEUgNzQ5Mjxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgPGJyPg0KJmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDsgSUVURiBJUHY2IHdvcmtpbmcgZ3Jv
dXAgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyBpcHY2QGlldGYub3JnPGJyPg0KJmd0OyBBZG1pbmlz
dHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
cHY2PGJyPg0KJmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCjwvZm9udD48L3R0Pg0K
--=_alternative 002B7DB848257B5F_=--

From zhou.sujing@zte.com.cn  Thu May  2 01:15:12 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6660121F8539 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 01:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.998
X-Spam-Level: 
X-Spam-Status: No, score=-101.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wgza7Z9Uit0u for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 01:15:06 -0700 (PDT)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id BD4D021F9934 for <ipv6@ietf.org>; Thu,  2 May 2013 01:15:04 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 88D27751BC for <ipv6@ietf.org>; Thu,  2 May 2013 16:14:32 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 2E1FB72D808; Thu,  2 May 2013 16:14:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r428EbHi046744; Thu, 2 May 2013 16:14:37 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
To: fgont@si6networks.com, huitema@microsoft.com, ipv6@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard 
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF51A0AB95.97793702-ON48257B5F.002C87CA-48257B5F.002D5C5C@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Thu, 2 May 2013 16:14:25 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-02 16:14:19, Serialize complete at 2013-05-02 16:14:19
Content-Type: multipart/alternative; boundary="=_alternative 002D5C5A48257B5F_="
X-MAIL: mse01.zte.com.cn r428EbHi046744
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 08:15:13 -0000

This is a multipart message in MIME format.
--=_alternative 002D5C5A48257B5F_=
Content-Type: text/plain; charset="US-ASCII"

>> However, in the case of
>> roaming the feature is highly debatable. If a host visits the same
>> network multiple times, should it always reuse the same ID, or should
>> it get a new identifier each time? It is very easy to argue that
>> "different each time" has better privacy properties.

>Agreed. For instance, draft-ietf-6man-stable-privacy-addresses-06.txt is
>not a replacement for RFC4941. If you're a roaming node, you probably
>want RFC4941 enabled (in addition to having
>draft-ietf-6man-stable-privacy-addresses-06.txt enabled).

Have you ever considered add a date/time (optional ) parameter  in 
generation of the new RID,
for example:
 RID = F(Prefix, Interface_Index, Network_ID, DAD_Counter,Date/Time, 
secret_key),
thus will result in different IID each different year, each different 
month, or even 
different day.

Of course, the IID owner can choose to change secret_key  to obtain 
different IID,
but with an addition of date/time option, it is more flexible. 


--=_alternative 002D5C5A48257B5F_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=3><br>
&gt;&gt; However, in the case of<br>
&gt;&gt; roaming the feature is highly debatable. If a host visits the
same<br>
&gt;&gt; network multiple times, should it always reuse the same ID, or
should<br>
&gt;&gt; it get a new identifier each time? It is very easy to argue that<br>
&gt;&gt; &quot;different each time&quot; has better privacy properties.<br>
<br>
&gt;Agreed. For instance, draft-ietf-6man-stable-privacy-addresses-06.txt
is<br>
&gt;not a replacement for RFC4941. If you're a roaming node, you probably<br>
&gt;want RFC4941 enabled (in addition to having<br>
&gt;draft-ietf-6man-stable-privacy-addresses-06.txt enabled).<br>
<br>
Have you ever considered add a date/time (optional ) parameter &nbsp;in
generation of the new RID,</font></tt>
<br><tt><font size=3>for example:</font></tt>
<br><tt><font size=3>&nbsp;RID = F(Prefix, Interface_Index, Network_ID,
DAD_Counter,</font></tt><tt><font size=3 color=red>Date/Time</font></tt><tt><font size=3>,
secret_key),</font></tt>
<br><tt><font size=3>thus will result in different IID each different year,
each different month, or even </font></tt>
<br><tt><font size=3>different day.</font></tt>
<br>
<br><tt><font size=3>Of course, the IID owner can choose to change secret_key
&nbsp;to obtain different IID,</font></tt>
<br><tt><font size=3>but with an addition of date/time option, it is more
flexible. <br>
<br>
</font></tt>
--=_alternative 002D5C5A48257B5F_=--

From fgont@si6networks.com  Thu May  2 06:43:39 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC5221F850F for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 06:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.266
X-Spam-Level: 
X-Spam-Status: No, score=-2.266 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, J_CHICKENPOX_16=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mrQ74rmwK8mn for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 06:43:39 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 380D821F8630 for <ipv6@ietf.org>; Thu,  2 May 2013 06:43:36 -0700 (PDT)
Received: from [186.134.26.236] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UXtmu-0007yM-7m; Thu, 02 May 2013 15:43:08 +0200
Message-ID: <518229CC.6020300@si6networks.com>
Date: Thu, 02 May 2013 05:54:36 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Sujing Zhou <zhou.sujing@zte.com.cn>
Subject: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
References: <OF51A0AB95.97793702-ON48257B5F.002C87CA-48257B5F.002D5C5C@zte.com.cn>
In-Reply-To: <OF51A0AB95.97793702-ON48257B5F.002C87CA-48257B5F.002D5C5C@zte.com.cn>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: huitema@microsoft.com, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 13:43:39 -0000

Hi, Sujing,

On 05/02/2013 05:14 AM, Sujing Zhou wrote:
> 
> Have you ever considered add a date/time (optional ) parameter  in
> generation of the new RID,
> for example:
>  RID = F(Prefix, Interface_Index, Network_ID, DAD_Counter,Date/Time,
> secret_key),
> thus will result in different IID each different year, each different
> month, or even
> different day.
> 
> Of course, the IID owner can choose to change secret_key  to obtain
> different IID,
> but with an addition of date/time option, it is more flexible.

Not really. The addresses are meant to be constant. And if you want to
change them, it's better to update the secret key (updating the key is
usually good, and you get the address change you expected as a side effect).

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





From ietf@rozanak.com  Thu May  2 10:25:46 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77B5621F90B1 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 10:25:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZW1Pw4b6vCXc for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 10:25:40 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 7D8A821F8FB6 for <ipv6@ietf.org>; Thu,  2 May 2013 10:25:40 -0700 (PDT)
Received: from kopoli (e179165239.adsl.alicedsl.de [85.179.165.239]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M0Q2H-1UJsDW33SH-00uzF2; Thu, 02 May 2013 13:25:37 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Fernando Gont'" <fgont@si6networks.com>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0C0656CF@tk5ex14mbxc272.redmond.corp.microsoft.com>	<517C9B07.8080807@si6networks.com>	<000301ce43f1$d449f8c0$7cddea40$@rozanak.com>	<000001ce4425$02082510$06186f30$@rozanak.com>	<517D7FFB.9070406@gmail.com>	<000901ce444c$ed75b2c0$c8611840$@rozanak.com>	<1367210846.64716.YahooMailNeo@web142503.mail.bf1.yahoo.com>	<000301ce44e5$1f4e5570$5deb0050$@rozanak.com>	<517ED03E.1090503@si6networks.com>	<000001ce451f$0363add0$0a2b0970$@rozanak.com> <20130429232737.GB10527@simplex.0x539.de> <000301ce45b8$ca16bd70$5e443850$@rozanak.com> <518004E8.9020604@si6networks.com>
In-Reply-To: <518004E8.9020604@si6networks.com>
Subject: RE: Last Call:	<draft-ietf-6man-stable-privacy-addresses-06.txt> (A	method for Generating Stable Privacy-Enhanced Addresses with	IPv6	Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
Date: Thu, 2 May 2013 19:25:25 +0200
Message-ID: <002101ce475a$0e0e73e0$2a2b5ba0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKcLtBe+C62qWLf2QteTIYCeGpuyAG1LFbVATDHCwECnWN6sQFvOP5IAWMsaG4B2Dg5DgMPoITyAnZM1FcCdsW8RwKL8DVjA3ZVyEAA+0TlTpaMh1Vw
Content-Language: en-us
X-Provags-ID: V02:K0:mVh/Xc/MTpxDoSCPtJF5GeXYa/ibUxWGO/x5WcWUSAZ LlMAM5EDGJMwoEel5gtBXIaOVq7mPxnu0mcdrIC+BJG9OhxRe9 XlsWNYFMWLuV/nYZxTKBIW+Igyols9kspcvCYUYWej24EyFrKe rKcptCC+kUxtMqQMjXJqNMdpKFZgAq2Ntmj9svuagA4E7AWDoT GuNMm46qoAWKhS9NRTMGxSaK1boNJo6SdaimLCPsIDmRBjzD4z H8mIdH+8qu9jNmUTQUVMD2ey2vDrbn8aEqQ6qTtnRLnnyHztMO 89FghGaujNzs1b1E9+NzHQVOYLV0c8oEDws5ZeL6adrJpubtcR 8TFhzPce15h5X9jjzKJk=
Cc: 'Christian Huitema' <huitema@microsoft.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 17:25:46 -0000

>Privacy is handled in the same way as security. Perfect privacy (as with
perfect security) doesn't exist... and you usually must decide when putting
even more effort on it doesn't make any more sense.

My point is that this is not true. Let's use a real life example. Suppose
that someone knows the address of some place. Would it behoove him to do
something bad against that place not really knowing what it is used for?
No, it wouldn't, not really. But what if this unsigned building was actually
a bank and the person in question is a bank robber? Then the plot thickens
and the bank robber's interest is piqued. YES. The borders of privacy are
different that those of security. If I only know the IP address of a node
and nothing more, there is no real incentive to harm the privacy of this
node. But when is this different? The answer would be when I could associate
information obtained about this node with its IP address. This information
could be obtained from the upper layers during the time this node has the
same IP address. Now it makes sense.

Your definition for privacy is just bound to layer 3. I refer to this
definition as pertaining partly to security but not privacy because you do
not want to leak patterns about this IP address. So what can happen if there
is a leak? What will I be able to obtain solely from the pattern of this IP
address? Will I be able to inflict damage to either privacy or security or
both? My definition of privacy has to do with how IP layer  is involved in
allowing for the gathering of information about the node in order to do harm
to its privacy. That is why, in my case, I feel that it is important to
change the IID within the same network if I make the assumption  that  by
staying in that network for a time period longer that x, without the router
prefix changing, I will be vulnerable to compromise.

>THis approach mitigate a number of privacy issues that arise from using
traditional slaac addresses. In many cases, mitigating those is "good
enough".

 I am not talking about the native SLAAC that generates the IID based on the
MAC. I am talking about the so called solution for privacy, RFC 4941. The
problem I can see with this RFC is that the lifetime of the IP address plays
the key role. I tested a windows machine with different prefixes and I did
not see any association of the IID with the MAC. Please explain where this
association is? I will give you a real example from my test
The MAC address is : 00:0c:29:fa:38:32
The IID generated in this windows machine is : 3007:efb7:125a:5c0

Several times I have suggested  that you show this in your draft  in order
to solve the problem of RFC 4941. But if you say this is just a new approach
for IID generation and my purpose is not privacy, then why you are talking
about privacy in your document while you cannot really provide the users
with the privacy they need?


>It does the following:
>* prevents leaking address patterns
>* prevents trivial host-tracking across networks.

 They can still follow you via the information they obtained when you joined
the first network and spent a long time there. So, it does not  prove to be
of much help.


>If your concern is the name, let's call this "Fernando's addresses" :-) or
whatever -- the meat is in the mechanism, rather than the title.

 First, it is not just the title. It is also your repeated reference to
privacy in several places in your document. Second, the title  should show
the purpose of the draft and not mislead readers.


 >Not sure what "conditions" you're referring to. Could you please
elaborate?

 The condition is related to the time you will remain using the same IID. If
it is longer than x, where x depends on many factors such as how important
the information of the users in this network is, how long it could  take an
attacker gather information about each individual users in this network, and
so on.


>This scheme results in addresses that have IIDs that **change across
networks**. --That's a big different, isn't it?

 What if my node is to move to and from  x different networks? If I generate
the same IID as well, then I will be a good victim for the attacker.
 
>Why would you expect a *prefix* to change, if your node does not move, when
an *address* is supposed to be topologically-dependent??

 Because privacy has to do with my information and not my IP address. I am
not talking about security where the attacker knows my IP  address which
enables him to do certain attacks against me or my network. I am talking
about the information that might leak during the time I am using the same IP
address.


>No matter how short-lived you make addresses, this will still be the case.
FOr instance, with current tools and bandwidths, you do not need a node to
be connected for more than a few seconds to have a >penetration testing tool
attempt what you refer to as "dirty deeds".
 
I think that you are confusing privacy with security.

>How many times do I need to repeat that RFC4941 addresses are generated
**in addition** to traditional slaac addresses?

 What it uses as a global address is a temporary one which is not based on
traditional SLAAC or it tries to randomize the IID. 

>Because while you're still in that network, some of the protocols you
employ may need a stable address... and because you may not want your e.g.
ssh sessions to break every X minutes.

What I know is that you cannot start a new session with your old or expired
IP address. But you can keep your current session with your old IP address
(see section 3 RFC 4941). Did you really try to see if the current session
is cut when using the current services? I have never experienced this. If
you or others have ever experienced this, then this is a bad interpretation
of RFC 4941 or a bad implementation.
 Now, when you move from one network to another, where the prefix changes
completely and you have a new IP address, do you still keep the same session
with your node? I do not think so, otherwise you should use Mobile IPv6
which is the solution here for mobility in IPv6. If your concern is this,
then why don't you use mobile ipv6? In this protocol, when a completely new
IP address is generated, it still maintains my session along with my old
nodes. So now, what is the reason for having stable addresses when there is
another solution for mobility in IPv6?

 >FWIW, I'm writing this email on a laptop, which is my mobile node. It
tends to stay cnnected for a few hours at home, then for a few hours at my
office, then for a few hours at some relative's home I'm >visiting, etc.

 I have already answered this. The solution is  the use mobile IPv6 and not
stable addresses.

 >Certainly not obvious/possible by just looking at the IPv6 address. -- and
if you don't think so, please explain your attack vector.

 This is what I am trying to tell you. The association of IP addresses to
the information obtained from other layers is important and might put
privacy at risk and not just hiding the "pattern" of your network. It has
more to do with partial security than privacy.

Thanks,
Hosnieh
 





From ietf@rozanak.com  Thu May  2 12:35:24 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACBC21F8FF3 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 12:35:24 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NbtaTQ3pT2Ak for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 12:35:18 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id E0CCE21F8FFC for <ipv6@ietf.org>; Thu,  2 May 2013 12:35:17 -0700 (PDT)
Received: from kopoli (e179165239.adsl.alicedsl.de [85.179.165.239]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MYfGM-1V2FZC1R0E-00VNnG; Thu, 02 May 2013 15:35:15 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
Subject: Solutions to the problem with RFC 4941
Date: Thu, 2 May 2013 21:35:06 +0200
Message-ID: <002601ce476c$297cae00$7c760a00$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01CE477C.ED099CB0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5Ha2dKn7zD6eIyS36uUkcAunbCuQ==
Content-Language: en-us
X-Provags-ID: V02:K0:p1ZXfTKUoifnS/B0eDLCwi96noHpOk1gvSGKF3KFMib Z6xl1vevHNchs5Fr0D1G6GDNphvR9o7zmxGPcCl5Of40Y4TlAh fB6gFGNXpY0zZ2zw4Bf1khoqcbc7UubbmPoqG+ezTePHfl9Kv1 GUvJPL35fwpM/92GHLZRv4Gg55wKoR0eFNIcl/7Adm8NdKsiCG vdjcUw5VDSeFbXp7W6Ir83xyk7KiPnYj9+ZEpGQ6Hsn/WpjJ26 17v+GbUEYQ8BdHYjq9Q6SStuAbVoD4J+YTh2anUzF2WZ1YwXi5 hIhVcNaXKgn5k7J5tw8hx0+IaEMCnP7YqRJwRMgAtfObvzBOFt yAQ6+kBI0RDLz+bzmLOA=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 19:35:24 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0027_01CE477C.ED099CB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Dear All,

 

Since Fernando's proposal is not going to solve the current problem with RFC
4941, I have suggested to him, on several occasions, that he resolve this
problem so that the node's privacy will be better protected but he ignored
this suggestion and claiming that his purpose is different. This is the main
reason that today I wrote an RFC draft which I will submit  to the IETF
repository. This draft does not overlap Fernando's proposal  it is related
to the problems with this RFC (RFC 4941) which he doesn't feel the need to
address. The problems that I address here concern the fact that the node
should also change its IID when it receives different router prefixes.

 

In the experimental results, Windows machine that implemented privacy
extension RFC, generates different IIDs by rebooting .But when it receives a
different prefix without a reboot, then, on the first two occasions that the
new  prefixes received, the node was generated a new IID, but not for other
new prefix generations. Also, as you can see, the temporary addresses have
the same IID. This means that there is a need to change section 8 of this
RFC

   6.  The node is now allowed to generate different interface

      identifiers for different prefixes, if it so desires.

 

Where a different IID should be generated when a different prefix is
received.  I called it "RA-based privacy extension for SLAAC".

   Physical Address. . . . . . . . . : 00-0C-29-FA-38-32

 

   IPv6 Address. . . . . . . . . . . :
2000:abc:ab:0:3003:bfe7:125a:5c0(Preferre

d)

   IPv6 Address. . . . . . . . . . . :
2000:abc:bad:bad:3003:bfe7:125a:5c0(Prefe

rred)

   Temporary IPv6 Address. . . . . . :
2000:abc:ab:0:5d60:2136:554:188b(Preferre

d)

   Temporary IPv6 Address. . . . . . :
2000:abc:bad:bad:5d60:2136:554:188b(Prefe

rred)

   Temporary IPv6 Address. . . . . . :
2000:bad:bad:bad:5d60:2136:554:188b(Prefe

rred)

 

Lifetime of the addresses as long as the computer is on

Addr Type  DAD State   Valid Life Pref. Life Address

---------  ----------- ---------- ---------- ------------------------

Public     Preferred   3314d21m1s 779d18h22m24s
2000:abc:ab:0:3003:bfe7:125a:5c0

Temporary  Preferred   6d23h51m4s 6d23h51m4s
2000:abc:ab:0:5d60:2136:554:188b

Public     Preferred  3314d16m15s 779d18h17m38s
2000:abc:bad:bad:3003:bfe7:125a:

5c0

Temporary  Preferred  6d23h50m22s  23h50m22s
2000:abc:bad:bad:5d60:2136:554:188b

Public     Preferred  3314d21m13s 779d18h22m36s
2000:aed:ab:0:3003:bfe7:125a:5c0

Temporary  Preferred  6d23h55m20s  23h55m20s
2000:aed:ab:0:5d60:2136:554:188b

Public     Preferred  3314d15m26s 779d18h16m49s
2000:bad:bad:bad:3003:bfe7:125a:

5c0

Temporary  Preferred  6d23h49m13s 6d23h49m13s
2000:bad:bad:bad:5d60:2136:554:188

b

 

A second problem that I found with that RFC is the second approach used to
generate the IID. In section 3.2.2 it describes a more randomized  IID
generation approach by using  CGA, but it does not explain how to use this
algorithm when security is not a consideration. In my extension, I also
explain how to use that algorithm if we do not wish to consider security as
a part of CGA. Of course, I derived that section from my last draft , SSAS,
and will remove that section from SSAS. I would prefer that the SSAS
algorithm  focus more on security and then focus on privacy.

 

Best,

Hosnieh


------=_NextPart_000_0027_01CE477C.ED099CB0
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 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@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>Dear =
All,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Since Fernando&#8217;s proposal is not going to solve =
the current problem with RFC 4941, I have suggested to him, on several =
occasions, that he resolve this problem so that the node's privacy will =
be better protected but he ignored this suggestion and claiming that his =
purpose is different. This is the main reason that today I wrote an RFC =
draft which I will submit&nbsp; to the IETF repository. This draft does =
not overlap Fernando&#8217;s proposal &nbsp;it is related to the =
problems with this RFC (RFC 4941) which he doesn't feel the need to =
address. The problems that I address here concern the fact that the node =
should also change its IID when it receives different router =
prefixes.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>In the experimental results, Windows machine that =
implemented privacy extension RFC, generates different IIDs by rebooting =
.But when it receives a different prefix without a reboot, then, on the =
first two occasions that the new&nbsp; prefixes received, the node was =
generated a new IID, but not for other new prefix generations. Also, as =
you can see, the temporary addresses have the same IID. This means that =
there is a need to change section 8 of this RFC<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp; 6.&nbsp; The node is now allowed to =
generate different interface<o:p></o:p></p><p =
class=3DMsoNormal>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; identifiers for =
different prefixes, if it so desires.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Where a =
different IID should be generated when a different prefix is =
received.&nbsp; I called it &#8220;RA-based privacy extension for =
SLAAC&#8221;.<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; Physical =
Address. . . . . . . . . : 00-0C-29-FA-38-32<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
IPv6 Address. . . . . . . . . . . : =
2000:abc:ab:0:3003:bfe7:125a:5c0(Preferre<o:p></o:p></p><p =
class=3DMsoNormal>d)<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
IPv6 Address. . . . . . . . . . . : =
2000:abc:bad:bad:3003:bfe7:125a:5c0(Prefe<o:p></o:p></p><p =
class=3DMsoNormal>rred)<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
Temporary IPv6 Address. . . . . . : =
2000:abc:ab:0:5d60:2136:554:188b(Preferre<o:p></o:p></p><p =
class=3DMsoNormal>d)<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
Temporary IPv6 Address. . . . . . : =
2000:abc:bad:bad:5d60:2136:554:188b(Prefe<o:p></o:p></p><p =
class=3DMsoNormal>rred)<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp; =
Temporary IPv6 Address. . . . . . : =
2000:bad:bad:bad:5d60:2136:554:188b(Prefe<o:p></o:p></p><p =
class=3DMsoNormal>rred)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Lifetime of =
the addresses as long as the computer is on<o:p></o:p></p><p =
class=3DMsoNormal>Addr Type&nbsp; DAD State&nbsp;&nbsp; Valid Life Pref. =
Life Address<o:p></o:p></p><p class=3DMsoNormal>---------&nbsp; =
----------- ---------- ---------- =
------------------------<o:p></o:p></p><p =
class=3DMsoNormal>Public&nbsp;&nbsp;&nbsp;&nbsp; Preferred&nbsp;&nbsp; =
3314d21m1s 779d18h22m24s =
2000:abc:ab:0:3003:bfe7:125a:5c0<o:p></o:p></p><p =
class=3DMsoNormal>Temporary&nbsp; Preferred&nbsp;&nbsp; 6d23h51m4s =
6d23h51m4s 2000:abc:ab:0:5d60:2136:554:188b<o:p></o:p></p><p =
class=3DMsoNormal>Public&nbsp;&nbsp;&nbsp;&nbsp; Preferred&nbsp; =
3314d16m15s 779d18h17m38s =
2000:abc:bad:bad:3003:bfe7:125a:<o:p></o:p></p><p =
class=3DMsoNormal>5c0<o:p></o:p></p><p class=3DMsoNormal>Temporary&nbsp; =
Preferred&nbsp; 6d23h50m22s&nbsp; 23h50m22s =
2000:abc:bad:bad:5d60:2136:554:188b<o:p></o:p></p><p =
class=3DMsoNormal>Public&nbsp;&nbsp;&nbsp;&nbsp; Preferred&nbsp; =
3314d21m13s 779d18h22m36s =
2000:aed:ab:0:3003:bfe7:125a:5c0<o:p></o:p></p><p =
class=3DMsoNormal>Temporary&nbsp; Preferred&nbsp; 6d23h55m20s&nbsp; =
23h55m20s 2000:aed:ab:0:5d60:2136:554:188b<o:p></o:p></p><p =
class=3DMsoNormal>Public&nbsp;&nbsp;&nbsp;&nbsp; Preferred&nbsp; =
3314d15m26s 779d18h16m49s =
2000:bad:bad:bad:3003:bfe7:125a:<o:p></o:p></p><p =
class=3DMsoNormal>5c0<o:p></o:p></p><p class=3DMsoNormal>Temporary&nbsp; =
Preferred&nbsp; 6d23h49m13s 6d23h49m13s =
2000:bad:bad:bad:5d60:2136:554:188<o:p></o:p></p><p =
class=3DMsoNormal>b<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>A second =
problem that I found with that RFC is the second approach used to =
generate the IID. In section 3.2.2 it describes a more randomized&nbsp; =
IID generation approach by using&nbsp; CGA, but it does not explain how =
to use this algorithm when security is not a consideration. In my =
extension, I also explain how to use that algorithm if we do not wish to =
consider security as a part of CGA. Of course, I derived that section =
from my last draft , SSAS, and will remove that section from SSAS. I =
would prefer that the SSAS algorithm&nbsp; focus more on security and =
then focus on privacy.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Best,<o:p></o:p></p><p =
class=3DMsoNormal>Hosnieh<o:p></o:p></p></div></body></html>
------=_NextPart_000_0027_01CE477C.ED099CB0--


From ietf@rozanak.com  Thu May  2 12:54:37 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19D821F8FE8 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 12:54:35 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EGjuNVtZJZ4A for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 12:54:30 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id BCEEA21F8F2F for <ipv6@ietf.org>; Thu,  2 May 2013 12:54:28 -0700 (PDT)
Received: from kopoli (e179165239.adsl.alicedsl.de [85.179.165.239]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M864P-1UKsds2DB3-00w3Xo; Thu, 02 May 2013 15:54:27 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
Subject: I-D: action -  draft-rafiee-6man-ra-privacy-00.txt
Date: Thu, 2 May 2013 21:54:20 +0200
Message-ID: <003101ce476e$d8d47520$8a7d5f60$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5HbRhjs819u116SgSbsb9n9420Sg==
Content-Language: en-us
X-Provags-ID: V02:K0:EM0OPKA+80hF+79qW5scoNXSV3ZLXof0Ud3P3J+TlFo kV8NzMpSBMfA89RmEfMseJMh4u8zvs1tiCVNwiysOhYdmjdhqP ZvXHJEFHdk8FGsVJFv6aX6YI9pyR+MZyG8ec74qLvlhe/Hme+V MigRAbfO1xt8dLGmgHstv0+VqZ0jxEcN6r+Nyh4DTgHga+JVJJ 3FLbNNLHKEoS9vWDMYa+CIQIgpwTUzKjNBi5o680KdiBJuDSiF 4yT1CJsSsS35qRF5L5jqAdX7ZbXb5Mm06xzyk/s7TPjWlYThU9 kHDMVkgjrdP+j6STc3PL3Uafcut5zrt5GBQg1F7yxY8Z96PE/n pctkzuq9h3FCStLNujVw=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 19:54:37 -0000

Dear all,

I explained the purpose of this draft in my last message to the list ( =
You can find it here =
http://www.ietf.org/mail-archive/web/ipv6/current/msg17718.html ). I =
upload this draft which addresses the problems in rfc 4941. I would =
appreciate your comments.=20
Share your ideas as to whether or not you find it useful.

Thanks,
Best,
Hosnieh


Filename:	 draft-rafiee-6man-ra-privacy
Revision:	 00
Title:		 Router Advertisement based privacy extension in IPv6 =
autoconfiguration
Creation date:	 2013-05-02
Group:		 Individual Submission
Number of pages: 6
URL:             =
http://www.ietf.org/internet-drafts/draft-rafiee-6man-ra-privacy-00.txt
Status:          =
http://datatracker.ietf.org/doc/draft-rafiee-6man-ra-privacy
Htmlized:        =
http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy-00


Abstract:
   Privacy is an important issue for many governments and users where
   its importance becomes more evident every day. Nodes might change
   their IP addresses frequently in order to avoid being tracked by
   attackers and which also results in the prevention of information
   being leaked from their nodes. In IPv6 networks there is currently
   one solution for maintaining privacy for nodes when IPv6 StateLess
   Address AutoConfiguration (SLAAC) (RFC-4662) is used. Unfortunately
   this solution, i.e., Privacy Extension (RFC-4941), has some problems,
   such as not generating a new Interface ID (IID) after changing the
   router prefix. The RFC also gives no explanation as to how to use CGA
   in its randomizing solution. The purpose of this document is to
   address these issues and to update the current RFC.



                                                                         =
        =20


The IETF Secretariat


From brian.e.carpenter@gmail.com  Thu May  2 13:12:42 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0D021F8E6B for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.333
X-Spam-Level: 
X-Spam-Status: No, score=-102.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mSRx3vyrTJdy for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:12:41 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 73A5F21F8EAF for <ipv6@ietf.org>; Thu,  2 May 2013 13:12:40 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id wy7so523336pbc.24 for <ipv6@ietf.org>; Thu, 02 May 2013 13:12:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MrOMz6uPqKtJS3HJXoFCA57JE4OoPF1hyTnYMwUe9Hw=; b=uY0IGdubO74R45jUo29WsMz1M3QJ6CQV70Nlb7aZTCEsXobk62TFtKKMtL2qpJK/cm UWQoxMsMNK31fmNxx7/h0hnnOf3N4iv45Zjpl1Fb9niu6EdwY8GpVHeQs2uJbYh93ud9 8IcUINAhXm0z27PYuTbNU+eKSm9X+cRRduBBs+o5hfG2nr44ofS2eFpOvPfTnbyESsNv ivOusGlyAjkmhn6rdtH5WKgGsHcdXlR964UxHJIgaPRQxZb1THQFsAoBf1/8tI/kPmUW Ks61wALpB49zeYNKnIuM0WFre3BPoOAyxxZdLbkh50l1iZ1cicwH7KrGBavV0iHS1x+k +spg==
X-Received: by 10.66.14.1 with SMTP id l1mr11566543pac.150.1367525559972; Thu, 02 May 2013 13:12:39 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id j13sm9500379pat.17.2013.05.02.13.12.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 13:12:38 -0700 (PDT)
Message-ID: <5182C8BD.9020904@gmail.com>
Date: Fri, 03 May 2013 08:12:45 +1200
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: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com>
In-Reply-To: <20130502183949.7430.21538.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Fred Baker <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 20:12:42 -0000

Yes, I know which WG this is, and I would like to test a
hypothesis here: that the draft below is incompatible with
RFC 6437 (and the long discussion that led to it).

The problem, if there is one, lies in section 4 of RFC 6437.

>    A node that sets the flow label MAY also take part in a flow state
>    establishment method that results in assigning specific treatments to
>    specific flows, possibly including signaling.  

That's OK - nodes using -ospf-dst-flowlabel-routing would be doing that.

>    Any such method MUST
>    NOT disturb nodes taking part in the stateless scenario just
>    described.  Thus, any node that sets flow label values according to a
>    stateful scheme MUST choose labels that conform to Section 3 of this
>    specification.  Further details are not discussed in this document.

That's the bit that -ospf-dst-flowlabel-routing does not conform to, as
far as I can see.

Regards
   Brian

On 03/05/2013 06:39, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : Using OSPFv3 with Role-Based Access Control
> 	Author(s)       : Fred Baker
> 	Filename        : draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
> 	Pages           : 10
> 	Date            : 2013-05-02
> 
> Abstract:
>    This note describes the changes necessary for OSPFv3 to route classes
>    of IPv6 traffic that are defined by an IPv6 Flow Label and a
>    destination prefix.  This implies not simply routing "to a
>    destination", but "traffic going to that destination AND using a
>    specified flow label".  It may be combined with other qualifying
>    attributes, such as "traffic going to that destination AND using a
>    specified flow label AND from a specified source prefix".  The
>    obvious application is data center inter-tenant routing using a form
>    of role-based access control.  If the sender doesn't know the value
>    to insert in the flow label (the receiver's tenant ID), it in effect
>    has no route to that destination, thus providing an access list that
>    is as changeable and scalable as routing.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-baker-ipv6-ospf-dst-flowlabel-routing
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-flowlabel-routing-01
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-baker-ipv6-ospf-dst-flowlabel-routing-01
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

From fgont@si6networks.com  Thu May  2 13:18:09 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADEF21F8E93 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:18:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6JrhkJrQIu2F for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:18:08 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1B75F21F8EA8 for <ipv6@ietf.org>; Thu,  2 May 2013 13:18:07 -0700 (PDT)
Received: from [186.134.26.236] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UXzx5-0000yo-HE; Thu, 02 May 2013 22:18:03 +0200
Message-ID: <5182C9F3.3040004@si6networks.com>
Date: Thu, 02 May 2013 17:17:55 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: Solutions to the problem with RFC 4941
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>
In-Reply-To: <002601ce476c$297cae00$7c760a00$@rozanak.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 20:18:09 -0000

Hosnieh,

You have been making many misleading claims about things I have said or
stated. Quite a few times I have corrected you, provided pointers, etc.
-- which you have systematically ignored. Your comments below seem to
indicate to you didn't bother reading the Introduction of
draft-ietf-6man-stable-privacy-addresses, or pay attention to the
clarifications I made on-list. I suggest you wait for the next rev of
the document, but meanwhile you may consult
<http://www.iab.org/wp-content/IAB-uploads/2011/07/IPv6-addresses-privacy-review.txt>
for an alternative explanation of the issues involved.

I believe such behavior is harmful.

All & chairs: I'm currently working a lot with all (off-list, to reduce
the noise) with all those folks that provided feedback during IETC LC
and right after IETF LC on the mailing-list... and we're making a lot of
progress on the I-D. My plan is to submit a rev of
draft-ietf-6man-stable-privacy-addresses fr broader review (i.e., have
the wg review that I have double-checked that addresses IETF LC comments).

FWIW, I'd like to express a big "thank you" to all the folks that have
provided timely comments/reviews, and that have been exchanging emails
with me (off-list) to improve the I-D.

P.S.: At this point I will not continue responding on this thread.

Thanks,
Fernando




On 05/02/2013 04:35 PM, Hosnieh Rafiee wrote:
> Dear All,
> 
>  
> 
> Since Fernando’s proposal is not going to solve the current problem with
> RFC 4941, I have suggested to him, on several occasions, that he resolve
> this problem so that the node's privacy will be better protected but he
> ignored this suggestion and claiming that his purpose is different. This
> is the main reason that today I wrote an RFC draft which I will submit 
> to the IETF repository. This draft does not overlap Fernando’s proposal
>  it is related to the problems with this RFC (RFC 4941) which he doesn't
> feel the need to address. The problems that I address here concern the
> fact that the node should also change its IID when it receives different
> router prefixes.
> 
>  
> 
> In the experimental results, Windows machine that implemented privacy
> extension RFC, generates different IIDs by rebooting .But when it
> receives a different prefix without a reboot, then, on the first two
> occasions that the new  prefixes received, the node was generated a new
> IID, but not for other new prefix generations. Also, as you can see, the
> temporary addresses have the same IID. This means that there is a need
> to change section 8 of this RFC
> 
>    6.  The node is now allowed to generate different interface
> 
>       identifiers for different prefixes, if it so desires.
> 
>  
> 
> Where a different IID should be generated when a different prefix is
> received.  I called it “RA-based privacy extension for SLAAC”.
> 
>    Physical Address. . . . . . . . . : 00-0C-29-FA-38-32
> 
>  
> 
>    IPv6 Address. . . . . . . . . . . :
> 2000:abc:ab:0:3003:bfe7:125a:5c0(Preferre
> 
> d)
> 
>    IPv6 Address. . . . . . . . . . . :
> 2000:abc:bad:bad:3003:bfe7:125a:5c0(Prefe
> 
> rred)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:abc:ab:0:5d60:2136:554:188b(Preferre
> 
> d)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:abc:bad:bad:5d60:2136:554:188b(Prefe
> 
> rred)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:bad:bad:bad:5d60:2136:554:188b(Prefe
> 
> rred)
> 
>  
> 
> Lifetime of the addresses as long as the computer is on
> 
> Addr Type  DAD State   Valid Life Pref. Life Address
> 
> ---------  ----------- ---------- ---------- ------------------------
> 
> Public     Preferred   3314d21m1s 779d18h22m24s
> 2000:abc:ab:0:3003:bfe7:125a:5c0
> 
> Temporary  Preferred   6d23h51m4s 6d23h51m4s
> 2000:abc:ab:0:5d60:2136:554:188b
> 
> Public     Preferred  3314d16m15s 779d18h17m38s
> 2000:abc:bad:bad:3003:bfe7:125a:
> 
> 5c0
> 
> Temporary  Preferred  6d23h50m22s  23h50m22s
> 2000:abc:bad:bad:5d60:2136:554:188b
> 
> Public     Preferred  3314d21m13s 779d18h22m36s
> 2000:aed:ab:0:3003:bfe7:125a:5c0
> 
> Temporary  Preferred  6d23h55m20s  23h55m20s
> 2000:aed:ab:0:5d60:2136:554:188b
> 
> Public     Preferred  3314d15m26s 779d18h16m49s
> 2000:bad:bad:bad:3003:bfe7:125a:
> 
> 5c0
> 
> Temporary  Preferred  6d23h49m13s 6d23h49m13s
> 2000:bad:bad:bad:5d60:2136:554:188
> 
> b
> 
>  
> 
> A second problem that I found with that RFC is the second approach used
> to generate the IID. In section 3.2.2 it describes a more randomized 
> IID generation approach by using  CGA, but it does not explain how to
> use this algorithm when security is not a consideration. In my
> extension, I also explain how to use that algorithm if we do not wish to
> consider security as a part of CGA. Of course, I derived that section
> from my last draft , SSAS, and will remove that section from SSAS. I
> would prefer that the SSAS algorithm  focus more on security and then
> focus on privacy.
> 
>  
> 
> Best,
> 
> Hosnieh
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


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





From fred@cisco.com  Thu May  2 13:37:53 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E90B21F8E7C for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.561
X-Spam-Level: 
X-Spam-Status: No, score=-110.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+cbJfVB7ptd for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 13:37:47 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id BF76A21F8E6E for <ipv6@ietf.org>; Thu,  2 May 2013 13:37:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1696; q=dns/txt; s=iport; t=1367527067; x=1368736667; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=gQnLVg8gV2M1wUhr8wQMg/rBlvE15+epUJBXZ3NZDIk=; b=jQlVMxrq/NEwckfZ6Oh7uGzUYerAehUallFTGRy8KYNZg6qLdzCczX5b bqkoyUN5i8ox4OjYSVFHeFbnpcHpHl1HJGxALDbPLDaO7yAciuueecbzZ 7piGrXN6+bkIv59ESVOC5kRv823ifWiYauHHukEE5gv3kwCtPqre4UQiq 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGXNglGtJXG9/2dsb2JhbABICoMHv19/FnSCHwEBAQQ6KxQQAgEIGAoUECERJQIEDgUIh3IDD7lNDYd8jE+BG4EJAjEHgnJhA5VHjXWFIYMNgic
X-IronPort-AV: E=Sophos;i="4.87,599,1363132800"; d="scan'208";a="205808984"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-7.cisco.com with ESMTP; 02 May 2013 20:37:47 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r42KblLB026997 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 20:37:47 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Thu, 2 May 2013 15:37:47 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Topic: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Index: AQHOR2SOLmLY/mFNc0KazQgDGFcTqJjyp9mAgAAG+wA=
Date: Thu, 2 May 2013 20:37:46 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com>
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com> <5182C8BD.9020904@gmail.com>
In-Reply-To: <5182C8BD.9020904@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BA94B90AA000EA449126729591A6EB49@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 20:37:53 -0000

On May 2, 2013, at 1:12 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
 wrote:
>>   Any such method MUST
>>   NOT disturb nodes taking part in the stateless scenario just
>>   described.  Thus, any node that sets flow label values according to a
>>   stateful scheme MUST choose labels that conform to Section 3 of this
>>   specification.  Further details are not discussed in this document.
>=20
> That's the bit that -ospf-dst-flowlabel-routing does not conform to, as
> far as I can see.

It may be so. Can you point me to an implementation depending on 6437, eith=
er host, router, or load balancer?

Here's my frustration. The Flow label, if one goes into the musty dusty mis=
ts of time, does not do what it was originally designed to do, which is ide=
ntify flows in the Nimrod routing model; to do that, it would need to be fu=
ngible in the network. It has been largely replaced by MPLS, which can stac=
k its equivalent. As you know (you wrote half of them), there are a several=
 RFCs that propose uses of the flow label, and those uses differ from each =
other. None of them obsolete the others, so they are all on the table.

You are taking one in that series and pushing it as the "one true religion"=
, and stating that it is therefore off limits to use the flow label for a s=
pecific well defined use case.

I call foul. If RFC 6437 is the only game in town, at least obsolete RFCs 1=
809 and 6294, and the section proposing a use case for it in 2460.

And explain to me why it would be inappropriate for a host (virtual or phys=
ical) or a hypervisor to set a flow label and use it end to end for a speci=
fic use case in a data center?=

From brian.e.carpenter@gmail.com  Thu May  2 14:18:08 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839DF21F85EE for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZGDF2g4T4rvF for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:18:07 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C5F1F21F85DC for <ipv6@ietf.org>; Thu,  2 May 2013 14:18:07 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id wz17so554443pbc.17 for <ipv6@ietf.org>; Thu, 02 May 2013 14:17:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=d9gVzq4+pxywg5nQVE+wBP+d4vK4JFfXYdoU4xjkEqo=; b=WoLwDgnbWFPXwK2XSIwwiznzrymBFE27xBEnwmxbJuXAysFMvPZQk/dV4R5VeY9K9F iqRrKLQAPUN5/Np6Ungf42wGyiF2NaLxrYUN0nnJgq9KqHd8NXYlqjn/b4QwKtchtzqi 6/+1H8vDmjY1WlAuN6MDBXy/2NWKBbKf0GtP948fTCISqegxAfaltzOx3wXf3OmZ23mf kl2kZjKF5mMLEKqha+igkUMNZdEK7vM4ToXsKwcvAqjraUn2eVQh33wxjR95zGwlUDoV AuidRwWap7S7rmM6ma7rHdr85vLifd1gX15h3NGoc4T8nyqo3URITLWqEIqt4KClu/85 MA6w==
X-Received: by 10.66.197.165 with SMTP id iv5mr11879868pac.67.1367529473800; Thu, 02 May 2013 14:17:53 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id aj2sm8710417pbc.1.2013.05.02.14.17.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 14:17:52 -0700 (PDT)
Message-ID: <5182D807.1050001@gmail.com>
Date: Fri, 03 May 2013 09:17:59 +1200
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: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com> <5182C8BD.9020904@gmail.com> <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:18:08 -0000

On 03/05/2013 08:37, Fred Baker (fred) wrote:
> On May 2, 2013, at 1:12 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>  wrote:
>>>   Any such method MUST
>>>   NOT disturb nodes taking part in the stateless scenario just
>>>   described.  Thus, any node that sets flow label values according to a
>>>   stateful scheme MUST choose labels that conform to Section 3 of this
>>>   specification.  Further details are not discussed in this document.
>> That's the bit that -ospf-dst-flowlabel-routing does not conform to, as
>> far as I can see.
> 
> It may be so. Can you point me to an implementation depending on 6437, either host, router, or load balancer?

No, but it's too recent - implementers have to look at the newest Node Requirements
and then do their product cycle thing. For load balancers, there's an Informational
draft wending its way through the system.

> Here's my frustration. The Flow label, if one goes into the musty dusty mists of time, does not do what it was originally designed to do, which is identify flows in the Nimrod routing model; to do that, it would need to be fungible in the network. It has been largely replaced by MPLS, which can stack its equivalent. As you know (you wrote half of them), there are a several RFCs that propose uses of the flow label, and those uses differ from each other. None of them obsolete the others, so they are all on the table.

I agree. That's why I've invested considerable effort myself.

> You are taking one in that series and pushing it as the "one true religion", and stating that it is therefore off limits to use the flow label for a specific well defined use case.

Well, there was a two year debate in 6man before we reached rough consensus.
That's all I know how to do. However, there is intentional wiggle room
in the RFC and maybe we can reconcile things; I'd like other peoples'
eyes on the that question. For compatibility with load balancing, all
we really need is pseudo-random bits - if the way of setting up
destination labels in your proposal could do that, it's probably fine.

> I call foul. If RFC 6437 is the only game in town, at least obsolete RFCs 1809 and 6294, and the section proposing a use case for it in 2460.

I thought we did obsolete those bits of 2460. iirc they were non-normative anyway.
1809 is informational; I've never thought of it as needing to be obsoleted.
6294 is purely descriptive, so I don't see why it's an issue.

> And explain to me why it would be inappropriate for a host (virtual or physical) or a hypervisor to set a flow label and use it end to end for a specific use case in a data center?

I don't think it would, but this WG disliked the concept of defining
a local flow label domain and it was dropped from what became RFC 6437.
That's why I think the way out is to use the wiggle room mentioned
above. I hope we can.

   Brian

From fred@cisco.com  Thu May  2 14:25:16 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212C121F8AD1 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.208
X-Spam-Level: 
X-Spam-Status: No, score=-110.208 tagged_above=-999 required=5 tests=[AWL=0.391, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8DegcLY2RDU for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:25:10 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 930EB21F89A6 for <ipv6@ietf.org>; Thu,  2 May 2013 14:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=882; q=dns/txt; s=iport; t=1367529910; x=1368739510; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RpOq3femNuaauI4lUrlOhrGdBcygn1bcCiyuzP+cxj4=; b=PUxfE0UCaC5+N/QGpG+03QQhdOl+hcdVyw017hDMrkjuHUfvzfvZPaJ9 La0kVW5rlSyzxpbFHkVYRQhB7d8w/e/U8oho14S2LMoSolonG3RpQso7k BCysQkMep7LkemH4WPF2rnMAK2D+uUfKEPruLuaPhnOfji1XXPom9m1Pj o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAGDZglGtJXG//2dsb2JhbABSgweDJ7w4fxZ0gh8BAQEDATo/BQsCAQgiFBAhESUCBA4FCIdyAwkGuUMNh3yMT4IkAjEHgnJhA5VHjXWFIYMNgic
X-IronPort-AV: E=Sophos;i="4.87,599,1363132800"; d="scan'208";a="205637011"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 02 May 2013 21:24:53 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r42LOrWd023315 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 21:24:53 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Thu, 2 May 2013 16:24:53 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Topic: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Index: AQHOR2SOLmLY/mFNc0KazQgDGFcTqJjyp9mAgAAG+wCAAAs/gIAAAewA
Date: Thu, 2 May 2013 21:24:52 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com>
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com> <5182C8BD.9020904@gmail.com> <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com> <5182D807.1050001@gmail.com>
In-Reply-To: <5182D807.1050001@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24551BBD1E10F347BFB606111D885ECE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:25:16 -0000

On May 2, 2013, at 2:17 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
 wrote:

> That's why I think the way out is to use the wiggle room mentioned
> above. I hope we can.

I'm afraid I don't see any wiggle room. Section 3 of RFC 6437 requires ever=
y new flow - every new TCP session, in the most extreme reading of that - t=
o have a new flow label value. This proposal presumes that all of the flows=
 subject to the same security policy would be identified by the same flow l=
abel. By your rubric, an operator who is not using the flow label for load =
balancing MUST NOT use the flow label for a different purpose. Frankly, I w=
ish you luck enforcing the ruling. Operators have a funny habit of doing wh=
at they deem important. Our job in the IETF is to help them be able to do t=
hat using software and hardware from multiple interoperable sources.=

From joelja@bogus.com  Thu May  2 14:35:16 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFCCC21F8ED8 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:35:16 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWq+hDMWu5Zj for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:35:16 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 02EB121F8ECE for <ipv6@ietf.org>; Thu,  2 May 2013 14:35:15 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r42LZCV3095835 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 2 May 2013 21:35:12 GMT (envelope-from joelja@bogus.com)
Message-ID: <5182DC0B.8020408@bogus.com>
Date: Thu, 02 May 2013 14:35:07 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com>	<5182C8BD.9020904@gmail.com>	<8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com>	<5182D807.1050001@gmail.com> <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 02 May 2013 21:35:13 +0000 (UTC)
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:35:16 -0000

On 5/2/13 2:24 PM, Fred Baker (fred) wrote:
> On May 2, 2013, at 2:17 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>   wrote:
>
>> That's why I think the way out is to use the wiggle room mentioned
>> above. I hope we can.
> I'm afraid I don't see any wiggle room. Section 3 of RFC 6437 requires every new flow - every new TCP session, in the most extreme reading of that - to have a new flow label value. This proposal presumes that all of the flows subject to the same security policy would be identified by the same flow label. By your rubric, an operator who is not using the flow label for load balancing MUST NOT use the flow label for a different purpose. Frankly, I wish you luck enforcing the ruling. Operators have a funny habit of doing what they deem important. Our job in the IETF is to help them be able to do that using software and hardware from multiple interoperable sources.
I've been uncomfortable with the attempts to rehabilitate the flow label 
since they seem to be inconsistent. I can't do something useful if 
that's largely unusable due to host behavior, if I keep changing what 
the hosts are doing with it.

If I can resuse it without the hosts changing their behavior, great 
especially if it's within my own span of control. but then I don't 
really need ietf consensus for that.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From ietf@rozanak.com  Thu May  2 14:36:22 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0364521F8EC7 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:36:22 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYgxBMfx+HaW for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:36:17 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 4816421F8EDA for <ipv6@ietf.org>; Thu,  2 May 2013 14:36:17 -0700 (PDT)
Received: from kopoli (e179165239.adsl.alicedsl.de [85.179.165.239]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0M1FRo-1UIP9q1DEu-00u2mH; Thu, 02 May 2013 17:36:01 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Fernando Gont'" <fgont@si6networks.com>
References: <002601ce476c$297cae00$7c760a00$@rozanak.com> <5182C9F3.3040004@si6networks.com>
In-Reply-To: <5182C9F3.3040004@si6networks.com>
Subject: RE: Solutions to the problem with RFC 4941
Date: Thu, 2 May 2013 23:35:51 +0200
Message-ID: <003801ce477d$0933b1f0$1b9b15d0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFkDy0wKnLTw64YzBf5YRtbXElpEgHU7crJmbgySjA=
Content-Language: en-us
X-Provags-ID: V02:K0:CFA1YXDerrwwlZ0b/efnqYKz5q71w38wHarftkoYdFw IJD4YBjXDfAhSUiGwZkEbf6UToxsWsTV4qtsJuR/gjzRwXkkgq igaKQKhKCQglgR12ooI3HJhEsMj8bXmkGzFhoaj8wuyf3EThv0 atmnJIA3H5Am/cM2z3Pu7u9KtYzyFsoIThyfk6ceKRTTTo8Gux c46Ptx9zyAS9D+LROpYatvUbSyb0DC7Gbh+DHqb7kbeXtFoXq/ qt0O6On2peMu7q64Uwy1jGOKgsKT/aUmQqC45FocYdf5lLcMh7 aqUE1QRj6djWJntVjhYCQiC9jRTtXZqxM3w77973MdWJdw4Mr1 6+fq0/0gTbxQg30FiFo4=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:36:22 -0000

Fernando,

The purpose of your draft was not to obsolete or update RFC 4941 and you
wanted to have your approach as an optional approach in parallel with that
approach. So what is your problem with improving that document. It has
nothing to do with your proposal. The people can accept or reject yours. I
do not see any harmful behavior here as I also asked you 1000 times to
update that rfc instead of having something new or in between two RFCs.

Hosnieh



-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com] 
Sent: Thursday, May 02, 2013 10:18 PM
To: Hosnieh Rafiee
Cc: ipv6@ietf.org
Subject: Re: Solutions to the problem with RFC 4941

Hosnieh,

You have been making many misleading claims about things I have said or
stated. Quite a few times I have corrected you, provided pointers, etc.
-- which you have systematically ignored. Your comments below seem to
indicate to you didn't bother reading the Introduction of
draft-ietf-6man-stable-privacy-addresses, or pay attention to the
clarifications I made on-list. I suggest you wait for the next rev of the
document, but meanwhile you may consult
<http://www.iab.org/wp-content/IAB-uploads/2011/07/IPv6-addresses-privacy-re
view.txt>
for an alternative explanation of the issues involved.

I believe such behavior is harmful.

All & chairs: I'm currently working a lot with all (off-list, to reduce the
noise) with all those folks that provided feedback during IETC LC and right
after IETF LC on the mailing-list... and we're making a lot of progress on
the I-D. My plan is to submit a rev of
draft-ietf-6man-stable-privacy-addresses fr broader review (i.e., have the
wg review that I have double-checked that addresses IETF LC comments).

FWIW, I'd like to express a big "thank you" to all the folks that have
provided timely comments/reviews, and that have been exchanging emails with
me (off-list) to improve the I-D.

P.S.: At this point I will not continue responding on this thread.

Thanks,
Fernando




On 05/02/2013 04:35 PM, Hosnieh Rafiee wrote:
> Dear All,
> 
>  
> 
> Since Fernando's proposal is not going to solve the current problem 
> with RFC 4941, I have suggested to him, on several occasions, that he 
> resolve this problem so that the node's privacy will be better 
> protected but he ignored this suggestion and claiming that his purpose 
> is different. This is the main reason that today I wrote an RFC draft 
> which I will submit to the IETF repository. This draft does not 
> overlap Fernando's proposal  it is related to the problems with this 
> RFC (RFC 4941) which he doesn't feel the need to address. The problems 
> that I address here concern the fact that the node should also change 
> its IID when it receives different router prefixes.
> 
>  
> 
> In the experimental results, Windows machine that implemented privacy 
> extension RFC, generates different IIDs by rebooting .But when it 
> receives a different prefix without a reboot, then, on the first two 
> occasions that the new  prefixes received, the node was generated a 
> new IID, but not for other new prefix generations. Also, as you can 
> see, the temporary addresses have the same IID. This means that there 
> is a need to change section 8 of this RFC
> 
>    6.  The node is now allowed to generate different interface
> 
>       identifiers for different prefixes, if it so desires.
> 
>  
> 
> Where a different IID should be generated when a different prefix is 
> received.  I called it "RA-based privacy extension for SLAAC".
> 
>    Physical Address. . . . . . . . . : 00-0C-29-FA-38-32
> 
>  
> 
>    IPv6 Address. . . . . . . . . . . :
> 2000:abc:ab:0:3003:bfe7:125a:5c0(Preferre
> 
> d)
> 
>    IPv6 Address. . . . . . . . . . . :
> 2000:abc:bad:bad:3003:bfe7:125a:5c0(Prefe
> 
> rred)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:abc:ab:0:5d60:2136:554:188b(Preferre
> 
> d)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:abc:bad:bad:5d60:2136:554:188b(Prefe
> 
> rred)
> 
>    Temporary IPv6 Address. . . . . . :
> 2000:bad:bad:bad:5d60:2136:554:188b(Prefe
> 
> rred)
> 
>  
> 
> Lifetime of the addresses as long as the computer is on
> 
> Addr Type  DAD State   Valid Life Pref. Life Address
> 
> ---------  ----------- ---------- ---------- ------------------------
> 
> Public     Preferred   3314d21m1s 779d18h22m24s
> 2000:abc:ab:0:3003:bfe7:125a:5c0
> 
> Temporary  Preferred   6d23h51m4s 6d23h51m4s
> 2000:abc:ab:0:5d60:2136:554:188b
> 
> Public     Preferred  3314d16m15s 779d18h17m38s
> 2000:abc:bad:bad:3003:bfe7:125a:
> 
> 5c0
> 
> Temporary  Preferred  6d23h50m22s  23h50m22s 
> 2000:abc:bad:bad:5d60:2136:554:188b
> 
> Public     Preferred  3314d21m13s 779d18h22m36s
> 2000:aed:ab:0:3003:bfe7:125a:5c0
> 
> Temporary  Preferred  6d23h55m20s  23h55m20s 
> 2000:aed:ab:0:5d60:2136:554:188b
> 
> Public     Preferred  3314d15m26s 779d18h16m49s
> 2000:bad:bad:bad:3003:bfe7:125a:
> 
> 5c0
> 
> Temporary  Preferred  6d23h49m13s 6d23h49m13s
> 2000:bad:bad:bad:5d60:2136:554:188
> 
> b
> 
>  
> 
> A second problem that I found with that RFC is the second approach 
> used to generate the IID. In section 3.2.2 it describes a more 
> randomized IID generation approach by using  CGA, but it does not 
> explain how to use this algorithm when security is not a 
> consideration. In my extension, I also explain how to use that 
> algorithm if we do not wish to consider security as a part of CGA. Of 
> course, I derived that section from my last draft , SSAS, and will 
> remove that section from SSAS. I would prefer that the SSAS algorithm  
> focus more on security and then focus on privacy.
> 
>  
> 
> Best,
> 
> Hosnieh
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


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





From brian.e.carpenter@gmail.com  Thu May  2 14:37:29 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C2921F8ECE for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:37: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LO7RvoRImFaZ for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:37:16 -0700 (PDT)
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE1F21F8EE8 for <ipv6@ietf.org>; Thu,  2 May 2013 14:37:16 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id x10so569554pdj.35 for <ipv6@ietf.org>; Thu, 02 May 2013 14:37:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1XqcoK4yr55tViMds6BCFH2E+6J/0ZAW3RCvMtPfkDY=; b=M9Zr2Idxyf7JcVLwQujWo2ufEAhAGsy38Bprl2A1rlWEWDcrXOYrtl8dr6Xg7qzLSr QLSiJlbhlEK5/6yIzyloO38QzsKDzaxPD9nH/A49q4ZSIa+Qqfoade0k2wCCsZ520HEj qhAcdLlPg+ewTwCHwjNDMdFKGL7NjNsta7DVUVu/Lhin2jn0wXQPuIfH8ucZtxLknicM j5TKKijm9cisXll2lwA176nd775ftF/ElXcC375b7U7fGimjXnqlvdjW4EkulZzCeuWS lwqLTkhe+Dyyw14PL5OGEJbtu3OnI/vptiHkw0xFH4l0DY8u7tH1k0QbBAMlW0wukxNP kRbA==
X-Received: by 10.66.27.68 with SMTP id r4mr11923825pag.151.1367530636005; Thu, 02 May 2013 14:37:16 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id qr7sm8736561pbc.16.2013.05.02.14.37.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 14:37:14 -0700 (PDT)
Message-ID: <5182DC92.1020403@gmail.com>
Date: Fri, 03 May 2013 09:37:22 +1200
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: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com> <5182C8BD.9020904@gmail.com> <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com> <5182D807.1050001@gmail.com> <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:37:29 -0000

Read the first paragraph of the Introduction carefully, in connection
with the SHOULD in the second paragraph of section 3.

You could definitely provide a good reason for bypassing that SHOULD.

Regards
   Brian

On 03/05/2013 09:24, Fred Baker (fred) wrote:
> On May 2, 2013, at 2:17 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
>  wrote:
> 
>> That's why I think the way out is to use the wiggle room mentioned
>> above. I hope we can.
> 
> I'm afraid I don't see any wiggle room. Section 3 of RFC 6437 requires every new flow - every new TCP session, in the most extreme reading of that - to have a new flow label value. This proposal presumes that all of the flows subject to the same security policy would be identified by the same flow label. By your rubric, an operator who is not using the flow label for load balancing MUST NOT use the flow label for a different purpose. Frankly, I wish you luck enforcing the ruling. Operators have a funny habit of doing what they deem important. Our job in the IETF is to help them be able to do that using software and hardware from multiple interoperable sources.

From fred@cisco.com  Thu May  2 14:45:54 2013
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D548A21F854D for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.354
X-Spam-Level: 
X-Spam-Status: No, score=-110.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdMBaIkHsGpy for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 14:45:39 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE1021F8D2C for <ipv6@ietf.org>; Thu,  2 May 2013 14:45:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1353; q=dns/txt; s=iport; t=1367531139; x=1368740739; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yVS8s1yfA4MaGXrCs75V/U4k5gfxOnG0DoOv90z/dTI=; b=Q+KyvJiVjp9d3xcLAszDL42xVI/V2r9SMfJvINGDOPjPMKaosRZuRocX jqJS32jWM8EC8M6hfXwY5hlzH7vlrRZmcIbJAhtZxCgSoBR7A+0PFcAes O6QN9U2CkIvJJGX/jKF+ZEhT1dKydrhLR2VMm9wdDA99DKG7Te3utTnYf 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFACbdglGtJV2d/2dsb2JhbABSgwe/X38WdIIfAQEBAwE6PwULAgEIGAoUECERJQIEDgUIh3IDCQa5Pw2HfIxPgiQCMQeCcmEDlUeNdYUhgw2CJw
X-IronPort-AV: E=Sophos;i="4.87,599,1363132800"; d="scan'208";a="205807946"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP; 02 May 2013 21:45:38 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r42LjcWR005976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 21:45:38 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Thu, 2 May 2013 16:45:38 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Topic: I-D Action: draft-baker-ipv6-ospf-dst-flowlabel-routing-01.txt
Thread-Index: AQHOR2SOLmLY/mFNc0KazQgDGFcTqJjyp9mAgAAG+wCAAAs/gIAAAewAgAADfgCAAAJOgA==
Date: Thu, 2 May 2013 21:45:37 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B83DE0D@xmb-rcd-x09.cisco.com>
References: <20130502183949.7430.21538.idtracker@ietfa.amsl.com> <5182C8BD.9020904@gmail.com> <8C48B86A895913448548E6D15DA7553B83BC5D@xmb-rcd-x09.cisco.com> <5182D807.1050001@gmail.com> <8C48B86A895913448548E6D15DA7553B83CD2C@xmb-rcd-x09.cisco.com> <5182DC92.1020403@gmail.com>
In-Reply-To: <5182DC92.1020403@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <24180E70711CF04A91ABC6AB72636F19@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 02 May 2013 21:45:55 -0000

On May 2, 2013, at 2:37 PM, Brian E Carpenter <brian.e.carpenter@gmail.com>
 wrote:

> Read the first paragraph of the Introduction carefully, in connection
> with the SHOULD in the second paragraph of section 3.
>=20
> You could definitely provide a good reason for bypassing that SHOULD.

Fine. I'll point to that and say that this is a different use case.

> Regards
>   Brian
>=20
> On 03/05/2013 09:24, Fred Baker (fred) wrote:
>> On May 2, 2013, at 2:17 PM, Brian E Carpenter <brian.e.carpenter@gmail.c=
om>
>> wrote:
>>=20
>>> That's why I think the way out is to use the wiggle room mentioned
>>> above. I hope we can.
>>=20
>> I'm afraid I don't see any wiggle room. Section 3 of RFC 6437 requires e=
very new flow - every new TCP session, in the most extreme reading of that =
- to have a new flow label value. This proposal presumes that all of the fl=
ows subject to the same security policy would be identified by the same flo=
w label. By your rubric, an operator who is not using the flow label for lo=
ad balancing MUST NOT use the flow label for a different purpose. Frankly, =
I wish you luck enforcing the ruling. Operators have a funny habit of doing=
 what they deem important. Our job in the IETF is to help them be able to d=
o that using software and hardware from multiple interoperable sources.


From zhou.sujing@zte.com.cn  Thu May  2 18:14:07 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208BD21F8540 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 18:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.02
X-Spam-Level: 
X-Spam-Status: No, score=-99.02 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8udfaJZYClc for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 18:14:02 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id C599F21F854D for <ipv6@ietf.org>; Thu,  2 May 2013 18:14:01 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 259E8440ED5; Fri,  3 May 2013 09:13:39 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r431DcSu034781; Fri, 3 May 2013 09:13:38 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <518229CC.6020300@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Re: Last Call: <draft-ietf-6man-stable-privacy-addresses-06.txt> (A method for Generating Stable Privacy-Enhanced Addresses with IPv6 Stateless Address Autoconfiguration (SLAAC)) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFDE183E67.25DB3B5D-ON48257B60.00062885-48257B60.0006D115@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Fri, 3 May 2013 09:13:22 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-03 09:13:17, Serialize complete at 2013-05-03 09:13:17
Content-Type: multipart/alternative; boundary="=_alternative 0006D11448257B60_="
X-MAIL: mse01.zte.com.cn r431DcSu034781
Cc: huitema@microsoft.com, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 01:14:07 -0000

This is a multipart message in MIME format.
--=_alternative 0006D11448257B60_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

RmVybmFuZG8gR29udCA8ZmdvbnRAc2k2bmV0d29ya3MuY29tPiDQtNPaIDIwMTMtMDUtMDIgMTY6
NTQ6MzY6DQoNCj4gSGksIFN1amluZywNCj4gDQo+IE9uIDA1LzAyLzIwMTMgMDU6MTQgQU0sIFN1
amluZyBaaG91IHdyb3RlOg0KPiA+IA0KPiA+IEhhdmUgeW91IGV2ZXIgY29uc2lkZXJlZCBhZGQg
YSBkYXRlL3RpbWUgKG9wdGlvbmFsICkgcGFyYW1ldGVyICBpbg0KPiA+IGdlbmVyYXRpb24gb2Yg
dGhlIG5ldyBSSUQsDQo+ID4gZm9yIGV4YW1wbGU6DQo+ID4gIFJJRCA9IEYoUHJlZml4LCBJbnRl
cmZhY2VfSW5kZXgsIE5ldHdvcmtfSUQsIERBRF9Db3VudGVyLERhdGUvVGltZSwNCj4gPiBzZWNy
ZXRfa2V5KSwNCj4gPiB0aHVzIHdpbGwgcmVzdWx0IGluIGRpZmZlcmVudCBJSUQgZWFjaCBkaWZm
ZXJlbnQgeWVhciwgZWFjaCBkaWZmZXJlbnQNCj4gPiBtb250aCwgb3IgZXZlbg0KPiA+IGRpZmZl
cmVudCBkYXkuDQo+ID4gDQo+ID4gT2YgY291cnNlLCB0aGUgSUlEIG93bmVyIGNhbiBjaG9vc2Ug
dG8gY2hhbmdlIHNlY3JldF9rZXkgIHRvIG9idGFpbg0KPiA+IGRpZmZlcmVudCBJSUQsDQo+ID4g
YnV0IHdpdGggYW4gYWRkaXRpb24gb2YgZGF0ZS90aW1lIG9wdGlvbiwgaXQgaXMgbW9yZSBmbGV4
aWJsZS4NCj4gDQo+IE5vdCByZWFsbHkuIFRoZSBhZGRyZXNzZXMgYXJlIG1lYW50IHRvIGJlIGNv
bnN0YW50LiBBbmQgaWYgeW91IHdhbnQgdG8NCj4gY2hhbmdlIHRoZW0sIGl0J3MgYmV0dGVyIHRv
IHVwZGF0ZSB0aGUgc2VjcmV0IGtleSAodXBkYXRpbmcgdGhlIGtleSBpcw0KPiB1c3VhbGx5IGdv
b2QsIGFuZCB5b3UgZ2V0IHRoZSBhZGRyZXNzIGNoYW5nZSB5b3UgZXhwZWN0ZWQgYXMgYSBzaWRl
IA0KZWZmZWN0KS4NCg0KV2VsbKOsdGhlIG93bmVyIG1heSBub3Qgd2FudCB0byB1cGRhdGUgc2Vj
cmV0IGtleSBqdXN0IHRvIGNoYW5nZSBoZXIvaGlzIA0KaXAgd2l0aCB0aW1lIHBhc3NpbmcsIA0K
dXBkYXRpbmcgc2VjcmV0IGtleSBmcmVxdWVudGx5IGlzIGJvdGhlcnNvbWUuDQpBbiBvcHRpb25h
bCBkYXRlL3RpbWUgY2FuIGFkZCBtb3JlIGZsZXhpYmlsaXR5LCBpZiB0aGUgb3duZXIgd2lzaGVz
IHRvIA0Kb2J0YWluIGEgY29uc3RhbnQgSVAsIHRoZSBkYXRlL3RpbWUgY2FuIGJlIGlnbm9yZWQs
DQppZiB0aGUgb3duZXIgd2FudHMgdG8gY2hhbmdlIElQIG9uY2UgYSB5ZWFyLCB0aGUgZGF0ZS90
aW1lIGNhbiBiZSBjaG9zZW4gDQp0aGUgeWVhciwuLi4uLi4NCiANCg0KDQo+IA0KPiBUaGFua3Ms
DQo+IC0tIA0KPiBGZXJuYW5kbyBHb250DQo+IFNJNiBOZXR3b3Jrcw0KPiBlLW1haWw6IGZnb250
QHNpNm5ldHdvcmtzLmNvbQ0KPiBQR1AgRmluZ2VycHJpbnQ6IDY2NjYgMzFDNiBENDg0IDYzQjIg
OEZCMSBFM0M0IEFFMjUgMEQ1NSAxRDRFIDc0OTINCj4gDQo+IA0KPiANCj4gDQoNCg==
--=_alternative 0006D11448257B60_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5GZXJuYW5kbyBHb250ICZsdDtmZ29udEBzaTZu
ZXR3b3Jrcy5jb20mZ3Q7INC009oNCjIwMTMtMDUtMDIgMTY6NTQ6MzY6PGJyPg0KPGJyPg0KJmd0
OyBIaSwgU3VqaW5nLDxicj4NCiZndDsgPGJyPg0KJmd0OyBPbiAwNS8wMi8yMDEzIDA1OjE0IEFN
LCBTdWppbmcgWmhvdSB3cm90ZTo8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IEhhdmUg
eW91IGV2ZXIgY29uc2lkZXJlZCBhZGQgYSBkYXRlL3RpbWUgKG9wdGlvbmFsICkgcGFyYW1ldGVy
DQombmJzcDtpbjxicj4NCiZndDsgJmd0OyBnZW5lcmF0aW9uIG9mIHRoZSBuZXcgUklELDxicj4N
CiZndDsgJmd0OyBmb3IgZXhhbXBsZTo8YnI+DQomZ3Q7ICZndDsgJm5ic3A7UklEID0gRihQcmVm
aXgsIEludGVyZmFjZV9JbmRleCwgTmV0d29ya19JRCwgREFEX0NvdW50ZXIsRGF0ZS9UaW1lLDxi
cj4NCiZndDsgJmd0OyBzZWNyZXRfa2V5KSw8YnI+DQomZ3Q7ICZndDsgdGh1cyB3aWxsIHJlc3Vs
dCBpbiBkaWZmZXJlbnQgSUlEIGVhY2ggZGlmZmVyZW50IHllYXIsIGVhY2ggZGlmZmVyZW50PGJy
Pg0KJmd0OyAmZ3Q7IG1vbnRoLCBvciBldmVuPGJyPg0KJmd0OyAmZ3Q7IGRpZmZlcmVudCBkYXku
PGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBPZiBjb3Vyc2UsIHRoZSBJSUQgb3duZXIg
Y2FuIGNob29zZSB0byBjaGFuZ2Ugc2VjcmV0X2tleSAmbmJzcDt0bw0Kb2J0YWluPGJyPg0KJmd0
OyAmZ3Q7IGRpZmZlcmVudCBJSUQsPGJyPg0KJmd0OyAmZ3Q7IGJ1dCB3aXRoIGFuIGFkZGl0aW9u
IG9mIGRhdGUvdGltZSBvcHRpb24sIGl0IGlzIG1vcmUgZmxleGlibGUuPGJyPg0KJmd0OyA8YnI+
DQomZ3Q7IE5vdCByZWFsbHkuIFRoZSBhZGRyZXNzZXMgYXJlIG1lYW50IHRvIGJlIGNvbnN0YW50
LiBBbmQgaWYgeW91IHdhbnQNCnRvPGJyPg0KJmd0OyBjaGFuZ2UgdGhlbSwgaXQncyBiZXR0ZXIg
dG8gdXBkYXRlIHRoZSBzZWNyZXQga2V5ICh1cGRhdGluZyB0aGUga2V5DQppczxicj4NCiZndDsg
dXN1YWxseSBnb29kLCBhbmQgeW91IGdldCB0aGUgYWRkcmVzcyBjaGFuZ2UgeW91IGV4cGVjdGVk
IGFzIGEgc2lkZQ0KZWZmZWN0KS48YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0yPldlbGyjrHRoZSBvd25lciBtYXkgbm90IHdhbnQgdG8gdXBkYXRlIHNlY3JldCBrZXkNCmp1
c3QgdG8gY2hhbmdlIGhlci9oaXMgaXAgd2l0aCB0aW1lIHBhc3NpbmcsIDwvZm9udD48L3R0Pg0K
PGJyPjx0dD48Zm9udCBzaXplPTI+dXBkYXRpbmcgc2VjcmV0IGtleSBmcmVxdWVudGx5IGlzIGJv
dGhlcnNvbWUuPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5BbiBvcHRpb25hbCBk
YXRlL3RpbWUgY2FuIGFkZCBtb3JlIGZsZXhpYmlsaXR5LCBpZg0KdGhlIG93bmVyIHdpc2hlcyB0
byBvYnRhaW4gYSBjb25zdGFudCBJUCwgdGhlIGRhdGUvdGltZSBjYW4gYmUgaWdub3JlZCw8L2Zv
bnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPmlmIHRoZSBvd25lciB3YW50cyB0byBjaGFu
Z2UgSVAgb25jZSBhIHllYXIsIHRoZSBkYXRlL3RpbWUNCmNhbiBiZSBjaG9zZW4gdGhlIHllYXIs
Li4uLi4uPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mbmJzcDs8L2ZvbnQ+PC90
dD4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBUaGFu
a3MsPGJyPg0KJmd0OyAtLSA8YnI+DQomZ3Q7IEZlcm5hbmRvIEdvbnQ8YnI+DQomZ3Q7IFNJNiBO
ZXR3b3Jrczxicj4NCiZndDsgZS1tYWlsOiBmZ29udEBzaTZuZXR3b3Jrcy5jb208YnI+DQomZ3Q7
IFBHUCBGaW5nZXJwcmludDogNjY2NiAzMUM2IEQ0ODQgNjNCMiA4RkIxIEUzQzQgQUUyNSAwRDU1
IDFENEUgNzQ5Mjxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJy
Pg0KPC9mb250PjwvdHQ+DQo=
--=_alternative 0006D11448257B60_=--

From v6ops@globis.net  Thu May  2 23:49:47 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B627A21F93B6 for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 23:49:47 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmpUb32ErjYe for <ipv6@ietfa.amsl.com>; Thu,  2 May 2013 23:49:47 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8F921F93B4 for <ipv6@ietf.org>; Thu,  2 May 2013 23:49:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0BE8B8700B6; Fri,  3 May 2013 08:49:31 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBsh5KypTRZb; Fri,  3 May 2013 08:49:30 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id D38D5870085; Fri,  3 May 2013 08:49:30 +0200 (CEST)
Message-ID: <51835DF4.10506@globis.net>
Date: Fri, 03 May 2013 08:49:24 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: RE: Solutions to the problem with RFC 4941
References: <002601ce476c$297cae00$7c760a00$@rozanak.com> <5182C9F3.3040004@si6networks.com> <003801ce477d$0933b1f0$1b9b15d0$@rozanak.com>
In-Reply-To: <003801ce477d$0933b1f0$1b9b15d0$@rozanak.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'Fernando Gont' <fgont@si6networks.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 06:49:47 -0000

Hosnieh Rafiee wrote:
> Fernando,
>
> The purpose of your draft was not to obsolete or update RFC 4941 and you
> wanted to have your approach as an optional approach in parallel with that
> approach. So what is your problem with improving that document. It has
> nothing to do with your proposal. The people can accept or reject yours. I
> do not see any harmful behavior here as I also asked you 1000 times to
> update that rfc instead of having something new or in between two RFCs.
>
> Hosnieh

IMHO You are missing how the standards documents relate to each other.

The base problem is that RFC4862 (IPv6 Stateless Address Autoconfiguration) uses an IID defined in RFC4291 (IP Version 6 Addressing Architecture) Appendix A.

The fact that IID's are derived from EUI64 identifiers using a reversible transformation (RFC4291 Appendix A) means that the IID portion of an IPV6 SLAAC address can be used to infer privacy information about living persons carrying a particular device.

RFC4941 (Privacy Extensions for Stateless Address Autoconfiguration in IPv6) attempted to plug that gap.

RFC4941 did NOT directly update RFC4862 nor RFC4291: it was an optional extension to 4862. This update method was chosen so that RFC4941 was backwards compatible with existing implementations (goal #1 of 4941 Section 3). RFC4941 addresses outbound connections. But RFC4941 is an incomplete solution: nodes implementing RFC4941 still respond on the native SLAAC address generated by RFC4862.


draft-ietf-6man-stable-privacy-addresses plugs that vestigial problem with nodes responding on RFC4862 SLAAC generated addresses, whether RFC4941 has been implemented or not.


If draft-ietf-6man-stable-privacy-addresses updated RFC4941, it would miss out all implementations that did not implement (the optional) RFC4941, so those nodes would be left with a problem.

If draft-ietf-6man-stable-privacy-addresses updated RFC4862, it would mean all existing implementations would have to be mandatorily updated. There's no need for this to guarantee interoperability, and it would clearly be undesirable to deprecate existing implementations (which is why RFC4941 included goal #1).

In the future there may even be better alternatives to RFC4941 and draft-ietf-6man-stable-privacy-addresses.

IMHO These proposed solutions are all orthogonal, and are therefore best defined in independent standards (that use each other as normative references).

best regards,
RayH

<snip>


From brian.e.carpenter@gmail.com  Fri May  3 13:16:46 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6970521F8B8F for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 13:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.7
X-Spam-Level: 
X-Spam-Status: No, score=-102.7 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXaRMcN+20aN for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 13:16:45 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC5C21F8AF8 for <ipv6@ietf.org>; Fri,  3 May 2013 13:16:45 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id uo1so1069060pbc.34 for <ipv6@ietf.org>; Fri, 03 May 2013 13:16:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mTRVSpcAE7HJHuywm+yyiJ1MtEhzQV6mLmdSZq+lwKQ=; b=nAxRh1prNyUP40m7ZlrVqkIwNjd2DYS1Tg2tbLsRwaarDGf/+Fr32tzhf60HkeHd8A 9P95Bak+s8nGnIF3ky/Dy0YI5Ao7Uf1vFApXZdzWrIXQxndJ0/1Lmj/4OdHp3sRoK3F6 4jbiWS0qjZype2bxnXMCFnxy/oVlt60c/PM/SOOnSYtsCWrTGh1uxSZszDN8wHnrKmkU HFksyBGPYoSHKFWSVvDkql3MTPs00mEDLQ6hRrmtgygj1fUgHOxDZcDdi25nDezbPtkB N3zgbK743YA+kXclVJGBdmQGgsw4V+wqsUpC7CGAMofrpBQ3NDQCL4wAfjpwsgP+SlVP f/Vw==
X-Received: by 10.68.164.130 with SMTP id yq2mr15531794pbb.106.1367612204827;  Fri, 03 May 2013 13:16:44 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id gi2sm12884279pbb.2.2013.05.03.13.16.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 13:16:43 -0700 (PDT)
Message-ID: <51841B33.8070207@gmail.com>
Date: Sat, 04 May 2013 08:16:51 +1200
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: Ray Hunter <v6ops@globis.net>
Subject: Re: Solutions to the problem with RFC 4941
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net>
In-Reply-To: <51835DF4.10506@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'Fernando Gont' <fgont@si6networks.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 20:16:46 -0000

On 03/05/2013 18:49, Ray Hunter wrote:
> 
> Hosnieh Rafiee wrote:
>> Fernando,
>>
>> The purpose of your draft was not to obsolete or update RFC 4941 and you
>> wanted to have your approach as an optional approach in parallel with that
>> approach. So what is your problem with improving that document. It has
>> nothing to do with your proposal. The people can accept or reject yours. I
>> do not see any harmful behavior here as I also asked you 1000 times to
>> update that rfc instead of having something new or in between two RFCs.
>>
>> Hosnieh
> 
> IMHO You are missing how the standards documents relate to each other.
> 
> The base problem is that RFC4862 (IPv6 Stateless Address Autoconfiguration) uses an IID defined in RFC4291 (IP Version 6 Addressing Architecture) Appendix A.
> 
> The fact that IID's are derived from EUI64 identifiers using a reversible transformation (RFC4291 Appendix A) means that the IID portion of an IPV6 SLAAC address can be used to infer privacy information about living persons carrying a particular device.
> 
> RFC4941 (Privacy Extensions for Stateless Address Autoconfiguration in IPv6) attempted to plug that gap.
> 
> RFC4941 did NOT directly update RFC4862 nor RFC4291: it was an optional extension to 4862. This update method was chosen so that RFC4941 was backwards compatible with existing implementations (goal #1 of 4941 Section 3). RFC4941 addresses outbound connections. But RFC4941 is an incomplete solution: nodes implementing RFC4941 still respond on the native SLAAC address generated by RFC4862.
> 
> 
> draft-ietf-6man-stable-privacy-addresses plugs that vestigial problem with nodes responding on RFC4862 SLAAC generated addresses, whether RFC4941 has been implemented or not.
> 
> 
> If draft-ietf-6man-stable-privacy-addresses updated RFC4941, it would miss out all implementations that did not implement (the optional) RFC4941, so those nodes would be left with a problem.
> 
> If draft-ietf-6man-stable-privacy-addresses updated RFC4862, it would mean all existing implementations would have to be mandatorily updated. There's no need for this to guarantee interoperability, and it would clearly be undesirable to deprecate existing implementations (which is why RFC4941 included goal #1).
> 
> In the future there may even be better alternatives to RFC4941 and draft-ietf-6man-stable-privacy-addresses.
> 
> IMHO These proposed solutions are all orthogonal, and are therefore best defined in independent standards (that use each other as normative references).

Exactly. I think that draft-ietf-6man-ug clarifies this to some extent,
as a side-effect of clarifying the U/G bits. Would it be useful to add
an extra sentence in that draft, simply stating that a number of
independent methods for forming an IID can exist?

    Brian

From bob.hinden@gmail.com  Fri May  3 14:39:48 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDF721F90B1 for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 14:39:48 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6Et0OLqkSNe for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 14:39:47 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2D16C21F91B0 for <ipv6@ietf.org>; Fri,  3 May 2013 14:39:45 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id pb11so1888090veb.19 for <ipv6@ietf.org>; Fri, 03 May 2013 14:39:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=bakT/mUzjcaR1GzCxYws3mECdg3JCoEfOxRMyNQQELU=; b=oLUCqw3QiVETQTqv+bNia0OFopHGJseeYo2rgUxTcRNa6nM89G6UduhslZQrfGq43k TyeFnQwzEi25SLpJ6C0IIvdg4p96FJKNZr76aklqiGC5U+NKccyckNc6QtPybHSU6aaO fm8NaAvbfaeY3fZO5rWZvdEpaRa83Zn//apNELtlgT2W1RnnhW0RkY6VbQEoDpb2rDAV jqdo8Y3iWEDcaDoPQdnGFdGahpGxQ4rW8D0GIB7xz9Za/wy0LsJxpu6wSM3B37RQVUzc LHrCl58JnVHuWzW3A0OjqZcBEq+TJNieMln9c+V+vJrTxxw+DGFzYXEKNRMgUqUT9gVF w7IQ==
X-Received: by 10.52.230.164 with SMTP id sz4mr3661835vdc.118.1367617184526; Fri, 03 May 2013 14:39:44 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id y20sm10258663vds.7.2013.05.03.14.39.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 14:39:43 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Solutions to the problem with RFC 4941
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <51841B33.8070207@gmail.com>
Date: Fri, 3 May 2013 14:39:41 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <303E3892-D75D-4EF8-9AE9-C74D08956167@gmail.com>
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: Ray Hunter <v6ops@globis.net>, ipv6@ietf.org, Bob Hinden <bob.hinden@gmail.com>, 'Fernando Gont' <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 21:39:48 -0000

>>=20
>>=20
>> IMHO These proposed solutions are all orthogonal, and are therefore =
best defined in independent standards (that use each other as normative =
references).
>=20
> Exactly. I think that draft-ietf-6man-ug clarifies this to some =
extent,
> as a side-effect of clarifying the U/G bits. Would it be useful to add
> an extra sentence in that draft, simply stating that a number of
> independent methods for forming an IID can exist?

Perhaps also referencing Appendix A of RFC4291.

Bob



From ietf@rozanak.com  Fri May  3 15:16:16 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762FF21F8EEC for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 15:16:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJU7YhVwyk2B for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 15:16:11 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id C3C2B21F8BE9 for <ipv6@ietf.org>; Fri,  3 May 2013 15:16:06 -0700 (PDT)
Received: from kopoli (g225090005.adsl.alicedsl.de [92.225.90.5]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LqytP-1U4XHj3KQF-00dyXB; Fri, 03 May 2013 18:15:31 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com>
In-Reply-To: <51841B33.8070207@gmail.com>
Subject: RE: Solutions to the problem with RFC 4941
Date: Sat, 4 May 2013 00:15:19 +0200
Message-ID: <000d01ce484b$b7d72380$27856a80$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFkDy0wKnLTw64YzBf5YRtbXElpEgHU7crJAeG8740DCrJN0QFzjPMGmYbMAgA=
Content-Language: en-us
X-Provags-ID: V02:K0:qhOxlzVBm4BUrcrX17XeDLemkPsjeN6DKaCfje0C71p KuAx292ylOfHqA8P4KoNesmpGy9xlp17o8a3KOuplPvnbpuelS FSFcHzVEErEly1dQPhI3NAIZi/R1PkPGZ0ZgOTHjeDVqhgcQUu a2oyAbuQ/vM3Y9rD/bQQOD6kgk+oThoa5CEsUXDjs5sLNm28qj Q8QJjn/hOQ6IOftnv2HTo+q2lbPM79G7tDBH+7mun0RHXod3e0 SHsa5VILeSowpuTiRwm9rTRsuGKiO9kFH71izmVwidIQbp2PMI rlfaKHW3POoOE/67tNcF3qej2MnFBmem5vjP1ssltyIk6tMIVs MVB432ZMg1bhYe0NLODA=
Cc: 'Ray Hunter' <v6ops@globis.net>, ipv6@ietf.org, Fernando Gont <fgont@si6networks.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 22:16:16 -0000

> On 03/05/2013 18:49, Ray Hunter wrote:
> >
> > Hosnieh Rafiee wrote:
> >> Fernando,
> >>
> >> The purpose of your draft was not to obsolete or update RFC 4941 =
and
> >> you wanted to have your approach as an optional approach in =
parallel
> >> with that approach. So what is your problem with improving that
> >> document. It has nothing to do with your proposal. The people can
> >> accept or reject yours. I do not see any harmful behavior here as I
> >> also asked you 1000 times to update that rfc instead of having =
something
> new or in between two RFCs.
> >>
> >> Hosnieh
> >
> > IMHO You are missing how the standards documents relate to each =
other.
> >
> > The base problem is that RFC4862 (IPv6 Stateless Address =
Autoconfiguration)
> uses an IID defined in RFC4291 (IP Version 6 Addressing Architecture) =
Appendix
> A.
> >
> > The fact that IID's are derived from EUI64 identifiers using a =
reversible
> transformation (RFC4291 Appendix A) means that the IID portion of an =
IPV6
> SLAAC address can be used to infer privacy information about living =
persons
> carrying a particular device.
>=20
> >
> > RFC4941 (Privacy Extensions for Stateless Address Autoconfiguration =
in IPv6)
> attempted to plug that gap.
> >
> > RFC4941 did NOT directly update RFC4862 nor RFC4291: it was an =
optional
> extension to 4862. This update method was chosen so that RFC4941 was
> backwards compatible with existing implementations (goal #1 of 4941 =
Section
> 3). RFC4941 addresses outbound connections. But RFC4941 is an =
incomplete
> solution: nodes implementing RFC4941 still respond on the native SLAAC
> address generated by RFC4862.
> >
> >
> > draft-ietf-6man-stable-privacy-addresses plugs that vestigial =
problem with
> nodes responding on RFC4862 SLAAC generated addresses, whether RFC4941
> has been implemented or not.
> >
> >
> > If draft-ietf-6man-stable-privacy-addresses updated RFC4941, it =
would miss
> out all implementations that did not implement (the optional) RFC4941, =
so
> those nodes would be left with a problem.
> >
> > If draft-ietf-6man-stable-privacy-addresses updated RFC4862, it =
would mean
> all existing implementations would have to be mandatorily updated. =
There's no
> need for this to guarantee interoperability, and it would clearly be =
undesirable
> to deprecate existing implementations (which is why RFC4941 included =
goal
> #1).
> >
> > In the future there may even be better alternatives to RFC4941 and =
draft-ietf-
> 6man-stable-privacy-addresses.
> >
> > IMHO These proposed solutions are all orthogonal, and are therefore =
best
> defined in independent standards (that use each other as normative
> references).
>=20
> Exactly

I have already responded to Ray about this. FYI: I have included that =
response here.=20

"We are on the same page. Probably you read the following proposal. That =
email and his defensive reaction was because he thinks I want to have =
his proposal.=20
http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy-00
I wrote this yesterday after I found out that his purpose is to have a =
new optional approach. You can read it. The total text is two pages. It =
has nothing to do with his proposal. It is just an improvement on RFC =
4941. If you see any overlap let me know and I will remove it. My plan =
is not to steal his idea or his proposal but to just improve the current =
document."

My concern is also about privacy in a same network and I see it as an =
important issue. I think that by making a small update to RFC 4941, this =
will take care the problem. However, some people seem to think that this =
RFC does not maintain privacy very well. Finally, implementations or =
RFCs have never been as fast as new RFCs. This means nobody expects that =
vendors will immediately update their implementations with new options.  =
In the off list messages exchanged between us, I explained this and =
asked Fernando whether or not he wants to also cover this privacy issue =
or he does not still see it as a problem and wants to have a stable IID =
in the same network. If he covers, I have no more need for my proposal =
and I can withdraw it but if he does not, then I will keep it because =
many implementations would rather implement RFC 4941. So why not update =
it?

Hosnieh



From v6ops@globis.net  Fri May  3 15:16:38 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F35C521F8E8F for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 15:16:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EO3I23wa0XHh for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 15:16:37 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id F362E21F8F1F for <ipv6@ietf.org>; Fri,  3 May 2013 15:16:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 33FA18700B6; Sat,  4 May 2013 00:16:18 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0jxyZrz7xejW; Sat,  4 May 2013 00:16:18 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 12D4C870085; Sat,  4 May 2013 00:16:18 +0200 (CEST)
Message-ID: <5184372B.1080604@globis.net>
Date: Sat, 04 May 2013 00:16:11 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Solutions to the problem with RFC 4941
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com>
In-Reply-To: <51841B33.8070207@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'Fernando Gont' <fgont@si6networks.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 22:16:38 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 3 May 2013 22:16
>
> Exactly. I think that draft-ietf-6man-ug clarifies this to some extent,
> as a side-effect of clarifying the U/G bits. Would it be useful to add
> an extra sentence in that draft, simply stating that a number of
> independent methods for forming an IID can exist?
>
> Brian
Yes.

I think there's potentially a number of things to consider clarifying  :

1) There may be multiple independent methods for forming an IID.

2) These methods SHOULD NOT assume any exclusivity, either on a per
link, per interface, or per prefix basis.

3) DAD is the recognised mechanism for testing whether a unicast address
is unique.

4) I have a question regarding existing RFC4862 implementations, and a
very unlikely chain of events.

Quote: draft-ietf-6man-ug  states "Specifications of other forms of
64-bit IID MUST specify how all 64 bits are set, but need not treat the
"u" and "g" bits in any special way." OK current text of
draft-ietf-6man-stable-privacy-addresses is compliant with that.

What happens in the unlikely event that these new mechanisms for
creating an IID (such as draft-ietf-6man-stable-privacy-addresses) and
which ignore setting u/g bits, cause a DAD clash with existing
link-local addresses created compliant to RFC 4862 (IPv6 Stateless
Address Autoconfiguration) especially regarding Section 5.4.5 (When
Duplicate Address Detection Fails), which DOES rely on the u bit?

4862 states: "On the other hand, if the duplicate link-local address is
not formed from an interface identifier based on the hardware address,
which is supposed to be uniquely assigned, IP operation on the interface
MAY be continued."

How would the node using 4862+4291 know the difference whether the
duplicate was caused by another node running 4862+4291 with a duplicate
MAC/EUI-64 hardware address, or because of
draft-ietf-6man-stable-privacy-addresses or some other mechanism?

Presumably by checking the incoming DAD probe NS packet to check if the
transform of the EUI-64 / link-layer hardware source address matches the
interface identifier stripped from the Target Address?

Do all existing 4862 implementations perform this check before disabling
IPv6 processing on the interface?

I think that this additional check is a candidate for a SHOULD, rather
than a MAY, and also needs highlighting in draft-ietf-6man-ug .

regards,
RayH

From markzzzsmith@yahoo.com.au  Fri May  3 16:43:58 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE48321F8E99 for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 16:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aF++22aUfuGA for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 16:43:53 -0700 (PDT)
Received: from nm32-vm6.bullet.mail.bf1.yahoo.com (nm32-vm6.bullet.mail.bf1.yahoo.com [72.30.239.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1B64821F8E34 for <ipv6@ietf.org>; Fri,  3 May 2013 16:43:52 -0700 (PDT)
Received: from [98.139.212.146] by nm32.bullet.mail.bf1.yahoo.com with NNFMP; 03 May 2013 23:43:52 -0000
Received: from [98.139.212.200] by tm3.bullet.mail.bf1.yahoo.com with NNFMP; 03 May 2013 23:43:52 -0000
Received: from [127.0.0.1] by omp1009.mail.bf1.yahoo.com with NNFMP; 03 May 2013 23:43:52 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 348231.51082.bm@omp1009.mail.bf1.yahoo.com
Received: (qmail 64337 invoked by uid 60001); 3 May 2013 23:43:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1367624632; bh=qzpkSyZzUdzpLnB87O8aJTg5CR6gB+vtPrc/u4GCUzI=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=vdfEDUU4807KAQvqiAgxFxuklEBbnDnX3xpH5p63ektysOmt7jPRGvcufin3r8S+u5W7qk266+vqMgmlG+gu0l5HsjuLgCTOfYOSz/cXjzkRlzYh9qNu056rwm0A1DckzYcwFmuznZg7M8gKacR9Efevuk1o80sgAYYJxEc8++k=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=MFc1DZNnVQcUF4towFd+pGZckj2kXALiOXryc9T5mMghPbtpRAsnnBpA/Jk/aAFG/rZVdeXCrGPyKfOAylsksrEmT3P/ihM4P8Agey2Y2Nd6jQVV1OoFdxPgdtGumwqAFXQ2YJYSZLu2GQ8zydbsdkkgFNtPeCRTT/m7IH6EMGg=;
X-YMail-OSG: V.QhTLYVM1le5eMc_1K_9Vs2QrG4z0hEZYVQo.1gUacamTh A1vtTM4sUZkQJulR_QrkmV318f87pTsU.X40bbCyYrJZ7Q9vs3SKlBqwGyOI DPYnxRIJBUw0ngMfDiJNpjagviQE32ltmbpkeNM3mZCow1KKCqX1qJuj73Zy JP6AvWydozMTyQpd4.fUfkje4bg584TkKTG4CDk6teY_TMoU27rupGQ9KF8W gPIJnFmkIQT6V8bpdGqMBOFa6Yvwj23_7tPeKv_d5zeNr9Ni5vSoLe4IFy6n v09dwDEIoEjbqJr3IhAGwiRrISMEmkhyoZekPJHRFc2TGuD7oVPkvoA0qYyK QIDgRwjYavzM6Ku2ZoVLYqhFgUKhelyWSn.mY1pQFUZ2kmD2fz5o.8PEPN_i zYWAyedeLz9_MHJZ2Cxe.9qVzUryhISpuX.4V_B0iI0Exn8Eh73hiJXsSYqd EYgfa5Bqbm2cb_cld0f1_DdRe4noVkjtqoBAZ1BNla.yo7SkQaKWqrRX5uFt htdg.XO3__SbKAv7vpDYvBKzZR8zyR8Ntj0Q-
Received: from [150.101.221.237] by web142503.mail.bf1.yahoo.com via HTTP; Fri, 03 May 2013 16:43:50 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBSYXkgSHVudGVyIDx2Nm9wc0BnbG9iaXMubmV0Pgo.IFRvOiBCcmlhbiBFIENhcnBlbnRlciA8YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPgo.IENjOiAnRmVybmFuZG8gR29udCcgPGZnb250QHNpNm5ldHdvcmtzLmNvbT47IGlwdjZAaWV0Zi5vcmcKPiBTZW50OiBTYXR1cmRheSwgNCBNYXkgMjAxMyA4OjE2IEFNCj4gU3ViamVjdDogUmU6IFNvbHV0aW9ucyB0byB0aGUgcHJvYmxlbSB3aXRoIFJGQyA0OTQxCj4gCj4.ICBCcmlhbiABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.141.536
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com> <5184372B.1080604@globis.net>
Message-ID: <1367624630.59920.YahooMailNeo@web142503.mail.bf1.yahoo.com>
Date: Fri, 3 May 2013 16:43:50 -0700 (PDT)
From: Mark Smith <markzzzsmith@yahoo.com.au>
Subject: Re: Solutions to the problem with RFC 4941
To: Ray Hunter <v6ops@globis.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <5184372B.1080604@globis.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 'Fernando Gont' <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 03 May 2013 23:43:59 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: Ray Hunter <v6ops@globis=
.net>=0A> To: Brian E Carpenter <brian.e.carpenter@gmail.com>=0A> Cc: 'Fern=
ando Gont' <fgont@si6networks.com>; ipv6@ietf.org=0A> Sent: Saturday, 4 May=
 2013 8:16 AM=0A> Subject: Re: Solutions to the problem with RFC 4941=0A> =
=0A>>  Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>=0A>>  3 May 2=
013 22:16=0A>> =0A>>  Exactly. I think that draft-ietf-6man-ug clarifies th=
is to some extent,=0A>>  as a side-effect of clarifying the U/G bits. Would=
 it be useful to add=0A>>  an extra sentence in that draft, simply stating =
that a number of=0A>>  independent methods for forming an IID can exist?=0A=
>> =0A>>  Brian=0A> Yes.=0A> =0A> I think there's potentially a number of t=
hings to consider clarifying=A0 :=0A> =0A> 1) There may be multiple indepen=
dent methods for forming an IID.=0A>=A0=0A=0AI think there are rather than =
may be, as static manually configured addresses would be a method of formin=
g an IID, and I understand they were the motivation for inverting the U bit=
.=0A=0A> 2) These methods SHOULD NOT assume any exclusivity, either on a pe=
r=0A=0A> link, per interface, or per prefix basis.=0A>=A0=0A> 3) DAD is the=
 recognised mechanism for testing whether a unicast address=0A=0A> is uniqu=
e.=0A>=A0=0A=0AIt may also be worth pointing out that more generally, the p=
refix length doesn't assure the presence of the other addresses within the =
prefix, and that the only way to test for their presence is to probe for th=
em them. For example, an address with a /127 prefix length on one end of a =
link doesn't ensure that the other address within the subnet either has bee=
n configured at the other end of the link, or isn't a duplicate of the loca=
l address. So neighbor presence discovery and DAD really need to take place=
 for all addresses, regardless of the prefix length.=0A=0AThis might also m=
ake it clearer that IPv6 addresses, when derived from link layer addresses,=
 aren't tightly bound to them, and that deriving them from the link-layer a=
ddress has been for operational convenience i.e., autoconfiguration, rather=
 than a requirement (something I struggled with for a while after having ex=
perienced Novell IPX, where link-layer addresses were also used as node add=
resses, and there was no neighbor discovery/address resolution protocol, as=
 the layer 3 node portion of address was directly copied into the link-laye=
r destination address at the last hop).=0A=0A<snip>=0A=0ARegards,=0AMark.

From internet-drafts@ietf.org  Fri May  3 17:33:38 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC1321F8F4F; Fri,  3 May 2013 17:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.584
X-Spam-Level: 
X-Spam-Status: No, score=-98.584 tagged_above=-999 required=5 tests=[AWL=-2.267, BAYES_00=-2.599, FH_HAS_XAIMC=2.696, HELO_MISMATCH_COM=0.553, RCVD_IN_XBL=3.033, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1OupKOacZjpI; Fri,  3 May 2013 17:33:33 -0700 (PDT)
Received: from jlonline.com (pip46.ptt.js.cn [61.155.13.222]) by ietfa.amsl.com (Postfix) with SMTP id 5A5D821F8E2C; Fri,  3 May 2013 17:33:17 -0700 (PDT)
Received: from jlonline.com([10.100.0.22]) by ptt.js.cn(AIMC 4.0.0.0) with SMTP id jm25184668d; Sat, 04 May 2013 08:39:06 +0800
Received: from mail.ietf.org([12.22.58.30]) by ptt.js.cn(AIMC 4.0.0.0) with SMTP id jm0517f80d7; Tue, 30 Apr 2013 14:37:00 +0800
Received: from mail.ietf.org([12.22.58.30]) by ptt.js.cn(AIMC 4.0.0.0) with SMTP id AISP action; Tue, 30 Apr 2013 14:36:54 +0800
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EC9C921F9C47; Mon, 29 Apr 2013 23:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1367303445; bh=b9vNYwF4l8iZoPwaqeEgic+cQr86lvz1QYCfQ5h/j4k=; h=MIME-Version:From:To:Subject:Message-ID:Date:Cc:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=KzDdKWHK1zvcGuU2n+aKriZ6nN3sMuz9+cU2zBXp5/bRSfakqLhHcPj0G6L1c5WnB MaYNcxlEwZpus4fqHcMrtSpIg1RV8Hm7szrN04OvdOdNMZsobDG81nUHlmWGLN41+H /G5JRpcOhwdO3SByGrWw4hwOgmotG422RJcccgsQ=
X-Original-To: i-d-announce@ietfa.amsl.com
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7867221F9C57; Mon, 29 Apr 2013 23:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wk7XZVAOyHhx; Mon, 29 Apr 2013 23:30:40 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E7321F9C3C; Mon, 29 Apr 2013 23:30:39 -0700 (PDT)
MIME-Version: 1.0
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-addr-select-opt-10.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p4
Message-ID: <20130430063039.18910.18065.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2013 23:30:39 -0700
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: i-d-announce-bounces@ietf.org
X-AIMC-Msg-ID: fw0LE74B
X-AIMC-AUTH: (null)
X-AIMC-MAILFROM: internet-drafts@ietf.org
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
Reply-To: internet-drafts@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 00:33:38 -0000

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

	Title           : Distributing Address Selection Policy using DHCPv6
	Author(s)       : Arifumi Matsumoto
                          Tomohiro Fujisaki
                          Tim Chown
	Filename        : draft-ietf-6man-addr-select-opt-10.txt
	Pages           : 10
	Date            : 2013-04-29

Abstract:
   RFC 6724 defines default address selection mechanisms for IPv6 that
   allow nodes to select an appropriate address when faced with multiple
   source and/or destination addresses to choose between.  The RFC 6724
   allowed for the future definition of methods to administratively
   configure the address selection policy information.  This document
   defines a new DHCPv6 option for such configuration, allowing a site
   administrator to distribute address selection policy overriding the
   default address selection parameters and policy table, and thus
   control the address selection behavior of nodes in their site.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-addr-select-opt

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-addr-select-opt-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-addr-select-opt-10


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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From fgont@si6networks.com  Fri May  3 18:58:21 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F9721F8FA5 for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 18:58: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8SiU7gR08sO for <ipv6@ietfa.amsl.com>; Fri,  3 May 2013 18:58:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3E21421F8FA4 for <ipv6@ietf.org>; Fri,  3 May 2013 18:58:19 -0700 (PDT)
Received: from [186.134.26.236] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UYRjl-0004X5-TS; Sat, 04 May 2013 03:58:10 +0200
Message-ID: <5184576C.3060907@si6networks.com>
Date: Fri, 03 May 2013 21:33:48 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: Solutions to the problem with RFC 4941
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com> <000d01ce484b$b7d72380$27856a80$@rozanak.com>
In-Reply-To: <000d01ce484b$b7d72380$27856a80$@rozanak.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'Ray Hunter' <v6ops@globis.net>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 01:58:21 -0000

On 05/03/2013 07:15 PM, Hosnieh Rafiee wrote:
> 
> "We are on the same page. Probably you read the following proposal.
> That email and his defensive reaction was because he thinks I want to
> have his proposal.

My reaction (frustration) is because you make assertions such as this.
e.g. how can you possibly know what I *think*?

In other emails you have not only systematically ignored my responses,
but also made statements like "you said X", when I never said such a thing.

That's where my response came from.

Besides, many times, others and myself have tried to explain that as
with most thinks in the engineering field, there are trade-offs. You
argue that draft-ietf-6man-stable-privacy-addresses doesn't have any
impact on privacy. But me and others have explained otherwise. And I
have even provided a reference to a document posted by the IAB which
essentially argues in favor of producing stable IIDs based on a hash (in
replacement of the embedded MAC address), and also explains why RFC4941
addresses are employed in addition to stable addresses (otherwise,
applications that rely on stable addresses would break).

Eventually, I guess that we need to agree to disagree on these technical
matters (but even then I'd still appreciate that you do not statements
on my behalf based on things I've not said or thought).

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





From ietf@rozanak.com  Sat May  4 00:18:54 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716FD21F965D for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 00:18:54 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ieMG0wigVn+o for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 00:18:49 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id A46DB21F964C for <ipv6@ietf.org>; Sat,  4 May 2013 00:18:49 -0700 (PDT)
Received: from kopoli (g226057156.adsl.alicedsl.de [92.226.57.156]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MFLYq-1UkZRL3zHw-00F3tl; Sat, 04 May 2013 03:18:45 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Fernando Gont'" <fgont@si6networks.com>
References: <002601ce476c$297cae00$7c760a00$@rozanak.com>	<5182C9F3.3040004@si6networks.com>	<003801ce477d$0933b1f0$1b9b15d0$@rozanak.com> <51835DF4.10506@globis.net> <51841B33.8070207@gmail.com> <000d01ce484b$b7d72380$27856a80$@rozanak.com> <5184576C.3060907@si6networks.com>
In-Reply-To: <5184576C.3060907@si6networks.com>
Subject: RE: Solutions to the problem with RFC 4941
Date: Sat, 4 May 2013 09:18:35 +0200
Message-ID: <000001ce4897$9b9cd010$d2d67030$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFkDy0wKnLTw64YzBf5YRtbXElpEgHU7crJAeG8740DCrJN0QFzjPMGAb2HLjsCcGmvtJll3LRA
Content-Language: en-us
X-Provags-ID: V02:K0:LGr0y5BaMXAOAjHlwkSWjrkGAiMH36ME2j4eD+nbgOd S0uv4qj2OYzyBhFS3tDcjLnrogwC3R3x5q84hWeytnaEolVeyK d9gbRst0mpcyemmpVIL/FSYUGWaAh+yEJ20pu2NYZi6oNOVdLu THsGgcBqAhYWGNQjnnnCp0ALx2pktIQn+gAXJmEyRfxjuKNOeX ZK1BNspwnSvEm9lt4nx6Dn2qbV1+ujF8vsG5N/CQsUIOTNq/gS aTluiN3s1+MgzhbpqXhyJSDWbovV/sPHS49z4do4u/bzZLejiN m7S8LUIuNinKaj67kSS7ahjkqWbsa05HtnwHe79Nel3WLXzZhq vtVKU7rmAdZ6Uv1QZuas=
Cc: 'Ray Hunter' <v6ops@globis.net>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 07:18:54 -0000

> In other emails=20
>"you said X", when I never said such a thing.

First, I did not talk on behalf of you. Probably there is =
misunderstanding in the meaning of the following sentence in my last =
email (not emails).

>Since Fernando=E2=80=99s proposal is not going to solve the current =
problem with RFC 4941, I have suggested to him, on several occasions, =
that he resolve this problem so that the node's privacy will be better =
>protected but he ignored this suggestion and claiming that his purpose =
is different.

The meaning of this sentence, if there was misunderstanding: (Based on =
your responses in the list to me) You are not planning to update this =
document for whatever reason that you have or explained AND you want to =
have your draft as one of " several optional standards" as others =
mentioned.=20

http://www.ietf.org/mail-archive/web/ipv6/current/msg16862.html=20
http://www.ietf.org/mail-archive/web/ipv6/current/msg16859.html
=20
http://www.ietf.org/mail-archive/web/ipv6/current/msg17710.html

Privacy as I defined it before :
" The information in my bank account is my private information and as =
such should be known to no one. This is privacy., i.e., the information =
that I do not want to be shared with anyone without my permission: it is =
so private for me. But by having the same IP address for a long period =
of time can lead to the leakage of private information. This is why I =
said that changing the IID from the same network would help. I did not =
say that the RFC Privacy Extension is perfect. (Nothing in life is =
perfect. We just strive for perfection but never really attain it.)"

"Why I think that privacy is more an application layer (and in other =
posts I said, upper layer than IP) issue than an issue with the other =
layers an why the IP layer might  cause problem in this vain. As an =
example suppose a criminal follows someone with the name A, Using his IP =
address to follow A he can then find his location and decide on a =
location for committing his misdeed, like killing him. Then the IP =
address proved harmful to his privacy because it exposed information =
about him to the this criminal. In another example A travels a lot. If a =
robber follows his IP and knows that he is not at home, he can easily =
ransack his house. This is again the IP layer causing harm to privacy."

-My concern that I repeated in my posts: If I stay in an x network for =
more than certain period of time I might be a victim of privacy attacks. =
The risk of attack depends on the X time.=20
-Having stable address helps: Depends on X. if it is short, Yes, but if =
I am permanently in that network and router prefix does not change, NO.=20
-Possible solution: Change my IP address within the same network too.
-How: set a lifetime to my IP address. =20

My second concern: moving from and to network a to x. Question: Do I =
have the same IP in each of these networks?
If yes, I might be a victim. =20
- Having stable address helps: If I have the same IP every time I enter =
to these networks and/or I stay in each networks more than x time, It =
might not help as the attacker have a chance to still correlate my =
information to my IP.=20

Is RFC 4941 can be of any help?
It might be but needs some improvements.=20

@ list: If you think RFC 4941 not really helps for privacy, why do you =
concern about implementations that use this RFC and talking about =
backward compatibility?=20
In my opinion, If I am a vendor and I see there is no update on a RFC, I =
assume that it is not a serious concern so when the new optional RFCs do =
not address my concerns, I still try to implement it for any new OS =
(using the same old code from my old OS).

@Fernando: If you are so frustrated (for misunderstanding or whatever =
reasons) Why don't you bring your boxing gloves to Frankfurt main? :-)  =
as I noticed you are speaker there as well as I. We can enjoy fighting =
there :-)



From ietf@rozanak.com  Sat May  4 12:17:50 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFDCD21F95E9 for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 12:17:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OH-4RHlM37S4 for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 12:17:46 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 0A88921F905C for <ipv6@ietf.org>; Sat,  4 May 2013 12:17:46 -0700 (PDT)
Received: from kopoli (g226057156.adsl.alicedsl.de [92.226.57.156]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MbfCP-1UorMw0aiD-00J0yg; Sat, 04 May 2013 15:17:44 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
Subject: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Date: Sat, 4 May 2013 21:17:37 +0200
Message-ID: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5I+/b+Jc4HWuodQNyU/er3ftfgrw==
Content-Language: en-us
X-Provags-ID: V02:K0:+a527diGkMpRl21WWpSm/Q9gwYoYMNpRGpX4jP7n7Vm D+r4txCIoYNDrapNUdepEphBVzaX4yx2N77Wj1iEoNlkJ9ieib pJpXPOsnd0BHOeX5aH2UEpxK6RsfGOmU6Ubt/hNwmwD+UtB50h U5KVRyLScNbAU4xx01FUI1q3Y8E3Q6A5oSLUTU019zLoKhkHei UabPGrPyf4tCSh+cYb+U+w/OgE60EMQLn01BDja9fXaNAYu8at QxNSITJGapJQc2BYE12cvFabzuKU3hiRz9bumB6ilFlhh+jq83 TSh/uP9YwFDu0b0rLBz5Hl2uHbLmZKu30i1dRTPxR/clORIhhV ja+/51TwTS/COpqjzZVg=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 19:17:50 -0000

Has anybody had a chance to look at this draft
(http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy )? Any comments?
The aim of this draft is to adapt the current RFC to the latest European law
http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=en and to
accommodate the needs of customers with relation to the new law for a long
term period. The purpose is to allow users to choose their means to the
privacy and anonymity within a network as well as across networks. 

There is still an option of merging this draft with other drafts, that
address the issue of allowing users to set the lifetime of the IP address
during the installation or an option to set it by the users, if people on
the mailing list thinks it would be useful. 
Share your technical ideas.

Thanks,
Best,
Hosnieh




From brian.e.carpenter@gmail.com  Sat May  4 12:54:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6AB21F9662 for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 12:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.799
X-Spam-Level: 
X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o75WcoVQlOuk for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 12:54:39 -0700 (PDT)
Received: from mail-da0-x22a.google.com (mail-da0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D907921F8D94 for <ipv6@ietf.org>; Sat,  4 May 2013 12:54:39 -0700 (PDT)
Received: by mail-da0-f42.google.com with SMTP id r6so1272625dad.29 for <ipv6@ietf.org>; Sat, 04 May 2013 12:54:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tTAhB3zE95PS6/Aw7jFHlLS/6v+zQ9LSBIvCvpsj/P8=; b=PJjan9T7Mf0gsuXSLETjgWbL1JB1ih1V2a+drdnTEBQLKPdBKLWDvtT/iYcWA/bm4O ZAddqL1dYMLVkHz53HyfDNXV3XdZhYxhjbrHN+e9V+13Ehig7562yuRBgOXcXF9BfIG7 qjNsHtlBN0p5GvVByvPL5HGIysihfW4sY9nx3gHV8YdafikCU0VliIz5s3wvGBZH0btc wlL4bti3ldbGeDxCjkje8atgq949MYC2Mz3D4kvXsTP7AgKjcN+nKbqGTwW2JFys1S/r k4RQZ3/lvhMGnSg8dK9VI3bheY3U+wB1cEXzCSiT8ai2y7g3plKp3on3U/exn79L3Ycc CNFQ==
X-Received: by 10.66.20.7 with SMTP id j7mr20312427pae.142.1367697279660; Sat, 04 May 2013 12:54:39 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id kv2sm16596546pbc.28.2013.05.04.12.54.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 May 2013 12:54:38 -0700 (PDT)
Message-ID: <51856775.9090809@gmail.com>
Date: Sun, 05 May 2013 07:54:29 +1200
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: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>
In-Reply-To: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 19:54:40 -0000

> The aim of this draft is to adapt the current RFC to the latest European law
> http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=en 

Can you please identify the exact clause in the proposed EU regulation
that would require pseudo-random IIDs that change when the subnet
prefix changes?

All I can see in the EU PR release is a hint that "your computer's IP
address" might be considered to be personal data, and might therefore
be covered by privacy regulations.

Even if you can identify the exact clause, we don't normally take
account of specific national or regional legislation in IETF standards.
I think the scarecrow references to EU regulation should be deleted.

It would be more useful if the draft contained a threat analysis.
As far as I can see, if I set the RFC 4941 timer to a reasonable
value, my IID will change much more often than my subnet prefix.

I don't understand the concern about CGA. A network that uses SEND
is highly unlikely to allow RFC 4941.

   Brian

From ietf@rozanak.com  Sat May  4 13:48:37 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92A821F9680 for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 13:48:37 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t1JaEc2qMRsk for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 13:48:33 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id DBB7A21F9679 for <ipv6@ietf.org>; Sat,  4 May 2013 13:48:32 -0700 (PDT)
Received: from kopoli (g226057156.adsl.alicedsl.de [92.226.57.156]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0M700b-1UKCpV45n3-00wi3j; Sat, 04 May 2013 16:48:31 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <51856775.9090809@gmail.com>
In-Reply-To: <51856775.9090809@gmail.com>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Date: Sat, 4 May 2013 22:48:23 +0200
Message-ID: <000001ce4908$bb574db0$3205e910$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEIl8rTHwJkn2ThdH61FAwJnuwKbAIHD3r6mnCiu5A=
Content-Language: en-us
X-Provags-ID: V02:K0:nHQDs2DNLjZs6G7yu8tTYpQ4+AqLxlc27gIdn2vVUAR xde2yRdD2zNcM4w+LZ0k81PE8meZw8wAI8yDDNXo23K66YmIMw 3oR7hRfbbclklezkRsuAR0cAn6SFy4yvjiyo+k4fYvlEoUHbb8 tF5Pjhjp9mLEpYUVqyOKSjFKlyF2dEBqF5Jv2BD2q2yOM3R06D beyVZ2UkZ/CbK8BnjRQ4qovVDdNIbtyfEqTUQ89ncpVejaZgLD BQS8x2hyrryHCHB7NB+IhD9+G/I56H68/SbSkU6ObVPgVarnDj oZgF7dqbKCYm+Z4K8CUcIPc/Wrspme38DbXa++6QAONTCEKRFY DQKTtRE8Nps8lMPQUlD8=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 04 May 2013 20:48:38 -0000

>=20
> > The aim of this draft is to adapt the current RFC to the latest
> > European law
> > http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=3Den
>=20
> Can you please identify the exact clause in the proposed EU regulation =
that
> would require pseudo-random IIDs that change when the subnet prefix
> changes?

Randomization of IID is my proposed solution to the privacy issues =
discussed in EU regulation.=20
"Personal data is any information relating to an individual, whether it =
relates to his or her private, professional or public life. It can be =
anything from a name, a photo, an email address, bank details, your =
posts on social networking websites, your medical information, or your =
computer's IP address. The EU Charter of Fundamental Rights says that =
everyone has the right to personal data protection in all aspects of =
life: at home, at work, whilst shopping, when receiving medical =
treatment, at a police station or on the Internet."
Not changing the IID after a period of time gives attackers the ability =
to invade an entity's privacy.

> All I can see in the EU PR release is a hint that "your computer's IP =
address"
> might be considered to be personal data, and might therefore be =
covered by
> privacy regulations.
> Even if you can identify the exact clause, we don't normally take =
account of
> specific national or regional legislation in IETF standards.
> I think the scarecrow references to EU regulation should be deleted.


This law was a reference for me as a meaning of privacy. I did not want =
to use my personal opinion of the definition of privacy. I will delete =
that reference if there is no need for it.


> It would be more useful if the draft contained a threat analysis.
> As far as I can see, if I set the RFC 4941 timer to a reasonable =
value, my IID will
> change much more often than my subnet prefix.

I will add this section, thanks

> I don't understand the concern about CGA. A network that uses SEND is =
highly
> unlikely to allow RFC 4941.

In that RFC is an explanation stating that there is a possibility for =
using CGA to generate a higher randomized IID but there is nothing =
mentioned on how to accomplish this. Here I used a modified version of =
that algorithm without any public/private key because here we want to =
address the privacy issues and not security issues.

Thanks,=20
Hosnieh





From markzzzsmith@yahoo.com.au  Sat May  4 18:45:29 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8DDC21F96C1 for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 18:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tt2mCBcjb+-I for <ipv6@ietfa.amsl.com>; Sat,  4 May 2013 18:45:24 -0700 (PDT)
Received: from nm7.bullet.mail.bf1.yahoo.com (nm7.bullet.mail.bf1.yahoo.com [98.139.212.166]) by ietfa.amsl.com (Postfix) with SMTP id 8037721F8B60 for <ipv6@ietf.org>; Sat,  4 May 2013 18:45:24 -0700 (PDT)
Received: from [98.139.215.140] by nm7.bullet.mail.bf1.yahoo.com with NNFMP; 05 May 2013 01:45:23 -0000
Received: from [98.139.212.214] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 05 May 2013 01:45:23 -0000
Received: from [127.0.0.1] by omp1023.mail.bf1.yahoo.com with NNFMP; 05 May 2013 01:45:23 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 889244.59201.bm@omp1023.mail.bf1.yahoo.com
Received: (qmail 12434 invoked by uid 60001); 5 May 2013 01:45:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1367718323; bh=trIxWILoUe5RUTeuB6gKoVpUFHwL9i0plwQUfcHvRFg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=cDMpcbf083PxCcoVIbiwd7504wou7GU6wDTP4bpuIetp7aHEdQPd0Ozpyf3Le2sTN+dJ3Tyta+LK2m4uDNpsted7GurJdLWOEAX3/aAz3lO2EfZTUQRSi+xFJN1W9SzOxG/iKB1eQeaBRfGPdmwgVNqDUfdml3+16uFyZA/Sld0=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FFHqq8kp09cqMnRhq0SbGQFqFDXPVRzy5xWm5QsDHT4NUXMyHCU6lmgMKAZ5YhjrTZXFk3VfCFqzVJtvYvgzicOGpHI9bxbtyqJofPMd606Cp6p/h3ucouwh/o8WYVN7CE8JUg1LqQIUOgpUG1czncrNhwqiRO4RMrGzEmO3h/U=;
X-YMail-OSG: 1vSC0woVM1n_pQzVO.dZ56gD.c7MGp8KJ.qfqcs_SmO50qu 01tE5yX4zIyi32uhIvERQsJ9h3AxOfFXhbp86T_UrQ1kCIsVr1Scs2_G1p9F JKus5YOaTOM9eAgJ8oYZRy_5yiBdFXfQWlNUVazy0hrwzoFt4GtpqsOdCFDi 9nyYbn7OEv9WKWDSt.icks3OzAHFVQMmJzbqGnC92amf1hctwXjLLMW6GQG7 0aO_wuJjcNJRkgkTJRC1kuAXi2n2UE3m7roiu8.7gRapO_vQGizdq21v7Bix dDv3RpuymQi6z.51s7pPxKauyn0K3D17_gW2q9tPW0UycWXjTqESsNAjiCY1 OqF.CaVWZVWMIz0fmbnYCsju1GgUZmtcDJKe7DvrEP.jOxF0pcSvccYI42e1 EZK2I8VEXs9O8gPFxka4TT9O2.ILR5Yp1kC4FZ4TKSFFgs9Tc30V9HIRMOfN z4mi_.9bNmvxdq96tJciFPNNbXQ.RVDeoA0XURL6SjPfQ4BjA5YlJOQ6xidf jIcQVRms01QenYk_Zg1Cr12yDofKF.P.Z_URCD1pgaw.4Gig8XKe0aWZ4P_W nQdo7GZ8kc53qP4LSoqQGsCQTWM4sqv4Pa03MS2lL4JX3.7LwxsHBj94p71J YzLlPV6_YsPw3TLl8bMpouRacQ3CCGKAO0SF8cqtkN_BF0vWrJqX0XEkH2_3 m0KzDTVnvsRcOECHYmcmpclWRkW1jSKVsRujoLhA-
Received: from [150.101.221.237] by web142504.mail.bf1.yahoo.com via HTTP; Sat, 04 May 2013 18:45:23 PDT
X-Rocket-MIMEInfo: 002.001, SGksCgpJJ3ZlIGhhZCBhIHZlcnkgYnJpZWYgbG9vaywgYmVjYXVzZSB0aGVyZSB3YXMgb25lIHNwZWNpZmljIHRoaW5nIEkgd2FzIGxvb2tpbmcgZm9yLCBhbmQgaXQgZG9lc24ndCBzZWVtIHRvIGJlIHRoZXJlLgoKQWRkcmVzc2VzL0lJRHMgaGF2ZSB0byBsYXN0IGF0IGxlYXN0IGFzIGxvbmcgYXMgdGhlIHRyYW5zcG9ydCBsYXllci9hcHBsaWNhdGlvbiBjb25uZWN0aW9ucyBhcmUgdXNpbmcgdGhlbSwgdW5sZXNzIHRoZSB0cmFuc3BvcnQgbGF5ZXIvYXBwbGljYXRpb24gY29ubmVjdGlvbiB0YWtlcyBvd24BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.141.536
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>
Message-ID: <1367718323.3497.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Date: Sat, 4 May 2013 18:45:23 -0700 (PDT)
From: Mark Smith <markzzzsmith@yahoo.com.au>
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
To: Hosnieh Rafiee <ietf@rozanak.com>, "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>
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.12
Precedence: list
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 May 2013 01:45:29 -0000

Hi,=0A=0AI've had a very brief look, because there was one specific thing I=
 was looking for, and it doesn't seem to be there.=0A=0AAddresses/IIDs have=
 to last at least as long as the transport layer/application connections ar=
e using them, unless the transport layer/application connection takes owner=
ship of dealing with addresses that might "change=A0underneath them". In ge=
neral, larger preferred and valid lifetimes (e.g, measured in hours or grea=
ter) and fairly stable identifiers are intended to avoid transport layer pr=
otocols/applications having to deal with them changing.=0A=0ARather than tr=
ying to shorten the lifetimes and lowering the stability of addresses to th=
e point where they may disrupt the applications using them, perhaps creatin=
g per-application or transport layer connection addresses may be a better i=
dea, as discussed in:=0A=0A"Transient Addressing for Related Processes: Imp=
roved Firewalling=A0by Using IPV6 and Multiple Addresses per Host"=0Ahttps:=
//www.cs.columbia.edu/~smb/papers/tarp.pdf=0A=0A=0A=0ARegards,=0AMark.=A0=
=0A=0A=0A=0A----- Original Message -----=0A> From: Hosnieh Rafiee <ietf@roz=
anak.com>=0A> To: ipv6@ietf.org=0A> Cc: =0A> Sent: Sunday, 5 May 2013 5:17 =
AM=0A> Subject: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-priv=
acy.txt - =0A> =0A> Has anybody had a chance to look at this draft=0A> (htt=
p://tools.ietf.org/html/draft-rafiee-6man-ra-privacy )? Any comments?=0A> T=
he aim of this draft is to adapt the current RFC to the latest European law=
=0A> http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=3Den and t=
o=0A> accommodate the needs of customers with relation to the new law for a=
 long=0A> term period. The purpose is to allow users to choose their means =
to the=0A> privacy and anonymity within a network as well as across network=
s. =0A> =0A> There is still an option of merging this draft with other draf=
ts, that=0A> address the issue of allowing users to set the lifetime of the=
 IP address=0A> during the installation or an option to set it by the users=
, if people on=0A> the mailing list thinks it would be useful. =0A> Share y=
our technical ideas.=0A> =0A> Thanks,=0A> Best,=0A> Hosnieh=0A> =0A> =0A> =
=0A> --------------------------------------------------------------------=
=0A> IETF IPv6 working group mailing list=0A> ipv6@ietf.org=0A> Administrat=
ive Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A> --------------=
------------------------------------------------------=0A> 

From Francis.Dupont@fdupont.fr  Sun May  5 06:24:24 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D5A21F9397 for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 06:24:24 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miuXAq62euCb for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 06:24:23 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 3463221F9387 for <ipv6@ietf.org>; Sun,  5 May 2013 06:24:23 -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 r45DNpdi030531; Sun, 5 May 2013 15:23:51 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201305051323.r45DNpdi030531@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Hosnieh Rafiee" <ietf@rozanak.com>
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
In-reply-to: Your message of Sat, 04 May 2013 21:17:37 +0200. <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> 
Date: Sun, 05 May 2013 15:23:51 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 May 2013 13:24:24 -0000

 In your previous mail you wrote:

>  The aim of this draft is to adapt the current RFC to the latest European law
>  http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=en

=> I tried to not participate to this... Nethertheless this is *not*
an European law, only a EC directive project. BTW even if (when?) it is
adopted it must be adapted in each country into a national law.
Note this doesn't mean there is no country in the EU with silly
legal position about IPv6 address (cf Germany).

Regards

Francis.Dupont@fdupont.fr

From ietf@rozanak.com  Sun May  5 08:01:50 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8D8521F884F for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 08:01:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TK9FD7qOUtQj for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 08:01:43 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id A0A3F21F8464 for <ipv6@ietf.org>; Sun,  5 May 2013 08:01:43 -0700 (PDT)
Received: from kopoli (g231249217.adsl.alicedsl.de [92.231.249.217]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Lxh59-1UWYpL19r9-016Swn; Sun, 05 May 2013 11:01:36 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <Francis.Dupont@fdupont.fr>
References: Your message of Sat, 04 May 2013 21:17:37 +0200. <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <201305051323.r45DNpdi030531@givry.fdupont.fr>
In-Reply-To: <201305051323.r45DNpdi030531@givry.fdupont.fr>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Date: Sun, 5 May 2013 17:01:28 +0200
Message-ID: <000001ce49a1$6fa4b2b0$4eee1810$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEBcT1SM66aJEJPHpGVIgFlSj4wSpqQXQCg
Content-Language: en-us
X-Provags-ID: V02:K0:ZmgAtW9jFffxshNjv+cEIZPvA34PDwYi5L2PIFl1iP0 LdN5ZvPZlcXVDO4Qf2fMCv+jT3ADLGAGISWV1GK9z7Y21rzNv2 A948ArknNebgno1vztszd4I58cl7Bpa/dAF2GuEvp86Gm+7gTI qQmaC71ispE5j3Pcb5wzBYAUml3OMkj5tjScnYNRQe51OHQa9D cb7ozIZJHfiYHrkXYytEDfWPwE2jSIXRh1BOOaGq/2wZZT6uVF E5mp3ir/4p981XCJFZBGdb6wBzpFSu03sZQb3hpFz5PPFnjCd6 kOGWlvRLxO4Csq3ifAx83t6Q5h02jZ4EKM2bM1E3XyabdyZ9pt Fd0c1jx52KfE70a9k1Io=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 May 2013 15:01:50 -0000

> => I tried to not participate to this... Nethertheless this is *not* an
European
> law, only a EC directive project. BTW even if (when?)

Yes, first as I explained to Brian, that was a reference for the meaning of
privacy and a possible way for protecting privacy. Second, it is better to
be prepared. Third, how long does it take a proposal to become a RFC and how
long does it take implementers to start the implementation. The answer is
the same as "when" for your question. 

regards,
Hosnieh




From ietf@rozanak.com  Sun May  5 08:32:59 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03B421F95FB for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 08:32:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFMsK-DC9PY2 for <ipv6@ietfa.amsl.com>; Sun,  5 May 2013 08:32:56 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id E1B1021F9424 for <ipv6@ietf.org>; Sun,  5 May 2013 08:32:55 -0700 (PDT)
Received: from kopoli (g231249217.adsl.alicedsl.de [92.231.249.217]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MLNtq-1UYShM1Jys-000Hj6; Sun, 05 May 2013 11:32:54 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Mark Smith'" <markzzzsmith@yahoo.com.au>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <1367718323.3497.YahooMailNeo@web142504.mail.bf1.yahoo.com>
In-Reply-To: <1367718323.3497.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Date: Sun, 5 May 2013 17:32:47 +0200
Message-ID: <000701ce49a5$cf03d750$6d0b85f0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEIl8rTHwJkn2ThdH61FAwJnuwKbAGQ1MammnWMo/A=
Content-Language: en-us
X-Provags-ID: V02:K0:vcmyImF4WR51D93284QJuB8nbUeenVp+S2rNe5t0fIp 8JwQ30Zwnth7KAz74z9Q6DMvzmaUIgw/IDYtmoN/KTmYqHYSkX GayYttpbQUsBTphQFKdL1vbmTUkjZXoXe4rSu/xAZPgq5+xblR X4A+EqfuqO/+8EkUE4MmDk9Rf25vB50zPHP1vfBjIHcxFNQvrF uxFqukjH29mVJK/7DG7wpFfW8e7oGtXcneDBZObxQSVNuv48PW ceHgOe8gQiSlghemoj8yKFshZmEurOZew+zfTTRYj3kNShXLHj CQFfivnHrlO/eNUY9vx8ElR7y+AJaRinHVJERA7DyROKM+S+l4 wI0J3EBB4LHH8nwkB97A=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 05 May 2013 15:33:00 -0000

As I  wrote in the draft, the time frame for the lifetime of the IP =
address
should be left up to the use choose based on network policy, but with =
the
caveat that it should not be so long as to let it be tracked by an =
attacker.
I explained that as long as the session is valid (layer 5), the node can =
use
its old IP address but cannot start any new session with the old, =
expired IP
address.  One might want  to change that sentence to read - the old IP
address can continue being used as long as the transport layer =
connection is
valid, but a new connection cannot be started using its old IP address.
Does this alleviate your concerns?
Thanks for your comments,
Hosnieh

>=20
> I've had a very brief look, because there was one specific thing I was
looking
> for, and it doesn't seem to be there.
>=20
> Addresses/IIDs have to last at least as long as the transport
layer/application
> connections are using them, unless the transport layer/application
connection
> takes ownership of dealing with addresses that might =
"change=A0underneath
> them". In general, larger preferred and valid lifetimes (e.g, measured =
in
hours
> or greater) and fairly stable identifiers are intended to avoid =
transport
layer
> protocols/applications having to deal with them changing.
>=20
> Rather than trying to shorten the lifetimes and lowering the stability =
of
> addresses to the point where they may disrupt the applications using =
them,
> perhaps creating per-application or transport layer connection =
addresses
may
> be a better idea, as discussed in:
>=20
> "Transient Addressing for Related Processes: Improved Firewalling=A0by =
Using
> IPV6 and Multiple Addresses per Host"
> https://www.cs.columbia.edu/~smb/papers/tarp.pdf
>=20
>=20
>=20
> Regards,
> Mark.
>=20
>=20
>=20
> ----- Original Message -----
> > From: Hosnieh Rafiee <ietf@rozanak.com>
> > To: ipv6@ietf.org
> > Cc:
> > Sent: Sunday, 5 May 2013 5:17 AM
> > Subject: solution to RFC 4941 I-D action :
> > draft-rafiee-6man-ra-privacy.txt -
> >
> > Has anybody had a chance to look at this draft
> > (http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy )? Any
comments?
> > The aim of this draft is to adapt the current RFC to the latest
> > European law
> > http://europa.eu/rapid/press-release_IP-12-46_en.htm?locale=3Den and =
to
> > accommodate the needs of customers with relation to the new law for =
a
> > long term period. The purpose is to allow users to choose their =
means to
the
> privacy and anonymity within a network as well as across networks.
> >
> > There is still an option of merging this draft with other drafts, =
that
> > address the issue of allowing users to set the lifetime of the IP
> > address during the installation or an option to set it by the users,
> > if people on the mailing list thinks it would be useful.
> > Share your technical ideas.
> >
> > Thanks,
> > Best,
> > Hosnieh
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >


From zhou.sujing@zte.com.cn  Mon May  6 02:42:59 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67B0C21F8FDF; Mon,  6 May 2013 02:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.906
X-Spam-Level: 
X-Spam-Status: No, score=-96.906 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MFjnB0rkszJC; Mon,  6 May 2013 02:42:55 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 641E021F8F87; Mon,  6 May 2013 02:42:55 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 2F38B12DAC19; Mon,  6 May 2013 17:42:26 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r469gPZD090108; Mon, 6 May 2013 17:42:25 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>
To: "Hosnieh Rafiee" <ietf@rozanak.com>
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFE9D4DE65.1800B9D7-ON48257B63.0034E1DF-48257B63.003566FE@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Mon, 6 May 2013 17:42:24 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-06 17:42:26, Serialize complete at 2013-05-06 17:42:26
Content-Type: multipart/alternative; boundary="=_alternative 003566FE48257B63_="
X-MAIL: mse01.zte.com.cn r469gPZD090108
Cc: ipv6-bounces@ietf.org, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 09:42:59 -0000

This is a multipart message in MIME format.
--=_alternative 003566FE48257B63_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

VG8gbXkgdW5kZXJzdGFuZGluZywgcmZjNDk0MSAgbWVhbnQgdG8gdXNlIENHQSBleGFjdGt5IGFz
IGRlZmluZWQgaW4gcmZjIA0KMzk3Mi4NClRoZSBtb2RpZmllZCBDR0EgYWxnb3JpdGhtIGluIGRy
YWZ0LXJhZmllZS02bWFuLXJhLXByaXZhY3kgaGFzIG5vdGhpbmcgdG8gDQpkbyB3aXRoIENHQS4N
CkhvdyBhcmUgdSBnb2luZyB0byBkbyB3aXRoIHRoZSBDR0EgcGFyYW1ldGVyPw0KVGhlcmUgaXMg
bm8gbWVhbmluZyBpbiBzZW5kIG1vZGlmaWVyIGluIENHQSBwYXJhbWV0ZXIgdGhlbi4NCklmIG1v
ZGlmaWVyIGlzIG1lYW50IHRvIGJlIGtlcHQgdG8gdGhlIElQIGFkZHJlc3Mgb3duZXIsIG1vZGlm
ZXIgY291bGQgYmUgDQp2aWV3ZWQgYXMgc2VjcmV0LA0KYXMgZGVmaW5lZCBpbiBkcmFmdC1pZXRm
LTZtYW4tc3RhYmxlLXByaXZhY3ktYWRkcmVzc2VzLg0KDQpJTUhPLCB1c2UgQ0dBIGp1c3QgZm9y
IGEgcmFuZG9tIElQIGFkZHJlc3MgaXMgYSB3YXN0ZS4NCg0KaXB2Ni1ib3VuY2VzQGlldGYub3Jn
INC009ogMjAxMy0wNS0wNSAwMzoxNzozNzoNCg0KPiBIYXMgYW55Ym9keSBoYWQgYSBjaGFuY2Ug
dG8gbG9vayBhdCB0aGlzIGRyYWZ0DQo+IChodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1yYWZpZWUtNm1hbi1yYS1wcml2YWN5ICk/IEFueSANCmNvbW1lbnRzPw0KPiBUaGUgYWltIG9m
IHRoaXMgZHJhZnQgaXMgdG8gYWRhcHQgdGhlIGN1cnJlbnQgUkZDIHRvIHRoZSBsYXRlc3QgRXVy
b3BlYW4gDQpsYXcNCj4gaHR0cDovL2V1cm9wYS5ldS9yYXBpZC9wcmVzcy1yZWxlYXNlX0lQLTEy
LTQ2X2VuLmh0bT9sb2NhbGU9ZW4gYW5kIHRvDQo+IGFjY29tbW9kYXRlIHRoZSBuZWVkcyBvZiBj
dXN0b21lcnMgd2l0aCByZWxhdGlvbiB0byB0aGUgbmV3IGxhdyBmb3IgYSANCmxvbmcNCj4gdGVy
bSBwZXJpb2QuIFRoZSBwdXJwb3NlIGlzIHRvIGFsbG93IHVzZXJzIHRvIGNob29zZSB0aGVpciBt
ZWFucyB0byB0aGUNCj4gcHJpdmFjeSBhbmQgYW5vbnltaXR5IHdpdGhpbiBhIG5ldHdvcmsgYXMg
d2VsbCBhcyBhY3Jvc3MgbmV0d29ya3MuIA0KPiANCj4gVGhlcmUgaXMgc3RpbGwgYW4gb3B0aW9u
IG9mIG1lcmdpbmcgdGhpcyBkcmFmdCB3aXRoIG90aGVyIGRyYWZ0cywgdGhhdA0KPiBhZGRyZXNz
IHRoZSBpc3N1ZSBvZiBhbGxvd2luZyB1c2VycyB0byBzZXQgdGhlIGxpZmV0aW1lIG9mIHRoZSBJ
UCANCmFkZHJlc3MNCj4gZHVyaW5nIHRoZSBpbnN0YWxsYXRpb24gb3IgYW4gb3B0aW9uIHRvIHNl
dCBpdCBieSB0aGUgdXNlcnMsIGlmIHBlb3BsZSANCm9uDQo+IHRoZSBtYWlsaW5nIGxpc3QgdGhp
bmtzIGl0IHdvdWxkIGJlIHVzZWZ1bC4gDQo+IFNoYXJlIHlvdXIgdGVjaG5pY2FsIGlkZWFzLg0K
PiANCj4gVGhhbmtzLA0KPiBCZXN0LA0KPiBIb3NuaWVoDQo+IA0KPiANCj4gDQo+IC0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQo+IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdA0KPiBpcHY2QGlldGYu
b3JnDQo+IEFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lwdjYNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0K
--=_alternative 003566FE48257B63_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlRvIG15IHVuZGVyc3RhbmRpbmcs
IHJmYzQ5NDEgJm5ic3A7bWVhbnQNCnRvIHVzZSBDR0EgZXhhY3RreSBhcyBkZWZpbmVkIGluIHJm
YyAzOTcyLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+VGhlIG1v
ZGlmaWVkIENHQSBhbGdvcml0aG0gaW4gPC9mb250Pjx0dD48Zm9udCBzaXplPTI+ZHJhZnQtcmFm
aWVlLTZtYW4tcmEtcHJpdmFjeTwvZm9udD48L3R0Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNl
cmlmIj4NCmhhcyBub3RoaW5nIHRvIGRvIHdpdGggQ0dBLjwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+SG93IGFyZSB1IGdvaW5nIHRvIGRvIHdpdGggdGhlIENHQSBw
YXJhbWV0ZXI/PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5UaGVy
ZSBpcyBubyBtZWFuaW5nIGluIHNlbmQgbW9kaWZpZXINCmluIENHQSBwYXJhbWV0ZXIgdGhlbi48
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPklmIG1vZGlmaWVyIGlz
IG1lYW50IHRvIGJlIGtlcHQgdG8gdGhlDQpJUCBhZGRyZXNzIG93bmVyLCBtb2RpZmVyIGNvdWxk
IGJlIHZpZXdlZCBhcyBzZWNyZXQsPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5z
LXNlcmlmIj5hcyBkZWZpbmVkIGluIGRyYWZ0LWlldGYtNm1hbi1zdGFibGUtcHJpdmFjeS1hZGRy
ZXNzZXMuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5J
TUhPLCB1c2UgQ0dBIGp1c3QgZm9yIGEgcmFuZG9tIElQIGFkZHJlc3MNCmlzIGEgd2FzdGUuPC9m
b250Pg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+aXB2Ni1ib3VuY2VzQGlldGYub3JnINC0
09ogMjAxMy0wNS0wNSAwMzoxNzozNzo8YnI+DQo8YnI+DQomZ3Q7IEhhcyBhbnlib2R5IGhhZCBh
IGNoYW5jZSB0byBsb29rIGF0IHRoaXMgZHJhZnQ8YnI+DQomZ3Q7IChodHRwOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1yYWZpZWUtNm1hbi1yYS1wcml2YWN5ICk/IEFueSBjb21tZW50cz88
YnI+DQomZ3Q7IFRoZSBhaW0gb2YgdGhpcyBkcmFmdCBpcyB0byBhZGFwdCB0aGUgY3VycmVudCBS
RkMgdG8gdGhlIGxhdGVzdCBFdXJvcGVhbg0KbGF3PGJyPg0KJmd0OyBodHRwOi8vZXVyb3BhLmV1
L3JhcGlkL3ByZXNzLXJlbGVhc2VfSVAtMTItNDZfZW4uaHRtP2xvY2FsZT1lbiBhbmQNCnRvPGJy
Pg0KJmd0OyBhY2NvbW1vZGF0ZSB0aGUgbmVlZHMgb2YgY3VzdG9tZXJzIHdpdGggcmVsYXRpb24g
dG8gdGhlIG5ldyBsYXcgZm9yDQphIGxvbmc8YnI+DQomZ3Q7IHRlcm0gcGVyaW9kLiBUaGUgcHVy
cG9zZSBpcyB0byBhbGxvdyB1c2VycyB0byBjaG9vc2UgdGhlaXIgbWVhbnMgdG8NCnRoZTxicj4N
CiZndDsgcHJpdmFjeSBhbmQgYW5vbnltaXR5IHdpdGhpbiBhIG5ldHdvcmsgYXMgd2VsbCBhcyBh
Y3Jvc3MgbmV0d29ya3MuDQo8YnI+DQomZ3Q7IDxicj4NCiZndDsgVGhlcmUgaXMgc3RpbGwgYW4g
b3B0aW9uIG9mIG1lcmdpbmcgdGhpcyBkcmFmdCB3aXRoIG90aGVyIGRyYWZ0cywNCnRoYXQ8YnI+
DQomZ3Q7IGFkZHJlc3MgdGhlIGlzc3VlIG9mIGFsbG93aW5nIHVzZXJzIHRvIHNldCB0aGUgbGlm
ZXRpbWUgb2YgdGhlIElQDQphZGRyZXNzPGJyPg0KJmd0OyBkdXJpbmcgdGhlIGluc3RhbGxhdGlv
biBvciBhbiBvcHRpb24gdG8gc2V0IGl0IGJ5IHRoZSB1c2VycywgaWYgcGVvcGxlDQpvbjxicj4N
CiZndDsgdGhlIG1haWxpbmcgbGlzdCB0aGlua3MgaXQgd291bGQgYmUgdXNlZnVsLiA8YnI+DQom
Z3Q7IFNoYXJlIHlvdXIgdGVjaG5pY2FsIGlkZWFzLjxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGFu
a3MsPGJyPg0KJmd0OyBCZXN0LDxicj4NCiZndDsgSG9zbmllaDxicj4NCiZndDsgPGJyPg0KJmd0
OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQomZ3Q7IElFVEYgSVB2NiB3
b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdDxicj4NCiZndDsgaXB2NkBpZXRmLm9yZzxicj4NCiZn
dDsgQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vaXB2Njxicj4NCiZndDsgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQo8L2ZvbnQ+PC90dD4NCg==
--=_alternative 003566FE48257B63_=--

From ietf@rozanak.com  Mon May  6 03:11:06 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0613621F9051 for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 03:11:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVHLKnYJT6cj for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 03:11:00 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 125AB21F9049 for <ipv6@ietf.org>; Mon,  6 May 2013 03:11:00 -0700 (PDT)
Received: from kopoli (f052071177.adsl.alicedsl.de [78.52.71.177]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0LjpUP-1U1tN028EL-00bZdX; Mon, 06 May 2013 06:10:58 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Sujing Zhou'" <zhou.sujing@zte.com.cn>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <OFE9D4DE65.1800B9D7-ON48257B63.0034E1DF-48257B63.003566FE@zte.com.cn>
In-Reply-To: <OFE9D4DE65.1800B9D7-ON48257B63.0034E1DF-48257B63.003566FE@zte.com.cn>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Date: Mon, 6 May 2013 12:10:52 +0200
Message-ID: <001201ce4a42$004ff4a0$00efdde0$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01CE4A52.C3DB35A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGKEgnz/NNnFtGOGIrz0iogXP6IVJmAWMSA
Content-Language: en-us
X-Provags-ID: V02:K0:0qToGqTTV3tJdxb/h7FFEoV8wnTXu2SAI97ALIRdSpM O3qFdl50cFjREac36I3TXIoi4dLUULYeMU3AWyHpBqbdmHfMiM hFVdNcarcpt+1d17kDJY6JgsP7Uum065SNJ1e2bReb28l3m7oW pamGXiiTohAnuilPwdhCa/NYPdYvmgN8Odjrq3uVrAi4IWHZ7s 5ZXd9i3o9D0pgO4VsB50D3nwOCbUKRYOQ5n0Tdtl9hNWME6U+Y Z0rOs/wZoz5c5a+l4w5rJZK5WLhyAQCojIODwNjbtMmjU/zCaj +P8gC6Y2f5849nmnPoHrbIbBGlcS5aQTPVODewm4uBqSjnHGY9 OF30duY2Vj0/5StU2jC8=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 10:11:06 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0013_01CE4A52.C3DB35A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

>To my understanding, rfc4941  meant to use CGA exactky as defined in rfc
3972. 

>The modified CGA algorithm in draft-rafiee-6man-ra-privacy has nothing to
do with CGA. 

>How are u going to do with the CGA parameter? 

 

There is no CGA option to add to the ICMP messages. Using a part of CGA
algorithm for IID generation (that I called it modified CGA is because I do
not use public private key and removed the condition checking for security
level. My purpose is not security here as I explained in the draft) is just
for the purpose of randomization in the absence of stable storage. It
provides better randomization than trying to use some random numbers as
explained in section 3.2.2 RFC 4941.

 

 

>There is no meaning in send modifier in CGA parameter then. 

>If modifier is meant to be kept to the IP address owner, modifier could be
viewed as secret, 

>as defined in draft-ietf-6man-stable-privacy-addresses. 

 

Not exactly. I am not planning to have any correlation between my modifier
and IID as "stable address draft" wants to have. It is because, in my
opinion, there is no reason for it so that others can guess my next IID
values by having my secret or re-generate it. It is because that approach
cannot either help to increase my security like what real CGA does to some
extent nor can help to increase my privacy.

 

The purpose of ra-privacy draft is first having more control on IID
lifetime. Second, to increase the randomization of IID. 

 

Thanks for your comments,

Hosnieh


------=_NextPart_000_0013_01CE4A52.C3DB35A0
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:SimSun;
	mso-fareast-language:ZH-CN;}
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;}
tt
	{mso-style-priority:99;
	font-family:SimSun;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;To my understanding, rfc4941&nbsp; meant to use CGA exactky as =
defined in rfc 3972. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;The modified CGA algorithm in draft-rafiee-6man-ra-privacy has =
nothing to do with CGA. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;How are u going to do with the CGA parameter? =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There is no CGA option to add to the ICMP messages. Using a part of =
CGA algorithm for IID generation (that I called it modified CGA is =
because I do not use public private key and removed the condition =
checking for security level. My purpose is not security here as I =
explained in the draft) is just for the purpose of randomization in the =
absence of stable storage. It provides better randomization than trying =
to use some random numbers as explained in section 3.2.2 RFC =
4941.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;There is no meaning in send modifier in CGA parameter then. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;If modifier is meant to be kept to the IP address owner, modifier =
could be viewed as secret, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&gt;as defined in draft-ietf-6man-stable-privacy-addresses. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Not exactly. I am not planning to have any correlation between my =
modifier and IID as &#8220;stable address draft&#8221; wants to have. It =
is because, in my opinion, there is no reason for it so that others can =
guess my next IID values by having my secret or re-generate it. It is =
because that approach cannot either help to increase my security like =
what real CGA does to some extent nor can help to increase my =
privacy.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The purpose of ra-privacy draft is first having more control on IID =
lifetime. Second, to increase the randomization of IID. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks for your comments,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hosnieh<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0013_01CE4A52.C3DB35A0--


From ietf@rozanak.com  Mon May  6 07:50:09 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9124B21F93B7 for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 07:50:09 -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=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKSAHNoVAksl for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 07:50:03 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id A195421F935B for <ipv6@ietf.org>; Mon,  6 May 2013 07:50:03 -0700 (PDT)
Received: from kopoli (f052071177.adsl.alicedsl.de [78.52.71.177]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0Le5rg-1UEOWx2aoW-00qidb; Mon, 06 May 2013 10:50:02 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Sujing Zhou'" <zhou.sujing@zte.com.cn>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>	<OFE9D4DE65.1800B9D7-ON48257B63.0034E1DF-48257B63.003566FE@zte.com.cn> <001201ce4a42$004ff4a0$00efdde0$@rozanak.com>
In-Reply-To: <001201ce4a42$004ff4a0$00efdde0$@rozanak.com>
Subject: RE: solution to RFC 4941 I-D action :	draft-rafiee-6man-ra-privacy.txt -
Date: Mon, 6 May 2013 16:49:55 +0200
Message-ID: <001801ce4a68$fbb9e000$f32da000$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEIl8rTHwJkn2ThdH61FAwJnuwKbAGKEgnzAWaeR+Caa/j3IA==
Content-Language: en-us
X-Provags-ID: V02:K0:b1uA9aLEjlXu8dcbqsAgDEmXHwV7K9NrmHX/YO/jBta mT6tNgipxjJ6BtFvCLxRChSjB3og9XRrEgoGDsaX3KF/ofxJWP d65ga6teRK8RQs8SB8G/dP/v1IQHGRy82UHPRqykLV2YsLtMSA 1QxZD7RilbSHXmueoWiQWPZgEB3T7R1TXQBDDGxLpZiCu69tUI E+p6BBVTccvAGjASrN1lamiJq1niweoA//7mrUxGBDPdHWukcz gXUmfspLChBbjTwnyToh/pWXqgMNyOfH2Ri2CYwb/fdgFEzADn 8vsD0wRHJ4TjUrhfAiAUpcyi0AXal6P6GuDLiyD/Ecu9niNdFe IIIsUMLatB7zp9dylUSg=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 14:50:09 -0000

Follow up:

>To my understanding, rfc4941  meant to use CGA exactky as defined in rfc
3972.

To clarify what my purpose is, I want to address the situation where the
node is not using stable storage but still needs to generate a random IID.
This document is only an update to that section  to provide a better
approach when there is no need to rely on stable storage for randomization.

>The modified CGA algorithm in draft-rafiee-6man-ra-privacy has nothing to
do with CGA. 

The steps are the same except for removing the steps associated with
security verification. I did not see any need for that.

Finally, the modifier depicted in RA-privacy is just a random number. You
can call it whatever you like, but it is not something secret that would
compromise privacy if somebody knew it. The node picks up whatever number it
likes. By combining this number with the timestamp and the subnet prefix a
unique IID is generated. If another node would happen to choose the same
number (that the probability of that is very low), then the timestamp
enables the generation of a different value than that for the other node in
this network.

Thanks again,
Hosnieh


From bob.hinden@gmail.com  Mon May  6 09:14:07 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C11321F910E for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 09:14:07 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfEz3NU8ZwMX for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 09:14:02 -0700 (PDT)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by ietfa.amsl.com (Postfix) with ESMTP id DC8F521F90EE for <ipv6@ietf.org>; Mon,  6 May 2013 09:14:01 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id hz10so3174219vcb.38 for <ipv6@ietf.org>; Mon, 06 May 2013 09:14:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=KR8PnpDn8fn5oLjOKotHh6CAE6cnugrBCpMYU29oRwY=; b=T3Pz+HrEvHbiXUdH0Vj3z7XWAvhyA6k5avzzGifsfxrOlbKKsgb61e+/aqh4da5uBX 5I97LMv/Y0hw3CL0aTKZJ5lkwTRkdFIpILybN9gE5zP0neUi3dii3Xn7JRiOppICVxZ2 uhKMJmxE9GtO7waRCAUiIv4C+fhEXnC1Kt93VrEZhf9r3/O26C9tY2EHUm9bWzKOu+pE fHuMa/EnswJM/4EuWKEOdDk4l0EOT0P1lBLIoqjiJ4DemqMKQeUvPzbYrO95rtrfhNZA T007SfytYsBZMTzxrhy/LwwaOsFCK+t1kDTaWUyC1i0M9K35NpxWIiMCVsmcTrWD2ZpA s0uw==
X-Received: by 10.220.82.3 with SMTP id z3mr7061083vck.18.1367856841381; Mon, 06 May 2013 09:14:01 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:9061:f10c:a588:7ac9? ([2601:9:4080:10:9061:f10c:a588:7ac9]) by mx.google.com with ESMTPSA id fj6sm17040354vdc.12.2013.05.06.09.13.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 May 2013 09:14:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <51856775.9090809@gmail.com>
Date: Mon, 6 May 2013 09:13:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <16DE82B6-45EB-4042-A1ED-B0DFFAF6489A@gmail.com>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <51856775.9090809@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ipv6@ietf.org List" <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 16:14:07 -0000

Hi,

On May 4, 2013, at 12:54 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

. . . .

>=20
> As far as I can see, if I set the RFC 4941 timer to a reasonable
> value, my IID will change much more often than my subnet prefix.
>=20

I would like to see the answer to Brian's comment, I didn't see a =
response to it in the thread.

Bob


From ietf@rozanak.com  Mon May  6 12:32:12 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E2321F918C for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 12:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z28zTb+9mL0M for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 12:32:06 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id B346721F91B0 for <ipv6@ietf.org>; Mon,  6 May 2013 12:32:03 -0700 (PDT)
Received: from kopoli (f052071177.adsl.alicedsl.de [78.52.71.177]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lb5Wr-1U7IFJ3ovh-00kjpM; Mon, 06 May 2013 15:32:02 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Bob Hinden'" <bob.hinden@gmail.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <51856775.9090809@gmail.com> <16DE82B6-45EB-4042-A1ED-B0DFFAF6489A@gmail.com>
In-Reply-To: <16DE82B6-45EB-4042-A1ED-B0DFFAF6489A@gmail.com>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Date: Mon, 6 May 2013 21:31:48 +0200
Message-ID: <000401ce4a90$60cf0890$226d19b0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEIl8rTHwJkn2ThdH61FAwJnuwKbAIHD3r6An3YsK6aX8QbEA==
Content-Language: en-us
X-Provags-ID: V02:K0:6CGnzHYxKYwLGzxonXT+BsnyDLoCkRVK1EybDsOfxXK qlrQrl7h+2PnwJsaqP0aYjuzUN2wR85ivHmtQZWhtzNplJgK6n 1OewkRRY66+JqsKXN+/nAdpfbVXOxmSoCJc9VCUNMty5k1rN83 d8NddQZux36779hLqlhWnWDnSKkgvYI3kQNosYyD2tLvAsQ0+c ysA9l/5RlrJlwWE0apOQQbaMFSHEJk3FuGbJB2Unc0bercMQ+n u+DAGs6G4+1+voDMQh5OGzMRSQ4FtQuAV+sDGn3LsnP8SqJpi7 1AmLsZ33vbC1D+cIcOjTVtcB72WbcwEQ60XNhak5VlMgaxircV gZ9bRnNvz/C8tIVNDTp0=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 19:32:12 -0000

Hi Bob,
> >
> > As far as I can see, if I set the RFC 4941 timer to a reasonable
> > value, my IID will change much more often than my subnet prefix.
> >
> 
> I would like to see the answer to Brian's comment, I didn't see a response
to it
> in the thread.
> 

That is true. But the problem that I address is not why my IID does not
change within the same subnet prefix. The problem is, based on this RFC,
that it is not mandatory to change the IID when my node receives a new
prefix. This is because it depends on the lifetime it receives from the RA.
If the RA message says that my node might extend its lifetime, then the node
does it while the IID is still valid (max lifetime). This means that when
the lifetime is still valid and the new prefix uses this option, my IID will
not change to a different prefix. What I added to my draft is that I set a
mandatory priority on the IID lifetime. When it receives a new prefix,
regardless of its own lifetime or on the lifetime that it received from the
prefix, it MUST generate a new IID and change the status of the current IID
to deprecated. This means that the node, after that, is not allowed to open
any new sessions (will change it to new connections) using the old IID, but
it can maintain its connection with the old IID.



From internet-drafts@ietf.org  Mon May  6 15:51:09 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC3A21F9180; Mon,  6 May 2013 15:51:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.664
X-Spam-Level: 
X-Spam-Status: No, score=-101.664 tagged_above=-999 required=5 tests=[AWL=0.936, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8DP6NLHWVvP; Mon,  6 May 2013 15:51:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C24C21F8F62; Mon,  6 May 2013 15:51:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-resilient-rs-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.44.p6
Message-ID: <20130506225104.23771.43608.idtracker@ietfa.amsl.com>
Date: Mon, 06 May 2013 15:51:04 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 06 May 2013 22:51:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : Packet loss resiliency for Router Solicitations
	Author(s)       : Suresh Krishnan
                          Dmitry Anipko
                          Dave Thaler
	Filename        : draft-ietf-6man-resilient-rs-01.txt
	Pages           : 7
	Date            : 2013-05-06

Abstract:
   When an interface on a host is initialized, the host transmits Router
   Solicitations in order to minimize the amount of time it needs to
   wait until the next unsolicited multicast Router Advertisement is
   received.  In certain scenarios, these router solicitations
   transmitted by the host might be lost.  This document specifies a
   mechanism for hosts to cope with the loss of the initial Router
   Solicitations.  Furthermore, on some links, unsolicited multicast
   Router Advertisements are never sent and the mechanism in this
   document is intended to work even in such scenarios.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-resilient-rs-01


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


From huitema@microsoft.com  Mon May  6 21:57:16 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0BB21F8617 for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 21:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-n4mQHmjxsG for <ipv6@ietfa.amsl.com>; Mon,  6 May 2013 21:57:10 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 0A4B721F8470 for <ipv6@ietf.org>; Mon,  6 May 2013 21:57:09 -0700 (PDT)
Received: from BL2FFO11FD018.protection.gbl (10.173.161.203) by BL2FFO11HUB008.protection.gbl (10.173.160.228) with Microsoft SMTP Server (TLS) id 15.0.687.1; Tue, 7 May 2013 04:48:40 +0000
Received: from TK5EX14MLTC102.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD018.mail.protection.outlook.com (10.173.161.36) with Microsoft SMTP Server (TLS) id 15.0.687.1 via Frontend Transport; Tue, 7 May 2013 04:48:39 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.184]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.02.0318.003; Tue, 7 May 2013 04:48:15 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Hosnieh Rafiee <ietf@rozanak.com>, 'Bob Hinden' <bob.hinden@gmail.com>, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
Subject: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Thread-Topic: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt - 
Thread-Index: AQHOSnTMNuqY3QxGxUayWmlOaKaQHJj4i8kAgACZvVA=
Date: Tue, 7 May 2013 04:48:14 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com> <51856775.9090809@gmail.com> <16DE82B6-45EB-4042-A1ED-B0DFFAF6489A@gmail.com> <000401ce4a90$60cf0890$226d19b0$@rozanak.com>
In-Reply-To: <000401ce4a90$60cf0890$226d19b0$@rozanak.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(55846006)(74706001)(76482001)(51856001)(74366001)(81542001)(81342001)(79102001)(69226001)(74876001)(50466002)(65816001)(77982001)(54316002)(47446002)(74502001)(46102001)(47776003)(53806001)(50986001)(80022001)(66066001)(6806003)(59766001)(33656001)(46406003)(4396001)(16406001)(74662001)(49866001)(56816002)(56776001)(23726002)(47736001)(54356001)(31966008)(44976003)(20776003)(63696002)(47976001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB008; H:TK5EX14MLTC102.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0839D067E7
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 04:57:16 -0000

There is a part of me that wishes that we just deploy what we have. There i=
s another part that notices that between IEEE802, privacy addresses, CGA, s=
table privacy addresses and probably a few more, we have built a nice mess =
and maybe we should clean it up. For example, we could decree that composin=
g and IID from a MAC address is obsolete, and we could unify CGA and other =
privacy addresses. Add some salt can make the CGA addresses as randomized a=
s the privacy addresses; change the lifetime of the key and you get whateve=
r address lifetime is deemed appropriate. But then, the best part of me obs=
erves that with the current level of IPv6 deployment, maybe we don't have a=
n urgent need for more specs...

-- Christian Huitema

=20

From zhou.sujing@zte.com.cn  Mon May  6 22:08:18 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7321E21F910D; Mon,  6 May 2013 22:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.998
X-Spam-Level: 
X-Spam-Status: No, score=-101.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrXJFOMF6sVM; Mon,  6 May 2013 22:08:14 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACB921F9017; Mon,  6 May 2013 22:08:12 -0700 (PDT)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 00FE41268AD2; Tue,  7 May 2013 13:07:46 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id r4757kB4062840; Tue, 7 May 2013 13:07:46 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Tue, 7 May 2013 13:07:43 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-07 13:07:46, Serialize complete at 2013-05-07 13:07:46
Content-Type: multipart/alternative; boundary="=_alternative 001C421A48257B64_="
X-MAIL: mse02.zte.com.cn r4757kB4062840
Cc: ipv6-bounces@ietf.org, "ipv6@ietf.org" <ipv6@ietf.org>, 'Bob Hinden' <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 05:08:18 -0000

This is a multipart message in MIME format.
--=_alternative 001C421A48257B64_=
Content-Type: text/plain; charset="US-ASCII"

Considering the current level of IPv6 deployment, we have got so many 
specs...
BTW,how to add some salt to make CGA randomized as provacy address? Since 
public key has 
to be kown to receiver.

> There is a part of me that wishes that we just deploy what we have. 
> There is another part that notices that between IEEE802, privacy 
> addresses, CGA, stable privacy addresses and probably a few more, we
> have built a nice mess and maybe we should clean it up. For example,
> we could decree that composing and IID from a MAC address is 
> obsolete, and we could unify CGA and other privacy addresses. Add 
> some salt can make the CGA addresses as randomized as the privacy 
> addresses; change the lifetime of the key and you get whatever 
> address lifetime is deemed appropriate. But then, the best part of 
> me observes that with the current level of IPv6 deployment, maybe we
> don't have an urgent need for more specs...
> 
> -- Christian Huitema
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--=_alternative 001C421A48257B64_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Considering the current level of IPv6 deployment,
we have got so many specs...</font></tt>
<br><tt><font size=2>BTW,how to add some salt to make CGA randomized as
provacy address? Since public key has </font></tt>
<br><tt><font size=2>to be kown to receiver.</font></tt>
<br><tt><font size=2><br>
&gt; There is a part of me that wishes that we just deploy what we have.
<br>
&gt; There is another part that notices that between IEEE802, privacy <br>
&gt; addresses, CGA, stable privacy addresses and probably a few more,
we<br>
&gt; have built a nice mess and maybe we should clean it up. For example,<br>
&gt; we could decree that composing and IID from a MAC address is <br>
&gt; obsolete, and we could unify CGA and other privacy addresses. Add
<br>
&gt; some salt can make the CGA addresses as randomized as the privacy
<br>
&gt; addresses; change the lifetime of the key and you get whatever <br>
&gt; address lifetime is deemed appropriate. But then, the best part of
<br>
&gt; me observes that with the current level of IPv6 deployment, maybe
we<br>
&gt; don't have an urgent need for more specs...<br>
&gt; <br>
&gt; -- Christian Huitema<br>
&gt; <br>
&gt; &nbsp;<br>
&gt; --------------------------------------------------------------------<br>
&gt; IETF IPv6 working group mailing list<br>
&gt; ipv6@ietf.org<br>
&gt; Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6<br>
&gt; --------------------------------------------------------------------<br>
</font></tt>
--=_alternative 001C421A48257B64_=--

From huitema@microsoft.com  Mon May  6 22:28:37 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4239621F930C; Mon,  6 May 2013 22:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.092
X-Spam-Level: 
X-Spam-Status: No, score=-1.092 tagged_above=-999 required=5 tests=[AWL=0.907,  BAYES_00=-2.599, J_CHICKENPOX_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BOXZH598dpJ9; Mon,  6 May 2013 22:28:31 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id CDE5821F8B5F; Mon,  6 May 2013 22:28:30 -0700 (PDT)
Received: from BN1BFFO11FD019.protection.gbl (10.58.52.203) by BN1AFFO11HUB015.protection.gbl (10.58.52.125) with Microsoft SMTP Server (TLS) id 15.0.687.1; Tue, 7 May 2013 05:28:22 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD019.mail.protection.outlook.com (10.58.53.79) with Microsoft SMTP Server (TLS) id 15.0.687.1 via Frontend Transport; Tue, 7 May 2013 05:28:22 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.184]) by TK5EX14HUBC104.redmond.corp.microsoft.com ([157.54.80.25]) with mapi id 14.02.0318.003; Tue, 7 May 2013 05:28:20 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Sujing Zhou <zhou.sujing@zte.com.cn>
Subject: RE: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Thread-Topic: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Thread-Index: AQHOSuDkF0mDSyjApEOwDXtCNh34jZj5LoFA
Date: Tue, 7 May 2013 05:28:19 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E73A@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com> <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
In-Reply-To: <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(59766001)(50986001)(47976001)(56776001)(4396001)(16406001)(51856001)(47736001)(49866001)(66066001)(65816001)(74706001)(77982001)(74662001)(31966008)(81542001)(81342001)(79102001)(80022001)(47446002)(74502001)(50466002)(76482001)(47776003)(63696002)(46406003)(69226001)(23726002)(20776003)(54356001)(55846006)(74366001)(33656001)(56816002)(54316002)(6806003)(53806001)(74876001)(46102001); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB015; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0839D067E7
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, 'Bob Hinden' <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 05:28:37 -0000

> Considering the current level of IPv6 deployment, we have got so many spe=
cs...=20
> BTW,how to add some salt to make CGA randomized as privacy address? Since=
 public key has=20
> to be kown to receiver.=20

The CGA identifiers result from the hash of a modifier, a subnet prefix, a =
collision count and certificate. A simple way to get privacy properties is =
to pick a new key. Failing that, the 128 bit modifier can be set to any ran=
dom value, as long as the hash properties are respected. Granted, the numbe=
r of valid values depends on the sec field, but for low values of sec, one =
can just pick a modifier seed at random, then search for the value that pro=
vides the right hash.=20

CGA nodes only have to disclose their public key if they want to prove thei=
r identity.

But as I observed previously, we have more than enough specs around already=
...

-- Christian Huitema



From zhou.sujing@zte.com.cn  Mon May  6 22:51:34 2013
Return-Path: <zhou.sujing@zte.com.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5393D21F851E; Mon,  6 May 2013 22:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.897
X-Spam-Level: 
X-Spam-Status: No, score=-99.897 tagged_above=-999 required=5 tests=[AWL=-2.102, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32Vhf33Pa35O; Mon,  6 May 2013 22:51:21 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 4875821F8556; Mon,  6 May 2013 22:51:17 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.120]) by Websense Email Security Gateway with ESMTP id B7817126998E; Tue,  7 May 2013 13:50:50 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id EF269CEE12B; Tue,  7 May 2013 13:50:48 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r475orwh097124; Tue, 7 May 2013 13:50:53 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E73A@tk5ex14mbxc272.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
Subject: Re: RE: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF152AE090.032B00CE-ON48257B64.001F94C4-48257B64.00203428@zte.com.cn>
From: "Sujing Zhou"<zhou.sujing@zte.com.cn>
Date: Tue, 7 May 2013 13:50:49 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-07 13:50:51, Serialize complete at 2013-05-07 13:50:51
Content-Type: multipart/alternative; boundary="=_alternative 0020342848257B64_="
X-MAIL: mse01.zte.com.cn r475orwh097124
Cc: "ipv6-bounces@ietf.org" <ipv6-bounces@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, 'Bob Hinden' <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 05:51:34 -0000

This is a multipart message in MIME format.
--=_alternative 0020342848257B64_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

Q2hyaXN0aWFuIEh1aXRlbWEgPGh1aXRlbWFAbWljcm9zb2Z0LmNvbT4g0LTT2iAyMDEzLTA1LTA3
IDEzOjI4OjE5Og0KDQo+ID4gQ29uc2lkZXJpbmcgdGhlIGN1cnJlbnQgbGV2ZWwgb2YgSVB2NiBk
ZXBsb3ltZW50LCB3ZSBoYXZlIGdvdCBzbyANCj4gbWFueSBzcGVjcy4uLiANCj4gPiBCVFcsaG93
IHRvIGFkZCBzb21lIHNhbHQgdG8gbWFrZSBDR0EgcmFuZG9taXplZCBhcyBwcml2YWN5IA0KPiBh
ZGRyZXNzPyBTaW5jZSBwdWJsaWMga2V5IGhhcyANCj4gPiB0byBiZSBrb3duIHRvIHJlY2VpdmVy
LiANCj4gDQo+IFRoZSBDR0EgaWRlbnRpZmllcnMgcmVzdWx0IGZyb20gdGhlIGhhc2ggb2YgYSBt
b2RpZmllciwgYSBzdWJuZXQgDQo+IHByZWZpeCwgYSBjb2xsaXNpb24gY291bnQgYW5kIGNlcnRp
ZmljYXRlLiBBIHNpbXBsZSB3YXkgdG8gZ2V0IA0KPiBwcml2YWN5IHByb3BlcnRpZXMgaXMgdG8g
cGljayBhIG5ldyBrZXkuIEZhaWxpbmcgdGhhdCwgdGhlIDEyOCBiaXQgDQo+IG1vZGlmaWVyIGNh
biBiZSBzZXQgdG8gYW55IHJhbmRvbSB2YWx1ZSwgYXMgbG9uZyBhcyB0aGUgaGFzaCANCj4gcHJv
cGVydGllcyBhcmUgcmVzcGVjdGVkLiBHcmFudGVkLCB0aGUgbnVtYmVyIG9mIHZhbGlkIHZhbHVl
cyANCj4gZGVwZW5kcyBvbiB0aGUgc2VjIGZpZWxkLCBidXQgZm9yIGxvdyB2YWx1ZXMgb2Ygc2Vj
LCBvbmUgY2FuIGp1c3QgDQo+IHBpY2sgYSBtb2RpZmllciBzZWVkIGF0IHJhbmRvbSwgdGhlbiBz
ZWFyY2ggZm9yIHRoZSB2YWx1ZSB0aGF0IA0KPiBwcm92aWRlcyB0aGUgcmlnaHQgaGFzaC4gDQpG
YWlsZWQgdG8gY2F0Y2ggd2hhdCB5b3UgZXhhY3RseSBtZWFuLg0KSU1ITywgYSBtZXRob2QgZm9y
IENHQSB0byBiZSBwcml2YWN5IGFkZHJlc3MgY291bGQgYmUgOg0Ka2VlcCBwdWJsaWMga2V5IHVu
Y2hhbmdlZCwgYW5kIGNob29zZSBkaWZmZXJlbnQgbW9kaWZpZXIgZWFjaCB0aW1lIHNvIGFzIA0K
dG8gb2J0YWluIGRpZmZlcmVudCBJUCwgYW5kIA0Kb25seSB3aGVuIGFkZHJlc3Mgb3duZXJzaGlw
IGlzIHJlcXVpcmVkLCBzZW5kIENHQSBwYXJhbWV0ZXIgaW5jbHVkaW5nIA0KbW9kaWVmZXIsIHB1
YmxpYyBrZXksZXRjLiANCg0KPiANCj4gQ0dBIG5vZGVzIG9ubHkgaGF2ZSB0byBkaXNjbG9zZSB0
aGVpciBwdWJsaWMga2V5IGlmIHRoZXkgd2FudCB0byANCj4gcHJvdmUgdGhlaXIgaWRlbnRpdHku
DQo+IA0KPiBCdXQgYXMgSSBvYnNlcnZlZCBwcmV2aW91c2x5LCB3ZSBoYXZlIG1vcmUgdGhhbiBl
bm91Z2ggc3BlY3MgYXJvdW5kIA0KYWxyZWFkeS4uLg0KPiANCj4gLS0gQ2hyaXN0aWFuIEh1aXRl
bWENCj4gDQo+IA0KDQo=
--=_alternative 0020342848257B64_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5DaHJpc3RpYW4gSHVpdGVtYSAmbHQ7aHVpdGVtYUBtaWNy
b3NvZnQuY29tJmd0OyDQtNPaDQoyMDEzLTA1LTA3IDEzOjI4OjE5Ojxicj4NCjxicj4NCiZndDsg
Jmd0OyBDb25zaWRlcmluZyB0aGUgY3VycmVudCBsZXZlbCBvZiBJUHY2IGRlcGxveW1lbnQsIHdl
IGhhdmUgZ290DQpzbyA8YnI+DQomZ3Q7IG1hbnkgc3BlY3MuLi4gPGJyPg0KJmd0OyAmZ3Q7IEJU
Vyxob3cgdG8gYWRkIHNvbWUgc2FsdCB0byBtYWtlIENHQSByYW5kb21pemVkIGFzIHByaXZhY3kg
PGJyPg0KJmd0OyBhZGRyZXNzPyBTaW5jZSBwdWJsaWMga2V5IGhhcyA8YnI+DQomZ3Q7ICZndDsg
dG8gYmUga293biB0byByZWNlaXZlci4gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRoZSBDR0EgaWRl
bnRpZmllcnMgcmVzdWx0IGZyb20gdGhlIGhhc2ggb2YgYSBtb2RpZmllciwgYSBzdWJuZXQgPGJy
Pg0KJmd0OyBwcmVmaXgsIGEgY29sbGlzaW9uIGNvdW50IGFuZCBjZXJ0aWZpY2F0ZS4gQSBzaW1w
bGUgd2F5IHRvIGdldCA8YnI+DQomZ3Q7IHByaXZhY3kgcHJvcGVydGllcyBpcyB0byBwaWNrIGEg
bmV3IGtleS4gRmFpbGluZyB0aGF0LCB0aGUgMTI4IGJpdA0KPGJyPg0KJmd0OyBtb2RpZmllciBj
YW4gYmUgc2V0IHRvIGFueSByYW5kb20gdmFsdWUsIGFzIGxvbmcgYXMgdGhlIGhhc2ggPGJyPg0K
Jmd0OyBwcm9wZXJ0aWVzIGFyZSByZXNwZWN0ZWQuIEdyYW50ZWQsIHRoZSBudW1iZXIgb2YgdmFs
aWQgdmFsdWVzIDxicj4NCiZndDsgZGVwZW5kcyBvbiB0aGUgc2VjIGZpZWxkLCBidXQgZm9yIGxv
dyB2YWx1ZXMgb2Ygc2VjLCBvbmUgY2FuIGp1c3QNCjxicj4NCiZndDsgcGljayBhIG1vZGlmaWVy
IHNlZWQgYXQgcmFuZG9tLCB0aGVuIHNlYXJjaCBmb3IgdGhlIHZhbHVlIHRoYXQgPGJyPg0KJmd0
OyBwcm92aWRlcyB0aGUgcmlnaHQgaGFzaC4gPGJyPg0KRmFpbGVkIHRvIGNhdGNoIHdoYXQgeW91
IGV4YWN0bHkgbWVhbi48L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPklNSE8sIGEg
bWV0aG9kIGZvciBDR0EgdG8gYmUgcHJpdmFjeSBhZGRyZXNzIGNvdWxkDQpiZSA6PC9mb250Pjwv
dHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5rZWVwIHB1YmxpYyBrZXkgdW5jaGFuZ2VkLCBhbmQg
Y2hvb3NlIGRpZmZlcmVudCBtb2RpZmllcg0KZWFjaCB0aW1lIHNvIGFzIHRvIG9idGFpbiBkaWZm
ZXJlbnQgSVAsIGFuZCA8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPm9ubHkgd2hl
biBhZGRyZXNzIG93bmVyc2hpcCBpcyByZXF1aXJlZCwgc2VuZCBDR0ENCnBhcmFtZXRlciBpbmNs
dWRpbmcgbW9kaWVmZXIsIHB1YmxpYyBrZXksZXRjLiA8L2ZvbnQ+PC90dD4NCjxicj4NCjxicj48
dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBDR0Egbm9kZXMgb25seSBoYXZlIHRvIGRp
c2Nsb3NlIHRoZWlyIHB1YmxpYyBrZXkgaWYgdGhleSB3YW50IHRvIDxicj4NCiZndDsgcHJvdmUg
dGhlaXIgaWRlbnRpdHkuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEJ1dCBhcyBJIG9ic2VydmVkIHBy
ZXZpb3VzbHksIHdlIGhhdmUgbW9yZSB0aGFuIGVub3VnaCBzcGVjcyBhcm91bmQNCmFscmVhZHku
Li48YnI+DQomZ3Q7IDxicj4NCiZndDsgLS0gQ2hyaXN0aWFuIEh1aXRlbWE8YnI+DQomZ3Q7IDxi
cj4NCiZndDsgPGJyPg0KPC9mb250PjwvdHQ+DQo=
--=_alternative 0020342848257B64_=--

From washam.fan@gmail.com  Mon May  6 23:20:42 2013
Return-Path: <washam.fan@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69C9D21F85D6; Mon,  6 May 2013 23:20:42 -0700 (PDT)
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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJ-JGL-d2-cq; Mon,  6 May 2013 23:20:37 -0700 (PDT)
Received: from mail-vc0-f170.google.com (mail-vc0-f170.google.com [209.85.220.170]) by ietfa.amsl.com (Postfix) with ESMTP id 20E0E21F85C9; Mon,  6 May 2013 23:20:37 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id gf12so168520vcb.29 for <multiple recipients>; Mon, 06 May 2013 23:20:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DY8M6B1BfBEUg8oPOFB/sNvjN2J/5hbgn4yGLwQlcRE=; b=nQReyIITUCNdx+cl3DPJeADAitXYI7iLziBulvbwfzJBCwKliW58qZXZhEUcjNM9uX 9bfjVMoMuOJXXz0NKjXAq/SUcjA4Hs2KRG9FSFlPeTQ+PBlGArYh/ONnJI+dluBg0dbM 4ZCg5SM/R82MJZhfpX2emYZnrURumE/VPtgSdWWwNQlF5zLkTMb7+3f0AzF4TcgqeBCK x+EtLFxF6WwKLE6NLXBuwIi4bQ/ldxAEbQ+mvBaTblVaPj30Od3P3PKWfMp8moauzitH BmhfOMlypAzwZlDrp+hJ+ql3pMEovL3smyab/vHBptwbdnq1rqnbVTaO1rnq5KQceBCF rIjw==
MIME-Version: 1.0
X-Received: by 10.220.177.8 with SMTP id bg8mr326961vcb.35.1367907636464; Mon, 06 May 2013 23:20:36 -0700 (PDT)
Received: by 10.220.29.6 with HTTP; Mon, 6 May 2013 23:20:36 -0700 (PDT)
In-Reply-To: <20130506225104.23771.43608.idtracker@ietfa.amsl.com>
References: <20130506225104.23771.43608.idtracker@ietfa.amsl.com>
Date: Tue, 7 May 2013 14:20:36 +0800
Message-ID: <CAAuHL_AoN7U3718R-SAGDYuA1y7wv3-f777W78kaSms20aQLdw@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-01.txt
From: Washam Fan <washam.fan@gmail.com>
To: internet-drafts@ietf.org
Content-Type: multipart/alternative; boundary=001a11c2c5eec1d27d04dc1ad093
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, i-d-announce@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 06:20:42 -0000

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

one question after i read this draft.
section 2.1:

   On non-multicast links, the hosts following this specification MUST
   continue retransmitting the RSs even after an RA that results in a
   default route is received.  This is required because, in such links,
   sending an RA can only be triggered by an RS.


Are you saying RSs will be ALWAYS (re)transmitted in an exponential backoff
way regardless of RA received or not.? In other words, RSs will end up
being retransmitted every 1 hour (according to MRT=3600 defined in previous
section)?

Just want to a confirmation. No objection from me.

Thanks,
washam

2013/5/7 <internet-drafts@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           : Packet loss resiliency for Router Solicitations
>         Author(s)       : Suresh Krishnan
>                           Dmitry Anipko
>                           Dave Thaler
>         Filename        : draft-ietf-6man-resilient-rs-01.txt
>         Pages           : 7
>         Date            : 2013-05-06
>
> Abstract:
>    When an interface on a host is initialized, the host transmits Router
>    Solicitations in order to minimize the amount of time it needs to
>    wait until the next unsolicited multicast Router Advertisement is
>    received.  In certain scenarios, these router solicitations
>    transmitted by the host might be lost.  This document specifies a
>    mechanism for hosts to cope with the loss of the initial Router
>    Solicitations.  Furthermore, on some links, unsolicited multicast
>    Router Advertisements are never sent and the mechanism in this
>    document is intended to work even in such scenarios.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-resilient-rs-01
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<div dir=3D"ltr"><div>one question after i read this draft.<br></div>sectio=
n 2.1:<br><div><div><div class=3D"gmail_extra"><pre class=3D"">   On non-mu=
lticast links, the hosts following this specification MUST
   continue retransmitting the RSs even after an RA that results in a
   default route is received.  This is required because, in such links,
   sending an RA can only be triggered by an RS.</pre><br></div><div class=
=3D"gmail_extra">Are you saying RSs will be ALWAYS (re)transmitted in an ex=
ponential backoff way regardless of RA received or not.? In other words, RS=
s will end up being retransmitted every 1 hour (according to MRT=3D3600 def=
ined in previous section)?<br>
<br></div><div class=3D"gmail_extra">Just want to a confirmation. No object=
ion from me.<br><br></div><div class=3D"gmail_extra">Thanks,<br>washam<br><=
br></div><div class=3D"gmail_extra"><div class=3D"gmail_quote">2013/5/7  <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_=
blank">internet-drafts@ietf.org</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=A0This draft is a work item of the IPv6 Maintenance Working Group of the I=
ETF.<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Packet loss resiliency for Rout=
er Solicitations<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Suresh Krishnan<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Dmitry Anipko<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Dave Thaler<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-6man-resilient-rs-01.t=
xt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 7<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-05-06<br>
<br>
Abstract:<br>
=A0 =A0When an interface on a host is initialized, the host transmits Route=
r<br>
=A0 =A0Solicitations in order to minimize the amount of time it needs to<br=
>
=A0 =A0wait until the next unsolicited multicast Router Advertisement is<br=
>
=A0 =A0received. =A0In certain scenarios, these router solicitations<br>
=A0 =A0transmitted by the host might be lost. =A0This document specifies a<=
br>
=A0 =A0mechanism for hosts to cope with the loss of the initial Router<br>
=A0 =A0Solicitations. =A0Furthermore, on some links, unsolicited multicast<=
br>
=A0 =A0Router Advertisements are never sent and the mechanism in this<br>
=A0 =A0document is intended to work even in such scenarios.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs" t=
arget=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-6man-resilient=
-rs</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01</a=
><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-resilient-rs-=
01" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-re=
silient-rs-01</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<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>
</blockquote></div><br></div></div></div></div>

--001a11c2c5eec1d27d04dc1ad093--

From sm@resistor.net  Tue May  7 00:07:40 2013
Return-Path: <sm@resistor.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3FE21F90B9 for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmuiaY6t8DIh for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:07:39 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F82C21F9080 for <ipv6@ietf.org>; Tue,  7 May 2013 00:07:38 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4777Wb4023882; Tue, 7 May 2013 00:07:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367910457; bh=vtJ0ZOljP0qKiJU5FbdHJBCZghCJV8K5Y136/LYzRL8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xJ5SDBOtKP5u5p68zlPs9PPey/gTfbUX2X3sliQeW+aw/caVbASiM/vNXNO8j0vH8 sBI+u5kTrRvxmkf4rvI9ck4BxCEuMwQE50ai676NQN1RD6GQ3AqM2stZq5S54eDvEq fQ09Lr7eVdQkqc7jZbSngxRGUR1bbmn6U6w890vY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367910457; i=@resistor.net; bh=vtJ0ZOljP0qKiJU5FbdHJBCZghCJV8K5Y136/LYzRL8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZZA6LNpT90T+Ru3WUWECNjJwni5pgmTj/KHw2Bc7m896pI7TigIZBD0dgSFMNdPhZ FicX/HrP49kxOjbNuH1Z+FVBp8xV1zdxDxcpDMc/U2j10jfzQZQ0g1UEyYPGf5glkI 0REI8+R1iHRD5LqSFmilt3aMIiz5Os8vlSy2PvVc=
Message-Id: <6.2.5.6.2.20130506231929.0b647f30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 07 May 2013 00:07:30 -0700
To: Sujing Zhou <zhou.sujing@zte.com.cn>
From: SM <sm@resistor.net>
Subject: Re: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
In-Reply-To: <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@ zte.com.cn>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com> <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 07:07:40 -0000

Hi Sujing,
At 22:07 06-05-2013, Sujing Zhou wrote:
>Considering the current level of IPv6 deployment, we have got so many specs...

Yes.

Here's what is read: "IPv6 is a well-defined set of completed standards."

Here's what is seen: "Lots of RFCs, both 'standard track' and 
informational, and IETF drafts floating around." [1][2]

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg79157.html
2. http://ripe58.ripe.net/content/presentations/ietf-update.pdf  


From ietf@rozanak.com  Tue May  7 00:31:35 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E087221F8EB9 for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:31:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wWlJL3nuXLh for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:31:31 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 2374121F899E for <ipv6@ietf.org>; Tue,  7 May 2013 00:31:31 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MAQc6-1Ugj7G2tDu-00BJHc; Tue, 07 May 2013 03:31:29 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Christian Huitema'" <huitema@microsoft.com>
References: <001201ce48fc$0cb092a0$2611b7e0$@rozanak.com>	<51856775.9090809@gmail.com>	<16DE82B6-45EB-4042-A1ED-B0DFFAF6489A@gmail.com> <000401ce4a90$60cf0890$226d19b0$@rozanak.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com>
Subject: RE: solution to RFC 4941 I-D action :	draft-rafiee-6man-ra-privacy.txt - 
Date: Tue, 7 May 2013 09:31:20 +0200
Message-ID: <000f01ce4af4$e2b65980$a8230c80$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEIl8rTHwJkn2ThdH61FAwJnuwKbAIHD3r6An3YsK4BNfpE4QH6QFB/mkcOWoA=
Content-Language: en-us
X-Provags-ID: V02:K0:IqiUK6aD6k0vG9eDMYICwxRiCWUdXkOe1az/0hfHqb3 N/BvTer2mx5K/4pgkF4WJEBUWCbNAYPNj5Z3WJQm7w3x5r8kRL EYySHtRx6LohBEc9/j53PNX2ARbouodzWJatR+42keiRRK02J/ lNVmsmB1rvAGfG9mFDlUyws2tn+sI/LLqxLRFQ5PInLj5OlhKh y1W5VFYl3eTmn971rusSJyE2Y1K4M3aA249vslURmU9mXX9WBO VWmbal7NDqWkwqj+7Ynai7Xz9mknIL7cHklEzoQzwqYDo1lZsa fOwqAbacaSLNS3fyPGi1hWsln9mPANDTe9ADJGJdqEb7TAtnYF oxkVuvoL2JpqTP4XugQA=
Cc: 'Bob Hinden' <bob.hinden@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 07:31:36 -0000

> 
> There is a part of me that wishes that we just deploy what we have. There
is
> another part that notices that between IEEE802, privacy addresses, CGA,
stable
> privacy addresses and probably a few more, we have built a nice mess and
> maybe we should clean it up. For example, we could decree that composing
> and IID from a MAC address is obsolete, and we could unify CGA and other
> privacy addresses. Add some salt can make the CGA addresses as randomized
> as the privacy addresses; change the lifetime of the key and you get
whatever
> address lifetime is deemed appropriate. But then, the best part of me
observes
> that with the current level of IPv6 deployment, maybe we don't have an
urgent
> need for more specs...
> 

This has been already stated in CGA RFC
http://tools.ietf.org/html/rfc3972#section-7.3 . The problem with CGA
deployment is not privacy, but the computational costs and the RPKI. It does
not need to merge to any other draft to fulfill the privacy. This is why I
am trying to address that problem in my other draft and find the simplest
way. I think the use of ECC is a good option but I will publish my results
soon.

Regards,
Hosnieh




From ietf@rozanak.com  Tue May  7 00:36:53 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4474721F8F62; Tue,  7 May 2013 00:36:53 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1j0BcCEyAbXZ; Tue,  7 May 2013 00:36:47 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8B521F8FA5; Tue,  7 May 2013 00:36:45 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0M6icu-1UNStB3mg0-00wuKu; Tue, 07 May 2013 03:36:41 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Sujing Zhou'" <zhou.sujing@zte.com.cn>, "'Christian Huitema'" <huitema@microsoft.com>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com> <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
In-Reply-To: <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn>
Subject: RE: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Date: Tue, 7 May 2013 09:36:29 +0200
Message-ID: <001001ce4af5$9c648780$d52d9680$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFk0iKxT4d3gwN4h2jjvx8t0+fCYJnMRang
Content-Language: en-us
X-Provags-ID: V02:K0:QFb3lYU3C1HX10nW+/Ty5FbpOj6Z0yWbmaB0asMIuh4 cumTRzoUxahEXL//MvjXD1xVTtRT7S7E+DhlA4yCC6bi+Z3jam hW5KgK99OC6+FZej0x6VUyC0z4IMpKBlF5F3A0JLbEBgetzkGH ycEEvRGBYLPpdkGJ/n6b3yQ2fYupTl7CWq3+NN2qoQ1DUm+5uY ZI8C005akTOdLIm8tYkV1FqMeMYUECX/i1+EdtP+gSyKKS3IIo Z7w0pWMPk89bfERr3evimKbNdp0vRDrKeFuYMfy2YZrPPvapbB jbwA9ix9R++oNWdQij5Jnl2ofqgDSUKhh6v+nk3PtTaUjSoH0W RGPZ2DMMqH9uDlCGmxKU=
Cc: ipv6-bounces@ietf.org, ipv6@ietf.org, 'Bob Hinden' <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 07:36:53 -0000

>BTW,how to add some salt to make CGA randomized as provacy address? Since
public key has 
>to be kown to receiver.

CGA provides local link security. So the public key is only exposed within
the same network and it is not published on the internet. The privacy is not
important if you are in the same network as other nodes. It is because if
you try to have privacy by your IP, your MAC address can expose your real
identity (if we skip talking about MAC address spoofing).

Regards,
Hosnieh


From ietf@rozanak.com  Tue May  7 00:50:59 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB1D121F8E63 for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:50:58 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyCV3-ktD3eh for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 00:50:54 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 40DE721F8BBA for <ipv6@ietf.org>; Tue,  7 May 2013 00:50:54 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MRGbv-1UznAo3qZz-00U8yR; Tue, 07 May 2013 03:50:49 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'SM'" <sm@resistor.net>, "'Sujing Zhou'" <zhou.sujing@zte.com.cn>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com>	<OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn> <6.2.5.6.2.20130506231929.0b647f30@resistor.net>
In-Reply-To: <6.2.5.6.2.20130506231929.0b647f30@resistor.net>
Subject: RE: RE: solution to RFC 4941 I-D action :	draft-rafiee-6man-ra-privacy.txt -
Date: Tue, 7 May 2013 09:50:41 +0200
Message-ID: <001401ce4af7$962f8fc0$c28eaf40$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH6QFB/qNl13OpkUL0HYUqLOI9edQFk0iKxARC6ZdeYjb+lUA==
Content-Language: en-us
X-Provags-ID: V02:K0:80NuFSXQvtKGIoj0W5r7vJ8EhPhnvVvdxr+eQUKcESJ XggULSOHroaRfjZIKDM2P1VW3d16TkJfl62n7tnwmQKVpt8uTv /+Qqqp10R8ifTANe2dvM2SpMdGIHlG4967OarZe1S6lwpxQFW5 VnIp2IEpg5+k+6/BQtNteE7yVWkHoY0SfYY5xNOm26n5TPWSlG 8Gl+KP+mF2IJ7hKV3q1rhRvKPNLBVGXv/HwVtMfBWaPiX++cMP PrxmiDL5YgcqB2c9RmAhWeKg+1Y3sI7iJsh1mcg4VQNOAH0X6s 01fcjJ0FWXO75hLE+uqNwg25DfTm76MNVn10A6+rjB7fcwM7EN 19sa9OlX6op3ytHUi1Hs=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 07:50:59 -0000

> Here's what is read: "IPv6 is a well-defined set of completed standards."
> 
> Here's what is seen: "Lots of RFCs, both 'standard track' and
informational, and
> IETF drafts floating around." [1][2]
> 
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg79157.html
> 2. http://ripe58.ripe.net/content/presentations/ietf-update.pdf
> 

In my opinion, it is better to update the current RFCs or obsolete them
instead of adding more specifications which will result on confusing
vendors. Of course, it is my point of view and some people are disagree with
that. They would like to have several optional standards and let the
implementers to choose. 

Hosnieh




From ietf@rozanak.com  Tue May  7 01:09:54 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A73321F8DFC for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 01:09:54 -0700 (PDT)
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_33=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZpcTsfhP2Yy9 for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 01:09:50 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id DBB5C21F8DCF for <ipv6@ietf.org>; Tue,  7 May 2013 01:09:49 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MUpds-1V3LZk3mBg-00YSrE; Tue, 07 May 2013 04:09:48 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Sujing Zhou'" <zhou.sujing@zte.com.cn>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E73A@tk5ex14mbxc272.redmond.corp.microsoft.com> <OF152AE090.032B00CE-ON48257B64.001F94C4-48257B64.00203428@zte.com.cn>
In-Reply-To: <OF152AE090.032B00CE-ON48257B64.001F94C4-48257B64.00203428@zte.com.cn>
Subject: RE: RE: RE: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt -
Date: Tue, 7 May 2013 10:09:40 +0200
Message-ID: <002701ce4afa$3d1419d0$b73c4d70$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH3i90EYrq0zbcBJnbXgATgX/BVjpim2gxQ
Content-Language: en-us
X-Provags-ID: V02:K0:Y+ojjQu0zG3H+n9qjM2SRaoihqqM6rB/CeUzJ+6/tGR 7kPYUrO0wX8+JunKlXYL7/PBOv+OXsn+nFqa8gnirwT2MiPsVJ 7Sq4emDbzu3IGm9E+DP/2xH1hCDkWtNOxd+0ZXETzUPdSC12+r Chsk4A61st+DGX1Bo+NoScBNOqdHZMvMILJYwpIIyyEQAk1CFf gvnM14cKR5Pg4zz+NafTnqmPaUwN13mDpsVzoawrGmd2eqmInu j96703GMEZPRSPmO+BShKhMXlIZDrR0RbB0sN47zh+7rw5JSW3 pihGkjPNXpjf5kRYc6zvrVIbkcUKmZEjWIoX7bIo0gMz0ewn7N w1KxqPaAsRC14zCKLIQk=
Cc: 'Christian Huitema' <huitema@microsoft.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 08:09:54 -0000

>Failed to catch what you exactly mean. 
>IMHO, a method for CGA to be privacy address could be : 
>keep public key unchanged, and choose different modifier each time so as to
obtain different IP, and 
>only when address ownership is required, send CGA parameter including
modiefer, public key,etc. 

Different modifier will result in doing the whole CGA computation again
otherwise you use sec value 0. So it does not matter whether you use the
same public/private key or you regenerate the new one as mentioned in the
following links:
http://link.springer.com/chapter/10.1007%2F978-3-642-37119-6_10#page-1
http://tools.ietf.org/html/rfc3972#section-7.3

The problem with CGA is different and not privacy. 

Hosnieh





From ietf@rozanak.com  Tue May  7 01:42:14 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4AE021F8FB2; Tue,  7 May 2013 01:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8ldN-4fPW69; Tue,  7 May 2013 01:42:07 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 5750C21F8F83; Tue,  7 May 2013 01:42:07 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LvVEJ-1URYcM177T-00zqDX; Tue, 07 May 2013 04:42:03 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <edu-discuss@ietf.org>
References: <C91E67751B1EFF41B857DE2FE1F68ABA0FF1E6E1@tk5ex14mbxc272.redmond.corp.microsoft.com> <OF9B334605.3F5D177D-ON48257B64.001C0657-48257B64.001C421C@zte.com.cn> <6.2.5.6.2.20130506231929.0b647f30@resistor.net> <001401ce4af7$962f8fc0$c28eaf40$@rozanak.com> <6.2.5.6.2.20130507010020.0c0667a0@resistor.net> 
In-Reply-To: 
Subject: FW: RE: solution to RFC 4941 I-D action :	draft-rafiee-6man-ra-privacy.txt -
Date: Tue, 7 May 2013 10:41:57 +0200
Message-ID: <000701ce4afe$be9111d0$3bb33570$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH6QFB/qNl13OpkUL0HYUqLOI9edQFk0iKxARC6ZdcB2mM9xQJNr+zymGyKHxCAAAWbYA==
Content-Language: en-us
X-Provags-ID: V02:K0:2ojiJY3FZ9J3ULbzUUC7LuDQgUKyGmKhA2+MRIgXWC5 E58XZhYu4kFxvElJvJlG55gbryRUe/f7MBXutvqw6nVgIiy7iP WpgmorHWfYhBMe1TkzSH6qW65yYsZtMRbMw0uzc7jNWvZjJuq7 yCYTd1LnvNMSp1h2auIeSLG5QJvzYYVjQYOUns9w4XYWfsmXhH yVizXyy2UhFP/Ir1ctwNJfm3bx+F5hVgOnmaHXk/3qIB22fPZP x54y1lO6A++ZNWIGR+n6+8sh78ZpFeMp29As3zHv6cvF+xGRoI 8U9mITxdPyWEN/0HO5Jn/QVpnJ0M2C9+SsnZf7/nSKcQvr8IKY of3cv4E/1n1tLCt3ejtI=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 08:42:15 -0000

Hi,

> >In my opinion, it is better to update the current RFCs or obsolete 
> >them instead of adding more specifications which will result on 
> >confusing vendors. Of course, it is my point of view and some people 
> >are disagree with that. They would like to have several optional 
> >standards and let the implementers to choose.
> 
> Proposed Standards were supposed to be "optional".  Implementers 
> choosing to implement them was a good test for running code (code 
> which is actually used on the Internet).  The specifications can then 
> be published as Standard.  If you don't have time to track all the 
> Proposed Standard you could implement the Standard and achieve at 
> least minimum interoperability.  It does not work in practice.  There 
> isn't any Standard for IPv6.  The Standard for SMTP (email) is old and it
is not worth basing an implementation on that.
> 
> I am curious about what you find difficult about IETF specifications.  
> Note that I am not going to disagree with your opinion or argue that 
> what you said is wrong. :-)
> 

As you stated here, there are some old RFCs that, in my opinion, we do not
know whether or not they still address today's minimum requirements. There
are also some vendors that still using them because they did not see any
update on them. This means we are adding more and more standards while we do
a few efforts to check the old standards and obsolete them or update them. I
do not have any problem with having several options. But I do think that
addressing the current RFCs has more priority on adding new specifications.
In other word, to say whether or not the current RFCs can still address our
needs or they need a few modifications to address our needs, has higher
priority than trying to come up with something that might have the same
impact as we resolve the problem with the current RFCs.  

I heard from some people that their problem of not addressing the old RFC is
backward compatibilities. In my opinion, It is the choice of vendors to
improve their old implementations or just leave it as it is. But by
addressing those RFCs at least the customers know that they did not choose
the best option. This means that the customers will force vendors to improve
their current implementations. Then instead of having thousands of RFCs we
will have some that we can rely on and we are sure that they are not
something not useful. When something does not have our today's requirement
why we need to think about that?! 

Regards,
Hosnieh


From Fred.L.Templin@boeing.com  Tue May  7 15:13:34 2013
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E62611E80BA for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 15:13:34 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILMNe8jRusPR for <ipv6@ietfa.amsl.com>; Tue,  7 May 2013 15:13:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8C711E80A5 for <ipv6@ietf.org>; Tue,  7 May 2013 15:13:29 -0700 (PDT)
Received: from slb-mbsout-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id r47MDSHx018767 for <ipv6@ietf.org>; Tue, 7 May 2013 15:13:29 -0700
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id r47MDSTD018764 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <ipv6@ietf.org>; Tue, 7 May 2013 15:13:28 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.93]) by XCH-PHX-112.sw.nos.boeing.com ([169.254.12.24]) with mapi id 14.02.0328.011; Tue, 7 May 2013 15:13:28 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-resilient-rs-01.txt
Thread-Topic: I-D Action: draft-ietf-6man-resilient-rs-01.txt
Thread-Index: AQHOSqxV6hLjkyQcO0OB4QaU570LJJj6Sphw
Date: Tue, 7 May 2013 22:13:27 +0000
Message-ID: <2134F8430051B64F815C691A62D9831807019A@XCH-BLV-504.nw.nos.boeing.com>
References: <20130506225104.23771.43608.idtracker@ietfa.amsl.com>
In-Reply-To: <20130506225104.23771.43608.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 07 May 2013 22:13:34 -0000

I support this work.

Fred

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-
> bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Monday, May 06, 2013 3:51 PM
> To: i-d-announce@ietf.org
> Cc: ipv6@ietf.org
> Subject: I-D Action: draft-ietf-6man-resilient-rs-01.txt
>=20
>=20
> 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.
>=20
> 	Title           : Packet loss resiliency for Router Solicitations
> 	Author(s)       : Suresh Krishnan
>                           Dmitry Anipko
>                           Dave Thaler
> 	Filename        : draft-ietf-6man-resilient-rs-01.txt
> 	Pages           : 7
> 	Date            : 2013-05-06
>=20
> Abstract:
>    When an interface on a host is initialized, the host transmits
> Router
>    Solicitations in order to minimize the amount of time it needs to
>    wait until the next unsolicited multicast Router Advertisement is
>    received.  In certain scenarios, these router solicitations
>    transmitted by the host might be lost.  This document specifies a
>    mechanism for hosts to cope with the loss of the initial Router
>    Solicitations.  Furthermore, on some links, unsolicited multicast
>    Router Advertisements are never sent and the mechanism in this
>    document is intended to work even in such scenarios.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-01
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-resilient-rs-01
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From trac+6man@trac.tools.ietf.org  Wed May  8 13:08:09 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D45921F8AE2 for <ipv6@ietfa.amsl.com>; Wed,  8 May 2013 13:07:55 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IueGCquh8-g3 for <ipv6@ietfa.amsl.com>; Wed,  8 May 2013 13:07:52 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3D121F8ADF for <6man@ietf.org>; Wed,  8 May 2013 13:07:51 -0700 (PDT)
Received: from localhost ([127.0.0.1]:37451 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1UaAeO-0007UZ-DK; Wed, 08 May 2013 22:07:44 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, otroan@employees.org
X-Trac-Project: 6man
Date: Wed, 08 May 2013 20:07:44 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: [6man] #3: Need for DAD counter
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/6man/trac/ticket/3
Message-ID: <062.becdaf063337699f365a7122b8d664cb@trac.tools.ietf.org>
X-Trac-Ticket-ID: 3
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, otroan@employees.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: fgont@si6networks.com
Resent-Message-Id: <20130508200752.1C3D121F8ADF@ietfa.amsl.com>
Resent-Date: Wed,  8 May 2013 13:07:51 -0700 (PDT)
Resent-From: trac+6man@trac.tools.ietf.org
X-Mailman-Approved-At: Wed, 08 May 2013 13:24:20 -0700
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 May 2013 20:08:09 -0000

#3: Need for DAD counter

 Your draft attempts to make the fallback predictable, by incorporating a
 DAD counter in the seeds of your nominal algorithm. But that means
 redefining the solution a only a guarantee that "the visiting host will
 have one of the same 2 or 3 addresses on the visited network." I am not
 sure it is worth the additional complexity, by opposition to just saying,
 "in case of collision, pick a new number."

-- 
-------------------------------------+-------------------------------------
 Reporter:  otroan@employees.org     |      Owner:  draft-ietf-6man-stable-
     Type:  defect                   |  privacy-addresses@tools.ietf.org
 Priority:  minor                    |     Status:  new
Component:  stable-privacy-          |  Milestone:
  addresses                          |    Version:
 Severity:  Active WG Document       |   Keywords:
-------------------------------------+-------------------------------------

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


From trac+6man@trac.tools.ietf.org  Wed May  8 13:14:09 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 076B521F8ECA for <ipv6@ietfa.amsl.com>; Wed,  8 May 2013 13:14:09 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4mBGR32YwOZ for <ipv6@ietfa.amsl.com>; Wed,  8 May 2013 13:14:08 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 408C721F8EBF for <6man@ietf.org>; Wed,  8 May 2013 13:14:07 -0700 (PDT)
Received: from localhost ([127.0.0.1]:37826 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1UaAkW-0001OC-A9; Wed, 08 May 2013 22:14:04 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, otroan@employees.org
X-Trac-Project: 6man
Date: Wed, 08 May 2013 20:14:04 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: [6man] #4: Normative section / Informational section
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/6man/trac/ticket/4
Message-ID: <062.0392147e793968fe69748976d23b0b94@trac.tools.ietf.org>
X-Trac-Ticket-ID: 4
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, otroan@employees.org, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: fgont@si6networks.com
Resent-Message-Id: <20130508201408.408C721F8EBF@ietfa.amsl.com>
Resent-Date: Wed,  8 May 2013 13:14:07 -0700 (PDT)
Resent-From: trac+6man@trac.tools.ietf.org
X-Mailman-Approved-At: Wed, 08 May 2013 13:24:20 -0700
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 08 May 2013 20:14:09 -0000

#4: Normative section / Informational section

 After reading the document again, the main issue is that the document
 specifies a solution to a problem by detailing a specific implementation,
 but does not explain the design choices behind that solution. As such, we
 end up with an over constrained specification, which at the same time
 fails to explain the problems at hand. The specification aims at providing
 addresses that are "stable and different," so that the same host
 connecting will have different and uncorrelated addresses when connecting
 to different networks, but will keep the same address when connecting
 repeatedly to the same network.

 As Mike St-Johns pointed out, the solution is trivial: create a different
 random number each time the host connect to a new network; make sure that
 the same random number is reused if the host reconnect to the same
 network. The latter property can be achieved either by keeping of log of
 previously visited networks and the corresponding address, or by using a
 "master random number" and combining it with the identification of the
 visited network. In theory, that's about all what the IETF ought to
 specify.

 Instead, the draft goes into great details on how to actually implement
 the random number generator. Apart from not being necessary, some of these
 details are wrong. For example, the suggested algorithm includes an
 "interface index," but different operating systems have different ways of
 enumerating interfaces, and the variations in enumeration could end up
 violating the "stable address" property.

 I would suggest reworking the draft to separate a normative section,
 effectively a variation of the 3 lines paragraph above, and an
 informational section, the current specification of the algorithm as  "an
 example of a way to achieve this result if the operating system meets
 certain condition, like stable interface identifiers."

 I would also explain the inherent issues that have to be solved, e.g.,
 swapping interfaces, or enabling multi-homed hosts. And I would observe
 that the DAD problem cannot be solved ina  reliable way.

-- 
-------------------------------------+-------------------------------------
 Reporter:  otroan@employees.org     |      Owner:  draft-ietf-6man-stable-
     Type:  defect                   |  privacy-addresses@tools.ietf.org
 Priority:  major                    |     Status:  new
Component:  stable-privacy-          |  Milestone:
  addresses                          |    Version:
 Severity:  Active WG Document       |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/6man/trac/ticket/4>
6man <http://tools.ietf.org/wg/6man/>


From ietf@rozanak.com  Tue May 14 13:37:43 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFD2D21F8F4F for <ipv6@ietfa.amsl.com>; Tue, 14 May 2013 13:37:42 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yjQzZwOQw6jT for <ipv6@ietfa.amsl.com>; Tue, 14 May 2013 13:37:38 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id E5C4E21F81FF for <ipv6@ietf.org>; Tue, 14 May 2013 13:37:37 -0700 (PDT)
Received: from kopoli (g225047160.adsl.alicedsl.de [92.225.47.160]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MNqrr-1UZuKy1Vdr-006dFm; Tue, 14 May 2013 16:37:34 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Bob Hinden" <bob.hinden@gmail.com>, "Christian Huitema" <huitema@microsoft.com>, "Mark Smith" <markzzzsmith@yahoo.com.au>
Subject: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt 
Date: Tue, 14 May 2013 22:37:22 +0200
Message-ID: <000001ce50e2$dc0aa840$941ff8c0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5Q4tCwmKa9QQwiTdOUwi+4KYZP5w==
Content-Language: en-us
X-Provags-ID: V02:K0:b/JU9WMpHK8OrQpLIzF9Tqy+kyGn1ExDWel37pRLR5x gji12zxMaP2FEKaEuVEhUsX/mwh1wuTnishDiVSyhQ0w2T0ZHF WQI/MSkACix/INtnXyS7LFXgnzhjggILWdRsr1sETofdBhtUlw 2ROaFtvNl9aLOyVuRBk8NoY1IBgoWdCVz2x/MW/S+leihy/2Gq RwHkd7XvRtdZFaxnlKYbQErtzxLYwBewgowsqBG4xEJT7KVmt5 kNGZ3USwEuAkWbXqHUhPCxvFEy+bXWdPpUyZ/zg4NpXppWiJER FRvCZ5TsFLn0jtim8/LPtJlO3hWA3AvUtlG57pzd+sokgb2WKd LgVrJ8Dg8EaxfY+taWGw=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 May 2013 20:37:43 -0000

Hello,

A new version of http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy is
available online. I considered the comments that I received and made the
pertinent changes to this version. I also improved the document to better
address the following issues that I have with RFC 4941.
1- lifetime of the IID  
The fact that the node might not generate a new IID when it receives a new
subnet prefix
Solution: Give the router prefix a higher priority than the IID's max
lifetime
2- Nodes may use an IID that was generated based on a MAC address and use
this in their response
A MAC based IID may still be valid and this RFC does not force the node to
stop using it.
 Solution: The node MUST not generate its IID based on a MAC address when
using this approach. The Privacy Extension RFC does not clearly address
this.
3- A better way to handle trouble shooting and debugging 
4-The need to maintain the status of reserved IIDs and already used IIDs
requiring  a large storage space and the fact that the randomization of IIDs
is limited.
Solution: Using modified CGA algorithm skipping the security steps
5-The cutting of connections when the max lifetime for the IID expires

I would be appreciative if you could find the time to review this draft RFC
and offer constructive comments.

Thanks,
Best,
Hosnieh


From wwwrun@rfc-editor.org  Tue May 14 14:13:55 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAB1F21F91BF; Tue, 14 May 2013 14:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.767
X-Spam-Level: 
X-Spam-Status: No, score=-101.767 tagged_above=-999 required=5 tests=[AWL=0.233, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Bda5v0fnvZa; Tue, 14 May 2013 14:13:55 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 6B89221F9049; Tue, 14 May 2013 14:13:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5DE3D72E189; Tue, 14 May 2013 14:13:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6946 on Processing of IPv6 "Atomic" Fragments
From: rfc-editor@rfc-editor.org
Message-Id: <20130514211350.5DE3D72E189@rfc-editor.org>
Date: Tue, 14 May 2013 14:13:50 -0700 (PDT)
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 14 May 2013 21:13:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6946

        Title:      Processing of IPv6 "Atomic" Fragments 
        Author:     F. Gont
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2013
        Mailbox:    fgont@si6networks.com
        Pages:      9
        Characters: 18843
        Updates:    RFC 2460, RFC 5722

        I-D Tag:    draft-ietf-6man-ipv6-atomic-fragments-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6946.txt

The IPv6 specification allows packets to contain a Fragment Header
without the packet being actually fragmented into multiple pieces (we
refer to these packets as "atomic fragments").  Such packets are
typically sent by hosts that have received an ICMPv6 "Packet Too Big"
error message that advertises a Next-Hop MTU smaller than 1280 bytes,
and are currently processed by some implementations as normal
"fragmented traffic" (i.e., they are "reassembled" with any other
queued fragments that supposedly correspond to the same original
packet).  Thus, an attacker can cause hosts to employ atomic
fragments by forging ICMPv6 "Packet Too Big" error messages, and then
launch any fragmentation-based attacks against such traffic.  This
document discusses the generation of the aforementioned atomic
fragments and the corresponding security implications.  Additionally,
this document formally updates RFC 2460 and RFC 5722, such that IPv6
atomic fragments are processed independently of any other fragments,
thus completely eliminating the aforementioned attack vector.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  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

From trac+6man@trac.tools.ietf.org  Thu May 16 20:23:47 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF9211E80F3 for <ipv6@ietfa.amsl.com>; Thu, 16 May 2013 20:23:46 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHAmgPQdmSZV for <ipv6@ietfa.amsl.com>; Thu, 16 May 2013 20:23:46 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 06F3E11E80E4 for <6man@ietf.org>; Thu, 16 May 2013 20:23:42 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49402 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1UdBGf-0006PJ-Rw; Fri, 17 May 2013 05:23:41 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com
X-Trac-Project: 6man
Date: Fri, 17 May 2013 03:23:41 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: Re: [6man] #3: Need for DAD counter
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/6man/trac/ticket/3#comment:1
Message-ID: <077.893aabc14481717bef507a4d060b4a6b@trac.tools.ietf.org>
References: <062.becdaf063337699f365a7122b8d664cb@trac.tools.ietf.org>
X-Trac-Ticket-ID: 3
In-Reply-To: <062.becdaf063337699f365a7122b8d664cb@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: fgont@si6networks.com
Resent-Message-Id: <20130517032346.06F3E11E80E4@ietfa.amsl.com>
Resent-Date: Thu, 16 May 2013 20:23:42 -0700 (PDT)
Resent-From: trac+6man@trac.tools.ietf.org
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 17 May 2013 03:23:49 -0000

#3: Need for DAD counter


Comment (by fgont@si6networks.com):

 Actually, it makes the algorithm simpler. By including DAD_counter, it's
 trivial to generate another Interface-ID with the same algorithm. Whereas
 if we were to select a "random interface ID" upon a DAD failure, the code
 would follow a different path (a.g., a call to rand()).

 Additionally, it's certainly better to, in the worst case scenario, have
 the address vary among, say, two options, than having a different address
 each time the host is bootstrapped.

-- 
-------------------------------------+-------------------------------------
 Reporter:  otroan@employees.org     |       Owner:  draft-ietf-6man-
     Type:  defect                   |  stable-privacy-
 Priority:  minor                    |  addresses@tools.ietf.org
Component:  stable-privacy-          |      Status:  new
  addresses                          |   Milestone:
 Severity:  Active WG Document       |     Version:
 Keywords:                           |  Resolution:
-------------------------------------+-------------------------------------

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


From trac+6man@trac.tools.ietf.org  Thu May 16 20:25:04 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20A1811E80E4 for <ipv6@ietfa.amsl.com>; Thu, 16 May 2013 20:25:04 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZH3zuvM8gUMl for <ipv6@ietfa.amsl.com>; Thu, 16 May 2013 20:25:03 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3EF11E80A3 for <6man@ietf.org>; Thu, 16 May 2013 20:25:03 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49447 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1UdBHx-0006O8-J3; Fri, 17 May 2013 05:25:01 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com
X-Trac-Project: 6man
Date: Fri, 17 May 2013 03:25:01 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: Re: [6man] #3: Need for DAD counter
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/6man/trac/ticket/3#comment:2
Message-ID: <077.5c55255646a4f3433c6a1cd5c71772fb@trac.tools.ietf.org>
References: <062.becdaf063337699f365a7122b8d664cb@trac.tools.ietf.org>
X-Trac-Ticket-ID: 3
In-Reply-To: <062.becdaf063337699f365a7122b8d664cb@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: fgont@si6networks.com
Resent-Message-Id: <20130517032503.7A3EF11E80A3@ietfa.amsl.com>
Resent-Date: Thu, 16 May 2013 20:25:03 -0700 (PDT)
Resent-From: trac+6man@trac.tools.ietf.org
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 17 May 2013 03:25:04 -0000

#3: Need for DAD counter

Changes (by fgont@si6networks.com):

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


-- 
-------------------------------------+-------------------------------------
 Reporter:  otroan@employees.org     |       Owner:  draft-ietf-6man-
     Type:  defect                   |  stable-privacy-
 Priority:  minor                    |  addresses@tools.ietf.org
Component:  stable-privacy-          |      Status:  closed
  addresses                          |   Milestone:
 Severity:  Active WG Document       |     Version:
 Keywords:                           |  Resolution:  wontfix
-------------------------------------+-------------------------------------

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


From trac+6man@trac.tools.ietf.org  Sun May 19 09:55:38 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D1E21F8721 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 09:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.149
X-Spam-Level: 
X-Spam-Status: No, score=-101.149 tagged_above=-999 required=5 tests=[AWL=-1.450, BAYES_00=-2.599, J_CHICKENPOX_16=0.6, MANGLED_OFF=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6b4dFY-MkTs0 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 09:55:38 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 0600E21F871D for <6man@ietf.org>; Sun, 19 May 2013 09:55:37 -0700 (PDT)
Received: from localhost ([127.0.0.1]:49865 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1Ue6tU-0001qp-FX; Sun, 19 May 2013 18:55:36 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: fgont@si6networks.com
X-Trac-Project: 6man
Date: Sun, 19 May 2013 16:55:36 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: Re: [6man] #1: Proper source for an "Interface Identifier"
X-Trac-Ticket-URL: http://tools.ietf.org/wg/6man/trac/ticket/1#comment:1
Message-ID: <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org>
References: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org>
X-Trac-Ticket-ID: 1
In-Reply-To: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: fgont@si6networks.com, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 16:55:39 -0000

#1: Proper source for an "Interface Identifier"

Changes (by fgont@si6networks.com):

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


Comment:

 The "Interface Identifier" has now been replaced with a generic
 "Net_Iface" parameter, and we describe what are the required properties
 for this ID. Additionally, Appendix A is devoted to an analysis of
 possible sources for the Net_Iface parameter, and their pros and cons.

 From Section 3:

        RID = F(Prefix, Net_Iface, Network_ID, DAD_Counter, secret_key)

 [....]

        Net_Iface:
           An implementation-dependent stable identifier associated with
           the network interface for which the RID is being generated.
           An implementation MAY provide a configuration option to select
           the source of the identifier to be used for the Net_Iface
           parameter.  A discussion of possible sources for this value
           (along with the corresponding trade-offs) can be found in
           Appendix A.

 [....]

    The Net_Iface is a value that identifies the network interface for
    which an IPv6 address is being generated.  The following properties
    are desirable for the Net_Iface:

    o  it MUST be constant across system bootstrap sequences and other
       network events (e.g., bringing another interface up or down)

    o  it MUST be different for each network interface

    Since the stability of the addresses generated with this method
    relies on the stability of all arguments of F(), it is key that the
    Net_Iface be constant across system bootstrap sequences and other
    network events.  Additionally, the Net_Iface must uniquely identify
    an interface within the node, such that two interfaces connecting to
    the same network do not result in duplicate addresses.  Different
    types of operating systems might benefit from different stability
    properties of the Net_Iface parameter.  For example, a client-
    oriented operating system might want to employ Net_Iface identifiers
    that are attached to the underlying network interface card (NIC),
    such that a removable NIC always gets the same IPv6 address,
    irrespective of the system communications port to which it is
    attached.  On the other hand, a server-oriented operating system
    might prefer Net_Iface identifers that are attached to system slots/
    ports, such that replacement of a network interface card does not
    result in an IPv6 address change.  Appendix A discusses possible
    sources for the Net_Iface, along with their pros and cons.

-- 
--------------------------------------+----------------------------
 Reporter:  fgont@si6networks.com     |       Owner:  Fernando Gont
     Type:  defect                    |      Status:  closed
 Priority:  major                     |   Milestone:
Component:  stable-privacy-addresses  |     Version:
 Severity:  Active WG Document        |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+----------------------------

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


From internet-drafts@ietf.org  Sun May 19 10:06:32 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0830F21F8E46; Sun, 19 May 2013 10:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QqN5hwvDBTP; Sun, 19 May 2013 10:06:30 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB7821F881C; Sun, 19 May 2013 10:06:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-stable-privacy-addresses-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.45
Message-ID: <20130519170630.13051.81006.idtracker@ietfa.amsl.com>
Date: Sun, 19 May 2013 10:06:30 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 17:06:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : A method for Generating Stable Privacy-Enhanced Addresse=
s with IPv6 Stateless Address Autoconfiguration (SLAAC)
	Author(s)       : Fernando Gont
	Filename        : draft-ietf-6man-stable-privacy-addresses-07.txt
	Pages           : 26
	Date            : 2013-05-19

Abstract:
   This document specifies a method for generating IPv6 Interface
   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
   (SLAAC), such that addresses configured using this method are stable
   within each subnet, but the Interface Identifier changes when hosts
   move from one network to another.  This method is meant to be an
   alternative to generating Interface Identifiers based on IEEE
   identifiers, such that the benefits of stable addresses can be
   achieved without sacrificing the privacy of users.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-stable-privacy-addresses=
-07


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


From trac+6man@trac.tools.ietf.org  Sun May 19 10:12:29 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0072021F8E84 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.116
X-Spam-Level: 
X-Spam-Status: No, score=-102.116 tagged_above=-999 required=5 tests=[AWL=0.483, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M9DK7Xlm1A0D for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:12:28 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB2821F8E06 for <6man@ietf.org>; Sun, 19 May 2013 10:12:27 -0700 (PDT)
Received: from localhost ([127.0.0.1]:51278 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1Ue79m-0007lv-Pz; Sun, 19 May 2013 19:12:26 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com
X-Trac-Project: 6man
Date: Sun, 19 May 2013 17:12:26 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: Re: [6man] #4: Normative section / Informational section
X-Trac-Ticket-URL: http://tools.ietf.org/wg/6man/trac/ticket/4#comment:1
Message-ID: <077.0e9a2d113dcfc10d5b2751cb9c36a243@trac.tools.ietf.org>
References: <062.0392147e793968fe69748976d23b0b94@trac.tools.ietf.org>
X-Trac-Ticket-ID: 4
In-Reply-To: <062.0392147e793968fe69748976d23b0b94@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-6man-stable-privacy-addresses@tools.ietf.org, fgont@si6networks.com, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: fgont@si6networks.com
Resent-Message-Id: <20130519171228.2DB2821F8E06@ietfa.amsl.com>
Resent-Date: Sun, 19 May 2013 10:12:27 -0700 (PDT)
Resent-From: trac+6man@trac.tools.ietf.org
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 17:12:29 -0000

#4: Normative section / Informational section

Changes (by fgont@si6networks.com):

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


Comment:

 My response to this post is available at: <http://www.ietf.org/mail-
 archive/web/ietf/current/msg78813.html>

 That said, as noted in another ticket, the current version of the I-D
 (-07) does not require any specific source for the "interface index" or
 the like, but rather specifies a Net_Iface parameter, and discussed
 desired properties for such parameter, and possible sources for it (along
 with a discussion of the pros and cons).

-- 
-------------------------------------+-------------------------------------
 Reporter:  otroan@employees.org     |       Owner:  draft-ietf-6man-
     Type:  defect                   |  stable-privacy-
 Priority:  major                    |  addresses@tools.ietf.org
Component:  stable-privacy-          |      Status:  closed
  addresses                          |   Milestone:
 Severity:  Active WG Document       |     Version:
 Keywords:                           |  Resolution:  fixed
-------------------------------------+-------------------------------------

Ticket URL: <http://tools.ietf.org/wg/6man/trac/ticket/4#comment:1>
6man <http://tools.ietf.org/wg/6man/>


From trac+6man@trac.tools.ietf.org  Sun May 19 10:14:37 2013
Return-Path: <trac+6man@trac.tools.ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCC421F87C5 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Level: 
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQjKhgXNArO6 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:14:37 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5FB21F8749 for <6man@ietf.org>; Sun, 19 May 2013 10:14:37 -0700 (PDT)
Received: from localhost ([127.0.0.1]:51594 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+6man@trac.tools.ietf.org>) id 1Ue7Bs-0006zT-70; Sun, 19 May 2013 19:14:36 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "6man issue tracker" <trac+6man@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: fgont@si6networks.com
X-Trac-Project: 6man
Date: Sun, 19 May 2013 17:14:36 -0000
X-URL: http://tools.ietf.org/wg/6man/
Subject: Re: [6man] #2: Description of issues with traditional SLAAC addresses (embedding IEEE identifiers)
X-Trac-Ticket-URL: http://tools.ietf.org/wg/6man/trac/ticket/2#comment:1
Message-ID: <078.1994a9fb601d63cc9fe28ed65414195e@trac.tools.ietf.org>
References: <063.489b47618ceae4216d09e7f502aceb95@trac.tools.ietf.org>
X-Trac-Ticket-ID: 2
In-Reply-To: <063.489b47618ceae4216d09e7f502aceb95@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: fgont@si6networks.com, 6man@ietf.org
X-SA-Exim-Mail-From: trac+6man@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: 6man@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 17:14:37 -0000

#2: Description of issues with traditional SLAAC addresses (embedding IEEE
identifiers)

Changes (by fgont@si6networks.com):

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


Comment:

 The introduction of this document has been augmented to make the problem
 statement for evident. Additionally, Appendix B has been improved to
 clarify issues that are not fixed by employing temporary addresses
 (RFC4941).

-- 
--------------------------------------+----------------------------
 Reporter:  fgont@si6networks.com     |       Owner:  Fernando Gont
     Type:  enhancement               |      Status:  closed
 Priority:  minor                     |   Milestone:
Component:  stable-privacy-addresses  |     Version:
 Severity:  Active WG Document        |  Resolution:  fixed
 Keywords:                            |
--------------------------------------+----------------------------

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


From fgont@si6networks.com  Sun May 19 10:34:39 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828C821F881C for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:34:39 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLlWGLSkos-T for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 10:34:39 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id E428C21F87D2 for <6man@ietf.org>; Sun, 19 May 2013 10:34:38 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Ue7UN-0007tq-Am; Sun, 19 May 2013 19:33:43 +0200
Message-ID: <51990CE7.7010903@si6networks.com>
Date: Sun, 19 May 2013 14:33:27 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "6man@ietf.org" <6man@ietf.org>
Subject: Revision of draft-ietf-6man-stable-privacy-addresses
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, Jouni Korhonen <jouni.korhonen@nsn.com>, Brian Haberman <brian@innovationslab.net>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 17:34:39 -0000

Folks,

I've posted a rev of the aforementioned document, meant to address the
comments received during IETF LC.

This rev is the result of the IETF LC discussions we had on the 6man wg
list and on the general IETF list, and of off-list discussions with a
number of folks who generously provided input, reviewed proposed
changes, etc.

I'd expect this rev to be "ready to ship" or very close to that. But
please provide your input confirming whether you think that's the case,
or whether there are any remaining issues to be solved.

The rev is available at:
<http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.

A diff from the previous version of the I-D is available at:
<tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-06.txt&url2=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-07.txt>.

Thanks so much!

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





From huitema@microsoft.com  Sun May 19 11:29:36 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8C521F89C3 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 11:29:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHxNcv9iU5Ip for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 11:29:31 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id 8F77221F882A for <6man@ietf.org>; Sun, 19 May 2013 11:29:31 -0700 (PDT)
Received: from BY2FFO11FD020.protection.gbl (10.1.15.204) by BY2FFO11HUB023.protection.gbl (10.1.14.110) with Microsoft SMTP Server (TLS) id 15.0.698.0; Sun, 19 May 2013 18:29:30 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD020.mail.protection.outlook.com (10.1.14.137) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Sun, 19 May 2013 18:29:30 +0000
Received: from TK5EX14MBXC274.redmond.corp.microsoft.com ([169.254.3.26]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0136.001; Sun, 19 May 2013 18:29:07 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
Subject: RE: Revision of draft-ietf-6man-stable-privacy-addresses
Thread-Topic: Revision of draft-ietf-6man-stable-privacy-addresses
Thread-Index: AQHOVLcspeHTOkw7DEaAZjTPDYiZ4pkM07Qw
Date: Sun, 19 May 2013 18:29:06 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF42852@TK5EX14MBXC274.redmond.corp.microsoft.com>
References: <51990CE7.7010903@si6networks.com>
In-Reply-To: <51990CE7.7010903@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.34]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(6806003)(54356001)(79102001)(49866001)(53806001)(74662001)(74502001)(47446002)(51856001)(74366001)(44976003)(46406003)(81342001)(33656001)(81542001)(59766001)(4396001)(74706001)(69226001)(31966008)(46102001)(50466002)(56776001)(77982001)(66066001)(20776003)(47776003)(65816001)(56816002)(54316002)(63696002)(50986001)(47976001)(80022001)(16406001)(558084002)(47736001)(55846006)(76482001)(23726002)(74876001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB023; H:TK5EX14HUBC107.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08512C5403
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, Brian Haberman <brian@innovationslab.net>, Jouni Korhonen <jouni.korhonen@nsn.com>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 18:29:36 -0000

> The rev is available at:
> <http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.

Nice job, Fernando. I have read this revision. I think it fairly reflects t=
he comments from the WG.

-- Christian Huitema



From v6ops@globis.net  Sun May 19 11:50:00 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5289721F8930 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 11:50:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-aFEPyyDIws for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 11:49:59 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id F133021F8470 for <6man@ietf.org>; Sun, 19 May 2013 11:49:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B92FC8700B1; Sun, 19 May 2013 20:49:42 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kglwU0GqCfcS; Sun, 19 May 2013 20:49:42 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 82467870062; Sun, 19 May 2013 20:49:42 +0200 (CEST)
Message-ID: <51991EC0.9030600@globis.net>
Date: Sun, 19 May 2013 20:49:36 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com>
In-Reply-To: <51990CE7.7010903@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, "6man@ietf.org" <6man@ietf.org>, Jouni Korhonen <jouni.korhonen@nsn.com>, Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 18:50:00 -0000

> Fernando Gont <mailto:fgont@si6networks.com>
> 19 May 2013 19:33
> Folks,
>
> I've posted a rev of the aforementioned document, meant to address the
> comments received during IETF LC.
>
> This rev is the result of the IETF LC discussions we had on the 6man wg
> list and on the general IETF list, and of off-list discussions with a
> number of folks who generously provided input, reviewed proposed
> changes, etc.
>
> I'd expect this rev to be "ready to ship" or very close to that. But
> please provide your input confirming whether you think that's the case,
> or whether there are any remaining issues to be solved.
>
> The rev is available at:
> <http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.
>
> A diff from the previous version of the I-D is available at:
> <tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-06.txt&url2=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-07.txt>.
>
> Thanks so much!
>
> Best regards,
> ------------------------------------------------------------------------
I think the draft is looking very good and is "ready to go." I support it.


I'm not 100.00000% convinced by one sentence, but I can live with it.

Quote: "We note that this method is incrementally deployable, since it
does not pose any interoperability implications when deployed on
networks where other nodes do not implement or employ it."

AFAICS there's a very very unlikely race condition scenario where a node
implementing draft-ietf-6man-stable-privacy-addresses could cause a
collision of a link local address with a node implementing existing
SLAAC, because the node running draft-ietf-6man-stable-privacy-addresses
arrived on link first and completes DAD before the SLAAC node connects
to the link.

If the SLAAC node continues to deploy 4862 literally as defined in
Section5.4.5, it will completely shut down IPv6 on the affected
interface, unless it implements the MAY clause in 5.4.5 and continues
IPv6 operation, in which case there will be a possibility of a node that
runs IPv6 on an interface and which configures IPv6 GUA using SLAAC, but
does not have a link-local address on the link. [5.4.5 still bans
assigning any address failing DAD AFAICS, even though IPv6 operation is
permitted on the interface]

If the SLAAC node arrives on link first,
draft-ietf-6man-stable-privacy-addresses will back off, increment (and
presumably remember) the DAD counter and everything will work nominally.

To be clear, I think this is probably more of an issue with
draft-ietf-6man-ug-00 than draft-ietf-6man-stable-privacy-addresses-07.

It does beg the question which node should back off in this case (if
any). Probably the best course of action would be for the SLAAC node to
choose a different link local address. Although this could have
consequences, as e.g. static routes may point to the link local address.

This is already hinted at indraft-ietf-6man-stable-privacy-addresses-07,
Quote:  "Real world data indicates that MAC address reuse is far more
common than assumed [HDMoore].  This means that even IPv6 addresses that
employ (allegedly) unique identifiers (such as IEEE identifiers) might
result in DAD failures, and hence implementations should be prepared to
gracefully handle such occurrences." Which I agree with.

So in summary, I'd be happy if this was put on a "to consider" list for
draft-ietf-6man-ug-0


Some minor nits
s/shouldproduce/should produce/

s/The prefix to be used for SLAAC, as learned from an ICMPv6/ Router
Advertisement message./The prefix to be used for SLAAC, as learned from
an ICMPv6 Router Advertisement message, or the Link-Local IPv6 Unicast
prefix./

s/or when network interface happen/or when network interfaces happen/


/Privacy issues still present when temporary addresses are employed/
/employed/ is not bold after the new line (XML source or rendering
artefact?)
B1.3 has the same /server-like functions/ with /functions/ not in bold,
so it looks like the rendering.


s#It is not unusual for people to assume or expect that all the
security/privacy implications of traditional SLAAC addresses to me
   mitigated when "temporary addresses"#It is not unusual for people to
assume or expect that all security/privacy implications of traditional
SLAAC addresses are mitigated when "temporary addresses"#

Thanks.

regards,
RayH

From jhw@apple.com  Sun May 19 12:32:05 2013
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59EDB21F8517 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 12:32:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Piw13aCixtEh for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 12:32:00 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4F43521F84F5 for <6man@ietf.org>; Sun, 19 May 2013 12:32:00 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay2.apple.com ([17.128.113.67]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN2008BS8VQKT60@mail-out.apple.com> for 6man@ietf.org; Sun, 19 May 2013 12:31:14 -0700 (PDT)
X-AuditID: 11807143-b7f856d000000818-fc-519928818fe7
Received: from [17.113.35.38] (Unknown_Domain [17.113.35.38]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay2.apple.com (Apple SCV relay) with SMTP id 10.39.02072.28829915; Sun, 19 May 2013 12:31:14 -0700 (PDT)
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: james woodyatt <jhw@apple.com>
In-reply-to: <51990CE7.7010903@si6networks.com>
Date: Sun, 19 May 2013 12:31:13 -0700
Message-id: <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com>
References: <51990CE7.7010903@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1752)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKLMWRmVeSWpSXmKPExsUiWKisptukMTPQ4NsfA4uVK+4yWTxZ9YbN gcljyZKfTB4fDvWwBzBFcdmkpOZklqUW6dslcGXcePWZqeAcX0XjhAtsDYytPF2MnBwSAiYS 6w99YoGwxSQu3FvP1sXIxSEk0M0kceHKVHaQBLOAlsSNfy+ZQGxeAT2J9U/esYLYwgKOEkcf bmQEsdkEVCS+Xb4LVMPBwSmgL/HhfwFImEVAVeLl8XZGiDHaEssWvmaGGGMj8ez/GrDxQkAj p+88DWaLCHhJ7D1yhg1kjISArMTi97kTGPlmITliFpIjZiGZuoCReRWjQFFqTmKlkV5iQUFO ql5yfu4mRlBgNRQ672A8tszqEKMAB6MSD2/Dh+mBQqyJZcWVuYcYJTiYlUR49wjNDBTiTUms rEotyo8vKs1JLT7EKM3BoiTOO+H8tEAhgfTEktTs1NSC1CKYLBMHp1QDY3RR6YWHB9W79nHO 8ms5Un593uQnB97+lGdn5JixYrmKQcnEuFlCXmrN3tPuTjn/rurpnUnbt1970f3AUOjtnRqu DWsCEhOYrvzWUFX9nN55aP8BzQu5G/Lr39y5+tv/ZWOwu/vc/VICagcvCTvInG4+u7owUuHS r3yZq53n7HdFW905NmPP9HolluKMREMt5qLiRABydcRUKAIAAA==
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 19:32:05 -0000

On May 19, 2013, at 10:33 , Fernando Gont <fgont@si6networks.com> wrote:
> 
> The rev is available at:
> <http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.
> 
> A diff from the previous version of the I-D is available at:
> <tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-06.txt&url2=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-07.txt>.

I have a problem with the following set of requirements:

   The Net_Iface is a value that identifies the network interface for
   which an IPv6 address is being generated.  The following properties
   are desirable for the Net_Iface:

   o  it MUST be constant across system bootstrap sequences and other
      network events (e.g., bringing another interface up or down)

   o  it MUST be different for each network interface

Some hosts have dynamic logical network interfaces (distinguishable from physical interface), which are created every time the host joins a network, and destroyed when the host separates from a previously joined network.  Examples are typically interfaces that involve signaling systems, point-to-point connection semantics for the link layer, e.g. virtual private networks, automatic tunnels, et cetera.

According to these requirements, such hosts MUST NOT reuse previously generated stable privacy addresses when joining the same network with a new logical interface.  That seems counter to the goal of this standard.

I think hosts need some latitude in these requirements to allow for temporally different network interfaces associated with the same network service from the host's view to have the same identity for the purpose of generating stable privacy addresses.


--
james woodyatt <jhw@apple.com>
core os networking


From fgont@si6networks.com  Sun May 19 13:08:26 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1D421F8529 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:08:26 -0700 (PDT)
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_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHsb-uGanv5c for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:08:25 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id BB48821F84D9 for <6man@ietf.org>; Sun, 19 May 2013 13:08:23 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Ue9tt-000367-1R; Sun, 19 May 2013 22:08:13 +0200
Message-ID: <51993123.3020100@si6networks.com>
Date: Sun, 19 May 2013 17:08:03 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <51991EC0.9030600@globis.net>
In-Reply-To: <51991EC0.9030600@globis.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, "6man@ietf.org" <6man@ietf.org>, Jouni Korhonen <jouni.korhonen@nsn.com>, Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 20:08:26 -0000

Hi, Ray,

Thanks so much for your feedback! -- Please find my comments in-line....

On 05/19/2013 03:49 PM, Ray Hunter wrote:
> I think the draft is looking very good and is "ready to go." I
> support it.

Thanks!



> I'm not 100.00000% convinced by one sentence, but I can live with
> it.
> 
> Quote: "We note that this method is incrementally deployable, since
> it does not pose any interoperability implications when deployed on 
> networks where other nodes do not implement or employ it."
> 
> AFAICS there's a very very unlikely race condition scenario where a
> node implementing draft-ietf-6man-stable-privacy-addresses could
> cause a collision of a link local address with a node implementing
> existing SLAAC, because the node running
> draft-ietf-6man-stable-privacy-addresses arrived on link first and
> completes DAD before the SLAAC node connects to the link.
> 
> If the SLAAC node continues to deploy 4862 literally as defined in 
> Section5.4.5, it will completely shut down IPv6 on the affected 
> interface, unless it implements the MAY clause in 5.4.5 and
> continues IPv6 operation, in which case there will be a possibility
> of a node that runs IPv6 on an interface and which configures IPv6
> GUA using SLAAC, but does not have a link-local address on the link.
> [5.4.5 still bans assigning any address failing DAD AFAICS, even
> though IPv6 operation is permitted on the interface]

A few comments here:

1) Windows doesn't implement the traditional "embed the MAC address in
the IID" scheme -- so Windows nodes are not affected.

2) This "risk" is the price of one additional bit of entropy (another
approach would have been to clear the U/L bit).

3) Since there's quite a bit of MAC address reuse out there, nodes
should probably have to gracefully handle DAD failures anyway.



> If the SLAAC node arrives on link first, 
> draft-ietf-6man-stable-privacy-addresses will back off, increment
> (and presumably remember) the DAD counter and everything will work
> nominally.
> 
> To be clear, I think this is probably more of an issue with 
> draft-ietf-6man-ug-00 than
> draft-ietf-6man-stable-privacy-addresses-07.

At ome IETF meeting I argued that deprecating the u/g bit is fine, but
one should have a scheme to deal with DAD failures.


> This is already hinted at
> indraft-ietf-6man-stable-privacy-addresses-07, Quote:  "Real world
> data indicates that MAC address reuse is far more common than assumed
> [HDMoore].  This means that even IPv6 addresses that employ
> (allegedly) unique identifiers (such as IEEE identifiers) might 
> result in DAD failures, and hence implementations should be prepared
> to gracefully handle such occurrences." Which I agree with.
> 
> So in summary, I'd be happy if this was put on a "to consider" list
> for draft-ietf-6man-ug-0

Any changes required on draft-ietf-6man-stable-privacy-addresses?


> Some minor nits s/shouldproduce/should produce/

Done! -- THanks! (for some reason, I obtained a zero-length output when
trying to sue the spell-checker at tools.ietf.org)



> s/The prefix to be used for SLAAC, as learned from an ICMPv6/ Router 
> Advertisement message./The prefix to be used for SLAAC, as learned
> from an ICMPv6 Router Advertisement message, or the Link-Local IPv6
> Unicast prefix./

Fixed. Thanks!



> s/or when network interface happen/or when network interfaces
> happen/

Fixed.


> /Privacy issues still present when temporary addresses are employed/ 
> /employed/ is not bold after the new line (XML source or rendering 
> artefact?) 

Yep -- the txt should be fine.


> B1.3 has the same /server-like functions/ with /functions/
> not in bold, so it looks like the rendering.

Yep.

> s#It is not unusual for people to assume or expect that all the 
> security/privacy implications of traditional SLAAC addresses to me 
> mitigated when "temporary addresses"#It is not unusual for people to 
> assume or expect that all security/privacy implications of
> traditional SLAAC addresses are mitigated when "temporary
> addresses"#

"be" rather than "are", actually?

Thanks!

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





From fgont@si6networks.com  Sun May 19 13:16:50 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7AF21F8EAE for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rm85CZyPWoSY for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:16:49 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 140A921F8EB2 for <6man@ietf.org>; Sun, 19 May 2013 13:16:45 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeA1y-0003Ka-RZ; Sun, 19 May 2013 22:16:35 +0200
Message-ID: <5199331B.7060000@si6networks.com>
Date: Sun, 19 May 2013 17:16:27 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com>
In-Reply-To: <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 20:16:50 -0000

On 05/19/2013 04:31 PM, james woodyatt wrote:
> I have a problem with the following set of requirements:
> 
> The Net_Iface is a value that identifies the network interface for 
> which an IPv6 address is being generated.  The following properties 
> are desirable for the Net_Iface:
> 
> o  it MUST be constant across system bootstrap sequences and other 
> network events (e.g., bringing another interface up or down)
> 
> o  it MUST be different for each network interface
> 
> Some hosts have dynamic logical network interfaces (distinguishable
> from physical interface), which are created every time the host joins
> a network, and destroyed when the host separates from a previously
> joined network.  Examples are typically interfaces that involve
> signaling systems, point-to-point connection semantics for the link
> layer, e.g. virtual private networks, automatic tunnels, et cetera.
> 
> According to these requirements, such hosts MUST NOT reuse previously
> generated stable privacy addresses when joining the same network with
> a new logical interface.  That seems counter to the goal of this
> standard.

I'm not sure I follow... The requirement is that you address changes
when you move from one network to another. The only requirement for
"Net_Iface" must be different for different network interface is that
DAD failures are avoided (i.e., you don't have any two interfaces
deterministically getting the same address).



> I think hosts need some latitude in these requirements to allow for
> temporally different network interfaces associated with the same
> network service from the host's view to have the same identity for
> the purpose of generating stable privacy addresses.

If you use the interface index for Net_Iface, you'd probably get exactly
this. Same thing if you use the interface name (these virtual interfaces
are likely to get the same names when they are re-created?).

Thanks!

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





From brian.e.carpenter@gmail.com  Sun May 19 13:23:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8892621F8EB2 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.854
X-Spam-Level: 
X-Spam-Status: No, score=-102.854 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QXGsrR50rd9 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 13:23:16 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1807921F8E87 for <6man@ietf.org>; Sun, 19 May 2013 13:23:16 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id rp8so3424061pbb.8 for <6man@ietf.org>; Sun, 19 May 2013 13:23:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=g1v//c29A+HImBDm+wr6b6SIKtP8B93lBq/6zUzG8sk=; b=PiVutWbRPKK2Zely6NpMglUe8bVqiArfbFy56nwJDZZB8jK4WqtwrZLllNFP3YhpFO 9NBr7biauBHwrPGxECEXAmeB53AygxgNRiQl5AfURpDNVnOk8bde1qcTJGt1xDW5Bgkf HYZpEs8t24uMRlI91esB5kIAOYSxd5m8jNNl5gasAdeD6Tl+mJnYTGG2Tl2nNr2V3ORz 6AKyiYkZHySSdl68BfmMhQ/n1/dYqA019Eet5ig/BITMr9VB1sVB8UTn6oVns/7zb7RV hhOyAR+5FMK22LQ+vU7NhEHj9uFVZWhWnERe3bNER/JROwwr2PoSn+evrMrB5pWppipr 7Hhg==
X-Received: by 10.66.150.168 with SMTP id uj8mr57035353pab.34.1368994995824; Sun, 19 May 2013 13:23:15 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id ya4sm20846062pbb.24.2013.05.19.13.23.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 May 2013 13:23:14 -0700 (PDT)
Message-ID: <519934A7.7060606@gmail.com>
Date: Mon, 20 May 2013 08:23:03 +1200
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 <fgont@si6networks.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <51991EC0.9030600@globis.net> <51993123.3020100@si6networks.com>
In-Reply-To: <51993123.3020100@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Jouni Korhonen <jouni.korhonen@nsn.com>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 20:23:16 -0000

On 20/05/2013 08:08, Fernando Gont wrote:
...
>> If the SLAAC node arrives on link first, 
>> draft-ietf-6man-stable-privacy-addresses will back off, increment
>> (and presumably remember) the DAD counter and everything will work
>> nominally.
>>
>> To be clear, I think this is probably more of an issue with 
>> draft-ietf-6man-ug-00 than
>> draft-ietf-6man-stable-privacy-addresses-07.
> 
> At ome IETF meeting I argued that deprecating the u/g bit is fine, but
> one should have a scheme to deal with DAD failures.
> 
> 
>> This is already hinted at
>> indraft-ietf-6man-stable-privacy-addresses-07, Quote:  "Real world
>> data indicates that MAC address reuse is far more common than assumed
>> [HDMoore].  This means that even IPv6 addresses that employ
>> (allegedly) unique identifiers (such as IEEE identifiers) might 
>> result in DAD failures, and hence implementations should be prepared
>> to gracefully handle such occurrences." Which I agree with.
>>
>> So in summary, I'd be happy if this was put on a "to consider" list
>> for draft-ietf-6man-ug-0

If you want to specify what to do after a DAD failure, I think that
is a separate issue. All we can reasonably do in draft-ietf-6man-ug is
mention the risk of IID collisions, I think.

    Brian

From v6ops@globis.net  Sun May 19 14:20:08 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAE721F8CE9 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RqinjptBhCI8 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:20:07 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id BC18021F896D for <6man@ietf.org>; Sun, 19 May 2013 14:20:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id DDE718700D5; Sun, 19 May 2013 23:19:50 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShUeIReH+CHS; Sun, 19 May 2013 23:19:50 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id A58E5870002; Sun, 19 May 2013 23:19:50 +0200 (CEST)
Message-ID: <519941F0.6070803@globis.net>
Date: Sun, 19 May 2013 23:19:44 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <51991EC0.9030600@globis.net> <51993123.3020100@si6networks.com>
In-Reply-To: <51993123.3020100@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, "6man@ietf.org" <6man@ietf.org>, Jouni Korhonen <jouni.korhonen@nsn.com>, Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 21:20:08 -0000

> Fernando Gont <mailto:fgont@si6networks.com>
> 19 May 2013 22:08
> Hi, Ray,
>
> Thanks so much for your feedback! -- Please find my comments in-line....
>
> On 05/19/2013 03:49 PM, Ray Hunter wrote:
>> I think the draft is looking very good and is "ready to go." I
>> support it.
>
> Thanks!
>
>
>
>> I'm not 100.00000% convinced by one sentence, but I can live with
>> it.
>>
>> Quote: "We note that this method is incrementally deployable, since
>> it does not pose any interoperability implications when deployed on 
>> networks where other nodes do not implement or employ it."
>>
>> AFAICS there's a very very unlikely race condition scenario where a
>> node implementing draft-ietf-6man-stable-privacy-addresses could
>> cause a collision of a link local address with a node implementing
>> existing SLAAC, because the node running
>> draft-ietf-6man-stable-privacy-addresses arrived on link first and
>> completes DAD before the SLAAC node connects to the link.
>>
>> If the SLAAC node continues to deploy 4862 literally as defined in 
>> Section5.4.5, it will completely shut down IPv6 on the affected 
>> interface, unless it implements the MAY clause in 5.4.5 and
>> continues IPv6 operation, in which case there will be a possibility
>> of a node that runs IPv6 on an interface and which configures IPv6
>> GUA using SLAAC, but does not have a link-local address on the link.
>> [5.4.5 still bans assigning any address failing DAD AFAICS, even
>> though IPv6 operation is permitted on the interface]
>
> A few comments here:
>
> 1) Windows doesn't implement the traditional "embed the MAC address in
> the IID" scheme -- so Windows nodes are not affected.

Do you happen to know how Windows behaves in this case?

Are we already effectively running with this (tiny) risk in production
but (I) just didn't know it?
> 2) This "risk" is the price of one additional bit of entropy (another
> approach would have been to clear the U/L bit).
Agreed.
> 3) Since there's quite a bit of MAC address reuse out there, nodes
> should probably have to gracefully handle DAD failures anyway.
Agreed.
>
>
>> If the SLAAC node arrives on link first, 
>> draft-ietf-6man-stable-privacy-addresses will back off, increment
>> (and presumably remember) the DAD counter and everything will work
>> nominally.
>>
>> To be clear, I think this is probably more of an issue with 
>> draft-ietf-6man-ug-00 than
>> draft-ietf-6man-stable-privacy-addresses-07.
>
> At ome IETF meeting I argued that deprecating the u/g bit is fine, but
> one should have a scheme to deal with DAD failures.

It's not clear to me what exactly that scheme would do. But the current
text in 4862 isn't that helpful either.

I'd personally expect draft-ietf-6man-ug-00 to mention the issue, but
not necessarily to "solve" it. A full solution might require updating or
expanding 4862, and perhaps other standards, and I don't think it would
be desirable to deprecate the majority of existing running code just for
this issue.


Rather than forcibly clearing the U/L bit in the standard, another way
out without changing any standards text might be for implementers of
draft-ietf-6man-stable-privacy-addresses to be reasonably smart when
they read the text "The resulting Interface Identifier should be
compared against the Subnet-Router Anycast [RFC4291] and the Reserved
Subnet Anycast Addresses [RFC2526], and against those Interface
Identifiers already employed in an address of the same network interface
and the same network prefix."

So they'd basically loop whilst incrementing the DAD counter for any
Random Interface Identifier generated with u=1 if there's reason to
suspect that there were any nodes running existing SLAAC code on the
link, because the IID may well be in use, even though this particular
address hasn't explicitly failed DAD, nor has the developer been told
that generating an IID with u=1 is invalid.
>
>> This is already hinted at
>> indraft-ietf-6man-stable-privacy-addresses-07, Quote:  "Real world
>> data indicates that MAC address reuse is far more common than assumed
>> [HDMoore].  This means that even IPv6 addresses that employ
>> (allegedly) unique identifiers (such as IEEE identifiers) might 
>> result in DAD failures, and hence implementations should be prepared
>> to gracefully handle such occurrences." Which I agree with.
>>
>> So in summary, I'd be happy if this was put on a "to consider" list
>> for draft-ietf-6man-ug-0
>
> Any changes required on draft-ietf-6man-stable-privacy-addresses?
No. Not from my part.
>
>> Some minor nits s/shouldproduce/should produce/
>
> Done! -- THanks! (for some reason, I obtained a zero-length output when
> trying to sue the spell-checker at tools.ietf.org)
>
>
>
>> s/The prefix to be used for SLAAC, as learned from an ICMPv6/ Router 
>> Advertisement message./The prefix to be used for SLAAC, as learned
>> from an ICMPv6 Router Advertisement message, or the Link-Local IPv6
>> Unicast prefix./
>
> Fixed. Thanks!
>
>
>
>> s/or when network interface happen/or when network interfaces
>> happen/
>
> Fixed.
>
>
>> /Privacy issues still present when temporary addresses are employed/ 
>> /employed/ is not bold after the new line (XML source or rendering 
>> artefact?) 
>
> Yep -- the txt should be fine.
>
>
>> B1.3 has the same /server-like functions/ with /functions/
>> not in bold, so it looks like the rendering.
>
> Yep.
>
>> s#It is not unusual for people to assume or expect that all the 
>> security/privacy implications of traditional SLAAC addresses to me 
>> mitigated when "temporary addresses"#It is not unusual for people to 
>> assume or expect that all security/privacy implications of
>> traditional SLAAC addresses are mitigated when "temporary
>> addresses"#
>
> "be" rather than "are", actually?
"be" sounds either imperative (e.g. "be gone!") or old style English to me.

present tense of to be + past participle = "passive voice"

You could also consider:

#It is not unusual for people to assume, or expect, that enabling
"temporary addresses" [RFC4941] would mitigate all of the
   security/privacy implications of traditional SLAAC addresses.#

> Thanks!
>
> Best regards,
> Ray Hunter <mailto:v6ops@globis.net>
> 19 May 2013 20:49
> I think the draft is looking very good and is "ready to go." I support it.
>
>
> I'm not 100.00000% convinced by one sentence, but I can live with it.
>
> Quote: "We note that this method is incrementally deployable, since it
> does not pose any interoperability implications when deployed on
> networks where other nodes do not implement or employ it."
>
> AFAICS there's a very very unlikely race condition scenario where a node
> implementing draft-ietf-6man-stable-privacy-addresses could cause a
> collision of a link local address with a node implementing existing
> SLAAC, because the node running draft-ietf-6man-stable-privacy-addresses
> arrived on link first and completes DAD before the SLAAC node connects
> to the link.
>
> If the SLAAC node continues to deploy 4862 literally as defined in
> Section5.4.5, it will completely shut down IPv6 on the affected
> interface, unless it implements the MAY clause in 5.4.5 and continues
> IPv6 operation, in which case there will be a possibility of a node that
> runs IPv6 on an interface and which configures IPv6 GUA using SLAAC, but
> does not have a link-local address on the link. [5.4.5 still bans
> assigning any address failing DAD AFAICS, even though IPv6 operation is
> permitted on the interface]
>
> If the SLAAC node arrives on link first,
> draft-ietf-6man-stable-privacy-addresses will back off, increment (and
> presumably remember) the DAD counter and everything will work nominally.
>
> To be clear, I think this is probably more of an issue with
> draft-ietf-6man-ug-00 than draft-ietf-6man-stable-privacy-addresses-07.
>
> It does beg the question which node should back off in this case (if
> any). Probably the best course of action would be for the SLAAC node to
> choose a different link local address. Although this could have
> consequences, as e.g. static routes may point to the link local address.
>
> This is already hinted at indraft-ietf-6man-stable-privacy-addresses-07,
> Quote: "Real world data indicates that MAC address reuse is far more
> common than assumed [HDMoore]. This means that even IPv6 addresses that
> employ (allegedly) unique identifiers (such as IEEE identifiers) might
> result in DAD failures, and hence implementations should be prepared to
> gracefully handle such occurrences." Which I agree with.
>
> So in summary, I'd be happy if this was put on a "to consider" list for
> draft-ietf-6man-ug-0
>
>
> Some minor nits
> s/shouldproduce/should produce/
>
> s/The prefix to be used for SLAAC, as learned from an ICMPv6/ Router
> Advertisement message./The prefix to be used for SLAAC, as learned from
> an ICMPv6 Router Advertisement message, or the Link-Local IPv6 Unicast
> prefix./
>
> s/or when network interface happen/or when network interfaces happen/
>
>
> /Privacy issues still present when temporary addresses are employed/
> /employed/ is not bold after the new line (XML source or rendering
> artefact?)
> B1.3 has the same /server-like functions/ with /functions/ not in bold,
> so it looks like the rendering.
>
>
> s#It is not unusual for people to assume or expect that all the
> security/privacy implications of traditional SLAAC addresses to me
> mitigated when "temporary addresses"#It is not unusual for people to
> assume or expect that all security/privacy implications of traditional
> SLAAC addresses are mitigated when "temporary addresses"#
>
> Thanks.
>
> regards,
> RayH
> Fernando Gont <mailto:fgont@si6networks.com>
> 19 May 2013 19:33
> Folks,
>
> I've posted a rev of the aforementioned document, meant to address the
> comments received during IETF LC.
>
> This rev is the result of the IETF LC discussions we had on the 6man wg
> list and on the general IETF list, and of off-list discussions with a
> number of folks who generously provided input, reviewed proposed
> changes, etc.
>
> I'd expect this rev to be "ready to ship" or very close to that. But
> please provide your input confirming whether you think that's the case,
> or whether there are any remaining issues to be solved.
>
> The rev is available at:
> <http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.
>
> A diff from the previous version of the I-D is available at:
> <tools.ietf.org//rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-06.txt&url2=http://tools.ietf.org/id/draft-ietf-6man-stable-privacy-addresses-07.txt>.
>
> Thanks so much!
>
> Best regards,
> ------------------------------------------------------------------------


From jhw@apple.com  Sun May 19 14:28:03 2013
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5544D21F8EAF for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTYYoQZM96Fi for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:27:57 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2101121F8E9A for <6man@ietf.org>; Sun, 19 May 2013 14:27:57 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN2002XHE9X07C0@mail-out.apple.com> for 6man@ietf.org; Sun, 19 May 2013 14:27:56 -0700 (PDT)
X-AuditID: 11807166-b7faa6d000003acb-16-519943dbfcf1
Received: from [17.113.34.48] (Unknown_Domain [17.113.34.48]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id 24.30.15051.CD349915; Sun, 19 May 2013 14:27:56 -0700 (PDT)
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: james woodyatt <jhw@apple.com>
In-reply-to: <5199331B.7060000@si6networks.com>
Date: Sun, 19 May 2013 14:27:55 -0700
Message-id: <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com>
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMLMWRmVeSWpSXmKPExsUiWKhkoHvHeWagwZQf2hYrV9xlsniy6g2b A5PHkiU/mTw+HOphD2CK4rJJSc3JLEst0rdL4MrYNvMMY8EGsYpDl/YwNzDOEOpi5OSQEDCR WLHpOQuELSZx4d56ti5GLg4hgW4miauf+5lAEswCOhI7t95hA7F5BfQkrn37yg5iCws4Shx9 uJERxGYTUJH4dvkuWD2ngL7E/DV7wYayCKhK7L/xnx1ijrLEnS1trBC2tsSyha+Zuxg5gGba SCxaWgKxt4lR4s3ZL2D1IgKaEnOfH2GCOE5W4vXzNywTGPlnITlpFpKTZiEZu4CReRWjQFFq TmKlhV5iQUFOql5yfu4mRlDQNRSm7WBsWm51iFGAg1GJh7fhw/RAIdbEsuLK3EOMEhzMSiK8 dtYzA4V4UxIrq1KL8uOLSnNSiw8xSnOwKInzTj4/LVBIID2xJDU7NbUgtQgmy8TBKdXAGPOx fv6Mp25vGtZeUnSz+VdosHO7fUkEy8vINUY37r37c5h7r9zB8wX/jdo4RThe3k8MuyS96SAz 85KW36WbTn+cn35dJ3r5lVVxggrPNA+8WvtFT3H39qj7TT6RMTYJnSevJ2dqHk8Xy9h86olc xdYLzZLTF7z8OfuCj+CONbf63NWOf12WHKPEUpyRaKjFXFScCABO2Iw5NgIAAA==
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 21:28:03 -0000

On May 19, 2013, at 13:16 , Fernando Gont <fgont@si6networks.com> wrote:
> On 05/19/2013 04:31 PM, james woodyatt wrote:
>> I have a problem with the following set of requirements:
>> 
>> The Net_Iface is a value that identifies the network interface for 
>> which an IPv6 address is being generated.  The following properties 
>> are desirable for the Net_Iface:
>> 
>> o  it MUST be constant across system bootstrap sequences and other 
>> network events (e.g., bringing another interface up or down)
>> 
>> o  it MUST be different for each network interface
>> 
>> Some hosts have dynamic logical network interfaces (distinguishable
>> from physical interface), which are created every time the host joins
>> a network, and destroyed when the host separates from a previously
>> joined network.  Examples are typically interfaces that involve
>> signaling systems, point-to-point connection semantics for the link
>> layer, e.g. virtual private networks, automatic tunnels, et cetera.
>> 
>> According to these requirements, such hosts MUST NOT reuse previously
>> generated stable privacy addresses when joining the same network with
>> a new logical interface.  That seems counter to the goal of this
>> standard.
> 
> I'm not sure I follow... The requirement is that you address changes
> when you move from one network to another. The only requirement for
> "Net_Iface" must be different for different network interface is that
> DAD failures are avoided (i.e., you don't have any two interfaces
> deterministically getting the same address).

If avoiding DAD failure is the goal, then the second clause is overly restrictive. It should suffice that the value of Net_Iface is different for each network interface in *simultaneous* use.

>> I think hosts need some latitude in these requirements to allow for
>> temporally different network interfaces associated with the same
>> network service from the host's view to have the same identity for
>> the purpose of generating stable privacy addresses.
> 
> If you use the interface index for Net_Iface, you'd probably get exactly
> this. Same thing if you use the interface name (these virtual interfaces
> are likely to get the same names when they are re-created?).

That's not the sort of assumption I want to see go unstated in a Standards Track RFC. Better would be to avoid the ambiguity altogether.  For example, OS X does not have a requirement that network interfaces have unique names.  There is a UUID that identifies network services, which are related to the network interfaces the system configuration service manages, but network *services* on OS X are not the same as network *interfaces*, and they are not mapped 1:1 to one another.


--
james woodyatt <jhw@apple.com>
core os networking


From fgont@si6networks.com  Sun May 19 14:43:07 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69A021F8F07 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06tziCzbIJyI for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:43:07 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id C8D3721F8EFE for <6man@ietf.org>; Sun, 19 May 2013 14:43:06 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeBNV-0005J3-QQ; Sun, 19 May 2013 23:42:54 +0200
Message-ID: <51994754.2070908@si6networks.com>
Date: Sun, 19 May 2013 18:42:44 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <51991EC0.9030600@globis.net> <51993123.3020100@si6networks.com> <519941F0.6070803@globis.net>
In-Reply-To: <519941F0.6070803@globis.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Ben Campbell <ben@nostrum.com>, "6man@ietf.org" <6man@ietf.org>, Jouni Korhonen <jouni.korhonen@nsn.com>, Brian Haberman <brian@innovationslab.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 21:43:07 -0000

On 05/19/2013 06:19 PM, Ray Hunter wrote:
>>
>> A few comments here:
>>
>> 1) Windows doesn't implement the traditional "embed the MAC address in
>> the IID" scheme -- so Windows nodes are not affected.
> 
> Do you happen to know how Windows behaves in this case?

No idea. -- Although it shouldn't be hard to find out with the ra6 tool
at <http://www.si6networks.com/tools/ipv6toolkit>



> Are we already effectively running with this (tiny) risk in production
> but (I) just didn't know it?

Well, Windows node essentially select their stable addresses as a random
number, so... unless I'm missing something, we are.



>>> If the SLAAC node arrives on link first, 
>>> draft-ietf-6man-stable-privacy-addresses will back off, increment
>>> (and presumably remember) the DAD counter and everything will work
>>> nominally.
>>>
>>> To be clear, I think this is probably more of an issue with 
>>> draft-ietf-6man-ug-00 than
>>> draft-ietf-6man-stable-privacy-addresses-07.
>>
>> At ome IETF meeting I argued that deprecating the u/g bit is fine, but
>> one should have a scheme to deal with DAD failures.
> 
> It's not clear to me what exactly that scheme would do. But the current
> text in 4862 isn't that helpful either.

We'll it's left unspecified -- my take is that there's a gap in this area.



> I'd personally expect draft-ietf-6man-ug-00 to mention the issue, but
> not necessarily to "solve" it. 

+1


> A full solution might require updating or
> expanding 4862, and perhaps other standards, and I don't think it would
> be desirable to deprecate the majority of existing running code just for
> this issue.

Well, it wouldn't be "deprecate existing running code" (i.e., we're not
really against existing behaviour, but rather arguing about augmenting
it with graceful handling of DAD collisions).



> Rather than forcibly clearing the U/L bit in the standard, another way
> out without changing any standards text might be for implementers of
> draft-ietf-6man-stable-privacy-addresses to be reasonably smart when
> they read the text "The resulting Interface Identifier should be
> compared against the Subnet-Router Anycast [RFC4291] and the Reserved
> Subnet Anycast Addresses [RFC2526], and against those Interface
> Identifiers already employed in an address of the same network interface
> and the same network prefix."
> 
> So they'd basically loop whilst incrementing the DAD counter for any
> Random Interface Identifier generated with u=1 if there's reason to
> suspect that there were any nodes running existing SLAAC code on the
> link, because the IID may well be in use, even though this particular
> address hasn't explicitly failed DAD, nor has the developer been told
> that generating an IID with u=1 is invalid.

Could that really be reliably determined?



>>> s#It is not unusual for people to assume or expect that all the 
>>> security/privacy implications of traditional SLAAC addresses to me 
>>> mitigated when "temporary addresses"#It is not unusual for people to 
>>> assume or expect that all security/privacy implications of
>>> traditional SLAAC addresses are mitigated when "temporary
>>> addresses"#
>>
>> "be" rather than "are", actually?
> "be" sounds either imperative (e.g. "be gone!") or old style English to me.
> 
> present tense of to be + past participle = "passive voice"

OK. Applied your original suggestion. :-)

Thanks so much!

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





From fgont@si6networks.com  Sun May 19 14:53:05 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A901821F8EAF for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+GGO+SFDRPO for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 14:53:05 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0001B21F8E93 for <6man@ietf.org>; Sun, 19 May 2013 14:53:04 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeBXG-0005XR-6l; Sun, 19 May 2013 23:52:58 +0200
Message-ID: <519949B2.8000409@si6networks.com>
Date: Sun, 19 May 2013 18:52:50 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com>
In-Reply-To: <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 21:53:05 -0000

On 05/19/2013 06:27 PM, james woodyatt wrote:
>>> The Net_Iface is a value that identifies the network interface
>>> for which an IPv6 address is being generated.  The following
>>> properties are desirable for the Net_Iface:
>>> 
>>> o  it MUST be constant across system bootstrap sequences and
>>> other network events (e.g., bringing another interface up or
>>> down)
>>> 
>>> o  it MUST be different for each network interface
>>> 
>>> Some hosts have dynamic logical network interfaces
>>> (distinguishable from physical interface), which are created
>>> every time the host joins a network, and destroyed when the host
>>> separates from a previously joined network.  Examples are
>>> typically interfaces that involve signaling systems,
>>> point-to-point connection semantics for the link layer, e.g.
>>> virtual private networks, automatic tunnels, et cetera.
>>> 
>>> According to these requirements, such hosts MUST NOT reuse
>>> previously generated stable privacy addresses when joining the
>>> same network with a new logical interface.  That seems counter to
>>> the goal of this standard.
>> 
>> I'm not sure I follow... The requirement is that you address
>> changes when you move from one network to another. The only
>> requirement for "Net_Iface" must be different for different network
>> interface is that DAD failures are avoided (i.e., you don't have
>> any two interfaces deterministically getting the same address).
> 
> If avoiding DAD failure is the goal, 

Yes.


> then the second clause is overly
> restrictive. It should suffice that the value of Net_Iface is
> different for each network interface in *simultaneous* use.

mm... how would you define simultaneous use?

Is an interface that is down considered "in use"? If not, is the
"Net_face" for that interface expeted to change (to comply with req #2)
when the interface is brought up?




>>> I think hosts need some latitude in these requirements to allow
>>> for temporally different network interfaces associated with the
>>> same network service from the host's view to have the same
>>> identity for the purpose of generating stable privacy addresses.
>> 
>> If you use the interface index for Net_Iface, you'd probably get
>> exactly this. Same thing if you use the interface name (these
>> virtual interfaces are likely to get the same names when they are
>> re-created?).
> 
> That's not the sort of assumption I want to see go unstated in a
> Standards Track RFC. Better would be to avoid the ambiguity
> altogether.  For example, OS X does not have a requirement that
> network interfaces have unique names.

How do you ifconfig(8) them if the name is not unique?


> There is a UUID that
> identifies network services, which are related to the network
> interfaces the system configuration service manages, but network
> *services* on OS X are not the same as network *interfaces*, and they
> are not mapped 1:1 to one another.

I'm kind of lost here, sine I don't know the details behind OS X.

Are you arguing tha the discussion of interfae names (or something else)
is incorrect? Are you arguing that there's something that should be
clarified? (if so, what, and how?)

ANy help in this respect will be really welcome.

Thanks!

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





From kauer@biplane.com.au  Sun May 19 15:03:16 2013
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71BFA21F8F41 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zrnyYPdNlZt for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:03:15 -0700 (PDT)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5E721F8F3E for <ipv6@ietf.org>; Sun, 19 May 2013 15:03:13 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMBAD5LmVGWZX+7/2dsb2JhbAANTYM4Q4ETv2WBFIMTAQEBBIEJCxguVxmIFKlKkViPKBaDPgOIZ496ineIQQ
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.202]) ([150.101.127.187]) by ipmail05.adl6.internode.on.net with ESMTP; 20 May 2013 07:33:11 +0930
Message-ID: <1369000989.3192.53.camel@karl>
Subject: Re: [6man] #1: Proper source for an "Interface Identifier"
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
Date: Mon, 20 May 2013 08:03:09 +1000
In-Reply-To: <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org>
References: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org> <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 22:03:16 -0000

On Sun, 2013-05-19 at 16:55 +0000, 6man issue tracker wrote:
> The following properties are desirable for the Net_Iface:
>     o  it MUST be constant across system bootstrap sequences and other
>        network events (e.g., bringing another interface up or down)
>     o  it MUST be different for each network interface

This is confusing. You say the properties are desirable, then you
describe them with MUST. So - are they desirable, or are they mandatory?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A
Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017


From fgont@si6networks.com  Sun May 19 15:07:10 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E870321F8F62 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3pbddsYlI7U for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:07:10 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5D121F8F4D for <ipv6@ietf.org>; Sun, 19 May 2013 15:07:10 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeBkt-0005tZ-CQ; Mon, 20 May 2013 00:07:03 +0200
Message-ID: <51994D02.1070603@si6networks.com>
Date: Sun, 19 May 2013 19:06:58 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: [6man] #1: Proper source for an "Interface Identifier"
References: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org> <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org> <1369000989.3192.53.camel@karl>
In-Reply-To: <1369000989.3192.53.camel@karl>
X-Enigmail-Version: 1.4.6
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 22:07:11 -0000

On 05/19/2013 07:03 PM, Karl Auer wrote:
> On Sun, 2013-05-19 at 16:55 +0000, 6man issue tracker wrote:
>> The following properties are desirable for the Net_Iface:
>>     o  it MUST be constant across system bootstrap sequences and other
>>        network events (e.g., bringing another interface up or down)
>>     o  it MUST be different for each network interface
> 
> This is confusing. You say the properties are desirable, then you
> describe them with MUST. So - are they desirable, or are they mandatory?

You're right. s/desirable/required/?

(I don't think "REQUIRED" (caps) would be needed, since the bullests
contain RFC2119-anguage, already).

Thoughts?

Thanks!

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





From jhw@apple.com  Sun May 19 15:19:34 2013
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 596F421F8F0C for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:19:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iS1P+8i7gcP4 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:19:27 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id DCC2021F8F24 for <6man@ietf.org>; Sun, 19 May 2013 15:19:27 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay3.apple.com ([17.128.113.83]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN20086ZGOCKTJ0@mail-out.apple.com> for 6man@ietf.org; Sun, 19 May 2013 15:19:27 -0700 (PDT)
X-AuditID: 11807153-b7f3c6d000007b32-9b-51994fefce89
Received: from [17.113.34.48] (Unknown_Domain [17.113.34.48]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay3.apple.com (Apple SCV relay) with SMTP id D6.11.31538.FEF49915; Sun, 19 May 2013 15:19:27 -0700 (PDT)
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: james woodyatt <jhw@apple.com>
In-reply-to: <519949B2.8000409@si6networks.com>
Date: Sun, 19 May 2013 15:19:26 -0700
Message-id: <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com>
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUiWKhkoPvef2agwaxVuhYrV9xlsniy6g2b A5PHkiU/mTw+HOphD2CK4rJJSc3JLEst0rdL4Mp49mIDU8Ev0Yppk1azNjBuE+xi5OSQEDCR eHn4MjOELSZx4d56ti5GLg4hgW4micbOnWAJZgEdiZ1b77CB2LwCehLXvn1lB7GFBRwljj7c yAhiswmoSHy7fJcJxOYU0Je4OvMlWC+LgKrEpHnHWSHmKEvc2dIGZWtLLFv4mhlipo3EvWNH oRZfY5TYsGAPWJGIgKbE3OdHmCCuk5V4/fwNywRG/llIbpqF5KZZSOYuYGRexShQlJqTWGms l1hQkJOql5yfu4kRFHYNhcE7GP8sszrEKMDBqMTDq/FueqAQa2JZcWXuIUYJDmYlEV4765mB QrwpiZVVqUX58UWlOanFhxilOViUxHknnp8WKCSQnliSmp2aWpBaBJNl4uCUamAsNTnCv8NF ijlYX6XklZTpOcnXqsJ2vmEaLkKnbKpfRMXKfzz4XkY3smd55spPDsLPHt/3zNuqPP1l7/r/ yb2PbGojmLdf3vpaw3eH2Z9pSSKGxzaFOKXwOe0uN9sbsPT4ox+7t9tsuT0zd/nE9Zd3peyZ GSshs3z2J5PMVsaEyJ3yHDNrnzorsRRnJBpqMRcVJwIAEg+xiDcCAAA=
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 22:19:34 -0000

On May 19, 2013, at 14:52 , Fernando Gont <fgont@si6networks.com> wrote:
> On 05/19/2013 06:27 PM, james woodyatt wrote:
>> 
>> That's not the sort of assumption I want to see go unstated in a
>> Standards Track RFC. Better would be to avoid the ambiguity
>> altogether.  For example, OS X does not have a requirement that
>> network interfaces have unique names.
> 
> How do you ifconfig(8) them if the name is not unique?

The names used by ifconfig(8) are temporally unique, but not universally unique, i.e. it is not the case that 'net0' at time t=0.0 ns is the same as 'net0' at time t=0.1 ns.  When they are different, the UUID of the network service associated with the 'net0' interface is different.

>> There is a UUID that
>> identifies network services, which are related to the network
>> interfaces the system configuration service manages, but network
>> *services* on OS X are not the same as network *interfaces*, and they
>> are not mapped 1:1 to one another.
> 
> I'm kind of lost here, sine I don't know the details behind OS X.

That's why I'm trying to help.

> Are you arguing tha the discussion of interfae names (or something else)
> is incorrect? Are you arguing that there's something that should be
> clarified? (if so, what, and how?)
> 
> ANy help in this respect will be really welcome.

Yes, I'm saying that interface names don't map well to the concept you're expecting them to indicate.  You seem to think that a networking interface interface used with a particular network service will always have the same name every time it is put into service.

That's not the case with OS X, which makes no such guarantee.  Yes, many people labor under the misconception that 'en0' is always the Ethernet port, but we try to disabuse them of that idea every chance we get.  The same thing goes for the interface index.  The only thing that really identifies the interface uniquely is the UUID for the network service that you find in the System Configuration Dynamic Store, but even that may not be good choice for the Net_Iface value here, because services come and go as users make configuration changes and migrate their systems from one operating system release to the next.

Look, the more I think about this issue, the clearer it becomes to me that you just need to change...

>>> o  it MUST be different for each network interface

...to...

>>> o  it MUST be different for each network interface simultaneously in use.

That will leave the OS X system configuration service with sufficient latitude that it can choose a value for each network interface it configures to meet the goals of this specification.


--
james woodyatt <jhw@apple.com>
core os networking


From kauer@biplane.com.au  Sun May 19 15:55:35 2013
Return-Path: <kauer@biplane.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612B721F8EB2 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNU3AHKnq32z for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 15:55:34 -0700 (PDT)
Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5A221F8EA4 for <ipv6@ietf.org>; Sun, 19 May 2013 15:55:33 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMBACJXmVGWZX+7/2dsb2JhbAANTYM4Q4ETv2WBFYMTAQEBBIEJCxguVxmIFKlXkVaPKBaDPgOIZ496ineIQQ
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.202]) ([150.101.127.187]) by ipmail05.adl6.internode.on.net with ESMTP; 20 May 2013 08:25:32 +0930
Message-ID: <1369004131.3192.68.camel@karl>
Subject: Re: [6man] #1: Proper source for an "Interface Identifier"
From: Karl Auer <kauer@biplane.com.au>
To: ipv6@ietf.org
Date: Mon, 20 May 2013 08:55:31 +1000
In-Reply-To: <51994D02.1070603@si6networks.com>
References: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org> <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org> <1369000989.3192.53.camel@karl> <51994D02.1070603@si6networks.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 22:55:35 -0000

On Sun, 2013-05-19 at 19:06 -0300, Fernando Gont wrote:
> You're right. s/desirable/required/?
> 
> (I don't think "REQUIRED" (caps) would be needed, since the bullests
> contain RFC2119-anguage, already).

LC or UC "required" would be OK.

Regards,K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: B862 FB15 FE96 4961 BC62 1A40 6239 1208 9865 5F9A
Old fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017


From fgont@si6networks.com  Sun May 19 16:21:39 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B24021F8AD8 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 16:21:39 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBfjnkx6SZsf for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 16:21:38 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3B21521F8AA6 for <ipv6@ietf.org>; Sun, 19 May 2013 16:21:37 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeCuu-0000Ms-TU; Mon, 20 May 2013 01:21:29 +0200
Message-ID: <51995E71.7010205@si6networks.com>
Date: Sun, 19 May 2013 20:21:21 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Karl Auer <kauer@biplane.com.au>
Subject: Re: [6man] #1: Proper source for an "Interface Identifier"
References: <063.6c182637b59f010c5f4ade2dffb3120a@trac.tools.ietf.org> <078.e3e0a130b33d64cb804adbbd62be84a1@trac.tools.ietf.org> <1369000989.3192.53.camel@karl> <51994D02.1070603@si6networks.com> <1369004131.3192.68.camel@karl>
In-Reply-To: <1369004131.3192.68.camel@karl>
X-Enigmail-Version: 1.4.6
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 23:21:39 -0000

On 05/19/2013 07:55 PM, Karl Auer wrote:
> On Sun, 2013-05-19 at 19:06 -0300, Fernando Gont wrote:
>> You're right. s/desirable/required/?
>>
>> (I don't think "REQUIRED" (caps) would be needed, since the bullests
>> contain RFC2119-anguage, already).
> 
> LC or UC "required" would be OK.

Ok, done. Thanks!

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





From fgont@si6networks.com  Sun May 19 16:44:13 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F45821F8E4E for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 16:44:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ie64p5Oqr7p2 for <ipv6@ietfa.amsl.com>; Sun, 19 May 2013 16:44:12 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id A668421F8C23 for <6man@ietf.org>; Sun, 19 May 2013 16:44:12 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeDGn-0000qq-HD; Mon, 20 May 2013 01:44:05 +0200
Message-ID: <519963BF.9010700@si6networks.com>
Date: Sun, 19 May 2013 20:43:59 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com> <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com>
In-Reply-To: <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 19 May 2013 23:44:13 -0000

On 05/19/2013 07:19 PM, james woodyatt wrote:
>>> That's not the sort of assumption I want to see go unstated in a 
>>> Standards Track RFC. Better would be to avoid the ambiguity 
>>> altogether.  For example, OS X does not have a requirement that 
>>> network interfaces have unique names.
>> 
>> How do you ifconfig(8) them if the name is not unique?
> 
> The names used by ifconfig(8) are temporally unique, but not
> universally unique, i.e. it is not the case that 'net0' at time t=0.0
> ns is the same as 'net0' at time t=0.1 ns.  When they are different,
> the UUID of the network service associated with the 'net0' interface
> is different.

I think that's the case with most systems. e.g., you plug two USB based
wireless cards, A and B, and they become wlan0 an wlan1.You unplug them,
and plug them again but in different order, and A becomes wlan1 and B
becomes wlan0.



>> Are you arguing tha the discussion of interfae names (or something
>> else) is incorrect? Are you arguing that there's something that
>> should be clarified? (if so, what, and how?)
>> 
>> ANy help in this respect will be really welcome.
> 
> Yes, I'm saying that interface names don't map well to the concept
> you're expecting them to indicate.  

Other than the fix you suggested ("it MUST be different for each network
interface simultaneously in use."), is there anything to be fixe in,
say, Appendix A?


> You seem to think that a
> networking interface interface used with a particular network service
> will always have the same name every time it is put into service.

Nop. Please see the discussion of interface names in Appendix A. They
are deemed as rather more constant than interface indexes, but still
might change when interfaces are removed/added.



> That's not the case with OS X, which makes no such guarantee.  Yes,
> many people labor under the misconception that 'en0' is always the
> Ethernet port, but we try to disabuse them of that idea every chance
> we get.  

Just out of curiosity: Do they use a different identifier with ifconfig?
O actually use some other command altogether?


> The same thing goes for the interface index.  The only thing
> that really identifies the interface uniquely is the UUID for the
> network service that you find in the System Configuration Dynamic
> Store, but even that may not be good choice for the Net_Iface value
> here, because services come and go as users make configuration
> changes and migrate their systems from one operating system release
> to the next.

Just ouf of curiosity: are UUIDs attahed to the NIC itself (as e.g. the
MAC address)? Can they vary upon installation/removal of network interfaces?



> Look, the more I think about this issue, the clearer it becomes to me
> that you just need to change...
> 
>>>> o  it MUST be different for each network interface
> 
> ...to...
> 
>>>> o  it MUST be different for each network interface
>>>> simultaneously in use.
> 
> That will leave the OS X system configuration service with sufficient
> latitude that it can choose a value for each network interface it
> configures to meet the goals of this specification.

Done. (this change will appear in upcoming version -08 of this document).

Thanks!

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





From tjc@ecs.soton.ac.uk  Mon May 20 06:56:22 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5196A21F93F4 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 06:56:21 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmGRB-x-j++I for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 06:56:20 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id ABBDD21F933B for <ipv6@ietf.org>; Mon, 20 May 2013 06:56:13 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4KDu7kR015094 for <ipv6@ietf.org>; Mon, 20 May 2013 14:56:07 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4KDu7kR015094
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369058167; bh=5Sofu4/q4knDjQuXGzCCAk4fIiA=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=Wy2y/itg/qIbC5J29nyEDKKvr5pqZ4MJuQYCqCDo5ggqwYIPIIne+Dk8J4JelAob3 LpUeTqf0BnIBm7v7Zx67qmnNs8OtlYqDxxtGonn56fZWa1sNRn3lbewwLVzVGgZ6on 7nW9swl1zntmdeJ/MMx/lD7DEnbVMkp8vXOHKuxI=
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 (valid=N/A) id p4JEu70430628970vZ ret-id none; Mon, 20 May 2013 14:56:07 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4KDu5iq019242 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Mon, 20 May 2013 14:56:05 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: I-D Action: draft-imadali-its-vinipv6-viid-00.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <515EF3F2.7000608@gmail.com>
Date: Mon, 20 May 2013 14:56:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|b1e2c664daa3c970f0d7c78843e5d27cp4JEu703tjc|ecs.soton.ac.uk|A30B80F6-8344-49FF-82E5-2DD38D2C1468@ecs.soton.ac.uk>
References: <515733A5.8080509@gmail.com> <5157C8CF.1060503@si6networks.com> <515AFF7A.80102@gmail.com> <515BC0DA.6040203@si6networks.com> <515C2CFF.3060809@gmail.com> <021E64FECA7E5A4699562F4E6671648101E304@XCH-PHX-503.sw.nos.boeing.com> <515DBF5E.2050809@gmail.com> <021E64FECA7E5A4699562F4E6671648101E660@XCH-PHX-503.sw.nos.boeing.com> <515EF3F2.7000608@gmail.com> <A30B80F6-8344-49FF-82E5-2DD38D2C1468@ecs.soton.ac.uk>
To: 6man <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4JEu7043062897000; tid=p4JEu70430628970vZ; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4KDu7kR015094
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 May 2013 13:56:22 -0000

On 5 Apr 2013, at 16:55, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> I wonder whether homenet people consider that the prefix to be =
delivered
> to a homenet could be longer than /64 (i.e. /65 or /66).

That would be considered a failure mode.

See 3.4.1 of the current homenet arch text (a new version of which is =
about to be posted).

Tim=

From jhw@apple.com  Mon May 20 10:33:55 2013
Return-Path: <jhw@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1DF921F9688 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 10:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8VpWLxqjzK7 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 10:33:49 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id F090B21F9682 for <6man@ietf.org>; Mon, 20 May 2013 10:33:48 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN300CMNY40MIX0@mail-out.apple.com> for 6man@ietf.org; Mon, 20 May 2013 10:33:48 -0700 (PDT)
X-AuditID: 11807166-b7faa6d000003acb-26-519a5e7b2f13
Received: from ba0301b-dhcp196.apple.com (ba0301b-dhcp196.apple.com [17.193.15.196]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id 28.67.15051.B7E5A915; Mon, 20 May 2013 10:33:47 -0700 (PDT)
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: james woodyatt <jhw@apple.com>
In-reply-to: <519963BF.9010700@si6networks.com>
Date: Mon, 20 May 2013 10:33:46 -0700
Message-id: <65C2C74A-E0C4-4E1F-A72E-5DFBCA038309@apple.com>
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com> <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com> <519963BF.9010700@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUieJD/iG513KxAg4knbSxWrrjLZPFk1Rs2 ByaPJUt+Mnl8ONTDHsAUxWWTkpqTWZZapG+XwJWx+usKtoIG0Yq237NZGxhvCHQxcnJICJhI fPrayAJhi0lcuLeerYuRi0NIYBGTxIPPXewgCWYBHYmdW++wgdi8AnoS1759BYsLCzhKHH24 kRHEZhNQkfh2+S4TiM0poC/R/Ow8WA2LgKpE37obzBBztCWWLXzNDDHHRmLVm22MEMtWMUk8 2/sBbIGIgI/Ek2e9TBAXyUq8fv6GZQIj3ywkd8xCcscsJHMXMDKvYhQoSs1JrLTQSywoyEnV S87P3cQICq+GwrQdjE3LrQ4xCnAwKvHwGvrOChRiTSwrrsw9xCjBwawkwhv9e2agEG9KYmVV alF+fFFpTmrxIUZpDhYlcd7J56cFCgmkJ5akZqemFqQWwWSZODilGhhv7n+e/+LhPE+XW33H XEKFpiZeM7Z2k3xfo/TvvJT2XfOvqTK6bpV3r7QseM98K5brY+Ks0r11fS89f1Xk/nv/8Yfl /DqRyUpLD+u+nxzLlS/UPX3ugnPfp632ap52z/ssV9/a8zW10cvnTlC50JqzaXPIo8OtLxfv jovzvPPf4qz1U6VEdZkzSizFGYmGWsxFxYkAcOjf6SsCAAA=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 May 2013 17:33:55 -0000

On May 19, 2013, at 16:43 , Fernando Gont <fgont@si6networks.com> wrote:
> 
> Other than the fix you suggested ("it MUST be different for each network
> interface simultaneously in use."), is there anything to be fixe in,
> say, Appendix A?

I don't see why Appendix A needs to comprise an exhaustive list of all possibilities, but it might be improved by the addition of something like this:

  A.4. Logical Network Service Identity

  Host operating systems with a conception of logical network service identity,
  distinct from network interface identity or index, may keep a UUID or similar
  number with the stability properties appropriate for use as the Net_Iface
  parameter.

> [I wrote:]

>> 
>> That's not the case with OS X, which makes no such guarantee.  Yes,
>> many people labor under the misconception that 'en0' is always the
>> Ethernet port, but we try to disabuse them of that idea every chance
>> we get.  
> 
> Just out of curiosity: Do they use a different identifier with ifconfig?
> O actually use some other command altogether?

The names used by ifconfig(8) on OS X are provided for POSIX compatibility.  The authoritative identity of network services and the interfaces where they are configured is managed by the system configuration daemon (configd).  The schema for that data tends to use UUID for unique identifiers.

>> The same thing goes for the interface index.  The only thing
>> that really identifies the interface uniquely is the UUID for the
>> network service that you find in the System Configuration Dynamic
>> Store, but even that may not be good choice for the Net_Iface value
>> here, because services come and go as users make configuration
>> changes and migrate their systems from one operating system release
>> to the next.
> 
> Just ouf of curiosity: are UUIDs attahed to the NIC itself (as e.g. the
> MAC address)? Can they vary upon installation/removal of network interfaces?

The UUID in the SCDynamicStore are always chosen from a random number source.  They may change as a result of user configuration events.  They may change when network interfaces are installed or removed.  They can be used to identify nodes in the System Configuration dynamic and persistent stores, and the natural way to implement the specification in this draft on OS X and iOS would be keep the Net_Iface parameter in the Network Service structure in the SC persistent store.

> Done. (this change will appear in upcoming version -08 of this document).

Awesome.  Thank you.


--
james woodyatt <jhw@apple.com>
core os networking


From dthaler@microsoft.com  Mon May 20 12:59:02 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549FA21F96A1 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 12:59:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.8
X-Spam-Level: 
X-Spam-Status: No, score=-97.8 tagged_above=-999 required=5 tests=[AWL=-0.333,  BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5rkvgpTUUSJ for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 12:58:56 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 5C50321F96A2 for <6man@ietf.org>; Mon, 20 May 2013 12:58:56 -0700 (PDT)
Received: from BY2FFO11FD005.protection.gbl (10.1.15.201) by BY2FFO11HUB032.protection.gbl (10.1.14.177) with Microsoft SMTP Server (TLS) id 15.0.698.0; Mon, 20 May 2013 19:57:48 +0000
Received: from TK5EX14HUBC107.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD005.mail.protection.outlook.com (10.1.14.126) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Mon, 20 May 2013 19:57:48 +0000
Received: from CO9EHSOBE036.bigfish.com (157.54.51.114) by mail.microsoft.com (157.54.80.67) with Microsoft SMTP Server (TLS) id 14.3.136.1; Mon, 20 May 2013 19:57:41 +0000
Received: from mail184-co9-R.bigfish.com (10.236.132.234) by CO9EHSOBE036.bigfish.com (10.236.130.99) with Microsoft SMTP Server id 14.1.225.23; Mon, 20 May 2013 19:57:03 +0000
Received: from mail184-co9 (localhost [127.0.0.1])	by mail184-co9-R.bigfish.com (Postfix) with ESMTP id B2180100155	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon, 20 May 2013 19:57:03 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT003.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: 4
X-BigFish: PS4(zzzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz17326ah8275bh8275chz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail184-co9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT003.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB270; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail184-co9 (localhost.localdomain [127.0.0.1]) by mail184-co9 (MessageSwitch) id 1369079821754853_26375; Mon, 20 May 2013 19:57:01 +0000 (UTC)
Received: from CO9EHSMHS004.bigfish.com (unknown [10.236.132.229])	by mail184-co9.bigfish.com (Postfix) with ESMTP id AABBA60006C; Mon, 20 May 2013 19:57:01 +0000 (UTC)
Received: from BL2PRD0310HT003.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS004.bigfish.com (10.236.130.14) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 20 May 2013 19:57:01 +0000
Received: from BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) by BL2PRD0310HT003.namprd03.prod.outlook.com (10.255.97.38) with Microsoft SMTP Server (TLS) id 14.16.311.1; Mon, 20 May 2013 19:56:58 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) with Microsoft SMTP Server (TLS) id 15.0.698.13; Mon, 20 May 2013 19:56:55 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Mon, 20 May 2013 19:56:54 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
Subject: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98Feg==
Date: Mon, 20 May 2013 19:56:53 +0000
Message-ID: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:c925:1c0b:4358:e80a]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB270.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC107.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC107.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(74876001)(81542001)(74706001)(69226001)(50466002)(80022001)(23726002)(6806003)(79102001)(46406003)(47446002)(65816001)(63696002)(74366001)(31966008)(74502001)(53806001)(54356001)(46102001)(20776003)(4396001)(51856001)(74662001)(74316001)(47776003)(44976003)(49866001)(47736001)(54316002)(33646001)(15202345002)(56776001)(77982001)(59766001)(50986001)(47976001)(16676001)(81342001)(56816002)(76482001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB032; H:TK5EX14HUBC107.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0852EB6797
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 20 May 2013 19:59:02 -0000

Disclaimer: haven't read all the prior list discussion so don't know if thi=
s duplicates some existing discussion.

I have some fundamental problems with this document as is.

I will concentrate on sections 1, 2, and Appendix B, being the motivation/g=
oals/justification,
as opposed to the technical details.

Let's start with B.1.1, which attempts to motivate a desire to prevent trac=
king hosts across networks
using their public address(es):
>   Some time later, the same host moves to a completely different
>   network, and employs the same P2P application, probably even with a
>   different username.  The attacker now interacts with the same host
>   again, and hence can learn its newly-configured stable address.
>   Since the Interface Identifier is the same as the one used before,
>   the attacker can infer that it is communicating with the same device
>   as before.

The above text convolutes two orthogonal issues: higher-layer ID (username =
in this case) and
location.   The higher-layer ID in other apps would be the DNS name, but he=
re the text uses
the username, though even in P2P applications the higher-layer ID used to r=
esolve an application
or piece of content would already be stable, and the question is what you c=
an link it to.
If you have two addresses that simultaneously or over time are associated w=
ith the same=20
higher-layer ID, then those two addresses can be linked.  Separate is the i=
ssue of location.
Once you have a stable higher-layer ID that anyone can resolve as you move =
around,
changing the address linked to it doesn't provide any additional privacy (u=
nlinkability).

So one problem with the quoted text is that it does not address the problem=
 of
"a different username" not having a different address (when not moving) and=
 hence
the two higher-layer IDs can be linked using a common address.   Whether on=
e moves or not
is a separate issue.

If unlinkability between two location is desired, then it's key that there =
be no higher-layer ID
in common that can be linked to both addresses.

Furthermore, this notion of unlinkability is that privacy addresses were de=
signed for.
The first paragraph in B.1.1 implies that one would not want to use privacy=
 addresses in
a P2P scenario, and then goes on to talk about why you lose privacy.   That=
's faulty logic in my view.
Privacy or lack of privacy is an explicit decision the application or admin=
istrator can make.
If you opt out of it, you can't complain that you don't have it.

So if the P2P app opted to use public addresses because the app is already =
using a=20
higher-layer ID that can be resolved to the addresses it will use then no p=
rivacy is lost that
wasn't already lost by using the higher-layer ID (which was linkable to the=
 addresses).

The same issue occurs with B.1.2 and B.1.3.

I *do* agree with the address scan prevention goal.   This is why Windows h=
as for the last
10 years used random (not MAC-derived) public (not just temporary) addresse=
s using the
algorithm in 4941.   The IETF works on rough consensus and running code.   =
We have running
code for over a decade now that's widely deployed (it's the default on all =
Windows machines
from XPSP3 onwards).   I would fully support an RFC that uses random public=
 (stable) addresses.

But I see no justification for having public addresses (linkable from DNS n=
ames, etc.) that
vary by network location.   Nor do I see any justification for having link-=
local addresses
(linkable to MAC addresses via ND) that vary by network location.

I think this comes down to fundamental disagreements on what a public addre=
ss is.
A public address is one intended to be resolvable from higher-layer IDs suc=
h as DNS names.
A privacy address is one either (a) not intended to be resolvable from high=
er-layer IDs, OR
(b) one resolvable only from a higher-layer ID that is invented for that ad=
dress and only ever
resolvable to that single address (example: the ipv6-literal.net form of th=
e address.  See
http://ipv6-literal.com/).

The doc says that apps wanting "server-like" functions use public addresses=
.   The key is in
defining what that means, and I'll fully agree it would make more sense to =
have more guidance
in this area.   But specifically "server-like" should be "makes the address=
 linkable to a higher-layer
ID whose lifetime or scope is more than just that one address".  In the IAB=
 documents, we try
to clarify this notion of linkability.

Once you agree on that definition, I think this notion of public addresses =
that vary by location
does not appear to be useful.   Rather than standardizing an ill-motivated =
notion, I would=20
rather see the WG focus on publishing an RFC focusing on the address scanni=
ng problem
that solves it in a way that we already have over a decade of operational e=
xperience with,
which is long overdue.  In doing so, the same doc could provide additional =
clarifications on
when to choose public vs privacy addresses.

-Dave


From fgont@si6networks.com  Mon May 20 20:43:39 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96AAB21F9707 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 20:43:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OtBlJVFvBooA for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 20:43:38 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 73A0D21F9705 for <6man@ietf.org>; Mon, 20 May 2013 20:43:36 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UedTw-0001c6-BS; Tue, 21 May 2013 05:43:25 +0200
Message-ID: <519AD0EF.60600@si6networks.com>
Date: Mon, 20 May 2013 22:42:07 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 May 2013 03:43:40 -0000

Hi, Dave,

This issue was debated more than a year ago, at the IETF Paris
timeframe. Since then, the wg adopted this document, and we went through
WGLC and IETF LC. So I'm not sure how it helps to raise this point again
and at this point in time.

That said, please let me try to clarify a few things, and respond to
your email.

Traditional SLAAC addresses suffer from two problems:

1) They result in addresses that follow specific patterns, and hence
allow attackers to reduce the search space when performing
address-scanning attacks.

2) They employ constant identifiers, which allow host-tracking.


I'll focus on "2)", since it seems that you agree with "1)" being a
problem that remains to be solved.

RFC 4941 specifies temporary addresses which change over time. Temporary
addresses help with passive host-tracking where e.g. a server keeps a
log of the IPv6 addresses that connected to it and could possibly
correlate node activities based on the IID (if th IID is constant).

However, there's still the issue of active-host tracking, where a node
(server or otherwise) actively probes a node to track it. As long as
nodes employ addresses which embed constant IIDs, such host tracking
attacks are feasible. For instance,
<http://www.iab.org/wp-content/IAB-uploads/2011/07/IPv6-addresses-privacy-review.txt>
notes:

---- cut here ----
For a temporary address to provide protection against tracking and
re-identification, it cannot be mixed together with a public address
for the same device, otherwise the temporary address could be
correlated to the persistent public address. This aspect has sometimes
been overlooked in applications' use of multiple addresses generated
in different ways.
---- cut here ----

and later adds:

---- cut here ----
The address-scanning problem can be mitigated by using
randomly-generated suffixes for all addresses, whether they are
public/persistent or temporary. These addresses can still be used for
tracking, but they remove the OUI-associated vulnerability and make
address scanning for IPv6 addresses no easier than for IPv4 addresses.
Windows uses random suffixes for all addresses, but many other
implementations do not.
---- cut here ----


This should make it evident that the scheme implemented by Windows fixes
the address-scanning problem, but is still flawed when it comes to privacy.

We have even implemented a tool to track nodes that employ constant IIDs
(whether derived from IEEE-identifiers, or the approach implemented by
Windows). The tool is scan6, availble as part of the IS6 toolkit at:
<http://www.si6networks.com/tools/ipv6toolkit>). The man page for the
tool contains examples of how to use the tool for such purpose.


Some additional comments in-line....



On 05/20/2013 04:56 PM, Dave Thaler wrote:
> I will concentrate on sections 1, 2, and Appendix B, being the
> motivation/goals/justification, as opposed to the technical details.
> 
> Let's start with B.1.1, which attempts to motivate a desire to
> prevent tracking hosts across networks using their public
> address(es):

[FWIW, the motivation is in the Intro, rather than the Appendix.
Appendix B simply rovides a clarification regarding issues not fixed
with RFC4941... and not that long ago even included a statemet such as
"this will be removed prior to publication of this document as an RFC"]



>> Some time later, the same host moves to a completely different 
>> network, and employs the same P2P application, probably even with
>> a different username.  The attacker now interacts with the same
>> host again, and hence can learn its newly-configured stable
>> address. Since the Interface Identifier is the same as the one used
>> before, the attacker can infer that it is communicating with the
>> same device as before.
> 
> The above text convolutes two orthogonal issues: higher-layer ID
> (username in this case) and location.  The higher-layer ID in other
> apps would be the DNS name, but here the text uses the username,
> though even in P2P applications the higher-layer ID used to resolve
> an application or piece of content would already be stable, and the
> question is what you can link it to.

The point this para is trying to make is that even if the user is
employing a different username in the hopes of hiding its identity, the
constant IID would reveal the identity of the device. (Put another way,
the text regarding the username could even be considered "superflous" in
this case).



> So one problem with the quoted text is that it does not address the
> problem of "a different username" not having a different address
> (when not moving) and hence the two higher-layer IDs can be linked
> using a common address.   Whether one moves or not is a separate
> issue.

As noted in draft-ietf-6man-stable-priacy-addresses, mitigating
correlation of node activities within the same network is, at times,
virtually impossible. And draft-ietf-6man-stable-privacy-addresses does
not aim to tackle such problem.



> If unlinkability between two location is desired, then it's key that
> there be no higher-layer ID in common that can be linked to both
> addresses.

If you have constant IIDs, node activities can be correlated even
without the need of a higher-layer ID.



> Furthermore, this notion of unlinkability is that privacy addresses
> were designed for. The first paragraph in B.1.1 implies that one
> would not want to use privacy addresses in a P2P scenario, and then
> goes on to talk about why you lose privacy. 

No. It actually argues that RFC 4941 didn't get rid of constant IIDs.
Hence you're still subject of active probing.

Trivial example:

I attend an IETF meeting, and learn the IID of your laptop. Then I can
actively probe your node regarding "Is David at the office?" "Is David
at home?", etc.... simply because your IID is known and constant.



> I *do* agree with the address scan prevention goal.   This is why
> Windows has for the last 10 years used random (not MAC-derived)
> public (not just temporary) addresses using the algorithm in 4941.

Which, as noted above, still brings you IIDs that are constant across
networks -- and the corresponding implications.


> The IETF works on rough consensus and running code.   We have
> running code for over a decade now that's widely deployed (it's the
> default on all Windows machines from XPSP3 onwards).  

A suboptimal (or flawed) scheme implemented in a widely-deployed OS
doesn't change the fact that that the scheme is flawed.

And the wg has been working (and progressing) on this document for more
than a year (which is the "rough consensus" part of your quote above).



> But I see no justification for having public addresses (linkable from
> DNS names, etc.) that vary by network location.   Nor do I see any
> justification for having link-local addresses (linkable to MAC
> addresses via ND) that vary by network location.

Actually, the analysis is: "I see no justification for employing an IID
that is constant across networks, nor do I see why should I embed my
address". That's the philosophy (pro-activity?) one would expect to be
applied. Otherwise you'll likely find out that there's this or that
other mechanism or application which informs e.g. all configured
addresses (e.g. ICMPv6 node information messages, to name one), and you
realize that you should have done the right thing from starters.



> I think this comes down to fundamental disagreements on what a public
> address is. A public address is one intended to be resolvable from
> higher-layer IDs such as DNS names.

I prefer to use terms such as stable vs. non-stable. -- At the end of
the day, nothing prevents you from advertising a temporary address in
the DNS, or *not* advertising a stable one in the DNS.



> The doc says that apps wanting "server-like" functions use public
> addresses.   The key is in defining what that means, 

"receiving incoming connections".


> and I'll fully
> agree it would make more sense to have more guidance in this area.
> But specifically "server-like" should be "makes the address linkable
> to a higher-layer ID whose lifetime or scope is more than just that
> one address".  In the IAB documents, we try to clarify this notion of
> linkability.

I should probably s/server-like/receiving incoming connections/ --
although stable addresses are also useful when you want...er.. the
addresses to be stable (prevent long-lived connections from breaking, etc.).



> Once you agree on that definition, I think this notion of public
> addresses that vary by location does not appear to be useful.

It's the other way around: you should find a very good reason for
embedding a super-cookie in your addresses (whether based on the MAC
address, r a random number). Unless you find one, you shouldn't.

This problem has hit some many protocols so many times that it's kind of
surprising that anyone could argue in favor of constant/predictable IDs
where they are not needed.

Thanks!

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





From fernando@gont.com.ar  Mon May 20 20:43:56 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564F321F9705 for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 20:43:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RM83Sqt9E2zs for <ipv6@ietfa.amsl.com>; Mon, 20 May 2013 20:43:55 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 77D8621F970F for <6man@ietf.org>; Mon, 20 May 2013 20:43:55 -0700 (PDT)
Received: from [186.134.40.103] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UedUC-0001cj-H1; Tue, 21 May 2013 05:43:40 +0200
Message-ID: <519AD550.3050005@gont.com.ar>
Date: Mon, 20 May 2013 23:00:48 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com> <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com> <519963BF.9010700@si6networks.com> <65C2C74A-E0C4-4E1F-A72E-5DFBCA038309@apple.com>
In-Reply-To: <65C2C74A-E0C4-4E1F-A72E-5DFBCA038309@apple.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 May 2013 03:43:56 -0000

Hi, James,

On 05/20/2013 02:33 PM, james woodyatt wrote:
>> 
>> Other than the fix you suggested ("it MUST be different for each
>> network interface simultaneously in use."), is there anything to be
>> fixe in, say, Appendix A?
> 
> I don't see why Appendix A needs to comprise an exhaustive list of
> all possibilities, but it might be improved by the addition of
> something like this:
> 
> A.4. Logical Network Service Identity
> 
> Host operating systems with a conception of logical network service
> identity, distinct from network interface identity or index, may keep
> a UUID or similar number with the stability properties appropriate
> for use as the Net_Iface parameter.

Thanks for the text! I'll incorporate it in th next rev.

Question: Is there any reference I could provide about "logical network
service identity"? (even a manpage would be okay...) -- I'd use it as:

"Host operating systems with a conception of logical network service
identity (see e.g. [REFERENCE])..."

Additionally, I'd like to better understand the stability properties of
UUIDs (and add some text about it right after the text that you have
suggested). My assumption is that one would have UUIDs for network
interfaces that would, at least, be constant across system bootstrap
sequences? (that would be something not yet present in OS X now, but
that could be added as part of the implementation of this specification?)


P.S.: Thanks for educating me about the OS X internals!

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fgont@si6networks.com  Tue May 21 14:33:43 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A2711E80BA; Tue, 21 May 2013 14:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.039
X-Spam-Level: 
X-Spam-Status: No, score=-3.039 tagged_above=-999 required=5 tests=[AWL=0.560,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id be++JsOWO9qB; Tue, 21 May 2013 14:33:37 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id 32CD221F92EB; Tue, 21 May 2013 14:33:36 -0700 (PDT)
Received: from [186.134.14.78] (helo=[192.168.123.125]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UeuAg-00029U-Ri; Tue, 21 May 2013 23:32:39 +0200
Message-ID: <519BE7F1.6090203@si6networks.com>
Date: Tue, 21 May 2013 18:32:33 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <253924A3-64BF-42AF-BEC8-EB3051555B59@nostrum.com>
In-Reply-To: <253924A3-64BF-42AF-BEC8-EB3051555B59@nostrum.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 May 2013 21:33:43 -0000

Hi, Ben,

On 05/21/2013 06:05 PM, Ben Campbell wrote:
> I'm not sure my last set of comments got to you; I kept getting email
> bounces. In any case, this version addressed all but one of my
> comments:
> 
> -- section 3, paragraphs starting with "The Interface_ID [Now
> Net_Iface] is a value..."
> 
> You say the following properties are "desirable", but then go on to
> state them with MUSTs in the following bullet points. This is
> ambiguous. If they are only "desirable properties", then the
> normative language is not appropriate. If you mean the MUSTs, then
> these are _requirements_.

Agreed. For instance, Karl Auer reported this one a couple of days ago.
I'll be s/desired/required/ in the upcoming -08 version.

Thanks so much!

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





From dthaler@microsoft.com  Tue May 21 18:35:34 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5E021F8EDA for <ipv6@ietfa.amsl.com>; Tue, 21 May 2013 18:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.717
X-Spam-Level: 
X-Spam-Status: No, score=-97.717 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GCgdUTdLgef4 for <ipv6@ietfa.amsl.com>; Tue, 21 May 2013 18:35:28 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id EF78E21F8EEC for <6man@ietf.org>; Tue, 21 May 2013 18:35:20 -0700 (PDT)
Received: from BY2FFO11FD024.protection.gbl (10.1.15.204) by BY2FFO11HUB006.protection.gbl (10.1.14.164) with Microsoft SMTP Server (TLS) id 15.0.698.0; Wed, 22 May 2013 01:35:18 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD024.mail.protection.outlook.com (10.1.15.213) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Wed, 22 May 2013 01:35:18 +0000
Received: from tx2outboundpool.messaging.microsoft.com (157.54.51.112) by mail.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.3.136.1; Wed, 22 May 2013 01:35:17 +0000
Received: from mail163-tx2-R.bigfish.com (10.9.14.252) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.23; Wed, 22 May 2013 01:35:07 +0000
Received: from mail163-tx2 (localhost [127.0.0.1])	by mail163-tx2-R.bigfish.com (Postfix) with ESMTP id E11511E015C	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 22 May 2013 01:35:07 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT004.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -25
X-BigFish: PS-25(zzbb2dI98dI9371I103dK542I1432I62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail163-tx2: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT004.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB272; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail163-tx2 (localhost.localdomain [127.0.0.1]) by mail163-tx2 (MessageSwitch) id 1369186504961160_8616; Wed, 22 May 2013 01:35:04 +0000 (UTC)
Received: from TX2EHSMHS009.bigfish.com (unknown [10.9.14.235])	by mail163-tx2.bigfish.com (Postfix) with ESMTP id E5C59220088; Wed, 22 May 2013 01:35:04 +0000 (UTC)
Received: from BL2PRD0310HT004.namprd03.prod.outlook.com (157.56.240.21) by TX2EHSMHS009.bigfish.com (10.9.99.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 22 May 2013 01:35:04 +0000
Received: from BY2PR03MB272.namprd03.prod.outlook.com (10.242.37.24) by BL2PRD0310HT004.namprd03.prod.outlook.com (10.255.97.39) with Microsoft SMTP Server (TLS) id 14.16.311.1; Wed, 22 May 2013 01:34:57 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB272.namprd03.prod.outlook.com (10.242.37.24) with Microsoft SMTP Server (TLS) id 15.0.698.13; Wed, 22 May 2013 01:34:54 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Wed, 22 May 2013 01:34:54 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7A=
Date: Wed, 22 May 2013 01:34:54 +0000
Message-ID: <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com>
In-Reply-To: <519AD0EF.60600@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:29f0:31eb:7f7b:c86e]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB272.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC103.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC103.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(41574002)(24454002)(51704005)(377454002)(479174002)(199002)(189002)(252514006)(13464003)(80022001)(16676001)(44976003)(65816001)(51856001)(74502001)(56776001)(33646001)(79102001)(20776003)(47976001)(50986001)(74662001)(46102001)(53806001)(31966008)(74876001)(4396001)(74366001)(47446002)(69226001)(47736001)(49866001)(59766001)(54316002)(47776003)(81342001)(77982001)(76482001)(74706001)(56816002)(23726002)(74316001)(81542001)(6806003)(63696002)(46406003)(50466002)(54356001)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB006; H:TK5EX14HUBC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0854128AF0
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 May 2013 01:35:34 -0000

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Monday, May 20, 2013 6:42 PM
> To: Dave Thaler
> Cc: 6man@ietf.org; 6man-chairs@tools.ietf.org; Brian Haberman; Ray Hunter=
;
> Alissa Cooper; tom.petch; Christian Huitema; He Xuan
> Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> Hi, Dave,
>=20
> This issue was debated more than a year ago, at the IETF Paris timeframe.
> Since then, the wg adopted this document, and we went through WGLC and
> IETF LC. So I'm not sure how it helps to raise this point again and at th=
is point
> in time.

The problem is that the draft does not contain any understandable=20
justification, and does not explain the threat model it's trying to address
in a way that's sufficient for readers like me to understand.  So regardles=
s of
whether or not the WG has consensus, the document is lacking in any case.
=20
> That said, please let me try to clarify a few things, and respond to your=
 email.
>=20
> Traditional SLAAC addresses suffer from two problems:
>=20
> 1) They result in addresses that follow specific patterns, and hence allo=
w
> attackers to reduce the search space when performing address-scanning
> attacks.

Agreed, that's the part I'm 100% in agreement with addressing.
=20
> 2) They employ constant identifiers, which allow host-tracking.

By design.  Host tracking is already allowed with constant higher-layer ide=
ntifiers,
e.g., DNS names, etc.  So having constant addresses associated with=20
constant higher-layer identifiers is not any different.  And having non-con=
stant=20
address associated with them does not provide any value add.

> I'll focus on "2)", since it seems that you agree with "1)" being a probl=
em that
> remains to be solved.

Actually it's been solved (and widely deployed) since over a decade ago.  I=
t
remains to be *standardized*, which is the part I agree with.
=20
> RFC 4941 specifies temporary addresses which change over time. Temporary
> addresses help with passive host-tracking where e.g. a server keeps a log=
 of
> the IPv6 addresses that connected to it and could possibly correlate node
> activities based on the IID (if th IID is constant).

Right.

> However, there's still the issue of active-host tracking, where a node (s=
erver
> or otherwise) actively probes a node to track it. As long as nodes employ
> addresses which embed constant IIDs, such host tracking attacks are feasi=
ble.
> For instance, <http://www.iab.org/wp-content/IAB-uploads/2011/07/IPv6-
> addresses-privacy-review.txt>
> notes:
> ---- cut here ----
> For a temporary address to provide protection against tracking and re-
> identification, it cannot be mixed together with a public address for the=
 same
> device, otherwise the temporary address could be correlated to the
> persistent public address. This aspect has sometimes been overlooked in
> applications' use of multiple addresses generated in different ways.
> ---- cut here ----

As you might know, that text is Alissa's nicely edited version of a talk I =
gave
to the IAB Privacy Program, so I will of course agree with all quotes from =
it=20
and fully endorse their use in any WG document :)   Some of the information
on that page is not currently in any IETF document to my knowledge, but=20
ought to be.

> and later adds:
>=20
> ---- cut here ----
> The address-scanning problem can be mitigated by using randomly-
> generated suffixes for all addresses, whether they are public/persistent =
or
> temporary. These addresses can still be used for tracking, but they remov=
e
> the OUI-associated vulnerability and make address scanning for IPv6
> addresses no easier than for IPv4 addresses.
> Windows uses random suffixes for all addresses, but many other
> implementations do not.
> ---- cut here ----
>=20
> This should make it evident that the scheme implemented by Windows fixes
> the address-scanning problem, but is still flawed when it comes to privac=
y.

Your conclusion doesn't make sense.   The text is explaining that there are
two issues.  Address scanning is mitigated by random suffixes.  Tracking
is mitigated by using temporary addresses (that change over time and locati=
on).
Windows does both, so is not "flawed" as you incorrectly conclude.

> We have even implemented a tool to track nodes that employ constant IIDs
> (whether derived from IEEE-identifiers, or the approach implemented by
> Windows). The tool is scan6, availble as part of the IS6 toolkit at:
> <http://www.si6networks.com/tools/ipv6toolkit>). The man page for the
> tool contains examples of how to use the tool for such purpose.

The key question is "employ" for what?  For example, if "employ for registe=
ring in
DNS" then I assure you I don't need your tool to track that...
If "employ for making outbound TCP connections", then temporary addresses=20
(not constant IIDs) are used for that, so again it doesn't apply.
So please elaborate on what you meant.
=20
> Some additional comments in-line....
>=20
> On 05/20/2013 04:56 PM, Dave Thaler wrote:
> > I will concentrate on sections 1, 2, and Appendix B, being the
> > motivation/goals/justification, as opposed to the technical details.
> >
> > Let's start with B.1.1, which attempts to motivate a desire to prevent
> > tracking hosts across networks using their public
> > address(es):
>=20
> [FWIW, the motivation is in the Intro, rather than the Appendix.
> Appendix B simply rovides a clarification regarding issues not fixed with
> RFC4941... and not that long ago even included a statemet such as "this w=
ill
> be removed prior to publication of this document as an RFC"]

I couldn't understand any motivation that made sense to me=20
for changing the IID of a *public* address or a *link-local* address, when
moving.
(I of course understand motivation for preventing address scans.)
=20
> >> Some time later, the same host moves to a completely different
> >> network, and employs the same P2P application, probably even with a
> >> different username.  The attacker now interacts with the same host
> >> again, and hence can learn its newly-configured stable address. Since
> >> the Interface Identifier is the same as the one used before, the
> >> attacker can infer that it is communicating with the same device as
> >> before.
> >
> > The above text convolutes two orthogonal issues: higher-layer ID
> > (username in this case) and location.  The higher-layer ID in other
> > apps would be the DNS name, but here the text uses the username,
> > though even in P2P applications the higher-layer ID used to resolve an
> > application or piece of content would already be stable, and the
> > question is what you can link it to.
>=20
> The point this para is trying to make is that even if the user is employi=
ng a
> different username in the hopes of hiding its identity, the constant IID =
would
> reveal the identity of the device. (Put another way, the text regarding t=
he
> username could even be considered "superflous" in this case).

Remove superfluous text that confuses the issue.  My point remains about
either there's a higher-layer ID that's constant (in which case changing th=
e
IID is not helpful) or there's not (in which case the app should be using
temporary addresses not stable addresses).   The text provides no clue
as to why an app would opt into stable addresses and then be concerned
about privacy, which makes no sense to me.

> > So one problem with the quoted text is that it does not address the
> > problem of "a different username" not having a different address (when
> > not moving) and hence the two higher-layer IDs can be linked
> > using a common address.   Whether one moves or not is a separate
> > issue.
>=20
> As noted in draft-ietf-6man-stable-priacy-addresses, mitigating correlati=
on of
> node activities within the same network is, at times, virtually impossibl=
e. And
> draft-ietf-6man-stable-privacy-addresses does not aim to tackle such
> problem.
>=20
>=20
>=20
> > If unlinkability between two location is desired, then it's key that
> > there be no higher-layer ID in common that can be linked to both
> > addresses.
>=20
> If you have constant IIDs, node activities can be correlated even without=
 the
> need of a higher-layer ID.

Yes, and if you have a higher-layer ID that's constant,  linking it to
non-constant IIDs is not helpful.   So I fail to see the point.

> > Furthermore, this notion of unlinkability is that privacy addresses
> > were designed for. The first paragraph in B.1.1 implies that one would
> > not want to use privacy addresses in a P2P scenario, and then goes on
> > to talk about why you lose privacy.
>=20
> No. It actually argues that RFC 4941 didn't get rid of constant IIDs.

RFC 4941 never intended to get rid of constant IIDs, which would only make =
sense
if you got rid of constant higher-layer IDs like DNS names.  But this is th=
e real world
where such higher-layer IDs are used all the time.

> Hence you're still subject of active probing.
>=20
> Trivial example:
>=20
> I attend an IETF meeting, and learn the IID of your laptop. Then I can ac=
tively
> probe your node regarding "Is David at the office?" "Is David at home?",
> etc.... simply because your IID is known and constant.

Since you're making this personal... please explain how you can probe wheth=
er=20
I'm at the office or at home, both of which are behind firewalls (so won't =
respond
to arbitrary probes) and have address prefixes you don't know to begin with=
.

Furthermore, how do you know I don't publish my addresses in a well-known
DNS name and hence want my node's location to be public?
(More generally, replace DNS name with any constant higher-layer ID.)
=20
> > I *do* agree with the address scan prevention goal.   This is why
> > Windows has for the last 10 years used random (not MAC-derived) public
> > (not just temporary) addresses using the algorithm in 4941.
>=20
> Which, as noted above, still brings you IIDs that are constant across net=
works
> -- and the corresponding implications.

I have yet to see a coherent threat model described for these
"implications".
=20
> > The IETF works on rough consensus and running code.   We have
> > running code for over a decade now that's widely deployed (it's the
> > default on all Windows machines from XPSP3 onwards).
>=20
> A suboptimal (or flawed) scheme implemented in a widely-deployed OS
> doesn't change the fact that that the scheme is flawed.

Have yet to see how.
=20
> And the wg has been working (and progressing) on this document for more
> than a year (which is the "rough consensus" part of your quote above).

Not a great excuse.  There's plenty of other examples of documents that
were flawed for more than a year and the WG reversed direction.
(I could point to one recent one in the 6man WG but this is really off topi=
c.)

> > But I see no justification for having public addresses (linkable from
> > DNS names, etc.) that vary by network location.   Nor do I see any
> > justification for having link-local addresses (linkable to MAC
> > addresses via ND) that vary by network location.
>=20
> Actually, the analysis is: "I see no justification for employing an IID t=
hat is
> constant across networks,=20

I provided you one in this thread, which you seem to have missed, so I'll
repeat it again.   If you have a constant higher-layer ID, such as a DNS na=
me
that you keep up to date with your current public address, there's no value
in having an IID that varies by network.  It only adds extra complexity wit=
hout
real value.   So the justification is "it works, it's widely deployed, and =
there's
no reason to change it in this particular case".

> nor do I see why should I embed my address".
> That's the philosophy (pro-activity?) one would expect to be applied.
> Otherwise you'll likely find out that there's this or that other mechanis=
m or
> application which informs e.g. all configured addresses (e.g. ICMPv6 node
> information messages, to name one), and you realize that you should have
> done the right thing from starters.
>=20
> > I think this comes down to fundamental disagreements on what a public
> > address is. A public address is one intended to be resolvable from
> > higher-layer IDs such as DNS names.
>=20
> I prefer to use terms such as stable vs. non-stable. -- At the end of the=
 day,
> nothing prevents you from advertising a temporary address in the DNS, or
> *not* advertising a stable one in the DNS.
>
> > The doc says that apps wanting "server-like" functions use public
> > addresses.   The key is in defining what that means,
>=20
> "receiving incoming connections".=20
>=20
> > and I'll fully
> > agree it would make more sense to have more guidance in this area.
> > But specifically "server-like" should be "makes the address linkable
> > to a higher-layer ID whose lifetime or scope is more than just that
> > one address".  In the IAB documents, we try to clarify this notion of
> > linkability.
>=20
> I should probably s/server-like/receiving incoming connections/ -- althou=
gh
> stable addresses are also useful when you want...er.. the addresses to be
> stable (prevent long-lived connections from breaking, etc.).
>=20
>=20
>=20
> > Once you agree on that definition, I think this notion of public
> > addresses that vary by location does not appear to be useful.
>=20
> It's the other way around: you should find a very good reason for embeddi=
ng
> a super-cookie in your addresses (whether based on the MAC address, r a
> random number). Unless you find one, you shouldn't.

Already answered above.
=20
> This problem has hit some many protocols so many times that it's kind of
> surprising that anyone could argue in favor of constant/predictable IDs
> where they are not needed.
>=20
> Thanks!
>=20
> Best regards,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
>=20



From fgont@si6networks.com  Tue May 21 21:33:27 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16CED21F8ED8 for <ipv6@ietfa.amsl.com>; Tue, 21 May 2013 21:33:27 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbvLUiWQXL4Q for <ipv6@ietfa.amsl.com>; Tue, 21 May 2013 21:33:22 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [93.186.182.34]) by ietfa.amsl.com (Postfix) with ESMTP id A262721F8ECB for <6man@ietf.org>; Tue, 21 May 2013 21:33:20 -0700 (PDT)
Received: from [2001:5c0:1000:a::539] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Uf0ir-0005kL-Vj; Wed, 22 May 2013 06:32:43 +0200
Message-ID: <519C46F2.8040406@si6networks.com>
Date: Wed, 22 May 2013 01:17:54 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 May 2013 04:33:27 -0000

On 05/21/2013 10:34 PM, Dave Thaler wrote:
>>
>> This issue was debated more than a year ago, at the IETF Paris timeframe.
>> Since then, the wg adopted this document, and we went through WGLC and
>> IETF LC. So I'm not sure how it helps to raise this point again and at this point
>> in time.
> 
> The problem is that the draft does not contain any understandable 
> justification, and does not explain the threat model it's trying to address
> in a way that's sufficient for readers like me to understand.  So regardless of
> whether or not the WG has consensus, the document is lacking in any case.

I'm always open for improvements. I personally believe that the current
version of the I-D is clear enough in that respect. In any case, since
you consider there's room for improvement, hopefully this email exchange
will either clarify things a bit and/or lead to improvements.



>> 2) They employ constant identifiers, which allow host-tracking.
> 
> By design.  Host tracking is already allowed with constant higher-layer identifiers,
> e.g., DNS names, etc.

You are assuming those identifiers are there. But they needn't.



> So having constant addresses associated with 
> constant higher-layer identifiers is not any different.  And having non-constant 
> address associated with them does not provide any value add.

I'm not sure why you bring this "higher-layer identifiers". The attack
vector I mentioned (actively polling possible addresses as opposed to
passively looking at IIDs still works pretty well without any sort of
higher-layer IID).



>> I'll focus on "2)", since it seems that you agree with "1)" being a problem that
>> remains to be solved.
> 
> Actually it's been solved (and widely deployed) since over a decade ago.  It
> remains to be *standardized*, which is the part I agree with.

I disagree it has been solved -- the only thing you've solved is
address-scanning.



>> ---- cut here ----
>> The address-scanning problem can be mitigated by using randomly-
>> generated suffixes for all addresses, whether they are public/persistent or
>> temporary. These addresses can still be used for tracking, but they remove
>> the OUI-associated vulnerability and make address scanning for IPv6
>> addresses no easier than for IPv4 addresses.
>> Windows uses random suffixes for all addresses, but many other
>> implementations do not.
>> ---- cut here ----
>>
>> This should make it evident that the scheme implemented by Windows fixes
>> the address-scanning problem, but is still flawed when it comes to privacy.
> 
> Your conclusion doesn't make sense.   The text is explaining that there are
> two issues.  Address scanning is mitigated by random suffixes.  Tracking
> is mitigated by using temporary addresses (that change over time and location).
> Windows does both, so is not "flawed" as you incorrectly conclude.

You don't mitigate tracking as long as you still keep some address with
constant IDs. The only thing that you "mitigate" with RFC 4941 is that
with RFC 4941 in place, the attacker can no longer "passively" track
you, but rather has to send some packet to cause you to use the address
that will leak your identity. -- Just firing a packet that will elicit a
response from that address is enough.



>> We have even implemented a tool to track nodes that employ constant IIDs
>> (whether derived from IEEE-identifiers, or the approach implemented by
>> Windows). The tool is scan6, availble as part of the IS6 toolkit at:
>> <http://www.si6networks.com/tools/ipv6toolkit>). The man page for the
>> tool contains examples of how to use the tool for such purpose.
> 
> The key question is "employ" for what?  For example, if "employ for registering in
> DNS" then I assure you I don't need your tool to track that...
> If "employ for making outbound TCP connections", then temporary addresses 
> (not constant IIDs) are used for that, so again it doesn't apply.
> So please elaborate on what you meant.

Let's say that your stable IID is 1111:2222:3333:4444:5555, and that,
for the sake of simplicity, the world consists of four networks:
2001:db8:1::/64, 2001:db8:2::/64, 2001:db8:3::/64, and 2001:db8:4::/64.

It thus becomes trivial to track you. Just periodically fire probe
packets to 2001:db8:1::1111:2222:3333:4444:5555,
2001:db8:2::1111:2222:3333:4444 (and so on), and the address that
responds leaks your location.



>> On 05/20/2013 04:56 PM, Dave Thaler wrote:
>>> I will concentrate on sections 1, 2, and Appendix B, being the
>>> motivation/goals/justification, as opposed to the technical details.
>>>
>>> Let's start with B.1.1, which attempts to motivate a desire to prevent
>>> tracking hosts across networks using their public
>>> address(es):
>>
>> [FWIW, the motivation is in the Intro, rather than the Appendix.
>> Appendix B simply rovides a clarification regarding issues not fixed with
>> RFC4941... and not that long ago even included a statemet such as "this will
>> be removed prior to publication of this document as an RFC"]
> 
> I couldn't understand any motivation that made sense to me 
> for changing the IID of a *public* address or a *link-local* address, when
> moving.
> (I of course understand motivation for preventing address scans.)

I couldn't understand any motivation for keeping them constant. And past
experience with virtually every ID you can think of indicates that, the
less predictable/constant such IDs are, the better.


>>> The above text convolutes two orthogonal issues: higher-layer ID
>>> (username in this case) and location.  The higher-layer ID in other
>>> apps would be the DNS name, but here the text uses the username,
>>> though even in P2P applications the higher-layer ID used to resolve an
>>> application or piece of content would already be stable, and the
>>> question is what you can link it to.
>>
>> The point this para is trying to make is that even if the user is employing a
>> different username in the hopes of hiding its identity, the constant IID would
>> reveal the identity of the device. (Put another way, the text regarding the
>> username could even be considered "superflous" in this case).
> 
> Remove superfluous text that confuses the issue. 

Agreed. Will fix this.


>  My point remains about
> either there's a higher-layer ID that's constant (in which case changing the
> IID is not helpful) or there's not (in which case the app should be using
> temporary addresses not stable addresses).   

As noted above, the app can use any address it wants. But since the
stable address is still there, and attacker can cause the node to use
that stable address by simpl directing a packet to it.



> The text provides no clue
> as to why an app would opt into stable addresses and then be concerned
> about privacy, which makes no sense to me.

All the above said the main benefit that temporary addresses buy you is
trying to mitigate correlation of node activities within the same
network (which, at times, is not possible no matter whether your
addresses are temporary of not). In those cases where temporary
addressess are deemed to be unacceptable (from an ops perspective),
draft-ietf-6man-stable-privacy-addreses can result in an acceptable
tradeoff.



> 
>>> Furthermore, this notion of unlinkability is that privacy addresses
>>> were designed for. The first paragraph in B.1.1 implies that one would
>>> not want to use privacy addresses in a P2P scenario, and then goes on
>>> to talk about why you lose privacy.
>>
>> No. It actually argues that RFC 4941 didn't get rid of constant IIDs.
> 
> RFC 4941 never intended to get rid of constant IIDs, which would only make sense
> if you got rid of constant higher-layer IDs like DNS names.  But this is the real world
> where such higher-layer IDs are used all the time.

Such higher-layer IDs are not required for all apps.. And employing
constant IIDs hurts the privacy of nodes that are not using using such
higher-layer IDs.



>> Hence you're still subject of active probing.
>>
>> Trivial example:
>>
>> I attend an IETF meeting, and learn the IID of your laptop. Then I can actively
>> probe your node regarding "Is David at the office?" "Is David at home?",
>> etc.... simply because your IID is known and constant.
> 
> Since you're making this personal... 

It wasn't meant to.


> please explain how you can probe whether 
> I'm at the office or at home, both of which are behind firewalls (so won't respond
> to arbitrary probes) and have address prefixes you don't know to begin with.

The fact that you clarify "Note: I'm behind a firewall" is pretty much
an implicit acknowledgement that the scheme you're using is flawed.

(With that logic, you can use any flawed scheme as long as you keep your
node unplugged from the net.)

You don't need any firewall to mitigate this attack vector if you
implement draft-ietf-6man-stable-privacy-addresses rather than the
scheme currently implemented by Windows.



> Furthermore, how do you know I don't publish my addresses in a well-known
> DNS name and hence want my node's location to be public?
> (More generally, replace DNS name with any constant higher-layer ID.)

Well, the challenge is in tracking nodes that we assume that do not want
to be tracked....



>>> But I see no justification for having public addresses (linkable from
>>> DNS names, etc.) that vary by network location.   Nor do I see any
>>> justification for having link-local addresses (linkable to MAC
>>> addresses via ND) that vary by network location.
>>
>> Actually, the analysis is: "I see no justification for employing an IID that is
>> constant across networks, 
> 
> I provided you one in this thread, which you seem to have missed, so I'll
> repeat it again.   If you have a constant higher-layer ID, such as a DNS name
> that you keep up to date with your current public address, there's no value
> in having an IID that varies by network. 

The onus is on you for wanting to keep them constant, rather than on me
for being proactive (and avoiding the kind of IDs that lead to flaws in
so many other protocols).



> It only adds extra complexity without
> real value.   So the justification is "it works, it's widely deployed, and there's
> no reason to change it in this particular case".

Sound pretty much sound like "It works -- as long as nobody wants to
exploit it --.. but our customers bought it anyway... so why should we
don't care?" to me.

That said, draft-ietf-6amn-stable-privacy-addresses doesn't obsolete the
traditional SLAAC IIDs, nor your non-standard approach... So you're free
to keep your stack "as is". In the same way that those who care about an
improved scheme, can implement it. It's a win-win situation, you might
say. :-)

FWIW, I know of at least three OSes that plan to implement
draft-ietf-6man-stableprivacy-addresses.

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





From ben@nostrum.com  Tue May 21 14:05:04 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55E801F0D38; Tue, 21 May 2013 14:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJYQamYfwC5Q; Tue, 21 May 2013 14:05:03 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2191F0D23; Tue, 21 May 2013 14:05:03 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4LL51SH009765 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 May 2013 16:05:02 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <51990CE7.7010903@si6networks.com>
Date: Tue, 21 May 2013 16:05:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <253924A3-64BF-42AF-BEC8-EB3051555B59@nostrum.com>
References: <51990CE7.7010903@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Wed, 22 May 2013 00:00:15 -0700
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 21 May 2013 21:05:04 -0000

(resending to include Gen-ART and 6man lists at Fernando's request)

Hi Fernando,

I'm not sure my last set of comments got to you; I kept getting email =
bounces. In any case, this version addressed all but one of my comments:

-- section 3, paragraphs starting with "The Interface_ID [Now Net_Iface] =
is a value..."

You say the following properties are "desirable", but then go on to =
state them with MUSTs in the following bullet points. This is ambiguous. =
If they are only "desirable properties", then the normative language is =
not appropriate. If you mean the MUSTs, then these are _requirements_.

Thanks!

Ben.


On May 19, 2013, at 12:33 PM, Fernando Gont <fgont@si6networks.com> =
wrote:

> Folks,
>=20
> I've posted a rev of the aforementioned document, meant to address the
> comments received during IETF LC.
>=20
> This rev is the result of the IETF LC discussions we had on the 6man =
wg
> list and on the general IETF list, and of off-list discussions with a
> number of folks who generously provided input, reviewed proposed
> changes, etc.
>=20
> I'd expect this rev to be "ready to ship" or very close to that. But
> please provide your input confirming whether you think that's the =
case,
> or whether there are any remaining issues to be solved.
>=20
> The rev is available at:
> =
<http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-07>.
>=20
> A diff from the previous version of the I-D is available at:
> =
<tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-ietf-6man-s=
table-privacy-addresses-06.txt&url2=3Dhttp://tools.ietf.org/id/draft-ietf-=
6man-stable-privacy-addresses-07.txt>.
>=20
> Thanks so much!
>=20
> Best regards,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20


From tjc@ecs.soton.ac.uk  Wed May 22 01:50:38 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C37B521F9609 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 01:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJC5ZBb2UmZ0 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 01:50:36 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 6E2E421F930C for <6man@ietf.org>; Wed, 22 May 2013 01:50:36 -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 r4M8oY4f002955 for <6man@ietf.org>; Wed, 22 May 2013 09:50:34 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4M8oY4f002955
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369212634; bh=MJxYeNmWcg69tJX7YapTM7T44xg=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=QXwJfZtESISg61uz1rVQ77yIK+qK0wYEzplXdqsDht6uCv0pYq1kacWFS9IEopUOw pj3xdx6lVuPUaQRdU+AdFibtccPl2F9jFcA1tcM/TvafY/flSR8wvAAjPpOO8zhO1b r/sSabEOU0nUsTZuWvyuugDI3vqIyA7IE/dvNnhw=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4L9oY0430652055xy ret-id none; Wed, 22 May 2013 09:50:34 +0100
Received: from dhcp-204-198.wireless.soton.ac.uk (dhcp-204-198.wireless.soton.ac.uk [152.78.204.198]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4M8oT95020969 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <6man@ietf.org>; Wed, 22 May 2013 09:50:29 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519AD550.3050005@gont.com.ar>
Date: Wed, 22 May 2013 09:50:29 +0100
Content-Transfer-Encoding: 7bit
Message-ID: <EMEW3|32101a301b8e63d6bd300ab5a68c5cecp4L9oY03tjc|ecs.soton.ac.uk|EB427E67-E67E-421D-8466-313F2F6C0453@ecs.soton.ac.uk>
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com> <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com> <519963BF.9010700@si6networks.com> <65C2C74A-E0C4-4E1F-A72E-5DFBCA038309@apple.com> <519AD550.3050005@gont.com.ar> <EB427E67-E67E-421D-8466-313F2F6C0453@ecs.soton.ac.uk>
To: 6man@ietf.org
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4L9oX043065205500; tid=p4L9oY0430652055xy; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4M8oY4f002955
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 May 2013 08:50:39 -0000

On 21 May 2013, at 03:00, Fernando Gont <fernando@gont.com.ar> wrote:
> 
> Additionally, I'd like to better understand the stability properties of
> UUIDs (and add some text about it right after the text that you have
> suggested). My assumption is that one would have UUIDs for network
> interfaces that would, at least, be constant across system bootstrap
> sequences? (that would be something not yet present in OS X now, but
> that could be added as part of the implementation of this specification?)

Hi Fernando, you may wish to look at RFC 6355 about that and similar issues.

Tim


From otroan@employees.org  Wed May 22 02:42:04 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 844E121F9607 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 02:42:04 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tno+cPPnMKig for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 02:41:57 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) by ietfa.amsl.com (Postfix) with ESMTP id D49E421F9603 for <ipv6@ietf.org>; Wed, 22 May 2013 02:41:57 -0700 (PDT)
Received: from dhcp-lys02-vla252-10-147-116-61.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 67F535E9B; Wed, 22 May 2013 02:41:56 -0700 (PDT)
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6man IETF87 Call for agenda items
Date: Wed, 22 May 2013 11:41:54 +0200
Message-Id: <AB05A86A-6D4E-413C-B98F-5E343E7B456F@employees.org>
To: "ipv6@ietf.org List" <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 May 2013 09:42:04 -0000

Since July is holiday month for many (at least for me), we are starting =
the planning for IETF87 early.

We have asked for a two hour slot in Berlin for the 6MAN working group.

If you have a draft you would like to discuss, please send your request =
for agenda time to the 6man chairs.
Please include in the request, the title and file name of the draft, the =
speakers name (and email),
and how much time you need.

We will prioritise drafts that are working group items and drafts that =
have been actively discussed on the list.
We expect about half the presentation time to be used for open =
discussion,
please plan your presentation accordingly.

New drafts not discussed on the mailing list prior to the meeting,
or drafts that do not appear to have support from the working group are =
unlikely to get time at the meeting.

Please have agenda items to us by 2013-06-30 and also note the following =
deadlines for IETF87:

2013-07-08 (Monday): Internet Draft Cut-off for initial document (-00) =
submission by UTC 24:00
2013-07-15 (Monday): Internet Draft final submission cut-off by UTC =
24:00

Regards,

Bob & Ole=

From tjc@ecs.soton.ac.uk  Wed May 22 06:19:55 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F24D21F8319 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 06:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grYZfUSap9MK for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 06:19:53 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id C505821F826B for <6man@ietf.org>; Wed, 22 May 2013 06:19:52 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4MDJnD3025103;  Wed, 22 May 2013 14:19:49 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4MDJnD3025103
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369228790; bh=6d0bmibhdMhXNyTkclZQGM/Qn6Y=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=Tt1howFM0C0+jI9DwSToJ9ujZgWENy+leME+CYxPCYGOopapA0L7+aG9Zd/qBetSy WZFjnaQPTliNNVwByiX5v7U+8Uk2o1cvwSCr+cXqyt4Z3E0Qt0mGcogbT1vfhgqIMT YDf0y1xpPq8xl1j2Vd4u+8GD3SG6r3cQI/bdbisM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4LEJn043065683951 ret-id none; Wed, 22 May 2013 14:19:50 +0100
Received: from dhcp-204-198.wireless.soton.ac.uk (dhcp-204-198.wireless.soton.ac.uk [152.78.204.198]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4MDJlJY024742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 May 2013 14:19:47 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519C46F2.8040406@si6networks.com>
Date: Wed, 22 May 2013 14:19:47 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519C46F2.8040406@si6networks.com> <ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk>
To: "6man@ietf.org" <6man@ietf.org>, Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4LEJn043065683900; tid=p4LEJn043065683951; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4MDJnD3025103
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: 6man-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 22 May 2013 13:19:55 -0000

Hi Fernando,

I've read -07 and have some comments. Apologies if they are duplicates =
of previous comments.

Overall, I think this is good work and should be progressed.

First, some general comments:

You may wish to be clearer earlier in the document (abstract and/or =
introduction) that your method applies to all prefixes a host may have, =
including link-local, ULA, and global(s).  As it stands, you only, for =
example, mention link-locals first in Section 3.

The implication of the above is that a multihomed host will have =
different IIDs per ISP it receives a prefix from. This may have privacy =
advantages in a static device scenario (this is implied, but never =
stated anywhere that I can see).

There is some focus in your text on why you might disable 4941. That's =
not that common a practice, esp. in campus networks, or home networks. =
While some admins may wish to disable 4941 where they can, I think you =
should promote use of your method with 4941 being perfectly reasonable =
to use alongside it, rather than saying "because 4941 may be turned off, =
we need this method". Related, is that in a few places you talk about =
your method helping to reduce tracking between networks, while in =
practice using 4941 for static (desktop) devices does have benefits.

Specific comments:

Section 1:=20

In the bullet point "since embedding" you may wish to be clearer that =
the "pattern" is the IID format caused by, for example, basing the IID =
on an IEEE identifier.

"other information collectors", I guess you mean sites running services, =
e.g. typically through web server logs.

Not sure what the point about inferring that temporary addresses are in =
use buys you.  Do you mean that with a small number of hosts in a subnet =
you may be able to deduce which devices are which by looking for when =
their addresses change?  That doesn't help you identify that same host =
later or in a different network though?

As an aside here, I looked in our network monitoring database, and my =
desktop Mac over the last month has been seen to use a link-local IPv6 =
address, many IPv6 privacy addresses, and an IPv4 global address, but =
not its global SLAAC address.  That's because nothing has connected to =
it from outside the local subnet. Sure, if we did not have an IPv6 =
firewall (as Dave pointed out) the host could be scannable due to its =
"predictable" Mac OUI, but it's interesting that in the last month, my =
global SLAAC address has never been used. Of course I don't happen to =
run any advertised services, though if I did my address would most =
likely be discoverable by looking at the DNS name it is referred to by.

Section 3:

Second main paragraph, you might add "just as per SLAAC today", or words =
to that effect. I don't think this is any change as such.

The Network_ID might perhaps in the future be some MIF-related =
provisioning domain identifier.  But your method does not preclude that.

Not sure about mentioning IIDs smaller than 64 bits here. You may wish =
to more clearly recommend that your method uses 64-bit IIDs?

"Including the SLAAC prefix"... you say the IID then varies across =
networks, but you may wish to add that the IID will also vary across =
each prefix the nodes uses (link-local, ULA, each global if multihomed).

There's a conflict in the next paragraph about "desirable" and "MUST" - =
which is it?

Perhaps you should state that you can never guarantee IID stability per =
prefix on any given interface, but your method seeks to honour that goal =
where it can.

The comment about MS Windows should perhaps be more orthogonal.  A node =
IID may be manually configured, it may use DHCP, it may use SLAAC with =
IEEE identifiers, it may use your method, it may use the method MS =
Windows uses, or it may even use the tokenised identifier method that I =
posted a while ago.  It can use any of those, AND use 4941 as well.  But =
saying "such implementations would not be affected by the method" =
doesn't sound quite right.=20

Section 4:

Fourth main paragraph, what is the most likely cause of repeated DAD =
conflicts/failures?  NS/NA DoS?  Is there anything else that would be =
likely to cause this?  Worth elaborating on that when considering tuning =
the retry limit?

Section 7:

Maybe clarify that the first bullet point is for inbound connections =
only.

A fourth bullet point could be that you do not disclose hints about =
hardware types.

A fifth could be that IIDs may only be tracked or probed for each prefix =
the host is known to use, e.g. detection or disclosure of the link-local =
IID does not compromise the IID used for incoming global connections.  =
So if you sniff for IPv6 service discovery traffic, for example, you may =
learn a node's link-local IID, but not be able to deduce its global =
address.

How does your RA "attack" work in practice here?  Do you mean issuing a =
rogue RA for the same prefix?  We should perhaps assume that robust =
rogue RA protection is in place, and if not there are many worse things =
an attacker can do!

Perhaps note/remind here that RFC4862 says to run DAD per prefix =
(section 5.4).

Appendix B:

B.1 you say "one possible attack", then list more than one.

B.1.1 It will be interesting to see what emerging IPv6 "peer to peer" =
applications do. Do both ends use SLAAC/your method, both ends use 4941, =
or the "client" use 4941 and the "server" SLAAC/your method.=20

B.1.3 Worth any consideration of MIPv6 here?  The Home Address is =
obviously trackable, by design, but any Care-of Address could benefit =
from your approach. Are there mobility methods anywhere else that might =
assume static IIDs though?

Tim

On 22 May 2013, at 05:17, Fernando Gont <fgont@si6networks.com> wrote:

> On 05/21/2013 10:34 PM, Dave Thaler wrote:
>>>=20
>>> This issue was debated more than a year ago, at the IETF Paris =
timeframe.
>>> Since then, the wg adopted this document, and we went through WGLC =
and
>>> IETF LC. So I'm not sure how it helps to raise this point again and =
at this point
>>> in time.
>>=20
>> The problem is that the draft does not contain any understandable=20
>> justification, and does not explain the threat model it's trying to =
address
>> in a way that's sufficient for readers like me to understand.  So =
regardless of
>> whether or not the WG has consensus, the document is lacking in any =
case.
>=20
> I'm always open for improvements. I personally believe that the =
current
> version of the I-D is clear enough in that respect. In any case, since
> you consider there's room for improvement, hopefully this email =
exchange
> will either clarify things a bit and/or lead to improvements.
>=20
>=20
>=20
>>> 2) They employ constant identifiers, which allow host-tracking.
>>=20
>> By design.  Host tracking is already allowed with constant =
higher-layer identifiers,
>> e.g., DNS names, etc.
>=20
> You are assuming those identifiers are there. But they needn't.
>=20
>=20
>=20
>> So having constant addresses associated with=20
>> constant higher-layer identifiers is not any different.  And having =
non-constant=20
>> address associated with them does not provide any value add.
>=20
> I'm not sure why you bring this "higher-layer identifiers". The attack
> vector I mentioned (actively polling possible addresses as opposed to
> passively looking at IIDs still works pretty well without any sort of
> higher-layer IID).
>=20
>=20
>=20
>>> I'll focus on "2)", since it seems that you agree with "1)" being a =
problem that
>>> remains to be solved.
>>=20
>> Actually it's been solved (and widely deployed) since over a decade =
ago.  It
>> remains to be *standardized*, which is the part I agree with.
>=20
> I disagree it has been solved -- the only thing you've solved is
> address-scanning.
>=20
>=20
>=20
>>> ---- cut here ----
>>> The address-scanning problem can be mitigated by using randomly-
>>> generated suffixes for all addresses, whether they are =
public/persistent or
>>> temporary. These addresses can still be used for tracking, but they =
remove
>>> the OUI-associated vulnerability and make address scanning for IPv6
>>> addresses no easier than for IPv4 addresses.
>>> Windows uses random suffixes for all addresses, but many other
>>> implementations do not.
>>> ---- cut here ----
>>>=20
>>> This should make it evident that the scheme implemented by Windows =
fixes
>>> the address-scanning problem, but is still flawed when it comes to =
privacy.
>>=20
>> Your conclusion doesn't make sense.   The text is explaining that =
there are
>> two issues.  Address scanning is mitigated by random suffixes.  =
Tracking
>> is mitigated by using temporary addresses (that change over time and =
location).
>> Windows does both, so is not "flawed" as you incorrectly conclude.
>=20
> You don't mitigate tracking as long as you still keep some address =
with
> constant IDs. The only thing that you "mitigate" with RFC 4941 is that
> with RFC 4941 in place, the attacker can no longer "passively" track
> you, but rather has to send some packet to cause you to use the =
address
> that will leak your identity. -- Just firing a packet that will elicit =
a
> response from that address is enough.
>=20
>=20
>=20
>>> We have even implemented a tool to track nodes that employ constant =
IIDs
>>> (whether derived from IEEE-identifiers, or the approach implemented =
by
>>> Windows). The tool is scan6, availble as part of the IS6 toolkit at:
>>> <http://www.si6networks.com/tools/ipv6toolkit>). The man page for =
the
>>> tool contains examples of how to use the tool for such purpose.
>>=20
>> The key question is "employ" for what?  For example, if "employ for =
registering in
>> DNS" then I assure you I don't need your tool to track that...
>> If "employ for making outbound TCP connections", then temporary =
addresses=20
>> (not constant IIDs) are used for that, so again it doesn't apply.
>> So please elaborate on what you meant.
>=20
> Let's say that your stable IID is 1111:2222:3333:4444:5555, and that,
> for the sake of simplicity, the world consists of four networks:
> 2001:db8:1::/64, 2001:db8:2::/64, 2001:db8:3::/64, and =
2001:db8:4::/64.
>=20
> It thus becomes trivial to track you. Just periodically fire probe
> packets to 2001:db8:1::1111:2222:3333:4444:5555,
> 2001:db8:2::1111:2222:3333:4444 (and so on), and the address that
> responds leaks your location.
>=20
>=20
>=20
>>> On 05/20/2013 04:56 PM, Dave Thaler wrote:
>>>> I will concentrate on sections 1, 2, and Appendix B, being the
>>>> motivation/goals/justification, as opposed to the technical =
details.
>>>>=20
>>>> Let's start with B.1.1, which attempts to motivate a desire to =
prevent
>>>> tracking hosts across networks using their public
>>>> address(es):
>>>=20
>>> [FWIW, the motivation is in the Intro, rather than the Appendix.
>>> Appendix B simply rovides a clarification regarding issues not fixed =
with
>>> RFC4941... and not that long ago even included a statemet such as =
"this will
>>> be removed prior to publication of this document as an RFC"]
>>=20
>> I couldn't understand any motivation that made sense to me=20
>> for changing the IID of a *public* address or a *link-local* address, =
when
>> moving.
>> (I of course understand motivation for preventing address scans.)
>=20
> I couldn't understand any motivation for keeping them constant. And =
past
> experience with virtually every ID you can think of indicates that, =
the
> less predictable/constant such IDs are, the better.
>=20
>=20
>>>> The above text convolutes two orthogonal issues: higher-layer ID
>>>> (username in this case) and location.  The higher-layer ID in other
>>>> apps would be the DNS name, but here the text uses the username,
>>>> though even in P2P applications the higher-layer ID used to resolve =
an
>>>> application or piece of content would already be stable, and the
>>>> question is what you can link it to.
>>>=20
>>> The point this para is trying to make is that even if the user is =
employing a
>>> different username in the hopes of hiding its identity, the constant =
IID would
>>> reveal the identity of the device. (Put another way, the text =
regarding the
>>> username could even be considered "superflous" in this case).
>>=20
>> Remove superfluous text that confuses the issue.=20
>=20
> Agreed. Will fix this.
>=20
>=20
>> My point remains about
>> either there's a higher-layer ID that's constant (in which case =
changing the
>> IID is not helpful) or there's not (in which case the app should be =
using
>> temporary addresses not stable addresses).  =20
>=20
> As noted above, the app can use any address it wants. But since the
> stable address is still there, and attacker can cause the node to use
> that stable address by simpl directing a packet to it.
>=20
>=20
>=20
>> The text provides no clue
>> as to why an app would opt into stable addresses and then be =
concerned
>> about privacy, which makes no sense to me.
>=20
> All the above said the main benefit that temporary addresses buy you =
is
> trying to mitigate correlation of node activities within the same
> network (which, at times, is not possible no matter whether your
> addresses are temporary of not). In those cases where temporary
> addressess are deemed to be unacceptable (from an ops perspective),
> draft-ietf-6man-stable-privacy-addreses can result in an acceptable
> tradeoff.
>=20
>=20
>=20
>>=20
>>>> Furthermore, this notion of unlinkability is that privacy addresses
>>>> were designed for. The first paragraph in B.1.1 implies that one =
would
>>>> not want to use privacy addresses in a P2P scenario, and then goes =
on
>>>> to talk about why you lose privacy.
>>>=20
>>> No. It actually argues that RFC 4941 didn't get rid of constant =
IIDs.
>>=20
>> RFC 4941 never intended to get rid of constant IIDs, which would only =
make sense
>> if you got rid of constant higher-layer IDs like DNS names.  But this =
is the real world
>> where such higher-layer IDs are used all the time.
>=20
> Such higher-layer IDs are not required for all apps.. And employing
> constant IIDs hurts the privacy of nodes that are not using using such
> higher-layer IDs.
>=20
>=20
>=20
>>> Hence you're still subject of active probing.
>>>=20
>>> Trivial example:
>>>=20
>>> I attend an IETF meeting, and learn the IID of your laptop. Then I =
can actively
>>> probe your node regarding "Is David at the office?" "Is David at =
home?",
>>> etc.... simply because your IID is known and constant.
>>=20
>> Since you're making this personal...=20
>=20
> It wasn't meant to.
>=20
>=20
>> please explain how you can probe whether=20
>> I'm at the office or at home, both of which are behind firewalls (so =
won't respond
>> to arbitrary probes) and have address prefixes you don't know to =
begin with.
>=20
> The fact that you clarify "Note: I'm behind a firewall" is pretty much
> an implicit acknowledgement that the scheme you're using is flawed.
>=20
> (With that logic, you can use any flawed scheme as long as you keep =
your
> node unplugged from the net.)
>=20
> You don't need any firewall to mitigate this attack vector if you
> implement draft-ietf-6man-stable-privacy-addresses rather than the
> scheme currently implemented by Windows.
>=20
>=20
>=20
>> Furthermore, how do you know I don't publish my addresses in a =
well-known
>> DNS name and hence want my node's location to be public?
>> (More generally, replace DNS name with any constant higher-layer ID.)
>=20
> Well, the challenge is in tracking nodes that we assume that do not =
want
> to be tracked....
>=20
>=20
>=20
>>>> But I see no justification for having public addresses (linkable =
from
>>>> DNS names, etc.) that vary by network location.   Nor do I see any
>>>> justification for having link-local addresses (linkable to MAC
>>>> addresses via ND) that vary by network location.
>>>=20
>>> Actually, the analysis is: "I see no justification for employing an =
IID that is
>>> constant across networks,=20
>>=20
>> I provided you one in this thread, which you seem to have missed, so =
I'll
>> repeat it again.   If you have a constant higher-layer ID, such as a =
DNS name
>> that you keep up to date with your current public address, there's no =
value
>> in having an IID that varies by network.=20
>=20
> The onus is on you for wanting to keep them constant, rather than on =
me
> for being proactive (and avoiding the kind of IDs that lead to flaws =
in
> so many other protocols).
>=20
>=20
>=20
>> It only adds extra complexity without
>> real value.   So the justification is "it works, it's widely =
deployed, and there's
>> no reason to change it in this particular case".
>=20
> Sound pretty much sound like "It works -- as long as nobody wants to
> exploit it --.. but our customers bought it anyway... so why should we
> don't care?" to me.
>=20
> That said, draft-ietf-6amn-stable-privacy-addresses doesn't obsolete =
the
> traditional SLAAC IIDs, nor your non-standard approach... So you're =
free
> to keep your stack "as is". In the same way that those who care about =
an
> improved scheme, can implement it. It's a win-win situation, you might
> say. :-)
>=20
> FWIW, I know of at least three OSes that plan to implement
> draft-ietf-6man-stableprivacy-addresses.
>=20
> Thanks,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From wwwrun@rfc-editor.org  Wed May 22 20:52:27 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9488411E8153 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 20:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.368
X-Spam-Level: 
X-Spam-Status: No, score=-102.368 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WxkKgWjxU9DG for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 20:52:26 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id AD00A11E8145 for <ipv6@ietf.org>; Wed, 22 May 2013 20:52:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B24A6210A; Wed, 22 May 2013 20:51:51 -0700 (PDT)
To: brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com, brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6874 (3630)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130523035151.7B24A6210A@rfc-editor.org>
Date: Wed, 22 May 2013 20:51:51 -0700 (PDT)
Cc: ipv6@ietf.org, msweet@apple.com, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 03:52:27 -0000

The following errata report has been submitted for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630

--------------------------------------
Type: Technical
Reported by: Michael Sweet <msweet@apple.com>

Section: 3

Original Text
-------------
   Such bare "%" signs are for user interface convenience, and need to
   be turned into properly encoded characters (where "%25" encodes "%")
   before the URI is used in any protocol or HTML document.  However,
   URIs including a ZoneID have no meaning outside the originating node.
   It would therefore be highly desirable for a browser to remove the
   ZoneID from a URI before including that URI in an HTTP request.

Corrected Text
--------------
   Such bare "%" signs are for user interface convenience, and need to
   be turned into properly encoded characters (where "%25" encodes "%")
   before the URI is used in any protocol or HTML document.  HTTP Clients
   MUST include a ZoneID in any URIs provided in an HTTP request since
   HTTP Servers will need it when generating URIs, otherwise the IPv6
   address will not be routable.

Notes
-----
The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From wwwrun@rfc-editor.org  Wed May 22 21:00:22 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1345E11E810D for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 21:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.385
X-Spam-Level: 
X-Spam-Status: No, score=-102.385 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYODGw1YXXXK for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 21:00:21 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 747E821F8EBC for <ipv6@ietf.org>; Wed, 22 May 2013 21:00:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3CAB96210A; Wed, 22 May 2013 20:59:36 -0700 (PDT)
To: brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com, brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6874 (3631)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130523035941.3CAB96210A@rfc-editor.org>
Date: Wed, 22 May 2013 20:59:36 -0700 (PDT)
Cc: ipv6@ietf.org, msweet@apple.com, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 04:00:22 -0000

The following errata report has been submitted for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3631

--------------------------------------
Type: Technical
Reported by: Michael Sweet <msweet@apple.com>

Section: 4

Original Text
-------------
   An HTTP client, proxy, or other intermediary MUST remove any ZoneID
   attached to an outgoing URI, as it has only local significance at the
   sending host.


Corrected Text
--------------
   An HTTP client, proxy, or other intermediary MUST retain any ZoneID
   attached to an outgoing URI, as it will be the only way for an HTTP server
   to return a URI containing a link-local address that can subsequently be
   used by the HTTP client.


Notes
-----
The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From brian.e.carpenter@gmail.com  Wed May 22 22:26:55 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C710021F9289 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 22:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.719
X-Spam-Level: 
X-Spam-Status: No, score=-102.719 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1kgbGlJdAsTW for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 22:26:51 -0700 (PDT)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id 21ADC21F9285 for <ipv6@ietf.org>; Wed, 22 May 2013 22:26:51 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y11so2499721pdj.14 for <ipv6@ietf.org>; Wed, 22 May 2013 22:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HfDSWkYznVpVeUygTuyLirAcVbGzGfOrthqeudTVdyU=; b=0Z3Sp0yOT+rIq+FMtoFPCvE60UOE2PUXQ1ok7wnuq4MUXAntRZgL5QPb5lS/KH8gDZ ar0GGMUQjwgmQmFlDiCCRMFwAkmWy+BWsma6CfosajOIXku449gqh0aFKyPGl6zFB/Gl 7d0W5w9nd3ZVv/WF/7dusdGffn2b2OxNB/v9Zc4+jS/HjgLHaDLvbWMyfTGdxlC/OmXX 9NpDsmT6usYg0k4ihoCdW+dXVqKhsvPyheKQFzrH/CjsJ4WMhzrnnDaNn4fCuLkugB0o Oeg7T7WBbzpLrsqW3MIHJAfwuDZiWtFNFJ0gKUv6oUll16z2mmKtYNV2ykaYkn+dskan cuVg==
X-Received: by 10.68.201.5 with SMTP id jw5mr11241231pbc.40.1369286810831; Wed, 22 May 2013 22:26:50 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id fr1sm10225355pbb.26.2013.05.22.22.26.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 May 2013 22:26:49 -0700 (PDT)
Message-ID: <519DA89C.5070704@gmail.com>
Date: Thu, 23 May 2013 17:26:52 +1200
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: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org>
In-Reply-To: <20130523035151.7B24A6210A@rfc-editor.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: brian@innovationslab.net, ipv6@ietf.org, bob.hinden@gmail.com, msweet@apple.com, ted.lemon@nominum.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 05:26:55 -0000

As far as I can tell this is completely incorrect and the RFC is
completely correct. It's so wrong that I can't even see how to
explain it. By definition, a ZoneID has no meaning outside the
host; its only effect is to direct the packet to the desired
interface on that host. It has absolutely nothing to do
with routing on the network.

Regards
   Brian Carpenter


On 23/05/2013 15:51, RFC Errata System wrote:
> The following errata report has been submitted for RFC6874,
> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
> 
> --------------------------------------
> Type: Technical
> Reported by: Michael Sweet <msweet@apple.com>
> 
> Section: 3
> 
> Original Text
> -------------
>    Such bare "%" signs are for user interface convenience, and need to
>    be turned into properly encoded characters (where "%25" encodes "%")
>    before the URI is used in any protocol or HTML document.  However,
>    URIs including a ZoneID have no meaning outside the originating node.
>    It would therefore be highly desirable for a browser to remove the
>    ZoneID from a URI before including that URI in an HTTP request.
> 
> Corrected Text
> --------------
>    Such bare "%" signs are for user interface convenience, and need to
>    be turned into properly encoded characters (where "%25" encodes "%")
>    before the URI is used in any protocol or HTML document.  HTTP Clients
>    MUST include a ZoneID in any URIs provided in an HTTP request since
>    HTTP Servers will need it when generating URIs, otherwise the IPv6
>    address will not be routable.
> 
> Notes
> -----
> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6874 (draft-ietf-6man-uri-zoneid-06)
> --------------------------------------
> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
> Publication Date    : February 2013
> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
> Category            : PROPOSED STANDARD
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
> 

From brian.e.carpenter@gmail.com  Wed May 22 22:28:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346FA21F928C for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 22:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vjfDPzmWDH1 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 22:27:59 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0E55221F92A5 for <ipv6@ietf.org>; Wed, 22 May 2013 22:27:55 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so2371432pdj.1 for <ipv6@ietf.org>; Wed, 22 May 2013 22:27:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KRF0XtRdupOO3CfBSTBBkMYDlBT0DpvyBHmCV3DP/Ow=; b=CC99HU1JEpTZq2iQcWlbaarj4GNqPLeizwpMc6RxUqhfx+o+UvYsAJPCfOjaM2gyN7 uAQmS8JjxAjWRU7ZZVJZq/CP3s0Dr45miWzbSFplxQzwSj7hwuB+uEl2XnwmJ8Q+KiYF nT9d1yDh+Bqvvem9zUo+BXdJHVFVMZdBSCksSQcmFZQD6qbd6CdU9+0Hs09rHektTnT2 Mb84dzkgVnERnak3ymuDwJRCJn++Agw+gM4ts0ODB0qnejdZ5OB0Zyy+FEsA9peUxkRM yNYAWd8e2uqIW7C+MRRGxdtOl5f0NDpkBckxWsQZko7m7hWsToyvvSjCfoZRqF1Lij23 WinQ==
X-Received: by 10.66.88.38 with SMTP id bd6mr11901807pab.184.1369286874811; Wed, 22 May 2013 22:27:54 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id wi6sm10235129pbc.22.2013.05.22.22.27.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 May 2013 22:27:53 -0700 (PDT)
Message-ID: <519DA8DC.4000204@gmail.com>
Date: Thu, 23 May 2013 17:27:56 +1200
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: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3631)
References: <20130523035941.3CAB96210A@rfc-editor.org>
In-Reply-To: <20130523035941.3CAB96210A@rfc-editor.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: brian@innovationslab.net, ipv6@ietf.org, bob.hinden@gmail.com, msweet@apple.com, ted.lemon@nominum.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 05:28:04 -0000

Again, completely wrong for the same reason that Erratum 3630 is wrong.

Regards
   Brian Carpenter

On 23/05/2013 15:59, RFC Errata System wrote:
> The following errata report has been submitted for RFC6874,
> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3631
> 
> --------------------------------------
> Type: Technical
> Reported by: Michael Sweet <msweet@apple.com>
> 
> Section: 4
> 
> Original Text
> -------------
>    An HTTP client, proxy, or other intermediary MUST remove any ZoneID
>    attached to an outgoing URI, as it has only local significance at the
>    sending host.
> 
> 
> Corrected Text
> --------------
>    An HTTP client, proxy, or other intermediary MUST retain any ZoneID
>    attached to an outgoing URI, as it will be the only way for an HTTP server
>    to return a URI containing a link-local address that can subsequently be
>    used by the HTTP client.
> 
> 
> Notes
> -----
> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
> 
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC6874 (draft-ietf-6man-uri-zoneid-06)
> --------------------------------------
> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
> Publication Date    : February 2013
> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
> Category            : PROPOSED STANDARD
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
> 

From msweet@apple.com  Wed May 22 23:10:25 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E14621F96C1 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxkD2Et-Y95T for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:10:20 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0481521F9616 for <ipv6@ietf.org>; Wed, 22 May 2013 23:10:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay4.apple.com ([17.128.113.87]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN8007ECMG4FNL1@mail-out.apple.com> for ipv6@ietf.org; Wed, 22 May 2013 23:10:06 -0700 (PDT)
X-AuditID: 11807157-b7f706d0000006c6-33-519db2bd0c16
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay4.apple.com (Apple SCV relay) with SMTP id 88.74.01734.DB2BD915; Wed, 22 May 2013 23:10:06 -0700 (PDT)
Received: from [10.0.1.102] (208-96-65-222.eastlink.ca [208.96.65.222]) by jimbu.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MN800HZ4MGSV760@jimbu.apple.com> for ipv6@ietf.org; Wed, 22 May 2013 23:10:05 -0700 (PDT)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com>
In-reply-to: <519DA89C.5070704@gmail.com>
Message-id: <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com>
X-Mailer: iPad Mail (10B329)
From: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
Date: Thu, 23 May 2013 02:10:05 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUiON1OVXffprmBBltrLF6efc/kwOixZMlP pgDGKC6blNSczLLUIn27BK6M209bWQuWyFZ8m7CHvYGxXbyLkZNDQsBEYtbFr8wQtpjEhXvr 2boYuTiEBBqYJN7/3ccE4Sxnklg8r4EVpEpIIFSib8YxNhCbV0Bc4vXRKYwgNqeApsTE5+vA bGYBLYn1O48zQdjaEk/eXWCFqLeRmPO2gxVkKLPAWSaJo1NmMkGslpHYvP0xO4jNJqAm8XtS H1iDsIC5xNzHn8GGsgioSvyb9hOsXkTAWKKx6zTrBEaBWUjumIVk9ywkuxcwMq9iFChKzUms NNFLLCjISdVLzs/dxAgKvYbC8B2M/5ZZHWIU4GBU4uGVuD0nUIg1say4MvcQowQHs5II7+ae uYFCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeX/OnRUoJJCeWJKanZpakFoEk2Xi4JRqYOzlWhxm 7Jl4f1u9vcnJD1x6ixIPTFl4Vcdwxar2y3v+2L0rPH57s92Nza0dJ+0fSdgyNxbeyJC/War2 b7n2visuh+8I1q7+W+VuXvYoKmC/U16a76RHF50X5Ezmnse86fzzV1mhoTcacziOr9LlnHp0 +oF7W4V8ZX8ofjyX2WxbXenfkMkUJa3EUpyRaKjFXFScCAABi08pOQIAAA==
X-Mailman-Approved-At: Wed, 22 May 2013 23:16:53 -0700
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 06:10:25 -0000

Brian,

What you're apparently missing is that the client is using the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care but the client depends on it (for link local anyways).

This issue is specifically why we (the Printer Working Group) require IPP Clients to include the zoneid in the HTTP Host header and require IPP Servers to use the Host value in any generated URIs.



Sent from my iPad

On 2013-05-23, at 1:26 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> As far as I can tell this is completely incorrect and the RFC is
> completely correct. It's so wrong that I can't even see how to
> explain it. By definition, a ZoneID has no meaning outside the
> host; its only effect is to direct the packet to the desired
> interface on that host. It has absolutely nothing to do
> with routing on the network.
> 
> Regards
>   Brian Carpenter
> 
> 
> On 23/05/2013 15:51, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6874,
>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Michael Sweet <msweet@apple.com>
>> 
>> Section: 3
>> 
>> Original Text
>> -------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  However,
>>   URIs including a ZoneID have no meaning outside the originating node.
>>   It would therefore be highly desirable for a browser to remove the
>>   ZoneID from a URI before including that URI in an HTTP request.
>> 
>> Corrected Text
>> --------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  HTTP Clients
>>   MUST include a ZoneID in any URIs provided in an HTTP request since
>>   HTTP Servers will need it when generating URIs, otherwise the IPv6
>>   address will not be routable.
>> 
>> Notes
>> -----
>> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
>> 
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary. 
>> 
>> --------------------------------------
>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>> --------------------------------------
>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>> Publication Date    : February 2013
>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG
>> 

From msweet@apple.com  Wed May 22 23:10:29 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C879321F9616 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eq+kj0qjHMet for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:10:24 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 727F821F96BE for <ipv6@ietf.org>; Wed, 22 May 2013 23:10:24 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay7.apple.com ([17.128.113.101]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN80090SMH8ZL50@mail-out.apple.com> for ipv6@ietf.org; Wed, 22 May 2013 23:10:24 -0700 (PDT)
X-AuditID: 11807165-b7f496d000000613-8a-519db2d0e481
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay7.apple.com (Apple SCV relay) with SMTP id C5.F7.01555.0D2BD915; Wed, 22 May 2013 23:10:24 -0700 (PDT)
Received: from [10.0.1.102] (208-96-65-222.eastlink.ca [208.96.65.222]) by jimbu.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MN800HZ4MGSV760@jimbu.apple.com> for ipv6@ietf.org; Wed, 22 May 2013 23:10:24 -0700 (PDT)
References: <20130523035941.3CAB96210A@rfc-editor.org> <519DA8DC.4000204@gmail.com>
In-reply-to: <519DA8DC.4000204@gmail.com>
Message-id: <321929FB-F82A-4388-8FB3-2DCCC2E0EF9D@apple.com>
X-Mailer: iPad Mail (10B329)
From: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3631)
Date: Thu, 23 May 2013 02:10:25 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOLMWRmVeSWpSXmKPExsUiON1OVffCprmBBl3NfBYvz75ncmD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRtPKPqaCb0IVV1qWsDQwvuXrYuTkkBAwkbi8YzYzhC0mceHe erYuRi4OIYEGJokv/UuYIZzlTBIvZi1lAakSEgiV2Lr2KROIzSsgLvH66BRGEJtTQFOi4cBt sDizgJbE+p3HoWxtiSfvLrBC1NtIHNnTxwoylFngLJPE0SkzmSBWy0hs3v6YHcRmE1CT+D2p D6xBWMBc4sbHN2A1LAKqEove7AE7QkTAWKKx6zTrBEaBWUjumIVk9ywkuxcwMq9iFChKzUms NNdLLCjISdVLzs/dxAgKvobC1B2MjcutDjEKcDAq8fAeuDEnUIg1say4MvcQowQHs5II7+ae uYFCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeX/PnRUoJJCeWJKanZpakFoEk2Xi4JRqYORh27xe /ZTijPZntT3CoT57Xjx4u4K7fM9+idoH/5Xua4dedbHhv571a/4O500vkkIOpshellE5qfz9 /t3vB7ifvRdborRQeynnv1ZdOSOFi1ouqSFn76kmbf9cuOuXWXVUlZnnkkQ2v5J1EQdnTPbI qGb6c6jZd1/4rB3OnBcrwgUWJf8IWKfEUpyRaKjFXFScCADoAGzaOgIAAA==
X-Mailman-Approved-At: Wed, 22 May 2013 23:16:53 -0700
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 06:10:29 -0000

See my previous response.

Sent from my iPad

On 2013-05-23, at 1:27 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> Again, completely wrong for the same reason that Erratum 3630 is wrong.
> 
> Regards
>   Brian Carpenter
> 
> On 23/05/2013 15:59, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6874,
>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3631
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Michael Sweet <msweet@apple.com>
>> 
>> Section: 4
>> 
>> Original Text
>> -------------
>>   An HTTP client, proxy, or other intermediary MUST remove any ZoneID
>>   attached to an outgoing URI, as it has only local significance at the
>>   sending host.
>> 
>> 
>> Corrected Text
>> --------------
>>   An HTTP client, proxy, or other intermediary MUST retain any ZoneID
>>   attached to an outgoing URI, as it will be the only way for an HTTP server
>>   to return a URI containing a link-local address that can subsequently be
>>   used by the HTTP client.
>> 
>> 
>> Notes
>> -----
>> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
>> 
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary. 
>> 
>> --------------------------------------
>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>> --------------------------------------
>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>> Publication Date    : February 2013
>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG
>> 

From swmike@swm.pp.se  Wed May 22 23:26:32 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2311721F96C8 for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:26:32 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bt8gN7ZUaGmW for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:26:31 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 5F97721F96A0 for <ipv6@ietf.org>; Wed, 22 May 2013 23:26:31 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6BFF89C; Thu, 23 May 2013 08:26:29 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 602449A; Thu, 23 May 2013 08:26:29 +0200 (CEST)
Date: Thu, 23 May 2013 08:26:29 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com>
Message-ID: <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.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: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 06:26:32 -0000

On Thu, 23 May 2013, Michael Sweet wrote:

> Brian,
>
> What you're apparently missing is that the client is using the zoneid to 
> choose a network interface to route packets to that link local address. 
> If the server returns a uri in its response that uses the same link 
> local address but without the client's zoneid, then the client will be 
> unable to use said uri because it won't know which interface to use. Yes 
> the server doesn't care but the client depends on it (for link local 
> anyways).

How would the server know the clients zoneid? It derives this from the 
initial request?

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

From huitema@microsoft.com  Wed May 22 23:51:43 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8877421F96DB for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:51:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OqZkyUTSP1J for <ipv6@ietfa.amsl.com>; Wed, 22 May 2013 23:51:38 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0235.outbound.protection.outlook.com [207.46.163.235]) by ietfa.amsl.com (Postfix) with ESMTP id 7E97D21F96D8 for <ipv6@ietf.org>; Wed, 22 May 2013 23:51:38 -0700 (PDT)
Received: from BL2FFO11FD026.protection.gbl (10.173.161.201) by BL2FFO11HUB024.protection.gbl (10.173.161.48) with Microsoft SMTP Server (TLS) id 15.0.698.0; Thu, 23 May 2013 06:47:19 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD026.mail.protection.outlook.com (10.173.161.105) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Thu, 23 May 2013 06:47:19 +0000
Received: from TK5EX14MBXC274.redmond.corp.microsoft.com ([169.254.3.26]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.02.0318.003; Thu, 23 May 2013 06:47:14 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Michael Sweet <msweet@apple.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: [Technical Errata Reported] RFC6874 (3630)
Thread-Topic: [Technical Errata Reported] RFC6874 (3630)
Thread-Index: AQHOV2lfBWe4Nw564U2vCg0gl6fTYpkSPXAAgAAME4CAAAnUUA==
Date: Thu, 23 May 2013 06:47:14 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com>
In-Reply-To: <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.35]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(479174002)(13464003)(377454002)(377424003)(24454002)(51704005)(66066001)(6806003)(15202345002)(16799955001)(15188155003)(31966008)(53806001)(33656001)(80022001)(74706001)(46406003)(50466002)(23726002)(79102001)(74876001)(65816001)(77982001)(74366001)(16406001)(59766001)(4396001)(49866001)(20776003)(54356001)(74662001)(74502001)(50986001)(47446002)(69226001)(63696002)(54316002)(81342001)(56776001)(47776003)(76482001)(47976001)(56816002)(47736001)(55846006)(81542001)(51856001)(44976003)(46102001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB024; H:TK5EX14MLTC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085551F5A8
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 06:51:43 -0000

Michael, you are asking that the consensus of the WG be reversed. The errat=
a process is not the way to handle this. You have to go through the motions=
: write a draft, submit it, get consensus...

-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Mic=
hael Sweet
Sent: Wednesday, May 22, 2013 11:10 PM
To: Brian E Carpenter
Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com; ted.lemo=
n@nominum.com; RFC Errata System
Subject: Re: [Technical Errata Reported] RFC6874 (3630)

Brian,

What you're apparently missing is that the client is using the zoneid to ch=
oose a network interface to route packets to that link local address. If th=
e server returns a uri in its response that uses the same link local addres=
s but without the client's zoneid, then the client will be unable to use sa=
id uri because it won't know which interface to use. Yes the server doesn't=
 care but the client depends on it (for link local anyways).

This issue is specifically why we (the Printer Working Group) require IPP C=
lients to include the zoneid in the HTTP Host header and require IPP Server=
s to use the Host value in any generated URIs.



Sent from my iPad

On 2013-05-23, at 1:26 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> =
wrote:

> As far as I can tell this is completely incorrect and the RFC is=20
> completely correct. It's so wrong that I can't even see how to explain=20
> it. By definition, a ZoneID has no meaning outside the host; its only=20
> effect is to direct the packet to the desired interface on that host.=20
> It has absolutely nothing to do with routing on the network.
>=20
> Regards
>   Brian Carpenter
>=20
>=20
> On 23/05/2013 15:51, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6874,=20
>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Reso=
urce Identifiers".
>>=20
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=3D6874&eid=3D3630
>>=20
>> --------------------------------------
>> Type: Technical
>> Reported by: Michael Sweet <msweet@apple.com>
>>=20
>> Section: 3
>>=20
>> Original Text
>> -------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  However,
>>   URIs including a ZoneID have no meaning outside the originating node.
>>   It would therefore be highly desirable for a browser to remove the
>>   ZoneID from a URI before including that URI in an HTTP request.
>>=20
>> Corrected Text
>> --------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  HTTP Clients
>>   MUST include a ZoneID in any URIs provided in an HTTP request since
>>   HTTP Servers will need it when generating URIs, otherwise the IPv6
>>   address will not be routable.
>>=20
>> Notes
>> -----
>> The original advice ignores a very real issue: HTTP Servers that generat=
e URIs from the client's Host: need to include the Client's zoneid in order=
 for the link local address to be usable/routable.
>>=20
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please=20
>> use "Reply All" to discuss whether it should be verified or rejected.=20
>> When a decision is reached, the verifying party (IESG) can log in to=20
>> change the status and edit the report, if necessary.
>>=20
>> --------------------------------------
>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>> --------------------------------------
>> Title               : Representing IPv6 Zone Identifiers in Address Lite=
rals and Uniform Resource Identifiers
>> Publication Date    : February 2013
>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG
>>=20
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

From internet-drafts@ietf.org  Thu May 23 01:02:27 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5553F21F9725; Thu, 23 May 2013 01:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKevuSII+8zF; Thu, 23 May 2013 01:02:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E67F421F93BF; Thu, 23 May 2013 01:02:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-multicast-addr-arch-update-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130523080226.25842.83947.idtracker@ietfa.amsl.com>
Date: Thu, 23 May 2013 01:02:26 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 08:02:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : Updates to the IPv6 Multicast Addressing Architecture
	Author(s)       : Mohamed Boucadair
                          Stig Venaas
	Filename        : draft-ietf-6man-multicast-addr-arch-update-01.txt
	Pages           : 10
	Date            : 2013-05-23

Abstract:
   This document updates the IPv6 multicast addressing architecture by
   defining the 17-20 reserved bits as generic flag bits.  The document
   provides also some clarifications related to the use of these flag
   bits.

   This document updates RFC 3956, RFC 3306, RFC 4607 and RFC 4291.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multicast-addr-arch-update

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-multicast-addr-arch-upda=
te-01


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


From mohamed.boucadair@orange.com  Thu May 23 01:17:01 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A648221F8FB3 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 01:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bVW2cmXvwx2 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 01:16:51 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id D3D8921F9060 for <ipv6@ietf.org>; Thu, 23 May 2013 01:16:26 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id C975722CD7D for <ipv6@ietf.org>; Thu, 23 May 2013 10:16:18 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id A76B227C06A for <ipv6@ietf.org>; Thu, 23 May 2013 10:16:18 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Thu, 23 May 2013 10:16:18 +0200
From: <mohamed.boucadair@orange.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Date: Thu, 23 May 2013 10:16:17 +0200
Subject: draft-ietf-6man-multicast-addr-arch-update: How to implement RFCs changes?
Thread-Topic: draft-ietf-6man-multicast-addr-arch-update: How to implement RFCs changes?
Thread-Index: Ac5Xjclm8D6IaijwSZajdqJAw0SrUA==
Message-ID: <94C682931C08B048B7A8645303FDC9F36ED1F52610@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.21.113319
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 08:17:01 -0000

Dear all,

We prepared a new version which lists the changes to be added to RFC 3956, =
RFC 3306 and RFC 4607:
http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01 =20

We are interested to hear your feedback on the proposed changes and also on=
 the better approach to actually do the changes.=20

We have considered two approaches:
(1) maintain all the changes in this document (i.e., it will update the add=
ress architecture + RFC 3956, RFC 3306 and RFC 4607)
(2) this document updates only the address architecture with the new flag +=
 edit bis documents which will update RFC 3956, RFC 3306 and RFC 4607.

What approach the WG want us to implement?=20
Comments are more than welcome.

Cheers,
Med


>-----Message d'origine-----
>De=A0: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] De la part de
>internet-drafts@ietf.org
>Envoy=E9=A0: jeudi 23 mai 2013 10:02
>=C0=A0: i-d-announce@ietf.org
>Cc=A0: ipv6@ietf.org
>Objet=A0: I-D Action: draft-ietf-6man-multicast-addr-arch-update-01.txt
>
>
>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           : Updates to the IPv6 Multicast Addressing
>Architecture
>	Author(s)       : Mohamed Boucadair
>                          Stig Venaas
>	Filename        : draft-ietf-6man-multicast-addr-arch-update-01.txt
>	Pages           : 10
>	Date            : 2013-05-23
>
>Abstract:
>   This document updates the IPv6 multicast addressing architecture by
>   defining the 17-20 reserved bits as generic flag bits.  The document
>   provides also some clarifications related to the use of these flag
>   bits.
>
>   This document updates RFC 3956, RFC 3306, RFC 4607 and RFC 4291.
>
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-6man-multicast-addr-arch-updat=
e
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-6man-multicast-addr-arch-update-01
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-multicast-addr-arch-
>update-01
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------

From Ted.Lemon@nominum.com  Thu May 23 06:42:22 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 106E421F9552 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 06:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id epPqrqwie9yP for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 06:42:15 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8B021F8E76 for <ipv6@ietf.org>; Thu, 23 May 2013 06:42:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ4ctrKzZRKa4dbkvSCqNhmn2pkjNx+a@postini.com; Thu, 23 May 2013 06:42:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9651D1B807E for <ipv6@ietf.org>; Thu, 23 May 2013 06:42:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 89BE619005D; Thu, 23 May 2013 06:42:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 23 May 2013 06:42:14 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
Thread-Topic: [Technical Errata Reported] RFC6874 (3630)
Thread-Index: AQHOV2jyoE5BESz8v0i6rHInlU3N/pkSsskAgAAME4CAAASVgIAAeOAAgAAA34A=
Date: Thu, 23 May 2013 13:42:13 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com>
In-Reply-To: <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AD239D5FFBB15D46B014C328D2C60B3F@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 13:42:22 -0000

I happen to agree that a change like this would be a good change, but I als=
o agree that it needs to be done as a consensus document, not as an erratum=
.   This is true not only for process reasons, but because I think the chan=
ge as proposed was too broad.   Is there a working group alive where this c=
ould get done?


From msweet@apple.com  Thu May 23 06:39:15 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E4A21F9428 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 06:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.298
X-Spam-Level: 
X-Spam-Status: No, score=-106.298 tagged_above=-999 required=5 tests=[AWL=3.701, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zk5pzff9OJnr for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 06:39:09 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7C821F9425 for <ipv6@ietf.org>; Thu, 23 May 2013 06:39:09 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay2.apple.com ([17.128.113.67]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN90091R798ZLJ1@mail-out.apple.com> for ipv6@ietf.org; Thu, 23 May 2013 06:39:08 -0700 (PDT)
X-AuditID: 11807143-b7f856d000000818-b6-519e1bfa90c4
Received: from [17.153.20.228] (Unknown_Domain [17.153.20.228]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay2.apple.com (Apple SCV relay) with SMTP id 97.D5.02072.BFB1E915; Thu, 23 May 2013 06:39:08 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se>
Date: Thu, 23 May 2013 09:39:06 -0400
Message-id: <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUiOFPkie4f6XmBBlvnK1lsfb+PzaLt4j4m i5k9/xgtXp59z2Rx5FusRdP+r2wWL5duZbPY2h3rwOGx9eQPNo+ds+6yeyxZ8pPJY+bxLywe rw/MZ/VoaDvG6vF30kOmAPYoLpuU1JzMstQifbsEroyG3fNYCt6LVTzcMoWtgXGtUBcjJ4eE gInE8V8fmSFsMYkL99azdTFycQgJ9DJJHNk9FSwhLGAuMffxZ0YQm1dAT+Lat6/sIDazgJbE jX8vmUBsNgE1id+T+lhBbE4BZ4mrj3rAbBYBVYnVJ1+zQtQvYZLovZYLYWtLLFv4mhlipo3E 4Qu7WSAW72aUWN77gAUkISKgKbFx+wY2iOtkJV4/f8MygZF/FpI7ZiG5YxaSuQsYmVcxChSl 5iRWGuklFhTkpOol5+duYgQFeEOh8w7GY8usDjEKcDAq8fAeuDEnUIg1say4MvcQowQHs5II 7+aeuYFCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeX/MnRUoJJCeWJKanZpakFoEk2Xi4JRqYFwt nx+9K6CM49fZM3Yty+NfflF53hC1KCc+y8X1xNPgubn87jMTOB02bvyxOXX7haQusbyySeW5 /HdvXJpz+EZg8asg6fgvx58mvLupGRyQZ9M145VdQwfDspBZLnN5FhxeW/m41n92AMumgKer lMs/BD1Ouik35UUGU2SVp92hBZyP1voLGSqxFGckGmoxFxUnAgBSThRobAIAAA==
X-Mailman-Approved-At: Thu, 23 May 2013 06:44:35 -0700
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 13:39:15 -0000

Mikael,

On 2013-05-23, at 2:26 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Thu, 23 May 2013, Michael Sweet wrote:
> 
>> Brian,
>> 
>> What you're apparently missing is that the client is using the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care but the client depends on it (for link local anyways).
> 
> How would the server know the clients zoneid? It derives this from the initial request?


Yes, in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):

    POST /ipp/print HTTP/1.1
    Host: [v1.fe80::1234+en0]:631
    Content-Type: application/ipp
    Transfer-Coding: chunked

    ... IPP request ...

The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.

The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...

Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.

The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From brian@innovationslab.net  Thu May 23 07:04:46 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440EE21F8E34 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id liO2VXwbGLyZ for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:04:40 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1A56C21F9497 for <ipv6@ietf.org>; Thu, 23 May 2013 07:04:40 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id EE13F8814F; Thu, 23 May 2013 07:04:39 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2F36514000C; Thu, 23 May 2013 07:04:39 -0700 (PDT)
Message-ID: <519E21F8.1040108@innovationslab.net>
Date: Thu, 23 May 2013 10:04:40 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com> <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, Michael Sweet <msweet@apple.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:04:46 -0000

On 5/23/13 9:42 AM, Ted Lemon wrote:
> I happen to agree that a change like this would be a good change, but I also agree that it needs to be done as a consensus document, not as an erratum.   This is true not only for process reasons, but because I think the change as proposed was too broad.   Is there a working group alive where this could get done?
>

6MAN.

From wwwrun@rfc-editor.org  Thu May 23 07:43:19 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC4D21F9684 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level: 
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGw5-i7XCLjs for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:43:18 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B63FC21F9029 for <ipv6@ietf.org>; Thu, 23 May 2013 07:43:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CC2C972F63F; Thu, 23 May 2013 07:42:35 -0700 (PDT)
To: brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com, brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6874 (3632)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130523144235.CC2C972F63F@rfc-editor.org>
Date: Thu, 23 May 2013 07:42:35 -0700 (PDT)
Cc: ipv6@ietf.org, msweet@apple.com, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:43:19 -0000

The following errata report has been submitted for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3632

--------------------------------------
Type: Technical
Reported by: Michael Sweet <msweet@apple.com>

Section: 3

Original Text
-------------
  Such bare "%" signs are for user interface convenience, and need to
  be turned into properly encoded characters (where "%25" encodes "%")
  before the URI is used in any protocol or HTML document.  However,
  URIs including a ZoneID have no meaning outside the originating node.
  It would therefore be highly desirable for a browser to remove the
  ZoneID from a URI before including that URI in an HTTP request.


Corrected Text
--------------
  Such bare "%" signs are for user interface convenience, and need to
  be turned into properly encoded characters (where "%25" encodes "%")
  before the URI is used in any protocol or HTML document.  HTTP Clients
  MUST include a ZoneID in any URIs provided in an HTTP request since
  HTTP Servers will need it when generating URIs, otherwise the IPv6
  address will not be usable by the Client.


Notes
-----
NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.

The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).

The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):

   POST /ipp/print HTTP/1.1
   Host: [v1.fe80::1234+en0]:631
   Content-Type: application/ipp
   Transfer-Coding: chunked

   ... IPP request ...

The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.

The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...

Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.

The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.

Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From brian@innovationslab.net  Thu May 23 07:43:27 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C2EE21F9691 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEdQDy5kbiky for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:43:22 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6688021F9690 for <ipv6@ietf.org>; Thu, 23 May 2013 07:43:22 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1F07A8814B; Thu, 23 May 2013 07:43:22 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 2F84214000C; Thu, 23 May 2013 07:43:21 -0700 (PDT)
Message-ID: <519E2B08.80201@innovationslab.net>
Date: Thu, 23 May 2013 10:43:20 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com>
In-Reply-To: <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, Christian Huitema <huitema@microsoft.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:43:27 -0000

Michael,
      I rejected the errata since they were both changing the consensus 
of a WG.  That level of change is not how the errata system is to be 
used.  Your approach of writing a new draft proposing these changes is 
the correct approach to changing that consensus.

Regards,
Brian

On 5/23/13 10:25 AM, Michael Sweet wrote:
> Christian,
>
> I'm happy to write up a new draft proposing my changes and go through that process. I'm not happy that my errata have been summarily rejected in less than 24 hours with no time for review.
>
> Consider: hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years.  It took those 8 years for the IETF to agree on a new format with serious compatibility and interoperability issues with the base IETF standard (STD 66 aka RFC 3986), and my errata against the published RFC have been rejected after less than 24 hours of discussion.
>
> How do we notify users of RFC 6874 that there are proposed changes, if not in pending errata?
>
> How long will it take to get a new draft approved that fixes the problems in RFC 6874? I certainly hope the answer is not 8 years...
>
>
> On 2013-05-23, at 2:47 AM, Christian Huitema <huitema@microsoft.com> wrote:
>
>> Michael, you are asking that the consensus of the WG be reversed. The errata process is not the way to handle this. You have to go through the motions: write a draft, submit it, get consensus...
>>
>> -----Original Message-----
>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Michael Sweet
>> Sent: Wednesday, May 22, 2013 11:10 PM
>> To: Brian E Carpenter
>> Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com; ted.lemon@nominum.com; RFC Errata System
>> Subject: Re: [Technical Errata Reported] RFC6874 (3630)
>>
>> Brian,
>>
>> What you're apparently missing is that the client is using the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care but the client depends on it (for link local anyways).
>>
>> This issue is specifically why we (the Printer Working Group) require IPP Clients to include the zoneid in the HTTP Host header and require IPP Servers to use the Host value in any generated URIs.
>>
>>
>>
>> Sent from my iPad
>>
>> On 2013-05-23, at 1:26 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>>> As far as I can tell this is completely incorrect and the RFC is
>>> completely correct. It's so wrong that I can't even see how to explain
>>> it. By definition, a ZoneID has no meaning outside the host; its only
>>> effect is to direct the packet to the desired interface on that host.
>>> It has absolutely nothing to do with routing on the network.
>>>
>>> Regards
>>>   Brian Carpenter
>>>
>>>
>>> On 23/05/2013 15:51, RFC Errata System wrote:
>>>> The following errata report has been submitted for RFC6874,
>>>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>>>>
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
>>>>
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Michael Sweet <msweet@apple.com>
>>>>
>>>> Section: 3
>>>>
>>>> Original Text
>>>> -------------
>>>>   Such bare "%" signs are for user interface convenience, and need to
>>>>   be turned into properly encoded characters (where "%25" encodes "%")
>>>>   before the URI is used in any protocol or HTML document.  However,
>>>>   URIs including a ZoneID have no meaning outside the originating node.
>>>>   It would therefore be highly desirable for a browser to remove the
>>>>   ZoneID from a URI before including that URI in an HTTP request.
>>>>
>>>> Corrected Text
>>>> --------------
>>>>   Such bare "%" signs are for user interface convenience, and need to
>>>>   be turned into properly encoded characters (where "%25" encodes "%")
>>>>   before the URI is used in any protocol or HTML document.  HTTP Clients
>>>>   MUST include a ZoneID in any URIs provided in an HTTP request since
>>>>   HTTP Servers will need it when generating URIs, otherwise the IPv6
>>>>   address will not be routable.
>>>>
>>>> Notes
>>>> -----
>>>> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
>>>>
>>>> Instructions:
>>>> -------------
>>>> This errata is currently posted as "Reported". If necessary, please
>>>> use "Reply All" to discuss whether it should be verified or rejected.
>>>> When a decision is reached, the verifying party (IESG) can log in to
>>>> change the status and edit the report, if necessary.
>>>>
>>>> --------------------------------------
>>>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>>>> --------------------------------------
>>>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>>>> Publication Date    : February 2013
>>>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>>>> Category            : PROPOSED STANDARD
>>>> Source              : IPv6 Maintenance
>>>> Area                : Internet
>>>> Stream              : IETF
>>>> Verifying Party     : IESG
>>>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>


From wwwrun@rfc-editor.org  Thu May 23 07:45:06 2013
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392C821F900C for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.969
X-Spam-Level: 
X-Spam-Status: No, score=-101.969 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, NO_RELAYS=-0.001, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjVy-eE5aJcg for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:45:05 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 382D421F8CEC for <ipv6@ietf.org>; Thu, 23 May 2013 07:45:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 581AE72F63F; Thu, 23 May 2013 07:44:25 -0700 (PDT)
To: brian.e.carpenter@gmail.com, cheshire@apple.com, bob.hinden@gmail.com, brian@innovationslab.net, ted.lemon@nominum.com, bob.hinden@gmail.com, otroan@employees.org
Subject: [Technical Errata Reported] RFC6874 (3633)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20130523144425.581AE72F63F@rfc-editor.org>
Date: Thu, 23 May 2013 07:44:25 -0700 (PDT)
Cc: ipv6@ietf.org, msweet@apple.com, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:45:06 -0000

The following errata report has been submitted for RFC6874,
"Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3633

--------------------------------------
Type: Technical
Reported by: Michael Sweet <msweet@apple.com>

Section: 4

Original Text
-------------
  An HTTP client, proxy, or other intermediary MUST remove any ZoneID
  attached to an outgoing URI, as it has only local significance at the
  sending host.


Corrected Text
--------------
  An HTTP client, proxy, or other intermediary MUST retain any ZoneID
  attached to an outgoing URI, as it will be the only way for an HTTP server
  to return a URI containing a link-local address that can subsequently be
  used by the HTTP client.


Notes
-----
NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.

The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).

The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):

   POST /ipp/print HTTP/1.1
   Host: [v1.fe80::1234+en0]:631
   Content-Type: application/ipp
   Transfer-Coding: chunked

   ... IPP request ...

The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.

The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...

Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.

The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.

Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6874 (draft-ietf-6man-uri-zoneid-06)
--------------------------------------
Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Publication Date    : February 2013
Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
Category            : PROPOSED STANDARD
Source              : IPv6 Maintenance
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From brian@innovationslab.net  Thu May 23 07:45:49 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8886121F93E8 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.043
X-Spam-Level: 
X-Spam-Status: No, score=-102.043 tagged_above=-999 required=5 tests=[AWL=-0.359, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bd2ANbCVMC7c for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:45:44 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE6621F8D70 for <ipv6@ietf.org>; Thu, 23 May 2013 07:45:44 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 5FBF78814B; Thu, 23 May 2013 07:45:44 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 67BF114000C; Thu, 23 May 2013 07:45:43 -0700 (PDT)
Message-ID: <519E2B96.40106@innovationslab.net>
Date: Thu, 23 May 2013 10:45:42 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3632)
References: <20130523144235.CC2C972F63F@rfc-editor.org>
In-Reply-To: <20130523144235.CC2C972F63F@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, bob.hinden@gmail.com, msweet@apple.com, ted.lemon@nominum.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:45:49 -0000

Michael,
      Let me repeat myself... This is not how the errata report system 
is to be used.  It is *not* a notification system for future proposals. 
  That type of notification can be accomplished by posting to the 
appropriate IETF mailing list (ipv6@ietf.org in this case).

Regards,
Brian

On 5/23/13 10:42 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC6874,
> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3632
>
> --------------------------------------
> Type: Technical
> Reported by: Michael Sweet <msweet@apple.com>
>
> Section: 3
>
> Original Text
> -------------
>    Such bare "%" signs are for user interface convenience, and need to
>    be turned into properly encoded characters (where "%25" encodes "%")
>    before the URI is used in any protocol or HTML document.  However,
>    URIs including a ZoneID have no meaning outside the originating node.
>    It would therefore be highly desirable for a browser to remove the
>    ZoneID from a URI before including that URI in an HTTP request.
>
>
> Corrected Text
> --------------
>    Such bare "%" signs are for user interface convenience, and need to
>    be turned into properly encoded characters (where "%25" encodes "%")
>    before the URI is used in any protocol or HTML document.  HTTP Clients
>    MUST include a ZoneID in any URIs provided in an HTTP request since
>    HTTP Servers will need it when generating URIs, otherwise the IPv6
>    address will not be usable by the Client.
>
>
> Notes
> -----
> NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.
>
> The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).
>
> The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):
>
>     POST /ipp/print HTTP/1.1
>     Host: [v1.fe80::1234+en0]:631
>     Content-Type: application/ipp
>     Transfer-Coding: chunked
>
>     ... IPP request ...
>
> The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.
>
> The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...
>
> Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.
>
> The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.
>
> Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC6874 (draft-ietf-6man-uri-zoneid-06)
> --------------------------------------
> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
> Publication Date    : February 2013
> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
> Category            : PROPOSED STANDARD
> Source              : IPv6 Maintenance
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG
>


From ietf@rozanak.com  Thu May 23 07:54:14 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D32121F96D4 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:54:13 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WAusPaFMVO0o for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:54:07 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA0F21F96D6 for <ipv6@ietf.org>; Thu, 23 May 2013 07:53:50 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MEXD7-1Uhyev00gD-00G123; Thu, 23 May 2013 10:53:46 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
Subject: Router advertisement based privacy - I-D: Action :draft-rafiee-6man-ra-privacy
Date: Thu, 23 May 2013 16:53:40 +0200
Message-ID: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CE57D6.1678B3B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5XkSZypPJDaHhZRNWc3pCIffaScA==
Content-Language: en-us
X-Provags-ID: V02:K0:wLI7yVwu1aT2kzh0anrLM/ppEu1G+QUUDOvTthDMOkl KBA6tjEvx6c/11iykdXJSaGKA1EJGdPNo9IUAnoLOx27x4xRvV dME4/dkhvV5bvfKn8l5THyd1/ZAuEjFgsJhZROCds72OobHNb0 yogXNgE1SmI/Xecj4WOBDJQduKDOEeSNJSW7i8DOwMKVVDJZtY 3xLjn0n2EnN0h4G2odb61Kx9CIXzC+cz8ZAL0syxa+LsvipjrL EsVRnh+E2l5a0sU44TgTpObtfPR69nBFqelD6veBUDYukfQ30S UAEU12QFKWaDSnS09V4z86l9N6qCRatpDCnJv+8PcT60mv6xGD Cx8HfjexH/aAPK6Q6gYA=
Cc: Dave Thaler <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:54:15 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0004_01CE57D6.1678B3B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I first want to thank Dave who took the time to read and comment on my draft
and to discuss the problems associated with it. Based on some offline
discussions with Dave, I have changed this document to better address the
current issues with RFC 4941 which are actually related to differences in
interpretation of the wording used in the that document. In many cases the
wording used gives implementations the choice of how best to accomplish the
goal which can lead to bad choices being made which negates the purpose of
the document. This draft is thus an update to the Privacy Extension document
and also, because it does not allow a node to generate and use an IID based
on a MAC address, an update to one section of RFC 4862 which pertains to
this.

 

In this document an approach is recommend that doesn't make use MAC
addresses in the generation of public addresses. It does, in fact, endorse
the use other approaches that aren't based on the use of MAC addresses in
the generation of public addresses. Public addresses can be valid forever
but it is recommended that, for privacy purposes, a node not make use of
public addresses.

The definition of public addresses here is the same as what Dave explained
in his last responses to the people on this list, i.e., the addresses that
need to have DNS records. In my opinion, these addresses are more useful for
servers than other nodes.

 

I appreciate your support and any and all comments that you might proffer. 

 

Thank you,

Best,

Hosnieh 

 


------=_NextPart_000_0004_01CE57D6.1678B3B0
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 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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;
	font-size:10.0pt;
	font-family:"Calibri","sans-serif";}
@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>I first =
want to thank Dave who took the time to read and comment on my draft and =
to discuss the problems associated with it. Based on some offline =
discussions with Dave, I have changed this document to better address =
the current issues with RFC 4941 which are actually related to =
differences in interpretation of the wording used in the that document. =
In many cases the wording used gives implementations the choice of how =
best to accomplish the goal which can lead to bad choices being made =
which negates the purpose of the document. This draft is thus an update =
to the Privacy Extension document and also, because it does not allow a =
node to generate and use an IID based on a MAC address, an update to one =
section of RFC 4862 which pertains to this.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In this =
document an approach is recommend that doesn't make use MAC addresses in =
the generation of public addresses. It does, in fact, endorse the use =
other approaches that aren't based on the use of MAC addresses in the =
generation of public addresses. Public addresses can be valid forever =
but it is recommended that, for privacy purposes, a node not make use of =
public addresses.<o:p></o:p></p><p class=3DMsoNormal>The definition of =
public addresses here is the same as what Dave explained in his last =
responses to the people on this list, i.e., the addresses that need to =
have DNS records. In my opinion, these addresses are more useful for =
servers than other nodes.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I appreciate =
your support and any and all comments that you might proffer. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thank you,<o:p></o:p></p><p =
class=3DMsoNormal>Best,<o:p></o:p></p><p class=3DMsoNormal>Hosnieh =
<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0004_01CE57D6.1678B3B0--


From ietf@rozanak.com  Thu May 23 08:04:48 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECB821F8FE8 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:04:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qoks4SDJ-420 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:04:43 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB2E21F91B8 for <ipv6@ietf.org>; Thu, 23 May 2013 08:04:43 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MVNTS-1UxiK83Sbm-00Yh8f; Thu, 23 May 2013 11:04:41 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>
In-Reply-To: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>
Subject: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
Date: Thu, 23 May 2013 17:04:34 +0200
Message-ID: <001401ce57c6$d93bf750$8bb3e5f0$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01CE57D7.9CC73850"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlJjmGyLA
Content-Language: en-us
X-Provags-ID: V02:K0:2ptI9XSpJPZ34wVSCdlC/r3HaX4RKjtSzbyohgbw5m0 TVWO1zLddsScdaYGHx4cTk2I0SyX2kUv2ISu9qJLdzm2ayEzZR 9+46nZLbmTTFBlfcIUgQ2vdkJZ9+AJ1KyN92SxGMiAVAjyaC4d 7I9fCuSYpTdkZE/RNKRXNEfQxsbl5jveILusAMLYAKlG2Onsl2 Q4n8+udinv69plPhjXAqypT/BUaxvyxq7GlK0dCxbuzQiaMp4V 3+zshHp6BMb2muqV+5J1CBWIF1UghEFHxF9O7K0sQhVo2qViWd /C7OWwB7HCvgUzbHK9qfh+AHE8jsEsER/3CIoElVmCjzIkGv5R ZY++QNcqMimmGZY5PFF0=
Cc: 'Dave Thaler' <dthaler@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:04:48 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0015_01CE57D7.9CC73850
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Follow up,

 

I forgot to post the link to the draft :-)

http://tools.ietf.org/rfcdiff?url2=draft-rafiee-6man-ra-privacy

 

Thanks,

Best,

Hosnieh

 

 

 

I first want to thank Dave who took the time to read and comment on my draft
and to discuss the problems associated with it. Based on some offline
discussions with Dave, I have changed this document to better address the
current issues with RFC 4941 which are actually related to differences in
interpretation of the wording used in the that document. In many cases the
wording used gives implementations the choice of how best to accomplish the
goal which can lead to bad choices being made which negates the purpose of
the document. This draft is thus an update to the Privacy Extension document
and also, because it does not allow a node to generate and use an IID based
on a MAC address, an update to one section of RFC 4862 which pertains to
this.

 

In this document an approach is recommend that doesn't make use MAC
addresses in the generation of public addresses. It does, in fact, endorse
the use other approaches that aren't based on the use of MAC addresses in
the generation of public addresses. Public addresses can be valid forever
but it is recommended that, for privacy purposes, a node not make use of
public addresses.

The definition of public addresses here is the same as what Dave explained
in his last responses to the people on this list, i.e., the addresses that
need to have DNS records. In my opinion, these addresses are more useful for
servers than other nodes.

 

I appreciate your support and any and all comments that you might proffer. 

 

Thank you,

Best,

Hosnieh 

 


------=_NextPart_000_0015_01CE57D7.9CC73850
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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'>Follow up,<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'>I forgot to post the =
link to the draft :-)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ra-privacy=
">http://tools.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ra-privacy</a><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'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Best,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hosnieh<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'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I =
first want to thank Dave who took the time to read and comment on my =
draft and to discuss the problems associated with it. Based on some =
offline discussions with Dave, I have changed this document to better =
address the current issues with RFC 4941 which are actually related to =
differences in interpretation of the wording used in the that document. =
In many cases the wording used gives implementations the choice of how =
best to accomplish the goal which can lead to bad choices being made =
which negates the purpose of the document. This draft is thus an update =
to the Privacy Extension document and also, because it does not allow a =
node to generate and use an IID based on a MAC address, an update to one =
section of RFC 4862 which pertains to this.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In this =
document an approach is recommend that doesn't make use MAC addresses in =
the generation of public addresses. It does, in fact, endorse the use =
other approaches that aren't based on the use of MAC addresses in the =
generation of public addresses. Public addresses can be valid forever =
but it is recommended that, for privacy purposes, a node not make use of =
public addresses.<o:p></o:p></p><p class=3DMsoNormal>The definition of =
public addresses here is the same as what Dave explained in his last =
responses to the people on this list, i.e., the addresses that need to =
have DNS records. In my opinion, these addresses are more useful for =
servers than other nodes.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I appreciate =
your support and any and all comments that you might proffer. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thank you,<o:p></o:p></p><p =
class=3DMsoNormal>Best,<o:p></o:p></p><p class=3DMsoNormal>Hosnieh =
<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0015_01CE57D7.9CC73850--


From Ted.Lemon@nominum.com  Thu May 23 08:15:46 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D685A11E80F9 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4eviQK0H9kw for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:15:37 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 6870B21F90BB for <ipv6@ietf.org>; Thu, 23 May 2013 08:15:37 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ4ymW36YFYI7A88QhkzBqna8GsbIsI6@postini.com; Thu, 23 May 2013 08:15:37 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E75551B819A for <ipv6@ietf.org>; Thu, 23 May 2013 08:15:36 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D244719005D; Thu, 23 May 2013 08:15:36 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 23 May 2013 08:15:30 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3632)
Thread-Topic: [Technical Errata Reported] RFC6874 (3632)
Thread-Index: AQHOV8PaiWIqAaAyl0qhrM6/JSpR4ZkTTjYAgAAERwCAAAQMgA==
Date: Thu, 23 May 2013 15:15:30 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751AE851@mbx-01.win.nominum.com>
References: <20130523144235.CC2C972F63F@rfc-editor.org> <519E2B96.40106@innovationslab.net> <5ECCB504-DF76-46BA-8482-7671E3E357C3@apple.com>
In-Reply-To: <5ECCB504-DF76-46BA-8482-7671E3E357C3@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C06D5852EB35DE4FBB025E7173AE1D56@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Brian Haberman <brian@innovationslab.net>, "<ipv6@ietf.org>" <ipv6@ietf.org>, "<bob.hinden@gmail.com>" <bob.hinden@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:15:46 -0000

On May 23, 2013, at 11:01 AM, Michael Sweet <msweet@apple.com> wrote:
> I've seen plenty of "pending" (not approved, not rejected) errata for oth=
er RFCs for stuff like this.  Posting to the ipv6 mailing list is useful fo=
r people involved in RFC development but is completely opaque to ordinary i=
mplementers of RFCs (which I have to deal with on a daily basis...)

We're trying to do a better job of responding to errata quickly=97the rapid=
ity of the rejection had nothing to do with the content of the report.   If=
 you look, you will find very few remaining un-examined errata.

I've added an agenda item on the informal telechat today about how to addre=
ss this problem.   The IESG can't actually _address_ the problem=97you will=
 have to write the document=97but hopefully we can come up with a way for y=
ou to get what you need in fewer than eight years.


From ietf@rozanak.com  Thu May 23 08:16:43 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 921BB11E8119 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:16:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TyeveKenGfdl for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:16:38 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id C78FB11E811A for <ipv6@ietf.org>; Thu, 23 May 2013 08:16:38 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LmJnW-1U5vFp2s78-00ZySG; Thu, 23 May 2013 11:16:37 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: <ipv6@ietf.org>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>
In-Reply-To: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>
Subject: RE: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
Date: Thu, 23 May 2013 17:16:31 +0200
Message-ID: <001f01ce57c8$83d80090$8b8801b0$@rozanak.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0020_01CE57D9.47625730"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlJjmHH/A
Content-Language: en-us
X-Provags-ID: V02:K0:OQOgul9wndSzU4nE6hurYhKPSkyun2SWop0A/QbgHUV 7YdvxnIuv7sCAfWeooETlpNyj3maL42dEyzv9hPWZSo/+y+M41 8LqENDbQD58eIqYZ2KY0a1RaEkhIPoHMkYMoDReAOGgYy8w8GZ SOanldfljbxIQukLkedtXqfiNRa91aZ2tPRObgkPuvzTkFMZGY f4oupAMjW76Udg4W6m6Q2kSj3hahbnBLHf4qiTgU87YUWkxvxg LHyV9B3bQ8n8gMxl6rAqyWuPo59N0xzOnwuTB9wayQcrABHjol nV0bl1uBqnlmVsEduTBtWWQxfT50v6mF5fT12g4ZjXa2ne690y 0ETXhoaqyDAFEav0IYOI=
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:16:43 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0020_01CE57D9.47625730
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

follow up to the follow up:

 

sorry, I sent the wrong link the last time. this is the correct link:

http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy 

 

:-|  it is not my day.. :-/

 

Hosnieh


------=_NextPart_000_0020_01CE57D9.47625730
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 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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'>follow up to the follow =
up:<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'>sorry, I sent the wrong =
link the last time. this is the correct link:<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'><a =
href=3D"http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy">http://t=
ools.ietf.org/html/draft-rafiee-6man-ra-privacy</a> =
<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'>:-|&nbsp; it is not my =
day&#8230;&#8230; :-/<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D'>=
<o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D'>=
Hosnieh<o:p></o:p></span></p></div></body></html>
------=_NextPart_000_0020_01CE57D9.47625730--


From Ted.Lemon@nominum.com  Thu May 23 08:24:00 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2643421F9607 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.555
X-Spam-Level: 
X-Spam-Status: No, score=-106.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KhRDgfZHeEyw for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:23:53 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 3E76D21F9606 for <ipv6@ietf.org>; Thu, 23 May 2013 08:23:53 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ40g2eQK0GMxHaJOUv6IFb7w3OcezEk@postini.com; Thu, 23 May 2013 08:23:53 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9FD2F1B818C for <ipv6@ietf.org>; Thu, 23 May 2013 08:23:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 96FB819005D; Thu, 23 May 2013 08:23:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 23 May 2013 08:23:48 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
Thread-Topic: [Technical Errata Reported] RFC6874 (3630)
Thread-Index: AQHOV2jyoE5BESz8v0i6rHInlU3N/pkSsskAgAAME4CAAASVgIAAeOAAgAAA34CAAAZFAIAAFhoA
Date: Thu, 23 May 2013 15:23:46 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751AE91F@mbx-01.win.nominum.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com> <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com> <519E21F8.1040108@innovationslab.net>
In-Reply-To: <519E21F8.1040108@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <054FE8267A4B38408648623C44E41325@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, Michael Sweet <msweet@apple.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:24:00 -0000

On May 23, 2013, at 10:04 AM, Brian Haberman <brian@innovationslab.net> wro=
te:
> 6MAN.

Really?   I would have assumed that this would be an http document, but if =
it can be done in 6man, that would be cool.


From brian@innovationslab.net  Thu May 23 08:26:15 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B9D21F8ACD for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.47
X-Spam-Level: 
X-Spam-Status: No, score=-102.47 tagged_above=-999 required=5 tests=[AWL=0.129, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9dJev5itxuSp for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:26:08 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3740421F93B9 for <ipv6@ietf.org>; Thu, 23 May 2013 08:26:06 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 233708814B; Thu, 23 May 2013 08:26:06 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 51CFD14000C; Thu, 23 May 2013 08:26:05 -0700 (PDT)
Message-ID: <519E350C.5050109@innovationslab.net>
Date: Thu, 23 May 2013 11:26:04 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com> <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com> <519E21F8.1040108@innovationslab.net> <8D23D4052ABE7A4490E77B1A012B6307751AE91F@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751AE91F@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, Michael Sweet <msweet@apple.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:26:15 -0000

On 5/23/13 11:23 AM, Ted Lemon wrote:
> On May 23, 2013, at 10:04 AM, Brian Haberman <brian@innovationslab.net> wrote:
>> 6MAN.
>
> Really?   I would have assumed that this would be an http document, but if it can be done in 6man, that would be cool.
>

RFC 6874 was published by 6MAN.  There was input from the Apps area as 
well (where the HTTPbis WG resides).


From otroan@employees.org  Thu May 23 08:42:27 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A084121F9784 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:42:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hf6Apv06ZTvx for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:42:21 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 8F90A21F9777 for <ipv6@ietf.org>; Thu, 23 May 2013 08:42:21 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFALY3nlGQ/khL/2dsb2JhbABagwjCWIELFnSCIwEBBAE6PxALRlcGiBoGukiOajMHgnNhA6h7gxE6
X-IronPort-AV: E=Sophos;i="4.87,729,1363132800"; d="scan'208";a="14147505"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 23 May 2013 15:42:17 +0000
Received: from dhcp-10-61-108-14.cisco.com (dhcp-10-61-108-14.cisco.com [10.61.108.14]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4NFgF6O014904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 May 2013 15:42:15 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <519E21F8.1040108@innovationslab.net>
Date: Thu, 23 May 2013 17:42:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DC58B99-24B0-425D-8B69-1F2BEB2E59DC@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com> <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com> <519E21F8.1040108@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1503)
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:42:27 -0000

>> I happen to agree that a change like this would be a good change, but =
I also agree that it needs to be done as a consensus document, not as an =
erratum.   This is true not only for process reasons, but because I =
think the change as proposed was too broad.   Is there a working group =
alive where this could get done?
>>=20
>=20
> 6MAN.

I'm fine with 6man owning given that we produced RFC6874.
if the intention here is to use zoneids in referrals (or even =
link-locals) then there has to be involvement from the apps area.

cheers,
Ole=

From brian@innovationslab.net  Thu May 23 08:47:24 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E30821F97EC for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvPnUuW-mnIQ for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:47:18 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 21ABD21F97E5 for <ipv6@ietf.org>; Thu, 23 May 2013 08:47:18 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0CD4A8814D; Thu, 23 May 2013 08:47:18 -0700 (PDT)
Received: from clemson.local (c-69-140-213-249.hsd1.md.comcast.net [69.140.213.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 538E614000C; Thu, 23 May 2013 08:47:17 -0700 (PDT)
Message-ID: <519E3A04.7030602@innovationslab.net>
Date: Thu, 23 May 2013 11:47:16 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <alpine.DEB.2.00.1305230824450.24367@uplift.swm.pp.se> <E8CDEB20-B437-41A4-BEF4-B415865BD871@apple.com> <8D23D4052ABE7A4490E77B1A012B6307751AE58B@mbx-01.win.nominum.com> <519E21F8.1040108@innovationslab.net> <5DC58B99-24B0-425D-8B69-1F2BEB2E59DC@employees.org>
In-Reply-To: <5DC58B99-24B0-425D-8B69-1F2BEB2E59DC@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:47:24 -0000

On 5/23/13 11:42 AM, Ole Troan wrote:
>>> I happen to agree that a change like this would be a good change, but I also agree that it needs to be done as a consensus document, not as an erratum.   This is true not only for process reasons, but because I think the change as proposed was too broad.   Is there a working group alive where this could get done?
>>>
>>
>> 6MAN.
>
> I'm fine with 6man owning given that we produced RFC6874.
> if the intention here is to use zoneids in referrals (or even link-locals) then there has to be involvement from the apps area.
>

If the work shows up in 6MAN, we will solicit advice/review from Apps 
and Security.  The ADs from those areas have already agreed to help.

Regards,
Brian



From v6ops@globis.net  Thu May 23 10:49:59 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A72821F8F7A for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 10:49:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Z-dfRPht6ye for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 10:49:48 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8591E21F8EE8 for <ipv6@ietf.org>; Thu, 23 May 2013 10:36:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1C0C2870105; Thu, 23 May 2013 19:36:37 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id id-Ma-bNA4L5; Thu, 23 May 2013 19:36:37 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 9F4AE870103; Thu, 23 May 2013 19:36:33 +0200 (CEST)
Message-ID: <519E539B.9040203@globis.net>
Date: Thu, 23 May 2013 19:36:27 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: RE: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001f01ce57c8$83d80090$8b8801b0$@rozanak.com>
In-Reply-To: <001f01ce57c8$83d80090$8b8801b0$@rozanak.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 17:49:59 -0000

Hosnieh Rafiee wrote:
>
> follow up to the follow up:
>
> sorry, I sent the wrong link the last time. this is the correct link:
>
> http://tools.ietf.org/html/draft-rafiee-6man-ra-privacy
>
> :-| it is not my day…… :-/
>
> Hosnieh
>
I have read this draft and I don't particularly like it for several
operational reasons.

1) Use of purely random unpredictable IIDs appears to impose an ISP
model of working where there is no trust relationship between the end
node and the network infrastructure.

In corporate environments it is very important that cross-correlation of
log events can occur to support various operational processes (also over
longer periods of time and for examining historical records). IPv4 did
not randomly rotate end node identifiers in an uncorrelated manner, and
the consequences of this new behaviour could be far reaching.

Even in an ISP environment, there is a requirement in many countries for
a log of identifiers that have been used for communication to be
available to law enforcement agencies. It could be argued that
maintaining the relationship between the /64 prefix and the natural
person holding the ISP contract would be sufficient, but some countries
might not accept this, and impose a requirement to log all IIDs that
have been used, which would be a significant burden on storage.

2) Section 3.1. Updating the IID after DAD has completed may disrupt
existing communications and applications.

Also if there is a collision, simply incrementing the modifier will
guarantee another collision if two colliding nodes are operating
draft-rafiee-6man-ra-privacy-03.

3) Section 5 & Section 6 requires dynamic DNS updates. In the event that
an implementer wishes to rotate these records for privacy reasons, there
may be unexpected consequences in the name space, especially in the
presence of distributed DNS with e.g. caching only servers. How would
they know to update their cached records? I think there's a lot more
detail required here on treatment of TTL of e.g. AAAA records, plus
handling of existing sessions. Applications using UDP could also be
problematic: when do they time out?

"In cases where the router prefix changes, the node MUST cut the
connection."
Hmmm unhappy eyeballs and potential negative impact on graceful
renumbering of RFC2894.

4) rotating the IID of link local address and other addresses could have
other unforeseen operational consequences on e.g. static routes, dynamic
routes that point to the end node, ACLs, DSCP QoS, Bandwidth Policing,
VPN tunnel endpoints, Intrusion Detection Systems, load balancers,
outbound firewall access authorisation .... everything where the IPv6
address is assumed to be largely time invariant and is used as a key to
some other relationship. I'd like some more detail of that.

regards,
RayH

From cheshire@apple.com  Thu May 23 15:39:31 2013
Return-Path: <cheshire@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FFE21F8673 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 15:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.142
X-Spam-Level: 
X-Spam-Status: No, score=-110.142 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EhlC7gIotdjS for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 15:39:25 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id E007B21F96C4 for <ipv6@ietf.org>; Thu, 23 May 2013 15:27:44 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay7.apple.com ([17.128.113.101]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN90055IVPRCP31@mail-out.apple.com> for ipv6@ietf.org; Thu, 23 May 2013 15:27:31 -0700 (PDT)
X-AuditID: 11807165-b7f496d000000613-f7-519e97d2c6a3
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay7.apple.com (Apple SCV relay) with SMTP id B0.66.01555.3D79E915; Thu, 23 May 2013 15:27:31 -0700 (PDT)
Received: from chesh1.apple.com (chesh1.apple.com [17.193.13.41]) by spicerack.apple.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MN9007CYVPUUM40@spicerack.apple.com> for ipv6@ietf.org; Thu, 23 May 2013 15:27:30 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3632)
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <519E2B96.40106@innovationslab.net>
Date: Thu, 23 May 2013 15:27:30 -0700
Message-id: <19E693A5-4847-4699-9997-7B771A5FB5A5@apple.com>
References: <20130523144235.CC2C972F63F@rfc-editor.org> <519E2B96.40106@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUi2FCsoXt5+rxAg09L2C1enn3P5MDosWTJ T6YAxigum5TUnMyy1CJ9uwSujKav7gVTDSr+/21ka2BcpNbFyMkhIWAi8e3tBHYIW0ziwr31 bF2MXBxCApOZJKZM+MsO4axkkth98AALSJWwgLnEin0rmEBsXgE9iW1zt7GB2MwCOhK9378x g9hsAloSLz5fAYtzChhInH6xBsxmEVCV+HL5P9hQZoEljBJfe1rYIZq1JZ68u8AKMdRGYv6v 9YwgtpBArMS5e8/AhooI6Eo0dqxggThVVuL18zcsExgFZiG5YxaSO2YhGbuAkXkVo0BRak5i pbleYkFBTqpecn7uJkZw6BWm7mBsXG51iFGAg1GJh3eGzrxAIdbEsuLK3EOMEhzMSiK8hWFA Id6UxMqq1KL8+KLSnNTiQ4zSHCxK4ry/584KFBJITyxJzU5NLUgtgskycXBKNTAKmWaynrCu vhowtVH5w7NNf2s/zjkd4hxtZ3/aZWnW94h17MLToludkyWlrASzdTfkuG76svBZ85YMz283 v77U3F6YkvsuJ7+17/kHZe1Vn55Lx8/9HTor00FMZuejyXNyZ8VzTbnwdH5dT2fUS4tjCzJ7 wrjmWUhH2x4UXuI57ceeh4KnJ3YpsRRnJBpqMRcVJwIADoGe0zkCAAA=
Cc: ipv6@ietf.org, bob.hinden@gmail.com, ted.lemon@nominum.com, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 22:39:31 -0000

On behalf of Apple I apologise. I will talk with Michael Sweet directly and try to resolve his concerns without any more errata reports.

Stuart Cheshire

On 23 May, 2013, at 07:45, Brian Haberman <brian@innovationslab.net> wrote:

> Michael,
>     Let me repeat myself... This is not how the errata report system is to be used.  It is *not* a notification system for future proposals.  That type of notification can be accomplished by posting to the appropriate IETF mailing list (ipv6@ietf.org in this case).
> 
> Regards,
> Brian
> 
> On 5/23/13 10:42 AM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6874,
>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3632
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Michael Sweet <msweet@apple.com>
>> 
>> Section: 3
>> 
>> Original Text
>> -------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  However,
>>   URIs including a ZoneID have no meaning outside the originating node.
>>   It would therefore be highly desirable for a browser to remove the
>>   ZoneID from a URI before including that URI in an HTTP request.
>> 
>> 
>> Corrected Text
>> --------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  HTTP Clients
>>   MUST include a ZoneID in any URIs provided in an HTTP request since
>>   HTTP Servers will need it when generating URIs, otherwise the IPv6
>>   address will not be usable by the Client.
>> 
>> 
>> Notes
>> -----
>> NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.
>> 
>> The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).
>> 
>> The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):
>> 
>>    POST /ipp/print HTTP/1.1
>>    Host: [v1.fe80::1234+en0]:631
>>    Content-Type: application/ipp
>>    Transfer-Coding: chunked
>> 
>>    ... IPP request ...
>> 
>> The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.
>> 
>> The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...
>> 
>> Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.
>> 
>> The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.
>> 
>> Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.
>> 
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>> 
>> --------------------------------------
>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>> --------------------------------------
>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>> Publication Date    : February 2013
>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG

From internet-drafts@ietf.org  Thu May 23 18:01:21 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D079A21F9330; Thu, 23 May 2013 18:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D54Kp1g1o2it; Thu, 23 May 2013 18:01:21 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3795421F90DF; Thu, 23 May 2013 18:01:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-stable-privacy-addresses-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130524010121.21180.81330.idtracker@ietfa.amsl.com>
Date: Thu, 23 May 2013 18:01:21 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 01:01:22 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : A method for Generating Stable Privacy-Enhanced Addresse=
s with IPv6 Stateless Address Autoconfiguration (SLAAC)
	Author(s)       : Fernando Gont
	Filename        : draft-ietf-6man-stable-privacy-addresses-08.txt
	Pages           : 26
	Date            : 2013-05-23

Abstract:
   This document specifies a method for generating IPv6 Interface
   Identifiers to be used with IPv6 Stateless Address Autoconfiguration
   (SLAAC), such that addresses configured using this method are stable
   within each subnet, but the Interface Identifier changes when hosts
   move from one network to another.  This method is meant to be an
   alternative to generating Interface Identifiers based on hardware
   address (e.g., using IEEE identifiers), such that the benefits of
   stable addresses can be achieved without sacrificing the privacy of
   users.  The method specified in this document applies to all prefixes
   a host may be employing, including link-local, global, and unique-
   local addresses.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-stable-privacy-addresses-08

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-stable-privacy-addresses=
-08


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


From fgont@si6networks.com  Thu May 23 18:08:19 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDAA21F91BF for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 18:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfwxUGYbRmHM for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 18:08:18 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFC921F9307 for <6man@ietf.org>; Thu, 23 May 2013 18:08:14 -0700 (PDT)
Received: from [186.134.15.210] (helo=[192.168.0.6]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UfgUK-0004wL-TC; Fri, 24 May 2013 03:08:10 +0200
Message-ID: <519EBBA7.5080300@si6networks.com>
Date: Thu, 23 May 2013 22:00:23 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519C46F2.8040406@si6networks.com> <ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man-chairs@tools.ietf.org, Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 01:08:19 -0000

Hi, Tim,

Thanks so much for your feedback! -- Please find my comments in-line...

On 05/22/2013 10:19 AM, Tim Chown wrote:
> 
> Overall, I think this is good work and should be progressed.

Thanks!


> First, some general comments:
> 
> You may wish to be clearer earlier in the document (abstract and/or
> introduction) that your method applies to all prefixes a host may
> have, including link-local, ULA, and global(s).  As it stands, you
> only, for example, mention link-locals first in Section 3.

Good point. I've tweaked the abstract, and have also clarified this
point in Section 3.



> The implication of the above is that a multihomed host will have
> different IIDs per ISP it receives a prefix from. This may have
> privacy advantages in a static device scenario (this is implied, but
> never stated anywhere that I can see).

So... how about a bullet along the lines of:

"Since the method specified in this document will result in different
Interface Identifiers, knowledge/leakage of the Interface Identifier
employed for the stable address of one prefix will not negatively affect
the security/privacy of the stable addresses configured for other prefixes"



> There is some focus in your text on why you might disable 4941.
> That's not that common a practice, esp. in campus networks, or home
> networks. While some admins may wish to disable 4941 where they can,
> I think you should promote use of your method with 4941 being
> perfectly reasonable to use alongside it, rather than saying "because
> 4941 may be turned off, we need this method". Related, is that in a
> few places you talk about your method helping to reduce tracking
> between networks, while in practice using 4941 for static (desktop)
> devices does have benefits.

I'm all for the use of this method along with RFC4941...I was just
noting that in some scenarios RFC4941 might be turned off not because a
non-desire for privacy, but for operational reasons.

I've tweaked the text a bit in the hopes that readers don't get the
impression that I'm arguing against use of RFC4941. (Most likely, by the
time you read this I'll have posted version -08... so please check that
one... and if there's still room for improvement in this area, I could
post a -09 version based on your suggestions).



> Specific comments:
> 
> Section 1:
> 
> In the bullet point "since embedding" you may wish to be clearer that
> the "pattern" is the IID format caused by, for example, basing the
> IID on an IEEE identifier.

I have added a clarification to that bullet. - Thanks!



> "other information collectors", I guess you mean sites running
> services, e.g. typically through web server logs.

This was borrowed from RFC 4941. -- anything to tweak here?



> Not sure what the point about inferring that temporary addresses are
> in use buys you. 

If you know that they are temporary addresses, you will expect them to
change. On the other hand, if temporary addresses looked exactly the
same as stable addresses, you'd have to figure out whether they are
different nodes, or the same node with a new temporary address.


> Do you mean that with a small number of hosts in a
> subnet you may be able to deduce which devices are which by looking
> for when their addresses change?

Yes.


> That doesn't help you identify that same host later or in a different network though?

If you can continually poll/see/communicate_with the node and detect the
address changes, you might still correlate the activities of a node
within a network (of course, when the number of nodes increases, and/or
the lifetime of temporary addresses is reduced, it gets much trickier).

The simple example would be:
Let's say you see two addresses on a given network. Say, 2001:db8::1 and
2001:db8::2. All out of the sudden you stop seeing packets from
2001:db8::2, but also start seeing packets from 2001:db8::10. -- It
would all look like 2001:db8::10 is the same node as 2001:db8::2.



> As an aside here, I looked in our network monitoring database, and my
> desktop Mac over the last month has been seen to use a link-local
> IPv6 address, many IPv6 privacy addresses, and an IPv4 global
> address, but not its global SLAAC address.  That's because nothing
> has connected to it from outside the local subnet. Sure, if we did
> not have an IPv6 firewall (as Dave pointed out) the host could be
> scannable due to its "predictable" Mac OUI, but it's interesting that
> in the last month, my global SLAAC address has never been used. Of
> course I don't happen to run any advertised services, though if I did
> my address would most likely be discoverable by looking at the DNS
> name it is referred to by.

The problem here is that once the stable address (or, more specifically,
its IID) becomes known to an attacker, you can be subject to
host-tracking by active probing. The stable IID might become known to an
attacker because at some point in time you advertised that IPv6 address,
but also because you e.g. shared a network with an attacker.

A simple example is that if we attend the same conference/cafe/whatever
and you could learn my stable IID (based on my MAC address). Then you
check the headers of my emails, and learn the v6 prefixes of the
networks I typically connect to. And, after that, you could tell whether
I am online by polling KnownPrefixes|IID.

An you shouldn't need a firewall to prevent *this*. Actually, strictly
speaking, the fireall won't prevent this: you can still probe the node
in different ways that the firewall won't block.



> Section 3:
> 
> Second main paragraph, you might add "just as per SLAAC today", or
> words to that effect. I don't think this is any change as such.

Agreed. I just wanted to clarify that the requirement of "MUST use this
method for all addresses" does not apply to temporary addresses -- since
they *can* be used in conjunction with
draft-ietf-6man-stable-privacy-addresses. -- I've moved the sentence you
mention right befre the parenthetical note.



> Not sure about mentioning IIDs smaller than 64 bits here. You may
> wish to more clearly recommend that your method uses 64-bit IIDs?

Previous versions of the I-D didn't. But then I was told that there was
no reason to hardcode the IID length in this I-D -- hence I tweaked the
text accordingly.

Although I agree that hardcoding the length of IIDs to be 64-bit long
makes the text clearer.



> "Including the SLAAC prefix"... you say the IID then varies across
> networks, but you may wish to add that the IID will also vary across
> each prefix the nodes uses (link-local, ULA, each global if
> multihomed).

I've tweaked the text accordingly.


> There's a conflict in the next paragraph about "desirable" and "MUST"
> - which is it?

s/desirable/required/ :-) -- fixed!



> The comment about MS Windows should perhaps be more orthogonal.  A
> node IID may be manually configured, it may use DHCP, it may use
> SLAAC with IEEE identifiers, it may use your method, it may use the
> method MS Windows uses, or it may even use the tokenised identifier
> method that I posted a while ago.  It can use any of those, AND use
> 4941 as well.  But saying "such implementations would not be affected
> by the method" doesn't sound quite right.

The point I was trying to make is that traditional slaac (in terms of #
of nodes) is not as widely deployed as one would expect.


> Section 4:
> 
> Fourth main paragraph, what is the most likely cause of repeated DAD
> conflicts/failures?  NS/NA DoS?

Yes (of course, assuming 64-bit IIDs).


> Is there anything else that would be likely to cause this?  Worth 
> elaborating on that when considering tuning the retry limit?

My take is that, in a really unlucky scenario, you might get 1
collision, but no more than that. The value "3" is somewhat arbitrary, I
should say.



> Section 7:
> 
> Maybe clarify that the first bullet point is for inbound connections
> only.

That's correct if this is implemented along RFC4941. However, if this is
implemented without RFC4941, this method still prevents such trivial
host tracking.



> A fourth bullet point could be that you do not disclose hints about
> hardware types.

Good point. Added!


> A fifth could be that IIDs may only be tracked or probed for each
> prefix the host is known to use, e.g. detection or disclosure of the
> link-local IID does not compromise the IID used for incoming global
> connections.  So if you sniff for IPv6 service discovery traffic, for
> example, you may learn a node's link-local IID, but not be able to
> deduce its global address.

Added as:

"Since the method specified in this document will result in different
Interface Identifiers, knowledge/leakage of the Interface Identifier
employed for the stable address of one prefix will not negatively affect
the security/privacy of the stable addresses configured for other prefixes"


> How does your RA "attack" work in practice here?  Do you mean issuing
> a rogue RA for the same prefix?  We should perhaps assume that robust
> rogue RA protection is in place, and if not there are many worse
> things an attacker can do!

Agreed. I added this attack vector description, since it was described
by Christian Huitema... so I added it for completeness sake. Should I
twek the text? Remove it?



> Perhaps note/remind here that RFC4862 says to run DAD per prefix
> (section 5.4).

mmmm... not sure what you mean.



> Appendix B:
> 
> B.1 you say "one possible attack", then list more than one.

Fixed.



> B.1.3 Worth any consideration of MIPv6 here?  

It has been years since I last checked MIPv6 (and when I did, I mostly
just skimmed through it). So... up to you. :-)


> The Home Address is
> obviously trackable, by design, but any Care-of Address could benefit
> from your approach. Are there mobility methods anywhere else that
> might assume static IIDs though?

You mean "IIDs that are stable across networks"?

P.S.: Please check version -08, and let me know if there are any further
tweaks I should apply.

Thanks so much!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




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





From brian.e.carpenter@gmail.com  Thu May 23 19:44:42 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730B821F95E5 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 19:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETv0kbNIYky6 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 19:44:41 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id D5AD721F958D for <ipv6@ietf.org>; Thu, 23 May 2013 19:44:41 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so3656177pbc.35 for <ipv6@ietf.org>; Thu, 23 May 2013 19:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+vLyR8ixcLbDgvd29Tm7BV3n8Vqz17j0RG8Vh5XFx5A=; b=qulvPC9+C14w42kmtCKEswrQu1rhLBCoExvlJA74duWoccEQaOPH4rXEJivaPgJ7me kpF5LIE0liE+dFwhuO2Is5fZpvCBP6C4mxU3wgOVcD+QznkOe0iI6QtGooZbOr2Cu4KT /uIfcdRBQh6fc+//usnPOwvkswCWTGCbHcQIfWsymOldBLiZiWvT5jhv9pNn1uFO12C8 q/Z4Bdx7wjjZCkUIBz1sv4pQ8wxeNP3zz+GaibiDbgRC+qnyhgg7Jlp+kZmGdWYE+Whl mmOxxizcqtNCS5znitHBgyh2D/X2U0twsNUgzVEZK94X1ZEptJN7UMeR9CbVXanLvGuf pdNQ==
X-Received: by 10.68.3.107 with SMTP id b11mr13380306pbb.118.1369363481565; Thu, 23 May 2013 19:44:41 -0700 (PDT)
Received: from [192.168.1.4] (118-92-59-145.dsl.dyn.ihug.co.nz. [118.92.59.145]) by mx.google.com with ESMTPSA id w8sm14146247pbo.9.2013.05.23.19.44.39 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 19:44:40 -0700 (PDT)
Message-ID: <519ED41F.5050306@gmail.com>
Date: Fri, 24 May 2013 14:44:47 +1200
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: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com>
In-Reply-To: <5155BD4C.9030307@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 02:44:42 -0000

Hi,

I haven't noticed a single comment on this version, so is it
fair to assume everybody has read it and is in agreement? If so,
we'll ask the WG Chairs to move it towards WGLC. If there are
more comments, we still have to time to update the draft before
Berlin.

Regards
   Brian Carpenter

On 30/03/2013 05:11, Brian E Carpenter wrote:
> Hi,
> 
> This version is intended to include the results of the discussion
> in Orlando.
> 
> Review and comments welcome!
> 
>    Brian & Sheng
> 
> -------- Original Message --------
> Subject: I-D Action: draft-ietf-6man-ext-transmit-00.txt
> Date: Fri, 29 Mar 2013 08:56:33 -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           : Transmission of IPv6 Extension Headers
> 	Author(s)       : Brian Carpenter
>                           Sheng Jiang
> 	Filename        : draft-ietf-6man-ext-transmit-00.txt
> 	Pages           : 9
> 	Date            : 2013-03-29
> 
> Abstract:
>    Various IPv6 extension headers have been defined since the IPv6
>    standard was first published.  This document updates RFC 2460 to
>    clarify how intermediate nodes should deal with such extension
>    headers and with any that are defined in future.  It also specifies
>    how extension headers should be registered by IANA, with a
>    corresponding minor update to RFC 2780.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-ext-transmit
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-ext-transmit-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 
> 

From msweet@apple.com  Thu May 23 07:25:45 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38AFF11E80E9 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:25:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.181
X-Spam-Level: 
X-Spam-Status: No, score=-107.181 tagged_above=-999 required=5 tests=[AWL=3.103, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aS1mIzTwnW7I for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 07:25:40 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 66E2321F8EAF for <ipv6@ietf.org>; Thu, 23 May 2013 07:25:40 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN9007W19EO77K1@mail-out.apple.com> for ipv6@ietf.org; Thu, 23 May 2013 07:25:39 -0700 (PDT)
X-AuditID: 1180715a-b7f506d000007d18-e7-519e26e17eb9
Received: from [17.153.20.228] (Unknown_Domain [17.153.20.228]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id B9.0A.32024.1E62E915; Thu, 23 May 2013 07:25:38 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com>
Date: Thu, 23 May 2013 10:25:37 -0400
Message-id: <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUiOFPkie4jtXmBBmc/Wlpsfb+PzaLt4j4m i5k9/xgtmj73MVq8PPueyeLIt1iLpv1f2Sy2dsc6cHhsPfmDzWPnrLvsHkuW/GTymHn8C4tH 646/7B6vD8xn9WhoO8YawB7FZZOSmpNZllqkb5fAlbF0m17BG92KE6uvsjQwvlLpYuTkkBAw kdjcfI4FwhaTuHBvPVsXIxeHkEAvk0TrymXMIAlhAXOJuY8/M4LYvAJ6Ete+fWUHsZkFtCRu /HvJBGKzCahJ/J7UxwpicwokSsw8vgYsziKgKrFpH8QcZoElTBK913IhbG2JZQtfM0PMtJG4 sLOVHWLxTUaJCw9Pgi0TEdCV2NdykBXiOlmJ18/fsExg5J+F5I5ZSO6YhWTuAkbmVYwCRak5 iZVmeokFBTmpesn5uZsYQeHdUBi1g7FhudUhRgEORiUe3oM35gQKsSaWFVfmHmKU4GBWEuG1 Vp4XKMSbklhZlVqUH19UmpNafIhRmoNFSZz319xZgUIC6YklqdmpqQWpRTBZJg5OqQbGpqMu Wbaqi8sOhLA6FemZJAgZppmpL2SctyrHJKjlXW+9+mHfFb//mQXHBrDoifqkz9x6xiXycVrV 9yx24Vie153R3hZfir4nrKpLXv70kkT7ZvcELqHfn66f3ptqqhypvTvY50fp47UfetJ2//Pi Ztc8IvzdnvX5qSsOtlZXLoq/t3knI6nEUpyRaKjFXFScCAC3/N5NawIAAA==
X-Mailman-Approved-At: Thu, 23 May 2013 22:17:12 -0700
Cc: "brian@innovationslab.net" <brian@innovationslab.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "ted.lemon@nominum.com" <ted.lemon@nominum.com>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 14:25:45 -0000

Christian,

I'm happy to write up a new draft proposing my changes and go through that process. I'm not happy that my errata have been summarily rejected in less than 24 hours with no time for review.

Consider: hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years.  It took those 8 years for the IETF to agree on a new format with serious compatibility and interoperability issues with the base IETF standard (STD 66 aka RFC 3986), and my errata against the published RFC have been rejected after less than 24 hours of discussion.

How do we notify users of RFC 6874 that there are proposed changes, if not in pending errata?

How long will it take to get a new draft approved that fixes the problems in RFC 6874? I certainly hope the answer is not 8 years...


On 2013-05-23, at 2:47 AM, Christian Huitema <huitema@microsoft.com> wrote:

> Michael, you are asking that the consensus of the WG be reversed. The errata process is not the way to handle this. You have to go through the motions: write a draft, submit it, get consensus...
> 
> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Michael Sweet
> Sent: Wednesday, May 22, 2013 11:10 PM
> To: Brian E Carpenter
> Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com; ted.lemon@nominum.com; RFC Errata System
> Subject: Re: [Technical Errata Reported] RFC6874 (3630)
> 
> Brian,
> 
> What you're apparently missing is that the client is using the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care but the client depends on it (for link local anyways).
> 
> This issue is specifically why we (the Printer Working Group) require IPP Clients to include the zoneid in the HTTP Host header and require IPP Servers to use the Host value in any generated URIs.
> 
> 
> 
> Sent from my iPad
> 
> On 2013-05-23, at 1:26 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>> As far as I can tell this is completely incorrect and the RFC is 
>> completely correct. It's so wrong that I can't even see how to explain 
>> it. By definition, a ZoneID has no meaning outside the host; its only 
>> effect is to direct the packet to the desired interface on that host. 
>> It has absolutely nothing to do with routing on the network.
>> 
>> Regards
>>  Brian Carpenter
>> 
>> 
>> On 23/05/2013 15:51, RFC Errata System wrote:
>>> The following errata report has been submitted for RFC6874, 
>>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>>> 
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
>>> 
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Michael Sweet <msweet@apple.com>
>>> 
>>> Section: 3
>>> 
>>> Original Text
>>> -------------
>>>  Such bare "%" signs are for user interface convenience, and need to
>>>  be turned into properly encoded characters (where "%25" encodes "%")
>>>  before the URI is used in any protocol or HTML document.  However,
>>>  URIs including a ZoneID have no meaning outside the originating node.
>>>  It would therefore be highly desirable for a browser to remove the
>>>  ZoneID from a URI before including that URI in an HTTP request.
>>> 
>>> Corrected Text
>>> --------------
>>>  Such bare "%" signs are for user interface convenience, and need to
>>>  be turned into properly encoded characters (where "%25" encodes "%")
>>>  before the URI is used in any protocol or HTML document.  HTTP Clients
>>>  MUST include a ZoneID in any URIs provided in an HTTP request since
>>>  HTTP Servers will need it when generating URIs, otherwise the IPv6
>>>  address will not be routable.
>>> 
>>> Notes
>>> -----
>>> The original advice ignores a very real issue: HTTP Servers that generate URIs from the client's Host: need to include the Client's zoneid in order for the link local address to be usable/routable.
>>> 
>>> Instructions:
>>> -------------
>>> This errata is currently posted as "Reported". If necessary, please 
>>> use "Reply All" to discuss whether it should be verified or rejected. 
>>> When a decision is reached, the verifying party (IESG) can log in to 
>>> change the status and edit the report, if necessary.
>>> 
>>> --------------------------------------
>>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>>> --------------------------------------
>>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>>> Publication Date    : February 2013
>>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>>> Category            : PROPOSED STANDARD
>>> Source              : IPv6 Maintenance
>>> Area                : Internet
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From msweet@apple.com  Thu May 23 08:01:20 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0431A21F9740 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.398
X-Spam-Level: 
X-Spam-Status: No, score=-107.398 tagged_above=-999 required=5 tests=[AWL=2.286, BAYES_00=-2.599, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tqumgEYGP30k for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 08:01:14 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id DDB1E21F92F0 for <ipv6@ietf.org>; Thu, 23 May 2013 08:01:13 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MN90097IB1DZLR1@mail-out.apple.com> for ipv6@ietf.org; Thu, 23 May 2013 08:01:02 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-32-519e2f2c10bc
Received: from [17.153.20.228] (Unknown_Domain [17.153.20.228]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id 49.00.31158.D2F2E915; Thu, 23 May 2013 08:01:02 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3632)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <519E2B96.40106@innovationslab.net>
Date: Thu, 23 May 2013 11:01:00 -0400
Message-id: <5ECCB504-DF76-46BA-8482-7671E3E357C3@apple.com>
References: <20130523144235.CC2C972F63F@rfc-editor.org> <519E2B96.40106@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsUiOFPkia6e/rxAg/szxC22vt/HZtF2cR+T xcyef4wWx+7UWLw8+57J4si3WIvJbSvYLJr2f2Wz2Nod68DpsfXkDzaPg8c+MnrsnHWX3WPJ kp9MHjOPf2HxeH1gPqtHQ9sx1gD2KC6blNSczLLUIn27BK6ML9s2shTsNKq43LmBqYFxkkYX IyeHhICJxIn5m5khbDGJC/fWs3UxcnEICfQySbxpewmWEBYwl1ixbwUTiM0roCdx7dtXdhCb WUBHYufWO2wgNpuAmsTvSX2sIDangIHEjv39QL0cHCwCqhJfZ5uCzGQWOMAocXrrbGaIXm2J ZQtfg9XwCthIbJiRChIWEoiWeP3sEdgYEQFdicaOFSwQt8lKvH7+hmUCI/8sJFfMQnLFLCRT FzAyr2IUKErNSaw01UssKMhJ1UvOz93ECAryhsKIHYz/l1kdYhTgYFTi4Z2hMy9QiDWxrLgy 9xCjBAezkgivtTJQiDclsbIqtSg/vqg0J7X4EKM0B4uSOO+vubMChQTSE0tSs1NTC1KLYLJM HJxSDYwPeC23XtsV8uO5wqTgt6HWp3+fuh3LwKF0+3jQ60IbhYL1XUZ16Z++n2bTO6XpeWdq IMPRBvN/a64fO8YspCkTej3CNN8lplD+TeUV2YO/Jvf+uW5fbK0tq90slNu8sSraKCRV+UVA Tt2DrRX/w91vfS4JzwmUyDbepHumpnPjSdENJx783qvEUpyRaKjFXFScCAClaCGsbgIAAA==
X-Mailman-Approved-At: Thu, 23 May 2013 22:17:12 -0700
Cc: ipv6@ietf.org, bob.hinden@gmail.com, ted.lemon@nominum.com, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 23 May 2013 15:01:20 -0000

Brian,

I've seen plenty of "pending" (not approved, not rejected) errata for other RFCs for stuff like this.  Posting to the ipv6 mailing list is useful for people involved in RFC development but is completely opaque to ordinary implementers of RFCs (which I have to deal with on a daily basis...)


On 2013-05-23, at 10:45 AM, Brian Haberman <brian@innovationslab.net> wrote:

> Michael,
>     Let me repeat myself... This is not how the errata report system is to be used.  It is *not* a notification system for future proposals.  That type of notification can be accomplished by posting to the appropriate IETF mailing list (ipv6@ietf.org in this case).
> 
> Regards,
> Brian
> 
> On 5/23/13 10:42 AM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC6874,
>> "Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers".
>> 
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3632
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Michael Sweet <msweet@apple.com>
>> 
>> Section: 3
>> 
>> Original Text
>> -------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  However,
>>   URIs including a ZoneID have no meaning outside the originating node.
>>   It would therefore be highly desirable for a browser to remove the
>>   ZoneID from a URI before including that URI in an HTTP request.
>> 
>> 
>> Corrected Text
>> --------------
>>   Such bare "%" signs are for user interface convenience, and need to
>>   be turned into properly encoded characters (where "%25" encodes "%")
>>   before the URI is used in any protocol or HTML document.  HTTP Clients
>>   MUST include a ZoneID in any URIs provided in an HTTP request since
>>   HTTP Servers will need it when generating URIs, otherwise the IPv6
>>   address will not be usable by the Client.
>> 
>> 
>> Notes
>> -----
>> NOTE: PLEASE DO NOT REJECT THIS ERRATA BEFORE FURTHER REVIEW. I WILL BE SUBMITTING A NEW DRAFT PROPOSING THESE CHANGES; THIS ERRATA CAN SERVE AS PUBLIC NOTICE OF POTENTIAL CHANGES TO THE RFC.
>> 
>> The client uses the zoneid to choose a network interface to route packets to that link local address. If the server returns a uri in its response that uses the same link local address but without the client's zoneid, then the client will be unable to use said uri because it won't know which interface to use. Yes the server doesn't care about the zoneid but the client depends on it (for link local anyways).
>> 
>> The client can supply the zoneid in the Host header. For example, the following illustrates a typical IPP request using the previously recommended IPvFuture format (which CUPS implements and uses):
>> 
>>    POST /ipp/print HTTP/1.1
>>    Host: [v1.fe80::1234+en0]:631
>>    Content-Type: application/ipp
>>    Transfer-Coding: chunked
>> 
>>    ... IPP request ...
>> 
>> The printer then validates the Host header and responds with URIs containing the same Host value in any reported IPv6 link-local URIs.
>> 
>> The key issue is one of context - the client *may* be able to query the interface used for a particular socket connection but it probably can't (easily) cache and map this information in the URIs that are embedded in the content returned by the printer, particularly when the client may have to process said content from a variety of sources - IPP is also supported over a USB transport, HTML can be read from disk, etc.  Clients are usually unable to connect to a given IPv6 link local address without the zoneid information to tell them which network interface to use.  And typically the only reason clients use an IPv6 link local address is because it was handed to them by a discovery protocol like WS-Discovery...
>> 
>> Requiring the client to rewrite all URIs is a tremendous burden and is error-prone.  Requiring the server to use the Host header is cheap in comparison.  Having the server validate and use the Host value also helps interoperability since existing clients may not support the new IPv6addrz format - for example, CUPS doesn't support it since it validates URIs and Host values using the ABNF in RFC 3986/STD 66.
>> 
>> The Host header mechanism has been standard practice outside the IETF for several years now. It is part of IPP Everywhere (Printer Working Group), Wi-Fi Direct Print Services (Wi-Fi Alliance), IPP USB (USB Implementers Forum), and AirPrint (Apple).  It solves the problem of client-side routing of IPv6 link local addresses that are used in URIs embedded in content returned by printers and other embedded devices.
>> 
>> Hundreds of millions of printers, computers, and mobile devices have been certified and shipped with IPv6 link local support using the IPvFuture format over the last 8 years. The new format is incompatible with parsers that use the ABNF in STD 66 (aka RFC 3986) and prevents the use of the Host header in HTTP requests to provide a backwards-compatible IPv6 implementation.
>> 
>> Instructions:
>> -------------
>> This errata is currently posted as "Reported". If necessary, please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party (IESG)
>> can log in to change the status and edit the report, if necessary.
>> 
>> --------------------------------------
>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>> --------------------------------------
>> Title               : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
>> Publication Date    : February 2013
>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>> Category            : PROPOSED STANDARD
>> Source              : IPv6 Maintenance
>> Area                : Internet
>> Stream              : IETF
>> Verifying Party     : IESG
>> 
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From v6ops@globis.net  Thu May 23 23:53:11 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F1F21F9588 for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 23:53:11 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mStIkJdY7OhM for <ipv6@ietfa.amsl.com>; Thu, 23 May 2013 23:53:10 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id E3E6521F9651 for <ipv6@ietf.org>; Thu, 23 May 2013 23:53:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B6D398700BD; Fri, 24 May 2013 08:52:49 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaQGzqfO-t4u; Fri, 24 May 2013 08:52:49 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 6C6118700B6; Fri, 24 May 2013 08:52:49 +0200 (CEST)
Message-ID: <519F0E3B.5010200@globis.net>
Date: Fri, 24 May 2013 08:52:43 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com>
In-Reply-To: <519ED41F.5050306@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 06:53:11 -0000

Brian E Carpenter wrote:
> Hi,
>
> I haven't noticed a single comment on this version, so is it
> fair to assume everybody has read it and is in agreement? If so,
> we'll ask the WG Chairs to move it towards WGLC. If there are
> more comments, we still have to time to update the draft before
> Berlin.
>
> Regards
>    Brian Carpenter

I think this version still contains a large element of King Cnut
commanding the tide to stop.

End users have different perspectives: one will see a firewall as evil
because it hinders innovation, whilst another will see a firewall as
absolutely necessary because innovation leads to bugs and
vulnerabilities in end nodes, which need to be protected until they are
patched. I'm not sure the current text is entirely balanced in this respect.

I would also like to see some text on whether it is possible/desirable
for a middleware box to strip unknown headers, or even some known
headers, rather than making a binary decision to drop or transmit the
entire packet. If (new) headers are truly optional or experimental, the
residual stripped packet may still have value e.g. stripping hop by hop
extension headers on entry to/ egress from a corporate network or
transit AS. That way the (new) extension headers could be usefully
deployed in an AS that supports them, but the end to end traffic would
not be blocked further along the path by firewalls in an AS that does not.

regards,
RayH

From ietfc@btconnect.com  Fri May 24 01:06:05 2013
Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A248F21F9649 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 01:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.292
X-Spam-Level: 
X-Spam-Status: No, score=-3.292 tagged_above=-999 required=5 tests=[AWL=-1.008, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id klE-NiPLHYPc for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 01:06:00 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com [213.199.154.186]) by ietfa.amsl.com (Postfix) with ESMTP id 30DFB21F8AD8 for <ipv6@ietf.org>; Fri, 24 May 2013 01:05:59 -0700 (PDT)
Received: from mail190-db8-R.bigfish.com (10.174.8.234) by DB8EHSOBE038.bigfish.com (10.174.4.101) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 08:05:59 +0000
Received: from mail190-db8 (localhost [127.0.0.1])	by mail190-db8-R.bigfish.com (Postfix) with ESMTP id EE1918E081D; Fri, 24 May 2013 08:05:58 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I936eI542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hz97hz8275ch1033IL17326ah19a27bh172cdfh8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail190-db8 (localhost.localdomain [127.0.0.1]) by mail190-db8 (MessageSwitch) id 1369382757512410_20606; Fri, 24 May 2013 08:05:57 +0000 (UTC)
Received: from DB8EHSMHS002.bigfish.com (unknown [10.174.8.229])	by mail190-db8.bigfish.com (Postfix) with ESMTP id 77F9F460153; Fri, 24 May 2013 08:05:57 +0000 (UTC)
Received: from AMSPRD0711HT003.eurprd07.prod.outlook.com (157.56.250.181) by DB8EHSMHS002.bigfish.com (10.174.4.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 08:05:56 +0000
Received: from pc6 (86.173.197.168) by pod51017.outlook.com (10.242.14.164) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 08:05:56 +0000
Message-ID: <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Michael Sweet <msweet@apple.com>, Christian Huitema <huitema@microsoft.com>
References: <20130523035151.7B24A6210A@rfc-editor.org><519DA89C.5070704@gmail.com><13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com><C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
Date: Fri, 24 May 2013 09:00:15 +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-Originating-IP: [86.173.197.168]
X-OriginatorOrg: btconnect.com
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 08:06:05 -0000

Michael

I would have been happy to see your erratum rejected in 24 minutes,
because it is an abuse of process.  It's a bit like submitting an I-D in
Swahili, nothing wrong with Swahili but quite wrong for the context.

Erratum are for errors, where the text did not mean what the WG had
agreed on, where the grammar is wrong, not English, where the text is
being misinterpreted.

Changes to the function require an I-D.  Having had that pointed out to
you, and you might well have not realised the meaning of an erratum in
the context of the IETF, other SDO may work differently, yet you persist
in submitting errata; I hope that future ones are rejected as quickly.

When I-Ds are urgently required, then they can become RFC in six months,
but that only happens when the correct processes are followed.

Tom Petch


----- Original Message -----
From: "Michael Sweet" <msweet@apple.com>
To: "Christian Huitema" <huitema@microsoft.com>
Cc: <brian@innovationslab.net>; <ipv6@ietf.org>; <bob.hinden@gmail.com>;
<ted.lemon@nominum.com>; "RFC Errata System" <rfc-editor@rfc-editor.org>
 Thursday, May 23, 2013 3:25 PM


> Christian,
>
> I'm happy to write up a new draft proposing my changes and go through
that process. I'm not happy that my errata have been summarily rejected
in less than 24 hours with no time for review.
>
> Consider: hundreds of millions of printers, computers, and mobile
devices have been certified and shipped with IPv6 link local support
using the IPvFuture format over the last 8 years.  It took those 8 years
for the IETF to agree on a new format with serious compatibility and
interoperability issues with the base IETF standard (STD 66 aka RFC
3986), and my errata against the published RFC have been rejected after
less than 24 hours of discussion.
>
> How do we notify users of RFC 6874 that there are proposed changes, if
not in pending errata?
>
> How long will it take to get a new draft approved that fixes the
problems in RFC 6874? I certainly hope the answer is not 8 years...
>
>
> On 2013-05-23, at 2:47 AM, Christian Huitema <huitema@microsoft.com>
wrote:
>
> > Michael, you are asking that the consensus of the WG be reversed.
The errata process is not the way to handle this. You have to go through
the motions: write a draft, submit it, get consensus...
> >
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
Of Michael Sweet
> > Sent: Wednesday, May 22, 2013 11:10 PM
> > To: Brian E Carpenter
> > Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com;
ted.lemon@nominum.com; RFC Errata System
> > Subject: Re: [Technical Errata Reported] RFC6874 (3630)
> >
> > Brian,
> >
> > What you're apparently missing is that the client is using the
zoneid to choose a network interface to route packets to that link local
address. If the server returns a uri in its response that uses the same
link local address but without the client's zoneid, then the client will
be unable to use said uri because it won't know which interface to use.
Yes the server doesn't care but the client depends on it (for link local
anyways).
> >
> > This issue is specifically why we (the Printer Working Group)
require IPP Clients to include the zoneid in the HTTP Host header and
require IPP Servers to use the Host value in any generated URIs.
> >
> >
> >
> > Sent from my iPad
> >
> > On 2013-05-23, at 1:26 AM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> >
> >> As far as I can tell this is completely incorrect and the RFC is
> >> completely correct. It's so wrong that I can't even see how to
explain
> >> it. By definition, a ZoneID has no meaning outside the host; its
only
> >> effect is to direct the packet to the desired interface on that
host.
> >> It has absolutely nothing to do with routing on the network.
> >>
> >> Regards
> >>  Brian Carpenter
> >>
> >>
> >> On 23/05/2013 15:51, RFC Errata System wrote:
> >>> The following errata report has been submitted for RFC6874,
> >>> "Representing IPv6 Zone Identifiers in Address Literals and
Uniform Resource Identifiers".
> >>>
> >>> --------------------------------------
> >>> You may review the report below and at:
> >>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
> >>>
> >>> --------------------------------------
> >>> Type: Technical
> >>> Reported by: Michael Sweet <msweet@apple.com>
> >>>
> >>> Section: 3
> >>>
> >>> Original Text
> >>> -------------
> >>>  Such bare "%" signs are for user interface convenience, and need
to
> >>>  be turned into properly encoded characters (where "%25" encodes
"%")
> >>>  before the URI is used in any protocol or HTML document.
However,
> >>>  URIs including a ZoneID have no meaning outside the originating
node.
> >>>  It would therefore be highly desirable for a browser to remove
the
> >>>  ZoneID from a URI before including that URI in an HTTP request.
> >>>
> >>> Corrected Text
> >>> --------------
> >>>  Such bare "%" signs are for user interface convenience, and need
to
> >>>  be turned into properly encoded characters (where "%25" encodes
"%")
> >>>  before the URI is used in any protocol or HTML document.  HTTP
Clients
> >>>  MUST include a ZoneID in any URIs provided in an HTTP request
since
> >>>  HTTP Servers will need it when generating URIs, otherwise the
IPv6
> >>>  address will not be routable.
> >>>
> >>> Notes
> >>> -----
> >>> The original advice ignores a very real issue: HTTP Servers that
generate URIs from the client's Host: need to include the Client's
zoneid in order for the link local address to be usable/routable.
> >>>
> >>> Instructions:
> >>> -------------
> >>> This errata is currently posted as "Reported". If necessary,
please
> >>> use "Reply All" to discuss whether it should be verified or
rejected.
> >>> When a decision is reached, the verifying party (IESG) can log in
to
> >>> change the status and edit the report, if necessary.
> >>>
> >>> --------------------------------------
> >>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
> >>> --------------------------------------
> >>> Title               : Representing IPv6 Zone Identifiers in
Address Literals and Uniform Resource Identifiers
> >>> Publication Date    : February 2013
> >>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
> >>> Category            : PROPOSED STANDARD
> >>> Source              : IPv6 Maintenance
> >>> Area                : Internet
> >>> Stream              : IETF
> >>> Verifying Party     : IESG
> >>>
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



From tjc@ecs.soton.ac.uk  Fri May 24 04:34:05 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1531921F95C4 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.565
X-Spam-Level: 
X-Spam-Status: No, score=-2.565 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UV5QJGtFeRJu for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:34:04 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id AE18121F9413 for <ipv6@ietf.org>; Fri, 24 May 2013 04:34:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OBXuSF009990 for <ipv6@ietf.org>; Fri, 24 May 2013 12:33:56 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4OBXuSF009990
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369395236; bh=ET5hCSbRg9na2kuyWdJj5CXgWjo=; h=From:Mime-Version:Subject:Date:References:To:In-Reply-To; b=np7WCp41wh69falmgyypd5AeHnk7WUJp5taNx59k/WQ/eKfIWomAo8pzR0dqu7slU yqRP3k5B5iRFNAhWfGZ/PqS53FGc/Be+3x4ov0a7K7inc/NsPu87QBhLTeCLuHDjJv A2xOHdp8kq3+K9NVW50KjZ4C4ITG+MPsCQG4sRoE=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4NCXu0430620506k1 ret-id none; Fri, 24 May 2013 12:33:56 +0100
Received: from dhcp-205-236.wireless.soton.ac.uk (dhcp-205-236.wireless.soton.ac.uk [152.78.205.236]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OBXrEP026964 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Fri, 24 May 2013 12:33:54 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8129A77C-ADC5-4B51-BEC7-B75510A18D99"
Message-ID: <EMEW3|923fc0fa8e0aff7696bf9637a758a90fp4NCXu03tjc|ecs.soton.ac.uk|3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
Date: Fri, 24 May 2013 12:33:53 +0100
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001401ce57c6$d93bf750$8bb3e5f0$@rozanak.com> <3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk>
To: ipv6@ietf.org
In-Reply-To: <001401ce57c6$d93bf750$8bb3e5f0$@rozanak.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NCXu043062050600; tid=p4NCXu0430620506k1; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4OBXuSF009990
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 11:34:05 -0000

--Apple-Mail=_8129A77C-ADC5-4B51-BEC7-B75510A18D99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Can you clarify, succinctly, what your proposal adds that you cannot =
achieve by a combination of =
http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addresses/ =
and RFC4941?

It seems a key point is that 4941 "only" says SHOULD for the IID =
regeneration when the prefix changes.  Yet afaics all implementations do =
this?

Tim

On 23 May 2013, at 16:04, "Hosnieh Rafiee" <ietf@rozanak.com> wrote:

> Follow up,
> =20
> I forgot to post the link to the draft :-)
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ra-privacy
> =20
> Thanks,
> Best,
> Hosnieh
> =20
> =20
> =20
> I first want to thank Dave who took the time to read and comment on my =
draft and to discuss the problems associated with it. Based on some =
offline discussions with Dave, I have changed this document to better =
address the current issues with RFC 4941 which are actually related to =
differences in interpretation of the wording used in the that document. =
In many cases the wording used gives implementations the choice of how =
best to accomplish the goal which can lead to bad choices being made =
which negates the purpose of the document. This draft is thus an update =
to the Privacy Extension document and also, because it does not allow a =
node to generate and use an IID based on a MAC address, an update to one =
section of RFC 4862 which pertains to this.
> =20
> In this document an approach is recommend that doesn't make use MAC =
addresses in the generation of public addresses. It does, in fact, =
endorse the use other approaches that aren't based on the use of MAC =
addresses in the generation of public addresses. Public addresses can be =
valid forever but it is recommended that, for privacy purposes, a node =
not make use of public addresses.
> The definition of public addresses here is the same as what Dave =
explained in his last responses to the people on this list, i.e., the =
addresses that need to have DNS records. In my opinion, these addresses =
are more useful for servers than other nodes.
> =20
> I appreciate your support and any and all comments that you might =
proffer.
> =20
> Thank you,
> Best,
> Hosnieh
> =20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_8129A77C-ADC5-4B51-BEC7-B75510A18D99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><base href=3D"x-msg://2619/"></head><body =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Hi,<div><br></div><div>Can you =
clarify, succinctly, what your proposal adds that you cannot achieve by =
a combination of&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-add=
resses/">http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-ad=
dresses/</a>&nbsp;and RFC4941?</div><div><br></div><div>It seems a key =
point is that 4941 "only" says SHOULD for the IID regeneration when the =
prefix changes. &nbsp;Yet afaics all implementations do =
this?</div><div><br></div><div>Tim</div><div><br><div><div>On 23 May =
2013, at 16:04, "Hosnieh Rafiee" &lt;<a =
href=3D"mailto:ietf@rozanak.com">ietf@rozanak.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" =
style=3D"font-family: Helvetica; font-size: medium; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><div class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"color: rgb(31, 73, 125); ">Follow =
up,<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(31, 73, 125); ">&nbsp;</span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><span =
style=3D"color: rgb(31, 73, 125); ">I forgot to post the link to the =
draft :-)<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(31, 73, 125); "><a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ra-privacy"=
 style=3D"color: purple; text-decoration: underline; =
">http://tools.ietf.org/rfcdiff?url2=3Ddraft-rafiee-6man-ra-privacy</a><o:=
p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"color: rgb(31, =
73, 125); ">&nbsp;</span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(31, 73, 125); ">Thanks,<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"color: rgb(31, 73, 125); =
">Best,<o:p></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; "><span style=3D"color:=
 rgb(31, 73, 125); ">Hosnieh<o:p></o:p></span></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><span style=3D"color: rgb(31, 73, 125); ">&nbsp;</span></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><span style=3D"color: rgb(31, 73, 125); =
">&nbsp;</span></div><div style=3D"border-style: none none none solid; =
border-left-width: 1.5pt; border-left-color: blue; padding: 0in 0in 0in =
4pt; "><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">I first want to thank Dave who took the time to =
read and comment on my draft and to discuss the problems associated with =
it. Based on some offline discussions with Dave, I have changed this =
document to better address the current issues with RFC 4941 which are =
actually related to differences in interpretation of the wording used in =
the that document. In many cases the wording used gives implementations =
the choice of how best to accomplish the goal which can lead to bad =
choices being made which negates the purpose of the document. This draft =
is thus an update to the Privacy Extension document and also, because it =
does not allow a node to generate and use an IID based on a MAC address, =
an update to one section of RFC 4862 which pertains to =
this.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">In this document an approach is recommend that =
doesn't make use MAC addresses in the generation of public addresses. It =
does, in fact, endorse the use other approaches that aren't based on the =
use of MAC addresses in the generation of public addresses. Public =
addresses can be valid forever but it is recommended that, for privacy =
purposes, a node not make use of public addresses.<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">The definition of public addresses here is the =
same as what Dave explained in his last responses to the people on this =
list, i.e., the addresses that need to have DNS records. In my opinion, =
these addresses are more useful for servers than other =
nodes.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">I appreciate your =
support and any and all comments that you might =
proffer.<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Thank =
you,<o:p></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; ">Best,<o:p></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; ">Hosnieh<o:p></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div></div>-------------------------------------=
-------------------------------<br>IETF IPv6 working group mailing =
list<br><a href=3D"mailto:ipv6@ietf.org" style=3D"color: purple; =
text-decoration: underline; ">ipv6@ietf.org</a><br>Administrative =
Requests:<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://www.ietf.org/mailman/listinfo/ipv6" style=3D"color: =
purple; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ipv6</a><br>----------------------=
----------------------------------------------<br></div></blockquote></div=
><br></div></body></html>=

--Apple-Mail=_8129A77C-ADC5-4B51-BEC7-B75510A18D99--

From fgont@si6networks.com  Fri May 24 04:34:48 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9DA621F867B for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQZ302E4rKqD for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:34:48 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id C58ED21F9622 for <6man@ietf.org>; Fri, 24 May 2013 04:34:44 -0700 (PDT)
Received: from [88.128.80.2] (helo=[10.53.209.217]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UfqGU-0003db-T0; Fri, 24 May 2013 13:34:35 +0200
Message-ID: <519F3364.80301@si6networks.com>
Date: Fri, 24 May 2013 11:31:16 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 11:34:49 -0000

On 05/22/2013 03:34 AM, Dave Thaler wrote:
>> I attend an IETF meeting, and learn the IID of your laptop. Then I can actively
>> probe your node regarding "Is David at the office?" "Is David at home?",
>> etc.... simply because your IID is known and constant.
> 
> Since you're making this personal... please explain how you can probe whether 
> I'm at the office or at home, both of which are behind firewalls (so won't respond
> to arbitrary probes) and have address prefixes you don't know to begin with.

As noted, this wasn't meant to be personal -- it was just meant to be an
example.

Now, given the example under discussion:

I could learn your IID when we both attend the IETF meeting. And I could
learn your prefixes when you post to mailing-lists from such places.
Then I could use Prefix|IID to track you.

The fact that you use a firewall is mostly irrelevant. I'd bet your
firewall still reponds to some packets (e.g., packets with unsupported
options?). And, if that were not the case, I could rely on the
ICMPv6 "address resolution failed" error messages sent by your local
router (i.e., if I receive one of such messages, you're not there. If I
don't, you are).

I've seen similar discussions for different kinds of IDs in the past,
and every time someone pushed a flawed/sub-optimal approach, they got
bitten. Moral of the story: don't leak more than necessary to achieve
your desired goal, or you'll be bitten.

P.S.: This was discussed off-list already... but I posted this on-list
so that wg participants are aware of my response.

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





From tjc@ecs.soton.ac.uk  Fri May 24 04:36:27 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B4C21F8793 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:36:27 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sU2XDc2XC+7 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:36:27 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id C2F5F21F8700 for <ipv6@ietf.org>; Fri, 24 May 2013 04:36:26 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OBaMD6010574 for <ipv6@ietf.org>; Fri, 24 May 2013 12:36:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4OBaMD6010574
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369395382; bh=lki/MALESLJFG8orFNsiAkoKDp4=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=3P6npLMr51CsvdRJiTRo7LVjj0VCRFAWkIznqwIGgSgIMWs54JkOXIxlPgNKGOsi4 0C7EDdBlFLRg/AMEAT6jZoazpK09EAgprMQKXieFSeGcPMKT7huVEXY5FnENzBt7u2 Wiv1fp8ufXqvW7QU19JoZdoHLaD1KDFRafpjpAtM=
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 (valid=N/A) id p4NCaM0430620532LU ret-id none; Fri, 24 May 2013 12:36:22 +0100
Received: from dhcp-205-236.wireless.soton.ac.uk (dhcp-205-236.wireless.soton.ac.uk [152.78.205.236]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OBaLVg027376 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Fri, 24 May 2013 12:36:21 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519E539B.9040203@globis.net>
Date: Fri, 24 May 2013 12:36:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|873904f0a39e9fa42dc5e97df56b302fp4NCaM03tjc|ecs.soton.ac.uk|BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001f01ce57c8$83d80090$8b8801b0$@rozanak.com> <519E539B.9040203@globis.net> <BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk>
To: "ipv6@ietf.org List" <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NCaM043062053200; tid=p4NCaM0430620532LU; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4OBaMD6010574
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 11:36:27 -0000

On 23 May 2013, at 18:36, Ray Hunter <v6ops@globis.net> wrote:
>=20
> In corporate environments it is very important that cross-correlation =
of
> log events can occur to support various operational processes (also =
over
> longer periods of time and for examining historical records). IPv4 did
> not randomly rotate end node identifiers in an uncorrelated manner, =
and
> the consequences of this new behaviour could be far reaching.

Well, I think the jury is out on use of 4941 in enterprise environments. =
There are advantages and disadvantages. Accountability is still =
manageable.

But in general I agree with Ray's points.

Tim


From tjc@ecs.soton.ac.uk  Fri May 24 04:45:40 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4B2021F8FBE for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTJhih8q13Jy for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 04:45:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 0425F21F8EFE for <6man@ietf.org>; Fri, 24 May 2013 04:45:39 -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 r4OBjX33013175; Fri, 24 May 2013 12:45:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4OBjX33013175
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369395933; bh=+Tl/yzZXLmuBWCGf71FZ1kQqf74=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=mdGNAxOQUG/Gcclz1d6lFmDn1YqgoWZXohxeMtllnwxzYHx/6AMgU4Fe7lV2DNwv6 Vj5vie0YeNRgfvnUkeQDntEK1h7cwRwTUGWgXG9pU9RHzvVxLRGAdHrAF1SJziJwYZ F9ktgp3VtXEZRrr/b/TzOyHZeEDPPqpp4tivqj20=
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 (valid=N/A) id p4NCjX04306206478q ret-id none; Fri, 24 May 2013 12:45:33 +0100
Received: from dhcp-205-236.wireless.soton.ac.uk (dhcp-205-236.wireless.soton.ac.uk [152.78.205.236]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OBjVOf029737 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 12:45:31 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519F3364.80301@si6networks.com>
Date: Fri, 24 May 2013 12:45:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|735d764a3447dd19694b3932baae9459p4NCjX03tjc|ecs.soton.ac.uk|55205B73-35CA-4DEF-BFFD-13D26E40F377@ecs.soton.ac.uk>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <55205B73-35CA-4DEF-BFFD-13D26E40F377@ecs.soton.ac.uk>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NCjX043062064700; tid=p4NCjX04306206478q; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4OBjX33013175
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "6man-chairs@tools.ietf.org Chairs" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 11:45:41 -0000

On 24 May 2013, at 10:31, Fernando Gont <fgont@si6networks.com> wrote:

> On 05/22/2013 03:34 AM, Dave Thaler wrote:
>>> I attend an IETF meeting, and learn the IID of your laptop. Then I =
can actively
>>> probe your node regarding "Is David at the office?" "Is David at =
home?",
>>> etc.... simply because your IID is known and constant.
>>=20
>> Since you're making this personal... please explain how you can probe =
whether=20
>> I'm at the office or at home, both of which are behind firewalls (so =
won't respond
>> to arbitrary probes) and have address prefixes you don't know to =
begin with.
>=20
> As noted, this wasn't meant to be personal -- it was just meant to be =
an
> example.
>=20
> Now, given the example under discussion:
>=20
> I could learn your IID when we both attend the IETF meeting. And I =
could
> learn your prefixes when you post to mailing-lists from such places.
> Then I could use Prefix|IID to track you.

Or you can sometimes get the user's IID in their home network via email =
headers, e.g.

Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk =
[IPv6:2001:630:d0:f102::22]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) =
with ESMTP id r4OBbV6x027652 (version=3DTLSv1/SSLv3 ...

Well, that's not a great example, but that information is available to =
anyone on a mail list you post to, though not usually in web archives of =
the same list.

> The fact that you use a firewall is mostly irrelevant. I'd bet your
> firewall still reponds to some packets (e.g., packets with unsupported
> options?). And, if that were not the case, I could rely on the
> ICMPv6 "address resolution failed" error messages sent by your local
> router (i.e., if I receive one of such messages, you're not there. If =
I
> don't, you are).
>=20
> I've seen similar discussions for different kinds of IDs in the past,
> and every time someone pushed a flawed/sub-optimal approach, they got
> bitten. Moral of the story: don't leak more than necessary to achieve
> your desired goal, or you'll be bitten.

Indeed.  Which is why I was keen to see the "harvesting" methods also in =
the reconnaissance draft.=20

Tim=

From msweet@apple.com  Fri May 24 05:10:45 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE18A21F9433 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:10:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.489
X-Spam-Level: 
X-Spam-Status: No, score=-107.489 tagged_above=-999 required=5 tests=[AWL=2.195, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fFzy8KDk4HEz for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:10:41 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 005AF21F9436 for <ipv6@ietf.org>; Fri, 24 May 2013 05:10:40 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay3.apple.com ([17.128.113.83]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNA00HWKXTRT6E0@mail-out.apple.com> for ipv6@ietf.org; Fri, 24 May 2013 05:10:39 -0700 (PDT)
X-AuditID: 11807153-b7f3c6d000007b32-20-519f58bd148c
Received: from [17.153.56.8] (Unknown_Domain [17.153.56.8]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay3.apple.com (Apple SCV relay) with SMTP id 2D.47.31538.EB85F915; Fri, 24 May 2013 05:10:39 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
X-Priority: 3
In-reply-to: <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net>
Date: Fri, 24 May 2013 08:10:36 -0400
Message-id: <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrELMWRmVeSWpSXmKPExsUiONOCQ3d/xPxAgzmvFSyaPvcxWlx7dJ/F 4uXZ90wWR77FOrB4bD35g81j19Ef7B5Llvxk8mjd8Zc9gCWKyyYlNSezLLVI3y6BK2PToYfM Ba99Kx70nmFrYGyz72Lk5JAQMJFYeuYFE4QtJnHh3nq2LkYuDiGBTiaJXRNfM4IkhAXMJeY+ /gxm8wroSVz79pUdxGYW0JHYufUOG4jNJqAm8XtSHyvEIF6JGe1PWUBsTgF7ibP/v4HVsAio Six5cgyohgOo106iYWolxBhtiWULXzNDjLeRWH19JSPEDXuZJBqm/ADrFRFQlDjVMoEFYr6s xOvnb1gmMArMQnLSLCQnzUIydwEj8ypGgaLUnMRKY73EgoKcVL3k/NxNjKCQbSgM3sH4Z5nV IUYBDkYlHt4PevMChVgTy4orcw8xSnAwK4nwrguZHyjEm5JYWZValB9fVJqTWnyIUZqDRUmc 9+fcWYFCAumJJanZqakFqUUwWSYOTqkGxg0Jm/0sTiTnqp+d25F5oupi2J5lFdkzu8+aXlwS unDfqS0/Sz5Fm2m7in9rSmwxqOqxqMsSnvxyWtL5O9NbhRluRCZ+dgq79d6m55zdpzMC92Q0 a+7+D+Z7MEN/kUvApr8lv5Vb3nZ3HZpvO8c5+Fn1y6r3XOvX71wqrvxoXnBP6OfF53j17ZRY ijMSDbWYi4oTAW6w4etVAgAA
Cc: Christian Huitema <huitema@microsoft.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 12:10:45 -0000

Tom,

On 2013-05-24, at 4:00 AM, t.petch <ietfc@btconnect.com> wrote:
> Michael
> 
> I would have been happy to see your erratum rejected in 24 minutes,
> because it is an abuse of process.  It's a bit like submitting an I-D in
> Swahili, nothing wrong with Swahili but quite wrong for the context.
> 
> Erratum are for errors, where the text did not mean what the WG had
> agreed on, where the grammar is wrong, not English, where the text is
> being misinterpreted.
> 
> Changes to the function require an I-D.  Having had that pointed out to
> you, and you might well have not realised the meaning of an erratum in
> the context of the IETF, other SDO may work differently, yet you persist
> in submitting errata; I hope that future ones are rejected as quickly.

First, I *have* submitted errata before, both technical and editorial, for basically all of the IPP specifications, and most have been accepted as posted.  In some cases the technical errata clearly change the meaning of the original text because the original text was plainly wrong.  This is ALLOWED by the currently published process on the RFC Editor's page (which also notes it is a "slippery slope"...):

    http://www.rfc-editor.org/draft-rfc-editor-errata-process-02.txt

I don't say this as an excuse, merely as explanation, and I don't know whether IPP's special status (PWG maintained) or my status (IPP Designated Expert) within the IETF has anything to do with the latitude that has been granted WRT my errata.

As for discussing errata in the relevant IETF WG prior to submission, I was not aware of any formal process in this regards and apologize if I have upset you by starting with the errata reports.  The process described in the above link implies that reporters start on the web portal to initiate such a discussion with the relevant working group, and the standards development process documents that are readily accessible from the IETF web page say nothing about errata or the errata process:

    http://www.ietf.org/about/process-docs.html
    http://tools.ietf.org/html/rfc2026

I can also report that the RFC pages do not provide links to the relevant working group or mailing lists, and that the mailing list links on the main IETF page all take you to the message archives and not to the list subscription page (which I had to search for with Google...)

So again I apologize if I did not follow the process, but honestly I thought I *was*.

(For reference, the PWG process for errata has direct reporting to the relevant workgroup, and that workgroup is identified in every document we produce...)

> When I-Ds are urgently required, then they can become RFC in six months,
> but that only happens when the correct processes are followed.

I'm glad to hear that is possible.  Aside from IPP Everywhere, the in-review Wi-Fi Direct Services Print specification is also affected and in fact depends on IPv6 Link Local addressing.

> 
> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Michael Sweet" <msweet@apple.com>
> To: "Christian Huitema" <huitema@microsoft.com>
> Cc: <brian@innovationslab.net>; <ipv6@ietf.org>; <bob.hinden@gmail.com>;
> <ted.lemon@nominum.com>; "RFC Errata System" <rfc-editor@rfc-editor.org>
> Thursday, May 23, 2013 3:25 PM
> 
> 
>> Christian,
>> 
>> I'm happy to write up a new draft proposing my changes and go through
> that process. I'm not happy that my errata have been summarily rejected
> in less than 24 hours with no time for review.
>> 
>> Consider: hundreds of millions of printers, computers, and mobile
> devices have been certified and shipped with IPv6 link local support
> using the IPvFuture format over the last 8 years.  It took those 8 years
> for the IETF to agree on a new format with serious compatibility and
> interoperability issues with the base IETF standard (STD 66 aka RFC
> 3986), and my errata against the published RFC have been rejected after
> less than 24 hours of discussion.
>> 
>> How do we notify users of RFC 6874 that there are proposed changes, if
> not in pending errata?
>> 
>> How long will it take to get a new draft approved that fixes the
> problems in RFC 6874? I certainly hope the answer is not 8 years...
>> 
>> 
>> On 2013-05-23, at 2:47 AM, Christian Huitema <huitema@microsoft.com>
> wrote:
>> 
>>> Michael, you are asking that the consensus of the WG be reversed.
> The errata process is not the way to handle this. You have to go through
> the motions: write a draft, submit it, get consensus...
>>> 
>>> -----Original Message-----
>>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> Of Michael Sweet
>>> Sent: Wednesday, May 22, 2013 11:10 PM
>>> To: Brian E Carpenter
>>> Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com;
> ted.lemon@nominum.com; RFC Errata System
>>> Subject: Re: [Technical Errata Reported] RFC6874 (3630)
>>> 
>>> Brian,
>>> 
>>> What you're apparently missing is that the client is using the
> zoneid to choose a network interface to route packets to that link local
> address. If the server returns a uri in its response that uses the same
> link local address but without the client's zoneid, then the client will
> be unable to use said uri because it won't know which interface to use.
> Yes the server doesn't care but the client depends on it (for link local
> anyways).
>>> 
>>> This issue is specifically why we (the Printer Working Group)
> require IPP Clients to include the zoneid in the HTTP Host header and
> require IPP Servers to use the Host value in any generated URIs.
>>> 
>>> 
>>> 
>>> Sent from my iPad
>>> 
>>> On 2013-05-23, at 1:26 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>> 
>>>> As far as I can tell this is completely incorrect and the RFC is
>>>> completely correct. It's so wrong that I can't even see how to
> explain
>>>> it. By definition, a ZoneID has no meaning outside the host; its
> only
>>>> effect is to direct the packet to the desired interface on that
> host.
>>>> It has absolutely nothing to do with routing on the network.
>>>> 
>>>> Regards
>>>> Brian Carpenter
>>>> 
>>>> 
>>>> On 23/05/2013 15:51, RFC Errata System wrote:
>>>>> The following errata report has been submitted for RFC6874,
>>>>> "Representing IPv6 Zone Identifiers in Address Literals and
> Uniform Resource Identifiers".
>>>>> 
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
>>>>> 
>>>>> --------------------------------------
>>>>> Type: Technical
>>>>> Reported by: Michael Sweet <msweet@apple.com>
>>>>> 
>>>>> Section: 3
>>>>> 
>>>>> Original Text
>>>>> -------------
>>>>> Such bare "%" signs are for user interface convenience, and need
> to
>>>>> be turned into properly encoded characters (where "%25" encodes
> "%")
>>>>> before the URI is used in any protocol or HTML document.
> However,
>>>>> URIs including a ZoneID have no meaning outside the originating
> node.
>>>>> It would therefore be highly desirable for a browser to remove
> the
>>>>> ZoneID from a URI before including that URI in an HTTP request.
>>>>> 
>>>>> Corrected Text
>>>>> --------------
>>>>> Such bare "%" signs are for user interface convenience, and need
> to
>>>>> be turned into properly encoded characters (where "%25" encodes
> "%")
>>>>> before the URI is used in any protocol or HTML document.  HTTP
> Clients
>>>>> MUST include a ZoneID in any URIs provided in an HTTP request
> since
>>>>> HTTP Servers will need it when generating URIs, otherwise the
> IPv6
>>>>> address will not be routable.
>>>>> 
>>>>> Notes
>>>>> -----
>>>>> The original advice ignores a very real issue: HTTP Servers that
> generate URIs from the client's Host: need to include the Client's
> zoneid in order for the link local address to be usable/routable.
>>>>> 
>>>>> Instructions:
>>>>> -------------
>>>>> This errata is currently posted as "Reported". If necessary,
> please
>>>>> use "Reply All" to discuss whether it should be verified or
> rejected.
>>>>> When a decision is reached, the verifying party (IESG) can log in
> to
>>>>> change the status and edit the report, if necessary.
>>>>> 
>>>>> --------------------------------------
>>>>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
>>>>> --------------------------------------
>>>>> Title               : Representing IPv6 Zone Identifiers in
> Address Literals and Uniform Resource Identifiers
>>>>> Publication Date    : February 2013
>>>>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
>>>>> Category            : PROPOSED STANDARD
>>>>> Source              : IPv6 Maintenance
>>>>> Area                : Internet
>>>>> Stream              : IETF
>>>>> Verifying Party     : IESG
>>>>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> 
>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> 
> 
> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From ietf@rozanak.com  Fri May 24 05:20:31 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EC3921F8793 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:20:31 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-Pr3BDqW1JR for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:20:25 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD8821F89A6 for <ipv6@ietf.org>; Fri, 24 May 2013 05:20:24 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LzswV-1URug32t4l-014GRJ; Fri, 24 May 2013 08:20:23 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001f01ce57c8$83d80090$8b8801b0$@rozanak.com>	<519E539B.9040203@globis.net>	<BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk> <EMEW3|873904f0a39e9fa42dc5e97df56b302fp4NCaM03tjc|ecs.soton.ac.uk|BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|873904f0a39e9fa42dc5e97df56b302fp4NCaM03tjc|ecs.soton.ac.uk|BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk>
Subject: RE: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
Date: Fri, 24 May 2013 14:20:15 +0200
Message-ID: <005c01ce5879$0f2d57c0$2d880740$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlAJd9CgkAWXHjHwCNyoHMQJrIkqbmKRN4HA=
Content-Language: en-us
X-Provags-ID: V02:K0:lj5wxaSsjFX5mD+XCEJMLIg1vsmc2AIIRY9T9aQq6L7 +B5CJwvjWegBDMDaVllesjt6f3AhEqm01fxLroKC0GnCp+Sakt UiLPHPyMAPePrwnxclKwGk6cN6NzYGkfULd5L17qUvHLes1I5E d4cTobD7X64XEtHf8yLoqtj6quX467yHS7hgdFEVRIU9C06x8O 0hvJMrrAN6fOMI++ob4a65PY+h6Kx6qE8JPINEJW8i+q8My8tq 7o5po/nlvURFVF7qOz+6zt9cV6qC50cW5CvFNwntr0Uq0HzuCs F+9ETpO1Zbx8N1MTtjjTu3ouE4l/QU02kq/PCBzVtU0/ZjH1jY 5AojjaNNgvyJ+aO5/vGc=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 12:20:31 -0000

> > In corporate environments it is very important that cross-correlation
> > of log events can occur to support various operational processes (also
> > over longer periods of time and for examining historical records).
> > IPv4 did not randomly rotate end node identifiers in an uncorrelated
> > manner, and the consequences of this new behaviour could be far
reaching.
> 
> Well, I think the jury is out on use of 4941 in enterprise environments.
There
> are advantages and disadvantages. Accountability is still manageable.
> 
> But in general I agree with Ray's points.
> 

If the monitoring is the key role in your network and you have access to the
inside of your whole network, the question is why you sacrifice your users
privacy by having the same IID forever in the same network? You can use a
monitoring system where log the MAC and IP addresses of the pcs. If the IP
addresses changes, you can still monitor them based on their MAC and log
this new IP address for this computer for further usage or any new events
and keep this log for a certain period of time. 

Thanks for your comments.
Regards,
Hosnieh






From john@jlc.net  Fri May 24 05:40:18 2013
Return-Path: <john@jlc.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0D0C21F88D8 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiHT6RK3jYwF for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 05:40:13 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD5B21F85D1 for <ipv6@ietf.org>; Fri, 24 May 2013 05:40:06 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B22A633C27; Fri, 24 May 2013 08:40:05 -0400 (EDT)
Date: Fri, 24 May 2013 08:40:05 -0400
From: John Leslie <john@jlc.net>
To: Ray Hunter <v6ops@globis.net>
Subject: Re: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
Message-ID: <20130524124005.GR23227@verdi>
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <519F0E3B.5010200@globis.net>
User-Agent: Mutt/1.4.1i
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 12:40:18 -0000

Ray Hunter <v6ops@globis.net> wrote:
> 
> I would also like to see some text on whether it is possible/desirable
> for a middleware box to strip unknown headers, or even some known
> headers, rather than making a binary decision to drop or transmit the
> entire packet. If (new) headers are truly optional or experimental, the
> residual stripped packet may still have value e.g. stripping hop by hop
> extension headers on entry to/ egress from a corporate network or
> transit AS. That way the (new) extension headers could be usefully
> deployed in an AS that supports them, but the end to end traffic would
> not be blocked further along the path by firewalls in an AS that does not.

   I had a similar thought -- even going so far as to posit a way to
notate that a header had been stripped...

   I think the answer is we don't want to do that in this document;
nonetheless some folks are likely to try it. I think a mention of the
issue, and a reference to RFC(s) stating the current rules, would help.

   (The prime purpose of this document is creating an IANA registry;
that purpose should not be clouded by discussion of what firewalls
"should" do.)

--
John Leslie <john@jlc.net>

From tjc@ecs.soton.ac.uk  Fri May 24 06:23:17 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 492FF21F8FE8 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 06:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAQ81DpKDuRO for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 06:23:10 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 85FEA21F8F43 for <6man@ietf.org>; Fri, 24 May 2013 06:23:04 -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 r4ODN0JS010266; Fri, 24 May 2013 14:23:00 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4ODN0JS010266
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369401780; bh=RFddU5rEzCd0tY6rXCGr6HawEBA=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=F4BEJOIvrJ5j/jx5F+/mNeK25EqYXnYVU5cpWOKzUSpRW9ShhFifvwNg0bD0CJd2p u7SHALbVDhsG4XFFNvM1ZpE1N5mh6FVkKMRU75UoAl+1aB2Ms0ZmZYJTVOJtQ9oSrU NMe4ae96QAexrTkVUjZdgXk2p1Vu9eBfAOo1AyvE=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4NEN004306221336p ret-id none; Fri, 24 May 2013 14:23:00 +0100
Received: from dhcp-205-236.wireless.soton.ac.uk (dhcp-205-236.wireless.soton.ac.uk [152.78.205.236]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4ODMupt022276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 14:22:57 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519EBBA7.5080300@si6networks.com>
Date: Fri, 24 May 2013 14:22:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|48d469f3a8488f633442e393c2d10dbfp4NEN003tjc|ecs.soton.ac.uk|41CFFE39-9488-4C75-B37A-C6306EA895BB@ecs.soton.ac.uk>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519C46F2.8040406@si6networks.com> <ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <519EBBA7.5080300@si6networks.com> <41CFFE39-9488-4C75-B37A-C6306EA895BB@ecs.soton.ac.uk>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NEN0043062213300; tid=p4NEN004306221336p; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4ODN0JS010266
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "6man-chairs@tools.ietf.org Chairs" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 13:23:17 -0000

Hi,

In-line...

On 24 May 2013, at 02:00, Fernando Gont <fgont@si6networks.com> wrote:

> Hi, Tim,
>=20
> Thanks so much for your feedback! -- Please find my comments =
in-line...
>=20
> On 05/22/2013 10:19 AM, Tim Chown wrote:
>>=20
>> Overall, I think this is good work and should be progressed.
>=20
> Thanks!
>=20
>> First, some general comments:
>>=20
>> You may wish to be clearer earlier in the document (abstract and/or
>> introduction) that your method applies to all prefixes a host may
>> have, including link-local, ULA, and global(s).  As it stands, you
>> only, for example, mention link-locals first in Section 3.
>=20
> Good point. I've tweaked the abstract, and have also clarified this
> point in Section 3.
>=20
>> The implication of the above is that a multihomed host will have
>> different IIDs per ISP it receives a prefix from. This may have
>> privacy advantages in a static device scenario (this is implied, but
>> never stated anywhere that I can see).
>=20
> So... how about a bullet along the lines of:
>=20
> "Since the method specified in this document will result in different
> Interface Identifiers, knowledge/leakage of the Interface Identifier
> employed for the stable address of one prefix will not negatively =
affect
> the security/privacy of the stable addresses configured for other =
prefixes"

OK.

>> There is some focus in your text on why you might disable 4941.
>> That's not that common a practice, esp. in campus networks, or home
>> networks. While some admins may wish to disable 4941 where they can,
>> I think you should promote use of your method with 4941 being
>> perfectly reasonable to use alongside it, rather than saying "because
>> 4941 may be turned off, we need this method". Related, is that in a
>> few places you talk about your method helping to reduce tracking
>> between networks, while in practice using 4941 for static (desktop)
>> devices does have benefits.
>=20
> I'm all for the use of this method along with RFC4941...I was just
> noting that in some scenarios RFC4941 might be turned off not because =
a
> non-desire for privacy, but for operational reasons.
>=20
> I've tweaked the text a bit in the hopes that readers don't get the
> impression that I'm arguing against use of RFC4941. (Most likely, by =
the
> time you read this I'll have posted version -08... so please check =
that
> one... and if there's still room for improvement in this area, I could
> post a -09 version based on your suggestions).

OK, I simply think that you were implying that because many enterprises =
will want to/try to disable 4941, that this was an argument for using =
stable privacy addresses.  In my view, I would certainly use stable =
privacy *and* 4941.

>> Specific comments:
>>=20
>> Section 1:
>>=20
>> In the bullet point "since embedding" you may wish to be clearer that
>> the "pattern" is the IID format caused by, for example, basing the
>> IID on an IEEE identifier.
>=20
> I have added a clarification to that bullet. - Thanks!
>=20
>> "other information collectors", I guess you mean sites running
>> services, e.g. typically through web server logs.
>=20
> This was borrowed from RFC 4941. -- anything to tweak here?

Maybe just add an example, ", e.g. such as addresses in web server logs, =
included in email headers, etc".

>> Not sure what the point about inferring that temporary addresses are
>> in use buys you.=20
>=20
> If you know that they are temporary addresses, you will expect them to
> change. On the other hand, if temporary addresses looked exactly the
> same as stable addresses, you'd have to figure out whether they are
> different nodes, or the same node with a new temporary address.

OK, that's an advantage, but you could still deduce something from the =
addresses that change, and whether the address is used as a source or =
destination address.

>> Do you mean that with a small number of hosts in a
>> subnet you may be able to deduce which devices are which by looking
>> for when their addresses change?
>=20
> Yes.
>=20
>> That doesn't help you identify that same host later or in a different =
network though?
>=20
> If you can continually poll/see/communicate_with the node and detect =
the
> address changes, you might still correlate the activities of a node
> within a network (of course, when the number of nodes increases, =
and/or
> the lifetime of temporary addresses is reduced, it gets much =
trickier).
>=20
> The simple example would be:
> Let's say you see two addresses on a given network. Say, 2001:db8::1 =
and
> 2001:db8::2. All out of the sudden you stop seeing packets from
> 2001:db8::2, but also start seeing packets from 2001:db8::10. -- It
> would all look like 2001:db8::10 is the same node as 2001:db8::2.

OK, but see above.

>> As an aside here, I looked in our network monitoring database, and my
>> desktop Mac over the last month has been seen to use a link-local
>> IPv6 address, many IPv6 privacy addresses, and an IPv4 global
>> address, but not its global SLAAC address.  That's because nothing
>> has connected to it from outside the local subnet. Sure, if we did
>> not have an IPv6 firewall (as Dave pointed out) the host could be
>> scannable due to its "predictable" Mac OUI, but it's interesting that
>> in the last month, my global SLAAC address has never been used. Of
>> course I don't happen to run any advertised services, though if I did
>> my address would most likely be discoverable by looking at the DNS
>> name it is referred to by.
>=20
> The problem here is that once the stable address (or, more =
specifically,
> its IID) becomes known to an attacker, you can be subject to
> host-tracking by active probing. The stable IID might become known to =
an
> attacker because at some point in time you advertised that IPv6 =
address,
> but also because you e.g. shared a network with an attacker.
>=20
> A simple example is that if we attend the same =
conference/cafe/whatever
> and you could learn my stable IID (based on my MAC address). Then you
> check the headers of my emails, and learn the v6 prefixes of the
> networks I typically connect to. And, after that, you could tell =
whether
> I am online by polling KnownPrefixes|IID.
>=20
> An you shouldn't need a firewall to prevent *this*. Actually, strictly
> speaking, the fireall won't prevent this: you can still probe the node
> in different ways that the firewall won't block.

Sure, the above was just an example. But Dave has a point, that if you =
have a default inbound policy at the edge, this type of exposure is =
unlikely, at least from network probes.  A similar argument to having =
protection against externally sourced ND exhaustion attacks the same =
way.  It may be worth stating this in the draft, as I'm sure others will =
point this out in the same way Dave has.

>> Section 3:
>>=20
>> Second main paragraph, you might add "just as per SLAAC today", or
>> words to that effect. I don't think this is any change as such.
>=20
> Agreed. I just wanted to clarify that the requirement of "MUST use =
this
> method for all addresses" does not apply to temporary addresses -- =
since
> they *can* be used in conjunction with
> draft-ietf-6man-stable-privacy-addresses. -- I've moved the sentence =
you
> mention right befre the parenthetical note.
>=20
>> Not sure about mentioning IIDs smaller than 64 bits here. You may
>> wish to more clearly recommend that your method uses 64-bit IIDs?
>=20
> Previous versions of the I-D didn't. But then I was told that there =
was
> no reason to hardcode the IID length in this I-D -- hence I tweaked =
the
> text accordingly.
>=20
> Although I agree that hardcoding the length of IIDs to be 64-bit long
> makes the text clearer.

OK.

>> "Including the SLAAC prefix"... you say the IID then varies across
>> networks, but you may wish to add that the IID will also vary across
>> each prefix the nodes uses (link-local, ULA, each global if
>> multihomed).
>=20
> I've tweaked the text accordingly.
>=20
>> There's a conflict in the next paragraph about "desirable" and "MUST"
>> - which is it?
>=20
> s/desirable/required/ :-) -- fixed!
>=20
>> The comment about MS Windows should perhaps be more orthogonal.  A
>> node IID may be manually configured, it may use DHCP, it may use
>> SLAAC with IEEE identifiers, it may use your method, it may use the
>> method MS Windows uses, or it may even use the tokenised identifier
>> method that I posted a while ago.  It can use any of those, AND use
>> 4941 as well.  But saying "such implementations would not be affected
>> by the method" doesn't sound quite right.
>=20
> The point I was trying to make is that traditional slaac (in terms of =
#
> of nodes) is not as widely deployed as one would expect.

Ah, OK.  I must run your script on my address samples some time :)

>> Section 4:
>>=20
>> Fourth main paragraph, what is the most likely cause of repeated DAD
>> conflicts/failures?  NS/NA DoS?
>=20
> Yes (of course, assuming 64-bit IIDs).

OK, I was wondering if you were implying something else.  That's fine.

>> Is there anything else that would be likely to cause this?  Worth=20
>> elaborating on that when considering tuning the retry limit?
>=20
> My take is that, in a really unlucky scenario, you might get 1
> collision, but no more than that. The value "3" is somewhat arbitrary, =
I
> should say.

OK.

>> Section 7:
>>=20
>> Maybe clarify that the first bullet point is for inbound connections
>> only.
>=20
> That's correct if this is implemented along RFC4941. However, if this =
is
> implemented without RFC4941, this method still prevents such trivial
> host tracking.

OK, I always assume the former, but I appreciate many prefer to disable =
4941 where they can.

>> A fourth bullet point could be that you do not disclose hints about
>> hardware types.
>=20
> Good point. Added!
>=20
>> A fifth could be that IIDs may only be tracked or probed for each
>> prefix the host is known to use, e.g. detection or disclosure of the
>> link-local IID does not compromise the IID used for incoming global
>> connections.  So if you sniff for IPv6 service discovery traffic, for
>> example, you may learn a node's link-local IID, but not be able to
>> deduce its global address.
>=20
> Added as:
>=20
> "Since the method specified in this document will result in different
> Interface Identifiers, knowledge/leakage of the Interface Identifier
> employed for the stable address of one prefix will not negatively =
affect
> the security/privacy of the stable addresses configured for other =
prefixes"

OK.

>> How does your RA "attack" work in practice here?  Do you mean issuing
>> a rogue RA for the same prefix?  We should perhaps assume that robust
>> rogue RA protection is in place, and if not there are many worse
>> things an attacker can do!
>=20
> Agreed. I added this attack vector description, since it was described
> by Christian Huitema... so I added it for completeness sake. Should I
> twek the text? Remove it?

I have no strong view, just noting that if a network permits rogue RAs, =
much worse things can happen.

>> Perhaps note/remind here that RFC4862 says to run DAD per prefix
>> (section 5.4).
>=20
> mmmm... not sure what you mean.

For each different IID generated.  Currently implementations *might* =
assume the IID is the same for link-local and global via traditional =
SLAAC.  RFC4862 notes that you should run DAD on all addresses.

>> Appendix B:
>>=20
>> B.1 you say "one possible attack", then list more than one.
>=20
> Fixed.
>=20
>> B.1.3 Worth any consideration of MIPv6 here? =20
>=20
> It has been years since I last checked MIPv6 (and when I did, I mostly
> just skimmed through it). So... up to you. :-)

Well, nor me, but if you run MIPv6 you're by design wanting to be =
reachable by a persistent address. I guess at the very least you can say =
your method can apply when forming the Home Address during the initial =
bootstrap with the Home Agent. And when the host roams and gets a =
Care-of Address, the IID used to form the CoA at each visited network =
will be different, and different to the IID used for the HoA.  This I =
guess would reduce trackability as you roam, but would be good for a MIP =
guru to comment.

>> The Home Address is
>> obviously trackable, by design, but any Care-of Address could benefit
>> from your approach. Are there mobility methods anywhere else that
>> might assume static IIDs though?
>=20
> You mean "IIDs that are stable across networks"?

Yes, just wondering.

Tim

> P.S.: Please check version -08, and let me know if there are any =
further
> tweaks I should apply.
>=20
> Thanks so much!
>=20
> Best regards,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
>=20
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20


From ietf@rozanak.com  Fri May 24 06:32:57 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95D9421F91CB for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 06:32:57 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6I4PHoiq6UJP for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 06:32:53 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id ABD0621F91CA for <ipv6@ietf.org>; Fri, 24 May 2013 06:32:52 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0MU0ld-1V5tGw0IbZ-00R3op; Fri, 24 May 2013 09:32:49 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001401ce57c6$d93bf750$8bb3e5f0$@rozanak.com>	<3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk> <EMEW3|923fc0fa8e0aff7696bf9637a758a90fp4NCXu03tjc|ecs.soton.ac.uk|3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|923fc0fa8e0aff7696bf9637a758a90fp4NCXu03tjc|ecs.soton.ac.uk|3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk>
Subject: RE: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
Date: Fri, 24 May 2013 15:32:41 +0200
Message-ID: <006401ce5883$2dd6e060$8984a120$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlAJ0huofA2hztmMCoxJ2QJijf8rw
Content-Language: en-us
X-Provags-ID: V02:K0:3V3HzF0QLb9saJ4lzkg9Uhsijt+9JZJH3tau9cQGc01 /6KUBKmKTrG9KaxdMLAbjQoHwChFIRx6RPjLiLVYvSjXy8R7ag SG8oKelDrfxcrZRkno5XXfuwT9n/qff5cGYAwGo5S/Q7FEY8Gh LAQxfu8jsGmOcnDIUp0GDTXNlOh7fdAXhQc67Yirxj1IUVwQZm OiNpCssbXxnB9NidbTgfMBOgTpvo+k4Tw5GPaYyvnFymkcWXWW 34yRnPUSYRpxEeAGZZD0Oh5ZAVJ/X2jmp/bHoRl1/dz4YW388n 1kcEz5rpeHudMhivd8lUTbnmwrjx1+lkIoOM17TqU54/04ZGCa XpUPqWjQmoMcn3xSB1QM=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 13:32:57 -0000

Hi Tim,
>Can you clarify, succinctly, what your proposal adds that you cannot
achieve by a combination
of=A0http://datatracker.ietf.org/doc/draft-ietf-6man-stable-privacy-addre=
sses/
=A0and RFC4941?

I do not want to open up the old discussion here again. If you use RFC =
4941
or in other word you enable the current implementations of RFC 4941 with =
any
other documents, you did not address the problems explained in my draft
about RFC 4941. You just used the current implementations with their =
current
problems. The reason that I wrote this draft was that the "stable =
addresses"
wanted to keep its IID within the same network and not assign several =
IIDs
within the same networks, in contrary with RFC 4941. In my opinion, =
there is
problems of leakage of users' private information such as bank accounts,
names, pictures, etc during the time that the node has the same IID. =
This
problem is more remarkable when the time the node is in the same network =
for
a long time or permanently.=20
RFC 4941 could better handle the privacy consideration but It also has =
some
problems such as:
- still the IID generated based on the MAC might be valid
- cutting the  connections to other nodes when the lifetime of the IID =
is
expired.
-etc



>It seems a key point is that 4941 "only" says SHOULD for the IID
regeneration when the prefix changes. =A0Yet afaics all implementations =
do
this?

Yes because many of them did not choose the best option for IID =
generation
and there might be a correlation between their generated IID which helps =
the
attacker understand this is the same node.

Thanks,
Hosnieh


From internet-drafts@ietf.org  Fri May 24 07:04:17 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA48321F9497; Fri, 24 May 2013 07:04:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbUakrrTwLwi; Fri, 24 May 2013 07:04:17 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A6D421F8E9D; Fri, 24 May 2013 07:04:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130524140417.3320.88007.idtracker@ietfa.amsl.com>
Date: Fri, 24 May 2013 07:04:17 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 14:04:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : Enhanced Duplicate Address Detection
	Author(s)       : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Eli Dart
                          Wes George
                          Carlos Pignataro
	Filename        : draft-ietf-6man-enhanced-dad-03.txt
	Pages           : 12
	Date            : 2013-05-24

Abstract:
   Appendix A of the IPv6 Duplicate Address Detection (DAD) document in
   RFC 4862 discusses Loopback Suppression and DAD.  However, RFC 4862
   does not settle on one specific automated means to detect loopback of
   Neighbor Discovery (ND of RFC 4861) messages used by DAD.  Several
   service provider communities have expressed a need for automated
   detection of looped backed ND messages used by DAD.  This document
   includes mitigation techniques and then outlines the Enhanced DAD
   algorithm to automate detection of looped back IPv6 ND messages used
   by DAD.  For network loopback tests, the Enhanced DAD algorithm
   allows IPv6 to self-heal after a loopback is placed and removed.
   Further, for certain access networks the document automates resolving
   a specific duplicate address conflict.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-enhanced-dad-03


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


From tjc@ecs.soton.ac.uk  Fri May 24 07:43:17 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0512521F9408 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 07:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOlJm8gjE5eo for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 07:43:16 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 37D6121F9401 for <ipv6@ietf.org>; Fri, 24 May 2013 07:43:15 -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 r4OEhF2o001822 for <ipv6@ietf.org>; Fri, 24 May 2013 15:43:15 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4OEhF2o001822
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369406595; bh=2SlJi7+dgzUKNj/6IQv6Y1mLgPc=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=sqHumqbM8Y3yZgI3khwSmFx4ATiF6D1dBSl9nqbst+OyLO/uxXjCdix3UzkTWhGD4 mPY3QlRjETGRjKywjJq3SrQ+CYnPe/fmw2Pz40OXZrB8zpjG5HZP2kW6TPv6rV8gHI 5m3ywEgHTHNoVmO1HBZNWRn/UXKXtuwoPBt9CMVU=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4NFhF04306234482d ret-id none; Fri, 24 May 2013 15:43:15 +0100
Received: from dhcp-205-236.wireless.soton.ac.uk (dhcp-205-236.wireless.soton.ac.uk [152.78.205.236]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OEhBS1009763 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Fri, 24 May 2013 15:43:11 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20130524124005.GR23227@verdi>
Date: Fri, 24 May 2013 15:43:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|5d4d2c0b4b23a0f019091cfa0a4dcf65p4NFhF03tjc|ecs.soton.ac.uk|67CC9520-D050-4870-8A2C-3ECC9462DF7C@ecs.soton.ac.uk>
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <67CC9520-D050-4870-8A2C-3ECC9462DF7C@ecs.soton.ac.uk>
To: 6man <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NFhF043062344800; tid=p4NFhF04306234482d; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4OEhF2o001822
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 14:43:17 -0000

On 24 May 2013, at 13:40, John Leslie <john@jlc.net> wrote:

> Ray Hunter <v6ops@globis.net> wrote:
>>=20
>> I would also like to see some text on whether it is =
possible/desirable
>> for a middleware box to strip unknown headers, or even some known
>> headers, rather than making a binary decision to drop or transmit the
>> entire packet. If (new) headers are truly optional or experimental, =
the
>> residual stripped packet may still have value e.g. stripping hop by =
hop
>> extension headers on entry to/ egress from a corporate network or
>> transit AS. That way the (new) extension headers could be usefully
>> deployed in an AS that supports them, but the end to end traffic =
would
>> not be blocked further along the path by firewalls in an AS that does =
not.
>=20
>   I had a similar thought -- even going so far as to posit a way to
> notate that a header had been stripped...

For that you need a new header... ;)

>   I think the answer is we don't want to do that in this document;
> nonetheless some folks are likely to try it. I think a mention of the
> issue, and a reference to RFC(s) stating the current rules, would =
help.
>=20
>   (The prime purpose of this document is creating an IANA registry;
> that purpose should not be clouded by discussion of what firewalls
> "should" do.)

Yes, the doc should focus on its primary reason for existence.=20

A couple of additional comments.

One is that from time to time there may be security issues raised with =
certain headers, e.g. RH0. These may obviously be raised over time. Is =
there a mechanism to catch these in the IANA registry somehow?

Another is whether there is any use of the "null" header type 59?  Or =
has that been deprecated?  If not, should it be so, given Brian doesn't =
list it.  Or is this viewed in the same category as TCP, etc as header =
types?

Tim


From ietfc@btconnect.com  Fri May 24 08:11:29 2013
Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4CBA21F8605 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.113
X-Spam-Level: 
X-Spam-Status: No, score=-3.113 tagged_above=-999 required=5 tests=[AWL=-0.514, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gF04c9bApLfS for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:11:23 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com [213.199.154.186]) by ietfa.amsl.com (Postfix) with ESMTP id 2AAE121F8532 for <6man@ietf.org>; Fri, 24 May 2013 08:11:22 -0700 (PDT)
Received: from mail207-db8-R.bigfish.com (10.174.8.234) by DB8EHSOBE016.bigfish.com (10.174.4.79) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 15:11:13 +0000
Received: from mail207-db8 (localhost [127.0.0.1])	by mail207-db8-R.bigfish.com (Postfix) with ESMTP id 0EFEF100721; Fri, 24 May 2013 15:11:13 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: PS-13(zz9371I542Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail207-db8 (localhost.localdomain [127.0.0.1]) by mail207-db8 (MessageSwitch) id 1369408269979367_23559; Fri, 24 May 2013 15:11:09 +0000 (UTC)
Received: from DB8EHSMHS028.bigfish.com (unknown [10.174.8.234])	by mail207-db8.bigfish.com (Postfix) with ESMTP id DEEC918004D; Fri, 24 May 2013 15:11:09 +0000 (UTC)
Received: from AMSPRD0711HT002.eurprd07.prod.outlook.com (157.56.250.181) by DB8EHSMHS028.bigfish.com (10.174.4.38) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 15:11:08 +0000
Received: from pc6 (86.173.197.168) by pod51017.outlook.com (10.242.14.163) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 15:10:55 +0000
Message-ID: <02f501ce5890$1d44b4e0$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Fernando Gont <fgont@si6networks.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com><519AD0EF.60600@si6networks.com><87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com><519C46F2.8040406@si6networks.com><ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk><EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <519EBBA7.5080300@si6networks.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-08
Date: Fri, 24 May 2013 16:04:14 +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-Originating-IP: [86.173.197.168]
X-OriginatorOrg: btconnect.com
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 15:11:29 -0000

Fernando

Looks good.

One more technical point, in a raft of lesser ones.

s1
/network, an  infer which addresses/network, and infer which addresses/

/(since the follow different patterns from that of traditional SLAAC
addresses),/
(since they follow different patterns from those of traditional SLAAC
addresses),/

s2
/When employed along "temporary addresses"/
When employed along with "temporary addresses"/

s3
/Identifiers (e.g. such as that specified in /
Identifiers (e.g. such as those specified in/

"Implementations conforming to this specification SHOULD provide the
   means for a system administrator to enable or disable the use of this
   algorithm for generating Interface Identifiers."
As and when the algorithm is disabled or enabled, should the box go back
and regenerate all its addresses?  The previous paragraph implies that
it is a MUST.

" starting from the rightmost bit."
Is that ambiguous?  Would least significant bit be clearer?

"Key lengths of at least 128 bits should be"
Should that be with an entropy of 128 bits?  1024 bit keys are not
always as strong as they first appear:-(

s.7
/limit the ability of an attacker from successfully performing /
limit the ability of an attacker to successfully perform/

Tom Petch

----- Original Message -----
From: "Fernando Gont" <fgont@si6networks.com>
To: "Tim Chown" <tjc@ecs.soton.ac.uk>
Cc: <6man-chairs@tools.ietf.org>; "Fernando Gont"
<fgont@si6networks.com>; <6man@ietf.org>
Sent: Friday, May 24, 2013 2:00 AM



From ietf@rozanak.com  Fri May 24 08:18:50 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F19121F8825 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:18:50 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZyVkHPlmsMOe for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:18:44 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 92DC821F8FDC for <ipv6@ietf.org>; Fri, 24 May 2013 08:18:43 -0700 (PDT)
Received: from kopoli ([141.89.226.146]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0LtpwD-1UVgac0XQL-010utk; Fri, 24 May 2013 11:18:07 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Ray Hunter'" <v6ops@globis.net>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001f01ce57c8$83d80090$8b8801b0$@rozanak.com> <519E539B.9040203@globis.net>
In-Reply-To: <519E539B.9040203@globis.net>
Subject: RE: RE: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
Date: Fri, 24 May 2013 17:17:58 +0200
Message-ID: <006501ce5891$e35258d0$a9f70a70$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlAJd9CgkAWXHjHyYyXtawA==
Content-Language: en-us
X-Provags-ID: V02:K0:JB2JZIlsgazahFlSCjvgWdfFMmYd2DHUiKgYAVBW02y TaJVC2odPIj1RfeeDVnWhLNutQUM68+fT+E4fjOqK+AfE2fYkg cSBITYvrZosdcgo3DvUgtYV5rGTQ0+L2mhHu5SPdiMJN5WIZP/ 11vXJOZKkFYmHI6clqshi2gGI3R/oUALurzMHnbrqNXkmO+56v GIIh45mb23lbYSe6JAMXQVl45b4P9WtqpbgfUqLavdE//AM2Sh ENmFQA5+g9qdJGrWl6tWeB3dNDMOw2ej+yCuYKz42Zul/tW0o3 TpWQxMeqyk0jA0PxRT4YHG0QCIZYJsAdK3c5owZ20BTKaCyWqd QE1U3rUjJZZvp8e88eqo=
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 15:18:50 -0000

> >
> I have read this draft and I don't particularly like it for several
operational
> reasons.
> 
> 1) Use of purely random unpredictable IIDs appears to impose an ISP model
of
> working where there is no trust relationship between the end node and the
> network infrastructure.
> 
> In corporate environments it is very important that cross-correlation of
log
> events can occur to support various operational processes (also over
longer
> periods of time and for examining historical records). IPv4 did not
randomly
> rotate end node identifiers in an uncorrelated manner, and the
consequences
> of this new behaviour could be far reaching.
> Even in an ISP environment, there is a requirement in many countries for a
log
> of identifiers that have been used for communication to be available to
law
> enforcement agencies. It could be argued that maintaining the relationship
> between the /64 prefix and the natural person holding the ISP contract
would
> be sufficient, but some countries might not accept this, and impose a
> requirement to log all IIDs that have been used, which would be a
significant
> burden on storage.

I just wonder why, when you can use a monitoring system to log all your
events (MAC + IP) when you are inside a corporate network, you see this as a
big issue. You can also rotate your logs so that a large amount of storage
is not necessary. Why would you sacrifice your user's privacy over a
logging issue? If you really have no concern about  user privacy,  then that
become another decision and you can use public IP addresses, that are not
generated based on MAC addresses, and use them for an unlimited time which
is explained in the draft. You can use either this draft or any other
approach.

 
> 
> 2) Section 3.1. Updating the IID after DAD has completed may disrupt
existing
> communications and applications.
> 
> Also if there is a collision, simply incrementing the modifier will
guarantee
> another collision if two colliding nodes are operating
draft-rafiee-6man-ra-
> privacy-03.

This is not true. Of course if your two nodes can predict the future, then
that becomes another issue which is not in the scope of my draft : -) . What
is the probability of the node choosing the same modifier  (16 bytes number)
and reading the computer time at the same instant in order to pick up the
same timestamp? And, if there is collision, what is the probability of the
node being able to repeat this process at the same time? 
CPU load and many other factors have an effect on this process which, in
general, makes the probability so low that it can be ignored.

> 3) Section 5 & Section 6 requires dynamic DNS updates. In the event that
an
> implementer wishes to rotate these records for privacy reasons, there may
be
> unexpected consequences in the name space, especially in the presence of
> distributed DNS with e.g. caching only servers. How would they know to
update
> their cached records? I think there's a lot more detail required here on
> treatment of TTL of e.g. AAAA records, plus handling of existing sessions.

Here you are talking about the use of public addresses which is explained in
the draft. About Dynamic Update, I do not believe that today anybody uses
open DNS update or allows nodes to update their DNS records without the use
of a security mechanism. Using security for DDNS is inevitable. So when you
use security for DNS, you can simply use one of the security approaches of
DDNS. One example is  the CGA-TSIG draft for a secure dynamic update and for
observing privacy.  

> Applications using UDP could also be
> problematic: when do they time out?

It is application based and as such the connection can be maintained for as
long as this application needs the connection.  I also have another
suggested  improvement to the draft for application layer connections that
is one of the key topics for discussion in the ra-privacy draft.

> "In cases where the router prefix changes, the node MUST cut the
connection."
> Hmmm unhappy eyeballs and potential negative impact on graceful
> renumbering of RFC2894.

I will change this sentence to the following:  "still can keep the old
connections but MUST use a new IID with the new RAs" . This addresses the
renumbering issue. I will improve this part as I did not consider
renumbering.

> 4) rotating the IID of link local address and other addresses could have
other
> unforeseen operational consequences on e.g. static routes, dynamic routes
that
> point to the end node, ACLs, DSCP QoS, Bandwidth Policing, VPN tunnel
> endpoints, Intrusion Detection Systems, load balancers, outbound firewall
> access authorisation .... everything where the IPv6 address is assumed to
be
> largely time invariant and is used as a key to some other relationship.
I'd like
> some more detail of that.

In the draft there is an explanation about link local addresses that is
different than privacy addresses. This is because it is not really important
to change the local link addresses  when others can see your MAC address.
When you expose your Identity via MAC, then privacy does not make sense.
Here I will give a brief explanation about the other issues. If you are
using VPN, then you can keep your connection for as long as you are using
it. I am not sure, but I think you use bandwidth policy not based on the IP
but based on the usernames or flow based control.  If the application needs
a fixed public address, then the question becomes why would you use  this
draft or any other documents that pertain to privacy?
If we are talking about privacy, then we need to also make changes to the
firewalls, like the way  DDNS does. This all pertains to application
considerations for privacy. When we want to take steps toward privacy, we
need to improve many of the current systems. This will not happen in one or
two days as this or many other drafts will not be implemented in one or two
days.

@ Tim: Sorry for bad English in the last messages. When I use a touch screen
device with a small screen to send messages it is really hard to recheck the
sentences.

Thanks,
Regards,
Hosnieh


From ietfc@btconnect.com  Fri May 24 08:37:16 2013
Return-Path: <ietfc@btconnect.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5030B21F8FE8 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:37:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level: 
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=-0.843, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZE5PSoVnZ5q for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 08:37:11 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com [213.199.154.186]) by ietfa.amsl.com (Postfix) with ESMTP id E43AE21F8F4A for <ipv6@ietf.org>; Fri, 24 May 2013 08:37:10 -0700 (PDT)
Received: from mail118-db8-R.bigfish.com (10.174.8.238) by DB8EHSOBE038.bigfish.com (10.174.4.101) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 15:37:09 +0000
Received: from mail118-db8 (localhost [127.0.0.1])	by mail118-db8-R.bigfish.com (Postfix) with ESMTP id B852A403C4; Fri, 24 May 2013 15:37:09 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I936eI542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah19a27bh172cdfh8275bh8275dh8275chz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail118-db8 (localhost.localdomain [127.0.0.1]) by mail118-db8 (MessageSwitch) id 1369409827400173_16791; Fri, 24 May 2013 15:37:07 +0000 (UTC)
Received: from DB8EHSMHS013.bigfish.com (unknown [10.174.8.241])	by mail118-db8.bigfish.com (Postfix) with ESMTP id 5EDBD3E007D; Fri, 24 May 2013 15:37:07 +0000 (UTC)
Received: from AMSPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.181) by DB8EHSMHS013.bigfish.com (10.174.4.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 15:37:06 +0000
Received: from pc6 (86.173.197.168) by pod51017.outlook.com (10.242.14.162) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 15:37:02 +0000
Message-ID: <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net>
From: t.petch <ietfc@btconnect.com>
To: Michael Sweet <msweet@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
Date: Fri, 24 May 2013 16:31:24 +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-Originating-IP: [86.173.197.168]
X-OriginatorOrg: btconnect.com
Cc: Christian Huitema <huitema@microsoft.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 15:37:16 -0000

---- Original Message -----
From: "Michael Sweet" <msweet@apple.com>
To: "t.petch" <ietfc@btconnect.com>
Cc: "Christian Huitema" <huitema@microsoft.com>; <ipv6@ietf.org>
Sent: Friday, May 24, 2013 1:10 PM
> Tom,
>
> On 2013-05-24, at 4:00 AM, t.petch <ietfc@btconnect.com> wrote:
> > Michael
> >
> > I would have been happy to see your erratum rejected in 24 minutes,
> > because it is an abuse of process.  It's a bit like submitting an
I-D in
> > Swahili, nothing wrong with Swahili but quite wrong for the context.
> >
> > Erratum are for errors, where the text did not mean what the WG had
> > agreed on, where the grammar is wrong, not English, where the text
is
> > being misinterpreted.
> >
> > Changes to the function require an I-D.  Having had that pointed out
to
> > you, and you might well have not realised the meaning of an erratum
in
> > the context of the IETF, other SDO may work differently, yet you
persist
> > in submitting errata; I hope that future ones are rejected as
quickly.
>
> First, I *have* submitted errata before, both technical and editorial,
for basically all of the IPP specifications, and most have been accepted
as posted.  In some cases the technical errata clearly change the
meaning of the original text because the original text was plainly
wrong.  This is ALLOWED by the currently published process on the RFC
Editor's page (which also notes it is a "slippery slope"...):
>
>     http://www.rfc-editor.org/draft-rfc-editor-errata-process-02.txt
>
> I don't say this as an excuse, merely as explanation, and I don't know
whether IPP's special status (PWG maintained) or my status (IPP
Designated Expert) within the IETF has anything to do with the latitude
that has been granted WRT my errata.
>
> As for discussing errata in the relevant IETF WG prior to submission,
I was not aware of any formal process in this regards and apologize if I
have upset you by starting with the errata reports.  The process
described in the above link implies that reporters start on the web
portal to initiate such a discussion with the relevant working group,
and the standards development process documents that are readily
accessible from the IETF web page say nothing about errata or the errata
process:
>
>     http://www.ietf.org/about/process-docs.html
>     http://tools.ietf.org/html/rfc2026
>
> I can also report that the RFC pages do not provide links to the
relevant working group or mailing lists, and that the mailing list links
on the main IETF page all take you to the message archives and not to
the list subscription page (which I had to search for with Google...)
>
> So again I apologize if I did not follow the process, but honestly I
thought I *was*.

Michael

No problem; my defensiveness is because I see the Area Director as the
critical resource in the IETF, and raising an erratum tweaks their tail
in a way that an e-mail to a WG list does not.  Some with an issue to
raise find and start with the main IETF list, where do I go with ...,
and someone will always point them to the right area or WG.

There is nothing wrong with raising an erratum as a first step when it
falls within the IETF's use thereof; it is fine to raise an error if it
really is an error.  In this case, you are referencing an RFC which,
like most such, was extensively discussed on a number of lists, so a lot
of people put a lot of effort into producing what you now see, so to say
it is wrong, well, that may not be the best way to get support for
amending it.

However, if you start with the RFC, by looking at the RFC-Editor pages,
then the summary screen for RFC6874 tells you that the source is 6man,
and clicking on that anchor takes you to a wiki for a Working Group,
6man in fact, which has a list of current work, archives and a charter,
which contains details of how to join the mailing list for 6man.

I did not know this until five minutes ago, but I expected that there
would be a way to make the connection and indeed, there is.

Could it be clearer?  Can't think of anything offhand.

Meanwhile, I don't understand the errata:-(  yes I get the gist, but do
not see the protocol sequence that causes you grief.  Perhaps spelling
it out in a longer e-mail to the 6man list would be a good step forward.
At the back of my mind is the inkling that this may fly in the face of
the IPv6 architecture, that ZoneIDs were carefully defined to have a
limited scope and that what you want to do is in violation of that.
Time will tell.

Tom Petch

PS I have always loved the term RFC; this is not a standard that the
IETF has produced, carved in tablets of stone, but the best that the
IETF has managed to produce so far and would LOVE to hear from anyone
with a better idea, it is a Request For Comments:-)

> (For reference, the PWG process for errata has direct reporting to the
relevant workgroup, and that workgroup is identified in every document
we produce...)
>
> > When I-Ds are urgently required, then they can become RFC in six
months,
> > but that only happens when the correct processes are followed.
>
> I'm glad to hear that is possible.  Aside from IPP Everywhere, the
in-review Wi-Fi Direct Services Print specification is also affected and
in fact depends on IPv6 Link Local addressing.
>
> >
> > Tom Petch
> >
> >
> > ----- Original Message -----
> > From: "Michael Sweet" <msweet@apple.com>
> > To: "Christian Huitema" <huitema@microsoft.com>
> > Cc: <brian@innovationslab.net>; <ipv6@ietf.org>;
<bob.hinden@gmail.com>;
> > <ted.lemon@nominum.com>; "RFC Errata System"
<rfc-editor@rfc-editor.org>
> > Thursday, May 23, 2013 3:25 PM
> >
> >
> >> Christian,
> >>
> >> I'm happy to write up a new draft proposing my changes and go
through
> > that process. I'm not happy that my errata have been summarily
rejected
> > in less than 24 hours with no time for review.
> >>
> >> Consider: hundreds of millions of printers, computers, and mobile
> > devices have been certified and shipped with IPv6 link local support
> > using the IPvFuture format over the last 8 years.  It took those 8
years
> > for the IETF to agree on a new format with serious compatibility and
> > interoperability issues with the base IETF standard (STD 66 aka RFC
> > 3986), and my errata against the published RFC have been rejected
after
> > less than 24 hours of discussion.
> >>
> >> How do we notify users of RFC 6874 that there are proposed changes,
if
> > not in pending errata?
> >>
> >> How long will it take to get a new draft approved that fixes the
> > problems in RFC 6874? I certainly hope the answer is not 8 years...
> >>
> >>
> >> On 2013-05-23, at 2:47 AM, Christian Huitema
<huitema@microsoft.com>
> > wrote:
> >>
> >>> Michael, you are asking that the consensus of the WG be reversed.
> > The errata process is not the way to handle this. You have to go
through
> > the motions: write a draft, submit it, get consensus...
> >>>
> >>> -----Original Message-----
> >>> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On
Behalf
> > Of Michael Sweet
> >>> Sent: Wednesday, May 22, 2013 11:10 PM
> >>> To: Brian E Carpenter
> >>> Cc: brian@innovationslab.net; ipv6@ietf.org; bob.hinden@gmail.com;
> > ted.lemon@nominum.com; RFC Errata System
> >>> Subject: Re: [Technical Errata Reported] RFC6874 (3630)
> >>>
> >>> Brian,
> >>>
> >>> What you're apparently missing is that the client is using the
> > zoneid to choose a network interface to route packets to that link
local
> > address. If the server returns a uri in its response that uses the
same
> > link local address but without the client's zoneid, then the client
will
> > be unable to use said uri because it won't know which interface to
use.
> > Yes the server doesn't care but the client depends on it (for link
local
> > anyways).
> >>>
> >>> This issue is specifically why we (the Printer Working Group)
> > require IPP Clients to include the zoneid in the HTTP Host header
and
> > require IPP Servers to use the Host value in any generated URIs.
> >>>
> >>>
> >>>
> >>> Sent from my iPad
> >>>
> >>> On 2013-05-23, at 1:26 AM, Brian E Carpenter
> > <brian.e.carpenter@gmail.com> wrote:
> >>>
> >>>> As far as I can tell this is completely incorrect and the RFC is
> >>>> completely correct. It's so wrong that I can't even see how to
> > explain
> >>>> it. By definition, a ZoneID has no meaning outside the host; its
> > only
> >>>> effect is to direct the packet to the desired interface on that
> > host.
> >>>> It has absolutely nothing to do with routing on the network.
> >>>>
> >>>> Regards
> >>>> Brian Carpenter
> >>>>
> >>>>
> >>>> On 23/05/2013 15:51, RFC Errata System wrote:
> >>>>> The following errata report has been submitted for RFC6874,
> >>>>> "Representing IPv6 Zone Identifiers in Address Literals and
> > Uniform Resource Identifiers".
> >>>>>
> >>>>> --------------------------------------
> >>>>> You may review the report below and at:
> >>>>> http://www.rfc-editor.org/errata_search.php?rfc=6874&eid=3630
> >>>>>
> >>>>> --------------------------------------
> >>>>> Type: Technical
> >>>>> Reported by: Michael Sweet <msweet@apple.com>
> >>>>>
> >>>>> Section: 3
> >>>>>
> >>>>> Original Text
> >>>>> -------------
> >>>>> Such bare "%" signs are for user interface convenience, and need
> > to
> >>>>> be turned into properly encoded characters (where "%25" encodes
> > "%")
> >>>>> before the URI is used in any protocol or HTML document.
> > However,
> >>>>> URIs including a ZoneID have no meaning outside the originating
> > node.
> >>>>> It would therefore be highly desirable for a browser to remove
> > the
> >>>>> ZoneID from a URI before including that URI in an HTTP request.
> >>>>>
> >>>>> Corrected Text
> >>>>> --------------
> >>>>> Such bare "%" signs are for user interface convenience, and need
> > to
> >>>>> be turned into properly encoded characters (where "%25" encodes
> > "%")
> >>>>> before the URI is used in any protocol or HTML document.  HTTP
> > Clients
> >>>>> MUST include a ZoneID in any URIs provided in an HTTP request
> > since
> >>>>> HTTP Servers will need it when generating URIs, otherwise the
> > IPv6
> >>>>> address will not be routable.
> >>>>>
> >>>>> Notes
> >>>>> -----
> >>>>> The original advice ignores a very real issue: HTTP Servers that
> > generate URIs from the client's Host: need to include the Client's
> > zoneid in order for the link local address to be usable/routable.
> >>>>>
> >>>>> Instructions:
> >>>>> -------------
> >>>>> This errata is currently posted as "Reported". If necessary,
> > please
> >>>>> use "Reply All" to discuss whether it should be verified or
> > rejected.
> >>>>> When a decision is reached, the verifying party (IESG) can log
in
> > to
> >>>>> change the status and edit the report, if necessary.
> >>>>>
> >>>>> --------------------------------------
> >>>>> RFC6874 (draft-ietf-6man-uri-zoneid-06)
> >>>>> --------------------------------------
> >>>>> Title               : Representing IPv6 Zone Identifiers in
> > Address Literals and Uniform Resource Identifiers
> >>>>> Publication Date    : February 2013
> >>>>> Author(s)           : B. Carpenter, S. Cheshire, R. Hinden
> >>>>> Category            : PROPOSED STANDARD
> >>>>> Source              : IPv6 Maintenance
> >>>>> Area                : Internet
> >>>>> Stream              : IETF
> >>>>> Verifying Party     : IESG
> >>>>>
>
>>> --------------------------------------------------------------------
> >>> IETF IPv6 working group mailing list
> >>> ipv6@ietf.org
> >>> Administrative Requests:
https://www.ietf.org/mailman/listinfo/ipv6
>
>>> --------------------------------------------------------------------
> >>
> >> _________________________________________________________
> >> Michael Sweet, Senior Printing System Engineer, PWG Chair
> >>
>
>> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>
>> --------------------------------------------------------------------
> >>
> >
> >
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>



From tjc@ecs.soton.ac.uk  Fri May 24 09:07:34 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8F721F961B for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 09:07:28 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id efY9PbkEfHcS for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 09:07:26 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 8888621F9601 for <ipv6@ietf.org>; Fri, 24 May 2013 09:07:24 -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 r4OG7Mn5028513 for <ipv6@ietf.org>; Fri, 24 May 2013 17:07:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4OG7Mn5028513
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369411642; bh=FPvhmV+m1bktc2tNbj23OZId70g=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=XMG15vNEpzNxgPZZMzrEWno4uRyRc1s36NhJjKN9w2vPF2E3bVi0pM4H/1ta6Oe2Q fmwYLOiqDPXdMSgd4qZzJAF++Y1kZlvKEDEj/8exAsxXN706fiPlJmd6aUDDoNQSOW T87snfut9y2HKbb0bC4ufzTYi12oC4uZt8NQXv+U=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4NH7M0430624802Ab ret-id none; Fri, 24 May 2013 17:07:22 +0100
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4OG7JGS031089 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ipv6@ietf.org>; Fri, 24 May 2013 17:07:19 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <006501ce5891$e35258d0$a9f70a70$@rozanak.com>
Date: Fri, 24 May 2013 17:07:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|09fe86e0eba5e5ceda1ea6badb896bb2p4NH7M03tjc|ecs.soton.ac.uk|426160B1-22EA-415B-BB18-46D4D9F72758@ecs.soton.ac.uk>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001f01ce57c8$83d80090$8b8801b0$@rozanak.com> <519E539B.9040203@globis.net> <006501ce5891$e35258d0$a9f70a70$@rozanak.com> <426160B1-22EA-415B-BB18-46D4D9F72758@ecs.soton.ac.uk>
To: ipv6@ietf.org
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4NH7M043062480200; tid=p4NH7M0430624802Ab; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4OG7Mn5028513
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 16:07:36 -0000

Comments in-line...

On 24 May 2013, at 16:17, Hosnieh Rafiee <ietf@rozanak.com> wrote:
>=20
> I just wonder why, when you can use a monitoring system to log all =
your
> events (MAC + IP) when you are inside a corporate network, you see =
this as a
> big issue. You can also rotate your logs so that a large amount of =
storage
> is not necessary. Why would you sacrifice your user's privacy over a
> logging issue? If you really have no concern about  user privacy,  =
then that
> become another decision and you can use public IP addresses, that are =
not
> generated based on MAC addresses, and use them for an unlimited time =
which
> is explained in the draft. You can use either this draft or any other
> approach.

At our site we do just this; an SNMP-based tool harvests IP/MAC/port =
data from the switches,routers etc.  I agree that it works very well.

That said, I expect quite a few (enterprise) sites will try to disable =
4941. Or if they use ULAs as well, to disable for ULAs for internal =
traffic. That's their choice.=20

The question is just what additional privacy you're delivering. In =
principle, 4941 addresses could be put in the DNS, or could be passed to =
peers to use for communications. Conceptually, it may be simpler to have =
just two classes of address; stable privacy addresses (as per Fernando's =
text) and "temporary" privacy addresses which change over time (RFC =
4941), whether the addresses are used to initiate or receive =
connections.

My current feeling is that we have Fernando's stable privacy draft =
that's getting quite close to being done (I hope :) and we of course =
have 4941.  I would personally prefer to see Fernando's text published, =
and then - if you feel it necessary - you could issue a proposal for any =
additional functionality you believe is needed beyond that, or for =
perceived fixes to 4941. You may have valid points to make, e.g. =
regarding requirements on dynamic DNS when using that, but it would be =
easier to assess them after the publication of Fernando's work.

In the meantime, it would be helpful if your draft listed the existing =
privacy concerns you have, and the key benefits of your proposed =
mechanism(s) as easy-to-parse bullet points in your text.  You can take =
out some of the more general comments about privacy, e.g. the first =
paragraph of the introduction.  Make the abstract more snappy, move the =
points in there to bullet-point concerns in the main body, and make your =
proposed solution clearer.  I think that would help other readers as =
well.  Just a suggestion at least.

>> "In cases where the router prefix changes, the node MUST cut the
> connection."
>> Hmmm unhappy eyeballs and potential negative impact on graceful
>> renumbering of RFC2894.
>=20
> I will change this sentence to the following:  "still can keep the old
> connections but MUST use a new IID with the new RAs" . This addresses =
the
> renumbering issue. I will improve this part as I did not consider
> renumbering.

Check RFC4192 about non-flag day renumbering.  In homenet though, we =
might see such "flash" renumbering.  These are important considerations.

>> 4) rotating the IID of link local address and other addresses could =
have
> other
>> unforeseen operational consequences on e.g. static routes, dynamic =
routes
> that
>> point to the end node, ACLs, DSCP QoS, Bandwidth Policing, VPN tunnel
>> endpoints, Intrusion Detection Systems, load balancers, outbound =
firewall
>> access authorisation .... everything where the IPv6 address is =
assumed to
> be
>> largely time invariant and is used as a key to some other =
relationship.
> I'd like
>> some more detail of that.
>=20
> In the draft there is an explanation about link local addresses that =
is
> different than privacy addresses. This is because it is not really =
important
> to change the local link addresses  when others can see your MAC =
address.
> When you expose your Identity via MAC, then privacy does not make =
sense.

This is a nice property of Fernando's draft. A "random" IID per prefix, =
with non-disclosure of MAC.

> Here I will give a brief explanation about the other issues. If you =
are
> using VPN, then you can keep your connection for as long as you are =
using
> it. I am not sure, but I think you use bandwidth policy not based on =
the IP
> but based on the usernames or flow based control.  If the application =
needs
> a fixed public address, then the question becomes why would you use  =
this
> draft or any other documents that pertain to privacy?
> If we are talking about privacy, then we need to also make changes to =
the
> firewalls, like the way  DDNS does. This all pertains to application
> considerations for privacy. When we want to take steps toward privacy, =
we
> need to improve many of the current systems. This will not happen in =
one or
> two days as this or many other drafts will not be implemented in one =
or two
> days.

Well, there are many knock-on effects of peers changing IP addresses =
over time. Many of these have been discussed in the context of =
renumbering.

> @ Tim: Sorry for bad English in the last messages. When I use a touch =
screen
> device with a small screen to send messages it is really hard to =
recheck the
> sentences.

Actually, Ray wrote the comments above, but I'm impressed how much you =
wrote on a small screen :)

Tim

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


From v6ops@globis.net  Fri May 24 09:54:08 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B41321F95FD for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 09:54:08 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rA92efQOmJhW for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 09:54:07 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA4421F8D70 for <ipv6@ietf.org>; Fri, 24 May 2013 09:54:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 4EDBF8700D7; Fri, 24 May 2013 18:53:51 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyopShv1Lu2H; Fri, 24 May 2013 18:53:51 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 289C48700D6; Fri, 24 May 2013 18:53:51 +0200 (CEST)
Message-ID: <519F9B18.9070907@globis.net>
Date: Fri, 24 May 2013 18:53:44 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: RE: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001f01ce57c8$83d80090$8b8801b0$@rozanak.com>	<519E539B.9040203@globis.net>	<BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk> <EMEW3|873904f0a39e9fa42dc5e97df56b302fp4NCaM03tjc|ecs.soton.ac.uk|BBC03805-F5AE-43EE-AF5F-B7DBDD58C97A@ecs.soton.ac.uk> <005c01ce5879$0f2d57c0$2d880740$@rozanak.com>
In-Reply-To: <005c01ce5879$0f2d57c0$2d880740$@rozanak.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'Tim Chown' <tjc@ecs.soton.ac.uk>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 16:54:08 -0000

Hosnieh Rafiee wrote:
>>> In corporate environments it is very important that cross-correlation
>>> of log events can occur to support various operational processes (also
>>> over longer periods of time and for examining historical records).
>>> IPv4 did not randomly rotate end node identifiers in an uncorrelated
>>> manner, and the consequences of this new behaviour could be far
> reaching.
>> Well, I think the jury is out on use of 4941 in enterprise environments.
> There
>> are advantages and disadvantages. Accountability is still manageable.
>>
>> But in general I agree with Ray's points.
>>
>
> If the monitoring is the key role in your network and you have access to the
> inside of your whole network, the question is why you sacrifice your users
> privacy by having the same IID forever in the same network? You can use a
> monitoring system where log the MAC and IP addresses of the pcs. If the IP
> addresses changes, you can still monitor them based on their MAC and log
> this new IP address for this computer for further usage or any new events
> and keep this log for a certain period of time. 
>
> Thanks for your comments.
> Regards,
> Hosnieh
>
>

I think you greatly underestimate and trivialise the proliferation of
operational processes and systems that use an IP address as a node
identifier and as a key to other data, and that rely on it being largely
time invariant/ stable (at the very least for a decent caching interval
so that it doesn't have to be resolved for every inbound
packet/connection being processed, or for the time that the machine is
switched on). I think that risk is well worth noting in your draft.

You only have to look at something like ~/.ssh/known_hosts, where a flat
file uses an IP address to associate a server with a public key, to see
how widespread this practice is. If you want it to stop this practice 1)
it's going to be a long and painful process 2) you'll probably need to
provide a viable alternative source for node identifiers and/or user
identifiers.

Otherwise if something like my SSH server process decides to time cycle
it's IP address and dynamically update DNS due to a lifetime timing out
1) it is likely that every single long-lived remote SSH session will be
broken at some point,
2) upon reconnection to the new server address registered in DNS, all
users will likely be asked to relearn/reconfirm the trust relationship
with the server.

That trust association can't be trivially repaired for an automatic/cron
process without an alternative trusted source of node identifier.

This is just one of a myriad of examples.

regards,
RayH

From huitema@microsoft.com  Fri May 24 10:45:49 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E2921F9697 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 10:45:49 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvKWTJowXzcs for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 10:45:42 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 6C03821F9600 for <ipv6@ietf.org>; Fri, 24 May 2013 10:45:39 -0700 (PDT)
Received: from BN1BFFO11FD014.protection.gbl (10.58.52.200) by BN1BFFO11HUB029.protection.gbl (10.58.53.139) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 17:45:37 +0000
Received: from TK5EX14MLTC104.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD014.mail.protection.outlook.com (10.58.53.74) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 17:45:37 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.80]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.02.0318.003; Fri, 24 May 2013 17:45:23 +0000
From: Christian Huitema <huitema@microsoft.com>
To: t.petch <ietfc@btconnect.com>, Michael Sweet <msweet@apple.com>
Subject: RE: [Technical Errata Reported] RFC6874 (3630)
Thread-Topic: [Technical Errata Reported] RFC6874 (3630)
Thread-Index: AQHOV2lfBWe4Nw564U2vCg0gl6fTYpkSPXAAgAAME4CAAAnUUIAAgJ+AgAEoRieAAERWAIAAObvygAAh3RA=
Date: Fri, 24 May 2013 17:45:23 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net>
In-Reply-To: <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.78]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(16406001)(46102001)(46406003)(74502001)(54356001)(51856001)(47776003)(81342001)(74662001)(20776003)(47976001)(54316002)(50986001)(59766001)(33656001)(76482001)(77982001)(4396001)(49866001)(56776001)(65816001)(79102001)(47736001)(63696002)(81542001)(69226001)(56816002)(55846006)(31966008)(74706001)(66066001)(47446002)(80022001)(74366001)(23726002)(53806001)(6806003)(50466002)(74876001); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB029; H:TK5EX14MLTC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 17:45:49 -0000

Can we move from the process discussion to the technical discussion?

Michael raised an interesting issue, and we have to analyze it. The consens=
us of the working group so far is that interface identifiers are private to=
 the host, that any leakage outside the host should be prevented, and that =
a way to prevent that leakage is to ask proxies to erase them whenever they=
 have an opportunity. Michael points that some servers take an opposite app=
roach, want to record the interface from which the host called them, and wa=
nt to ensure that further calls in the same session use exactly the same in=
terface. That seems that a fairly legitimate debate, and I can see two alte=
rnatives -- one would be to reaffirm the old guidance and provides alternat=
ive to ensure session continuity, and the other would be to reverse the gui=
dance and accept that the layer violation performed by servers is just fine=
.

-- Christian Huitema




From kerlyn2001@gmail.com  Fri May 24 10:58:35 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5261321F9635 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 10:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.661
X-Spam-Level: 
X-Spam-Status: No, score=-102.661 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LapZsbOF28Pb for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 10:58:27 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id BFE6B21F9622 for <ipv6@ietf.org>; Fri, 24 May 2013 10:58:26 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so6511409oah.21 for <ipv6@ietf.org>; Fri, 24 May 2013 10:58:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SXnq8d+p0u8vIq/NzynNAHhjPoIc8SHFlJNQdlwJz4w=; b=ZF5KyBdMBjzN2JeAeR/RleC3hBQP65kWWzgxiz+fM3ieM5g40X72SPP9AQ7cq/XTk8 y3jylAGvYCpiJ/gcur8C4CBkiIigMoer4J7+R+N8d2yoMyPgtndtfHIrSRzxtllXOM+b 7z4wCvtnTuKNYM0BnelxXvt3sT/9VZNOJNkXOzOS949KJ6Xgyt8s8FOjtgyJyR8XPLpS I/e3h9WimhfQDsVqT2OA+KA1uOizowXztwlncLQq8J5s+N9BPcnlRjhmMiv3yaJ200qr 7HlyjCugA7jus9bMp3hCCmR/YXanxijG1gy/mRmskn2R+/vGvrXLk3+o1Q8WEhfprjWC Ws9A==
MIME-Version: 1.0
X-Received: by 10.60.58.4 with SMTP id m4mr12454487oeq.41.1369418306336; Fri, 24 May 2013 10:58:26 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.148.197 with HTTP; Fri, 24 May 2013 10:58:26 -0700 (PDT)
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>
Date: Fri, 24 May 2013 13:58:26 -0400
X-Google-Sender-Auth: dHeg30vaqruyprzi89KgbBUNXzM
Message-ID: <CABOxzu1xpbBvd_aWJEHD9qTTmG_Ly0=Pry9X4PqY+xBLMf01Vw@mail.gmail.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Kerry Lynn <kerlyn@ieee.org>
To: Michael Sweet <msweet@apple.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=089e0158b0aeb30a8d04dd7a8be9
Cc: Christian Huitema <huitema@microsoft.com>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 17:58:35 -0000

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

Michael,

Can I echo what Tom and Christian have said - that you join the 6man working
group and start by clearly and concisely stating the problem that this RFC
poses
for your application and how you suggest we fix it?

When you speak of "hundreds of millions of printers..." it gives the
impression that
the RFC makes illegal something that printers have been doing for some
time.  If
so, can you also provide relevant references to the deployed functionality
that you
believe this RFC makes illegal?

-K-

On Fri, May 24, 2013 at 1:45 PM, Christian Huitema <huitema@microsoft.com>wrote:

> Can we move from the process discussion to the technical discussion?
>
> Michael raised an interesting issue, and we have to analyze it. The
> consensus of the working group so far is that interface identifiers are
> private to the host, that any leakage outside the host should be prevented,
> and that a way to prevent that leakage is to ask proxies to erase them
> whenever they have an opportunity. Michael points that some servers take an
> opposite approach, want to record the interface from which the host called
> them, and want to ensure that further calls in the same session use exactly
> the same interface. That seems that a fairly legitimate debate, and I can
> see two alternatives -- one would be to reaffirm the old guidance and
> provides alternative to ensure session continuity, and the other would be
> to reverse the guidance and accept that the layer violation performed by
> servers is just fine.
>
> -- Christian Huitema
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

Michael,<br><br>Can I echo what Tom and Christian have said - that you join=
 the 6man working<br>group and start by clearly and concisely stating the p=
roblem that this RFC poses<br>for your application and how you suggest we f=
ix it?<br>
<br>When you speak of &quot;hundreds of millions of printers...&quot; it gi=
ves the impression that<br>the RFC makes illegal something that printers ha=
ve been doing for some time.=A0 If<br>so, can you also provide relevant ref=
erences to the deployed functionality that you<br>
believe this RFC makes illegal?<br><br>-K-<br><br><div class=3D"gmail_quote=
">On Fri, May 24, 2013 at 1:45 PM, Christian Huitema <span dir=3D"ltr">&lt;=
<a href=3D"mailto:huitema@microsoft.com" target=3D"_blank">huitema@microsof=
t.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Can we move from the process discussion to t=
he technical discussion?<br>
<br>
Michael raised an interesting issue, and we have to analyze it. The consens=
us of the working group so far is that interface identifiers are private to=
 the host, that any leakage outside the host should be prevented, and that =
a way to prevent that leakage is to ask proxies to erase them whenever they=
 have an opportunity. Michael points that some servers take an opposite app=
roach, want to record the interface from which the host called them, and wa=
nt to ensure that further calls in the same session use exactly the same in=
terface. That seems that a fairly legitimate debate, and I can see two alte=
rnatives -- one would be to reaffirm the old guidance and provides alternat=
ive to ensure session continuity, and the other would be to reverse the gui=
dance and accept that the layer violation performed by servers is just fine=
.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Christian Huitema<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><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: <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>

--089e0158b0aeb30a8d04dd7a8be9--

From msweet@apple.com  Fri May 24 11:28:30 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE4A421F9403 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.191
X-Spam-Level: 
X-Spam-Status: No, score=-108.191 tagged_above=-999 required=5 tests=[AWL=2.408, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zx6GbpYD00wd for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:28:24 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id A1F5311E80E2 for <ipv6@ietf.org>; Fri, 24 May 2013 11:28:24 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay3.apple.com ([17.128.113.83]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNB00HMZFA1T621@mail-out.apple.com> for ipv6@ietf.org; Fri, 24 May 2013 11:27:59 -0700 (PDT)
X-AuditID: 11807153-b7f3c6d000007b32-f0-519fb12ed5f2
Received: from [17.153.56.8] (Unknown_Domain [17.153.56.8]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay3.apple.com (Apple SCV relay) with SMTP id EB.D5.31538.E21BF915; Fri, 24 May 2013 11:27:59 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>
Date: Fri, 24 May 2013 14:27:56 -0400
Message-id: <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUiONOCQ1d/4/xAgwdTFSyaPvcxWlx7dJ/F 4uXZ90wWR77FOrB4bD35g81j19Ef7B5Llvxk8mjd8Zc9gCWKyyYlNSezLLVI3y6BK2P13Wb2 gvViFbvvPGdqYJwq1MXIySEhYCLx/staZghbTOLCvfVsILaQQCeTxL2PoiC2sIC5xNzHnxlB bF4BPYlr376yg9jMAloSN/69ZAKx2QTUJH5P6mMFsTkFEiWmr7sGNodFQFXi9oSvrBD1bhKT DzxggbC1JZYtfM0MMdNGYnb3HqA5XEB7vzFL7Hj5CKxBREBXYl/LQVaI42QlXj9/wzKBkX8W kjtmIbljFpK5CxiZVzEKFKXmJFYa6yUWFOSk6iXn525iBIVmQ2HwDsY/y6wOMQpwMCrx8AqU zw8UYk0sK67MPcQowcGsJMKbuBAoxJuSWFmVWpQfX1Sak1p8iFGag0VJnPfn3FmBQgLpiSWp 2ampBalFMFkmDk6pBsZlG6deKjz0Yb73hetf+QuC1uh+iPf5vrMwcLswQ8m1Dxsn25+bnNkq 68baPcmqOD53tdyusmZbhi1rLnP+/DRh06zp5mqTLnk/un6DKfy77aPt5mppG1+yNFueYl6R ZD53IqNxqyLXAa7qgzN2G/ltdd96+VjRyy75M5prPytKNHjvy53CcWylEktxRqKhFnNRcSIA KKGlVUkCAAA=
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 18:28:31 -0000

Christian,

On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com> wrote:
> Can we move from the process discussion to the technical discussion?
> 
> Michael raised an interesting issue, and we have to analyze it. The consensus of the working group so far is that interface identifiers are private to the host, that any leakage outside the host should be prevented, and that a way to prevent that leakage is to ask proxies to erase them whenever they have an opportunity. Michael points that some servers take an opposite approach, want to record the interface from which the host called them, and want to ensure that further calls in the same session use exactly the same interface. That seems that a fairly legitimate debate, and I can see two alternatives -- one would be to reaffirm the old guidance and provides alternative to ensure session continuity, and the other would be to reverse the guidance and accept that the layer violation performed by servers is just fine.


(the following is printer-centric, but the same applies to network video cameras and other embedded network devices)

Some background: HTTP and IPP services in printers include absolute URIs in the content they return. For IPP this can be http/https URLs to the printer's web page, ICC profiles, and other resources, along with the ipp/ipps URIs that the printer supports. For HTTP the most common are https URLs for "secure" areas of the printer's web interface.  Because a printer is often known by multiple names and addresses ("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation guidance (and in IPP Everywhere, this is a conformance requirement) is that the server use the HTTP Host header provided in the request in the host/address field of its responses, subject to the usual security considerations (SHOULD validate Host value, etc.)  This allows the client to use the name or address it can resolve/connect to and makes sure that the printer-generated absolute URIs lead back to same printer.

All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".

What I propose is that we change the wording to allow the zoneid in the Host header but not in the Request-URI.  HTTP proxies would be required to strip any zoneid information in the Host header.  HTTP servers would be required to ignore any zoneid information for purposes of address validation but include it for any absolute URIs to the server they generate.

Thoughts?

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From huitema@microsoft.com  Fri May 24 11:42:12 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246F721F944F for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:42:12 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DgVxHheh+7Ii for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:42:05 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id E0A3D11E80E6 for <ipv6@ietf.org>; Fri, 24 May 2013 11:41:53 -0700 (PDT)
Received: from BL2FFO11FD015.protection.gbl (10.173.161.201) by BL2FFO11HUB039.protection.gbl (10.173.160.245) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 18:41:51 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD015.mail.protection.outlook.com (10.173.160.223) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 18:41:50 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.80]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Fri, 24 May 2013 18:41:34 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Michael Sweet <msweet@apple.com>
Subject: RE: [Technical Errata Reported] RFC6874 (3630)
Thread-Topic: [Technical Errata Reported] RFC6874 (3630)
Thread-Index: AQHOV2lfBWe4Nw564U2vCg0gl6fTYpkSPXAAgAAME4CAAAnUUIAAgJ+AgAEoRieAAERWAIAAObvygAAh3RCAAA3VAIAAA1bA
Date: Fri, 24 May 2013 18:41:33 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0FF62E8B@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
In-Reply-To: <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.78]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(46034005)(199002)(189002)(80022001)(47776003)(79102001)(65816001)(23726002)(63696002)(66066001)(47446002)(50466002)(20776003)(74502001)(74366001)(74706001)(74876001)(54356001)(55846006)(56776001)(77982001)(69226001)(54316002)(56816002)(50986001)(76482001)(46102001)(31966008)(81342001)(53806001)(4396001)(49866001)(47976001)(74662001)(47736001)(33656001)(51856001)(59766001)(6806003)(16406001)(46406003)(81542001)(44976003); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB039; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 18:42:12 -0000

> Some background: HTTP and IPP services in printers include absolute URIs =
in the content they return. For IPP this can be http/https URLs to the prin=
ter's web page, ICC profiles, and other resources, along with the ipp/ipps =
URIs that the printer supports. For HTTP the most common are https URLs for=
 "secure" areas of the printer's web interface.  Because a printer is often=
 known by multiple names and addresses ("printer.local.", "printer.example.=
com.", 192.168.0.100, fe80::1234, etc.), the implementation guidance (and i=
n IPP Everywhere, this is a conformance requirement) is that the server use=
 the HTTP Host header provided in the request in the host/address field of =
its responses, subject to the usual security considerations (SHOULD validat=
e Host value, etc.)  This allows the client to use the name or address it c=
an resolve/connect to and makes sure that the printer-generated absolute UR=
Is lead back to same printer.

> All of this falls apart with link-local addresses and RFC 6874.  Because =
the client is required to remove the zoneid from the outgoing request, the =
URIs it gets back from the server are no longer "reachable".

Do you have this problem only with link local addresses, or with some other=
 addresses as well?

-- Christian Huitema



From kerlyn2001@gmail.com  Fri May 24 11:51:51 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 592DA21F8AF4 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level: 
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ea9brZI4JUrY for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 11:51:50 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A06B221F95FB for <ipv6@ietf.org>; Fri, 24 May 2013 11:51:47 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so2589551obc.6 for <ipv6@ietf.org>; Fri, 24 May 2013 11:51:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UUmzW4BBsdEqQqic2th8PgCAW+9cJEvY44FjwyB13Jw=; b=0qVGcAXRAkZjDZD+8FZW5X82NGvQDQFr0gAipG1GHWrSZyS7oFam3G0OOkT70tsRpr X31/XLix1cFwNrysHSWfQirlduNZ0C+hVd52Ljd0Xh59DWOjMmp+BKqmLRYLhhPkcTzq SOsZpAIvqCI7kUwiIslNGHQRXQJkWbZkBpxYr/Au3S3tRLKRgCsDPQBzqA9A+hcJUuQm lhJzrAFbcZPK+mSSlzyvP9rVkfeuBkQAP1AQqAodSdsnly2vvCEL+6SdkEK96xqaQafp AlDOMuUZaBSytD71Fa+DUAZfxKWsS22zQ/vPdNVBnrUbXPMV3YZzIL/jxMnylma+ayzU 66Jg==
MIME-Version: 1.0
X-Received: by 10.182.125.4 with SMTP id mm4mr12573595obb.63.1369421507179; Fri, 24 May 2013 11:51:47 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.148.197 with HTTP; Fri, 24 May 2013 11:51:47 -0700 (PDT)
In-Reply-To: <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
Date: Fri, 24 May 2013 14:51:47 -0400
X-Google-Sender-Auth: _1KmWeIefFY3KbqlDBF-VXryqHM
Message-ID: <CABOxzu1qrPiPKQiqsS-TizCJsrJ+ONKBGkr3VEvaPD-AV8Tk5g@mail.gmail.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Kerry Lynn <kerlyn@ieee.org>
To: Michael Sweet <msweet@apple.com>
Content-Type: multipart/alternative; boundary=089e0118413e7bbfc304dd7b4a7e
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 18:51:52 -0000

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

On Fri, May 24, 2013 at 2:27 PM, Michael Sweet <msweet@apple.com> wrote:

> Christian,
>
> On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com>
> wrote:
> > Can we move from the process discussion to the technical discussion?
> >
> > Michael raised an interesting issue, and we have to analyze it. The
> consensus of the working group so far is that interface identifiers are
> private to the host, that any leakage outside the host should be prevented,
> and that a way to prevent that leakage is to ask proxies to erase them
> whenever they have an opportunity. Michael points that some servers take an
> opposite approach, want to record the interface from which the host called
> them, and want to ensure that further calls in the same session use exactly
> the same interface. That seems that a fairly legitimate debate, and I can
> see two alternatives -- one would be to reaffirm the old guidance and
> provides alternative to ensure session continuity, and the other would be
> to reverse the guidance and accept that the layer violation performed by
> servers is just fine.
>
>
> (the following is printer-centric, but the same applies to network video
> cameras and other embedded network devices)
>
> Some background: HTTP and IPP services in printers include absolute URIs
> in the content they return. For IPP this can be http/https URLs to the
> printer's web page, ICC profiles, and other resources, along with the
> ipp/ipps URIs that the printer supports. For HTTP the most common are https
> URLs for "secure" areas of the printer's web interface.  Because a printer
> is often known by multiple names and addresses ("printer.local.", "
> printer.example.com.", 192.168.0.100, fe80::1234, etc.), the
> implementation guidance (and in IPP Everywhere, this is a conformance
> requirement) is that the server use the HTTP Host header provided in the
> request in the host/address field of its responses, subject to the usual
> security considerations (SHOULD validate Host value, etc.)  This allows the
> client to use the name or address it can resolve/connect to and makes sure
> that the printer-generated absolute URIs lead back to same printer.
>
> All of this falls apart with link-local addresses and RFC 6874.  Because
> the client is required to remove the zoneid from the outgoing request, the
> URIs it gets back from the server are no longer "reachable".
>
> Just so we're clear, I assume this does NOT work today with link-local
IPv6 addresses (because no print client yet
constructs a Host URI with link-local address and zoneID according to RFC
6874)?  And you're saying that RFC 6874
does not improve on the current situation?

-K-

What I propose is that we change the wording to allow the zoneid in the
> Host header but not in the Request-URI.  HTTP proxies would be required to
> strip any zoneid information in the Host header.  HTTP servers would be
> required to ignore any zoneid information for purposes of address
> validation but include it for any absolute URIs to the server they generate.
>
> Thoughts?
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

On Fri, May 24, 2013 at 2:27 PM, Michael Sweet <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:msweet@apple.com" target=3D"_blank">msweet@apple.com</a>&gt;</s=
pan> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Christian,<br>
<div class=3D"im"><br>
On 2013-05-24, at 1:45 PM, Christian Huitema &lt;<a href=3D"mailto:huitema@=
microsoft.com">huitema@microsoft.com</a>&gt; wrote:<br>
&gt; Can we move from the process discussion to the technical discussion?<b=
r>
&gt;<br>
&gt; Michael raised an interesting issue, and we have to analyze it. The co=
nsensus of the working group so far is that interface identifiers are priva=
te to the host, that any leakage outside the host should be prevented, and =
that a way to prevent that leakage is to ask proxies to erase them whenever=
 they have an opportunity. Michael points that some servers take an opposit=
e approach, want to record the interface from which the host called them, a=
nd want to ensure that further calls in the same session use exactly the sa=
me interface. That seems that a fairly legitimate debate, and I can see two=
 alternatives -- one would be to reaffirm the old guidance and provides alt=
ernative to ensure session continuity, and the other would be to reverse th=
e guidance and accept that the layer violation performed by servers is just=
 fine.<br>

<br>
<br>
</div>(the following is printer-centric, but the same applies to network vi=
deo cameras and other embedded network devices)<br>
<br>
Some background: HTTP and IPP services in printers include absolute URIs in=
 the content they return. For IPP this can be http/https URLs to the printe=
r&#39;s web page, ICC profiles, and other resources, along with the ipp/ipp=
s URIs that the printer supports. For HTTP the most common are https URLs f=
or &quot;secure&quot; areas of the printer&#39;s web interface. =A0Because =
a printer is often known by multiple names and addresses (&quot;printer.loc=
al.&quot;, &quot;<a href=3D"http://printer.example.com" target=3D"_blank">p=
rinter.example.com</a>.&quot;, 192.168.0.100, fe80::1234, etc.), the implem=
entation guidance (and in IPP Everywhere, this is a conformance requirement=
) is that the server use the HTTP Host header provided in the request in th=
e host/address field of its responses, subject to the usual security consid=
erations (SHOULD validate Host value, etc.) =A0This allows the client to us=
e the name or address it can resolve/connect to and makes sure that the pri=
nter-generated absolute URIs lead back to same printer.<br>

<br>
All of this falls apart with link-local addresses and RFC 6874. =A0Because =
the client is required to remove the zoneid from the outgoing request, the =
URIs it gets back from the server are no longer &quot;reachable&quot;.<br>

<br></blockquote><div>Just so we&#39;re clear, I assume this does NOT work =
today with link-local IPv6 addresses (because no print client yet<br>constr=
ucts a Host URI with link-local address and zoneID according to RFC 6874)?=
=A0 And you&#39;re saying that RFC 6874<br>
does not improve on the current situation?<br><br>-K-<br><br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
What I propose is that we change the wording to allow the zoneid in the Hos=
t header but not in the Request-URI. =A0HTTP proxies would be required to s=
trip any zoneid information in the Host header. =A0HTTP servers would be re=
quired to ignore any zoneid information for purposes of address validation =
but include it for any absolute URIs to the server they generate.<br>

<br>
Thoughts?<br>
<div class=3D"im HOEnZb"><br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">-----------------------------=
---------------------------------------<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>
</div></div></blockquote></div><br>

--089e0118413e7bbfc304dd7b4a7e--

From msweet@apple.com  Fri May 24 12:09:09 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F55521E8054 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.431
X-Spam-Level: 
X-Spam-Status: No, score=-108.431 tagged_above=-999 required=5 tests=[AWL=2.168, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRN0aymjMMV4 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:09:03 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC8E11E80F5 for <ipv6@ietf.org>; Fri, 24 May 2013 12:09:03 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNB00H75H5AT671@mail-out.apple.com> for ipv6@ietf.org; Fri, 24 May 2013 12:09:02 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-df-519fbaccac2e
Received: from [17.153.56.8] (Unknown_Domain [17.153.56.8]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id F2.84.31158.DCABF915; Fri, 24 May 2013 12:09:02 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <C91E67751B1EFF41B857DE2FE1F68ABA0FF62E8B@TK5EX14MBXC273.redmond.corp.microsoft.com>
Date: Fri, 24 May 2013 15:08:59 -0400
Message-id: <70C01E63-6201-4604-BB66-C11753CF3FD3@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF62E8B@TK5EX14MBXC273.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKLMWRmVeSWpSXmKPExsUiONOCQ/fcrvmBBj+uMFk0fe5jtLj26D6L xcuz75ksjnyLdWDx2HryB5vHrqM/2D2WLPnJ5NG64y97AEsUl01Kak5mWWqRvl0CV0brf/OC iawVW87UNTBOZuli5OSQEDCROHj6KBuELSZx4d56IJuLQ0igk0nizP2zYEXCAuYScx9/ZgSx eQX0JK59+8oOYjMLaEnc+PeSCcRmE1CT+D2pjxXE5hRIlJi5eCNYnEVAVWLG5C9Q9W4Skw88 YIGwtSWWLXzNDDHTRmL3rLWMEIv/sEicffYQrEFEQFdiX8tBVojrZCVeP3/DMoGRfxaSO2Yh uWMWkrkLGJlXMQoUpeYkVprqJRYU5KTqJefnbmIEBWZDYcQOxv/LrA4xCnAwKvHwCpTPDxRi TSwrrsw9xCjBwawkwiuzEyjEm5JYWZValB9fVJqTWnyIUZqDRUmc99fcWYFCAumJJanZqakF qUUwWSYOTqkGxoZ7+Vlr53z+xWO3gDn6dU+qh/m7I88X8Ur/rN3moGTgk/iG41GadnJM64J7 NW9j7F/djd56tV0wWG2hWP+Hl6aBmoe56+/5Z59UnyJbvsr2hauj4/aTx4PXHamLKfOsnM0p /lvFU6vo1vHjjbIOiYeC7lgY2e7n+3vvFsMkNdnpovOvMzupKbEUZyQaajEXFScCADOSkiNI	AgAA
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 19:09:09 -0000

Christian,

On 2013-05-24, at 2:41 PM, Christian Huitema <huitema@microsoft.com> wrote:
> ...
>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
> 
> Do you have this problem only with link local addresses, or with some other addresses as well?


As far as losing address information, so far it has only been an issue for link-local addresses.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From msweet@apple.com  Fri May 24 12:28:01 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 818F811E80C5 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.628
X-Spam-Level: 
X-Spam-Status: No, score=-108.628 tagged_above=-999 required=5 tests=[AWL=1.970, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJvRamQk1uCQ for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:27:55 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 0535B11E80F5 for <ipv6@ietf.org>; Fri, 24 May 2013 12:27:51 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_qOzZvLqY2QlrQBuC+5Y/oA)"
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNB009CTI2FSN00@mail-out.apple.com> for ipv6@ietf.org; Fri, 24 May 2013 12:27:51 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-4b-519fbf361a37
Received: from [17.153.56.8] (Unknown_Domain [17.153.56.8]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id 6F.8D.31158.73FBF915; Fri, 24 May 2013 12:27:51 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <CABOxzu1qrPiPKQiqsS-TizCJsrJ+ONKBGkr3VEvaPD-AV8Tk5g@mail.gmail.com>
Date: Fri, 24 May 2013 15:27:48 -0400
Message-id: <4DFFED51-06C9-485B-9F77-3FB8941845E5@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <CABOxzu1qrPiPKQiqsS-TizCJsrJ+ONKBGkr3VEvaPD-AV8Tk5g@mail.gmail.com>
To: Kerry Lynn <kerlyn@ieee.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUiONOCQ9d8//xAgz1bVSxenn3PZHF5/Spm iyPfYh2YPbae/MHm8XTCQSaPJUt+MgUwR3HZpKTmZJalFunbJXBlLJvxnKlggU7F8gN/mBoY z6t2MXJySAiYSDx9sJMVwhaTuHBvPVsXIxeHkEAnk8SlnX/ZQBLCAuYScx9/ZgSxeQX0JK59 +8oOYjMLJEicuP6IBcRmE1CT+D2pD2wQp0CgxJ9/TUwgNouAqsT5HU8ZIeolJB7u28YGMcdG 4t6qjewQy96wSGx5NQesWURAQeLToj1MEBfJSrx+/oZlAiPfLCS7ZyHZDWFrSyxb+JoZwtaT eNn0jh1TXFfi4rpJjAsY2VYxChSl5iRWmuolFhTkpOol5+duYgQFbkNhxA7G/8usDjEKcDAq 8fAKlM8PFGJNLCuuzD3EKMHBrCTCK7MTKMSbklhZlVqUH19UmpNafIhRmoNFSZz319xZgUIC 6YklqdmpqQWpRTBZJg5OqQbG3b58Qlw+XHcbdavY8ttTnvS1d3I42jUwbT4qrRLr1Pht4opv pW+/J2pmc0Sutt2+t/eoTvx+j0nPZb+tXWlY+vmczLXVOTd/ZXgu/rwh0/h56UQfPdFnT/cf 3OZ3t+mZyO+js83dDj4336r41UndQFwzosdReYWMk9LztDj2SZnf9zv07F2nxFKckWioxVxU nAgAIqZx0FgCAAA=
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 19:28:01 -0000

--Boundary_(ID_qOzZvLqY2QlrQBuC+5Y/oA)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Kerry,

On 2013-05-24, at 2:51 PM, Kerry Lynn <kerlyn@ieee.org> wrote:
> ...
> Just so we're clear, I assume this does NOT work today with link-local IPv6 addresses (because no print client yet
> constructs a Host URI with link-local address and zoneID according to RFC 6874)?  And you're saying that RFC 6874
> does not improve on the current situation?

Correct on both counts.

What we have been advising printer vendors to do for the last 8 years is to support the IPvFuture address syntax, based on some discussions I had 8 years ago with one of the HTTP WG members at the time (and I apologize for not having more details, I lost my email archives recently and haven't been able to recover the files yet...) The "recommended" syntax at the time was:

    scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:port/path

Support for that format got added to CUPS back in 2005, with most current printers supporting it as well.  By printer support, I mean they use the address as-is when returning URIs, they don't actually care about the zoneid...

I've been doing some testing locally and it seems that some OS libraries/frameworks work with the new address format, some with the old IPvFuture format, but so far none work with both.

Another data point: none of the web browsers I've tested allow link-local IPv6 addresses, period. Some don't understand the IPvFuture or RFC 6874 formats, some decide you meant to search for the IPv6 address (which produces some interesting search results...)

I still need to do more testing with printers to see what they do with RFC 6874 URIs once the print client (CUPS) is updated.  I suspect it will be a mixed result...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


--Boundary_(ID_qOzZvLqY2QlrQBuC+5Y/oA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Kerry,<div><br><div><div>On 2013-05-24, at 2:51 PM, Kerry Lynn &lt;<a =
href=3D"mailto:kerlyn@ieee.org">kerlyn@ieee.org</a>&gt; =
wrote:</div><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>...</div></div></blockquote><blockquote =
type=3D"cite"><div class=3D"gmail_quote"><div>Just so we're clear, I =
assume this does NOT work today with link-local IPv6 addresses (because =
no print client yet<br>constructs a Host URI with link-local address and =
zoneID according to RFC 6874)?&nbsp; And you're saying that RFC 6874<br>
does not improve on the current =
situation?<br></div></div></blockquote><div><br></div></div><div>Correct =
on both counts.</div><div><br></div><div>What we have been advising =
printer vendors to do for the last 8 years is to support the IPvFuture =
address syntax, based on some discussions I had 8 years ago with one of =
the HTTP WG members at the time (and I apologize for not having more =
details, I lost my email archives recently and haven't been able to =
recover the files yet...) The "recommended" syntax at the time =
was:</div><div><br></div><div>&nbsp; &nbsp; <a =
href=3D"scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:port/path">scheme://[v1.f=
e80::xxxx:...:xxxx+zoneid]:port/path</a></div><div><br></div><div>Support =
for that format got added to CUPS back in 2005, with most current =
printers supporting it as well. &nbsp;By printer support, I mean they =
use the address as-is when returning URIs, they don't actually care =
about the zoneid...</div><div><br></div><div>I've been doing some =
testing locally and it seems that some OS libraries/frameworks work with =
the new address format, some with the old IPvFuture format, but so far =
none work with both.</div><div><br></div><div>Another data =
point:&nbsp;none of the web browsers I've tested allow link-local IPv6 =
addresses, period. Some don't understand the IPvFuture or RFC 6874 =
formats, some decide you meant to search for the IPv6 address (which =
produces some interesting search results...)</div><div><br></div><div>I =
still need to do more testing with printers to see what they do with RFC =
6874 URIs once the print client (CUPS) is updated. &nbsp;I suspect it =
will be a mixed result...</div><div><br></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Andale Mono'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">_________________________________________________________<br>Michael =
Sweet, Senior Printing System&nbsp;Engineer, PWG =
Chair</div></span></span>
</div>
<br></div></body></html>=

--Boundary_(ID_qOzZvLqY2QlrQBuC+5Y/oA)--

From kerlyn2001@gmail.com  Fri May 24 12:44:56 2013
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1948F21E80A1 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.819
X-Spam-Level: 
X-Spam-Status: No, score=-102.819 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9LGQXMYEv1N for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 12:44:51 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id E141D21E80A0 for <ipv6@ietf.org>; Fri, 24 May 2013 12:44:50 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so6519240oah.7 for <ipv6@ietf.org>; Fri, 24 May 2013 12:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=dly+r56tXenPPPFPeCgQtajNQ/KjlxGLqzOTQUetD44=; b=lzYOcyClQZd5BKtmK8POevGetQhlBTZcyF91Pisbr1gbNsp4MNCiPusNw+qNHSTjGQ jAaKkYmuqdvAwsxcQGf1Afbdc2lb000P+J+ZcHCj2Txw6fvkKpyzVx5aWIRqjvUYTD8d G1nfgCNYN8kF5QbbCbBbmxlg7veJMvZ6voRUtitvOpQKJU/HiGWitYlXzly1uc5+satB sks2jOtJW/9xuBgCoYFmE3vAhJyQHteXo8JlP5IcFAys1QVA9JMgJdd3rakKrKaRcXyZ EoyIJ5ESUm/CsAa2nICLhTvrh+utRjhuQDR/JSMrptXVF9NkeBm9AR7N/HrdTzMhgDYK 3nIw==
MIME-Version: 1.0
X-Received: by 10.60.47.1 with SMTP id z1mr13050810oem.134.1369424690342; Fri, 24 May 2013 12:44:50 -0700 (PDT)
Sender: kerlyn2001@gmail.com
Received: by 10.60.148.197 with HTTP; Fri, 24 May 2013 12:44:50 -0700 (PDT)
In-Reply-To: <4DFFED51-06C9-485B-9F77-3FB8941845E5@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <CABOxzu1qrPiPKQiqsS-TizCJsrJ+ONKBGkr3VEvaPD-AV8Tk5g@mail.gmail.com> <4DFFED51-06C9-485B-9F77-3FB8941845E5@apple.com>
Date: Fri, 24 May 2013 15:44:50 -0400
X-Google-Sender-Auth: wCB3x2kj38T27TIZeXbpe9pWbFA
Message-ID: <CABOxzu1Rnc0hf=U3h6owUyKbD9rM7dyZMm_uxoR4H=aTcXpnQQ@mail.gmail.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Kerry Lynn <kerlyn@ieee.org>
To: Michael Sweet <msweet@apple.com>
Content-Type: multipart/alternative; boundary=001a11c2103e373c4b04dd7c08ae
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 19:44:56 -0000

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

On Fri, May 24, 2013 at 3:27 PM, Michael Sweet <msweet@apple.com> wrote:

> Kerry,
>
> On 2013-05-24, at 2:51 PM, Kerry Lynn <kerlyn@ieee.org> wrote:
>
> ...
>
> Just so we're clear, I assume this does NOT work today with link-local
> IPv6 addresses (because no print client yet
> constructs a Host URI with link-local address and zoneID according to RFC
> 6874)?  And you're saying that RFC 6874
> does not improve on the current situation?
>
>
> Correct on both counts.
>
> What we have been advising printer vendors to do for the last 8 years is
> to support the IPvFuture address syntax, based on some discussions I had 8
> years ago with one of the HTTP WG members at the time (and I apologize for
> not having more details, I lost my email archives recently and haven't been
> able to recover the files yet...) The "recommended" syntax at the time was:
>
>     scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:port/path
>
> So it appears the current 'host' production used by print drivers is not
currently specified
by any RFC; why not just continue to use the same format irrespective of
RFC 6874?


> Support for that format got added to CUPS back in 2005, with most current
> printers supporting it as well.  By printer support, I mean they use the
> address as-is when returning URIs, they don't actually care about the
> zoneid...
>
> I've been doing some testing locally and it seems that some OS
> libraries/frameworks work with the new address format, some with the old
> IPvFuture format, but so far none work with both.
>
> Another data point: none of the web browsers I've tested allow link-local
> IPv6 addresses, period. Some don't understand the IPvFuture or RFC 6874
> formats, some decide you meant to search for the IPv6 address (which
> produces some interesting search results...)
>
> It's the browser case that RFC 6874 was primarily meant to deal with.

-K-

I still need to do more testing with printers to see what they do with RFC
> 6874 URIs once the print client (CUPS) is updated.  I suspect it will be a
> mixed result...
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>

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

On Fri, May 24, 2013 at 3:27 PM, Michael Sweet <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:msweet@apple.com" target=3D"_blank">msweet@apple.com</a>&gt;</s=
pan> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word">Kerry,<div><br><div><div>On 2013-05-24,=
 at 2:51 PM, Kerry Lynn &lt;<a href=3D"mailto:kerlyn@ieee.org" target=3D"_b=
lank">kerlyn@ieee.org</a>&gt; wrote:</div><blockquote type=3D"cite"><div cl=
ass=3D"gmail_quote">
<div>...</div></div></blockquote><div class=3D"im"><blockquote type=3D"cite=
"><div class=3D"gmail_quote"><div>Just so we&#39;re clear, I assume this do=
es NOT work today with link-local IPv6 addresses (because no print client y=
et<br>
constructs a Host URI with link-local address and zoneID according to RFC 6=
874)?=A0 And you&#39;re saying that RFC 6874<br>
does not improve on the current situation?<br></div></div></blockquote><div=
><br></div></div></div><div>Correct on both counts.</div><div><br></div><di=
v>What we have been advising printer vendors to do for the last 8 years is =
to support the IPvFuture address syntax, based on some discussions I had 8 =
years ago with one of the HTTP WG members at the time (and I apologize for =
not having more details, I lost my email archives recently and haven&#39;t =
been able to recover the files yet...) The &quot;recommended&quot; syntax a=
t the time was:</div>
<div><br></div><div>=A0 =A0 <a>scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:por=
t/path</a></div><div><br></div></div></div></blockquote><div>So it appears =
the current &#39;host&#39; production used by print drivers is not currentl=
y specified<br>
by any RFC; why not just continue to use the same format irrespective of RF=
C 6874?<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-w=
rap:break-word">
<div><div></div><div>Support for that format got added to CUPS back in 2005=
, with most current printers supporting it as well. =A0By printer support, =
I mean they use the address as-is when returning URIs, they don&#39;t actua=
lly care about the zoneid...</div>
<div><br></div><div>I&#39;ve been doing some testing locally and it seems t=
hat some OS libraries/frameworks work with the new address format, some wit=
h the old IPvFuture format, but so far none work with both.</div><div><br>
</div><div>Another data point:=A0none of the web browsers I&#39;ve tested a=
llow link-local IPv6 addresses, period. Some don&#39;t understand the IPvFu=
ture or RFC 6874 formats, some decide you meant to search for the IPv6 addr=
ess (which produces some interesting search results...)</div>
<div><br></div></div></div></blockquote><div>It&#39;s the browser case that=
 RFC 6874 was primarily meant to deal with.<br><br>-K-<br><br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><div></div><div>I still need to do=
 more testing with printers to see what they do with RFC 6874 URIs once the=
 print client (CUPS) is updated. =A0I suspect it will be a mixed result...<=
/div>
<div class=3D"im"><div><br></div><div>
<span style=3D"border-collapse:separate;border-spacing:0px"><span style=3D"=
text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webki=
t-auto;font-style:normal;font-weight:normal;line-height:normal;border-colla=
pse:separate;text-transform:none;font-size:medium;white-space:normal;font-f=
amily:&#39;Andale Mono&#39;;word-spacing:0px"><div style=3D"word-wrap:break=
-word">
_________________________________________________________<br>Michael Sweet,=
 Senior Printing System=A0Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></div></blockquote></div><br>

--001a11c2103e373c4b04dd7c08ae--

From msweet@apple.com  Fri May 24 13:33:05 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 504D011E8112 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.792
X-Spam-Level: 
X-Spam-Status: No, score=-108.792 tagged_above=-999 required=5 tests=[AWL=1.806, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6D1vIvxU+vk for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:32:59 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 227DF21F933B for <ipv6@ietf.org>; Fri, 24 May 2013 13:32:58 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_8bYxnlyITJep6fO0N6eJ0Q)"
Received: from relay2.apple.com ([17.128.113.67]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNB00NALL1Y0TD1@mail-out.apple.com> for ipv6@ietf.org; Fri, 24 May 2013 13:32:52 -0700 (PDT)
X-AuditID: 11807143-b7f856d000000818-df-519fce7307de
Received: from [17.153.56.8] (Unknown_Domain [17.153.56.8]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay2.apple.com (Apple SCV relay) with SMTP id 70.16.02072.37ECF915; Fri, 24 May 2013 13:32:52 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <CABOxzu1Rnc0hf=U3h6owUyKbD9rM7dyZMm_uxoR4H=aTcXpnQQ@mail.gmail.com>
Date: Fri, 24 May 2013 16:32:49 -0400
Message-id: <D3549645-05D6-4583-86F1-08EDFCBA4420@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <CABOxzu1qrPiPKQiqsS-TizCJsrJ+ONKBGkr3VEvaPD-AV8Tk5g@mail.gmail.com> <4DFFED51-06C9-485B-9F77-3FB8941845E5@apple.com> <CABOxzu1Rnc0hf=U3h6owUyKbD9rM7dyZMm_uxoR4H=aTcXpnQQ@mail.gmail.com>
To: Kerry Lynn <kerlyn@ieee.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCLMWRmVeSWpSXmKPExsUiONOCQ7fk3PxAgzOTZCxenn3PZHF5/Spm iyPfYh2YPbae/MHm8XTCQSaPJUt+MgUwR3HZpKTmZJalFunbJXBl/Np1grFgqULFocPqDYxn ZLoYOTkkBEwknp35zghhi0lcuLeerYuRi0NIoJNJovFkLytIQljAXGLu489gRbwCehLXvn1l B7GZBRIkXrfvYwOx2QTUJH5P6gOr5xQIlHixtB+snkVAVeJO8xxGiHoJiYf7trFBzLGR6Nj3 kgli2SNWibNXm8GKRAQUJD4t2sMEcZGsxOvnb1gmMPLNQrJ7FpLdELa2xLKFr5khbD2Jl03v oGrkJba/nQMV15W4uG4S4wJGtlWMAkWpOYmVRnqJBQU5qXrJ+bmbGEFh21DovIPx2DKrQ4wC HIxKPLwC5fMDhVgTy4orcw8xSnAwK4nwyuwECvGmJFZWpRblxxeV5qQWH2KU5mBREuf9MXdW oJBAemJJanZqakFqEUyWiYNTqoFRsT1cK87UYRbvjoDHNRctZR9dV75wpJjPLab+7IGiRTsZ uhkOP9sQs3JBxqOsgN7J2TVPS9QT5i30DoryjWvapq/x5ZxFEHOr5W/pPqmv/zm45sS+i7f0 tsyb4BXzoXRiUnK5nPJbzgjJXZ6dnbG5X9WOfg3c5Jj976oDT+5Pw8TA7alP3iixFGckGmox FxUnAgA7yi5AVwIAAA==
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 20:33:05 -0000

--Boundary_(ID_8bYxnlyITJep6fO0N6eJ0Q)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Kerry,

On 2013-05-24, at 3:44 PM, Kerry Lynn <kerlyn@ieee.org> wrote:
> ...
>     scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:port/path
> 
> So it appears the current 'host' production used by print drivers is not currently specified
> by any RFC; why not just continue to use the same format irrespective of RFC 6874?

Mainly because I expect that future (browser and print) software will use the RFC 6874 format, and we don't want to have one format for IPP printers and another for everything else...

> ...
> It's the browser case that RFC 6874 was primarily meant to deal with.

The issue is that a) we need the printer to report admin and supply level page URLs the browser can use and b) printer web pages usually contain absolute URLs, so regardless of the client involved we'd need the printer to preserve the full address for the client.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


--Boundary_(ID_8bYxnlyITJep6fO0N6eJ0Q)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Kerry,<div><br><div><div>On 2013-05-24, at 3:44 PM, Kerry Lynn &lt;<a href="mailto:kerlyn@ieee.org">kerlyn@ieee.org</a>&gt; wrote:</div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div style="word-wrap:break-word"><div><div><font color="#000000">...</font></div><div>&nbsp; &nbsp; <a>scheme://[v1.fe80::xxxx:...:xxxx+zoneid]:port/path</a></div><div><br></div></div></div></blockquote><div>So it appears the current 'host' production used by print drivers is not currently specified<br>
by any RFC; why not just continue to use the same format irrespective of RFC 6874?<br></div></div></blockquote><div><br></div>Mainly because I expect that future (browser and print) software will use the RFC 6874 format, and we don't want to have one format for IPP printers and another for everything else...</div><div><br></div><div><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">...</div></blockquote><div>It's the browser case that RFC 6874 was primarily meant to deal with.<br></div></div></blockquote><div><br></div></div>The issue is that a) we need the printer to report&nbsp;admin and supply level page&nbsp;URLs the&nbsp;browser&nbsp;can use and b) printer web pages usually contain absolute URLs, so regardless of the client involved we'd need the printer to preserve the full address for the client.</div><div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System&nbsp;Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>

--Boundary_(ID_8bYxnlyITJep6fO0N6eJ0Q)--

From otroan@employees.org  Fri May 24 13:33:35 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D0D11E811B for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dTxreRTebdbb for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:33:30 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id AA00A11E8116 for <ipv6@ietf.org>; Fri, 24 May 2013 13:33:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYGAEHNn1GQ/khM/2dsb2JhbABQCoMIMMIugQcWdIIjAQEEATo/BQsLDjhXBogaBro0jWGBCTMHgnNhA5hkkBeDETqBLiQ
X-IronPort-AV: E=Sophos;i="4.87,737,1363132800"; d="scan'208";a="82840923"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 24 May 2013 20:33:26 +0000
Received: from dhcp-10-61-107-201.cisco.com (dhcp-10-61-107-201.cisco.com [10.61.107.201]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4OKXNO5009123 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 May 2013 20:33:23 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
Date: Fri, 24 May 2013 22:33:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD44AD09-B91C-41CA-9CE7-45D3E84A26CE@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
To: Michael Sweet <msweet@apple.com>
X-Mailer: Apple Mail (2.1503)
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 20:33:36 -0000

Michael,

>> Can we move from the process discussion to the technical discussion?
>>=20
>> Michael raised an interesting issue, and we have to analyze it. The =
consensus of the working group so far is that interface identifiers are =
private to the host, that any leakage outside the host should be =
prevented, and that a way to prevent that leakage is to ask proxies to =
erase them whenever they have an opportunity. Michael points that some =
servers take an opposite approach, want to record the interface from =
which the host called them, and want to ensure that further calls in the =
same session use exactly the same interface. That seems that a fairly =
legitimate debate, and I can see two alternatives -- one would be to =
reaffirm the old guidance and provides alternative to ensure session =
continuity, and the other would be to reverse the guidance and accept =
that the layer violation performed by servers is just fine.
>=20
>=20
> (the following is printer-centric, but the same applies to network =
video cameras and other embedded network devices)
>=20
> Some background: HTTP and IPP services in printers include absolute =
URIs in the content they return. For IPP this can be http/https URLs to =
the printer's web page, ICC profiles, and other resources, along with =
the ipp/ipps URIs that the printer supports. For HTTP the most common =
are https URLs for "secure" areas of the printer's web interface.  =
Because a printer is often known by multiple names and addresses =
("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, =
etc.), the implementation guidance (and in IPP Everywhere, this is a =
conformance requirement) is that the server use the HTTP Host header =
provided in the request in the host/address field of its responses, =
subject to the usual security considerations (SHOULD validate Host =
value, etc.)  This allows the client to use the name or address it can =
resolve/connect to and makes sure that the printer-generated absolute =
URIs lead back to same printer.
>=20
> All of this falls apart with link-local addresses and RFC 6874.  =
Because the client is required to remove the zoneid from the outgoing =
request, the URIs it gets back from the server are no longer =
"reachable".

how is this different from any other application using link-local =
addresses?
the application has to be 'bound' to the given zone. if a host receives =
an RA from a router, it learns the link-local address of the router,
but it locally ties that link-local address to the zone it belongs to.

given that you cannot use link-locals in referrals outside of the =
correct zone, why doesn't this also work for your application?

client connects to http:://[fe80::1%Ethernet0/0]
the client has to assume that all embedded URIs with link-local =
addresses belong to the same zone that it connected to.
after all they cannot belong to any other zone...  the server obviously =
has to make sure it never gives out these URIs
to a client connecting using non-link-local addresses multiple hops =
away.

> What I propose is that we change the wording to allow the zoneid in =
the Host header but not in the Request-URI.  HTTP proxies would be =
required to strip any zoneid information in the Host header.  HTTP =
servers would be required to ignore any zoneid information for purposes =
of address validation but include it for any absolute URIs to the server =
they generate.
>=20
> Thoughts?

to reword. you need something for which the client gives the server some =
opaque information that it can use to identify interface when it gets =
the embedded URIs in the reply back?
again I don't understand why the client doesn't know the interface to =
use already.

cheers,
Ole=

From brian.e.carpenter@gmail.com  Fri May 24 13:50:35 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D30F21E808B for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.189
X-Spam-Level: 
X-Spam-Status: No, score=-103.189 tagged_above=-999 required=5 tests=[AWL=0.410, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2ss-yl7oXzM for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 13:50:24 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 17D5A11E8135 for <ipv6@ietf.org>; Fri, 24 May 2013 13:50:22 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id wp1so2132564pac.3 for <ipv6@ietf.org>; Fri, 24 May 2013 13:50:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qa4hwU1Snf7wBini5qQyVlydGG5TRT7GuEHf7qeeUM4=; b=Otz7wtM9A9YxH4V8rwe+HESUAxL8jBOefZOkLBI3rGLMzW2eOY0ZbhW/3GtcN/fEhu uTnzlSyC+OGDMIzp7k6s+wzsyK3KwOxHgb7+gZ/GECbqyl4M7xhAKrA2ThK+5tpGankh hkqEeiCVb3+t8uX/y13s9URekz/W9iSoENw0qXO1PnPNmKyqyZlRFa/crsu/TxNYaFEG 17dFARE6E/blQZYfVQn4FvMgzC/cgmuY/ujUR9wpJIOUa/0gxOB6UCV7Y9yLe9Disfbr Kbb4FIhJH+r+X8YfmQAADcIqph8T16FLCUHmuuN+Eu813lTLV+/2oL/Hff51F6UeT1ca YyAw==
X-Received: by 10.68.236.38 with SMTP id ur6mr10343054pbc.188.1369428621888; Fri, 24 May 2013 13:50:21 -0700 (PDT)
Received: from [192.168.1.2] (229.187.252.27.dyn.cust.vf.net.nz. [27.252.187.229]) by mx.google.com with ESMTPSA id vm10sm18858430pab.5.2013.05.24.13.50.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 13:50:20 -0700 (PDT)
Message-ID: <519FD295.2060201@gmail.com>
Date: Sat, 25 May 2013 08:50:29 +1200
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: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi>
In-Reply-To: <20130524124005.GR23227@verdi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 20:50:35 -0000

On 25/05/2013 00:40, John Leslie wrote:
> Ray Hunter <v6ops@globis.net> wrote:
>> I would also like to see some text on whether it is possible/desirable
>> for a middleware box to strip unknown headers, or even some known
>> headers, rather than making a binary decision to drop or transmit the
>> entire packet. If (new) headers are truly optional or experimental, the
>> residual stripped packet may still have value e.g. stripping hop by hop
>> extension headers on entry to/ egress from a corporate network or
>> transit AS. That way the (new) extension headers could be usefully
>> deployed in an AS that supports them, but the end to end traffic would
>> not be blocked further along the path by firewalls in an AS that does not.
> 
>    I had a similar thought -- even going so far as to posit a way to
> notate that a header had been stripped...
> 
>    I think the answer is we don't want to do that in this document;
> nonetheless some folks are likely to try it. I think a mention of the
> issue, and a reference to RFC(s) stating the current rules, would help.

What rules? As far as I know, no such mechanism is defined or allowed,
so there is nothing to refer to. I would object (as a WG participant)
to even mentioning such a mechanism. (As a document editor, I would
of course edit the document according to WG consensus.)
> 
>    (The prime purpose of this document is creating an IANA registry;
> that purpose should not be clouded by discussion of what firewalls
> "should" do.)

Not so. The prime purpose of this document is to make extension headers
useable. The registry is a means to that end; describing precisely how
middleboxes should treat them is another means to that end. We can make
that clearer in the text, of course.

Describing how middleboxes might block or destroy them is antithetical
to the purpose of the document. That's why Ray says "I'm not sure the
current text is entirely balanced in this respect." He's right. Again
speaking as a WG participant, I'm happy with that.

On 25/05/2013 02:43, Tim Chown wrote:

> A couple of additional comments.
> 
> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?

Shouldn't this just be part of the Security Comsiderations for
the definition of each header? The registry will always contain a pointer
to the relevant RFCs. IANA can't do much if the Security Considerations
are insufficient.

> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?

I think we included that in an earlier draft, but then removed it
because it appears to function as a null transport header. It's
a judgment call, and only needs a few keystrokes to put it back in the
list.

   Brian

From dthaler@microsoft.com  Fri May 24 15:06:11 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C790421F96A0 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.067
X-Spam-Level: 
X-Spam-Status: No, score=-97.067 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_63=0.6, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yEGm0HzwJ-9G for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:06:06 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id CB1C521F969A for <6man@ietf.org>; Fri, 24 May 2013 15:06:05 -0700 (PDT)
Received: from BL2FFO11FD014.protection.gbl (10.173.161.203) by BL2FFO11HUB028.protection.gbl (10.173.161.52) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 22:06:03 +0000
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD014.mail.protection.outlook.com (10.173.160.222) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 22:06:03 +0000
Received: from db9outboundpool.messaging.microsoft.com (157.54.51.114) by mail.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.3.136.1; Fri, 24 May 2013 22:06:01 +0000
Received: from mail1-db9-R.bigfish.com (10.174.16.254) by DB9EHSOBE002.bigfish.com (10.174.14.65) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 22:04:10 +0000
Received: from mail1-db9 (localhost [127.0.0.1])	by mail1-db9-R.bigfish.com (Postfix) with ESMTP id 7D11BB00064	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 24 May 2013 22:04:10 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT001.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371I542I1432I111aI62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah5eeeK8275bhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail1-db9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT001.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB269; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail1-db9 (localhost.localdomain [127.0.0.1]) by mail1-db9 (MessageSwitch) id 1369433048346741_25221; Fri, 24 May 2013 22:04:08 +0000 (UTC)
Received: from DB9EHSMHS001.bigfish.com (unknown [10.174.16.232])	by mail1-db9.bigfish.com (Postfix) with ESMTP id 4F26BD00049; Fri, 24 May 2013 22:04:08 +0000 (UTC)
Received: from BL2PRD0310HT001.namprd03.prod.outlook.com (157.56.240.21) by DB9EHSMHS001.bigfish.com (10.174.14.11) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 24 May 2013 22:04:08 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BL2PRD0310HT001.namprd03.prod.outlook.com (10.255.97.36) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 22:04:06 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) with Microsoft SMTP Server (TLS) id 15.0.698.13; Fri, 24 May 2013 22:04:04 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Fri, 24 May 2013 22:04:04 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Alissa Cooper <acooper@cdt.org>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAZOUUAAAClyEA=
Date: Fri, 24 May 2013 22:04:03 +0000
Message-ID: <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org>
In-Reply-To: <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:c925:1c0b:4358:e80a]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB269.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC105.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC105.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(479174002)(189002)(13464003)(43784003)(199002)(377454002)(24454002)(243025003)(252514006)(51704005)(59766001)(49866001)(6806003)(53806001)(69226001)(74876001)(77982001)(15202345002)(16676001)(80022001)(33646001)(74706001)(54356001)(65816001)(79102001)(23726002)(54316002)(51856001)(31966008)(50986001)(56816002)(74662001)(81342001)(74366001)(81542001)(76482001)(50466002)(47776003)(47976001)(4396001)(46102001)(47446002)(44976003)(47736001)(74316001)(46406003)(20776003)(74502001)(63696002)(56776001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB028; H:TK5EX14HUBC105.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:06:11 -0000

Thanks Alissa for the nice table, this is very helpful.

> -----Original Message-----
> From: Alissa Cooper [mailto:acooper@cdt.org]
> Sent: Friday, May 24, 2013 2:34 PM
> To: Fernando Gont
> Cc: Dave Thaler; 6man@ietf.org; 6man-chairs@tools.ietf.org; Brian
> Haberman; Ray Hunter; tom.petch; Christian Huitema; He Xuan
> Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> This discussion got me thinking about how to be rigorous in articulating =
the
> specific threats that different kinds of addresses do and do not mitigate=
. I put
> together a little table to try to sum this up:
> http://www.alissacooper.com/files/IPv6-address-threats.pdf
>=20
> The table assumes, for simplicity, that the node in question doesn't use =
any
> higher-layer identifiers and is never behind a firewall.
>=20
> I think I've seen four different kinds of threats described in the course=
 of the
> discussion of this draft, listed as the columns in the table:
> (a) A typical address scanning attack for the purpose of exploiting the n=
odes
> found by scanning
> (b) An attack that involves scanning an address space, identifying which =
nodes
> respond, and subsequently tracking the locations of those nodes. I'm not
> exactly sure what the point of doing this is, so maybe it shouldn't be in=
cluded,
> but I left it in.
> (c) An attack wherein the attacker receives a node's address through some
> channel (email, p2p serving, etc.) and then tracks the location of that n=
ode
> later.
> (d) An attack wherein the attacker receives a node's address through some
> channel and then correlates the node's activities together.

I'm assuming here by (d) you mean correlation over_time_ of activities from=
 the
same node, even if it never moves.

>=20
> The rows of the table are the address generation methods that have been
> discussed. The first three are for nodes that only use stable addresses a=
nd
> never use temporary addresses. Incidentally, I assume that it is this kin=
d of
> configuration that Fernando's draft is targeting -- the scenario where a
> network administrator has disabled temporary addresses regardless of the
> desires of the user, as described in section 1 of the draft. As can be se=
en in
> the table, both random and random-per-network (my term for what the draft
> calls stable privacy addresses) mitigate both types of address scanning a=
ttacks.
> Random-per-network additionally mitigates location tracking and potential=
ly
> reduces the amount of time over which correlation can take place.
>=20
> The second group of three are for nodes that only use temporary addresses
> (but that also configure a stable address that never gets used). This is =
what
> would be expected by users that want to avoid correlation attacks, assumi=
ng
> their admins allow it. In this case random and random-per-network provide
> equivalent protection.
>=20
> The last group of three are for nodes that use both temporary and stable
> addresses. Again here both random and random-per-network prevent the
> first two attacks, but random-per-network also prevents location tracking=
 and
> potentially reduces the scope for correlation.
>=20
> I think the conclusion from this is that if there are lots of nodes out t=
here that
> want to be protected from location tracking and correlation but their adm=
ins
> won't let them use temporary addresses, then random-per-network (row 3)
> provides some benefits over random (row 2).

Also, for nodes that never move (e.g., servers, desktop PCs, etc.) random a=
nd
random-per-network are equivalent.

>
> If we're talking about the case
> where a node can use temporary addresses and only uses them, random and
> random-per-network provide the same benefits (rows 5 and 6). I'm assuming
> those are the two common cases (could be wrong though).
>=20
> If we take away the assumption that the node uses no higher-layer identif=
iers,
> then correlation becomes possible in all of the cases for the duration of
> max(life of higher-layer identifier, longest-lived address).

Agree.

>=20
> If we take away the assumption that the node is never behind a firewall a=
nd
> assume that it will never respond to unsolicited packets (maybe too much =
too
> assume, but let's try), then the only differences between the address
> generation mechanisms are with respect to correlation. Random-per-network
> still provides some benefits over random in this case.

Agree.  For nodes that move between networks, yes.
Nodes that never move don't gain those benefits of course.

>=20
> Not sure if this is helpful to anyone else, but it clarified my thinking =
on this a
> bit, and it might be worth making the threat analysis in the draft more s=
pecific
> along these lines.

I think it would definitely help the draft to include this analysis.

Thanks again,
-Dave

>=20
> Alissa
>=20
> On May 24, 2013, at 5:31 AM, Fernando Gont <fgont@si6networks.com>
> wrote:
>=20
> > On 05/22/2013 03:34 AM, Dave Thaler wrote:
> >>> I attend an IETF meeting, and learn the IID of your laptop. Then I
> >>> can actively probe your node regarding "Is David at the office?" "Is
> >>> David at home?", etc.... simply because your IID is known and constan=
t.
> >>
> >> Since you're making this personal... please explain how you can probe
> >> whether I'm at the office or at home, both of which are behind
> >> firewalls (so won't respond to arbitrary probes) and have address pref=
ixes
> you don't know to begin with.
> >
> > As noted, this wasn't meant to be personal -- it was just meant to be
> > an example.
> >
> > Now, given the example under discussion:
> >
> > I could learn your IID when we both attend the IETF meeting. And I
> > could learn your prefixes when you post to mailing-lists from such plac=
es.
> > Then I could use Prefix|IID to track you.
> >
> > The fact that you use a firewall is mostly irrelevant. I'd bet your
> > firewall still reponds to some packets (e.g., packets with unsupported
> > options?). And, if that were not the case, I could rely on the
> > ICMPv6 "address resolution failed" error messages sent by your local
> > router (i.e., if I receive one of such messages, you're not there. If
> > I don't, you are).
> >
> > I've seen similar discussions for different kinds of IDs in the past,
> > and every time someone pushed a flawed/sub-optimal approach, they got
> > bitten. Moral of the story: don't leak more than necessary to achieve
> > your desired goal, or you'll be bitten.
> >
> > P.S.: This was discussed off-list already... but I posted this on-list
> > so that wg participants are aware of my response.
> >
> > Cheers,
> > --
> > Fernando Gont
> > SI6 Networks
> > e-mail: fgont@si6networks.com
> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> >
> >
> >
> >
> >
>=20
>=20
>=20



From Dmitry.Anipko@microsoft.com  Fri May 24 15:20:08 2013
Return-Path: <Dmitry.Anipko@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C207221F8E9D for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kO9D+JoU5fiL for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:20:04 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0237.outbound.protection.outlook.com [207.46.163.237]) by ietfa.amsl.com (Postfix) with ESMTP id D580C21F8E6E for <6man@ietf.org>; Fri, 24 May 2013 15:20:03 -0700 (PDT)
Received: from BN1AFFO11FD021.protection.gbl (10.58.52.203) by BN1BFFO11HUB023.protection.gbl (10.58.53.133) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 22:20:01 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BN1AFFO11FD021.mail.protection.outlook.com (10.58.52.81) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 22:20:00 +0000
Received: from TK5EX14MBXC254.redmond.corp.microsoft.com ([169.254.2.45]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0136.001; Fri, 24 May 2013 22:19:08 +0000
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, Alissa Cooper <acooper@cdt.org>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAZOUUAAAClyEAAALzbQA==
Date: Fri, 24 May 2013 22:19:08 +0000
Message-ID: <FB329D818C7CAB438F0C7DD772EA1025063C66C8@TK5EX14MBXC254.redmond.corp.microsoft.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.23]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51704005)(377454002)(13464003)(243025003)(479174002)(252514006)(43784003)(24454002)(33656001)(76482001)(56776001)(59766001)(1511001)(66066001)(55846006)(74706001)(69226001)(63696002)(50466002)(77982001)(46102001)(80022001)(81342001)(23726002)(47776003)(31966008)(4396001)(47976001)(20776003)(74876001)(46406003)(47736001)(74502001)(50986001)(81542001)(74662001)(51856001)(56816002)(65816001)(54356001)(47446002)(16406001)(15202345002)(49866001)(53806001)(79102001)(6806003)(74366001)(54316002); DIR:OUT; SFP:; SCL:1; SRVR:BN1BFFO11HUB023; H:TK5EX14HUBC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:20:08 -0000

> correlation but their admins won't let them use temporary addresses,=20
> then random-per-network (row 3) provides some benefits over random (row 2=
).

So is the goal of the draft to give a new way for network administrators to=
 decrease privacy of users? If yes, then if this goal was removed, would th=
e rest of the outlined benefits still warrant the proposed type of addresse=
s?


-----Original Message-----
From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of Dav=
e Thaler
Sent: Friday, May 24, 2013 3:04 PM
To: Alissa Cooper; Fernando Gont
Cc: 6man-chairs@tools.ietf.org; Brian Haberman; 6man@ietf.org; Ray Hunter; =
tom.petch; Christian Huitema; He Xuan
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07

Thanks Alissa for the nice table, this is very helpful.

> -----Original Message-----
> From: Alissa Cooper [mailto:acooper@cdt.org]
> Sent: Friday, May 24, 2013 2:34 PM
> To: Fernando Gont
> Cc: Dave Thaler; 6man@ietf.org; 6man-chairs@tools.ietf.org; Brian=20
> Haberman; Ray Hunter; tom.petch; Christian Huitema; He Xuan
> Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> This discussion got me thinking about how to be rigorous in=20
> articulating the specific threats that different kinds of addresses do=20
> and do not mitigate. I put together a little table to try to sum this up:
> http://www.alissacooper.com/files/IPv6-address-threats.pdf
>=20
> The table assumes, for simplicity, that the node in question doesn't=20
> use any higher-layer identifiers and is never behind a firewall.
>=20
> I think I've seen four different kinds of threats described in the=20
> course of the discussion of this draft, listed as the columns in the tabl=
e:
> (a) A typical address scanning attack for the purpose of exploiting=20
> the nodes found by scanning
> (b) An attack that involves scanning an address space, identifying=20
> which nodes respond, and subsequently tracking the locations of those=20
> nodes. I'm not exactly sure what the point of doing this is, so maybe=20
> it shouldn't be included, but I left it in.
> (c) An attack wherein the attacker receives a node's address through=20
> some channel (email, p2p serving, etc.) and then tracks the location=20
> of that node later.
> (d) An attack wherein the attacker receives a node's address through=20
> some channel and then correlates the node's activities together.

I'm assuming here by (d) you mean correlation over_time_ of activities from=
 the same node, even if it never moves.

>=20
> The rows of the table are the address generation methods that have=20
> been discussed. The first three are for nodes that only use stable=20
> addresses and never use temporary addresses. Incidentally, I assume=20
> that it is this kind of configuration that Fernando's draft is=20
> targeting -- the scenario where a network administrator has disabled=20
> temporary addresses regardless of the desires of the user, as=20
> described in section 1 of the draft. As can be seen in the table, both=20
> random and random-per-network (my term for what the draft calls stable pr=
ivacy addresses) mitigate both types of address scanning attacks.
> Random-per-network additionally mitigates location tracking and=20
> potentially reduces the amount of time over which correlation can take pl=
ace.
>=20
> The second group of three are for nodes that only use temporary=20
> addresses (but that also configure a stable address that never gets=20
> used). This is what would be expected by users that want to avoid=20
> correlation attacks, assuming their admins allow it. In this case=20
> random and random-per-network provide equivalent protection.
>=20
> The last group of three are for nodes that use both temporary and=20
> stable addresses. Again here both random and random-per-network=20
> prevent the first two attacks, but random-per-network also prevents=20
> location tracking and potentially reduces the scope for correlation.
>=20
> I think the conclusion from this is that if there are lots of nodes=20
> out there that want to be protected from location tracking and=20
> correlation but their admins won't let them use temporary addresses,=20
> then random-per-network (row 3) provides some benefits over random (row 2=
).

Also, for nodes that never move (e.g., servers, desktop PCs, etc.) random a=
nd random-per-network are equivalent.

>
> If we're talking about the case
> where a node can use temporary addresses and only uses them, random=20
> and random-per-network provide the same benefits (rows 5 and 6). I'm=20
> assuming those are the two common cases (could be wrong though).
>=20
> If we take away the assumption that the node uses no higher-layer=20
> identifiers, then correlation becomes possible in all of the cases for=20
> the duration of max(life of higher-layer identifier, longest-lived addres=
s).

Agree.

>=20
> If we take away the assumption that the node is never behind a=20
> firewall and assume that it will never respond to unsolicited packets=20
> (maybe too much too assume, but let's try), then the only differences=20
> between the address generation mechanisms are with respect to=20
> correlation. Random-per-network still provides some benefits over random =
in this case.

Agree.  For nodes that move between networks, yes.
Nodes that never move don't gain those benefits of course.

>=20
> Not sure if this is helpful to anyone else, but it clarified my=20
> thinking on this a bit, and it might be worth making the threat=20
> analysis in the draft more specific along these lines.

I think it would definitely help the draft to include this analysis.

Thanks again,
-Dave

>=20
> Alissa
>=20
> On May 24, 2013, at 5:31 AM, Fernando Gont <fgont@si6networks.com>
> wrote:
>=20
> > On 05/22/2013 03:34 AM, Dave Thaler wrote:
> >>> I attend an IETF meeting, and learn the IID of your laptop. Then I=20
> >>> can actively probe your node regarding "Is David at the office?"=20
> >>> "Is David at home?", etc.... simply because your IID is known and con=
stant.
> >>
> >> Since you're making this personal... please explain how you can=20
> >> probe whether I'm at the office or at home, both of which are=20
> >> behind firewalls (so won't respond to arbitrary probes) and have=20
> >> address prefixes
> you don't know to begin with.
> >
> > As noted, this wasn't meant to be personal -- it was just meant to=20
> > be an example.
> >
> > Now, given the example under discussion:
> >
> > I could learn your IID when we both attend the IETF meeting. And I=20
> > could learn your prefixes when you post to mailing-lists from such plac=
es.
> > Then I could use Prefix|IID to track you.
> >
> > The fact that you use a firewall is mostly irrelevant. I'd bet your=20
> > firewall still reponds to some packets (e.g., packets with=20
> > unsupported options?). And, if that were not the case, I could rely=20
> > on the
> > ICMPv6 "address resolution failed" error messages sent by your local=20
> > router (i.e., if I receive one of such messages, you're not there.=20
> > If I don't, you are).
> >
> > I've seen similar discussions for different kinds of IDs in the=20
> > past, and every time someone pushed a flawed/sub-optimal approach,=20
> > they got bitten. Moral of the story: don't leak more than necessary=20
> > to achieve your desired goal, or you'll be bitten.
> >
> > P.S.: This was discussed off-list already... but I posted this=20
> > on-list so that wg participants are aware of my response.
> >
> > Cheers,
> > --
> > Fernando Gont
> > SI6 Networks
> > e-mail: fgont@si6networks.com
> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> >
> >
> >
> >
> >
>=20
>=20
>=20


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

From dthaler@microsoft.com  Fri May 24 15:23:29 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD56521F8FA9 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.934
X-Spam-Level: 
X-Spam-Status: No, score=-96.934 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_63=0.6, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3ZqfGvdZZMZ for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:23:24 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 514FD21F8F61 for <6man@ietf.org>; Fri, 24 May 2013 15:23:24 -0700 (PDT)
Received: from BY2FFO11FD019.protection.gbl (10.1.15.201) by BY2FFO11HUB008.protection.gbl (10.1.14.166) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 22:23:15 +0000
Received: from TK5EX14HUBC106.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD019.mail.protection.outlook.com (10.1.14.107) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 22:23:15 +0000
Received: from va3outboundpool.messaging.microsoft.com (157.54.51.113) by mail.microsoft.com (157.54.80.61) with Microsoft SMTP Server (TLS) id 14.3.136.1; Fri, 24 May 2013 22:23:10 +0000
Received: from mail161-va3-R.bigfish.com (10.7.14.227) by VA3EHSOBE006.bigfish.com (10.7.40.26) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 22:21:15 +0000
Received: from mail161-va3 (localhost [127.0.0.1])	by mail161-va3-R.bigfish.com (Postfix) with ESMTP id 98C8A2A06FD	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 24 May 2013 22:21:15 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT001.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371I542I1432I111aI62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hz97hz1033IL17326ah5eeeK8275bh8275dhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail161-va3: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT001.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB270; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail161-va3 (localhost.localdomain [127.0.0.1]) by mail161-va3 (MessageSwitch) id 136943401299479_26906; Fri, 24 May 2013 22:20:12 +0000 (UTC)
Received: from VA3EHSMHS008.bigfish.com (unknown [10.7.14.226])	by mail161-va3.bigfish.com (Postfix) with ESMTP id A553DC0066; Fri, 24 May 2013 22:19:52 +0000 (UTC)
Received: from BL2PRD0310HT001.namprd03.prod.outlook.com (157.56.240.21) by VA3EHSMHS008.bigfish.com (10.7.99.18) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 22:19:48 +0000
Received: from BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) by BL2PRD0310HT001.namprd03.prod.outlook.com (10.255.97.36) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 22:19:48 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) with Microsoft SMTP Server (TLS) id 15.0.698.13; Fri, 24 May 2013 22:19:45 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Fri, 24 May 2013 22:19:45 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Dave Thaler <dthaler@microsoft.com>, Alissa Cooper <acooper@cdt.org>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAZOUUAAAClyEAAANgt8A==
Date: Fri, 24 May 2013 22:19:44 +0000
Message-ID: <deafa695f8004dc69996dee23e1400f8@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:c925:1c0b:4358:e80a]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB270.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC106.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC106.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(377454002)(479174002)(252514006)(43784003)(13464003)(199002)(51704005)(243025003)(24454002)(74706001)(74316001)(77982001)(54356001)(46102001)(47776003)(76482001)(81342001)(50466002)(63696002)(46406003)(6806003)(56816002)(1511001)(81542001)(15202345002)(23726002)(44976003)(74366001)(16676001)(20776003)(49866001)(33646001)(74876001)(79102001)(50986001)(74502001)(47446002)(56776001)(65816001)(4396001)(47976001)(31966008)(54316002)(59766001)(74662001)(47736001)(53806001)(80022001)(69226001)(51856001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB008; H:TK5EX14HUBC106.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:23:29 -0000

I'd also like to see CGAs (3972) added to this analysis.  It seems to me th=
ey're
the existing standards-track "random-per-network" addresses.  So all of the
"random-per-network" statements would seem apply equally to the existing RF=
C.

This draft references that RFC but does not contain any discussion on the
relative use cases.  I.e., if I already use CGAs for my "random-per-network=
"
solution, is there any benefit in this draft?

What problem is this solving that wasn't already solved by that existing=20
Proposed Standard RFC?

-Dave

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Dave Thaler
> Sent: Friday, May 24, 2013 3:04 PM
> To: Alissa Cooper; Fernando Gont
> Cc: 6man-chairs@tools.ietf.org; Brian Haberman; 6man@ietf.org; Ray Hunter=
;
> tom.petch; Christian Huitema; He Xuan
> Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> Thanks Alissa for the nice table, this is very helpful.
>=20
> > -----Original Message-----
> > From: Alissa Cooper [mailto:acooper@cdt.org]
> > Sent: Friday, May 24, 2013 2:34 PM
> > To: Fernando Gont
> > Cc: Dave Thaler; 6man@ietf.org; 6man-chairs@tools.ietf.org; Brian
> > Haberman; Ray Hunter; tom.petch; Christian Huitema; He Xuan
> > Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
> >
> > This discussion got me thinking about how to be rigorous in
> > articulating the specific threats that different kinds of addresses do
> > and do not mitigate. I put together a little table to try to sum this u=
p:
> > http://www.alissacooper.com/files/IPv6-address-threats.pdf
> >
> > The table assumes, for simplicity, that the node in question doesn't
> > use any higher-layer identifiers and is never behind a firewall.
> >
> > I think I've seen four different kinds of threats described in the
> > course of the discussion of this draft, listed as the columns in the ta=
ble:
> > (a) A typical address scanning attack for the purpose of exploiting
> > the nodes found by scanning
> > (b) An attack that involves scanning an address space, identifying
> > which nodes respond, and subsequently tracking the locations of those
> > nodes. I'm not exactly sure what the point of doing this is, so maybe
> > it shouldn't be included, but I left it in.
> > (c) An attack wherein the attacker receives a node's address through
> > some channel (email, p2p serving, etc.) and then tracks the location
> > of that node later.
> > (d) An attack wherein the attacker receives a node's address through
> > some channel and then correlates the node's activities together.
>=20
> I'm assuming here by (d) you mean correlation over_time_ of activities fr=
om
> the same node, even if it never moves.
>=20
> >
> > The rows of the table are the address generation methods that have
> > been discussed. The first three are for nodes that only use stable
> > addresses and never use temporary addresses. Incidentally, I assume
> > that it is this kind of configuration that Fernando's draft is
> > targeting -- the scenario where a network administrator has disabled
> > temporary addresses regardless of the desires of the user, as
> > described in section 1 of the draft. As can be seen in the table, both
> > random and random-per-network (my term for what the draft calls stable
> privacy addresses) mitigate both types of address scanning attacks.
> > Random-per-network additionally mitigates location tracking and
> > potentially reduces the amount of time over which correlation can take
> place.
> >
> > The second group of three are for nodes that only use temporary
> > addresses (but that also configure a stable address that never gets
> > used). This is what would be expected by users that want to avoid
> > correlation attacks, assuming their admins allow it. In this case
> > random and random-per-network provide equivalent protection.
> >
> > The last group of three are for nodes that use both temporary and
> > stable addresses. Again here both random and random-per-network
> > prevent the first two attacks, but random-per-network also prevents
> > location tracking and potentially reduces the scope for correlation.
> >
> > I think the conclusion from this is that if there are lots of nodes
> > out there that want to be protected from location tracking and
> > correlation but their admins won't let them use temporary addresses,
> > then random-per-network (row 3) provides some benefits over random
> (row 2).
>=20
> Also, for nodes that never move (e.g., servers, desktop PCs, etc.) random=
 and
> random-per-network are equivalent.
>=20
> >
> > If we're talking about the case
> > where a node can use temporary addresses and only uses them, random
> > and random-per-network provide the same benefits (rows 5 and 6). I'm
> > assuming those are the two common cases (could be wrong though).
> >
> > If we take away the assumption that the node uses no higher-layer
> > identifiers, then correlation becomes possible in all of the cases for
> > the duration of max(life of higher-layer identifier, longest-lived addr=
ess).
>=20
> Agree.
>=20
> >
> > If we take away the assumption that the node is never behind a
> > firewall and assume that it will never respond to unsolicited packets
> > (maybe too much too assume, but let's try), then the only differences
> > between the address generation mechanisms are with respect to
> > correlation. Random-per-network still provides some benefits over rando=
m
> in this case.
>=20
> Agree.  For nodes that move between networks, yes.
> Nodes that never move don't gain those benefits of course.
>=20
> >
> > Not sure if this is helpful to anyone else, but it clarified my
> > thinking on this a bit, and it might be worth making the threat
> > analysis in the draft more specific along these lines.
>=20
> I think it would definitely help the draft to include this analysis.
>=20
> Thanks again,
> -Dave
>=20
> >
> > Alissa
> >
> > On May 24, 2013, at 5:31 AM, Fernando Gont <fgont@si6networks.com>
> > wrote:
> >
> > > On 05/22/2013 03:34 AM, Dave Thaler wrote:
> > >>> I attend an IETF meeting, and learn the IID of your laptop. Then I
> > >>> can actively probe your node regarding "Is David at the office?"
> > >>> "Is David at home?", etc.... simply because your IID is known and
> constant.
> > >>
> > >> Since you're making this personal... please explain how you can
> > >> probe whether I'm at the office or at home, both of which are
> > >> behind firewalls (so won't respond to arbitrary probes) and have
> > >> address prefixes
> > you don't know to begin with.
> > >
> > > As noted, this wasn't meant to be personal -- it was just meant to
> > > be an example.
> > >
> > > Now, given the example under discussion:
> > >
> > > I could learn your IID when we both attend the IETF meeting. And I
> > > could learn your prefixes when you post to mailing-lists from such pl=
aces.
> > > Then I could use Prefix|IID to track you.
> > >
> > > The fact that you use a firewall is mostly irrelevant. I'd bet your
> > > firewall still reponds to some packets (e.g., packets with
> > > unsupported options?). And, if that were not the case, I could rely
> > > on the
> > > ICMPv6 "address resolution failed" error messages sent by your local
> > > router (i.e., if I receive one of such messages, you're not there.
> > > If I don't, you are).
> > >
> > > I've seen similar discussions for different kinds of IDs in the
> > > past, and every time someone pushed a flawed/sub-optimal approach,
> > > they got bitten. Moral of the story: don't leak more than necessary
> > > to achieve your desired goal, or you'll be bitten.
> > >
> > > P.S.: This was discussed off-list already... but I posted this
> > > on-list so that wg participants are aware of my response.
> > >
> > > Cheers,
> > > --
> > > Fernando Gont
> > > SI6 Networks
> > > e-mail: fgont@si6networks.com
> > > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20



From brian.e.carpenter@gmail.com  Fri May 24 15:28:29 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9BD111E811F for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.713
X-Spam-Level: 
X-Spam-Status: No, score=-102.713 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q22oU0ROQ9nC for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:28:23 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id B284C11E80F9 for <6man@ietf.org>; Fri, 24 May 2013 15:28:23 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 6so4282151pdd.34 for <6man@ietf.org>; Fri, 24 May 2013 15:28:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b63lLx7G/2b+LYVN/XzAsLYDcVJCpfXMRzrnGz5SiJE=; b=x+fDKMc/1oadHr7F03pQkPCJDsEE/2HD5mWPRUPjK8Ia+N2BUogazv0Vk5FYL2qyjC 4xJiVS1MLAk9ncZz4gF88/U7NXT2rE/3k7rFy9rjQmHc4+8o2cBhqnaeIxqlYWeKPqS2 kVcHQKtHKOruif/WOsC2GARgTil0bzGO+OYQ7vlc2SNAe8UmAnw1ND10TjFFJ1pyfgCB PmXS8HbN3xLDkihFtpj5t5w7gwc6T2LbLZMPSQhchzYFvs0ipPiq+vTVlEGZ2syTtRt7 Vxs/f/xoMoCYhAHO49IWn5eqForHMa0al4nUyC0FRGwo+p9+nWC2jjx8HavLCFpgWEfk H+fA==
X-Received: by 10.66.150.168 with SMTP id uj8mr20295958pab.34.1369434503456; Fri, 24 May 2013 15:28:23 -0700 (PDT)
Received: from [192.168.1.2] (229.187.252.27.dyn.cust.vf.net.nz. [27.252.187.229]) by mx.google.com with ESMTPSA id gc5sm17769486pbb.19.2013.05.24.15.28.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 15:28:22 -0700 (PDT)
Message-ID: <519FE98D.8070705@gmail.com>
Date: Sat, 25 May 2013 10:28:29 +1200
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: Alissa Cooper <acooper@cdt.org>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com>	<519AD0EF.60600@si6networks.com>	<87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>	<519F3364.80301@si6networks.com>	<AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:28:30 -0000

On 25/05/2013 10:04, Dave Thaler wrote:
> Thanks Alissa for the nice table, this is very helpful.

Agreed. Two points though:

1. It seems to me that location tracking to the level of the 64-bit
prefix is *always* possible, which may well identify a specific
customer and/or physical location, but not a specific host and/or
user. That qualifies column (c).

2. For completeness, include static manual addresses (yes, they
still exist in IPv6), which presumably get "possible" in every
column.

   Brian

From dthaler@microsoft.com  Fri May 24 15:30:11 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A00821F9362 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.438
X-Spam-Level: 
X-Spam-Status: No, score=-97.438 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5y2iJYViod2 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:30:04 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id DCF6E21F8EA8 for <6man@ietf.org>; Fri, 24 May 2013 15:30:04 -0700 (PDT)
Received: from BY2FFO11FD011.protection.gbl (10.1.15.200) by BY2FFO11HUB036.protection.gbl (10.1.14.179) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 22:30:03 +0000
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD011.mail.protection.outlook.com (10.1.14.129) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 22:30:03 +0000
Received: from CO9EHSOBE040.bigfish.com (157.54.51.113) by mail.microsoft.com (157.54.79.174) with Microsoft SMTP Server (TLS) id 14.2.318.3; Fri, 24 May 2013 22:30:02 +0000
Received: from mail108-co9-R.bigfish.com (10.236.132.245) by CO9EHSOBE040.bigfish.com (10.236.130.103) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 22:30:00 +0000
Received: from mail108-co9 (localhost [127.0.0.1])	by mail108-co9-R.bigfish.com (Postfix) with ESMTP id AB820C04FC	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 24 May 2013 22:30:00 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: 4
X-BigFish: PS4(zzzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzzz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail108-co9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT002.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB271; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail108-co9 (localhost.localdomain [127.0.0.1]) by mail108-co9 (MessageSwitch) id 1369434599259615_17142; Fri, 24 May 2013 22:29:59 +0000 (UTC)
Received: from CO9EHSMHS012.bigfish.com (unknown [10.236.132.230])	by mail108-co9.bigfish.com (Postfix) with ESMTP id 3C9B9380076; Fri, 24 May 2013 22:29:59 +0000 (UTC)
Received: from BL2PRD0310HT002.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS012.bigfish.com (10.236.130.22) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 22:29:59 +0000
Received: from BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) by BL2PRD0310HT002.namprd03.prod.outlook.com (10.255.97.37) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 22:29:55 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) with Microsoft SMTP Server (TLS) id 15.0.698.13; Fri, 24 May 2013 22:29:52 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Fri, 24 May 2013 22:29:52 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAbHCNg
Date: Fri, 24 May 2013 22:29:52 +0000
Message-ID: <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com>
In-Reply-To: <519F3364.80301@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:c925:1c0b:4358:e80a]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB271.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14MLTC103.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14MLTC103.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(65816001)(47446002)(80022001)(53806001)(44976003)(50466002)(69226001)(6806003)(76482001)(63696002)(81542001)(31966008)(79102001)(74876001)(74366001)(20776003)(74706001)(47776003)(23726002)(4396001)(74502001)(74662001)(49866001)(59766001)(46102001)(81342001)(33646001)(16676001)(51856001)(46406003)(56816002)(50986001)(47976001)(54356001)(54316002)(56776001)(74316001)(77982001)(47736001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB036; H:TK5EX14MLTC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:30:11 -0000

[...]
> The fact that you use a firewall is mostly irrelevant. I'd bet your firew=
all still
> reponds to some packets (e.g., packets with unsupported options?).
[..]

No, the Windows firewall doesn't allow any ICMP responses to unsolicited tr=
affic,
they're all dropped.  This is what is sometimes called "stealth mode".

> And, if
> that were not the case, I could rely on the
> ICMPv6 "address resolution failed" error messages sent by your local rout=
er
> (i.e., if I receive one of such messages, you're not there. If I don't, y=
ou are).

Ok, yes that one is interesting.

-Dave


From dthaler@microsoft.com  Fri May 24 15:46:00 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3339611E812E for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.842
X-Spam-Level: 
X-Spam-Status: No, score=-96.842 tagged_above=-999 required=5 tests=[AWL=-0.575, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_63=0.6, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqxGoMF69A0p for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 15:45:55 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0238.outbound.protection.outlook.com [207.46.163.238]) by ietfa.amsl.com (Postfix) with ESMTP id 253D421F90FD for <6man@ietf.org>; Fri, 24 May 2013 15:45:55 -0700 (PDT)
Received: from BL2FFO11FD028.protection.gbl (10.1.15.202) by BY2FFO11HUB032.protection.gbl (10.1.14.177) with Microsoft SMTP Server (TLS) id 15.0.698.0; Fri, 24 May 2013 22:44:47 +0000
Received: from TK5EX14HUBC104.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD028.mail.protection.outlook.com (10.173.161.107) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Fri, 24 May 2013 22:44:46 +0000
Received: from DB8EHSOBE014.bigfish.com (157.54.51.114) by mail.microsoft.com (157.54.80.25) with Microsoft SMTP Server (TLS) id 14.3.136.1; Fri, 24 May 2013 22:44:25 +0000
Received: from mail65-db8-R.bigfish.com (10.174.8.232) by DB8EHSOBE014.bigfish.com (10.174.4.77) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 22:43:38 +0000
Received: from mail65-db8 (localhost [127.0.0.1])	by mail65-db8-R.bigfish.com (Postfix) with ESMTP id 6EF85BC07B4	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 24 May 2013 22:43:38 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT002.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -26
X-BigFish: PS-26(zzbb2dI98dI9371I542I1432I111aI62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah5eeeK8275bh8275dhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh17ej9a9j1155h)
Received-SPF: softfail (mail65-db8: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT002.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB269; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail65-db8 (localhost.localdomain [127.0.0.1]) by mail65-db8 (MessageSwitch) id 1369435415752587_15143; Fri, 24 May 2013 22:43:35 +0000 (UTC)
Received: from DB8EHSMHS023.bigfish.com (unknown [10.174.8.244])	by mail65-db8.bigfish.com (Postfix) with ESMTP id B194AB80081; Fri, 24 May 2013 22:43:35 +0000 (UTC)
Received: from BL2PRD0310HT002.namprd03.prod.outlook.com (157.56.240.21) by DB8EHSMHS023.bigfish.com (10.174.4.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 22:43:35 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BL2PRD0310HT002.namprd03.prod.outlook.com (10.255.97.37) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 22:43:31 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) with Microsoft SMTP Server (TLS) id 15.0.698.13; Fri, 24 May 2013 22:43:28 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Fri, 24 May 2013 22:43:28 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Alissa Cooper <acooper@cdt.org>, Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAZOUUAAAClyEAAANgt8AAA0lZg
Date: Fri, 24 May 2013 22:43:28 +0000
Message-ID: <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:c925:1c0b:4358:e80a]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB269.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC104.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC104.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(24454002)(243025003)(43784003)(252514006)(479174002)(13464003)(189002)(377454002)(51704005)(74316001)(44976003)(46102001)(46406003)(74502001)(51856001)(54356001)(81342001)(47776003)(74662001)(16676001)(47976001)(20776003)(54316002)(33646001)(59766001)(50986001)(15202345002)(76482001)(4396001)(49866001)(79102001)(47736001)(63696002)(81542001)(69226001)(74706001)(56816002)(77982001)(31966008)(65816001)(80022001)(23726002)(47446002)(53806001)(74366001)(56776001)(6806003)(74876001)(50466002)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB032; H:TK5EX14HUBC104.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 085634EFF4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 22:46:00 -0000

It also now occurs to me that since RFC 3972 has IPR disclosures from both=
=20
Microsoft and Ericsson, those disclosures may or may not apply to
draft-ietf-6man-stable-privacy-addresses as well.

Per the Note Well, I'm at least sending this email, but will check with
Microsoft folks to see whether an IPR statement would be needed on=20
this draft (personally I have no clue).

I'd suggest that any Ericsson folks paying attention might need to do the s=
ame.

-Dave

> -----Original Message-----
> From: Dave Thaler
> Sent: Friday, May 24, 2013 3:20 PM
> To: Dave Thaler; Alissa Cooper; Fernando Gont
> Cc: 6man-chairs@tools.ietf.org; Brian Haberman; 6man@ietf.org; Ray Hunter=
;
> tom.petch; Christian Huitema; He Xuan
> Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> I'd also like to see CGAs (3972) added to this analysis.  It seems to me =
they're
> the existing standards-track "random-per-network" addresses.  So all of t=
he
> "random-per-network" statements would seem apply equally to the existing
> RFC.
>=20
> This draft references that RFC but does not contain any discussion on the
> relative use cases.  I.e., if I already use CGAs for my "random-per-netwo=
rk"
> solution, is there any benefit in this draft?
>=20
> What problem is this solving that wasn't already solved by that existing
> Proposed Standard RFC?
>=20
> -Dave
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf
> > Of Dave Thaler
> > Sent: Friday, May 24, 2013 3:04 PM
> > To: Alissa Cooper; Fernando Gont
> > Cc: 6man-chairs@tools.ietf.org; Brian Haberman; 6man@ietf.org; Ray
> > Hunter; tom.petch; Christian Huitema; He Xuan
> > Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
> >
> > Thanks Alissa for the nice table, this is very helpful.
> >
> > > -----Original Message-----
> > > From: Alissa Cooper [mailto:acooper@cdt.org]
> > > Sent: Friday, May 24, 2013 2:34 PM
> > > To: Fernando Gont
> > > Cc: Dave Thaler; 6man@ietf.org; 6man-chairs@tools.ietf.org; Brian
> > > Haberman; Ray Hunter; tom.petch; Christian Huitema; He Xuan
> > > Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
> > >
> > > This discussion got me thinking about how to be rigorous in
> > > articulating the specific threats that different kinds of addresses
> > > do and do not mitigate. I put together a little table to try to sum t=
his up:
> > > http://www.alissacooper.com/files/IPv6-address-threats.pdf
> > >
> > > The table assumes, for simplicity, that the node in question doesn't
> > > use any higher-layer identifiers and is never behind a firewall.
> > >
> > > I think I've seen four different kinds of threats described in the
> > > course of the discussion of this draft, listed as the columns in the =
table:
> > > (a) A typical address scanning attack for the purpose of exploiting
> > > the nodes found by scanning
> > > (b) An attack that involves scanning an address space, identifying
> > > which nodes respond, and subsequently tracking the locations of
> > > those nodes. I'm not exactly sure what the point of doing this is,
> > > so maybe it shouldn't be included, but I left it in.
> > > (c) An attack wherein the attacker receives a node's address through
> > > some channel (email, p2p serving, etc.) and then tracks the location
> > > of that node later.
> > > (d) An attack wherein the attacker receives a node's address through
> > > some channel and then correlates the node's activities together.
> >
> > I'm assuming here by (d) you mean correlation over_time_ of activities
> > from the same node, even if it never moves.
> >
> > >
> > > The rows of the table are the address generation methods that have
> > > been discussed. The first three are for nodes that only use stable
> > > addresses and never use temporary addresses. Incidentally, I assume
> > > that it is this kind of configuration that Fernando's draft is
> > > targeting -- the scenario where a network administrator has disabled
> > > temporary addresses regardless of the desires of the user, as
> > > described in section 1 of the draft. As can be seen in the table,
> > > both random and random-per-network (my term for what the draft calls
> > > stable
> > privacy addresses) mitigate both types of address scanning attacks.
> > > Random-per-network additionally mitigates location tracking and
> > > potentially reduces the amount of time over which correlation can
> > > take
> > place.
> > >
> > > The second group of three are for nodes that only use temporary
> > > addresses (but that also configure a stable address that never gets
> > > used). This is what would be expected by users that want to avoid
> > > correlation attacks, assuming their admins allow it. In this case
> > > random and random-per-network provide equivalent protection.
> > >
> > > The last group of three are for nodes that use both temporary and
> > > stable addresses. Again here both random and random-per-network
> > > prevent the first two attacks, but random-per-network also prevents
> > > location tracking and potentially reduces the scope for correlation.
> > >
> > > I think the conclusion from this is that if there are lots of nodes
> > > out there that want to be protected from location tracking and
> > > correlation but their admins won't let them use temporary addresses,
> > > then random-per-network (row 3) provides some benefits over random
> > (row 2).
> >
> > Also, for nodes that never move (e.g., servers, desktop PCs, etc.)
> > random and random-per-network are equivalent.
> >
> > >
> > > If we're talking about the case
> > > where a node can use temporary addresses and only uses them, random
> > > and random-per-network provide the same benefits (rows 5 and 6). I'm
> > > assuming those are the two common cases (could be wrong though).
> > >
> > > If we take away the assumption that the node uses no higher-layer
> > > identifiers, then correlation becomes possible in all of the cases
> > > for the duration of max(life of higher-layer identifier, longest-live=
d
> address).
> >
> > Agree.
> >
> > >
> > > If we take away the assumption that the node is never behind a
> > > firewall and assume that it will never respond to unsolicited
> > > packets (maybe too much too assume, but let's try), then the only
> > > differences between the address generation mechanisms are with
> > > respect to correlation. Random-per-network still provides some
> > > benefits over random
> > in this case.
> >
> > Agree.  For nodes that move between networks, yes.
> > Nodes that never move don't gain those benefits of course.
> >
> > >
> > > Not sure if this is helpful to anyone else, but it clarified my
> > > thinking on this a bit, and it might be worth making the threat
> > > analysis in the draft more specific along these lines.
> >
> > I think it would definitely help the draft to include this analysis.
> >
> > Thanks again,
> > -Dave
> >
> > >
> > > Alissa
> > >
> > > On May 24, 2013, at 5:31 AM, Fernando Gont <fgont@si6networks.com>
> > > wrote:
> > >
> > > > On 05/22/2013 03:34 AM, Dave Thaler wrote:
> > > >>> I attend an IETF meeting, and learn the IID of your laptop. Then
> > > >>> I can actively probe your node regarding "Is David at the office?=
"
> > > >>> "Is David at home?", etc.... simply because your IID is known
> > > >>> and
> > constant.
> > > >>
> > > >> Since you're making this personal... please explain how you can
> > > >> probe whether I'm at the office or at home, both of which are
> > > >> behind firewalls (so won't respond to arbitrary probes) and have
> > > >> address prefixes
> > > you don't know to begin with.
> > > >
> > > > As noted, this wasn't meant to be personal -- it was just meant to
> > > > be an example.
> > > >
> > > > Now, given the example under discussion:
> > > >
> > > > I could learn your IID when we both attend the IETF meeting. And I
> > > > could learn your prefixes when you post to mailing-lists from such
> places.
> > > > Then I could use Prefix|IID to track you.
> > > >
> > > > The fact that you use a firewall is mostly irrelevant. I'd bet
> > > > your firewall still reponds to some packets (e.g., packets with
> > > > unsupported options?). And, if that were not the case, I could
> > > > rely on the
> > > > ICMPv6 "address resolution failed" error messages sent by your
> > > > local router (i.e., if I receive one of such messages, you're not t=
here.
> > > > If I don't, you are).
> > > >
> > > > I've seen similar discussions for different kinds of IDs in the
> > > > past, and every time someone pushed a flawed/sub-optimal approach,
> > > > they got bitten. Moral of the story: don't leak more than
> > > > necessary to achieve your desired goal, or you'll be bitten.
> > > >
> > > > P.S.: This was discussed off-list already... but I posted this
> > > > on-list so that wg participants are aware of my response.
> > > >
> > > > Cheers,
> > > > --
> > > > Fernando Gont
> > > > SI6 Networks
> > > > e-mail: fgont@si6networks.com
> > > > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E
> 7492
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >



From dougb@dougbarton.us  Fri May 24 20:26:23 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587BB21F9339 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 20:26:23 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpHUNKkWeFoE for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 20:26:12 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 45E3021F90BB for <ipv6@ietf.org>; Fri, 24 May 2013 20:26:12 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532] (unknown [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532]) by dougbarton.us (Postfix) with ESMTPSA id ED06C22B42 for <ipv6@ietf.org>; Sat, 25 May 2013 03:26:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369452372; bh=PqT3vLk3wtaspRIZ0VMzJw29eHJs+j6X+c1zAjgnago=; h=Date:From:To:Subject:References:In-Reply-To; b=T8AP8LMty5rulVh2dKyANUvfhXyyiVk+wNhMpYmZRRwlHj78H//hwC2Qd7ZvtZE7E 85/HTjPRgNw0xF/uLalYQU22drAZzHGo/spSERr5pwwP9NndsxqMs66xK8xiR3BoQG He2m/YhBu5nfMdLZfjedVtgphzYPxN4XGnamn7JI=
Message-ID: <51A02F53.9040106@dougbarton.us>
Date: Fri, 24 May 2013 20:26:11 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Router advertisement based privacy - I-D: Action	:draft-rafiee-6man-ra-privacy
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com> <001f01ce57c8$83d80090$8b8801b0$@rozanak.com> <519E539B.9040203@globis.net> <006501ce5891$e35258d0$a9f70a70$@rozanak.com>
In-Reply-To: <006501ce5891$e35258d0$a9f70a70$@rozanak.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 03:26:23 -0000

On 05/24/2013 08:17 AM, Hosnieh Rafiee wrote:
> I just wonder why, when you can use a monitoring system to log all your
> events (MAC + IP) when you are inside a corporate network, you see this as a
> big issue.

I work primarily with customers who implement networks inside their own 
borders. Ray is 100% correct that stable addressing for end users is a 
very high priority for things like access control, accountability, 
reporting, SOX, etc. Whether or not it should  be so is an entirely 
different question. For the middle of the bell-shaped curve, it IS so.

For IPv6 purposes, I can tell those customers to turn off 4941 addresses 
and they're good to go. What I cannot do is tell them, "IPv6 addresses 
constantly rotate, so you will have to log every data connection, keep 
those logs for N {weeks|months|years}, and use them to find out who did 
what when, instead of going to the tool you use now which will tell you 
that in 2 seconds." If I tell customers that this is the cost of IPv6, 
they will simply tell me "No thank you," and continue using their 
(comfortable, familiar) 1918 addresses internally behind their NAT.

We have to stop the line of thinking that goes, "We can introduce $this 
cool new feature to IPv6, and the cost is only $so_much." "The Market" 
has already responded with deafening silence to the costs that already 
exist to migrate to IPv6. Adding more is not an option.

Doug


From internet-drafts@ietf.org  Fri May 24 21:23:55 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0BF21E804B; Fri, 24 May 2013 21:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcwqcrAd99qd; Fri, 24 May 2013 21:23:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A79411E80AD; Fri, 24 May 2013 21:23:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ug-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130525042355.10057.59918.idtracker@ietfa.amsl.com>
Date: Fri, 24 May 2013 21:23:55 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 04:23:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : Significance of IPv6 Interface Identifiers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ug-01.txt
	Pages           : 11
	Date            : 2013-05-24

Abstract:
   The IPv6 addressing architecture includes a unicast interface
   identifier that is used in the creation of many IPv6 addresses.
   Interface identifiers are formed by a variety of methods.  This
   document clarifies that the bits in an interface identifier have no
   generic meaning and that the identifier should be treated as an
   opaque value.  In particular, RFC 4291 defines a method by which the
   Universal and Group bits of an IEEE link-layer address are mapped
   into an IPv6 unicast interface identifier.  This document clarifies
   that those bits apply only to interface identifiers that are derived
   from an IEEE link-layer address.  It updates RFC 4291 accordingly.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ug-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-ug-01


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


From brian.e.carpenter@gmail.com  Fri May 24 21:30:28 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE54621F91A0 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 21:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.201
X-Spam-Level: 
X-Spam-Status: No, score=-103.201 tagged_above=-999 required=5 tests=[AWL=0.398, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKwPYrzs+dQ6 for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 21:30:24 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4509321F91B2 for <ipv6@ietf.org>; Fri, 24 May 2013 21:30:24 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb11so3626307pad.9 for <ipv6@ietf.org>; Fri, 24 May 2013 21:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=lY+YworJIM1izoJ35q+56F0949UhmsLJI0gFqq1MlF8=; b=BQw7jnqUgZw3ckXQo01alkSFdNFOomd7fFaGzmZFxsbb7MTOtuSz78Z1lTNuIp6h+P aiuHgsxfw3tSjRNLgyDAmv9WWbbD1eFCH7ZFzTdE8oEp0h6b7ZZYrifvNSQ6EooBzSn2 28r375N5anZeKEyxGA2901ewSyrk482KkrLxr+w72caHeBhk8B+xHqUHzVAYipkDidcO fjN0suGquIF6XdBZz+hFeTt6EG+ygfKbqWM7IcOKM84wel9x76cIMuEMm19cfwkabWsR o2fMqSkMBrygkQeLaV7z8UBJEoDHVBZUmpqi0ou4UnriBL4YvGwfFw6LSFjqKSRdLjXe UoKA==
X-Received: by 10.68.226.39 with SMTP id rp7mr20387920pbc.97.1369456224012; Fri, 24 May 2013 21:30:24 -0700 (PDT)
Received: from [192.168.1.2] (229.187.252.27.dyn.cust.vf.net.nz. [27.252.187.229]) by mx.google.com with ESMTPSA id dr6sm20288574pac.11.2013.05.24.21.30.20 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 21:30:22 -0700 (PDT)
Message-ID: <51A03E67.6040009@gmail.com>
Date: Sat, 25 May 2013 16:30:31 +1200
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-ug-01.txt]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 04:30:29 -0000

Hi,

This version is intended to respond to WG comments. In particular:

- the title, Abstract and text have been modified to clarify
  the nature of the entire IID, not just the U/G bits;

- there is additional text about DAD failures;

- expanded IANA considerations.

Please read and comment.

   Brian + Sheng

-------- Original Message --------
Subject: I-D Action: draft-ietf-6man-ug-01.txt
Date: Fri, 24 May 2013 21:23:55 -0700
From: internet-drafts@ietf.org
Reply-To: 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           : Significance of IPv6 Interface Identifiers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ug-01.txt
	Pages           : 11
	Date            : 2013-05-24

Abstract:
   The IPv6 addressing architecture includes a unicast interface
   identifier that is used in the creation of many IPv6 addresses.
   Interface identifiers are formed by a variety of methods.  This
   document clarifies that the bits in an interface identifier have no
   generic meaning and that the identifier should be treated as an
   opaque value.  In particular, RFC 4291 defines a method by which the
   Universal and Group bits of an IEEE link-layer address are mapped
   into an IPv6 unicast interface identifier.  This document clarifies
   that those bits apply only to interface identifiers that are derived
   from an IEEE link-layer address.  It updates RFC 4291 accordingly.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ug-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ug-01


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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt



From acooper@cdt.org  Fri May 24 14:33:40 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BE911E811F for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 14:33:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.779
X-Spam-Level: 
X-Spam-Status: No, score=-101.779 tagged_above=-999 required=5 tests=[AWL=-0.380, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_63=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEjhkMnMvU2Q for <ipv6@ietfa.amsl.com>; Fri, 24 May 2013 14:33:36 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC7911E8120 for <6man@ietf.org>; Fri, 24 May 2013 14:33:36 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Fri, 24 May 2013 17:33:31 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <519F3364.80301@si6networks.com>
Date: Fri, 24 May 2013 17:33:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Sat, 25 May 2013 02:24:58 -0700
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 24 May 2013 21:33:41 -0000

This discussion got me thinking about how to be rigorous in articulating =
the specific threats that different kinds of addresses do and do not =
mitigate. I put together a little table to try to sum this up: =
http://www.alissacooper.com/files/IPv6-address-threats.pdf

The table assumes, for simplicity, that the node in question doesn't use =
any higher-layer identifiers and is never behind a firewall.=20

I think I've seen four different kinds of threats described in the =
course of the discussion of this draft, listed as the columns in the =
table:
(a) A typical address scanning attack for the purpose of exploiting the =
nodes found by scanning
(b) An attack that involves scanning an address space, identifying which =
nodes respond, and subsequently tracking the locations of those nodes. =
I'm not exactly sure what the point of doing this is, so maybe it =
shouldn't be included, but I left it in.
(c) An attack wherein the attacker receives a node's address through =
some channel (email, p2p serving, etc.) and then tracks the location of =
that node later.
(d) An attack wherein the attacker receives a node's address through =
some channel and then correlates the node's activities together.

The rows of the table are the address generation methods that have been =
discussed. The first three are for nodes that only use stable addresses =
and never use temporary addresses. Incidentally, I assume that it is =
this kind of configuration that Fernando's draft is targeting -- the =
scenario where a network administrator has disabled temporary addresses =
regardless of the desires of the user, as described in section 1 of the =
draft. As can be seen in the table, both random and random-per-network =
(my term for what the draft calls stable privacy addresses) mitigate =
both types of address scanning attacks. Random-per-network additionally =
mitigates location tracking and potentially reduces the amount of time =
over which correlation can take place.

The second group of three are for nodes that only use temporary =
addresses (but that also configure a stable address that never gets =
used). This is what would be expected by users that want to avoid =
correlation attacks, assuming their admins allow it. In this case random =
and random-per-network provide equivalent protection.

The last group of three are for nodes that use both temporary and stable =
addresses. Again here both random and random-per-network prevent the =
first two attacks, but random-per-network also prevents location =
tracking and potentially reduces the scope for correlation.

I think the conclusion from this is that if there are lots of nodes out =
there that want to be protected from location tracking and correlation =
but their admins won't let them use temporary addresses, then =
random-per-network (row 3) provides some benefits over random (row 2). =
If we're talking about the case where a node can use temporary addresses =
and only uses them, random and random-per-network provide the same =
benefits (rows 5 and 6). I'm assuming those are the two common cases =
(could be wrong though).

If we take away the assumption that the node uses no higher-layer =
identifiers, then correlation becomes possible in all of the cases for =
the duration of max(life of higher-layer identifier, longest-lived =
address).

If we take away the assumption that the node is never behind a firewall =
and assume that it will never respond to unsolicited packets (maybe too =
much too assume, but let's try), then the only differences between the =
address generation mechanisms are with respect to correlation. =
Random-per-network still provides some benefits over random in this =
case.

Not sure if this is helpful to anyone else, but it clarified my thinking =
on this a bit, and it might be worth making the threat analysis in the =
draft more specific along these lines.

Alissa

On May 24, 2013, at 5:31 AM, Fernando Gont <fgont@si6networks.com> =
wrote:

> On 05/22/2013 03:34 AM, Dave Thaler wrote:
>>> I attend an IETF meeting, and learn the IID of your laptop. Then I =
can actively
>>> probe your node regarding "Is David at the office?" "Is David at =
home?",
>>> etc.... simply because your IID is known and constant.
>>=20
>> Since you're making this personal... please explain how you can probe =
whether=20
>> I'm at the office or at home, both of which are behind firewalls (so =
won't respond
>> to arbitrary probes) and have address prefixes you don't know to =
begin with.
>=20
> As noted, this wasn't meant to be personal -- it was just meant to be =
an
> example.
>=20
> Now, given the example under discussion:
>=20
> I could learn your IID when we both attend the IETF meeting. And I =
could
> learn your prefixes when you post to mailing-lists from such places.
> Then I could use Prefix|IID to track you.
>=20
> The fact that you use a firewall is mostly irrelevant. I'd bet your
> firewall still reponds to some packets (e.g., packets with unsupported
> options?). And, if that were not the case, I could rely on the
> ICMPv6 "address resolution failed" error messages sent by your local
> router (i.e., if I receive one of such messages, you're not there. If =
I
> don't, you are).
>=20
> I've seen similar discussions for different kinds of IDs in the past,
> and every time someone pushed a flawed/sub-optimal approach, they got
> bitten. Moral of the story: don't leak more than necessary to achieve
> your desired goal, or you'll be bitten.
>=20
> P.S.: This was discussed off-list already... but I posted this on-list
> so that wg participants are aware of my response.
>=20
> Cheers,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
>=20



From v6ops@globis.net  Sat May 25 02:55:30 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84FD321F9410 for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 02:55:30 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZoMidArCCJSa for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 02:55:29 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 70FC721F93E1 for <ipv6@ietf.org>; Sat, 25 May 2013 02:55:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 59BBE8700DD; Sat, 25 May 2013 11:55:13 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXH3WbmrUCj7; Sat, 25 May 2013 11:55:13 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 3144C8700BA; Sat, 25 May 2013 11:55:13 +0200 (CEST)
Message-ID: <51A08A7A.4000700@globis.net>
Date: Sat, 25 May 2013 11:55:06 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com>
In-Reply-To: <519FD295.2060201@gmail.com>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 09:55:30 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 24 May 2013 22:50
> On 25/05/2013 00:40, John Leslie wrote:
>> Ray Hunter <v6ops@globis.net> wrote:
>>> I would also like to see some text on whether it is possible/desirable
>>> for a middleware box to strip unknown headers, or even some known
>>> headers, rather than making a binary decision to drop or transmit the
>>> entire packet. If (new) headers are truly optional or experimental, the
>>> residual stripped packet may still have value e.g. stripping hop by hop
>>> extension headers on entry to/ egress from a corporate network or
>>> transit AS. That way the (new) extension headers could be usefully
>>> deployed in an AS that supports them, but the end to end traffic would
>>> not be blocked further along the path by firewalls in an AS that does not.
>>    I had a similar thought -- even going so far as to posit a way to
>> notate that a header had been stripped...
>>
>>    I think the answer is we don't want to do that in this document;
>> nonetheless some folks are likely to try it. I think a mention of the
>> issue, and a reference to RFC(s) stating the current rules, would help.
>
> What rules? As far as I know, no such mechanism is defined or allowed,
> so there is nothing to refer to. I would object (as a WG participant)
> to even mentioning such a mechanism. (As a document editor, I would
> of course edit the document according to WG consensus.)
It's a clear answer that you feel stripping of headers from the chain is
not allowed, and stating that in the draft this would give clear
direction to middlebox developers.

But equally, and without wanting to appear confrontational, I thought
that the point of the header chain and the fact the header chain was
excluded from checksums, was to allow various middleware boxes to
process portions of the packet on the fly en route as appropriate, thus
fostering innovation.

As an example, the flow label has certain limitations and DSCP is
limited, so inclusion of an extra header with a tag to be used for
traffic engineering purposes (and which only has significance within a
single AS) might prove useful in the future, without having to resort to
tunnels and wrappers. On the other hand, transmitting that tag over an
AS boundary might prove harmful.

So inserting and stripping headers at various points on the path could
conceivably provide useful innovation IMHO. So wouldn't it be a bit
self-inconsistent for this draft to block that if the stated aim is to
foster innovation?


>>    (The prime purpose of this document is creating an IANA registry;
>> that purpose should not be clouded by discussion of what firewalls
>> "should" do.)
>
> Not so. The prime purpose of this document is to make extension headers
> useable. The registry is a means to that end; describing precisely how
> middleboxes should treat them is another means to that end. We can make
> that clearer in the text, of course.
>
> Describing how middleboxes might block or destroy them is antithetical
> to the purpose of the document. That's why Ray says "I'm not sure the
> current text is entirely balanced in this respect." He's right. Again
> speaking as a WG participant, I'm happy with that.

So you're asking the WG to make a consensus call that a default drop
policy in firewalls is harmful because the need for innovation on the
Internet always outweighs any benefit from devices shipping with such a
default drop policy?

Is that not akin to demanding that every Linux and BSD distribution
always ships with "experimental" repositories enabled, because we might
have some cool new kernel hack or network code that everyone must try?

Speaking entirely personally, I think the market has already clearly
decided on that point.
>
> On 25/05/2013 02:43, Tim Chown wrote:
>
>> A couple of additional comments.
>>
>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>
> Shouldn't this just be part of the Security Comsiderations for
> the definition of each header? The registry will always contain a pointer
> to the relevant RFCs. IANA can't do much if the Security Considerations
> are insufficient.
>
>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>
> I think we included that in an earlier draft, but then removed it
> because it appears to function as a null transport header. It's
> a judgment call, and only needs a few keystrokes to put it back in the
> list.
>
>    Brian
>


From acooper@cdt.org  Sat May 25 04:00:56 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8DF21F9425 for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 04:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.353
X-Spam-Level: 
X-Spam-Status: No, score=-102.353 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MfOi5ZmKzmBW for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 04:00:51 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id CD62B21F930A for <6man@ietf.org>; Sat, 25 May 2013 04:00:50 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Sat, 25 May 2013 07:00:22 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <519FE98D.8070705@gmail.com>
Date: Sat, 25 May 2013 07:00:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D2AAC51-57A9-49E8-9A61-A3138A7B531E@cdt.org>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com>	<519AD0EF.60600@si6networks.com>	<87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com>	<519F3364.80301@si6networks.com>	<AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <519FE98D.8070705@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Sat, 25 May 2013 04:10:00 -0700
Cc: Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 11:00:56 -0000

I made updates in response to this email and Dave's emails and made the =
table publicly viewable and editable if folks want to make further =
changes themselves: =
https://docs.google.com/spreadsheet/ccc?key=3D0Au4OS7RZgZwHdHozNzNHdUNtVEJ=
SNlo3N3NFMG5Wa1E&usp=3Dsharing

On May 24, 2013, at 6:28 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 25/05/2013 10:04, Dave Thaler wrote:
>> Thanks Alissa for the nice table, this is very helpful.
>=20
> Agreed. Two points though:
>=20
> 1. It seems to me that location tracking to the level of the 64-bit
> prefix is *always* possible, which may well identify a specific
> customer and/or physical location, but not a specific host and/or
> user. That qualifies column (c).
>=20
> 2. For completeness, include static manual addresses (yes, they
> still exist in IPv6), which presumably get "possible" in every
> column.
>=20
>   Brian
>=20



From rdroms@cisco.com  Sat May 25 06:59:19 2013
Return-Path: <rdroms@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEF6821F8900; Sat, 25 May 2013 06:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F467bN5SIyM4; Sat, 25 May 2013 06:59:15 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 07EB821F8916; Sat, 25 May 2013 06:59:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1510; q=dns/txt; s=iport; t=1369490355; x=1370699955; h=from:to:cc:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=HkbBluw/FOofuu/VZ+68HJOo8AKyfGjfCILmP5y5g1A=; b=A0iKqpTugZ9K6n3lS3jC0bsYzeewvyHHA5lgTn5ElDJtRGipPk2/t3vH hYzLi1txef1u+N3osoKw11YZHNyEyTTe6pVcMjIPlQ1lIbaQ+20BJ2Aki GNXsMip8bs1UwrXjpetHz3swin57j1K+71bfBsSCH1ljyDPAdEp/lKUAC o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnEGANDCoFGtJXG9/2dsb2JhbABagwgwwjeBBhZtB4IjAQEBAwE6PQIFCwIBGQMBAgsUEDIbAggCBA4FCAGHfgYMvBOObDENgm1hA5hkkBeDD4Im
X-IronPort-AV: E=Sophos;i="4.87,741,1363132800"; d="scan'208";a="214931207"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-6.cisco.com with ESMTP; 25 May 2013 13:59:13 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4PDxCU6032277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 25 May 2013 13:59:12 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.232]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Sat, 25 May 2013 08:59:12 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: "6man@ietf.org" <6man@ietf.org>
Subject: Fwd: New Version Notification for draft-droms-6man-multicast-scopes-00.txt
Thread-Topic: New Version Notification for draft-droms-6man-multicast-scopes-00.txt
Thread-Index: AQHOVyC3u4DpmQfwQ0+bgRMNO4shfw==
Date: Sat, 25 May 2013 13:59:12 +0000
Message-ID: <4518F39EB578034D8C99A9B7776CDBA36A0A37@xmb-aln-x04.cisco.com>
References: <20130522191522.2297.24938.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.164.54]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D5B9CAC1A2264842BF31BF130E46AF30@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "v6ops@ietf.org Operations" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 13:59:20 -0000

This draft proposes to redefine IPv6 multicast scope 0x03 from "reserved" t=
o "Network-Specific scope, greater than Link-Local scope, defined automatic=
ally from the network topology".  The expectation is that mesh trickle mult=
icast, as defined in draft-ietf-roll-trickle-mcast, will define multicast s=
cope 0x03 as "all interfaces attached to links in the mesh", for use in mul=
ticast delivery.

I've requested a slot on the 6man agenda in Berlin to discuss the draft.

- Ralph

Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-droms-6man-multicast-scopes-0=
0.txt
> Date: May 22, 2013 3:15:22 PM EDT
> To: Ralph Droms <rdroms@cisco.com>
>=20
>=20
> A new version of I-D, draft-droms-6man-multicast-scopes-00.txt
> has been successfully submitted by Ralph Droms and posted to the
> IETF repository.
>=20
> Filename:	 draft-droms-6man-multicast-scopes
> Revision:	 00
> Title:		 IPv6 Multicast Address Scopes
> Creation date:	 2013-05-22
> Group:		 Individual Submission
> Number of pages: 3
> URL:             http://www.ietf.org/internet-drafts/draft-droms-6man-mul=
ticast-scopes-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-droms-6man-multica=
st-scopes
> Htmlized:        http://tools.ietf.org/html/draft-droms-6man-multicast-sc=
opes-00
>=20
>=20
> Abstract:
>   This document updates the definitions of IPv6 multicast scopes.
>=20
>=20
>=20
>=20
> The IETF Secretariat
>=20


From ietf@rozanak.com  Sat May 25 08:31:13 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72AB21F880F for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 08:31:13 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNXSU02ryD7a for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 08:31:09 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 10C4921F84E7 for <ipv6@ietf.org>; Sat, 25 May 2013 08:31:08 -0700 (PDT)
Received: from kopoli (g225190094.adsl.alicedsl.de [92.225.190.94]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MLNMo-1UgofF3sPq-000efb; Sat, 25 May 2013 11:31:07 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Tim Chown'" <tjc@ecs.soton.ac.uk>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001f01ce57c8$83d80090$8b8801b0$@rozanak.com>	<519E539B.9040203@globis.net>	<006501ce5891$e35258d0$a9f70a70$@rozanak.com>	<426160B1-22EA-415B-BB18-46D4D9F72758@ecs.soton.ac.uk> <EMEW3|09fe86e0eba5e5ceda1ea6badb896bb2p4NH7M03tjc|ecs.soton.ac.uk|426160B1-22EA-415B-BB18-46D4D9F72758@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|09fe86e0eba5e5ceda1ea6badb896bb2p4NH7M03tjc|ecs.soton.ac.uk|426160B1-22EA-415B-BB18-46D4D9F72758@ecs.soton.ac.uk>
Subject: RE: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
Date: Sat, 25 May 2013 17:30:57 +0200
Message-ID: <000101ce595c$deafce90$9c0f6bb0$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlAJd9CgkAWXHjHwClNwzRwKO6ra6Aw02Af+YiZZzoA==
Content-Language: en-us
X-Provags-ID: V02:K0:ogFmGeCkygDhzOoGwKbNPUA9pJmpJ8OJHVSyOOxj1d/ KDZHZMFAyOMTzW6d8ESP22PSxIaONW7knQNhopzvEe9YrLQX77 trlz7I9HL5/ReOd6cjZgF28zOrQK7pf/DcxGxMClvU5eSBlJ7E iSlp5T/cBKT6tUxzeJRv/IYBScwOo1T2g1s0zk+BExdfvpj1gR Lem+uzW0gVebGl7T+PkEd8GAohe9pCfJSFGBGvy3CqOwcw1IZF Lj5LyJWWODVygyB2M7argXajKcCS7fRnxHcr4wiEe3b6U7Hc8L Nr8HO/hDa2eY4pvkyfwhl99yPhkojcooaf8TnaqthO8Bg/deJf +ysIaSRdMm7pjjipFYHA=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 15:31:13 -0000

> At our site we do just this; an SNMP-based tool harvests IP/MAC/port data
from
> the switches,routers etc.  I agree that it works very well.
> 
> That said, I expect quite a few (enterprise) sites will try to disable
4941. Or if
> they use ULAs as well, to disable for ULAs for internal traffic. That's
their
> choice.
> 
> The question is just what additional privacy you're delivering. In
principle, 4941
> addresses could be put in the DNS, or could be passed to peers to use for
> communications. Conceptually, it may be simpler to have just two classes
of
> address; stable privacy addresses (as per Fernando's text) and "temporary"
> privacy addresses which change over time (RFC 4941), whether the addresses
> are used to initiate or receive connections.

This is not something different from RFC 4941 or new, but just an update to
clarify the choice of  words used in the RFC that deals with the handling of
the lifetime. Some implementations did not make a good option choice which
then allowed for a correlation to be made between their generated IIDs. It
will not change the main nature of RFC 4941. Thus, if an enterprise wants to
use it, then they can do so. You can also use the privacy addresses in DNS,
but in this case I think it would be better to   generate the privacy
addresses using CGA or SSAS (new version). 
http://www.ietf.org/mail-archive/web/ipv6/current/msg17760.html
You can then use CGA-TSIG for dynamic DNS updates and solve both the problem
for privacy and DNS update. 

 
> In the meantime, it would be helpful if your draft listed the existing
privacy
> concerns you have, and the key benefits of your proposed mechanism(s) as
> easy-to-parse bullet points in your text.  You can take out some of the
more
> general comments about privacy, e.g. the first paragraph of the
introduction.
> Make the abstract more snappy, move the points in there to bullet-point
> concerns in the main body, and make your proposed solution clearer.  I
think
> that would help other readers as well.  Just a suggestion at least.

Thanks , I will do it in the next version.

Thanks again,
Regards,
Hosnieh


From ietf@rozanak.com  Sat May 25 09:06:56 2013
Return-Path: <ietf@rozanak.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D42121F8BBC for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 09:06:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QsAOzTo9hb6 for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 09:06:50 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 520E321F8B65 for <ipv6@ietf.org>; Sat, 25 May 2013 09:06:50 -0700 (PDT)
Received: from kopoli (g225190094.adsl.alicedsl.de [92.225.190.94]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MIL5z-1UkPak1n1L-004ErN; Sat, 25 May 2013 12:06:48 -0400
From: "Hosnieh Rafiee" <ietf@rozanak.com>
To: "'Doug Barton'" <dougb@dougbarton.us>
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001f01ce57c8$83d80090$8b8801b0$@rozanak.com>	<519E539B.9040203@globis.net>	<006501ce5891$e35258d0$a9f70a70$@rozanak.com> <51A02F53.9040106@dougbarton.us>
In-Reply-To: <51A02F53.9040106@dougbarton.us>
Subject: RE: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
Date: Sat, 25 May 2013 18:06:39 +0200
Message-ID: <000201ce5961$db22e500$9168af00$@rozanak.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHkuRgQLUQieMf1iXLc6yqZx0HXlAJd9CgkAWXHjHwClNwzRwJyrNdQmKLtoQA=
Content-Language: en-us
X-Provags-ID: V02:K0:5epG80CSp04keIFciydg0Fo5yVI9AjmHvpGUzm8A5zm DnWFPv9fuxYxHmRZQViF/QreKE/TJorbdaYxmrj7Kv3ggDvCVG 1qCvCB3cqNdygBA2CBPwdjux1BC7W2ePJue3JmP7p3vcJIuU5B 7mSFvc+cfDI8mZIaXhunSr/OcL3udA6WIx0412cZhFPHvp/zrS Oo0arPVXyXgORSSk5ZosFiHjiB5eo3SIjGzP2JOLvipXRnvpJM 2WYcEazRp651VqNoubLQ8Hn7euTow7/84jypMYQs6c4WxzF4xB x74UFnCwqeDCQ2Wh0l7Hg2VbdCF/PkE+ifHSZcClXcaT8DIZ7Q 3+xNAaPQPCevmsETfuGM=
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 16:06:56 -0000

 
> I work primarily with customers who implement networks inside their own
> borders. Ray is 100% correct that stable addressing for end users is a
very high
> priority for things like access control, accountability, reporting, SOX,
etc.
> Whether or not it should  be so is an entirely different question. For the
middle
> of the bell-shaped curve, it IS so.

As I explained in my answer to Ray in my last message, if monitoring and
other things are your first priority, then you can use another approach
rather than that of RFC 4941. But  you cannot say that this RFC will not be
used in future because we think that our customers won't want to spend any
more pennies on their current systems. It is again their choice. There are
also customers who would prefer to use that RFC rather than another
approach. 
What I am trying to do in my draft is give customers, who want to use this
RFC 4941, have a better choice of implementation options than they do now
(it might be used along with any other approach that is not based on the use
of a MAC address) 
About privacy. The laws of many countries are not concerned with privacy
which is actually the opposite of what is true in other countries. An
example can be found in the EU  where there are two DPDs, one promulgated in
1995 and the other in 2012. Both were concerned with privacy, but after the
first one was not interpreted correctly by all countries the second one was
promulgated.  Your country might be among those countries where privacy
makes little sense to them. Some countries talk about privacy, but in action
and reality, there is no privacy for users.

Regards,
Hosnieh



From brian.e.carpenter@gmail.com  Sat May 25 13:36:06 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112D221F8629 for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 13:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.221
X-Spam-Level: 
X-Spam-Status: No, score=-103.221 tagged_above=-999 required=5 tests=[AWL=0.378, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHUtUkzgE-5E for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 13:36:00 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 07E2F21F86CB for <ipv6@ietf.org>; Sat, 25 May 2013 13:35:59 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so5491679pab.41 for <ipv6@ietf.org>; Sat, 25 May 2013 13:35:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wCDofUgbRFyv0UQVZgrwWeCeS16VvB4Q0SutD7a/6b0=; b=RALKCgALsycB9ZyRg/2iU8p9+XzhH8l3eux/b9c7wDaJeGhuu/KXQmOZ7BsWafiIgs ExR8FxDXyWchQULQLC0oVDgnJGswftjW/wO0f719cTMR1CwgNvv3TZ6FWWJFFeG77UNK 1vp0E2I+zGPOGOYnzKYEvUwizy1mZ6OGYwBedPohSceH+UHheICgOAtPYcOjTN4L4n3I 6sUX3E8vWB+RZPGR90JHniYklrCuflOnaC8pRlHe1bHOl95rmkJNzBWRuy+mPN1zpp/R LiWm+zTO6MECev25SnrKE3xXl8nPfLwptL/BVJCSh3cm/19urSilb7ogQa/h/AG7NyWw y30Q==
X-Received: by 10.66.19.234 with SMTP id i10mr23789191pae.152.1369514159670; Sat, 25 May 2013 13:35:59 -0700 (PDT)
Received: from [192.168.1.2] (229.187.252.27.dyn.cust.vf.net.nz. [27.252.187.229]) by mx.google.com with ESMTPSA id zy5sm21639174pbb.43.2013.05.25.13.35.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 May 2013 13:35:58 -0700 (PDT)
Message-ID: <51A120BA.2020805@gmail.com>
Date: Sun, 26 May 2013 08:36:10 +1200
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: Ray Hunter <v6ops@globis.net>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net>
In-Reply-To: <51A08A7A.4000700@globis.net>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 20:36:06 -0000

Ray,

On 25/05/2013 21:55, Ray Hunter wrote:
>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>> 24 May 2013 22:50
>> On 25/05/2013 00:40, John Leslie wrote:
>>> Ray Hunter <v6ops@globis.net> wrote:
>>>> I would also like to see some text on whether it is possible/desirable
>>>> for a middleware box to strip unknown headers, or even some known
>>>> headers, rather than making a binary decision to drop or transmit the
>>>> entire packet. If (new) headers are truly optional or experimental, the
>>>> residual stripped packet may still have value e.g. stripping hop by hop
>>>> extension headers on entry to/ egress from a corporate network or
>>>> transit AS. That way the (new) extension headers could be usefully
>>>> deployed in an AS that supports them, but the end to end traffic would
>>>> not be blocked further along the path by firewalls in an AS that does not.
>>>    I had a similar thought -- even going so far as to posit a way to
>>> notate that a header had been stripped...
>>>
>>>    I think the answer is we don't want to do that in this document;
>>> nonetheless some folks are likely to try it. I think a mention of the
>>> issue, and a reference to RFC(s) stating the current rules, would help.
>> What rules? As far as I know, no such mechanism is defined or allowed,
>> so there is nothing to refer to. I would object (as a WG participant)
>> to even mentioning such a mechanism. (As a document editor, I would
>> of course edit the document according to WG consensus.)

> It's a clear answer that you feel stripping of headers from the chain is
> not allowed, and stating that in the draft this would give clear
> direction to middlebox developers.

It seems completely clear to me from the words in RFC 2460 that the
only extension header that is to be inspected by intermediate nodes is
the hop-by-hop header, and that the design intention was that all
other headers were to be transmitted transparently. If we were being
strict, there's no need to do anything except bash middlebox implementers
over the head with those words. As far as I can tell, designers of
extension headers since RFC 2460 have relied completely on this.

But, in the real world we have firewalls that do *not* conform to 2460,
and we need to deal with them realistically.

> 
> But equally, and without wanting to appear confrontational, I thought
> that the point of the header chain and the fact the header chain was
> excluded from checksums, was to allow various middleware boxes to
> process portions of the packet on the fly en route as appropriate, thus
> fostering innovation.

Where do you find any support for that in RFC 2460? I see exactly the
opposite, and I'm not aware of any IETF specification that suggests
modification of extension headers on the fly. (Routing headers may
be modified at routing hops, but that is after the packet has been
delivered to its next hop.)

> As an example, the flow label has certain limitations and DSCP is
> limited, so inclusion of an extra header with a tag to be used for
> traffic engineering purposes (and which only has significance within a
> single AS) might prove useful in the future, without having to resort to
> tunnels and wrappers. On the other hand, transmitting that tag over an
> AS boundary might prove harmful.

If IPv6 had been designed that way, but it wasn't.

> So inserting and stripping headers at various points on the path could
> conceivably provide useful innovation IMHO. So wouldn't it be a bit
> self-inconsistent for this draft to block that if the stated aim is to
> foster innovation?

We'd have to invent a third form of extension header to do that (in addition
to HbH and E2E). It's an interesting idea, and I wouldn't want to exclude
it without debate, but I think it's on top of what this draft is trying to
do, which is to make E2E extension headers useable. (I assure you from experience
that they are not useable today, with off-the-shelf firewalls on the path).
> 
> 
>>>    (The prime purpose of this document is creating an IANA registry;
>>> that purpose should not be clouded by discussion of what firewalls
>>> "should" do.)
>> Not so. The prime purpose of this document is to make extension headers
>> useable. The registry is a means to that end; describing precisely how
>> middleboxes should treat them is another means to that end. We can make
>> that clearer in the text, of course.
>>
>> Describing how middleboxes might block or destroy them is antithetical
>> to the purpose of the document. That's why Ray says "I'm not sure the
>> current text is entirely balanced in this respect." He's right. Again
>> speaking as a WG participant, I'm happy with that.
> 
> So you're asking the WG to make a consensus call that a default drop
> policy in firewalls is harmful because the need for innovation on the
> Internet always outweighs any benefit from devices shipping with such a
> default drop policy?

No. Please read the draft very closely. What it intends to say is
that brainless default-deny is the wrong approach, that firewalls must
recognize all valid extensions (most of them don't) and allow
tailored drop rules per extension type (some of them don't). If the
draft doesn't say that, we'd be glad to adjust the wording to meet
the intent.

> Is that not akin to demanding that every Linux and BSD distribution
> always ships with "experimental" repositories enabled, because we might
> have some cool new kernel hack or network code that everyone must try?

No, the draft also contains words intended to explain that newly
defined extension headers will take time to be recognized by firewalls,
as well as providing a registry where firewall developers can find them
(which is not the case today). Again, if the words don't meet the
intent, please suggest new words.

> Speaking entirely personally, I think the market has already clearly
> decided on that point.

The draft is intended to deal with the real world, but if the IETF
doesn't specify how things should work, who else is going to?
Firewall developers are not deaf and blind to innovation, and in my
experience are open to this discussion.

    Brian

>> On 25/05/2013 02:43, Tim Chown wrote:
>>
>>> A couple of additional comments.
>>>
>>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>> Shouldn't this just be part of the Security Comsiderations for
>> the definition of each header? The registry will always contain a pointer
>> to the relevant RFCs. IANA can't do much if the Security Considerations
>> are insufficient.
>>
>>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>> I think we included that in an earlier draft, but then removed it
>> because it appears to function as a null transport header. It's
>> a judgment call, and only needs a few keystrokes to put it back in the
>> list.
>>
>>    Brian
>>
> 
> 

From dougb@dougbarton.us  Sat May 25 15:39:02 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 836BE21F8C4C for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 15:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AT6jwB93vJcg for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 15:39:02 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id EFD5121F8C1A for <ipv6@ietf.org>; Sat, 25 May 2013 15:39:01 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 01ACC22B42 for <ipv6@ietf.org>; Sat, 25 May 2013 22:39:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369521541; bh=otrlo852hO+CP0qFytXHN9cnFBEfsjZ3sX/83MZ6FKY=; h=Date:From:To:Subject:References:In-Reply-To; b=lsLh49hqCHxKczffEUhExlS3FqTQtULiz6EhPejd+EDkTKFUGP9O0HBmD7Vknj3fS eCapiKe68tWPucGeUPDL22/yVu8gcA5A9pQ0SWy2SrwVgEKyrzbdwiVELM3IBKCoud /+LrgpejPKCW15Fr89gdsV8mfGr3janJYsUe1MEY=
Message-ID: <51A13D84.8030109@dougbarton.us>
Date: Sat, 25 May 2013 15:39:00 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001f01ce57c8$83d80090$8b8801b0$@rozanak.com>	<519E539B.9040203@globis.net>	<006501ce5891$e35258d0$a9f70a70$@rozanak.com> <51A02F53.9040106@dougbarton.us> <000201ce5961$db22e500$9168af00$@rozanak.com>
In-Reply-To: <000201ce5961$db22e500$9168af00$@rozanak.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 25 May 2013 22:39:02 -0000

On 05/25/2013 09:06 AM, Hosnieh Rafiee wrote:
> As I explained in my answer to Ray in my last message, if monitoring and
> other things are your first priority, then you can use another approach
> rather than that of RFC 4941. But  you cannot say that this RFC will not be
> used in future because we think that our customers won't want to spend any
> more pennies on their current systems.

Hosnieh,

You are responding to something I didn't write, and ignoring what I did. :)

I'm ambivalent about your draft itself. What I responded to was your 
reply to Ray that organizations that need accountability can simply do 
more network probing, more logging, etc.

Doug


From fgont@si6networks.com  Sat May 25 23:13:44 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF1C721F8F0F for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 23:13:44 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6bHb66xlcMm for <ipv6@ietfa.amsl.com>; Sat, 25 May 2013 23:13:44 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 51D3221F8ED8 for <6man@ietf.org>; Sat, 25 May 2013 23:13:43 -0700 (PDT)
Received: from [2001:5c0:1400:a::2cf] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UgUCm-0007DU-Mi; Sun, 26 May 2013 08:13:20 +0200
Message-ID: <51A1A7FE.9010501@si6networks.com>
Date: Sun, 26 May 2013 08:13:18 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 06:13:45 -0000

Dave,

What does draft-ietf-6man-stable-privacy-addresses has to do with CGAs?

Has MS or Ericsson patented the use of PRFs?

Have you guys any IPR on RFC1948? -- Because
draft-ietf-6man-stableprivacy-addresses is essentially Bellovin's
RFC1948 applied to IPv6 addresses.

Thanks,
Fernando




On 05/25/2013 12:43 AM, Dave Thaler wrote:
> It also now occurs to me that since RFC 3972 has IPR disclosures from both 
> Microsoft and Ericsson, those disclosures may or may not apply to
> draft-ietf-6man-stable-privacy-addresses as well.
> 
> Per the Note Well, I'm at least sending this email, but will check with
> Microsoft folks to see whether an IPR statement would be needed on 
> this draft (personally I have no clue).
> 
> I'd suggest that any Ericsson folks paying attention might need to do the same.


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





From v6ops@globis.net  Sun May 26 01:51:59 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D89421F8F38 for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 01:51:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dtakofWebNkb for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 01:51:58 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 99A6B21F8F32 for <ipv6@ietf.org>; Sun, 26 May 2013 01:51:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 4EFF88700B1; Sun, 26 May 2013 10:51:41 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3Dp45Fg+YOC; Sun, 26 May 2013 10:51:41 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 22042870077; Sun, 26 May 2013 10:51:41 +0200 (CEST)
Message-ID: <51A1CD16.1060006@globis.net>
Date: Sun, 26 May 2013 10:51:34 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net> <51A120BA.2020805@gmail.com>
In-Reply-To: <51A120BA.2020805@gmail.com>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 08:51:59 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 25 May 2013 22:36
> Ray,
>
> On 25/05/2013 21:55, Ray Hunter wrote:
>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>> 24 May 2013 22:50
>>> On 25/05/2013 00:40, John Leslie wrote:
>>>> Ray Hunter <v6ops@globis.net> wrote:
>>>>> I would also like to see some text on whether it is possible/desirable
>>>>> for a middleware box to strip unknown headers, or even some known
>>>>> headers, rather than making a binary decision to drop or transmit the
>>>>> entire packet. If (new) headers are truly optional or experimental, the
>>>>> residual stripped packet may still have value e.g. stripping hop by hop
>>>>> extension headers on entry to/ egress from a corporate network or
>>>>> transit AS. That way the (new) extension headers could be usefully
>>>>> deployed in an AS that supports them, but the end to end traffic would
>>>>> not be blocked further along the path by firewalls in an AS that does not.
>>>>    I had a similar thought -- even going so far as to posit a way to
>>>> notate that a header had been stripped...
>>>>
>>>>    I think the answer is we don't want to do that in this document;
>>>> nonetheless some folks are likely to try it. I think a mention of the
>>>> issue, and a reference to RFC(s) stating the current rules, would help.
>>> What rules? As far as I know, no such mechanism is defined or allowed,
>>> so there is nothing to refer to. I would object (as a WG participant)
>>> to even mentioning such a mechanism. (As a document editor, I would
>>> of course edit the document according to WG consensus.)
>
>> It's a clear answer that you feel stripping of headers from the chain is
>> not allowed, and stating that in the draft this would give clear
>> direction to middlebox developers.
>
> It seems completely clear to me from the words in RFC 2460 that the
> only extension header that is to be inspected by intermediate nodes is
> the hop-by-hop header, and that the design intention was that all
> other headers were to be transmitted transparently. If we were being
> strict, there's no need to do anything except bash middlebox implementers
> over the head with those words. As far as I can tell, designers of
> extension headers since RFC 2460 have relied completely on this.
>
> But, in the real world we have firewalls that do *not* conform to 2460,
> and we need to deal with them realistically.
>
>> But equally, and without wanting to appear confrontational, I thought
>> that the point of the header chain and the fact the header chain was
>> excluded from checksums, was to allow various middleware boxes to
>> process portions of the packet on the fly en route as appropriate, thus
>> fostering innovation.

I guess we could always use a hop by hop option for that use case, so
that's no big deal to me.
> Where do you find any support for that in RFC 2460? I see exactly the
> opposite, and I'm not aware of any IETF specification that suggests
> modification of extension headers on the fly. (Routing headers may
> be modified at routing hops, but that is after the packet has been
> delivered to its next hop.)
With the danger of being unnecessarily pedantic, RFC2460 says "With one
exception, extension headers are not examined or processed by any node
along a packet's delivery path, until the packet reaches the node (or
each of the set of nodes, in the case of multicast) identified in the
Destination Address field of the IPv6 header."

And we're now defining how a middlebox along the path examines and
processes headers other than the hop by hop header. So pointing at 2460
alone wouldn't seem to be adequate to conclude that intermediate nodes
MUST either pass a packet unmodified or discard it.

I think that is worth pointing out in the draft that "Contrary to
RFC2460 Section 4, middleboxes, such as firewalls, load balancers or
packet classifiers, MAY examine and process the entire IPv6 packet
before making a decision to either forward or discard the packet."
>> As an example, the flow label has certain limitations and DSCP is
>> limited, so inclusion of an extra header with a tag to be used for
>> traffic engineering purposes (and which only has significance within a
>> single AS) might prove useful in the future, without having to resort to
>> tunnels and wrappers. On the other hand, transmitting that tag over an
>> AS boundary might prove harmful.
>
> If IPv6 had been designed that way, but it wasn't.
>
>> So inserting and stripping headers at various points on the path could
>> conceivably provide useful innovation IMHO. So wouldn't it be a bit
>> self-inconsistent for this draft to block that if the stated aim is to
>> foster innovation?
>
> We'd have to invent a third form of extension header to do that (in addition
> to HbH and E2E). It's an interesting idea, and I wouldn't want to exclude
> it without debate, but I think it's on top of what this draft is trying to
> do, which is to make E2E extension headers useable. (I assure you from experience
> that they are not useable today, with off-the-shelf firewalls on the path).
>>>>    (The prime purpose of this document is creating an IANA registry;
>>>> that purpose should not be clouded by discussion of what firewalls
>>>> "should" do.)
>>> Not so. The prime purpose of this document is to make extension headers
>>> useable. The registry is a means to that end; describing precisely how
>>> middleboxes should treat them is another means to that end. We can make
>>> that clearer in the text, of course.
>>>
>>> Describing how middleboxes might block or destroy them is antithetical
>>> to the purpose of the document. That's why Ray says "I'm not sure the
>>> current text is entirely balanced in this respect." He's right. Again
>>> speaking as a WG participant, I'm happy with that.
>> So you're asking the WG to make a consensus call that a default drop
>> policy in firewalls is harmful because the need for innovation on the
>> Internet always outweighs any benefit from devices shipping with such a
>> default drop policy?
>
> No. Please read the draft very closely. What it intends to say is
> that brainless default-deny is the wrong approach, that firewalls must
> recognize all valid extensions (most of them don't) and allow
> tailored drop rules per extension type (some of them don't). If the
> draft doesn't say that, we'd be glad to adjust the wording to meet
> the intent.
I've read the draft several times.

The two portions that lead me to conclude "default drop policy is evil" are:

1. "RFC 2460 requires destination hosts to discard packets containing
   unrecognised extension headers.  However, intermediate forwarding
   nodes MUST NOT do this by default, since that might cause them to
   inadvertently discard traffic using a recently defined extension
   header, not yet recognised by the intermediate node."

I do not see how this demand to forward unknown headers is in any way
consistent with a middlebox node being able to implement a "drop by
default" policy. It seems counter-intuitive from a security perspective
that an intermediate node, whose job it is to protect end nodes from
zero day exploits, MUST allow "unknown headers" to transit, whilst the
node they are supposed to be protecting MUST drop "unknown headers"
(which may well be the same ones crafted in some way to form an
exploit). It seems to me that this sentence implies that the danger of
false positives in firewall code (caused by innovation) are more harmful
than false negatives (firewall code and end node code has not yet caught
up with new standards or new exploits). I don't share that view and I'm
sure I'm not alone.

Also the above text would seem to be in direct contradiction to the
following text later in the draft:

Quote: "Forwarding nodes MUST be configurable to allow packets
containing unrecognised extension headers, and such packets MAY be
dropped by default."

I have no problem with that text.


2. "The default configuration SHOULD allow all defined extension headers. "

That, in my reading, is directly contrary to recommending that a
manufacturer ship a middlebox to run a "drop unless" policy out of the
shrinkwrap, which is de facto market behaviour. Market behaviour might
change, but attempting to reverse it via this draft undermines the rest
of the draft IMHO.

Hence my comment about enabling all "experimental" repositories by
default in Linux distributions. I'm also sure that I'm not alone in
believing that some existing headers and any new optional headers may
prove controversial from a security perspective. Previous operational
experience with extension headers has proven that a prudent approach to
introducing changes may be necessary for many customers.

I therefore suggest deleting this text.

regards,
RayH
>
>> Is that not akin to demanding that every Linux and BSD distribution
>> always ships with "experimental" repositories enabled, because we might
>> have some cool new kernel hack or network code that everyone must try?
>
> No, the draft also contains words intended to explain that newly
> defined extension headers will take time to be recognized by firewalls,
> as well as providing a registry where firewall developers can find them
> (which is not the case today). Again, if the words don't meet the
> intent, please suggest new words.
>
>> Speaking entirely personally, I think the market has already clearly
>> decided on that point.
>
> The draft is intended to deal with the real world, but if the IETF
> doesn't specify how things should work, who else is going to?
> Firewall developers are not deaf and blind to innovation, and in my
> experience are open to this discussion.
>
>     Brian
>
>>> On 25/05/2013 02:43, Tim Chown wrote:
>>>
>>>> A couple of additional comments.
>>>>
>>>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>>> Shouldn't this just be part of the Security Comsiderations for
>>> the definition of each header? The registry will always contain a pointer
>>> to the relevant RFCs. IANA can't do much if the Security Considerations
>>> are insufficient.
>>>
>>>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>>> I think we included that in an earlier draft, but then removed it
>>> because it appears to function as a null transport header. It's
>>> a judgment call, and only needs a few keystrokes to put it back in the
>>> list.
>>>
>>>    Brian
>>>
>>>


From fgont@si6networks.com  Sun May 26 05:27:42 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF42E21F8F0F for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:27:42 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZPIURYtVtfJ for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:27:42 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5A021F8895 for <ipv6@ietf.org>; Sun, 26 May 2013 05:27:41 -0700 (PDT)
Received: from [2001:5c0:1400:a::11] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Uga2v-00075Z-15; Sun, 26 May 2013 14:27:33 +0200
Message-ID: <51A1FFB3.3090505@si6networks.com>
Date: Sun, 26 May 2013 14:27:31 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: Router advertisement based privacy - I-D:	Action	:draft-rafiee-6man-ra-privacy
References: <000301ce57c5$52ee0ef0$f8ca2cd0$@rozanak.com>	<001401ce57c6$d93bf750$8bb3e5f0$@rozanak.com>	<3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk> <EMEW3|923fc0fa8e0aff7696bf9637a758a90fp4NCXu03tjc|ecs.soton.ac.uk|3353E00C-3C57-4D14-8DB7-B0116546AAAC@ecs.soton.ac.uk> <006401ce5883$2dd6e060$8984a120$@rozanak.com>
In-Reply-To: <006401ce5883$2dd6e060$8984a120$@rozanak.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 'Tim Chown' <tjc@ecs.soton.ac.uk>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 12:27:42 -0000

On 05/24/2013 03:32 PM, Hosnieh Rafiee wrote:
> about RFC 4941. You just used the current implementations with their current
> problems. The reason that I wrote this draft was that the "stable addresses"
> wanted to keep its IID within the same network and not assign several IIDs
> within the same networks, in contrary with RFC 4941. 

This is plain wrong.

RFC4941 calls for stable *and* temporary addresses.
draft-ietf-6man-stable-privacy-addresses improves the current stable
addresses.

You keep making statements that you don't back in any way... and that's
an inappropriate way of having a technical discussion.





> In my opinion, there is
> problems of leakage of users' private information such as bank accounts,
> names, pictures, etc during the time that the node has the same IID. This
> problem is more remarkable when the time the node is in the same network for
> a long time or permanently.

Please add and elaborate on this in your I-D, because I don't follow the
relationship between bank accounts and IPv6 addresses.

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





From fgont@si6networks.com  Sun May 26 05:34:19 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA90521F8F4A for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:34:19 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RowtawlNjPRj for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:34:19 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCB621F8F69 for <ipv6@ietf.org>; Sun, 26 May 2013 05:34:15 -0700 (PDT)
Received: from [2001:5c0:1400:a::11] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Uga9J-0007Cx-5X; Sun, 26 May 2013 14:34:09 +0200
Message-ID: <51A2013F.5050204@si6networks.com>
Date: Sun, 26 May 2013 14:34:07 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Hosnieh Rafiee <ietf@rozanak.com>
Subject: Re: solution to RFC 4941 I-D action : draft-rafiee-6man-ra-privacy.txt
References: <000001ce50e2$dc0aa840$941ff8c0$@rozanak.com>
In-Reply-To: <000001ce50e2$dc0aa840$941ff8c0$@rozanak.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, Bob Hinden <bob.hinden@gmail.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 12:34:19 -0000

On 05/14/2013 10:37 PM, Hosnieh Rafiee wrote:
> 2- Nodes may use an IID that was generated based on a MAC address and use
> this in their response
> A MAC based IID may still be valid and this RFC does not force the node to
> stop using it.
>  Solution: The node MUST not generate its IID based on a MAC address when
> using this approach. The Privacy Extension RFC does not clearly address
> this.

So I assume that you also require such IID to vary across networks, right?

If not, it would be pretty ironic (*) that you make the effort of
clarifying that the IID of temporary addresses should change when you
move from one network to another, but then allow the stable IID to
remain constant across networks.

(*) unless we just want to rubberstamp what Microsoft has implemented
(stable addresses with IIDs that are constant across networks), and
pretend that that's the right thing to do

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





From fernando@gont.com.ar  Sun May 26 05:47:27 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9769B21F8FBA for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pe1PDGC7orM for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:47:27 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id E572C21F8FA9 for <6man@ietf.org>; Sun, 26 May 2013 05:47:26 -0700 (PDT)
Received: from [2001:5c0:1400:a::11] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UgaLl-0007Xi-D6; Sun, 26 May 2013 14:47:01 +0200
Message-ID: <51A20440.4030304@gont.com.ar>
Date: Sun, 26 May 2013 14:46:56 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <deafa695f8004dc69996dee23e1400f8@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <deafa695f8004dc69996dee23e1400f8@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 12:47:27 -0000

On 05/25/2013 12:19 AM, Dave Thaler wrote:
> I'd also like to see CGAs (3972) added to this analysis.  It seems to me they're
> the existing standards-track "random-per-network" addresses.  So all of the
> "random-per-network" statements would seem apply equally to the existing RFC.
> 
> This draft references that RFC but does not contain any discussion on the
> relative use cases.  I.e., if I already use CGAs for my "random-per-network"
> solution, is there any benefit in this draft?
> 
> What problem is this solving that wasn't already solved by that existing 
> Proposed Standard RFC?

I could give you multiple reasons for
draft-ietf-6manstable-privacy-addresses:

* The whole point of CGAs is validating the ownership of an IPv6
address. If you're going to use CGAs for that, that's overkill
(bothering with a public key, etc., etc.)

* CGAs are more complex and difficult to undestand. OTOH, if one
understands RFC1948 or how a hash function works, understanding
draf-tietf-6man-stable-privacy-addresses is straightforward.

* CGAs are far more expensive than
draft-ietf-6man-stable-privacy-addresses. You compute at least two
hashes, where in stable privacy you need only one.

* CGAs require a specific hash algorithm (SHA-1), since they neey other
to be able to verify the CGA. We give implementations to employ the
algorithm they feel is more appropriate (based on their specific tradeoffs).

* CGAs are IPR encumbered. draft-ietf-6man-stable-privacy-addresses are not.

* CGAs cannot be used in conjunction with RFC4941.


To be honest, the argument of "using CGAs instead of stable privacy"
sounds to me pretty much like "you don't need a hammer, because you can
use pliers to knock the nail".

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fgont@si6networks.com  Sun May 26 05:50:15 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85CE321F8ADF for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:50:15 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRkeqXITSsOO for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 05:50:15 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id F17A221F8609 for <6man@ietf.org>; Sun, 26 May 2013 05:50:14 -0700 (PDT)
Received: from [2001:5c0:1400:a::11] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UgaOa-0007YG-37; Sun, 26 May 2013 14:49:56 +0200
Message-ID: <51A204F2.7060400@si6networks.com>
Date: Sun, 26 May 2013 14:49:54 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 12:50:15 -0000

On 05/25/2013 12:29 AM, Dave Thaler wrote:
> [...]
>> The fact that you use a firewall is mostly irrelevant. I'd bet your firewall still
>> reponds to some packets (e.g., packets with unsupported options?).
> [..]
> 
> No, the Windows firewall doesn't allow any ICMP responses to unsolicited traffic,
> they're all dropped.  This is what is sometimes called "stealth mode".
> 
>> And, if
>> that were not the case, I could rely on the
>> ICMPv6 "address resolution failed" error messages sent by your local router
>> (i.e., if I receive one of such messages, you're not there. If I don't, you are).
> 
> Ok, yes that one is interesting.

An attacker just needs one vector to be successful. And at the point
such vector is not under your control (as in this case), all bets are off.

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





From fgont@si6networks.com  Sun May 26 06:01:56 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A686421F8FEC for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 06:01:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYJpa8rqG6hT for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 06:01:56 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 06AAB21F8FA5 for <6man@ietf.org>; Sun, 26 May 2013 06:01:56 -0700 (PDT)
Received: from [2001:5c0:1400:a::11] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UgaZu-0007tE-Kw; Sun, 26 May 2013 15:01:38 +0200
Message-ID: <51A207B0.4000900@si6networks.com>
Date: Sun, 26 May 2013 15:01:36 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org>
In-Reply-To: <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 13:01:56 -0000

HI Alissa,

Thanks for posting this. Please find my comments inline...

On 05/24/2013 11:33 PM, Alissa Cooper wrote:
> 
> The rows of the table are the address generation methods that have
> been discussed. The first three are for nodes that only use stable
> addresses and never use temporary addresses. Incidentally, I assume
> that it is this kind of configuration that Fernando's draft is
> targeting 

Nope. We're improving stable addresses. Whether you use RFC4941 or not
is pretty much orthogonal.



>-- the scenario where a network administrator has disabled
> temporary addresses regardless of the desires of the user, as
> described in section 1 of the draft. As can be seen in the table,
> both random and random-per-network (my term for what the draft calls
> stable privacy addresses) mitigate both types of address scanning
> attacks. Random-per-network additionally mitigates location tracking
> and potentially reduces the amount of time over which correlation can
> take place.

This assessment is correct. Note, however, that stable privacy addresses
are also meant to be used in conjunction with rfc4941.



> The second group of three are for nodes that only use temporary
> addresses (but that also configure a stable address that never gets
> used). This is what would be expected by users that want to avoid
> correlation attacks, assuming their admins allow it. In this case
> random and random-per-network provide equivalent protection.

The problem here is that the assumption of "never gets used" is not
correct. Or, well, you might argue "is not intentionally used for
legitimate purposes".

An attacker can trigger the use of such addresses, e.g., y sending his
probe packets to the stable address.




> (row 2). If we're talking about the case where a node can use
> temporary addresses and only uses them, random and random-per-network
> provide the same benefits (rows 5 and 6). I'm assuming those are the
> two common cases (could be wrong though).

Please see above.



> If we take away the assumption that the node is never behind a
> firewall and assume that it will never respond to unsolicited packets
> (maybe too much too assume, but let's try), then the only differences
> between the address generation mechanisms are with respect to
> correlation. Random-per-network still provides some benefits over
> random in this case.

As noted, it is always possible to probe such node. e.g., rely on ICMPv6
"address resolution failed" from the local router at the victim cite to
tell whether the node is there or not.



> Not sure if this is helpful to anyone else, but it clarified my
> thinking on this a bit, and it might be worth making the threat
> analysis in the draft more specific along these lines.

How about including something along these lines (*) in an Appendix?

(*) Discussion of possible attacks, and what stable privacy addresses do
about them (analyzing this for every possible address generation
mechanism would be out of scope for this I-D, IMO).

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




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





From sm@resistor.net  Sun May 26 12:08:41 2013
Return-Path: <sm@resistor.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B98521F9031 for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 12:08:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKn3FGz+9Erk for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 12:08:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E8021F8F11 for <6man@ietf.org>; Sun, 26 May 2013 12:08:40 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4QJ8Xx7022504; Sun, 26 May 2013 12:08:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369595319; bh=XYFVE6Trc7wWxzMROO+zlQ0ZW6bQNXC14mKC0yUeQgQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eH4oGuYSCbC8blBFYyLdT24o+7lMS0s3gEJ9qRC6szDT+Ph9E+mxYgyM27rS+cqBq 2xHYNgERn+eyuv3mnhnbvd6sbqs2KzEfQcbifJjLeyXHUof5qmtgdAOUd6XyWNt/s7 VvJBNbwrBIgYeswS+liLSe0Ys6lzvH3v7t3DOgOU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369595319; i=@resistor.net; bh=XYFVE6Trc7wWxzMROO+zlQ0ZW6bQNXC14mKC0yUeQgQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=e+MOXK1nFr/JjcnXXXHA/zCjlEZa+pbCbjpaUy1KekWvFmeONVlsv4bDqsnMX9W1v 3oE6UqVRfb8XOgIllzp1y0zbJD9JPljG8TocMsAWi28bX9HBhSgf15XXaVZXGWazUw ThprZhpfDn3hZaiICN7x1cFYC8/L+tIcGJFXS54s=
Message-Id: <6.2.5.6.2.20130526113747.0c844960@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 May 2013 11:53:57 -0700
To: 6man-chairs@tools.ietf.org
From: SM <sm@resistor.net>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
In-Reply-To: <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.pro d.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Fernando Gont <fgont@si6networks.com>, 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 26 May 2013 19:08:41 -0000

At 15:43 24-05-2013, Dave Thaler wrote:
>It also now occurs to me that since RFC 3972 has IPR disclosures from both
>Microsoft and Ericsson, those disclosures may or may not apply to
>draft-ietf-6man-stable-privacy-addresses as well.
>
>Per the Note Well, I'm at least sending this email, but will check with
>Microsoft folks to see whether an IPR statement would be needed on
>this draft (personally I have no clue).
>
>I'd suggest that any Ericsson folks paying attention might need to 
>do the same.

draft-ietf-6man-stable-privacy-addresses-00 was submitted as a 
working group document in May 2012.  There was a Last Call in April 
2013.  The Acknowledgement Section clearly says that the algorithm 
specified in the draft has been inspired by RFC 1948.  There isn't 
any IPR disclosure filed against RFC 1948.

Does draft-ietf-6man-stable-privacy-addresses have to wait for IPR 
disclosures, if any, to be filed before it is moved forward?

Could someone provide a summary of the issues for 
draft-ietf-6man-stable-privacy-addresses-08?

Thanks,
-sm  


From brian.e.carpenter@gmail.com  Sun May 26 21:47:10 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3646321F8F44 for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 21:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tg0AmGs9v45E for <ipv6@ietfa.amsl.com>; Sun, 26 May 2013 21:47:09 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1688021F8F06 for <ipv6@ietf.org>; Sun, 26 May 2013 21:47:09 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id wz12so6345056pbc.31 for <ipv6@ietf.org>; Sun, 26 May 2013 21:47:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NP5yyBxmHKlyGWwNytV1YBcx57NKcwNP/Pw3q/ZDAyg=; b=NBxYDQooXVgVjPqT5WPvVDEZY9TDoyY8TRsagAzOt+hhfpfS3EjHi0a8IAXeU/iuKa CDvmjuxSG2Q0MWXTm8ukD+iqJH3m3Vrzd0tm0/nZtYJ3/cjGbOVfLnK1w1E3miofBKka FKNWLCmtAU+Ci2xcOKy9ae9KqiB6yOOMKakWDpgBmlBTO1idiBSgPW3gepuTBw8d3APV iFyUlGYz4KK02M2P2+xLVKaBMo9iUrDFjkqhby1BE65Cmmg/whtWueBk/u9DiDixWvIq mTzSpwfudSs7sER4yUdT6DnEf+4RXZu4pDlHp7pXefvZXmwahyAGmtfnxsIaCABZZwQv vALw==
X-Received: by 10.66.138.75 with SMTP id qo11mr27994265pab.172.1369630028741;  Sun, 26 May 2013 21:47:08 -0700 (PDT)
Received: from [192.168.1.2] (253.150.252.27.dyn.cust.vf.net.nz. [27.252.150.253]) by mx.google.com with ESMTPSA id 10sm26989606pbm.0.2013.05.26.21.47.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 21:47:07 -0700 (PDT)
Message-ID: <51A2E547.7040502@gmail.com>
Date: Mon, 27 May 2013 16:47:03 +1200
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: Ray Hunter <v6ops@globis.net>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net> <51A120BA.2020805@gmail.com> <51A1CD16.1060006@globis.net>
In-Reply-To: <51A1CD16.1060006@globis.net>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 May 2013 04:47:10 -0000

On 26/05/2013 20:51, Ray Hunter wrote:
>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>> 25 May 2013 22:36
>> Ray,
>>
>> On 25/05/2013 21:55, Ray Hunter wrote:
>>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>>> 24 May 2013 22:50
>>>> On 25/05/2013 00:40, John Leslie wrote:
>>>>> Ray Hunter <v6ops@globis.net> wrote:
>>>>>> I would also like to see some text on whether it is possible/desirable
>>>>>> for a middleware box to strip unknown headers, or even some known
>>>>>> headers, rather than making a binary decision to drop or transmit the
>>>>>> entire packet. If (new) headers are truly optional or experimental, the
>>>>>> residual stripped packet may still have value e.g. stripping hop by hop
>>>>>> extension headers on entry to/ egress from a corporate network or
>>>>>> transit AS. That way the (new) extension headers could be usefully
>>>>>> deployed in an AS that supports them, but the end to end traffic would
>>>>>> not be blocked further along the path by firewalls in an AS that does not.
>>>>>    I had a similar thought -- even going so far as to posit a way to
>>>>> notate that a header had been stripped...
>>>>>
>>>>>    I think the answer is we don't want to do that in this document;
>>>>> nonetheless some folks are likely to try it. I think a mention of the
>>>>> issue, and a reference to RFC(s) stating the current rules, would help.
>>>> What rules? As far as I know, no such mechanism is defined or allowed,
>>>> so there is nothing to refer to. I would object (as a WG participant)
>>>> to even mentioning such a mechanism. (As a document editor, I would
>>>> of course edit the document according to WG consensus.)
>>> It's a clear answer that you feel stripping of headers from the chain is
>>> not allowed, and stating that in the draft this would give clear
>>> direction to middlebox developers.
>> It seems completely clear to me from the words in RFC 2460 that the
>> only extension header that is to be inspected by intermediate nodes is
>> the hop-by-hop header, and that the design intention was that all
>> other headers were to be transmitted transparently. If we were being
>> strict, there's no need to do anything except bash middlebox implementers
>> over the head with those words. As far as I can tell, designers of
>> extension headers since RFC 2460 have relied completely on this.
>>
>> But, in the real world we have firewalls that do *not* conform to 2460,
>> and we need to deal with them realistically.
>>
>>> But equally, and without wanting to appear confrontational, I thought
>>> that the point of the header chain and the fact the header chain was
>>> excluded from checksums, was to allow various middleware boxes to
>>> process portions of the packet on the fly en route as appropriate, thus
>>> fostering innovation.
> 
> I guess we could always use a hop by hop option for that use case, so
> that's no big deal to me.
>> Where do you find any support for that in RFC 2460? I see exactly the
>> opposite, and I'm not aware of any IETF specification that suggests
>> modification of extension headers on the fly. (Routing headers may
>> be modified at routing hops, but that is after the packet has been
>> delivered to its next hop.)
> With the danger of being unnecessarily pedantic, RFC2460 says "With one
> exception, extension headers are not examined or processed by any node
> along a packet's delivery path, until the packet reaches the node (or
> each of the set of nodes, in the case of multicast) identified in the
> Destination Address field of the IPv6 header."
> 
> And we're now defining how a middlebox along the path examines and
> processes headers other than the hop by hop header. So pointing at 2460
> alone wouldn't seem to be adequate to conclude that intermediate nodes
> MUST either pass a packet unmodified or discard it.

Correct, that's why it's a standards track update. We are clarifying
the meaning.

> 
> I think that is worth pointing out in the draft that "Contrary to
> RFC2460 Section 4, middleboxes, such as firewalls, load balancers or
> packet classifiers, MAY examine and process the entire IPv6 packet
> before making a decision to either forward or discard the packet."

I'm not sure if it's really a MAY or simply a statement of what
occurs in the real world.

>>> As an example, the flow label has certain limitations and DSCP is
>>> limited, so inclusion of an extra header with a tag to be used for
>>> traffic engineering purposes (and which only has significance within a
>>> single AS) might prove useful in the future, without having to resort to
>>> tunnels and wrappers. On the other hand, transmitting that tag over an
>>> AS boundary might prove harmful.
>> If IPv6 had been designed that way, but it wasn't.
>>
>>> So inserting and stripping headers at various points on the path could
>>> conceivably provide useful innovation IMHO. So wouldn't it be a bit
>>> self-inconsistent for this draft to block that if the stated aim is to
>>> foster innovation?
>> We'd have to invent a third form of extension header to do that (in addition
>> to HbH and E2E). It's an interesting idea, and I wouldn't want to exclude
>> it without debate, but I think it's on top of what this draft is trying to
>> do, which is to make E2E extension headers useable. (I assure you from experience
>> that they are not useable today, with off-the-shelf firewalls on the path).
>>>>>    (The prime purpose of this document is creating an IANA registry;
>>>>> that purpose should not be clouded by discussion of what firewalls
>>>>> "should" do.)
>>>> Not so. The prime purpose of this document is to make extension headers
>>>> useable. The registry is a means to that end; describing precisely how
>>>> middleboxes should treat them is another means to that end. We can make
>>>> that clearer in the text, of course.
>>>>
>>>> Describing how middleboxes might block or destroy them is antithetical
>>>> to the purpose of the document. That's why Ray says "I'm not sure the
>>>> current text is entirely balanced in this respect." He's right. Again
>>>> speaking as a WG participant, I'm happy with that.
>>> So you're asking the WG to make a consensus call that a default drop
>>> policy in firewalls is harmful because the need for innovation on the
>>> Internet always outweighs any benefit from devices shipping with such a
>>> default drop policy?
>> No. Please read the draft very closely. What it intends to say is
>> that brainless default-deny is the wrong approach, that firewalls must
>> recognize all valid extensions (most of them don't) and allow
>> tailored drop rules per extension type (some of them don't). If the
>> draft doesn't say that, we'd be glad to adjust the wording to meet
>> the intent.
> I've read the draft several times.
> 
> The two portions that lead me to conclude "default drop policy is evil" are:
> 
> 1. "RFC 2460 requires destination hosts to discard packets containing
>    unrecognised extension headers.  However, intermediate forwarding
>    nodes MUST NOT do this by default, since that might cause them to
>    inadvertently discard traffic using a recently defined extension
>    header, not yet recognised by the intermediate node."
> 
> I do not see how this demand to forward unknown headers is in any way
> consistent with a middlebox node being able to implement a "drop by
> default" policy. It seems counter-intuitive from a security perspective
> that an intermediate node, whose job it is to protect end nodes from
> zero day exploits, MUST allow "unknown headers" to transit, whilst the
> node they are supposed to be protecting MUST drop "unknown headers"

Well, the IPv6 design was, I suspect, intended to make layer 3
firewalls unnecessary. (I am not claiming that has succeeded.) However,
the aim here was to write a spec that treads the narrow path between
making the Internet transparent to well-defined extension headers
and allowing firewalls to defend a perimeter. I think you're correct
that the present version is still slightly inconsistent, and needs
a bit more fine-tuning of the normative language.

> (which may well be the same ones crafted in some way to form an
> exploit). It seems to me that this sentence implies that the danger of
> false positives in firewall code (caused by innovation) are more harmful
> than false negatives (firewall code and end node code has not yet caught
> up with new standards or new exploits). I don't share that view and I'm
> sure I'm not alone.

No, it's a common view in some security circles. I don't happen to agree
with it as far as layer 3 attacks go; and not all sites would set the
risk vs innovation tradeoff at the same point. We really need this to
be under IT managers' control, I think.

> Also the above text would seem to be in direct contradiction to the
> following text later in the draft:
> 
> Quote: "Forwarding nodes MUST be configurable to allow packets
> containing unrecognised extension headers, and such packets MAY be
> dropped by default."

Yes, this is why the internal consistency of the draft probably
needs tuning. That sentence should take priority over the earlier
MUST NOT that you quoted. We missed that.

> I have no problem with that text.
> 
> 
> 2. "The default configuration SHOULD allow all defined extension headers. "
> 
> That, in my reading, is directly contrary to recommending that a
> manufacturer ship a middlebox to run a "drop unless" policy out of the
> shrinkwrap, which is de facto market behaviour. Market behaviour might
> change, but attempting to reverse it via this draft undermines the rest
> of the draft IMHO.

Why? It's a SHOULD, which means "there may exist valid reasons in particular
circumstances to ignore a particular item, but the full implications must
be understood and carefully weighed before choosing a different course."
Isn't that what firewall implementers do about every protocol feature
they consider?

Also, recall that the WG asked us to make the document applicable
to all kinds of middlebox, not just firewalls. Non-firewall boxes
certainly have no business censoring extension headers.

> Hence my comment about enabling all "experimental" repositories by
> default in Linux distributions. 

The word "defined" is supposed to mean "not experimental", at least in
my mind. Maybe the language needs to be more explicit on that point.
Perhaps we should be explicit that standards track action is needed.
That would update RFC 5237, which allows standards action *or*
IESG approval. No disrespect, but the latter seems very casual for
a new extension header.

> I'm also sure that I'm not alone in
> believing that some existing headers and any new optional headers may
> prove controversial from a security perspective. Previous operational
> experience with extension headers has proven that a prudent approach to
> introducing changes may be necessary for many customers.

Yes, certainly, and I think a few words on that would fit in the Security
Considerations, where it is already mentioned that deployment of a new
extension will be slow.

> I therefore suggest deleting this text.

But we're not defining firewall product specs here. We're defining
how to make IPv6 work. You are of course correct that firewall vendors
will do whatever they decide to do, but it seems to me that the IETF
position should always favour connectivity while pointing out
security risks and how to alleviate them.

    Brian

> 
> regards,
> RayH
>>> Is that not akin to demanding that every Linux and BSD distribution
>>> always ships with "experimental" repositories enabled, because we might
>>> have some cool new kernel hack or network code that everyone must try?
>> No, the draft also contains words intended to explain that newly
>> defined extension headers will take time to be recognized by firewalls,
>> as well as providing a registry where firewall developers can find them
>> (which is not the case today). Again, if the words don't meet the
>> intent, please suggest new words.
>>
>>> Speaking entirely personally, I think the market has already clearly
>>> decided on that point.
>> The draft is intended to deal with the real world, but if the IETF
>> doesn't specify how things should work, who else is going to?
>> Firewall developers are not deaf and blind to innovation, and in my
>> experience are open to this discussion.
>>
>>     Brian
>>
>>>> On 25/05/2013 02:43, Tim Chown wrote:
>>>>
>>>>> A couple of additional comments.
>>>>>
>>>>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>>>> Shouldn't this just be part of the Security Comsiderations for
>>>> the definition of each header? The registry will always contain a pointer
>>>> to the relevant RFCs. IANA can't do much if the Security Considerations
>>>> are insufficient.
>>>>
>>>>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>>>> I think we included that in an earlier draft, but then removed it
>>>> because it appears to function as a null transport header. It's
>>>> a judgment call, and only needs a few keystrokes to put it back in the
>>>> list.
>>>>
>>>>    Brian
>>>>
>>>>
> 
> 

From v6ops@globis.net  Mon May 27 00:32:42 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4547D21F8A14 for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 00:32:42 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EuAA8ou3-asz for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 00:32:41 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 58A0C21F8D31 for <ipv6@ietf.org>; Mon, 27 May 2013 00:32:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 83F1C8700D7; Mon, 27 May 2013 09:32:24 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MXwS1Smk8VVm; Mon, 27 May 2013 09:32:24 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 182DC870070; Mon, 27 May 2013 09:32:24 +0200 (CEST)
Message-ID: <51A30C01.1070601@globis.net>
Date: Mon, 27 May 2013 09:32:17 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net> <51A120BA.2020805@gmail.com> <51A1CD16.1060006@globis.net> <51A2E547.7040502@gmail.com>
In-Reply-To: <51A2E547.7040502@gmail.com>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 May 2013 07:32:42 -0000

> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
> 27 May 2013 06:47
> On 26/05/2013 20:51, Ray Hunter wrote:
>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>> 25 May 2013 22:36
>>> Ray,
>>>
>>> On 25/05/2013 21:55, Ray Hunter wrote:
>>>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>>>> 24 May 2013 22:50
>>>>> On 25/05/2013 00:40, John Leslie wrote:
>>>>>> Ray Hunter <v6ops@globis.net> wrote:
>>>>>>> I would also like to see some text on whether it is possible/desirable
>>>>>>> for a middleware box to strip unknown headers, or even some known
>>>>>>> headers, rather than making a binary decision to drop or transmit the
>>>>>>> entire packet. If (new) headers are truly optional or experimental, the
>>>>>>> residual stripped packet may still have value e.g. stripping hop by hop
>>>>>>> extension headers on entry to/ egress from a corporate network or
>>>>>>> transit AS. That way the (new) extension headers could be usefully
>>>>>>> deployed in an AS that supports them, but the end to end traffic would
>>>>>>> not be blocked further along the path by firewalls in an AS that does not.
>>>>>>    I had a similar thought -- even going so far as to posit a way to
>>>>>> notate that a header had been stripped...
>>>>>>
>>>>>>    I think the answer is we don't want to do that in this document;
>>>>>> nonetheless some folks are likely to try it. I think a mention of the
>>>>>> issue, and a reference to RFC(s) stating the current rules, would help.
>>>>> What rules? As far as I know, no such mechanism is defined or allowed,
>>>>> so there is nothing to refer to. I would object (as a WG participant)
>>>>> to even mentioning such a mechanism. (As a document editor, I would
>>>>> of course edit the document according to WG consensus.)
>>>> It's a clear answer that you feel stripping of headers from the chain is
>>>> not allowed, and stating that in the draft this would give clear
>>>> direction to middlebox developers.
>>> It seems completely clear to me from the words in RFC 2460 that the
>>> only extension header that is to be inspected by intermediate nodes is
>>> the hop-by-hop header, and that the design intention was that all
>>> other headers were to be transmitted transparently. If we were being
>>> strict, there's no need to do anything except bash middlebox implementers
>>> over the head with those words. As far as I can tell, designers of
>>> extension headers since RFC 2460 have relied completely on this.
>>>
>>> But, in the real world we have firewalls that do *not* conform to 2460,
>>> and we need to deal with them realistically.
>>>
>>>> But equally, and without wanting to appear confrontational, I thought
>>>> that the point of the header chain and the fact the header chain was
>>>> excluded from checksums, was to allow various middleware boxes to
>>>> process portions of the packet on the fly en route as appropriate, thus
>>>> fostering innovation.
>> I guess we could always use a hop by hop option for that use case, so
>> that's no big deal to me.
>>> Where do you find any support for that in RFC 2460? I see exactly the
>>> opposite, and I'm not aware of any IETF specification that suggests
>>> modification of extension headers on the fly. (Routing headers may
>>> be modified at routing hops, but that is after the packet has been
>>> delivered to its next hop.)
>> With the danger of being unnecessarily pedantic, RFC2460 says "With one
>> exception, extension headers are not examined or processed by any node
>> along a packet's delivery path, until the packet reaches the node (or
>> each of the set of nodes, in the case of multicast) identified in the
>> Destination Address field of the IPv6 header."
>>
>> And we're now defining how a middlebox along the path examines and
>> processes headers other than the hop by hop header. So pointing at 2460
>> alone wouldn't seem to be adequate to conclude that intermediate nodes
>> MUST either pass a packet unmodified or discard it.
>
> Correct, that's why it's a standards track update. We are clarifying
> the meaning.
>
>> I think that is worth pointing out in the draft that "Contrary to
>> RFC2460 Section 4, middleboxes, such as firewalls, load balancers or
>> packet classifiers, MAY examine and process the entire IPv6 packet
>> before making a decision to either forward or discard the packet."
>
> I'm not sure if it's really a MAY or simply a statement of what
> occurs in the real world.
>
>>>> As an example, the flow label has certain limitations and DSCP is
>>>> limited, so inclusion of an extra header with a tag to be used for
>>>> traffic engineering purposes (and which only has significance within a
>>>> single AS) might prove useful in the future, without having to resort to
>>>> tunnels and wrappers. On the other hand, transmitting that tag over an
>>>> AS boundary might prove harmful.
>>> If IPv6 had been designed that way, but it wasn't.
>>>
>>>> So inserting and stripping headers at various points on the path could
>>>> conceivably provide useful innovation IMHO. So wouldn't it be a bit
>>>> self-inconsistent for this draft to block that if the stated aim is to
>>>> foster innovation?
>>> We'd have to invent a third form of extension header to do that (in addition
>>> to HbH and E2E). It's an interesting idea, and I wouldn't want to exclude
>>> it without debate, but I think it's on top of what this draft is trying to
>>> do, which is to make E2E extension headers useable. (I assure you from experience
>>> that they are not useable today, with off-the-shelf firewalls on the path).
>>>>>>    (The prime purpose of this document is creating an IANA registry;
>>>>>> that purpose should not be clouded by discussion of what firewalls
>>>>>> "should" do.)
>>>>> Not so. The prime purpose of this document is to make extension headers
>>>>> useable. The registry is a means to that end; describing precisely how
>>>>> middleboxes should treat them is another means to that end. We can make
>>>>> that clearer in the text, of course.
>>>>>
>>>>> Describing how middleboxes might block or destroy them is antithetical
>>>>> to the purpose of the document. That's why Ray says "I'm not sure the
>>>>> current text is entirely balanced in this respect." He's right. Again
>>>>> speaking as a WG participant, I'm happy with that.
>>>> So you're asking the WG to make a consensus call that a default drop
>>>> policy in firewalls is harmful because the need for innovation on the
>>>> Internet always outweighs any benefit from devices shipping with such a
>>>> default drop policy?
>>> No. Please read the draft very closely. What it intends to say is
>>> that brainless default-deny is the wrong approach, that firewalls must
>>> recognize all valid extensions (most of them don't) and allow
>>> tailored drop rules per extension type (some of them don't). If the
>>> draft doesn't say that, we'd be glad to adjust the wording to meet
>>> the intent.
>> I've read the draft several times.
>>
>> The two portions that lead me to conclude "default drop policy is evil" are:
>>
>> 1. "RFC 2460 requires destination hosts to discard packets containing
>>    unrecognised extension headers.  However, intermediate forwarding
>>    nodes MUST NOT do this by default, since that might cause them to
>>    inadvertently discard traffic using a recently defined extension
>>    header, not yet recognised by the intermediate node."
>>
>> I do not see how this demand to forward unknown headers is in any way
>> consistent with a middlebox node being able to implement a "drop by
>> default" policy. It seems counter-intuitive from a security perspective
>> that an intermediate node, whose job it is to protect end nodes from
>> zero day exploits, MUST allow "unknown headers" to transit, whilst the
>> node they are supposed to be protecting MUST drop "unknown headers"
>
> Well, the IPv6 design was, I suspect, intended to make layer 3
> firewalls unnecessary. (I am not claiming that has succeeded.) However,
> the aim here was to write a spec that treads the narrow path between
> making the Internet transparent to well-defined extension headers
> and allowing firewalls to defend a perimeter. I think you're correct
> that the present version is still slightly inconsistent, and needs
> a bit more fine-tuning of the normative language.
>
>> (which may well be the same ones crafted in some way to form an
>> exploit). It seems to me that this sentence implies that the danger of
>> false positives in firewall code (caused by innovation) are more harmful
>> than false negatives (firewall code and end node code has not yet caught
>> up with new standards or new exploits). I don't share that view and I'm
>> sure I'm not alone.
>
> No, it's a common view in some security circles. I don't happen to agree
> with it as far as layer 3 attacks go; and not all sites would set the
> risk vs innovation tradeoff at the same point. We really need this to
> be under IT managers' control, I think.
Agreed.
>
>> Also the above text would seem to be in direct contradiction to the
>> following text later in the draft:
>>
>> Quote: "Forwarding nodes MUST be configurable to allow packets
>> containing unrecognised extension headers, and such packets MAY be
>> dropped by default."
>
> Yes, this is why the internal consistency of the draft probably
> needs tuning. That sentence should take priority over the earlier
> MUST NOT that you quoted. We missed that.
ACK.
>> I have no problem with that text.
>>
>>
>> 2. "The default configuration SHOULD allow all defined extension headers. "
>>
>> That, in my reading, is directly contrary to recommending that a
>> manufacturer ship a middlebox to run a "drop unless" policy out of the
>> shrinkwrap, which is de facto market behaviour. Market behaviour might
>> change, but attempting to reverse it via this draft undermines the rest
>> of the draft IMHO.
>
> Why? It's a SHOULD, which means "there may exist valid reasons in particular
> circumstances to ignore a particular item, but the full implications must
> be understood and carefully weighed before choosing a different course."
> Isn't that what firewall implementers do about every protocol feature
> they consider?

I have no problem if load balancers always forward.
> Also, recall that the WG asked us to make the document applicable
> to all kinds of middlebox, not just firewalls. Non-firewall boxes
> certainly have no business censoring extension headers.
>
>> Hence my comment about enabling all "experimental" repositories by
>> default in Linux distributions. 
>
> The word "defined" is supposed to mean "not experimental", at least in
> my mind. Maybe the language needs to be more explicit on that point.
> Perhaps we should be explicit that standards track action is needed.
> That would update RFC 5237, which allows standards action *or*
> IESG approval. No disrespect, but the latter seems very casual for
> a new extension header.
Right.

What I explicitly don't want to happen (and I think this is entirely
likely reading the current text literally)

Firewall is explicitly configured by the user and is running v1.0 code.

 Allow hop-by-hop
 Deny unknown headers

Later, the IETF defines the XYZZY IPv6 extension header as standards track

XYZZY is considered OK by "everyone"
(but so were Type 0 Routing headers for 7 years.... and we already had
the same negative experience in IPv4 with source routing)

Much later the manufacturer's code catches up with the RFC for XYZZY.

Even later on, the end user considers the manufacturers code to no
longer be bleeding edge, and the box is updated to v2.0 code

Config automatically becomes

 Allow hop-by-hop
 Allow XYZZY
 Deny unknown headers

without human intervention.

We should respect that end users have the right to choose which
extensions they allow on their networks. Extensions, by definition, are
not part of the core protocol IMHO.

So my conclusion is that any automatic/default setting for a security
device to allow any headers (not available in a previous release, or
which do not already have an explicit configuration) SHOULD inherit the
explicit wish of the network administrator for treatment of unknown headers.

Or else my personal preference would really be a "deny all" terminal
rule, but I guess you would object to that, which I respect.


>> I'm also sure that I'm not alone in
>> believing that some existing headers and any new optional headers may
>> prove controversial from a security perspective. Previous operational
>> experience with extension headers has proven that a prudent approach to
>> introducing changes may be necessary for many customers.
>
> Yes, certainly, and I think a few words on that would fit in the Security
> Considerations, where it is already mentioned that deployment of a new
> extension will be slow.
>
>> I therefore suggest deleting this text.
>
> But we're not defining firewall product specs here. We're defining
> how to make IPv6 work. You are of course correct that firewall vendors
> will do whatever they decide to do, but it seems to me that the IETF
> position should always favour connectivity while pointing out
> security risks and how to alleviate them.
>
>     Brian
Agreed for boxes that do not explicitly perform filtering functions.
Filtering functions need to be left in the hands of the network
administrator.
>
>> regards,
>> RayH
>>>> Is that not akin to demanding that every Linux and BSD distribution
>>>> always ships with "experimental" repositories enabled, because we might
>>>> have some cool new kernel hack or network code that everyone must try?
>>> No, the draft also contains words intended to explain that newly
>>> defined extension headers will take time to be recognized by firewalls,
>>> as well as providing a registry where firewall developers can find them
>>> (which is not the case today). Again, if the words don't meet the
>>> intent, please suggest new words.
>>>
>>>> Speaking entirely personally, I think the market has already clearly
>>>> decided on that point.
>>> The draft is intended to deal with the real world, but if the IETF
>>> doesn't specify how things should work, who else is going to?
>>> Firewall developers are not deaf and blind to innovation, and in my
>>> experience are open to this discussion.
>>>
>>>     Brian
>>>
>>>>> On 25/05/2013 02:43, Tim Chown wrote:
>>>>>
>>>>>> A couple of additional comments.
>>>>>>
>>>>>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>>>>> Shouldn't this just be part of the Security Comsiderations for
>>>>> the definition of each header? The registry will always contain a pointer
>>>>> to the relevant RFCs. IANA can't do much if the Security Considerations
>>>>> are insufficient.
>>>>>
>>>>>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>>>>> I think we included that in an earlier draft, but then removed it
>>>>> because it appears to function as a null transport header. It's
>>>>> a judgment call, and only needs a few keystrokes to put it back in the
>>>>> list.
>>>>>
>>>>>    Brian
>>>>>
>>>>>
>>>>>

From joelja@bogus.com  Mon May 27 08:03:09 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA1D21F969D for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 08:03:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVkI3EyUmJUf for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 08:03:08 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B802121F969C for <ipv6@ietf.org>; Mon, 27 May 2013 08:03:08 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4RF2cPl089738 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 27 May 2013 15:02:38 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A3758D.7050403@bogus.com>
Date: Mon, 27 May 2013 08:02:37 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ray Hunter <v6ops@globis.net>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com>	<519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi>	<519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net> <51A120BA.2020805@gmail.com>
In-Reply-To: <51A120BA.2020805@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 27 May 2013 15:02:38 +0000 (UTC)
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 May 2013 15:03:10 -0000

On 5/25/13 1:36 PM, Brian E Carpenter wrote:
> Ray,
>
> On 25/05/2013 21:55, Ray Hunter wrote:
>>> Brian E Carpenter <mailto:brian.e.carpenter@gmail.com>
>>> 24 May 2013 22:50
>>> On 25/05/2013 00:40, John Leslie wrote:
>>>> Ray Hunter <v6ops@globis.net> wrote:
>>>>> I would also like to see some text on whether it is possible/desirable
>>>>> for a middleware box to strip unknown headers, or even some known
>>>>> headers, rather than making a binary decision to drop or transmit the
>>>>> entire packet. If (new) headers are truly optional or experimental, the
>>>>> residual stripped packet may still have value e.g. stripping hop by hop
>>>>> extension headers on entry to/ egress from a corporate network or
>>>>> transit AS. That way the (new) extension headers could be usefully
>>>>> deployed in an AS that supports them, but the end to end traffic would
>>>>> not be blocked further along the path by firewalls in an AS that does not.
>>>>     I had a similar thought -- even going so far as to posit a way to
>>>> notate that a header had been stripped...
>>>>
>>>>     I think the answer is we don't want to do that in this document;
>>>> nonetheless some folks are likely to try it. I think a mention of the
>>>> issue, and a reference to RFC(s) stating the current rules, would help.
>>> What rules? As far as I know, no such mechanism is defined or allowed,
>>> so there is nothing to refer to. I would object (as a WG participant)
>>> to even mentioning such a mechanism. (As a document editor, I would
>>> of course edit the document according to WG consensus.)
>> It's a clear answer that you feel stripping of headers from the chain is
>> not allowed, and stating that in the draft this would give clear
>> direction to middlebox developers.
> It seems completely clear to me from the words in RFC 2460 that the
> only extension header that is to be inspected by intermediate nodes is
> the hop-by-hop header, and that the design intention was that all
> other headers were to be transmitted transparently. If we were being
> strict, there's no need to do anything except bash middlebox implementers
> over the head with those words. As far as I can tell, designers of
> extension headers since RFC 2460 have relied completely on this.
>
> But, in the real world we have firewalls that do *not* conform to 2460,
> and we need to deal with them realistically.
We also have middleboxes which we call routers which are somewhat less 
functional if they can't find the L4 header, with all the attendant 
consequences that entails. That may not have been a big deal in 1994 but 
it's basically all of them now.
>
>> But equally, and without wanting to appear confrontational, I thought
>> that the point of the header chain and the fact the header chain was
>> excluded from checksums, was to allow various middleware boxes to
>> process portions of the packet on the fly en route as appropriate, thus
>> fostering innovation.
> Where do you find any support for that in RFC 2460? I see exactly the
> opposite, and I'm not aware of any IETF specification that suggests
> modification of extension headers on the fly. (Routing headers may
> be modified at routing hops, but that is after the packet has been
> delivered to its next hop.)
>
>> As an example, the flow label has certain limitations and DSCP is
>> limited, so inclusion of an extra header with a tag to be used for
>> traffic engineering purposes (and which only has significance within a
>> single AS) might prove useful in the future, without having to resort to
>> tunnels and wrappers. On the other hand, transmitting that tag over an
>> AS boundary might prove harmful.
> If IPv6 had been designed that way, but it wasn't.
>
>> So inserting and stripping headers at various points on the path could
>> conceivably provide useful innovation IMHO. So wouldn't it be a bit
>> self-inconsistent for this draft to block that if the stated aim is to
>> foster innovation?
> We'd have to invent a third form of extension header to do that (in addition
> to HbH and E2E). It's an interesting idea, and I wouldn't want to exclude
> it without debate, but I think it's on top of what this draft is trying to
> do, which is to make E2E extension headers useable. (I assure you from experience
> that they are not useable today, with off-the-shelf firewalls on the path).
>>
>>>>     (The prime purpose of this document is creating an IANA registry;
>>>> that purpose should not be clouded by discussion of what firewalls
>>>> "should" do.)
>>> Not so. The prime purpose of this document is to make extension headers
>>> useable. The registry is a means to that end; describing precisely how
>>> middleboxes should treat them is another means to that end. We can make
>>> that clearer in the text, of course.
>>>
>>> Describing how middleboxes might block or destroy them is antithetical
>>> to the purpose of the document. That's why Ray says "I'm not sure the
>>> current text is entirely balanced in this respect." He's right. Again
>>> speaking as a WG participant, I'm happy with that.
>> So you're asking the WG to make a consensus call that a default drop
>> policy in firewalls is harmful because the need for innovation on the
>> Internet always outweighs any benefit from devices shipping with such a
>> default drop policy?
> No. Please read the draft very closely. What it intends to say is
> that brainless default-deny is the wrong approach, that firewalls must
> recognize all valid extensions (most of them don't) and allow
> tailored drop rules per extension type (some of them don't). If the
> draft doesn't say that, we'd be glad to adjust the wording to meet
> the intent.
>
>> Is that not akin to demanding that every Linux and BSD distribution
>> always ships with "experimental" repositories enabled, because we might
>> have some cool new kernel hack or network code that everyone must try?
> No, the draft also contains words intended to explain that newly
> defined extension headers will take time to be recognized by firewalls,
> as well as providing a registry where firewall developers can find them
> (which is not the case today). Again, if the words don't meet the
> intent, please suggest new words.
>
>> Speaking entirely personally, I think the market has already clearly
>> decided on that point.
> The draft is intended to deal with the real world, but if the IETF
> doesn't specify how things should work, who else is going to?
> Firewall developers are not deaf and blind to innovation, and in my
> experience are open to this discussion.
>
>      Brian
>
>>> On 25/05/2013 02:43, Tim Chown wrote:
>>>
>>>> A couple of additional comments.
>>>>
>>>> One is that from time to time there may be security issues raised with certain headers, e.g. RH0. These may obviously be raised over time. Is there a mechanism to catch these in the IANA registry somehow?
>>> Shouldn't this just be part of the Security Comsiderations for
>>> the definition of each header? The registry will always contain a pointer
>>> to the relevant RFCs. IANA can't do much if the Security Considerations
>>> are insufficient.
>>>
>>>> Another is whether there is any use of the "null" header type 59?  Or has that been deprecated?  If not, should it be so, given Brian doesn't list it.  Or is this viewed in the same category as TCP, etc as header types?
>>> I think we included that in an earlier draft, but then removed it
>>> because it appears to function as a null transport header. It's
>>> a judgment call, and only needs a few keystrokes to put it back in the
>>> list.
>>>
>>>     Brian
>>>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From msweet@apple.com  Tue May 28 06:50:59 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2752D21F8689 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 06:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwbNB5QPk5EJ for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 06:50:52 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id EBDA721F84F9 for <ipv6@ietf.org>; Tue, 28 May 2013 06:50:52 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNI0046NH3REH81@mail-out.apple.com> for ipv6@ietf.org; Tue, 28 May 2013 06:50:30 -0700 (PDT)
X-AuditID: 1180715a-b7f506d000007d18-1d-51a4b624c76f
Received: from [17.153.23.147] (Unknown_Domain [17.153.23.147]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id A1.BF.32024.526B4A15; Tue, 28 May 2013 06:50:30 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <DD44AD09-B91C-41CA-9CE7-45D3E84A26CE@employees.org>
Date: Tue, 28 May 2013 09:50:28 -0400
Message-id: <EE7FC9D1-3702-4237-B7CF-9FFA98E2088C@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <DD44AD09-B91C-41CA-9CE7-45D3E84A26CE@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUiOFN8sq7atiWBBueXMFo0fe5jtLj26D6L xcuz75ksjnyLtZjctoLNgdVj68kfbB67jv5g9zh47COjx5IlP5k8Wnf8ZQ9gjeKySUnNySxL LdK3S+DKeL/zFVNBi0LFpq+/mRoYn0p2MXJySAiYSNxccIYNwhaTuHBvPZDNxSEk0MskserP B3aQhLCAucTcx58ZQWxeAT2Ja9++gsWZBbQkbvx7yQRiswmoSfye1McKYnMKOEr0PFwGNpRF QFVi7vqnUPXFEt+X3GCCsLUlli18zQwx00Zi7aFTYL1CAndYJP7vFQWxRQRUJM5Pe8cIcZys xOvnb1gmMPLPQnLGLCRnzEIydgEj8ypGgaLUnMRKM73EgoKcVL3k/NxNjKBwbSiM2sHYsNzq EKMAB6MSD++E7MWBQqyJZcWVuYcYJTiYlUR4L61cEijEm5JYWZValB9fVJqTWnyIUZqDRUmc 99fcWYFCAumJJanZqakFqUUwWSYOTqkGxslcSZnxERKdPZunrTkvPK2gN2bKprP3LA690f5e bRu2+UTKgv3GVuwG8+bxsJ/vSHC9HxqWxGCfU3TrnUYwY795CLPmxNgV8iuK+psen9r252KV KJ91m016UExnz7lqoSvhN9qsNZnP/N49be+tN8K3rgY9f9U7/7qH9HO3Y5ueTPBZ9Wn+IyWW 4oxEQy3mouJEANSLoQ5TAgAA
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 13:50:59 -0000

Ole,

On 2013-05-24, at 4:33 PM, Ole Troan <otroan@employees.org> wrote:
>> ...
>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
> 
> how is this different from any other application using link-local addresses?

In this case, the server is returning absolute URIs (for printers, typically URIs with http, https, ipp, or ipps schemes on a variety of ports) that the client can later use for accessing the corresponding resources.

> ...
> client connects to http:://[fe80::1%Ethernet0/0]
> the client has to assume that all embedded URIs with link-local addresses belong to the same zone that it connected to.
> after all they cannot belong to any other zone...  the server obviously has to make sure it never gives out these URIs
> to a client connecting using non-link-local addresses multiple hops away.

OK, so the problem is that absolute URIs are embedded in the content returned by the server. Forcing the client to rewrite all of the URIs in the returned content is a tremendous burden on the client, while the server is generating these absolute URIs on-the-fly to satisfy the client's request and could include the zoneid information essentially "for free" with minor changes to its input validation (to allow addresses with zoneid information).

Put another way, would you rather write the client code that "fixes" every embedded URI in an IPP response, HTML document, CSS file, XML file, XSLT file, PDF file, etc., or would you prefer writing the server code that just embeds the client-provided address in the URIs it returns?

>> What I propose is that we change the wording to allow the zoneid in the Host header but not in the Request-URI.  HTTP proxies would be required to strip any zoneid information in the Host header.  HTTP servers would be required to ignore any zoneid information for purposes of address validation but include it for any absolute URIs to the server they generate.
>> 
>> Thoughts?
> 
> to reword. you need something for which the client gives the server some opaque information that it can use to identify interface when it gets the embedded URIs in the reply back?
> again I don't understand why the client doesn't know the interface to use already.


The client software /may/ know the interface in use because it has an absolute URI containing this information.  I say may because in many cases this information is abstracted away in some toolkit so all the client software may see is a printer name, e.g., "Acme Laser Printer down the Hall".

Moreover, the returned IPP response, HTML document, etc. may be used by code that no longer has access to the original address information - it has lost the original context and thus a link local address without zoneid information is basically inaccessible short of iterating over all the client's interfaces (assuming your OS of choice even allows ordinary users/applications to do that...)

For example, CUPS supports PPD keywords that specify the absolute URI of the printer's administration and supply report web pages. This information is collected when the queue is setup, and if the printer is setup using a numeric IPv6 link local address we need to store the client's interface name (zoneid) with the URI so it can be accessed in the future.  We made an implementation choice 8 years ago (in cooperation with the printer vendors) to support this configuration by passing the client's zoneid in the request so that the printer could return the same address+zoneid in any URIs, and that has served us well for the (small number of) users that want/need this capability.  Each client has its own PPD file using its own zoneid information...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From msweet@apple.com  Tue May 28 06:52:03 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88CB221F9497 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 06:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.441
X-Spam-Level: 
X-Spam-Status: No, score=-10.441 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTconXSdjkdC for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 06:51:57 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5188621F8EB1 for <ipv6@ietf.org>; Tue, 28 May 2013 06:51:57 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_d1nvURb9rb/01jo85GF62g)"
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNI006NTH6KZLF0@mail-out.apple.com> for ipv6@ietf.org; Tue, 28 May 2013 06:51:57 -0700 (PDT)
X-AuditID: 11807166-b7faa6d000003acb-91-51a4b67bd74f
Received: from [17.153.23.147] (Unknown_Domain [17.153.23.147]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id D9.6C.15051.C76B4A15; Tue, 28 May 2013 06:51:56 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <CABOxzu1xpbBvd_aWJEHD9qTTmG_Ly0=Pry9X4PqY+xBLMf01Vw@mail.gmail.com>
Date: Tue, 28 May 2013 09:51:54 -0400
Message-id: <A300002E-7EEF-4078-8554-8B385B881753@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <CABOxzu1xpbBvd_aWJEHD9qTTmG_Ly0=Pry9X4PqY+xBLMf01Vw@mail.gmail.com>
To: Kerry Lynn <kerlyn@ieee.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUiOFN8sm7NtiWBBtfmG1s0fe5jtLj26D6L xcuz75ksLq9fxWxx5FusA6vH1pM/2Dx2Hf3B7vF0wkEmjyVLfjJ5tO74yx7AGsVlk5Kak1mW WqRvl8CV0bhvLUvBNPmK4/sfsTUwfpDqYuTkkBAwkTjzciYjhC0mceHeerYuRi4OIYFeJomF 0yewgCSEBcwl5j7+DFbEK6Ance3bV3YQm1kgQWL62V9gNWwCahK/J/WxgticAoES3951MIPY LAKqEktvXmSDqC+WuDrrLxPEHBuJq3tvMkEs280isXjRFbAGEQEFiU+L9jBBXCQr8fr5G5YJ jHyzkOyehWQ3hK0tsWzha2YIW0/iZdM7dkxxXYmL6yYxLmBkW8UoUJSak1hpoZdYUJCTqpec n7uJERTgDYVpOxibllsdYhTgYFTi4bXIXBwoxJpYVlyZe4hRgoNZSYT30solgUK8KYmVValF +fFFpTmpxYcYpTlYlMR5f8+dFSgkkJ5YkpqdmlqQWgSTZeLglGpgzFr//8WU1Of9ekurvN+c zZVaenmht7n/i6Luy5cniWauuzlRu9v5oJXOhuQWhZmTLqzS9qoRil17PsjczoznvFKe3ufp RZ1fO6Q3GF+uOCUve/PztSXhZ3fOvapyzlZZ++X1m6K95zb8EdpvrLHoa8Or57eWHa/qP7B2 kXvpBba7H82exH2aU6vEUpyRaKjFXFScCADtMX1QbAIAAA==
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 13:52:03 -0000

--Boundary_(ID_d1nvURb9rb/01jo85GF62g)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Kerry,

On 2013-05-24, at 1:58 PM, Kerry Lynn <kerlyn@ieee.org> wrote:
> Michael,
> 
> Can I echo what Tom and Christian have said - that you join the 6man working
> group and start by clearly and concisely stating the problem that this RFC poses
> for your application and how you suggest we fix it?

Yes, I did get a useful pointer to the mailing list subscription page last week and am now a member of the ipv6 list.

> When you speak of "hundreds of millions of printers..." it gives the impression that
> the RFC makes illegal something that printers have been doing for some time.  If
> so, can you also provide relevant references to the deployed functionality that you
> believe this RFC makes illegal?

I am putting together a full proposal and draft to do just that...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


--Boundary_(ID_d1nvURb9rb/01jo85GF62g)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Kerry,<div><br><div><div>On 2013-05-24, at 1:58 PM, Kerry Lynn &lt;<a =
href=3D"mailto:kerlyn@ieee.org">kerlyn@ieee.org</a>&gt; =
wrote:</div><blockquote type=3D"cite">Michael,<br><br>Can I echo what =
Tom and Christian have said - that you join the 6man working<br>group =
and start by clearly and concisely stating the problem that this RFC =
poses<br>for your application and how you suggest we fix =
it?<br></blockquote><div><br></div>Yes, I did get a useful pointer to =
the mailing list subscription page last week and am now a member of the =
ipv6 list.</div><div><br><blockquote type=3D"cite">
When you speak of "hundreds of millions of printers..." it gives the =
impression that<br>the RFC makes illegal something that printers have =
been doing for some time.&nbsp; If<br>so, can you also provide relevant =
references to the deployed functionality that you<br>
believe this RFC makes =
illegal?<br></blockquote><div><br></div></div><div>I am putting together =
a full proposal and draft to do just that...</div><div><br></div><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Andale Mono'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; =
">_________________________________________________________<br>Michael =
Sweet, Senior Printing System&nbsp;Engineer, PWG =
Chair</div></span></span>
</div>
<br></div></body></html>=

--Boundary_(ID_d1nvURb9rb/01jo85GF62g)--

From v6ops@globis.net  Tue May 28 12:34:45 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E9A21F96B2 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 12:34:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHFFdrjfUuOu for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 12:34:44 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0B521F96B7 for <ipv6@ietf.org>; Tue, 28 May 2013 12:34:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 4522A8700B1; Tue, 28 May 2013 21:34:28 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lq1lSioIFmBU; Tue, 28 May 2013 21:34:28 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 1C98D87007A; Tue, 28 May 2013 21:34:28 +0200 (CEST)
Message-ID: <51A506BD.9060804@globis.net>
Date: Tue, 28 May 2013 21:34:21 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Michael Sweet <msweet@apple.com>
Subject: Re: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
In-Reply-To: <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 19:34:45 -0000

Warning: post contains dumb questions.

Michael Sweet wrote:
> Christian,
>
> On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com> wr=
ote:
>> Can we move from the process discussion to the technical discussion?
>>
>> Michael raised an interesting issue, and we have to analyze it. The co=
nsensus of the working group so far is that interface identifiers are pri=
vate to the host, that any leakage outside the host should be prevented, =
and that a way to prevent that leakage is to ask proxies to erase them wh=
enever they have an opportunity. Michael points that some servers take an=
 opposite approach, want to record the interface from which the host call=
ed them, and want to ensure that further calls in the same session use ex=
actly the same interface. That seems that a fairly legitimate debate, and=
 I can see two alternatives -- one would be to reaffirm the old guidance =
and provides alternative to ensure session continuity, and the other woul=
d be to reverse the guidance and accept that the layer violation performe=
d by servers is just fine.
>
>
> (the following is printer-centric, but the same applies to network vide=
o cameras and other embedded network devices)
>
> Some background: HTTP and IPP services in printers include absolute URI=
s in the content they return. For IPP this can be http/https URLs to the =
printer's web page, ICC profiles, and other resources, along with the ipp=
/ipps URIs that the printer supports. For HTTP the most common are https =
URLs for "secure" areas of the printer's web interface.  Because a printe=
r is often known by multiple names and addresses ("printer.local.", "prin=
ter.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation g=
uidance (and in IPP Everywhere, this is a conformance requirement) is tha=
t the server use the HTTP Host header provided in the request in the host=
/address field of its responses, subject to the usual security considerat=
ions (SHOULD validate Host value, etc.)  This allows the client to use th=
e name or address it can resolve/connect to and makes sure that the print=
er-generated absolute URIs lead back to same printer.
>
> All of this falls apart with link-local addresses and RFC 6874.  Becaus=
e the client is required to remove the zoneid from the outgoing request, =
the URIs it gets back from the server are no longer "reachable".
Trying to understand what's going on here and what the root problem is.

I have some dumb questions:

Is the zoneid in the URI the interface on the client or the server node?

What does other party learn from this information, since zoneid is
currently defined as being local to the node and has no significance
outside the context of the node?

If the other party learns nothing, and the originating node just needs
to hear an echo of it's own information for it's own use, what's wrong
with using a cookie (server originated), or a hidden variable (client
originated), to transport this interface information along with the
request/reply?

What if both the server AND the client have multiple interfaces: how do
they both know which local interface on their own node is mutually
connected and to be used for communication? There's only one single
zoneid in the URI, so presumably one of the nodes is lacking some
information.

Shouldn't both nodes be using ND to learn this information?
If there's nothing in the cache, try all interfaces?

regards,
RayH

> What I propose is that we change the wording to allow the zoneid in the=
 Host header but not in the Request-URI.  HTTP proxies would be required =
to strip any zoneid information in the Host header.  HTTP servers would b=
e required to ignore any zoneid information for purposes of address valid=
ation but include it for any absolute URIs to the server they generate.
>
> Thoughts?
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>


From brian.e.carpenter@gmail.com  Tue May 28 13:38:33 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D2D11E80D5 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 13:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.333
X-Spam-Level: 
X-Spam-Status: No, score=-102.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzGmIWa0LYN2 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 13:38:28 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA3721F93E0 for <ipv6@ietf.org>; Tue, 28 May 2013 13:38:28 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 10so8089568pdi.17 for <ipv6@ietf.org>; Tue, 28 May 2013 13:38:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=30FuDhdAUf5ZzAFSrtfMgBWbhAVhbasEXrbMGT87ysU=; b=O8sCZ9NHU5e6WduX8Ef9Fvs++oO9QlCrlKOL0jtKfNE2X24k+Ixsc+unoyEkXQF1Gx ao4s8aEtz8Arj4qxH27lLjiVsrqB47vO4eQDwZDZOXKyZigvhUfs67toryUUwlCG3I6v Wa2Ap8zUZ9nyGYndL5d24yBjbM+9MYu9SgJ7cokPaLqYYNp4MHEBLXurbQalLxSWRhOv d69Fpq3fEMUByuiSFooau2GX3SkooRKBs7XJrDtL6uiB7213W9vsqwzGV/PsSPKPjy/X UQcytQePPaf/LxrrzL5fQhnQUue5oKXwiDyQ5N6xjdiOhrNb/4AfY+NT/ks8EO198hQr kiTQ==
X-Received: by 10.66.26.52 with SMTP id i20mr57223pag.209.1369773507114; Tue, 28 May 2013 13:38:27 -0700 (PDT)
Received: from [192.168.1.2] (253.150.252.27.dyn.cust.vf.net.nz. [27.252.150.253]) by mx.google.com with ESMTPSA id un15sm34890774pab.7.2013.05.28.13.38.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 13:38:25 -0700 (PDT)
Message-ID: <51A515C2.1090208@gmail.com>
Date: Wed, 29 May 2013 08:38:26 +1200
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: Ray Hunter <v6ops@globis.net>
Subject: Strange use of link-local (was: [Technical Errata Reported] RFC6874 (3630))
References: <20130523035151.7B24A6210A@rfc-editor.org>	<519DA89C.5070704@gmail.com>	<13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com>	<C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com>	<CF457469-49FC-42CC-9E04-487FE035CA10@apple.com>	<014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net>	<9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com>	<033d01ce5893$c3522360$4001a8c0@gateway.2wire.net>	<C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com>	<51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net>
In-Reply-To: <51A506BD.9060804@globis.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 20:38:33 -0000

I'm increasingly baffled by the use case. If the host is
in a context where it can reach a server *and* has more than
one interface (such that a ZoneID is needed at all), it
shouldn't be using a link local address anyway - it
should have configured a global scope address (possibly
under a ULA prefix). Discussion of this use case surely
belongs in MIF or HOMENET.

    Brian

On 29/05/2013 07:34, Ray Hunter wrote:
> Warning: post contains dumb questions.
> 
> Michael Sweet wrote:
>> Christian,
>>
>> On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com> wrote:
>>> Can we move from the process discussion to the technical discussion?
>>>
>>> Michael raised an interesting issue, and we have to analyze it. The consensus of the working group so far is that interface identifiers are private to the host, that any leakage outside the host should be prevented, and that a way to prevent that leakage is to ask proxies to erase them whenever they have an opportunity. Michael points that some servers take an opposite approach, want to record the interface from which the host called them, and want to ensure that further calls in the same session use exactly the same interface. That seems that a fairly legitimate debate, and I can see two alternatives -- one would be to reaffirm the old guidance and provides alternative to ensure session continuity, and the other would be to reverse the guidance and accept that the layer violation performed by servers is just fine.
>>
>> (the following is printer-centric, but the same applies to network video cameras and other embedded network devices)
>>
>> Some background: HTTP and IPP services in printers include absolute URIs in the content they return. For IPP this can be http/https URLs to the printer's web page, ICC profiles, and other resources, along with the ipp/ipps URIs that the printer supports. For HTTP the most common are https URLs for "secure" areas of the printer's web interface.  Because a printer is often known by multiple names and addresses ("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation guidance (and in IPP Everywhere, this is a conformance requirement) is that the server use the HTTP Host header provided in the request in the host/address field of its responses, subject to the usual security considerations (SHOULD validate Host value, etc.)  This allows the client to use the name or address it can resolve/connect to and makes sure that the printer-generated absolute URIs lead back to same printer.
>>
>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
> Trying to understand what's going on here and what the root problem is.
> 
> I have some dumb questions:
> 
> Is the zoneid in the URI the interface on the client or the server node?
> 
> What does other party learn from this information, since zoneid is
> currently defined as being local to the node and has no significance
> outside the context of the node?
> 
> If the other party learns nothing, and the originating node just needs
> to hear an echo of it's own information for it's own use, what's wrong
> with using a cookie (server originated), or a hidden variable (client
> originated), to transport this interface information along with the
> request/reply?
> 
> What if both the server AND the client have multiple interfaces: how do
> they both know which local interface on their own node is mutually
> connected and to be used for communication? There's only one single
> zoneid in the URI, so presumably one of the nodes is lacking some
> information.
> 
> Shouldn't both nodes be using ND to learn this information?
> If there's nothing in the cache, try all interfaces?
> 
> regards,
> RayH
> 
>> What I propose is that we change the wording to allow the zoneid in the Host header but not in the Request-URI.  HTTP proxies would be required to strip any zoneid information in the Host header.  HTTP servers would be required to ignore any zoneid information for purposes of address validation but include it for any absolute URIs to the server they generate.
>>
>> Thoughts?
>>
>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>
>>
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

From msweet@apple.com  Tue May 28 16:28:05 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99E1E21F896B for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 16:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.546
X-Spam-Level: 
X-Spam-Status: No, score=-10.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4++RcgsEd4o for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 16:27:59 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE9621F88EA for <ipv6@ietf.org>; Tue, 28 May 2013 16:27:59 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNJ00KSN7UMSRP1@mail-out.apple.com> for ipv6@ietf.org; Tue, 28 May 2013 16:27:59 -0700 (PDT)
X-AuditID: 11807166-b7faa6d000003acb-1c-51a53d7d5349
Received: from [17.153.23.147] (Unknown_Domain [17.153.23.147]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id 34.00.15051.E7D35A15; Tue, 28 May 2013 16:27:58 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <51A506BD.9060804@globis.net>
Date: Tue, 28 May 2013 19:27:56 -0400
Message-id: <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUiOFN8sm6d7dJAgx+vLC2aPvcxWlx7dJ/F 4uXZ90wWR77FWuy5Wu/A6rH15A82j11Hf7B7PDl7nc1jyZKfTB6tO/6yB7BGcdmkpOZklqUW 6dslcGVs+XuLpeCYeMWfTVNYGxgfCnUxcnJICJhIvF09gRnCFpO4cG89WxcjF4eQQC+TRPfN M0wgCWEBc4m5jz8zgti8AnoS1759ZQexmQV0JHZuvcMGYrMJqEn8ntTHCmJzCmhJXJ79FKyX RUBV4umTx1D1xRLfl9xggrC1JZYtfM0MMdNGYkrnPCaIxUdZJDrnHQVrEBFQlJj+7wsTxHWy Eq+fv2GZwMg/C8kds5DcMQvJ3AWMzKsYBYpScxIrLfQSCwpyUvWS83M3MYLCtaEwbQdj03Kr Q4wCHIxKPLwrvi8JFGJNLCuuzD3EKMHBrCTCmyq4NFCINyWxsiq1KD++qDQntfgQozQHi5I4 r6kNUEogPbEkNTs1tSC1CCbLxMEp1cDo/HQaU2a76lHLjvZnbXPTK4R89tddYdt/X+ihs8uH qxMPCX92iJM+t2GldPz2Z91HDolvmpFXq7axovH8+8C+L1eYFvOZfudp5zh4d4LYYd9s1jrh c0/F75tmBJ3g/qq87nNc0zEFidvlsrvyc4QXFX51f252MvZszFFd9hSfiK8LEk2DDk9QYinO SDTUYi4qTgQAHpDCHFMCAAA=
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 23:28:05 -0000

Ray,

On 2013-05-28, at 3:34 PM, Ray Hunter <v6ops@globis.net> wrote:
> Warning: post contains dumb questions.

No such thing! :)

>> ...
>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
> Trying to understand what's going on here and what the root problem is.
> 
> I have some dumb questions:
> 
> Is the zoneid in the URI the interface on the client or the server node?

It is the interface on the client.

> What does other party learn from this information, since zoneid is
> currently defined as being local to the node and has no significance
> outside the context of the node?

The only thing it learns is "this is the address the client is using to talk to me".

> If the other party learns nothing, and the originating node just needs
> to hear an echo of it's own information for it's own use, what's wrong
> with using a cookie (server originated), or a hidden variable (client
> originated), to transport this interface information along with the
> request/reply?

Well, for starters none of that is standardized, whereas "Host" is a required HTTP request header that printers (and web servers) already support.

Also, passing the information back from the server in a cookie doesn't address the client-sde URI rewriting problem: it is much simpler (and less error prone) for the server to use the client-supplied address for the URIs in its response than for the client to parse and rewrite all of the URIs in the server's response.

> What if both the server AND the client have multiple interfaces: how do
> they both know which local interface on their own node is mutually
> connected and to be used for communication? There's only one single
> zoneid in the URI, so presumably one of the nodes is lacking some
> information.

The server knows its own link-local addresses and doesn't need the zoneid information.

For the use case under discussion, the client only knows its zoneid information because the user/administrator has supplied it along with the printer's link-local address.

> Shouldn't both nodes be using ND to learn this information?
> If there's nothing in the cache, try all interfaces?


It would be awesome if printers supported Neighbor Discovery, but of the four printers in my home office only three support IPv6 and only one supports ND.  One of the IPv6 printers is 3 years old, the other three are less than a year old...

On the client side you'll find a similar story - sporadic support, and in many cases the ND information isn't wired into the resolver libraries, making it impossible to use a bare IPv6 link-local address without the zoneid added at the end...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From heard@pobox.com  Mon May 27 14:17:00 2013
Return-Path: <heard@pobox.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8E721F8B07 for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 14:17:00 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nNULn5tazPou for <ipv6@ietfa.amsl.com>; Mon, 27 May 2013 14:16:55 -0700 (PDT)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFC721F8E84 for <ipv6@ietf.org>; Mon, 27 May 2013 14:16:54 -0700 (PDT)
Received: (qmail 28443 invoked from network); 27 May 2013 14:16:52 -0700
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 27 May 2013 14:16:52 -0700
Date: Mon, 27 May 2013 14:16:52 -0700 (PDT)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: 6man <ipv6@ietf.org>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
In-Reply-To: <51A2E547.7040502@gmail.com>
Message-ID: <Pine.LNX.4.64.1305271409240.25557@shell4.bayarea.net>
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net> <51A120BA.2020805@gmail.com> <51A1CD16.1060006@globis.net> <51A2E547.7040502@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 28 May 2013 16:30:28 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 27 May 2013 21:17:00 -0000

On Mon, 27 May 2013, Brian E Carpenter wrote:
> On 26/05/2013 20:51, Ray Hunter wrote:
> > I think that is worth pointing out in the draft that "Contrary to
> > RFC2460 Section 4, middleboxes, such as firewalls, load balancers or
> > packet classifiers, MAY examine and process the entire IPv6 packet
> > before making a decision to either forward or discard the packet."
> 
> I'm not sure if it's really a MAY or simply a statement of what
> occurs in the real world.

It should just be a statement of what occurs in the real world.  
The IETF should not endorse behaviours that violate IPv6 design 
assumptions with a standards-track MAY.  I would suggest that the 
text be modified along the following lines:

"Contrary to RFC2460 Section 4, middleboxes, such as firewalls, load 
balancers or packet classifiers, sometimes examine and process the 
entire IPv6 packet before making a decision to either forward or 
discard the packet."

//cmh

From acooper@cdt.org  Tue May 28 14:07:53 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1B421E809B for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 14:07:53 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0g-EhhGIgIF for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 14:07:47 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACE911E80D5 for <6man@ietf.org>; Tue, 28 May 2013 14:07:44 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Tue, 28 May 2013 17:07:38 -0400
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <51A207B0.4000900@si6networks.com>
Date: Tue, 28 May 2013 17:07:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE92F20E-0AE2-40D3-8637-16F9869869B6@cdt.org>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <51A207B0.4000900@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Tue, 28 May 2013 16:30:28 -0700
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 21:07:53 -0000

Hi Fernando,

Comments inline.

On May 26, 2013, at 9:01 AM, Fernando Gont <fgont@si6networks.com> =
wrote:

> HI Alissa,
>=20
> Thanks for posting this. Please find my comments inline...
>=20
> On 05/24/2013 11:33 PM, Alissa Cooper wrote:
>>=20
>> The rows of the table are the address generation methods that have
>> been discussed. The first three are for nodes that only use stable
>> addresses and never use temporary addresses. Incidentally, I assume
>> that it is this kind of configuration that Fernando's draft is
>> targeting=20
>=20
> Nope. We're improving stable addresses. Whether you use RFC4941 or not
> is pretty much orthogonal.
>=20

Fair enough.

>=20
>=20
>> -- the scenario where a network administrator has disabled
>> temporary addresses regardless of the desires of the user, as
>> described in section 1 of the draft. As can be seen in the table,
>> both random and random-per-network (my term for what the draft calls
>> stable privacy addresses) mitigate both types of address scanning
>> attacks. Random-per-network additionally mitigates location tracking
>> and potentially reduces the amount of time over which correlation can
>> take place.
>=20
> This assessment is correct. Note, however, that stable privacy =
addresses
> are also meant to be used in conjunction with rfc4941.
>=20
>=20
>=20
>> The second group of three are for nodes that only use temporary
>> addresses (but that also configure a stable address that never gets
>> used). This is what would be expected by users that want to avoid
>> correlation attacks, assuming their admins allow it. In this case
>> random and random-per-network provide equivalent protection.
>=20
> The problem here is that the assumption of "never gets used" is not
> correct. Or, well, you might argue "is not intentionally used for
> legitimate purposes".
>=20

Intentionally used is what I was going for, since some of the discussion =
about the choice of address generation mechanism revolves around =
intention. That is, some implementations/users might choose temporary =
addresses for specific reasons, sys admins might choose to disable them =
for specific reasons, etc.

> An attacker can trigger the use of such addresses, e.g., y sending his
> probe packets to the stable address.
>=20

In the case of a node that only intentionally uses temporary addresses, =
are there other uses you envision of that node's stable address besides =
the attacks in (a) and (b) in the table?


>=20
>=20
>=20
>> (row 2). If we're talking about the case where a node can use
>> temporary addresses and only uses them, random and random-per-network
>> provide the same benefits (rows 5 and 6). I'm assuming those are the
>> two common cases (could be wrong though).
>=20
> Please see above.

Not sure what this means -- in terms of the user's intent, I assume most =
users intend to either use a stable address all the time or use =
temporary addresses all the time.

>=20
>=20
>=20
>> If we take away the assumption that the node is never behind a
>> firewall and assume that it will never respond to unsolicited packets
>> (maybe too much too assume, but let's try), then the only differences
>> between the address generation mechanisms are with respect to
>> correlation. Random-per-network still provides some benefits over
>> random in this case.
>=20
> As noted, it is always possible to probe such node. e.g., rely on =
ICMPv6
> "address resolution failed" from the local router at the victim cite =
to
> tell whether the node is there or not.
>=20
>=20
>=20
>> Not sure if this is helpful to anyone else, but it clarified my
>> thinking on this a bit, and it might be worth making the threat
>> analysis in the draft more specific along these lines.
>=20
> How about including something along these lines (*) in an Appendix?
>=20
> (*) Discussion of possible attacks, and what stable privacy addresses =
do
> about them (analyzing this for every possible address generation
> mechanism would be out of scope for this I-D, IMO).

Agreed. However, even with the appendix, there are still some places =
where the discussion of the threat models in section 1 could be clearer, =
IMO. For example:

      However, even with temporary addresses [RFC4941] in place,
      preventing correlation of activities of a node within a network
      may be difficult (if at all possible) to achieve.  As a trivial
      example, consider a scenario where there is a single node (or a
      reduced number of nodes) connected to a specific network.  An
      attacker could detect new addresses in use at that network, an
      infer which addresses are being employed by which hosts.  This
      task is made particularly easier by the fact that use of
      "temporary addresses" can be easily inferred (since the follow
      different patterns from that of traditional SLAAC addresses), and
      since they are re-generated periodically (i.e., after a specific
      amount of time has elapsed).

My read of this is that you're talking about either (1) a situation =
where a node has a globally unique prefix, or (2) a situation where a =
small number of nodes share the same prefix and an attacker can =
disambiguate them using some other information about their behavior =
besides their IP addresses. Is that right? If that's the case, isn't =
correlation possible regardless of how the suffix is generated? The =
document seems to imply that nodes with temporary addresses are more =
susceptible to these two situations than nodes that use other address =
generation mechanisms, when in fact the first situation (globally unique =
prefix) probably affects all nodes equally regardless of generation =
mechanism, and in the second situation the fact that temporary addresses =
refresh frequently might erect a barrier that makes correlation more =
difficult and that would not exist with random or random-per-network =
addresses.

Another point for clarification:

   On the other hand, in scenarios in which "temporary addresses" are =
employed
   together with stable addresses such as those based on IEEE
   identifiers, implementation of the mechanism described in this
   document would mitigate address-scanning attacks and also mitigate
   some vectors for correlating host activities that are not mitigated
   by the use of temporary addresses.

Which correlation attack vectors do random-per-network addresses =
mitigate that temporary addresses do not? In the analysis in column (d) =
of the table, the correlation entries are the same for all of the =
address generation mechanisms in cases where the node intentionally uses =
temporary addresses.=20

Thanks,
Alissa

>=20
> Thanks!
>=20
> Best regards,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@si6networks.com
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
>=20
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
>=20



From msweet@apple.com  Tue May 28 16:58:12 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 386A721F8E93 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 16:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.559
X-Spam-Level: 
X-Spam-Status: No, score=-10.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id adEXCKtjM4oB for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 16:58:07 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 297C621F8E9A for <ipv6@ietf.org>; Tue, 28 May 2013 16:58:07 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNJ00JFP9785NM1@mail-out.apple.com> for ipv6@ietf.org; Tue, 28 May 2013 16:57:15 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-6f-51a54459d5d3
Received: from [17.153.23.147] (Unknown_Domain [17.153.23.147]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id 4C.56.31158.A5445A15; Tue, 28 May 2013 16:57:15 -0700 (PDT)
Subject: Re: Strange use of link-local (was: [Technical Errata Reported] RFC6874 (3630))
From: Michael Sweet <msweet@apple.com>
In-reply-to: <51A515C2.1090208@gmail.com>
Date: Tue, 28 May 2013 19:57:13 -0400
Message-id: <A9ABF29D-3195-4C62-AA99-9A599F4204F3@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <51A515C2.1090208@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUiOFN8sm60y9JAg64uUYu2i/uYLJo+9zFa XHt0n8Xi5dn3TBZHvsVa7Lla78DmsfXkDzaPXUd/sHs8OXudzWPnrLvsHkuW/GTyaN3xlz2A LYrLJiU1J7MstUjfLoEr4+DpBcwFK3Ur9i9dyNTA+Fili5GDQ0LAROLj9+ouRk4gU0ziwr31 bCC2kEAvk8SCpRYgtrBAhMSdy1PA4rwCehLXvn1lB7GZBbQkbvx7yQRiswmoSfye1McKYnMK aEr8udHHCGKzCKhKdC96DGRzAdVPYZR4vXYGK0SztsSyha+ZIYbaSEx9sIIFpEhI4BGLxJ+J e8E2iAgYSzR2nWaFuE5W4vXzNywTGPlnITlkFpJDZiGZu4CReRWjQFFqTmKlqV5iQUFOql5y fu4mRlAANxRG7GD8v8zqEKMAB6MSD++K70sChVgTy4orcw8xSnAwK4nwpgouDRTiTUmsrEot yo8vKs1JLT7EKM3BoiTOa2wDlBJITyxJzU5NLUgtgskycXBKNTBed42+oHXbTOxew8qwklvp SsdOvFXgzPM9IdMUvOHGDZd3t0RLRTo5622KNxa/vye7s/o9Y2xg6mPuMEstp9W7b5nfaueX PXpMcueVGTIW3WecP38Vvnx5gd+l5MZ/2+529i1yakrRfbttNq/4jc3dFXbaDxcH8325yJKq +anVb4KPVsHa7wFKLMUZiYZazEXFiQDNALFbXAIAAA==
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 28 May 2013 23:58:12 -0000

Brian,

On 2013-05-28, at 4:38 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> I'm increasingly baffled by the use case. If the host is
> in a context where it can reach a server *and* has more than
> one interface (such that a ZoneID is needed at all), it
> shouldn't be using a link local address anyway - it
> should have configured a global scope address (possibly
> under a ULA prefix). Discussion of this use case surely
> belongs in MIF or HOMENET.

Most hosts (and probably all of the ones we care about) have multiple network interfaces, if only the loopback interface plus some sort of external network interface, forcing the use of the zoneid.  Also, the most common place you would need to use a link-local address for access is the place where global scope addresses are basically never used - the home.

So I agree that the MIF or HOMENET working groups might have something to say here, but RFC 6874 was published by *this* group and IPv6 link local addresses have broader context than either of the other groups.



> 
>    Brian
> 
> On 29/05/2013 07:34, Ray Hunter wrote:
>> Warning: post contains dumb questions.
>> 
>> Michael Sweet wrote:
>>> Christian,
>>> 
>>> On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com> wrote:
>>>> Can we move from the process discussion to the technical discussion?
>>>> 
>>>> Michael raised an interesting issue, and we have to analyze it. The consensus of the working group so far is that interface identifiers are private to the host, that any leakage outside the host should be prevented, and that a way to prevent that leakage is to ask proxies to erase them whenever they have an opportunity. Michael points that some servers take an opposite approach, want to record the interface from which the host called them, and want to ensure that further calls in the same session use exactly the same interface. That seems that a fairly legitimate debate, and I can see two alternatives -- one would be to reaffirm the old guidance and provides alternative to ensure session continuity, and the other would be to reverse the guidance and accept that the layer violation performed by servers is just fine.
>>> 
>>> (the following is printer-centric, but the same applies to network video cameras and other embedded network devices)
>>> 
>>> Some background: HTTP and IPP services in printers include absolute URIs in the content they return. For IPP this can be http/https URLs to the printer's web page, ICC profiles, and other resources, along with the ipp/ipps URIs that the printer supports. For HTTP the most common are https URLs for "secure" areas of the printer's web interface.  Because a printer is often known by multiple names and addresses ("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation guidance (and in IPP Everywhere, this is a conformance requirement) is that the server use the HTTP Host header provided in the request in the host/address field of its responses, subject to the usual security considerations (SHOULD validate Host value, etc.)  This allows the client to use the name or address it can resolve/connect to and makes sure that the printer-generated absolute URIs lead back to same printer.
>>> 
>>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
>> Trying to understand what's going on here and what the root problem is.
>> 
>> I have some dumb questions:
>> 
>> Is the zoneid in the URI the interface on the client or the server node?
>> 
>> What does other party learn from this information, since zoneid is
>> currently defined as being local to the node and has no significance
>> outside the context of the node?
>> 
>> If the other party learns nothing, and the originating node just needs
>> to hear an echo of it's own information for it's own use, what's wrong
>> with using a cookie (server originated), or a hidden variable (client
>> originated), to transport this interface information along with the
>> request/reply?
>> 
>> What if both the server AND the client have multiple interfaces: how do
>> they both know which local interface on their own node is mutually
>> connected and to be used for communication? There's only one single
>> zoneid in the URI, so presumably one of the nodes is lacking some
>> information.
>> 
>> Shouldn't both nodes be using ND to learn this information?
>> If there's nothing in the cache, try all interfaces?
>> 
>> regards,
>> RayH
>> 
>>> What I propose is that we change the wording to allow the zoneid in the Host header but not in the Request-URI.  HTTP proxies would be required to strip any zoneid information in the Host header.  HTTP servers would be required to ignore any zoneid information for purposes of address validation but include it for any absolute URIs to the server they generate.
>>> 
>>> Thoughts?
>>> 
>>> _________________________________________________________
>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> 
>>> 
>> 
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> 

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From brian.e.carpenter@gmail.com  Tue May 28 18:37:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1075621F8EDF for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 18:37:40 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-laskQd4TXC for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 18:37:39 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 9B53821F8ED8 for <ipv6@ietf.org>; Tue, 28 May 2013 18:37:39 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id um15so8564943pbc.39 for <ipv6@ietf.org>; Tue, 28 May 2013 18:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=q3WOxxmGVv3wh19ivtOy6SHAN6EelX6afCd8GadwnCY=; b=saxrAc2kdNhZhYbRB3le4CD6ePBIRnMpvZ8jIzb2NHVyy5UHHqRNbZTY1CQPYwH/QH 8+JL/yhxkkmit9Dsk4tmfqGk+e9LgBAWmYQTeSpuKtmqfbeV34LqObWMJfG31vs3oFCf 0EjnCafx4HDUSpbthwaWhBjfNrrzRUZEGjcVEmM24fsux/WzJovqnIYFZZuBydSphLGD P0PSQ9/SWDfAc6aocSkeJFNNZxfBVlEftLEdS9xWAVubEwJEZuvVYlYz1eSWQFpUNK9c jWVhDRGH72vDsVadnJ7+Fg8+3/D+ib0Qwgl6IRwYhL4WfotwcjSICDh/+XNMJaynp+r5 B1ng==
X-Received: by 10.68.108.163 with SMTP id hl3mr417689pbb.160.1369791459390; Tue, 28 May 2013 18:37:39 -0700 (PDT)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id xu10sm37499268pab.3.2013.05.28.18.37.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 18:37:38 -0700 (PDT)
Message-ID: <51A55BE3.1070703@gmail.com>
Date: Wed, 29 May 2013 13:37:39 +1200
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: "C. M. Heard" <heard@pobox.com>
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com>	<519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi>	<519FD295.2060201@gmail.com> <51A08A7A.4000700@globis.net>	<51A120BA.2020805@gmail.com>	<51A1CD16.1060006@globis.net> <51A2E547.7040502@gmail.com> <Pine.LNX.4.64.1305271409240.25557@shell4.bayarea.net>
In-Reply-To: <Pine.LNX.4.64.1305271409240.25557@shell4.bayarea.net>
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.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 01:37:40 -0000

On 28/05/2013 09:16, C. M. Heard wrote:
> On Mon, 27 May 2013, Brian E Carpenter wrote:
>> On 26/05/2013 20:51, Ray Hunter wrote:
>>> I think that is worth pointing out in the draft that "Contrary to
>>> RFC2460 Section 4, middleboxes, such as firewalls, load balancers or
>>> packet classifiers, MAY examine and process the entire IPv6 packet
>>> before making a decision to either forward or discard the packet."
>> I'm not sure if it's really a MAY or simply a statement of what
>> occurs in the real world.
> 
> It should just be a statement of what occurs in the real world.  
> The IETF should not endorse behaviours that violate IPv6 design 
> assumptions with a standards-track MAY.  I would suggest that the 
> text be modified along the following lines:
> 
> "Contrary to RFC2460 Section 4, middleboxes, such as firewalls, load 
> balancers or packet classifiers, sometimes examine and process the 
> entire IPv6 packet before making a decision to either forward or 
> discard the packet."

Yes, IMHO that's well phrased. I'm going to have a go at a new version
that includes that, and various other changes following Ray's comments.
Please watch this space.

     Brian

From dthaler@microsoft.com  Tue May 28 19:01:17 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469E821F86C0 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 19:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.467
X-Spam-Level: 
X-Spam-Status: No, score=-97.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKLvNRZ3-6Yk for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 19:01:10 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id 0E2BE21F86F5 for <6man@ietf.org>; Tue, 28 May 2013 19:01:09 -0700 (PDT)
Received: from BY2FFO11FD022.protection.gbl (10.1.15.204) by BY2FFO11HUB040.protection.gbl (10.1.14.161) with Microsoft SMTP Server (TLS) id 15.0.698.0; Wed, 29 May 2013 02:01:07 +0000
Received: from TK5EX14HUBC105.redmond.corp.microsoft.com (131.107.125.37) by BY2FFO11FD022.mail.protection.outlook.com (10.1.15.211) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Wed, 29 May 2013 02:01:07 +0000
Received: from CO9EHSOBE012.bigfish.com (157.54.51.114) by mail.microsoft.com (157.54.80.48) with Microsoft SMTP Server (TLS) id 14.3.136.1; Wed, 29 May 2013 02:01:05 +0000
Received: from mail171-co9-R.bigfish.com (10.236.132.251) by CO9EHSOBE012.bigfish.com (10.236.130.75) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 May 2013 02:01:05 +0000
Received: from mail171-co9 (localhost [127.0.0.1])	by mail171-co9-R.bigfish.com (Postfix) with ESMTP id 2F21DCC013C	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 29 May 2013 02:01:05 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT005.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zzbb2dI98dI9371I542I1432I4015I62a3Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275bhz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h17ej9a9j1155h)
Received-SPF: softfail (mail171-co9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT005.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB270; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail171-co9 (localhost.localdomain [127.0.0.1]) by mail171-co9 (MessageSwitch) id 1369792863590035_2580; Wed, 29 May 2013 02:01:03 +0000 (UTC)
Received: from CO9EHSMHS002.bigfish.com (unknown [10.236.132.249])	by mail171-co9.bigfish.com (Postfix) with ESMTP id 8324F2C004D; Wed, 29 May 2013 02:01:03 +0000 (UTC)
Received: from BL2PRD0310HT005.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS002.bigfish.com (10.236.130.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 May 2013 02:01:01 +0000
Received: from BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) by BL2PRD0310HT005.namprd03.prod.outlook.com (10.255.97.40) with Microsoft SMTP Server (TLS) id 14.16.311.1; Wed, 29 May 2013 02:00:58 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB270.namprd03.prod.outlook.com (10.242.37.12) with Microsoft SMTP Server (TLS) id 15.0.698.13; Wed, 29 May 2013 02:00:55 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Wed, 29 May 2013 02:00:55 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAZOUUAAAClyEAAANgt8AAA0lZgAEIhrwAAjdWMYA==
Date: Wed, 29 May 2013 02:00:55 +0000
Message-ID: <6f1339e1ed4e440e8d560a1183ac178b@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com> <51A1A7FE.9010501@si6networks.com>
In-Reply-To: <51A1A7FE.9010501@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:24d6:67ae:ed1b:a4be]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB270.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC105.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC105.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(252514006)(479174002)(199002)(24454002)(13464003)(189002)(164054003)(51704005)(377454002)(31966008)(81542001)(69226001)(63696002)(56816002)(47736001)(56776001)(59766001)(74662001)(4396001)(49866001)(46102001)(77982001)(74366001)(51856001)(46406003)(33646001)(44976003)(53806001)(50986001)(76482001)(16676001)(47976001)(74316001)(81342001)(6806003)(54356001)(20776003)(80022001)(74706001)(47776003)(79102001)(74876001)(54316002)(23726002)(50466002)(47446002)(65816001)(76576001)(74502001)(24736002)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BY2FFO11HUB040; H:TK5EX14HUBC105.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08617F610C
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 02:01:17 -0000

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Saturday, May 25, 2013 11:13 PM
> To: Dave Thaler
> Cc: Alissa Cooper; 6man-chairs@tools.ietf.org; Brian Haberman;
> 6man@ietf.org; Ray Hunter; tom.petch; Christian Huitema; He Xuan
> Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> Dave,
>=20
> What does draft-ietf-6man-stable-privacy-addresses has to do with CGAs?

1) Both give "random-per-network" addresses, using Alissa's terminology.
2) Both generate an IP address using a secret + a network prefix + a DAD co=
unter + other information.

So it comes down to what was claimed, which I don't know offhand.

> Has MS or Ericsson patented the use of PRFs?

Pseudorandom functions themselves are well known.  Some folks (don't know) =
might
have patented using PRFs in novel ways to do specific things.

> Have you guys any IPR on RFC1948? -- Because draft-ietf-6man-stableprivac=
y-
> addresses is essentially Bellovin's
> RFC1948 applied to IPv6 addresses.

I'm not personally familiar with RFC1948 so will leave that to others to an=
swer.

-Dave

>=20
> Thanks,
> Fernando
>=20
>=20
>=20
>=20
> On 05/25/2013 12:43 AM, Dave Thaler wrote:
> > It also now occurs to me that since RFC 3972 has IPR disclosures from
> > both Microsoft and Ericsson, those disclosures may or may not apply to
> > draft-ietf-6man-stable-privacy-addresses as well.
> >
> > Per the Note Well, I'm at least sending this email, but will check
> > with Microsoft folks to see whether an IPR statement would be needed
> > on this draft (personally I have no clue).
> >
> > I'd suggest that any Ericsson folks paying attention might need to do t=
he
> same.
>=20
>=20
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
>=20



From dthaler@microsoft.com  Tue May 28 19:03:44 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16F0821F8F9E for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 19:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.467
X-Spam-Level: 
X-Spam-Status: No, score=-97.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+s8KPDM5zSU for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 19:03:37 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0236.outbound.protection.outlook.com [207.46.163.236]) by ietfa.amsl.com (Postfix) with ESMTP id 8615B21F87B7 for <6man@ietf.org>; Tue, 28 May 2013 19:03:37 -0700 (PDT)
Received: from BL2FFO11FD026.protection.gbl (10.173.161.203) by BL2FFO11HUB025.protection.gbl (10.173.161.49) with Microsoft SMTP Server (TLS) id 15.0.698.0; Wed, 29 May 2013 02:03:35 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD026.mail.protection.outlook.com (10.173.161.105) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Wed, 29 May 2013 02:03:35 +0000
Received: from CO9EHSOBE033.bigfish.com (157.54.51.114) by mail.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.3.136.1; Wed, 29 May 2013 02:03:32 +0000
Received: from mail68-co9-R.bigfish.com (10.236.132.250) by CO9EHSOBE033.bigfish.com (10.236.130.96) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 May 2013 02:03:22 +0000
Received: from mail68-co9 (localhost [127.0.0.1])	by mail68-co9-R.bigfish.com (Postfix) with ESMTP id C41631801B9	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Wed, 29 May 2013 02:03:22 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT005.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: 3
X-BigFish: PS3(zz1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzzz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h17ej9a9j1155h)
Received-SPF: softfail (mail68-co9: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT005.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BY2PR03MB271; H:BY2PR03MB269.namprd03.prod.outlook.com; LANG:en; 
Received: from mail68-co9 (localhost.localdomain [127.0.0.1]) by mail68-co9 (MessageSwitch) id 1369793000933873_8056; Wed, 29 May 2013 02:03:20 +0000 (UTC)
Received: from CO9EHSMHS026.bigfish.com (unknown [10.236.132.254])	by mail68-co9.bigfish.com (Postfix) with ESMTP id E0DB82E008C; Wed, 29 May 2013 02:03:20 +0000 (UTC)
Received: from BL2PRD0310HT005.namprd03.prod.outlook.com (157.56.240.21) by CO9EHSMHS026.bigfish.com (10.236.130.36) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 May 2013 02:03:20 +0000
Received: from BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) by BL2PRD0310HT005.namprd03.prod.outlook.com (10.255.97.40) with Microsoft SMTP Server (TLS) id 14.16.311.1; Wed, 29 May 2013 02:03:20 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com (10.242.37.11) by BY2PR03MB271.namprd03.prod.outlook.com (10.242.37.14) with Microsoft SMTP Server (TLS) id 15.0.698.13; Wed, 29 May 2013 02:03:17 +0000
Received: from BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) by BY2PR03MB269.namprd03.prod.outlook.com ([169.254.5.183]) with mapi id 15.00.0698.010; Wed, 29 May 2013 02:03:17 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAbHCNgAFBo/gAAgD2i4A==
Date: Wed, 29 May 2013 02:03:16 +0000
Message-ID: <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com>
In-Reply-To: <51A204F2.7060400@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:1a:3:24d6:67ae:ed1b:a4be]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BY2PR03MB271.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC103.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC103.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(51704005)(46406003)(47776003)(74876001)(20776003)(63696002)(74366001)(69226001)(16676001)(50466002)(74316001)(65816001)(74706001)(6806003)(33646001)(44976003)(80022001)(23726002)(81342001)(47446002)(56816002)(49866001)(47736001)(81542001)(56776001)(47976001)(54316002)(46102001)(4396001)(77982001)(74662001)(74502001)(31966008)(54356001)(76482001)(79102001)(50986001)(51856001)(53806001)(59766001)(76576001)(3826001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2FFO11HUB025; H:TK5EX14HUBC103.redmond.corp.microsoft.com; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08617F610C
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 02:03:44 -0000

> >> [...] I could rely on the
> >> ICMPv6 "address resolution failed" error messages sent by your local
> >> router (i.e., if I receive one of such messages, you're not there. If =
I don't,
> you are).
> >
> > Ok, yes that one is interesting.
>=20
> An attacker just needs one vector to be successful.

Agree.  Putting the above example vector into the draft would help the read=
er
understand the motivation for the problem.

-dave



From tjc@ecs.soton.ac.uk  Tue May 28 23:20:50 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344E121F901F for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wCL9aCvAZqJ for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:20:47 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id B0A6421F9017 for <ipv6@ietf.org>; Tue, 28 May 2013 23:20:44 -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 r4T6K7H7000509; Wed, 29 May 2013 07:20:07 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4T6K7H7000509
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369808408; bh=F3hJAjtGOJclsjPkjNyHRzfTWts=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=Az6kubxAdgNNmqQKs/kkAjGEWPjltyDUiCs1diV5b9t0ECvDJlFTH8bpkP+YFtJrZ OPi/YjRSqAcwRhoBYvne9Eo1wRapPMw433tG0rX8zik+tpOAIV9CVQbWEEMKKA9C58 r2guwY9Z60YesIPOkToQMpEN6rGZvcK4qA7ue9t0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4S7K70430601530FL ret-id none; Wed, 29 May 2013 07:20:08 +0100
Received: from [192.168.1.103] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4T6IlHK025445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 07:18:48 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_8BD846AF-F672-403A-8587-DEC8149DE2EC"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Strange use of link-local (was: [Technical Errata Reported] RFC6874 (3630))
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <A9ABF29D-3195-4C62-AA99-9A599F4204F3@apple.com>
Date: Wed, 29 May 2013 07:18:50 +0100
Message-ID: <EMEW3|0bdacdb5983756ea5d3dee7295117e37p4S7K703tjc|ecs.soton.ac.uk|D9870A41-91CC-4383-89DB-B64928DD9DD8@ecs.soton.ac.uk>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <51A515C2.1090208@gmail.com> <A9ABF29D-3195-4C62-AA99-9A599F4204F3@apple.com> <D9870A41-91CC-4383-89DB-B64928DD9DD8@ecs.soton.ac.uk>
To: Michael Sweet <msweet@apple.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4S7K7043060153000; tid=p4S7K70430601530FL; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4T6K7H7000509
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Ray Hunter <v6ops@globis.net>, Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 06:20:50 -0000

--Apple-Mail=_8BD846AF-F672-403A-8587-DEC8149DE2EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 29 May 2013, at 00:57, Michael Sweet <msweet@apple.com> wrote:

> Brian,
>=20
> On 2013-05-28, at 4:38 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> I'm increasingly baffled by the use case. If the host is
>> in a context where it can reach a server *and* has more than
>> one interface (such that a ZoneID is needed at all), it
>> shouldn't be using a link local address anyway - it
>> should have configured a global scope address (possibly
>> under a ULA prefix). Discussion of this use case surely
>> belongs in MIF or HOMENET.
>=20
> Most hosts (and probably all of the ones we care about) have multiple =
network interfaces, if only the loopback interface plus some sort of =
external network interface, forcing the use of the zoneid.  Also, the =
most common place you would need to use a link-local address for access =
is the place where global scope addresses are basically never used - the =
home.
>=20
> So I agree that the MIF or HOMENET working groups might have something =
to say here, but RFC 6874 was published by *this* group and IPv6 link =
local addresses have broader context than either of the other groups.

Indeed, the single subnet view may be the case today for IPv4 homenets, =
but not necessarily so in an IPv6 homenet future.  See =
http://tools.ietf.org/html/draft-ietf-homenet-arch-08.  So any design =
should take that into account.=20

One interesting question for homenet is how zeroconf naming and service =
discovery protocols are extended to work in routed homenets.  Protocols =
such as PCP will also need to work in such environments should devices =
wish to open firewall holes. If there are other cases where link-local =
protocols need to work across multi-subnet zeroconf environments, where =
those environments are typically single subnets today, those would be =
good to tease out. =20

Tim

>=20
>>=20
>>   Brian
>>=20
>> On 29/05/2013 07:34, Ray Hunter wrote:
>>> Warning: post contains dumb questions.
>>>=20
>>> Michael Sweet wrote:
>>>> Christian,
>>>>=20
>>>> On 2013-05-24, at 1:45 PM, Christian Huitema =
<huitema@microsoft.com> wrote:
>>>>> Can we move from the process discussion to the technical =
discussion?
>>>>>=20
>>>>> Michael raised an interesting issue, and we have to analyze it. =
The consensus of the working group so far is that interface identifiers =
are private to the host, that any leakage outside the host should be =
prevented, and that a way to prevent that leakage is to ask proxies to =
erase them whenever they have an opportunity. Michael points that some =
servers take an opposite approach, want to record the interface from =
which the host called them, and want to ensure that further calls in the =
same session use exactly the same interface. That seems that a fairly =
legitimate debate, and I can see two alternatives -- one would be to =
reaffirm the old guidance and provides alternative to ensure session =
continuity, and the other would be to reverse the guidance and accept =
that the layer violation performed by servers is just fine.
>>>>=20
>>>> (the following is printer-centric, but the same applies to network =
video cameras and other embedded network devices)
>>>>=20
>>>> Some background: HTTP and IPP services in printers include absolute =
URIs in the content they return. For IPP this can be http/https URLs to =
the printer's web page, ICC profiles, and other resources, along with =
the ipp/ipps URIs that the printer supports. For HTTP the most common =
are https URLs for "secure" areas of the printer's web interface.  =
Because a printer is often known by multiple names and addresses =
("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, =
etc.), the implementation guidance (and in IPP Everywhere, this is a =
conformance requirement) is that the server use the HTTP Host header =
provided in the request in the host/address field of its responses, =
subject to the usual security considerations (SHOULD validate Host =
value, etc.)  This allows the client to use the name or address it can =
resolve/connect to and makes sure that the printer-generated absolute =
URIs lead back to same printer.
>>>>=20
>>>> All of this falls apart with link-local addresses and RFC 6874.  =
Because the client is required to remove the zoneid from the outgoing =
request, the URIs it gets back from the server are no longer =
"reachable".
>>> Trying to understand what's going on here and what the root problem =
is.
>>>=20
>>> I have some dumb questions:
>>>=20
>>> Is the zoneid in the URI the interface on the client or the server =
node?
>>>=20
>>> What does other party learn from this information, since zoneid is
>>> currently defined as being local to the node and has no significance
>>> outside the context of the node?
>>>=20
>>> If the other party learns nothing, and the originating node just =
needs
>>> to hear an echo of it's own information for it's own use, what's =
wrong
>>> with using a cookie (server originated), or a hidden variable =
(client
>>> originated), to transport this interface information along with the
>>> request/reply?
>>>=20
>>> What if both the server AND the client have multiple interfaces: how =
do
>>> they both know which local interface on their own node is mutually
>>> connected and to be used for communication? There's only one single
>>> zoneid in the URI, so presumably one of the nodes is lacking some
>>> information.
>>>=20
>>> Shouldn't both nodes be using ND to learn this information?
>>> If there's nothing in the cache, try all interfaces?
>>>=20
>>> regards,
>>> RayH
>>>=20
>>>> What I propose is that we change the wording to allow the zoneid in =
the Host header but not in the Request-URI.  HTTP proxies would be =
required to strip any zoneid information in the Host header.  HTTP =
servers would be required to ignore any zoneid information for purposes =
of address validation but include it for any absolute URIs to the server =
they generate.
>>>>=20
>>>> Thoughts?
>>>>=20
>>>> _________________________________________________________
>>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>=20
>>>>=20
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>=20
>=20
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_8BD846AF-F672-403A-8587-DEC8149DE2EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 29 May 2013, at 00:57, Michael Sweet &lt;<a =
href=3D"mailto:msweet@apple.com">msweet@apple.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Brian,<br><br>On 2013-05-28, at 4:38 PM, Brian E Carpenter =
&lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:<br><blockquote type=3D"cite">I'm increasingly baffled by =
the use case. If the host is<br>in a context where it can reach a server =
*and* has more than<br>one interface (such that a ZoneID is needed at =
all), it<br>shouldn't be using a link local address anyway - =
it<br>should have configured a global scope address (possibly<br>under a =
ULA prefix). Discussion of this use case surely<br>belongs in MIF or =
HOMENET.<br></blockquote><br>Most hosts (and probably all of the ones we =
care about) have multiple network interfaces, if only the loopback =
interface plus some sort of external network interface, forcing the use =
of the zoneid. &nbsp;Also, the most common place you would need to use a =
link-local address for access is the place where global scope addresses =
are basically never used - the home.<br><br>So I agree that the MIF or =
HOMENET working groups might have something to say here, but RFC 6874 =
was published by *this* group and IPv6 link local addresses have broader =
context than either of the other =
groups.<br></blockquote><div><br></div>Indeed, the single subnet =
view&nbsp;may be the case today for IPv4 homenets, but not necessarily =
so in an IPv6 homenet future. &nbsp;See&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-homenet-arch-08">http://tool=
s.ietf.org/html/draft-ietf-homenet-arch-08</a>. &nbsp;So any design =
should take that into account.&nbsp;</div><div><br></div><div>One =
interesting question for homenet is how zeroconf naming and service =
discovery protocols are extended to work in routed homenets. =
&nbsp;Protocols such as PCP will also need to work in such environments =
should devices wish to open firewall holes. If there are other cases =
where link-local protocols need to work across multi-subnet zeroconf =
environments, where those environments are typically single subnets =
today, those would be good to tease out. =
&nbsp;</div><div><br></div><div>Tim</div><div><br><blockquote =
type=3D"cite"><br><blockquote type=3D"cite"><br> =
&nbsp;&nbsp;Brian<br><br>On 29/05/2013 07:34, Ray Hunter =
wrote:<br><blockquote type=3D"cite">Warning: post contains dumb =
questions.<br><br>Michael Sweet wrote:<br><blockquote =
type=3D"cite">Christian,<br><br>On 2013-05-24, at 1:45 PM, Christian =
Huitema &lt;<a =
href=3D"mailto:huitema@microsoft.com">huitema@microsoft.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">Can we move from the process =
discussion to the technical discussion?<br><br>Michael raised an =
interesting issue, and we have to analyze it. The consensus of the =
working group so far is that interface identifiers are private to the =
host, that any leakage outside the host should be prevented, and that a =
way to prevent that leakage is to ask proxies to erase them whenever =
they have an opportunity. Michael points that some servers take an =
opposite approach, want to record the interface from which the host =
called them, and want to ensure that further calls in the same session =
use exactly the same interface. That seems that a fairly legitimate =
debate, and I can see two alternatives -- one would be to reaffirm the =
old guidance and provides alternative to ensure session continuity, and =
the other would be to reverse the guidance and accept that the layer =
violation performed by servers is just fine.<br></blockquote><br>(the =
following is printer-centric, but the same applies to network video =
cameras and other embedded network devices)<br><br>Some background: HTTP =
and IPP services in printers include absolute URIs in the content they =
return. For IPP this can be http/https URLs to the printer's web page, =
ICC profiles, and other resources, along with the ipp/ipps URIs that the =
printer supports. For HTTP the most common are https URLs for "secure" =
areas of the printer's web interface. &nbsp;Because a printer is often =
known by multiple names and addresses ("printer.local.", "<a =
href=3D"http://printer.example.com">printer.example.com</a>.", =
192.168.0.100, fe80::1234, etc.), the implementation guidance (and in =
IPP Everywhere, this is a conformance requirement) is that the server =
use the HTTP Host header provided in the request in the host/address =
field of its responses, subject to the usual security considerations =
(SHOULD validate Host value, etc.) &nbsp;This allows the client to use =
the name or address it can resolve/connect to and makes sure that the =
printer-generated absolute URIs lead back to same printer.<br><br>All of =
this falls apart with link-local addresses and RFC 6874. &nbsp;Because =
the client is required to remove the zoneid from the outgoing request, =
the URIs it gets back from the server are no longer =
"reachable".<br></blockquote>Trying to understand what's going on here =
and what the root problem is.<br><br>I have some dumb =
questions:<br><br>Is the zoneid in the URI the interface on the client =
or the server node?<br><br>What does other party learn from this =
information, since zoneid is<br>currently defined as being local to the =
node and has no significance<br>outside the context of the =
node?<br><br>If the other party learns nothing, and the originating node =
just needs<br>to hear an echo of it's own information for it's own use, =
what's wrong<br>with using a cookie (server originated), or a hidden =
variable (client<br>originated), to transport this interface information =
along with the<br>request/reply?<br><br>What if both the server AND the =
client have multiple interfaces: how do<br>they both know which local =
interface on their own node is mutually<br>connected and to be used for =
communication? There's only one single<br>zoneid in the URI, so =
presumably one of the nodes is lacking =
some<br>information.<br><br>Shouldn't both nodes be using ND to learn =
this information?<br>If there's nothing in the cache, try all =
interfaces?<br><br>regards,<br>RayH<br><br><blockquote type=3D"cite">What =
I propose is that we change the wording to allow the zoneid in the Host =
header but not in the Request-URI. &nbsp;HTTP proxies would be required =
to strip any zoneid information in the Host header. &nbsp;HTTP servers =
would be required to ignore any zoneid information for purposes of =
address validation but include it for any absolute URIs to the server =
they =
generate.<br><br>Thoughts?<br><br>________________________________________=
_________________<br>Michael Sweet, Senior Printing System Engineer, PWG =
Chair<br><br><br></blockquote><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><br></blockquote></blockquote>=
<br>_________________________________________________________<br>Michael =
Sweet, Senior Printing System Engineer, PWG =
Chair<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></blockquote></div><br></body>=
</html>=

--Apple-Mail=_8BD846AF-F672-403A-8587-DEC8149DE2EC--

From tjc@ecs.soton.ac.uk  Tue May 28 23:22:58 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F32E121F8F29 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level: 
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDlJ0ICONWdA for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:22:57 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id EEA9621F8F27 for <ipv6@ietf.org>; Tue, 28 May 2013 23:22:56 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4T6MSJB000840;  Wed, 29 May 2013 07:22:28 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4T6MSJB000840
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369808549; bh=TKxNqPEYoAHnt9XKcHFAzod9Hjo=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jBIaxhTKVkFFUaTRg0OhXFYTJY4Lu11XL42pRd9wNaA+TUzHl/7Fnnu/ff6rpjX8t /NiKKGCcPM2U50E6QX86M+efjI3RHTPPqOiu2RceKVU9tU82V9b27Y8ImWD/eRkhof lOCkDxRFcgt+cD6twRvAkwFU/kzuT+GGB7mKdb/M=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4S7MS0430601540Z3 ret-id none; Wed, 29 May 2013 07:22:29 +0100
Received: from [192.168.1.103] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4T6MMN8027147 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 07:22:22 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Fwd: I-D Action: draft-ietf-6man-ext-transmit-00.txt]
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <519FD295.2060201@gmail.com>
Date: Wed, 29 May 2013 07:22:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|46babc55361b412a01619584c2d3b0adp4S7MS03tjc|ecs.soton.ac.uk|F023F6DF-30EC-41CA-BEEA-AE5080F10320@ecs.soton.ac.uk>
References: <5155BD4C.9030307@gmail.com> <519ED41F.5050306@gmail.com> <519F0E3B.5010200@globis.net> <20130524124005.GR23227@verdi> <519FD295.2060201@gmail.com> <F023F6DF-30EC-41CA-BEEA-AE5080F10320@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4S7MS043060154000; tid=p4S7MS0430601540Z3; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4T6MSJB000840
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Ray Hunter <v6ops@globis.net>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 06:22:58 -0000

On 24 May 2013, at 21:50, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 25/05/2013 02:43, Tim Chown wrote:
>=20
>> A couple of additional comments.
>>=20
>> One is that from time to time there may be security issues raised =
with certain headers, e.g. RH0. These may obviously be raised over time. =
Is there a mechanism to catch these in the IANA registry somehow?
>=20
> Shouldn't this just be part of the Security Comsiderations for
> the definition of each header? The registry will always contain a =
pointer
> to the relevant RFCs. IANA can't do much if the Security =
Considerations
> are insufficient.

Fair enough. It was just a question as to how it can be made as easy as =
possible for a developer to catch all the latest requirements/specs.

>> Another is whether there is any use of the "null" header type 59?  Or =
has that been deprecated?  If not, should it be so, given Brian doesn't =
list it.  Or is this viewed in the same category as TCP, etc as header =
types?
>=20
> I think we included that in an earlier draft, but then removed it
> because it appears to function as a null transport header. It's
> a judgment call, and only needs a few keystrokes to put it back in the
> list.

OK, I have no strong preference, but you could maybe state in the draft =
that it is excluded and why, so readers don't wonder about it.

Overall I think the draft is in good shape, and the tweaks based on =
Ray's comments should make it even better.

Tim

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


From v6ops@globis.net  Tue May 28 23:53:07 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDCCC21F8E76 for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:53:06 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2ss4l98C+DD for <ipv6@ietfa.amsl.com>; Tue, 28 May 2013 23:53:02 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id E0B5A21F901A for <ipv6@ietf.org>; Tue, 28 May 2013 23:52:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B16138700BD; Wed, 29 May 2013 08:52:42 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diKUv-q4F9hD; Wed, 29 May 2013 08:52:42 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 91F5D87005E; Wed, 29 May 2013 08:52:42 +0200 (CEST)
Message-ID: <51A5A5B4.8040500@globis.net>
Date: Wed, 29 May 2013 08:52:36 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com>
In-Reply-To: <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 06:53:08 -0000

> Michael Sweet <mailto:msweet@apple.com>
> 29 May 2013 01:27
> Ray,
>
> On 2013-05-28, at 3:34 PM, Ray Hunter <v6ops@globis.net> wrote:
>> Warning: post contains dumb questions.
>
> No such thing! :)
>
>>> ...
>>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
>> Trying to understand what's going on here and what the root problem is.
>>
>> I have some dumb questions:
>>
>> Is the zoneid in the URI the interface on the client or the server node?
>
> It is the interface on the client.
ACK.

So the server's CGI script echoes the HTTP request header field "Host"
set by the client browser back to the client in the URI
so that when the link to the next request is clicked at the client's
browser (or interpreted by another app on the client), it knows which
local interface to use to reach the server again?

Where's the standard that says ZoneID MUST be included in the Host
header? I presume this is rfc2616#page-128.

And the value of "Host" is always set to the host portion of the
original URI [which will currently include a ZoneID on current
implementations]?

Do you think that 6874 mandates that the ZoneID MUST be stripped from
the "Host" HTTP request header, as Host is sub-string of a URI?
>
>> What does other party learn from this information, since zoneid is
>> currently defined as being local to the node and has no significance
>> outside the context of the node?
>
> The only thing it learns is "this is the address the client is using to talk to me".
ACK.
>> If the other party learns nothing, and the originating node just needs
>> to hear an echo of it's own information for it's own use, what's wrong
>> with using a cookie (server originated), or a hidden variable (client
>> originated), to transport this interface information along with the
>> request/reply?
>
> Well, for starters none of that is standardized, whereas "Host" is a required HTTP request header that printers (and web servers) already support.
>
> Also, passing the information back from the server in a cookie doesn't address the client-sde URI rewriting problem: it is much simpler (and less error prone) for the server to use the client-supplied address for the URIs in its response than for the client to parse and rewrite all of the URIs in the server's response.
ACK.
>> What if both the server AND the client have multiple interfaces: how do
>> they both know which local interface on their own node is mutually
>> connected and to be used for communication? There's only one single
>> zoneid in the URI, so presumably one of the nodes is lacking some
>> information.
>
> The server knows its own link-local addresses and doesn't need the zoneid information.
I don't understand this logic. I'm presuming the outbound interface for
replies is being selected by mirroring the inbound addresses of the
request [quoting RFC6724: "In many cases, this is trivially dealt with
by an application using the source address of a received packet as the
response destination and the destination address of the received packet
as the response source."]

However I thought one of the use cases was the printer sending
unsolicited information such as "out of paper".

How would the server then select its correct local outbound interface,
if it had multiple?
Does the client supply a "callback address/port" that the printer
stores/caches?

 

>  For the use case under discussion, the client only knows its zoneid information because the user/administrator has supplied it along with the printer's link-local address.
Right. That was going to be my next question.

How does the very first URI learn the correct ZoneID in the first place?
Manually.



>> Shouldn't both nodes be using ND to learn this information?
>> If there's nothing in the cache, try all interfaces?
>
>
> It would be awesome if printers supported Neighbor Discovery, but of the four printers in my home office only three support IPv6 and only one supports ND.  One of the IPv6 printers is 3 years old, the other three are less than a year old...
Understood.
>
> On the client side you'll find a similar story - sporadic support, and in many cases the ND information isn't wired into the resolver libraries, making it impossible to use a bare IPv6 link-local address without the zoneid added at the end...
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>

From jiangsheng@huawei.com  Wed May 29 00:07:19 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28B121F9195; Wed, 29 May 2013 00:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3053boJLw0+K; Wed, 29 May 2013 00:07:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D168B21F85B4; Wed, 29 May 2013 00:07:10 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATG86921; Wed, 29 May 2013 07:07:03 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 29 May 2013 08:06:30 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 29 May 2013 08:07:00 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.01.0323.007; Wed, 29 May 2013 15:06:54 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "<v6ops@ietf.org>" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV98w==
Date: Wed, 29 May 2013 07:06:54 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 07:07:19 -0000

SVAgYWRkcmVzc2VzIGFyZSBkZXNpZ25lZCBhcyB0b3BvbG9neSBsb2NhdG9yLCBzbyB0aGF0IGV2
ZXJ5IHBhY2tldCBjYW4gYmUgcm91dGVkIHRvIGl0cyBuZXR3b3JrIGRlc3RpbmF0aW9uLg0KDQpI
b3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBzb21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFw
cGVkIHRoZWlyIElQIGFkZHJlc3Mgd2l0aCBjZXJ0YWluIHNlbWFudGljIGxvY2FsbHkuIFRoZXNl
IGtpbmQgb2YgbWVjaGFuaXNtIGV4cGxpY2l0bHkgZXhwcmVzcyB0aGUgc2VtYW50aWMgcHJvcGVy
dGllcyBvZiBldmVyeSBwYWNrZXQuIENvbnNlcXVlbnRseSwgdGhlc2UgbmV0d29yayBvcGVyYXRv
cnMgY2FuIGluc3BlY3QgdGhlIHByb3BlcnRpZXMgb2YgcGFja2V0cyBlYXNpbHkgYnkgbWFwcGlu
ZyB0aGUgYWRkcmVzc2VzIGJhY2sgdG8gc2VtYW50aWMuDQoNCk5ldHdvcmsgb3BlcmF0b3JzLCB3
aG8gaGF2ZSBsYXJnZSBJUHY2IGFkZHJlc3Mgc3BhY2UsIG1heSBhbHNvIGNob29zZSB0byBlbWJl
ZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGJ5IGFzc2lnbmluZyBhZGRp
dGlvbmFsIHNpZ25pZmljYW5jZSB0byBzcGVjaWZpYyBiaXRzIHdpdGhpbiB0aGUgcHJlZml4LiBk
cmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXggZG9jdW1lbnRzIGEgZnJhbWV3b3JrIG1l
dGhvZCB0aGF0IG5ldHdvcmsgb3BlcmF0aW9ucyBtYXkgdXNlIHRoZWlyIGFkZHJlc3NlcyB3aXRo
IGVtYmVkZGVkIHNlbWFudGljcy4gVGhlc2Ugc2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmlu
Z2Z1bCB3aXRoaW4gYSBzaW5nbGUgbmV0d29yaywgb3IgZ3JvdXAgb2YgaW50ZXJjb25uZWN0ZWQg
bmV0d29ya3Mgd2hpY2ggc2hhcmUgYSBjb21tb24gYWRkcmVzc2luZyBwb2xpY3kuIEJhc2VkIG9u
IHRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMgaW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJl
c3NlcywgdGhlIG5ldHdvcmsgb3BlcmF0b3JzIGNhbiBhY2NvcmRpbmdseSB0cmVhdCBuZXR3b3Jr
IHBhY2tldHMgZGlmZmVyZW50bHkgYW5kIGVmZmljaWVudGx5Lg0KDQpodHRwOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMNCg0KQ291bGQg
eW91IHBsZWFzZSByZXZpZXcgdGhpcyBkcmFmdCBhbmQgY29tbWVudHM/IEl0IHdpbGwgaGVscCB0
aGUgZG9jdW1lbnQgYmVjb21lIG1vcmUgdXNlZnVsIGluZm9ybWF0aW9uIHRvIGJlIHNoYXJlZC4N
Cg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cj5Gcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNA
aWV0Zi5vcmddDQo+U2VudDogVHVlc2RheSwgTWF5IDI4LCAyMDEzIDEwOjI4IEFNDQo+VG86IFFp
b25nIFN1bjsgSWFuIEZhcnJlcjsgU2hlbmcgSmlhbmc7IEJveWFuZw0KPlN1YmplY3Q6IE5ldyBW
ZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3INCj5kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVm
aXgtMDMudHh0DQo+DQo+DQo+QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWppYW5nLXY2b3Bz
LXNlbWFudGljLXByZWZpeC0wMy50eHQNCj5oYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVk
IGJ5IFNoZW5nIEppYW5nIGFuZCBwb3N0ZWQgdG8gdGhlDQo+SUVURiByZXBvc2l0b3J5Lg0KPg0K
PkZpbGVuYW1lOgkgZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4DQo+UmV2aXNpb246
CSAwMw0KPlRpdGxlOgkJIEEgRnJhbWV3b3JrIGZvciBTZW1hbnRpYyBJUHY2IFByZWZpeA0KPkNy
ZWF0aW9uIGRhdGU6CSAyMDEzLTA1LTI4DQo+R3JvdXA6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9u
DQo+TnVtYmVyIG9mIHBhZ2VzOiAxOQ0KPlVSTDoNCj5odHRwOi8vd3d3LmlldGYub3JnL2ludGVy
bmV0LWRyYWZ0cy9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMudHh0DQo+U3Rh
dHVzOg0KPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtamlhbmctdjZvcHMt
c2VtYW50aWMtcHJlZml4DQo+SHRtbGl6ZWQ6DQo+aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+RGlmZjoNCj5odHRwOi8vd3d3
LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgt
MDMNCj4NCj5BYnN0cmFjdDoNCj4gICBUaGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIGZyYW1ld29y
ayBtZXRob2QgdGhhdCBuZXR3b3JrIG9wZXJhdGlvbnMNCj4gICBtYXkgdXNlIHRoZWlyIGFkZHJl
c3Nlcy4gIE5ldHdvcmsgb3BlcmF0b3JzLCB3aG8gaGF2ZSBsYXJnZSBJUHY2DQo+ICAgYWRkcmVz
cyBzcGFjZSwgbWF5IGNob29zZSB0byBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYN
Cj4gICBhZGRyZXNzZXMgYnkgYXNzaWduaW5nIGFkZGl0aW9uYWwgc2lnbmlmaWNhbmNlIHRvIHNw
ZWNpZmljIGJpdHMNCj4gICB3aXRoaW4gdGhlIHByZWZpeC4gIEJ5IGVtYmVkZGVkIHNlbWFudGlj
cyBpbnRvIElQdjYgcHJlZml4ZXMsIHRoZQ0KPiAgIHNlbWFudGljcyBvZiBwYWNrZXRzIGNhbiBi
ZSBpbnNwZWN0ZWQgZWFzaWx5LiAgUm91dGVycyBhbmQgb3RoZXINCj4gICBpbnRlcm1lZGlhcnkg
ZGV2aWNlcyBjYW4gZWFzaWx5IGFwcGx5IHJlbGV2YW50IHBvbGljaWVzIGFzIHJlcXVpcmVkLg0K
PiAgIFBhY2tldC1sZXZlbCBkaWZmZXJlbnRpYXRpb24gY2FuIGFsc28gZW5hYmxlIGZsb3ctbGV2
ZWwgYW5kIHVzZXItDQo+ICAgbGV2ZWwgZGlmZmVyZW50aWF0aW9uLiAgQ29uc2VxdWVudGx5LCB0
aGUgbmV0d29yayBvcGVyYXRvcnMgY2FuDQo+ICAgYWNjb3JkaW5nbHkgdHJlYXQgbmV0d29yayBw
YWNrZXRzIGRpZmZlcmVudGx5IGFuZCBlZmZpY2llbnRseS4gIFRoZQ0KPiAgIG1hbmFnZW1lbnQg
YW5kIG1haW50ZW5hbmNlIG9mIG5ldHdvcmtzIGNhbiBiZSBtdWNoIHNpbXBsZXIuDQo+DQo+DQo+
DQo+DQo+VGhlIElFVEYgU2VjcmV0YXJpYXQNCg0K

From tjc@ecs.soton.ac.uk  Wed May 29 01:44:32 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C5B21F871C for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 01:44:32 -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=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vV4kgJXsTyOX for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 01:44:31 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 4369B21F8746 for <6man@ietf.org>; Wed, 29 May 2013 01:44:30 -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 r4T8iNUR003524; Wed, 29 May 2013 09:44:23 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4T8iNUR003524
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369817064; bh=ubBqQt/pWkXkBzFm5uF/KWdzM0M=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=4vdapK/Ngt6nCfqNEERmatpeLRe5CVHM5qORGN5ZBVrYRqIMrNe+M0y9eLVhEBHlE osEIxURUcY1skqRi69HsAu1l4I1WVaYsiH45AC7vW3RtA8HPCc0Tll+lMCVN8eFjGQ JQvqpHaxWbSG/zjiZVxwXs1Ya7TpNB3H+aQ7HsM0=
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 (valid=N/A) id p4S9iN0430603015Y8 ret-id none; Wed, 29 May 2013 09:44:24 +0100
Received: from dhcp-204-149.wireless.soton.ac.uk (dhcp-204-149.wireless.soton.ac.uk [152.78.204.149]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4T8iMvN028351 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 09:44:22 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <BE92F20E-0AE2-40D3-8637-16F9869869B6@cdt.org>
Date: Wed, 29 May 2013 09:44:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|2686e46729bbb33b1013a52fd5042fedp4S9iN03tjc|ecs.soton.ac.uk|682D447F-BE65-4FD5-95EB-8FE64D4E4F85@ecs.soton.ac.uk>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <51A207B0.4000900@si6networks.com> <BE92F20E-0AE2-40D3-8637-16F9869869B6@cdt.org> <682D447F-BE65-4FD5-95EB-8FE64D4E4F85@ecs.soton.ac.uk>
To: "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4S9iN043060301500; tid=p4S9iN0430603015Y8; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4T8iNUR003524
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "6man-chairs@tools.ietf.org Chairs" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 08:44:32 -0000

On 28 May 2013, at 22:07, Alissa Cooper <acooper@cdt.org> wrote:
>=20
> On May 26, 2013, at 9:01 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
>> How about including something along these lines (*) in an Appendix?
>>=20
>> (*) Discussion of possible attacks, and what stable privacy addresses =
do
>> about them (analyzing this for every possible address generation
>> mechanism would be out of scope for this I-D, IMO).
>=20
> Agreed. However, even with the appendix, there are still some places =
where the discussion of the threat models in section 1 could be clearer, =
IMO. For example:
>=20
>      However, even with temporary addresses [RFC4941] in place,
>      preventing correlation of activities of a node within a network
>      may be difficult (if at all possible) to achieve.  As a trivial
>      example, consider a scenario where there is a single node (or a
>      reduced number of nodes) connected to a specific network.  An
>      attacker could detect new addresses in use at that network, an
>      infer which addresses are being employed by which hosts.  This
>      task is made particularly easier by the fact that use of
>      "temporary addresses" can be easily inferred (since the follow
>      different patterns from that of traditional SLAAC addresses), and
>      since they are re-generated periodically (i.e., after a specific
>      amount of time has elapsed).
>=20
> My read of this is that you're talking about either (1) a situation =
where a node has a globally unique prefix, or (2) a situation where a =
small number of nodes share the same prefix and an attacker can =
disambiguate them using some other information about their behavior =
besides their IP addresses. Is that right? If that's the case, isn't =
correlation possible regardless of how the suffix is generated? The =
document seems to imply that nodes with temporary addresses are more =
susceptible to these two situations than nodes that use other address =
generation mechanisms, when in fact the first situation (globally unique =
prefix) probably affects all nodes equally regardless of generation =
mechanism, and in the second situation the fact that temporary addresses =
refresh frequently might erect a barrier that makes correlation more =
difficult and that would not exist with random or random-per-network =
addresses.

A static global prefix for IPv6 is not that dissimilar to a static IPv4 =
address with NAT for IPv4.  You can correlate the home, for example, not =
necessarily devices within it.

If devices rotate their 4941 address at fixed intervals, then you might =
be able to infer which devices are which from noting the number of =
addresses in use, and changes in addresses over time (e.g. old privacy =
address not seen for an outbound SYN, new address is seen).   in =
principle the use of "TEMP_PREFERRED_LIFETIME - REGEN_ADVANCE - =
DESYNC_FACTOR" for the refresh should provide some variation.  In =
practice, the implementations I've observed seem pretty regular.  More =
variation could be good in this respect.  But that's not the topic for =
this draft.

> Another point for clarification:
>=20
>   On the other hand, in scenarios in which "temporary addresses" are =
employed
>   together with stable addresses such as those based on IEEE
>   identifiers, implementation of the mechanism described in this
>   document would mitigate address-scanning attacks and also mitigate
>   some vectors for correlating host activities that are not mitigated
>   by the use of temporary addresses.
>=20
> Which correlation attack vectors do random-per-network addresses =
mitigate that temporary addresses do not? In the analysis in column (d) =
of the table, the correlation entries are the same for all of the =
address generation mechanisms in cases where the node intentionally uses =
temporary addresses.=20

If you use 4941 for outbound connections, and IEEE SLAAC default for =
inbound, then your IEEE based address is more readily guessable than had =
you used a stable privacy address.

The above is currently the default for most IPv6 devices; 4941 support =
is now very common, and usually on by default.

What is rarer (very rare?) is using 4941 addresses to initiate *and* =
receive new connections.  I think that's the type of case that =
draft-rafiee-6man-ra-privacy discusses/proposes.

Tim

>=20
> Thanks,
> Alissa
>=20
>>=20
>> Thanks!
>>=20
>> Best regards,
>> --=20
>> Fernando Gont
>> e-mail: fernando@gont.com.ar || fgont@si6networks.com
>> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From otroan@employees.org  Wed May 29 04:47:54 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E2621F9347 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 04:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.39
X-Spam-Level: 
X-Spam-Status: No, score=-10.39 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SkMtmj4ByTvD for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 04:47:48 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 04BA121F9318 for <ipv6@ietf.org>; Wed, 29 May 2013 04:47:47 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFALHqpVGQ/khR/2dsb2JhbABagwnCK4EKFnSCIwEBBAE6PwULCw44VwaIGga6S45iMweCc2EDqHuDETo
X-IronPort-AV: E=Sophos;i="4.87,763,1363132800"; d="scan'208";a="13822625"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 29 May 2013 11:47:21 +0000
Received: from dhcp-lys01-vla250-10-147-112-52.cisco.com (dhcp-lys01-vla250-10-147-112-52.cisco.com [10.147.112.52]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4TBlJiM003918 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 11:47:19 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com>
Date: Wed, 29 May 2013 13:47:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com>
To: Michael Sweet <msweet@apple.com>
X-Mailer: Apple Mail (2.1503)
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 11:47:54 -0000

Michael,

> It would be awesome if printers supported Neighbor Discovery, but of =
the four printers in my home office only three support IPv6 and only one =
supports ND.  One of the IPv6 printers is 3 years old, the other three =
are less than a year old...
>=20
> On the client side you'll find a similar story - sporadic support, and =
in many cases the ND information isn't wired into the resolver =
libraries, making it impossible to use a bare IPv6 link-local address =
without the zoneid added at the end...

confused. a host cannot support IPv6 if it doesn't support ND. could you =
please clarify?

cheers,
Ole=

From roland.bless@kit.edu  Wed May 29 05:46:31 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D22521F8681 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 05:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OCVMG3f6IQ7T for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 05:46:24 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id B61B621F86C3 for <ipv6@ietf.org>; Wed, 29 May 2013 05:46:23 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1UhflW-00026g-R4; Wed, 29 May 2013 14:46:13 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1UhflW-0001Os-K4; Wed, 29 May 2013 14:46:06 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 2D90BA800EE; Wed, 29 May 2013 14:46:06 +0200 (CEST)
Message-ID: <51A5F88E.9070405@kit.edu>
Date: Wed, 29 May 2013 14:46:06 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org>
In-Reply-To: <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1369831573.834552000
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 12:46:31 -0000

Hi Ole,

Am 29.05.2013 13:47, schrieb Ole Troan:

> confused. a host cannot support IPv6 if it doesn't support ND. could
> you please clarify?

I'm not sure that your statement is fully correct.
Though I'm convinced that ND provides many useful
features, in specific environments and rare cases
the use of ND may be problematic (due to security
or "performance" reasons).
The IPv6 spec luckily doesn't require that a node MUST
use ND. If you create static permanent Neighbor Cache
entries and switch off NUD, there is no need to perform
ND (sacrificing flexibility and some robustness).

Regards,
 Roland

From otroan@employees.org  Wed May 29 05:49:55 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C11921F870F for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 05:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.432
X-Spam-Level: 
X-Spam-Status: No, score=-10.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PxlEhpdU60Uv for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 05:49:49 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 5E12021F86F4 for <ipv6@ietf.org>; Wed, 29 May 2013 05:49:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFAPL3pVGQ/khM/2dsb2JhbABaDoJ7vlODWIEKFnSCIwEBBAF5EAtGVwaIGga6VY5iMweCc2EDqHuCUUA6
X-IronPort-AV: E=Sophos;i="4.87,764,1363132800"; d="scan'208";a="14294255"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 29 May 2013 12:49:46 +0000
Received: from dhcp-lys01-vla250-10-147-112-52.cisco.com (dhcp-lys01-vla250-10-147-112-52.cisco.com [10.147.112.52]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4TCnitP015915 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 12:49:44 GMT
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <51A5F88E.9070405@kit.edu>
Date: Wed, 29 May 2013 14:49:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF395D28-E337-4543-98E1-D6E6C1329DFD@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu>
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
X-Mailer: Apple Mail (2.1503)
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 12:49:55 -0000

>> confused. a host cannot support IPv6 if it doesn't support ND. could
>> you please clarify?
>=20
> I'm not sure that your statement is fully correct.
> Though I'm convinced that ND provides many useful
> features, in specific environments and rare cases
> the use of ND may be problematic (due to security
> or "performance" reasons).
> The IPv6 spec luckily doesn't require that a node MUST
> use ND. If you create static permanent Neighbor Cache
> entries and switch off NUD, there is no need to perform
> ND (sacrificing flexibility and some robustness).

I presume you are not suggesting that to install my new printer I need =
to:
 - manually pick and configure any addresses on the printer that isn't =
link-local
 - manually install a default route on the printer
 - configure the neighbor cache on the printer for _all_ directly =
connected hosts and routers
 - configure the neighbor cache on all the other hosts and routers.

in the department of splitting hairs, I think we're done here. ;-)

cheers,
Ole=

From brian@innovationslab.net  Wed May 29 06:00:59 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25A7521F8D94 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:00:47 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWp5j4cBYrzJ for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:00:26 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 42C8F21F8CE9 for <ipv6@ietf.org>; Wed, 29 May 2013 06:00:25 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id AFDB288148 for <ipv6@ietf.org>; Wed, 29 May 2013 06:00:25 -0700 (PDT)
Received: from clemson.local (nat-gwifi.jhuapl.edu [128.244.87.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 7940C13680BC for <ipv6@ietf.org>; Wed, 29 May 2013 06:00:25 -0700 (PDT)
Message-ID: <51A5FBE7.2040807@innovationslab.net>
Date: Wed, 29 May 2013 09:00:23 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu>
In-Reply-To: <51A5F88E.9070405@kit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 13:00:59 -0000

Hi Roland,
On 5/29/13 8:46 AM, Bless, Roland (TM) wrote:
> Hi Ole,
>
> Am 29.05.2013 13:47, schrieb Ole Troan:
>
>> confused. a host cannot support IPv6 if it doesn't support ND. could
>> you please clarify?
>
> I'm not sure that your statement is fully correct.
> Though I'm convinced that ND provides many useful
> features, in specific environments and rare cases
> the use of ND may be problematic (due to security
> or "performance" reasons).
> The IPv6 spec luckily doesn't require that a node MUST
> use ND. If you create static permanent Neighbor Cache
> entries and switch off NUD, there is no need to perform
> ND (sacrificing flexibility and some robustness).


I am not sure which IPv6 spec you are talking about.  The Node 
Requirements RFC, especially section 5.2, is the definitive guide to 
what is (and isn't) required...

https://tools.ietf.org/html/rfc6434#section-5.2

Regards,
Brian


From msweet@apple.com  Wed May 29 06:17:34 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 913A821F8E1C for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.567
X-Spam-Level: 
X-Spam-Status: No, score=-10.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SMTVn5jZA5nG for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:17:28 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5EE21F8D94 for <ipv6@ietf.org>; Wed, 29 May 2013 06:17:28 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay8.apple.com ([17.128.113.102]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK003MQA8SUAI0@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 06:17:28 -0700 (PDT)
X-AuditID: 11807166-b7faa6d000003acb-de-51a5ffe64048
Received: from [17.153.104.11] (Unknown_Domain [17.153.104.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay8.apple.com (Apple SCV relay) with SMTP id 8B.6E.15051.7EFF5A15; Wed, 29 May 2013 06:17:27 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <51A5A5B4.8040500@globis.net>
Date: Wed, 29 May 2013 09:17:26 -0400
Message-id: <8392F595-9740-4FD7-9C2D-E8363DC77FF3@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUiODODW/f5/6WBBlffW1s0fe5jtLj26D6L xcuz75ksjnyLtdhztd6B1WPryR9sHruO/mD3eHL2OpvHkiU/mTxad/xlD2CN4rJJSc3JLEst 0rdL4MpoWLqAuWCWYkXH18fsDYxnpLoYOTkkBEwkfv+5ywphi0lcuLeeDcQWEuhlkjjeFgZi CwuYS8x9/JkRxOYV0JO49u0rO4jNLKAjsXPrHbB6NgE1id+T+sDmcApoSbS96gGKc3CwCKhK 3LntCFFeLPF9yQ0mCFtbYtnC18wQI20kHsx8BTSeC2jtFFaJN1O/gc0XEVCUmP7vCxPEbbIS r5+/YZnAyD8LyRmzkJwxC8ncBYzMqxgFilJzEist9BILCnJS9ZLzczcxgkK1oTBtB2PTcqtD jAIcjEo8vCu+LwkUYk0sK67MPcQowcGsJMKbKrg0UIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv qQ1QSiA9sSQ1OzW1ILUIJsvEwSnVwGimbv1pvZqe6IW9NrPmRuTtdw9lnMw9RVb97zSed7a9 6gy6W9ZYVsV+ygtqEBXsb3x35Ubtrrv/CwymVzT5yG9s7rmx6qdgcvbVnc23PsTk/F18q2he 8Z434lovJIRfVHCxeO8x+iv8ouoNN1f2uf/LvVW5FnfEP0nYvybSkK1JcwP33E+cR5RYijMS DbWYi4oTAevmCWZRAgAA
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 13:17:34 -0000

Ray,

On 2013-05-29, at 2:52 AM, Ray Hunter <v6ops@globis.net> wrote:
> ...
> Where's the standard that says ZoneID MUST be included in the Host
> header? I presume this is rfc2616#page-128.

RFC 2616 just says to use the host and port from the original URI.  It doesn't say anything about IPv6 link-local addresses and preceded RFC 3986's IPvFuture format. And section 3.2.2 just says that IP addresses SHOULD be avoided whenever possible with a reference to RFC 1900.

> And the value of "Host" is always set to the host portion of the
> original URI [which will currently include a ZoneID on current
> implementations]?

Correct.

> Do you think that 6874 mandates that the ZoneID MUST be stripped from
> the "Host" HTTP request header, as Host is sub-string of a URI?

Yes, from section 4 of RFC 6874:

   An HTTP client, proxy, or other intermediary MUST remove any ZoneID
   attached to an outgoing URI, as it has only local significance at the
   sending host.

Since the Host value is extracted from the outgoing URI, my assumption would be that this prohibition applies to the Host value as well, which should probably be spelled out in the future (perhaps with examples).

(this is text I plan on updating in my draft...)

>> ...
>> The server knows its own link-local addresses and doesn't need the zoneid information.
> I don't understand this logic. I'm presuming the outbound interface for
> replies is being selected by mirroring the inbound addresses of the
> request [quoting RFC6724: "In many cases, this is trivially dealt with
> by an application using the source address of a received packet as the
> response destination and the destination address of the received packet
> as the response source."]
> 
> However I thought one of the use cases was the printer sending
> unsolicited information such as "out of paper".

In the case of IPP, the connection is always initiated by the client, and the server only responds to requests sent by the client.  There is an asynchronous event notification extension for IPP (RFC 3995 combined with RFC 3996), but that is effectively a long-duration pull operation (the client sends a Get-Notifications request to the printer, and the printer will continue sending events in the same response as needed) and not a push operation back to the client.

> How would the server then select its correct local outbound interface,
> if it had multiple?
> Does the client supply a "callback address/port" that the printer
> stores/caches?

As indicated above, the printer never contacts the client, it is always the client contacting the printer.

>> For the use case under discussion, the client only knows its zoneid information because the user/administrator has supplied it along with the printer's link-local address.
> Right. That was going to be my next question.
> 
> How does the very first URI learn the correct ZoneID in the first place?
> Manually.

The manually-entered URI case is actually the edge case of an edge case, i.e., that 1-in-a-million user that just tries things to see if they will work...

The more typical case is where the client uses a discovery protocol that either does not support name-based resolution or makes it optional.  The specific protocols I personally have to deal with are WS-Discovery, UPNP, and (coming soon) Wi-Fi Direct Services.  The first two generally use IPv4, but for Wi-Fi Direct the preference will be IPv6.

Once a client discovers the printer they may only have an IPv6 link local address for it, and that's what gets put in the URI for the printer. Conceptually one could do some clever name mapping on the host ("mac-xxxxxxxxxxxx.something.") so that the URIs would not need to contain link-local addresses at all, but given that I can't expect every OS to adopt such a strategy I need to be able to target a printer using a URI containing an IPv6 link-local address, have it return resource URIs that the client can use, have a functional web interface, etc.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From msweet@apple.com  Wed May 29 06:24:34 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18DE21F8689 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.573
X-Spam-Level: 
X-Spam-Status: No, score=-10.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PSKJduToekFE for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 06:24:28 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id C8E2C21F8633 for <ipv6@ietf.org>; Wed, 29 May 2013 06:24:28 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK00FUDAKKWW50@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 06:24:28 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-d2-51a6018a4463
Received: from [17.153.104.11] (Unknown_Domain [17.153.104.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id 47.79.31158.B8106A15; Wed, 29 May 2013 06:24:28 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org>
Date: Wed, 29 May 2013 09:24:26 -0400
Message-id: <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUiODODW7eHcVmgwZOlghZNn/sYLa49us9i 8fLseyaLI99iLSa3rWCz2HO13oHNY+vJH2weu47+YPc4eOwjo8eTs9fZPJYs+cnk0brjL3sA WxSXTUpqTmZZapG+XQJXxpd3yxkLmngqXs3rYGlgPMPZxcjJISFgInF8zzJGCFtM4sK99Wwg tpBAL5PEz8USILawgLnE3MefwWp4BfQkrn37yg5iMwtoSdz495IJxGYTUJP4PamPtYuRg4NT wFGic3EVSJhFQFXiUudKoDAXUPkURonXa2ewQvRqSyxb+JoZYqaNxKNtk5hAioQEVrNKTLi5 EGyZiICKxPlp76COk5V4/fwNywRG/llI7piF5I5ZSOYuYGRexShQlJqTWGmql1hQkJOql5yf u4kRFMANhRE7GP8vszrEKMDBqMTDu+L7kkAh1sSy4srcQ4wSHMxKIrypgksDhXhTEiurUovy 44tKc1KLDzFKc7AoifMa2wClBNITS1KzU1MLUotgskwcnFINjL1LmFtfSM5Y3PXiUbGUj0DP 4pJp1SZP836/89qZwLOV7fL8FZ19Hsqx947fdC53fJPZ1iV+YvPaGuUgzjdTL3Q9WrXdqPl1 pZDDtler+nzDPaU3t083krByfPRqqgR/t9cV1R3Kp973dN+TTzx6f2PTw4cNAYvXfLhiOXVW y83Tby4uXHtP6J8SS3FGoqEWc1FxIgDAF9hTXAIAAA==
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 13:24:35 -0000

Ole,

On 2013-05-29, at 7:47 AM, Ole Troan <otroan@employees.org> wrote:
> Michael,
> 
>> It would be awesome if printers supported Neighbor Discovery, but of the four printers in my home office only three support IPv6 and only one supports ND.  One of the IPv6 printers is 3 years old, the other three are less than a year old...
>> 
>> On the client side you'll find a similar story - sporadic support, and in many cases the ND information isn't wired into the resolver libraries, making it impossible to use a bare IPv6 link-local address without the zoneid added at the end...
> 
> confused. a host cannot support IPv6 if it doesn't support ND. could you please clarify?


Well, when I looked at the ND table on my Mac ("ndp -aln") I daw one of my IPv6 printers but not the other two.  Yet I had used them all recently over IPv6, specifically to investigate whether ND might be a solution to the problem.

Moreover, running "ping6" with a link-local address but no zoneid fails, even for the printer that was listed...

Perhaps these are implementation issues in OS X, and I intend to continue testing on Linux and Windows and with some standalone ND tools, but thus far it doesn't look like ND will solve our particular problems, nor does it address how we might deal with embedded URIs in IPP responses and web pages without major changes...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From roland.bless@kit.edu  Wed May 29 07:56:16 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6389D21F8CA5 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 07:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UqtZ727NDQM for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 07:55:51 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1A44021F90CD for <ipv6@ietf.org>; Wed, 29 May 2013 07:55:45 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1UhhmY-0003pO-Aw; Wed, 29 May 2013 16:55:24 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1UhhmY-0000aH-4l; Wed, 29 May 2013 16:55:18 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id EDE39A800EE; Wed, 29 May 2013 16:55:17 +0200 (CEST)
Message-ID: <51A616D5.4070507@kit.edu>
Date: Wed, 29 May 2013 16:55:17 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu> <CF395D28-E337-4543-98E1-D6E6C1329DFD@employees.org>
In-Reply-To: <CF395D28-E337-4543-98E1-D6E6C1329DFD@employees.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1369839324.746560000
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 14:56:16 -0000

Hi Ole,

Am 29.05.2013 14:49, schrieb Ole Troan:
>>> confused. a host cannot support IPv6 if it doesn't support ND. could
>>> you please clarify?
>>
>> I'm not sure that your statement is fully correct.
>> Though I'm convinced that ND provides many useful
>> features, in specific environments and rare cases
>> the use of ND may be problematic (due to security
>> or "performance" reasons).
>> The IPv6 spec luckily doesn't require that a node MUST
>> use ND. If you create static permanent Neighbor Cache
>> entries and switch off NUD, there is no need to perform
>> ND (sacrificing flexibility and some robustness).
> 
> I presume you are not suggesting that to install my new printer I need to:
>  - manually pick and configure any addresses on the printer that isn't link-local
>  - manually install a default route on the printer
>  - configure the neighbor cache on the printer for _all_ directly connected hosts and routers
>  - configure the neighbor cache on all the other hosts and routers.

No, I'm obviously _not_ suggesting this
and you don't want this in ordinary environments.
But in theory, IPv6 works w/o ND, which was my point.
(e.g., consider using devices with unidirectional channels only).

> in the department of splitting hairs, I think we're done here. ;-)

Yep.

Regards,
 Roland


From roland.bless@kit.edu  Wed May 29 08:00:10 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA24221F91CB for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYo3BTiwjfhW for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:00:05 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id DA45021F8F0C for <ipv6@ietf.org>; Wed, 29 May 2013 08:00:04 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1Uhhr3-00043z-13; Wed, 29 May 2013 17:00:03 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1Uhhr2-00081g-Qq; Wed, 29 May 2013 16:59:56 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id A8B4AA800EE; Wed, 29 May 2013 16:59:56 +0200 (CEST)
Message-ID: <51A617EC.8030008@kit.edu>
Date: Wed, 29 May 2013 16:59:56 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu> <51A5FBE7.2040807@innovationslab.net>
In-Reply-To: <51A5FBE7.2040807@innovationslab.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1369839603.527357000
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 15:00:11 -0000

Hi Brian,

Am 29.05.2013 15:00, schrieb Brian Haberman:
> On 5/29/13 8:46 AM, Bless, Roland (TM) wrote:
>> I'm not sure that your statement is fully correct.
>> Though I'm convinced that ND provides many useful
>> features, in specific environments and rare cases
>> the use of ND may be problematic (due to security
>> or "performance" reasons).
>> The IPv6 spec luckily doesn't require that a node MUST
>> use ND. If you create static permanent Neighbor Cache
>> entries and switch off NUD, there is no need to perform
>> ND (sacrificing flexibility and some robustness).
> 
> 
> I am not sure which IPv6 spec you are talking about.  The Node
> Requirements RFC, especially section 5.2, is the definitive guide to
> what is (and isn't) required...
> 
> https://tools.ietf.org/html/rfc6434#section-5.2

I was referring to RFC 2460. RFC 6434 states
ND SHOULD be supported, which makes perfectly sense.
In very rare cases you may not be able to use ND
(e.g., if you have a unidirectional medium etc.).

Regards,
 Roland


From brian@innovationslab.net  Wed May 29 08:01:36 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA28021F888F for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:01:36 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuTFPig94rAm for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:01:31 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id DA29221F8900 for <ipv6@ietf.org>; Wed, 29 May 2013 08:01:31 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id ACD1188132; Wed, 29 May 2013 08:01:31 -0700 (PDT)
Received: from clemson.local (nat-gwifi.jhuapl.edu [128.244.87.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 5E30E136807A; Wed, 29 May 2013 08:01:31 -0700 (PDT)
Message-ID: <51A61849.9060109@innovationslab.net>
Date: Wed, 29 May 2013 11:01:29 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu> <51A5FBE7.2040807@innovationslab.net> <51A617EC.8030008@kit.edu>
In-Reply-To: <51A617EC.8030008@kit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 15:01:37 -0000

On 5/29/13 10:59 AM, Bless, Roland (TM) wrote:
> Hi Brian,
>
> Am 29.05.2013 15:00, schrieb Brian Haberman:
>> On 5/29/13 8:46 AM, Bless, Roland (TM) wrote:
>>> I'm not sure that your statement is fully correct.
>>> Though I'm convinced that ND provides many useful
>>> features, in specific environments and rare cases
>>> the use of ND may be problematic (due to security
>>> or "performance" reasons).
>>> The IPv6 spec luckily doesn't require that a node MUST
>>> use ND. If you create static permanent Neighbor Cache
>>> entries and switch off NUD, there is no need to perform
>>> ND (sacrificing flexibility and some robustness).
>>
>>
>> I am not sure which IPv6 spec you are talking about.  The Node
>> Requirements RFC, especially section 5.2, is the definitive guide to
>> what is (and isn't) required...
>>
>> https://tools.ietf.org/html/rfc6434#section-5.2
>
> I was referring to RFC 2460. RFC 6434 states
> ND SHOULD be supported, which makes perfectly sense.
> In very rare cases you may not be able to use ND
> (e.g., if you have a unidirectional medium etc.).

But there are MUSTs sprinkled in that section as well...

Regards,
Brian


From roland.bless@kit.edu  Wed May 29 08:21:40 2013
Return-Path: <roland.bless@kit.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8AE821F93F8 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sOlhpBJYelgz for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 08:21:33 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id B1B7121F8E9D for <ipv6@ietf.org>; Wed, 29 May 2013 08:21:29 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1UhiBm-00069r-8x; Wed, 29 May 2013 17:21:28 +0200
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1UhiBm-0004rN-1u; Wed, 29 May 2013 17:21:22 +0200
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id DF120A800EE; Wed, 29 May 2013 17:21:21 +0200 (CEST)
Message-ID: <51A61CF1.8030309@kit.edu>
Date: Wed, 29 May 2013 17:21:21 +0200
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <51A5F88E.9070405@kit.edu> <51A5FBE7.2040807@innovationslab.net> <51A617EC.8030008@kit.edu> <51A61849.9060109@innovationslab.net>
In-Reply-To: <51A61849.9060109@innovationslab.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1369840888.604792000
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 15:21:40 -0000

Hi Brian,

>> I was referring to RFC 2460. RFC 6434 states
>> ND SHOULD be supported, which makes perfectly sense.
>> In very rare cases you may not be able to use ND
>> (e.g., if you have a unidirectional medium etc.).
> 
> But there are MUSTs sprinkled in that section as well...

The way I read it was:
"Neighbor Discovery SHOULD be supported."
...
"Some detailed analysis of Neighbor Discovery follows:"
....MUST....MUST...MUST... and so on
[i.e., in case you support ND then you MUST support the following
features of ND...]

Furthermore, I guess that "support" != "use", i.e., it's
also ok if my host supports ND, but if I'm not using
it for some exceptions that's ok, too.

Regards,
 Roland


From mcr@sandelman.ca  Wed May 29 09:59:12 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CA721F96D5 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 09:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.232
X-Spam-Level: 
X-Spam-Status: No, score=-1.232 tagged_above=-999 required=5 tests=[AWL=1.233,  BAYES_00=-2.599, HTTP_ESCAPED_HOST=0.134]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iV4JBcbRH-r0 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 09:59:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 440D921F96CD for <ipv6@ietf.org>; Wed, 29 May 2013 09:59:07 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id EFDA92017A; Wed, 29 May 2013 13:11:36 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B89EF63A8C; Wed, 29 May 2013 12:58:18 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A665D63A88; Wed, 29 May 2013 12:58:18 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <51A506BD.9060804@globis.net>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 May 2013 12:58:18 -0400
Message-ID: <21129.1369846698@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Ray Hunter <v6ops@globis.net>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 16:59:12 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Ray" =3D=3D Ray Hunter <v6ops@globis.net> writes:
    Ray> Warning: post contains dumb questions.

good.  That usually mean that the document says something dumb.

    >>> Michael raised an interesting issue, and we have to analyze
    >>> it. The consensus of the working group so far is that interface
    >>> identifiers are private to the host, that any leakage outside
    >>> the host should be prevented, and that a way to prevent that
    >>> leakage is to ask proxies to erase them whenever they have an
    >>> opportunity. Michael points that some servers take an opposite

I have a stupid question.
What does it mean to have an interface identifier go through an HTTP proxy?

Given that a proxy works by having the client send the entire URL on the
GET line, it means that my web browser would send something like:

   GET http://[fe80::a%25en1]/printers/laserwrite
   Host: [fe80::a%25en1]

to the proxy.  Now, where is %en1 going to be interpreted?
On the proxy?  How can the client have any idea what to send.
It can't mean anything on the client, because the entire URL
goes to the proxy.

Okay, so may this is a "transparent" proxy. (I.e. something that
violates end to end!)   That means that the host made a request to
fe80::a on interface en1, and it turned out that to get there, some
device intercepted packets which were not supposed to leave the local
link, and well, I guess did something else to the data.

My take is that in this situation this device is doing something outside
of our entire architecture, and therefore that device is really the end
point, and it had better rewrite URLs appropriately.

    >> Some background: HTTP and IPP services in printers include
    >> absolute URIs in the content they return. For IPP this can be
    >> http/https URLs to the printer's web page, ICC profiles, and
    >> other resources, along with the ipp/ipps URIs that the printer
    >> supports. For HTTP the most common are https URLs for "secure"
    >> areas of the printer's web interface.  Because a printer is often
    >> known by multiple names and addresses ("printer.local.",
    >> "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the

We have an existing problem in CUPS at least, that the certificates
generated for the https do not have all the valid names, nor can they.

    >> All of this falls apart with link-local addresses and RFC 6874.
    >> Because the client is required to remove the zoneid from the
    >> outgoing request, the URIs it gets back from the server are no
    >> longer "reachable".=20

I think that part of the bug is the return of absolute URLs.  I question
whether that is truly necessary.. Why aren't relative URLs (rooted at /)
useable?

    Ray> If the other party learns nothing, and the originating node just n=
eeds
    Ray> to hear an echo of it's own information for it's own use, what's w=
rong
    Ray> with using a cookie (server originated), or a hidden variable (cli=
ent
    Ray> originated), to transport this interface information along with the
    Ray> request/reply?

That's new behaviour at a high-level.
Even so, I don't know how that could be done without some javascript or
something to do translation, which completely runs afoul of RESTful
interfaces, I think.

    Ray> What if both the server AND the client have multiple interfaces: h=
ow do
    Ray> they both know which local interface on their own node is mutually
    Ray> connected and to be used for communication? There's only one single
    Ray> zoneid in the URI, so presumably one of the nodes is lacking some
    Ray> information.

The server never needs to specify it's link local address.

    >> What I propose is that we change the wording to allow the zoneid
    >> in the Host header but not in the Request-URI.  HTTP proxies
    >> would be required to strip any zoneid information in the Host
    >> header.  HTTP servers would be required to ignore any zoneid
    >> information for purposes of address validation but include it for
    >> any absolute URIs to the server they generate.=20

This seems nonsensical to me.
If the zoneid is not in the Request-URI, then how can the proxy do
anything with it?  What address is in the Host: header that has a
meaningful zoneid?

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

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

iQCVAwUAUaYzqoqHRg3pndX9AQJjvQQAvbEntS1LzfoHBKGkoZXrrhC9CUxwsPDo
ViA5/CMWuX1LsaJ/krUQfLsKxpC1SnQAE/t8pXiAWPjEN8EzZsPQf9XijGymemKW
p/y9cwyGIApYMMUtD1sv27PJcM3Mcn0eW3H56qp5pukyaHZpLH8QTyQAW6w5DNbF
0Wukz/OI7R4=
=GihX
-----END PGP SIGNATURE-----
--=-=-=--

From fgont@si6networks.com  Wed May 29 10:08:51 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0955D21F9734 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 10:08:51 -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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjJrqKwb-I5h for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 10:08:49 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0066321F9706 for <6man@ietf.org>; Wed, 29 May 2013 10:08:48 -0700 (PDT)
Received: from 87-205-5-39.ip.netia.com.pl ([87.205.5.39] helo=[192.168.1.58]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UhjrW-00086m-SL; Wed, 29 May 2013 19:08:35 +0200
Message-ID: <51A635B5.2060308@si6networks.com>
Date: Wed, 29 May 2013 19:07:01 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <931aed1a25284492822421a82364d560@BY2PR03MB269.namprd03.prod.outlook.com> <b1564eeb912c456fa2739f466bd7c4c4@BY2PR03MB269.namprd03.prod.outlook.com> <51A1A7FE.9010501@si6networks.com> <6f1339e1ed4e440e8d560a1183ac178b@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <6f1339e1ed4e440e8d560a1183ac178b@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 17:08:51 -0000

On 05/29/2013 04:00 AM, Dave Thaler wrote:
>>
>> What does draft-ietf-6man-stable-privacy-addresses has to do with CGAs?
> 
> 1) Both give "random-per-network" addresses, using Alissa's terminology.

CGA's doesn't seem to aim at stable-per-network addresses. For instance,
the modifier is expected to be random.



> 2) Both generate an IP address using a secret + a network prefix + a DAD counter + other information.

But both have completely different goals. CGAs have the goal of encoding
a public key, whereas stable-privacy has the goal of producing
meaningles random bits.



> So it comes down to what was claimed, which I don't know offhand.
> 
>> Has MS or Ericsson patented the use of PRFs?
> 
> Pseudorandom functions themselves are well known.  Some folks (don't know) might
> have patented using PRFs in novel ways to do specific things.

What I did was to apply Bellovin's RFC1948. So any IPR claim on
draft-ietf-6man-stable-addresses that predates RFC1948 and that's is not
Bellovin's is claiming credit for somebody else's work.

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





From mcr@sandelman.ca  Wed May 29 10:10:37 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0AFC21F970B for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 10:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.684,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hqm0AcBEvo3E for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 10:10:32 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 6485221F9742 for <ipv6@ietf.org>; Wed, 29 May 2013 10:10:32 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7EF5F2017A; Wed, 29 May 2013 13:23:03 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 43B4D63A8C; Wed, 29 May 2013 13:09:15 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3322263A88; Wed, 29 May 2013 13:09:15 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ray Hunter <v6ops@globis.net>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <51A5A5B4.8040500@globis.net>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 May 2013 13:09:15 -0400
Message-ID: <23153.1369847355@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Christian Huitema <huitema@microsoft.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 17:10:37 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Ray" =3D=3D Ray Hunter <v6ops@globis.net> writes:
    >>> What if both the server AND the client have multiple interfaces: ho=
w do
    >>> they both know which local interface on their own node is mutually
    >>> connected and to be used for communication? There's only one single
    >>> zoneid in the URI, so presumably one of the nodes is lacking some
    >>> information.

    >> The server knows its own link-local addresses and doesn't need
    >> the zoneid information.=20

    Ray> I don't understand this logic. I'm presuming the outbound interfac=
e for
    Ray> replies is being selected by mirroring the inbound addresses of the
    Ray> request [quoting RFC6724: "In many cases, this is trivially
    Ray> dealt with

yeah, that's just TCP.

    Ray> However I thought one of the use cases was the printer sending
    Ray> unsolicited information such as "out of paper".

I don't know how this works in an unsolicited way.
I thought that with the ways we have tried to standardize (IPP, XMPP,
SIP, forgive me... I don't know which won) the client pretty much always
has to subscribe, or it's a broadcast/multicast.

    >> For the use case under discussion, the client only knows its
    >> zoneid information because the user/administrator has supplied it
    >> along with the printer's link-local address.=20
    Ray> Right. That was going to be my next question.

    Ray> How does the very first URI learn the correct ZoneID in the first =
place?
    Ray> Manually.

In a Bonjour/mDNS scenario, the client sees the link-local address on inter=
face
with zoneID FOO, and records that.  The client learns it's correct ZoneID.
(At no point does it matter what the server's zoneid for the interface
is)

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09


--=-=-=
Content-Type: application/pgp-signature

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

iQCVAwUAUaY2O4qHRg3pndX9AQK1GQP+InSQ3homWMsUagHRV6gvPcHJByMUrGJ7
H3AqJLE+OJOCSyKlZWqaYL2V56M4FA9oqqgUfVtf0TwXp+FKdF4z+nQ7rsOlcW83
VRycRnzxCRVDb4qNhClDynmyzqXpLxi+6pfMiS5JmHJpAhYgtipgL1AWYmsy0Vvd
aASH4/MnEzw=
=dIHP
-----END PGP SIGNATURE-----
--=-=-=--

From msweet@apple.com  Wed May 29 11:01:42 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F52421F87FB for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 11:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.509
X-Spam-Level: 
X-Spam-Status: No, score=-10.509 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, HTTP_ESCAPED_HOST=0.134, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1NRDIaZtb8d for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 11:01:10 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 73A9221F871D for <ipv6@ietf.org>; Wed, 29 May 2013 11:00:02 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay5.apple.com ([17.128.113.88]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK00D86N9RX881@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 10:58:45 -0700 (PDT)
X-AuditID: 11807158-b7f486d0000079b6-4a-51a641d344a4
Received: from [17.153.104.11] (Unknown_Domain [17.153.104.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay5.apple.com (Apple SCV relay) with SMTP id 95.99.31158.4D146A15; Wed, 29 May 2013 10:58:45 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <21129.1369846698@sandelman.ca>
Date: Wed, 29 May 2013 13:58:43 -0400
Message-id: <BA264742-10DB-4BED-A6F2-4EC57789DCD4@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <21129.1369846698@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCLMWRmVeSWpSXmKPExsUiODODW/eq47JAg57FPBYvz75nsug51M9u ceRbrMWeq/UOLB5bT/5g83hy9jqbx5IlP5k8WubsYQ5gieKySUnNySxLLdK3S+DKWHPwHHNB m1TF1hfTmBoYz4h0MXJySAiYSLxbsZAJwhaTuHBvPVsXIxeHkEAvk8TnL6tZQRLCAuYScx9/ ZgSxeQX0JK59+8oOYjMLaEnc+PcSrJlNQE3i96Q+oHoODk4BHYkbV+1BwiwCqhI9d/+zg4SZ BVwk1s1PgujUlli28DUzxEQbiS+7+9kh1j5lkdh9tAdspAjQquVHnjFC3CYr8fr5G5YJjPyz kFwxC8kVs5DMXcDIvIpRoCg1J7HSVC+xoCAnVS85P3cTIygsGwojdjD+X2Z1iFGAg1GJh3eD 1rJAIdbEsuLK3EOMEhzMSiK8a7SBQrwpiZVVqUX58UWlOanFhxilOViUxHmNbZYGCgmkJ5ak ZqemFqQWwWSZODilGhiNPy5fuux7xIl57tqe6zT7Z6wrvGyzQcar0vTg/6bPpi+nMH4yljgT HvlHrcvv1rdPR9iW3fb2VnicJ7vohPg7+fbaa3vvX1D7mPGs7RdL/8vKyXfaf+86cXW11M8F 7lofPTOVyl/UvdL+KHNYJ0fmxbkmTwXpWTPfTn/SozF1etuLxwbTZB9YKLEUZyQaajEXFScC AGM/CMpHAgAA
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 18:01:43 -0000

Michael,

On 2013-05-29, at 12:58 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> ...
> I have a stupid question.
> What does it mean to have an interface identifier go through an HTTP proxy?
> 
> Given that a proxy works by having the client send the entire URL on the
> GET line, it means that my web browser would send something like:
> 
>   GET http://[fe80::a%25en1]/printers/laserwrite
>   Host: [fe80::a%25en1]
> 
> to the proxy.  Now, where is %en1 going to be interpreted?
> On the proxy?  How can the client have any idea what to send.
> It can't mean anything on the client, because the entire URL
> goes to the proxy.

You might be able to stretch things to allow a proxy for a locally-discovered device like a printer, e.g,, some sort of security policy at an organization.  But in that case while the proxy might forward the link-local URI as-is, it would also need to ignore the zoneid  and use ND or an "all interfaces" approach to forward the request to the device.

> ...
> We have an existing problem in CUPS at least, that the certificates
> generated for the https do not have all the valid names, nor can they.

Well, there *are* multi-domain certificates, but most people stick with self-signed or organization-signed certs.  Longer term I want to add full SNI support - this mostly works for OS X already (we'll search for a matching cert in the system keychain) but needs more work on Linux.
 
>>> All of this falls apart with link-local addresses and RFC 6874.
>>> Because the client is required to remove the zoneid from the
>>> outgoing request, the URIs it gets back from the server are no
>>> longer "reachable". 
> 
> I think that part of the bug is the return of absolute URLs.  I question
> whether that is truly necessary.. Why aren't relative URLs (rooted at /)
> useable?

Because we have four URI schemes/protocols - http, https, ipp, and ipps - and multiple port numbers to deal with for printers.  And right now there is no way to do a relative URI that just changes the scheme and/or port.

> ...
>>> What I propose is that we change the wording to allow the zoneid
>>> in the Host header but not in the Request-URI.  HTTP proxies
>>> would be required to strip any zoneid information in the Host
>>> header.  HTTP servers would be required to ignore any zoneid
>>> information for purposes of address validation but include it for
>>> any absolute URIs to the server they generate. 
> 
> This seems nonsensical to me.
> If the zoneid is not in the Request-URI, then how can the proxy do
> anything with it?  What address is in the Host: header that has a
> meaningful zoneid?


The reason for having proxies strip the zoneid is because the zoneid is only useful to the client - not to the proxy and not to the server.  But I wasn't really considering the use of a proxy for local network access (above).

The Host header contains the client's zoneid information and gets used in any URIs returned by the server (so that the client is able to access the server via those URIs without having to figure out what zoneid to use...)

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From msweet@apple.com  Wed May 29 11:13:17 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F03021F9675 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 11:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.571
X-Spam-Level: 
X-Spam-Status: No, score=-10.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSl7JD+WCXvH for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 11:13:10 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id B7ACA21F9509 for <ipv6@ietf.org>; Wed, 29 May 2013 11:13:10 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay4.apple.com ([17.128.113.87]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK002H8NT4N2O0@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 11:13:10 -0700 (PDT)
X-AuditID: 11807157-b7f706d0000006c6-d9-51a64534caf0
Received: from [17.153.104.11] (Unknown_Domain [17.153.104.11]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay4.apple.com (Apple SCV relay) with SMTP id 95.E0.01734.53546A15; Wed, 29 May 2013 11:13:10 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <23153.1369847355@sandelman.ca>
Date: Wed, 29 May 2013 14:13:08 -0400
Message-id: <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net> <23153.1369847355@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUiODODW9fMdVmgwfRtbBZNn/sYLa49us9i 8fLseyaLnkP97BZHvsVa7Lla78DmsfXkDzaPXUd/sHs8OXudzWPJkp9MHq07/rJ7tMzZwxzA FsVlk5Kak1mWWqRvl8CVMbn7MmPBBfaKf9NesTcw9rB1MXJySAiYSGycOpcZwhaTuHBvPVCc i0NIoJdJYtL6A2AJYQFzibmPPzOC2LwCehLXvn1lB7GZBbQkbvx7yQRiswmoSfye1McKYnMK 6EhcmrsSrIZFQFVi7ZeFTCBDmQWmMEq8XjuDFaJZW2LZwtfMEENtJG5f2cAIsXkLq8SWI/PA tokAbVt+5BkjxHmyEq+fv2GZwMg/C8khs5AcMgvJ3AWMzKsYBYpScxIrTfQSCwpyUvWS83M3 MYKCuKEwfAfjv2VWhxgFOBiVeHg3aC0LFGJNLCuuzD3EKMHBrCTCu0YbKMSbklhZlVqUH19U mpNafIhRmoNFSZzXyGZpoJBAemJJanZqakFqEUyWiYNTqoHxnlupXOn5iC5Lt4MhEtWBsecf Pcze++LwGS6rCc3NRQ9cb/7Szz5eP7sx7S7Lj2yFr9M9ZdXtJZpuch1luK7BrnPTWLKiZ0/j J74Kdf720mtumXI7L355OMPl9OIfx06lLLr+0nHvqurQB7ZaPV0vPq+a2TIhT+nClI3z3t36 MTF0quLuvTpBSizFGYmGWsxFxYkA+Doms14CAAA=
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 18:13:17 -0000

Michael,

On 2013-05-29, at 1:09 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> ...
>   Ray> How does the very first URI learn the correct ZoneID in the first place?
>    Ray> Manually.
> 
> In a Bonjour/mDNS scenario, the client sees the link-local address on interface
> with zoneID FOO, and records that.  The client learns it's correct ZoneID.
> (At no point does it matter what the server's zoneid for the interface
> is)


One important point here: we don't send IPv6 link local addresses in this case, we send the .local hostname that the printer is using.  This avoids the whole issue of IPv6 link-local addresses in URIs, we just have to deal with changing printer hostnames (due to name collisions) and the normal issues of changing networks on the client - home Wi-Fi vs. work network, etc.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From v6ops@globis.net  Wed May 29 12:10:35 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD1E21F8CEC for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 12:10:35 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mKw9qzgqyqA for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 12:10:34 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6B89721F9769 for <ipv6@ietf.org>; Wed, 29 May 2013 12:10:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id D33358700DB; Wed, 29 May 2013 21:10:11 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKETNbIhwEa8; Wed, 29 May 2013 21:10:11 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id A793A8700AE; Wed, 29 May 2013 21:10:11 +0200 (CEST)
Message-ID: <51A6528D.2030304@globis.net>
Date: Wed, 29 May 2013 21:10:05 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Michael Sweet <msweet@apple.com>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net> <23153.1369847355@sandelman.ca> <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com>
In-Reply-To: <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 19:10:35 -0000

> Michael Sweet <mailto:msweet@apple.com>
> 29 May 2013 20:13
> Michael,
>
>
> One important point here: we don't send IPv6 link local addresses in
> this case, we send the .local hostname that the printer is using. This
> avoids the whole issue of IPv6 link-local addresses in URIs, we just
> have to deal with changing printer hostnames (due to name collisions)
> and the normal issues of changing networks on the client - home Wi-Fi
> vs. work network, etc.
>
.local is also strongly scoped to a link. So how does a using a .local
name help compared to using an IPv6 link local literal in a URI?

In the case of receiving a .local URI, don't you then have to run name
resolution using mDNS on all possible interfaces to work out which
outgoing interface to use?

Point being that if a client can learn the outgoing interface because of
an incoming service advertisement from the printer, or failing that you
run multicast name discovery on all interfaces to discover which one has
the printer connected to it, why then in the case of an IPv6 literal
link local can't the client first look at the local Neighbor Discovery
cache for the literal IPv6 link local of the server to discover the
outgoing interface, or if that is absent attempt connecting to port 80
via all interfaces and cache which one works (attempting to use fixed
links before wireless before 3gpp)?

Thanks,
RayH


From otroan@employees.org  Wed May 29 12:40:22 2013
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210DE21F9821 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 12:40:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id keoaWxaGHDN3 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 12:40:21 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) by ietfa.amsl.com (Postfix) with ESMTP id A391C21F9820 for <ipv6@ietf.org>; Wed, 29 May 2013 12:40:21 -0700 (PDT)
Received: from dhcp-10-61-110-248.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id A052F5EB6; Wed, 29 May 2013 12:40:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Ole Troan <otroan@employees.org>
In-Reply-To: <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com>
Date: Wed, 29 May 2013 21:40:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com>
To: Michael Sweet <msweet@apple.com>
X-Mailer: Apple Mail (2.1503)
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 19:40:22 -0000

Michael,

let me try a restart.

you need to use link-local addresses for the HTTP connection between a =
client and a printer.

a link-local address has link-local scope. it is ambiguous outside of =
the given link (zone).
see RFC4007.

an application using link-local addresses must be bound to the interface =
in the chosen link-local zone.

now the question becomes, what do you do with the embedded URIs =
containing link-local addresses?
the referral clearly has no value outside of the given link-local zone.

could you not infer the link-local zone of the referral from the =
transport session?
given a link-local transport connection using a link-local zone, would =
it ever make
sense that the referrals using link-locals would belong to a different =
zone?

if not, then the client can just ensure to use the same zone for =
referrals that it does the transport
it received the HTML over.

cheers,
Ole


From msweet@apple.com  Wed May 29 13:16:35 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E445E21F8F2C for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:16:34 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23X0dIHY6OQu for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:16:27 -0700 (PDT)
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) by ietfa.amsl.com (Postfix) with ESMTP id 4AACD21F8459 for <ipv6@ietf.org>; Wed, 29 May 2013 13:16:27 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay3.apple.com ([17.128.113.83]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK00210TN0N211@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 13:16:27 -0700 (PDT)
X-AuditID: 11807153-b7f3c6d000007b32-85-51a66217ee7c
Received: from [17.153.24.240] (Unknown_Domain [17.153.24.240]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay3.apple.com (Apple SCV relay) with SMTP id 25.17.31538.81266A15; Wed, 29 May 2013 13:16:26 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <51A6528D.2030304@globis.net>
Date: Wed, 29 May 2013 16:16:22 -0400
Message-id: <164F0C33-5F6C-46EC-A598-70CFAD16072F@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net> <23153.1369847355@sandelman.ca> <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com> <51A6528D.2030304@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1758)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUiOFPig65U0rJAg++TLCyaPvcxWlx7dJ/F 4uXZ90wWPYf62S2OfIu12HO13oHNY+vJH2weu47+YPd4cvY6m8eSJT+ZPFp3/GX3aJmzhzmA LYrLJiU1J7MstUjfLoErY8fXkIJ30hWz3q9mamBcKdbFyMkhIWAisXnlSVYIW0ziwr31bF2M XBxCAr1MEj1X+sASwgLmEnMff2YEsXkF9CTOrmhlAbGZBXQkdm69wwZiswmoSfyeBFLPwcEp oCWx/XQdSJhFQFVi082rTCAzmQXmMkosmHmJCaJXW2LZwtfMEDNtJJ6vessMsbiZTWLptAaw xSICihLT/31hgrhOVqLl6Wz2CYz8s5DcMQvJHbOQzF3AyLyKUaAoNSex0lgvsaAgJ1UvOT93 EyMogBsKg3cw/llmdYhRgINRiYd3o9ayQCHWxLLiytxDjBIczEoivGu0gUK8KYmVValF+fFF pTmpxYcYpTlYlMR5jWyWBgoJpCeWpGanphakFsFkmTg4pRoY59WZcV/QjRGLVRfblyxXfj7C IrF08rRDW07J9cZ+t0uonHnLeE+R9dn1Pc98oq4sXRq4Ozj4v/uJpF1qDz4fzDVSfJFSblK2 S+Pg/Hm3JEMLJ7htvXqv9iVbSPqWLCuBpkDD36sF2wUitKsz+18ffcpxMqty0+K++PumM5v3 cv/MLdocUBOixFKckWioxVxUnAgAfFpzSFwCAAA=
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 20:16:35 -0000

Ray,

On May 29, 2013, at 3:10 PM, Ray Hunter <v6ops@globis.net> wrote:
>> Michael Sweet <mailto:msweet@apple.com>
>> 29 May 2013 20:13
>> Michael,
>> 
>> 
>> One important point here: we don't send IPv6 link local addresses in
>> this case, we send the .local hostname that the printer is using. This
>> avoids the whole issue of IPv6 link-local addresses in URIs, we just
>> have to deal with changing printer hostnames (due to name collisions)
>> and the normal issues of changing networks on the client - home Wi-Fi
>> vs. work network, etc.
>> 
> .local is also strongly scoped to a link. So how does a using a .local
> name help compared to using an IPv6 link local literal in a URI?

For one, it doesn't have an RFC telling implementers to not put the .local name in the Host: header or in URIs... :)

But in all seriousness, clients are able to lookup the .local name using mDNS (through the system networking libraries), which gives them the proper IPv6 link-local address complete with the zoneid.  The same is not generally true of IPv6 link-local addresses - there is no standard network API for getting the interface name/zoneid for a given link-local address, and things like getaddrinfo will not accept an IPv6 link-local address without its zoneid.

> In the case of receiving a .local URI, don't you then have to run name
> resolution using mDNS on all possible interfaces to work out which
> outgoing interface to use?

Absolutely, but that resolution is provided through a stable, well-known interface that is also used for looking up regular DNS names.  An application doesn't need to know about the details of the lookup, it just does the host name lookup and the right things happen.

> Point being that if a client can learn the outgoing interface because of
> an incoming service advertisement from the printer, or failing that you
> run multicast name discovery on all interfaces to discover which one has
> the printer connected to it, why then in the case of an IPv6 literal
> link local can't the client first look at the local Neighbor Discovery
> cache for the literal IPv6 link local of the server to discover the
> outgoing interface, or if that is absent attempt connecting to port 80
> via all interfaces and cache which one works (attempting to use fixed
> links before wireless before 3gpp)?


This approach makes the assumption that the printer supports ND and the OS allows applications to query the ND cache or provides a way to "resolve" (for lack of a better word) which interface should be used for a link-local address.  From my own testing, I'm not certain that all IPv6 printers support ND - only one of my three IPv6 printers shows up in my system's ND cache - and no OS does interface lookup (or enumeration) when given an IPv6 link-local address, you have to specify it.

I make no claim that my approach is perfect/ideal, merely that it works with current IPv6 implementations and has been deployed in CUPS and IPP printers since 2005 (just with the IPvFuture format).

If the consensus is to *not* include the zoneid in outgoing URIs, I'd still like to update RFC 6874 to provide some more examples, a history of what has been done before, and conformance requirements to ensure that everything needed to transparently support link-local addresses is in place.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From internet-drafts@ietf.org  Wed May 29 13:21:27 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFA6F21F96D4; Wed, 29 May 2013 13:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N6VM6FdF0EQ4; Wed, 29 May 2013 13:21:26 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 13DBE21F9696; Wed, 29 May 2013 13:21:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ext-transmit-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130529202108.28103.57187.idtracker@ietfa.amsl.com>
Date: Wed, 29 May 2013 13:21:08 -0700
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 20:21:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

	Title           : Transmission of IPv6 Extension Headers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ext-transmit-01.txt
	Pages           : 9
	Date            : 2013-05-29

Abstract:
   Various IPv6 extension headers have been standardised since the IPv6
   standard was first published.  This document updates RFC 2460 to
   clarify how intermediate nodes should deal with such extension
   headers and with any that are defined in future.  It also specifies
   how extension headers should be registered by IANA, with a
   corresponding minor update to RFC 2780.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ext-transmit-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-ext-transmit-01


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


From brian.e.carpenter@gmail.com  Wed May 29 13:29:34 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2351221F96CF for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:29:34 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDjxrr1LMcqB for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:29:29 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1FD21F958B for <ipv6@ietf.org>; Wed, 29 May 2013 13:29:29 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 6so8990110pdd.6 for <ipv6@ietf.org>; Wed, 29 May 2013 13:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=9/ZcXAyqrfHNJle5wBE6D7OwNvzIugz9XJXJJAqoJ8M=; b=cuLQ+ruciPDuPnJ4mNcCP6HSrhpSjsFAqjHR5UOT51SIZNqW/NFCzrZxvmLHQH9qfu rgVqnHBqhTLEVtjDlNbc5aR9gWLGHPXKape4ibeUY/9ODiBCGwVc826zoEUZH2Ch4dru GXbCtgKAwVGi6vBh2pvYF8P8jR8gLyf7aStpWJwgW/Xrzp3iqHxBkCquCkA33sShWYwC lkJWy+e9+u/DBuqhF5dmtQGiTTK56bRzfRiNgJKRbsVSJQ9S/eAKpjz0QpZMbfzNi1gM 6OwzulG+K9Iu5eko0Up1ezm8Bx/ZEIL3feMkqWobObzay2cWNRRr8f9vurAC+eZpEF0J x9fw==
X-Received: by 10.66.164.161 with SMTP id yr1mr5133793pab.77.1369859368979; Wed, 29 May 2013 13:29:28 -0700 (PDT)
Received: from [192.168.1.2] (51.191.252.27.dyn.cust.vf.net.nz. [27.252.191.51]) by mx.google.com with ESMTPSA id b7sm38540678pba.39.2013.05.29.13.29.25 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 13:29:27 -0700 (PDT)
Message-ID: <51A66527.2030408@gmail.com>
Date: Thu, 30 May 2013 08:29:27 +1200
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-ext-transmit-01.txt]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 20:29:34 -0000

Hi,

This version is intended to respond to Ray Hunter's comments.
There are two important changes:

1. The MUST NOT that Ray mentioned is now SHOULD NOT. Really
this is a matter of internal consistency in the document, since
the exceptions to the SHOULD NOT are specified, so the MUST NOT
was inappropriate.

2. It is now made explicit that only standards-track extension
headers are covered. That knocks out HIP, which is Experimental.

There are a few other changes of editorial nature.

   Brian + Sheng

-------- Original Message --------
Subject: I-D Action: draft-ietf-6man-ext-transmit-01.txt
Date: Wed, 29 May 2013 13:21:08 -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           : Transmission of IPv6 Extension Headers
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6man-ext-transmit-01.txt
	Pages           : 9
	Date            : 2013-05-29

Abstract:
   Various IPv6 extension headers have been standardised since the IPv6
   standard was first published.  This document updates RFC 2460 to
   clarify how intermediate nodes should deal with such extension
   headers and with any that are defined in future.  It also specifies
   how extension headers should be registered by IANA, with a
   corresponding minor update to RFC 2780.


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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ext-transmit-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ext-transmit-01


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

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


From msweet@apple.com  Wed May 29 13:47:49 2013
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E1C21F973A for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.576
X-Spam-Level: 
X-Spam-Status: No, score=-10.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SG+MLVLlq1bc for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 13:47:42 -0700 (PDT)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE0A21F9716 for <ipv6@ietf.org>; Wed, 29 May 2013 13:47:42 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay3.apple.com ([17.128.113.83]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MNK003O4V2PUA31@mail-out.apple.com> for ipv6@ietf.org; Wed, 29 May 2013 13:47:41 -0700 (PDT)
X-AuditID: 11807153-b7f3c6d000007b32-28-51a6696aeff7
Received: from [17.153.24.240] (Unknown_Domain [17.153.24.240]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate)	by relay3.apple.com (Apple SCV relay) with SMTP id 39.83.31538.B6966A15; Wed, 29 May 2013 13:47:41 -0700 (PDT)
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
Date: Wed, 29 May 2013 16:47:37 -0400
Message-id: <D80C2382-0994-4BD6-871A-AF3A2C717611@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com> <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1758)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJLMWRmVeSWpSXmKPExsUiOFPig25u5rJAg+cLFC2aPvcxWlx7dJ/F 4uXZ90wWR77FWkxuW8FmsedqvQObx9aTP9g8dh39we5x8NhHRo8nZ6+zeSxZ8pPJo3XHX/YA tigum5TUnMyy1CJ9uwSujAM/5rIVrOavuDTjNWsD43yeLkZODgkBE4n2Kx9ZIGwxiQv31rN1 MXJxCAn0MklsOt/LBpIQFjCXmPv4MyOIzSugJ3F2RStYA7OAlsSNfy+ZQGw2ATWJ35P6WEFs TgFHic8tZ8FqWARUJfrfvWUBGcosMIFR4tSkpWwQzdoSyxa+Zu5i5AAaaiPx5QRYvZDARDaJ s+0BILaIgIrE+WnvGCGOk5VoeTqbfQIj/ywkZ8xCcsYsJFMXMDKvYhQoSs1JrDTWSywoyEnV S87P3cQICuCGwuAdjH+WWR1iFOBgVOLh3ai1LFCINbGsuDL3EKMEB7OSCO8abaAQb0piZVVq UX58UWlOavEhRmkOFiVxXiObpYFCAumJJanZqakFqUUwWSYOTqkGRq2Vf1N4u9xcCs9zL5r+ 27xCatqc6Px4i9Y7ZS8cXr4xk7wjFRd2SXrT1vka/hd89Hck1ntfUGJt0It51Mqw4vce/mRe 61Mnje4GXFlrcCyTd0HpxKSCa5WZy58b9szpuXdektnmfUKHht3MsNerJ7O3ziu6coZRYwaz kM6pZuV4v0uhXSvjlFiKMxINtZiLihMBy/WPw1wCAAA=
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 20:47:49 -0000

Ole,

On May 29, 2013, at 3:40 PM, Ole Troan <otroan@employees.org> wrote:
> ...
> now the question becomes, what do you do with the embedded URIs containing link-local addresses?

For a web page, the user would click on links/buttons that open other pages on the printer.

For an IPP response, the client would fetch localization data, ICC profiles, etc. or open web pages in a browser (printer administration and supply pages).

> the referral clearly has no value outside of the given link-local zone.

Agreed.

> could you not infer the link-local zone of the referral from the transport session?
> given a link-local transport connection using a link-local zone, would it ever make
> sense that the referrals using link-locals would belong to a different zone?

No.

The issue is one of preserving that context, in every application or in every data store.  If the context (zoneid) is part of the URIs, then the URIs will continue to work as long as the two devices remain in the same link-local zone, without changes to the software.

If the context is not included in the URIs, then *every* client application has to be updated to add that context back to the URIs for every kind of content that might be returned. *Or* every operating system needs to be updated to support handling link-local addresses without a zoneid so that applications do not require changes.

> if not, then the client can just ensure to use the same zone for referrals that it does the transport it received the HTML over.


That implies adding extra code to every network application that wants to support link-local addressing, which is what I want to avoid (makes for a bad user experience when some things work and others do not because software hasn't been updated...)

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From brian.e.carpenter@gmail.com  Wed May 29 14:46:09 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 467B621F9779 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 14:46:09 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qrl7HMII4x+s for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 14:46:03 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id E511C21F9769 for <ipv6@ietf.org>; Wed, 29 May 2013 14:46:02 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id g10so9450657pdj.41 for <ipv6@ietf.org>; Wed, 29 May 2013 14:46:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hWV4+DQ3yEumAbG90KFoR9NcdoW5xLLBQFJXUHYIORw=; b=Kh94An3OPDBJ685htwN3WkdqojCEUHZQUV6Ybr2Is098UK+CjAkdbJEVhiDtISzZ6o PVonBaA5aeFDIUuNoSS7CzM/sa+fnP5txiPI/y5E67Z5mr6fiN/hXDsLLd+kqPWlkAy8 fb4RDe63wxMPMLS0OqWlbJe8lgwqJyfU5jPT5XHQyyIMiji0Jxl4U06duZoE9hH2S7BF Wc6F0U64i00+WoQ8ZglMvurTczIpZEmQKZlx5MasPEQvtLq8/htWBA961HJkPXR78b8K 1hS3Va2qSxdjbYx5eSfVLwi8qu+R6uDmB+P9y46jWLAg5LbyKb7CYhUfvQTn7s78u+qg cS5w==
X-Received: by 10.66.145.164 with SMTP id sv4mr5366370pab.46.1369863962677; Wed, 29 May 2013 14:46:02 -0700 (PDT)
Received: from [192.168.1.2] (51.191.252.27.dyn.cust.vf.net.nz. [27.252.191.51]) by mx.google.com with ESMTPSA id at1sm38791441pbc.10.2013.05.29.14.45.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 14:46:01 -0700 (PDT)
Message-ID: <51A6771C.5030805@gmail.com>
Date: Thu, 30 May 2013 09:46:04 +1200
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: Michael Sweet <msweet@apple.com>
Subject: Re: Strange use of link-local
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <51A515C2.1090208@gmail.com> <A9ABF29D-3195-4C62-AA99-9A599F4204F3@apple.com>
In-Reply-To: <A9ABF29D-3195-4C62-AA99-9A599F4204F3@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 21:46:09 -0000

On 29/05/2013 11:57, Michael Sweet wrote:
> Brian,
> 
> On 2013-05-28, at 4:38 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> I'm increasingly baffled by the use case. If the host is
>> in a context where it can reach a server *and* has more than
>> one interface (such that a ZoneID is needed at all), it
>> shouldn't be using a link local address anyway - it
>> should have configured a global scope address (possibly
>> under a ULA prefix). Discussion of this use case surely
>> belongs in MIF or HOMENET.
> 
> Most hosts (and probably all of the ones we care about) have multiple network interfaces, if only the loopback interface plus some sort of external network interface, forcing the use of the zoneid.  Also, the most common place you would need to use a link-local address for access is the place where global scope addresses are basically never used - the home.
> 
> So I agree that the MIF or HOMENET working groups might have something to say here, but RFC 6874 was published by *this* group and IPv6 link local addresses have broader context than either of the other groups.

Yes, but the limitation of the meaning of the Zone ID to a single
host isn't new; RFC 6874 simply reiterates it. The problem is that
the whole notion of scope is defective as currently defined (hence
http://tools.ietf.org/html/draft-carpenter-referral-ps, which we plan
to come back to when time permits). Today, the only clean fix is
to use a global-scope address, which means a ULA for disconnected
networks.

    Brian

>>    Brian
>>
>> On 29/05/2013 07:34, Ray Hunter wrote:
>>> Warning: post contains dumb questions.
>>>
>>> Michael Sweet wrote:
>>>> Christian,
>>>>
>>>> On 2013-05-24, at 1:45 PM, Christian Huitema <huitema@microsoft.com> wrote:
>>>>> Can we move from the process discussion to the technical discussion?
>>>>>
>>>>> Michael raised an interesting issue, and we have to analyze it. The consensus of the working group so far is that interface identifiers are private to the host, that any leakage outside the host should be prevented, and that a way to prevent that leakage is to ask proxies to erase them whenever they have an opportunity. Michael points that some servers take an opposite approach, want to record the interface from which the host called them, and want to ensure that further calls in the same session use exactly the same interface. That seems that a fairly legitimate debate, and I can see two alternatives -- one would be to reaffirm the old guidance and provides alternative to ensure session continuity, and the other would be to reverse the guidance and accept that the layer violation performed by servers is just fine.
>>>> (the following is printer-centric, but the same applies to network video cameras and other embedded network devices)
>>>>
>>>> Some background: HTTP and IPP services in printers include absolute URIs in the content they return. For IPP this can be http/https URLs to the printer's web page, ICC profiles, and other resources, along with the ipp/ipps URIs that the printer supports. For HTTP the most common are https URLs for "secure" areas of the printer's web interface.  Because a printer is often known by multiple names and addresses ("printer.local.", "printer.example.com.", 192.168.0.100, fe80::1234, etc.), the implementation guidance (and in IPP Everywhere, this is a conformance requirement) is that the server use the HTTP Host header provided in the request in the host/address field of its responses, subject to the usual security considerations (SHOULD validate Host value, etc.)  This allows the client to use the name or address it can resolve/connect to and makes sure that the printer-generated absolute URIs lead back to same printer.
>>>>
>>>> All of this falls apart with link-local addresses and RFC 6874.  Because the client is required to remove the zoneid from the outgoing request, the URIs it gets back from the server are no longer "reachable".
>>> Trying to understand what's going on here and what the root problem is.
>>>
>>> I have some dumb questions:
>>>
>>> Is the zoneid in the URI the interface on the client or the server node?
>>>
>>> What does other party learn from this information, since zoneid is
>>> currently defined as being local to the node and has no significance
>>> outside the context of the node?
>>>
>>> If the other party learns nothing, and the originating node just needs
>>> to hear an echo of it's own information for it's own use, what's wrong
>>> with using a cookie (server originated), or a hidden variable (client
>>> originated), to transport this interface information along with the
>>> request/reply?
>>>
>>> What if both the server AND the client have multiple interfaces: how do
>>> they both know which local interface on their own node is mutually
>>> connected and to be used for communication? There's only one single
>>> zoneid in the URI, so presumably one of the nodes is lacking some
>>> information.
>>>
>>> Shouldn't both nodes be using ND to learn this information?
>>> If there's nothing in the cache, try all interfaces?
>>>
>>> regards,
>>> RayH
>>>
>>>> What I propose is that we change the wording to allow the zoneid in the Host header but not in the Request-URI.  HTTP proxies would be required to strip any zoneid information in the Host header.  HTTP servers would be required to ignore any zoneid information for purposes of address validation but include it for any absolute URIs to the server they generate.
>>>>
>>>> Thoughts?
>>>>
>>>> _________________________________________________________
>>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>
>>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>>
> 
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
> 
> 

From markzzzsmith@yahoo.com.au  Wed May 29 14:56:21 2013
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3AC21F96E9 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 14:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZm5PLJaJ3bY for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 14:56:15 -0700 (PDT)
Received: from nm11-vm1.bullet.mail.bf1.yahoo.com (nm11-vm1.bullet.mail.bf1.yahoo.com [98.139.213.152]) by ietfa.amsl.com (Postfix) with ESMTP id 07EA121F9782 for <ipv6@ietf.org>; Wed, 29 May 2013 14:56:10 -0700 (PDT)
Received: from [98.139.215.141] by nm11.bullet.mail.bf1.yahoo.com with NNFMP; 29 May 2013 21:56:10 -0000
Received: from [98.139.212.244] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 29 May 2013 21:56:10 -0000
Received: from [127.0.0.1] by omp1053.mail.bf1.yahoo.com with NNFMP; 29 May 2013 21:56:10 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 218324.99353.bm@omp1053.mail.bf1.yahoo.com
Received: (qmail 9758 invoked by uid 60001); 29 May 2013 21:56:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1369864569; bh=xoCy3tyv5Lu7hoDQ3cJYyBf4OgXXBgnkUa9RupP8Z8Y=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RPCzObvl7JFNFSB08EtbYT9H4apjgsMesUlWfM7AOWplJ1SCQ/YwsKlGxb7Gc/MPlHwm1LUek44SCFUy23EMvJInEKR/SnE+5YMQB9m0c2mT7c85C6wHwqO3yrJXgKKPqIbqRwkgBM0Ik0w2hYk2l/08uzWwndcHhGVpxBwoGn4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=SBDfzfmLNgz2CCfazRiLD3VbAAoOF6gyba+xcWh5vFfk0/xnRPOIRzycJIWbeNcp8Dcew3HvwH6xDUjqh6wrMPl735KozSRxCicDYbnDS/zUQuEhAWwBVkPgRuu44P0gWOTFxCQnvaklHCyIAfWDxCjrd/UhDY7YDx1BNIgnCK8=;
X-YMail-OSG: INh0sXQVM1keWHGgSs3CrpzerrGSfFrZHCEEhqhmcp_AyQM V.DUA7VmmzRmqKN0QJKUZqDqSFkycc9OqwdLdaWTZkb9ufk6YH.k06SFvcEq dATcDobOkd0hSIM8_MSJ7fCBM3Qo2tS1fs54.Sh6ondHJ7tdEeHUNM8yRBZT kBMesET5d_QxCBQNtPJLmfD8BO7Ue8.TYKhjiEqV0jPzbu6iFATnOyvXuaBp 68lRTwiIUu..9haS0onO9wsYhxrW.oiG7No3Zk9uFUbT8G07EjF0lXFh.9Dl tlcVuOk_PUaraNKckJBD5PYIXdiOJ86IZ1MpKaBXU87R5v5YUTRCpTSM5beW 5NQWeovAk3m8pgma9ZkxIxaEvDGNRF17.fcaa1BtP9OqBkQRXp960h.Y0exw hTHhHG96xauEqNOOtnn0Z_H70A_Z6jezfagB9PQ5UHIrMynlietpTgXySSTg YTrIQy2_v7eBLG2oKdvel.SkLgEBDxg6.aspTINmYoI.95ZI3fX8WFSzBq8x YffgH2jzE6Lrxwjl4gM3rmzuurVFM29V.goUo0kipnAm7DZ9jNT7hVfAECZB 2xxTto2c-
Received: from [150.101.221.237] by web142504.mail.bf1.yahoo.com via HTTP; Wed, 29 May 2013 14:56:09 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBPbGUgVHJvYW4gPG90cm9hbkBlbXBsb3llZXMub3JnPgo.IFRvOiBNaWNoYWVsIFN3ZWV0IDxtc3dlZXRAYXBwbGUuY29tPgo.IENjOiBSYXkgSHVudGVyIDx2Nm9wc0BnbG9iaXMubmV0PjsgImlwdjZAaWV0Zi5vcmciIDxpcHY2QGlldGYub3JnPjsgdC5wZXRjaCA8aWV0ZmNAYnRjb25uZWN0LmNvbT47IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQG1pY3Jvc29mdC5jb20.Cj4gU2VudDogVGh1cnNkYXksIDMwIE1heSAyMDEzIDU6NDABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.144.546
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com> <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
Message-ID: <1369864569.9389.YahooMailNeo@web142504.mail.bf1.yahoo.com>
Date: Wed, 29 May 2013 14:56:09 -0700 (PDT)
From: Mark Smith <markzzzsmith@yahoo.com.au>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
To: Ole Troan <otroan@employees.org>, Michael Sweet <msweet@apple.com>
In-Reply-To: <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Ray Hunter <v6ops@globis.net>, "ipv6@ietf.org" <ipv6@ietf.org>, "t.petch" <ietfc@btconnect.com>, Christian Huitema <huitema@microsoft.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 21:56:22 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: Ole Troan <otroan@employ=
ees.org>=0A> To: Michael Sweet <msweet@apple.com>=0A> Cc: Ray Hunter <v6ops=
@globis.net>; "ipv6@ietf.org" <ipv6@ietf.org>; t.petch <ietfc@btconnect.com=
>; Christian Huitema <huitema@microsoft.com>=0A> Sent: Thursday, 30 May 201=
3 5:40 AM=0A> Subject: Re: [Technical Errata Reported] RFC6874 (3630)=0A> =
=0A> Michael,=0A> =0A> let me try a restart.=0A> =0A> you need to use link-=
local addresses for the HTTP connection between a client =0A> and a printer=
.=0A> =0A> a link-local address has link-local scope. it is ambiguous outsi=
de of the given =0A> link (zone).=0A> see RFC4007.=0A> =0A> an application =
using link-local addresses must be bound to the interface in the =0A> chose=
n link-local zone.=0A>=A0=0A=0AI too have been struggling to understand the=
 problem. If an application has chosen to use a link-local destination addr=
ess as a destination for a query, it has also chosen to use and specify an =
outbound interface, and needs to remember this interface information if it =
is expecting a response. All responses to this query will arrive on the sam=
e interface the query it was sent on. It is impossible for them not to, bec=
ause of the link scope of link-local addresses. If it receives responses on=
 a different interface, even if they look like they match the original quer=
y (e.g., via an application level transaction id), they are invalid.=0A=0A=
=0A> now the question becomes, what do you do with the embedded URIs contai=
ning =0A> link-local addresses?=0A> the referral clearly has no value outsi=
de of the given link-local zone.=0A> =0A> could you not infer the link-loca=
l zone of the referral from the transport =0A> session?=0A> given a link-lo=
cal transport connection using a link-local zone, would it ever =0A> make=
=0A> sense that the referrals using link-locals would belong to a different=
 zone?=0A> =0A> if not, then the client can just ensure to use the same zon=
e for referrals that =0A> it does the transport=0A> it received the HTML ov=
er.=0A> =0A> cheers,=0A> Ole=0A> =0A> -------------------------------------=
-------------------------------=0A> IETF IPv6 working group mailing list=0A=
> ipv6@ietf.org=0A> Administrative Requests: https://www.ietf.org/mailman/l=
istinfo/ipv6=0A> ----------------------------------------------------------=
----------=0A> 

From owen@delong.com  Wed May 29 16:04:03 2013
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B4A21F96D2; Wed, 29 May 2013 16:04:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pswECC7jYog; Wed, 29 May 2013 16:04:02 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 1357A21F9677; Wed, 29 May 2013 16:04:01 -0700 (PDT)
Received: from [172.19.131.173] ([199.108.68.10]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r4TN2NdX003797 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 29 May 2013 16:02:35 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r4TN2NdX003797
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1369868560; bh=JreFYMlSPem26IEHEOTWatzqEQA=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=yVndiO/26qw3isrewtwAonZbdSKi6Y8G8fI+JCPpVu6dEs0PFiC2ykvss3+fTSOQY tRY2bJlGPpyQHRlGpq5h3gNYFDP3mEURVdT2NemomjfzHcGjZqcIKtTUEiD93M3pnY fXm3hEIJMkfPMyYu/PAb1gl+N9kvr7brkig3MMgk=
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Owen DeLong <owen@delong.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
Date: Wed, 29 May 2013 16:02:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1503)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Wed, 29 May 2013 16:02:40 -0700 (PDT)
X-Mailman-Approved-At: Wed, 29 May 2013 16:19:06 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 29 May 2013 23:04:03 -0000

Personally, I think this is an inherently bad idea.

IP addresses need less overloading of semantics, not more.

We already use IP addresses for two conflicting purposes=85 Topology =
locator and End System Identifier.

This overloading is at the heart of our current scaling issues with =
respect to the routing table. While these issues are currently less =
critical than they have been in the past and will likely get quite a bit =
less critical in IPv6, that is only because we have given up a fair =
amount of functionality to preserve scalability in this regard.

If we did not have this overloading, then an entity could obtain a set =
of end-system identifiers and keep them throughout their lifetime, =
regardless of topological changes. Today, where the addresses are =
overloaded with both semantics, we either have to force most entities to =
change their numbers when they change topology or we face unsustainable =
growth in the routing tables.

The idea of adding more semantics to addressing rather than seeking to =
reduce this overloading seems a step in the wrong direction, IMHO.

Owen

On May 29, 2013, at 12:06 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> IP addresses are designed as topology locator, so that every packet =
can be routed to its network destination.
>=20
> However, even in IPv4 era, some network operators have mapped their IP =
address with certain semantic locally. These kind of mechanism =
explicitly express the semantic properties of every packet. =
Consequently, these network operators can inspect the properties of =
packets easily by mapping the addresses back to semantic.
>=20
> Network operators, who have large IPv6 address space, may also choose =
to embedded some semantics into IPv6 addresses by assigning additional =
significance to specific bits within the prefix. =
draft-jiang-v6ops-semantic-prefix documents a framework method that =
network operations may use their addresses with embedded semantics. =
These semantics bits are only meaningful within a single network, or =
group of interconnected networks which share a common addressing policy. =
Based on these embedded semantic bits in source/destination addresses, =
the network operators can accordingly treat network packets differently =
and efficiently.
>=20
> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>=20
> Could you please review this draft and comments? It will help the =
document become more useful information to be shared.
>=20
> Best regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Tuesday, May 28, 2013 10:28 AM
>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang
>> Subject: New Version Notification for
>> draft-jiang-v6ops-semantic-prefix-03.txt
>>=20
>>=20
>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt
>> has been successfully submitted by Sheng Jiang and posted to the
>> IETF repository.
>>=20
>> Filename:	 draft-jiang-v6ops-semantic-prefix
>> Revision:	 03
>> Title:		 A Framework for Semantic IPv6 Prefix
>> Creation date:	 2013-05-28
>> Group:		 Individual Submission
>> Number of pages: 19
>> URL:
>> =
http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03.t=
xt
>> Status:
>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix
>> Htmlized:
>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03=

>>=20
>> Abstract:
>>  This document describes a framework method that network operations
>>  may use their addresses.  Network operators, who have large IPv6
>>  address space, may choose to embedded some semantics into IPv6
>>  addresses by assigning additional significance to specific bits
>>  within the prefix.  By embedded semantics into IPv6 prefixes, the
>>  semantics of packets can be inspected easily.  Routers and other
>>  intermediary devices can easily apply relevant policies as required.
>>  Packet-level differentiation can also enable flow-level and user-
>>  level differentiation.  Consequently, the network operators can
>>  accordingly treat network packets differently and efficiently.  The
>>  management and maintenance of networks can be much simpler.
>>=20
>>=20
>>=20
>>=20
>> The IETF Secretariat
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From mcr@sandelman.ca  Wed May 29 18:14:16 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB93721F9374 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:14:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+15KAJPUYov for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:14:16 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 0C38221F85B8 for <ipv6@ietf.org>; Wed, 29 May 2013 18:14:16 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 761E220168 for <ipv6@ietf.org>; Wed, 29 May 2013 21:26:45 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 65EC563A8C; Wed, 29 May 2013 21:13:25 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 5160C63A88 for <ipv6@ietf.org>; Wed, 29 May 2013 21:13:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com> <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 May 2013 21:13:25 -0400
Message-ID: <15024.1369876405@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 01:14:16 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Ole" =3D=3D Ole Troan <otroan@employees.org> writes:
    Ole> could you not infer the link-local zone of the referral from
    Ole> the transport session?=20
    Ole> given a link-local transport connection using a link-local
    Ole> zone, would it ever make=20
    Ole> sense that the referrals using link-locals would belong to a
    Ole> different zone?=20

Or to put it another way, if the URI you started with was bound to a
particular zoneID, then any link locals you see in the HTML (or JSON or
...) that you get from that direction, are also bound to that zoneID.

This is a bit like what MIF's RFC 6731 does for DNS.
(as much as I hate that solution)

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

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

iQCVAwUAUaantIqHRg3pndX9AQL17wP9HLOASgGhuIWsRo4Aq/EjUEDjbZ/H2VTK
H4Ok58PSa8Irj6fri8LcjNJpVoVSaWDglKqQk/VDOhD2DGn6KIcvTBu0+lq4Odpp
X3vOUHCElcrjgycxEDRrK7C6cMZegmvGvdKeQtDFKOs1rrUzkIC+u+UFiAn1YNYT
R6nZnDaqf+s=
=gOEe
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Wed May 29 18:16:40 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB8E21F87BB for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:16: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V11ckyz-dlj2 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:16:39 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 8045F21F8808 for <ipv6@ietf.org>; Wed, 29 May 2013 18:16:39 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C46E020168 for <ipv6@ietf.org>; Wed, 29 May 2013 21:29:11 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 3131A63A8C; Wed, 29 May 2013 21:15:51 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id DF66863A88 for <ipv6@ietf.org>; Wed, 29 May 2013 21:15:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <51A5A5B4.8040500@globis.net> <23153.1369847355@sandelman.ca> <E823DA83-C3EB-4952-B785-71ED5B95E44A@apple.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 May 2013 21:15:51 -0400
Message-ID: <15481.1369876551@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 01:16:40 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Michael" =3D=3D Michael Sweet <msweet@apple.com> writes:
    Ray> How does the very first URI learn the correct ZoneID in the first =
place?
    Ray> Manually.
    >>=20
    >> In a Bonjour/mDNS scenario, the client sees the link-local address o=
n interface
    >> with zoneID FOO, and records that.  The client learns it's correct Z=
oneID.
    >> (At no point does it matter what the server's zoneid for the interfa=
ce
    >> is)

    Michael> One important point here: we don't send IPv6 link local
    Michael> addresses in this case, we send the .local hostname that
    Michael> the printer is using.  This avoids the whole issue of IPv6
    Michael> link-local addresses in URIs, we just have to deal with

Yes, I see your point that in the mDNS case, likely we have a name.
But not always.  Sometimes, one starts with a name, it gets translated
to an address, then gets passed elsewhere in some way, and only the
address is left.  When the name got turned into an address, it got a
zoneID (in the struct addrinfo) assigned.=20=20

If you then pass that somewhere else, or into the kernel, maybe it goes
through some network policy code (e.g. IPsec SPD... into a key daemon),
the name is long lost.

And of course, we have the human debugging situation, which is the most
likely use.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09





--=-=-=
Content-Type: application/pgp-signature

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

iQCVAwUAUaaoR4qHRg3pndX9AQKPXAQAlo7J6GtO6zenfopjFyUkIKFCad5eU96Q
PT864m2/Y203tH4Ztmqi+S9AkK1hdb+Y+DwIQYBAQXGJkVD37O0Y/RLtOzWVNbZH
2/G9T1Jq7JjfnOFUZW321XLFpAv3GWQTBbLhjPLv6a2mwAQfRAxKpbHPKfgjnW2C
kDpjl2ADMnA=
=f/5/
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Wed May 29 18:19:22 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EEA21F9424 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:19:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJsq0Cb9lV29 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 18:19:21 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id F378D21F87FB for <ipv6@ietf.org>; Wed, 29 May 2013 18:19:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3FA4720168; Wed, 29 May 2013 21:31:53 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A685363A8C; Wed, 29 May 2013 21:18:33 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 957A963A88; Wed, 29 May 2013 21:18:33 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Smith <markzzzsmith@yahoo.com.au>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: [Technical Errata Reported] RFC6874 (3630)
In-Reply-To: <1369864569.9389.YahooMailNeo@web142504.mail.bf1.yahoo.com>
References: <20130523035151.7B24A6210A@rfc-editor.org> <519DA89C.5070704@gmail.com> <13FD8630-3CB7-46D5-9A27-A83EAD2E7F74@apple.com> <C91E67751B1EFF41B857DE2FE1F68ABA0FF4CC0A@TK5EX14MBXC274.redmond.corp.microsoft.com> <CF457469-49FC-42CC-9E04-487FE035CA10@apple.com> <014b01ce5854$be6c7880$4001a8c0@gateway.2wire.net> <9B503485-D9A7-4D90-991C-162D9C7EE8FF@apple.com> <033d01ce5893$c3522360$4001a8c0@gateway.2wire.net> <C91E67751B1EFF41B857DE2FE1F68ABA0FF60CCD@TK5EX14MBXC273.redmond.corp.microsoft.com> <51A2795C-4D7D-4A59-933B-7CCF527CE10C@apple.com> <51A506BD.9060804@globis.net> <C2714AED-38EC-4A5A-9C1A-BC9619C6A5D7@apple.com> <F0D34E7C-9E35-46E9-A3C4-687D97A08019@employees.org> <D86D37D6-1977-4350-8C1B-691F1C345450@apple.com> <F44FB3FA-F1E0-4F3C-9614-38BA849F0D50@employees.org> <1369864569.9389.YahooMailNeo@web142504.mail.bf1.yahoo.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 29 May 2013 21:18:33 -0400
Message-ID: <16011.1369876713@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 01:19:22 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Mark" =3D=3D Mark Smith <markzzzsmith@yahoo.com.au> writes:
    Mark> I too have been struggling to understand the problem. If an
    Mark> application has chosen to use a link-local destination address
    Mark> as a destination for a query, it has also chosen to use and

The application passed a "struct sockaddr" that it got from
getaddrinfo() to connect(2).  TCP took care of the rest.  The
application didn't "choose" anything.  It just ran the normal protocol
machinery.=20

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

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

iQCVAwUAUaao6YqHRg3pndX9AQLC5gQAzWgGip1XiAry5nkLDx2MeR9y7ovBJ72K
gSqEzfJ/TywtLY4dOPOxGq+Bv0Be/moFAcvbm9UgZvKSarLxdN4sDCVDJZ4/hgKJ
zqIkLtqSXtJeNfBVU+wv9PGV+1BYAonlgJO/tv213RXaIIwmuMYTeW96Uy45id7/
jw6VyoaVKjI=
=lISD
-----END PGP SIGNATURE-----
--=-=-=--

From jeremy.duncan@salientfed.com  Wed May 29 19:20:10 2013
Return-Path: <jeremy.duncan@salientfed.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA25121F91B8; Wed, 29 May 2013 19:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.996
X-Spam-Level: 
X-Spam-Status: No, score=-3.996 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80ylOn0APKa7; Wed, 29 May 2013 19:20:04 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe006.messaging.microsoft.com [216.32.180.16]) by ietfa.amsl.com (Postfix) with ESMTP id 6DEEC21F9301; Wed, 29 May 2013 19:20:00 -0700 (PDT)
Received: from mail38-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE003.bigfish.com (10.7.40.23) with Microsoft SMTP Server id 14.1.225.23; Thu, 30 May 2013 02:19:59 +0000
Received: from mail38-va3 (localhost [127.0.0.1])	by mail38-va3-R.bigfish.com (Postfix) with ESMTP id 418691400AD; Thu, 30 May 2013 02:19:59 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.234.117; KIP:(null); UIP:(null); IPV:NLI; H:SN2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I936eI542I1432Idf9Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz2fh2a8h668h839h946hd24hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18deh18e1h1946h19b5h1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh17ej1155h)
Received-SPF: pass (mail38-va3: domain of salientfed.com designates 157.56.234.117 as permitted sender) client-ip=157.56.234.117; envelope-from=jeremy.duncan@salientfed.com; helo=SN2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail38-va3 (localhost.localdomain [127.0.0.1]) by mail38-va3 (MessageSwitch) id 1369880397671238_24797; Thu, 30 May 2013 02:19:57 +0000 (UTC)
Received: from VA3EHSMHS019.bigfish.com (unknown [10.7.14.248])	by mail38-va3.bigfish.com (Postfix) with ESMTP id 9B6EF26004D; Thu, 30 May 2013 02:19:57 +0000 (UTC)
Received: from SN2PRD0510HT004.namprd05.prod.outlook.com (157.56.234.117) by VA3EHSMHS019.bigfish.com (10.7.99.29) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 30 May 2013 02:19:55 +0000
Received: from SN2PRD0510MB370.namprd05.prod.outlook.com ([169.254.12.154]) by SN2PRD0510HT004.namprd05.prod.outlook.com ([10.255.116.39]) with mapi id 14.16.0311.000; Thu, 30 May 2013 02:19:54 +0000
From: "Duncan, Richard (Jeremy)" <jeremy.duncan@salientfed.com>
To: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcyJkAgAA3Ses=
Date: Thu, 30 May 2013 02:19:54 +0000
Message-ID: <eg56ow4ob19bwj5507xajo8n.1369880374960@email.android.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>, <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
In-Reply-To: <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [::]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: salientfed.com
X-Mailman-Approved-At: Wed, 29 May 2013 19:22:58 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 02:20:10 -0000

I tend to agree with Owen here.  In fact, I am curious how an allocation fr=
om a provider to a organization would look?  Instead of following standard =
issuing practices of a /48, are you suggesting the provider would issue mul=
tiple /52s that follow functional categories (VoIP, management, etc)?  Or m=
aybe I missed something?


010100110110010101101101011100000110010101110010001000000100011001101001

Jeremy Duncan
Senior Director, IPv6 Network Architect
Salient Federal Solutions, Inc. (Now including SGIS & Command Information I=
nc.)
4000 Legato Road, Suite 600
Fairfax, VA 22033
Google Voice: 540.440.1193
jeremy.duncan@salientfed.com

Owen DeLong <owen@delong.com> wrote:


Personally, I think this is an inherently bad idea.

IP addresses need less overloading of semantics, not more.

We already use IP addresses for two conflicting purposes=85 Topology locato=
r and End System Identifier.

This overloading is at the heart of our current scaling issues with respect=
 to the routing table. While these issues are currently less critical than =
they have been in the past and will likely get quite a bit less critical in=
 IPv6, that is only because we have given up a fair amount of functionality=
 to preserve scalability in this regard.

If we did not have this overloading, then an entity could obtain a set of e=
nd-system identifiers and keep them throughout their lifetime, regardless o=
f topological changes. Today, where the addresses are overloaded with both =
semantics, we either have to force most entities to change their numbers wh=
en they change topology or we face unsustainable growth in the routing tabl=
es.

The idea of adding more semantics to addressing rather than seeking to redu=
ce this overloading seems a step in the wrong direction, IMHO.

Owen

On May 29, 2013, at 12:06 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> IP addresses are designed as topology locator, so that every packet can b=
e routed to its network destination.
>
> However, even in IPv4 era, some network operators have mapped their IP ad=
dress with certain semantic locally. These kind of mechanism explicitly exp=
ress the semantic properties of every packet. Consequently, these network o=
perators can inspect the properties of packets easily by mapping the addres=
ses back to semantic.
>
> Network operators, who have large IPv6 address space, may also choose to =
embedded some semantics into IPv6 addresses by assigning additional signifi=
cance to specific bits within the prefix. draft-jiang-v6ops-semantic-prefix=
 documents a framework method that network operations may use their address=
es with embedded semantics. These semantics bits are only meaningful within=
 a single network, or group of interconnected networks which share a common=
 addressing policy. Based on these embedded semantic bits in source/destina=
tion addresses, the network operators can accordingly treat network packets=
 differently and efficiently.
>
> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>
> Could you please review this draft and comments? It will help the documen=
t become more useful information to be shared.
>
> Best regards,
>
> Sheng
>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Tuesday, May 28, 2013 10:28 AM
>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang
>> Subject: New Version Notification for
>> draft-jiang-v6ops-semantic-prefix-03.txt
>>
>>
>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt
>> has been successfully submitted by Sheng Jiang and posted to the
>> IETF repository.
>>
>> Filename:     draft-jiang-v6ops-semantic-prefix
>> Revision:     03
>> Title:                A Framework for Semantic IPv6 Prefix
>> Creation date:        2013-05-28
>> Group:                Individual Submission
>> Number of pages: 19
>> URL:
>> http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03=
.txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix
>> Htmlized:
>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03
>>
>> Abstract:
>>  This document describes a framework method that network operations
>>  may use their addresses.  Network operators, who have large IPv6
>>  address space, may choose to embedded some semantics into IPv6
>>  addresses by assigning additional significance to specific bits
>>  within the prefix.  By embedded semantics into IPv6 prefixes, the
>>  semantics of packets can be inspected easily.  Routers and other
>>  intermediary devices can easily apply relevant policies as required.
>>  Packet-level differentiation can also enable flow-level and user-
>>  level differentiation.  Consequently, the network operators can
>>  accordingly treat network packets differently and efficiently.  The
>>  management and maintenance of networks can be much simpler.
>>
>>
>>
>>
>> The IETF Secretariat
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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



From jiangsheng@huawei.com  Wed May 29 23:34:52 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755D721F9473; Wed, 29 May 2013 23:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujQ4Ee0T7to7; Wed, 29 May 2013 23:34:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8059721F9485; Wed, 29 May 2013 23:34:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH76785; Thu, 30 May 2013 06:34:44 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 07:34:10 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 14:34:43 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Thu, 30 May 2013 14:34:38 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAEA7rA=
Date: Thu, 30 May 2013 06:34:36 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9924F@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
In-Reply-To: <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 06:34:52 -0000

SGksIE93ZW4sDQoNClRoZXNlIGVtYmVkZGVkIHNlbWFudGljcyBhcmUgdmVyeSBkaWZmZXJlbnQg
ZnJvbSBFbmQgU3lzdGVtIElkZW50aWZpZXIuIFRoZSBlbmQgc3lzdGVtIGlkZW50aWZpZXIgZnVu
Y3Rpb25zIHdhcyBwcm9ibGVtIGJlY2F1c2UgaXQgdmlvbGVudHMgdGhlIGxheWVyIG1vZGVsLiBN
YW55IEFQUHMgb3IgdHJhbnNwb3J0IGxheWVyIHVzZSBJUCBhZGRyZXNzIGFzIHRoZWlyIGlkZW50
aWZpZXIuIEFuZCB0aGUgZW5kIHN5c3RlbSBpZGVudGlmaWVyIGJyZWFrcyBpbiBhdCBsZWFzdCB0
d28gc2NlbmFyaW9zOiB3aGVuIGVuZCBkZXZpY2VzIGNoYW5nZSB0aGUgYWNjZXNzIHBvaW50cyBv
ciB3aGVuIElQIGxheWVyIHRyYW5zbGF0aW9uIChOQVQ0NCBvciBOQVQ2NCkgaGFwcGVucy4NCg0K
VGhlIHByb3Bvc2VkIGVtYmVkZGVkIHNlbWFudGljcyBpcyBzdGlsbCBsYXllciAzLiBUaGV5IGFy
ZSB1c2VkIGZvciByb3V0ZXIncyBwYWNrZXQgcHJvY2Vzc2luZy4gVGhlc2UgZW1iZWRkZWQgc2Vt
YW50aWNzIGlzIG9ubHkgbWVhbmluZ2Z1bCBsb2NhbGx5IHdpdGhpbiBJU1Agb3duZXIgbmV0d29y
ay4gQWZ0ZXIgbGVhdmluZyB0aGUgSVNQIG5ldHdvcmssIElQIGFkZHJlc3NlcyBhcmUgb25seSBs
b2NhdG9yLCBub3RoaW5nIG1vcmUuIFRoZSBib3R0b20gbGluZSBpcyBhIG5ldHdvcmsgb3BlcmF0
b3IgY2FuIGNob29zZSB0byBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVz
c2VzIGFzc2lnbm1lbnQuIFdlLCBhcyBJRVRGLCBtYXkgbm90IGVuY291cmFnZSBzdWNoIHVzYWdl
LCBidXQgc2hvdWxkIGRvY3VtZW50IGl0IGFuZCBtYXkgZ2l2ZSBzb21lIGd1aWRhbmNlIG9yIGFu
YWx5c2lzIG9mIGl0Lg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPkZyb206IE93ZW4gRGVMb25nIFttYWlsdG86b3dlbkBkZWxvbmcuY29t
XQ0KPlNlbnQ6IFRodXJzZGF5LCBNYXkgMzAsIDIwMTMgNzowMiBBTQ0KPlRvOiBTaGVuZyBKaWFu
Zw0KPkNjOiA8djZvcHNAaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnOw0KPmRyYWZ0LWppYW5nLXY2
b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZw0KPlN1YmplY3Q6IFJlOiBbdjZvcHNd
IENvdWxkIElQdjYgYWRkcmVzcyBiZSBtb3JlIHRoYW4NCj5sb2NhdG9yPy8vZHJhZnQtamlhbmct
djZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+DQo+UGVyc29uYWxseSwgSSB0aGluayB0aGlzIGlz
IGFuIGluaGVyZW50bHkgYmFkIGlkZWEuDQo+DQo+SVAgYWRkcmVzc2VzIG5lZWQgbGVzcyBvdmVy
bG9hZGluZyBvZiBzZW1hbnRpY3MsIG5vdCBtb3JlLg0KPg0KPldlIGFscmVhZHkgdXNlIElQIGFk
ZHJlc3NlcyBmb3IgdHdvIGNvbmZsaWN0aW5nIHB1cnBvc2Vz4oCmIFRvcG9sb2d5IGxvY2F0b3IN
Cj5hbmQgRW5kIFN5c3RlbSBJZGVudGlmaWVyLg0KPg0KPlRoaXMgb3ZlcmxvYWRpbmcgaXMgYXQg
dGhlIGhlYXJ0IG9mIG91ciBjdXJyZW50IHNjYWxpbmcgaXNzdWVzIHdpdGggcmVzcGVjdCB0bw0K
PnRoZSByb3V0aW5nIHRhYmxlLiBXaGlsZSB0aGVzZSBpc3N1ZXMgYXJlIGN1cnJlbnRseSBsZXNz
IGNyaXRpY2FsIHRoYW4gdGhleSBoYXZlDQo+YmVlbiBpbiB0aGUgcGFzdCBhbmQgd2lsbCBsaWtl
bHkgZ2V0IHF1aXRlIGEgYml0IGxlc3MgY3JpdGljYWwgaW4gSVB2NiwgdGhhdCBpcyBvbmx5DQo+
YmVjYXVzZSB3ZSBoYXZlIGdpdmVuIHVwIGEgZmFpciBhbW91bnQgb2YgZnVuY3Rpb25hbGl0eSB0
byBwcmVzZXJ2ZQ0KPnNjYWxhYmlsaXR5IGluIHRoaXMgcmVnYXJkLg0KPg0KPklmIHdlIGRpZCBu
b3QgaGF2ZSB0aGlzIG92ZXJsb2FkaW5nLCB0aGVuIGFuIGVudGl0eSBjb3VsZCBvYnRhaW4gYSBz
ZXQgb2YNCj5lbmQtc3lzdGVtIGlkZW50aWZpZXJzIGFuZCBrZWVwIHRoZW0gdGhyb3VnaG91dCB0
aGVpciBsaWZldGltZSwgcmVnYXJkbGVzcyBvZg0KPnRvcG9sb2dpY2FsIGNoYW5nZXMuIFRvZGF5
LCB3aGVyZSB0aGUgYWRkcmVzc2VzIGFyZSBvdmVybG9hZGVkIHdpdGggYm90aA0KPnNlbWFudGlj
cywgd2UgZWl0aGVyIGhhdmUgdG8gZm9yY2UgbW9zdCBlbnRpdGllcyB0byBjaGFuZ2UgdGhlaXIg
bnVtYmVycw0KPndoZW4gdGhleSBjaGFuZ2UgdG9wb2xvZ3kgb3Igd2UgZmFjZSB1bnN1c3RhaW5h
YmxlIGdyb3d0aCBpbiB0aGUgcm91dGluZw0KPnRhYmxlcy4NCj4NCj5UaGUgaWRlYSBvZiBhZGRp
bmcgbW9yZSBzZW1hbnRpY3MgdG8gYWRkcmVzc2luZyByYXRoZXIgdGhhbiBzZWVraW5nIHRvDQo+
cmVkdWNlIHRoaXMgb3ZlcmxvYWRpbmcgc2VlbXMgYSBzdGVwIGluIHRoZSB3cm9uZyBkaXJlY3Rp
b24sIElNSE8uDQo+DQo+T3dlbg0KPg0KPk9uIE1heSAyOSwgMjAxMywgYXQgMTI6MDYgQU0sIFNo
ZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdlaS5jb20+DQo+d3JvdGU6DQo+DQo+PiBJUCBhZGRy
ZXNzZXMgYXJlIGRlc2lnbmVkIGFzIHRvcG9sb2d5IGxvY2F0b3IsIHNvIHRoYXQgZXZlcnkgcGFj
a2V0IGNhbiBiZQ0KPnJvdXRlZCB0byBpdHMgbmV0d29yayBkZXN0aW5hdGlvbi4NCj4+DQo+PiBI
b3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBzb21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFw
cGVkIHRoZWlyIElQDQo+YWRkcmVzcyB3aXRoIGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhl
c2Uga2luZCBvZiBtZWNoYW5pc20gZXhwbGljaXRseQ0KPmV4cHJlc3MgdGhlIHNlbWFudGljIHBy
b3BlcnRpZXMgb2YgZXZlcnkgcGFja2V0LiBDb25zZXF1ZW50bHksIHRoZXNlIG5ldHdvcmsNCj5v
cGVyYXRvcnMgY2FuIGluc3BlY3QgdGhlIHByb3BlcnRpZXMgb2YgcGFja2V0cyBlYXNpbHkgYnkg
bWFwcGluZyB0aGUNCj5hZGRyZXNzZXMgYmFjayB0byBzZW1hbnRpYy4NCj4+DQo+PiBOZXR3b3Jr
IG9wZXJhdG9ycywgd2hvIGhhdmUgbGFyZ2UgSVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbyBj
aG9vc2UgdG8NCj5lbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGJ5
IGFzc2lnbmluZyBhZGRpdGlvbmFsDQo+c2lnbmlmaWNhbmNlIHRvIHNwZWNpZmljIGJpdHMgd2l0
aGluIHRoZSBwcmVmaXguDQo+ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4IGRvY3Vt
ZW50cyBhIGZyYW1ld29yayBtZXRob2QgdGhhdA0KPm5ldHdvcmsgb3BlcmF0aW9ucyBtYXkgdXNl
IHRoZWlyIGFkZHJlc3NlcyB3aXRoIGVtYmVkZGVkIHNlbWFudGljcy4gVGhlc2UNCj5zZW1hbnRp
Y3MgYml0cyBhcmUgb25seSBtZWFuaW5nZnVsIHdpdGhpbiBhIHNpbmdsZSBuZXR3b3JrLCBvciBn
cm91cCBvZg0KPmludGVyY29ubmVjdGVkIG5ldHdvcmtzIHdoaWNoIHNoYXJlIGEgY29tbW9uIGFk
ZHJlc3NpbmcgcG9saWN5LiBCYXNlZCBvbg0KPnRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMg
aW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlIG5ldHdvcmsNCj5vcGVyYXRvcnMg
Y2FuIGFjY29yZGluZ2x5IHRyZWF0IG5ldHdvcmsgcGFja2V0cyBkaWZmZXJlbnRseSBhbmQgZWZm
aWNpZW50bHkuDQo+Pg0KPj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmct
djZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pg0KPj4gQ291bGQgeW91IHBsZWFzZSByZXZpZXcg
dGhpcyBkcmFmdCBhbmQgY29tbWVudHM/IEl0IHdpbGwgaGVscCB0aGUgZG9jdW1lbnQNCj5iZWNv
bWUgbW9yZSB1c2VmdWwgaW5mb3JtYXRpb24gdG8gYmUgc2hhcmVkLg0KPj4NCj4+IEJlc3QgcmVn
YXJkcywNCj4+DQo+PiBTaGVuZw0KPj4NCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
Pj4+IEZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0
c0BpZXRmLm9yZ10NCj4+PiBTZW50OiBUdWVzZGF5LCBNYXkgMjgsIDIwMTMgMTA6MjggQU0NCj4+
PiBUbzogUWlvbmcgU3VuOyBJYW4gRmFycmVyOyBTaGVuZyBKaWFuZzsgQm95YW5nDQo+Pj4gU3Vi
amVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPj4+IGRyYWZ0LWppYW5nLXY2b3Bz
LXNlbWFudGljLXByZWZpeC0wMy50eHQNCj4+Pg0KPj4+DQo+Pj4gQSBuZXcgdmVyc2lvbiBvZiBJ
LUQsIGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMy50eHQNCj4+PiBoYXMgYmVl
biBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNoZW5nIEppYW5nIGFuZCBwb3N0ZWQgdG8gdGhl
DQo+Pj4gSUVURiByZXBvc2l0b3J5Lg0KPj4+DQo+Pj4gRmlsZW5hbWU6CSBkcmFmdC1qaWFuZy12
Nm9wcy1zZW1hbnRpYy1wcmVmaXgNCj4+PiBSZXZpc2lvbjoJIDAzDQo+Pj4gVGl0bGU6CQkgQSBG
cmFtZXdvcmsgZm9yIFNlbWFudGljIElQdjYgUHJlZml4DQo+Pj4gQ3JlYXRpb24gZGF0ZToJIDIw
MTMtMDUtMjgNCj4+PiBHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4+PiBOdW1iZXIg
b2YgcGFnZXM6IDE5DQo+Pj4gVVJMOg0KPj4+DQo+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzLnR4dA0KPj4+IFN0
YXR1czoNCj4+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWppYW5nLXY2
b3BzLXNlbWFudGljLXByZWZpeA0KPj4+IEh0bWxpemVkOg0KPj4+IGh0dHA6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0KPj4+IERpZmY6
DQo+Pj4gaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtamlhbmctdjZvcHMt
c2VtYW50aWMtcHJlZml4LTAzDQo+Pj4NCj4+PiBBYnN0cmFjdDoNCj4+PiAgVGhpcyBkb2N1bWVu
dCBkZXNjcmliZXMgYSBmcmFtZXdvcmsgbWV0aG9kIHRoYXQgbmV0d29yayBvcGVyYXRpb25zDQo+
Pj4gIG1heSB1c2UgdGhlaXIgYWRkcmVzc2VzLiAgTmV0d29yayBvcGVyYXRvcnMsIHdobyBoYXZl
IGxhcmdlIElQdjYNCj4+PiAgYWRkcmVzcyBzcGFjZSwgbWF5IGNob29zZSB0byBlbWJlZGRlZCBz
b21lIHNlbWFudGljcyBpbnRvIElQdjYNCj4+PiAgYWRkcmVzc2VzIGJ5IGFzc2lnbmluZyBhZGRp
dGlvbmFsIHNpZ25pZmljYW5jZSB0byBzcGVjaWZpYyBiaXRzDQo+Pj4gIHdpdGhpbiB0aGUgcHJl
Zml4LiAgQnkgZW1iZWRkZWQgc2VtYW50aWNzIGludG8gSVB2NiBwcmVmaXhlcywgdGhlDQo+Pj4g
IHNlbWFudGljcyBvZiBwYWNrZXRzIGNhbiBiZSBpbnNwZWN0ZWQgZWFzaWx5LiAgUm91dGVycyBh
bmQgb3RoZXINCj4+PiAgaW50ZXJtZWRpYXJ5IGRldmljZXMgY2FuIGVhc2lseSBhcHBseSByZWxl
dmFudCBwb2xpY2llcyBhcyByZXF1aXJlZC4NCj4+PiAgUGFja2V0LWxldmVsIGRpZmZlcmVudGlh
dGlvbiBjYW4gYWxzbyBlbmFibGUgZmxvdy1sZXZlbCBhbmQgdXNlci0NCj4+PiAgbGV2ZWwgZGlm
ZmVyZW50aWF0aW9uLiAgQ29uc2VxdWVudGx5LCB0aGUgbmV0d29yayBvcGVyYXRvcnMgY2FuDQo+
Pj4gIGFjY29yZGluZ2x5IHRyZWF0IG5ldHdvcmsgcGFja2V0cyBkaWZmZXJlbnRseSBhbmQgZWZm
aWNpZW50bHkuICBUaGUNCj4+PiAgbWFuYWdlbWVudCBhbmQgbWFpbnRlbmFuY2Ugb2YgbmV0d29y
a3MgY2FuIGJlIG11Y2ggc2ltcGxlci4NCj4+Pg0KPj4+DQo+Pj4NCj4+Pg0KPj4+IFRoZSBJRVRG
IFNlY3JldGFyaWF0DQo+Pg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+IHY2b3BzIG1haWxpbmcgbGlzdA0KPj4gdjZvcHNAaWV0Zi5vcmcNCj4+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjZvcHMNCg0K

From tjc@ecs.soton.ac.uk  Wed May 29 23:40:27 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB37B21F9485; Wed, 29 May 2013 23:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.124
X-Spam-Level: 
X-Spam-Status: No, score=-2.124 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JjJ4ATH9+k6V; Wed, 29 May 2013 23:40:27 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id B819C21F940D; Wed, 29 May 2013 23:40:26 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4U6YePM004727;  Thu, 30 May 2013 07:34:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4U6YePM004727
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369895681; bh=WGxpwHSirCteWOy01LYNFQrGRKE=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=Wl5PPwrbrsiAfVkXWKgHF1eb7b6Ee5ebHITX2X/BQCSwHyc/6qlDF+RIYabRv4feO l8tXK1CF2zqDkn8WI/SgOW3zx1uBZX8N7UgFoUFoBv/UiAFj3FfkAqUNLpUzmHqAl7 HwY75X4m2h9JYO4JlZi0/vDgTdMzyZ/erMeEA3DM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4Y7Ye0430616311ed ret-id none; Thu, 30 May 2013 07:34:41 +0100
Received: from [192.168.1.103] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4U6XFXP017497 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 07:33:16 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <8E492087-390E-4F8E-8078-1D0E63849243@delong.com>
Date: Thu, 30 May 2013 07:33:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
To: Owen DeLong <owen@delong.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4Y7Ye043061631100; tid=p4Y7Ye0430616311ed; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4U6YePM004727
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 06:40:28 -0000

On 30 May 2013, at 00:02, Owen DeLong <owen@delong.com> wrote:

> Personally, I think this is an inherently bad idea.
>=20
> IP addresses need less overloading of semantics, not more.
>=20
> We already use IP addresses for two conflicting purposes=85 Topology =
locator and End System Identifier.
>=20
> This overloading is at the heart of our current scaling issues with =
respect to the routing table. While these issues are currently less =
critical than they have been in the past and will likely get quite a bit =
less critical in IPv6, that is only because we have given up a fair =
amount of functionality to preserve scalability in this regard.
>=20
> If we did not have this overloading, then an entity could obtain a set =
of end-system identifiers and keep them throughout their lifetime, =
regardless of topological changes. Today, where the addresses are =
overloaded with both semantics, we either have to force most entities to =
change their numbers when they change topology or we face unsustainable =
growth in the routing tables.
>=20
> The idea of adding more semantics to addressing rather than seeking to =
reduce this overloading seems a step in the wrong direction, IMHO.

I agree. That said, an ISP, enterprise or group of organisations can =
follow whatever semantics they wish within their own borders. Just don't =
expect anyone else to follow or use those semantics.  What Sheng is =
proposing is clearly stated as only being for interpretation between =
agreeing organisations.

There are examples of organisations or protocols already doing this, be =
it embedding VLAN IDs or port number representations in addresses.  And =
of protocols - in particular 6rd comes to mind as an example of an IPv6 =
addressing scheme with embedded semantics, which only has meaning within =
one ISP.

It's not that different to DSCP semantics, which for example have been =
widely applied across academic networks, except of course the DSCP can =
be rewritten in transit. Whether someone outside the  organisation can =
infer "private" information from the semantics may be an open question.

I think people will do this type of thing, so an Informational document =
discussing the pros and cons, and how semantics can be used, is probably =
a good thing.  Perhaps a "Potential Pitfalls" type section after the =
"Potential Benefits" section would balance the document a little better?

Tim

> Owen
>=20
> On May 29, 2013, at 12:06 AM, Sheng Jiang <jiangsheng@huawei.com> =
wrote:
>=20
>> IP addresses are designed as topology locator, so that every packet =
can be routed to its network destination.
>>=20
>> However, even in IPv4 era, some network operators have mapped their =
IP address with certain semantic locally. These kind of mechanism =
explicitly express the semantic properties of every packet. =
Consequently, these network operators can inspect the properties of =
packets easily by mapping the addresses back to semantic.
>>=20
>> Network operators, who have large IPv6 address space, may also choose =
to embedded some semantics into IPv6 addresses by assigning additional =
significance to specific bits within the prefix. =
draft-jiang-v6ops-semantic-prefix documents a framework method that =
network operations may use their addresses with embedded semantics. =
These semantics bits are only meaningful within a single network, or =
group of interconnected networks which share a common addressing policy. =
Based on these embedded semantic bits in source/destination addresses, =
the network operators can accordingly treat network packets differently =
and efficiently.
>>=20
>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>=20
>> Could you please review this draft and comments? It will help the =
document become more useful information to be shared.
>>=20
>> Best regards,
>>=20
>> Sheng
>>=20
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Tuesday, May 28, 2013 10:28 AM
>>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang
>>> Subject: New Version Notification for
>>> draft-jiang-v6ops-semantic-prefix-03.txt
>>>=20
>>>=20
>>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt
>>> has been successfully submitted by Sheng Jiang and posted to the
>>> IETF repository.
>>>=20
>>> Filename:	 draft-jiang-v6ops-semantic-prefix
>>> Revision:	 03
>>> Title:		 A Framework for Semantic IPv6 Prefix
>>> Creation date:	 2013-05-28
>>> Group:		 Individual Submission
>>> Number of pages: 19
>>> URL:
>>> =
http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03.t=
xt
>>> Status:
>>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>> Diff:
>>> =
http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03
>>>=20
>>> Abstract:
>>> This document describes a framework method that network operations
>>> may use their addresses.  Network operators, who have large IPv6
>>> address space, may choose to embedded some semantics into IPv6
>>> addresses by assigning additional significance to specific bits
>>> within the prefix.  By embedded semantics into IPv6 prefixes, the
>>> semantics of packets can be inspected easily.  Routers and other
>>> intermediary devices can easily apply relevant policies as required.
>>> Packet-level differentiation can also enable flow-level and user-
>>> level differentiation.  Consequently, the network operators can
>>> accordingly treat network packets differently and efficiently.  The
>>> management and maintenance of networks can be much simpler.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From jiangsheng@huawei.com  Wed May 29 23:45:30 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB1A21F9590; Wed, 29 May 2013 23:45:30 -0700 (PDT)
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.100, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XINh+ru8ZDwT; Wed, 29 May 2013 23:45:26 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1F06A21F95F9; Wed, 29 May 2013 23:45:19 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH77537; Thu, 30 May 2013 06:45:14 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 07:44:40 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 14:45:13 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Thu, 30 May 2013 14:45:10 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Duncan, Richard (Jeremy)" <jeremy.duncan@salientfed.com>, Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXNw0JNfUIpIfbEiqc0a18kokB5kdRjJg
Date: Thu, 30 May 2013 06:45:09 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9927B@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>, <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <eg56ow4ob19bwj5507xajo8n.1369880374960@email.android.com>
In-Reply-To: <eg56ow4ob19bwj5507xajo8n.1369880374960@email.android.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 06:45:30 -0000

SGksIER1bmNhbiwNCg0KQWN0dWFsbHksIHlvdSBxdWVzdGlvbiBpcyB2ZXJ5IGRldGFpbGVkIHNj
ZW5hcmlvIGluIHRoZSBhcHByb2FjaC4gVGhlIGFuc3dlciBpcyB0aGUgcHJvdmlkZXIgc3RpbGwg
YXNzaWduIGEgLzQ4IHRvIGFuIG9yZ2FuaXphdGlvbi4gQnV0IHdpdGhpbiB0aGUgYXNzaWduZWQg
LzQ4LCBzb21lIGJpdCAoZm9yIGV4YW1wbGUsIGJpdCBuby4gMzB+MzIpIGhhcyBzb21lIHNlbWFu
dGljIChmb3IgZXhhbXBsZSwgbmVlZCBleHRyYSBzZWN1cml0eSBwcm9jZXNzaW5nKSBmb3IgdGhl
IGFzc2lnbmluZyBwcm92aWRlci4gVGhlbiwgd2hlbiB0aGUgcHJvdmlkZXIgcmVjZWl2ZWQgcGFj
a2V0cyBmcm9tIHN1Y2ggb3JnYW5pemF0aW9ucyAodGhlcmUgYXJlIG11bHRpcGxlIGVudGVycHJp
c2UgaGFzIHRoZSBzYW1lIHNlbWFudGljIGFuZCB0aGUgc2FtZSBiaXQgbm8uIDMwfjMyKSwgaXQg
Y2FuIHRyZWF0IGFjY29yZGluZ2x5Lg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4tLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IER1bmNhbiwgUmljaGFyZCAoSmVyZW15KSBb
bWFpbHRvOmplcmVteS5kdW5jYW5Ac2FsaWVudGZlZC5jb21dDQo+U2VudDogVGh1cnNkYXksIE1h
eSAzMCwgMjAxMyAxMDoyMCBBTQ0KPlRvOiBPd2VuIERlTG9uZw0KPkNjOiBTaGVuZyBKaWFuZzsg
PHY2b3BzQGlldGYub3JnPjsNCj5kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9v
bHMuaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmcNCj5TdWJqZWN0OiBSZTogW3Y2b3BzXSBDb3VsZCBJ
UHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuDQo+bG9jYXRvcj8vL2RyYWZ0LWppYW5nLXY2b3BzLXNl
bWFudGljLXByZWZpeC0wMw0KPg0KPkkgdGVuZCB0byBhZ3JlZSB3aXRoIE93ZW4gaGVyZS4gIElu
IGZhY3QsIEkgYW0gY3VyaW91cyBob3cgYW4gYWxsb2NhdGlvbg0KPmZyb20gYSBwcm92aWRlciB0
byBhIG9yZ2FuaXphdGlvbiB3b3VsZCBsb29rPyAgSW5zdGVhZCBvZiBmb2xsb3dpbmcgc3RhbmRh
cmQNCj5pc3N1aW5nIHByYWN0aWNlcyBvZiBhIC80OCwgYXJlIHlvdSBzdWdnZXN0aW5nIHRoZSBw
cm92aWRlciB3b3VsZCBpc3N1ZQ0KPm11bHRpcGxlIC81MnMgdGhhdCBmb2xsb3cgZnVuY3Rpb25h
bCBjYXRlZ29yaWVzIChWb0lQLCBtYW5hZ2VtZW50LCBldGMpPyAgT3INCj5tYXliZSBJIG1pc3Nl
ZCBzb21ldGhpbmc/DQo+DQo+DQo+MDEwMTAwMTEwMTEwMDEwMTAxMTAxMTAxMDExMTAwMDAwMTEw
MDEwMTAxMTEwMDEwMDAxMDAwMDAwMTAwMDExDQo+MDAxMTAxMDAxDQo+DQo+SmVyZW15IER1bmNh
bg0KPlNlbmlvciBEaXJlY3RvciwgSVB2NiBOZXR3b3JrIEFyY2hpdGVjdA0KPlNhbGllbnQgRmVk
ZXJhbCBTb2x1dGlvbnMsIEluYy4gKE5vdyBpbmNsdWRpbmcgU0dJUyAmIENvbW1hbmQgSW5mb3Jt
YXRpb24NCj5JbmMuKQ0KPjQwMDAgTGVnYXRvIFJvYWQsIFN1aXRlIDYwMA0KPkZhaXJmYXgsIFZB
IDIyMDMzDQo+R29vZ2xlIFZvaWNlOiA1NDAuNDQwLjExOTMNCj5qZXJlbXkuZHVuY2FuQHNhbGll
bnRmZWQuY29tDQo+DQo+T3dlbiBEZUxvbmcgPG93ZW5AZGVsb25nLmNvbT4gd3JvdGU6DQo+DQo+
DQo+UGVyc29uYWxseSwgSSB0aGluayB0aGlzIGlzIGFuIGluaGVyZW50bHkgYmFkIGlkZWEuDQo+
DQo+SVAgYWRkcmVzc2VzIG5lZWQgbGVzcyBvdmVybG9hZGluZyBvZiBzZW1hbnRpY3MsIG5vdCBt
b3JlLg0KPg0KPldlIGFscmVhZHkgdXNlIElQIGFkZHJlc3NlcyBmb3IgdHdvIGNvbmZsaWN0aW5n
IHB1cnBvc2Vz4oCmIFRvcG9sb2d5IGxvY2F0b3INCj5hbmQgRW5kIFN5c3RlbSBJZGVudGlmaWVy
Lg0KPg0KPlRoaXMgb3ZlcmxvYWRpbmcgaXMgYXQgdGhlIGhlYXJ0IG9mIG91ciBjdXJyZW50IHNj
YWxpbmcgaXNzdWVzIHdpdGggcmVzcGVjdCB0bw0KPnRoZSByb3V0aW5nIHRhYmxlLiBXaGlsZSB0
aGVzZSBpc3N1ZXMgYXJlIGN1cnJlbnRseSBsZXNzIGNyaXRpY2FsIHRoYW4gdGhleSBoYXZlDQo+
YmVlbiBpbiB0aGUgcGFzdCBhbmQgd2lsbCBsaWtlbHkgZ2V0IHF1aXRlIGEgYml0IGxlc3MgY3Jp
dGljYWwgaW4gSVB2NiwgdGhhdCBpcyBvbmx5DQo+YmVjYXVzZSB3ZSBoYXZlIGdpdmVuIHVwIGEg
ZmFpciBhbW91bnQgb2YgZnVuY3Rpb25hbGl0eSB0byBwcmVzZXJ2ZQ0KPnNjYWxhYmlsaXR5IGlu
IHRoaXMgcmVnYXJkLg0KPg0KPklmIHdlIGRpZCBub3QgaGF2ZSB0aGlzIG92ZXJsb2FkaW5nLCB0
aGVuIGFuIGVudGl0eSBjb3VsZCBvYnRhaW4gYSBzZXQgb2YNCj5lbmQtc3lzdGVtIGlkZW50aWZp
ZXJzIGFuZCBrZWVwIHRoZW0gdGhyb3VnaG91dCB0aGVpciBsaWZldGltZSwgcmVnYXJkbGVzcyBv
Zg0KPnRvcG9sb2dpY2FsIGNoYW5nZXMuIFRvZGF5LCB3aGVyZSB0aGUgYWRkcmVzc2VzIGFyZSBv
dmVybG9hZGVkIHdpdGggYm90aA0KPnNlbWFudGljcywgd2UgZWl0aGVyIGhhdmUgdG8gZm9yY2Ug
bW9zdCBlbnRpdGllcyB0byBjaGFuZ2UgdGhlaXIgbnVtYmVycw0KPndoZW4gdGhleSBjaGFuZ2Ug
dG9wb2xvZ3kgb3Igd2UgZmFjZSB1bnN1c3RhaW5hYmxlIGdyb3d0aCBpbiB0aGUgcm91dGluZw0K
PnRhYmxlcy4NCj4NCj5UaGUgaWRlYSBvZiBhZGRpbmcgbW9yZSBzZW1hbnRpY3MgdG8gYWRkcmVz
c2luZyByYXRoZXIgdGhhbiBzZWVraW5nIHRvDQo+cmVkdWNlIHRoaXMgb3ZlcmxvYWRpbmcgc2Vl
bXMgYSBzdGVwIGluIHRoZSB3cm9uZyBkaXJlY3Rpb24sIElNSE8uDQo+DQo+T3dlbg0KPg0KPk9u
IE1heSAyOSwgMjAxMywgYXQgMTI6MDYgQU0sIFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdl
aS5jb20+DQo+d3JvdGU6DQo+DQo+PiBJUCBhZGRyZXNzZXMgYXJlIGRlc2lnbmVkIGFzIHRvcG9s
b2d5IGxvY2F0b3IsIHNvIHRoYXQgZXZlcnkgcGFja2V0IGNhbiBiZQ0KPnJvdXRlZCB0byBpdHMg
bmV0d29yayBkZXN0aW5hdGlvbi4NCj4+DQo+PiBIb3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBz
b21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyIElQDQo+YWRkcmVzcyB3aXRo
IGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5pc20gZXhwbGlj
aXRseQ0KPmV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRpZXMgb2YgZXZlcnkgcGFja2V0LiBD
b25zZXF1ZW50bHksIHRoZXNlIG5ldHdvcmsNCj5vcGVyYXRvcnMgY2FuIGluc3BlY3QgdGhlIHBy
b3BlcnRpZXMgb2YgcGFja2V0cyBlYXNpbHkgYnkgbWFwcGluZyB0aGUNCj5hZGRyZXNzZXMgYmFj
ayB0byBzZW1hbnRpYy4NCj4+DQo+PiBOZXR3b3JrIG9wZXJhdG9ycywgd2hvIGhhdmUgbGFyZ2Ug
SVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbyBjaG9vc2UgdG8NCj5lbWJlZGRlZCBzb21lIHNl
bWFudGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGJ5IGFzc2lnbmluZyBhZGRpdGlvbmFsDQo+c2ln
bmlmaWNhbmNlIHRvIHNwZWNpZmljIGJpdHMgd2l0aGluIHRoZSBwcmVmaXguDQo+ZHJhZnQtamlh
bmctdjZvcHMtc2VtYW50aWMtcHJlZml4IGRvY3VtZW50cyBhIGZyYW1ld29yayBtZXRob2QgdGhh
dA0KPm5ldHdvcmsgb3BlcmF0aW9ucyBtYXkgdXNlIHRoZWlyIGFkZHJlc3NlcyB3aXRoIGVtYmVk
ZGVkIHNlbWFudGljcy4gVGhlc2UNCj5zZW1hbnRpY3MgYml0cyBhcmUgb25seSBtZWFuaW5nZnVs
IHdpdGhpbiBhIHNpbmdsZSBuZXR3b3JrLCBvciBncm91cCBvZg0KPmludGVyY29ubmVjdGVkIG5l
dHdvcmtzIHdoaWNoIHNoYXJlIGEgY29tbW9uIGFkZHJlc3NpbmcgcG9saWN5LiBCYXNlZCBvbg0K
PnRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMgaW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJl
c3NlcywgdGhlIG5ldHdvcmsNCj5vcGVyYXRvcnMgY2FuIGFjY29yZGluZ2x5IHRyZWF0IG5ldHdv
cmsgcGFja2V0cyBkaWZmZXJlbnRseSBhbmQgZWZmaWNpZW50bHkuDQo+Pg0KPj4gaHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+
Pg0KPj4gQ291bGQgeW91IHBsZWFzZSByZXZpZXcgdGhpcyBkcmFmdCBhbmQgY29tbWVudHM/IEl0
IHdpbGwgaGVscCB0aGUgZG9jdW1lbnQNCj5iZWNvbWUgbW9yZSB1c2VmdWwgaW5mb3JtYXRpb24g
dG8gYmUgc2hhcmVkLg0KPj4NCj4+IEJlc3QgcmVnYXJkcywNCj4+DQo+PiBTaGVuZw0KPj4NCj4+
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+IEZyb206IGludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4+PiBTZW50OiBUdWVz
ZGF5LCBNYXkgMjgsIDIwMTMgMTA6MjggQU0NCj4+PiBUbzogUWlvbmcgU3VuOyBJYW4gRmFycmVy
OyBTaGVuZyBKaWFuZzsgQm95YW5nDQo+Pj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0
aW9uIGZvcg0KPj4+IGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMy50eHQNCj4+
Pg0KPj4+DQo+Pj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFu
dGljLXByZWZpeC0wMy50eHQNCj4+PiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5
IFNoZW5nIEppYW5nIGFuZCBwb3N0ZWQgdG8gdGhlDQo+Pj4gSUVURiByZXBvc2l0b3J5Lg0KPj4+
DQo+Pj4gRmlsZW5hbWU6ICAgICBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgNCj4+
PiBSZXZpc2lvbjogICAgIDAzDQo+Pj4gVGl0bGU6ICAgICAgICAgICAgICAgIEEgRnJhbWV3b3Jr
IGZvciBTZW1hbnRpYyBJUHY2IFByZWZpeA0KPj4+IENyZWF0aW9uIGRhdGU6ICAgICAgICAyMDEz
LTA1LTI4DQo+Pj4gR3JvdXA6ICAgICAgICAgICAgICAgIEluZGl2aWR1YWwgU3VibWlzc2lvbg0K
Pj4+IE51bWJlciBvZiBwYWdlczogMTkNCj4+PiBVUkw6DQo+Pj4NCj5odHRwOi8vd3d3LmlldGYu
b3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMu
dHh0DQo+Pj4gU3RhdHVzOg0KPj4+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4DQo+Pj4gSHRtbGl6ZWQ6DQo+Pj4gaHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAz
DQo+Pj4gRGlmZjoNCj4+PiBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1q
aWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMNCj4+Pg0KPj4+IEFic3RyYWN0Og0KPj4+ICBU
aGlzIGRvY3VtZW50IGRlc2NyaWJlcyBhIGZyYW1ld29yayBtZXRob2QgdGhhdCBuZXR3b3JrIG9w
ZXJhdGlvbnMNCj4+PiAgbWF5IHVzZSB0aGVpciBhZGRyZXNzZXMuICBOZXR3b3JrIG9wZXJhdG9y
cywgd2hvIGhhdmUgbGFyZ2UgSVB2Ng0KPj4+ICBhZGRyZXNzIHNwYWNlLCBtYXkgY2hvb3NlIHRv
IGVtYmVkZGVkIHNvbWUgc2VtYW50aWNzIGludG8gSVB2Ng0KPj4+ICBhZGRyZXNzZXMgYnkgYXNz
aWduaW5nIGFkZGl0aW9uYWwgc2lnbmlmaWNhbmNlIHRvIHNwZWNpZmljIGJpdHMNCj4+PiAgd2l0
aGluIHRoZSBwcmVmaXguICBCeSBlbWJlZGRlZCBzZW1hbnRpY3MgaW50byBJUHY2IHByZWZpeGVz
LCB0aGUNCj4+PiAgc2VtYW50aWNzIG9mIHBhY2tldHMgY2FuIGJlIGluc3BlY3RlZCBlYXNpbHku
ICBSb3V0ZXJzIGFuZCBvdGhlcg0KPj4+ICBpbnRlcm1lZGlhcnkgZGV2aWNlcyBjYW4gZWFzaWx5
IGFwcGx5IHJlbGV2YW50IHBvbGljaWVzIGFzIHJlcXVpcmVkLg0KPj4+ICBQYWNrZXQtbGV2ZWwg
ZGlmZmVyZW50aWF0aW9uIGNhbiBhbHNvIGVuYWJsZSBmbG93LWxldmVsIGFuZCB1c2VyLQ0KPj4+
ICBsZXZlbCBkaWZmZXJlbnRpYXRpb24uICBDb25zZXF1ZW50bHksIHRoZSBuZXR3b3JrIG9wZXJh
dG9ycyBjYW4NCj4+PiAgYWNjb3JkaW5nbHkgdHJlYXQgbmV0d29yayBwYWNrZXRzIGRpZmZlcmVu
dGx5IGFuZCBlZmZpY2llbnRseS4gIFRoZQ0KPj4+ICBtYW5hZ2VtZW50IGFuZCBtYWludGVuYW5j
ZSBvZiBuZXR3b3JrcyBjYW4gYmUgbXVjaCBzaW1wbGVyLg0KPj4+DQo+Pj4NCj4+Pg0KPj4+DQo+
Pj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCj4+DQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPj4gdjZvcHMgbWFpbGluZyBsaXN0DQo+PiB2Nm9wc0Bp
ZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0K
Pg0KPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tDQo+SUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQo+
aXB2NkBpZXRmLm9yZw0KPkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYNCj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KDQo=

From lorenzo@google.com  Wed May 29 23:47:59 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9900F21F94BA for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 23:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WA83MHp7NJES for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 23:47:59 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 045F121F9467 for <ipv6@ietf.org>; Wed, 29 May 2013 23:47:57 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id fb19so4907543obc.9 for <ipv6@ietf.org>; Wed, 29 May 2013 23:47:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zqkpCqqa2dBuyl9d+q6N4iR+cg85d9vMFhTSZeVaUCM=; b=UogYVuPKMbMWOSp5bs3HFEZfYpGmiIIY8T4srgzp6I0107HlCVrF7/Aw5Xf8D2k9vW NuOdDkUBFuXwDt8NA1hic1FRLpOseecx7yvRdPP2cMiZiD+7UZYF4N43qABbE9Y7nRAV Ykd4N1uC+ffLnspPov+/Ovf8uCUwdtLCpvuK4TlGC1RoxnCzlwBOKiNVablowprd6bd+ qEk2v8SCRw8m329lCcDrkFLqmvGGVIMCvXoxfr2KWrKIjBRYhy7DbKmcTyStYCzx5AcT 3E+SbchtIYMagSv8OFModEf5TCtkPGqI/7XqXs6QveTIWbWNTqkhRgSvhDrYsHo4xoyU WvVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=zqkpCqqa2dBuyl9d+q6N4iR+cg85d9vMFhTSZeVaUCM=; b=Qi19HOrTqHfIoJo2plVKnAcihT+qupkL+ucwD7a90D4fs75enhLED+kHbMeiAfzmmW 3gbwYqF54IykVXnaboyZ1wtyk4dT7wxyiRdnyoe5nwgloSa/RciPxHEC23TEEP/ioQOK YsVNZhtuGKiUI8Vr6HtePsUg5YzGJLuJ/Vwb74g/WKM76drti4Vu/Qgt2wj4ak13K9pq 0HBoDlAvDFZq2vwZvrWThrdTRc+FwvxRSydrwwSje+1myW4bWCsiqPZ9RsECRBMyGo/b 8yGPdIqpQWI9VbQ6uT4rnsF9oqUA/yXfLGa3+5ykT3hMoWETM+1aQ70/cvUCYfjBP6se 3SAA==
X-Received: by 10.60.141.231 with SMTP id rr7mr3451249oeb.77.1369896477565; Wed, 29 May 2013 23:47:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.146.47 with HTTP; Wed, 29 May 2013 23:47:37 -0700 (PDT)
In-Reply-To: <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 30 May 2013 15:47:37 +0900
Message-ID: <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=047d7b339a3fecc88304dde9e074
X-Gm-Message-State: ALoCoQk2My1XZP8bq79hkIO06O0PxlynOq+hWc21G9huuWCFnkpbSYqDVEDJyD+2awUak0EzUSk5nkZUWOnrSHFJiNQgNzV+ur/k5BWBB2T+9AJOBCHGhgtZPoKBMq9wmkHAmWLPnFXaqgFIkrqjyeOccTBDTbhyJTUImLZbf2R9LaIupdrqeomEU9kk/9fhyB38XWTp20T0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 06:47:59 -0000

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

On Thu, May 30, 2013 at 3:33 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> I agree. That said, an ISP, enterprise or group of organisations can
> follow whatever semantics they wish within their own borders.
>

As long as the RIRs are willing to give them enough address space to do so.

If an ISP requested an IPv6 /10 from ARIN because they wanted to give every
customer a /48 and wanted to geocode the customer's subscriber ID into the
/48, then ARIN would do well to say, "no, sorry, that doesn't make sense".

Lest someone not realize this, the draft should clearly state that
embedding N bits of semantics into IPv6 addresses causes the network to use
2^N times the address space that it normally would.

IMO I think it should also state that although it is an IETF RFC, this
model is not necessarily a recommended model, and that RIRs are not obliged
to accept this type of address allocation as a justification for obtaining
larger address blocks than they would normally be able to obtain.

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

<div dir=3D"ltr">On Thu, May 30, 2013 at 3:33 PM, Tim Chown <span dir=3D"lt=
r">&lt;<a href=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.sot=
on.ac.uk</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(3=
4,34,34)">I agree. That said, an ISP, enterprise or group of organisations =
can follow whatever semantics they wish within their own borders.</span></d=
iv>

</blockquote><div><br></div><div style>As long as the RIRs are willing to g=
ive them enough address space to do so.</div><div style><br></div><div styl=
e>If an ISP requested an IPv6 /10 from ARIN because they wanted to give eve=
ry customer a /48 and wanted to geocode the customer&#39;s subscriber ID in=
to the /48, then ARIN would do well to say, &quot;no, sorry, that doesn&#39=
;t make sense&quot;.</div>

<div style><br></div><div style>Lest someone not realize this, the draft sh=
ould clearly state that embedding N bits of semantics into IPv6 addresses c=
auses the network to use 2^N times the address space that it normally would=
.</div>

<div style><br></div><div style>IMO I think it should also state that altho=
ugh it is an IETF RFC, this model is not necessarily a recommended model, a=
nd that RIRs are not obliged to accept this type of address allocation as a=
 justification for obtaining larger address blocks than they would normally=
 be able to obtain.</div>

</div></div></div>

--047d7b339a3fecc88304dde9e074--

From ggm@algebras.org  Wed May 29 23:55:50 2013
Return-Path: <ggm@algebras.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 230A821F939E for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 23:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level: 
X-Spam-Status: No, score=-1.676 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j0WduPvkWo36 for <ipv6@ietfa.amsl.com>; Wed, 29 May 2013 23:55:45 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id EB3DA21F9590 for <ipv6@ietf.org>; Wed, 29 May 2013 23:55:44 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so10016160pdi.8 for <ipv6@ietf.org>; Wed, 29 May 2013 23:55:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=yu4fFl1x0mPnM1BdW6vtZsZGrkn07Wwnent5354ZMPc=; b=omO8idoQst6YUibFwNH+IprjfLh3R5uPT2n+i4E1jZ1xIfQWVtiJ1n5TS8omGE0tXp A/i9B5z/nu1smL1fT/F5TDWIaSYEUFRDC2zXzbvASQcXKwtMMPtRnnqEXniTNptzbnaW MfdqQvAeBfXnIEFy9srEPqUbX0EAAnB+jT1pfaoWXAivYxBlwXxKrMn3k29Ix3TLL1Ai HqTmU8fa1q2Wicq+4nHxLB46ceTzpIQBX+Pc6rlzswoj9qMH1XS2XLxK+zWI+GLWgrKg olFd0qJW7p7EGRXDCxHICM4SLbjJPJjTAJFAL+sTfwRyTb1D1caoEQdVAZ8Zqf0uAd5J TWNw==
MIME-Version: 1.0
X-Received: by 10.68.212.196 with SMTP id nm4mr6506931pbc.216.1369896941634; Wed, 29 May 2013 23:55:41 -0700 (PDT)
Received: by 10.70.25.195 with HTTP; Wed, 29 May 2013 23:55:41 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:8d02:94ac:45f4:abe8]
In-Reply-To: <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
Date: Thu, 30 May 2013 16:55:41 +1000
Message-ID: <CAKr6gn0QeTyQ54a4MRc_HK=X+1-2tXYf2PXqTWc-H=Hox4ojeA@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: George Michaelson <ggm@algebras.org>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=e89a8ff1c13a95d89c04dde9fc2a
X-Gm-Message-State: ALoCoQm7yCahxE64w5/75i4IVAkBp2IhhxvujywJ5V83DH2zmxoh/C8zjzt3ZEH6AwSrGLReK7U1
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 06:55:50 -0000

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

Which is pretty much what was said to mike, when this came up in the WG 2
IETFs ago. Overloading parts of the allocation space under your /32 makes a
complete mockery of the process model which justified the /32 based on /56
or /48 consumption plans, and while the H/D ratio is a somewhat rei-fied
number, this kind of scheme will alter consumption of the address space
massively.

That some large ISPs and network operators *want* to overload bits in the
address to have meaning? Sure. I can believe that. That vendors, knowing
this, *want* to encode logic into sold routers, devices, to exploit this?
Sure. I can believe that.

is it a good architecture? No. I cannot currently believe that.

-george


On Thu, May 30, 2013 at 4:47 PM, Lorenzo Colitti <lorenzo@google.com> wrote:

> On Thu, May 30, 2013 at 3:33 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>
>> I agree. That said, an ISP, enterprise or group of organisations can
>> follow whatever semantics they wish within their own borders.
>>
>
> As long as the RIRs are willing to give them enough address space to do so.
>
> If an ISP requested an IPv6 /10 from ARIN because they wanted to give
> every customer a /48 and wanted to geocode the customer's subscriber ID
> into the /48, then ARIN would do well to say, "no, sorry, that doesn't make
> sense".
>
> Lest someone not realize this, the draft should clearly state that
> embedding N bits of semantics into IPv6 addresses causes the network to use
> 2^N times the address space that it normally would.
>
> IMO I think it should also state that although it is an IETF RFC, this
> model is not necessarily a recommended model, and that RIRs are not obliged
> to accept this type of address allocation as a justification for obtaining
> larger address blocks than they would normally be able to obtain.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

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

<div dir=3D"ltr">Which is pretty much what was said to mike, when this came=
 up in the WG 2 IETFs ago. Overloading parts of the allocation space under =
your /32 makes a complete mockery of the process model which justified the =
/32 based on /56 or /48 consumption plans, and while the H/D ratio is a som=
ewhat rei-fied number, this kind of scheme will alter consumption of the ad=
dress space massively.<div>
<br></div><div style>That some large ISPs and network operators *want* to o=
verload bits in the address to have meaning? Sure. I can believe that. That=
 vendors, knowing this, *want* to encode logic into sold routers, devices, =
to exploit this? Sure. I can believe that.</div>
<div style><br></div><div style>is it a good architecture? No. I cannot cur=
rently believe that.</div><div style><br></div><div style>-george</div></di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, May=
 30, 2013 at 4:47 PM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"mail=
to:lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Thu, M=
ay 30, 2013 at 3:33 PM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:t=
jc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wr=
ote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><span style=3D"color:rgb(34,34,34)">I a=
gree. That said, an ISP, enterprise or group of organisations can follow wh=
atever semantics they wish within their own borders.</span></div>


</blockquote><div><br></div></div><div>As long as the RIRs are willing to g=
ive them enough address space to do so.</div><div><br></div><div>If an ISP =
requested an IPv6 /10 from ARIN because they wanted to give every customer =
a /48 and wanted to geocode the customer&#39;s subscriber ID into the /48, =
then ARIN would do well to say, &quot;no, sorry, that doesn&#39;t make sens=
e&quot;.</div>


<div><br></div><div>Lest someone not realize this, the draft should clearly=
 state that embedding N bits of semantics into IPv6 addresses causes the ne=
twork to use 2^N times the address space that it normally would.</div>


<div><br></div><div>IMO I think it should also state that although it is an=
 IETF RFC, this model is not necessarily a recommended model, and that RIRs=
 are not obliged to accept this type of address allocation as a justificati=
on for obtaining larger address blocks than they would normally be able to =
obtain.</div>


</div></div></div>
<br>_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
<br></blockquote></div><br></div>

--e89a8ff1c13a95d89c04dde9fc2a--

From jiangsheng@huawei.com  Thu May 30 00:01:11 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9B521F96AC; Thu, 30 May 2013 00:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.074
X-Spam-Level: 
X-Spam-Status: No, score=-6.074 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cMcWd25OrXMC; Thu, 30 May 2013 00:01:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 48F9221F96AA; Thu, 30 May 2013 00:01:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH78915; Thu, 30 May 2013 07:01:04 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:00:30 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 15:01:03 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Thu, 30 May 2013 15:01:00 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAIm9sA==
Date: Thu, 30 May 2013 07:00:59 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:01:11 -0000

Pj4gSVAgYWRkcmVzc2VzIG5lZWQgbGVzcyBvdmVybG9hZGluZyBvZiBzZW1hbnRpY3MsIG5vdCBt
b3JlLg0KPj4NCj4+IFdlIGFscmVhZHkgdXNlIElQIGFkZHJlc3NlcyBmb3IgdHdvIGNvbmZsaWN0
aW5nIHB1cnBvc2Vz4oCmIFRvcG9sb2d5IGxvY2F0b3INCj5hbmQgRW5kIFN5c3RlbSBJZGVudGlm
aWVyLg0KPj4NCj4+IFRoaXMgb3ZlcmxvYWRpbmcgaXMgYXQgdGhlIGhlYXJ0IG9mIG91ciBjdXJy
ZW50IHNjYWxpbmcgaXNzdWVzIHdpdGggcmVzcGVjdCB0bw0KPnRoZSByb3V0aW5nIHRhYmxlLiBX
aGlsZSB0aGVzZSBpc3N1ZXMgYXJlIGN1cnJlbnRseSBsZXNzIGNyaXRpY2FsIHRoYW4gdGhleSBo
YXZlDQo+YmVlbiBpbiB0aGUgcGFzdCBhbmQgd2lsbCBsaWtlbHkgZ2V0IHF1aXRlIGEgYml0IGxl
c3MgY3JpdGljYWwgaW4gSVB2NiwgdGhhdCBpcyBvbmx5DQo+YmVjYXVzZSB3ZSBoYXZlIGdpdmVu
IHVwIGEgZmFpciBhbW91bnQgb2YgZnVuY3Rpb25hbGl0eSB0byBwcmVzZXJ2ZQ0KPnNjYWxhYmls
aXR5IGluIHRoaXMgcmVnYXJkLg0KPj4NCj4+IElmIHdlIGRpZCBub3QgaGF2ZSB0aGlzIG92ZXJs
b2FkaW5nLCB0aGVuIGFuIGVudGl0eSBjb3VsZCBvYnRhaW4gYSBzZXQgb2YNCj5lbmQtc3lzdGVt
IGlkZW50aWZpZXJzIGFuZCBrZWVwIHRoZW0gdGhyb3VnaG91dCB0aGVpciBsaWZldGltZSwgcmVn
YXJkbGVzcyBvZg0KPnRvcG9sb2dpY2FsIGNoYW5nZXMuIFRvZGF5LCB3aGVyZSB0aGUgYWRkcmVz
c2VzIGFyZSBvdmVybG9hZGVkIHdpdGggYm90aA0KPnNlbWFudGljcywgd2UgZWl0aGVyIGhhdmUg
dG8gZm9yY2UgbW9zdCBlbnRpdGllcyB0byBjaGFuZ2UgdGhlaXIgbnVtYmVycw0KPndoZW4gdGhl
eSBjaGFuZ2UgdG9wb2xvZ3kgb3Igd2UgZmFjZSB1bnN1c3RhaW5hYmxlIGdyb3d0aCBpbiB0aGUg
cm91dGluZw0KPnRhYmxlcy4NCj4+DQo+PiBUaGUgaWRlYSBvZiBhZGRpbmcgbW9yZSBzZW1hbnRp
Y3MgdG8gYWRkcmVzc2luZyByYXRoZXIgdGhhbiBzZWVraW5nIHRvDQo+cmVkdWNlIHRoaXMgb3Zl
cmxvYWRpbmcgc2VlbXMgYSBzdGVwIGluIHRoZSB3cm9uZyBkaXJlY3Rpb24sIElNSE8uDQo+DQo+
SSBhZ3JlZS4gVGhhdCBzYWlkLCBhbiBJU1AsIGVudGVycHJpc2Ugb3IgZ3JvdXAgb2Ygb3JnYW5p
c2F0aW9ucyBjYW4gZm9sbG93DQo+d2hhdGV2ZXIgc2VtYW50aWNzIHRoZXkgd2lzaCB3aXRoaW4g
dGhlaXIgb3duIGJvcmRlcnMuIEp1c3QgZG9uJ3QgZXhwZWN0DQo+YW55b25lIGVsc2UgdG8gZm9s
bG93IG9yIHVzZSB0aG9zZSBzZW1hbnRpY3MuICBXaGF0IFNoZW5nIGlzIHByb3Bvc2luZyBpcw0K
PmNsZWFybHkgc3RhdGVkIGFzIG9ubHkgYmVpbmcgZm9yIGludGVycHJldGF0aW9uIGJldHdlZW4g
YWdyZWVpbmcNCj5vcmdhbmlzYXRpb25zLg0KDQpIaSwgVGltLA0KDQpJdCBpcyBleGFjdGx5IHdo
YXQgdGhlIGRyYWZ0IGRvY3VtZW50LiBUaGVzZSBzZW1hbnRpY3MgaXMgb25seSBtZWFuaW5nZnVs
IGxvY2FsbHkgd2l0aGluIHRoZSBhc3NpZ25pbmcgcHJvdmlkZXIgbmV0d29yay4gSXQgbWF5IG9u
bHkgYmUgaW50ZXJwcmV0YXRpb24gYmV0d2VlbiBhZ3JlZWluZyBwcm92aWRlcnMuDQoNCkFueSBl
ZmZvcnRzIHRvIGFkZCBnbG9iYWwgb3IgZ2VuZXJpYyBzZW1hbnRpY3MgdG8gSVAgYWRkcmVzcyBp
cyBvdmVybG9hZCB0aGUgSVAgYXJjaGl0ZWN0dXJlIGFuZCBpdCBiYWQgZGlyZWN0aW9uLCBJIGFn
cmVlLg0KDQo+SSB0aGluayBwZW9wbGUgd2lsbCBkbyB0aGlzIHR5cGUgb2YgdGhpbmcsIHNvIGFu
IEluZm9ybWF0aW9uYWwgZG9jdW1lbnQNCj5kaXNjdXNzaW5nIHRoZSBwcm9zIGFuZCBjb25zLCBh
bmQgaG93IHNlbWFudGljcyBjYW4gYmUgdXNlZCwgaXMgcHJvYmFibHkgYQ0KPmdvb2QgdGhpbmcu
ICBQZXJoYXBzIGEgIlBvdGVudGlhbCBQaXRmYWxscyIgdHlwZSBzZWN0aW9uIGFmdGVyIHRoZSAi
UG90ZW50aWFsDQo+QmVuZWZpdHMiIHNlY3Rpb24gd291bGQgYmFsYW5jZSB0aGUgZG9jdW1lbnQg
YSBsaXR0bGUgYmV0dGVyPw0KDQpZZXMuIFdlIHdpbGwgZG8gc28gaW4gdGhlIGZ1dHVyZSB2ZXJz
aW9uLiANCg0KQ2hlZXJzLA0KDQpTaGVuZw0KDQo+VGltDQo+DQo+PiBPd2VuDQo+Pg0KPj4gT24g
TWF5IDI5LCAyMDEzLCBhdCAxMjowNiBBTSwgU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdAaHVhd2Vp
LmNvbT4NCj53cm90ZToNCj4+DQo+Pj4gSVAgYWRkcmVzc2VzIGFyZSBkZXNpZ25lZCBhcyB0b3Bv
bG9neSBsb2NhdG9yLCBzbyB0aGF0IGV2ZXJ5IHBhY2tldCBjYW4gYmUNCj5yb3V0ZWQgdG8gaXRz
IG5ldHdvcmsgZGVzdGluYXRpb24uDQo+Pj4NCj4+PiBIb3dldmVyLCBldmVuIGluIElQdjQgZXJh
LCBzb21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyIElQDQo+YWRkcmVzcyB3
aXRoIGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5pc20gZXhw
bGljaXRseQ0KPmV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRpZXMgb2YgZXZlcnkgcGFja2V0
LiBDb25zZXF1ZW50bHksIHRoZXNlIG5ldHdvcmsNCj5vcGVyYXRvcnMgY2FuIGluc3BlY3QgdGhl
IHByb3BlcnRpZXMgb2YgcGFja2V0cyBlYXNpbHkgYnkgbWFwcGluZyB0aGUNCj5hZGRyZXNzZXMg
YmFjayB0byBzZW1hbnRpYy4NCj4+Pg0KPj4+IE5ldHdvcmsgb3BlcmF0b3JzLCB3aG8gaGF2ZSBs
YXJnZSBJUHY2IGFkZHJlc3Mgc3BhY2UsIG1heSBhbHNvIGNob29zZQ0KPnRvIGVtYmVkZGVkIHNv
bWUgc2VtYW50aWNzIGludG8gSVB2NiBhZGRyZXNzZXMgYnkgYXNzaWduaW5nIGFkZGl0aW9uYWwN
Cj5zaWduaWZpY2FuY2UgdG8gc3BlY2lmaWMgYml0cyB3aXRoaW4gdGhlIHByZWZpeC4NCj5kcmFm
dC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXggZG9jdW1lbnRzIGEgZnJhbWV3b3JrIG1ldGhv
ZCB0aGF0DQo+bmV0d29yayBvcGVyYXRpb25zIG1heSB1c2UgdGhlaXIgYWRkcmVzc2VzIHdpdGgg
ZW1iZWRkZWQgc2VtYW50aWNzLiBUaGVzZQ0KPnNlbWFudGljcyBiaXRzIGFyZSBvbmx5IG1lYW5p
bmdmdWwgd2l0aGluIGEgc2luZ2xlIG5ldHdvcmssIG9yIGdyb3VwIG9mDQo+aW50ZXJjb25uZWN0
ZWQgbmV0d29ya3Mgd2hpY2ggc2hhcmUgYSBjb21tb24gYWRkcmVzc2luZyBwb2xpY3kuIEJhc2Vk
IG9uDQo+dGhlc2UgZW1iZWRkZWQgc2VtYW50aWMgYml0cyBpbiBzb3VyY2UvZGVzdGluYXRpb24g
YWRkcmVzc2VzLCB0aGUgbmV0d29yaw0KPm9wZXJhdG9ycyBjYW4gYWNjb3JkaW5nbHkgdHJlYXQg
bmV0d29yayBwYWNrZXRzIGRpZmZlcmVudGx5IGFuZCBlZmZpY2llbnRseS4NCj4+Pg0KPj4+IGh0
dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZp
eC0wMw0KPj4+DQo+Pj4gQ291bGQgeW91IHBsZWFzZSByZXZpZXcgdGhpcyBkcmFmdCBhbmQgY29t
bWVudHM/IEl0IHdpbGwgaGVscCB0aGUNCj5kb2N1bWVudCBiZWNvbWUgbW9yZSB1c2VmdWwgaW5m
b3JtYXRpb24gdG8gYmUgc2hhcmVkLg0KPj4+DQo+Pj4gQmVzdCByZWdhcmRzLA0KPj4+DQo+Pj4g
U2hlbmcNCj4+Pg0KPj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+PiBGcm9tOiBp
bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmdd
DQo+Pj4+IFNlbnQ6IFR1ZXNkYXksIE1heSAyOCwgMjAxMyAxMDoyOCBBTQ0KPj4+PiBUbzogUWlv
bmcgU3VuOyBJYW4gRmFycmVyOyBTaGVuZyBKaWFuZzsgQm95YW5nDQo+Pj4+IFN1YmplY3Q6IE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3INCj4+Pj4gZHJhZnQtamlhbmctdjZvcHMtc2VtYW50
aWMtcHJlZml4LTAzLnR4dA0KPj4+Pg0KPj4+Pg0KPj4+PiBBIG5ldyB2ZXJzaW9uIG9mIEktRCwg
ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzLnR4dA0KPj4+PiBoYXMgYmVlbiBz
dWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNoZW5nIEppYW5nIGFuZCBwb3N0ZWQgdG8gdGhlDQo+
Pj4+IElFVEYgcmVwb3NpdG9yeS4NCj4+Pj4NCj4+Pj4gRmlsZW5hbWU6CSBkcmFmdC1qaWFuZy12
Nm9wcy1zZW1hbnRpYy1wcmVmaXgNCj4+Pj4gUmV2aXNpb246CSAwMw0KPj4+PiBUaXRsZToJCSBB
IEZyYW1ld29yayBmb3IgU2VtYW50aWMgSVB2NiBQcmVmaXgNCj4+Pj4gQ3JlYXRpb24gZGF0ZToJ
IDIwMTMtMDUtMjgNCj4+Pj4gR3JvdXA6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+Pj4+IE51
bWJlciBvZiBwYWdlczogMTkNCj4+Pj4gVVJMOg0KPj4+Pg0KPmh0dHA6Ly93d3cuaWV0Zi5vcmcv
aW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMy50eHQN
Cj4+Pj4gU3RhdHVzOg0KPj4+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeA0KPj4+PiBIdG1saXplZDoNCj4+Pj4gaHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAz
DQo+Pj4+IERpZmY6DQo+Pj4+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0
LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0KPj4+Pg0KPj4+PiBBYnN0cmFjdDoNCj4+
Pj4gVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBmcmFtZXdvcmsgbWV0aG9kIHRoYXQgbmV0d29y
ayBvcGVyYXRpb25zDQo+Pj4+IG1heSB1c2UgdGhlaXIgYWRkcmVzc2VzLiAgTmV0d29yayBvcGVy
YXRvcnMsIHdobyBoYXZlIGxhcmdlIElQdjYNCj4+Pj4gYWRkcmVzcyBzcGFjZSwgbWF5IGNob29z
ZSB0byBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYNCj4+Pj4gYWRkcmVzc2VzIGJ5
IGFzc2lnbmluZyBhZGRpdGlvbmFsIHNpZ25pZmljYW5jZSB0byBzcGVjaWZpYyBiaXRzDQo+Pj4+
IHdpdGhpbiB0aGUgcHJlZml4LiAgQnkgZW1iZWRkZWQgc2VtYW50aWNzIGludG8gSVB2NiBwcmVm
aXhlcywgdGhlDQo+Pj4+IHNlbWFudGljcyBvZiBwYWNrZXRzIGNhbiBiZSBpbnNwZWN0ZWQgZWFz
aWx5LiAgUm91dGVycyBhbmQgb3RoZXINCj4+Pj4gaW50ZXJtZWRpYXJ5IGRldmljZXMgY2FuIGVh
c2lseSBhcHBseSByZWxldmFudCBwb2xpY2llcyBhcyByZXF1aXJlZC4NCj4+Pj4gUGFja2V0LWxl
dmVsIGRpZmZlcmVudGlhdGlvbiBjYW4gYWxzbyBlbmFibGUgZmxvdy1sZXZlbCBhbmQgdXNlci0N
Cj4+Pj4gbGV2ZWwgZGlmZmVyZW50aWF0aW9uLiAgQ29uc2VxdWVudGx5LCB0aGUgbmV0d29yayBv
cGVyYXRvcnMgY2FuDQo+Pj4+IGFjY29yZGluZ2x5IHRyZWF0IG5ldHdvcmsgcGFja2V0cyBkaWZm
ZXJlbnRseSBhbmQgZWZmaWNpZW50bHkuICBUaGUNCj4+Pj4gbWFuYWdlbWVudCBhbmQgbWFpbnRl
bmFuY2Ugb2YgbmV0d29ya3MgY2FuIGJlIG11Y2ggc2ltcGxlci4NCj4+Pj4NCj4+Pj4NCj4+Pj4N
Cj4+Pj4NCj4+Pj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCj4+Pg0KPj4+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gdjZvcHMgbWFpbGluZyBsaXN0
DQo+Pj4gdjZvcHNAaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL3Y2b3BzDQo+Pg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+IHY2b3BzIG1haWxpbmcgbGlzdA0KPj4gdjZvcHNAaWV0Zi5vcmcNCj4+
IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjZvcHMNCg0K

From tjc@ecs.soton.ac.uk  Thu May 30 00:12:20 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFFD21F9695; Thu, 30 May 2013 00:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PC8xRMtes56E; Thu, 30 May 2013 00:12:19 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id D687921F972B; Thu, 30 May 2013 00:12:10 -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 r4U7BcVS012759; Thu, 30 May 2013 08:11:38 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4U7BcVS012759
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369897898; bh=D2wyjBRWrZdA8kQame64PK+VAtI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=uyZirk8kEmlFkL8O16f7ccfCMXYHUsQ2JR9dDeAW1wo46XrkQ3x9ZeIpBFbMcLJ2o vFpIXkYS+TzFHeCLNlr4uJCCbTTGaQQf77Yfd5tx2dxl3DSWZ2EXMkP0VsBqvPUUJU enOv4PhsJQrIY0XN7yE6ZpWvurJHyeYaiOdByxCU=
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 (valid=N/A) id p4Y8Bc04306166134K ret-id none; Thu, 30 May 2013 08:11:38 +0100
Received: from [192.168.1.103] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4U7B9xM002129 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 08:11:10 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com>
Date: Thu, 30 May 2013 08:11:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|6fd619d4c2dbea7721e947e7faff5203p4Y8Bc03tjc|ecs.soton.ac.uk|C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4Y8Bc043061661300; tid=p4Y8Bc04306166134K; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4U7BcVS012759
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:12:20 -0000

On 30 May 2013, at 08:00, Sheng Jiang <jiangsheng@huawei.com> wrote:
>>=20
>> I agree. That said, an ISP, enterprise or group of organisations can =
follow
>> whatever semantics they wish within their own borders. Just don't =
expect
>> anyone else to follow or use those semantics.  What Sheng is =
proposing is
>> clearly stated as only being for interpretation between agreeing
>> organisations.
>=20
> Hi, Tim,
>=20
> It is exactly what the draft document. These semantics is only =
meaningful locally within the assigning provider network. It may only be =
interpretation between agreeing providers.
>=20
> Any efforts to add global or generic semantics to IP address is =
overload the IP architecture and it bad direction, I agree.
>=20
>> I think people will do this type of thing, so an Informational =
document
>> discussing the pros and cons, and how semantics can be used, is =
probably a
>> good thing.  Perhaps a "Potential Pitfalls" type section after the =
"Potential
>> Benefits" section would balance the document a little better?
>=20
> Yes. We will do so in the future version.=20

Good, and I think it's important to do so. George and Lorenzo's comments =
are good starting points for that section. The potential =
privacy/information leakage aspect is also worth capturing, should those =
addresses be seen outside the organisation.

6rd is a good example of a scheme that typically requires a larger =
allocation from the RIR purely because of the semantics used.  But in =
some cases the semantics need not require a larger allocation; we could =
include semantics in a campus /48 for example.

Tim=

From jiangsheng@huawei.com  Thu May 30 00:13:48 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B9021F9729; Thu, 30 May 2013 00:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.359
X-Spam-Level: 
X-Spam-Status: No, score=-6.359 tagged_above=-999 required=5 tests=[AWL=0.240,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjAd1rDB0E-g; Thu, 30 May 2013 00:13:42 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B44AF21F9726; Thu, 30 May 2013 00:13:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARX97033; Thu, 30 May 2013 07:13:37 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:12:34 +0100
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:13:07 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Thu, 30 May 2013 15:13:02 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Lorenzo Colitti <lorenzo@google.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAAQAgIAAioBg
Date: Thu, 30 May 2013 07:13:01 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC992D2nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:13:48 -0000

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

SGksIExvcmVuem8sDQoNCj5BcyBsb25nIGFzIHRoZSBSSVJzIGFyZSB3aWxsaW5nIHRvIGdpdmUg
dGhlbSBlbm91Z2ggYWRkcmVzcyBzcGFjZSB0byBkbyBzby4NCg0KPklmIGFuIElTUCByZXF1ZXN0
ZWQgYW4gSVB2NiAvMTAgZnJvbSBBUklOIGJlY2F1c2UgdGhleSB3YW50ZWQgdG8gZ2l2ZSBldmVy
eSBjdXN0b21lciBhIC80OCBhbmQgd2FudGVkIHRvIGdlb2NvZGUgdGhlIGN1c3RvbWVyJ3Mgc3Vi
c2NyaWJlciBJRCBpbnRvIHRoZSAvNDgsIHRoZW4gQVJJTiB3b3VsZCBkbyB3ZWxsIHRvIHNheSwg
Im5vLCBzb3JyeSwgdGhhdCBkb2Vzbid0IG1ha2Ugc2Vuc2UiLg0KDQo+IElNTyBJIHRoaW5rIGl0
IHNob3VsZCBhbHNvIHN0YXRlIHRoYXQgYWx0aG91Z2ggaXQgaXMgYW4gSUVURiBSRkMsIHRoaXMg
bW9kZWwgaXMgbm90IG5lY2Vzc2FyaWx5IGEgcmVjb21tZW5kZWQgbW9kZWwsIGFuZCB0aGF0IFJJ
UnMgYXJlIG5vdCBvYmxpZ2VkIHRvIGFjY2VwdCB0aGlzIHR5cGUgb2YgYWRkcmVzcyBhbGxvY2F0
aW9uIGFzIGEganVzdGlmaWNhdGlvbiBmb3Igb2J0YWluaW5nIGxhcmdlciBhZGRyZXNzIGJsb2Nr
cyB0aGFuIHRoZXkgd291bGQgbm9ybWFsbHkgYmUgYWJsZSB0byBvYnRhaW4uDQoNClllcywgdGhl
cmUgaXMgbm8gaW50ZW5zaW9uIHRvIGNoYW5nZSBBUklO4oCZcyBwb2xpY3kgYXQgYWxsLiBBUklO
IHNob3VsZCByZW1haW4gdGhlIGN1cnJlbnQgcG9saWN5IG9mIGFzc2lnbiBJUHY2IGFkZHJlc3Mg
YmxvY2suIEJ1dCB0aGUgbmV0d29yayBwcm92aWRlcnMsIHdobyBoYXMgYWxyZWFkeSBnZXQgYWRk
cmVzcyBibG9jaywgY2FuIGNob29zZSB0byB1c2UgdGhlIGFkZHJlc3NlcyB3aXRoIGNlcnRhaW4g
c2VtYW50aWNzLiBBbmQgbm8gb25lLCBpbmNsdWRpbmcgQVJJTiBjYW4gc3RvcCB0aGlzLiBUaGlz
IGlzIGp1c3Qgb25lIG9mIHRoZSBtYW55IHdheXMgcHJvdmlkZXJzIG1heSB1dGlsaXR5IHRoZWly
IGFkZHJlc3Nlcy4NCg0KPkxlc3Qgc29tZW9uZSBub3QgcmVhbGl6ZSB0aGlzLCB0aGUgZHJhZnQg
c2hvdWxkIGNsZWFybHkgc3RhdGUgdGhhdCBlbWJlZGRpbmcgTiBiaXRzIG9mIHNlbWFudGljcyBp
bnRvIElQdjYgYWRkcmVzc2VzIGNhdXNlcyB0aGUgbmV0d29yayB0byB1c2UgMl5OIHRpbWVzIHRo
ZSBhZGRyZXNzIHNwYWNlIHRoYXQgaXQgbm9ybWFsbHkgd291bGQuDQoNClllcywgd2Ugd2lsbCBz
dGF0ZSB0aGUgc2VtYW50aWNzIHdpbGwgbG93ZXIgdGhlIGFkZHJlc3MgdXRpbGl6YXRpb24gcmF0
aW8gaW4gdGhlIGZ1dHVyZSB1cGRhdGUuIEhvd2V2ZXIsIGl0IGlzIG5vdCBuZWNlc3NhcnkgYXMg
d29yc2UgYXMgMl5OIHRpbWVzLiBGb3IgZXhhbXBsZSwgaXQgdGhlcmUgYXJlIDIgYml0cyB0byBz
ZXBhcmF0ZSBkaWZmZXJlbnQgdXNlIHR5cGVzIChzYXkgNCBkaWZmZXJlbnQgdHlwZXMpLCBpdCBh
Y3R1YWxseSBvbmx5IHNlcGFyYXRlIHVzZSBhZGRyZXNzIHNwYWNlcyBpbnRvIGZvdXIgZGlmZmVy
ZW50IHNwYWNlcy4gSXQgZG9lcyBub3QgbGltaXQgdGhlIGFkZHJlc3Mgc3BhY2UgdG8gYmUgMS80
IG9mIG9yaWdpbmFsIHNwYWNlLg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCkZyb206IExv
cmVuem8gQ29saXR0aSBbbWFpbHRvOmxvcmVuem9AZ29vZ2xlLmNvbV0NClNlbnQ6IFRodXJzZGF5
LCBNYXkgMzAsIDIwMTMgMjo0OCBQTQ0KVG86IFRpbSBDaG93bg0KQ2M6IE93ZW4gRGVMb25nOyA8
djZvcHNAaWV0Zi5vcmc+OyBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9vbHMu
aWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbdjZvcHNdIENvdWxkIElQdjYg
YWRkcmVzcyBiZSBtb3JlIHRoYW4gbG9jYXRvcj8vL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGlj
LXByZWZpeC0wMw0KDQpPbiBUaHUsIE1heSAzMCwgMjAxMyBhdCAzOjMzIFBNLCBUaW0gQ2hvd24g
PHRqY0BlY3Muc290b24uYWMudWs8bWFpbHRvOnRqY0BlY3Muc290b24uYWMudWs+PiB3cm90ZToN
CkkgYWdyZWUuIFRoYXQgc2FpZCwgYW4gSVNQLCBlbnRlcnByaXNlIG9yIGdyb3VwIG9mIG9yZ2Fu
aXNhdGlvbnMgY2FuIGZvbGxvdyB3aGF0ZXZlciBzZW1hbnRpY3MgdGhleSB3aXNoIHdpdGhpbiB0
aGVpciBvd24gYm9yZGVycy4NCg0KQXMgbG9uZyBhcyB0aGUgUklScyBhcmUgd2lsbGluZyB0byBn
aXZlIHRoZW0gZW5vdWdoIGFkZHJlc3Mgc3BhY2UgdG8gZG8gc28uDQoNCklmIGFuIElTUCByZXF1
ZXN0ZWQgYW4gSVB2NiAvMTAgZnJvbSBBUklOIGJlY2F1c2UgdGhleSB3YW50ZWQgdG8gZ2l2ZSBl
dmVyeSBjdXN0b21lciBhIC80OCBhbmQgd2FudGVkIHRvIGdlb2NvZGUgdGhlIGN1c3RvbWVyJ3Mg
c3Vic2NyaWJlciBJRCBpbnRvIHRoZSAvNDgsIHRoZW4gQVJJTiB3b3VsZCBkbyB3ZWxsIHRvIHNh
eSwgIm5vLCBzb3JyeSwgdGhhdCBkb2Vzbid0IG1ha2Ugc2Vuc2UiLg0KDQpMZXN0IHNvbWVvbmUg
bm90IHJlYWxpemUgdGhpcywgdGhlIGRyYWZ0IHNob3VsZCBjbGVhcmx5IHN0YXRlIHRoYXQgZW1i
ZWRkaW5nIE4gYml0cyBvZiBzZW1hbnRpY3MgaW50byBJUHY2IGFkZHJlc3NlcyBjYXVzZXMgdGhl
IG5ldHdvcmsgdG8gdXNlIDJeTiB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGF0IGl0IG5vcm1h
bGx5IHdvdWxkLg0KDQpJTU8gSSB0aGluayBpdCBzaG91bGQgYWxzbyBzdGF0ZSB0aGF0IGFsdGhv
dWdoIGl0IGlzIGFuIElFVEYgUkZDLCB0aGlzIG1vZGVsIGlzIG5vdCBuZWNlc3NhcmlseSBhIHJl
Y29tbWVuZGVkIG1vZGVsLCBhbmQgdGhhdCBSSVJzIGFyZSBub3Qgb2JsaWdlZCB0byBhY2NlcHQg
dGhpcyB0eXBlIG9mIGFkZHJlc3MgYWxsb2NhdGlvbiBhcyBhIGp1c3RpZmljYXRpb24gZm9yIG9i
dGFpbmluZyBsYXJnZXIgYWRkcmVzcyBibG9ja3MgdGhhbiB0aGV5IHdvdWxkIG5vcm1hbGx5IGJl
IGFibGUgdG8gb2J0YWluLg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsN
CglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAx
MSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMi
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBj
bTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxp
bmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0
aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFG
NDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBw
dCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNl
Y3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPkhpLCBMb3JlbnpvLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPiZndDtBcyBsb25nIGFzIHRoZSBSSVJzIGFyZSB3aWxsaW5nIHRvIGdp
dmUgdGhlbSBlbm91Z2ggYWRkcmVzcyBzcGFjZSB0byBkbyBzby48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZndDtJZiBhbiBJU1AgcmVxdWVzdGVkIGFuIElQdjYgLzEwIGZyb20gQVJJTiBiZWNhdXNlIHRo
ZXkgd2FudGVkIHRvIGdpdmUgZXZlcnkgY3VzdG9tZXIgYSAvNDggYW5kIHdhbnRlZCB0byBnZW9j
b2RlIHRoZSBjdXN0b21lcidzIHN1YnNjcmliZXIgSUQgaW50byB0aGUgLzQ4LCB0aGVuIEFSSU4g
d291bGQgZG8gd2VsbCB0byBzYXksICZxdW90O25vLCBzb3JyeSwgdGhhdCBkb2Vzbid0IG1ha2UN
CiBzZW5zZSZxdW90Oy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgSU1PIEkgdGhpbmsgaXQgc2hv
dWxkIGFsc28gc3RhdGUgdGhhdCBhbHRob3VnaCBpdCBpcyBhbiBJRVRGIFJGQywgdGhpcyBtb2Rl
bCBpcyBub3QgbmVjZXNzYXJpbHkgYSByZWNvbW1lbmRlZCBtb2RlbCwgYW5kIHRoYXQgUklScyBh
cmUgbm90IG9ibGlnZWQgdG8gYWNjZXB0IHRoaXMgdHlwZSBvZiBhZGRyZXNzIGFsbG9jYXRpb24g
YXMgYSBqdXN0aWZpY2F0aW9uIGZvciBvYnRhaW5pbmcNCiBsYXJnZXIgYWRkcmVzcyBibG9ja3Mg
dGhhbiB0aGV5IHdvdWxkIG5vcm1hbGx5IGJlIGFibGUgdG8gb2J0YWluLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5ZZXMsIHRoZXJlIGlzIG5vIGludGVuc2lvbiB0byBjaGFu
Z2UgQVJJTuKAmXMgcG9saWN5IGF0IGFsbC4gQVJJTiBzaG91bGQgcmVtYWluIHRoZSBjdXJyZW50
IHBvbGljeSBvZiBhc3NpZ24gSVB2NiBhZGRyZXNzIGJsb2NrLiBCdXQgdGhlIG5ldHdvcmsNCiBw
cm92aWRlcnMsIHdobyBoYXMgYWxyZWFkeSBnZXQgYWRkcmVzcyBibG9jaywgY2FuIGNob29zZSB0
byB1c2UgdGhlIGFkZHJlc3NlcyB3aXRoIGNlcnRhaW4gc2VtYW50aWNzLiBBbmQgbm8gb25lLCBp
bmNsdWRpbmcgQVJJTiBjYW4gc3RvcCB0aGlzLiBUaGlzIGlzIGp1c3Qgb25lIG9mIHRoZSBtYW55
IHdheXMgcHJvdmlkZXJzIG1heSB1dGlsaXR5IHRoZWlyIGFkZHJlc3Nlcy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7TGVzdCBzb21l
b25lIG5vdCByZWFsaXplIHRoaXMsIHRoZSBkcmFmdCBzaG91bGQgY2xlYXJseSBzdGF0ZSB0aGF0
IGVtYmVkZGluZyBOIGJpdHMgb2Ygc2VtYW50aWNzIGludG8gSVB2NiBhZGRyZXNzZXMgY2F1c2Vz
IHRoZSBuZXR3b3JrIHRvIHVzZSAyXk4gdGltZXMgdGhlIGFkZHJlc3Mgc3BhY2UgdGhhdCBpdCBu
b3JtYWxseSB3b3VsZC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+WWVzLCB3
ZSB3aWxsIHN0YXRlIHRoZSBzZW1hbnRpY3Mgd2lsbCBsb3dlciB0aGUgYWRkcmVzcyB1dGlsaXph
dGlvbiByYXRpbyBpbiB0aGUgZnV0dXJlIHVwZGF0ZS4gSG93ZXZlciwgaXQgaXMgbm90IG5lY2Vz
c2FyeSBhcyB3b3JzZSBhcyAyXk4gdGltZXMuDQogRm9yIGV4YW1wbGUsIGl0IHRoZXJlIGFyZSAy
IGJpdHMgdG8gc2VwYXJhdGUgZGlmZmVyZW50IHVzZSB0eXBlcyAoc2F5IDQgZGlmZmVyZW50IHR5
cGVzKSwgaXQgYWN0dWFsbHkgb25seSBzZXBhcmF0ZSB1c2UgYWRkcmVzcyBzcGFjZXMgaW50byBm
b3VyIGRpZmZlcmVudCBzcGFjZXMuIEl0IGRvZXMgbm90IGxpbWl0IHRoZSBhZGRyZXNzIHNwYWNl
IHRvIGJlIDEvNCBvZiBvcmlnaW5hbCBzcGFjZS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj5CZXN0IHJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtw
YWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IExvcmVuem8gQ29saXR0aSBbbWFp
bHRvOmxvcmVuem9AZ29vZ2xlLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgTWF5
IDMwLCAyMDEzIDI6NDggUE08YnI+DQo8Yj5Ubzo8L2I+IFRpbSBDaG93bjxicj4NCjxiPkNjOjwv
Yj4gT3dlbiBEZUxvbmc7ICZsdDt2Nm9wc0BpZXRmLm9yZyZndDs7IGRyYWZ0LWppYW5nLXY2b3Bz
LXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzxicj4NCjxiPlN1
YmplY3Q6PC9iPiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuIGxv
Y2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gVGh1LCBNYXkgMzAsIDIwMTMgYXQgMzoz
MyBQTSwgVGltIENob3duICZsdDs8YSBocmVmPSJtYWlsdG86dGpjQGVjcy5zb3Rvbi5hYy51ayIg
dGFyZ2V0PSJfYmxhbmsiPnRqY0BlY3Muc290b24uYWMudWs8L2E+Jmd0OyB3cm90ZTo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20g
Ni4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjojMjIyMjIyIj5J
IGFncmVlLiBUaGF0IHNhaWQsIGFuIElTUCwgZW50ZXJwcmlzZSBvciBncm91cCBvZiBvcmdhbmlz
YXRpb25zIGNhbiBmb2xsb3cgd2hhdGV2ZXIgc2VtYW50aWNzIHRoZXkgd2lzaCB3aXRoaW4gdGhl
aXIgb3duIGJvcmRlcnMuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFzIGxvbmcg
YXMgdGhlIFJJUnMgYXJlIHdpbGxpbmcgdG8gZ2l2ZSB0aGVtIGVub3VnaCBhZGRyZXNzIHNwYWNl
IHRvIGRvIHNvLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+SWYgYW4gSVNQIHJlcXVlc3RlZCBhbiBJUHY2IC8xMCBmcm9tIEFSSU4gYmVjYXVzZSB0aGV5
IHdhbnRlZCB0byBnaXZlIGV2ZXJ5IGN1c3RvbWVyIGEgLzQ4IGFuZCB3YW50ZWQgdG8gZ2VvY29k
ZSB0aGUgY3VzdG9tZXIncyBzdWJzY3JpYmVyIElEIGludG8gdGhlIC80OCwgdGhlbiBBUklOIHdv
dWxkIGRvIHdlbGwgdG8gc2F5LCAmcXVvdDtubywgc29ycnksIHRoYXQgZG9lc24ndCBtYWtlDQog
c2Vuc2UmcXVvdDsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj5MZXN0IHNvbWVvbmUgbm90IHJlYWxpemUgdGhpcywgdGhlIGRyYWZ0IHNob3VsZCBjbGVh
cmx5IHN0YXRlIHRoYXQgZW1iZWRkaW5nIE4gYml0cyBvZiBzZW1hbnRpY3MgaW50byBJUHY2IGFk
ZHJlc3NlcyBjYXVzZXMgdGhlIG5ldHdvcmsgdG8gdXNlIDJeTiB0aW1lcyB0aGUgYWRkcmVzcyBz
cGFjZSB0aGF0IGl0IG5vcm1hbGx5IHdvdWxkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+SU1PIEkgdGhpbmsgaXQgc2hvdWxkIGFsc28gc3RhdGUgdGhh
dCBhbHRob3VnaCBpdCBpcyBhbiBJRVRGIFJGQywgdGhpcyBtb2RlbCBpcyBub3QgbmVjZXNzYXJp
bHkgYSByZWNvbW1lbmRlZCBtb2RlbCwgYW5kIHRoYXQgUklScyBhcmUgbm90IG9ibGlnZWQgdG8g
YWNjZXB0IHRoaXMgdHlwZSBvZiBhZGRyZXNzIGFsbG9jYXRpb24gYXMgYSBqdXN0aWZpY2F0aW9u
IGZvciBvYnRhaW5pbmcNCiBsYXJnZXIgYWRkcmVzcyBibG9ja3MgdGhhbiB0aGV5IHdvdWxkIG5v
cm1hbGx5IGJlIGFibGUgdG8gb2J0YWluLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC992D2nkgeml512mbxchi_--

From lorenzo@google.com  Thu May 30 00:19:19 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD3CC21F978C for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 00:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.927
X-Spam-Level: 
X-Spam-Status: No, score=-1.927 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FgfUOGCrqhe9 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 00:19:19 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 38B8A21F978A for <ipv6@ietf.org>; Thu, 30 May 2013 00:19:19 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so5900507obb.19 for <ipv6@ietf.org>; Thu, 30 May 2013 00:19:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=zRsoECF5LwpYV4GdY53AX2spNEic1hNSP5Dx2UHIHAI=; b=he66ESO6kwAAVtnIpyMX5pepny1oAIWb1Cy2sIHJAmJzX8P5/o28F4gHa/taWQKi8J teRQOWlWpS5xqS8+IMOLH+BSTL8wkbHqyROtdvTxb/DYl/1MhKqHljvsdDQCgLP6LVQr EkNFUQICbRMjSC7jrt8XEzKRQtcuB6aXIFIwIRVW5EUu3I+gvCjXS+7kZYGIEVkSkF/B qVC+S74Tp5SZCn3zoinoS5n6FN8oqRJ+w4fEWLrMW9FxLnP3DiYHUv8XnTsaTUFYoUYa hIXrHBrpRE8xWtjX80Z+rFsdTJuqT7YACLSJldFJnSsJGa7jgnJl/TRgPmeXA6juwi4f pvOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=zRsoECF5LwpYV4GdY53AX2spNEic1hNSP5Dx2UHIHAI=; b=Yp5VFqVOmsAZIGqYsqZCnybUmeVBzFkU5OZHNbJQ/pf2FQMxq1crUG7FzLOsQ+8pHs QM4zhcTZEPidMliov8S29SlbH84qnmxmQuUlbOHYzC+Qe8XdB0m3JApasSX4ivpZzwJ2 j4moEuxe2da3ZIvjwy+xonJfhX/pzoyNe5oqX2amehDyazzGic4c0+C99zl5ij7rZAsd wX6ZD99cqC7hazYJ88qDYyl30vCiQe3v0vM1xHAgeLsnl7BWYrogt300Dl6zq2R3Ezut PWwmyTqAJiRVTi/HnQcpTzMq/zoA3RwK1v3Yd7tuhQCfca5HpSzvnyPjOIEERdQ2cz2c C58w==
X-Received: by 10.60.115.73 with SMTP id jm9mr3501783oeb.126.1369898358739; Thu, 30 May 2013 00:19:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.146.47 with HTTP; Thu, 30 May 2013 00:18:58 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 30 May 2013 16:18:58 +0900
Message-ID: <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary=089e0115ec300d36dc04ddea51e3
X-Gm-Message-State: ALoCoQmJHp6AgT6SUcDNfqM2CU4J4vO+AdQSTDWHRPypHUqmC64b+dDeHCrgmpBU5E1LDB7u89x6AkK3PQoiNr9bnAIPknGXPyvpOWRYHxlhkzo/ik99dOzqgbkirDuKZK4KexpVgX3yzAf1x/O95LEv65xVGlkYkIcaLOiMVOik9cqLCbr9ZwXwJglPAMhGH9oD79RtoQaA
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>, "<v6ops@ietf.org>" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:19:20 -0000

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

On Thu, May 30, 2013 at 4:13 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:

>  Yes, there is no intension to change ARIN=92s policy at all. ARIN should
> remain the current policy of assign IPv6 address block. But the network
> providers, who has already get address block, can choose to use the
> addresses with certain semantics. And no one, including ARIN can stop thi=
s.
>

Agreed, but even for network providers that already have blocks, this will
be an issue if they ever need another block. But I do think you should
write this in the draft.


> However, it is not necessary as worse as 2^N times. For example, it there
> are 2 bits to separate different use types (say 4 different types), it
> actually only separate use address spaces into four different spaces. It
> does not limit the address space to be 1/4 of original space.
>

How is that different from saying "by adding two bits of semantics in the
prefix, the network will use 4 times the address space than it would
otherwise"?

--089e0115ec300d36dc04ddea51e3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, May 30, 2013 at 4:13 PM, Sheng Jiang <span dir=3D"=
ltr">&lt;<a href=3D"mailto:jiangsheng@huawei.com" target=3D"_blank">jiangsh=
eng@huawei.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:Cali=
bri,sans-serif;font-size:10.5pt">Yes, there is no intension to change ARIN=
=92s policy at all. ARIN should remain the current policy of assign IPv6 ad=
dress block. But the network
 providers, who has already get address block, can choose to use the addres=
ses with certain semantics. And no one, including ARIN can stop this.</span=
></p></div></div></blockquote><div><br></div><div style>Agreed, but even fo=
r network providers that already have blocks, this will be an issue if they=
 ever need another block. But I do think you should write this in the draft=
.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"ZH-CN" link=3D"bl=
ue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"color:rgb(3=
1,73,125);font-family:Calibri,sans-serif;font-size:10.5pt">However, it is n=
ot necessary as worse as 2^N times.
 For example, it there are 2 bits to separate different use types (say 4 di=
fferent types), it actually only separate use address spaces into four diff=
erent spaces. It does not limit the address space to be 1/4 of original spa=
ce.</span></p>

</div></div></blockquote><div><br></div><div style>How is that different fr=
om saying &quot;by adding two bits of semantics in the prefix, the network =
will use 4 times the address space than it would otherwise&quot;?</div>

</div></div></div>

--089e0115ec300d36dc04ddea51e3--

From jiangsheng@huawei.com  Thu May 30 00:39:05 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8252821F96E9; Thu, 30 May 2013 00:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.098
X-Spam-Level: 
X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0R702HYh6ZZ; Thu, 30 May 2013 00:39:01 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 223A921F96EA; Thu, 30 May 2013 00:38:46 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH82157; Thu, 30 May 2013 07:38:45 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:38:03 +0100
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:38:33 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Thu, 30 May 2013 15:38:28 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: George Michaelson <ggm@algebras.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAAQAgIAAAkGAgACOuhA=
Date: Thu, 30 May 2013 07:38:28 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9933F@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <CAKr6gn0QeTyQ54a4MRc_HK=X+1-2tXYf2PXqTWc-H=Hox4ojeA@mail.gmail.com>
In-Reply-To: <CAKr6gn0QeTyQ54a4MRc_HK=X+1-2tXYf2PXqTWc-H=Hox4ojeA@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC9933Fnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:39:05 -0000

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

SGksIEdlb3JnZSwNCg0KSSB0aGluayB3ZSBzaGFyZSB0aGUgc2FtZSB2aWV3IGhlcmUuIEFjdHVh
bGx5LCBJIG5ldmVyIHRyeSB0byByZWNvbW1lbmQgdGhpcyBhcyBhIGdvb2QgYXJjaGl0ZWN0dXJl
LiBXaGF0IEkgYW0gdHJ5aW5nIHRvIGRvIGlzIHR3byB0aGluZ3M6IGEpIGRvY3VtZW50IHN1Y2gg
bWVjaGFuaXNtIGFzIHdlIGFyZSBzdXJlIHRoaXMgaXMgaGFwcGVuaW5nIG9yIG1lYW50IHRvIGhh
cHBlbiwgYikgZ2l2aW5nIGFuYWx5c2lzIG9mIHRoaXMgbWVjaGFuaXNtLg0KDQpJIGd1ZXNzIEkg
c2hvdWxkIGFsc28gY2xlYXIgc3RhdGUgdGhhdCB0aGUgcHJvdmlkZXIsIHdobyBjaG9vc2Ugc3Vj
aCBzY2hlbWEsIHNob3VsZCBiZSB3YXJlIHRoYXQgdGhleSBjYW5ub3QgZ2V0IG5ldyBhZGRyZXNz
IGJsb2NrIHNpbmNlIHRoZXkgY29uc3VtZSB0aGVpciBhZGRyZXNzIGluIGEgbG93IHV0aWxpdHkg
cmF0ZS4NCg0KQ2hlZXJzLA0KDQpTaGVuZw0KDQpGcm9tOiBHZW9yZ2UgTWljaGFlbHNvbiBbbWFp
bHRvOmdnbUBhbGdlYnJhcy5vcmddDQpTZW50OiBUaHVyc2RheSwgTWF5IDMwLCAyMDEzIDI6NTYg
UE0NClRvOiBMb3JlbnpvIENvbGl0dGkNCkNjOiBUaW0gQ2hvd247IGlwdjZAaWV0Zi5vcmc7IDx2
Nm9wc0BpZXRmLm9yZz47IGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5p
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFt2Nm9wc10gQ291bGQgSVB2NiBhZGRyZXNzIGJlIG1vcmUg
dGhhbiBsb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQoNCldo
aWNoIGlzIHByZXR0eSBtdWNoIHdoYXQgd2FzIHNhaWQgdG8gbWlrZSwgd2hlbiB0aGlzIGNhbWUg
dXAgaW4gdGhlIFdHIDIgSUVURnMgYWdvLiBPdmVybG9hZGluZyBwYXJ0cyBvZiB0aGUgYWxsb2Nh
dGlvbiBzcGFjZSB1bmRlciB5b3VyIC8zMiBtYWtlcyBhIGNvbXBsZXRlIG1vY2tlcnkgb2YgdGhl
IHByb2Nlc3MgbW9kZWwgd2hpY2gganVzdGlmaWVkIHRoZSAvMzIgYmFzZWQgb24gLzU2IG9yIC80
OCBjb25zdW1wdGlvbiBwbGFucywgYW5kIHdoaWxlIHRoZSBIL0QgcmF0aW8gaXMgYSBzb21ld2hh
dCByZWktZmllZCBudW1iZXIsIHRoaXMga2luZCBvZiBzY2hlbWUgd2lsbCBhbHRlciBjb25zdW1w
dGlvbiBvZiB0aGUgYWRkcmVzcyBzcGFjZSBtYXNzaXZlbHkuDQoNClRoYXQgc29tZSBsYXJnZSBJ
U1BzIGFuZCBuZXR3b3JrIG9wZXJhdG9ycyAqd2FudCogdG8gb3ZlcmxvYWQgYml0cyBpbiB0aGUg
YWRkcmVzcyB0byBoYXZlIG1lYW5pbmc/IFN1cmUuIEkgY2FuIGJlbGlldmUgdGhhdC4gVGhhdCB2
ZW5kb3JzLCBrbm93aW5nIHRoaXMsICp3YW50KiB0byBlbmNvZGUgbG9naWMgaW50byBzb2xkIHJv
dXRlcnMsIGRldmljZXMsIHRvIGV4cGxvaXQgdGhpcz8gU3VyZS4gSSBjYW4gYmVsaWV2ZSB0aGF0
Lg0KDQppcyBpdCBhIGdvb2QgYXJjaGl0ZWN0dXJlPyBOby4gSSBjYW5ub3QgY3VycmVudGx5IGJl
bGlldmUgdGhhdC4NCg0KLWdlb3JnZQ0KDQpPbiBUaHUsIE1heSAzMCwgMjAxMyBhdCA0OjQ3IFBN
LCBMb3JlbnpvIENvbGl0dGkgPGxvcmVuem9AZ29vZ2xlLmNvbTxtYWlsdG86bG9yZW56b0Bnb29n
bGUuY29tPj4gd3JvdGU6DQpPbiBUaHUsIE1heSAzMCwgMjAxMyBhdCAzOjMzIFBNLCBUaW0gQ2hv
d24gPHRqY0BlY3Muc290b24uYWMudWs8bWFpbHRvOnRqY0BlY3Muc290b24uYWMudWs+PiB3cm90
ZToNCkkgYWdyZWUuIFRoYXQgc2FpZCwgYW4gSVNQLCBlbnRlcnByaXNlIG9yIGdyb3VwIG9mIG9y
Z2FuaXNhdGlvbnMgY2FuIGZvbGxvdyB3aGF0ZXZlciBzZW1hbnRpY3MgdGhleSB3aXNoIHdpdGhp
biB0aGVpciBvd24gYm9yZGVycy4NCg0KQXMgbG9uZyBhcyB0aGUgUklScyBhcmUgd2lsbGluZyB0
byBnaXZlIHRoZW0gZW5vdWdoIGFkZHJlc3Mgc3BhY2UgdG8gZG8gc28uDQoNCklmIGFuIElTUCBy
ZXF1ZXN0ZWQgYW4gSVB2NiAvMTAgZnJvbSBBUklOIGJlY2F1c2UgdGhleSB3YW50ZWQgdG8gZ2l2
ZSBldmVyeSBjdXN0b21lciBhIC80OCBhbmQgd2FudGVkIHRvIGdlb2NvZGUgdGhlIGN1c3RvbWVy
J3Mgc3Vic2NyaWJlciBJRCBpbnRvIHRoZSAvNDgsIHRoZW4gQVJJTiB3b3VsZCBkbyB3ZWxsIHRv
IHNheSwgIm5vLCBzb3JyeSwgdGhhdCBkb2Vzbid0IG1ha2Ugc2Vuc2UiLg0KDQpMZXN0IHNvbWVv
bmUgbm90IHJlYWxpemUgdGhpcywgdGhlIGRyYWZ0IHNob3VsZCBjbGVhcmx5IHN0YXRlIHRoYXQg
ZW1iZWRkaW5nIE4gYml0cyBvZiBzZW1hbnRpY3MgaW50byBJUHY2IGFkZHJlc3NlcyBjYXVzZXMg
dGhlIG5ldHdvcmsgdG8gdXNlIDJeTiB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGF0IGl0IG5v
cm1hbGx5IHdvdWxkLg0KDQpJTU8gSSB0aGluayBpdCBzaG91bGQgYWxzbyBzdGF0ZSB0aGF0IGFs
dGhvdWdoIGl0IGlzIGFuIElFVEYgUkZDLCB0aGlzIG1vZGVsIGlzIG5vdCBuZWNlc3NhcmlseSBh
IHJlY29tbWVuZGVkIG1vZGVsLCBhbmQgdGhhdCBSSVJzIGFyZSBub3Qgb2JsaWdlZCB0byBhY2Nl
cHQgdGhpcyB0eXBlIG9mIGFkZHJlc3MgYWxsb2NhdGlvbiBhcyBhIGp1c3RpZmljYXRpb24gZm9y
IG9idGFpbmluZyBsYXJnZXIgYWRkcmVzcyBibG9ja3MgdGhhbiB0aGV5IHdvdWxkIG5vcm1hbGx5
IGJlIGFibGUgdG8gb2J0YWluLg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KdjZvcHMgbWFpbGluZyBsaXN0DQp2Nm9wc0BpZXRmLm9yZzxtYWlsdG86
djZvcHNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Y2
b3BzDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJn
aW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFn
ZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJs
dWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+SGksIEdlb3JnZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+SSB0aGluayB3ZSBzaGFyZSB0aGUgc2FtZSB2aWV3IGhlcmUuIEFjdHVhbGx5LCBJIG5ldmVy
IHRyeSB0byByZWNvbW1lbmQgdGhpcyBhcyBhIGdvb2QgYXJjaGl0ZWN0dXJlLiBXaGF0IEkgYW0g
dHJ5aW5nIHRvIGRvIGlzIHR3byB0aGluZ3M6IGEpIGRvY3VtZW50DQogc3VjaCBtZWNoYW5pc20g
YXMgd2UgYXJlIHN1cmUgdGhpcyBpcyBoYXBwZW5pbmcgb3IgbWVhbnQgdG8gaGFwcGVuLCBiKSBn
aXZpbmcgYW5hbHlzaXMgb2YgdGhpcyBtZWNoYW5pc20uPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkkgZ3Vlc3MgSSBzaG91bGQgYWxzbyBjbGVhciBzdGF0ZSB0aGF0IHRoZSBw
cm92aWRlciwgd2hvIGNob29zZSBzdWNoIHNjaGVtYSwgc2hvdWxkIGJlIHdhcmUgdGhhdCB0aGV5
IGNhbm5vdCBnZXQgbmV3IGFkZHJlc3MgYmxvY2sgc2luY2UgdGhleSBjb25zdW1lDQogdGhlaXIg
YWRkcmVzcyBpbiBhIGxvdyB1dGlsaXR5IHJhdGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+U2hl
bmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gR2VvcmdlIE1pY2hhZWxzb24gW21haWx0bzpn
Z21AYWxnZWJyYXMub3JnXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMzAsIDIw
MTMgMjo1NiBQTTxicj4NCjxiPlRvOjwvYj4gTG9yZW56byBDb2xpdHRpPGJyPg0KPGI+Q2M6PC9i
PiBUaW0gQ2hvd247IGlwdjZAaWV0Zi5vcmc7ICZsdDt2Nm9wc0BpZXRmLm9yZyZndDs7IGRyYWZ0
LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzxicj4NCjxiPlN1Ympl
Y3Q6PC9iPiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuIGxvY2F0
b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+V2hpY2ggaXMgcHJldHR5IG11Y2ggd2hhdCB3YXMg
c2FpZCB0byBtaWtlLCB3aGVuIHRoaXMgY2FtZSB1cCBpbiB0aGUgV0cgMiBJRVRGcyBhZ28uIE92
ZXJsb2FkaW5nIHBhcnRzIG9mIHRoZSBhbGxvY2F0aW9uIHNwYWNlIHVuZGVyIHlvdXIgLzMyIG1h
a2VzIGEgY29tcGxldGUgbW9ja2VyeSBvZiB0aGUgcHJvY2VzcyBtb2RlbCB3aGljaCBqdXN0aWZp
ZWQgdGhlIC8zMiBiYXNlZA0KIG9uIC81NiBvciAvNDggY29uc3VtcHRpb24gcGxhbnMsIGFuZCB3
aGlsZSB0aGUgSC9EIHJhdGlvIGlzIGEgc29tZXdoYXQgcmVpLWZpZWQgbnVtYmVyLCB0aGlzIGtp
bmQgb2Ygc2NoZW1lIHdpbGwgYWx0ZXIgY29uc3VtcHRpb24gb2YgdGhlIGFkZHJlc3Mgc3BhY2Ug
bWFzc2l2ZWx5LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRoYXQg
c29tZSBsYXJnZSBJU1BzIGFuZCBuZXR3b3JrIG9wZXJhdG9ycyAqd2FudCogdG8gb3ZlcmxvYWQg
Yml0cyBpbiB0aGUgYWRkcmVzcyB0byBoYXZlIG1lYW5pbmc/IFN1cmUuIEkgY2FuIGJlbGlldmUg
dGhhdC4gVGhhdCB2ZW5kb3JzLCBrbm93aW5nIHRoaXMsICp3YW50KiB0byBlbmNvZGUgbG9naWMg
aW50byBzb2xkIHJvdXRlcnMsIGRldmljZXMsIHRvIGV4cGxvaXQgdGhpcz8NCiBTdXJlLiBJIGNh
biBiZWxpZXZlIHRoYXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj5pcyBpdCBhIGdvb2QgYXJjaGl0ZWN0dXJlPyBOby4gSSBjYW5ub3QgY3VycmVudGx5
IGJlbGlldmUgdGhhdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiPi1nZW9yZ2U8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gVGh1LCBNYXkgMzAsIDIwMTMg
YXQgNDo0NyBQTSwgTG9yZW56byBDb2xpdHRpICZsdDs8YSBocmVmPSJtYWlsdG86bG9yZW56b0Bn
b29nbGUuY29tIiB0YXJnZXQ9Il9ibGFuayI+bG9yZW56b0Bnb29nbGUuY29tPC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gVGh1LCBNYXkgMzAsIDIwMTMgYXQgMzozMyBQTSwg
VGltIENob3duICZsdDs8YSBocmVmPSJtYWlsdG86dGpjQGVjcy5zb3Rvbi5hYy51ayIgdGFyZ2V0
PSJfYmxhbmsiPnRqY0BlY3Muc290b24uYWMudWs8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjoj
MjIyMjIyIj5JIGFncmVlLiBUaGF0IHNhaWQsIGFuIElTUCwgZW50ZXJwcmlzZSBvciBncm91cCBv
ZiBvcmdhbmlzYXRpb25zIGNhbiBmb2xsb3cgd2hhdGV2ZXIgc2VtYW50aWNzIHRoZXkgd2lzaCB3
aXRoaW4gdGhlaXIgb3duIGJvcmRlcnMuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+QXMgbG9uZyBhcyB0aGUgUklScyBhcmUgd2lsbGluZyB0byBnaXZlIHRoZW0gZW5v
dWdoIGFkZHJlc3Mgc3BhY2UgdG8gZG8gc28uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIj5JZiBhbiBJU1AgcmVxdWVzdGVkIGFuIElQdjYgLzEwIGZyb20g
QVJJTiBiZWNhdXNlIHRoZXkgd2FudGVkIHRvIGdpdmUgZXZlcnkgY3VzdG9tZXIgYSAvNDggYW5k
IHdhbnRlZCB0byBnZW9jb2RlIHRoZSBjdXN0b21lcidzIHN1YnNjcmliZXIgSUQgaW50byB0aGUg
LzQ4LCB0aGVuIEFSSU4gd291bGQgZG8gd2VsbCB0byBzYXksICZxdW90O25vLCBzb3JyeSwgdGhh
dCBkb2Vzbid0IG1ha2UNCiBzZW5zZSZxdW90Oy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPkxlc3Qgc29tZW9uZSBub3QgcmVhbGl6ZSB0aGlzLCB0aGUg
ZHJhZnQgc2hvdWxkIGNsZWFybHkgc3RhdGUgdGhhdCBlbWJlZGRpbmcgTiBiaXRzIG9mIHNlbWFu
dGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGNhdXNlcyB0aGUgbmV0d29yayB0byB1c2UgMl5OIHRp
bWVzIHRoZSBhZGRyZXNzIHNwYWNlIHRoYXQgaXQgbm9ybWFsbHkgd291bGQuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5JTU8gSSB0aGluayBpdCBzaG91
bGQgYWxzbyBzdGF0ZSB0aGF0IGFsdGhvdWdoIGl0IGlzIGFuIElFVEYgUkZDLCB0aGlzIG1vZGVs
IGlzIG5vdCBuZWNlc3NhcmlseSBhIHJlY29tbWVuZGVkIG1vZGVsLCBhbmQgdGhhdCBSSVJzIGFy
ZSBub3Qgb2JsaWdlZCB0byBhY2NlcHQgdGhpcyB0eXBlIG9mIGFkZHJlc3MgYWxsb2NhdGlvbiBh
cyBhIGp1c3RpZmljYXRpb24gZm9yIG9idGFpbmluZw0KIGxhcmdlciBhZGRyZXNzIGJsb2NrcyB0
aGFuIHRoZXkgd291bGQgbm9ybWFsbHkgYmUgYWJsZSB0byBvYnRhaW4uPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCnY2
b3BzIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzp2Nm9wc0BpZXRmLm9yZyI+djZv
cHNAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby92Nm9wcyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vdjZvcHM8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC9933Fnkgeml512mbxchi_--

From jiangsheng@huawei.com  Thu May 30 00:56:44 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB80C21F974A; Thu, 30 May 2013 00:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.384
X-Spam-Level: 
X-Spam-Status: No, score=-6.384 tagged_above=-999 required=5 tests=[AWL=0.214,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LseThAxJPE56; Thu, 30 May 2013 00:56:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1C86E21F8825; Thu, 30 May 2013 00:56:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY01020; Thu, 30 May 2013 07:56:33 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:55:58 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 08:56:29 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Thu, 30 May 2013 15:56:25 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAAQAgIAAioBg//9+QwCAAIvnkA==
Date: Thu, 30 May 2013 07:56:24 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC99354nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>, "<v6ops@ietf.org>" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 07:56:44 -0000

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

Pj5ZZXMsIHRoZXJlIGlzIG5vIGludGVuc2lvbiB0byBjaGFuZ2UgQVJJTuKAmXMgcG9saWN5IGF0
IGFsbC4gQVJJTiBzaG91bGQgcmVtYWluIHRoZSBjdXJyZW50IHBvbGljeSBvZiBhc3NpZ24gSVB2
NiBhZGRyZXNzIGJsb2NrLiBCdXQgdGhlIG5ldHdvcmsgcHJvdmlkZXJzLCB3aG8gaGFzIGFscmVh
ZHkgZ2V0IGFkZHJlc3MgYmxvY2ssIGNhbiBjaG9vc2UgdG8gdXNlIHRoZSBhZGRyZXNzZXMgd2l0
aCBjZXJ0YWluIHNlbWFudGljcy4gQW5kIG5vIG9uZSwgaW5jbHVkaW5nIEFSSU4gY2FuIHN0b3Ag
dGhpcy4NCj5BZ3JlZWQsIGJ1dCBldmVuIGZvciBuZXR3b3JrIHByb3ZpZGVycyB0aGF0IGFscmVh
ZHkgaGF2ZSBibG9ja3MsIHRoaXMgd2lsbCBiZSBhbiBpc3N1ZSBpZiB0aGV5IGV2ZXIgbmVlZCBh
bm90aGVyIGJsb2NrLiBCdXQgSSBkbyB0aGluayB5b3Ugc2hvdWxkIHdyaXRlIHRoaXMgaW4gdGhl
IGRyYWZ0Lg0KV2lsbCBkby4gVGhlIHByb3ZpZGVyLCB3aG8gY2hvb3NlIHN1Y2ggc2NoZW1hLCBz
aG91bGQgYmUgYXdhcmUgdGhhdCB0aGV5IGNhbm5vdCBnZXQgbmV3IGFkZHJlc3MgYmxvY2sgb25s
eSBiZWNhdXNlIHRoZXkgY29uc3VtZSB0aGVpciBhZGRyZXNzIHNwYWNlIGluIGEgbG93IHV0aWxp
dHkgcmF0ZS4NCj4+SG93ZXZlciwgaXQgaXMgbm90IG5lY2Vzc2FyeSBhcyB3b3JzZSBhcyAyXk4g
dGltZXMuIEZvciBleGFtcGxlLCBpdCB0aGVyZSBhcmUgMiBiaXRzIHRvIHNlcGFyYXRlIGRpZmZl
cmVudCB1c2UgdHlwZXMgKHNheSA0IGRpZmZlcmVudCB0eXBlcyksIGl0IGFjdHVhbGx5IG9ubHkg
c2VwYXJhdGUgdXNlIGFkZHJlc3Mgc3BhY2VzIGludG8gZm91ciBkaWZmZXJlbnQgc3BhY2VzLiBJ
dCBkb2VzIG5vdCBsaW1pdCB0aGUgYWRkcmVzcyBzcGFjZSB0byBiZSAxLzQgb2Ygb3JpZ2luYWwg
c3BhY2UuDQpIb3cgaXMgdGhhdCBkaWZmZXJlbnQgZnJvbSBzYXlpbmcgImJ5IGFkZGluZyB0d28g
Yml0cyBvZiBzZW1hbnRpY3MgaW4gdGhlIHByZWZpeCwgdGhlIG5ldHdvcmsgd2lsbCB1c2UgNCB0
aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGFuIGl0IHdvdWxkIG90aGVyd2lzZSI/DQpOby4gVGhp
cyBpcyB2ZXJ5IGRpZmZlcmVudC4gUHV0dGluZyB0aGUgZXhhbXBsZSBpbnRvIG51bWJlcnMgbWF5
IGJlIG1vcmUgaW50dWl0aW9uaXN0aWMuIFNheSBhbiBJU1AgaGFzIDQgbWlsbGlvbiBzdWJzY3Jp
YmVycywgaXQgbmVlZHMgNCBtaWxsaW9uIC81NiAoYXNzdW1pbmcgZXZlcnkgdXNlciBnZXQgYSAv
NTYpLiBCeSBzZXBhcmF0aW5nIHRoZW0gaW50byA0IGRpZmZlcmVudCB0eXBlcywgdGhlIGFkZHJl
c3MgY29uc3VtcHRpb24gaXMgc3RpbGwgNCBtaWxsaW9uIC81NiBpZiB0aGUgc2VwYXJhdGlvbiBp
cyBleGFjdGx5IGV2ZW4uIEhvd2V2ZXIsIHRoZSBtb3JlIGFkZHJlc3MgbWF5IG5lZWQgd2hlbiB0
aGUgc2VwYXJhdGlvbiBpcyBub3QgZXZlbi4gRm9yIGV4YW1wbGUsIGlmIHRoZSBiaWdnZXN0IHVz
ZXIgdHlwZSBoYXMgMiBtaWxsaW9uIHVzZXJzLCB0aGVuIHRoZSB0b3RhbCBhZGRyZXNzIHNwYWNl
IG1heSBiZWNvbWUgOCBtaWxsaW9uIC81NiDigJMgdHdvIHRpbWVzIG9mIG9yaWdpbmFsLiBJdCBj
b21lcyBmcm9tIGFsaWduLiBUaGUgaW5jcmVhc2VkIHNlbWFudGljcyBiaXQgYXJlIGFsc28gaW5j
cmVhc2luZyB0aGUgYWRkcmVzcyBzcGFjZSBhbHRob3VnaCBub3QgaW5jcmVhc2luZyBsaW5lYXJs
eS4gU28sIGF0IHRoZSBlbmQsIGl0IGlzIG5vdCB0b3RhbGx5IHdhc3RlLg0KQmVzdCByZWdhcmRz
LA0KU2hlbmcNCkZyb206IExvcmVuem8gQ29saXR0aSBbbWFpbHRvOmxvcmVuem9AZ29vZ2xlLmNv
bV0NClNlbnQ6IFRodXJzZGF5LCBNYXkgMzAsIDIwMTMgMzoxOSBQTQ0KVG86IFNoZW5nIEppYW5n
DQpDYzogVGltIENob3duOyBPd2VuIERlTG9uZzsgPHY2b3BzQGlldGYub3JnPjsgZHJhZnQtamlh
bmctdjZvcHMtc2VtYW50aWMtcHJlZml4QHRvb2xzLmlldGYub3JnOyBpcHY2QGlldGYub3JnDQpT
dWJqZWN0OiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuIGxvY2F0
b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMNCg0KT24gVGh1LCBNYXkg
MzAsIDIwMTMgYXQgNDoxMyBQTSwgU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdAaHVhd2VpLmNvbTxt
YWlsdG86amlhbmdzaGVuZ0BodWF3ZWkuY29tPj4gd3JvdGU6DQpZZXMsIHRoZXJlIGlzIG5vIGlu
dGVuc2lvbiB0byBjaGFuZ2UgQVJJTuKAmXMgcG9saWN5IGF0IGFsbC4gQVJJTiBzaG91bGQgcmVt
YWluIHRoZSBjdXJyZW50IHBvbGljeSBvZiBhc3NpZ24gSVB2NiBhZGRyZXNzIGJsb2NrLiBCdXQg
dGhlIG5ldHdvcmsgcHJvdmlkZXJzLCB3aG8gaGFzIGFscmVhZHkgZ2V0IGFkZHJlc3MgYmxvY2ss
IGNhbiBjaG9vc2UgdG8gdXNlIHRoZSBhZGRyZXNzZXMgd2l0aCBjZXJ0YWluIHNlbWFudGljcy4g
QW5kIG5vIG9uZSwgaW5jbHVkaW5nIEFSSU4gY2FuIHN0b3AgdGhpcy4NCg0KQWdyZWVkLCBidXQg
ZXZlbiBmb3IgbmV0d29yayBwcm92aWRlcnMgdGhhdCBhbHJlYWR5IGhhdmUgYmxvY2tzLCB0aGlz
IHdpbGwgYmUgYW4gaXNzdWUgaWYgdGhleSBldmVyIG5lZWQgYW5vdGhlciBibG9jay4gQnV0IEkg
ZG8gdGhpbmsgeW91IHNob3VsZCB3cml0ZSB0aGlzIGluIHRoZSBkcmFmdC4NCg0KSG93ZXZlciwg
aXQgaXMgbm90IG5lY2Vzc2FyeSBhcyB3b3JzZSBhcyAyXk4gdGltZXMuIEZvciBleGFtcGxlLCBp
dCB0aGVyZSBhcmUgMiBiaXRzIHRvIHNlcGFyYXRlIGRpZmZlcmVudCB1c2UgdHlwZXMgKHNheSA0
IGRpZmZlcmVudCB0eXBlcyksIGl0IGFjdHVhbGx5IG9ubHkgc2VwYXJhdGUgdXNlIGFkZHJlc3Mg
c3BhY2VzIGludG8gZm91ciBkaWZmZXJlbnQgc3BhY2VzLiBJdCBkb2VzIG5vdCBsaW1pdCB0aGUg
YWRkcmVzcyBzcGFjZSB0byBiZSAxLzQgb2Ygb3JpZ2luYWwgc3BhY2UuDQoNCkhvdyBpcyB0aGF0
IGRpZmZlcmVudCBmcm9tIHNheWluZyAiYnkgYWRkaW5nIHR3byBiaXRzIG9mIHNlbWFudGljcyBp
biB0aGUgcHJlZml4LCB0aGUgbmV0d29yayB3aWxsIHVzZSA0IHRpbWVzIHRoZSBhZGRyZXNzIHNw
YWNlIHRoYW4gaXQgd291bGQgb3RoZXJ3aXNlIj8NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsN
CglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAx
MSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMi
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBj
bTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZh
bWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxp
bmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0
aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFG
NDk3RDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBw
dCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNl
Y3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+Jmd0OyZndDtZZXMsIHRoZXJlIGlzIG5vIGludGVuc2lvbiB0byBjaGFuZ2UgQVJJTuKA
mXMgcG9saWN5IGF0IGFsbC4gQVJJTiBzaG91bGQgcmVtYWluIHRoZQ0KIGN1cnJlbnQgcG9saWN5
IG9mIGFzc2lnbiBJUHY2IGFkZHJlc3MgYmxvY2suIEJ1dCB0aGUgbmV0d29yayBwcm92aWRlcnMs
IHdobyBoYXMgYWxyZWFkeSBnZXQgYWRkcmVzcyBibG9jaywgY2FuIGNob29zZSB0byB1c2UgdGhl
IGFkZHJlc3NlcyB3aXRoIGNlcnRhaW4gc2VtYW50aWNzLiBBbmQgbm8gb25lLCBpbmNsdWRpbmcg
QVJJTiBjYW4gc3RvcCB0aGlzLjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDtB
Z3JlZWQsIGJ1dCBldmVuIGZvciBuZXR3b3JrIHByb3ZpZGVycyB0aGF0IGFscmVhZHkgaGF2ZSBi
bG9ja3MsIHRoaXMgd2lsbCBiZSBhbiBpc3N1ZSBpZiB0aGV5IGV2ZXIgbmVlZCBhbm90aGVyIGJs
b2NrLiBCdXQgSSBkbyB0aGluayB5b3Ugc2hvdWxkIHdyaXRlIHRoaXMgaW4gdGhlIGRyYWZ0Ljxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+V2lsbCBkby4gVDwvc3Bh
bj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PmhlIHByb3ZpZGVyLCB3aG8gY2hvb3NlIHN1Y2ggc2NoZW1hLA0KIHNob3VsZCBiZSBhd2FyZSB0
aGF0IHRoZXkgY2Fubm90IGdldCBuZXcgYWRkcmVzcyBibG9jayBvbmx5IGJlY2F1c2UgdGhleSBj
b25zdW1lIHRoZWlyIGFkZHJlc3Mgc3BhY2UgaW4gYSBsb3cgdXRpbGl0eSByYXRlLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mZ3Q7Jmd0O0hvd2V2ZXIsIGl0
IGlzIG5vdCBuZWNlc3NhcnkgYXMgd29yc2UgYXMgMl5OIHRpbWVzLiBGb3IgZXhhbXBsZSwgaXQg
dGhlcmUgYXJlIDIgYml0cw0KIHRvIHNlcGFyYXRlIGRpZmZlcmVudCB1c2UgdHlwZXMgKHNheSA0
IGRpZmZlcmVudCB0eXBlcyksIGl0IGFjdHVhbGx5IG9ubHkgc2VwYXJhdGUgdXNlIGFkZHJlc3Mg
c3BhY2VzIGludG8gZm91ciBkaWZmZXJlbnQgc3BhY2VzLiBJdCBkb2VzIG5vdCBsaW1pdCB0aGUg
YWRkcmVzcyBzcGFjZSB0byBiZSAxLzQgb2Ygb3JpZ2luYWwgc3BhY2UuPC9zcGFuPjxzcGFuIGxh
bmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyI+SG93IGlzIHRoYXQgZGlmZmVyZW50IGZyb20gc2F5aW5nICZxdW90
O2J5IGFkZGluZyB0d28gYml0cyBvZiBzZW1hbnRpY3MgaW4gdGhlIHByZWZpeCwgdGhlIG5ldHdv
cmsgd2lsbCB1c2UgNCB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGFuIGl0IHdvdWxkIG90aGVy
d2lzZSZxdW90Oz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
Tm8uIFRoaXMgaXMgdmVyeSBkaWZmZXJlbnQuIFB1dHRpbmcgdGhlIGV4YW1wbGUgaW50byBudW1i
ZXJzIG1heSBiZSBtb3JlIGludHVpdGlvbmlzdGljLg0KIFNheSBhbiBJU1AgaGFzIDQgbWlsbGlv
biBzdWJzY3JpYmVycywgaXQgbmVlZHMgNCBtaWxsaW9uIC81NiAoYXNzdW1pbmcgZXZlcnkgdXNl
ciBnZXQgYSAvNTYpLiBCeSBzZXBhcmF0aW5nIHRoZW0gaW50byA0IGRpZmZlcmVudCB0eXBlcywg
dGhlIGFkZHJlc3MgY29uc3VtcHRpb24gaXMgc3RpbGwgNCBtaWxsaW9uIC81NiBpZiB0aGUgc2Vw
YXJhdGlvbiBpcyBleGFjdGx5IGV2ZW4uIEhvd2V2ZXIsIHRoZSBtb3JlIGFkZHJlc3MgbWF5IG5l
ZWQgd2hlbg0KIHRoZSBzZXBhcmF0aW9uIGlzIG5vdCBldmVuLiBGb3IgZXhhbXBsZSwgaWYgdGhl
IGJpZ2dlc3QgdXNlciB0eXBlIGhhcyAyIG1pbGxpb24gdXNlcnMsIHRoZW4gdGhlIHRvdGFsIGFk
ZHJlc3Mgc3BhY2UgbWF5IGJlY29tZSA4IG1pbGxpb24gLzU2IOKAkyB0d28gdGltZXMgb2Ygb3Jp
Z2luYWwuIEl0IGNvbWVzIGZyb20gYWxpZ24uIFRoZSBpbmNyZWFzZWQgc2VtYW50aWNzIGJpdCBh
cmUgYWxzbyBpbmNyZWFzaW5nIHRoZSBhZGRyZXNzIHNwYWNlIGFsdGhvdWdoDQogbm90IGluY3Jl
YXNpbmcgbGluZWFybHkuIFNvLCBhdCB0aGUgZW5kLCBpdCBpcyBub3QgdG90YWxseSB3YXN0ZS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRz
LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5TaGVuZzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gTG9yZW56byBDb2xpdHRpIFttYWlsdG86bG9y
ZW56b0Bnb29nbGUuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMzAsIDIw
MTMgMzoxOSBQTTxicj4NCjxiPlRvOjwvYj4gU2hlbmcgSmlhbmc8YnI+DQo8Yj5DYzo8L2I+IFRp
bSBDaG93bjsgT3dlbiBEZUxvbmc7ICZsdDt2Nm9wc0BpZXRmLm9yZyZndDs7IGRyYWZ0LWppYW5n
LXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0
aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+T24gVGh1LCBNYXkgMzAsIDIwMTMg
YXQgNDoxMyBQTSwgU2hlbmcgSmlhbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqaWFuZ3NoZW5nQGh1
YXdlaS5jb20iIHRhcmdldD0iX2JsYW5rIj5qaWFuZ3NoZW5nQGh1YXdlaS5jb208L2E+Jmd0OyB3
cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6
MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5ZZXMsIHRoZXJlIGlzIG5vIGludGVu
c2lvbiB0byBjaGFuZ2UgQVJJTuKAmXMgcG9saWN5IGF0IGFsbC4gQVJJTiBzaG91bGQgcmVtYWlu
IHRoZSBjdXJyZW50DQogcG9saWN5IG9mIGFzc2lnbiBJUHY2IGFkZHJlc3MgYmxvY2suIEJ1dCB0
aGUgbmV0d29yayBwcm92aWRlcnMsIHdobyBoYXMgYWxyZWFkeSBnZXQgYWRkcmVzcyBibG9jaywg
Y2FuIGNob29zZSB0byB1c2UgdGhlIGFkZHJlc3NlcyB3aXRoIGNlcnRhaW4gc2VtYW50aWNzLiBB
bmQgbm8gb25lLCBpbmNsdWRpbmcgQVJJTiBjYW4gc3RvcCB0aGlzLjwvc3Bhbj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2tx
dW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFncmVlZCwgYnV0IGV2ZW4gZm9yIG5ldHdvcmsgcHJv
dmlkZXJzIHRoYXQgYWxyZWFkeSBoYXZlIGJsb2NrcywgdGhpcyB3aWxsIGJlIGFuIGlzc3VlIGlm
IHRoZXkgZXZlciBuZWVkIGFub3RoZXIgYmxvY2suIEJ1dCBJIGRvIHRoaW5rIHlvdSBzaG91bGQg
d3JpdGUgdGhpcyBpbiB0aGUgZHJhZnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBw
dDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPkhvd2V2ZXIsIGl0IGlzIG5vdCBuZWNlc3NhcnkgYXMgd29yc2Ug
YXMgMl5OIHRpbWVzLiBGb3IgZXhhbXBsZSwgaXQgdGhlcmUgYXJlIDIgYml0cw0KIHRvIHNlcGFy
YXRlIGRpZmZlcmVudCB1c2UgdHlwZXMgKHNheSA0IGRpZmZlcmVudCB0eXBlcyksIGl0IGFjdHVh
bGx5IG9ubHkgc2VwYXJhdGUgdXNlIGFkZHJlc3Mgc3BhY2VzIGludG8gZm91ciBkaWZmZXJlbnQg
c3BhY2VzLiBJdCBkb2VzIG5vdCBsaW1pdCB0aGUgYWRkcmVzcyBzcGFjZSB0byBiZSAxLzQgb2Yg
b3JpZ2luYWwgc3BhY2UuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
SG93IGlzIHRoYXQgZGlmZmVyZW50IGZyb20gc2F5aW5nICZxdW90O2J5IGFkZGluZyB0d28gYml0
cyBvZiBzZW1hbnRpY3MgaW4gdGhlIHByZWZpeCwgdGhlIG5ldHdvcmsgd2lsbCB1c2UgNCB0aW1l
cyB0aGUgYWRkcmVzcyBzcGFjZSB0aGFuIGl0IHdvdWxkIG90aGVyd2lzZSZxdW90Oz88bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC99354nkgeml512mbxchi_--

From jiangsheng@huawei.com  Thu May 30 01:47:01 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD6821F975C; Thu, 30 May 2013 01:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.411
X-Spam-Level: 
X-Spam-Status: No, score=-6.411 tagged_above=-999 required=5 tests=[AWL=0.188,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 287gIDM5VIfw; Thu, 30 May 2013 01:46:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3225D21F9758; Thu, 30 May 2013 01:46:55 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATH88660; Thu, 30 May 2013 08:46:52 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 09:46:15 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 09:46:48 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Thu, 30 May 2013 16:46:42 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAIm9sP//gNoAgACfxeA=
Date: Thu, 30 May 2013 08:46:41 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9940B@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk> <EMEW3|6fd619d4c2dbea7721e947e7faff5203p4Y8Bc03tjc|ecs.soton.ac.uk|C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|6fd619d4c2dbea7721e947e7faff5203p4Y8Bc03tjc|ecs.soton.ac.uk|C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 08:47:01 -0000

DQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IFRpbSBDaG93biBbbWFpbHRv
OnRqY0BlY3Muc290b24uYWMudWtdDQo+U2VudDogVGh1cnNkYXksIE1heSAzMCwgMjAxMyAzOjEx
IFBNDQo+VG86IFNoZW5nIEppYW5nDQo+Q2M6IE93ZW4gRGVMb25nOyA8djZvcHNAaWV0Zi5vcmc+
Ow0KPmRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2
NkBpZXRmLm9yZw0KPlN1YmplY3Q6IFJlOiBbdjZvcHNdIENvdWxkIElQdjYgYWRkcmVzcyBiZSBt
b3JlIHRoYW4NCj5sb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAz
DQo+DQo+T24gMzAgTWF5IDIwMTMsIGF0IDA4OjAwLCBTaGVuZyBKaWFuZyA8amlhbmdzaGVuZ0Bo
dWF3ZWkuY29tPiB3cm90ZToNCj4+Pg0KPj4+IEkgYWdyZWUuIFRoYXQgc2FpZCwgYW4gSVNQLCBl
bnRlcnByaXNlIG9yIGdyb3VwIG9mIG9yZ2FuaXNhdGlvbnMgY2FuIGZvbGxvdw0KPj4+IHdoYXRl
dmVyIHNlbWFudGljcyB0aGV5IHdpc2ggd2l0aGluIHRoZWlyIG93biBib3JkZXJzLiBKdXN0IGRv
bid0IGV4cGVjdA0KPj4+IGFueW9uZSBlbHNlIHRvIGZvbGxvdyBvciB1c2UgdGhvc2Ugc2VtYW50
aWNzLiAgV2hhdCBTaGVuZyBpcyBwcm9wb3NpbmcgaXMNCj4+PiBjbGVhcmx5IHN0YXRlZCBhcyBv
bmx5IGJlaW5nIGZvciBpbnRlcnByZXRhdGlvbiBiZXR3ZWVuIGFncmVlaW5nDQo+Pj4gb3JnYW5p
c2F0aW9ucy4NCj4+DQo+PiBIaSwgVGltLA0KPj4NCj4+IEl0IGlzIGV4YWN0bHkgd2hhdCB0aGUg
ZHJhZnQgZG9jdW1lbnQuIFRoZXNlIHNlbWFudGljcyBpcyBvbmx5IG1lYW5pbmdmdWwNCj5sb2Nh
bGx5IHdpdGhpbiB0aGUgYXNzaWduaW5nIHByb3ZpZGVyIG5ldHdvcmsuIEl0IG1heSBvbmx5IGJl
IGludGVycHJldGF0aW9uDQo+YmV0d2VlbiBhZ3JlZWluZyBwcm92aWRlcnMuDQo+Pg0KPj4gQW55
IGVmZm9ydHMgdG8gYWRkIGdsb2JhbCBvciBnZW5lcmljIHNlbWFudGljcyB0byBJUCBhZGRyZXNz
IGlzIG92ZXJsb2FkIHRoZQ0KPklQIGFyY2hpdGVjdHVyZSBhbmQgaXQgYmFkIGRpcmVjdGlvbiwg
SSBhZ3JlZS4NCj4+DQo+Pj4gSSB0aGluayBwZW9wbGUgd2lsbCBkbyB0aGlzIHR5cGUgb2YgdGhp
bmcsIHNvIGFuIEluZm9ybWF0aW9uYWwgZG9jdW1lbnQNCj4+PiBkaXNjdXNzaW5nIHRoZSBwcm9z
IGFuZCBjb25zLCBhbmQgaG93IHNlbWFudGljcyBjYW4gYmUgdXNlZCwgaXMgcHJvYmFibHkgYQ0K
Pj4+IGdvb2QgdGhpbmcuICBQZXJoYXBzIGEgIlBvdGVudGlhbCBQaXRmYWxscyIgdHlwZSBzZWN0
aW9uIGFmdGVyIHRoZQ0KPiJQb3RlbnRpYWwNCj4+PiBCZW5lZml0cyIgc2VjdGlvbiB3b3VsZCBi
YWxhbmNlIHRoZSBkb2N1bWVudCBhIGxpdHRsZSBiZXR0ZXI/DQo+Pg0KPj4gWWVzLiBXZSB3aWxs
IGRvIHNvIGluIHRoZSBmdXR1cmUgdmVyc2lvbi4NCj4NCj5Hb29kLCBhbmQgSSB0aGluayBpdCdz
IGltcG9ydGFudCB0byBkbyBzby4gR2VvcmdlIGFuZCBMb3JlbnpvJ3MgY29tbWVudHMgYXJlDQo+
Z29vZCBzdGFydGluZyBwb2ludHMgZm9yIHRoYXQgc2VjdGlvbi4gVGhlIHBvdGVudGlhbCBwcml2
YWN5L2luZm9ybWF0aW9uDQo+bGVha2FnZSBhc3BlY3QgaXMgYWxzbyB3b3J0aCBjYXB0dXJpbmcs
IHNob3VsZCB0aG9zZSBhZGRyZXNzZXMgYmUgc2Vlbg0KPm91dHNpZGUgdGhlIG9yZ2FuaXNhdGlv
bi4NCg0KVGhhbmtzLCBUaW0uIFRoZSBwdXJwb3NlIG9mIHRoaXMgZG9jdW1lbnQgaXMgbm90IHJl
Y29tbWVuZCBvciBwcm9wb3NlIGEgZ29vZCBhcmNoaXRlY3R1cmUuIEl0IGlzIHRvIGRvY3VtZW50
IHNvbWV0aGluZyB0aGF0IGlzIGdvaW5nIHRvIGV4aXN0IGFuZCBhbmFseXplIGl0LiBUaGUgcGl0
ZmFsbHMgaXMgdmVyeSBpbXBvcnRhbnQgZm9yIGEgbmV1dHJhbCBhbmFseXNpcw0KDQpDaGVlcnMs
DQoNClNoZW5nDQoNCj42cmQgaXMgYSBnb29kIGV4YW1wbGUgb2YgYSBzY2hlbWUgdGhhdCB0eXBp
Y2FsbHkgcmVxdWlyZXMgYSBsYXJnZXIgYWxsb2NhdGlvbg0KPmZyb20gdGhlIFJJUiBwdXJlbHkg
YmVjYXVzZSBvZiB0aGUgc2VtYW50aWNzIHVzZWQuICBCdXQgaW4gc29tZSBjYXNlcyB0aGUNCj5z
ZW1hbnRpY3MgbmVlZCBub3QgcmVxdWlyZSBhIGxhcmdlciBhbGxvY2F0aW9uOyB3ZSBjb3VsZCBp
bmNsdWRlIHNlbWFudGljcyBpbg0KPmEgY2FtcHVzIC80OCBmb3IgZXhhbXBsZS4NCj4NCj5UaW0N
Cg==

From v6ops@globis.net  Thu May 30 02:24:50 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1392B21F97B7; Thu, 30 May 2013 02:24:50 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7H1gG-Nw2Ql; Thu, 30 May 2013 02:24:49 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6B78621F97B3; Thu, 30 May 2013 02:24:49 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id A2EFF8700E7; Thu, 30 May 2013 11:24:33 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8rxElZdLc9R; Thu, 30 May 2013 11:24:33 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 30C3F870077; Thu, 30 May 2013 11:24:33 +0200 (CEST)
Message-ID: <51A71ACA.3000608@globis.net>
Date: Thu, 30 May 2013 11:24:26 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 09:24:50 -0000

Sheng Jiang wrote:

> IP addresses are designed as topology locator, so that every packet can be routed to its network destination.
>
> However, even in IPv4 era, some network operators have mapped their IP address with certain semantic locally. These kind of mechanism explicitly express the semantic properties of every packet. Consequently, these network operators can inspect the properties of packets easily by mapping the addresses back to semantic.
>
> Network operators, who have large IPv6 address space, may also choose to embedded some semantics into IPv6 addresses by assigning additional significance to specific bits within the prefix. draft-jiang-v6ops-semantic-prefix documents a framework method that network operations may use their addresses with embedded semantics. These semantics bits are only meaningful within a single network, or group of interconnected networks which share a common addressing policy. Based on these embedded semantic bits in source/destination addresses, the network operators can accordingly treat network packets differently and efficiently.
>
> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>
> Could you please review this draft and comments? It will help the document become more useful information to be shared.
>
> Best regards,
>
> Sheng
>  
I completely understand the desire for operators to have additional
semantics available for customized packet processing. Flow label now has
very limited properties optimised for load balancers. DSCP only has a
few bits (way less than the number of customers' policies). ACLs are
heavy to process at each hop....

But wouldn't this information be better off encoded as tags in one or
more hop-by-hop header options (that could be re-written on the fly),
rather than encoded in the IPv6 address space?

regards,
RayH

From jiangsheng@huawei.com  Thu May 30 02:58:50 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0265A21F9590; Thu, 30 May 2013 02:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.432
X-Spam-Level: 
X-Spam-Status: No, score=-6.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ah1P33S+2hpl; Thu, 30 May 2013 02:58:45 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id DB5DA21F8F0C; Thu, 30 May 2013 02:58:44 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY12916; Thu, 30 May 2013 09:58:43 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 10:58:06 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 30 May 2013 10:58:36 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Thu, 30 May 2013 17:58:30 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kc8GIAgACHYyA=
Date: Thu, 30 May 2013 09:58:29 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net>
In-Reply-To: <51A71ACA.3000608@globis.net>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 09:58:50 -0000

Pj4gSVAgYWRkcmVzc2VzIGFyZSBkZXNpZ25lZCBhcyB0b3BvbG9neSBsb2NhdG9yLCBzbyB0aGF0
IGV2ZXJ5IHBhY2tldCBjYW4gYmUNCj5yb3V0ZWQgdG8gaXRzIG5ldHdvcmsgZGVzdGluYXRpb24u
DQo+Pg0KPj4gSG93ZXZlciwgZXZlbiBpbiBJUHY0IGVyYSwgc29tZSBuZXR3b3JrIG9wZXJhdG9y
cyBoYXZlIG1hcHBlZCB0aGVpciBJUA0KPmFkZHJlc3Mgd2l0aCBjZXJ0YWluIHNlbWFudGljIGxv
Y2FsbHkuIFRoZXNlIGtpbmQgb2YgbWVjaGFuaXNtIGV4cGxpY2l0bHkNCj5leHByZXNzIHRoZSBz
ZW1hbnRpYyBwcm9wZXJ0aWVzIG9mIGV2ZXJ5IHBhY2tldC4gQ29uc2VxdWVudGx5LCB0aGVzZSBu
ZXR3b3JrDQo+b3BlcmF0b3JzIGNhbiBpbnNwZWN0IHRoZSBwcm9wZXJ0aWVzIG9mIHBhY2tldHMg
ZWFzaWx5IGJ5IG1hcHBpbmcgdGhlDQo+YWRkcmVzc2VzIGJhY2sgdG8gc2VtYW50aWMuDQo+Pg0K
Pj4gTmV0d29yayBvcGVyYXRvcnMsIHdobyBoYXZlIGxhcmdlIElQdjYgYWRkcmVzcyBzcGFjZSwg
bWF5IGFsc28gY2hvb3NlIHRvDQo+ZW1iZWRkZWQgc29tZSBzZW1hbnRpY3MgaW50byBJUHY2IGFk
ZHJlc3NlcyBieSBhc3NpZ25pbmcgYWRkaXRpb25hbA0KPnNpZ25pZmljYW5jZSB0byBzcGVjaWZp
YyBiaXRzIHdpdGhpbiB0aGUgcHJlZml4Lg0KPmRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXBy
ZWZpeCBkb2N1bWVudHMgYSBmcmFtZXdvcmsgbWV0aG9kIHRoYXQNCj5uZXR3b3JrIG9wZXJhdGlv
bnMgbWF5IHVzZSB0aGVpciBhZGRyZXNzZXMgd2l0aCBlbWJlZGRlZCBzZW1hbnRpY3MuIFRoZXNl
DQo+c2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBzaW5nbGUgbmV0
d29yaywgb3IgZ3JvdXAgb2YNCj5pbnRlcmNvbm5lY3RlZCBuZXR3b3JrcyB3aGljaCBzaGFyZSBh
IGNvbW1vbiBhZGRyZXNzaW5nIHBvbGljeS4gQmFzZWQgb24NCj50aGVzZSBlbWJlZGRlZCBzZW1h
bnRpYyBiaXRzIGluIHNvdXJjZS9kZXN0aW5hdGlvbiBhZGRyZXNzZXMsIHRoZSBuZXR3b3JrDQo+
b3BlcmF0b3JzIGNhbiBhY2NvcmRpbmdseSB0cmVhdCBuZXR3b3JrIHBhY2tldHMgZGlmZmVyZW50
bHkgYW5kIGVmZmljaWVudGx5Lg0KPj4NCj4+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0KPj4NCj4+IENvdWxkIHlvdSBwbGVh
c2UgcmV2aWV3IHRoaXMgZHJhZnQgYW5kIGNvbW1lbnRzPyBJdCB3aWxsIGhlbHAgdGhlIGRvY3Vt
ZW50DQo+YmVjb21lIG1vcmUgdXNlZnVsIGluZm9ybWF0aW9uIHRvIGJlIHNoYXJlZC4NCj4+DQo+
PiBCZXN0IHJlZ2FyZHMsDQo+Pg0KPj4gU2hlbmcNCj4+DQo+SSBjb21wbGV0ZWx5IHVuZGVyc3Rh
bmQgdGhlIGRlc2lyZSBmb3Igb3BlcmF0b3JzIHRvIGhhdmUgYWRkaXRpb25hbA0KPnNlbWFudGlj
cyBhdmFpbGFibGUgZm9yIGN1c3RvbWl6ZWQgcGFja2V0IHByb2Nlc3NpbmcuIEZsb3cgbGFiZWwg
bm93IGhhcw0KPnZlcnkgbGltaXRlZCBwcm9wZXJ0aWVzIG9wdGltaXNlZCBmb3IgbG9hZCBiYWxh
bmNlcnMuIERTQ1Agb25seSBoYXMgYQ0KPmZldyBiaXRzICh3YXkgbGVzcyB0aGFuIHRoZSBudW1i
ZXIgb2YgY3VzdG9tZXJzJyBwb2xpY2llcykuIEFDTHMgYXJlDQo+aGVhdnkgdG8gcHJvY2VzcyBh
dCBlYWNoIGhvcC4uLi4NCj4NCj5CdXQgd291bGRuJ3QgdGhpcyBpbmZvcm1hdGlvbiBiZSBiZXR0
ZXIgb2ZmIGVuY29kZWQgYXMgdGFncyBpbiBvbmUgb3INCj5tb3JlIGhvcC1ieS1ob3AgaGVhZGVy
IG9wdGlvbnMgKHRoYXQgY291bGQgYmUgcmUtd3JpdHRlbiBvbiB0aGUgZmx5KSwNCj5yYXRoZXIg
dGhhbiBlbmNvZGVkIGluIHRoZSBJUHY2IGFkZHJlc3Mgc3BhY2U/DQoNClRoZSBzZWN0aW9uIDQu
MSAiSnVzdGlmY2F0aW9uIGZvciBTZW1hbnRpY3Mgd2l0aCB0aGUgSVB2NiBQcmVmaXgiIGRlc2Ny
aWJlcyB0aGUgcmVhc29ucy4NCg0KVXNlcnMgbWF5IGVhc2lseSBjaGFuZ2UgdGhlIHNldHRpbmcg
b2YgZXh0ZW5zaW9uIGhlYWRlciBpbiBvcmRlciB0byBvYnRhaW4gdW5kZXNlcnZlZCBwcmlvcml0
aWVzL3ByaXZpbGVnZXMuIFNlbWFudGljIHByZWZpeCBhcHByb2FjaCBkb2VzIHJlcXVpcmUgdGhl
IGRlcGxveW1lbnQgb2YgYWNjZXNzIGNvbnRyb2wgZmlsdGVycy4gVGhlIHBhY2tldHMgd2l0aCB0
aGUgbm9uY29tcGxpYW5jZSBzb3VyY2UgYWRkcmVzc2VzIHNob3VsZCBiZSBmaWx0ZXJlZC4gVGhl
IHByZWZpeCBpcyBkZWxlZ2F0ZWQgYnkgdGhlIG5ldHdvcmsuIFRoZXJlZm9yZSB0aGUgbmV0d29y
ayBpcyBhYmxlIHRvIGRldGVjdCBhbnkgdW5kZXNpcmVkIG1vZGlmaWNhdGlvbnMgYW5kIGZpbHRl
ciB0aGUgcGFja2V0IGFjY29yZGluZ2x5Lg0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCj5yZWdhcmRz
LA0KPlJheUgNCg==

From v6ops@globis.net  Thu May 30 04:11:53 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055F621F9133; Thu, 30 May 2013 04:11:53 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZLbd9fBukyt; Thu, 30 May 2013 04:11:52 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id EF61021F9121; Thu, 30 May 2013 04:11:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0F214870077; Thu, 30 May 2013 13:11:36 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SMPUWCgNYgFd; Thu, 30 May 2013 13:11:35 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id E3CF287002E; Thu, 30 May 2013 13:11:35 +0200 (CEST)
Message-ID: <51A733E1.7040008@globis.net>
Date: Thu, 30 May 2013 13:11:29 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 11:11:53 -0000

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 30 May 2013 11:58
>>> IP addresses are designed as topology locator, so that every packet can be
>> routed to its network destination.
>>> However, even in IPv4 era, some network operators have mapped their IP
>> address with certain semantic locally. These kind of mechanism explicitly
>> express the semantic properties of every packet. Consequently, these network
>> operators can inspect the properties of packets easily by mapping the
>> addresses back to semantic.
>>> Network operators, who have large IPv6 address space, may also choose to
>> embedded some semantics into IPv6 addresses by assigning additional
>> significance to specific bits within the prefix.
>> draft-jiang-v6ops-semantic-prefix documents a framework method that
>> network operations may use their addresses with embedded semantics. These
>> semantics bits are only meaningful within a single network, or group of
>> interconnected networks which share a common addressing policy. Based on
>> these embedded semantic bits in source/destination addresses, the network
>> operators can accordingly treat network packets differently and efficiently.
>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>>
>>> Could you please review this draft and comments? It will help the document
>> become more useful information to be shared.
>>> Best regards,
>>>
>>> Sheng
>>>
>> I completely understand the desire for operators to have additional
>> semantics available for customized packet processing. Flow label now has
>> very limited properties optimised for load balancers. DSCP only has a
>> few bits (way less than the number of customers' policies). ACLs are
>> heavy to process at each hop....
>>
>> But wouldn't this information be better off encoded as tags in one or
>> more hop-by-hop header options (that could be re-written on the fly),
>> rather than encoded in the IPv6 address space?
>
> The section 4.1 "Justifcation for Semantics with the IPv6 Prefix" describes the reasons.
>
> Users may easily change the setting of extension header in order to obtain undeserved priorities/privileges. Semantic prefix approach does require the deployment of access control filters. The packets with the noncompliance source addresses should be filtered. The prefix is delegated by the network. Therefore the network is able to detect any undesired modifications and filter the packet accordingly.
>
> Cheers,
>
> Sheng
>
>
I don't buy your justification. Whether an operator filters on
authorised address range or re-writes/filters an unauthorised hop-by-hop
tag is effectively the same IMHO. We have exactly the same issues of
potential theft of service with DSCP today, and the solution is equally
simple: DSCP markdown at the ingress port.

regards,
RayH

From arturo.servin@gmail.com  Thu May 30 05:46:21 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF55D21F86AE; Thu, 30 May 2013 05:46: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mytzptSRA+LC; Thu, 30 May 2013 05:46:16 -0700 (PDT)
Received: from mail-qe0-f51.google.com (mail-qe0-f51.google.com [209.85.128.51]) by ietfa.amsl.com (Postfix) with ESMTP id 48DB621F93E8; Thu, 30 May 2013 05:46:13 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id nd7so88425qeb.24 for <multiple recipients>; Thu, 30 May 2013 05:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=w82eZ54PnVjN8Sg2z5ff7RsZSsbXEWB7udOI966ibCE=; b=GJBpNWfwavGqAt6whgQSdN8T/J2Jxyk4oLbzolb4ky32guBHWTjBT+Bmejqo6hM++H XVDCeFp6tHr92nb/ZIAxOLyqqqFWseDKc/14Nq9raPuPKvBKzMk3HPOG4K+8bMKSAR7o 06lAE5+UvtolTFN55b0uPQhGl+Rq62Jb2XTXZ0piVhKZQdLfr5zZBr3ruWtFeqE9wOzE Wifvk2OE6yO0Q/6kiUjW+hl4S/b9khCj41/1mWsr6Obe4pzJls1AnmBbdnp3OqXOX1ns jugPL1yxLOn2oZ11pLmG2VZ6gTl3F9P1u4juvMAzQllaVJqfs+JaZzdt3/DT2pdjjH39 Jbvw==
X-Received: by 10.229.11.7 with SMTP id r7mr2380203qcr.61.1369917972726; Thu, 30 May 2013 05:46:12 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([200.7.87.33]) by mx.google.com with ESMTPSA id hs4sm35202977qeb.8.2013.05.30.05.46.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 05:46:11 -0700 (PDT)
Message-ID: <51A74A18.3060600@gmail.com>
Date: Thu, 30 May 2013 09:46:16 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk> <EMEW3|6fd619d4c2dbea7721e947e7faff5203p4Y8Bc03tjc|ecs.soton.ac.uk|C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC9940B@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC9940B@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, draft-jiang-v6ops-semantic-prefix@tools.ietf.org, ipv6@ietf.org, v6ops@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Arturo Servin <arturo.servin@gmail.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 12:46:21 -0000

>>> Yes. We will do so in the future version.
>>
>>Good, and I think it's important to do so. George and Lorenzo's 
>> comments are
>>good starting points for that section. The potential 
>> privacy/information
>>leakage aspect is also worth capturing, should those addresses be 
>> seen
>>outside the organisation.
>
> Thanks, Tim. The purpose of this document is not recommend or propose
> a good architecture. It is to document something that is going to
> exist and analyze it. The pitfalls is very important for a neutral
> analysis
>
> Cheers,
>
> Sheng

Sheng,

  Yes please do this. To me it now it reads more like "you can do this,
we recommend you to do it" when it should say "you can do this, it is
bad for this, it is good for this" and even you could include something
like "we do not recommend you do it but if you want to shoot you in the
foot you are free to do so."

/as

From jmh@joelhalpern.com  Thu May 30 08:17:42 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2EC721F8FCB; Thu, 30 May 2013 08:17:42 -0700 (PDT)
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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gcu4BNRy9+OS; Thu, 30 May 2013 08:17:37 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id D50EB21F8F62; Thu, 30 May 2013 08:17:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 533671C0704; Thu, 30 May 2013 08:17:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-119.clppva.east.verizon.net [70.106.134.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2A4AE1C06A2; Thu, 30 May 2013 08:17:28 -0700 (PDT)
Message-ID: <51A76D81.9020504@joelhalpern.com>
Date: Thu, 30 May 2013 11:17:21 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 15:17:42 -0000

While it is true that any operator can do whatever they want, this 
proposal is architecturally a bad way to achieve the kind of goals you 
outline.
So I would oppose publishing even an informational RFC on how one might 
do this.

As an example of the problems with this, you suggested that allocations 
to enterprise would not change with this approach.  That the enterprise 
would receive a certain semantic, and would be allocated a certain /48 
to match that.  While this sounds attractive and harmless:
1) It is extremely unlike that a customer will fall into a single 
"semantic" with any useful definition of semantic
2) You have argued that you can not use DSCP because they are not fine 
enough grained.  This means that you want to increase the routing 
complexity by more than a factor of 64, which seems to be a VERY bad 
idea for any operator infrastructure.

So even from a simple analysis, this seems somewhere between useless and 
extremely dangerous.

Yours,
Joel M. Halpern

On 5/30/2013 3:00 AM, Sheng Jiang wrote:
...
> Hi, Tim,
>
> It is exactly what the draft document. These semantics is only meaningful locally within the assigning provider network. It may only be interpretation between agreeing providers.
>
> Any efforts to add global or generic semantics to IP address is overload the IP architecture and it bad direction, I agree.
>
>> I think people will do this type of thing, so an Informational document
>> discussing the pros and cons, and how semantics can be used, is probably a
>> good thing.  Perhaps a "Potential Pitfalls" type section after the "Potential
>> Benefits" section would balance the document a little better?
>
> Yes. We will do so in the future version.
>
> Cheers,
>
> Sheng
...

From fgont@si6networks.com  Thu May 30 08:29:13 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3EF021F8B45 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 08:29:13 -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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id od-84K0CdNhv for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 08:29:13 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 146B321F9318 for <6man@ietf.org>; Thu, 30 May 2013 08:29:12 -0700 (PDT)
Received: from 87-205-5-39.ip.netia.com.pl ([87.205.5.39] helo=[192.168.0.100]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1Ui4mf-0007QY-88; Thu, 30 May 2013 17:28:57 +0200
Message-ID: <51A77038.9000706@si6networks.com>
Date: Thu, 30 May 2013 17:28:56 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com> <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com>
In-Reply-To: <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 15:29:14 -0000

On 05/29/2013 04:03 AM, Dave Thaler wrote:
>>>> [...] I could rely on the
>>>> ICMPv6 "address resolution failed" error messages sent by your local
>>>> router (i.e., if I receive one of such messages, you're not there. If I don't,
>> you are).
>>>
>>> Ok, yes that one is interesting.
>>
>> An attacker just needs one vector to be successful.
> 
> Agree.  Putting the above example vector into the draft would help the reader
> understand the motivation for the problem.

Isn't it enough simply noting that the target node can be probed?
Getting into the specific details of the probe packet
(stimulus/response) seems like "over-specifying" things to me...

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





From arturo.servin@gmail.com  Thu May 30 08:40:35 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D352321F9401; Thu, 30 May 2013 08:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKG2XalCCMto; Thu, 30 May 2013 08:40:33 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC0521F9421; Thu, 30 May 2013 08:40:31 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id bs12so2937169qab.8 for <multiple recipients>; Thu, 30 May 2013 08:40:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=f37kS6cNRG6AibkCKIgfmH3DrCXLsda5OlDkohgBEwQ=; b=LYhRLsfWQGLOuGrA6iS/tSY4KHlKBIIufe28IiYbt4R1pjr1CnLULGzkjXh+DdiWzt T//LV1c0CZGxxs8pVPSCTIiCWfkkVAxww5NYIemO792XjpK1BY+07zSAjJFzY/5oz5c6 2N6AN/QC9iFV6O+Ix+0wu75HNpZdI1Rk7KSdOloDswSAtVKETfps6L/Ha4ykaxQTHTJU aecOAS10zWM6Wai7SNnbJYo64aAOjoFANV6WKSJeG7h7lzMZnIiEPcFulGmNaNFpK2Uv Zi7n+3uCciN1e07oCTWVrIDeYh1qKmKsqaMc55+SA8LvQ+x3mvyfrirmbiNKhDYpyEVa Zkvg==
X-Received: by 10.229.138.2 with SMTP id y2mr2612648qct.124.1369928430560; Thu, 30 May 2013 08:40:30 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:a937:ede1:dd66:aaad]) by mx.google.com with ESMTPSA id u14sm37208154qao.6.2013.05.30.08.40.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 08:40:29 -0700 (PDT)
Message-ID: <51A772EF.60408@gmail.com>
Date: Thu, 30 May 2013 12:40:31 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <51A76D81.9020504@joelhalpern.com>
In-Reply-To: <51A76D81.9020504@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 15:40:36 -0000

	Probably this could be a good opportunity to publish a document "do not
do this".

	
/as

	

	

On 5/30/13 12:17 PM, Joel M. Halpern wrote:
> While it is true that any operator can do whatever they want, this
> proposal is architecturally a bad way to achieve the kind of goals you
> outline.
> So I would oppose publishing even an informational RFC on how one might
> do this.
> 
> As an example of the problems with this, you suggested that allocations
> to enterprise would not change with this approach.  That the enterprise
> would receive a certain semantic, and would be allocated a certain /48
> to match that.  While this sounds attractive and harmless:
> 1) It is extremely unlike that a customer will fall into a single
> "semantic" with any useful definition of semantic
> 2) You have argued that you can not use DSCP because they are not fine
> enough grained.  This means that you want to increase the routing
> complexity by more than a factor of 64, which seems to be a VERY bad
> idea for any operator infrastructure.
> 
> So even from a simple analysis, this seems somewhere between useless and
> extremely dangerous.
> 
> Yours,
> Joel M. Halpern
> 
> On 5/30/2013 3:00 AM, Sheng Jiang wrote:
> ...
>> Hi, Tim,
>>
>> It is exactly what the draft document. These semantics is only
>> meaningful locally within the assigning provider network. It may only
>> be interpretation between agreeing providers.
>>
>> Any efforts to add global or generic semantics to IP address is
>> overload the IP architecture and it bad direction, I agree.
>>
>>> I think people will do this type of thing, so an Informational document
>>> discussing the pros and cons, and how semantics can be used, is
>>> probably a
>>> good thing.  Perhaps a "Potential Pitfalls" type section after the
>>> "Potential
>>> Benefits" section would balance the document a little better?
>>
>> Yes. We will do so in the future version.
>>
>> Cheers,
>>
>> Sheng
> ...
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From dthaler@microsoft.com  Thu May 30 09:10:34 2013
Return-Path: <dthaler@microsoft.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A76B21F9610 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 09:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.467
X-Spam-Level: 
X-Spam-Status: No, score=-97.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LxO8m5WwYcX for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 09:10:27 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0244.outbound.protection.outlook.com [207.46.163.244]) by ietfa.amsl.com (Postfix) with ESMTP id A768921F968D for <6man@ietf.org>; Thu, 30 May 2013 09:10:27 -0700 (PDT)
Received: from BN1BFFO11FD028.protection.gbl (10.58.52.200) by BN1AFFO11HUB022.protection.gbl (10.58.52.132) with Microsoft SMTP Server (TLS) id 15.0.707.0; Thu, 30 May 2013 16:10:21 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD028.mail.protection.outlook.com (10.58.53.88) with Microsoft SMTP Server (TLS) id 15.0.698.0 via Frontend Transport; Thu, 30 May 2013 16:10:21 +0000
Received: from co1outboundpool.messaging.microsoft.com (157.54.51.113) by mail.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.3.136.1; Thu, 30 May 2013 16:10:09 +0000
Received: from mail36-co1-R.bigfish.com (10.243.78.225) by CO1EHSOBE019.bigfish.com (10.243.66.82) with Microsoft SMTP Server id 14.1.225.23; Thu, 30 May 2013 16:09:27 +0000
Received: from mail36-co1 (localhost [127.0.0.1])	by mail36-co1-R.bigfish.com (Postfix) with ESMTP id 5DF4D240147	for <6man@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 30 May 2013 16:09:27 +0000 (UTC)
X-Forefront-Antispam-Report-Untrusted: CIP:157.56.240.21; KIP:(null); UIP:(null); (null); H:BL2PRD0310HT003.namprd03.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zzbb2dI98dI9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033ILz31h2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh9a9j1155h)
Received-SPF: softfail (mail36-co1: transitioning domain of microsoft.com does not designate 157.56.240.21 as permitted sender) client-ip=157.56.240.21; envelope-from=dthaler@microsoft.com; helo=BL2PRD0310HT003.namprd03.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:BN1PR03MB266; H:BN1PR03MB267.namprd03.prod.outlook.com; LANG:en; 
Received: from mail36-co1 (localhost.localdomain [127.0.0.1]) by mail36-co1 (MessageSwitch) id 1369930165932007_24003; Thu, 30 May 2013 16:09:25 +0000 (UTC)
Received: from CO1EHSMHS016.bigfish.com (unknown [10.243.78.240])	by mail36-co1.bigfish.com (Postfix) with ESMTP id D477F40004B; Thu, 30 May 2013 16:09:25 +0000 (UTC)
Received: from BL2PRD0310HT003.namprd03.prod.outlook.com (157.56.240.21) by CO1EHSMHS016.bigfish.com (10.243.66.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 30 May 2013 16:09:24 +0000
Received: from BN1PR03MB266.namprd03.prod.outlook.com (10.255.200.15) by BL2PRD0310HT003.namprd03.prod.outlook.com (10.255.97.38) with Microsoft SMTP Server (TLS) id 14.16.311.1; Thu, 30 May 2013 16:09:22 +0000
Received: from BN1PR03MB267.namprd03.prod.outlook.com (10.255.200.17) by BN1PR03MB266.namprd03.prod.outlook.com (10.255.200.15) with Microsoft SMTP Server (TLS) id 15.0.698.13; Thu, 30 May 2013 16:09:21 +0000
Received: from BN1PR03MB267.namprd03.prod.outlook.com ([169.254.15.233]) by BN1PR03MB267.namprd03.prod.outlook.com ([169.254.15.233]) with mapi id 15.00.0698.010; Thu, 30 May 2013 16:09:20 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: RE: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Topic: Comments on draft-ietf-6man-stable-privacy-addresses-07
Thread-Index: Ac5VkEDuntBqcaI7QV+XaTZhX98FegANCYOAADDtt7AAdlSfAAAbHCNgAFBo/gAAgD2i4ABOeqYAAAFb9mA=
Date: Thu, 30 May 2013 16:09:19 +0000
Message-ID: <e342a259f6bf4ed38b1247ed98cc2fdd@BN1PR03MB267.namprd03.prod.outlook.com>
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com> <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com> <51A77038.9000706@si6networks.com>
In-Reply-To: <51A77038.9000706@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.135.4.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: BN1PR03MB266.namprd03.prod.outlook.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%CDT.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%GLOBIS.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%HITACHI.CN$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%DIAL.PIPEX.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%TOOLS.IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%SI6NETWORKS.COM$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%IETF.ORG$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-FOPE-CONNECTOR: Id%59$Dn%INNOVATIONSLAB.NET$RO%2$TLS%6$FQDN%corpf5vips-237160.customer.frontbridge.com$TlsDn%
X-CrossPremisesHeadersPromoted: TK5EX14HUBC103.redmond.corp.microsoft.com
X-CrossPremisesHeadersFiltered: TK5EX14HUBC103.redmond.corp.microsoft.com
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(479174002)(13464003)(51704005)(377454002)(189002)(199002)(24454002)(33646001)(46406003)(77982001)(16676001)(76576001)(74316001)(6806003)(74366001)(76482001)(81542001)(66066001)(74876001)(50466002)(65816001)(74706001)(81342001)(80022001)(76796001)(63696002)(31966008)(46102001)(56816002)(54356001)(53806001)(56776001)(4396001)(23726002)(51856001)(74662001)(54316002)(47736001)(47976001)(50986001)(47446002)(49866001)(59766001)(74502001)(79102001)(76786001)(20776003)(69226001)(47776003)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB022; H:TK5EX14HUBC103.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 08626BE3A5
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, "tom.petch" <cfinss@dial.pipex.com>, Christian Huitema <huitema@microsoft.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 16:10:34 -0000

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Thursday, May 30, 2013 8:29 AM
> To: Dave Thaler
> Cc: 6man-chairs@tools.ietf.org; Brian Haberman; 6man@ietf.org; Ray Hunter=
;
> Alissa Cooper; Christian Huitema; tom.petch; He Xuan
> Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
>=20
> On 05/29/2013 04:03 AM, Dave Thaler wrote:
> >>>> [...] I could rely on the
> >>>> ICMPv6 "address resolution failed" error messages sent by your
> >>>> local router (i.e., if I receive one of such messages, you're not
> >>>> there. If I don't,
> >> you are).
> >>>
> >>> Ok, yes that one is interesting.
> >>
> >> An attacker just needs one vector to be successful.
> >
> > Agree.  Putting the above example vector into the draft would help the
> > reader understand the motivation for the problem.
>=20
> Isn't it enough simply noting that the target node can be probed?
> Getting into the specific details of the probe packet
> (stimulus/response) seems like "over-specifying" things to me...

My opinion is that this example is important, since the example is
one where there's nothing the target node itself can do about it,
which is non-obvious.   Otherwise readers could be as confused as
I was.  So pointing it out adds significant clarity.

-Dave


From owen@delong.com  Thu May 30 09:04:11 2013
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9D421F96D9; Thu, 30 May 2013 09:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.903
X-Spam-Level: 
X-Spam-Status: No, score=-0.903 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id whEGMOPS3QaK; Thu, 30 May 2013 09:04:10 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 109E621F96EB; Thu, 30 May 2013 09:03:37 -0700 (PDT)
Received: from [10.26.83.252] (mobile-198-228-194-095.mycingular.net [198.228.194.95]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r4UFvgGq005530 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 30 May 2013 08:57:44 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r4UFvgGq005530
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1369929465; bh=5dmYaWdz9xHNf9g/4gp4C2SNdBY=; h=References:Mime-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:Message-Id:Cc:From:Subject:Date:To; b=RPgWo6FZDcoZcZgGdZN8bdSmjAKHjwYy41o+PNnPiWPDO3GvB+mrKm5zj7FxC03hc ueFuXlu6ayoKjHtWWn+wjVmF2KtOCEsZ35oDOpoYFDq6fOR36PPBLWra0FnYdGoPFE nAyK7aiGj4KyT8UAJIFl5VUoVCI1UqLYCpioz0jo=
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <5D36713D8A4E7348A7E10DF7437A4B923AC9924F@nkgeml512-mbx.china.huawei.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC9924F@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B817425-B386-4D9F-AD4C-DF69718411EE@delong.com>
X-Mailer: iPad Mail (10B329)
From: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Date: Thu, 30 May 2013 11:57:34 -0400
To: Sheng Jiang <jiangsheng@huawei.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Thu, 30 May 2013 08:57:45 -0700 (PDT)
X-Mailman-Approved-At: Thu, 30 May 2013 09:13:16 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 16:04:11 -0000

Sent from my iPad

On May 30, 2013, at 2:34 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> Hi, Owen,
>=20
> These embedded semantics are very different from End System Identifier. Th=
e end system identifier functions was problem because it violents the layer m=
odel. Many APPs or transport layer use IP address as their identifier. And t=
he end system identifier breaks in at least two scenarios: when end devices c=
hange the access points or when IP layer translation (NAT44 or NAT64) happen=
s.

I'm not sure how that's relevant to this discussion.

It does not change the fact that overloading semantics onto addresses is an i=
nherently bad idea.

> The proposed embedded semantics is still layer 3. They are used for router=
's packet processing. These embedded semantics is only meaningful locally wi=
thin ISP owner network. After leaving the ISP network, IP addresses are only=
 locator, nothing more. The bottom line is a network operator can choose to e=
mbedded some semantics into IPv6 addresses assignment. We, as IETF, may not e=
ncourage such usage, but should document it and may give some guidance or an=
alysis of it.

The problem with overloading semantics can occur regardless of whether or no=
t you cross layer boundaries.

You are creating artificial partitions of address space which creates the po=
ssibility of filling up one partition while space remains in another. This m=
ay create a situation where you are unable to get more space from the RIR or=
 upstream due to inefficient utilization and you are then forced to violate y=
our semantic boundaries just to keep the network running. Unfortunately, sin=
ce you've cultivated all these semantic assumptions in peoples heads (if not=
 running code), now you've got additional problems which last a very long ti=
me and don't necessarily appear right away.

It's a really great way to install time bombs in to operational systems. I d=
o not recommend it.

Owen

>=20
> Best regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: Owen DeLong [mailto:owen@delong.com]
>> Sent: Thursday, May 30, 2013 7:02 AM
>> To: Sheng Jiang
>> Cc: <v6ops@ietf.org>; ipv6@ietf.org;
>> draft-jiang-v6ops-semantic-prefix@tools.ietf.org
>> Subject: Re: [v6ops] Could IPv6 address be more than
>> locator?//draft-jiang-v6ops-semantic-prefix-03
>>=20
>> Personally, I think this is an inherently bad idea.
>>=20
>> IP addresses need less overloading of semantics, not more.
>>=20
>> We already use IP addresses for two conflicting purposes=E2=80=A6 Topolog=
y locator
>> and End System Identifier.
>>=20
>> This overloading is at the heart of our current scaling issues with respe=
ct to
>> the routing table. While these issues are currently less critical than th=
ey have
>> been in the past and will likely get quite a bit less critical in IPv6, t=
hat is only
>> because we have given up a fair amount of functionality to preserve
>> scalability in this regard.
>>=20
>> If we did not have this overloading, then an entity could obtain a set of=

>> end-system identifiers and keep them throughout their lifetime, regardles=
s of
>> topological changes. Today, where the addresses are overloaded with both
>> semantics, we either have to force most entities to change their numbers
>> when they change topology or we face unsustainable growth in the routing
>> tables.
>>=20
>> The idea of adding more semantics to addressing rather than seeking to
>> reduce this overloading seems a step in the wrong direction, IMHO.
>>=20
>> Owen
>>=20
>> On May 29, 2013, at 12:06 AM, Sheng Jiang <jiangsheng@huawei.com>
>> wrote:
>>=20
>>> IP addresses are designed as topology locator, so that every packet can b=
e
>> routed to its network destination.
>>>=20
>>> However, even in IPv4 era, some network operators have mapped their IP
>> address with certain semantic locally. These kind of mechanism explicitly=

>> express the semantic properties of every packet. Consequently, these netw=
ork
>> operators can inspect the properties of packets easily by mapping the
>> addresses back to semantic.
>>>=20
>>> Network operators, who have large IPv6 address space, may also choose to=

>> embedded some semantics into IPv6 addresses by assigning additional
>> significance to specific bits within the prefix.
>> draft-jiang-v6ops-semantic-prefix documents a framework method that
>> network operations may use their addresses with embedded semantics. These=

>> semantics bits are only meaningful within a single network, or group of
>> interconnected networks which share a common addressing policy. Based on
>> these embedded semantic bits in source/destination addresses, the network=

>> operators can accordingly treat network packets differently and efficient=
ly.
>>>=20
>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>>=20
>>> Could you please review this draft and comments? It will help the docume=
nt
>> become more useful information to be shared.
>>>=20
>>> Best regards,
>>>=20
>>> Sheng
>>>=20
>>>> -----Original Message-----
>>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>>> Sent: Tuesday, May 28, 2013 10:28 AM
>>>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang
>>>> Subject: New Version Notification for
>>>> draft-jiang-v6ops-semantic-prefix-03.txt
>>>>=20
>>>>=20
>>>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt
>>>> has been successfully submitted by Sheng Jiang and posted to the
>>>> IETF repository.
>>>>=20
>>>> Filename:     draft-jiang-v6ops-semantic-prefix
>>>> Revision:     03
>>>> Title:         A Framework for Semantic IPv6 Prefix
>>>> Creation date:     2013-05-28
>>>> Group:         Individual Submission
>>>> Number of pages: 19
>>>> URL:
>> http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03.=
txt
>>>> Status:
>>>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix
>>>> Htmlized:
>>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>>> Diff:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03=

>>>>=20
>>>> Abstract:
>>>> This document describes a framework method that network operations
>>>> may use their addresses.  Network operators, who have large IPv6
>>>> address space, may choose to embedded some semantics into IPv6
>>>> addresses by assigning additional significance to specific bits
>>>> within the prefix.  By embedded semantics into IPv6 prefixes, the
>>>> semantics of packets can be inspected easily.  Routers and other
>>>> intermediary devices can easily apply relevant policies as required.
>>>> Packet-level differentiation can also enable flow-level and user-
>>>> level differentiation.  Consequently, the network operators can
>>>> accordingly treat network packets differently and efficiently.  The
>>>> management and maintenance of networks can be much simpler.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The IETF Secretariat
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>=20

From owen@delong.com  Thu May 30 09:14:16 2013
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0634621F936E; Thu, 30 May 2013 09:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.053
X-Spam-Level: 
X-Spam-Status: No, score=-1.053 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTuer0C-5W-x; Thu, 30 May 2013 09:14:15 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 2B62E21F9347; Thu, 30 May 2013 09:14:14 -0700 (PDT)
Received: from [10.26.83.252] (mobile-198-228-194-095.mycingular.net [198.228.194.95]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r4UG8StT006049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 30 May 2013 09:08:30 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r4UG8StT006049
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1369930112; bh=gfqnnu8Nd0HwdJH49AgH/HRIYho=; h=References:Mime-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:Message-Id:Cc:From:Subject:Date:To; b=pIyILrsByk5bP1o/qrItvNNujiGdy63RPAqzuugglsf8a6z9H7Z16rO/A1jlFIfYK yvIaw7Lu2NiphMROOr5TnBe18QFTyKIKK3bSiGLhRqRUoL3DQd/iyy2peT9lrh05xU 3wPrlxJpOl39ODFLK8ll35Btlco8W3uYsDcZ9L3g=
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-2400563C-E085-4E7B-9E6A-8DBA89C6A4F4
Content-Transfer-Encoding: 7bit
Message-Id: <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com>
X-Mailer: iPad Mail (10B329)
From: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Date: Thu, 30 May 2013 12:08:28 -0400
To: Sheng Jiang <jiangsheng@huawei.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Thu, 30 May 2013 09:08:32 -0700 (PDT)
X-Mailman-Approved-At: Thu, 30 May 2013 09:15:16 -0700
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 16:14:16 -0000

--Apple-Mail-2400563C-E085-4E7B-9E6A-8DBA89C6A4F4
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

> >>However, it is not necessary as worse as 2^N times. For example, it ther=
e are 2 bits to separate different use types (say 4 different types), it act=
ually only separate use address spaces into four different spaces. It does n=
ot limit the address space to be 1/4 of original space.
>=20
> How is that different from saying "by adding two bits of semantics in the p=
refix, the network will use 4 times the address space than it would otherwis=
e"?
>=20
> No. This is very different. Putting the example into numbers may be more i=
ntuitionistic. Say an ISP has 4 million subscribers, it needs 4 million /56 (=
assuming every user get a /56). By separating them into 4 different types, t=
he address consumption is still 4 million /56 if the separation is exactly e=
ven. However, the more
>=20
Not a great assumption... They should need 4 million or more /48s since ever=
y subscriber is at least one end site and every subscriber end site should r=
eceive a /48.

Assuming that you will get 4 million subscribers that conveniently divide in=
to buckets of 1 million per bucket is absurd. More likely, you'll get 500,00=
0, 750,000, 2,000,000, and 750,000, or other similarly skewed distribution. I=
t might even be 3,500,000, 125,000, 125,000, 250,000.
> address may need when the separation is not even. For example, if the bigg=
est user type has 2 million users, then the total address space may become 8=
 million /56 =E2=80=93 two times of original. It comes from align. The incre=
ased semantics bit are also increasing the address space although not increa=
sing linearly. So, at the end, it is not totally waste.
>=20
If you get extraordinarily lucky, it's no waste. Otherwise, it's at least 50=
% waste and can easily reach 75% waste (4x space utilization, as Lorenzo sai=
d).

For example, if you have 4,000,000 end sites and you get as little as 2,097,=
153 subscribers in one of the buckets, you have to go to 4x your address spa=
ce to preserve the semantics.

Owen

> Best regards,
>=20
> Sheng
>=20
> From: Lorenzo Colitti [mailto:lorenzo@google.com]=20
> Sent: Thursday, May 30, 2013 3:19 PM
> To: Sheng Jiang
> Cc: Tim Chown; Owen DeLong; <v6ops@ietf.org>; draft-jiang-v6ops-semantic-p=
refix@tools.ietf.org; ipv6@ietf.org
> Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang=
-v6ops-semantic-prefix-03
>=20
> =20
>=20
> On Thu, May 30, 2013 at 4:13 PM, Sheng Jiang <jiangsheng@huawei.com> wrote=
:
>=20
> Yes, there is no intension to change ARIN=E2=80=99s policy at all. ARIN sh=
ould remain the current policy of assign IPv6 address block. But the network=
 providers, who has already get address block, can choose to use the address=
es with certain semantics. And no one, including ARIN can stop this.
>=20
> =20
>=20
> Agreed, but even for network providers that already have blocks, this will=
 be an issue if they ever need another block. But I do think you should writ=
e this in the draft.
>=20
> =20
>=20
> However, it is not necessary as worse as 2^N times. For example, it there a=
re 2 bits to separate different use types (say 4 different types), it actual=
ly only separate use address spaces into four different spaces. It does not l=
imit the address space to be 1/4 of original space.
>=20
> =20
>=20
> How is that different from saying "by adding two bits of semantics in the p=
refix, the network will use 4 times the address space than it would otherwis=
e"?

--Apple-Mail-2400563C-E085-4E7B-9E6A-8DBA89C6A4F4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><blockquote type=3D"cite"><div><div class=3D=
"WordSection1"><p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-m=
argin-bottom-alt:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&gt;&gt;Howe=
ver, it is not necessary as worse as 2^N times. For example, it there are 2 b=
its
 to separate different use types (say 4 different types), it actually only s=
eparate use address spaces into four different spaces. It does not limit the=
 address space to be 1/4 of original space.</span><span lang=3D"EN-US"><o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">How is that different from sayin=
g "by adding two bits of semantics in the prefix, the network will use 4 tim=
es the address space than it would otherwise"?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">No. This is very different.=
 Putting the example into numbers may be more intuitionistic.
 Say an ISP has 4 million subscribers, it needs 4 million /56 (assuming ever=
y user get a /56). By separating them into 4 different types, the address co=
nsumption is still 4 million /56 if the separation is exactly even. However,=
 the more</span></p></div></div></blockquote><div>Not a great assumption... T=
hey should need 4 million or more /48s since every subscriber is at least on=
e end site and every subscriber end site should receive a /48.</div><div><br=
></div><div>Assuming that you will get 4 million subscribers that convenient=
ly divide into buckets of 1 million per bucket is absurd. More likely, you'l=
l get 500,000, 750,000, 2,000,000, and 750,000, or other similarly skewed di=
stribution. It might even be 3,500,000, 125,000, 125,000, 250,000.</div><blo=
ckquote type=3D"cite"><div><div class=3D"WordSection1"><p class=3D"MsoNormal=
" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=3D=
"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D"> address may need when
 the separation is not even. For example, if the biggest user type has 2 mil=
lion users, then the total address space may become 8 million /56 =E2=80=93 t=
wo times of original. It comes from align. The increased semantics bit are a=
lso increasing the address space although
 not increasing linearly. So, at the end, it is not totally waste.</span></p=
></div></div></blockquote><div>If you get extraordinarily lucky, it's no was=
te. Otherwise, it's at least 50% waste and can easily reach 75% waste (4x sp=
ace utilization, as Lorenzo said).</div><div><br></div><div>For example, if y=
ou have 4,000,000 end sites and you get as little as 2,097,153 subscribers i=
n one of the buckets, you have to go to 4x your address space to preserve th=
e semantics.</div><div><br></div><div>Owen</div><div><br></div><blockquote t=
ype=3D"cite"><div><div class=3D"WordSection1"><p class=3D"MsoNormal" style=3D=
"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang=3D"EN-US" st=
yle=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Best regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Sheng<o:p></o:p></span></p>=

<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4=
.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0=
cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span la=
ng=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;=
sans-serif&quot;"> Lorenzo Colitti [<a href=3D"mailto:lorenzo@google.com">ma=
ilto:lorenzo@google.com</a>]
<br>
<b>Sent:</b> Thursday, May 30, 2013 3:19 PM<br>
<b>To:</b> Sheng Jiang<br>
<b>Cc:</b> Tim Chown; Owen DeLong; &lt;<a href=3D"mailto:v6ops@ietf.org">v6o=
ps@ietf.org</a>&gt;; <a href=3D"mailto:draft-jiang-v6ops-semantic-prefix@too=
ls.ietf.org">draft-jiang-v6ops-semantic-prefix@tools.ietf.org</a>; <a href=3D=
"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
<b>Subject:</b> Re: [v6ops] Could IPv6 address be more than locator?//draft-=
jiang-v6ops-semantic-prefix-03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Thu, May 30, 2013 at 4:13 PM,=
 Sheng Jiang &lt;<a href=3D"mailto:jiangsheng@huawei.com" target=3D"_blank">=
jiangsheng@huawei.com</a>&gt; wrote:<o:p></o:p></span></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm=
 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yes, there is no intension t=
o change ARIN=E2=80=99s policy at all. ARIN should remain the current
 policy of assign IPv6 address block. But the network providers, who has alr=
eady get address block, can choose to use the addresses with certain semanti=
cs. And no one, including ARIN can stop this.</span><span lang=3D"EN-US"><o:=
p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Agreed, but even for network pro=
viders that already have blocks, this will be an issue if they ever need ano=
ther block. But I do think you should write this in the draft.<o:p></o:p></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;<o:p></o:p></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm=
 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-al=
t:auto"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:#1F497D">However, it is not necessar=
y as worse as 2^N times. For example, it there are 2 bits
 to separate different use types (say 4 different types), it actually only s=
eparate use address spaces into four different spaces. It does not limit the=
 address space to be 1/4 of original space.</span><span lang=3D"EN-US"><o:p>=
</o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">How is that different from sayin=
g "by adding two bits of semantics in the prefix, the network will use 4 tim=
es the address space than it would otherwise"?<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>


</div></blockquote></body></html>=

--Apple-Mail-2400563C-E085-4E7B-9E6A-8DBA89C6A4F4--

From joelja@bogus.com  Thu May 30 12:18:05 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D541B21F92BB; Thu, 30 May 2013 12:18:05 -0700 (PDT)
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_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MbSo3HY2xzMi; Thu, 30 May 2013 12:18:05 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B9F8221F8F11; Thu, 30 May 2013 12:17:48 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4UJHAa4039626 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 30 May 2013 19:17:11 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A7A5B1.3050709@bogus.com>
Date: Thu, 30 May 2013 12:17:05 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>	<03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk>	<8E492087-390E-4F8E-8078-1D0E63849243@delong.com>	<EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 30 May 2013 19:17:11 +0000 (UTC)
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 19:18:06 -0000

On 5/29/13 11:47 PM, Lorenzo Colitti wrote:
> On Thu, May 30, 2013 at 3:33 PM, Tim Chown <tjc@ecs.soton.ac.uk 
> <mailto:tjc@ecs.soton.ac.uk>> wrote:
>
>     I agree. That said, an ISP, enterprise or group of organisations
>     can follow whatever semantics they wish within their own borders.
>
>
> As long as the RIRs are willing to give them enough address space to 
> do so.
>
> If an ISP requested an IPv6 /10 from ARIN because they wanted to give 
> every customer a /48 and wanted to geocode the customer's subscriber 
> ID into the /48, then ARIN would do well to say, "no, sorry, that 
> doesn't make sense".
>
> Lest someone not realize this, the draft should clearly state that 
> embedding N bits of semantics into IPv6 addresses causes the network 
> to use 2^N times the address space that it normally would.
>
pretty much what I said at the mic... If this ever shows up in a 
jsutification for a /18 or /24 vs a  /26 at an RIR that's a really bad 
thing imho.
> IMO I think it should also state that although it is an IETF RFC, this 
> model is not necessarily a recommended model, and that RIRs are not 
> obliged to accept this type of address allocation as a justification 
> for obtaining larger address blocks than they would normally be able 
> to obtain.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From Ted.Lemon@nominum.com  Thu May 30 12:29:15 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D52C721F922A; Thu, 30 May 2013 12:29:15 -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.046, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NF24QxfjBlBd; Thu, 30 May 2013 12:29:09 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 10EB821F911B; Thu, 30 May 2013 12:29:08 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUaeogzki/uaMjGxg8eDTuDg0ZOuDZyo9@postini.com; Thu, 30 May 2013 12:29:09 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 888F21B81BF; Thu, 30 May 2013 12:29:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7D350190052; Thu, 30 May 2013 12:29:07 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 30 May 2013 12:29:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXVDE6lnGpdObXU2opXguZDBozpkekp0A
Date: Thu, 30 May 2013 19:29:07 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com>
In-Reply-To: <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751BD21Embx01winnominum_"
MIME-Version: 1.0
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 19:29:16 -0000

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

On May 30, 2013, at 12:08 PM, Owen DeLong <owen@delong.com<mailto:owen@delo=
ng.com>> wrote:
Not a great assumption... They should need 4 million or more /48s since eve=
ry subscriber is at least one end site and every subscriber end site should=
 receive a /48.

I am not in love with using bits from prefixes as semantic tags.   However,=
 having said that, I think it's a bit ironic that you're talking about wast=
ing space with semantic bits, on the one hand, and talking about the need f=
or a /48 in every home on the other.   It would be perfectly reasonable for=
 the ISP to specify that some of the bits in the /48 have semantic meaning,=
 for example, and given that we think it's okay to give the home network a =
/48, we are hardly in a position to quibble about how the bits in that /48 =
are used.


--_000_8D23D4052ABE7A4490E77B1A012B6307751BD21Embx01winnominum_
Content-Type: text/html; charset="us-ascii"
Content-ID: <C9D78B3D7644C74C9EF8D9CC3860B9EB@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On May 30, 2013, at 12:08 PM, Owen DeLong &lt;<a href=3D"mailto:owen@d=
elong.com">owen@delong.com</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Not a great assumption... They should need 4 million or more /48s since eve=
ry subscriber is at least one end site and every subscriber end site should=
 receive a /48.</div>
</blockquote>
</div>
<br>
<div>I am not in love with using bits from prefixes as semantic tags. &nbsp=
; However, having said that, I think it's a bit ironic that you're talking =
about wasting space with semantic bits, on the one hand, and talking about =
the need for a /48 in every home on the
 other. &nbsp; It would be perfectly reasonable for the ISP to specify that=
 some of the bits in the /48 have semantic meaning, for example, and given =
that we think it's okay to give the home network a /48, we are hardly in a =
position to quibble about how the bits
 in that /48 are used.</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751BD21Embx01winnominum_--

From jeremy.duncan@salientfed.com  Thu May 30 12:30:07 2013
Return-Path: <jeremy.duncan@salientfed.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922C121F9413; Thu, 30 May 2013 12:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.996
X-Spam-Level: 
X-Spam-Status: No, score=-0.996 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, TRACKER_ID=2.003]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMIaw-SIGfXS; Thu, 30 May 2013 12:30:02 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe004.messaging.microsoft.com [216.32.180.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3CB21F93FF; Thu, 30 May 2013 12:30:02 -0700 (PDT)
Received: from mail56-va3-R.bigfish.com (10.7.14.243) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Thu, 30 May 2013 19:30:01 +0000
Received: from mail56-va3 (localhost [127.0.0.1])	by mail56-va3-R.bigfish.com (Postfix) with ESMTP id 39E8D2A00C9; Thu, 30 May 2013 19:30:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.236.101; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: PS-26(zz98dI9371I936eI542I1432Idf9Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz2fh2a8h668h839h946hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1155h)
Received-SPF: pass (mail56-va3: domain of salientfed.com designates 157.56.236.101 as permitted sender) client-ip=157.56.236.101; envelope-from=jeremy.duncan@salientfed.com; helo=BY2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail56-va3 (localhost.localdomain [127.0.0.1]) by mail56-va3 (MessageSwitch) id 1369942197699664_27880; Thu, 30 May 2013 19:29:57 +0000 (UTC)
Received: from VA3EHSMHS003.bigfish.com (unknown [10.7.14.244])	by mail56-va3.bigfish.com (Postfix) with ESMTP id A65221A0173; Thu, 30 May 2013 19:29:57 +0000 (UTC)
Received: from BY2PRD0510HT005.namprd05.prod.outlook.com (157.56.236.101) by VA3EHSMHS003.bigfish.com (10.7.99.13) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 30 May 2013 19:29:57 +0000
Received: from BY2PRD0510MB366.namprd05.prod.outlook.com ([169.254.5.143]) by BY2PRD0510HT005.namprd05.prod.outlook.com ([10.255.84.40]) with mapi id 14.16.0311.000; Thu, 30 May 2013 19:29:51 +0000
From: "Duncan, Richard (Jeremy)" <jeremy.duncan@salientfed.com>
To: Sheng Jiang <jiangsheng@huawei.com>, Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcyJkAgAA3SeuAAEobgIAA1Jq2
Date: Thu, 30 May 2013 19:29:50 +0000
Message-ID: <923297B868FB664FBFA90FCC255696DF591E69CC@BY2PRD0510MB366.namprd05.prod.outlook.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>, <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <eg56ow4ob19bwj5507xajo8n.1369880374960@email.android.com>, <5D36713D8A4E7348A7E10DF7437A4B923AC9927B@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC9927B@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [214.3.40.3]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: salientfed.com
X-Mailman-Approved-At: Thu, 30 May 2013 12:32:36 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 19:30:07 -0000

Sheng-=0A=
=0A=
Not following..  If the provider puts semantics on bits 30-32, and I had a =
need for services covered by other bits I would then need to have a multi-d=
isparate allocation of say (3) /48s - or (3) /52s, whatever.  Then the prov=
ider will have a lot of unused space inside their /30 for services.=0A=
=0A=
I just don't understanding why using HbH options, TC for DiffServ or the FL=
 doesn't already answer the mail?  If this was my providers plan, I would s=
hop for another provider.=0A=
=0A=
=0A=
010100110110010101101101011100000110010101110010001000000100011001101001=0A=
=0A=
Jeremy Duncan=0A=
Senior Director, IPv6 Network Architect Salient Federal Solutions, Inc.=0A=
(Now including SGIS & Command Information Inc.)=0A=
4000 Legato Road, Suite 600 Fairfax, VA 22033=0A=
Google Voice:  540.440.1193=0A=
jeremy.duncan@salientfed.com=0A=
=0A=
________________________________________=0A=
From: Sheng Jiang [jiangsheng@huawei.com]=0A=
Sent: Thursday, May 30, 2013 2:45 AM=0A=
To: Duncan, Richard (Jeremy); Owen DeLong=0A=
Cc: <v6ops@ietf.org>; draft-jiang-v6ops-semantic-prefix@tools.ietf.org; ipv=
6@ietf.org=0A=
Subject: RE: [v6ops] Could IPv6 address be more than    locator?//draft-jia=
ng-v6ops-semantic-prefix-03=0A=
=0A=
Hi, Duncan,=0A=
=0A=
Actually, you question is very detailed scenario in the approach. The answe=
r is the provider still assign a /48 to an organization. But within the ass=
igned /48, some bit (for example, bit no. 30~32) has some semantic (for exa=
mple, need extra security processing) for the assigning provider. Then, whe=
n the provider received packets from such organizations (there are multiple=
 enterprise has the same semantic and the same bit no. 30~32), it can treat=
 accordingly.=0A=
=0A=
Best regards,=0A=
=0A=
Sheng=0A=
=0A=
>-----Original Message-----=0A=
>From: Duncan, Richard (Jeremy) [mailto:jeremy.duncan@salientfed.com]=0A=
>Sent: Thursday, May 30, 2013 10:20 AM=0A=
>To: Owen DeLong=0A=
>Cc: Sheng Jiang; <v6ops@ietf.org>;=0A=
>draft-jiang-v6ops-semantic-prefix@tools.ietf.org; ipv6@ietf.org=0A=
>Subject: Re: [v6ops] Could IPv6 address be more than=0A=
>locator?//draft-jiang-v6ops-semantic-prefix-03=0A=
>=0A=
>I tend to agree with Owen here.  In fact, I am curious how an allocation=
=0A=
>from a provider to a organization would look?  Instead of following standa=
rd=0A=
>issuing practices of a /48, are you suggesting the provider would issue=0A=
>multiple /52s that follow functional categories (VoIP, management, etc)?  =
Or=0A=
>maybe I missed something?=0A=
>=0A=
>=0A=
>010100110110010101101101011100000110010101110010001000000100011=0A=
>001101001=0A=
>=0A=
>Jeremy Duncan=0A=
>Senior Director, IPv6 Network Architect=0A=
>Salient Federal Solutions, Inc. (Now including SGIS & Command Information=
=0A=
>Inc.)=0A=
>4000 Legato Road, Suite 600=0A=
>Fairfax, VA 22033=0A=
>Google Voice: 540.440.1193=0A=
>jeremy.duncan@salientfed.com=0A=
>=0A=
>Owen DeLong <owen@delong.com> wrote:=0A=
>=0A=
>=0A=
>Personally, I think this is an inherently bad idea.=0A=
>=0A=
>IP addresses need less overloading of semantics, not more.=0A=
>=0A=
>We already use IP addresses for two conflicting purposes=85 Topology locat=
or=0A=
>and End System Identifier.=0A=
>=0A=
>This overloading is at the heart of our current scaling issues with respec=
t to=0A=
>the routing table. While these issues are currently less critical than the=
y have=0A=
>been in the past and will likely get quite a bit less critical in IPv6, th=
at is only=0A=
>because we have given up a fair amount of functionality to preserve=0A=
>scalability in this regard.=0A=
>=0A=
>If we did not have this overloading, then an entity could obtain a set of=
=0A=
>end-system identifiers and keep them throughout their lifetime, regardless=
 of=0A=
>topological changes. Today, where the addresses are overloaded with both=
=0A=
>semantics, we either have to force most entities to change their numbers=
=0A=
>when they change topology or we face unsustainable growth in the routing=
=0A=
>tables.=0A=
>=0A=
>The idea of adding more semantics to addressing rather than seeking to=0A=
>reduce this overloading seems a step in the wrong direction, IMHO.=0A=
>=0A=
>Owen=0A=
>=0A=
>On May 29, 2013, at 12:06 AM, Sheng Jiang <jiangsheng@huawei.com>=0A=
>wrote:=0A=
>=0A=
>> IP addresses are designed as topology locator, so that every packet can =
be=0A=
>routed to its network destination.=0A=
>>=0A=
>> However, even in IPv4 era, some network operators have mapped their IP=
=0A=
>address with certain semantic locally. These kind of mechanism explicitly=
=0A=
>express the semantic properties of every packet. Consequently, these netwo=
rk=0A=
>operators can inspect the properties of packets easily by mapping the=0A=
>addresses back to semantic.=0A=
>>=0A=
>> Network operators, who have large IPv6 address space, may also choose to=
=0A=
>embedded some semantics into IPv6 addresses by assigning additional=0A=
>significance to specific bits within the prefix.=0A=
>draft-jiang-v6ops-semantic-prefix documents a framework method that=0A=
>network operations may use their addresses with embedded semantics. These=
=0A=
>semantics bits are only meaningful within a single network, or group of=0A=
>interconnected networks which share a common addressing policy. Based on=
=0A=
>these embedded semantic bits in source/destination addresses, the network=
=0A=
>operators can accordingly treat network packets differently and efficientl=
y.=0A=
>>=0A=
>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03=0A=
>>=0A=
>> Could you please review this draft and comments? It will help the docume=
nt=0A=
>become more useful information to be shared.=0A=
>>=0A=
>> Best regards,=0A=
>>=0A=
>> Sheng=0A=
>>=0A=
>>> -----Original Message-----=0A=
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=0A=
>>> Sent: Tuesday, May 28, 2013 10:28 AM=0A=
>>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang=0A=
>>> Subject: New Version Notification for=0A=
>>> draft-jiang-v6ops-semantic-prefix-03.txt=0A=
>>>=0A=
>>>=0A=
>>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt=0A=
>>> has been successfully submitted by Sheng Jiang and posted to the=0A=
>>> IETF repository.=0A=
>>>=0A=
>>> Filename:     draft-jiang-v6ops-semantic-prefix=0A=
>>> Revision:     03=0A=
>>> Title:                A Framework for Semantic IPv6 Prefix=0A=
>>> Creation date:        2013-05-28=0A=
>>> Group:                Individual Submission=0A=
>>> Number of pages: 19=0A=
>>> URL:=0A=
>>>=0A=
>http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03.t=
xt=0A=
>>> Status:=0A=
>>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix=0A=
>>> Htmlized:=0A=
>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03=0A=
>>> Diff:=0A=
>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03=
=0A=
>>>=0A=
>>> Abstract:=0A=
>>>  This document describes a framework method that network operations=0A=
>>>  may use their addresses.  Network operators, who have large IPv6=0A=
>>>  address space, may choose to embedded some semantics into IPv6=0A=
>>>  addresses by assigning additional significance to specific bits=0A=
>>>  within the prefix.  By embedded semantics into IPv6 prefixes, the=0A=
>>>  semantics of packets can be inspected easily.  Routers and other=0A=
>>>  intermediary devices can easily apply relevant policies as required.=
=0A=
>>>  Packet-level differentiation can also enable flow-level and user-=0A=
>>>  level differentiation.  Consequently, the network operators can=0A=
>>>  accordingly treat network packets differently and efficiently.  The=0A=
>>>  management and maintenance of networks can be much simpler.=0A=
>>>=0A=
>>>=0A=
>>>=0A=
>>>=0A=
>>> The IETF Secretariat=0A=
>>=0A=
>> _______________________________________________=0A=
>> v6ops mailing list=0A=
>> v6ops@ietf.org=0A=
>> https://www.ietf.org/mailman/listinfo/v6ops=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=


From brian.e.carpenter@gmail.com  Thu May 30 13:42:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C56B21F91B1 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 13:42:36 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqqcqDwZfZB9 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 13:42:35 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 33C4921F91A5 for <ipv6@ietf.org>; Thu, 30 May 2013 13:42:35 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so1003629pbb.33 for <ipv6@ietf.org>; Thu, 30 May 2013 13:42:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=6mMfi5ffH2mR5IKvjLFW6Od3T8P6pIBJQ+tkLIrHokI=; b=y+QNSTB3c/zTJCUg4KOThVvxdJirGo56DviXKLcR+iSqtNGQp67gZ6mOrLywhHCzYi 9NZa+6bk8I/ECux2tzvrPNIz8kSrVuLlonyM6V6WLYaEvw+x4wXx3bSjuY9lxqlahEr4 x16Dv9nqKnbzlnS+ibFoks2IEe0wPDDI3PU3M/pgAs/E2jq8Om973UaolBfKSmhVmA9D /HJs0FAUYFeO6Hl3a1BaKrZQkzV+pWJ9IAbS8hFLBCZafug4J0KLytC5PNd7PfAnGP4x vEo4dzIIkAObYh+BD1dwMbIMIKqlB0/lfHpuYNUtfggqZ/n46LVub+Ri3ib0KwAtotU2 8Ruw==
X-Received: by 10.67.21.226 with SMTP id hn2mr9736364pad.135.1369946554998; Thu, 30 May 2013 13:42:34 -0700 (PDT)
Received: from [192.168.1.2] (166.193.252.27.dyn.cust.vf.net.nz. [27.252.193.166]) by mx.google.com with ESMTPSA id k8sm39530050pag.18.2013.05.30.13.42.32 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 13:42:33 -0700 (PDT)
Message-ID: <51A7B9C1.6020100@gmail.com>
Date: Fri, 31 May 2013 08:42:41 +1200
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: draft-ietf-6man-oversized-header-chain?
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 30 May 2013 20:42:36 -0000

Hi,

What's up with draft-ietf-6man-oversized-header-chain? The tracker
says it has been in WGLC since February...

Regards
   Brian

From fgont@si6networks.com  Thu May 30 17:53:40 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630FB21F8F4A for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 17:53:40 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kasBN0-KNIoB for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 17:53:39 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 983B321F8EFE for <ipv6@ietf.org>; Thu, 30 May 2013 17:53:39 -0700 (PDT)
Received: from [2001:5c0:1400:a::257] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UiDb8-0004gR-7P; Fri, 31 May 2013 02:53:38 +0200
Message-ID: <51A7F48F.9080400@si6networks.com>
Date: Fri, 31 May 2013 02:53:35 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-ietf-6man-oversized-header-chain?
References: <51A7B9C1.6020100@gmail.com>
In-Reply-To: <51A7B9C1.6020100@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 00:53:40 -0000

On 05/30/2013 10:42 PM, Brian E Carpenter wrote:
> Hi,
> 
> What's up with draft-ietf-6man-oversized-header-chain? The tracker
> says it has been in WGLC since February...

I'll be posting an update this weekend. Sorry for the delay -- a few
personal things happened that got me sidetracked (including a car
accident -- although everything's fine now).

Thanks for checking!

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





From jiangsheng@huawei.com  Thu May 30 18:39:06 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E6221F86DD; Thu, 30 May 2013 18:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level: 
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofKDyxnDqh5W; Thu, 30 May 2013 18:39:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B844421F8FAF; Thu, 30 May 2013 18:39:00 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ02100; Fri, 31 May 2013 01:38:59 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 02:38:26 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 09:38:58 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Fri, 31 May 2013 09:38:55 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kc8GIAgACHYyD//5aGgIABdpag
Date: Fri, 31 May 2013 01:38:55 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net>
In-Reply-To: <51A733E1.7040008@globis.net>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 01:39:06 -0000

Pj4gU2hlbmcgSmlhbmcgPG1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20+DQo+PiAzMCBNYXkg
MjAxMyAxMTo1OA0KPj4+PiBJUCBhZGRyZXNzZXMgYXJlIGRlc2lnbmVkIGFzIHRvcG9sb2d5IGxv
Y2F0b3IsIHNvIHRoYXQgZXZlcnkgcGFja2V0IGNhbg0KPmJlDQo+Pj4gcm91dGVkIHRvIGl0cyBu
ZXR3b3JrIGRlc3RpbmF0aW9uLg0KPj4+PiBIb3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBzb21l
IG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyIElQDQo+Pj4gYWRkcmVzcyB3aXRo
IGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5pc20gZXhwbGlj
aXRseQ0KPj4+IGV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRpZXMgb2YgZXZlcnkgcGFja2V0
LiBDb25zZXF1ZW50bHksIHRoZXNlDQo+bmV0d29yaw0KPj4+IG9wZXJhdG9ycyBjYW4gaW5zcGVj
dCB0aGUgcHJvcGVydGllcyBvZiBwYWNrZXRzIGVhc2lseSBieSBtYXBwaW5nIHRoZQ0KPj4+IGFk
ZHJlc3NlcyBiYWNrIHRvIHNlbWFudGljLg0KPj4+PiBOZXR3b3JrIG9wZXJhdG9ycywgd2hvIGhh
dmUgbGFyZ2UgSVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbyBjaG9vc2UNCj50bw0KPj4+IGVt
YmVkZGVkIHNvbWUgc2VtYW50aWNzIGludG8gSVB2NiBhZGRyZXNzZXMgYnkgYXNzaWduaW5nIGFk
ZGl0aW9uYWwNCj4+PiBzaWduaWZpY2FuY2UgdG8gc3BlY2lmaWMgYml0cyB3aXRoaW4gdGhlIHBy
ZWZpeC4NCj4+PiBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXggZG9jdW1lbnRzIGEg
ZnJhbWV3b3JrIG1ldGhvZCB0aGF0DQo+Pj4gbmV0d29yayBvcGVyYXRpb25zIG1heSB1c2UgdGhl
aXIgYWRkcmVzc2VzIHdpdGggZW1iZWRkZWQgc2VtYW50aWNzLg0KPlRoZXNlDQo+Pj4gc2VtYW50
aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBzaW5nbGUgbmV0d29yaywgb3Ig
Z3JvdXAgb2YNCj4+PiBpbnRlcmNvbm5lY3RlZCBuZXR3b3JrcyB3aGljaCBzaGFyZSBhIGNvbW1v
biBhZGRyZXNzaW5nIHBvbGljeS4gQmFzZWQNCj5vbg0KPj4+IHRoZXNlIGVtYmVkZGVkIHNlbWFu
dGljIGJpdHMgaW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlDQo+bmV0d29yaw0K
Pj4+IG9wZXJhdG9ycyBjYW4gYWNjb3JkaW5nbHkgdHJlYXQgbmV0d29yayBwYWNrZXRzIGRpZmZl
cmVudGx5IGFuZCBlZmZpY2llbnRseS4NCj4+Pj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+DQo+Pj4+IENvdWxkIHlv
dSBwbGVhc2UgcmV2aWV3IHRoaXMgZHJhZnQgYW5kIGNvbW1lbnRzPyBJdCB3aWxsIGhlbHAgdGhl
DQo+ZG9jdW1lbnQNCj4+PiBiZWNvbWUgbW9yZSB1c2VmdWwgaW5mb3JtYXRpb24gdG8gYmUgc2hh
cmVkLg0KPj4+PiBCZXN0IHJlZ2FyZHMsDQo+Pj4+DQo+Pj4+IFNoZW5nDQo+Pj4+DQo+Pj4gSSBj
b21wbGV0ZWx5IHVuZGVyc3RhbmQgdGhlIGRlc2lyZSBmb3Igb3BlcmF0b3JzIHRvIGhhdmUgYWRk
aXRpb25hbA0KPj4+IHNlbWFudGljcyBhdmFpbGFibGUgZm9yIGN1c3RvbWl6ZWQgcGFja2V0IHBy
b2Nlc3NpbmcuIEZsb3cgbGFiZWwgbm93IGhhcw0KPj4+IHZlcnkgbGltaXRlZCBwcm9wZXJ0aWVz
IG9wdGltaXNlZCBmb3IgbG9hZCBiYWxhbmNlcnMuIERTQ1Agb25seSBoYXMgYQ0KPj4+IGZldyBi
aXRzICh3YXkgbGVzcyB0aGFuIHRoZSBudW1iZXIgb2YgY3VzdG9tZXJzJyBwb2xpY2llcykuIEFD
THMgYXJlDQo+Pj4gaGVhdnkgdG8gcHJvY2VzcyBhdCBlYWNoIGhvcC4uLi4NCj4+Pg0KPj4+IEJ1
dCB3b3VsZG4ndCB0aGlzIGluZm9ybWF0aW9uIGJlIGJldHRlciBvZmYgZW5jb2RlZCBhcyB0YWdz
IGluIG9uZSBvcg0KPj4+IG1vcmUgaG9wLWJ5LWhvcCBoZWFkZXIgb3B0aW9ucyAodGhhdCBjb3Vs
ZCBiZSByZS13cml0dGVuIG9uIHRoZSBmbHkpLA0KPj4+IHJhdGhlciB0aGFuIGVuY29kZWQgaW4g
dGhlIElQdjYgYWRkcmVzcyBzcGFjZT8NCj4+DQo+PiBUaGUgc2VjdGlvbiA0LjEgIkp1c3RpZmNh
dGlvbiBmb3IgU2VtYW50aWNzIHdpdGggdGhlIElQdjYgUHJlZml4IiBkZXNjcmliZXMNCj50aGUg
cmVhc29ucy4NCj4+DQo+PiBVc2VycyBtYXkgZWFzaWx5IGNoYW5nZSB0aGUgc2V0dGluZyBvZiBl
eHRlbnNpb24gaGVhZGVyIGluIG9yZGVyIHRvIG9idGFpbg0KPnVuZGVzZXJ2ZWQgcHJpb3JpdGll
cy9wcml2aWxlZ2VzLiBTZW1hbnRpYyBwcmVmaXggYXBwcm9hY2ggZG9lcyByZXF1aXJlIHRoZQ0K
PmRlcGxveW1lbnQgb2YgYWNjZXNzIGNvbnRyb2wgZmlsdGVycy4gVGhlIHBhY2tldHMgd2l0aCB0
aGUgbm9uY29tcGxpYW5jZQ0KPnNvdXJjZSBhZGRyZXNzZXMgc2hvdWxkIGJlIGZpbHRlcmVkLiBU
aGUgcHJlZml4IGlzIGRlbGVnYXRlZCBieSB0aGUgbmV0d29yay4NCj5UaGVyZWZvcmUgdGhlIG5l
dHdvcmsgaXMgYWJsZSB0byBkZXRlY3QgYW55IHVuZGVzaXJlZCBtb2RpZmljYXRpb25zIGFuZCBm
aWx0ZXINCj50aGUgcGFja2V0IGFjY29yZGluZ2x5Lg0KPj4NCj4+IENoZWVycywNCj4+DQo+PiBT
aGVuZw0KPj4NCj4+DQo+SSBkb24ndCBidXkgeW91ciBqdXN0aWZpY2F0aW9uLiBXaGV0aGVyIGFu
IG9wZXJhdG9yIGZpbHRlcnMgb24NCj5hdXRob3Jpc2VkIGFkZHJlc3MgcmFuZ2Ugb3IgcmUtd3Jp
dGVzL2ZpbHRlcnMgYW4gdW5hdXRob3Jpc2VkIGhvcC1ieS1ob3ANCj50YWcgaXMgZWZmZWN0aXZl
bHkgdGhlIHNhbWUgSU1ITy4gV2UgaGF2ZSBleGFjdGx5IHRoZSBzYW1lIGlzc3VlcyBvZg0KPnBv
dGVudGlhbCB0aGVmdCBvZiBzZXJ2aWNlIHdpdGggRFNDUCB0b2RheSwgYW5kIHRoZSBzb2x1dGlv
biBpcyBlcXVhbGx5DQo+c2ltcGxlOiBEU0NQIG1hcmtkb3duIGF0IHRoZSBpbmdyZXNzIHBvcnQu
DQoNClllcywgdGhlIHRydXN0IGlzc3VlIGlzIHRoZSBzYW1lIHdpdGggRFNDUC4gSG93ZXZlciwg
dGhlIERTQ1AgYWJzdHJhY3QgYWxsIHRoZSBzZW1hbnRpY3MgaW50byBzZXJ2aWNlIGNsYXNzZXMs
IHdoaWNoIGlzIG9uZSBzaW5nbGUgZGltZW5zaW9uLiBUaGlzIGFic3RyYWN0IHByb2Nlc3Npbmcg
aGFzIGxvc3QgYSBsb3Qgb2YgaW5mb3JtYXRpb24sIHdoaWNoIHByb3ZpZGVycyB3YW50IHRvIGlu
c3BlY3QgZm9yIGV2ZXJ5IHBhY2tldCwgdGhlbiBwcm9jZXNzIHRoZSBwYWNrZXQgYWNjb3JkaW5n
bHkuIFRoZSBleHBsaWNpdGx5IGV4cHJlc3NlZCBzZW1hbnRpY3MgaW4gcHJlZml4IHByb3ZpZGVz
IG11Y2ggbW9yZSBpbmZvcm1hdGlvbnMNCg0KU2hlbmcNCg0KPnJlZ2FyZHMsDQo+UmF5SA0K

From ggm@algebras.org  Thu May 30 18:40:36 2013
Return-Path: <ggm@algebras.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2986E21F91CB for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 18:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-b+B32pjGI8 for <ipv6@ietfa.amsl.com>; Thu, 30 May 2013 18:40:35 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E1C3021F9180 for <ipv6@ietf.org>; Thu, 30 May 2013 18:40:34 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so1348787pbb.5 for <ipv6@ietf.org>; Thu, 30 May 2013 18:40:34 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=KYTz0TL6NWBHgH++oTG6OPnPH9CEKUvjjRiPwPLw+BM=; b=pU+dbpyIcoHWY0EBMC4/M1yK5UWNrjT6G4O+qZvQYQpZJ0OzoEnkL+Oz60ofymcOGu VqkVzNDK7TNiaijqeMzNvJVUzslWHWZSs3KtAEbmBAVN43v/d1BHipW4I0GGGONIqlfT PQC9/R5OpsnU6eXBUpQUSCvysFcWwHukqlCTVWKS4Z08+yISGfc/b8GjzXTPp0MSzzvd uzFwcQogzdsdmKj95TDDbMGcC2L7gC7JV9paj+grEPqWFZIMIsXLagumYJaDCfbFTVGw XelKxw33p4kq2WWu11DFG7gFbFH3rUIheyHOyNXjUq4nKD49HIKRSFZfekOYad7Qc43S k+og==
MIME-Version: 1.0
X-Received: by 10.68.253.230 with SMTP id ad6mr10359108pbd.182.1369964434632;  Thu, 30 May 2013 18:40:34 -0700 (PDT)
Received: by 10.70.25.195 with HTTP; Thu, 30 May 2013 18:40:34 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:2471:ba1a:be48:1771]
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com>
Date: Fri, 31 May 2013 11:40:34 +1000
Message-ID: <CAKr6gn17UZCUVNwbJuOtkthnEF5Ri+s+aPd18ShhbP92RDwR2A@mail.gmail.com>
Subject: Re: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: George Michaelson <ggm@algebras.org>
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary=047d7b2e0bff7b43ae04ddf9b325
X-Gm-Message-State: ALoCoQmRpfRkZ0lpp7z3Z1PtBp11FctqEa/Ff+nuNa2+YrWYIciX+pDK4UttVNz16dhDajEmibhz
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 01:40:36 -0000

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

why on address and not per flow? you already have ASICS/FPGA which do flow
discrimination, is a packet classifier on src,dst really better, when you
cannot actually trust it?


On Fri, May 31, 2013 at 11:38 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> >> Sheng Jiang <mailto:jiangsheng@huawei.com>
> >> 30 May 2013 11:58
> >>>> IP addresses are designed as topology locator, so that every packet
> can
> >be
> >>> routed to its network destination.
> >>>> However, even in IPv4 era, some network operators have mapped their IP
> >>> address with certain semantic locally. These kind of mechanism
> explicitly
> >>> express the semantic properties of every packet. Consequently, these
> >network
> >>> operators can inspect the properties of packets easily by mapping the
> >>> addresses back to semantic.
> >>>> Network operators, who have large IPv6 address space, may also choose
> >to
> >>> embedded some semantics into IPv6 addresses by assigning additional
> >>> significance to specific bits within the prefix.
> >>> draft-jiang-v6ops-semantic-prefix documents a framework method that
> >>> network operations may use their addresses with embedded semantics.
> >These
> >>> semantics bits are only meaningful within a single network, or group of
> >>> interconnected networks which share a common addressing policy. Based
> >on
> >>> these embedded semantic bits in source/destination addresses, the
> >network
> >>> operators can accordingly treat network packets differently and
> efficiently.
> >>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
> >>>>
> >>>> Could you please review this draft and comments? It will help the
> >document
> >>> become more useful information to be shared.
> >>>> Best regards,
> >>>>
> >>>> Sheng
> >>>>
> >>> I completely understand the desire for operators to have additional
> >>> semantics available for customized packet processing. Flow label now
> has
> >>> very limited properties optimised for load balancers. DSCP only has a
> >>> few bits (way less than the number of customers' policies). ACLs are
> >>> heavy to process at each hop....
> >>>
> >>> But wouldn't this information be better off encoded as tags in one or
> >>> more hop-by-hop header options (that could be re-written on the fly),
> >>> rather than encoded in the IPv6 address space?
> >>
> >> The section 4.1 "Justifcation for Semantics with the IPv6 Prefix"
> describes
> >the reasons.
> >>
> >> Users may easily change the setting of extension header in order to
> obtain
> >undeserved priorities/privileges. Semantic prefix approach does require
> the
> >deployment of access control filters. The packets with the noncompliance
> >source addresses should be filtered. The prefix is delegated by the
> network.
> >Therefore the network is able to detect any undesired modifications and
> filter
> >the packet accordingly.
> >>
> >> Cheers,
> >>
> >> Sheng
> >>
> >>
> >I don't buy your justification. Whether an operator filters on
> >authorised address range or re-writes/filters an unauthorised hop-by-hop
> >tag is effectively the same IMHO. We have exactly the same issues of
> >potential theft of service with DSCP today, and the solution is equally
> >simple: DSCP markdown at the ingress port.
>
> Yes, the trust issue is the same with DSCP. However, the DSCP abstract all
> the semantics into service classes, which is one single dimension. This
> abstract processing has lost a lot of information, which providers want to
> inspect for every packet, then process the packet accordingly. The
> explicitly expressed semantics in prefix provides much more informations
>
> Sheng
>
> >regards,
> >RayH
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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

<div dir=3D"ltr">why on address and not per flow? you already have ASICS/FP=
GA which do flow discrimination, is a packet classifier on src,dst really b=
etter, when you cannot actually trust it?=A0</div><div class=3D"gmail_extra=
"><br>
<br><div class=3D"gmail_quote">On Fri, May 31, 2013 at 11:38 AM, Sheng Jian=
g <span dir=3D"ltr">&lt;<a href=3D"mailto:jiangsheng@huawei.com" target=3D"=
_blank">jiangsheng@huawei.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<div class=3D"HOEnZb"><div class=3D"h5">&gt;&gt; Sheng Jiang &lt;mailto:<a =
href=3D"mailto:jiangsheng@huawei.com">jiangsheng@huawei.com</a>&gt;<br>
&gt;&gt; 30 May 2013 11:58<br>
&gt;&gt;&gt;&gt; IP addresses are designed as topology locator, so that eve=
ry packet can<br>
&gt;be<br>
&gt;&gt;&gt; routed to its network destination.<br>
&gt;&gt;&gt;&gt; However, even in IPv4 era, some network operators have map=
ped their IP<br>
&gt;&gt;&gt; address with certain semantic locally. These kind of mechanism=
 explicitly<br>
&gt;&gt;&gt; express the semantic properties of every packet. Consequently,=
 these<br>
&gt;network<br>
&gt;&gt;&gt; operators can inspect the properties of packets easily by mapp=
ing the<br>
&gt;&gt;&gt; addresses back to semantic.<br>
&gt;&gt;&gt;&gt; Network operators, who have large IPv6 address space, may =
also choose<br>
&gt;to<br>
&gt;&gt;&gt; embedded some semantics into IPv6 addresses by assigning addit=
ional<br>
&gt;&gt;&gt; significance to specific bits within the prefix.<br>
&gt;&gt;&gt; draft-jiang-v6ops-semantic-prefix documents a framework method=
 that<br>
&gt;&gt;&gt; network operations may use their addresses with embedded seman=
tics.<br>
&gt;These<br>
&gt;&gt;&gt; semantics bits are only meaningful within a single network, or=
 group of<br>
&gt;&gt;&gt; interconnected networks which share a common addressing policy=
. Based<br>
&gt;on<br>
&gt;&gt;&gt; these embedded semantic bits in source/destination addresses, =
the<br>
&gt;network<br>
&gt;&gt;&gt; operators can accordingly treat network packets differently an=
d efficiently.<br>
&gt;&gt;&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-jiang-v6ops-se=
mantic-prefix-03" target=3D"_blank">http://tools.ietf.org/html/draft-jiang-=
v6ops-semantic-prefix-03</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Could you please review this draft and comments? It will h=
elp the<br>
&gt;document<br>
&gt;&gt;&gt; become more useful information to be shared.<br>
&gt;&gt;&gt;&gt; Best regards,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Sheng<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; I completely understand the desire for operators to have addit=
ional<br>
&gt;&gt;&gt; semantics available for customized packet processing. Flow lab=
el now has<br>
&gt;&gt;&gt; very limited properties optimised for load balancers. DSCP onl=
y has a<br>
&gt;&gt;&gt; few bits (way less than the number of customers&#39; policies)=
. ACLs are<br>
&gt;&gt;&gt; heavy to process at each hop....<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; But wouldn&#39;t this information be better off encoded as tag=
s in one or<br>
&gt;&gt;&gt; more hop-by-hop header options (that could be re-written on th=
e fly),<br>
&gt;&gt;&gt; rather than encoded in the IPv6 address space?<br>
&gt;&gt;<br>
&gt;&gt; The section 4.1 &quot;Justifcation for Semantics with the IPv6 Pre=
fix&quot; describes<br>
&gt;the reasons.<br>
&gt;&gt;<br>
&gt;&gt; Users may easily change the setting of extension header in order t=
o obtain<br>
&gt;undeserved priorities/privileges. Semantic prefix approach does require=
 the<br>
&gt;deployment of access control filters. The packets with the noncomplianc=
e<br>
&gt;source addresses should be filtered. The prefix is delegated by the net=
work.<br>
&gt;Therefore the network is able to detect any undesired modifications and=
 filter<br>
&gt;the packet accordingly.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt;<br>
&gt;&gt; Sheng<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;I don&#39;t buy your justification. Whether an operator filters on<br>
&gt;authorised address range or re-writes/filters an unauthorised hop-by-ho=
p<br>
&gt;tag is effectively the same IMHO. We have exactly the same issues of<br=
>
&gt;potential theft of service with DSCP today, and the solution is equally=
<br>
&gt;simple: DSCP markdown at the ingress port.<br>
<br>
</div></div>Yes, the trust issue is the same with DSCP. However, the DSCP a=
bstract all the semantics into service classes, which is one single dimensi=
on. This abstract processing has lost a lot of information, which providers=
 want to inspect for every packet, then process the packet accordingly. The=
 explicitly expressed semantics in prefix provides much more informations<b=
r>

<div class=3D"HOEnZb"><div class=3D"h5"><br>
Sheng<br>
<br>
&gt;regards,<br>
&gt;RayH<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>
</div></div></blockquote></div><br></div>

--047d7b2e0bff7b43ae04ddf9b325--

From jiangsheng@huawei.com  Thu May 30 18:45:12 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7D621F922A; Thu, 30 May 2013 18:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.474
X-Spam-Level: 
X-Spam-Status: No, score=-6.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+MgI6YoKubY; Thu, 30 May 2013 18:45:07 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id E60A521F9123; Thu, 30 May 2013 18:45:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ02380; Fri, 31 May 2013 01:45:05 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 02:44:31 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 02:45:04 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.01.0323.007; Fri, 31 May 2013 09:44:57 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAIm9sP//gNoAgACfxeD//73ZAIABXijQ
Date: Fri, 31 May 2013 01:44:57 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99A22@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk> <EMEW3|6fd619d4c2dbea7721e947e7faff5203p4Y8Bc03tjc|ecs.soton.ac.uk|C71FA5EF-1E54-48FC-84A0-A359C7009EF7@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC9940B@nkgeml512-mbx.china.huawei.com> <51A74A18.3060600@gmail.com>
In-Reply-To: <51A74A18.3060600@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 01:45:12 -0000

Pj4+PiBZZXMuIFdlIHdpbGwgZG8gc28gaW4gdGhlIGZ1dHVyZSB2ZXJzaW9uLg0KPj4+DQo+Pj5H
b29kLCBhbmQgSSB0aGluayBpdCdzIGltcG9ydGFudCB0byBkbyBzby4gR2VvcmdlIGFuZCBMb3Jl
bnpvJ3MNCj4+PiBjb21tZW50cyBhcmUNCj4+Pmdvb2Qgc3RhcnRpbmcgcG9pbnRzIGZvciB0aGF0
IHNlY3Rpb24uIFRoZSBwb3RlbnRpYWwNCj4+PiBwcml2YWN5L2luZm9ybWF0aW9uDQo+Pj5sZWFr
YWdlIGFzcGVjdCBpcyBhbHNvIHdvcnRoIGNhcHR1cmluZywgc2hvdWxkIHRob3NlIGFkZHJlc3Nl
cyBiZQ0KPj4+IHNlZW4NCj4+Pm91dHNpZGUgdGhlIG9yZ2FuaXNhdGlvbi4NCj4+DQo+PiBUaGFu
a3MsIFRpbS4gVGhlIHB1cnBvc2Ugb2YgdGhpcyBkb2N1bWVudCBpcyBub3QgcmVjb21tZW5kIG9y
IHByb3Bvc2UNCj4+IGEgZ29vZCBhcmNoaXRlY3R1cmUuIEl0IGlzIHRvIGRvY3VtZW50IHNvbWV0
aGluZyB0aGF0IGlzIGdvaW5nIHRvDQo+PiBleGlzdCBhbmQgYW5hbHl6ZSBpdC4gVGhlIHBpdGZh
bGxzIGlzIHZlcnkgaW1wb3J0YW50IGZvciBhIG5ldXRyYWwNCj4+IGFuYWx5c2lzDQo+Pg0KPj4g
Q2hlZXJzLA0KPj4NCj4+IFNoZW5nDQo+DQo+U2hlbmcsDQo+DQo+ICBZZXMgcGxlYXNlIGRvIHRo
aXMuIFRvIG1lIGl0IG5vdyBpdCByZWFkcyBtb3JlIGxpa2UgInlvdSBjYW4gZG8gdGhpcywNCj53
ZSByZWNvbW1lbmQgeW91IHRvIGRvIGl0IiB3aGVuIGl0IHNob3VsZCBzYXkgInlvdSBjYW4gZG8g
dGhpcywgaXQgaXMNCj5iYWQgZm9yIHRoaXMsIGl0IGlzIGdvb2QgZm9yIHRoaXMiIGFuZCBldmVu
IHlvdSBjb3VsZCBpbmNsdWRlIHNvbWV0aGluZw0KPmxpa2UgIndlIGRvIG5vdCByZWNvbW1lbmQg
eW91IGRvIGl0IGJ1dCBpZiB5b3Ugd2FudCB0byBzaG9vdCB5b3UgaW4gdGhlDQo+Zm9vdCB5b3Ug
YXJlIGZyZWUgdG8gZG8gc28uIg0KDQpJIHdpbGwgZG8gdGhpcyBmb3Igc3VyZS4gSXQgc2VlbXMg
dGhlIGN1cnJlbnQgZm9ybSBnaXZpbmcgcGVvcGxlIHRoZSBleHByZXNzaW9uIHRoYXQgSSBhbSAn
c2VsbGluZycgdGhpcyAnZ29vZCcgYXBwcm9hY2guIEkgYW0gbm90LiBJIGp1c3Qgd2FudCB0byBj
YWxsIHBlb3BsZSdzIGF0dGVudGlvbiAtIHRoaXMgaXMgc29tZSB3YXkgc29tZSBwcm92aWRlcnMg
d291bGQgdXNlIHRoZWlyIGFkZHJlc3Nlcy4gV2UsIGFzIElFVEYsIHNob3VsZCBkb2N1bWVudCBp
dCBhbmQgZ2l2ZSBhbmFseXNpcyBvbiBpdC4gSSB3aWxsIG1ha2UgdGhpcyBtdWNoIGNsZWFyZXIg
aW4gdGhlIGZ1dHVyZSB2ZXJzaW9uLg0KDQpCZXN0IHJlZ2FyZHMsDQoNClNoZW5nDQoNCj4vYXMN
Cg==

From jiangsheng@huawei.com  Thu May 30 18:58:59 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B495C21F96FE; Thu, 30 May 2013 18:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.484
X-Spam-Level: 
X-Spam-Status: No, score=-6.484 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yllBOloQeHw0; Thu, 30 May 2013 18:58:53 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 22E5521F96FF; Thu, 30 May 2013 18:58:50 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ03001; Fri, 31 May 2013 01:58:50 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 02:58:16 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 02:58:48 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Fri, 31 May 2013 09:58:45 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAIm9sIAACK6AgAE2CUA=
Date: Fri, 31 May 2013 01:58:45 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99A45@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <5D36713D8A4E7348A7E10DF7437A4B923AC992AE@nkgeml512-mbx.china.huawei.com> <51A76D81.9020504@joelhalpern.com>
In-Reply-To: <51A76D81.9020504@joelhalpern.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 01:58:59 -0000

PldoaWxlIGl0IGlzIHRydWUgdGhhdCBhbnkgb3BlcmF0b3IgY2FuIGRvIHdoYXRldmVyIHRoZXkg
d2FudCwgdGhpcw0KPnByb3Bvc2FsIGlzIGFyY2hpdGVjdHVyYWxseSBhIGJhZCB3YXkgdG8gYWNo
aWV2ZSB0aGUga2luZCBvZiBnb2FscyB5b3UNCj5vdXRsaW5lLg0KDQpXaWxsIGltcHJvdmUgdGhl
IGV4cHJlc3Npb24gdG8gcmVtb3ZlIHRoZSBtaXNsZWFkIHRoYXQgd2UgYXJlICdzZWxsaW5nJyBp
dC4NCg0KPlNvIEkgd291bGQgb3Bwb3NlIHB1Ymxpc2hpbmcgZXZlbiBhbiBpbmZvcm1hdGlvbmFs
IFJGQyBvbiBob3cgb25lIG1pZ2h0DQo+ZG8gdGhpcy4NCj4NCj5BcyBhbiBleGFtcGxlIG9mIHRo
ZSBwcm9ibGVtcyB3aXRoIHRoaXMsIHlvdSBzdWdnZXN0ZWQgdGhhdCBhbGxvY2F0aW9ucw0KPnRv
IGVudGVycHJpc2Ugd291bGQgbm90IGNoYW5nZSB3aXRoIHRoaXMgYXBwcm9hY2guICBUaGF0IHRo
ZSBlbnRlcnByaXNlDQo+d291bGQgcmVjZWl2ZSBhIGNlcnRhaW4gc2VtYW50aWMsIGFuZCB3b3Vs
ZCBiZSBhbGxvY2F0ZWQgYSBjZXJ0YWluIC80OA0KPnRvIG1hdGNoIHRoYXQuICBXaGlsZSB0aGlz
IHNvdW5kcyBhdHRyYWN0aXZlIGFuZCBoYXJtbGVzczoNCj4xKSBJdCBpcyBleHRyZW1lbHkgdW5s
aWtlIHRoYXQgYSBjdXN0b21lciB3aWxsIGZhbGwgaW50byBhIHNpbmdsZQ0KPiJzZW1hbnRpYyIg
d2l0aCBhbnkgdXNlZnVsIGRlZmluaXRpb24gb2Ygc2VtYW50aWMNCg0KQWdyZWUuIFR5cGljYWxs
eSwgdGhlcmUgc2hvdWxkIGJlIG1vcmUgdGhhbiBvbmUgc2VtYW50aWMgZW1iZWRkZWQuIEFjdHVh
bGx5LCBpdCBpcyB0aGUgcHJvYmxlbSBvZiBEU0NQLCB3aGljaCBhYnN0cmFjdCBhbGwgdGhlIHNl
bWFudGljcyBpbnRvIHNlcnZpY2UgY2xhc3Nlcywgd2hpY2ggaXMgb25lIHNpbmdsZSBkaW1lbnNp
b24uIFRoaXMgYWJzdHJhY3QgcHJvY2Vzc2luZyBoYXMgbG9zdCBhIGxvdCBvZiBpbmZvcm1hdGlv
biwgd2hpY2ggcHJvdmlkZXJzIHdhbnQgdG8gaW5zcGVjdCBmb3IgZXZlcnkgcGFja2V0LCB0aGVu
IHByb2Nlc3MgdGhlIHBhY2tldCBhY2NvcmRpbmdseS4gVGhlIGV4cGxpY2l0bHkgZXhwcmVzc2Vk
IHNlbWFudGljcyBpbiBwcmVmaXggcHJvdmlkZXMgbXVjaCBtb3JlIGluZm9ybWF0aW9uLg0KDQo+
MikgWW91IGhhdmUgYXJndWVkIHRoYXQgeW91IGNhbiBub3QgdXNlIERTQ1AgYmVjYXVzZSB0aGV5
IGFyZSBub3QgZmluZQ0KPmVub3VnaCBncmFpbmVkLiAgVGhpcyBtZWFucyB0aGF0IHlvdSB3YW50
IHRvIGluY3JlYXNlIHRoZSByb3V0aW5nDQo+Y29tcGxleGl0eSBieSBtb3JlIHRoYW4gYSBmYWN0
b3Igb2YgNjQsIHdoaWNoIHNlZW1zIHRvIGJlIGEgVkVSWSBiYWQNCj5pZGVhIGZvciBhbnkgb3Bl
cmF0b3IgaW5mcmFzdHJ1Y3R1cmUuDQoNCk5vdCBleGFjdGx5IG1vcmUgdGhhbiA2NC4gSXQgaXMg
bW9yZSB0aGFuIG9uZSBkaW1lbnNpb24uIFNheSwgd2UgbWF5IGhhdmUgdGhyZWUgc2VtYW50aWNz
ICgyLCAzLCA0IHR5cGVzIGZvciBlYWNoIHNlbWFudGljcykgaXQgaXMgb25seSAyNCBwb3NzaWJp
bGl0aWVzLiBGdXJ0aGVybW9yZSwgaW4gdGhpcyB3YXksIGl0IGlzIG5vdCBuZWNlc3NhcnkgdGhh
dCBvbmUgc2luZ2xlIHJvdXRlciB0byB1bmRlcnN0YW5kIGFsbCBzZW1hbnRpY3MgYW5kIGRpZmZl
cmVudGlhdGUgdGhlIHBhY2tldCBwcm9jZXNzaW5nLiBEaWZmZXJlbnQgc2VtYW50aWNzIG1heSB0
cmlnZ2VyIGRpZmZlcmVudCBvbiBkaWZmZXJlbnQgcm91dGVycy4gRm9yIGV4YW1wbGUsIGV4cHJl
c3Mgcm91dGVyIG1heSBvbmx5IGNhcmUgYWJvdXQgb25lIHNpbmdsZSBzZW1hbnRpYyAtIHdoZXRo
ZXIgdGhlIHBhY2tldCBzaG91bGQgYmUgYWxsb3dlZCB0byBsZWF2ZSB0aGUgZG9tYWluLCB3aGls
ZSBzb21lIGZpbHRlciBtYXkgY2FyZSBhYm91dCBhbm90aGVyIHNlbWFudGljcy4NCg0KQ2hlZXJz
LA0KDQpTaGVuZw0KDQo+U28gZXZlbiBmcm9tIGEgc2ltcGxlIGFuYWx5c2lzLCB0aGlzIHNlZW1z
IHNvbWV3aGVyZSBiZXR3ZWVuIHVzZWxlc3MgYW5kDQo+ZXh0cmVtZWx5IGRhbmdlcm91cy4NCj4N
Cj5Zb3VycywNCj5Kb2VsIE0uIEhhbHBlcm4NCj4NCj5PbiA1LzMwLzIwMTMgMzowMCBBTSwgU2hl
bmcgSmlhbmcgd3JvdGU6DQo+Li4uDQo+PiBIaSwgVGltLA0KPj4NCj4+IEl0IGlzIGV4YWN0bHkg
d2hhdCB0aGUgZHJhZnQgZG9jdW1lbnQuIFRoZXNlIHNlbWFudGljcyBpcyBvbmx5IG1lYW5pbmdm
dWwNCj5sb2NhbGx5IHdpdGhpbiB0aGUgYXNzaWduaW5nIHByb3ZpZGVyIG5ldHdvcmsuIEl0IG1h
eSBvbmx5IGJlIGludGVycHJldGF0aW9uDQo+YmV0d2VlbiBhZ3JlZWluZyBwcm92aWRlcnMuDQo+
Pg0KPj4gQW55IGVmZm9ydHMgdG8gYWRkIGdsb2JhbCBvciBnZW5lcmljIHNlbWFudGljcyB0byBJ
UCBhZGRyZXNzIGlzIG92ZXJsb2FkIHRoZQ0KPklQIGFyY2hpdGVjdHVyZSBhbmQgaXQgYmFkIGRp
cmVjdGlvbiwgSSBhZ3JlZS4NCj4+DQo+Pj4gSSB0aGluayBwZW9wbGUgd2lsbCBkbyB0aGlzIHR5
cGUgb2YgdGhpbmcsIHNvIGFuIEluZm9ybWF0aW9uYWwgZG9jdW1lbnQNCj4+PiBkaXNjdXNzaW5n
IHRoZSBwcm9zIGFuZCBjb25zLCBhbmQgaG93IHNlbWFudGljcyBjYW4gYmUgdXNlZCwgaXMgcHJv
YmFibHkgYQ0KPj4+IGdvb2QgdGhpbmcuICBQZXJoYXBzIGEgIlBvdGVudGlhbCBQaXRmYWxscyIg
dHlwZSBzZWN0aW9uIGFmdGVyIHRoZQ0KPiJQb3RlbnRpYWwNCj4+PiBCZW5lZml0cyIgc2VjdGlv
biB3b3VsZCBiYWxhbmNlIHRoZSBkb2N1bWVudCBhIGxpdHRsZSBiZXR0ZXI/DQo+Pg0KPj4gWWVz
LiBXZSB3aWxsIGRvIHNvIGluIHRoZSBmdXR1cmUgdmVyc2lvbi4NCj4+DQo+PiBDaGVlcnMsDQo+
Pg0KPj4gU2hlbmcNCj4uLi4NCg==

From jiangsheng@huawei.com  Thu May 30 19:23:15 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C16321F9950; Thu, 30 May 2013 19:23:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.192
X-Spam-Level: 
X-Spam-Status: No, score=-6.192 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfK9kpuLyHDB; Thu, 30 May 2013 19:23:10 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CCC7721F910D; Thu, 30 May 2013 19:23:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ04124; Fri, 31 May 2013 02:23:04 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 03:22:06 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 03:22:41 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Fri, 31 May 2013 10:22:38 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAEA7rCAABrPAIABMw5Q
Date: Fri, 31 May 2013 02:22:37 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99A9B@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <5D36713D8A4E7348A7E10DF7437A4B923AC9924F@nkgeml512-mbx.china.huawei.com> <5B817425-B386-4D9F-AD4C-DF69718411EE@delong.com>
In-Reply-To: <5B817425-B386-4D9F-AD4C-DF69718411EE@delong.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 02:23:15 -0000

Pj4gVGhlc2UgZW1iZWRkZWQgc2VtYW50aWNzIGFyZSB2ZXJ5IGRpZmZlcmVudCBmcm9tIEVuZCBT
eXN0ZW0gSWRlbnRpZmllci4NCj5UaGUgZW5kIHN5c3RlbSBpZGVudGlmaWVyIGZ1bmN0aW9ucyB3
YXMgcHJvYmxlbSBiZWNhdXNlIGl0IHZpb2xlbnRzIHRoZSBsYXllcg0KPm1vZGVsLiBNYW55IEFQ
UHMgb3IgdHJhbnNwb3J0IGxheWVyIHVzZSBJUCBhZGRyZXNzIGFzIHRoZWlyIGlkZW50aWZpZXIu
IEFuZCB0aGUNCj5lbmQgc3lzdGVtIGlkZW50aWZpZXIgYnJlYWtzIGluIGF0IGxlYXN0IHR3byBz
Y2VuYXJpb3M6IHdoZW4gZW5kIGRldmljZXMNCj5jaGFuZ2UgdGhlIGFjY2VzcyBwb2ludHMgb3Ig
d2hlbiBJUCBsYXllciB0cmFuc2xhdGlvbiAoTkFUNDQgb3IgTkFUNjQpDQo+aGFwcGVucy4NCj4N
Cj5JJ20gbm90IHN1cmUgaG93IHRoYXQncyByZWxldmFudCB0byB0aGlzIGRpc2N1c3Npb24uDQo+
DQo+SXQgZG9lcyBub3QgY2hhbmdlIHRoZSBmYWN0IHRoYXQgb3ZlcmxvYWRpbmcgc2VtYW50aWNz
IG9udG8gYWRkcmVzc2VzIGlzIGFuDQo+aW5oZXJlbnRseSBiYWQgaWRlYS4NCj4NCj4+IFRoZSBw
cm9wb3NlZCBlbWJlZGRlZCBzZW1hbnRpY3MgaXMgc3RpbGwgbGF5ZXIgMy4gVGhleSBhcmUgdXNl
ZCBmb3Igcm91dGVyJ3MNCj5wYWNrZXQgcHJvY2Vzc2luZy4gVGhlc2UgZW1iZWRkZWQgc2VtYW50
aWNzIGlzIG9ubHkgbWVhbmluZ2Z1bCBsb2NhbGx5DQo+d2l0aGluIElTUCBvd25lciBuZXR3b3Jr
LiBBZnRlciBsZWF2aW5nIHRoZSBJU1AgbmV0d29yaywgSVAgYWRkcmVzc2VzIGFyZQ0KPm9ubHkg
bG9jYXRvciwgbm90aGluZyBtb3JlLiBUaGUgYm90dG9tIGxpbmUgaXMgYSBuZXR3b3JrIG9wZXJh
dG9yIGNhbiBjaG9vc2UNCj50byBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRk
cmVzc2VzIGFzc2lnbm1lbnQuIFdlLCBhcyBJRVRGLA0KPm1heSBub3QgZW5jb3VyYWdlIHN1Y2gg
dXNhZ2UsIGJ1dCBzaG91bGQgZG9jdW1lbnQgaXQgYW5kIG1heSBnaXZlIHNvbWUNCj5ndWlkYW5j
ZSBvciBhbmFseXNpcyBvZiBpdC4NCj4NCj5UaGUgcHJvYmxlbSB3aXRoIG92ZXJsb2FkaW5nIHNl
bWFudGljcyBjYW4gb2NjdXIgcmVnYXJkbGVzcyBvZiB3aGV0aGVyIG9yDQo+bm90IHlvdSBjcm9z
cyBsYXllciBib3VuZGFyaWVzLg0KPg0KPllvdSBhcmUgY3JlYXRpbmcgYXJ0aWZpY2lhbCBwYXJ0
aXRpb25zIG9mIGFkZHJlc3Mgc3BhY2Ugd2hpY2ggY3JlYXRlcyB0aGUNCj5wb3NzaWJpbGl0eSBv
ZiBmaWxsaW5nIHVwIG9uZSBwYXJ0aXRpb24gd2hpbGUgc3BhY2UgcmVtYWlucyBpbiBhbm90aGVy
LiBUaGlzIG1heQ0KPmNyZWF0ZSBhIHNpdHVhdGlvbiB3aGVyZSB5b3UgYXJlIHVuYWJsZSB0byBn
ZXQgbW9yZSBzcGFjZSBmcm9tIHRoZSBSSVIgb3INCj51cHN0cmVhbSBkdWUgdG8gaW5lZmZpY2ll
bnQgdXRpbGl6YXRpb24gYW5kIHlvdSBhcmUgdGhlbiBmb3JjZWQgdG8gdmlvbGF0ZSB5b3VyDQo+
c2VtYW50aWMgYm91bmRhcmllcyBqdXN0IHRvIGtlZXAgdGhlIG5ldHdvcmsgcnVubmluZy4NCg0K
RnVsbHkgYWdyZWUuIFdlIHdpbGwgZG9jdW1lbnQgdGhpcyBpbnRvIGEgbmV3IHNlY3Rpb24gb2Yg
dGhpcyBkb2N1bWVudC4gIlBvdGVudGlhbCBQaXRmYWxscyINCg0KPlVuZm9ydHVuYXRlbHksIHNp
bmNlDQo+eW91J3ZlIGN1bHRpdmF0ZWQgYWxsIHRoZXNlIHNlbWFudGljIGFzc3VtcHRpb25zIGlu
IHBlb3BsZXMgaGVhZHMgKGlmIG5vdA0KPnJ1bm5pbmcgY29kZSksIG5vdyB5b3UndmUgZ290IGFk
ZGl0aW9uYWwgcHJvYmxlbXMgd2hpY2ggbGFzdCBhIHZlcnkgbG9uZyB0aW1lDQo+YW5kIGRvbid0
IG5lY2Vzc2FyaWx5IGFwcGVhciByaWdodCBhd2F5Lg0KPg0KPkl0J3MgYSByZWFsbHkgZ3JlYXQg
d2F5IHRvIGluc3RhbGwgdGltZSBib21icyBpbiB0byBvcGVyYXRpb25hbCBzeXN0ZW1zLg0KDQpJ
IGFtIG5vdCBzdXJlIHdoZXRoZXIgZ29vZCBkZXNpZ25pbmcgYXQgdGhlIGJlZ2lubmluZyBjYW4g
YXZvaWQgdGhpcyByZXN1bHQgb3Igbm90LiBJIGFtIHZlcnkgbXVjaCB3aXRoIHlvdSB0aGF0IHBy
b3ZpZGVyLCB3aG8gY2hvb3NlIHRvIHBsYXkgdGhlaXIgb3duIGFkZHJlc3MgdGhpcyB3YXksIHNo
b3VsZCBiZSBhd2FyZSBzdWNoIHJpc2suIFNvLCB3ZSBzaG91bGQgcHVibGljIHRoZXNlIGluZm9y
bWF0aW9uIGluIG9yZGVyIHRvIG1ha2UgdGhlbSBrbm93IGl0IGJlZm9yZSB0aGV5IGRlY2lkZSBq
dW1wIGludG8gaXQuDQoNCkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPiBJIGRvIG5vdA0KPnJl
Y29tbWVuZCBpdC4NCj4NCj5Pd2VuDQo+DQo+Pg0KPj4gQmVzdCByZWdhcmRzLA0KPj4NCj4+IFNo
ZW5nDQo+Pg0KPj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4gRnJvbTogT3dlbiBE
ZUxvbmcgW21haWx0bzpvd2VuQGRlbG9uZy5jb21dDQo+Pj4gU2VudDogVGh1cnNkYXksIE1heSAz
MCwgMjAxMyA3OjAyIEFNDQo+Pj4gVG86IFNoZW5nIEppYW5nDQo+Pj4gQ2M6IDx2Nm9wc0BpZXRm
Lm9yZz47IGlwdjZAaWV0Zi5vcmc7DQo+Pj4gZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJl
Zml4QHRvb2xzLmlldGYub3JnDQo+Pj4gU3ViamVjdDogUmU6IFt2Nm9wc10gQ291bGQgSVB2NiBh
ZGRyZXNzIGJlIG1vcmUgdGhhbg0KPj4+IGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1h
bnRpYy1wcmVmaXgtMDMNCj4+Pg0KPj4+IFBlcnNvbmFsbHksIEkgdGhpbmsgdGhpcyBpcyBhbiBp
bmhlcmVudGx5IGJhZCBpZGVhLg0KPj4+DQo+Pj4gSVAgYWRkcmVzc2VzIG5lZWQgbGVzcyBvdmVy
bG9hZGluZyBvZiBzZW1hbnRpY3MsIG5vdCBtb3JlLg0KPj4+DQo+Pj4gV2UgYWxyZWFkeSB1c2Ug
SVAgYWRkcmVzc2VzIGZvciB0d28gY29uZmxpY3RpbmcgcHVycG9zZXPigKYgVG9wb2xvZ3kNCj5s
b2NhdG9yDQo+Pj4gYW5kIEVuZCBTeXN0ZW0gSWRlbnRpZmllci4NCj4+Pg0KPj4+IFRoaXMgb3Zl
cmxvYWRpbmcgaXMgYXQgdGhlIGhlYXJ0IG9mIG91ciBjdXJyZW50IHNjYWxpbmcgaXNzdWVzIHdp
dGggcmVzcGVjdCB0bw0KPj4+IHRoZSByb3V0aW5nIHRhYmxlLiBXaGlsZSB0aGVzZSBpc3N1ZXMg
YXJlIGN1cnJlbnRseSBsZXNzIGNyaXRpY2FsIHRoYW4gdGhleQ0KPmhhdmUNCj4+PiBiZWVuIGlu
IHRoZSBwYXN0IGFuZCB3aWxsIGxpa2VseSBnZXQgcXVpdGUgYSBiaXQgbGVzcyBjcml0aWNhbCBp
biBJUHY2LCB0aGF0IGlzIG9ubHkNCj4+PiBiZWNhdXNlIHdlIGhhdmUgZ2l2ZW4gdXAgYSBmYWly
IGFtb3VudCBvZiBmdW5jdGlvbmFsaXR5IHRvIHByZXNlcnZlDQo+Pj4gc2NhbGFiaWxpdHkgaW4g
dGhpcyByZWdhcmQuDQo+Pj4NCj4+PiBJZiB3ZSBkaWQgbm90IGhhdmUgdGhpcyBvdmVybG9hZGlu
ZywgdGhlbiBhbiBlbnRpdHkgY291bGQgb2J0YWluIGEgc2V0IG9mDQo+Pj4gZW5kLXN5c3RlbSBp
ZGVudGlmaWVycyBhbmQga2VlcCB0aGVtIHRocm91Z2hvdXQgdGhlaXIgbGlmZXRpbWUsIHJlZ2Fy
ZGxlc3MNCj5vZg0KPj4+IHRvcG9sb2dpY2FsIGNoYW5nZXMuIFRvZGF5LCB3aGVyZSB0aGUgYWRk
cmVzc2VzIGFyZSBvdmVybG9hZGVkIHdpdGggYm90aA0KPj4+IHNlbWFudGljcywgd2UgZWl0aGVy
IGhhdmUgdG8gZm9yY2UgbW9zdCBlbnRpdGllcyB0byBjaGFuZ2UgdGhlaXIgbnVtYmVycw0KPj4+
IHdoZW4gdGhleSBjaGFuZ2UgdG9wb2xvZ3kgb3Igd2UgZmFjZSB1bnN1c3RhaW5hYmxlIGdyb3d0
aCBpbiB0aGUNCj5yb3V0aW5nDQo+Pj4gdGFibGVzLg0KPj4+DQo+Pj4gVGhlIGlkZWEgb2YgYWRk
aW5nIG1vcmUgc2VtYW50aWNzIHRvIGFkZHJlc3NpbmcgcmF0aGVyIHRoYW4gc2Vla2luZyB0bw0K
Pj4+IHJlZHVjZSB0aGlzIG92ZXJsb2FkaW5nIHNlZW1zIGEgc3RlcCBpbiB0aGUgd3JvbmcgZGly
ZWN0aW9uLCBJTUhPLg0KPj4+DQo+Pj4gT3dlbg0KPj4+DQo+Pj4gT24gTWF5IDI5LCAyMDEzLCBh
dCAxMjowNiBBTSwgU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdAaHVhd2VpLmNvbT4NCj4+PiB3cm90
ZToNCj4+Pg0KPj4+PiBJUCBhZGRyZXNzZXMgYXJlIGRlc2lnbmVkIGFzIHRvcG9sb2d5IGxvY2F0
b3IsIHNvIHRoYXQgZXZlcnkgcGFja2V0IGNhbg0KPmJlDQo+Pj4gcm91dGVkIHRvIGl0cyBuZXR3
b3JrIGRlc3RpbmF0aW9uLg0KPj4+Pg0KPj4+PiBIb3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBz
b21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyIElQDQo+Pj4gYWRkcmVzcyB3
aXRoIGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5pc20gZXhw
bGljaXRseQ0KPj4+IGV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRpZXMgb2YgZXZlcnkgcGFj
a2V0LiBDb25zZXF1ZW50bHksIHRoZXNlDQo+bmV0d29yaw0KPj4+IG9wZXJhdG9ycyBjYW4gaW5z
cGVjdCB0aGUgcHJvcGVydGllcyBvZiBwYWNrZXRzIGVhc2lseSBieSBtYXBwaW5nIHRoZQ0KPj4+
IGFkZHJlc3NlcyBiYWNrIHRvIHNlbWFudGljLg0KPj4+Pg0KPj4+PiBOZXR3b3JrIG9wZXJhdG9y
cywgd2hvIGhhdmUgbGFyZ2UgSVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbyBjaG9vc2UNCj50
bw0KPj4+IGVtYmVkZGVkIHNvbWUgc2VtYW50aWNzIGludG8gSVB2NiBhZGRyZXNzZXMgYnkgYXNz
aWduaW5nIGFkZGl0aW9uYWwNCj4+PiBzaWduaWZpY2FuY2UgdG8gc3BlY2lmaWMgYml0cyB3aXRo
aW4gdGhlIHByZWZpeC4NCj4+PiBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXggZG9j
dW1lbnRzIGEgZnJhbWV3b3JrIG1ldGhvZCB0aGF0DQo+Pj4gbmV0d29yayBvcGVyYXRpb25zIG1h
eSB1c2UgdGhlaXIgYWRkcmVzc2VzIHdpdGggZW1iZWRkZWQgc2VtYW50aWNzLg0KPlRoZXNlDQo+
Pj4gc2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBzaW5nbGUgbmV0
d29yaywgb3IgZ3JvdXAgb2YNCj4+PiBpbnRlcmNvbm5lY3RlZCBuZXR3b3JrcyB3aGljaCBzaGFy
ZSBhIGNvbW1vbiBhZGRyZXNzaW5nIHBvbGljeS4gQmFzZWQNCj5vbg0KPj4+IHRoZXNlIGVtYmVk
ZGVkIHNlbWFudGljIGJpdHMgaW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlDQo+
bmV0d29yaw0KPj4+IG9wZXJhdG9ycyBjYW4gYWNjb3JkaW5nbHkgdHJlYXQgbmV0d29yayBwYWNr
ZXRzIGRpZmZlcmVudGx5IGFuZCBlZmZpY2llbnRseS4NCj4+Pj4NCj4+Pj4gaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+
DQo+Pj4+IENvdWxkIHlvdSBwbGVhc2UgcmV2aWV3IHRoaXMgZHJhZnQgYW5kIGNvbW1lbnRzPyBJ
dCB3aWxsIGhlbHAgdGhlDQo+ZG9jdW1lbnQNCj4+PiBiZWNvbWUgbW9yZSB1c2VmdWwgaW5mb3Jt
YXRpb24gdG8gYmUgc2hhcmVkLg0KPj4+Pg0KPj4+PiBCZXN0IHJlZ2FyZHMsDQo+Pj4+DQo+Pj4+
IFNoZW5nDQo+Pj4+DQo+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+Pj4gRnJv
bTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnXQ0KPj4+Pj4gU2VudDogVHVlc2RheSwgTWF5IDI4LCAyMDEzIDEwOjI4IEFNDQo+Pj4+PiBU
bzogUWlvbmcgU3VuOyBJYW4gRmFycmVyOyBTaGVuZyBKaWFuZzsgQm95YW5nDQo+Pj4+PiBTdWJq
ZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+Pj4+PiBkcmFmdC1qaWFuZy12Nm9w
cy1zZW1hbnRpYy1wcmVmaXgtMDMudHh0DQo+Pj4+Pg0KPj4+Pj4NCj4+Pj4+IEEgbmV3IHZlcnNp
b24gb2YgSS1ELCBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMudHh0DQo+Pj4+
PiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IFNoZW5nIEppYW5nIGFuZCBwb3N0
ZWQgdG8gdGhlDQo+Pj4+PiBJRVRGIHJlcG9zaXRvcnkuDQo+Pj4+Pg0KPj4+Pj4gRmlsZW5hbWU6
ICAgICBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgNCj4+Pj4+IFJldmlzaW9uOiAg
ICAgMDMNCj4+Pj4+IFRpdGxlOiAgICAgICAgIEEgRnJhbWV3b3JrIGZvciBTZW1hbnRpYyBJUHY2
IFByZWZpeA0KPj4+Pj4gQ3JlYXRpb24gZGF0ZTogICAgIDIwMTMtMDUtMjgNCj4+Pj4+IEdyb3Vw
OiAgICAgICAgIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KPj4+Pj4gTnVtYmVyIG9mIHBhZ2VzOiAx
OQ0KPj4+Pj4gVVJMOg0KPj4+DQo+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMv
ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzLnR4dA0KPj4+Pj4gU3RhdHVzOg0K
Pj4+Pj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1qaWFuZy12Nm9wcy1z
ZW1hbnRpYy1wcmVmaXgNCj4+Pj4+IEh0bWxpemVkOg0KPj4+Pj4gaHR0cDovL3Rvb2xzLmlldGYu
b3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+PiBEaWZm
Og0KPj4+Pj4gaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtamlhbmctdjZv
cHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+Pg0KPj4+Pj4gQWJzdHJhY3Q6DQo+Pj4+PiBUaGlz
IGRvY3VtZW50IGRlc2NyaWJlcyBhIGZyYW1ld29yayBtZXRob2QgdGhhdCBuZXR3b3JrIG9wZXJh
dGlvbnMNCj4+Pj4+IG1heSB1c2UgdGhlaXIgYWRkcmVzc2VzLiAgTmV0d29yayBvcGVyYXRvcnMs
IHdobyBoYXZlIGxhcmdlIElQdjYNCj4+Pj4+IGFkZHJlc3Mgc3BhY2UsIG1heSBjaG9vc2UgdG8g
ZW1iZWRkZWQgc29tZSBzZW1hbnRpY3MgaW50byBJUHY2DQo+Pj4+PiBhZGRyZXNzZXMgYnkgYXNz
aWduaW5nIGFkZGl0aW9uYWwgc2lnbmlmaWNhbmNlIHRvIHNwZWNpZmljIGJpdHMNCj4+Pj4+IHdp
dGhpbiB0aGUgcHJlZml4LiAgQnkgZW1iZWRkZWQgc2VtYW50aWNzIGludG8gSVB2NiBwcmVmaXhl
cywgdGhlDQo+Pj4+PiBzZW1hbnRpY3Mgb2YgcGFja2V0cyBjYW4gYmUgaW5zcGVjdGVkIGVhc2ls
eS4gIFJvdXRlcnMgYW5kIG90aGVyDQo+Pj4+PiBpbnRlcm1lZGlhcnkgZGV2aWNlcyBjYW4gZWFz
aWx5IGFwcGx5IHJlbGV2YW50IHBvbGljaWVzIGFzIHJlcXVpcmVkLg0KPj4+Pj4gUGFja2V0LWxl
dmVsIGRpZmZlcmVudGlhdGlvbiBjYW4gYWxzbyBlbmFibGUgZmxvdy1sZXZlbCBhbmQgdXNlci0N
Cj4+Pj4+IGxldmVsIGRpZmZlcmVudGlhdGlvbi4gIENvbnNlcXVlbnRseSwgdGhlIG5ldHdvcmsg
b3BlcmF0b3JzIGNhbg0KPj4+Pj4gYWNjb3JkaW5nbHkgdHJlYXQgbmV0d29yayBwYWNrZXRzIGRp
ZmZlcmVudGx5IGFuZCBlZmZpY2llbnRseS4gIFRoZQ0KPj4+Pj4gbWFuYWdlbWVudCBhbmQgbWFp
bnRlbmFuY2Ugb2YgbmV0d29ya3MgY2FuIGJlIG11Y2ggc2ltcGxlci4NCj4+Pj4+DQo+Pj4+Pg0K
Pj4+Pj4NCj4+Pj4+DQo+Pj4+PiBUaGUgSUVURiBTZWNyZXRhcmlhdA0KPj4+Pg0KPj4+PiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+PiB2Nm9wcyBt
YWlsaW5nIGxpc3QNCj4+Pj4gdjZvcHNAaWV0Zi5vcmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KPj4NCg==

From jiangsheng@huawei.com  Thu May 30 19:54:54 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC4E821F9339; Thu, 30 May 2013 19:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.179
X-Spam-Level: 
X-Spam-Status: No, score=-6.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGZWFV53I0ud; Thu, 30 May 2013 19:54:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B8B4421F8CB4; Thu, 30 May 2013 19:54:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ05831; Fri, 31 May 2013 02:54:46 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 03:53:48 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 03:54:20 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Fri, 31 May 2013 10:54:16 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Duncan, Richard (Jeremy)" <jeremy.duncan@salientfed.com>, Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXNw0JNfUIpIfbEiqc0a18kokB5kdRjJggABSEwCAAP8ssA==
Date: Fri, 31 May 2013 02:54:15 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99AF7@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>, <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <eg56ow4ob19bwj5507xajo8n.1369880374960@email.android.com>, <5D36713D8A4E7348A7E10DF7437A4B923AC9927B@nkgeml512-mbx.china.huawei.com> <923297B868FB664FBFA90FCC255696DF591E69CC@BY2PRD0510MB366.namprd05.prod.outlook.com>
In-Reply-To: <923297B868FB664FBFA90FCC255696DF591E69CC@BY2PRD0510MB366.namprd05.prod.outlook.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 02:54:54 -0000

Pk5vdCBmb2xsb3dpbmcuLiAgSWYgdGhlIHByb3ZpZGVyIHB1dHMgc2VtYW50aWNzIG9uIGJpdHMg
MzAtMzIsIGFuZCBJIGhhZCBhDQo+bmVlZCBmb3Igc2VydmljZXMgY292ZXJlZCBieSBvdGhlciBi
aXRzIEkgd291bGQgdGhlbiBuZWVkIHRvIGhhdmUgYQ0KPm11bHRpLWRpc3BhcmF0ZSBhbGxvY2F0
aW9uIG9mIHNheSAoMykgLzQ4cyAtIG9yICgzKSAvNTJzLCB3aGF0ZXZlci4gIFRoZW4gdGhlDQo+
cHJvdmlkZXIgd2lsbCBoYXZlIGEgbG90IG9mIHVudXNlZCBzcGFjZSBpbnNpZGUgdGhlaXIgLzMw
IGZvciBzZXJ2aWNlcy4NCg0KWWVzLCBEdW5jYW4uIEkgd2lsbCBub3QgZGVueSB0aGVyZSB3aWxs
IGJlIG1vcmUgYWRkcmVzcyB3YXN0ZWQuIEhvd2V2ZXIsIEkgZG9uJ3QgdGhpbmsgeW91ciBjb25j
ZXJuIHNjZW5hcmlvIHdpbGwgaGFwcGVuLiBUaGUgcHJvdmlkZXIncyBhbGxvY2F0aW9uIHBsYW4g
Zm9yIGVudGVycHJpc2Ugc2hvdWxkIGJlIHN0YWJsZS4gVGhlIHRyYWZmaWMgZnJvbSBvbmUgc2lu
Z2xlIGVudGVycHJpc2Ugc2hvdWxkIGJlIHRyZWF0ZWQgYXMgZXF1YWwgb24gcHJvdmlkZXIncyBz
aWRlLiBUaGUgYWJvdmUgbWVudGlvbmVkIHNjZW5hcmlvIHNob3VsZCBvbmx5IGhhcHBlbiBpZiB0
aGUgZW50ZXJwcmlzZSBpdHNlbGYgd2FudHMgdGhlIHByb3ZpZGVyIHRyZWF0IHRoZWlyIHRyYWZm
aWMgZGlmZmVyZW50bHkuIEZvciBleGFtcGxlLCBwYXJ0IG9mIHByb3ZpZGVycyB0cmFmZmljIG1h
eSB3YW50IHRvIGJlIGhpZ2hseSBzZWN1cmVkLCB0aGV5IHNob3VsZCB1c2Ugb24gLzQ4LCB0aGUg
b3RoZXIgdHJhZmZpY3MgaXMgbm9ybWFsLCB0aGV5IHVzZSBhbm90aGVyIC80OC4NCg0KU2hlbmcN
Cg0KPkkganVzdCBkb24ndCB1bmRlcnN0YW5kaW5nIHdoeSB1c2luZyBIYkggb3B0aW9ucywgVEMg
Zm9yIERpZmZTZXJ2IG9yIHRoZSBGTA0KPmRvZXNuJ3QgYWxyZWFkeSBhbnN3ZXIgdGhlIG1haWw/
ICBJZiB0aGlzIHdhcyBteSBwcm92aWRlcnMgcGxhbiwgSSB3b3VsZCBzaG9wDQo+Zm9yIGFub3Ro
ZXIgcHJvdmlkZXIuDQo+DQo+MDEwMTAwMTEwMTEwMDEwMTAxMTAxMTAxMDExMTAwMDAwMTEwMDEw
MTAxMTEwMDEwMDAxMDAwMDAwMTAwMDExDQo+MDAxMTAxMDAxDQo+DQo+SmVyZW15IER1bmNhbg0K
PlNlbmlvciBEaXJlY3RvciwgSVB2NiBOZXR3b3JrIEFyY2hpdGVjdCBTYWxpZW50IEZlZGVyYWwg
U29sdXRpb25zLCBJbmMuDQo+KE5vdyBpbmNsdWRpbmcgU0dJUyAmIENvbW1hbmQgSW5mb3JtYXRp
b24gSW5jLikNCj40MDAwIExlZ2F0byBSb2FkLCBTdWl0ZSA2MDAgRmFpcmZheCwgVkEgMjIwMzMN
Cj5Hb29nbGUgVm9pY2U6ICA1NDAuNDQwLjExOTMNCj5qZXJlbXkuZHVuY2FuQHNhbGllbnRmZWQu
Y29tDQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPkZyb206
IFNoZW5nIEppYW5nIFtqaWFuZ3NoZW5nQGh1YXdlaS5jb21dDQo+U2VudDogVGh1cnNkYXksIE1h
eSAzMCwgMjAxMyAyOjQ1IEFNDQo+VG86IER1bmNhbiwgUmljaGFyZCAoSmVyZW15KTsgT3dlbiBE
ZUxvbmcNCj5DYzogPHY2b3BzQGlldGYub3JnPjsgZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMt
cHJlZml4QHRvb2xzLmlldGYub3JnOw0KPmlwdjZAaWV0Zi5vcmcNCj5TdWJqZWN0OiBSRTogW3Y2
b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuDQo+bG9jYXRvcj8vL2RyYWZ0LWpp
YW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0KPg0KPkhpLCBEdW5jYW4sDQo+DQo+QWN0dWFs
bHksIHlvdSBxdWVzdGlvbiBpcyB2ZXJ5IGRldGFpbGVkIHNjZW5hcmlvIGluIHRoZSBhcHByb2Fj
aC4gVGhlIGFuc3dlciBpcw0KPnRoZSBwcm92aWRlciBzdGlsbCBhc3NpZ24gYSAvNDggdG8gYW4g
b3JnYW5pemF0aW9uLiBCdXQgd2l0aGluIHRoZSBhc3NpZ25lZCAvNDgsDQo+c29tZSBiaXQgKGZv
ciBleGFtcGxlLCBiaXQgbm8uIDMwfjMyKSBoYXMgc29tZSBzZW1hbnRpYyAoZm9yIGV4YW1wbGUs
IG5lZWQNCj5leHRyYSBzZWN1cml0eSBwcm9jZXNzaW5nKSBmb3IgdGhlIGFzc2lnbmluZyBwcm92
aWRlci4gVGhlbiwgd2hlbiB0aGUgcHJvdmlkZXINCj5yZWNlaXZlZCBwYWNrZXRzIGZyb20gc3Vj
aCBvcmdhbml6YXRpb25zICh0aGVyZSBhcmUgbXVsdGlwbGUgZW50ZXJwcmlzZSBoYXMNCj50aGUg
c2FtZSBzZW1hbnRpYyBhbmQgdGhlIHNhbWUgYml0IG5vLiAzMH4zMiksIGl0IGNhbiB0cmVhdCBh
Y2NvcmRpbmdseS4NCj4NCj5CZXN0IHJlZ2FyZHMsDQo+DQo+U2hlbmcNCj4NCj4+LS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCj4+RnJvbTogRHVuY2FuLCBSaWNoYXJkIChKZXJlbXkpIFttYWls
dG86amVyZW15LmR1bmNhbkBzYWxpZW50ZmVkLmNvbV0NCj4+U2VudDogVGh1cnNkYXksIE1heSAz
MCwgMjAxMyAxMDoyMCBBTQ0KPj5UbzogT3dlbiBEZUxvbmcNCj4+Q2M6IFNoZW5nIEppYW5nOyA8
djZvcHNAaWV0Zi5vcmc+Ow0KPj5kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9v
bHMuaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmcNCj4+U3ViamVjdDogUmU6IFt2Nm9wc10gQ291bGQg
SVB2NiBhZGRyZXNzIGJlIG1vcmUgdGhhbg0KPj5sb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMt
c2VtYW50aWMtcHJlZml4LTAzDQo+Pg0KPj5JIHRlbmQgdG8gYWdyZWUgd2l0aCBPd2VuIGhlcmUu
ICBJbiBmYWN0LCBJIGFtIGN1cmlvdXMgaG93IGFuIGFsbG9jYXRpb24NCj4+ZnJvbSBhIHByb3Zp
ZGVyIHRvIGEgb3JnYW5pemF0aW9uIHdvdWxkIGxvb2s/ICBJbnN0ZWFkIG9mIGZvbGxvd2luZw0K
PnN0YW5kYXJkDQo+Pmlzc3VpbmcgcHJhY3RpY2VzIG9mIGEgLzQ4LCBhcmUgeW91IHN1Z2dlc3Rp
bmcgdGhlIHByb3ZpZGVyIHdvdWxkIGlzc3VlDQo+Pm11bHRpcGxlIC81MnMgdGhhdCBmb2xsb3cg
ZnVuY3Rpb25hbCBjYXRlZ29yaWVzIChWb0lQLCBtYW5hZ2VtZW50LCBldGMpPw0KPk9yDQo+Pm1h
eWJlIEkgbWlzc2VkIHNvbWV0aGluZz8NCj4+DQo+Pg0KPj4wMTAxMDAxMTAxMTAwMTAxMDExMDEx
MDEwMTExMDAwMDAxMTAwMTAxMDExMTAwMTAwMDEwMDAwMDAxMDAwMQ0KPjENCj4+MDAxMTAxMDAx
DQo+Pg0KPj5KZXJlbXkgRHVuY2FuDQo+PlNlbmlvciBEaXJlY3RvciwgSVB2NiBOZXR3b3JrIEFy
Y2hpdGVjdA0KPj5TYWxpZW50IEZlZGVyYWwgU29sdXRpb25zLCBJbmMuIChOb3cgaW5jbHVkaW5n
IFNHSVMgJiBDb21tYW5kIEluZm9ybWF0aW9uDQo+PkluYy4pDQo+PjQwMDAgTGVnYXRvIFJvYWQs
IFN1aXRlIDYwMA0KPj5GYWlyZmF4LCBWQSAyMjAzMw0KPj5Hb29nbGUgVm9pY2U6IDU0MC40NDAu
MTE5Mw0KPj5qZXJlbXkuZHVuY2FuQHNhbGllbnRmZWQuY29tDQo+Pg0KPj5Pd2VuIERlTG9uZyA8
b3dlbkBkZWxvbmcuY29tPiB3cm90ZToNCj4+DQo+Pg0KPj5QZXJzb25hbGx5LCBJIHRoaW5rIHRo
aXMgaXMgYW4gaW5oZXJlbnRseSBiYWQgaWRlYS4NCj4+DQo+PklQIGFkZHJlc3NlcyBuZWVkIGxl
c3Mgb3ZlcmxvYWRpbmcgb2Ygc2VtYW50aWNzLCBub3QgbW9yZS4NCj4+DQo+PldlIGFscmVhZHkg
dXNlIElQIGFkZHJlc3NlcyBmb3IgdHdvIGNvbmZsaWN0aW5nIHB1cnBvc2Vz4oCmIFRvcG9sb2d5
IGxvY2F0b3INCj4+YW5kIEVuZCBTeXN0ZW0gSWRlbnRpZmllci4NCj4+DQo+PlRoaXMgb3Zlcmxv
YWRpbmcgaXMgYXQgdGhlIGhlYXJ0IG9mIG91ciBjdXJyZW50IHNjYWxpbmcgaXNzdWVzIHdpdGgg
cmVzcGVjdCB0bw0KPj50aGUgcm91dGluZyB0YWJsZS4gV2hpbGUgdGhlc2UgaXNzdWVzIGFyZSBj
dXJyZW50bHkgbGVzcyBjcml0aWNhbCB0aGFuIHRoZXkgaGF2ZQ0KPj5iZWVuIGluIHRoZSBwYXN0
IGFuZCB3aWxsIGxpa2VseSBnZXQgcXVpdGUgYSBiaXQgbGVzcyBjcml0aWNhbCBpbiBJUHY2LCB0
aGF0IGlzIG9ubHkNCj4+YmVjYXVzZSB3ZSBoYXZlIGdpdmVuIHVwIGEgZmFpciBhbW91bnQgb2Yg
ZnVuY3Rpb25hbGl0eSB0byBwcmVzZXJ2ZQ0KPj5zY2FsYWJpbGl0eSBpbiB0aGlzIHJlZ2FyZC4N
Cj4+DQo+PklmIHdlIGRpZCBub3QgaGF2ZSB0aGlzIG92ZXJsb2FkaW5nLCB0aGVuIGFuIGVudGl0
eSBjb3VsZCBvYnRhaW4gYSBzZXQgb2YNCj4+ZW5kLXN5c3RlbSBpZGVudGlmaWVycyBhbmQga2Vl
cCB0aGVtIHRocm91Z2hvdXQgdGhlaXIgbGlmZXRpbWUsIHJlZ2FyZGxlc3MNCj5vZg0KPj50b3Bv
bG9naWNhbCBjaGFuZ2VzLiBUb2RheSwgd2hlcmUgdGhlIGFkZHJlc3NlcyBhcmUgb3ZlcmxvYWRl
ZCB3aXRoIGJvdGgNCj4+c2VtYW50aWNzLCB3ZSBlaXRoZXIgaGF2ZSB0byBmb3JjZSBtb3N0IGVu
dGl0aWVzIHRvIGNoYW5nZSB0aGVpciBudW1iZXJzDQo+PndoZW4gdGhleSBjaGFuZ2UgdG9wb2xv
Z3kgb3Igd2UgZmFjZSB1bnN1c3RhaW5hYmxlIGdyb3d0aCBpbiB0aGUgcm91dGluZw0KPj50YWJs
ZXMuDQo+Pg0KPj5UaGUgaWRlYSBvZiBhZGRpbmcgbW9yZSBzZW1hbnRpY3MgdG8gYWRkcmVzc2lu
ZyByYXRoZXIgdGhhbiBzZWVraW5nIHRvDQo+PnJlZHVjZSB0aGlzIG92ZXJsb2FkaW5nIHNlZW1z
IGEgc3RlcCBpbiB0aGUgd3JvbmcgZGlyZWN0aW9uLCBJTUhPLg0KPj4NCj4+T3dlbg0KPj4NCj4+
T24gTWF5IDI5LCAyMDEzLCBhdCAxMjowNiBBTSwgU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdAaHVh
d2VpLmNvbT4NCj4+d3JvdGU6DQo+Pg0KPj4+IElQIGFkZHJlc3NlcyBhcmUgZGVzaWduZWQgYXMg
dG9wb2xvZ3kgbG9jYXRvciwgc28gdGhhdCBldmVyeSBwYWNrZXQgY2FuIGJlDQo+PnJvdXRlZCB0
byBpdHMgbmV0d29yayBkZXN0aW5hdGlvbi4NCj4+Pg0KPj4+IEhvd2V2ZXIsIGV2ZW4gaW4gSVB2
NCBlcmEsIHNvbWUgbmV0d29yayBvcGVyYXRvcnMgaGF2ZSBtYXBwZWQgdGhlaXIgSVANCj4+YWRk
cmVzcyB3aXRoIGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5p
c20gZXhwbGljaXRseQ0KPj5leHByZXNzIHRoZSBzZW1hbnRpYyBwcm9wZXJ0aWVzIG9mIGV2ZXJ5
IHBhY2tldC4gQ29uc2VxdWVudGx5LCB0aGVzZQ0KPm5ldHdvcmsNCj4+b3BlcmF0b3JzIGNhbiBp
bnNwZWN0IHRoZSBwcm9wZXJ0aWVzIG9mIHBhY2tldHMgZWFzaWx5IGJ5IG1hcHBpbmcgdGhlDQo+
PmFkZHJlc3NlcyBiYWNrIHRvIHNlbWFudGljLg0KPj4+DQo+Pj4gTmV0d29yayBvcGVyYXRvcnMs
IHdobyBoYXZlIGxhcmdlIElQdjYgYWRkcmVzcyBzcGFjZSwgbWF5IGFsc28gY2hvb3NlDQo+dG8N
Cj4+ZW1iZWRkZWQgc29tZSBzZW1hbnRpY3MgaW50byBJUHY2IGFkZHJlc3NlcyBieSBhc3NpZ25p
bmcgYWRkaXRpb25hbA0KPj5zaWduaWZpY2FuY2UgdG8gc3BlY2lmaWMgYml0cyB3aXRoaW4gdGhl
IHByZWZpeC4NCj4+ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4IGRvY3VtZW50cyBh
IGZyYW1ld29yayBtZXRob2QgdGhhdA0KPj5uZXR3b3JrIG9wZXJhdGlvbnMgbWF5IHVzZSB0aGVp
ciBhZGRyZXNzZXMgd2l0aCBlbWJlZGRlZCBzZW1hbnRpY3MuDQo+VGhlc2UNCj4+c2VtYW50aWNz
IGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBzaW5nbGUgbmV0d29yaywgb3IgZ3Jv
dXAgb2YNCj4+aW50ZXJjb25uZWN0ZWQgbmV0d29ya3Mgd2hpY2ggc2hhcmUgYSBjb21tb24gYWRk
cmVzc2luZyBwb2xpY3kuIEJhc2VkIG9uDQo+PnRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMg
aW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlIG5ldHdvcmsNCj4+b3BlcmF0b3Jz
IGNhbiBhY2NvcmRpbmdseSB0cmVhdCBuZXR3b3JrIHBhY2tldHMgZGlmZmVyZW50bHkgYW5kIGVm
ZmljaWVudGx5Lg0KPj4+DQo+Pj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlh
bmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4NCj4+PiBDb3VsZCB5b3UgcGxlYXNlIHJl
dmlldyB0aGlzIGRyYWZ0IGFuZCBjb21tZW50cz8gSXQgd2lsbCBoZWxwIHRoZQ0KPmRvY3VtZW50
DQo+PmJlY29tZSBtb3JlIHVzZWZ1bCBpbmZvcm1hdGlvbiB0byBiZSBzaGFyZWQuDQo+Pj4NCj4+
PiBCZXN0IHJlZ2FyZHMsDQo+Pj4NCj4+PiBTaGVuZw0KPj4+DQo+Pj4+IC0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQo+Pj4+IEZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRv
OmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4+Pj4gU2VudDogVHVlc2RheSwgTWF5IDI4LCAy
MDEzIDEwOjI4IEFNDQo+Pj4+IFRvOiBRaW9uZyBTdW47IElhbiBGYXJyZXI7IFNoZW5nIEppYW5n
OyBCb3lhbmcNCj4+Pj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPj4+
PiBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMudHh0DQo+Pj4+DQo+Pj4+DQo+
Pj4+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVm
aXgtMDMudHh0DQo+Pj4+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgU2hlbmcg
SmlhbmcgYW5kIHBvc3RlZCB0byB0aGUNCj4+Pj4gSUVURiByZXBvc2l0b3J5Lg0KPj4+Pg0KPj4+
PiBGaWxlbmFtZTogICAgIGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeA0KPj4+PiBS
ZXZpc2lvbjogICAgIDAzDQo+Pj4+IFRpdGxlOiAgICAgICAgICAgICAgICBBIEZyYW1ld29yayBm
b3IgU2VtYW50aWMgSVB2NiBQcmVmaXgNCj4+Pj4gQ3JlYXRpb24gZGF0ZTogICAgICAgIDIwMTMt
MDUtMjgNCj4+Pj4gR3JvdXA6ICAgICAgICAgICAgICAgIEluZGl2aWR1YWwgU3VibWlzc2lvbg0K
Pj4+PiBOdW1iZXIgb2YgcGFnZXM6IDE5DQo+Pj4+IFVSTDoNCj4+Pj4NCj4+aHR0cDovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4
LTAzLnR4DQo+dA0KPj4+PiBTdGF0dXM6DQo+Pj4+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4DQo+Pj4+IEh0bWxpemVkOg0K
Pj4+PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRp
Yy1wcmVmaXgtMDMNCj4+Pj4gRGlmZjoNCj4+Pj4gaHR0cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZm
P3VybDI9ZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+DQo+Pj4+IEFi
c3RyYWN0Og0KPj4+PiAgVGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYSBmcmFtZXdvcmsgbWV0aG9k
IHRoYXQgbmV0d29yayBvcGVyYXRpb25zDQo+Pj4+ICBtYXkgdXNlIHRoZWlyIGFkZHJlc3Nlcy4g
IE5ldHdvcmsgb3BlcmF0b3JzLCB3aG8gaGF2ZSBsYXJnZSBJUHY2DQo+Pj4+ICBhZGRyZXNzIHNw
YWNlLCBtYXkgY2hvb3NlIHRvIGVtYmVkZGVkIHNvbWUgc2VtYW50aWNzIGludG8gSVB2Ng0KPj4+
PiAgYWRkcmVzc2VzIGJ5IGFzc2lnbmluZyBhZGRpdGlvbmFsIHNpZ25pZmljYW5jZSB0byBzcGVj
aWZpYyBiaXRzDQo+Pj4+ICB3aXRoaW4gdGhlIHByZWZpeC4gIEJ5IGVtYmVkZGVkIHNlbWFudGlj
cyBpbnRvIElQdjYgcHJlZml4ZXMsIHRoZQ0KPj4+PiAgc2VtYW50aWNzIG9mIHBhY2tldHMgY2Fu
IGJlIGluc3BlY3RlZCBlYXNpbHkuICBSb3V0ZXJzIGFuZCBvdGhlcg0KPj4+PiAgaW50ZXJtZWRp
YXJ5IGRldmljZXMgY2FuIGVhc2lseSBhcHBseSByZWxldmFudCBwb2xpY2llcyBhcyByZXF1aXJl
ZC4NCj4+Pj4gIFBhY2tldC1sZXZlbCBkaWZmZXJlbnRpYXRpb24gY2FuIGFsc28gZW5hYmxlIGZs
b3ctbGV2ZWwgYW5kIHVzZXItDQo+Pj4+ICBsZXZlbCBkaWZmZXJlbnRpYXRpb24uICBDb25zZXF1
ZW50bHksIHRoZSBuZXR3b3JrIG9wZXJhdG9ycyBjYW4NCj4+Pj4gIGFjY29yZGluZ2x5IHRyZWF0
IG5ldHdvcmsgcGFja2V0cyBkaWZmZXJlbnRseSBhbmQgZWZmaWNpZW50bHkuICBUaGUNCj4+Pj4g
IG1hbmFnZW1lbnQgYW5kIG1haW50ZW5hbmNlIG9mIG5ldHdvcmtzIGNhbiBiZSBtdWNoIHNpbXBs
ZXIuDQo+Pj4+DQo+Pj4+DQo+Pj4+DQo+Pj4+DQo+Pj4+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+
Pj4NCj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
Pj4+IHY2b3BzIG1haWxpbmcgbGlzdA0KPj4+IHY2b3BzQGlldGYub3JnDQo+Pj4gaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KPj4NCj4+LS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4+
SUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQo+PmlwdjZAaWV0Zi5vcmcNCj4+
QWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaXB2Ng0KPj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4NCj4NCg0K

From jiangsheng@huawei.com  Thu May 30 20:09:20 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405C521F96FE; Thu, 30 May 2013 20:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.467
X-Spam-Level: 
X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7YnNw84n1Wf; Thu, 30 May 2013 20:09:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 634AD21F896D; Thu, 30 May 2013 20:09:13 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ07152; Fri, 31 May 2013 03:09:12 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:08:38 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:09:11 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Fri, 31 May 2013 11:09:06 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAAQAgIAAioBg//9+QwCAAIvnkIAACAoAgAE8FgA=
Date: Fri, 31 May 2013 03:09:05 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99B0D@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com>
In-Reply-To: <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC99B0Dnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:09:20 -0000

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

SSBhbSBub3QgZGVueSB0aGVyZSB3aWxsIGJlIHdhc3RlLiBNeSBwb2ludCBpcyBvbmx5IGl0IGlz
IG5vdCBhcyBtdWNoIHdhc3RlIGFzIDEvMl5uLiBIb3dldmVyLCBnaXZpbmcgLzQ4IHRvIGV2ZXJ5
IHN1YnNjcmliZXIsIGZvciBtZSwgaXMgbXVjaCBiaWdnZXIgd2FzdGUgYW5kIGx1eHVyeS4gWW91
IGFyZSBhc3N1bWluZyBldmVyeSBzdWJzY3JpYmVyIGhhcyBhcyBtYW55IGFzIHRoYW4gMl4xNiBz
dWJuZXRzPyBDdXJyZW50bHksIHRoZXJlIG1heSBub3QgYmUgbW9yZSB0aGFuIDE2IGRldmljZXMg
aW4gYW4gYXZlcmFnZSBzdWJzY3JpYmVy4oCZcyBvd24gbmV0d29yay4gIE9uIG90aGVyIHNpZGUs
IHdoeSBzdWJzY3JpYmVyIG1heSB3YW50IG1vcmUgdGhhbiBvbmUgc3VibmV0cz8gT25lIHJlYXNv
bmFibGUgcmVhc29uIGlzIHRvIG9yZ2FuaXplIGRpZmZlcmVudCB0cmFmZmljcyBvciBhcHBsaWNh
dGlvbnMgaW4gZGlmZmVyZW50IHN1Ym5ldHMuIFNvLCB0aGVzZSBraW5kIG9mIHRyYWZmaWMgZGlm
ZmVyZW50aWF0aW9uIGlzIGFsc28gbWVhbmluZ2Z1bCBzZW1hbnRpYyBmb3IgcHJvdmlkZXJzLiBJ
ZiB0aGUgcHJvdmlkZXIgaGFzIGRpZmZlcmVudGlhdGUgdGhlc2UgdHJhZmZpY3MgaW4gaGlnaGVy
IGJpdHMgb2YgcHJlZml4ZXMgdXNpbmcgc2VtYW50aWMgcHJlZml4LCB0aGUgc21hbGxlciBwcmVm
aXggc3Vic2NyaWJlciBhcmUgbmVlZGVkLiBNYXliZSAvNTgsIG9yIC82MCBpcyBlbm91Z2ggZm9y
IHN1YnNjcmliZXJzLCBpZiB0aGUgcHJvdmlkZXJzIGhhcyB3ZWxsIHNlcGFyYXRlIHRoZSB0cmFm
ZmljIGZvciB0aGVtIGJ5IGFzc2lnbiBtdWx0aXBsZSBwcmVmaXggcmVnYXJkaW5nIHRvIGRpZmZl
cmVudCBzZW1hbnRpYz8NCg0KQ2hlZXJzLA0KDQpTaGVuZw0KDQpGcm9tOiBPd2VuIERlTG9uZyBb
bWFpbHRvOm93ZW5AZGVsb25nLmNvbV0NClNlbnQ6IEZyaWRheSwgTWF5IDMxLCAyMDEzIDEyOjA4
IEFNDQpUbzogU2hlbmcgSmlhbmcNCkNjOiBMb3JlbnpvIENvbGl0dGk7IFRpbSBDaG93bjsgPHY2
b3BzQGlldGYub3JnPjsgZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4QHRvb2xzLmll
dGYub3JnOyBpcHY2QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFk
ZHJlc3MgYmUgbW9yZSB0aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1w
cmVmaXgtMDMNCg0KPj5Ib3dldmVyLCBpdCBpcyBub3QgbmVjZXNzYXJ5IGFzIHdvcnNlIGFzIDJe
TiB0aW1lcy4gRm9yIGV4YW1wbGUsIGl0IHRoZXJlIGFyZSAyIGJpdHMgdG8gc2VwYXJhdGUgZGlm
ZmVyZW50IHVzZSB0eXBlcyAoc2F5IDQgZGlmZmVyZW50IHR5cGVzKSwgaXQgYWN0dWFsbHkgb25s
eSBzZXBhcmF0ZSB1c2UgYWRkcmVzcyBzcGFjZXMgaW50byBmb3VyIGRpZmZlcmVudCBzcGFjZXMu
IEl0IGRvZXMgbm90IGxpbWl0IHRoZSBhZGRyZXNzIHNwYWNlIHRvIGJlIDEvNCBvZiBvcmlnaW5h
bCBzcGFjZS4NCkhvdyBpcyB0aGF0IGRpZmZlcmVudCBmcm9tIHNheWluZyAiYnkgYWRkaW5nIHR3
byBiaXRzIG9mIHNlbWFudGljcyBpbiB0aGUgcHJlZml4LCB0aGUgbmV0d29yayB3aWxsIHVzZSA0
IHRpbWVzIHRoZSBhZGRyZXNzIHNwYWNlIHRoYW4gaXQgd291bGQgb3RoZXJ3aXNlIj8NCk5vLiBU
aGlzIGlzIHZlcnkgZGlmZmVyZW50LiBQdXR0aW5nIHRoZSBleGFtcGxlIGludG8gbnVtYmVycyBt
YXkgYmUgbW9yZSBpbnR1aXRpb25pc3RpYy4gU2F5IGFuIElTUCBoYXMgNCBtaWxsaW9uIHN1YnNj
cmliZXJzLCBpdCBuZWVkcyA0IG1pbGxpb24gLzU2IChhc3N1bWluZyBldmVyeSB1c2VyIGdldCBh
IC81NikuIEJ5IHNlcGFyYXRpbmcgdGhlbSBpbnRvIDQgZGlmZmVyZW50IHR5cGVzLCB0aGUgYWRk
cmVzcyBjb25zdW1wdGlvbiBpcyBzdGlsbCA0IG1pbGxpb24gLzU2IGlmIHRoZSBzZXBhcmF0aW9u
IGlzIGV4YWN0bHkgZXZlbi4gSG93ZXZlciwgdGhlIG1vcmUNCk5vdCBhIGdyZWF0IGFzc3VtcHRp
b24uLi4gVGhleSBzaG91bGQgbmVlZCA0IG1pbGxpb24gb3IgbW9yZSAvNDhzIHNpbmNlIGV2ZXJ5
IHN1YnNjcmliZXIgaXMgYXQgbGVhc3Qgb25lIGVuZCBzaXRlIGFuZCBldmVyeSBzdWJzY3JpYmVy
IGVuZCBzaXRlIHNob3VsZCByZWNlaXZlIGEgLzQ4Lg0KDQpBc3N1bWluZyB0aGF0IHlvdSB3aWxs
IGdldCA0IG1pbGxpb24gc3Vic2NyaWJlcnMgdGhhdCBjb252ZW5pZW50bHkgZGl2aWRlIGludG8g
YnVja2V0cyBvZiAxIG1pbGxpb24gcGVyIGJ1Y2tldCBpcyBhYnN1cmQuIE1vcmUgbGlrZWx5LCB5
b3UnbGwgZ2V0IDUwMCwwMDAsIDc1MCwwMDAsIDIsMDAwLDAwMCwgYW5kIDc1MCwwMDAsIG9yIG90
aGVyIHNpbWlsYXJseSBza2V3ZWQgZGlzdHJpYnV0aW9uLiBJdCBtaWdodCBldmVuIGJlIDMsNTAw
LDAwMCwgMTI1LDAwMCwgMTI1LDAwMCwgMjUwLDAwMC4NCmFkZHJlc3MgbWF5IG5lZWQgd2hlbiB0
aGUgc2VwYXJhdGlvbiBpcyBub3QgZXZlbi4gRm9yIGV4YW1wbGUsIGlmIHRoZSBiaWdnZXN0IHVz
ZXIgdHlwZSBoYXMgMiBtaWxsaW9uIHVzZXJzLCB0aGVuIHRoZSB0b3RhbCBhZGRyZXNzIHNwYWNl
IG1heSBiZWNvbWUgOCBtaWxsaW9uIC81NiDigJMgdHdvIHRpbWVzIG9mIG9yaWdpbmFsLiBJdCBj
b21lcyBmcm9tIGFsaWduLiBUaGUgaW5jcmVhc2VkIHNlbWFudGljcyBiaXQgYXJlIGFsc28gaW5j
cmVhc2luZyB0aGUgYWRkcmVzcyBzcGFjZSBhbHRob3VnaCBub3QgaW5jcmVhc2luZyBsaW5lYXJs
eS4gU28sIGF0IHRoZSBlbmQsIGl0IGlzIG5vdCB0b3RhbGx5IHdhc3RlLg0KSWYgeW91IGdldCBl
eHRyYW9yZGluYXJpbHkgbHVja3ksIGl0J3Mgbm8gd2FzdGUuIE90aGVyd2lzZSwgaXQncyBhdCBs
ZWFzdCA1MCUgd2FzdGUgYW5kIGNhbiBlYXNpbHkgcmVhY2ggNzUlIHdhc3RlICg0eCBzcGFjZSB1
dGlsaXphdGlvbiwgYXMgTG9yZW56byBzYWlkKS4NCg0KRm9yIGV4YW1wbGUsIGlmIHlvdSBoYXZl
IDQsMDAwLDAwMCBlbmQgc2l0ZXMgYW5kIHlvdSBnZXQgYXMgbGl0dGxlIGFzIDIsMDk3LDE1MyBz
dWJzY3JpYmVycyBpbiBvbmUgb2YgdGhlIGJ1Y2tldHMsIHlvdSBoYXZlIHRvIGdvIHRvIDR4IHlv
dXIgYWRkcmVzcyBzcGFjZSB0byBwcmVzZXJ2ZSB0aGUgc2VtYW50aWNzLg0KDQpPd2VuDQoNCkJl
c3QgcmVnYXJkcywNClNoZW5nDQpGcm9tOiBMb3JlbnpvIENvbGl0dGkgW21haWx0bzpsb3Jlbnpv
QGdvb2dsZS5jb21dDQpTZW50OiBUaHVyc2RheSwgTWF5IDMwLCAyMDEzIDM6MTkgUE0NClRvOiBT
aGVuZyBKaWFuZw0KQ2M6IFRpbSBDaG93bjsgT3dlbiBEZUxvbmc7IDx2Nm9wc0BpZXRmLm9yZzxt
YWlsdG86djZvcHNAaWV0Zi5vcmc+PjsgZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4
QHRvb2xzLmlldGYub3JnPG1haWx0bzpkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhA
dG9vbHMuaWV0Zi5vcmc+OyBpcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGlldGYub3JnPg0KU3Vi
amVjdDogUmU6IFt2Nm9wc10gQ291bGQgSVB2NiBhZGRyZXNzIGJlIG1vcmUgdGhhbiBsb2NhdG9y
Py8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQoNCk9uIFRodSwgTWF5IDMw
LCAyMDEzIGF0IDQ6MTMgUE0sIFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdlaS5jb208bWFp
bHRvOmppYW5nc2hlbmdAaHVhd2VpLmNvbT4+IHdyb3RlOg0KWWVzLCB0aGVyZSBpcyBubyBpbnRl
bnNpb24gdG8gY2hhbmdlIEFSSU7igJlzIHBvbGljeSBhdCBhbGwuIEFSSU4gc2hvdWxkIHJlbWFp
biB0aGUgY3VycmVudCBwb2xpY3kgb2YgYXNzaWduIElQdjYgYWRkcmVzcyBibG9jay4gQnV0IHRo
ZSBuZXR3b3JrIHByb3ZpZGVycywgd2hvIGhhcyBhbHJlYWR5IGdldCBhZGRyZXNzIGJsb2NrLCBj
YW4gY2hvb3NlIHRvIHVzZSB0aGUgYWRkcmVzc2VzIHdpdGggY2VydGFpbiBzZW1hbnRpY3MuIEFu
ZCBubyBvbmUsIGluY2x1ZGluZyBBUklOIGNhbiBzdG9wIHRoaXMuDQoNCkFncmVlZCwgYnV0IGV2
ZW4gZm9yIG5ldHdvcmsgcHJvdmlkZXJzIHRoYXQgYWxyZWFkeSBoYXZlIGJsb2NrcywgdGhpcyB3
aWxsIGJlIGFuIGlzc3VlIGlmIHRoZXkgZXZlciBuZWVkIGFub3RoZXIgYmxvY2suIEJ1dCBJIGRv
IHRoaW5rIHlvdSBzaG91bGQgd3JpdGUgdGhpcyBpbiB0aGUgZHJhZnQuDQoNCkhvd2V2ZXIsIGl0
IGlzIG5vdCBuZWNlc3NhcnkgYXMgd29yc2UgYXMgMl5OIHRpbWVzLiBGb3IgZXhhbXBsZSwgaXQg
dGhlcmUgYXJlIDIgYml0cyB0byBzZXBhcmF0ZSBkaWZmZXJlbnQgdXNlIHR5cGVzIChzYXkgNCBk
aWZmZXJlbnQgdHlwZXMpLCBpdCBhY3R1YWxseSBvbmx5IHNlcGFyYXRlIHVzZSBhZGRyZXNzIHNw
YWNlcyBpbnRvIGZvdXIgZGlmZmVyZW50IHNwYWNlcy4gSXQgZG9lcyBub3QgbGltaXQgdGhlIGFk
ZHJlc3Mgc3BhY2UgdG8gYmUgMS80IG9mIG9yaWdpbmFsIHNwYWNlLg0KDQpIb3cgaXMgdGhhdCBk
aWZmZXJlbnQgZnJvbSBzYXlpbmcgImJ5IGFkZGluZyB0d28gYml0cyBvZiBzZW1hbnRpY3MgaW4g
dGhlIHByZWZpeCwgdGhlIG5ldHdvcmsgd2lsbCB1c2UgNCB0aW1lcyB0aGUgYWRkcmVzcyBzcGFj
ZSB0aGFuIGl0IHdvdWxkIG90aGVyd2lzZSI/DQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OuWui+S9kzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEw
LjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFy
Z2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkkgYW0gbm90IGRlbnkgdGhlcmUgd2lsbCBiZSB3YXN0ZS4gTXkgcG9pbnQg
aXMgb25seSBpdCBpcyBub3QgYXMgbXVjaCB3YXN0ZSBhcyAxLzJebi4gSG93ZXZlciwgZ2l2aW5n
IC80OCB0byBldmVyeSBzdWJzY3JpYmVyLCBmb3IgbWUsIGlzIG11Y2gNCiBiaWdnZXIgd2FzdGUg
YW5kIGx1eHVyeS4gWW91IGFyZSBhc3N1bWluZyBldmVyeSBzdWJzY3JpYmVyIGhhcyBhcyBtYW55
IGFzIHRoYW4gMl4xNiBzdWJuZXRzPyBDdXJyZW50bHksIHRoZXJlIG1heSBub3QgYmUgbW9yZSB0
aGFuIDE2IGRldmljZXMgaW4gYW4gYXZlcmFnZSBzdWJzY3JpYmVy4oCZcyBvd24gbmV0d29yay4g
Jm5ic3A7T24gb3RoZXIgc2lkZSwgd2h5IHN1YnNjcmliZXIgbWF5IHdhbnQgbW9yZSB0aGFuIG9u
ZSBzdWJuZXRzPyBPbmUgcmVhc29uYWJsZQ0KIHJlYXNvbiBpcyB0byBvcmdhbml6ZSBkaWZmZXJl
bnQgdHJhZmZpY3Mgb3IgYXBwbGljYXRpb25zIGluIGRpZmZlcmVudCBzdWJuZXRzLiBTbywgdGhl
c2Uga2luZCBvZiB0cmFmZmljIGRpZmZlcmVudGlhdGlvbiBpcyBhbHNvIG1lYW5pbmdmdWwgc2Vt
YW50aWMgZm9yIHByb3ZpZGVycy4gSWYgdGhlIHByb3ZpZGVyIGhhcyBkaWZmZXJlbnRpYXRlIHRo
ZXNlIHRyYWZmaWNzIGluIGhpZ2hlciBiaXRzIG9mIHByZWZpeGVzIHVzaW5nIHNlbWFudGljIHBy
ZWZpeCwNCiB0aGUgc21hbGxlciBwcmVmaXggc3Vic2NyaWJlciBhcmUgbmVlZGVkLiBNYXliZSAv
NTgsIG9yIC82MCBpcyBlbm91Z2ggZm9yIHN1YnNjcmliZXJzLCBpZiB0aGUgcHJvdmlkZXJzIGhh
cyB3ZWxsIHNlcGFyYXRlIHRoZSB0cmFmZmljIGZvciB0aGVtIGJ5IGFzc2lnbiBtdWx0aXBsZSBw
cmVmaXggcmVnYXJkaW5nIHRvIGRpZmZlcmVudCBzZW1hbnRpYz8NCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5DaGVlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRp
dj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IE93ZW4gRGVMb25nIFttYWls
dG86b3dlbkBkZWxvbmcuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IEZyaWRheSwgTWF5IDMxLCAy
MDEzIDEyOjA4IEFNPGJyPg0KPGI+VG86PC9iPiBTaGVuZyBKaWFuZzxicj4NCjxiPkNjOjwvYj4g
TG9yZW56byBDb2xpdHRpOyBUaW0gQ2hvd247ICZsdDt2Nm9wc0BpZXRmLm9yZyZndDs7IGRyYWZ0
LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBpZXRmLm9y
Zzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUg
bW9yZSB0aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9j
a3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jmd0OyZndDtIb3dldmVyLCBpdCBpcyBu
b3QgbmVjZXNzYXJ5IGFzIHdvcnNlIGFzIDJeTiB0aW1lcy4gRm9yIGV4YW1wbGUsIGl0IHRoZXJl
IGFyZSAyIGJpdHMNCiB0byBzZXBhcmF0ZSBkaWZmZXJlbnQgdXNlIHR5cGVzIChzYXkgNCBkaWZm
ZXJlbnQgdHlwZXMpLCBpdCBhY3R1YWxseSBvbmx5IHNlcGFyYXRlIHVzZSBhZGRyZXNzIHNwYWNl
cyBpbnRvIGZvdXIgZGlmZmVyZW50IHNwYWNlcy4gSXQgZG9lcyBub3QgbGltaXQgdGhlIGFkZHJl
c3Mgc3BhY2UgdG8gYmUgMS80IG9mIG9yaWdpbmFsIHNwYWNlLjwvc3Bhbj48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBsYW5nPSJFTi1VUyI+SG93IGlzIHRoYXQgZGlmZmVyZW50IGZyb20gc2F5aW5nICZxdW90O2J5
IGFkZGluZyB0d28gYml0cyBvZiBzZW1hbnRpY3MgaW4gdGhlIHByZWZpeCwgdGhlIG5ldHdvcmsg
d2lsbCB1c2UgNCB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGFuIGl0IHdvdWxkIG90aGVyd2lz
ZSZxdW90Oz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Tm8u
IFRoaXMgaXMgdmVyeSBkaWZmZXJlbnQuIFB1dHRpbmcgdGhlIGV4YW1wbGUgaW50byBudW1iZXJz
IG1heSBiZSBtb3JlIGludHVpdGlvbmlzdGljLg0KIFNheSBhbiBJU1AgaGFzIDQgbWlsbGlvbiBz
dWJzY3JpYmVycywgaXQgbmVlZHMgNCBtaWxsaW9uIC81NiAoYXNzdW1pbmcgZXZlcnkgdXNlciBn
ZXQgYSAvNTYpLiBCeSBzZXBhcmF0aW5nIHRoZW0gaW50byA0IGRpZmZlcmVudCB0eXBlcywgdGhl
IGFkZHJlc3MgY29uc3VtcHRpb24gaXMgc3RpbGwgNCBtaWxsaW9uIC81NiBpZiB0aGUgc2VwYXJh
dGlvbiBpcyBleGFjdGx5IGV2ZW4uIEhvd2V2ZXIsIHRoZSBtb3JlPC9zcGFuPjxzcGFuIGxhbmc9
IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5Ob3Qg
YSBncmVhdCBhc3N1bXB0aW9uLi4uIFRoZXkgc2hvdWxkIG5lZWQgNCBtaWxsaW9uIG9yIG1vcmUg
LzQ4cyBzaW5jZSBldmVyeSBzdWJzY3JpYmVyIGlzIGF0IGxlYXN0IG9uZSBlbmQgc2l0ZSBhbmQg
ZXZlcnkgc3Vic2NyaWJlciBlbmQgc2l0ZSBzaG91bGQgcmVjZWl2ZSBhIC80OC48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkFzc3VtaW5nIHRoYXQgeW91
IHdpbGwgZ2V0IDQgbWlsbGlvbiBzdWJzY3JpYmVycyB0aGF0IGNvbnZlbmllbnRseSBkaXZpZGUg
aW50byBidWNrZXRzIG9mIDEgbWlsbGlvbiBwZXIgYnVja2V0IGlzIGFic3VyZC4gTW9yZSBsaWtl
bHksIHlvdSdsbCBnZXQgNTAwLDAwMCwgNzUwLDAwMCwgMiwwMDAsMDAwLCBhbmQgNzUwLDAwMCwg
b3Igb3RoZXIgc2ltaWxhcmx5IHNrZXdlZCBkaXN0cmlidXRpb24uDQogSXQgbWlnaHQgZXZlbiBi
ZSAzLDUwMCwwMDAsIDEyNSwwMDAsIDEyNSwwMDAsIDI1MCwwMDAuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4t
Ym90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPmFkZHJl
c3MgbWF5IG5lZWQgd2hlbiB0aGUgc2VwYXJhdGlvbiBpcyBub3QgZXZlbi4gRm9yIGV4YW1wbGUs
IGlmIHRoZSBiaWdnZXN0IHVzZXIgdHlwZQ0KIGhhcyAyIG1pbGxpb24gdXNlcnMsIHRoZW4gdGhl
IHRvdGFsIGFkZHJlc3Mgc3BhY2UgbWF5IGJlY29tZSA4IG1pbGxpb24gLzU2IOKAkyB0d28gdGlt
ZXMgb2Ygb3JpZ2luYWwuIEl0IGNvbWVzIGZyb20gYWxpZ24uIFRoZSBpbmNyZWFzZWQgc2VtYW50
aWNzIGJpdCBhcmUgYWxzbyBpbmNyZWFzaW5nIHRoZSBhZGRyZXNzIHNwYWNlIGFsdGhvdWdoIG5v
dCBpbmNyZWFzaW5nIGxpbmVhcmx5LiBTbywgYXQgdGhlIGVuZCwgaXQgaXMgbm90IHRvdGFsbHkg
d2FzdGUuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIj5JZiB5b3UgZ2V0IGV4dHJhb3JkaW5hcmlseSBsdWNreSwgaXQn
cyBubyB3YXN0ZS4gT3RoZXJ3aXNlLCBpdCdzIGF0IGxlYXN0IDUwJSB3YXN0ZSBhbmQgY2FuIGVh
c2lseSByZWFjaCA3NSUgd2FzdGUgKDR4IHNwYWNlIHV0aWxpemF0aW9uLCBhcyBMb3JlbnpvIHNh
aWQpLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+Rm9y
IGV4YW1wbGUsIGlmIHlvdSBoYXZlIDQsMDAwLDAwMCBlbmQgc2l0ZXMgYW5kIHlvdSBnZXQgYXMg
bGl0dGxlIGFzIDIsMDk3LDE1MyBzdWJzY3JpYmVycyBpbiBvbmUgb2YgdGhlIGJ1Y2tldHMsIHlv
dSBoYXZlIHRvIGdvIHRvIDR4IHlvdXIgYWRkcmVzcyBzcGFjZSB0byBwcmVzZXJ2ZSB0aGUgc2Vt
YW50aWNzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
T3dlbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QmVzdCByZWdhcmRz
LDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPlNoZW5nPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBi
bHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0
IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gTG9yZW56bw0KIENvbGl0dGkgWzxhIGhyZWY9Im1h
aWx0bzpsb3JlbnpvQGdvb2dsZS5jb20iPm1haWx0bzpsb3JlbnpvQGdvb2dsZS5jb208L2E+XSA8
YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIE1heSAzMCwgMjAxMyAzOjE5IFBNPGJyPg0KPGI+
VG86PC9iPiBTaGVuZyBKaWFuZzxicj4NCjxiPkNjOjwvYj4gVGltIENob3duOyBPd2VuIERlTG9u
ZzsgJmx0OzxhIGhyZWY9Im1haWx0bzp2Nm9wc0BpZXRmLm9yZyI+djZvcHNAaWV0Zi5vcmc8L2E+
Jmd0OzsNCjxhIGhyZWY9Im1haWx0bzpkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhA
dG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5p
ZXRmLm9yZzwvYT47DQo8YSBocmVmPSJtYWlsdG86aXB2NkBpZXRmLm9yZyI+aXB2NkBpZXRmLm9y
ZzwvYT48YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFt2Nm9wc10gQ291bGQgSVB2NiBhZGRyZXNz
IGJlIG1vcmUgdGhhbiBsb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4
LTAzPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5i
c3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gbGFuZz0iRU4tVVMiPk9uIFRodSwgTWF5IDMwLCAyMDEzIGF0IDQ6MTMgUE0sIFNoZW5n
IEppYW5nICZsdDs8YSBocmVmPSJtYWlsdG86amlhbmdzaGVuZ0BodWF3ZWkuY29tIiB0YXJnZXQ9
Il9ibGFuayI+amlhbmdzaGVuZ0BodWF3ZWkuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlll
cywgdGhlcmUgaXMgbm8gaW50ZW5zaW9uIHRvIGNoYW5nZSBBUklO4oCZcyBwb2xpY3kgYXQgYWxs
LiBBUklOIHNob3VsZCByZW1haW4gdGhlIGN1cnJlbnQNCiBwb2xpY3kgb2YgYXNzaWduIElQdjYg
YWRkcmVzcyBibG9jay4gQnV0IHRoZSBuZXR3b3JrIHByb3ZpZGVycywgd2hvIGhhcyBhbHJlYWR5
IGdldCBhZGRyZXNzIGJsb2NrLCBjYW4gY2hvb3NlIHRvIHVzZSB0aGUgYWRkcmVzc2VzIHdpdGgg
Y2VydGFpbiBzZW1hbnRpY3MuIEFuZCBubyBvbmUsIGluY2x1ZGluZyBBUklOIGNhbiBzdG9wIHRo
aXMuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPkFncmVlZCwg
YnV0IGV2ZW4gZm9yIG5ldHdvcmsgcHJvdmlkZXJzIHRoYXQgYWxyZWFkeSBoYXZlIGJsb2Nrcywg
dGhpcyB3aWxsIGJlIGFuIGlzc3VlIGlmIHRoZXkgZXZlciBuZWVkIGFub3RoZXIgYmxvY2suIEJ1
dCBJIGRvIHRoaW5rIHlvdSBzaG91bGQgd3JpdGUgdGhpcyBpbg0KIHRoZSBkcmFmdC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu
MHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRv
cDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SG93ZXZlciwgaXQgaXMgbm90IG5lY2Vzc2FyeSBh
cyB3b3JzZSBhcyAyXk4gdGltZXMuIEZvciBleGFtcGxlLCBpdCB0aGVyZSBhcmUgMiBiaXRzDQog
dG8gc2VwYXJhdGUgZGlmZmVyZW50IHVzZSB0eXBlcyAoc2F5IDQgZGlmZmVyZW50IHR5cGVzKSwg
aXQgYWN0dWFsbHkgb25seSBzZXBhcmF0ZSB1c2UgYWRkcmVzcyBzcGFjZXMgaW50byBmb3VyIGRp
ZmZlcmVudCBzcGFjZXMuIEl0IGRvZXMgbm90IGxpbWl0IHRoZSBhZGRyZXNzIHNwYWNlIHRvIGJl
IDEvNCBvZiBvcmlnaW5hbCBzcGFjZS48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyI+SG93IGlzIHRoYXQgZGlmZmVyZW50IGZyb20gc2F5aW5nICZxdW90O2J5IGFk
ZGluZyB0d28gYml0cyBvZiBzZW1hbnRpY3MgaW4gdGhlIHByZWZpeCwgdGhlIG5ldHdvcmsgd2ls
bCB1c2UgNCB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGFuIGl0IHdvdWxkIG90aGVyd2lzZSZx
dW90Oz88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC99B0Dnkgeml512mbxchi_--

From jiangsheng@huawei.com  Thu May 30 20:25:00 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40F3321F8FA3; Thu, 30 May 2013 20:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUF7s7OxNIlp; Thu, 30 May 2013 20:24:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4E07321F918F; Thu, 30 May 2013 20:24:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ08069; Fri, 31 May 2013 03:24:52 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:24:11 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 11:24:47 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Fri, 31 May 2013 11:24:35 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Owen DeLong <owen@delong.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXWv5NCdRGHUzf0iyRc5RG5uUgJkenj6Q
Date: Fri, 31 May 2013 03:24:34 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99B42@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC99B42nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:25:00 -0000

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

Q29tcGFyaW5nIGdpdmluZyAxNiBiaXRzIGZvciBzdWJzY3JpYmVycywgd2hpY2ggcmFyZWx5IHVz
ZSBpdCBvciB3ZSBzdGlsbCBoYXZlIG5vIGNvbmNyZXRlIGlkZWEgaG93IHRoaXMgd2lsbCBiZSB1
c2VkLCB0aGUgc2VtYW50aWMgYml0cyBvbiB0aGUgcHJvdmlkZXIgc2lkZSBsb29rcyBtb3JlIGhl
bHBmdWwuDQoNCk9yIHByb3ZpZGVyIG1heSBkZXNpZ25hdGUgdGhlIGJpdCBpbiB0aGUgbG93ZXIg
MTYgYml0cyBjYW4gaGF2ZSBzb21lIHNlbWFudGljcy4gRm9yIGV4YW1wbGUsIGEgcHJvdmlkZXIg
bWF5IGdpdmUgZXZlcnkgc3Vic2NyaWJlciAvNDggYW5kIGFwcG9pbnQgdGhhdCBhbGwgc3Vic2Ny
aWJlcnMgc2hvdWxkIHVzZSB0aGVpciAvNDgrMDAwMCAoNDh+NTEgYml0KSAtPiBhIC81MiBwcmVm
aXggZm9yIGEgY2VydGFpbiBhcHBsaWNhdGlvbiwgbGlrZSBWb0lQLiBUaGVuIHRoZSBwcm92aWRl
ciBjYW4gaW5zcGVjdCBhbGwgVm9JUCB0cmFmZmljIGZyb20gZGlmZmVyZW50IHN1YnNjcmliZXJz
IGJ5IG9ubHkgc2V0IGNvbmRpdGlvbiA0OH41MSBiaXQgZXF1YWwgdG8gMDAwMC4gVGhpcyB2YXJp
YXRpb24gb2Ygc2VtYW50aWMgcHJlZml4IGlzIGFsc28gaGVscGZ1bC4NCg0KQ2hlZXJzLA0KDQpT
aGVuZw0KDQpGcm9tOiBUZWQgTGVtb24gW21haWx0bzpUZWQuTGVtb25Abm9taW51bS5jb21dDQpT
ZW50OiBGcmlkYXksIE1heSAzMSwgMjAxMyAzOjI5IEFNDQpUbzogT3dlbiBEZUxvbmcNCkNjOiBT
aGVuZyBKaWFuZzsgZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4QHRvb2xzLmlldGYu
b3JnOyBpcHY2QGlldGYub3JnOyA8djZvcHNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW3Y2b3Bz
XSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12
Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDMNCg0KT24gTWF5IDMwLCAyMDEzLCBhdCAxMjowOCBQTSwg
T3dlbiBEZUxvbmcgPG93ZW5AZGVsb25nLmNvbTxtYWlsdG86b3dlbkBkZWxvbmcuY29tPj4gd3Jv
dGU6DQpOb3QgYSBncmVhdCBhc3N1bXB0aW9uLi4uIFRoZXkgc2hvdWxkIG5lZWQgNCBtaWxsaW9u
IG9yIG1vcmUgLzQ4cyBzaW5jZSBldmVyeSBzdWJzY3JpYmVyIGlzIGF0IGxlYXN0IG9uZSBlbmQg
c2l0ZSBhbmQgZXZlcnkgc3Vic2NyaWJlciBlbmQgc2l0ZSBzaG91bGQgcmVjZWl2ZSBhIC80OC4N
Cg0KSSBhbSBub3QgaW4gbG92ZSB3aXRoIHVzaW5nIGJpdHMgZnJvbSBwcmVmaXhlcyBhcyBzZW1h
bnRpYyB0YWdzLiAgIEhvd2V2ZXIsIGhhdmluZyBzYWlkIHRoYXQsIEkgdGhpbmsgaXQncyBhIGJp
dCBpcm9uaWMgdGhhdCB5b3UncmUgdGFsa2luZyBhYm91dCB3YXN0aW5nIHNwYWNlIHdpdGggc2Vt
YW50aWMgYml0cywgb24gdGhlIG9uZSBoYW5kLCBhbmQgdGFsa2luZyBhYm91dCB0aGUgbmVlZCBm
b3IgYSAvNDggaW4gZXZlcnkgaG9tZSBvbiB0aGUgb3RoZXIuICAgSXQgd291bGQgYmUgcGVyZmVj
dGx5IHJlYXNvbmFibGUgZm9yIHRoZSBJU1AgdG8gc3BlY2lmeSB0aGF0IHNvbWUgb2YgdGhlIGJp
dHMgaW4gdGhlIC80OCBoYXZlIHNlbWFudGljIG1lYW5pbmcsIGZvciBleGFtcGxlLCBhbmQgZ2l2
ZW4gdGhhdCB3ZSB0aGluayBpdCdzIG9rYXkgdG8gZ2l2ZSB0aGUgaG9tZSBuZXR3b3JrIGEgLzQ4
LCB3ZSBhcmUgaGFyZGx5IGluIGEgcG9zaXRpb24gdG8gcXVpYmJsZSBhYm91dCBob3cgdGhlIGJp
dHMgaW4gdGhhdCAvNDggYXJlIHVzZWQuDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5Ok9wdGltYTsNCglwYW5vc2UtMTowIDAgMCAwIDAgMCAwIDAgMCAwO30NCi8q
IFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNv
Tm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6
ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkw
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0i
d29yZC13cmFwOiBicmVhay13b3JkOy13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTstd2Via2l0LWxp
bmUtYnJlYWs6IGFmdGVyLXdoaXRlLXNwYWNlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkNvbXBhcmluZyBnaXZpbmcgMTYgYml0cyBmb3Igc3Vic2Ny
aWJlcnMsIHdoaWNoIHJhcmVseSB1c2UgaXQgb3Igd2Ugc3RpbGwgaGF2ZSBubyBjb25jcmV0ZSBp
ZGVhIGhvdyB0aGlzIHdpbGwgYmUgdXNlZCwgdGhlIHNlbWFudGljIGJpdHMgb24gdGhlDQogcHJv
dmlkZXIgc2lkZSBsb29rcyBtb3JlIGhlbHBmdWwuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPk9yIHByb3ZpZGVyIG1heSBkZXNpZ25hdGUgdGhlIGJpdCBpbiB0aGUgbG93ZXIg
MTYgYml0cyBjYW4gaGF2ZSBzb21lIHNlbWFudGljcy4gRm9yIGV4YW1wbGUsIGEgcHJvdmlkZXIg
bWF5IGdpdmUgZXZlcnkgc3Vic2NyaWJlciAvNDggYW5kIGFwcG9pbnQNCiB0aGF0IGFsbCBzdWJz
Y3JpYmVycyBzaG91bGQgdXNlIHRoZWlyIC80OCYjNDM7MDAwMCAoNDh+NTEgYml0KSAtJmd0OyBh
IC81MiBwcmVmaXggZm9yIGEgY2VydGFpbiBhcHBsaWNhdGlvbiwgbGlrZSBWb0lQLiBUaGVuIHRo
ZSBwcm92aWRlciBjYW4gaW5zcGVjdCBhbGwgVm9JUCB0cmFmZmljIGZyb20gZGlmZmVyZW50IHN1
YnNjcmliZXJzIGJ5IG9ubHkgc2V0IGNvbmRpdGlvbiA0OH41MSBiaXQgZXF1YWwgdG8gMDAwMC4g
VGhpcyB2YXJpYXRpb24gb2Ygc2VtYW50aWMNCiBwcmVmaXggaXMgYWxzbyBoZWxwZnVsLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5DaGVlcnMsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPlNoZW5nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20g
NC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQg
I0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8
L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IFRlZCBM
ZW1vbiBbbWFpbHRvOlRlZC5MZW1vbkBub21pbnVtLmNvbV0NCjxicj4NCjxiPlNlbnQ6PC9iPiBG
cmlkYXksIE1heSAzMSwgMjAxMyAzOjI5IEFNPGJyPg0KPGI+VG86PC9iPiBPd2VuIERlTG9uZzxi
cj4NCjxiPkNjOjwvYj4gU2hlbmcgSmlhbmc7IGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXBy
ZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBpZXRmLm9yZzsgJmx0O3Y2b3BzQGlldGYub3JnJmd0
Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW3Y2b3BzXSBDb3VsZCBJUHY2IGFkZHJlc3MgYmUg
bW9yZSB0aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIE1heSAz
MCwgMjAxMywgYXQgMTI6MDggUE0sIE93ZW4gRGVMb25nICZsdDs8YSBocmVmPSJtYWlsdG86b3dl
bkBkZWxvbmcuY29tIj5vd2VuQGRlbG9uZy5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtPcHRp
bWEmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPk5vdCBhIGdyZWF0IGFzc3VtcHRpb24uLi4gVGhl
eSBzaG91bGQgbmVlZCA0IG1pbGxpb24gb3IgbW9yZSAvNDhzIHNpbmNlIGV2ZXJ5IHN1YnNjcmli
ZXIgaXMgYXQgbGVhc3Qgb25lIGVuZCBzaXRlIGFuZCBldmVyeSBzdWJzY3JpYmVyIGVuZCBzaXRl
IHNob3VsZCByZWNlaXZlIGEgLzQ4LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9i
bG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5JIGFtIG5vdCBpbiBsb3ZlIHdpdGggdXNpbmcgYml0cyBm
cm9tIHByZWZpeGVzIGFzIHNlbWFudGljIHRhZ3MuICZuYnNwOyBIb3dldmVyLCBoYXZpbmcgc2Fp
ZCB0aGF0LCBJIHRoaW5rIGl0J3MgYSBiaXQgaXJvbmljIHRoYXQgeW91J3JlIHRhbGtpbmcgYWJv
dXQgd2FzdGluZyBzcGFjZSB3aXRoIHNlbWFudGljIGJpdHMsIG9uIHRoZSBvbmUgaGFuZCwgYW5k
IHRhbGtpbmcgYWJvdXQgdGhlDQogbmVlZCBmb3IgYSAvNDggaW4gZXZlcnkgaG9tZSBvbiB0aGUg
b3RoZXIuICZuYnNwOyBJdCB3b3VsZCBiZSBwZXJmZWN0bHkgcmVhc29uYWJsZSBmb3IgdGhlIElT
UCB0byBzcGVjaWZ5IHRoYXQgc29tZSBvZiB0aGUgYml0cyBpbiB0aGUgLzQ4IGhhdmUgc2VtYW50
aWMgbWVhbmluZywgZm9yIGV4YW1wbGUsIGFuZCBnaXZlbiB0aGF0IHdlIHRoaW5rIGl0J3Mgb2th
eSB0byBnaXZlIHRoZSBob21lIG5ldHdvcmsgYSAvNDgsIHdlIGFyZSBoYXJkbHkgaW4gYSBwb3Np
dGlvbg0KIHRvIHF1aWJibGUgYWJvdXQgaG93IHRoZSBiaXRzIGluIHRoYXQgLzQ4IGFyZSB1c2Vk
Ljwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4N
Cg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC99B42nkgeml512mbxchi_--

From jiangsheng@huawei.com  Thu May 30 20:28:26 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C64821F922A; Thu, 30 May 2013 20:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.182
X-Spam-Level: 
X-Spam-Status: No, score=-6.182 tagged_above=-999 required=5 tests=[AWL=-0.183, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v0B7kEGic5Nx; Thu, 30 May 2013 20:28:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 561F721F918F; Thu, 30 May 2013 20:28:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY70412; Fri, 31 May 2013 03:28:08 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:27:34 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:28:07 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Fri, 31 May 2013 11:28:03 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: joel jaeggli <joelja@bogus.com>, Lorenzo Colitti <lorenzo@google.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kcQnwAgAB+FQCAAAQAgIAA0WeAgAEOlHA=
Date: Fri, 31 May 2013 03:28:02 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99B56@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <51A7A5B1.3050709@bogus.com>
In-Reply-To: <51A7A5B1.3050709@bogus.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:28:26 -0000

Pj4gICAgIEkgYWdyZWUuIFRoYXQgc2FpZCwgYW4gSVNQLCBlbnRlcnByaXNlIG9yIGdyb3VwIG9m
IG9yZ2FuaXNhdGlvbnMNCj4+ICAgICBjYW4gZm9sbG93IHdoYXRldmVyIHNlbWFudGljcyB0aGV5
IHdpc2ggd2l0aGluIHRoZWlyIG93biBib3JkZXJzLg0KPj4NCj4+DQo+PiBBcyBsb25nIGFzIHRo
ZSBSSVJzIGFyZSB3aWxsaW5nIHRvIGdpdmUgdGhlbSBlbm91Z2ggYWRkcmVzcyBzcGFjZSB0bw0K
Pj4gZG8gc28uDQo+Pg0KPj4gSWYgYW4gSVNQIHJlcXVlc3RlZCBhbiBJUHY2IC8xMCBmcm9tIEFS
SU4gYmVjYXVzZSB0aGV5IHdhbnRlZCB0byBnaXZlDQo+PiBldmVyeSBjdXN0b21lciBhIC80OCBh
bmQgd2FudGVkIHRvIGdlb2NvZGUgdGhlIGN1c3RvbWVyJ3Mgc3Vic2NyaWJlcg0KPj4gSUQgaW50
byB0aGUgLzQ4LCB0aGVuIEFSSU4gd291bGQgZG8gd2VsbCB0byBzYXksICJubywgc29ycnksIHRo
YXQNCj4+IGRvZXNuJ3QgbWFrZSBzZW5zZSIuDQo+Pg0KPj4gTGVzdCBzb21lb25lIG5vdCByZWFs
aXplIHRoaXMsIHRoZSBkcmFmdCBzaG91bGQgY2xlYXJseSBzdGF0ZSB0aGF0DQo+PiBlbWJlZGRp
bmcgTiBiaXRzIG9mIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGNhdXNlcyB0aGUgbmV0
d29yaw0KPj4gdG8gdXNlIDJeTiB0aW1lcyB0aGUgYWRkcmVzcyBzcGFjZSB0aGF0IGl0IG5vcm1h
bGx5IHdvdWxkLg0KPj4NCj5wcmV0dHkgbXVjaCB3aGF0IEkgc2FpZCBhdCB0aGUgbWljLi4uIElm
IHRoaXMgZXZlciBzaG93cyB1cCBpbiBhDQo+anN1dGlmaWNhdGlvbiBmb3IgYSAvMTggb3IgLzI0
IHZzIGEgIC8yNiBhdCBhbiBSSVIgdGhhdCdzIGEgcmVhbGx5IGJhZA0KPnRoaW5nIGltaG8uDQoN
CkFncmVlLiBUaGUgbmV0d29yayBwcm92aWRlcnMgc2hvdWxkIGtub3cgdGhleSBjYW5ub3QgZ2V0
IG1vcmUgYWRkcmVzc2VzIGJlY2F1c2UgdGhleSB1c2UgdGhlaXIgYmxvY2sgZm9yIHNlbWFudGlj
LCB3aGljaCBsZWFkIHRvIGxvd2VyIGFkZHJlc3MgdXRpbGl0eSByYXRlLg0KDQpXaWxsIG1ha2Ug
dGhpcyBjbGVhciBpbiB0aGUgbmV3IHNlY3Rpb24gInBvdGVudGlhbCBwaXRmYWxscyIuDQoNCkNo
ZWVycywNCg0KU2hlbmcNCg0KPj4gSU1PIEkgdGhpbmsgaXQgc2hvdWxkIGFsc28gc3RhdGUgdGhh
dCBhbHRob3VnaCBpdCBpcyBhbiBJRVRGIFJGQywgdGhpcw0KPj4gbW9kZWwgaXMgbm90IG5lY2Vz
c2FyaWx5IGEgcmVjb21tZW5kZWQgbW9kZWwsIGFuZCB0aGF0IFJJUnMgYXJlIG5vdA0KPj4gb2Js
aWdlZCB0byBhY2NlcHQgdGhpcyB0eXBlIG9mIGFkZHJlc3MgYWxsb2NhdGlvbiBhcyBhIGp1c3Rp
ZmljYXRpb24NCj4+IGZvciBvYnRhaW5pbmcgbGFyZ2VyIGFkZHJlc3MgYmxvY2tzIHRoYW4gdGhl
eSB3b3VsZCBub3JtYWxseSBiZSBhYmxlDQo+PiB0byBvYnRhaW4uDQo+Pg0KPj4NCj4+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiB2Nm9wcyBtYWls
aW5nIGxpc3QNCj4+IHY2b3BzQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3Y2b3BzDQoNCg==

From jiangsheng@huawei.com  Thu May 30 20:41:59 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 367D521F8B07; Thu, 30 May 2013 20:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.172
X-Spam-Level: 
X-Spam-Status: No, score=-6.172 tagged_above=-999 required=5 tests=[AWL=-0.174, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CWiuM0hVw2X; Thu, 30 May 2013 20:41:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 84B3721F89C3; Thu, 30 May 2013 20:41:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY71211; Fri, 31 May 2013 03:41:36 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:40:33 +0100
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:41:08 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Fri, 31 May 2013 11:41:03 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: George Michaelson <ggm@algebras.org>
Subject: RE: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kc8GIAgACHYyD//5aGgIABdpag//98OwCAAKUh8A==
Date: Fri, 31 May 2013 03:41:02 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99BA8@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <CAKr6gn17UZCUVNwbJuOtkthnEF5Ri+s+aPd18ShhbP92RDwR2A@mail.gmail.com>
In-Reply-To: <CAKr6gn17UZCUVNwbJuOtkthnEF5Ri+s+aPd18ShhbP92RDwR2A@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC99BA8nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:41:59 -0000

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

SGksIEdlb3JnZSwNCg0KTXkgZ3Vlc3MgaXMgd2UgbWF5IHRhbGtpbmcgYWJvdXQgZGlmZmVyZW50
IHRoaW5ncy4gQVNJQ1MvRlBHQSBjYW4gZGlzY3JpbWluYXRlIGZsb3dzLiBCdXQgdGhlcmUgaXMg
bm8gZ2lzdCB3aGljaCBmbG93IHNob3VsZCBiZSB0cmVhdGVkIGluIHdoaWNoIHByb2Nlc3MuIFRo
ZSBlbWJlZGRlZCBzZW1hbnRpY3MgZ2l2ZXMgc3VjaCBnaXN0LiBBbHNvIHRoaXMgd2lsbCBzaW1w
bGlmeSB0aGUgcG9saWN5IGNvbmZpZ3VyYXRpb24uIEN1cnJlbnRseSwgeW91IG1heSBuZWVkIGEg
bGFyZ2Ugc3RhdGVmdWwgdGFibGUgZm9yIGhvdyB0byBwcm9jZXNzIGV2ZXJ5IGZsb3dzLiBXaXRo
IGV4cGxpY2l0bHkgZXhwcmVzc2VkIHNlbWFudGljIGJpdHMsIHlvdSBtYXkgZG8gaXQgaW4gc2lt
cGxlIHdheSwgaWYgc2VtYW50aWMgYml0ID09IHZhbHVlIEEsIHByb2Nlc3MgcGFja2V0IGluIEEg
bWV0aG9kLg0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCkZyb206IEdlb3JnZSBNaWNoYWVsc29uIFtt
YWlsdG86Z2dtQGFsZ2VicmFzLm9yZ10NClNlbnQ6IEZyaWRheSwgTWF5IDMxLCAyMDEzIDk6NDEg
QU0NClRvOiBTaGVuZyBKaWFuZw0KQ2M6IFJheSBIdW50ZXI7IDx2Nm9wc0BpZXRmLm9yZz47IGRy
YWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IENvdWxkIElQdjYgYWRkcmVzcyBiZSBtb3JlIHRoYW4gbG9jYXRv
cj8vL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0KDQp3aHkgb24gYWRkcmVz
cyBhbmQgbm90IHBlciBmbG93PyB5b3UgYWxyZWFkeSBoYXZlIEFTSUNTL0ZQR0Egd2hpY2ggZG8g
ZmxvdyBkaXNjcmltaW5hdGlvbiwgaXMgYSBwYWNrZXQgY2xhc3NpZmllciBvbiBzcmMsZHN0IHJl
YWxseSBiZXR0ZXIsIHdoZW4geW91IGNhbm5vdCBhY3R1YWxseSB0cnVzdCBpdD8NCg0KT24gRnJp
LCBNYXkgMzEsIDIwMTMgYXQgMTE6MzggQU0sIFNoZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdl
aS5jb208bWFpbHRvOmppYW5nc2hlbmdAaHVhd2VpLmNvbT4+IHdyb3RlOg0KPj4gU2hlbmcgSmlh
bmcgPG1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb208bWFpbHRvOmppYW5nc2hlbmdAaHVhd2Vp
LmNvbT4+DQo+PiAzMCBNYXkgMjAxMyAxMTo1OA0KPj4+PiBJUCBhZGRyZXNzZXMgYXJlIGRlc2ln
bmVkIGFzIHRvcG9sb2d5IGxvY2F0b3IsIHNvIHRoYXQgZXZlcnkgcGFja2V0IGNhbg0KPmJlDQo+
Pj4gcm91dGVkIHRvIGl0cyBuZXR3b3JrIGRlc3RpbmF0aW9uLg0KPj4+PiBIb3dldmVyLCBldmVu
IGluIElQdjQgZXJhLCBzb21lIG5ldHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyIElQ
DQo+Pj4gYWRkcmVzcyB3aXRoIGNlcnRhaW4gc2VtYW50aWMgbG9jYWxseS4gVGhlc2Uga2luZCBv
ZiBtZWNoYW5pc20gZXhwbGljaXRseQ0KPj4+IGV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRp
ZXMgb2YgZXZlcnkgcGFja2V0LiBDb25zZXF1ZW50bHksIHRoZXNlDQo+bmV0d29yaw0KPj4+IG9w
ZXJhdG9ycyBjYW4gaW5zcGVjdCB0aGUgcHJvcGVydGllcyBvZiBwYWNrZXRzIGVhc2lseSBieSBt
YXBwaW5nIHRoZQ0KPj4+IGFkZHJlc3NlcyBiYWNrIHRvIHNlbWFudGljLg0KPj4+PiBOZXR3b3Jr
IG9wZXJhdG9ycywgd2hvIGhhdmUgbGFyZ2UgSVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbyBj
aG9vc2UNCj50bw0KPj4+IGVtYmVkZGVkIHNvbWUgc2VtYW50aWNzIGludG8gSVB2NiBhZGRyZXNz
ZXMgYnkgYXNzaWduaW5nIGFkZGl0aW9uYWwNCj4+PiBzaWduaWZpY2FuY2UgdG8gc3BlY2lmaWMg
Yml0cyB3aXRoaW4gdGhlIHByZWZpeC4NCj4+PiBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1w
cmVmaXggZG9jdW1lbnRzIGEgZnJhbWV3b3JrIG1ldGhvZCB0aGF0DQo+Pj4gbmV0d29yayBvcGVy
YXRpb25zIG1heSB1c2UgdGhlaXIgYWRkcmVzc2VzIHdpdGggZW1iZWRkZWQgc2VtYW50aWNzLg0K
PlRoZXNlDQo+Pj4gc2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBz
aW5nbGUgbmV0d29yaywgb3IgZ3JvdXAgb2YNCj4+PiBpbnRlcmNvbm5lY3RlZCBuZXR3b3JrcyB3
aGljaCBzaGFyZSBhIGNvbW1vbiBhZGRyZXNzaW5nIHBvbGljeS4gQmFzZWQNCj5vbg0KPj4+IHRo
ZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMgaW4gc291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3Nl
cywgdGhlDQo+bmV0d29yaw0KPj4+IG9wZXJhdG9ycyBjYW4gYWNjb3JkaW5nbHkgdHJlYXQgbmV0
d29yayBwYWNrZXRzIGRpZmZlcmVudGx5IGFuZCBlZmZpY2llbnRseS4NCj4+Pj4gaHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+
Pj4+DQo+Pj4+IENvdWxkIHlvdSBwbGVhc2UgcmV2aWV3IHRoaXMgZHJhZnQgYW5kIGNvbW1lbnRz
PyBJdCB3aWxsIGhlbHAgdGhlDQo+ZG9jdW1lbnQNCj4+PiBiZWNvbWUgbW9yZSB1c2VmdWwgaW5m
b3JtYXRpb24gdG8gYmUgc2hhcmVkLg0KPj4+PiBCZXN0IHJlZ2FyZHMsDQo+Pj4+DQo+Pj4+IFNo
ZW5nDQo+Pj4+DQo+Pj4gSSBjb21wbGV0ZWx5IHVuZGVyc3RhbmQgdGhlIGRlc2lyZSBmb3Igb3Bl
cmF0b3JzIHRvIGhhdmUgYWRkaXRpb25hbA0KPj4+IHNlbWFudGljcyBhdmFpbGFibGUgZm9yIGN1
c3RvbWl6ZWQgcGFja2V0IHByb2Nlc3NpbmcuIEZsb3cgbGFiZWwgbm93IGhhcw0KPj4+IHZlcnkg
bGltaXRlZCBwcm9wZXJ0aWVzIG9wdGltaXNlZCBmb3IgbG9hZCBiYWxhbmNlcnMuIERTQ1Agb25s
eSBoYXMgYQ0KPj4+IGZldyBiaXRzICh3YXkgbGVzcyB0aGFuIHRoZSBudW1iZXIgb2YgY3VzdG9t
ZXJzJyBwb2xpY2llcykuIEFDTHMgYXJlDQo+Pj4gaGVhdnkgdG8gcHJvY2VzcyBhdCBlYWNoIGhv
cC4uLi4NCj4+Pg0KPj4+IEJ1dCB3b3VsZG4ndCB0aGlzIGluZm9ybWF0aW9uIGJlIGJldHRlciBv
ZmYgZW5jb2RlZCBhcyB0YWdzIGluIG9uZSBvcg0KPj4+IG1vcmUgaG9wLWJ5LWhvcCBoZWFkZXIg
b3B0aW9ucyAodGhhdCBjb3VsZCBiZSByZS13cml0dGVuIG9uIHRoZSBmbHkpLA0KPj4+IHJhdGhl
ciB0aGFuIGVuY29kZWQgaW4gdGhlIElQdjYgYWRkcmVzcyBzcGFjZT8NCj4+DQo+PiBUaGUgc2Vj
dGlvbiA0LjEgIkp1c3RpZmNhdGlvbiBmb3IgU2VtYW50aWNzIHdpdGggdGhlIElQdjYgUHJlZml4
IiBkZXNjcmliZXMNCj50aGUgcmVhc29ucy4NCj4+DQo+PiBVc2VycyBtYXkgZWFzaWx5IGNoYW5n
ZSB0aGUgc2V0dGluZyBvZiBleHRlbnNpb24gaGVhZGVyIGluIG9yZGVyIHRvIG9idGFpbg0KPnVu
ZGVzZXJ2ZWQgcHJpb3JpdGllcy9wcml2aWxlZ2VzLiBTZW1hbnRpYyBwcmVmaXggYXBwcm9hY2gg
ZG9lcyByZXF1aXJlIHRoZQ0KPmRlcGxveW1lbnQgb2YgYWNjZXNzIGNvbnRyb2wgZmlsdGVycy4g
VGhlIHBhY2tldHMgd2l0aCB0aGUgbm9uY29tcGxpYW5jZQ0KPnNvdXJjZSBhZGRyZXNzZXMgc2hv
dWxkIGJlIGZpbHRlcmVkLiBUaGUgcHJlZml4IGlzIGRlbGVnYXRlZCBieSB0aGUgbmV0d29yay4N
Cj5UaGVyZWZvcmUgdGhlIG5ldHdvcmsgaXMgYWJsZSB0byBkZXRlY3QgYW55IHVuZGVzaXJlZCBt
b2RpZmljYXRpb25zIGFuZCBmaWx0ZXINCj50aGUgcGFja2V0IGFjY29yZGluZ2x5Lg0KPj4NCj4+
IENoZWVycywNCj4+DQo+PiBTaGVuZw0KPj4NCj4+DQo+SSBkb24ndCBidXkgeW91ciBqdXN0aWZp
Y2F0aW9uLiBXaGV0aGVyIGFuIG9wZXJhdG9yIGZpbHRlcnMgb24NCj5hdXRob3Jpc2VkIGFkZHJl
c3MgcmFuZ2Ugb3IgcmUtd3JpdGVzL2ZpbHRlcnMgYW4gdW5hdXRob3Jpc2VkIGhvcC1ieS1ob3AN
Cj50YWcgaXMgZWZmZWN0aXZlbHkgdGhlIHNhbWUgSU1ITy4gV2UgaGF2ZSBleGFjdGx5IHRoZSBz
YW1lIGlzc3VlcyBvZg0KPnBvdGVudGlhbCB0aGVmdCBvZiBzZXJ2aWNlIHdpdGggRFNDUCB0b2Rh
eSwgYW5kIHRoZSBzb2x1dGlvbiBpcyBlcXVhbGx5DQo+c2ltcGxlOiBEU0NQIG1hcmtkb3duIGF0
IHRoZSBpbmdyZXNzIHBvcnQuDQpZZXMsIHRoZSB0cnVzdCBpc3N1ZSBpcyB0aGUgc2FtZSB3aXRo
IERTQ1AuIEhvd2V2ZXIsIHRoZSBEU0NQIGFic3RyYWN0IGFsbCB0aGUgc2VtYW50aWNzIGludG8g
c2VydmljZSBjbGFzc2VzLCB3aGljaCBpcyBvbmUgc2luZ2xlIGRpbWVuc2lvbi4gVGhpcyBhYnN0
cmFjdCBwcm9jZXNzaW5nIGhhcyBsb3N0IGEgbG90IG9mIGluZm9ybWF0aW9uLCB3aGljaCBwcm92
aWRlcnMgd2FudCB0byBpbnNwZWN0IGZvciBldmVyeSBwYWNrZXQsIHRoZW4gcHJvY2VzcyB0aGUg
cGFja2V0IGFjY29yZGluZ2x5LiBUaGUgZXhwbGljaXRseSBleHByZXNzZWQgc2VtYW50aWNzIGlu
IHByZWZpeCBwcm92aWRlcyBtdWNoIG1vcmUgaW5mb3JtYXRpb25zDQoNClNoZW5nDQoNCj5yZWdh
cmRzLA0KPlJheUgNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5n
IGxpc3QNCmlwdjZAaWV0Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+DQpBZG1pbmlzdHJhdGl2
ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2DQot
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5v
c2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJc
QOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZp
bml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXtt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1z
b0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xs
b3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJn
aW46NzIuMHB0IDkwLjBwdCA3Mi4wcHQgOTAuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFn
ZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iWkgtQ04iIGxpbms9ImJs
dWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+SGksIEdlb3JnZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9y
OiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+TXkgZ3Vlc3MgaXMgd2UgbWF5IHRhbGtpbmcgYWJvdXQgZGlmZmVyZW50IHRoaW5ncy4gQVNJ
Q1MvRlBHQSBjYW4gZGlzY3JpbWluYXRlIGZsb3dzLiBCdXQgdGhlcmUgaXMgbm8gZ2lzdCB3aGlj
aCBmbG93IHNob3VsZCBiZSB0cmVhdGVkIGluIHdoaWNoDQogcHJvY2Vzcy4gVGhlIGVtYmVkZGVk
IHNlbWFudGljcyBnaXZlcyBzdWNoIGdpc3QuIEFsc28gdGhpcyB3aWxsIHNpbXBsaWZ5IHRoZSBw
b2xpY3kgY29uZmlndXJhdGlvbi4gQ3VycmVudGx5LCB5b3UgbWF5IG5lZWQgYSBsYXJnZSBzdGF0
ZWZ1bCB0YWJsZSBmb3IgaG93IHRvIHByb2Nlc3MgZXZlcnkgZmxvd3MuIFdpdGggZXhwbGljaXRs
eSBleHByZXNzZWQgc2VtYW50aWMgYml0cywgeW91IG1heSBkbyBpdCBpbiBzaW1wbGUgd2F5LCBp
ZiBzZW1hbnRpYw0KIGJpdCA9PSB2YWx1ZSBBLCBwcm9jZXNzIHBhY2tldCBpbiBBIG1ldGhvZC48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5TaGVuZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20g
MGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNv
bGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZy
b206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBH
ZW9yZ2UgTWljaGFlbHNvbiBbbWFpbHRvOmdnbUBhbGdlYnJhcy5vcmddDQo8YnI+DQo8Yj5TZW50
OjwvYj4gRnJpZGF5LCBNYXkgMzEsIDIwMTMgOTo0MSBBTTxicj4NCjxiPlRvOjwvYj4gU2hlbmcg
Smlhbmc8YnI+DQo8Yj5DYzo8L2I+IFJheSBIdW50ZXI7ICZsdDt2Nm9wc0BpZXRmLm9yZyZndDs7
IGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZzsgaXB2NkBp
ZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogQ291bGQgSVB2NiBhZGRyZXNzIGJlIG1v
cmUgdGhhbiBsb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPndoeSBvbiBhZGRyZXNzIGFu
ZCBub3QgcGVyIGZsb3c/IHlvdSBhbHJlYWR5IGhhdmUgQVNJQ1MvRlBHQSB3aGljaCBkbyBmbG93
IGRpc2NyaW1pbmF0aW9uLCBpcyBhIHBhY2tldCBjbGFzc2lmaWVyIG9uIHNyYyxkc3QgcmVhbGx5
IGJldHRlciwgd2hlbiB5b3UgY2Fubm90IGFjdHVhbGx5IHRydXN0IGl0PyZuYnNwOzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+T24gRnJpLCBNYXkgMzEsIDIwMTMgYXQgMTE6MzggQU0sIFNoZW5nIEppYW5nICZsdDs8
YSBocmVmPSJtYWlsdG86amlhbmdzaGVuZ0BodWF3ZWkuY29tIiB0YXJnZXQ9Il9ibGFuayI+amlh
bmdzaGVuZ0BodWF3ZWkuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbTox
Mi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7Jmd0OyBTaGVuZyBKaWFuZyAmbHQ7bWFpbHRv
OjxhIGhyZWY9Im1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20iPmppYW5nc2hlbmdAaHVhd2Vp
LmNvbTwvYT4mZ3Q7PGJyPg0KJmd0OyZndDsgMzAgTWF5IDIwMTMgMTE6NTg8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7IElQIGFkZHJlc3NlcyBhcmUgZGVzaWduZWQgYXMgdG9wb2xvZ3kgbG9jYXRvciwg
c28gdGhhdCBldmVyeSBwYWNrZXQgY2FuPGJyPg0KJmd0O2JlPGJyPg0KJmd0OyZndDsmZ3Q7IHJv
dXRlZCB0byBpdHMgbmV0d29yayBkZXN0aW5hdGlvbi48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IEhv
d2V2ZXIsIGV2ZW4gaW4gSVB2NCBlcmEsIHNvbWUgbmV0d29yayBvcGVyYXRvcnMgaGF2ZSBtYXBw
ZWQgdGhlaXIgSVA8YnI+DQomZ3Q7Jmd0OyZndDsgYWRkcmVzcyB3aXRoIGNlcnRhaW4gc2VtYW50
aWMgbG9jYWxseS4gVGhlc2Uga2luZCBvZiBtZWNoYW5pc20gZXhwbGljaXRseTxicj4NCiZndDsm
Z3Q7Jmd0OyBleHByZXNzIHRoZSBzZW1hbnRpYyBwcm9wZXJ0aWVzIG9mIGV2ZXJ5IHBhY2tldC4g
Q29uc2VxdWVudGx5LCB0aGVzZTxicj4NCiZndDtuZXR3b3JrPGJyPg0KJmd0OyZndDsmZ3Q7IG9w
ZXJhdG9ycyBjYW4gaW5zcGVjdCB0aGUgcHJvcGVydGllcyBvZiBwYWNrZXRzIGVhc2lseSBieSBt
YXBwaW5nIHRoZTxicj4NCiZndDsmZ3Q7Jmd0OyBhZGRyZXNzZXMgYmFjayB0byBzZW1hbnRpYy48
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IE5ldHdvcmsgb3BlcmF0b3JzLCB3aG8gaGF2ZSBsYXJnZSBJ
UHY2IGFkZHJlc3Mgc3BhY2UsIG1heSBhbHNvIGNob29zZTxicj4NCiZndDt0bzxicj4NCiZndDsm
Z3Q7Jmd0OyBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVzc2VzIGJ5IGFz
c2lnbmluZyBhZGRpdGlvbmFsPGJyPg0KJmd0OyZndDsmZ3Q7IHNpZ25pZmljYW5jZSB0byBzcGVj
aWZpYyBiaXRzIHdpdGhpbiB0aGUgcHJlZml4Ljxicj4NCiZndDsmZ3Q7Jmd0OyBkcmFmdC1qaWFu
Zy12Nm9wcy1zZW1hbnRpYy1wcmVmaXggZG9jdW1lbnRzIGEgZnJhbWV3b3JrIG1ldGhvZCB0aGF0
PGJyPg0KJmd0OyZndDsmZ3Q7IG5ldHdvcmsgb3BlcmF0aW9ucyBtYXkgdXNlIHRoZWlyIGFkZHJl
c3NlcyB3aXRoIGVtYmVkZGVkIHNlbWFudGljcy48YnI+DQomZ3Q7VGhlc2U8YnI+DQomZ3Q7Jmd0
OyZndDsgc2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1bCB3aXRoaW4gYSBzaW5nbGUg
bmV0d29yaywgb3IgZ3JvdXAgb2Y8YnI+DQomZ3Q7Jmd0OyZndDsgaW50ZXJjb25uZWN0ZWQgbmV0
d29ya3Mgd2hpY2ggc2hhcmUgYSBjb21tb24gYWRkcmVzc2luZyBwb2xpY3kuIEJhc2VkPGJyPg0K
Jmd0O29uPGJyPg0KJmd0OyZndDsmZ3Q7IHRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMgaW4g
c291cmNlL2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlPGJyPg0KJmd0O25ldHdvcms8YnI+DQom
Z3Q7Jmd0OyZndDsgb3BlcmF0b3JzIGNhbiBhY2NvcmRpbmdseSB0cmVhdCBuZXR3b3JrIHBhY2tl
dHMgZGlmZmVyZW50bHkgYW5kIGVmZmljaWVudGx5Ljxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgPGEg
aHJlZj0iaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlhbmctdjZvcHMtc2VtYW50
aWMtcHJlZml4LTAzIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXgtMDM8L2E+PGJyPg0KJmd0OyZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgQ291bGQgeW91IHBsZWFzZSByZXZpZXcgdGhp
cyBkcmFmdCBhbmQgY29tbWVudHM/IEl0IHdpbGwgaGVscCB0aGU8YnI+DQomZ3Q7ZG9jdW1lbnQ8
YnI+DQomZ3Q7Jmd0OyZndDsgYmVjb21lIG1vcmUgdXNlZnVsIGluZm9ybWF0aW9uIHRvIGJlIHNo
YXJlZC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IEJlc3QgcmVnYXJkcyw8YnI+DQomZ3Q7Jmd0OyZn
dDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBTaGVuZzxicj4NCiZndDsmZ3Q7Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyZndDsgSSBjb21wbGV0ZWx5IHVuZGVyc3RhbmQgdGhlIGRlc2lyZSBmb3Ig
b3BlcmF0b3JzIHRvIGhhdmUgYWRkaXRpb25hbDxicj4NCiZndDsmZ3Q7Jmd0OyBzZW1hbnRpY3Mg
YXZhaWxhYmxlIGZvciBjdXN0b21pemVkIHBhY2tldCBwcm9jZXNzaW5nLiBGbG93IGxhYmVsIG5v
dyBoYXM8YnI+DQomZ3Q7Jmd0OyZndDsgdmVyeSBsaW1pdGVkIHByb3BlcnRpZXMgb3B0aW1pc2Vk
IGZvciBsb2FkIGJhbGFuY2Vycy4gRFNDUCBvbmx5IGhhcyBhPGJyPg0KJmd0OyZndDsmZ3Q7IGZl
dyBiaXRzICh3YXkgbGVzcyB0aGFuIHRoZSBudW1iZXIgb2YgY3VzdG9tZXJzJyBwb2xpY2llcyku
IEFDTHMgYXJlPGJyPg0KJmd0OyZndDsmZ3Q7IGhlYXZ5IHRvIHByb2Nlc3MgYXQgZWFjaCBob3Au
Li4uPGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IEJ1dCB3b3VsZG4ndCB0aGlz
IGluZm9ybWF0aW9uIGJlIGJldHRlciBvZmYgZW5jb2RlZCBhcyB0YWdzIGluIG9uZSBvcjxicj4N
CiZndDsmZ3Q7Jmd0OyBtb3JlIGhvcC1ieS1ob3AgaGVhZGVyIG9wdGlvbnMgKHRoYXQgY291bGQg
YmUgcmUtd3JpdHRlbiBvbiB0aGUgZmx5KSw8YnI+DQomZ3Q7Jmd0OyZndDsgcmF0aGVyIHRoYW4g
ZW5jb2RlZCBpbiB0aGUgSVB2NiBhZGRyZXNzIHNwYWNlPzxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0
OyZndDsgVGhlIHNlY3Rpb24gNC4xICZxdW90O0p1c3RpZmNhdGlvbiBmb3IgU2VtYW50aWNzIHdp
dGggdGhlIElQdjYgUHJlZml4JnF1b3Q7IGRlc2NyaWJlczxicj4NCiZndDt0aGUgcmVhc29ucy48
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IFVzZXJzIG1heSBlYXNpbHkgY2hhbmdlIHRoZSBz
ZXR0aW5nIG9mIGV4dGVuc2lvbiBoZWFkZXIgaW4gb3JkZXIgdG8gb2J0YWluPGJyPg0KJmd0O3Vu
ZGVzZXJ2ZWQgcHJpb3JpdGllcy9wcml2aWxlZ2VzLiBTZW1hbnRpYyBwcmVmaXggYXBwcm9hY2gg
ZG9lcyByZXF1aXJlIHRoZTxicj4NCiZndDtkZXBsb3ltZW50IG9mIGFjY2VzcyBjb250cm9sIGZp
bHRlcnMuIFRoZSBwYWNrZXRzIHdpdGggdGhlIG5vbmNvbXBsaWFuY2U8YnI+DQomZ3Q7c291cmNl
IGFkZHJlc3NlcyBzaG91bGQgYmUgZmlsdGVyZWQuIFRoZSBwcmVmaXggaXMgZGVsZWdhdGVkIGJ5
IHRoZSBuZXR3b3JrLjxicj4NCiZndDtUaGVyZWZvcmUgdGhlIG5ldHdvcmsgaXMgYWJsZSB0byBk
ZXRlY3QgYW55IHVuZGVzaXJlZCBtb2RpZmljYXRpb25zIGFuZCBmaWx0ZXI8YnI+DQomZ3Q7dGhl
IHBhY2tldCBhY2NvcmRpbmdseS48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IENoZWVycyw8
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IFNoZW5nPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7
Jmd0Ozxicj4NCiZndDtJIGRvbid0IGJ1eSB5b3VyIGp1c3RpZmljYXRpb24uIFdoZXRoZXIgYW4g
b3BlcmF0b3IgZmlsdGVycyBvbjxicj4NCiZndDthdXRob3Jpc2VkIGFkZHJlc3MgcmFuZ2Ugb3Ig
cmUtd3JpdGVzL2ZpbHRlcnMgYW4gdW5hdXRob3Jpc2VkIGhvcC1ieS1ob3A8YnI+DQomZ3Q7dGFn
IGlzIGVmZmVjdGl2ZWx5IHRoZSBzYW1lIElNSE8uIFdlIGhhdmUgZXhhY3RseSB0aGUgc2FtZSBp
c3N1ZXMgb2Y8YnI+DQomZ3Q7cG90ZW50aWFsIHRoZWZ0IG9mIHNlcnZpY2Ugd2l0aCBEU0NQIHRv
ZGF5LCBhbmQgdGhlIHNvbHV0aW9uIGlzIGVxdWFsbHk8YnI+DQomZ3Q7c2ltcGxlOiBEU0NQIG1h
cmtkb3duIGF0IHRoZSBpbmdyZXNzIHBvcnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5ZZXMsIHRo
ZSB0cnVzdCBpc3N1ZSBpcyB0aGUgc2FtZSB3aXRoIERTQ1AuIEhvd2V2ZXIsIHRoZSBEU0NQIGFi
c3RyYWN0IGFsbCB0aGUgc2VtYW50aWNzIGludG8gc2VydmljZSBjbGFzc2VzLCB3aGljaCBpcyBv
bmUgc2luZ2xlIGRpbWVuc2lvbi4gVGhpcyBhYnN0cmFjdCBwcm9jZXNzaW5nIGhhcyBsb3N0IGEg
bG90IG9mIGluZm9ybWF0aW9uLCB3aGljaCBwcm92aWRlcnMgd2FudA0KIHRvIGluc3BlY3QgZm9y
IGV2ZXJ5IHBhY2tldCwgdGhlbiBwcm9jZXNzIHRoZSBwYWNrZXQgYWNjb3JkaW5nbHkuIFRoZSBl
eHBsaWNpdGx5IGV4cHJlc3NlZCBzZW1hbnRpY3MgaW4gcHJlZml4IHByb3ZpZGVzIG11Y2ggbW9y
ZSBpbmZvcm1hdGlvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQpTaGVuZzxicj4NCjxicj4N
CiZndDtyZWdhcmRzLDxicj4NCiZndDtSYXlIPGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQpJRVRGIElQ
djYgd29ya2luZyBncm91cCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86aXB2NkBp
ZXRmLm9yZyI+aXB2NkBpZXRmLm9yZzwvYT48YnI+DQpBZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czog
PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2IiB0YXJn
ZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjY8
L2E+PGJyPg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC99BA8nkgeml512mbxchi_--

From jiangsheng@huawei.com  Thu May 30 20:52:21 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8673521F8A68; Thu, 30 May 2013 20:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.163
X-Spam-Level: 
X-Spam-Status: No, score=-6.163 tagged_above=-999 required=5 tests=[AWL=-0.165, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+JG6nt6Kyl9; Thu, 30 May 2013 20:52:17 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 644EB21F8A0B; Thu, 30 May 2013 20:52:15 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY71800; Fri, 31 May 2013 03:52:13 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:51:36 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 04:52:11 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.01.0323.007; Fri, 31 May 2013 11:52:06 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Qiong <bingxuere@gmail.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXbFYPRFGuqgFt0q7mRTZXmU/OZkep5Pg
Date: Fri, 31 May 2013 03:52:05 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99BE0@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99B42@nkgeml512-mbx.china.huawei.com> <CAH3bfABsXEcuhh-FKZn-3VjMYzhjpbHiCbrSWXHeVE+Zaw4izw@mail.gmail.com>
In-Reply-To: <CAH3bfABsXEcuhh-FKZn-3VjMYzhjpbHiCbrSWXHeVE+Zaw4izw@mail.gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923AC99BE0nkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:52:21 -0000

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

SGksIFFpb25nLA0KDQpTaGFyaW5nIHlvdXIgY29uY2Vybi4gVGhpcyB2YXJpYXRpb24gaXMgb25s
eSBvbmUgb2YgcG9zc2libGUgd2F5IHRvIHVzZSB0aGUgYWRkcmVzcy4gU28gZmFyLCBJIGFtIG5v
dCBjb252aW5jZWQgd2h5IGdpdmUgc3Vic2NyaWJlciBzb21lIG11Y2ggZnJlZSBiaXRzIGFuZCBo
b3cgdG8gdXNlIGl0IHdlbGwuIE1heWJlIE93ZW4sIHdobyBzdWdnZXN0IHRoaXMgY2FuIGdpdmUg
dXMgZm9yIGluZm9ybWF0aW9uLiBMZXRz4oCZIGRpc2N1c3MgdGhlIGZ1cnRoZXIuIEF0IHRoZSBl
bmQsIG1heWJlIHdoYXQgd2Ugb25seSBuZWVkIHRvIGRvIGluIHRoZSBkcmFmdCBpcyB0byBkb2N1
bWVudCB0aGlzIHBvc3NpYmlsaXRpZXMgYW5kIG5ldXRyYWxseSByZWNvcmQgaXRzIGFkdmFudGFn
ZXMgYW5kIHBpdGZhbGxzLg0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCkZyb206IFFpb25nIFttYWls
dG86YmluZ3h1ZXJlQGdtYWlsLmNvbV0NClNlbnQ6IEZyaWRheSwgTWF5IDMxLCAyMDEzIDExOjQ1
IEFNDQpUbzogU2hlbmcgSmlhbmcNCkNjOiBUZWQgTGVtb247IE93ZW4gRGVMb25nOyA8djZvcHNA
aWV0Zi5vcmc+OyBkcmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9vbHMuaWV0Zi5v
cmc7IGlwdjZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbdjZvcHNdIENvdWxkIElQdjYgYWRkcmVz
cyBiZSBtb3JlIHRoYW4gbG9jYXRvcj8vL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZp
eC0wMw0KDQpIaSBTaGVuZywNCg0KT24gRnJpLCBNYXkgMzEsIDIwMTMgYXQgMTE6MjQgQU0sIFNo
ZW5nIEppYW5nIDxqaWFuZ3NoZW5nQGh1YXdlaS5jb208bWFpbHRvOmppYW5nc2hlbmdAaHVhd2Vp
LmNvbT4+IHdyb3RlOg0KQ29tcGFyaW5nIGdpdmluZyAxNiBiaXRzIGZvciBzdWJzY3JpYmVycywg
d2hpY2ggcmFyZWx5IHVzZSBpdCBvciB3ZSBzdGlsbCBoYXZlIG5vIGNvbmNyZXRlIGlkZWEgaG93
IHRoaXMgd2lsbCBiZSB1c2VkLCB0aGUgc2VtYW50aWMgYml0cyBvbiB0aGUgcHJvdmlkZXIgc2lk
ZSBsb29rcyBtb3JlIGhlbHBmdWwuDQoNCk9yIHByb3ZpZGVyIG1heSBkZXNpZ25hdGUgdGhlIGJp
dCBpbiB0aGUgbG93ZXIgMTYgYml0cyBjYW4gaGF2ZSBzb21lIHNlbWFudGljcy4gRm9yIGV4YW1w
bGUsIGEgcHJvdmlkZXIgbWF5IGdpdmUgZXZlcnkgc3Vic2NyaWJlciAvNDggYW5kIGFwcG9pbnQg
dGhhdCBhbGwgc3Vic2NyaWJlcnMgc2hvdWxkIHVzZSB0aGVpciAvNDgrMDAwMCAoNDh+NTEgYml0
KSAtPiBhIC81MiBwcmVmaXggZm9yIGEgY2VydGFpbiBhcHBsaWNhdGlvbiwgbGlrZSBWb0lQLiBU
aGVuIHRoZSBwcm92aWRlciBjYW4gaW5zcGVjdCBhbGwgVm9JUCB0cmFmZmljIGZyb20gZGlmZmVy
ZW50IHN1YnNjcmliZXJzIGJ5IG9ubHkgc2V0IGNvbmRpdGlvbiA0OH41MSBiaXQgZXF1YWwgdG8g
MDAwMC4gVGhpcyB2YXJpYXRpb24gb2Ygc2VtYW50aWMgcHJlZml4IGlzIGFsc28gaGVscGZ1bC4N
CltRaW9uZ10gSSBoYXZlIGxpdHRsZSBjb25jZXJuIGZvciB0aGlzIHZhcmlhdGlvbi4gRm9yIG9w
ZXJhdG9ycyB3aG8gY2FuIG5vdCBmdWxseSBjb250cm9sIG9mIHN1YnNjcmliZXIncyBDUEUsIHRo
aXMgc29sdXRpb24gbWF5IGhhdmUgdHJ1c3QgaXNzdWUsIGFuZCBpdCBtYXkgZ2V0IGNvbmZsaWN0
IHdpdGggb3RoZXIgQ1BFJ3MgYWxsb2NhdGlvbiBwb2xpY3kuIEJ1dCBpdCBpcyBvayBmb3Igb3Bl
cmF0b3JzIHdobyBjYW4gZnVsbHkgY29udHJvbCBvZiBzdWJzY3JpYmVyJ3MgQ1BFLg0KDQpCZXN0
IHdpc2hlcw0KUWlvbmcNCg0KDQoNCkZyb206IFRlZCBMZW1vbiBbbWFpbHRvOlRlZC5MZW1vbkBu
b21pbnVtLmNvbTxtYWlsdG86VGVkLkxlbW9uQG5vbWludW0uY29tPl0NClNlbnQ6IEZyaWRheSwg
TWF5IDMxLCAyMDEzIDM6MjkgQU0NClRvOiBPd2VuIERlTG9uZw0KQ2M6IFNoZW5nIEppYW5nOyBk
cmFmdC1qaWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRy
YWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZz47IGlwdjZAaWV0
Zi5vcmc8bWFpbHRvOmlwdjZAaWV0Zi5vcmc+OyA8djZvcHNAaWV0Zi5vcmc8bWFpbHRvOnY2b3Bz
QGlldGYub3JnPj4NClN1YmplY3Q6IFJlOiBbdjZvcHNdIENvdWxkIElQdjYgYWRkcmVzcyBiZSBt
b3JlIHRoYW4gbG9jYXRvcj8vL2RyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeC0wMw0K
DQpPbiBNYXkgMzAsIDIwMTMsIGF0IDEyOjA4IFBNLCBPd2VuIERlTG9uZyA8b3dlbkBkZWxvbmcu
Y29tPG1haWx0bzpvd2VuQGRlbG9uZy5jb20+PiB3cm90ZToNCk5vdCBhIGdyZWF0IGFzc3VtcHRp
b24uLi4gVGhleSBzaG91bGQgbmVlZCA0IG1pbGxpb24gb3IgbW9yZSAvNDhzIHNpbmNlIGV2ZXJ5
IHN1YnNjcmliZXIgaXMgYXQgbGVhc3Qgb25lIGVuZCBzaXRlIGFuZCBldmVyeSBzdWJzY3JpYmVy
IGVuZCBzaXRlIHNob3VsZCByZWNlaXZlIGEgLzQ4Lg0KDQpJIGFtIG5vdCBpbiBsb3ZlIHdpdGgg
dXNpbmcgYml0cyBmcm9tIHByZWZpeGVzIGFzIHNlbWFudGljIHRhZ3MuICAgSG93ZXZlciwgaGF2
aW5nIHNhaWQgdGhhdCwgSSB0aGluayBpdCdzIGEgYml0IGlyb25pYyB0aGF0IHlvdSdyZSB0YWxr
aW5nIGFib3V0IHdhc3Rpbmcgc3BhY2Ugd2l0aCBzZW1hbnRpYyBiaXRzLCBvbiB0aGUgb25lIGhh
bmQsIGFuZCB0YWxraW5nIGFib3V0IHRoZSBuZWVkIGZvciBhIC80OCBpbiBldmVyeSBob21lIG9u
IHRoZSBvdGhlci4gICBJdCB3b3VsZCBiZSBwZXJmZWN0bHkgcmVhc29uYWJsZSBmb3IgdGhlIElT
UCB0byBzcGVjaWZ5IHRoYXQgc29tZSBvZiB0aGUgYml0cyBpbiB0aGUgLzQ4IGhhdmUgc2VtYW50
aWMgbWVhbmluZywgZm9yIGV4YW1wbGUsIGFuZCBnaXZlbiB0aGF0IHdlIHRoaW5rIGl0J3Mgb2th
eSB0byBnaXZlIHRoZSBob21lIG5ldHdvcmsgYSAvNDgsIHdlIGFyZSBoYXJkbHkgaW4gYSBwb3Np
dGlvbiB0byBxdWliYmxlIGFib3V0IGhvdyB0aGUgYml0cyBpbiB0aGF0IC80OCBhcmUgdXNlZC4N
Cg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnY2b3Bz
IG1haWxpbmcgbGlzdA0KdjZvcHNAaWV0Zi5vcmc8bWFpbHRvOnY2b3BzQGlldGYub3JnPg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KDQoNCg0KLS0NCj09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NClFpb25nIFN1bg0KQ2hp
bmEgVGVsZWNvbSBCZWlqaW5nIFJlc2VhcmNoIEluc3RpdHVkZQ0KDQoNCk9wZW4gc291cmNlIGNv
ZGU6DQpsaWdodHdlaWdodCA0b3ZlcjY6IGh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcHJvamVjdHMv
bGFmdDYvDQpQQ1AtbmF0Y29vcmQ6IGh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcHJvamVjdHMvcGNw
cG9ydHNldGRlbW8vDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PQ0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDEyIChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT48IS0tDQov
KiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OuWui+S9kzsN
CglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAx
MSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMi
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh
bWlseTpPcHRpbWE7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0
Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1h
cmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9
DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcy
LjBwdCA5MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQot
LT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4
dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpl
eHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+
DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSwgUWlv
bmcsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlNoYXJpbmcgeW91ciBjb25j
ZXJuLiBUaGlzIHZhcmlhdGlvbiBpcyBvbmx5IG9uZSBvZiBwb3NzaWJsZSB3YXkgdG8gdXNlIHRo
ZSBhZGRyZXNzLiBTbyBmYXIsIEkgYW0gbm90IGNvbnZpbmNlZCB3aHkgZ2l2ZSBzdWJzY3JpYmVy
IHNvbWUgbXVjaCBmcmVlDQogYml0cyBhbmQgaG93IHRvIHVzZSBpdCB3ZWxsLiBNYXliZSBPd2Vu
LCB3aG8gc3VnZ2VzdCB0aGlzIGNhbiBnaXZlIHVzIGZvciBpbmZvcm1hdGlvbi4gTGV0c+KAmSBk
aXNjdXNzIHRoZSBmdXJ0aGVyLiBBdCB0aGUgZW5kLCBtYXliZSB3aGF0IHdlIG9ubHkgbmVlZCB0
byBkbyBpbiB0aGUgZHJhZnQgaXMgdG8gZG9jdW1lbnQgdGhpcyBwb3NzaWJpbGl0aWVzIGFuZCBu
ZXV0cmFsbHkgcmVjb3JkIGl0cyBhZHZhbnRhZ2VzIGFuZCBwaXRmYWxscy48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEw
LjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj5TaGVuZzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYg
MS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwv
Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBRaW9uZyBbbWFpbHRv
OmJpbmd4dWVyZUBnbWFpbC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBNYXkgMzEs
IDIwMTMgMTE6NDUgQU08YnI+DQo8Yj5Ubzo8L2I+IFNoZW5nIEppYW5nPGJyPg0KPGI+Q2M6PC9i
PiBUZWQgTGVtb247IE93ZW4gRGVMb25nOyAmbHQ7djZvcHNAaWV0Zi5vcmcmZ3Q7OyBkcmFmdC1q
aWFuZy12Nm9wcy1zZW1hbnRpYy1wcmVmaXhAdG9vbHMuaWV0Zi5vcmc7IGlwdjZAaWV0Zi5vcmc8
YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFt2Nm9wc10gQ291bGQgSVB2NiBhZGRyZXNzIGJlIG1v
cmUgdGhhbiBsb2NhdG9yPy8vZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkhpIFNoZW5nLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBGcmksIE1heSAzMSwgMjAxMyBhdCAxMToyNCBB
TSwgU2hlbmcgSmlhbmcgJmx0OzxhIGhyZWY9Im1haWx0bzpqaWFuZ3NoZW5nQGh1YXdlaS5jb20i
IHRhcmdldD0iX2JsYW5rIj5qaWFuZ3NoZW5nQGh1YXdlaS5jb208L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+Q29tcGFyaW5nIGdpdmluZyAxNiBiaXRzIGZvciBzdWJzY3JpYmVycywgd2hpY2ggcmFy
ZWx5IHVzZSBpdCBvciB3ZSBzdGlsbCBoYXZlIG5vIGNvbmNyZXRlDQogaWRlYSBob3cgdGhpcyB3
aWxsIGJlIHVzZWQsIHRoZSBzZW1hbnRpYyBiaXRzIG9uIHRoZSBwcm92aWRlciBzaWRlIGxvb2tz
IG1vcmUgaGVscGZ1bC48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5PciBwcm92
aWRlciBtYXkgZGVzaWduYXRlIHRoZSBiaXQgaW4gdGhlIGxvd2VyIDE2IGJpdHMgY2FuIGhhdmUg
c29tZSBzZW1hbnRpY3MuIEZvcg0KIGV4YW1wbGUsIGEgcHJvdmlkZXIgbWF5IGdpdmUgZXZlcnkg
c3Vic2NyaWJlciAvNDggYW5kIGFwcG9pbnQgdGhhdCBhbGwgc3Vic2NyaWJlcnMgc2hvdWxkIHVz
ZSB0aGVpciAvNDgmIzQzOzAwMDAgKDQ4fjUxIGJpdCkgLSZndDsgYSAvNTIgcHJlZml4IGZvciBh
IGNlcnRhaW4gYXBwbGljYXRpb24sIGxpa2UgVm9JUC4gVGhlbiB0aGUgcHJvdmlkZXIgY2FuIGlu
c3BlY3QgYWxsIFZvSVAgdHJhZmZpYyBmcm9tIGRpZmZlcmVudCBzdWJzY3JpYmVycyBieSBvbmx5
DQogc2V0IGNvbmRpdGlvbiA0OH41MSBiaXQgZXF1YWwgdG8gMDAwMC4gVGhpcyB2YXJpYXRpb24g
b2Ygc2VtYW50aWMgcHJlZml4IGlzIGFsc28gaGVscGZ1bC48L3NwYW4+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+W1Fpb25nXSBJIGhhdmUg
bGl0dGxlIGNvbmNlcm4gZm9yIHRoaXMgdmFyaWF0aW9uLiBGb3Igb3BlcmF0b3JzIHdobyBjYW4g
bm90IGZ1bGx5IGNvbnRyb2wgb2Ygc3Vic2NyaWJlcidzIENQRSwgdGhpcyBzb2x1dGlvbiBtYXkg
aGF2ZSB0cnVzdCBpc3N1ZSwgYW5kIGl0IG1heSBnZXQgY29uZmxpY3Qgd2l0aCBvdGhlciBDUEUn
cyBhbGxvY2F0aW9uIHBvbGljeS4gQnV0IGl0IGlzDQogb2sgZm9yIG9wZXJhdG9ycyB3aG8gY2Fu
IGZ1bGx5IGNvbnRyb2wgb2Ygc3Vic2NyaWJlcidzIENQRS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkJlc3Qgd2lzaGVzPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPlFpb25nPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNt
IDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjxzcGFu
IGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNt
IDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsi
PiBUZWQNCiBMZW1vbiBbbWFpbHRvOjxhIGhyZWY9Im1haWx0bzpUZWQuTGVtb25Abm9taW51bS5j
b20iIHRhcmdldD0iX2JsYW5rIj5UZWQuTGVtb25Abm9taW51bS5jb208L2E+XQ0KPC9zcGFuPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiPlNlbnQ6PC9zcGFuPjwvYj48c3BhbiBs
YW5nPSJFTi1VUyI+IEZyaWRheSwgTWF5IDMxLCAyMDEzIDM6MjkgQU08YnI+DQo8Yj5Ubzo8L2I+
IE93ZW4gRGVMb25nPGJyPg0KPGI+Q2M6PC9iPiBTaGVuZyBKaWFuZzsgPGEgaHJlZj0ibWFpbHRv
OmRyYWZ0LWppYW5nLXY2b3BzLXNlbWFudGljLXByZWZpeEB0b29scy5pZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPg0KZHJhZnQtamlhbmctdjZvcHMtc2VtYW50aWMtcHJlZml4QHRvb2xzLmlldGYu
b3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4N
CmlwdjZAaWV0Zi5vcmc8L2E+OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnY2b3BzQGlldGYub3JnIiB0
YXJnZXQ9Il9ibGFuayI+djZvcHNAaWV0Zi5vcmc8L2E+Jmd0OzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIj5TdWJqZWN0Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBSZTogW3Y2b3BzXSBD
b3VsZCBJUHY2IGFkZHJlc3MgYmUgbW9yZSB0aGFuIGxvY2F0b3I/Ly9kcmFmdC1qaWFuZy12Nm9w
cy1zZW1hbnRpYy1wcmVmaXgtMDM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJz
cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIE1heSAzMCwgMjAxMywgYXQgMTI6MDggUE0sIE93
ZW4gRGVMb25nICZsdDs8YSBocmVmPSJtYWlsdG86b3dlbkBkZWxvbmcuY29tIiB0YXJnZXQ9Il9i
bGFuayI+b3dlbkBkZWxvbmcuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFy
Z2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7T3B0
aW1hJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij5Ob3QgYSBncmVhdCBhc3N1bXB0aW9uLi4uIFRo
ZXkgc2hvdWxkIG5lZWQgNCBtaWxsaW9uIG9yIG1vcmUgLzQ4cyBzaW5jZSBldmVyeSBzdWJzY3Jp
YmVyIGlzIGF0IGxlYXN0IG9uZQ0KIGVuZCBzaXRlIGFuZCBldmVyeSBzdWJzY3JpYmVyIGVuZCBz
aXRlIHNob3VsZCByZWNlaXZlIGEgLzQ4Ljwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMiPiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFu
IGxhbmc9IkVOLVVTIj5JIGFtIG5vdCBpbiBsb3ZlIHdpdGggdXNpbmcgYml0cyBmcm9tIHByZWZp
eGVzIGFzIHNlbWFudGljIHRhZ3MuICZuYnNwOyBIb3dldmVyLCBoYXZpbmcgc2FpZCB0aGF0LCBJ
IHRoaW5rIGl0J3MgYSBiaXQgaXJvbmljIHRoYXQgeW91J3JlIHRhbGtpbmcgYWJvdXQgd2FzdGlu
ZyBzcGFjZQ0KIHdpdGggc2VtYW50aWMgYml0cywgb24gdGhlIG9uZSBoYW5kLCBhbmQgdGFsa2lu
ZyBhYm91dCB0aGUgbmVlZCBmb3IgYSAvNDggaW4gZXZlcnkgaG9tZSBvbiB0aGUgb3RoZXIuICZu
YnNwOyBJdCB3b3VsZCBiZSBwZXJmZWN0bHkgcmVhc29uYWJsZSBmb3IgdGhlIElTUCB0byBzcGVj
aWZ5IHRoYXQgc29tZSBvZiB0aGUgYml0cyBpbiB0aGUgLzQ4IGhhdmUgc2VtYW50aWMgbWVhbmlu
ZywgZm9yIGV4YW1wbGUsIGFuZCBnaXZlbiB0aGF0IHdlIHRoaW5rIGl0J3MNCiBva2F5IHRvIGdp
dmUgdGhlIGhvbWUgbmV0d29yayBhIC80OCwgd2UgYXJlIGhhcmRseSBpbiBhIHBvc2l0aW9uIHRv
IHF1aWJibGUgYWJvdXQgaG93IHRoZSBiaXRzIGluIHRoYXQgLzQ4IGFyZSB1c2VkLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxh
bmc9IkVOLVVTIj48YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXzxicj4NCnY2b3BzIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzp2Nm9w
c0BpZXRmLm9yZyI+djZvcHNAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vdjZvcHM8L2E+PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyI+PGJyPg0KPGJyIGNsZWFyPSJhbGwiPg0KPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPi0tIDxicj4NCj09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08YnI+DQpRaW9uZyBTdW48
YnI+DQpDaGluYSBUZWxlY29tIEJlaWppbmcgUmVzZWFyY2ggSW5zdGl0dWRlPGJyPg0KPGJyPg0K
PGJyPg0KT3BlbiBzb3VyY2UgY29kZTo8YnI+DQpsaWdodHdlaWdodCA0b3ZlcjY6IDxpPjxhIGhy
ZWY9Imh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcHJvamVjdHMvbGFmdDYvIiB0YXJnZXQ9Il9ibGFu
ayI+aHR0cDovL3NvdXJjZWZvcmdlLm5ldC9wcm9qZWN0cy9sYWZ0Ni88L2E+PC9pPjxicj4NClBD
UC1uYXRjb29yZDo8aT4gPGEgaHJlZj0iaHR0cDovL3NvdXJjZWZvcmdlLm5ldC9wcm9qZWN0cy9w
Y3Bwb3J0c2V0ZGVtby8iIHRhcmdldD0iX2JsYW5rIj4NCmh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQv
cHJvamVjdHMvcGNwcG9ydHNldGRlbW8vPC9hPiA8L2k+PGJyPg0KPT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923AC99BE0nkgeml512mbxchi_--

From v6ops@globis.net  Thu May 30 23:23:09 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB2E21F928C; Thu, 30 May 2013 23:23:09 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dgxui7H21jfU; Thu, 30 May 2013 23:23:08 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D592D21F909A; Thu, 30 May 2013 23:23:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 81190870076; Fri, 31 May 2013 08:22:51 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAJm0d-621Ii; Fri, 31 May 2013 08:22:51 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 6273487002E; Fri, 31 May 2013 08:22:51 +0200 (CEST)
Message-ID: <51A841B5.3010805@globis.net>
Date: Fri, 31 May 2013 08:22:45 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 06:23:09 -0000

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 31 May 2013 03:38
>>> Sheng Jiang <mailto:jiangsheng@huawei.com>
>>> 30 May 2013 11:58
>>>>> IP addresses are designed as topology locator, so that every packet can
>> be
>>>> routed to its network destination.
>>>>> However, even in IPv4 era, some network operators have mapped their IP
>>>> address with certain semantic locally. These kind of mechanism explicitly
>>>> express the semantic properties of every packet. Consequently, these
>> network
>>>> operators can inspect the properties of packets easily by mapping the
>>>> addresses back to semantic.
>>>>> Network operators, who have large IPv6 address space, may also choose
>> to
>>>> embedded some semantics into IPv6 addresses by assigning additional
>>>> significance to specific bits within the prefix.
>>>> draft-jiang-v6ops-semantic-prefix documents a framework method that
>>>> network operations may use their addresses with embedded semantics.
>> These
>>>> semantics bits are only meaningful within a single network, or group of
>>>> interconnected networks which share a common addressing policy. Based
>> on
>>>> these embedded semantic bits in source/destination addresses, the
>> network
>>>> operators can accordingly treat network packets differently and efficiently.
>>>>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>>>>>
>>>>> Could you please review this draft and comments? It will help the
>> document
>>>> become more useful information to be shared.
>>>>> Best regards,
>>>>>
>>>>> Sheng
>>>>>
>>>> I completely understand the desire for operators to have additional
>>>> semantics available for customized packet processing. Flow label now has
>>>> very limited properties optimised for load balancers. DSCP only has a
>>>> few bits (way less than the number of customers' policies). ACLs are
>>>> heavy to process at each hop....
>>>>
>>>> But wouldn't this information be better off encoded as tags in one or
>>>> more hop-by-hop header options (that could be re-written on the fly),
>>>> rather than encoded in the IPv6 address space?
>>> The section 4.1 "Justifcation for Semantics with the IPv6 Prefix" describes
>> the reasons.
>>> Users may easily change the setting of extension header in order to obtain
>> undeserved priorities/privileges. Semantic prefix approach does require the
>> deployment of access control filters. The packets with the noncompliance
>> source addresses should be filtered. The prefix is delegated by the network.
>> Therefore the network is able to detect any undesired modifications and filter
>> the packet accordingly.
>>> Cheers,
>>>
>>> Sheng
>>>
>>>
>> I don't buy your justification. Whether an operator filters on
>> authorised address range or re-writes/filters an unauthorised hop-by-hop
>> tag is effectively the same IMHO. We have exactly the same issues of
>> potential theft of service with DSCP today, and the solution is equally
>> simple: DSCP markdown at the ingress port.
>
> Yes, the trust issue is the same with DSCP. However, the DSCP abstract all the semantics into service classes, which is one single dimension. This abstract processing has lost a lot of information, which providers want to inspect for every packet, then process the packet accordingly. The explicitly expressed semantics in prefix provides much more informations
>
> Sheng
>
>> regards,
>> RayH
>
Which is why I wrote "wouldn't this information be better off encoded as
tags in one or more hop-by-hop header options?" and not just "go and use
DSCP"

I contend that hop by hop options acting as tags would:

1) be the correct and logical place to transport such information

2) be capable of handling multiple semantics simultaneously

3) not unnecessarily waste/reserve IPv6 address space, which is large,
but not infinite

4) have much more information carrying capacity than a small and fixed
number of bits stolen from the IPv6 prefix
Your example in Appendix A shows 12 bits of information with only 3 bits
available per type of semantic bits. I suspect it will be impossible to
agree on a standard division of 12 bits that works for everyone, just as
DSCP gets overwritten at every AS boundary. Whereas a single hop by hop
option header has 4 octets as a minimum and can be extended by another 8
octets if necessary.

5) be optional: if a particular tag isn't required by a particular
session or node or LAN or site, you don't add it.
Rather than having a fixed 12 bits of information as suggested in
appendix A, you could only tag those properties necessary for this
packet (penalty of course is potentially more parsing on the fly, but
that trade off can be discussed e.g. by fixing the option length as you
suggest)

The conclusion from replies to the draft so far would seem to read "No,
don't do it"

I would therefore humbly suggest you concentrate more effort on
documenting a problem statement detailing the requirements for the
semantics of tagging that aren't met by today's solutions, and which are
making people turn to this alternative of prefix encoding, rather than
focussing on the mechanics of how to encode the semantics into the
prefix. One example I can think of would be Bellovin's distributed
firewalls and marking of security zones.

regards
RayH

From bingxuere@gmail.com  Thu May 30 20:45:46 2013
Return-Path: <bingxuere@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B1C21F8EBC; Thu, 30 May 2013 20:45:46 -0700 (PDT)
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, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwlLMXTAbh21; Thu, 30 May 2013 20:45:45 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0372E21F8CF4; Thu, 30 May 2013 20:45:43 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db10so765720veb.26 for <multiple recipients>; Thu, 30 May 2013 20:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ocrAnoUn+ziKeerM1jzZMmNBmpAxHCw/Ut0F3hJ2bm0=; b=ypqDG3kpq4mH13sI9DQ7Yzbx8QM+E2MtT8ePvRzGJRk4tj1xmAKolRjGl/hdObm3R3 owBBJDIAuwSbiJMmSDjqYlRepkrXmQuIGpJt9FP6U89ay0UVdj+rx071HXNDZGi7m3ah oKMIOj/NagMvt58SoMaVg7UveH865jVdkd0b0D+BJu+Pbi3z3YTPxfwYzwwBqAUYpaJs 1DoJYJc4fY19nMkfIZLEI2ei5y7+3HxRgQnXiWmlCCcE/P0eMLl1G90Tuo2Wrv62ZVMR SMEwZazVB2jLkVnh7KietayoMXnySpXatEqwdtteW0eAv12QkGLMlQsLuUdrvou2/8t3 26LQ==
X-Received: by 10.52.76.103 with SMTP id j7mr7173687vdw.90.1369971943154; Thu, 30 May 2013 20:45:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.115.3 with HTTP; Thu, 30 May 2013 20:45:02 -0700 (PDT)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99B42@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99B42@nkgeml512-mbx.china.huawei.com>
From: Qiong <bingxuere@gmail.com>
Date: Fri, 31 May 2013 11:45:02 +0800
Message-ID: <CAH3bfABsXEcuhh-FKZn-3VjMYzhjpbHiCbrSWXHeVE+Zaw4izw@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
To: Sheng Jiang <jiangsheng@huawei.com>
Content-Type: multipart/alternative; boundary=bcaec50162330658ad04ddfb735f
X-Mailman-Approved-At: Fri, 31 May 2013 00:07:46 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, Owen DeLong <owen@delong.com>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 03:45:46 -0000

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

Hi Sheng,

On Fri, May 31, 2013 at 11:24 AM, Sheng Jiang <jiangsheng@huawei.com> wrote:

>  Comparing giving 16 bits for subscribers, which rarely use it or we
> still have no concrete idea how this will be used, the semantic bits on the
> provider side looks more helpful.****
>
> ** **
>
> Or provider may designate the bit in the lower 16 bits can have some
> semantics. For example, a provider may give every subscriber /48 and
> appoint that all subscribers should use their /48+0000 (48~51 bit) -> a /52
> prefix for a certain application, like VoIP. Then the provider can inspect
> all VoIP traffic from different subscribers by only set condition 48~51 bit
> equal to 0000. This variation of semantic prefix is also helpful.
>
[Qiong] I have little concern for this variation. For operators who can not
fully control of subscriber's CPE, this solution may have trust issue, and
it may get conflict with other CPE's allocation policy. But it is ok for
operators who can fully control of subscriber's CPE.

Best wishes
Qiong


 ** **
>
> *From:* Ted Lemon [mailto:Ted.Lemon@nominum.com]
> *Sent:* Friday, May 31, 2013 3:29 AM
> *To:* Owen DeLong
> *Cc:* Sheng Jiang; draft-jiang-v6ops-semantic-prefix@tools.ietf.org;
> ipv6@ietf.org; <v6ops@ietf.org>
> *Subject:* Re: [v6ops] Could IPv6 address be more than
> locator?//draft-jiang-v6ops-semantic-prefix-03****
>
>  ** **
>
> On May 30, 2013, at 12:08 PM, Owen DeLong <owen@delong.com> wrote:****
>
>  Not a great assumption... They should need 4 million or more /48s since
> every subscriber is at least one end site and every subscriber end site
> should receive a /48.****
>
>  ** **
>
> I am not in love with using bits from prefixes as semantic tags.
> However, having said that, I think it's a bit ironic that you're talking
> about wasting space with semantic bits, on the one hand, and talking about
> the need for a /48 in every home on the other.   It would be perfectly
> reasonable for the ISP to specify that some of the bits in the /48 have
> semantic meaning, for example, and given that we think it's okay to give
> the home network a /48, we are hardly in a position to quibble about how
> the bits in that /48 are used.****
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/ *
===============================================

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

<div dir=3D"ltr">Hi Sheng,<div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Fri, May 31, 2013 at 11:24 AM, Sheng Jiang <span dir=3D"ltr">&l=
t;<a href=3D"mailto:jiangsheng@huawei.com" target=3D"_blank">jiangsheng@hua=
wei.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:break=
-word">
<div><div class=3D"im">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Comparing =
giving 16 bits for subscribers, which rarely use it or we still have no con=
crete idea how this will be used, the semantic bits on the
 provider side looks more helpful.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Or provide=
r may designate the bit in the lower 16 bits can have some semantics. For e=
xample, a provider may give every subscriber /48 and appoint
 that all subscribers should use their /48+0000 (48~51 bit) -&gt; a /52 pre=
fix for a certain application, like VoIP. Then the provider can inspect all=
 VoIP traffic from different subscribers by only set condition 48~51 bit eq=
ual to 0000. This variation of semantic
 prefix is also helpful.</span></p></div></div></div></blockquote><div styl=
e>[Qiong] I have little concern for this variation. For operators who can n=
ot fully control of subscriber&#39;s CPE, this solution may have trust issu=
e, and it may get conflict with other CPE&#39;s allocation policy. But it i=
s ok for operators who can fully control of subscriber&#39;s CPE.</div>

<div style><br></div><div style>Best wishes</div><div style>Qiong</div><div=
 style><br></div><div style><br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div l=
ang=3D"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:break-word"=
>

<div><div class=3D"im">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
</div><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0c=
m 0cm 4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> Ted Lemon [mailto:<a href=3D"mailto:Ted.Lemon@nominum=
.com" target=3D"_blank">Ted.Lemon@nominum.com</a>]
<br></span></p><div class=3D"im">
<b>Sent:</b> Friday, May 31, 2013 3:29 AM<br>
<b>To:</b> Owen DeLong<br>
<b>Cc:</b> Sheng Jiang; <a href=3D"mailto:draft-jiang-v6ops-semantic-prefix=
@tools.ietf.org" target=3D"_blank">draft-jiang-v6ops-semantic-prefix@tools.=
ietf.org</a>; <a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.=
org</a>; &lt;<a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6ops@ietf=
.org</a>&gt;<br>


</div><div class=3D"im"><b>Subject:</b> Re: [v6ops] Could IPv6 address be m=
ore than locator?//draft-jiang-v6ops-semantic-prefix-03<u></u><u></u></div>=
<p></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On May 30, 2013, at 12:08 PM, O=
wen DeLong &lt;<a href=3D"mailto:owen@delong.com" target=3D"_blank">owen@de=
long.com</a>&gt; wrote:<u></u><u></u></span></p>
</div><div class=3D"im">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:13.5pt;font-=
family:&quot;Optima&quot;,&quot;serif&quot;">Not a great assumption... They=
 should need 4 million or more /48s since every subscriber is at least one =
end site and every subscriber end site should receive a /48.<u></u><u></u><=
/span></p>


</div>
</blockquote>
</div></div><div class=3D"im">
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I am not in love with using bit=
s from prefixes as semantic tags. =C2=A0 However, having said that, I think=
 it&#39;s a bit ironic that you&#39;re talking about wasting space with sem=
antic bits, on the one hand, and talking about the
 need for a /48 in every home on the other. =C2=A0 It would be perfectly re=
asonable for the ISP to specify that some of the bits in the /48 have seman=
tic meaning, for example, and given that we think it&#39;s okay to give the=
 home network a /48, we are hardly in a position
 to quibble about how the bits in that /48 are used.</span><span lang=3D"EN=
-US" style=3D"color:#1f497d"><u></u><u></u></span></p>
</div>
</div></div>
</div>
</div>

<br>_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/v6ops</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=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=3D=3D=3D=3D=3D=3D<br>Qiong Sun<br>C=
hina Telecom Beijing Research Institude<br><br><br>Open source code:<br>lig=
htweight 4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/" targ=
et=3D"_blank">http://sourceforge.net/projects/laft6/</a></i><br>

PCP-natcoord:<i> <a href=3D"http://sourceforge.net/projects/pcpportsetdemo/=
" target=3D"_blank">http://sourceforge.net/projects/pcpportsetdemo/</a> </i=
><br>=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=3D=3D=3D=3D=3D=3D=3D<br=
><br>
</div></div>

--bcaec50162330658ad04ddfb735f--

From martin@millnert.se  Thu May 30 23:48:45 2013
Return-Path: <martin@millnert.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172EA21F9123; Thu, 30 May 2013 23:48:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.603
X-Spam-Level: 
X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rQzvH8jEhoJ; Thu, 30 May 2013 23:48:44 -0700 (PDT)
Received: from ncis.csbnet.se (smtp.millnert.se [IPv6:2a02:9a0:100:2:5054:ff:feb8:99a4]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9EB21F919D; Thu, 30 May 2013 23:48:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id 6282E7596; Fri, 31 May 2013 08:37:26 +0200 (CEST)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vP9oc8eUlGUD; Fri, 31 May 2013 08:37:26 +0200 (CEST)
Received: from [10.140.114.24] (unknown [91.143.127.196]) by ncis.csbnet.se (Postfix) with ESMTPSA id 5A50493; Fri, 31 May 2013 08:37:25 +0200 (CEST)
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4960C9F-F0C8-4F19-9CE4-F17E4FB5556F@millnert.se>
X-Mailer: iPad Mail (10B329)
From: Martin Millnert <martin@millnert.se>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Date: Fri, 31 May 2013 08:48:40 +0200
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailman-Approved-At: Fri, 31 May 2013 00:07:46 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 06:48:45 -0000

Hi Sheng,

For reference, Deutsche Telekom's Peter L=C3=B6thberg brainchild-project Ter=
astream puts locally significant information in IPv6 addresses (recreating s=
ome sort of label switching/routing). It's currently being deployed in Croat=
ia.

Regards,
Martin

On 29 maj 2013, at 09:06, Sheng Jiang <jiangsheng@huawei.com> wrote:

> IP addresses are designed as topology locator, so that every packet can be=
 routed to its network destination.
>=20
> However, even in IPv4 era, some network operators have mapped their IP add=
ress with certain semantic locally. These kind of mechanism explicitly expre=
ss the semantic properties of every packet. Consequently, these network oper=
ators can inspect the properties of packets easily by mapping the addresses b=
ack to semantic.
>=20
> Network operators, who have large IPv6 address space, may also choose to e=
mbedded some semantics into IPv6 addresses by assigning additional significa=
nce to specific bits within the prefix. draft-jiang-v6ops-semantic-prefix do=
cuments a framework method that network operations may use their addresses w=
ith embedded semantics. These semantics bits are only meaningful within a si=
ngle network, or group of interconnected networks which share a common addre=
ssing policy. Based on these embedded semantic bits in source/destination ad=
dresses, the network operators can accordingly treat network packets differe=
ntly and efficiently.
>=20
> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>=20
> Could you please review this draft and comments? It will help the document=
 become more useful information to be shared.
>=20
> Best regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Tuesday, May 28, 2013 10:28 AM
>> To: Qiong Sun; Ian Farrer; Sheng Jiang; Boyang
>> Subject: New Version Notification for
>> draft-jiang-v6ops-semantic-prefix-03.txt
>>=20
>>=20
>> A new version of I-D, draft-jiang-v6ops-semantic-prefix-03.txt
>> has been successfully submitted by Sheng Jiang and posted to the
>> IETF repository.
>>=20
>> Filename:     draft-jiang-v6ops-semantic-prefix
>> Revision:     03
>> Title:         A Framework for Semantic IPv6 Prefix
>> Creation date:     2013-05-28
>> Group:         Individual Submission
>> Number of pages: 19
>> URL:
>> http://www.ietf.org/internet-drafts/draft-jiang-v6ops-semantic-prefix-03.=
txt
>> Status:
>> http://datatracker.ietf.org/doc/draft-jiang-v6ops-semantic-prefix
>> Htmlized:
>> http://tools.ietf.org/html/draft-jiang-v6ops-semantic-prefix-03
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-jiang-v6ops-semantic-prefix-03
>>=20
>> Abstract:
>>  This document describes a framework method that network operations
>>  may use their addresses.  Network operators, who have large IPv6
>>  address space, may choose to embedded some semantics into IPv6
>>  addresses by assigning additional significance to specific bits
>>  within the prefix.  By embedded semantics into IPv6 prefixes, the
>>  semantics of packets can be inspected easily.  Routers and other
>>  intermediary devices can easily apply relevant policies as required.
>>  Packet-level differentiation can also enable flow-level and user-
>>  level differentiation.  Consequently, the network operators can
>>  accordingly treat network packets differently and efficiently.  The
>>  management and maintenance of networks can be much simpler.
>>=20
>>=20
>>=20
>>=20
>> The IETF Secretariat
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From jiangsheng@huawei.com  Fri May 31 00:38:14 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C0E21F9289; Fri, 31 May 2013 00:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.456
X-Spam-Level: 
X-Spam-Status: No, score=-6.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ISgz9z6X6WN; Fri, 31 May 2013 00:38:10 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 47C5721F9425; Fri, 31 May 2013 00:38:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATJ26653; Fri, 31 May 2013 07:38:06 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 08:37:24 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 08:37:57 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 31 May 2013 15:37:51 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kc8GIAgACHYyD//5aGgIABdpag///LE4CAAJHXcA==
Date: Fri, 31 May 2013 07:37:50 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net>
In-Reply-To: <51A841B5.3010805@globis.net>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 07:38:14 -0000

Pj4+Pj4+IElQIGFkZHJlc3NlcyBhcmUgZGVzaWduZWQgYXMgdG9wb2xvZ3kgbG9jYXRvciwgc28g
dGhhdCBldmVyeSBwYWNrZXQgY2FuDQo+Pj4gYmUNCj4+Pj4+IHJvdXRlZCB0byBpdHMgbmV0d29y
ayBkZXN0aW5hdGlvbi4NCj4+Pj4+PiBIb3dldmVyLCBldmVuIGluIElQdjQgZXJhLCBzb21lIG5l
dHdvcmsgb3BlcmF0b3JzIGhhdmUgbWFwcGVkIHRoZWlyDQo+SVANCj4+Pj4+IGFkZHJlc3Mgd2l0
aCBjZXJ0YWluIHNlbWFudGljIGxvY2FsbHkuIFRoZXNlIGtpbmQgb2YgbWVjaGFuaXNtIGV4cGxp
Y2l0bHkNCj4+Pj4+IGV4cHJlc3MgdGhlIHNlbWFudGljIHByb3BlcnRpZXMgb2YgZXZlcnkgcGFj
a2V0LiBDb25zZXF1ZW50bHksIHRoZXNlDQo+Pj4gbmV0d29yaw0KPj4+Pj4gb3BlcmF0b3JzIGNh
biBpbnNwZWN0IHRoZSBwcm9wZXJ0aWVzIG9mIHBhY2tldHMgZWFzaWx5IGJ5IG1hcHBpbmcgdGhl
DQo+Pj4+PiBhZGRyZXNzZXMgYmFjayB0byBzZW1hbnRpYy4NCj4+Pj4+PiBOZXR3b3JrIG9wZXJh
dG9ycywgd2hvIGhhdmUgbGFyZ2UgSVB2NiBhZGRyZXNzIHNwYWNlLCBtYXkgYWxzbw0KPmNob29z
ZQ0KPj4+IHRvDQo+Pj4+PiBlbWJlZGRlZCBzb21lIHNlbWFudGljcyBpbnRvIElQdjYgYWRkcmVz
c2VzIGJ5IGFzc2lnbmluZyBhZGRpdGlvbmFsDQo+Pj4+PiBzaWduaWZpY2FuY2UgdG8gc3BlY2lm
aWMgYml0cyB3aXRoaW4gdGhlIHByZWZpeC4NCj4+Pj4+IGRyYWZ0LWppYW5nLXY2b3BzLXNlbWFu
dGljLXByZWZpeCBkb2N1bWVudHMgYSBmcmFtZXdvcmsgbWV0aG9kIHRoYXQNCj4+Pj4+IG5ldHdv
cmsgb3BlcmF0aW9ucyBtYXkgdXNlIHRoZWlyIGFkZHJlc3NlcyB3aXRoIGVtYmVkZGVkIHNlbWFu
dGljcy4NCj4+PiBUaGVzZQ0KPj4+Pj4gc2VtYW50aWNzIGJpdHMgYXJlIG9ubHkgbWVhbmluZ2Z1
bCB3aXRoaW4gYSBzaW5nbGUgbmV0d29yaywgb3IgZ3JvdXAgb2YNCj4+Pj4+IGludGVyY29ubmVj
dGVkIG5ldHdvcmtzIHdoaWNoIHNoYXJlIGEgY29tbW9uIGFkZHJlc3NpbmcgcG9saWN5Lg0KPkJh
c2VkDQo+Pj4gb24NCj4+Pj4+IHRoZXNlIGVtYmVkZGVkIHNlbWFudGljIGJpdHMgaW4gc291cmNl
L2Rlc3RpbmF0aW9uIGFkZHJlc3NlcywgdGhlDQo+Pj4gbmV0d29yaw0KPj4+Pj4gb3BlcmF0b3Jz
IGNhbiBhY2NvcmRpbmdseSB0cmVhdCBuZXR3b3JrIHBhY2tldHMgZGlmZmVyZW50bHkgYW5kDQo+
ZWZmaWNpZW50bHkuDQo+Pj4+Pj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtamlh
bmctdjZvcHMtc2VtYW50aWMtcHJlZml4LTAzDQo+Pj4+Pj4NCj4+Pj4+PiBDb3VsZCB5b3UgcGxl
YXNlIHJldmlldyB0aGlzIGRyYWZ0IGFuZCBjb21tZW50cz8gSXQgd2lsbCBoZWxwIHRoZQ0KPj4+
IGRvY3VtZW50DQo+Pj4+PiBiZWNvbWUgbW9yZSB1c2VmdWwgaW5mb3JtYXRpb24gdG8gYmUgc2hh
cmVkLg0KPj4+Pj4+IEJlc3QgcmVnYXJkcywNCj4+Pj4+Pg0KPj4+Pj4+IFNoZW5nDQo+Pj4+Pj4N
Cj4+Pj4+IEkgY29tcGxldGVseSB1bmRlcnN0YW5kIHRoZSBkZXNpcmUgZm9yIG9wZXJhdG9ycyB0
byBoYXZlIGFkZGl0aW9uYWwNCj4+Pj4+IHNlbWFudGljcyBhdmFpbGFibGUgZm9yIGN1c3RvbWl6
ZWQgcGFja2V0IHByb2Nlc3NpbmcuIEZsb3cgbGFiZWwgbm93DQo+aGFzDQo+Pj4+PiB2ZXJ5IGxp
bWl0ZWQgcHJvcGVydGllcyBvcHRpbWlzZWQgZm9yIGxvYWQgYmFsYW5jZXJzLiBEU0NQIG9ubHkg
aGFzIGENCj4+Pj4+IGZldyBiaXRzICh3YXkgbGVzcyB0aGFuIHRoZSBudW1iZXIgb2YgY3VzdG9t
ZXJzJyBwb2xpY2llcykuIEFDTHMgYXJlDQo+Pj4+PiBoZWF2eSB0byBwcm9jZXNzIGF0IGVhY2gg
aG9wLi4uLg0KPj4+Pj4NCj4+Pj4+IEJ1dCB3b3VsZG4ndCB0aGlzIGluZm9ybWF0aW9uIGJlIGJl
dHRlciBvZmYgZW5jb2RlZCBhcyB0YWdzIGluIG9uZSBvcg0KPj4+Pj4gbW9yZSBob3AtYnktaG9w
IGhlYWRlciBvcHRpb25zICh0aGF0IGNvdWxkIGJlIHJlLXdyaXR0ZW4gb24gdGhlIGZseSksDQo+
Pj4+PiByYXRoZXIgdGhhbiBlbmNvZGVkIGluIHRoZSBJUHY2IGFkZHJlc3Mgc3BhY2U/DQo+Pj4+
IFRoZSBzZWN0aW9uIDQuMSAiSnVzdGlmY2F0aW9uIGZvciBTZW1hbnRpY3Mgd2l0aCB0aGUgSVB2
NiBQcmVmaXgiIGRlc2NyaWJlcw0KPj4+IHRoZSByZWFzb25zLg0KPj4+PiBVc2VycyBtYXkgZWFz
aWx5IGNoYW5nZSB0aGUgc2V0dGluZyBvZiBleHRlbnNpb24gaGVhZGVyIGluIG9yZGVyIHRvDQo+
b2J0YWluDQo+Pj4gdW5kZXNlcnZlZCBwcmlvcml0aWVzL3ByaXZpbGVnZXMuIFNlbWFudGljIHBy
ZWZpeCBhcHByb2FjaCBkb2VzIHJlcXVpcmUgdGhlDQo+Pj4gZGVwbG95bWVudCBvZiBhY2Nlc3Mg
Y29udHJvbCBmaWx0ZXJzLiBUaGUgcGFja2V0cyB3aXRoIHRoZSBub25jb21wbGlhbmNlDQo+Pj4g
c291cmNlIGFkZHJlc3NlcyBzaG91bGQgYmUgZmlsdGVyZWQuIFRoZSBwcmVmaXggaXMgZGVsZWdh
dGVkIGJ5IHRoZQ0KPm5ldHdvcmsuDQo+Pj4gVGhlcmVmb3JlIHRoZSBuZXR3b3JrIGlzIGFibGUg
dG8gZGV0ZWN0IGFueSB1bmRlc2lyZWQgbW9kaWZpY2F0aW9ucyBhbmQNCj5maWx0ZXINCj4+PiB0
aGUgcGFja2V0IGFjY29yZGluZ2x5Lg0KPj4+PiBDaGVlcnMsDQo+Pj4+DQo+Pj4+IFNoZW5nDQo+
Pj4+DQo+Pj4+DQo+Pj4gSSBkb24ndCBidXkgeW91ciBqdXN0aWZpY2F0aW9uLiBXaGV0aGVyIGFu
IG9wZXJhdG9yIGZpbHRlcnMgb24NCj4+PiBhdXRob3Jpc2VkIGFkZHJlc3MgcmFuZ2Ugb3IgcmUt
d3JpdGVzL2ZpbHRlcnMgYW4gdW5hdXRob3Jpc2VkIGhvcC1ieS1ob3ANCj4+PiB0YWcgaXMgZWZm
ZWN0aXZlbHkgdGhlIHNhbWUgSU1ITy4gV2UgaGF2ZSBleGFjdGx5IHRoZSBzYW1lIGlzc3VlcyBv
Zg0KPj4+IHBvdGVudGlhbCB0aGVmdCBvZiBzZXJ2aWNlIHdpdGggRFNDUCB0b2RheSwgYW5kIHRo
ZSBzb2x1dGlvbiBpcyBlcXVhbGx5DQo+Pj4gc2ltcGxlOiBEU0NQIG1hcmtkb3duIGF0IHRoZSBp
bmdyZXNzIHBvcnQuDQo+Pg0KPj4gWWVzLCB0aGUgdHJ1c3QgaXNzdWUgaXMgdGhlIHNhbWUgd2l0
aCBEU0NQLiBIb3dldmVyLCB0aGUgRFNDUCBhYnN0cmFjdCBhbGwNCj50aGUgc2VtYW50aWNzIGlu
dG8gc2VydmljZSBjbGFzc2VzLCB3aGljaCBpcyBvbmUgc2luZ2xlIGRpbWVuc2lvbi4gVGhpcw0K
PmFic3RyYWN0IHByb2Nlc3NpbmcgaGFzIGxvc3QgYSBsb3Qgb2YgaW5mb3JtYXRpb24sIHdoaWNo
IHByb3ZpZGVycyB3YW50IHRvDQo+aW5zcGVjdCBmb3IgZXZlcnkgcGFja2V0LCB0aGVuIHByb2Nl
c3MgdGhlIHBhY2tldCBhY2NvcmRpbmdseS4gVGhlIGV4cGxpY2l0bHkNCj5leHByZXNzZWQgc2Vt
YW50aWNzIGluIHByZWZpeCBwcm92aWRlcyBtdWNoIG1vcmUgaW5mb3JtYXRpb25zDQo+Pg0KPj4g
U2hlbmcNCj4+DQo+Pj4gcmVnYXJkcywNCj4+PiBSYXlIDQo+Pg0KPldoaWNoIGlzIHdoeSBJIHdy
b3RlICJ3b3VsZG4ndCB0aGlzIGluZm9ybWF0aW9uIGJlIGJldHRlciBvZmYgZW5jb2RlZCBhcw0K
PnRhZ3MgaW4gb25lIG9yIG1vcmUgaG9wLWJ5LWhvcCBoZWFkZXIgb3B0aW9ucz8iIGFuZCBub3Qg
anVzdCAiZ28gYW5kIHVzZQ0KPkRTQ1AiDQo+DQo+SSBjb250ZW5kIHRoYXQgaG9wIGJ5IGhvcCBv
cHRpb25zIGFjdGluZyBhcyB0YWdzIHdvdWxkOg0KPg0KPjEpIGJlIHRoZSBjb3JyZWN0IGFuZCBs
b2dpY2FsIHBsYWNlIHRvIHRyYW5zcG9ydCBzdWNoIGluZm9ybWF0aW9uDQo+DQo+MikgYmUgY2Fw
YWJsZSBvZiBoYW5kbGluZyBtdWx0aXBsZSBzZW1hbnRpY3Mgc2ltdWx0YW5lb3VzbHkNCj4NCj4z
KSBub3QgdW5uZWNlc3NhcmlseSB3YXN0ZS9yZXNlcnZlIElQdjYgYWRkcmVzcyBzcGFjZSwgd2hp
Y2ggaXMgbGFyZ2UsDQo+YnV0IG5vdCBpbmZpbml0ZQ0KPg0KPjQpIGhhdmUgbXVjaCBtb3JlIGlu
Zm9ybWF0aW9uIGNhcnJ5aW5nIGNhcGFjaXR5IHRoYW4gYSBzbWFsbCBhbmQgZml4ZWQNCj5udW1i
ZXIgb2YgYml0cyBzdG9sZW4gZnJvbSB0aGUgSVB2NiBwcmVmaXgNCj5Zb3VyIGV4YW1wbGUgaW4g
QXBwZW5kaXggQSBzaG93cyAxMiBiaXRzIG9mIGluZm9ybWF0aW9uIHdpdGggb25seSAzIGJpdHMN
Cj5hdmFpbGFibGUgcGVyIHR5cGUgb2Ygc2VtYW50aWMgYml0cy4gSSBzdXNwZWN0IGl0IHdpbGwg
YmUgaW1wb3NzaWJsZSB0bw0KPmFncmVlIG9uIGEgc3RhbmRhcmQgZGl2aXNpb24gb2YgMTIgYml0
cyB0aGF0IHdvcmtzIGZvciBldmVyeW9uZSwganVzdCBhcw0KPkRTQ1AgZ2V0cyBvdmVyd3JpdHRl
biBhdCBldmVyeSBBUyBib3VuZGFyeS4gV2hlcmVhcyBhIHNpbmdsZSBob3AgYnkgaG9wDQo+b3B0
aW9uIGhlYWRlciBoYXMgNCBvY3RldHMgYXMgYSBtaW5pbXVtIGFuZCBjYW4gYmUgZXh0ZW5kZWQg
YnkgYW5vdGhlciA4DQo+b2N0ZXRzIGlmIG5lY2Vzc2FyeS4NCj4NCj41KSBiZSBvcHRpb25hbDog
aWYgYSBwYXJ0aWN1bGFyIHRhZyBpc24ndCByZXF1aXJlZCBieSBhIHBhcnRpY3VsYXINCj5zZXNz
aW9uIG9yIG5vZGUgb3IgTEFOIG9yIHNpdGUsIHlvdSBkb24ndCBhZGQgaXQuDQo+UmF0aGVyIHRo
YW4gaGF2aW5nIGEgZml4ZWQgMTIgYml0cyBvZiBpbmZvcm1hdGlvbiBhcyBzdWdnZXN0ZWQgaW4N
Cj5hcHBlbmRpeCBBLCB5b3UgY291bGQgb25seSB0YWcgdGhvc2UgcHJvcGVydGllcyBuZWNlc3Nh
cnkgZm9yIHRoaXMNCj5wYWNrZXQgKHBlbmFsdHkgb2YgY291cnNlIGlzIHBvdGVudGlhbGx5IG1v
cmUgcGFyc2luZyBvbiB0aGUgZmx5LCBidXQNCj50aGF0IHRyYWRlIG9mZiBjYW4gYmUgZGlzY3Vz
c2VkIGUuZy4gYnkgZml4aW5nIHRoZSBvcHRpb24gbGVuZ3RoIGFzIHlvdQ0KPnN1Z2dlc3QpDQo+
DQo+VGhlIGNvbmNsdXNpb24gZnJvbSByZXBsaWVzIHRvIHRoZSBkcmFmdCBzbyBmYXIgd291bGQg
c2VlbSB0byByZWFkICJObywNCj5kb24ndCBkbyBpdCINCj4NCj5JIHdvdWxkIHRoZXJlZm9yZSBo
dW1ibHkgc3VnZ2VzdCB5b3UgY29uY2VudHJhdGUgbW9yZSBlZmZvcnQgb24NCj5kb2N1bWVudGlu
ZyBhIHByb2JsZW0gc3RhdGVtZW50IGRldGFpbGluZyB0aGUgcmVxdWlyZW1lbnRzIGZvciB0aGUN
Cj5zZW1hbnRpY3Mgb2YgdGFnZ2luZyB0aGF0IGFyZW4ndCBtZXQgYnkgdG9kYXkncyBzb2x1dGlv
bnMsIGFuZCB3aGljaCBhcmUNCj5tYWtpbmcgcGVvcGxlIHR1cm4gdG8gdGhpcyBhbHRlcm5hdGl2
ZSBvZiBwcmVmaXggZW5jb2RpbmcsIHJhdGhlciB0aGFuDQo+Zm9jdXNzaW5nIG9uIHRoZSBtZWNo
YW5pY3Mgb2YgaG93IHRvIGVuY29kZSB0aGUgc2VtYW50aWNzIGludG8gdGhlDQo+cHJlZml4LiBP
bmUgZXhhbXBsZSBJIGNhbiB0aGluayBvZiB3b3VsZCBiZSBCZWxsb3ZpbidzIGRpc3RyaWJ1dGVk
DQo+ZmlyZXdhbGxzIGFuZCBtYXJraW5nIG9mIHNlY3VyaXR5IHpvbmVzLg0KDQpIaSwgUmF5LA0K
DQpUaGFua3MgZm9yIHlvdXIgc3VnZ2VzdGlvbi4gSG9wLWJ5LWhvcCBoZWFkZXIgb3B0aW9ucyBt
YXkgYWxzbyBiZSBhbHRlcm5hdGl2ZSBmb3IgdGhpcy4gQnV0IGl0J3MgbW9yZSBkaWZmaWN1bHQg
dG8gdmVyaWZ5IGFuZCB0cnVzdCBpdC4gSWYgeW91IHdlcmUgZ29pbmcgdG8gcHJvcG9zZSBzdWNo
IG1lY2hhbmlzbSwgSSB3aWxsIGNvbnNpZGVyIHRvIGNvbnRyaWJ1dGUuIDopDQoNCkFjdHVhbGx5
LCBteSBtb3RpdmF0aW9uIGlzIE5PVCB0byBzZWxsIHRoaXMgbWVjaGFuaXNtIHRvIGFueW9uZS4g
TXkgb2JzZXJ2YXRpb24gaXMgc29tZSBuZXR3b3JrIG9wZXJhdG9ycywgYm90aCBJU1BzIGFuZCBl
bnRlcnByaXNlIG5ldHdvcmsgb3BlcmF0b3IsIGhhcyBzdWNoIGFkZHJlc3MgcGxhbiwgb3IgYWxy
ZWFkeSBpbiB1c2UuIFdlLCBhcyBJRVRGLCBjYW5ub3Qgc3RvcCB0aGVtLiBTbywgd2Ugc2hvdWxk
IGRvY3VtZW50IGFuZCBhbmFseXplIHRoaXMgbWVjaGFuaXNtLiBUaGlzIHNob3VsZCBnaXZlIHNv
bWUgaW5mb3JtYXRpb24gdG8gdGhlc2Ugd2hvIGhhdmUgbm90IG1hZGUgdGhlaXIgYWRkcmVzcyBw
bGFuIHlldCBvbiB3aGV0aGVyIHRoZXkgbWF5IGZvbGxvdyBvciBub3QuDQoNCkkgaGF2ZSB0byBh
ZG1pdCB0aGF0IHRoZSBjdXJyZW50IHN0cnVjdHVyZSBvZiB0aGlzIGRyYWZ0IG1vcmUgbGlrZSBh
IHByb3Bvc2FsIHJhdGhlciB0aGFuIGFuIGFuYWx5c2lzLiBJIHdpbGwgaW1wcm92ZSB0aGlzIGlu
IG5leHQgdXBkYXRlLg0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCj5yZWdhcmRzDQo+UmF5SA0K

From tjc@ecs.soton.ac.uk  Fri May 31 01:55:03 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D89121F9344; Fri, 31 May 2013 01:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level: 
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5xLNKtyDsAz; Fri, 31 May 2013 01:55:02 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 23D4521F9339; Fri, 31 May 2013 01:55:01 -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 r4V8sM9D020678; Fri, 31 May 2013 09:54:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4V8sM9D020678
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369990462; bh=Lj9mHNzjOjtoq2IRo+ftDiJ0CGU=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=CyFZaEEgcaZ86WgiHxmkD9mMcwEkgWH/EjxrEXfIKnx3fpOjEVYyulvCekYYDooMg hed//SQlm4BGWNYAqS3MB90TLAmSY2OfxuVdVSglR2rzGBfWVnHYSO8O8LBo0yEIGB ycPcX8dk+kacMsp83yQPhd0fR9YeOeskuOgAEKv0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4U9sM0430633418Yx ret-id none; Fri, 31 May 2013 09:54:22 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4V8sIO5032360 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 May 2013 09:54:19 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com>
Date: Fri, 31 May 2013 09:54:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|66f143221743f238c7214d3d388a1d6bp4U9sM03tjc|ecs.soton.ac.uk|257DD6F7-C63E-4A03-A0E5-46ADADCBBEC9@ecs.soton.ac.uk>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <257DD6F7-C63E-4A03-A0E5-46ADADCBBEC9@ecs.soton.ac.uk>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4U9sM043063341800; tid=p4U9sM0430633418Yx; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4V8sM9D020678
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 08:55:03 -0000

On 31 May 2013, at 08:37, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> Actually, my motivation is NOT to sell this mechanism to anyone. My =
observation is some network operators, both ISPs and enterprise network =
operator, has such address plan, or already in use. We, as IETF, cannot =
stop them. So, we should document and analyze this mechanism. This =
should give some information to these who have not made their address =
plan yet on whether they may follow or not.

Sheng, are those ISPs and enterprises already contributors within the =
IETF?  Can you say any more about who these are, and examples of the =
semantics actually being deployed?  I assume China Telecom and Deutsche =
Telekom are two of them.

As you say, at the moment the draft reads as a proposal, rather than an =
analysis of something already in use.  Some concrete examples may help.

Tim


From jiangsheng@huawei.com  Fri May 31 02:10:06 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF9321F9433; Fri, 31 May 2013 02:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.462
X-Spam-Level: 
X-Spam-Status: No, score=-6.462 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qi2KTQZbve9R; Fri, 31 May 2013 02:10:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9F43021F9425; Fri, 31 May 2013 02:09:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARY99373; Fri, 31 May 2013 09:09:58 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 10:09:18 +0100
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 31 May 2013 10:09:54 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.01.0323.007; Fri, 31 May 2013 17:09:51 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: RE: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXDsZXTVBYam7gkul8TB7nKV985kc8GIAgACHYyD//5aGgIABdpag///LE4CAAJHXcP//mI6AABDpg3A=
Date: Fri, 31 May 2013 09:09:51 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC99D6B@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <257DD6F7-C63E-4A03-A0E5-46ADADCBBEC9@ecs.soton.ac.uk> <EMEW3|66f143221743f238c7214d3d388a1d6bp4U9sM03tjc|ecs.soton.ac.uk|257DD6F7-C63E-4A03-A0E5-46ADADCBBEC9@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|66f143221743f238c7214d3d388a1d6bp4U9sM03tjc|ecs.soton.ac.uk|257DD6F7-C63E-4A03-A0E5-46ADADCBBEC9@ecs.soton.ac.uk>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 09:10:06 -0000

Pj4gQWN0dWFsbHksIG15IG1vdGl2YXRpb24gaXMgTk9UIHRvIHNlbGwgdGhpcyBtZWNoYW5pc20g
dG8gYW55b25lLiBNeQ0KPm9ic2VydmF0aW9uIGlzIHNvbWUgbmV0d29yayBvcGVyYXRvcnMsIGJv
dGggSVNQcyBhbmQgZW50ZXJwcmlzZSBuZXR3b3JrDQo+b3BlcmF0b3IsIGhhcyBzdWNoIGFkZHJl
c3MgcGxhbiwgb3IgYWxyZWFkeSBpbiB1c2UuIFdlLCBhcyBJRVRGLCBjYW5ub3Qgc3RvcA0KPnRo
ZW0uIFNvLCB3ZSBzaG91bGQgZG9jdW1lbnQgYW5kIGFuYWx5emUgdGhpcyBtZWNoYW5pc20uIFRo
aXMgc2hvdWxkIGdpdmUNCj5zb21lIGluZm9ybWF0aW9uIHRvIHRoZXNlIHdobyBoYXZlIG5vdCBt
YWRlIHRoZWlyIGFkZHJlc3MgcGxhbiB5ZXQgb24NCj53aGV0aGVyIHRoZXkgbWF5IGZvbGxvdyBv
ciBub3QuDQo+DQo+U2hlbmcsIGFyZSB0aG9zZSBJU1BzIGFuZCBlbnRlcnByaXNlcyBhbHJlYWR5
IGNvbnRyaWJ1dG9ycyB3aXRoaW4gdGhlIElFVEY/DQo+Q2FuIHlvdSBzYXkgYW55IG1vcmUgYWJv
dXQgd2hvIHRoZXNlIGFyZSwgYW5kIGV4YW1wbGVzIG9mIHRoZSBzZW1hbnRpY3MNCj5hY3R1YWxs
eSBiZWluZyBkZXBsb3llZD8gIEkgYXNzdW1lIENoaW5hIFRlbGVjb20gYW5kIERldXRzY2hlIFRl
bGVrb20gYXJlDQo+dHdvIG9mIHRoZW0uDQoNCkhpLCBUaW0sDQoNCkFjdHVhbGx5LCBpbiB0aGUg
YXBwZW5kaXhlcyB0aGVyZSBhcmUgb25lIGV4YW1wbGUgZm9yIElTUCBhbmQgb25lIGZvciBlbnRl
cnByaXNlLiBUaGUgZXhhbXBsZSBmb3IgSVNQIChBcHBlbmRpeCBBKSBpcyBtYWlubHkgYWJzdHJh
Y3RlZCBmcm9tIENoaW5hIFRlbGVjb20ncyBhZGRyZXNzIHBsYW4uIEFzIGZhciBhcyBJIGtub3cs
IENoaW5hIFRlbGVjb20gYW5kIENoaW5hIE1vYmlsZSBoYXZlIHZlcnkgc2ltaWxhciBhZGRyZXNz
IHBsYW4uIERldXRzY2hlIFRlbGVrb20ncyBwbGFuIGhhcyBtdWNoIG1vcmUgY29tcGxpY2F0ZWQg
c2VtYW50aWNzLCB3aGljaCBJIHBlcnNvbmFsbHkgdGhpbmsgaGFzIGJpZ2dlciB0ZWNobmljYWwg
Z2FwcyB0byBiZWNvbWUgZGVwbG95YWJsZS4gVGhlIGVudGVycHJpc2UgZXhhbXBsZSAoQXBwZW5k
aXggQikgaXMgYWJzdHJhY3RlZCBmcm9tIGFuIG9uZ29pbmcgcHJvamVjdCB0aGF0IGNvbm5lY3Qg
YWxsIHZpZGVvIG1vbml0b3JzIGluIGEgYmlnIGNpdHkgYW5kIHRoZWlyIHJlYWwtdGltZSB2aWRl
byBpbnRvIGFuIElQIGludHJhbmV0Lg0KDQo+QXMgeW91IHNheSwgYXQgdGhlIG1vbWVudCB0aGUg
ZHJhZnQgcmVhZHMgYXMgYSBwcm9wb3NhbCwgcmF0aGVyIHRoYW4gYW4NCj5hbmFseXNpcyBvZiBz
b21ldGhpbmcgYWxyZWFkeSBpbiB1c2UuICBTb21lIGNvbmNyZXRlIGV4YW1wbGVzIG1heSBoZWxw
Lg0KDQpJIGd1ZXNzIHRoZSBpbnRyb2R1Y3Rpb24gYW5kIGFic3RyYWN0IHNlY3Rpb25zIGhhdmUg
dG8gYmUgcmV3cml0dGVuIGZvciBiZXR0ZXIgZXhwbGFuYXRpb24uIEl0IGlzIG5vdyBtaXNsZWFk
aW5nIHNvIG11Y2guDQoNClRoYW5rcywNCg0KU2hlbmcNCg0KPlRpbQ0KDQo=

From v6ops@globis.net  Fri May 31 02:46:51 2013
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E66821F92E3; Fri, 31 May 2013 02:46:51 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EWX9ncsCt5Qr; Fri, 31 May 2013 02:46:50 -0700 (PDT)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8E36621F91CA; Fri, 31 May 2013 02:46:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B84998700E7; Fri, 31 May 2013 11:46:34 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DdSoy4EKvjy; Fri, 31 May 2013 11:46:34 +0200 (CEST)
Received: from Rays-iMac-2.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 881D2870076; Fri, 31 May 2013 11:46:34 +0200 (CEST)
Message-ID: <51A87174.3080204@globis.net>
Date: Fri, 31 May 2013 11:46:28 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Martin Millnert <martin@millnert.se>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se>
In-Reply-To: <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 09:46:51 -0000

> Martin Millnert <mailto:martin@millnert.se>
> 31 May 2013 11:14
> Hi,
>
> On 31 maj 2013, at 09:37, Sheng Jiang <jiangsheng@huawei.com> wrote:
> <snip>
> <snip>
>
> Extra headers is a no-go for efficient FIB-lookup and thus a waste of
> time in many aspects to standardize.
>
> My 2 cents.
>
> Regards,
> Martin

I was suggesting looking at using a tag option within an existing header
(the hop by hop header), which theoretically is already processed by all
nodes along the path. So new options rather than a new header.

Whether we encode these additional semantics via an address match, or a
DSCP match, or a hop by hop approach, I agree the tag has to be found
and parsed and processed, so it would seem sensible to me to avoid
unnecessarily overloading existing semantics and instead to encode it in
the position in the packet where you'd expect to find something meant
for hop by hop processing i.e. the hop by hop header.

If operators don't want to process the hop by hop header in the network
core for whatever reason, draft-carpenter-6man-ext-transmit already
proposes allowing skipping it. The alternatives: tagging in the address
structure, creating tunnels, and tagging by encapsulation e.g. MPLS,
also have significant pros and cons for both parsing and forwarding.

But why are people coming up with these schemes for encoding semantics
in the address prefixes in the first place? That's what I'd like to
understand first and foremost: what lack of functionality is
motivating/forcing these people to adopt such schemes?

regards,
RayH

From fernando@gont.com.ar  Fri May 31 03:54:01 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C5221F9691 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 03:54:01 -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=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+kn+mJvZamr for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 03:54:00 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9522B21F8629 for <6man@ietf.org>; Fri, 31 May 2013 03:53:55 -0700 (PDT)
Received: from b00150.krakowskiinternet.pl ([91.231.45.150] helo=[192.168.1.160]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UiMxk-0002L8-0V; Fri, 31 May 2013 12:53:36 +0200
Message-ID: <51A8812E.9090309@gont.com.ar>
Date: Fri, 31 May 2013 12:53:34 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Dave Thaler <dthaler@microsoft.com>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com> <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com> <51A77038.9000706@si6networks.com> <e342a259f6bf4ed38b1247ed98cc2fdd@BN1PR03MB267.namprd03.prod.outlook.com>
In-Reply-To: <e342a259f6bf4ed38b1247ed98cc2fdd@BN1PR03MB267.namprd03.prod.outlook.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Ray Hunter <v6ops@globis.net>, Alissa Cooper <acooper@cdt.org>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 10:54:01 -0000

On 05/30/2013 06:09 PM, Dave Thaler wrote:
>> Isn't it enough simply noting that the target node can be probed?
>> Getting into the specific details of the probe packet
>> (stimulus/response) seems like "over-specifying" things to me...
> 
> My opinion is that this example is important, since the example is
> one where there's nothing the target node itself can do about it,
> which is non-obvious.   Otherwise readers could be as confused as
> I was.  So pointing it out adds significant clarity.

Ok. Will do.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From Ted.Lemon@nominum.com  Fri May 31 04:37:51 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA2D21F9371; Fri, 31 May 2013 04:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.559
X-Spam-Level: 
X-Spam-Status: No, score=-106.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nL9ABe5ZLvVo; Fri, 31 May 2013 04:37:44 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6A32421F9344; Fri, 31 May 2013 04:37:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUaiLiIpB+lUnTKZsB/lR1B5SxT0mZ8RP@postini.com; Fri, 31 May 2013 04:37:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E367E1B81BF; Fri, 31 May 2013 04:37:43 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D8151190052; Fri, 31 May 2013 04:37:43 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 31 May 2013 04:37:43 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ray Hunter <v6ops@globis.net>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXd9SQdyBVa+4iEqfP8l0AGeJNJkfgQsAgAAfFYA=
Date: Fri, 31 May 2013 11:37:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BE653@mbx-01.win.nominum.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se> <51A87174.3080204@globis.net>
In-Reply-To: <51A87174.3080204@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EEA8F39916C16E4CAB06596B34E599F2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Martin Millnert <martin@millnert.se>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 11:37:51 -0000

On May 31, 2013, at 5:46 AM, Ray Hunter <v6ops@globis.net> wrote:
> I was suggesting looking at using a tag option within an existing header
> (the hop by hop header), which theoretically is already processed by all
> nodes along the path. So new options rather than a new header.

Right, but the hop-by-hop header doesn't exist unless you add it, and it ca=
n't be processed on the fast path.   It's useful for networks where there _=
is_ no fast path (e.g., llns), but not so useful for the applications we're=
 talking about here (e.g., VoIP).

> But why are people coming up with these schemes for encoding semantics
> in the address prefixes in the first place? That's what I'd like to
> understand first and foremost: what lack of functionality is
> motivating/forcing these people to adopt such schemes?

This is a good question to be asking.


From nalini.elkins@insidethestack.com  Fri May 31 05:32:31 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF99A21F92FC for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 05:32:31 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yn-SoEcijCtW for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 05:32:26 -0700 (PDT)
Received: from nm24.access.bullet.mail.sp2.yahoo.com (nm24.access.bullet.mail.sp2.yahoo.com [98.139.44.151]) by ietfa.amsl.com (Postfix) with ESMTP id A109021F905F for <6man@ietf.org>; Fri, 31 May 2013 05:32:26 -0700 (PDT)
Received: from [98.139.44.102] by nm24.access.bullet.mail.sp2.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
Received: from [98.139.44.64] by tm7.access.bullet.mail.sp2.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
Received: from [127.0.0.1] by omp1001.access.mail.sp2.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 506419.47031.bm@omp1001.access.mail.sp2.yahoo.com
Received: (qmail 30163 invoked by uid 60001); 31 May 2013 12:32:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1370003545; bh=HgHo37lAk7szLYDhe0d9pgrS39AxORZF3xTKCRLbCXY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=sR+maXKJJKUl9F9zVrBofByo1bVtZW0UQ8wp7Szx+UUyUXUHUcRCipAz5MmD6lN8pYPSjshslKtKl4Nxfve2FqWVruNsZ5PVvjpvMBjWpBQh1kp6AzQEKjhumrhIzTMJkrf+ZIC25H4wwGcCIfrRda/oT2gDdY/7d7CWSKgNRrY=
X-YMail-OSG: raSX900VM1kPcRHjVeM1d.RScdbzcf3Fg3GlLvGLVRgqIuF wemwhq03WSe7C5c_ydiKpYbCCWBnAfPcdTM9fi29P6RhD7JdEuXkLT1HsldD 9fpwA7jre4BKFLuiQCxwNuIkfPewU_Lip9RgTqN4FFQYeg6013hgscSUN4ii yV_FYOSvm9nMjWythrWUzauW4s9oFgRnZRWL0_K1lcnT1IpPqyujo.kYniYB ZeNxBv9MYxqnVWm5CJNwcwUNLdb9hkzkQo8LGmcSQoRZEUGXo8t8TVtsTy_3 KExJ9sfVA0OqDUebtYQkA4kRUoHB7JJ8bl7gnTPOxC2O0J6_Vs3CxBT50f37 pLkWGc5peLHPsXjsmHZNztwo3gCWSM3cRtpMOh0p_8JjxY7sDmNKX64M4dDy XqVe3WZGjlI9IC3kBVwq1R.0qmTfDkFjxrTn0SLoLus6NIE18oBaiX3BO.PP iBhPaNmqqNYJ9gTo38uCLJbRRtWbJ6Is9.WrT1XVCfhyy0n.9kHG.hLqCpeO Sv72owmROyOaw8.yVOHPH3ehF5RbLxW9LhaMwOSzY0bfgXDKUFiakGNAwJ_5 fScPH.ktO9IFVs2uU6Yofi0JepWGa_KXb_ECdjXYcIbOYKxMfmcQiPukiDoh MBZXEqxmBlOtDuYc8tt0ty_0KN1lgACwaIgq9.w3vXRbDGG0au5aNQWvox5u cbmp.e8GM8yQP2.CUcpqpNSmcNXm8AOa2g26geEWZEjkzApAfVaXintfsiRw X0UqNSxEVoMo-
Received: from [24.130.37.147] by web2806.biz.mail.ne1.yahoo.com via HTTP; Fri, 31 May 2013 05:32:25 PDT
X-Rocket-MIMEInfo: 002.001, QWxsLAoKUGxlYXNlIGNvbW1lbnQgb24gYSBuZXcgRGVzdGluYXRpb24gT3B0aW9uIHRoYXQgd2UgYXJlIHByb3Bvc2luZzoKCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWVsa2lucy02bWFuLWlwdjYtcGRtLWRlc3Qtb3B0aW9uLwoKVGhlcmUgYXJlIHR3byBkb2N1bWVudHMgd2hpY2ggZ2l2ZSB0aGUgYmFja2dyb3VuZDoKCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWVsa2lucy12Nm9wcy1pcHY2LWVuZC10by1lbmQtcnQtbmVlZGVkLwoKCmh0dHBzOi8vZGEBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.145.547
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com> <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com> <51A77038.9000706@si6networks.com> <e342a259f6bf4ed38b1247ed98cc2fdd@BN1PR03MB267.namprd03.prod.outlook.com> <51A8812E.9090309@gont.com.ar>
Message-ID: <1370003545.24023.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Date: Fri, 31 May 2013 05:32:25 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: New PDM Destination Option Proposed
To: "6man@ietf.org" <6man@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <51A8812E.9090309@gont.com.ar>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1510626085-1457027007-1370003545=:24023"
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 12:32:31 -0000

--1510626085-1457027007-1370003545=:24023
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

All,=0A=0APlease comment on a new Destination Option that we are proposing:=
=0A=0Ahttps://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pdm-dest-opti=
on/=0A=0AThere are two documents which give the background:=0A=0Ahttps://da=
tatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-end-rt-needed/=0A=0A=
=0Ahttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequence=
-needed/=0A=0A=0AAnd one which gives the recommended usage of this destinat=
ion option:=0A=0Ahttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-p=
dm-recommended-usage/=0A=0AWe will be contacting the 6Man chairs to get on =
the agenda for Berlin.=0A=0A=A0=0AThanks,=0A=0A=0ANalini Elkins=0AInside Pr=
oducts, Inc.=0A(831) 659-8360=0Awww.insidethestack.com
--1510626085-1457027007-1370003545=:24023
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div>All,</div><div><br></div><d=
iv style=3D"background-color: transparent;">Please comment on a new Destina=
tion Option that we are proposing:</div><div style=3D"background-color: tra=
nsparent;"><br></div><div style=3D"background-color: transparent;"><span><a=
 rel=3D"nofollow" target=3D"_blank" href=3D"https://datatracker.ietf.org/do=
c/draft-elkins-6man-ipv6-pdm-dest-option/" style=3D"color: rgb(40, 98, 197)=
; outline: 0px;">https://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pd=
m-dest-option/</a></span></div><div style=3D"background-color: transparent;=
"><br></div><div style=3D"background-color: transparent;">There are two doc=
uments which give the background:</div><div style=3D"background-color: tran=
sparent;"><br></div><div style=3D"background-color: transparent;"><a rel=3D=
"nofollow" target=3D"_blank"
 href=3D"https://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-en=
d-rt-needed/" style=3D"color: rgb(40, 98, 197); outline: 0px;">https://data=
tracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-end-rt-needed/</a><br><=
/div><div style=3D"background-color: transparent;"><br></div><div style=3D"=
background-color: transparent;"><a rel=3D"nofollow" target=3D"_blank" href=
=3D"https://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequenc=
e-needed/" style=3D"color: rgb(40, 98, 197); outline: 0px;">https://datatra=
cker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequence-needed/</a><br></=
div><div style=3D"background-color: transparent;"><br></div><div style=3D"b=
ackground-color: transparent;">And one which gives the recommended usage of=
 this destination option:</div><div style=3D"background-color: transparent;=
"><br></div><div></div><div><a rel=3D"nofollow" target=3D"_blank" href=3D"h=
ttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-pdm-recommended-usa=
ge/" style=3D"color:
 rgb(40, 98, 197); outline: 0px; font-size: 12pt;">https://datatracker.ietf=
.org/doc/draft-elkins-v6ops-ipv6-pdm-recommended-usage/</a></div><div><br><=
/div><div><span></span></div><div>We will be contacting the 6Man chairs to =
get on the agenda for Berlin.</div><div><br></div><div></div><div>&nbsp;</d=
iv><div>Thanks,<br><br></div><div>Nalini Elkins<br>Inside Products, Inc.<br=
>(831) 659-8360<br>www.insidethestack.com<br><br>  <div style=3D"font-famil=
y: arial, helvetica, sans-serif; font-size: 12pt;"> <div style=3D"font-fami=
ly: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div di=
r=3D"ltr"> </div><div class=3D"y_msg_container"><br></div> </div> </div>  <=
/div></div></body></html>
--1510626085-1457027007-1370003545=:24023--

From nalini.elkins@insidethestack.com  Fri May 31 05:32:31 2013
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD8221F8FB3 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 05:32:31 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuJuNEENh8cw for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 05:32:31 -0700 (PDT)
Received: from nm7.access.bullet.mail.mud.yahoo.com (nm7.access.bullet.mail.mud.yahoo.com [66.94.237.208]) by ietfa.amsl.com (Postfix) with ESMTP id CB45C21F91A5 for <ipv6@ietf.org>; Fri, 31 May 2013 05:32:26 -0700 (PDT)
Received: from [66.94.237.200] by nm7.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
Received: from [66.94.237.104] by tm11.access.bullet.mail.mud.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
Received: from [127.0.0.1] by omp1009.access.mail.mud.yahoo.com with NNFMP; 31 May 2013 12:32:26 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 155015.70841.bm@omp1009.access.mail.mud.yahoo.com
Received: (qmail 30163 invoked by uid 60001); 31 May 2013 12:32:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1370003545; bh=HgHo37lAk7szLYDhe0d9pgrS39AxORZF3xTKCRLbCXY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=sR+maXKJJKUl9F9zVrBofByo1bVtZW0UQ8wp7Szx+UUyUXUHUcRCipAz5MmD6lN8pYPSjshslKtKl4Nxfve2FqWVruNsZ5PVvjpvMBjWpBQh1kp6AzQEKjhumrhIzTMJkrf+ZIC25H4wwGcCIfrRda/oT2gDdY/7d7CWSKgNRrY=
X-YMail-OSG: raSX900VM1kPcRHjVeM1d.RScdbzcf3Fg3GlLvGLVRgqIuF wemwhq03WSe7C5c_ydiKpYbCCWBnAfPcdTM9fi29P6RhD7JdEuXkLT1HsldD 9fpwA7jre4BKFLuiQCxwNuIkfPewU_Lip9RgTqN4FFQYeg6013hgscSUN4ii yV_FYOSvm9nMjWythrWUzauW4s9oFgRnZRWL0_K1lcnT1IpPqyujo.kYniYB ZeNxBv9MYxqnVWm5CJNwcwUNLdb9hkzkQo8LGmcSQoRZEUGXo8t8TVtsTy_3 KExJ9sfVA0OqDUebtYQkA4kRUoHB7JJ8bl7gnTPOxC2O0J6_Vs3CxBT50f37 pLkWGc5peLHPsXjsmHZNztwo3gCWSM3cRtpMOh0p_8JjxY7sDmNKX64M4dDy XqVe3WZGjlI9IC3kBVwq1R.0qmTfDkFjxrTn0SLoLus6NIE18oBaiX3BO.PP iBhPaNmqqNYJ9gTo38uCLJbRRtWbJ6Is9.WrT1XVCfhyy0n.9kHG.hLqCpeO Sv72owmROyOaw8.yVOHPH3ehF5RbLxW9LhaMwOSzY0bfgXDKUFiakGNAwJ_5 fScPH.ktO9IFVs2uU6Yofi0JepWGa_KXb_ECdjXYcIbOYKxMfmcQiPukiDoh MBZXEqxmBlOtDuYc8tt0ty_0KN1lgACwaIgq9.w3vXRbDGG0au5aNQWvox5u cbmp.e8GM8yQP2.CUcpqpNSmcNXm8AOa2g26geEWZEjkzApAfVaXintfsiRw X0UqNSxEVoMo-
Received: from [24.130.37.147] by web2806.biz.mail.ne1.yahoo.com via HTTP; Fri, 31 May 2013 05:32:25 PDT
X-Rocket-MIMEInfo: 002.001, QWxsLAoKUGxlYXNlIGNvbW1lbnQgb24gYSBuZXcgRGVzdGluYXRpb24gT3B0aW9uIHRoYXQgd2UgYXJlIHByb3Bvc2luZzoKCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWVsa2lucy02bWFuLWlwdjYtcGRtLWRlc3Qtb3B0aW9uLwoKVGhlcmUgYXJlIHR3byBkb2N1bWVudHMgd2hpY2ggZ2l2ZSB0aGUgYmFja2dyb3VuZDoKCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWVsa2lucy12Nm9wcy1pcHY2LWVuZC10by1lbmQtcnQtbmVlZGVkLwoKCmh0dHBzOi8vZGEBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.145.547
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <d42e3a94ecc2441da5106ded00c92f9a@BY2PR03MB269.namprd03.prod.outlook.com> <51A204F2.7060400@si6networks.com> <7047d3011cea40a4979aed6ab339b515@BY2PR03MB269.namprd03.prod.outlook.com> <51A77038.9000706@si6networks.com> <e342a259f6bf4ed38b1247ed98cc2fdd@BN1PR03MB267.namprd03.prod.outlook.com> <51A8812E.9090309@gont.com.ar>
Message-ID: <1370003545.24023.YahooMailNeo@web2806.biz.mail.ne1.yahoo.com>
Date: Fri, 31 May 2013 05:32:25 -0700 (PDT)
From: Nalini Elkins <nalini.elkins@insidethestack.com>
Subject: New PDM Destination Option Proposed
To: "6man@ietf.org" <6man@ietf.org>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
In-Reply-To: <51A8812E.9090309@gont.com.ar>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1510626085-1457027007-1370003545=:24023"
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Nalini Elkins <nalini.elkins@insidethestack.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 12:32:32 -0000

--1510626085-1457027007-1370003545=:24023
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

All,=0A=0APlease comment on a new Destination Option that we are proposing:=
=0A=0Ahttps://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pdm-dest-opti=
on/=0A=0AThere are two documents which give the background:=0A=0Ahttps://da=
tatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-end-rt-needed/=0A=0A=
=0Ahttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequence=
-needed/=0A=0A=0AAnd one which gives the recommended usage of this destinat=
ion option:=0A=0Ahttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-p=
dm-recommended-usage/=0A=0AWe will be contacting the 6Man chairs to get on =
the agenda for Berlin.=0A=0A=A0=0AThanks,=0A=0A=0ANalini Elkins=0AInside Pr=
oducts, Inc.=0A(831) 659-8360=0Awww.insidethestack.com
--1510626085-1457027007-1370003545=:24023
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ar=
ial, helvetica, sans-serif;font-size:12pt"><div>All,</div><div><br></div><d=
iv style=3D"background-color: transparent;">Please comment on a new Destina=
tion Option that we are proposing:</div><div style=3D"background-color: tra=
nsparent;"><br></div><div style=3D"background-color: transparent;"><span><a=
 rel=3D"nofollow" target=3D"_blank" href=3D"https://datatracker.ietf.org/do=
c/draft-elkins-6man-ipv6-pdm-dest-option/" style=3D"color: rgb(40, 98, 197)=
; outline: 0px;">https://datatracker.ietf.org/doc/draft-elkins-6man-ipv6-pd=
m-dest-option/</a></span></div><div style=3D"background-color: transparent;=
"><br></div><div style=3D"background-color: transparent;">There are two doc=
uments which give the background:</div><div style=3D"background-color: tran=
sparent;"><br></div><div style=3D"background-color: transparent;"><a rel=3D=
"nofollow" target=3D"_blank"
 href=3D"https://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-en=
d-rt-needed/" style=3D"color: rgb(40, 98, 197); outline: 0px;">https://data=
tracker.ietf.org/doc/draft-elkins-v6ops-ipv6-end-to-end-rt-needed/</a><br><=
/div><div style=3D"background-color: transparent;"><br></div><div style=3D"=
background-color: transparent;"><a rel=3D"nofollow" target=3D"_blank" href=
=3D"https://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequenc=
e-needed/" style=3D"color: rgb(40, 98, 197); outline: 0px;">https://datatra=
cker.ietf.org/doc/draft-elkins-v6ops-ipv6-packet-sequence-needed/</a><br></=
div><div style=3D"background-color: transparent;"><br></div><div style=3D"b=
ackground-color: transparent;">And one which gives the recommended usage of=
 this destination option:</div><div style=3D"background-color: transparent;=
"><br></div><div></div><div><a rel=3D"nofollow" target=3D"_blank" href=3D"h=
ttps://datatracker.ietf.org/doc/draft-elkins-v6ops-ipv6-pdm-recommended-usa=
ge/" style=3D"color:
 rgb(40, 98, 197); outline: 0px; font-size: 12pt;">https://datatracker.ietf=
.org/doc/draft-elkins-v6ops-ipv6-pdm-recommended-usage/</a></div><div><br><=
/div><div><span></span></div><div>We will be contacting the 6Man chairs to =
get on the agenda for Berlin.</div><div><br></div><div></div><div>&nbsp;</d=
iv><div>Thanks,<br><br></div><div>Nalini Elkins<br>Inside Products, Inc.<br=
>(831) 659-8360<br>www.insidethestack.com<br><br>  <div style=3D"font-famil=
y: arial, helvetica, sans-serif; font-size: 12pt;"> <div style=3D"font-fami=
ly: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div di=
r=3D"ltr"> </div><div class=3D"y_msg_container"><br></div> </div> </div>  <=
/div></div></body></html>
--1510626085-1457027007-1370003545=:24023--

From martin@millnert.se  Fri May 31 02:14:40 2013
Return-Path: <martin@millnert.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BBE321F96F2; Fri, 31 May 2013 02:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rowEleqVrY-x; Fri, 31 May 2013 02:14:39 -0700 (PDT)
Received: from ncis.csbnet.se (smtp.millnert.se [IPv6:2a02:9a0:100:2:5054:ff:feb8:99a4]) by ietfa.amsl.com (Postfix) with ESMTP id AE0F421F9433; Fri, 31 May 2013 02:14:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id 41A9A7596; Fri, 31 May 2013 11:03:21 +0200 (CEST)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OUT5rgbT2t3; Fri, 31 May 2013 11:03:20 +0200 (CEST)
Received: from [172.16.58.216] (unknown [77.233.232.198]) by ncis.csbnet.se (Postfix) with ESMTPSA id 968F493; Fri, 31 May 2013 11:03:20 +0200 (CEST)
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se>
X-Mailer: iPad Mail (10B329)
From: Martin Millnert <martin@millnert.se>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Date: Fri, 31 May 2013 11:14:36 +0200
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailman-Approved-At: Fri, 31 May 2013 07:25:29 -0700
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 09:14:40 -0000

Hi,

On 31 maj 2013, at 09:37, Sheng Jiang <jiangsheng@huawei.com> wrote:
<snip>
> Hi, Ray,
>=20
> Thanks for your suggestion. Hop-by-hop header options may also be alternat=
ive for this.
<snip>

Extra headers is a no-go for efficient FIB-lookup and thus a waste of time i=
n many aspects to standardize.=20

My 2 cents.

Regards,
Martin


From bingxuere@gmail.com  Fri May 31 07:02:32 2013
Return-Path: <bingxuere@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6C7421F8FEB; Fri, 31 May 2013 07:02:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[AWL=-0.898, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48ZGNU7633iD; Fri, 31 May 2013 07:02:27 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF3F21F8F83; Fri, 31 May 2013 07:02:27 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 10so2244305pdi.31 for <multiple recipients>; Fri, 31 May 2013 07:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=lkq6mdcf5vCjfHmfV9JixwN/j7lyb/2gCUwgQiJcGzI=; b=J1OuERpRjpnVoVGh8K+wBW54mUSGvJOrjB7kfkx2Kf7a7lPozU14FKDB+xRYNfElU6 dzYhBNmIPOoB9ydoe8r66GPoGHJghgXmIJlwpphEZ5O4ldrls6hxojFFvj1vHt4MWtK1 hRvn/nE70ZM0IJqwK2+b/Xlfii/pJ+WV/zatKhK+2D2ymKHZF/FAzYdG8KuSdmj5OC8u WsGrPLETcvq13IwVMlc9wuropvS+szzQ469n4uT63Eeep852VJ2d0t55SXkc5KVMKd6C kbp+enkCC8nPD6cVZV2khRxGjSpl0eOqZLbGK1PnQV4yxkBg3FuCuE0RjBTX+l9CyD98 nUoQ==
X-Received: by 10.66.248.228 with SMTP id yp4mr13627185pac.158.1370008944836;  Fri, 31 May 2013 07:02:24 -0700 (PDT)
Received: from [10.4.128.172] ([61.148.242.239]) by mx.google.com with ESMTPSA id l4sm46865651pbo.6.2013.05.31.07.02.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 07:02:23 -0700 (PDT)
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se> <51A87174.3080204@globis.net> <8D23D4052ABE7A4490E77B1A012B6307751BE653@mbx-01.win.nominum.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BE653@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <4EF22CF5-7BF1-4FF5-8696-C3EC2CEC3427@gmail.com>
X-Mailer: iPad Mail (10A8500)
From: "bingxuere@gmail.com" <bingxuere@gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Date: Fri, 31 May 2013 22:02:12 +0800
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailman-Approved-At: Fri, 31 May 2013 07:25:29 -0700
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 14:02:33 -0000

Hi Ted and all,

On 2013-5-31, at 19:37, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On May 31, 2013, at 5:46 AM, Ray Hunter <v6ops@globis.net> wrote:
>> I was suggesting looking at using a tag option within an existing header
>> (the hop by hop header), which theoretically is already processed by all
>> nodes along the path. So new options rather than a new header.
>=20
> Right, but the hop-by-hop header doesn't exist unless you add it, and it c=
an't be processed on the fast path.   It's useful for networks where there _=
is_ no fast path (e.g., llns), but not so useful for the applications we're t=
alking about here (e.g., VoIP).
>=20
>> But why are people coming up with these schemes for encoding semantics
>> in the address prefixes in the first place? That's what I'd like to
>> understand first and foremost: what lack of functionality is
>> motivating/forcing these people to adopt such schemes?
>=20
> This is a good question to be asking.
[Qiong] I'm trying to answer this question from operator's aspect. When we a=
re trying to encode semantics e.g service type, subscriber type, etc., in so=
me flag, it should have the following features:
1) It should exist and be encoded from the beginning. Otherwise, we still ne=
ed to introduce dpi-related system to identify certain services, which I bel=
ieve is not scalable.
2) It cannot be changed along the path. Otherwise, there will be trust issue=
 and may be changed to a different value without notice.
3) It can be easily treated in existing routers. In the ideal way, it does n=
ot need to introduce new functionality so that all our existing routers can d=
eal with it. This can greatly reduce our upgrading cost.
These are major reasons that we embed semantics in prefixes.  But I'm still o=
pen suggestions if there is a better choice.

Best wishes
Qiong
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From fgont@si6networks.com  Fri May 31 15:20:23 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A7F721F8FDD for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 15:20:22 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A1Y8NcKpDzNp for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 15:20:21 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 8961721F901B for <6man@ietf.org>; Fri, 31 May 2013 15:20:15 -0700 (PDT)
Received: from abll8.neoplus.adsl.tpnet.pl ([83.7.205.8] helo=[192.168.1.116]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UiXfZ-0002Vc-VL; Sat, 01 Jun 2013 00:19:34 +0200
Message-ID: <51A921F2.2040401@si6networks.com>
Date: Sat, 01 Jun 2013 00:19:30 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Revision of draft-ietf-6man-stable-privacy-addresses
References: <51990CE7.7010903@si6networks.com> <4D6C62EB-AE9F-4B73-A274-D1BF5E92ABEC@apple.com> <5199331B.7060000@si6networks.com> <59BBAF36-4DF5-4877-A9B9-112A6DC72D3E@apple.com> <519949B2.8000409@si6networks.com> <B9FAF44E-81E8-4DF7-B135-B316C96EC0D1@apple.com> <519963BF.9010700@si6networks.com> <65C2C74A-E0C4-4E1F-A72E-5DFBCA038309@apple.com> <519AD550.3050005@gont.com.ar> <EB427E67-E67E-421D-8466-313F2F6C0453@ecs.soton.ac.uk> <EMEW3|32101a301b8e63d6bd300ab5a68c5cecp4L9oY03tjc|ecs.soton.ac.uk|EB427E67-E67E-421D-8466-313F2F6C0453@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|32101a301b8e63d6bd300ab5a68c5cecp4L9oY03tjc|ecs.soton.ac.uk|EB427E67-E67E-421D-8466-313F2F6C0453@ecs.soton.ac.uk>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 6man@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 22:20:23 -0000

Hi, Tim,

On 05/22/2013 10:50 AM, Tim Chown wrote:
> 
> On 21 May 2013, at 03:00, Fernando Gont <fernando@gont.com.ar> wrote:
>>
>> Additionally, I'd like to better understand the stability properties of
>> UUIDs (and add some text about it right after the text that you have
>> suggested). My assumption is that one would have UUIDs for network
>> interfaces that would, at least, be constant across system bootstrap
>> sequences? (that would be something not yet present in OS X now, but
>> that could be added as part of the implementation of this specification?)
> 
> Hi Fernando, you may wish to look at RFC 6355 about that and similar issues.

FWIW, I've referenced RFC4122, which seems to be a more general document
on UUIDs (I got the reference to RFC4122 in RFC6355 :-) )

Thanks s much!

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





From fgont@si6networks.com  Fri May 31 15:36:37 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A61A21F8B04 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 15:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xjSqrans0iUT for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 15:36:35 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id DE32021F8F7A for <6man@ietf.org>; Fri, 31 May 2013 15:36:16 -0700 (PDT)
Received: from abll8.neoplus.adsl.tpnet.pl ([83.7.205.8] helo=[192.168.1.116]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UiXv8-0003BM-Ky; Sat, 01 Jun 2013 00:35:38 +0200
Message-ID: <51A925B3.4060709@si6networks.com>
Date: Sat, 01 Jun 2013 00:35:31 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519C46F2.8040406@si6networks.com> <ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <EMEW3|f20e38499b955ff19bf14c71bf316deap4LEJn03tjc|ecs.soton.ac.uk|ACF99238-1B5B-44CE-8123-82A9CC7874FF@ecs.soton.ac.uk> <519EBBA7.5080300@si6networks.com> <41CFFE39-9488-4C75-B37A-C6306EA895BB@ecs.soton.ac.uk> <EMEW3|48d469f3a8488f633442e393c2d10dbfp4NEN003tjc|ecs.soton.ac.uk|41CFFE39-9488-4C75-B37A-C6306EA895BB@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|48d469f3a8488f633442e393c2d10dbfp4NEN003tjc|ecs.soton.ac.uk|41CFFE39-9488-4C75-B37A-C6306EA895BB@ecs.soton.ac.uk>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org Chairs" <6man-chairs@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 31 May 2013 22:36:37 -0000

On 05/24/2013 03:22 PM, Tim Chown wrote:
> 
>> I've tweaked the text a bit in the hopes that readers don't get the
>> impression that I'm arguing against use of RFC4941. (Most likely,
>> by the time you read this I'll have posted version -08... so please
>> check that one... and if there's still room for improvement in this
>> area, I could post a -09 version based on your suggestions).
> 
> OK, I simply think that you were implying that because many 
> enterprises will want to/try to disable 4941, that this was an 
> argument for using stable privacy addresses.  In my view, I would 
> certainly use stable privacy *and* 4941.

I would use stable privacy and RFC 4941, too.

What I tried to convey in the text was something like "we need to
improve the stable addresses. This scheme have these benefits, which
complement those of rfc4941... That aside, in those scenarios where
rfc4941 is disabled, implementing this will bring you these benefits,
and provide an interesting trade-off for folks that disable rfc4941".

Me, i'm in favor of having stable privacy + RFC 4941. Applications are
in a better position of deciding which type of address is better for
them. But I understand that folks operating e.g. enterprise networks may
have valid reasons to disable rfc4941.



>>> "other information collectors", I guess you mean sites running 
>>> services, e.g. typically through web server logs.
>> 
>> This was borrowed from RFC 4941. -- anything to tweak here?
> 
> Maybe just add an example, ", e.g. such as addresses in web server 
> logs, included in email headers, etc".

Ok, done.



>>> Not sure what the point about inferring that temporary addresses 
>>> are in use buys you.
>> 
>> If you know that they are temporary addresses, you will expect
>> them to change. On the other hand, if temporary addresses looked
>> exactly the same as stable addresses, you'd have to figure out
>> whether they are different nodes, or the same node with a new
>> temporary address.
> 
> OK, that's an advantage, but you could still deduce something from 
> the addresses that change, and whether the address is used as a 
> source or destination address.

Agreed.



[context: talking about mac-based addreses not used much in practice]
>> 
>> The problem here is that once the stable address (or, more 
>> specifically, its IID) becomes known to an attacker, you can be 
>> subject to host-tracking by active probing. The stable IID might 
>> become known to an attacker because at some point in time you 
>> advertised that IPv6 address, but also because you e.g. shared a 
>> network with an attacker.
>> 
>> A simple example is that if we attend the same 
>> conference/cafe/whatever and you could learn my stable IID (based 
>> on my MAC address). Then you check the headers of my emails, and 
>> learn the v6 prefixes of the networks I typically connect to. And, 
>> after that, you could tell whether I am online by polling 
>> KnownPrefixes|IID.
>> 
>> An you shouldn't need a firewall to prevent *this*. Actually, 
>> strictly speaking, the fireall won't prevent this: you can still 
>> probe the node in different ways that the firewall won't block.
> 
> Sure, the above was just an example. But Dave has a point, that if 
> you have a default inbound policy at the edge, this type of exposure 
> is unlikely, at least from network probes. 

Would relying on something that is not under your control be a wise
thing to do?


> A similar argument to 
> having protection against externally sourced ND exhaustion attacks 
> the same way.  It may be worth stating this in the draft, as I'm
> sure others will point this out in the same way Dave has.

I'm of the idea that if your implementations suffers from ND exhaustion
attacks, you should fix it. -- Temporary mitigations are okay (operators
need a quick fix they can apply now), as long as the origin of the
problem is tackled, too.


>>> The comment about MS Windows should perhaps be more orthogonal. A
>>> node IID may be manually configured, it may use DHCP, it may use
>>> SLAAC with IEEE identifiers, it may use your method, it may use
>>> the method MS Windows uses, or it may even use the tokenised 
>>> identifier method that I posted a while ago.  It can use any of 
>>> those, AND use 4941 as well.  But saying "such implementations 
>>> would not be affected by the method" doesn't sound quite right.
>> 
>> The point I was trying to make is that traditional slaac (in terms 
>> of # of nodes) is not as widely deployed as one would expect.
> 
> Ah, OK.  I must run your script on my address samples some time :)

Please do. :-) -- BTW, ISOC's Mat Ford did, already (have you seen it?).



>>> Section 7:
>>> 
>>> Maybe clarify that the first bullet point is for inbound 
>>> connections only.
>> 
>> That's correct if this is implemented along RFC4941. However, if 
>> this is implemented without RFC4941, this method still prevents 
>> such trivial host tracking.
> 
> OK, I always assume the former, but I appreciate many prefer to 
> disable 4941 where they can.

I personally think that we should improve the stable addresses. And for
my client node, I'd use RFC 4941, too.

Improving the stable addresses help both the guys that do rfc4941, *and*
the guys that don't.


>>> How does your RA "attack" work in practice here?  Do you mean 
>>> issuing a rogue RA for the same prefix?  We should perhaps
>>> assume that robust rogue RA protection is in place, and if not
>>> there are many worse things an attacker can do!
>> 
>> Agreed. I added this attack vector description, since it was 
>> described by Christian Huitema... so I added it for completeness 
>> sake. Should I twek the text? Remove it?
> 
> I have no strong view, just noting that if a network permits rogue 
> RAs, much worse things can happen.

Agreed.



>>> Perhaps note/remind here that RFC4862 says to run DAD per prefix
>>>  (section 5.4).
>> 
>> mmmm... not sure what you mean.
> 
> For each different IID generated.  Currently implementations *might* 
> assume the IID is the same for link-local and global via traditional 
> SLAAC.  RFC4862 notes that you should run DAD on all addresses.

I'd have no problem with adding this. However, isn't it a *requirement*
to do that, already?


>>> B.1.3 Worth any consideration of MIPv6 here?
>> 
>> It has been years since I last checked MIPv6 (and when I did, I 
>> mostly just skimmed through it). So... up to you. :-)
> 
> Well, nor me, but if you run MIPv6 you're by design wanting to be 
> reachable by a persistent address. I guess at the very least you can 
> say your method can apply when forming the Home Address during the 
> initial bootstrap with the Home Agent. And when the host roams and 
> gets a Care-of Address, the IID used to form the CoA at each visited 
> network will be different, and different to the IID used for the
> HoA. This I guess would reduce trackability as you roam, but would be
> good for a MIP guru to comment.

Will try to find one, and ask for input.

Thanks!

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





From fernando@gont.com.ar  Fri May 31 17:23:41 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E66121F8E6E for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 17:23:41 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRBlvgr5V4Me for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 17:23:40 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id DD8A821F8E37 for <6man@ietf.org>; Fri, 31 May 2013 17:23:38 -0700 (PDT)
Received: from ablo153.neoplus.adsl.tpnet.pl ([83.7.208.153] helo=[192.168.1.122]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UiZbH-0005Vq-KS; Sat, 01 Jun 2013 02:23:15 +0200
Message-ID: <51A93EEE.7080902@gont.com.ar>
Date: Sat, 01 Jun 2013 02:23:10 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: Comments on draft-ietf-6man-stable-privacy-addresses-07
References: <72fb5db097d443eebb554cdc43d7a01f@BY2PR03MB269.namprd03.prod.outlook.com> <519AD0EF.60600@si6networks.com> <87b8552e4b4a479dbfca94bd88a09ce7@BY2PR03MB269.namprd03.prod.outlook.com> <519F3364.80301@si6networks.com> <AB3E7E6E-4E70-4A8E-AD39-37D1A11DB47B@cdt.org> <51A207B0.4000900@si6networks.com> <BE92F20E-0AE2-40D3-8637-16F9869869B6@cdt.org>
In-Reply-To: <BE92F20E-0AE2-40D3-8637-16F9869869B6@cdt.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, Brian Haberman <brian@innovationslab.net>, "6man@ietf.org" <6man@ietf.org>, Dave Thaler <dthaler@microsoft.com>, Ray Hunter <v6ops@globis.net>, Christian Huitema <huitema@microsoft.com>, "tom.petch" <cfinss@dial.pipex.com>, Fernando Gont <fgont@si6networks.com>, He Xuan <xhe@hitachi.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 00:23:41 -0000

On 05/28/2013 11:07 PM, Alissa Cooper wrote:
>>> The second group of three are for nodes that only use temporary 
>>> addresses (but that also configure a stable address that never
>>> gets used). This is what would be expected by users that want to
>>> avoid correlation attacks, assuming their admins allow it. In
>>> this case random and random-per-network provide equivalent
>>> protection.
>> 
>> The problem here is that the assumption of "never gets used" is
>> not correct. Or, well, you might argue "is not intentionally used
>> for legitimate purposes".
>> 
> 
> Intentionally used is what I was going for, since some of the
> discussion about the choice of address generation mechanism revolves
> around intention. That is, some implementations/users might choose
> temporary addresses for specific reasons, sys admins might choose to
> disable them for specific reasons, etc.

IMO, there's a big difference between e.g. RFC4941-disabled vs.
RFC4941-not-used (e.g. as a result of default source address selection).
(the same applies to other combinations).

As noted in stable-privacy, an attacker can leverage e.g. the MAC-based
addresses even if RFC4941 are implemented, enabled, and preferred.



>> An attacker can trigger the use of such addresses, e.g., y sending
>> his probe packets to the stable address.
> 
> In the case of a node that only intentionally uses temporary
> addresses, are there other uses you envision of that node's stable
> address besides the attacks in (a) and (b) in the table?

Not sure what you mean.  Attack (c) employs the stable addresses, too.



>>> (row 2). If we're talking about the case where a node can use 
>>> temporary addresses and only uses them, random and
>>> random-per-network provide the same benefits (rows 5 and 6). I'm
>>> assuming those are the two common cases (could be wrong though).
>> 
>> Please see above.
> 
> Not sure what this means -- in terms of the user's intent, I assume
> most users intend to either use a stable address all the time or use
> temporary addresses all the time.

Not necessarily: the policy might be conveyed by the application.

BTW, what's "random"? -- Microsoft approach to stable addresses, or what?



>>> Not sure if this is helpful to anyone else, but it clarified my 
>>> thinking on this a bit, and it might be worth making the threat 
>>> analysis in the draft more specific along these lines.
>> 
>> How about including something along these lines (*) in an
>> Appendix?
>> 
>> (*) Discussion of possible attacks, and what stable privacy
>> addresses do about them (analyzing this for every possible address
>> generation mechanism would be out of scope for this I-D, IMO).
> 
> Agreed. However, even with the appendix, there are still some places
> where the discussion of the threat models in section 1 could be
> clearer, IMO. For example:
> 
> However, even with temporary addresses [RFC4941] in place, preventing
> correlation of activities of a node within a network may be difficult
> (if at all possible) to achieve.  As a trivial example, consider a
> scenario where there is a single node (or a reduced number of nodes)
> connected to a specific network.  An attacker could detect new
> addresses in use at that network, an infer which addresses are being
> employed by which hosts.  This task is made particularly easier by
> the fact that use of "temporary addresses" can be easily inferred
> (since the follow different patterns from that of traditional SLAAC
> addresses), and since they are re-generated periodically (i.e., after
> a specific amount of time has elapsed).

(FWIW, I moved the above text to Appendix B).



> My read of this is that you're talking about either (1) a situation
> where a node has a globally unique prefix,

Not sure what you mean.


> or (2) a situation where a
> small number of nodes share the same prefix and an attacker can
> disambiguate them using some other information about their behavior
> besides their IP addresses. 

Not sure what you mean by "other information"...


> Is that right? If that's the case, isn't
> correlation possible regardless of how the suffix is generated? The
> document seems to imply that nodes with temporary addresses are more
> susceptible to these two situations than nodes that use other address
> generation mechanisms,

No. The document just says that those attacks are still possible with
RFC4941 -- of course, they are possible without RF4941, too.



> when in fact the first situation (globally
> unique prefix) probably affects all nodes equally regardless of
> generation mechanism, and in the second situation the fact that
> temporary addresses refresh frequently might erect a barrier that
> makes correlation more difficult and that would not exist with random
> or random-per-network addresses.

Of course,  if you don't implement RFC5941, you don't even need to
analyze the address changes.

Again: The appendix just highlights attacks still present with RFC4941.
It does not imply that those attacks are not impossible with the
traditional IEEE-based addresses r with the Microsoft approach t stable
addresses-


> 
> Another point for clarification:
> 
> On the other hand, in scenarios in which "temporary addresses" are
> employed together with stable addresses such as those based on IEEE 
> identifiers, implementation of the mechanism described in this 
> document would mitigate address-scanning attacks and also mitigate 
> some vectors for correlating host activities that are not mitigated 
> by the use of temporary addresses.
> 
> Which correlation attack vectors do random-per-network addresses
> mitigate that temporary addresses do not? 

See appendix B of drat-ietf-6man-stable-privacy-addresses.




> In the analysis in column
> (d) of the table, the correlation entries are the same for all of the
> address generation mechanisms in cases where the node intentionally
> uses temporary addresses.

Agreed.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From Ted.Lemon@nominum.com  Fri May 31 19:23:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C111221F8B3D; Fri, 31 May 2013 19:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+6k2IIVYUDV; Fri, 31 May 2013 19:22:58 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 162B021F88FB; Fri, 31 May 2013 19:22:54 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUala/jrRr/8dltpX/lfnsYB4a1/X2ezb@postini.com; Fri, 31 May 2013 19:22:55 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3864E1B81D2; Fri, 31 May 2013 19:22:54 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2E61119005C; Fri, 31 May 2013 19:22:54 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 31 May 2013 19:22:54 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Owen DeLong <owen@delong.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOXm45WoMnwVBJ2U2+cujDGH1pcpkgllOA
Date: Sat, 1 Jun 2013 02:22:54 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BFE2D@mbx-01.win.nominum.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com> <65746D62-1F0E-4FAD-AC6A-270BD5757C8A@delong.com>
In-Reply-To: <65746D62-1F0E-4FAD-AC6A-270BD5757C8A@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751BFE2Dmbx01winnominum_"
MIME-Version: 1.0
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 02:23:06 -0000

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

On May 31, 2013, at 10:14 PM, Owen DeLong <owen@delong.com<mailto:owen@delo=
ng.com>> wrote:
The /48 is in order to allow 16 bits of space for automating the deployment=
 of hierarchy and routing within the end-site.

Right, which is ludicrous overkill, given that we have two different soluti=
ons for the problem of efficiently distributing prefixes in the home, neith=
er of which require 16 bits of prefix unless you have 64k distinct links in=
 the home.



--_000_8D23D4052ABE7A4490E77B1A012B6307751BFE2Dmbx01winnominum_
Content-Type: text/html; charset="us-ascii"
Content-ID: <8FD8C39946879F4F80BC70D4B45D7F72@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On May 31, 2013, at 10:14 PM, Owen DeLong &lt;<a href=3D"mailto:owen@d=
elong.com">owen@delong.com</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite">
<div style=3D"font-family: Optima; font-size: medium; font-style: normal; f=
ont-variant: normal; font-weight: normal; letter-spacing: normal; line-heig=
ht: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-tr=
ansform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-t=
ext-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
The /48 is in order to allow 16 bits of space for automating the deployment=
 of hierarchy and routing within the end-site.</div>
</blockquote>
<br>
</div>
<div>Right, which is ludicrous overkill, given that we have two different s=
olutions for the problem of efficiently distributing prefixes in the home, =
neither of which require 16 bits of prefix unless you have 64k distinct lin=
ks in the home.</div>
<div><br>
</div>
<br>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751BFE2Dmbx01winnominum_--

From lorenzo@google.com  Fri May 31 20:13:11 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1D821F8956 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 20:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mEGZrfmPzSC for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 20:13:10 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 8AAD621F84EF for <ipv6@ietf.org>; Fri, 31 May 2013 20:13:10 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id ih17so870566qab.7 for <ipv6@ietf.org>; Fri, 31 May 2013 20:13:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Jqk0N6pviClAItEl4TQNG1HIDE6A3prVWzbNS7pjCUg=; b=eK4hL7y6JrkvwJ3mQD8+tFacMPeD0dvt+IXfJ7gy3YldUGzuaB2s8bEOXhyYuYTy7C smAQq4DKwUw8sh9hdKFMb+Q0WaHaCjUtHVXdAJw3QQz7DHwM3V5AdFfAFFbaym98clfx brZi53fH/L0zeBpgcbDWEI/jvEYLK8DRf+fkL2np28mcO7L968TqvHSYhY6JjMPFnIfS JzKIApadJjAEB3pogLs0xwPW0LdZlc0OYpMomaa2c9PDbEsIZN8CJOJTQsLXaFY0dbiY cxeHJM9tSbduERLq/ADACcaQu/vgPH2lZuetEDYv/lKELivf94PQMmMBM7nIezpwkW5C KOxw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=Jqk0N6pviClAItEl4TQNG1HIDE6A3prVWzbNS7pjCUg=; b=Dx7QjeCluGNMkx8/F5Mu23WQ+umEYVlM6RSCo+lTDFPzoV90XYWuCAbQ+3VpCWRIsR m0LR1EXFodTWQO81C4+CioAdZQEpbSfyUDxGf58g/hNnTaGN7WpbCgLXxhbnXLHICqBi X1Blrw+CR3HCCqxQaIlcfQCKM6NqDwaeGXaZBofCAHc1d9ZXYFG2cjoWw12EaE2c2EfY UXw2VnG71TGHKrKa2f18OkGR4BKDu+eV1UjlcaU75Dgk7pCMnStZmc1JnoG9YtK+wSt0 eatuE4bdIYJDubR+EEIbUsFvT4o1rpHUALS46EQUBVc0+z05g7aIosnzgFHa7tu3mEni /eoQ==
X-Received: by 10.224.42.195 with SMTP id t3mr10962565qae.44.1370056389355; Fri, 31 May 2013 20:13:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.135.198 with HTTP; Fri, 31 May 2013 20:12:49 -0700 (PDT)
In-Reply-To: <4EF22CF5-7BF1-4FF5-8696-C3EC2CEC3427@gmail.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se> <51A87174.3080204@globis.net> <8D23D4052ABE7A4490E77B1A012B6307751BE653@mbx-01.win.nominum.com> <4EF22CF5-7BF1-4FF5-8696-C3EC2CEC3427@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sat, 1 Jun 2013 12:12:49 +0900
Message-ID: <CAKD1Yr2bChWu-wCCPvT8jJoGScwsqSwOif6v0DHWcBx_bgrOZQ@mail.gmail.com>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
To: "bingxuere@gmail.com" <bingxuere@gmail.com>
Content-Type: multipart/alternative; boundary=089e0160bbb26927fd04de0f1c22
X-Gm-Message-State: ALoCoQmYfZ5tw1iKzYK4vHRK+w+CUqweqVHpAaDo/jW1pKaDaIJ1ZgbE/IJWSjoCPjTx1t6HUASO8pTnVgPgM6KvZBuZGDyFVjo+pfriUX6nEtX3+0+XXbfD+zTZOg27qVjLL+GbJEYmhIUhHgZImXqTwWTQUlDZJF+vQrjcy33BVgl4536ufVlCk8YT6wRfEZzFg9uG3YWF
Cc: Ray Hunter <v6ops@globis.net>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 03:13:11 -0000

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

On Fri, May 31, 2013 at 11:02 PM, bingxuere@gmail.com
<bingxuere@gmail.com>wrote:

> [Qiong] I'm trying to answer this question from operator's aspect. When we
> are trying to encode semantics e.g service type, subscriber type, etc., in
> some flag, it should have the following features:
> 1) It should exist and be encoded from the beginning. Otherwise, we still
> need to introduce dpi-related system to identify certain services, which I
> believe is not scalable.
> 2) It cannot be changed along the path. Otherwise, there will be trust
> issue and may be changed to a different value without notice.
> 3) It can be easily treated in existing routers. In the ideal way, it does
> not need to introduce new functionality so that all our existing routers
> can deal with it. This can greatly reduce our upgrading cost.
> These are major reasons that we embed semantics in prefixes.  But I'm
> still open suggestions if there is a better choice.
>

DSCP does all of those today. All you need to do is ensure that you always
mark the packets on ingress.

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

<div dir=3D"ltr">On Fri, May 31, 2013 at 11:02 PM, <a href=3D"mailto:bingxu=
ere@gmail.com">bingxuere@gmail.com</a> <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:bingxuere@gmail.com" target=3D"_blank">bingxuere@gmail.com</a>&gt;</spa=
n> wrote:<br>

<div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">[Qiong] I&#39;m trying to answer this question from operator&#39;=
s aspect. When we are trying to encode semantics e.g service type, subscrib=
er type, etc., in some flag, it should have the following features:<br>


1) It should exist and be encoded from the beginning. Otherwise, we still n=
eed to introduce dpi-related system to identify certain services, which I b=
elieve is not scalable.<br>
2) It cannot be changed along the path. Otherwise, there will be trust issu=
e and may be changed to a different value without notice.<br>
3) It can be easily treated in existing routers. In the ideal way, it does =
not need to introduce new functionality so that all our existing routers ca=
n deal with it. This can greatly reduce our upgrading cost.<br>
These are major reasons that we embed semantics in prefixes. =A0But I&#39;m=
 still open suggestions if there is a better choice.<br></blockquote><div><=
br></div><div style>DSCP does all of those today. All you need to do is ens=
ure that you always mark the packets on ingress.=A0</div>

</div></div></div>

--089e0160bbb26927fd04de0f1c22--

From shane@castlepoint.net  Fri May 31 20:20:34 2013
Return-Path: <shane@castlepoint.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67F2D21F8E41 for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 20:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5dbZWScNGpW for <ipv6@ietfa.amsl.com>; Fri, 31 May 2013 20:20:28 -0700 (PDT)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 996F821F8AD5 for <ipv6@ietf.org>; Fri, 31 May 2013 20:20:27 -0700 (PDT)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id A0E20300079 for <ipv6@ietf.org>; Sat,  1 Jun 2013 03:20:27 +0000 (UTC)
Received: from mbp.castlepoint.net (184-96-123-182.hlrn.qwest.net [184.96.123.182]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id AF7BA300062; Fri, 31 May 2013 21:20:25 -0600 (MDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <51A87174.3080204@globis.net>
Date: Fri, 31 May 2013 21:20:23 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <708D821F-0EA0-44EE-AA5E-6321C7E73910@castlepoint.net>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <51A71ACA.3000608@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC994A0@nkgeml512-mbx.china.huawei.com> <51A733E1.7040008@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99A07@nkgeml512-mbx.china.huawei.com> <51A841B5.3010805@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AC99CF4@nkgeml512-mbx.china.huawei.com> <6B838546-4FB3-4EDB-9F84-D8CF0AF3080D@millnert.se> <51A87174.3080204@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1503)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Fri May 31 21:20:27 2013
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 51a9687b42076619113923
X-DSPAM-Factors: 27, 2013+at, 0.40000, encoding+semantics, 0.40000, Mime-Version*Mail+6.3, 0.40000, SP+able, 0.40000, to+#+#+#+an, 0.40000, trusted+If, 0.40000, But+#+#+#+coming, 0.40000, I'd+like, 0.40000, and+#+#+#+the, 0.40000, incoming+packets, 0.40000, incoming+packets, 0.40000, prefixes+#+#+first, 0.40000, such+#+1, 0.40000, 3+#+#+Ray, 0.40000, somehow+#+#+#+prefixes, 0.40000, to+#+#+#+enforce, 0.40000, an+#+#+IP, 0.40000, encoding+#+#+#+address, 0.40000, May+31, 0.40000, But+#+#+people, 0.40000, such+schemes, 0.40000, trust+and, 0.40000, packets+with, 0.40000, 3+46, 0.40000, foremost+what, 0.40000, foremost+#+lack, 0.40000, be+#+If, 0.40000
Cc: Martin Millnert <martin@millnert.se>, "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 03:20:34 -0000

Hi Sheng, Ray,

On May 31, 2013, at 3:46 AM, Ray Hunter <v6ops@globis.net> wrote:
[--snip--]
> But why are people coming up with these schemes for encoding semantics
> in the address prefixes in the first place? That's what I'd like to
> understand first and foremost: what lack of functionality is
> motivating/forcing these people to adopt such schemes?

+1. =20

In one part of the draft, Section 2.1, it appears to suggest that =
packets coming in to the border of an SP boundary are "untrusted", =
therefore existing packet header fields (e.g.: IPv6 TC) cannot be =
trusted.  If incoming packets are untrusted:
- why doesn't the SP deploy unicast RPF to drop incoming packets with an =
illegitimate source IP address/prefix?
- more importantly, how is an SP able to _trust_ and somehow enforce =
that the prefixes that it is handing out (dynamically via DHCP?) are =
being properly assigned according the policies governing the mapping of =
semantic prefix <-> user-type/application/security-domain/etc.?

-shane=


From owen@delong.com  Fri May 31 19:17:53 2013
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D40D21F8DDD; Fri, 31 May 2013 19:17:53 -0700 (PDT)
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.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8fmwZYhKhbe; Fri, 31 May 2013 19:17:52 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 10E6521F8CF4; Fri, 31 May 2013 19:17:51 -0700 (PDT)
Received: from [192.168.6.83] (ip-64-134-24-48.public.wayport.net [64.134.24.48]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r512ES4J008556 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 31 May 2013 19:14:31 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r512ES4J008556
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1370052874; bh=pysIzCnRrFRw0tONDGMTKfi0Xsc=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=gtUZlioDG1gTRaKYpSHYIsPUepLO2TzXx4Goax6O2Xj0Hx7ZCGZUF4aMjzbi+6JCo huK8Pi836V34Dv8Nz7VeNFypX6jaJFLcD7ws7DTYS1FN+iBher66S4OR6mpXu3iUoT MOxEZ2HTJw0GaWZe0J90jGJOey8hcqtCPJbXSqGs=
Content-Type: multipart/alternative; boundary="Apple-Mail=_B7579E1E-80E8-4B9D-973F-0E637B85058C"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Owen DeLong <owen@delong.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com>
Date: Fri, 31 May 2013 19:14:33 -0700
Message-Id: <65746D62-1F0E-4FAD-AC6A-270BD5757C8A@delong.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Fri, 31 May 2013 19:14:34 -0700 (PDT)
X-Mailman-Approved-At: Fri, 31 May 2013 21:27:43 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 02:17:53 -0000

--Apple-Mail=_B7579E1E-80E8-4B9D-973F-0E637B85058C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On May 30, 2013, at 12:29 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On May 30, 2013, at 12:08 PM, Owen DeLong <owen@delong.com> wrote:
>> Not a great assumption... They should need 4 million or more /48s =
since every subscriber is at least one end site and every subscriber end =
site should receive a /48.
>=20
> I am not in love with using bits from prefixes as semantic tags.   =
However, having said that, I think it's a bit ironic that you're talking =
about wasting space with semantic bits, on the one hand, and talking =
about the need for a /48 in every home on the  other.   It would be =
perfectly reasonable for the ISP to specify that some of the bits in the =
/48 have semantic meaning, for example, and given that we think it's =
okay to give the home network a /48, we are hardly in a position to =
quibble about how the bits in that /48 are used.
>=20

The /48 is in order to allow 16 bits of space for automating the =
deployment of hierarchy and routing within the end-site.

I wasn't specific about the nature of the end-site (home or otherwise, =
as I believe all end sites should be treated the same).

Taking away from those bits for ISP semantics (or some antics, depending =
on your perspective) is an entirely different can of worms.

Owen


--Apple-Mail=_B7579E1E-80E8-4B9D-973F-0E637B85058C
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 30, 2013, at 12:29 PM, Ted Lemon &lt;<a href="mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On May 30, 2013, at 12:08 PM, Owen DeLong &lt;<a href="mailto:owen@delong.com">owen@delong.com</a>&gt; wrote:</div>
<blockquote type="cite">
<div style="font-family: Optima; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
Not a great assumption... They should need 4 million or more /48s since every subscriber is at least one end site and every subscriber end site should receive a /48.</div>
</blockquote>
</div>
<br>
<div>I am not in love with using bits from prefixes as semantic tags. &nbsp; However, having said that, I think it's a bit ironic that you're talking about wasting space with semantic bits, on the one hand, and talking about the need for a /48 in every home on the
 other. &nbsp; It would be perfectly reasonable for the ISP to specify that some of the bits in the /48 have semantic meaning, for example, and given that we think it's okay to give the home network a /48, we are hardly in a position to quibble about how the bits
 in that /48 are used.</div>
<div><br>
</div>
</div>

</blockquote></div><br><div>The /48 is in order to allow 16 bits of space for automating the deployment of hierarchy and routing within the end-site.</div><div><br></div><div>I wasn't specific about the nature of the end-site (home or otherwise, as I believe all end sites should be treated the same).</div><div><br></div><div>Taking away from those bits for ISP semantics (or some antics, depending on your perspective) is an entirely different can of worms.</div><div><br></div><div>Owen</div><div><br></div></body></html>
--Apple-Mail=_B7579E1E-80E8-4B9D-973F-0E637B85058C--

From owen@delong.com  Fri May 31 19:48:04 2013
Return-Path: <owen@delong.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC41521F8EAE; Fri, 31 May 2013 19:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MiMrTr4O9BYW; Fri, 31 May 2013 19:48:04 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id EF83F21F8EAD; Fri, 31 May 2013 19:48:03 -0700 (PDT)
Received: from [192.168.6.83] (ip-64-134-24-48.public.wayport.net [64.134.24.48]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r512l0xU009137 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 31 May 2013 19:47:04 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r512l0xU009137
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1370054827; bh=zlditU8r2xm7zgLsGW0yBEC/mJY=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=J+aEq0OOeJxaLDS8zYA7OY/+gBCsi9W84a3Txa2Z4+TkClFLzTiUngGgWtCLBa8aX ozDmokvVISYWARl6gqSdGAV21wrqJ0J1QIxaTqLzRbdrVKAu6fTKEujVZO0LuPRF52 ybC/j9FZjKffqPyA+nYiHrxnQZkDYzRG7v3yzYaQ=
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E55564B-F1E1-4E70-8BB1-450BA7294A2B"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
From: Owen DeLong <owen@delong.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BFE2D@mbx-01.win.nominum.com>
Date: Fri, 31 May 2013 19:47:05 -0700
Message-Id: <F8A3E2C6-57B1-4276-93F8-86E962368182@delong.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC992D2@nkgeml512-mbx.china.huawei.com> <CAKD1Yr1c+-S02oWF1GjTdu-Vatee-EgXLKr=2=xdtYOtUubsYQ@mail.gmail.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99354@nkgeml512-mbx.china.huawei.com> <B001C1A1-DCF6-43AD-A792-56A58661E924@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BD21E@mbx-01.win.nominum.com> <65746D62-1F0E-4FAD-AC6A-270BD5757C8A@delong.com> <8D23D4052ABE7A4490E77B1A012B6307751BFE2D@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Fri, 31 May 2013 19:47:07 -0700 (PDT)
X-Mailman-Approved-At: Fri, 31 May 2013 21:27:43 -0700
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@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, 01 Jun 2013 02:48:05 -0000

--Apple-Mail=_9E55564B-F1E1-4E70-8BB1-450BA7294A2B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On May 31, 2013, at 7:22 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On May 31, 2013, at 10:14 PM, Owen DeLong <owen@delong.com> wrote:
>> The /48 is in order to allow 16 bits of space for automating the =
deployment of hierarchy and routing within the end-site.
>=20
> Right, which is ludicrous overkill, given that we have two different =
solutions for the problem of efficiently distributing prefixes in the =
home, neither of which require 16 bits of prefix unless you have 64k =
distinct links in the home.
>=20
>=20

Please explicate.

What solutions exist today that provide for the home of the future where =
there are, in fact, multiple levels of routers many of which are =
managing routers underneath them with multiple links attached?

How do these solutions adapt to arbitrary topologies and hierarchies as =
they are built in the home?

I've only seen such capabilities in early development stages. I haven't =
seen anything like it deployed in the wild.

Owen


--Apple-Mail=_9E55564B-F1E1-4E70-8BB1-450BA7294A2B
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 31, 2013, at 7:22 PM, Ted Lemon &lt;<a href="mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominum.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On May 31, 2013, at 10:14 PM, Owen DeLong &lt;<a href="mailto:owen@delong.com">owen@delong.com</a>&gt;&nbsp;wrote:</div>
<blockquote type="cite">
<div style="font-family: Optima; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
The /48 is in order to allow 16 bits of space for automating the deployment of hierarchy and routing within the end-site.</div>
</blockquote>
<br>
</div>
<div>Right, which is ludicrous overkill, given that we have two different solutions for the problem of efficiently distributing prefixes in the home, neither of which require 16 bits of prefix unless you have 64k distinct links in the home.</div>
<div><br>
</div>
<br>
</div>

</blockquote></div><br><div>Please explicate.</div><div><br></div><div>What solutions exist today that provide for the home of the future where there are, in fact, multiple levels of routers many of which are managing routers underneath them with multiple links attached?</div><div><br></div><div>How do these solutions adapt to arbitrary topologies and hierarchies as they are built in the home?</div><div><br></div><div>I've only seen such capabilities in early development stages. I haven't seen anything like it deployed in the wild.</div><div><br></div><div>Owen</div><div><br></div></body></html>
--Apple-Mail=_9E55564B-F1E1-4E70-8BB1-450BA7294A2B--
